After Upgrading to windows 6 Some times My phone screen suddenly fade to white , blue or black.. I've tried different roms and still the problem exist
can someone help me? what is happening to my universal? is it because WM6 still not stable?
please some one help me
free_10w said:
After Upgrading to windows 6 Some times My phone screen suddenly fade to white , blue or black.. I've tried different roms and still the problem exist
can someone help me? what is happening to my universal? is it because WM6 still not stable?
Click to expand...
Click to collapse
Which Radio Rom are you using ?
Try another
wout
I've been using 1.17 but when I use 1.15 the screen also fade to blue or white
Try without sd card
or
try older (reliable) wm5 rom
wout
I already try KAMAL WM5 but still it happens and I also forget to mention that when the screen fade to white or blue my phone suddenly become hot..is there any possibility that the problem is from the hardware?
That doesn't sound good.
could you try another battery ?
and turn wifi of
was wifi on ? when screen went with/blue
wout
Yes, I have try another battery and the wifi is off..
The screen went blue when I was receiving sms or when I want to send sms.
sometime when I left the phone standby for half an hour the phone cannot be turned on and I have to press the reset button and after entering the splash screen the screen went blue/white again so I have to reset several time
i think its something e related to the vibrate? its shorted or somehting and the power is going there but no vibration.. thus causing the overheating and the freezing.. im not sure but maybe.. also have you dropped the machine?
Appears to be a hardware problem. You may try this, it may work:
1. Remove the battery. Keep the battery out at least for a few hours.
2. With the battery out operate a few keys randomly. Also operate the on/off switch a couple of times.
3. Remove your sim card and storage card.
4. Put the battery back.
5.Allow the booting process without intruption.
6. If it works well just switch off, remove battery and insert the sim card and sd card. reboot
Although it sounds a bit wierd it does work in some cases. Worth giving it a try.
thanks Wout,dj_gabzz,d_ranade for the help
I have installed the official WM5 and now it seems ok..
it means that the problem is because of the roms not the hardware..
and once again thanks a lot guys
free_10w said:
thanks Wout,dj_gabzz,d_ranade for the help
I have installed the official WM5 and now it seems ok..
it means that the problem is because of the roms not the hardware..
and once again thanks a lot guys
Click to expand...
Click to collapse
Glad you could solve your problem.
same here man.. glad you got everything straightened out, i hope you dont encounter further problems..
once again thanks
Hi
Today this has happened twice in same day -When ever my Vox is lying Ideal the network indicator blinks also if its on charge i wil get a orange LED.but if I press any keys (lets assume to make a call) the Screen still remains Blank...
This problem I had also faced earlier my O2 NEO (Prophet) before it went dead completely!!
I am worried is it an indication of slow death!!
P.s I dont wanna lose the vox as i lost my beloved prophet
Still waiting for some useful tip
which ROM?
I guess you are talking about similar problem as what I have.
http://forum.xda-developers.com/showthread.php?t=394358
I usually get this problem once in every two days. I uninstalled all the extra apps leaving very few which I am sure wouldn't cause any harm. Since then I haven't seen this problem. Its been more than two days.
What I do when I get this problem is, remove the battery for 5 seconds and put it back before I attempt a restart. I don't think you need to worry about this too much if not for the calls that gets lost when the phone is in this state.
Sometimes it happens to me where the screen, once it goes blank, will not come back on. I usually just reboot it and forget about it. I've had my vox for a year and its happened on every rom I've used probably about 5 or 6 times.
sankarrv said:
I guess you are talking about similar problem as what I have.
http://forum.xda-developers.com/showthread.php?t=394358
Actually My vox does not show any thing on the screen totally blank and just the GREEN LED (network) blinks...
Thats also true tht I sometimes goes off completely and its too hot to handle.
In my case (blank screen) i usually make a call on my cell and it comes out of the blank screen to display incoming call...
I guess u shud try the same thing rather thn removing the batt ...as i had already lost my O2 Neo in the same manner.!!
I think we still need a solution on this
Ps. My ROM is Windows mobile 6.1 v1.0b for Vox by Dr. Martin Gonzo
Click to expand...
Click to collapse
hey...so i think there something really wrong with my wizard...
when im just using it sometimes when i switch it off ( not ike completly just press the button once...) and then when i want to switch it on again it doesnt work...! its still on cuz the green LED still works but i get no picture...so i have to take aut the battery and restart it...!
whats wrong there<???
and then i have another problem and its that sometimes when im starting the wizard again after that happened it turns to white screen after the second boot screen (but its not the same moment every time...some time between the second boot screen and till its started up )...or there are wired stripes on the screen for a few seconds and then it restarts...or sometimes it just stucks at the 2nd splash screen or some other time during starting up...
i already switched the rom so i used crackings 6.1 rom before now i use his 6.5 rom...
i thought it could be the cpu??
i runned it on 240 or 252 for like 6 month now...
does anyone know how to fix that or is there no way of fixing it?
thanks so far
nick
the-nj said:
hey...so i think there something really wrong with my wizard...
when im just using it sometimes when i switch it off ( not ike completly just press the button once...) and then when i want to switch it on again it doesnt work...! its still on cuz the green LED still works but i get no picture...so i have to take aut the battery and restart it...!
whats wrong there<???
and then i have another problem and its that sometimes when im starting the wizard again after that happened it turns to white screen after the second boot screen (but its not the same moment every time...some time between the second boot screen and till its started up )...or there are wired stripes on the screen for a few seconds and then it restarts...or sometimes it just stucks at the 2nd splash screen or some other time during starting up...
i already switched the rom so i used crackings 6.1 rom before now i use his 6.5 rom...
i thought it could be the cpu??
i runned it on 240 or 252 for like 6 month now...
does anyone know how to fix that or is there no way of fixing it?
thanks so far
nick
Click to expand...
Click to collapse
Open the phone and check the connection between the mother board
and the video (its the push connector on the back of the MB) if its tight
you will have to take the lcd section apart ,the other end of the ribbon
cable goes to the lcd and digitizer its a tab locking connection with clear yellow tape over it. check and see if its all the way in ... if that don't fix it get get a new LCD/digitizer from Ebay .. it plugs in i one piece ...
then your off a running ... id watch the over clocking too ... when you
OC the cpu everything runs faster and heat builds up and can damage the phone .. i have seen several OMAP versions here that OC when needed
and return when the phone is idle ..
thats my 2 cents worth on that
the-nj said:
hey...so i think there something really wrong with my wizard...
when im just using it sometimes when i switch it off ( not ike completly just press the button once...)
...
thanks so far
nick
Click to expand...
Click to collapse
If you are sure that your problems are not rom specific (you faced the same problems with different Roms?) then maybe this is the solution for your problem .
Good luck finding what's going wrong.-
Same thing has started happening to me. I just press the reset button and it restarts just fine. I don't see why others are thinking its a problem with the LCD. A reset shouldn't fix that (I'm guessing).
ave you checked the battrey?
ya so the problem i have is not the one descibed in the video...
its differnet...the stripes are ther not the whole time ...it comes sometimes and then there are these stripes and then the screen turns slowly white...and then sometimes it restarts or its just stays white...
and when i normaly switch it off then the leds are still working just the screen wouldnt turn on...
so i really have no idea whats going on there...i tried to make a video but now it didnt happen for almost 4 days so i just hope that its not happening again...
but its really wired and i think its the cpu cuz i cant think of another reason for that...
I have read this forum and many other internet sites until mys eyes cross!
I have Sprint HTC Touch Pro2 running winmo 6.5. duelboot android.
I have flashed many times and the problem isnt fixing itself.
Its like when my backlight goes to sleep I cant wake it up. I can still here the
phone ring and answer it.. just cant see anything after it has gone to sleep.
In Android i dont have this problem..
Anyone know where the registry is to do some editing??
Your help would be so APPRECIATED!!
Thanks in Advance.. Tammy
Tp2 Zombie
I Have the same issue. I Recently tried to flash back to 6.5, and somehow it all went wrong and i got the white screen of death. i could get to the boot loader(tri color) screen but it would just go right back to that White back ground with Green letters 'htc'. Now I finally found the post that helped getting to that tricolor screen then loading rom. IT WORKED! then i tried the sleep/ pwr button and sure enough it STILL WON'T WAKE!!!! Seems like the only answer is to break down and get the droidX. but i need windows for a 3rd party program i use....so i might just stick to the lil slide fone i have as a back up...
I just leave the light on 30% if Im expecting any txts or calls, when Im not I just turn the light out I can still hear incoming calls and if I hear a couple txt I pull the battery and stick it back in so that I can see the screen again.. its all I can do for now.
Im amazed with so many smart folks here I havent had anyone offer any fix's yet??
I have been hoping for easy registry fix.
Good Luck and please let me know if you get any help with yours??
yes, its becoming a problem. pulling out the battery to get the screen is more damage than good
Hi. I have been running pacman v22.0.1 for quite some time now and I could quite easily make and receive calls with no problems, the rom was fast and battery life was great. But quite recently, I received a call and answered it spoke but when it came to ending it, I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that. But I switched to another rom then wiped everything and flashed pacman again but still had the same problem. Is there anybody who is facing the same problem or has a solution? I have tried on 4 different 4.2 roms now and have experienced the same problem with all.
Just uploaded a very, very long log cat if you are a dev or have knowledge of logs, please read!
Problem solved, it was my screen protector which was covering my proximity sensor and jelly beans behaviour with the proximity sensor caused it to stay off. When buying a screen protector always make sure it has a hole or gap of some sort for the proximity sensor. The bug in the log cat was something else which was fixed by a build.prop tweak.
My radio is 3831.19.00.110
ifti786 said:
I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that.
Click to expand...
Click to collapse
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
paulie-uk said:
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
Click to expand...
Click to collapse
That could just be it: the reason for my problem is my impatience! Still need to check though...
No, that didn't fix it. I think it might have something to do with my proximity sensor because on vipersaga, it used to turn the screen on when I moved my phone from my ear but now it doesn't so I have to press the power button.
Also have the same problem on jelly bean fire
Sent from my HTC Desire S
Please help because I really want Jelly Bean 4.2 but at the current moment, it looks like my desire s is incapable of running it!
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
sanilii said:
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
Click to expand...
Click to collapse
Wipe all partitions except sd card AMD done this on pacman v22.0.1, JellyFireBean, JellyTime, flinny cm10.1 and AOKP redefined. I have just flashed a new radio and will check if that fixed it
Flashing a new radio did not fix the problem please somebody help!
ifti786 said:
Flashing a new radio did not fix the problem please somebody help!
Click to expand...
Click to collapse
I've got the same problem. My screen won't turn on after I move the phone away from my head after a call, altho I can turn it on with the powerbutton somehow. Happens on all JB ROMs for me aswell.
I tried Proximity Sensor Finder app from play store and it says 9cm when theres nothing infront of the sensor, then goes to 0cm when there is something, but doesn't go back to 9cm when the sensor is free again. It only goes back to 0cm when I restart the app.
I don't know whats the problem, but I think its software related.
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
NVardan said:
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
Click to expand...
Click to collapse
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
ifti786 said:
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
Click to expand...
Click to collapse
Maybe you should upload the logcat in the PACman thread.
Ok will do that now
Sent from my HTC Desire S
NVardan said:
Maybe you should upload the logcat in the PACman thread.
Click to expand...
Click to collapse
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
ifti786 said:
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
Click to expand...
Click to collapse
Unfortunately I am NOT a developer so I can't help you.
You must copy-paste your logcat in a .txt file and upload it in the PACman thread.
Sent from my Desire S using Tapatalk 2
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Right, I've just had a look through the logcat and i've found a bug. I'm going to try some build.prop tweaks and see what the results are. I will let you know but please bear in mind that it might take some time as I am having some very important exams coming up so I'm going to be revising in most of my free time.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Do you have a screen protector on your phone by any chance?