Guest dwallersv Posted March 25, 2009 Report Posted March 25, 2009 So far i've tried this on 2 DXIa5 roms (Qbus and StevenH) and both worked perfectly. One more thing...when you check SRS settings, is it set to headphones or internal? I don't think it should matter...but make sure that there is something there. Sometimes QBus' rom causes it to go blank. On the 910 (stock firmware -- that's the only choice!) the output device dropdown is always blank after a reboot. Failing to re-set this to headphones will result in the hang issues when suspending. It must be set to "headphones" -- "internal" still causes hangs. It sounds aweful anyway, because it's intended for stereo speakers, which the Omnia doesn't have. I've tried playing with both the InitialSRSMode and DisableInternal registry values in the SRS settings with no success in altering this startup behavior. DisableInternal doesn't seem to do anything (at least with 0 or 1). InitialSRSMode will make the driver boot initialize to "Internal" if set to 1, but comes up blank with values 0 or 2. I didn't try any others -- there may be a magic value that initializes to headphones, but I'm too lazy to go through value/boot over and over again -- my phone takes a long time to boot with all my customizations. Anyone that wants to play with this, here are the reg keys: HKLM\Software\SRS\WOWHD\[btA2dpSnd,WaveDev]\[DisableInternal,InitialSRSMode] [] notation just means select one of the choices. The WaveDev key affects wired headphones, the Bt key bluetooth stereo.
Guest dwallersv Posted March 25, 2009 Report Posted March 25, 2009 S2U2 can auto lock the phone without having the phone hang. The MAIN issue with S2U2 is the Don't Suspend Power option which MUST be set to ON else it is guaranteed to freeze. As long as that is set to on for S2U2 users, the phone shouldn't hang. I am using QBus DXIA5's clean rom and am getting MUCH better battery life than i had previously with StevenH's DXIA5's (clean /2) rom. I understand. What I'm saying is that on my 910 -- which should be the same firmware as every 910 -- this limitation doesn't seem to be an issue. I deviated from your instructions and have S2U2 set to power off (i.e. suspend) after the power off timeout. I have the "but only blank screen" setting OFF. No hangs yet (except one that I'm pretty sure was caused by SpbBackup rebooting the phone overnight). So, with these S2U2 settings, I have the same functionality as if there were not a problem at all -- S2U2 suspends the phone for me, instead of the WM Power Cpl, and this seems to avoid the hang problem.
Guest Supadan Posted March 25, 2009 Report Posted March 25, 2009 I understand. What I'm saying is that on my 910 -- which should be the same firmware as every 910 -- this limitation doesn't seem to be an issue. I deviated from your instructions and have S2U2 set to power off (i.e. suspend) after the power off timeout. I have the "but only blank screen" setting OFF. No hangs yet (except one that I'm pretty sure was caused by SpbBackup rebooting the phone overnight). So, with these S2U2 settings, I have the same functionality as if there were not a problem at all -- S2U2 suspends the phone for me, instead of the WM Power Cpl, and this seems to avoid the hang problem. Ah sorry for the misunderstanding. It seems like i needa raise this question one more time...is anyones battery being drained due to the SRS? I know that the Input and Output makes a difference in system noises (ring tones, alerts, etc) and mine are maxed to help me achieve louder text alerts/call alerts. With StevenH's rom, my battery would DRAIN. Im talking 50% by the end of the day. With QBus' rom, I fully charged it last night and lost 10% just now so that's about..(slept at 5am, it's currently 2pm) 9 hours = 10% considering half of those hours the phone was left untouched, it scares me a bit.
Guest fane Posted March 25, 2009 Report Posted March 25, 2009 Ah sorry for the misunderstanding. It seems like i needa raise this question one more time...is anyones battery being drained due to the SRS? I know that the Input and Output makes a difference in system noises (ring tones, alerts, etc) and mine are maxed to help me achieve louder text alerts/call alerts. With StevenH's rom, my battery would DRAIN. Im talking 50% by the end of the day. With QBus' rom, I fully charged it last night and lost 10% just now so that's about..(slept at 5am, it's currently 2pm) 9 hours = 10% considering half of those hours the phone was left untouched, it scares me a bit. I didnt noticed any battery drain faster thing.Its the oposite for me because with the setings on the first page im able to gain some more hours of battery life
Guest dwallersv Posted March 25, 2009 Report Posted March 25, 2009 ** UPDATE ** Figured out that the phone IS allowed to sleep by itself using S2U2. So now you can just walk away from your phone and it'll lock itself (if you use S2U2 that is) New WORKING S2U2 settings (But follow the start>settings>system instructions from first post) On Battery Power: Lock when backlight turns off: ON but only blank screen: OFF blank sceen on talk: OFF Advanced: Power save mode: ON Don't suspend power: ON >>MUST BE ON! This is what crashes the phone and refuses to let it wake up. Don't double check: OFF Don't use keyboard: ON Check exceptional exes: ON Working as of all night up to this morning. So far so good These settings don't suspend (sleep) WM when S2U2 times out. It simply blanks the screen. The setting, "Don't suspend power: ON" is the same as turning "But only blank screen" on in the two power variants (battery, external). I had made the mistake of having the above setting on and then thinking that suspend by S2U2 was working (see previous posts). Sadly, that wasn't the case, and when I discovered this, and turned off "Don't suspend power", hangs started appearing right away from S2U2 actually sleeping the phone. So far, putting it to sleep with the power button seems to be safe, and somehow different as far as WM is concerned. It's a curious thing... something in the execution path is different when it goes through the power button handler than when it goes through the WM suspend API from a program. Anyway, your settings are still king, Supadan. The one caveat is that to save the most power, remember to lock phone with the power button! If you just let S2U2 lock it, it will not go to sleep, and even though the screen is blank and unresponsive, the OS is still running, soaking up electrons from the battery. A quick way to tell whether the phone is really asleep or just has its eyes closed is to set the wakeup button to just the front action button (the optomouse). Then, when the screen's blank, it will come alive when you press this button if it's really asleep. If it's just got the screen blanked by is otherwise running, this button will not turn the screen back on -- you will have to press the power button to get it to open its eyes.
Guest Supadan Posted March 26, 2009 Report Posted March 26, 2009 These settings don't suspend (sleep) WM when S2U2 times out. It simply blanks the screen. The setting, "Don't suspend power: ON" is the same as turning "But only blank screen" on in the two power variants (battery, external). I had made the mistake of having the above setting on and then thinking that suspend by S2U2 was working (see previous posts). Sadly, that wasn't the case, and when I discovered this, and turned off "Don't suspend power", hangs started appearing right away from S2U2 actually sleeping the phone. So far, putting it to sleep with the power button seems to be safe, and somehow different as far as WM is concerned. It's a curious thing... something in the execution path is different when it goes through the power button handler than when it goes through the WM suspend API from a program. Anyway, your settings are still king, Supadan. The one caveat is that to save the most power, remember to lock phone with the power button! If you just let S2U2 lock it, it will not go to sleep, and even though the screen is blank and unresponsive, the OS is still running, soaking up electrons from the battery. A quick way to tell whether the phone is really asleep or just has its eyes closed is to set the wakeup button to just the front action button (the optomouse). Then, when the screen's blank, it will come alive when you press this button if it's really asleep. If it's just got the screen blanked by is otherwise running, this button will not turn the screen back on -- you will have to press the power button to get it to open its eyes. That's also what I noticed. So that's why sometimes it would wake up and sometimes it wouldnt with the front button B) hahaha thank you for that extra info. Yeah I read the description of the "don't suspend power" on S2U2 and it won't suspend any of the power options as long as the option is set to OFF. Sad.. :'( Sigh... well dwallersv, have you noticed any kind of battery drainage? I thought maybe the app TouchResponse to add haptic to my touchpal keyboard might be draining extra battery buttt if you say yours drains battery too, then ill leave it as is. For now, i'm going to try uninstalling the 2.
Guest thescope Posted March 26, 2009 Report Posted March 26, 2009 Ok, now I am sure the battery drains alot more without suspend (sleep) and just backlight off... at least 20-30% less battery at the end of the day. Looking for a way to fix this...
Guest dwallersv Posted March 26, 2009 Report Posted March 26, 2009 well dwallersv, have you noticed any kind of battery drainage? I thought maybe the app TouchResponse to add haptic to my touchpal keyboard might be draining extra battery buttt if you say yours drains battery too, then ill leave it as is. For now, i'm going to try uninstalling the 2. Ok, now I am sure the battery drains alot more without suspend (sleep) and just backlight off... at least 20-30% less battery at the end of the day. Looking for a way to fix this... Same as thescope. Drain seems to be about 1.5-2x while asleep. It's a big price to pay, but in my subjective opinion it's worth it for the benefits of SRS (for awhile at least; I'm betting this gets resolved one way or another, either by the user community, or a future update from SRS Labs).
Guest Supadan Posted March 26, 2009 Report Posted March 26, 2009 Same as thescope. Drain seems to be about 1.5-2x while asleep. It's a big price to pay, but in my subjective opinion it's worth it for the benefits of SRS (for awhile at least; I'm betting this gets resolved one way or another, either by the user community, or a future update from SRS Labs). I hope so too. Battery drainage is pretty hardcore...im getting sometimes 50% by the end of the day whereas before SRS, by day 3 i'd have 70-60%
Guest dwallersv Posted March 26, 2009 Report Posted March 26, 2009 I hope so too. Battery drainage is pretty hardcore...im getting sometimes 50% by the end of the day whereas before SRS, by day 3 i'd have 70-60% Yeah... it sucks. Something you might consider, if your media usage is similar to mine: I really only care about this very much for listening to music. Watching video, listening to talk streams, and other audio usage I can live without it quite comfortably. So, I uninstalled it. I plan to suffer through a pair of reboots for install/uninstall when I will be using the phone as an mp3 player. If that proves to be too much of a pain, I'll just go back to suffering through the heavy power drain. The value in terms of improvement while listening to music is just too damn great to pass on this thing!
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now