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.
Related
This is from the pm.dll (powermanager) of 2003se (also applicable for wm5?)
The dword value must be set in
HKLM\System\CurrentControlSet\Control\Power
"SuspendToUnattendedMode"=dword:00000001
What is Unattended Mode? Does it prevent Alarms going off?
Is it a deep sleep mode?
Anybody with a clue?
I also found in my registry (dunno where it comes from after so much messing about) a strange value:
HKLM\System\CurrentControlSet\Control\Power\Timeouts
"BattStandbyPeriod"=dword:00000004
However I cannot find this in any of my rom files. Must be a leftover from
a test with HP power management I guess.
ps: alarms work so much better if
HKLM\System\CurrentControlSet\Control\Power\Timeouts
"ACResumingSuspendTimeout"=dword:0000001E (30 secs)
"BattResumingSuspendTimeout"=dword:0000001E (30 secs)
or even 60 secs.
Cheers
Unattended: This is a confusing state in which the screen, the backlight, and the audio are off. I won't go into too many details, other than to say thatthis is a PocketPC-only state that is used by applications which need to do things without alerting... of the other states.
Click to expand...
Click to collapse
http://blogs.msdn.com/windowsmobile/archive/2005/08/10/450186.aspx
V
Thanks for the info vijay
I can't believe it!!!!
At last!!!
this little "SuspendToUnattendedMode" value is what I've been searching for all over the place for the last couple weeks! This one little edit solves a ton of problems with the buggy WM2003 and WM5 issues, (bluetooth, wifi, missing SDcard, pda freezing on 'off/standby' etc, etc). It's not perfect... it burns the battery like crazy, but at least it allows the pda to function somewhat normal without constant soft resets.
Thanks for sharing this. My device is finally working sufficiently.
First, I am newly signed up to XDA Developers and this is a great resource. You guys/gals really know your stuff, awesome learning from you.
On topic.
I picked up a Cingular 2125 and have been playing with it. I upgraded to the i-mate sp5 2.0.8.0 rom.
I noticed on the original 2125 1.0.9.0 (?) rom when the keys were locked and the screen / display timed out, moving the joystick didn't light up the screen. Now on the i-mate rom, the joystick does light up the screen, this causes excessive battery drain.
I played with the iPhone ROM (2.0.11.0) and it also doesn't light up the screen on joystick movement.
I did the WM6 beta romm (not the PEE version yet) and it does light up the screen.
I am coming from the 3125 (Star100) and am used to much longer battery life, I am thinking that the screen being lit up all the time is eating the batteries, has this been discussed and resolved already by you guys?
I am wondering which ROM I should settle on for the combination of best features. I am thinking about going to the PEE WM6 rom, but am wondering about this feature and will read the PEE WM6 thread in full before making up my mind.
Thanks in advance.
Brett
Edit - 20070914
- 1.0.9.0 - Original Cingular 2125 Rom - Joystick doesn't light up screen, no automatic time synchronization.
- Andot WM6 PEE version and it lights up the screen , has automatic time synchronization.
- Phil WM6 Beta version and it lights up the screen , no automatic time synchronization.
- imate SP5 2.0.8.0 and it lights up the screen , no automatic time synchronization.
- iPhone ROM (2.0.11.0) - Chinese - Joystick doesn't light up screen, has automatic time synchronization.
- HTC 2.0.13.0 2125 Rom - and it lights up the screen , no automatic time synchronization.
- Vista Rom SPV C600 2.0.14.0 - Chinese - Joystick lights up the screen - has automatic time synchronization.
Me too
I have the same problem. I am running Andot's latest on my 2125 and with the old (1.0.9.0) ROM I could run for days.
I notice it most when I use the holster that came with the phone. If I use the holster, the battery will be down to 30% by the end of the day. If I carry the phone in my pocket it will only be down to 80% at the end of the day.
I turned on the screensaver feature in Automatic Keylock to keep the backlight from turning on. It helps a bit, but the battery still runs down pretty fast since the LCD is still on without the backlight.
This is the only real problem that I have had, aside from some intermittent network problems.
hmm, so 1.09 and the iPhone rom both don't light up off of the Joystick and the iPhone ROM has automatic time synchronization, does the PEE edition have automatic time synch?
ttt with edit updates, in case anyone is interested.
So I'm having trouble with my work exchange server synch with that iPhone rom. Must be something in the registry.
Any other ROMs have those features?
fyi, I updated to the T-Mobile 1.0.14.0 ROM and it doesn't light up the display when the keys are locked when the joystick is moved.
I am running this one until I find something better. It works well for my needs. I'm hoping we can get a WM6 ROM with this feature.
Found a link to it via google.
http://www.howardforums.com/showthread.php?t=1035146&page=1&pp=15&highlight=htc+sda+rom
Fahtrim said:
- Andot WM6 PEE version and it lights up the screen , no automatic time synchronization.
Click to expand...
Click to collapse
It HAS automatic time synchronization. before updating to this ROM, everytime when I had to pull out the battery the time reset. Now, the time is automatically synched with operator's date&time.
Have you flashed Radio 4.1.13.28_02.61.01 ?
and about the light up on joystick press.. maybe there is some settings in registry? if you have time, you can dump the roms and compare the registry of them.. and see..
DSF said:
It HAS automatic time synchronization. before updating to this ROM, everytime when I had to pull out the battery the time reset. Now, the time is automatically synched with operator's date&time.
Have you flashed Radio 4.1.13.28_02.61.01 ?
and about the light up on joystick press.. maybe there is some settings in registry? if you have time, you can dump the roms and compare the registry of them.. and see..
Click to expand...
Click to collapse
I'm embarassed to say that I don't know how to dump the ROMs and compare the registries. I'd be willing to do it, if someone can shoot me a link on how this is done.
we are offtopic, aren't we?
for rom dumping you need typho5.exe & tadzio's ImgfsTools
read more here
.
read here how to convert registry HV to RGU .
compare the default.rgu & user.rgu from both ROM with Compare It or Microsoft WinDiff or other text comparing program.
Good luck!
I've looked into it, can't download http://rapidshare.com/files/20560641/MolskiBiz_DevPack.exe from work, but I do have the PEE rom dumped.
I also looked at the PEE rom again, and the automatic time feature is on the Date & time page (Start --> Settings --> Clock & Alarm --> Date and Time --> Automatic Time/Time zone is there), sorry for the misinformation. I will update the above now.
I was able to export PEE & The t-mobile registry with PHM and compare. They are significantly different, not sure where to start............
I'd suggest searching for keys and values containing: lock, key, stick, time, light, back ...
I've searched the reg of my WM6 Beta as well as on the internet (incl. MS sources) and found "some" keys/values but yet I couldn't find anything that seemed fitting.
Pop5k said:
I'd suggest searching for keys and values containing: lock, key, stick, time, light, back ...
I've searched the reg of my WM6 Beta as well as on the internet (incl. MS sources) and found "some" keys/values but yet I couldn't find anything that seemed fitting.
Click to expand...
Click to collapse
I've tried searching on various keywords and did the ones you tried above. I made changes to Display but it messed me up and I had to completely reflash. Different drivers in different ROMS??
As an update, since running the T-mobile rom, my battery life has been noticeably better.
Yesterday I wrote up a custom home screen using RJTime and Smartmonitor, purely for function, but even with the Smartmonitor running my battery life is still much better with the "no light up when keys locked when joystick pressed"
I have done some more searches and changes. No luck. A couple of the changes made so I had to reflash the device to get display back.
This rom: http://forum.xda-developers.com/showthread.php?t=331319
Does it better. Hitting the joystick while key-locked will turn on the screen but only for 7 seconds - no matter what timeouts the user set for non-locked operation.
However, the rom's far from "perfect english" with quite a few elements/texts being in chinese.
Pop5k said:
This rom: http://forum.xda-developers.com/showthread.php?t=331319
Does it better. Hitting the joystick while key-locked will turn on the screen but only for 7 seconds - no matter what timeouts the user set for non-locked operation.
However, the rom's far from "perfect english" with quite a few elements/texts being in chinese.
Click to expand...
Click to collapse
I disagree on that being better. If you are bumping the joystick constantly while in your pocket or in a holster, it is continually lighting up the screen. That is a battery killer.
I guess no luck on this issue. I have pretty much not found anything.
With "better" I meant better having the screen light up for just 7 seconds than 30, 60 or whatever else your normal un-locked display timeout is.
Obviously "best" would be if the screen did not turn on at all upon joystick presses.
I'm currently using the "WM6 HTC Edition" you can find in this forum. It's clean english and works with the 7 sec timeout as well.
My battery life drastically increased since I've started using the 7 sec versions. So I guess (unless you're wearing realy tight pants) the joystick aint constantly getting pressed. It just get's pressed every now in a while. So it's obviously better to have the screen unwanted on for "a few times 7 sec's" rather than "a few times 60 sec's" druing the day. But as I said that's true "unless you're wearing realy tight pants".
Hi.
I am solving the issues of CommMgrPro with Raphael. The most important were.
1) CMP didnt change the band correctly (2G <-> Auto <-> 3G)
2) CMP didnt set correctly the speaker volume.
Any help to see if those issues are gone in this version will be wellcome with free licenses
Version V2.2(2008-09-12)
1) There are towers on each country with same cell id. So now the primary key for Cell Mode will be CellID + LAC. CMP will convert your database so make a backup before and will fill the lac information each time it finds a cell with lac equals 0
2) Compatibility with HTC Touch Diamond and HTC Touch Pro (Fixed Band manager, speaker manager, GPS manager and some GUI changes).
3) New option to repair the database.
4) New page for connections option (In connections/menu/options)
5) Option to disable/enable connections on roaming
6) Option to CMP startup delayed on page Options 3.
7) Option to Show/Hide the main window after start CMP.
8) Clicking on the higher part of the battery bar opens the battery page
9) Clicking on the lower part of the battery bar opens the battery page
10) Hide button is raplaced by calendar button.
11) New Today tab. This dialog lets you see the next events that will happen in the place, including calendar events, "Always on" schedules and other events (time limits, etc)
I´m on it!
I´m curious to see how much battery economy this will bring when switching off 3G? I´ll post my findings. What do you mean by speaker volume (in call?).
thanks
Belive me, it really save your battery if you swith off 3G mode. My battery lifetime increase from 8 to 26h.
Regards
B.
danielherrero said:
Hi.
I am solving the issues of CommMgrPro with Raphael. The most important were.
1) CMP didnt change the band correctly (2G <-> Auto <-> 3G)
2) CMP didnt set correctly the speaker volume.
Any help to see if those issues are gone in this version will be wellcome with free licenses
Click to expand...
Click to collapse
Hi Daniel,
I'm expecting my Touch Pro on Friday, I'll report as soon as I can.
Manni
So far so good on the band...
I´ve tried all day switching between 2G and 3G and it seem to work seamlessly, which comes as a huge plus for me to save on battery when 3G is not needed.
One thing I don´t get.. the HIDE button. CMP is hidden but how to unhide it without having to press the icon to launch it again.
Update: Yes it asks for the PIN but naturally it has to since it´s reestablishing a connection to the Celular provider.
Regarding band switching - it works sometimes because sometimes CM just reset himself (generate errors)
Another thing is that if I'm switching from 3g to 2g is asking me for PIN
When I'm doing it mannualy (GSM to WCMDA switching) system never ask for it.
B.
Hi
In the options page you can set the pin code. In this way CMP will enter automatically the pin when switches the band....
fllysurfer said:
I´ve tried all day switching between 2G and 3G and it seem to work seamlessly, which comes as a huge plus for me to save on battery when 3G is not needed.
One thing I don´t get.. the HIDE button. CMP is hidden but how to unhide it without having to press the icon to launch it again.
Update: Yes it asks for the PIN but naturally it has to since it´s reestablishing a connection to the Celular provider.
Click to expand...
Click to collapse
Well, I usually assign a hw button to CommMgrPro. Raphael has few buttons so I assigned long press phone button to CMP. CMP installs a Today plugin and a tray icon to manupulate CMP directly from today screen or bring it to front but you cannot see them with touchflo 3d. Sorry for not saying it before, you can set pic code in options dialog so cmp will enter pin code automatically....
Dani
fllysurfer said:
I´m curious to see how much battery economy this will bring when switching off 3G? I´ll post my findings. What do you mean by speaker volume (in call?).
thanks
Click to expand...
Click to collapse
No, system volume. You can control ring tone and ring volume as a action associated to enter/exit in a profile/place (using cell ID)
It was short and 5min test - I'll check everything once again tomorrow and let you know.
Regards
B.
For those who want to check the 3g effect on the battery live. There is a tab on CMP that shows graphically the battery evolution in different scales of time and if you touch two points it tells you the speed, for example, 6 units per hour. Ok, let your device during some hours in 3g and check the drain speed. Do the same test using 2g. As you will see battery live lasts double (or more) using 2g...
Great Commmanager Replacement
Testing for about 15 mins now and so far no problems.
Although the ON/OFF switching for phone with the "no time limit" function is not very responsive. I had to click another icon before i could switch it on again.
Great work on the battery graphs very useful
I will report tomorrow after some intesive usage.
WatskeBart said:
Testing for about 15 mins now and so far no problems.
Although the ON/OFF switching for phone with the "no time limit" function is not very responsive. I had to click another icon before i could switch it on again.
Great work on the battery graphs very useful
I will report tomorrow after some intesive usage.
Click to expand...
Click to collapse
hehe I see to tested it deeply. Turn on phone with time limit was disabled one month ago because the people requested in this way. Anyway I will remove the time limit dialog to avoid confussion....
CommManager replacement is only a little feature. The main one is let CMP (CommMgrPro) to set the state of the device (phone, band, BT, WIFI, speaker, connections, beam, messaging, brightness, ring tone, today theme, call forward, open and close programs, etc) depending on your current location by cell id (home, work, cinema, etc) and weekday/hour. In this way the state of the device will be different on your work&monday&10:00 than on home&sunday&13:00, isnt it?
Dani
Hi
I ve uploaded a new beta (b6). It warns if you want to change the band but you didnt set the pin code on options and a few more things. If you look at the screenshots on first post you will see there is a screen dedicated to the current (different than the battery page)with two lines, one for instant current drain and other for average. In this way is easy to check the current (in mA) needed for your device under different circunstances (wifi, band, gps, etc) and the temperature of the battery (important for the people like me having problems with device not charging if running gps/tomtom in a warm day).
ps: Talking about gps and temperature, finally I bought and A/C mount system so the battery's temperature is always low and no problem charging....
Hi Daniel,
So I received my Touch Pro today, and the first program I installed was CMP
Couple of issues:
- I installed without deactivating Touch Flo 3D, so I got an error message when the program first launched (I guess it couldn't launch the today plugin).
- If I deactivate the Touch Flo 3D, the icons in the plugin are stil QVGA. Same thing if you change the icons of the location (which makes it difficult to select the right one, as they are not for the software where the seem to be on the screen, if you see what I mean)
- Same thing for the fonts on mostpages / menus. Most of them are very small (hard coded for QVGA I guess) which makes them much harder to reads than on a QVGA device. The location line, or the function icons at the bottom of the main screen, are normal size. Everything else is small (for example, "there is a newer version").
- When Touch Flo 3D is activated, there is no directaccess to CMP (lower right globe icon), but I guess that's normal.
Otherwise, everything seems to work fine. I guess most of this is VGA related rather than Touch Pro related, but here you go, I'm coming from CMP on a Tytn II...
Edit: forgot to specify that the speaker setting and the band switching seems to work fine.
Hi
Thank you very much for your comments and help. Fortunately most of those issues are related with the sizzo vga skin so can be changed modifying the file skin.xml. Modify and enhance the vga skizzo skin is one of the pending things to do. Please follow reporting anything you see
Hi Daniel,
Done a bit more testing today, and I found out that there are two connections in CMP (T-mobile PicMessage and T-Mobile Internet), while I have only one connection setup by default (T-mobile).
They are both enabled, none of them is always on, and only the PicMessage is connected.
Is this normal? I'm quite sure I had only one on my Vario III. Which one do I need to get my push email? If I want to get my exchange email as it arrives, do I need to switch one of these to always on? (by the way, my exchange server is setup properly, and it works thanks to MrVanx...).
Hi Manni
CMP shows all the connectios,even hidden connection. Probably in the connections wizard your operator set up the second connection for other pourposes like mms,wap,etc.
If you re using direct push(like me) you dont need to mark any connection as "always on" because activesync will keep the connection alive....
Dani
danielherrero said:
Hi Manni
CMP shows all the connectios,even hidden connection. Probably in the connections wizard your operator set up the second connection for other pourposes like mms,wap,etc.
If you re using direct push(like me) you dont need to mark any connection as "always on" because activesync will keep the connection alive....
Dani
Click to expand...
Click to collapse
Thanks a lot for the clarification!
I've tested both b5 and b6 versions on orygial HTC rom.
Discovered that :
1. Cannot clear history of battery usage in CURRENT tab - on BATTERY tab this feature works fine
2. Cannot verify database integristy - error message appear
3. Switching between G2 and G3 works smooth - tested VERY intensivly for last 3-4 days.
Small hints
1. there are two graphs on main screen - on the left is graph for battery and on the right for available field. Is nice of you if you can just create the link between battery graph on main screen and CURRENT/BATTERY tab on settings. This is common problem that Touch Pro battery has very short lifetime and I'm very interested in checking which action is draining my battery more than normal - graph is perfect place for this.
5. Last suggestion for booting TP and application starting process. Everytime when I'm performing soft reset or just starting device, I'm waiting to put my PIN as fast as possible to get my TP online, but THEN CommManPro LOGO is showing and grrrrrrrrrrrrrr I'm must wait next 5sek to tap my PIN.
You know, this is not a problem if you are using your phone for private, and there is no more than 3-4 calls from you sister/girlfriend/mother/lover by day, but I'm using my TP for buisness (and testing everything in the same time) manner so time when I'm available is critical - one missed call (because of 5sek delay) and couple of bucks less in my pocket
If it possible for you to just pospone CommManPro to starting just after TF3D it's nice!
Regards
B.
Hi all,
I tried searching but cannot find anything on this, so as my first post, here goes...
I have a Touch Diamond with official ROM (WM6.1). I want to get over the known "issue" that with the device set to pin lock after 0 minute timeout, it still locks automatically after 1 minute of idle time.
Of course, I found an answer on this forum, see, for example http://forum.xda-developers.com/showthread.php?t=291868: in the registry, set AEFrequencyType to 2 (instead of 1), which works as hoped as far as the device is concerned... it no longer auto-locks after any amount of time, but locks instead whenever it goes into standby.
The issue is this: Activesync no longer requires the pin to connect to the device and without pin can read ALL files from its memory, even if the phone is locked at the time. Setting AEFrequencyType back to 1 forces Activesync to require the pin even if it is not locked when it is plugged in to the computer. Does anyone know a way to force Activesync to require the pin... of course, I am looking for a setting on the device, not the PC, as I want to make it hard for anyone who might steal the phone (or if I lose it!) to read the data on the device.
In case anyone is wondering, I also found another workaround. Having set the pin timeout to some large time, like 30 minutes, I can then use a pin locking program, Zenyee's 'Pin Lock.exe', and create a wakeup event notification with Dotfred's Task Manager (seems very useful app for free!). This works, until I run FlexMail, which seems to intercept these notifications and prevent it from locking!! So, I have to override a soft key on the home screen to run the pin lock, then hit the power button to put the device into standby. Not too bad, but there must be a better way...!
Thanks in advance,
Martin
Just a quick follow up for anyone who may be interested. FlexMail DOES NOT intercept the wakeup events... however, because it causes a little processing to be done, it seems it can delay the device from sleeping for a while (a minute or two) whenever a full synchronisation is performed. So, the wakeup event, whilst normally quick to activate, can sometimes take a minute before becoming effective.
However, I now have a workable solution for me. Just as I said above, I set my Pin Lock timeout to something large, like 30 minutes. However, instead of relying solely on wakeup events, I have now installed Gyrator 2 (http://forum.xda-developers.com/showthread.php?t=427805) which is an excellent application for many reasons... I particularly like being able to identify the window class/title using the stylus-in event to identify the in-focus window! More importantly, for this issue, it has the option to both Pin Lock and Suspend the device whenever a certain criteria is met. For me, this is when it is held face down for a second. So, now I just do this instead of hitting the power button and I'm guaranteed to have the device Pin Locked on next wakeup. ActiveSync also requires the Pin as AEFrequencyType is the default value of 1. A perfectly workable solution.
All the best,
Martin
I strongly suggest you take this towards the Diamond section as knowledge about specific problems in specific devices are usually conversed over at that specific section.. more than here.
Thanks, but I think this is WM6/WM6.1 specific, not Diamond specific. The problem with AEFrequencyType set to 1 giving a timeout even with zero minutes is known and seems to be device independent. I just found that setting it to 2 to fix this timeout issue, as many people do, seems to prevent ActiveSync from requiring the PIN as well! Not a good result.
That said, my workaround solution is probably Diamond specific, sorry! Perhaps I should post in the original thread that I found out about the AEFrequencyType registry tweak?
All the best,
Martin
Hey all,
Recently i've been having some problems with my emails coming through to my handset. I have the settings set to send/receive every 5 minutes.. but for some reason if my screen is turned off (phone on standby) no email comes through but when i turn my screen back on the emails come.
Has anyone else has this problem? I've never had this problem before it started out of no where...
Which software are you using as your email handler?
The original software that came with the phone.. I havn't installed anything on the phone its at its original state...
jayt2008 said:
Hey all,
Recently i've been having some problems with my emails coming through to my handset. I have the settings set to send/receive every 5 minutes.. but for some reason if my screen is turned off (phone on standby) no email comes through but when i turn my screen back on the emails come.
Has anyone else has this problem? I've never had this problem before it started out of no where...
Click to expand...
Click to collapse
are you using wifi or data connections? If its wifi do you have wifi enabled during standby?
i am using data...like i said if my screen is turned on theres no problems at all but its just when the screen is off in stand by mode no emails will come through..
This is a huuuuge issue which stems from the dawn of WM6. To be honest, it works sporadically for me. A few hours of no email, then a whole group arrives at a time. Sometimes it wont check by itself all day. Other times it will go 1-2 days without missing a beat. This makes it really hard to determine if what I have been doing fixes it.
Here are links to threads I have dug up:
http://forum.xda-developers.com/showthread.php?t=420513
^This is not a good fix imo, as it forces your data connection to be awake 24/7, killing your battery.
http://forum.xda-developers.com/showthread.php?t=437199&page=2
^ I am using the outlook email scheduler. Not sure if its working, or placebo. It still doesnt stick to every 30 mins, sometimes an hour late heh. At least you can have day/night settings and weekend settings. Maybe not a perfect fix, but increases email checking options.
http://forum.xda-developers.com/showthread.php?t=332362
^ Many Kaiser users had/have same problem, no solution found.
http://forum.xda-developers.com/showthread.php?t=445434
^Same problem, no fix in the Blackstone forum.
Thanks everyone for the help.
There has to be some kind of fix out there somewhere.. its unreliable
could try out the seven beta app
If I might make a suggestion...
Maybe you should edit the thread title to "No email in standby" as "Email..." doesn't really tell the story, more people will be likely to find it and post a solution
Problem solved with my Touch Pro
I also had this problem but I found the settings to change this. But you do need schaps advanced config 3 (and a regeditor) to make it happen. Now i always receive my email, it checks every 10 minutes, even in standby mode, with my own data connection.
With a registry editor go to:
HKLM - Comm - ConnMgr - Providers - [GUID] - Connections - [Connection Name] - Always On
and change this value from 0 to 1
(You can also change this setting with Schaps' Advanced Config under menu (right softkey) - More Settings - Connections.
Here you can select "Always On" for the type of data-connection that you use to receive your email)
The second thing is using advanced config and change the setting under power management:
- AC resuming from suspend timeout
- Battery resuming from suspend timeout
I have changed both to 60 seconds.
Now my touch pro is notifying me of new email, even in standby mode.
Good luck
^ by forcing the eternal data connection, are you not killing the battery? I think the phone should be able to connect, query, download emails, disconnect at set intervals while in standby. I think it is supposed to, but for some reason it doesn't do it reliably.
The way I have done it is to use SKSchema to watch for a data connection being connected and turn on the screen when this event happens. This wakes th ephone up and is able to download email. Then I use advance config to close inactive data connection after 10 seconds. As the phone is awake the data disconnects fine. As long as your phones screen is set not to power off quickly, mine is a minute it should be fine.
In the last day I got fed up with TF3D again and turned it off, email seems to check every 30 minutes. I'll let it go for a few days to make sure its not placebo effect.
Anybody here having this problem while manila disabled? Perhaps there is some obscure power saving setting running in the background of manila
Well i have no idea how to fix this problem.. i have played with my phone to try figure it out but nothing.
I will probably have to take rvjacobs advice and see if that works.
It looks like quite a few people are having this same problem.
Its weird.. If my phone is on standby no email comes through..but if its on standby and an SMS comes through, the screen doesnt wake but the email also comes through..
not sure whats happening there.
Mine does it with TF3D disabled also. Thats why I have to use SKSchema to turn the screen on when it detects an internet connection. This way, mail comes through fine and it also auto disconnects the data.
I can now confirm that the issue is still there, regardless of TF3D. Damn, I've tried everything, maybe this is a dead end... Maybe wm 6.5 will see a solution
Maybe it helps you to look for/change the following key:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts]
"ACResumingSuspendTimeout"=dword:00000001
"BattResumingSuspendTimeout"=dword:00000001
If you've got these values in the registry, try to cange them to
"dword:0000001e"
It's the time in seconds the device keeps running (without turning on the display) when it's automaticly woke up from the suspend mode (i.e. to look for mails). And if the value is "1", the time might be to short for picking up your emails.
With the new value you set the time up to 30 seconds.
The key exists since WM2003 and most of roms had a higher value in the past. But in the last time more and more roms come with a value of 1. I think its because the manufacturers want to get a good standby time for the devices...
I hope it works for you and you won't have to wait for WM6.5
Thanks for that deroland! I did manage to find them in the reg but it just says "Value Data 1".. doesnt say anything like "dword:00000001"?
I am new to this whole thing so it may be a stupid mistake im making..
jayt2008 said:
Thanks for that deroland! I did manage to find them in the reg but it just says "Value Data 1".. doesnt say anything like "dword:00000001"?
Click to expand...
Click to collapse
Then your value is like "dword:00000001". This is a hexdecimal dword key.
So your device has one second to look for new mails.
Try to change it to "1e" and I hope it will help you.
jayt2008 said:
I am new to this whole thing so it may be a stupid mistake im making..
Click to expand...
Click to collapse
The only stupid thing is that there is no open support by the manufacturers of the devices and microsoft for windows mobile. They only want to make their money ignoring the problem we have by the stuff they sell.
deroland said:
Maybe it helps you to look for/change the following key:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts]
"ACResumingSuspendTimeout"=dword:00000001
"BattResumingSuspendTimeout"=dword:00000001
If you've got these values in the registry, try to cange them to
"dword:0000001e"
It's the time in seconds the device keeps running (without turning on the display) when it's automaticly woke up from the suspend mode (i.e. to look for mails). And if the value is "1", the time might be to short for picking up your emails.
With the new value you set the time up to 30 seconds.
The key exists since WM2003 and most of roms had a higher value in the past. But in the last time more and more roms come with a value of 1. I think its because the manufacturers want to get a good standby time for the devices...
I hope it works for you and you won't have to wait for WM6.5
Click to expand...
Click to collapse
This is a setting which can be changed in advanced config, under power. I have mine set to 90 seconds, to no avail. I think this is what is causing it to work sporadically, as opposed to not at all.