Well... It seems that all WM6 ROMs have an issue with automatic wake-ups when you have a PIN number set. Some WM5 ROMs had it, faria fixed it in his ROMs, but apparently he couldn't (or didn't) do this in WM6. This is one big show-stopper for me...
EDIT: This seems to be a bug in WM6. If you turn off the backlight off feature in Control Panel and Auto Time Zone, you can have PIN enabled and it won't turn on, otherwise it will.
herzzreh said:
Well... It seems that all WM6 ROMs have an issue with automatic wake-ups when you have a PIN number set. Some WM5 ROMs had it, faria fixed it in his ROMs, but apparently he couldn't (or didn't) do this in WM6. This is one big show-stopper for me...
Click to expand...
Click to collapse
Explain a little more
Power up after what time ?
And are you positive that it's got something to do with the PIN and not something else like an exchange server(from what i remember)?
herzzreh said:
Well... It seems that all WM6 ROMs have an issue with automatic wake-ups when you have a PIN number set. Some WM5 ROMs had it, faria fixed it in his ROMs, but apparently he couldn't (or didn't) do this in WM6. This is one big show-stopper for me...
Click to expand...
Click to collapse
I am using a pin, no wake-ups yet with Faria's WM6. Lucky me I guess.
--M
Found a solution...
anichillus said:
Explain a little more
Power up after what time ?
And are you positive that it's got something to do with the PIN and not something else like an exchange server(from what i remember)?
Click to expand...
Click to collapse
After ripping my hair out and testing, yes, exchange is not to blame, but I found a solution...
It is the combination of having the PIN set and blacklight off feature set to ON in the Control Panel.
Without the pin set, but with backlight off enables it stays off.
If you disable the backlight off in control panel, you can safely enable the pin - it'll stay off.
Backlight off enabled, pin enabled - it turns on.
This seems to be a bug in WM6...
herzzreh said:
Well... It seems that all WM6 ROMs have an issue with automatic wake-ups when you have a PIN number set. Some WM5 ROMs had it, Faria fixed it in his ROMs, but apparently he couldn't (or didn't) do this in WM6. This is one big show-stopper for me...
Click to expand...
Click to collapse
It happened to me as well, but only when connecting my phone via USB to my vista work PC while it's version of Activesync (windows mobile device center) was configured to accept USB connections. if I disable USB connections and use the PC only for charging the phone - it doesn't happen.
I think we need more than a few people to be having this problem to call it a legit "bug"...this is really random though.
This reminds me of one of those random baseball stats like some pitcher has under a 1.00 ERA when facing lefties in the month of August when the humidity is over 80% north of the mason dixon line on an even numbered day and playing in a dome...lol...I'm just bustin' your chops bro...no worries.
I'll test myself and let ya know.
j3d1n4s7y said:
I think we need more than a few people to be having this problem to call it a legit "bug"...this is really random though.
This reminds me of one of those random baseball stats like some pitcher has under a 1.00 ERA when facing lefties in the month of August when the humidity is over 80% north of the mason dixon line on an even numbered day and playing in a dome...lol...I'm just bustin' your chops bro...no worries.
I'll test myself and let ya know.
Click to expand...
Click to collapse
I also confirm that this work. I had the same bug. So I disable the backlight off and it went way...
Here's my testing...
1. no PIN + no backlight timeout = no random power-ons
2. no PIN + backlight timeout = no random power-ons
3. PIN + no backlight timeout set = no random power-ons
4. PIN + backlight timeout set = random power-ons
Looks to me like it is the combination of having both a PIN and a backlight timout set. Didn't seem to make a difference on the amount of time the backlight timeout was set for, nor did it make a difference whether the PIN was simple or complex.
Thanx.
j3d1n4s7y said:
I think we need more than a few people to be having this problem to call it a legit "bug"...this is really random though.
This reminds me of one of those random baseball stats like some pitcher has under a 1.00 ERA when facing lefties in the month of August when the humidity is over 80% north of the mason dixon line on an even numbered day and playing in a dome...lol...I'm just bustin' your chops bro...no worries.
I'll test myself and let ya know.
Click to expand...
Click to collapse
It was an issue under WM5 also... it is just that I haven't suffered under WM6... bonus for me
--M
I've never seen this fault/bug before on my device and ive used underground, orwells, mun, MB,two or three of faria's and probably a few more that i cant think off of the top of my head on a cid-locked G4.
me too
i hava the same issue...
PIN and turn off backlight enabled = random power-ups
it happends with undeground edition and the one i m using now: MB
don't know other roms....
isamts said:
Here's my testing...
1. no PIN + no backlight timeout = no random power-ons
2. no PIN + backlight timeout = no random power-ons
3. PIN + no backlight timeout set = no random power-ons
4. PIN + backlight timeout set = random power-ons
Looks to me like it is the combination of having both a PIN and a backlight timout set. Didn't seem to make a difference on the amount of time the backlight timeout was set for, nor did it make a difference whether the PIN was simple or complex.
Thanx.
Click to expand...
Click to collapse
confirmed this... Qtek-labeled G3 WIZA200, IPL/SPL 2.26, "nottoosmart-vanilla-WM6" main ROM, radio 2.19.11, no overclocking and no installed software yet. Any lock timer + any backlight timer = random power-ons. Experiments with the device power-off setting under Settings->Power->Advanced show no effect.
Since the battery charging and level query on these devices are traditionally handled by the radio side of things, has anyone seen any correlation between this bug (and the various power drain issues) and different radio ROM versions? I was thinking about trying 2.25.11 Cingular or 2.61.xx because the reception on 2.19.xx is just awful, even when I'm in linde of sight of a known T-Mobile-US tower.
brtb said:
confirmed this... Qtek-labeled G3 WIZA200, IPL/SPL 2.26, "nottoosmart-vanilla-WM6" main ROM, radio 2.19.11, no overclocking and no installed software yet. Any lock timer + any backlight timer = random power-ons. Experiments with the device power-off setting under Settings->Power->Advanced show no effect.
Since the battery charging and level query on these devices are traditionally handled by the radio side of things, has anyone seen any correlation between this bug (and the various power drain issues) and different radio ROM versions? I was thinking about trying 2.25.11 Cingular or 2.61.xx because the reception on 2.19.xx is just awful, even when I'm in linde of sight of a known T-Mobile-US tower.
Click to expand...
Click to collapse
Forgot to mention, mine is T-Mobile-labeled G3 WIZA200, IPL/SPL: 2.26, Faria's 'The Real Thing', Radio: 2.61.11, OCd to 260-boost to 273-low to 130.
Well someones got to be different!
I have not set a pin and still have random power ons.
any suggestions for this scenario?
thanks
Bhayani
Same Issue Here
I too was having random power-ons using NotTooSmart-Vanilla and Xplore 1.1 with a password set. Unchecking the "backlight turn off" seems to have fixed the random power-on problem.
Something else I have noticed that occurs as soon as I set up a password is when I press the power button to wake up the device the screen turns on, quickly turns blank, and then comes back on. While it is not a big deal, it is annoying and I hate that I have to wait a second or two each time it wakes.
I can confirm the issue + solution. I'm using Wizard Moblie 6 Business Edition RC1.
Same issue here + Solution confirmed.
Funny but this is not the first time this issue has been spoken about. It's been a known bug for some time. Maybe next rev will fix this.
Problem confirmed on my wizard with Faria WM6 ROM.
My solution: I lock the device, it then keeps switched off...
The combination of settings has been screwing me up. Another bug when fixing the problem, if you don't have "Turn on backlight when a button is pressed or the screen is tapped," when you turn off your device and turn on, then the backlight settings goes low. With all the proper settings correct, things worked fine.
My WM6 (Build17913) changes time and date
Suddenly time and date changes on my wizard. i culnt find and workaround for this so I will dump the rom and get the older (and stable) one.
I'm wondering if this is because of my device (HTC Titan) or because of WM6... all I know is that I never had this happen before!
Basically, I'll pull out my phone sometimes and find that its turned on by itself, and has been sitting with the dim idle backlight on.
I noticed it can be caused by several things but the 2 main ones I've seen is:
1) when the phone switches to/from roaming, it wakes up
2) when using A2DP controls (AVRCP), it wakes up.
I've been using workarounds to keep the backlight off for now (set the phone to roam only, or carrier-only, so it won't be switching in/out of roam, and use core player or just remember to toggle the screen off everytime I use a media AVRCP control), but there has got to be a better way to keep the darned screen off until I press power!
Anyone have any suggestions? This is really an unexpected annoyance as it eats up my battery quickly not knowing its on...
I had a similar issue with whenever I received an email and didnt shut off the device manually. What I eventually ended up doing was setting the device to automagically lock when it was powered off, and this seemed to solve the issue. I'm not sure however if this will fix it in your case because locking it may interfere with AVRCP controls working.
Hello,
since a few days I'm testing the new Mobile Shell 3. My first impression is very well. But one thing causes problems.
While I had installed Mobile Shell 2.x I was using S2U2 to make my device switch off.
S2U2 settings -> device switches off 10 sec after background-light turned off
WM6 power-settings -> background-light turns off after 15 sec - device switch off is not activated.
Everything worked fine... Background-light turns off after 15 sec. Further 10 sec later device switches completely off...
Now I've upgrated Mobile Shell 2 to version 3 but I've absolutely nothing changed on any settings - and suddenly S2U2 doesn't switch off my device any more...
My PPC turns off background-light after 10 sec (everything ok) - but S2U2 seems not to be able to switch off the device completely. Display is still on and shown darkly. But Touchscreen has turned off (doesn't react on finger-tapping).
When I close Mobile Shell everything works fine again.
So it seems that MS3 is blocking the suspend mode of some programs.
I think with Nitrogen (Mp3-player) it was nearly the same. In this prog does exist a suspend button but by tapping it only background-light switches off...
Anybody an idea or made same experiences?
Thank you
flahn
why don't you just change it in your setting of the battery in WM? I have a Lg ks20 and i change it there so after 1( sec he turns of the light) and after 3 minutes he switches off my phone. I also have spb mobile shell 3.0 and there are bugs in it atm.
Just click on your battery and go to the advanced tab.
Hope this helps you a bit
Switchke said:
why don't you just change it in your setting of the battery in WM? I have a Lg ks20 and i change it there so after 1( sec he turns of the light) and after 3 minutes he switches off my phone. I also have spb mobile shell 3.0 and there are bugs in it atm.
Just click on your battery and go to the advanced tab.
Hope this helps you a bit
Click to expand...
Click to collapse
Hello Switchke,
thanx for your answer.
My problem is a little bit complicated.
I'm using my KS20 in combination with the prog phoneAlarm. For me it's the only possibility to get the LED's of my KS20 turn on (if there is an new SMS for example) although it is in suspend-mode. Or do you know another way to make the LED's shine when device is turned off?
I got the same idea you described before. I changed the settings of power options in wm and deactivated s2u2. But it appeared a new problem.
If there is an unread SMS phoneAlarm is set to send every x seconds a signal for the LED to light it up. In older Mobile Shell 2.x or by turning off MS3 everything works fine - after 15 sec light turns off, after 1 min device switches off.
But by using MS3 the device every 10 sec after switching off turns on again (because of the signal of phoneAlarm I think). Problem only causes with MS3.
If I can't find a solution I will reinstall MS2 - the shining LED is very useful for me because I don't have to switch on device every time for looking after unread sms or new calls...
Hey guys
I have this weird problem with the LCD backlight since I upgraded to the new AT&T stock ROM (5.11.502.2 WWE)
Usually the backlight is supposed to dim down after 30sec and then turn off after the specified time set in (start/settings/system/power/advanced). Now suddenly this stopped working correctly. The screen just turns off completely after 30sec, no matter what I change the control panel settings to.
I found the registry key (HKCU/ControlPanel/Power/Display) which is set to 30 seconds so yeah, I can increase that to make the screen turn off later, but I want the dimming back!
Where is it defined *WHAT* is supposed to happen after these 30 seconds?
No one?
Am I the only one here with a stock rom? LOL
My Fuze light sensor doesn't seem to be working correctly either. It's not the same problem, though. And I'm not really sure if mine stopped working right after the new ROM or after I installed Diamond Tweak and Advanced Config.
There used to be a noticeable change in the backlighting when moving between different ambient lighting conditions but now I don't notice anything. If I cup my hand over the light sensor, the backlight stays the same whereas before it would dim a little and then brighten up again after removing my hand.
Can anyone tell me what the default registry settings for it are so I can see if either DT or AC did something?
Thanks.
I have the screen set to always on (no time out) when I have it in the car, it stays on fine while listening to music or if it just sitting there doing nothing, but no matter if I get a call or I make a call -- the screen will always turn off after a couple seconds even though the screen is set to always stay on, also as soon as the call ends -- the phone automatically locks and I have to log in / unlock it every time. I know on the old Froyo ROMs it would stay on if I had it set to always on -- didn't matter a call or not, it stayed on like it is supposed to do and it did not automatically lock either. I am on the Weapon 3.0ROM and I am using the same widgetsoid app as the the switching mechanism for the "always on" screen setting in a widget on one of the home screens. I have checked the widgetsoid settings and there is no definition between call settings and normal data for the screen time out. Under settings in the main menu, there is no toggle to enable/disable the proximity sensor either, but since the phone face has nothing close to it when it is mounted in the car (like it would be if you had it up to your ear), I don't think that this is the proper setting to manipulate. I really believe that this is a timing setting, and I am wondering if it is separate setting that can be changed or linked to the normal screen time out settings.
Is there a way to stop the screen from timing out on the Weapon3.0 Rom during phone calls and then automatically locking the phone when the call ends? its getting a bit annoying and any help would be appreciated.
Am I really the only one experienceing this?
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
crockashat said:
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
Click to expand...
Click to collapse
I think that is an unwanted "feature" of the 2.3.3 Gingerbread rom. I am not sure of anyway around it without changing to a rom that is not 2.3.3 based.