Related
Hi Guys.
I've had my orbit for about 3 weeks now, and its been perfect. I had a spare 512mb microSD card lying about so I used that, but my 2Gb microSD card came in the post yesterday.
I put the card into the phone, and then plugged the phone into my computer via USB. The screen turned off, and no matter what I did, it wouldn't come back on.
I reset it using the small button on the side (sticking my stylex pen into it) and it restarted itself, showing the splash screen no problem, but as soon as you would expect the Today screen to show, the screen goes off. It get's weirder, because if I hold down the camera button to turn that on, the screen switches itself on, and you can use the camera no problem. If i hit the windows key, the menu appears, but if I try clicking an icon, the screen goes dead again.
Also, sometimes (not always, don't ask why) if I leave it for a couple of minutes, the screen slowly appears, as if the backlight is very very dim. But the second i tap anywhere, or touch a button, it goes off again.
I can still answer calls, and my alarms still go off. The phone seems to work perfectly, but just not the screen. I think that it might be the backlight having been turned so far down its off, but I don't know how I would go about reseting that.
Sorry for the long story, but any help would be greatly appreciated.
Cheers
have you tried to make a hard reset?
Man I had the exact sane issue. Its to do with the backlight. I had to angle the screen to try and see anything on it, then changed the backlight to full and made sure it didnt switch off after certain time, everything fine since then. dont know how it happened.
exactly like fubofo wrote,try to unplug,screen should be visible again, check backlight prop.-and plug it in.
i have the same problem this appears sometimes.I think this is a damn bug that appears randomized.It happend to me like 6 times.I have the o2 xda orbit with german o2 rom.What's about yours? it dims the light under the normal makeable settings this sucks.And the camera works because the light settings goes automaticly to the highest settings in camera mode.
Hi guys,
I remember having that problem but it was when I tried some programs, including HTC X-button and another called Invisible Shooter. I haven't got any further incident after uninstalling them.
Do you think what you've encountered with may also link to some program you've installed?
BUSPBP
Totally confirmed! Had same issue after replacing a touch screen. Thanks, guys, for a clue!
Hi, i have just got a new xda orbit and noticed that when the backlight goes off after a set period (30 secs), it seems to be still lit but only very slighty, so at night you still see the today screen etc. But if i press the power button then the display goes off. Is this correct ?
The reason im asking as i have been using an xda mini s for over a year and when the backlight times out the display is not visible at all in the dark. You have to press the power button to see the screen again.
Hope this makes sense
Yes, that is fine. The dim backlight will go out in time too.
MaskedMarauder is 100% right. It will go out eventually.
Ok thanks guys for the quick reply, just obsevered it last night and noticed it was different.
Thanks again...
I've tried posting about this before, but it never gets answered - i've got a mda III, and that dims to brightness 1 (from within the registry), but will never go out - regardless of what rom i've tried.
I've also noticed that i can force set it to 0 in the registry, but thats the overall screen brightness. None of the other reg keys (putting bkl1:, etc in the various power keys) seem to work.
Any one got any ideas or utils to sort this? I'd try to code this as there are some code samples which allow you to force this, but i've not got VS
Like you i've tried all the registry edits i can think off to no avail. I too have a wizard and find this irritating - plus backllight stays on when media player on etc.. No difference with wm6 so i guess it maybe a hardware issue. I use a small app to turn off display when apps are running and i want the display off.
I use backlight time of 30 secs and power of 1 minute - so overall similar to my wizards backlight time of 1 minute.
why not..
why not just pres the I/O button on the side to turn off the backlight when u don't want it on? obviosuly a bit of a hassle, but if u get into the habit of doing it, no problems
Because that puts the device into standby and turns everything else off too (except the phone etc.) So if your listening to music your plunged into silence.
I had an XDA2i (Alpine) previous to my Orbit and I actually prefer the dimmed screen.
A brief press on the 1/0 power button WILL make the device go into standby.... BUT...
press and HOLD the power button for LONGER than 2-3 seconds and it toggles the backlight on and off, whilst STILL keeping the device on!
hope this helps
Joe
I'm on a g2, running cm7.. when ever I hit power button to put phone to sleep, the phone light goes black.. that's normal, obviously... but when ever I tick power button to awaken it, the home menu back and search keys light up but the screen goes black. Ill have to press power off and on button like 6 times for the screen to actually show up.. each time, quite annoying..
Any idea y? Thanks guys!
are you overclocked?
screen on/off animations?
using setcpu?
I've had some issues with screen on not responding as it should, and this is what fixed it for me:
-lower overclock (I was at ~1.3 ghz, went down to ~1.0ghz)
-disable screen on/off animations
-change setCPU from ondemand to interactive
obviously, what worked for me may not work for you.. but you might give that a shot.
I have mine set to performance? I don't really know the difference.
However, I don't use setcpu, I use cm7 settings the one that gives you the "warning this may cause blah blah blah when changing settings)
But I have it set to 1ghz.. ill test it though thanks!
I have almost the same problem but mine does that once in a while. The phone is not rooted. So I don't use set cpu or anything like that. The problem that I am having is when I turn the phone on (after it is shut down) it does not display the htc logo, then when it gets to the g2 it does not display that either. When the finishes turning on the screen is still black. I can press the digitizer where I know the unlock is and I can feel it vibrate then when I unlock it I can still feel it vibrate when it unlocks and it takes about 2 to get the screen on from this just pressing the on and off power button. Some1 please help.
Sent from my T-Mobile G2 using XDA Premium App
Well it turns out it was because I set it to powersaver, I set it to interactive and it works great now! I noticed my web browsing speed increased to. No more slightly lag scrolling/zooming... maybe perfomance govern is to fast?
I notice performance made quadrant skip cpu and go straight to graphics and data write and scrdw up the test, and even youtube videos would play like 2 seconds, to 8 seconds, and skip all the way to the end, with choppy playback..
Emulators ran flawless at 1.3ghz hooked up with wii remote.. dk country 2 is epic
Hi guys.
So i managed to get my desire wet/damp and whilst it still works it has developed 3 issues:
1) The weirdest of all - the phone wont go into standby, as soon as you press the power button or let it timeout the screen goes off and they instantly turns back on to the lock screen. If i leave it, it will timeout again on lockscreen and come back on, it does this forever. I have done factory resets etc, all the same. Weird right. As i result i would like to reflash the mod and see if that fixed it as assuming its software related (somehow).
2) Volume keys do not work - think means i had issues getting into recovery. Finally found a widget to do it and then....
3) Trackpad does not work in recovery so i cannot re-flash or try any new rom to see if that fixed (1)
Proper catch 22
Any suggestions appreciated.
Thanks
Bridgstfer
Install 4ext touch recovery.
Update after installing touch recovery
OK I HAVE AN UPDATE:
The plot thickens but i have managed to S-OFF my Desire and eventually install Clockworkmod Touch which obviously doesn't require me to use the trackpad button so I was able to use Recovery. I wiped the phone and tried reflashing the ROM i had been using (Insertcoin) but this made no difference, the phone still keeps waking up immediately that it goes to sleep (either with power button or by sleeping timeout).
So i decided to install a completely different ROM (CM10_VJ_4.1.2_v3.0) and this installed fine. Now the phone will go to sleep and stay asleep if I press the power button. Problem solved I thought!
Now when the phone is asleep 50% of the time, trying to wake it with the power button will cause it to reset immediately and goto the white HTC screen. When it restarted it sits on the unlock screen and keeps timing out, screen goes off, then immediately on again - weird. If i unlock and lock with power button it will behave. For some reason the Search key will wake the phone every time no issues. Only the power key to unlock causes it to reset. Phone is sleeping according to Battery info.
Any other suggestions for what I could try. Could this possibly be something hardware related now? If there a way i can log the key presses or reason it wakes/resets?
Any help really appreciated, the phone is pretty unusable with this reset issue now.
THanks
Bridgstfer
theres a few videos on youtube, if it was me i would take the phone apart and clean all round the buttons. mite solve it. But as it got wet, the water could of damaged something in around the trackpad r power button, hense always waking the phone.
Sent from my HTC Desire
Thanks mate. So i tried this and installed CM7 today and have discovered something. As i said above the volume down button doesn't work and the volume up only works with some persuasion. Once i installed CM7 the problem where I lock phone with power key and it instantly wakes up now persists (on the JB rom it at least stayed asleep but reset if power button was pressed again).
However whe i changed the display timeout to 15seconds i watched as it timed out and instantly woke then noticed the volume would increment down one notch each it woke up again. This leads me to think that rather then the volume down not working at all it is actually stuck down permanently and could be causing the issue here. Is there any way I can find out if this is the case and disable the volume keys through software or do i need to open up the phone and disconnect it?
Thanks for any help - i think we are getting there!
Bridgstfer
I actually worked out that the trackpad is being pressed down constantly too because on CM7 when i disable trackpad to wake the phone actually stays asleep. Stil the phone resets if i try to wake with power button though, must be something to do with the button combo being held down.
Is there any way to disable both volume and trackpad buttons at the kernal/system level?
Tried button remapper but does not allow to remap the trackpad press.
With a file explorer, go to
system>usr>keylayout and modify bravo-keypad.kl.
I'm just back from holiday where my Desire had a ten-minute swim in sea water!
Naturally it was stone dead when I remembered it was in my pocket as I waded across an inlet which was supposed to be ankle- deep but was over 1.5 metres in places
I thought there was no point in drying it out without first removing all salt so (minus battery and cards) held it under a tap for several minutes then left it to soak in tap water in the sink for 30 minutes.
I then dried it over gentle heat for a few days then tried the battery. The vibrator ran continually and the white LED flashed randomly but nothing else. After another two days drying it booted - but only into Fastboot and the vol switch didn't move the cursor. But after another two days - it worked almost perfectly! The vibrator is dead and the screen a bit streaky, but all the other sensors work just fine and it's quite useable.
I had been logging the hike using My Tracks and it actually shows the course going a short way into the sea.
do you have an assurance or warranty?
if yes-->change phone.
abaaaabbbb63 said:
With a file explorer, go to
system>usr>keylayout and modify bravo-keypad.kl.
Click to expand...
Click to collapse
Thanks for this. I actually got an app that let you remap the keys but it does not let you do anything to the trackpad click button (which is now the one stuck down). See photo of whats in my bravo-keypad.kl file here:
http://dl.dropbox.com/u/64089332/20130106_194659.jpg
Any other way i can disable the trackpad completely. Perhaps at the kernel level?
Thanks
As we all know(or should know if you read around the forums) that there is an issue with "sod". Now these sods are not the same as the sod i was familiar with before 4.2. Before 4.2, the device(s) were for all intensive purposes not alive. Sure you could connect to adb, but the device was "dead" until you pulled the battery and rebooted. But with these 4.2 "sods", the device is alive, with the exception of the screen not being able to turn on. Phone calls and messages still come in. notification sounds still play, and you can use the volume buttons to raise/lower the volume. But you still have to pull the battery and reboot for the screen to come back on. Running logcats via adb doesnt seem to show anything related. Well, ive found a way to reproduce these 4.2.X "sods" while the device is awake with the screen on. I can reproduce it at will, and have had other users confirm this. What i do is this.. I go into the main settings, display, then brightness. Turn off automatic brightness if its on. Now adjust the brightness, up, then down, then up(back and forth, but take your finger off the slider when you go up then down). now press ok to set the brightness. Go back into the brightness setting and repeat. Eventually(sometimes seconds, sometimes minutes) the screen goes completely black, like its off, but the device is completely awake. same as these 4.2 sods, phone calls and messages come in, notifications sound, etc. Only difference is the device screen is on when it goes black instead of it being off. The symptoms are the same. This behavior leads me to believe that it most likely isnt a kernel issue like many believe. I believe that its related to some coding that controls the screen. As we know, every rom/kernel has shown this behavior, even stock and unrooted(some more, some less). Personally, i had 3 of these sods last month(trinity kernel/rasbean rom), but i know that some users have them many times a day unfortunately. What could it mean that i can replicate this behavior on an awake device? Any more thoughts about this?
maybe someone using another kernel/rom can try to reproduce this?
I haven't tried your method yet. I'll and post my results here. I was able to replicate it using another program (check the links below)
But reading your post, I'm sure now that SOD has to do with autobrightness or brightness control (knowing that, maybe it is easy to solve?)
Check my posts:
http://forum.xda-developers.com/showthread.php?p=35205418#post35205418
http://forum.xda-developers.com/showthread.php?p=35496824#post35496824
Check my post here:
[URL="http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638"]http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638[/URL]
whre I answered to that phenomen. I was on RBJ + franco r348 that time
I can't reproduce (force) it now with RBJ + franco r360, I tried about 100 times.
Just wanted to post my results, maybe it's too early to tell as r360 is too young.
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
Maybe because OMAP is abandoned at 3.0.
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Jessie-James said:
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
if your device wakes, even after a few presses, its not sod.
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
pressing and holding the power button for 10-20 seconds will force reboot those devices.
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
MondoMor said:
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
Click to expand...
Click to collapse
wouldnt it be easier to just pull the battery? thank you for your observations btw.
simms22, I actually think it is a kernel issue. I only experience SOD problems when i use a custom kernel. Also yesterday I flashed stock 4.2.1 and tried for 10 min to replicate SOD using your method - I could not. Today I tried again - nothing.
simms22 said:
wouldnt it be easier to just pull the battery? thank you for your observations btw.
Click to expand...
Click to collapse
My phone is in an Incipio case, and it's more of a pain to separate the case, especially if I'm in my car or out hiking or whatever. I've gotten pretty good at doing it blind. Also, years of running Windows have made me anal about doing orderly shutdowns. :laugh:
Forgot to add earlier: I was unable to replicate with the technique described in the OP. But as long as someone can get this to happen on demand, it ought to be solvable.
Edit: although I got the SOD in normal usage a few minutes after trying the technique in the OP. Maybe the display SODs on some specific number of brightness changes? That would explain it happening more often with autobrightness, also.
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
Just hold down the power button for several seconds. Continue to hold down the power button until the screen blinks off and the boot logo appears.
We are flooding here.. lets discusse this other place and leave the devs alone here
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
andQlimax said:
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
Click to expand...
Click to collapse
When I was running the first few nightlies of CM10.1 it still did the "sod" on me. By default the animation settings are at 1.0. Not sure if it's different on stock.
I've had several sod's daily for last few day's and today finally flashed RBJ from the beginning plus dax's modified kernel and now i'm in watching phase. So far so good.
I have time without any sod... Maybe because I'm trying not to use auto brightness or because of the lastest versions of Francos kernel... Stock ROM
Sent from my Galaxy Nexus using xda app-developers app