Develop Bugs

XDA Orbit Screen Problem

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!

Can't power off... volume goes down by itself...

Guys, need help... can't figure out if it is a soft or a hard problem...
Have had SX66 for 3 years. Almost never a problem (except for occasional thing when people could not hear me, I could hear them, but after soft reset that thing usually corrected itself).
However, just recently got a real problem.
- Can't power it off. Power buttom only works on powering on, but not on powering off.
- At the same time, the volume window pops up (with two volume sliders, "on", "vibrate", and "off), and the left slider automatically slides down on its own, preventing me from accessing anything else. When I try to do something else, go to Programs, or else, this freaking Volume window keeps popping up, and left slider keeps going down and stays down there.
When I try to increase volume, it keeps going down right after I raise it. And the volume window is almost constantly popped up.
From time to time, it disappears, allowing me to do something for several seconds or even minutes, but then pops up again.
Yesterday, I even managed to do something for several minutes without it, and even managed to turn SX66 off, although I had to press the button for a second longer than usual to turn it off. Today, no luck, can't power it off. If I press it for a bit longer, it just goes in "dimmed" screen mode, but stays powered on.
Any advice?
Thanks.

I guess, I'll have to try to clean the power button and volume slider on the side. Looking for good disassembly instructions. Found one, but more would be appreciated...
http://pdasmart.zftp.com/instructions/sx66_09.pdf

pecq said:
I guess, I'll have to try to clean the power button and volume slider on the side. Looking for good disassembly instructions. Found one, but more would be appreciated...
http://pdasmart.zftp.com/instructions/sx66_09.pdf
Click to expand...
Click to collapse
Check the wiki, there are disassembly instructions in there.

Did you solved your problem ? I have hte same only my volume go up ...

i need help
hi everyone...i need help ...coz my qtek 9090 windows 2003 is stucked when i was upgrading it ..now it shows only written serial v2.06 or usb v2.06...and screen back light is off,i tried many things...bt i failed now pls somone help me....soon ..

maybe the problem is not in button but in varistors because they can do this...

pecq said:
- Can't power it off. Power buttom only works on powering on, but not on powering off.
Click to expand...
Click to collapse
I have the same problem. I was starting to think that there is no way to turn of BA . Any help?

I have the same problem, only that mine is a HTC touch dual (niki).
the volume screen keeps popping up, and does a "volume down" command... sometimes it goes away, sometimes it comes back...

:S
Ive got a similar problem ive upgraded my BA to wm 6.1 (Xplod) the problem that i am having is that i cant seem to power it off..only way that im able to do that is by removing the battery..when i keep the power button pressed only the backlight turns off but no the phone..How to i power it off?
and secondly ive a problem with the keyboard..while writing some times i press a key and it keeps typing that for example i write s it keeps writing ssssss or giving spaces untill i press something else...is this a software issue or a hardware issue..cant seem to figure it out

I know this thread has been a while but if anyone has the same problem, you'd probably be interested about what i did.
well i had the same problem of the volume going down by itself and the volume icon pops which basically lets you do nothing.
tried all the approaches thinking it was a software issue. but i finally went nuts and took my torx screwdriver, opened the blue angel and tore off the part in the motherboard where the outer volume lever is attached to.
It worked.
So if you could with the fact you wont a direct volume adjustment at the side, you could probably try it

Phone no longer goes into standby itself

After 30 seconds or so the TP2 goes into standby, oddly mine doesn't anymore and I keep forgetting to turn off the screen and then running out of battery.
Any ideas?

Check your battery/backlight settings.

Hello,
i got the same effect.
I put the setting i.e. to 10 seconds screen off and 1 minute poweroff in accumode and 1 min. screen off and 1 min. poweroff. It wont be recognized by the phone. It stays on, with screen and device on.
At first I thougt it was some effect produced by the glight app i tested out, because i noticed this error not directly.
So i made a hardreset, but the effect is the same with the original htc rom without any mods, spl or some of this stuff.
any new ideas ?
Doktor.Wahnsinn

Just a random thought:
If you're screen won't turn off, perhaps it thinks the screen is being tapped somewhere or a button is being pressed? If so, then you've got a hardware defect...
Ideas on testing this:
Create a new Note in drawing mode. See if any random spots/lines appear on screen. Try in both portrait and landscape.
Install the Rhodium Keyboard Controller. Add a new hardware key to map. If there's a key acting up, it should be picked up here.

[Q] power button issue?

Hi all,
does anyone sometimes have to press the power button (when phone is completely turned off) twice (2 presses to turn on) sometimes?...
so just to confirm
- handset is off
- push power button once (sometimes doesnt come on
- push for second time (and powers up)
im defiantly pushing for long enough
iv have no issues with the button at all when in the UI or when locking/unlocking display
iv done a few tests where i have turned off. then went to switch on, with the same pressure and sometimes it starts with one, sometimes it starts with two presses,
do u think this is a fault? anyone experience this? normal?
just checking...
thanks heaps!

I had the opposite on my first one. When I pressed the power button to turn screen off, the screen went black for 1 sec and jumped back on lock screen.

brodiecb said:
Hi all,
does anyone sometimes have to press the power button (when phone is completely turned off) twice (2 presses to turn on) sometimes?...
so just to confirm
- handset is off
- push power button once (sometimes doesnt come on
- push for second time (and powers up)
im defiantly pushing for long enough
iv have no issues with the button at all when in the UI or when locking/unlocking display
iv done a few tests where i have turned off. then went to switch on, with the same pressure and sometimes it starts with one, sometimes it starts with two presses,
do u think this is a fault? anyone experience this? normal?
just checking...
thanks heaps!
Click to expand...
Click to collapse
to switch on device you have to keep pressed power button for few seconds or u can keep it pressed until you see lights at the touch keys.. :good:

Hi
brodiecb said:
Hi all,
does anyone sometimes have to press the power button (when phone is completely turned off) twice (2 presses to turn on) sometimes?...
so just to confirm
- handset is off
- push power button once (sometimes doesnt come on
- push for second time (and powers up)
im defiantly pushing for long enough
iv have no issues with the button at all when in the UI or when locking/unlocking display
iv done a few tests where i have turned off. then went to switch on, with the same pressure and sometimes it starts with one, sometimes it starts with two presses,
do u think this is a fault? anyone experience this? normal?
just checking...
thanks heaps!
Click to expand...
Click to collapse
I don't think many people would turn their phone completely off so haven't found the issue.
When you power off what will be happening is the phone is off as much as it can be, but these buttons are soft off, the battery is still connected and some power must be drawn to run the power circuitry to detect the button being pressed again to signal to power back up the phone, in the same way when you turn your TV off by the remote, power is still drawn to run the remote sensor on the TV.
To keep the drain on the battery as low as possible so the battery isn't completely discharged over months of storage I suspect the power chip waiting for the on signal again is only sampling every so often to save power so it can be in super deep sleep state. This means depending on where in this cycle you are when you press the power button it might seem like it isn't responding, so typically you have to leave it depressed long enough for it to be "seen".
The better option is to just to put your phone into flight mode if you don't want to be disturbed or want the phone off. I do this overnight and lose no battery power by the morning, so it is as good as off. You can add a button to your home screen to do this quickly, widgets are included already for that.
Regards
Phil

Mine does the same thing.. Sometimes it does it with waking up from sleep also.
Sent from my HTC One X using xda app-developers app

Replicating 4.2.X "sod" and what it means..

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