anything im missing guys?
after flashing with the new ATT wm6 all works fine except the screen backlight keps coming on, even after pressing the screen off button it comes back on after a few secs.
peeps. anyone experience this?
i had the same problem
u cent stop it by turning your screen brightnes to 50% or above (using palm bult in brightness program (press function button (the white spot) + "P" ))
vladimir2989 said:
i had the same problem
u cent stop it by turning your screen brightnes to 50% or above (using palm bult in brightness program (press function button (the white spot) + "P" ))
Click to expand...
Click to collapse
woohoo! problem solved, thanks man!
My Voda WM6 works fine with backlight set to 40%
Sigh...I should have come here to see the solution first before I hard reset my phone.
I got the same problem, but I perform a hard reset to resolve it.
Guys I posted this on another thread here but I thought I'd mention it here as well just in case you guys can help me out.
I have my Treo 750v to connect to the net and check for emails every 30 minutes but whenever it does, the screen comes on!
Is there anyway I can get around this?
I would appreciate any help.
Thanks.
D.C
Dead Cell said:
Guys I posted this on another thread here but I thought I'd mention it here as well just in case you guys can help me out.
I have my Treo 750v to connect to the net and check for emails every 30 minutes but whenever it does, the screen comes on!
Is there anyway I can get around this?
I would appreciate any help.
Thanks.
D.C
Click to expand...
Click to collapse
Stupid as it sounds, this does appear to be a bug in the Treo WM6 update. It's still there in 2.23 VF as well. If you have Keyguard set to kick in at screen off and you set the brightness to anything other than 20% or 60% (at least for me) then the screen keeps turning on and often won't turn off after the 1 minute timeout. Got mine at 60% and its fine.
Related
Greetings,
I just upgraded to the 2.02.00 ROM last night but still have the occassional lockups. I need to do a soft reboot to get the phone to respond. I believe when it locks up, the radio is still running since I see the blinking Green LED for the GSM. I have to switch off the POWER MANAGEMENT option of "Turn off in x min in not used" for battery power to be able to use the device for calls. The only level of battery saving I am stuck with now is the Backlight auto-off and the beam settings.
Is this something others are having as well or are any applications the culprit?
Thanks in advance for your assistance.
Regards
BHAMEED
------------------------------------------------------------------------
I-Mate JASJAR
--------------
Windiws Mobile 6 (CROSSBOW)Jwright
OS 5.2.318 (Build 15341.0.0.0) AKU 0.0
CE ROM Version : (2.02.00 WWE)
RADIO Version : 1.13.00
ExtROM Version : (2.03.05 WWE) UNLOCKED
Bootloader Version : ver 2.01
Try the power button
All buttons..including the power button...no response.
try holding down the power button
or setting the backlight to atleast one notch.
Urm... uh... ah.... eeee... aaaaaaaaaaaahhhhhhhhhh.
I can confirm this behavior on my MDA Pro (G3).
All ROM versions the same like Bhameed's on my MDA, ...except bootloader of course.
Anyone else noticed this on 2.02.00?
Hold on, can you guys be more specific with this? Are you absolutely sure it doesn't come back on when you PRESS AND HOLD the power button??? Really sorry if I sound like I'm being pedantic, but just from what you've written it sounds like you don't know how to turn on the phone???
hahahaHAHAHA!!! awesome reply spyder
ok, yeah i was thinking this is an issue of not being able to turn on your phone.
yeah what's going on that was different from before?
There have been only few moments where you think "Surely not"... I hate those moments, I'm just hoping this isn't one of them! If it is a genuine problem it's pretty serious and needs to be addressed, but if not.... well, I don't think I should say much more
Please please please say this is all a big joke. I'm tired, please excuse me.
I confirm this behaviour!
And more!
My Qtek freezes... freezes... and then PUFFF. Dead.
I wait some minutes (30 minutes) and I can turn it on again.
I'll send it to qtek.
Mine has a thing sometimes where there will be a pause between pressing the power button and it coming to life... sometimes if I get impatient and press the power button again it will turn it back off before it's come on.
I don't really get it though. Does it freeze while it's still on, or while it's turned off? If it freezes when on, there's plenty of info about how to prevent freezes (mostly 3rd party apps + reg tweaks).
If it really does freeze when off, then please let us know anything more on the issue that you can.
SpyderTracks said:
Mine has a thing sometimes where there will be a pause between pressing the power button and it coming to life... sometimes if I get impatient and press the power button again it will turn it back off before it's come on.
I don't really get it though. Does it freeze while it's still on, or while it's turned off? If it freezes when on, there's plenty of info about how to prevent freezes (mostly 3rd party apps + reg tweaks).
If it really does freeze when off, then please let us know anything more on the issue that you can.
Click to expand...
Click to collapse
Mine freezes everywhere. Bootscreen, Pin code menu (when u type your pin). It depends.
then pda doesn't turn on.
Many problems.
Just go to the assistance. :\
1.Sometimes it freezes while its on. For Instance I had program opened and then whenI tried pressing X to close nothing happened. I had to use the red hardware button to close. Wonder why.
2.I too agree while the phone boots and is searching for network, it takes very long, Meanwhile when the pin enter screen come up, unless the network is fully searched one cannot enter the sim pin code, it has few freezes. or at time the phone signal icon disappears on top bar and again you need to reset the phone.
aniel1 said:
1.Sometimes it freezes while its on. For Instance I had program opened and then whenI tried pressing X to close nothing happened. I had to use the red hardware button to close. Wonder why.
2.I too agree while the phone boots and is searching for network, it takes very long, Meanwhile when the pin enter screen come up, unless the network is fully searched one cannot enter the sim pin code, it has few freezes. or at time the phone signal icon disappears on top bar and again you need to reset the phone.
Click to expand...
Click to collapse
Again, I don't have this problem for some reason... I get very few freezes at all.
I think we're getting away from the original point of the post though... and normal freezing is well documented in most OS threads with means to prevent it.
Same here...Confirmed. Tried all button combinations to get the display back (short presses and long ones), but then end up having to do a soft-reboot to finally get the phone to work properly....
Bhameed said:
Same here...Confirmed. Tried all button combinations to get the display back (short presses and long ones), but then end up having to do a soft-reboot to finally get the phone to work properly....
Click to expand...
Click to collapse
And then you don't have other problems? Like freezes?
EDIT: I flash the original rom but the problem still here
I wonder if this could be a memory leak like someone suggested.... I'm sorry guys, I haven't experienced this problem, and I haven't seen any posts about it until this thread, is there any chance you guys with this issue can keep an eye over your memory status over say a couple of days to see if there's a leek and keep us posted? Once we find out what the problem is it should make a solution easier.
I experienced this problem as well using a cooked WM5 ROM on my HERM200 the only fix I found was migrating to another ROM. I'm currently using CUSTEL_Cing_v1.3, the battery life sucks but I love WM6, it is so much faster, I'm still tweaking and trying to resolve some other issues but other than that I am quite happy with it.
If you are experiencing the lockup I would suggest moving to another ROM as an option, that worked for me. Although a clean install usually fixes a lot of problems.
Bonjour
I upgraded to WM6 (pdaviet) 2 months ago (I guess..), and problems started to appear a few weeks ago. First it just was hard to boot sometimes, had to reboot several times to get it up and running, but when it could start everything was fine. Then since yesterday, it became harder. And today, couldn't start it at all. Tried several times, and everytime the screen went melted, corrupted, like if it couldn't stand an o/c, but it always runs at normal speeds. I guess it has something to do with the battery and the way WM6 handles it (or at least the implementation we have on our prophet).
I tried to hard-reset, I left it a long time on the format screen (before the actual HR) and it handled it for long enough, but the same thing started while setting up WM.... too bad !
While writing this message I tought I could try to downgrade, and I did using AKU3.3-Jester-b1.
I had no problem while the phone was in guest mode after the HR.
Everything went nice during first step upgrade, but on final reset it did the same thing, and now..... it cannot start at all !!!!
Someone has an idea ? I own a G4 and it has the following roms :
IPL 2.10, SPL 2.20, GSM 2.47 (or something like that)
It won't charge (but my batteries are full, I've got an external charger), it won't start from battery nor from power, even if the battery is removed.
Damn, at least I guess I can return it like that to orange, since it cannot start one can't see the modified rom...
If anyone has a suggestion, it is more than welcome ^^
Thanks !
Niko
huh !
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
lastnikita said:
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
Click to expand...
Click to collapse
Hey LastNikita,
I had the same problem ! The white scanlines thing just after re-updating a WM6 version (pdaviet), because I was tired of the constant reset issue.. suddenly, the update went wrong, and I stupidly followed the "recovery" process, which tells u to remove the battery... bang ! screen went corrupted !
Like you, I tought it was over... but I noticed that if you connect your phone and PC with USB, and keep pressed power (ON/OFF button on side) + camera after reseting (little hole on bottom - press during 5 sec!), the PC recognizes a USB device (not the usual phone drivers...) at this moment, I launched the Jester 3.3 (step1) update, in order to downgrade from the ugly WM6 pdaviet... My phone was not yet fixed (still with white scanlines), but at least, I could hear again the WM "start" sound, the scanlines would also "move" across the screen borders when I touched the screen, which made me imagine I was on the calibrating process... also, while connected to PC, after a while, ActiveSync would launch, asking for 1st time synch... this kept me confident as the phone (software) seemed to be reacting fine although HW prob...
I completely charged the phone again (till green light) then kept on reseting the phone (until I hear the WM sound) hoping the lines would finish scanning and come back with the normal .. and guess what, it did !!! Of course, PIGHEAD as I am, I wasn't totally happy it recovered with WM5, so i digged for a better rom, and I can tell you I'm very happy with the smart1 (wizard version) which works fine, but still has some minor bugs as Live Messenger not working... but runs fine (specialy when pressing the ON/OFF button !
PS: Make sure the ALWAYS completely switch off your phone (ON/OFF for 3 secs) before removing the battery... it did happen again... when I stupidly trusted the "recovery" process, again !
DUHHHH !!!!
PS: at least, now you ALL know !
Kokiri
Finally ok for warranty )))
Thanks for sharing mate
I finally managed to downgrade to my original Orange rom, and I'm in the process of putting the original Orange splash screens back (I made the nk.nbf but I can't find the right utility to upgrade... "Update utility cannot open the requested file").
BUT I still have that HW problem afterall.... so I guess it still has to go back to warranty right ? This isn't a big deal since Orange is VERY prompt (I guess I'll get it tomorrow or monday morning, the delivery guy brings a new one and goes back wiv my phone, quite nice !), and I have a button which is stucked (from the begining) anyway ^^
While I'm writing this my phone is docked and synced, and it seems fine.... but, I guess, as soon as I will reset it will start over again.... I'll keep you posted.
Anyway, I'm no longer desesperate and that's good news (for me ^^)
++
niko
yip
ok, everything's back to original.
Actually, it works well when docked, but it freezes/melted screen as soon as I tried to use it on battery, so that I'm quite sure it has something to do wiv WM6.... I'll post that on some crossbow threads this weekend if I have time enough (there are so many of them now !)....
But once more, if YOU read this, keep that in mind.
Hope you guys won't have that kind of failure while trying it.
++
niko
confused
I am having the same problem except the screen showing white scanlines everything else is working on the handset. Could it be a LCD Problem?
Me too...
I have the same issue (black/colored vertical lines and a white screen). I think it has to do with upgrading to WM6 or with overclocking with batteryStatus, not sure. This are the suspects in my opinion....
Now I downgraded to WM5 but the problem seems to persist, I disabled batteryStatus and will see if the situation improves... crossing fingers
Uhm ... possible Overclocked!
I have read 3 threads with same errors!
how much was your highes clock? do you use it for navigation? long time on highest clock or only for speed up?
i dont have a problem with scan lines but with my prophet i use the scaling option and go max to 234 i also set to 234 when using certain apps.
is this damaging to my prophet?
at the moment trying to upgrade to PDAViet 4.0.0.0.3 with a world of pain but thats another topic!
not sure why but as soon as the timer for the screen kicks in it turns right back on.....anyone have suggestions?
Unlocked ATT 750 with ATT leaked WM6.
It is something to do with the brightness setting. Put it 40% or more.
Hello
I've got a Treo 750v with the latest WM6 installed and I'm getting the same problem too. I've got it set so that after 2 minutes, it turns off, but instead of doing so, the password screen comes on and stays lit till I put it to standby manually!
The other problem is, I've got mine to auto connect and check for messages via GPRS, and whenever it does this, the screen turns on and never turns off again.
I've had to turn this feature off else when I wake up, in the morning or even during the day when I'm at work, I find that this kills the battery!
Any ideas?
Thanks
D.C
I ocasionally have the same problem, I do a soft-reset when it happens.
I couldn't reproduce the problem, but when it happens again I'll investigate the brightness setting...
It really is the brightness-setting...
Isn't that redicioulus?
so heres a weird thing that happened last night. i was playing around with tornadopowercontrol and i accidently set cpu speed to ultra slow. it stayed workin for a few seconds and then turned off. got scared, i turn it back on, it loads to the main home screen, loads up tornadopowercontrol (had it in the startup mode -hidden) and then it turns off and reboots. Not sure why, maybe cause its still stuck in that low cpu speed? this continues to happen, not sure how to stop it.... any suggestions?
Try a hard reset! From the Wiki: "Turn off your phone, then press both soft keys next to D-Pad and power on device. After moment release both soft keys. On the black screen asking for confirmation press "green phone" button and wait couple minutes for phone to initialize"
Sync it and edit your Power_On.lnk inside \Windows\ and put it back to whatever speed you had it at,
I don't think he can get it to this point!
thanks a lot!!!!
I was just about to try the ultra slow thingy
prajith said:
thanks a lot!!!!
I was just about to try the ultra slow thingy
Click to expand...
Click to collapse
lol no problem ya couldn't sync it to reset it back to original settings. ultimately required a hard reset hope i have my stuff backed up somewhere! lol i tried puttin it to a lower settin cause i was just listening to music and didnt' think i needed it running at 252. but i guess 116mhz is much to low, anyone know wats probably the safest (and lowest) speed it can run at?
i had a similar problem but managed to solve it without hard reset. i powered up the phone with pc cable connected ... lucklly it was able to connect through ActiveSync before programs from startUp and i`ve managed to overwrite the file.
my vox works ok even with 140 as lower setting but SmartToolKit seems to lockup way too often ... right now i`m using 164 and i haven`t see a lockup in about a week or so.
264 seems to be the upper limit (damn rocket) , beyond that it start to act crazy.
lastOne said:
i had a similar problem but managed to solve it without hard reset. i powered up the phone with pc cable connected ... lucklly it was able to connect through ActiveSync before programs from startUp and i`ve managed to overwrite the file.
my vox works ok even with 140 as lower setting but SmartToolKit seems to lockup way too often ... right now i`m using 164 and i haven`t see a lockup in about a week or so.
264 seems to be the upper limit (damn rocket) , beyond that it start to act crazy.
Click to expand...
Click to collapse
is the 264 mhz stable? or does it lock up? anything with smartoolkit locks up i just turn it off nowadays
Hello everyone. I wasn't sure where to post this issue so hopefully this is the right place.
I own a HTC Diamond 2 clone I purchased from ebay. It has WM 6.1 installed. Everything works just fine except for a backlight problem I can't control. Unfortunately when I manually turn off the screen or when the phone actually dims the screen to complete black for inactivity it somehow turns itself back to full brightness after 2 seconds. I've tried everything in the settings but nothing helps. I've made sure there are no applications running that could be initiating it to turn on. I'm at a total loss...and my battery dies within hours obviously since it won't stop turning itself on.
Has anyone had a similar problem? Any ideas? Please help i'm desperate.
Thanks