Hi ,
I noticed this on all the WM6 Roms ( never even used the real WM5 ATT ROM)
But when you open the qwerty keyboard and start typing fast the light goes off and then when you press any botton it goes back on. I`m just wondering if its my unit or is it just ROMs flaw ? I didnt see anyone talking about this so I`m starting to think its my unit. Thanks in advance.
Mine's done that. It usually goes off when the phone tries to do something else, like checking or downloading email.
Also, turn off the word suggestion feature, that just caused problems such as missed letters, and I think it added to the light turn off problem as well.
harlenm said:
Mine's done that. It usually goes off when the phone tries to do something else, like checking or downloading email.
Also, turn off the word suggestion feature, that just caused problems such as missed letters, and I think it added to the light turn off problem as well.
Click to expand...
Click to collapse
yeah I always turn that off. didn't notice that it happenes durring something. thanks for the reply
yozh said:
Hi ,
I noticed this on all the WM6 Roms ( never even used the real WM5 ATT ROM)
But when you open the qwerty keyboard and start typing fast the light goes off and then when you press any botton it goes back on. I`m just wondering if its my unit or is it just ROMs flaw ? I didnt see anyone talking about this so I`m starting to think its my unit. Thanks in advance.
Click to expand...
Click to collapse
i don't think it particularly happens on wm6. it happened when i used jap wm5 by softbank, and it still happens with lvsw. thought it was more like a hardware issue.
qtotter said:
i don't think it particularly happens on wm6. it happened when i used jap wm5 by softbank, and it still happens with lvsw. thought it was more like a hardware issue.
Click to expand...
Click to collapse
ok thank god Im not alone
qtotter said:
i don't think it particularly happens on wm6. it happened when i used jap wm5 by softbank, and it still happens with lvsw. thought it was more like a hardware issue.
Click to expand...
Click to collapse
it used to happen to me on black pro 3.0
It's happened on all WM6 ROMs that I've tried (Custel, LVSW, JJ). There was a dicussion on this, and changing the word completion helped but did not completely resolve the issue.
BorisTheSpider said:
It's happened on all WM6 ROMs that I've tried (Custel, LVSW, JJ). There was a dicussion on this, and changing the word completion helped but did not completely resolve the issue.
Click to expand...
Click to collapse
I always had the it off, just "Enable Auto Correct" on and since day one and it does it, it does it less on the black IV, but still does it.
Related
Hi forum!
Before anything, thanks for your invaluable help and support, without it I would feel even more lonly on my PPC life
OK, said so...
I'm having currently some problems with the phone part of this great device. Sometimes when I answer a call (with the hardware key) it takes 2 to 3 seconds before I can hear anything from the person calling me. The same happens when I hang. It takes time to hang the conversation, so I never know if it's really hanged..
Lately I'm having also problems with the "today" app I think. It never shows up and the upper bar (status?) does not change when I receive a call.
I went trhu a hard resseting and restore (Sprite) process 1 week ago, but I had the phone problems before that...
Thanks a lot for your help.
by the sound of it, you have upgraded to the wm5.0 rom, i have these problems also, until there is a known fix for the minor bugs, with the today screen you can just go into settings and today, then come out again, and what wasnt there before should be there now, also , have you tried to upgrade the radio rom too??? 8)
thanks for your answer! But I'm currently using wm2003. Though I'm considering switching to wm5 now we can if I don't get a solution to this
I normally use the phone for work-job and this minor things annoys me big deal!
joey jojo said:
by the sound of it, you have upgraded to the wm5.0 rom, i have these problems also, until there is a known fix for the minor bugs, with the today screen you can just go into settings and today, then come out again, and what wasnt there before should be there now, also , have you tried to upgrade the radio rom too??? 8)
Click to expand...
Click to collapse
heelp
PLease, someone help!
did a search and nothing really came up...
My problem is that when i make a phone call i cannot hang up. The system seems to lag. i touch end...nothing happens, i push the red hangup button...nothing happens, then after SEVERAL seconds it finally hangs up.
Did not have the problem with wm5 but every rom for wm6 has had this issue on my phone.
Currently have blackshadow 4.0
radio 1.41
Please help!!! its really annoying when i dont want to leave a voice mail but cant hang up.
I appreciate any help i can get!
jwagman1 said:
did a search and nothing really came up...
My problem is that when i make a phone call i cannot hang up. The system seems to lag. i touch end...nothing happens, i push the red hangup button...nothing happens, then after SEVERAL seconds it finally hangs up.
Did not have the problem with wm5 but every rom for wm6 has had this issue on my phone.
Currently have blackshadow 4.0
radio 1.41
Please help!!! its really annoying when i dont want to leave a voice mail but cant hang up.
I appreciate any help i can get!
Click to expand...
Click to collapse
i am running black shadow with radio 1.43 and i have the same problem, the response time for hangup on shadow is really long!! i have to press the red cancel button 4-5 times to get a call to end
Try the latest LSVW 0616, it functions well and seems very stable.
Good luck.
simple said:
Try the latest LSVW 0616, it functions well and seems very stable.
Good luck.
Click to expand...
Click to collapse
Excuse me but was that REALLY helpful? If I was to post "my Chevy truck won't turn off" would you post "get a Ford truck, they do"??
(no, my post wasn't helpful either)
anyone else have this problem or know how to fix??
I had the same problem with the 143 radio.. First I installed the 141 radio and then reinstalled Shadow. works fine now.Try reinstalling Shadow.
could this actually be the radio? only reason i ask is i had just flashed radio 1.43 and shadow at the same time, can someone please tell if it is jus a radio reflash or do i have to go through and reinstall shadow as well?
There is a new 3g dialler made available by Jasjamming at his new home that will now work on the Shadow rom, this will probably help you.
jwagman1 said:
anyone else have this problem or know how to fix??
Click to expand...
Click to collapse
ew
ewewewewewew
Dr Puttingham said:
Excuse me but was that REALLY helpful? If I was to post "my Chevy truck won't turn off" would you post "get a Ford truck, they do"??
(no, my post wasn't helpful either)
Click to expand...
Click to collapse
Actually that might be helpful because the Chevy maybe doesn't work. I have had the same problem with Shadow and had to switch. I am using 1.43 and Schap's 3.30b now and it seems to be better. Custel's worked ok too - waiting for his next update.
Mark
Edit - Based on other posts maybe I should switch to 1.41.
Is this what you do just to increase your post count?
JBaxendale said:
ewewewewewew
Click to expand...
Click to collapse
boz said:
There is a new 3g dialler made available by Jasjamming at his new home that will now work on the Shadow rom, this will probably help you.
Click to expand...
Click to collapse
Sorry for being dim but i seem to have lost the address of Jasjamming's ne home, can you tell me please?
thanks in advance
fmg9800 said:
Actually that might be helpful because the Chevy maybe doesn't work. I have had the same problem with Shadow and had to switch. I am using 1.43 and Schap's 3.30b now and it seems to be better. Custel's worked ok too - waiting for his next update.
Mark
Edit - Based on other posts maybe I should switch to 1.41.
Click to expand...
Click to collapse
Maybe it DOES work, just not for you. Be careful when you dis a ROM here my friend, especially when you're using the latest GSM.
I had the same problem with Black Shadow IV using Radio 1.43 and 1.41, Now i use 1.40 and it is working fine.
i have tried 1.43 and 1.41 and neither fix this, ill revert to 1.40 and see if that fixes it.
shafez said:
I had the same problem with Black Shadow IV using Radio 1.43 and 1.41, Now i use 1.40 and it is working fine.
Click to expand...
Click to collapse
1.40 doesnt work either...
Hi jwagman1,
Dont have such a problem. When testing black shadow with 1.43 with different software, there was a lot of issues - in general the rom was very unstable etc. - almost permanently freezing. The test (not very scientific) showed that all kind of battery status software are causing problems - My solution was to reinstal the shadow only, not using any battery status packages, and the rom is performing really well now.
The problem might come also from some kind of incompatibility with the network of your carrier - as I got the 1.43 is not Hermes radio. Pumpiron579, who had the same problem also seems to be on Cingular
In such a situation I wll install new radio (e.g. 1.40), and new Rom (not shadow) too, and see.
Same problem with me on Shadow. Let's try Shadow lite or dymond 3.5 BS, it's work fine for me.
(radio 1.43)
dont mean to sound funny guys, bet everyone is trying radios and no-one is getting the right effect, might i suggest that it is a common problem within shadow.
I have tryed backdating 1.43 -> 1.41 -> 1.40 -> flashing to 1.38
this is getting silly now, 20 mins per flash lol i have been flashing for nearly 80 mins (if i was on a street i would have been arrested by now lol)
Same problem here Custel v2.5, Radio 1.40.30.00.
Hang up button (hard and soft) will not work 25%+ of the time.
Hi all!
I recently upgraded to WM6/AX3L. This excellent ROM solved many problems I had with WM5, such as SD card problems, USB connection problems with activesync and the missing sync... I am really happy with it!
I was aware of a lot of people suffering the auto-pressing of the "start button", and blaming the LCD screen and high temperature. But, in 6 months using WM5, it never happened to me.
5 minutes after installing WM6 I started suffering this problem. It is not very serious, as it only happen quite sporadically.
This problem is specific of WM6? or this is not related and it was just a random coincidence?
it's a problem of your device... many p3600 have this issue, it's not a problem releated wm6 rom.
Guybrush said:
it's a problem of your device... many p3600 have this issue, it's not a problem releated wm6 rom.
Click to expand...
Click to collapse
yes, is a hardware problem...
see warranty, in case go in a customarker centre for repaire o change the device!!
yep, it is a hardware problem, not WM6. happened to mine and they replaced the whole unit.... very good service but took 8 weeks for the new one to arrive....
What do you guys mean by autostart? I seem to notice this happening when I use my finger to press something on the touch screen then the start menu comes up sometimes. Is that what you mean?
Or does it appear by itself without touching the screen?
Thanks
touching the screen sometimes device is like press randomly the start button without start button is touched
Hi,
Sure that it's a hardware pb? I've been having this issue with different ROMS and a lot with the FAMAN ROMS. At present I'm running a home-cooked ROM and don't have this pb any more (not once in the last week).
Also with FAMAN this pb occured a lot in similar situations (almost able to reproduce it on demand), ex.: when entering the third digit of the Pin-code.
I'm not saying that this can't be an hardware issue, but as far as I am/was concerned, it seemed rather software/ROM related or a mix out of both.
Bye.
Your device is broken
I had the same problem.
Sent it for repair and got a complete new device.
There is a treat about this in the normal trinity forum (not the WM6 forum). It has nothing to do with any rom!
Just out of curiousity...
Since the Trinity P3600 is out of production now...do you think they would replace a faulty phone with the new P3600i?
ervius said:
yes, is a hardware problem...
see warranty, in case go in a customarker centre for repaire o change the device!!
Click to expand...
Click to collapse
Yea it smells hardwarish... but the strange thing is.. it started to happen 5 seconds after installing WM6... had WM5 for months, heavy use, and NEVER happened. Thats why I asked.
i bet a woman was walking her dog outside the windows at that time too
It happens to me when I try to press about the center of the screen with my index finger. Never happens when I'm tapping with the stylus though.
mm gotta give a try. When it happens, I am always using my fingers. As I lost the stylus can't try :S
I've been running the 6.1 rom for about a week now and I'm seeing an issue where when the phone is synced with the pc or when I'm in the middle of a phone call the screen goes all white. I quick key press and it goes back to normal but this keeps happening over and over.
I tried reflashing the rom, reverting to official tmobile then reflashing 6.1 and it still does it.
Anyone else?
sledwrecker said:
I've been running the 6.1 rom for about a week now and I'm seeing an issue where when the phone is synced with the pc or when I'm in the middle of a phone call the screen goes all white. I quick key press and it goes back to normal but this keeps happening over and over.
I tried reflashing the rom, reverting to official tmobile then reflashing 6.1 and it still does it.
Anyone else?
Click to expand...
Click to collapse
Touch JOGGER 3 times in 10 seconds will open Lowlight.Attention,this will maybe make your backlight always on if you don't close it.
in 080318 this function has been closed as default
That did the trick! Thanks!
My phone recently started doing this as well. I try tapping the jogger bar 3 times, but doesn't seem to do anything. I'm I missing something this seems too simple for even me to mess up...
fiveohhh said:
My phone recently started doing this as well. I try tapping the jogger bar 3 times, but doesn't seem to do anything. I'm I missing something this seems too simple for even me to mess up...
Click to expand...
Click to collapse
Nvm, fixed it by ticking the box in the JOGGR setting area.
hey, i dont understand what that did. can anyone explain.
Did you try a hard reset ?
loser said:
Did you try a hard reset ?
Click to expand...
Click to collapse
yep, i dont understand that lowlight thing, might make me sound like a dumbass haha.
i did the lowlight, and the screen popped up. iono what was there to do.
Hey just want to state that the 3 click thing was unchecked on my phone when i installed kavana 6.1 so i've click on it and i'll report back what happenes.
We'll it seems clicking the 3 in 10 seconds option in the jogger options keeps the white screen from poping up on me, will keep posted soon.
White Screen
So it i havent had anymore issues today, click on 3 in 10 option in Jogger settings.
Seems to be pretty stable now for me seems better with the 3 in 10 setting checked.
will report if i get it again.
Microsoft branded S621 Pro WM6.1 6.1 Made in Taiwan overclocked to 288 stable.
Wonder if someone could make one, a visual plug-in be sweet the pocket pc verson has a visual plug-in, so i'm surprised this one doesn't.
pocket pc verson: HHCv10final.cab
plug-in for visuals HTC-Home-pluginv1-0.cab
This just started to happen today....every time my screen timeouts...it goes completely blank...i can still hear things and receive calls...but it will stay white for like 20 seconds and then come back on... i am using Ricky's Wm6.1 any help would be great...thanks
zdub27 said:
This just started to happen today....every time my screen timeouts...it goes completely blank...i can still hear things and receive calls...but it will stay white for like 20 seconds and then come back on... i am using Ricky's Wm6.1 any help would be great...thanks
Click to expand...
Click to collapse
Hard-reset if this doesn`t solve it re-flash...
stylez said:
Hard-reset if this doesn`t solve it re-flash...
Click to expand...
Click to collapse
Interesting.... I just started having this problem as well. I went hard reset... not solved. I re-flashed (using proper procedure)... and it was solved for a couple of days... and then returned.
I then used the forum search function, crazy how that works and found this thread.
Hope that helps.
Are you using maniac's AutoKeylock ?
I have experienced this issue ever since loading Rose ROMs - didn't happen on earlier ones.
However, this last time I flashed to the latest update, I did not install AutoKeylock immediately after flashing. I left this off as I had noticed that the screen was going white 30 seconds into calls (which was the timeout I had configured in AutoKeylock) and I wondered if there was a correlation.
Can anyone else who has seen the issue comment on whether they use AutoKeylock or not. It is possible there is some change in the ROM that AutoKeylock does not handle well.
Thanks.
LiverpoolFCfan said:
I have experienced this issue ever since loading Rose ROMs - didn't happen on earlier ones.
However, this last time I flashed to the latest update, I did not install AutoKeylock immediately after flashing. I left this off as I had noticed that the screen was going white 30 seconds into calls (which was the timeout I had configured in AutoKeylock) and I wondered if there was a correlation.
Can anyone else who has seen the issue comment on whether they use AutoKeylock or not. It is possible there is some change in the ROM that AutoKeylock does not handle well.
Thanks.
Click to expand...
Click to collapse
I think that the WSOA (white screen of annoyance) is tied to the low-light function and joggr bar. Go to joggr settings, and be sure that the checkbox with the lowlight function is disabled.
I had the white screen issue for a few days, tried everything.....as soon as I uninstalled GlyphCache 65535 found here, the problem went away
Capper5016 said:
I had the white screen issue for a few days, tried everything.....as soon as I uninstalled GlyphCache 65535 found here, the problem went away
Click to expand...
Click to collapse
it comes and goes its just something messed up that happenes probably nothing to worry about, just little anoying is all.
Check power management registry settings
Hi,
I had this problem once and fixed it by changing the registry settings that control what happens when the device enters various power states. Search the forum about this as the answer is in there somewhere Hope this helps.