ANY help on backlight button issue?!

[unreal253]

wuts good yall.
i need to figure out wut kind of issue this is.
say my phone is on and screen is on. i press the 'Backlight' button(NOT the red/end/power ) on the top of the phone.. and the screen will turn off. Normal. Great. Okay now I go to press it again. The screen doesn't power on. I noticed the phone is definitely on and as if the phone is being used with no screen. The lights and controls works.

I tried flashing new roms of all sorts. I primarily use NRG roms. Can ANYone help me out here? I cant seem to figure it out. Can it be hardware, even tho it still turns the screen off?

[boredandtattooed]

you just get a TP2 or something??? been here 2 and a half years and youve never read about the SOD issue??

certain builds have the SLeep of Death issue

[unreal253]

Originally Posted by boredandtattooed

you just get a TP2 or something??? been here 2 and a half years and youve never read about the SOD issue??

certain builds have the SLeep of Death issue

I had it since august of this year...but never had this issue. n i found another interestin factor. when i try to change the backlight through the app, the light wont dim or light up..

is there a fix for this SOD? it seems like google only has articles bout the SOD and how it infested phones..

[Amamba]

I just got my 1st SOD after having the phone for 6 months. I installed lots of applications and mods on it (still on original Sprint ROM), so I figured this is a good time for hard reset. Just after HR, with no apps installed, I got another SOD.

Well, there seems to be a number of posts related to this problems, with everyone having their own theory, from faulty hardware to SD / SIM card issue to programs.

I've had various PDAs from the early Palm days, so to me while there's a probability of it being an internal hw issue, this seems much more likely to be either a s/w problem or a card issue. I also noticed that on the morning of the day I got my first SOD the battery was half-drained overnight (which doesn't typically happen) and the task bar wouldn't show.

One of the posts I read indicated this is likely to be a card issue, specifically some program installed on the card trying to load / update while the device is off. This made lots of sense, since even though I did a HR, I didn't wipe the card; if there was some program "hook" in the root of the card, or some corruption on it, this would explain getting a SOD even on a freshly wiped device.

So, I wiped the SD card, formatted it, and only copied back documents, CABs and music - no programs whatsoever. I also decided to go easy on installed programs, installing only in main memory, and only the absolute bare necessities (e.g. going with stock Manilla vs CHT2, which so far I find not at all limiting). Instead of Quickmenu I went with DotFred TaskMgr that doesn't have to be installed. Basically, a device as close to the stock as possible without severely limiting myself.

So far, 3rd day and no SOD... knock on wood.

[Amamba]

Three things to check, then:

1) There's a setting that allows your backlight to be controlled automatically. Make sure it's unchecked. May be this is a faulty light sensor.

2) Take out both the SIM card and SD card & reboot. Better else, hard reset. (You don't really need a SIM card unless you're using your phone abroad).

3) If it still doesn't wake up after going to sleep, hook it up to your PC via Pocket Controller or a freeware MyMobiler, and see if the device actually responds when you press the power button (which would mean it's a backlight issue) or remains in sleep mode.

[unreal253]

Originally Posted by Amamba

Three things to check, then:

1) There's a setting that allows your backlight to be controlled automatically. Make sure it's unchecked. May be this is a faulty light sensor.

2) Take out both the SIM card and SD card & reboot. Better else, hard reset. (You don't really need a SIM card unless you're using your phone abroad).

3) If it still doesn't wake up after going to sleep, hook it up to your PC via Pocket Controller or a freeware MyMobiler, and see if the device actually responds when you press the power button (which would mean it's a backlight issue) or remains in sleep mode.

1:: I checked the auto dimming, and it was unchecked, but I even tried using it, still didnt change whatsoever.

2:: Took both out, flashed new ROM, fresh install, still had the issue.

3:: Any mobile smartphone controller from PC wont detect it when the screen is "off". When I press the backlight button once to turn the device on without the light makes the software see the phone for maybe a second. But if i soft reset not letting the screen turn off, myMobiler works fine.

-- I'm thinkin that its a hardware issue, i cant believe its a software issue, when the data gets cleared off so theres no trace of configuration of any sorts..?

[shaggylive]

yup, sounds like a stuck/broken power button. very common on the tp1 & tp2.

[eric12341]

the 218xx builds and i believe the 235xx builds too suffer from the SOD issue. try either flashing a rom thats a (2105x or 219xx ) and then say bye to the SOD i have many programs, 3000 texts, about 60 emails on my 21052 ROM and i've never experienced it, i also had the same setup on some 219xx roms and havent experienced it also

[elesbb]

i am running a 21916 build and never experienced SOD .. except for one time i had gotten it and the screen would come on simply by keeping it plugged in for awhile seemed to fix it . but , i dont exactly think it is a software issue . i have experienced two types of SOD the kind the OP describes where you hit the sleep button the screen goes off then you hit it again the screen DOESNT come on but the button lights do . the other type nothing would hapen at all when hiting the power button on top .

Also , this type of SOD the OP describes seems to be some sort of hardware problem . As i have gotten a replacement from Sprint and without any mods, apps or anything installed it did that to me . so i went home and flashed a newer ROM , the 219xx build and it still did that . so i just took it back . so i dont think all SOD's are the OS's fault .