Hello there, first post on here.
Anyone have/had a similar problem to this? The three soft key lights on my Optimus 4X now stay illuminated permanently. Even when the phone is switched off, they remain lit. I went so far as to completely drain the battery (or so I thought) so that there was insufficient power to turn the device on but the lights are still on. Does anyone know of any fix for this? Obviously, having these lights on all the time drains my battery quicker. I've tried the options in settings to switch it off and nothing works. I can only assume that this is a hardware fault.
Any thoughts?
foggyhorse said:
Hello there, first post on here.
Anyone have/had a similar problem to this? The three soft key lights on my Optimus 4X now stay illuminated permanently. Even when the phone is switched off, they remain lit. I went so far as to completely drain the battery (or so I thought) so that there was insufficient power to turn the device on but the lights are still on. Does anyone know of any fix for this? Obviously, having these lights on all the time drains my battery quicker. I've tried the options in settings to switch it off and nothing works. I can only assume that this is a hardware fault.
Any thoughts?
Click to expand...
Click to collapse
Maybe its some kind of short circuit...
You didn't do nothing like messing with firmware (flashing or rooting), or any crazy app?
It was always like that?
RuedasLocas said:
Maybe its some kind of short circuit...
You didn't do nothing like messing with firmware (flashing or rooting), or any crazy app?
It was always like that?
Click to expand...
Click to collapse
Nope, I wouldn't even know how. I've done a factory reset so it appears it is a short circuit. You think this can be fixed? I'm thinking I have an expensive phone on my hands that I can't use now.
Could these be related?
http://forum.xda-developers.com/showpost.php?p=34083067&postcount=35
Arne_B said:
Could these be related?
http://forum.xda-developers.com/showpost.php?p=34083067&postcount=35
Click to expand...
Click to collapse
Unlikely. The other thread is a well known problem with the phone, whereas this thread is the only time I have ever heard of the lights staying on all the time.
SimonTS said:
Unlikely. The other thread is a well known problem with the phone, whereas this thread is the only time I have ever heard of the lights staying on all the time.
Click to expand...
Click to collapse
Is it? I couldn't find a forum thread about this specifically so I thought only a few had this strange problem.
But you're right that this probably is a different problem than what I'm experiencing.
Related
How to stop startup vibration? I detest this feature very much! help!
Im sorry to report I can't really help you with this as im no real genius on the matter but im guessing it may be due to some sort of P.O.S.T response on the device similar to the beep you here on some older pc's and laptop's. If so it may be easier for someone to find the right registry entry to change. Then again I may be talking out of my backside. Good Luck!
yinyfxda said:
How to stop startup vibration? I detest this feature very much! help!
Click to expand...
Click to collapse
Are you talking about vibrate on connection ?
Start> phone> menu>options> advanced> uncheck vibrate device when connection is established.
He's talking about when you turn the device on..
I think he's talking about the vibrate when the phone boots (from a soft or hard reset, or from turning the phone completely off)
why so bother about that vibration?
What's it matter...? He still wants to turn it off....
I'd like to as well..
I means how to stop power-on vibration or hard or soft startup vibration. anyone has already stop the vibration, it's really boring!
i would actually be interested in that as well, i have my phone setup to automatically reset itself every day at 3 in the morning, and the vibration from the reset sometimes wakes me up.
yea, i dun like the vibration either.. But i doesnt make a very big deal though
My phone feels shaking , something loose from vibrating effect.
morizq said:
why so bother about that vibration?
Click to expand...
Click to collapse
It is decreasing the battery life time , maybe not much for 1 boot.. but if you boot 20 times in a day.. ( god may know why ) Than it would be handy
freaknormel said:
It is decreasing the battery life time , maybe not much for 1 boot.. but if you boot 20 times in a day.. ( god may know why ) Than it would be handy
Click to expand...
Click to collapse
I think the booting itself will require more power than the one short vibration at the beginning
Cryonic90 said:
I think the booting itself will require more power than the one short vibration at the beginning
Click to expand...
Click to collapse
the vibrating sure isnt helping the battery life either and i would like to disable this also. 10+ resets a day here and each time it vibrates my wife thinks someone is texting me! lol
Additionally, can anyone help get rid of those red numbers during boot-up?
I know that's an obnoxiously complex task that may be impossible for seemingly little payoff, but consider:
1. They prevent using the entire display for splash images, unless you want it covered up for part of the time,
2. My friend is color-blind, and won't be able to tell if they're red, green, or purple - I don't want him to not be sure,
3. They could attract a bull, if you waved it around accidentally in Madrid,
Etc.
I'm sure you can tell there are no shortage of reasons.
Anyone have any ideas?
mikentucson said:
the vibrating sure isnt helping the battery life either and i would like to disable this also. 10+ resets a day here and each time it vibrates my wife thinks someone is texting me! lol
Click to expand...
Click to collapse
If you're SR'ing 10 times a day, it's time to fix something on your phone.
khaytsus said:
If you're SR'ing 10 times a day, it's time to fix something on your phone.
Click to expand...
Click to collapse
i probably flash just about every new rom thats posted in the rom section. that and i've been testing the android builds that get released
Since a week or so I've had some minor problems with my Diamond.
First after a couple of hours with no use, I saw the led blinking (hey, a new text messag, let's have a look) and the phone wouldn't wake up.
Even pressing the power button for a long time didn't make a difference, I resorted to taking out the battery and restarting it that way.
Everything was back to normal after turning it back on so I didn't really worry about it.
Until this weekend, I tried to wake it up from standby and the screen looked euhm... rather strange
I made a picture of it (please have a look at the attachment). In this state it didn't respond to any button, not even a long press of the power button.
While I was putting back my camera this screen disappeared and the normal touchflo was back, but still the device didn't respond to anything.
So again I resorted to removing the battery and everything has been fine eversince...
But now I'm a bit worried... Anyone have any idea what might be causing this? I must say it's been quite warm in my house the last week (about 27C) so I can imagine that temperature could have an effect...
Thanks for any suggestions.
Oh, I almost forgot..
It's a stock Dutch Diamond.
The latest ROM (2.03.404.3 NLD)
Radio 2.09.25.23
Protocol 52.51.25.26H
That's a cool screen saver!
defaria said:
That's a cool screen saver!
Click to expand...
Click to collapse
It sure is
My first thought was: Oeh! Capture it!!
But I couldn't start the screencap program because well... the screen didn't really work
I have seen too this strange screen in my Diamond a couple of times, but I couldn't tell the reason. I was forced to reset the device as well.
I'm curious about the reason, any ideas?
JavierV said:
I have seen too this strange screen in my Diamond a couple of times, but I couldn't tell the reason. I was forced to reset the device as well.
Click to expand...
Click to collapse
Has your Diamond been functioning normally after that? Or has it developed more problems (and has perhaps been repaired)?
I'm a bit worried that this is the beginning of major problems...
Hey guys so. My thrill dropped in value even more the other day when i turned my screen on. And all of a sudden realized that led for the capacitive home button has either blown or severely dimmed. I have never heard of this happening on any device. And it is kinda ugly to look at. I have tried reboots, roms, LG hidden menu... everything to try to get it back. All to no avail. Then i decided it would be far more pleasant to look upon if all the led's were dead. So i apart from taking my phone apart and shorting them out i have tried everything to achieve this goal. Still failure was my result.
My questions to you, the community, is:
1 has this ever happened to you?
2 does anyone no a way of disabling them with a script or mod?
Thanks
do you have the option to leave them on all the time?
if you do leave them on for at least 30 minutes
that in my opinion should reheat the light and just maybe have a working light again.
latinohot said:
do you have the option to leave them on all the time?
if you do leave them on for at least 30 minutes
that in my opinion should reheat the light and just maybe have a working light again.
Click to expand...
Click to collapse
that i have not tried. Do you kow a setting or app for that?
There are no stupid questions, just stupid people.
Trekfan422991 said:
that i have not tried. Do you kow a setting or app for that?
There are no stupid questions, just stupid people.
Click to expand...
Click to collapse
I can't remember which baseband had the option to go to settings-display-touch key light duration
but I saw it once, but I can't remember which? sorry
latinohot said:
I can't remember which baseband had the option to go to settings-display-touch key light duration
but I saw it once, but I can't remember which? sorry
Click to expand...
Click to collapse
I actually just turned on and off my cm7 rom and it got locked screen off buttons on for like an hour. It didn't work
There are no stupid questions, just stupid people.
latinohot said:
I can't remember which baseband had the option to go to settings-display-touch key light duration
but I saw it once, but I can't remember which? sorry
Click to expand...
Click to collapse
That is the way Samsung controls the LEDs for the capacitive buttons on GB and ICS.
When I had the Thrill I used this app to keep the lights on with the screen. If I recall correct there was a way to have them always off. But I'm not sure.
https://play.google.com/store/apps/details?id=com.martinborjesson.o2xtouchlednotifications
Sent from my Galaxy S II (i777)
So... woke up this morning and the home button is now brighter than it has been. But its still a bit more dim then the rest... strange...
isn't the phone covered under warranty?
it is less than a year old right?
Like a fool.. i didn't get the warranty package.
Doesn't matter any way. I scratched the speaker out to make it look silver. Lol
yeah, I wanted to do the same thing to the speaker but was too afraid to press too hard or go over and scratch the screen.
Well I think this phone is great even thou my daily is the galaxy skyrocket, but I like it so much that I bought my daughter a Thrill from craigslist for $150 unlocked, I thought it was a very good deal
I have a brand new Nook, with CM7.2 installed on the EMMC. This is my second Nook I gave my old one to my mom. Never had a problem like this with the old one. The problem with this one is when it sleeps and I turn it back on, quite often my touch screen won't function. The tablet seems to be working fine otherwise, but I can touch the screen all I want and it will do nothing. Can't even shut off the tablet by holding POWER for a few seconds because I can't click "Shut Down" on that menu. So i have to do a hard reboot. Every time. It's very annoying. Any help from anywhere would be greatly appreciated!
Do you actually see the screen and it won't work or is it just black? If it is just black it sounds like you might be dealing with the "sleep of death" issue.
If you can see the screen but it is just frozen to touch you may want to try a screen calibration app and see if it fixes the issue. Also try cleaning the screen really well.
Landara said:
I have a brand new Nook, with CM7.2 installed on the EMMC. This is my second Nook I gave my old one to my mom. Never had a problem like this with the old one. The problem with this one is when it sleeps and I turn it back on, quite often my touch screen won't function. The tablet seems to be working fine otherwise, but I can touch the screen all I want and it will do nothing. Can't even shut off the tablet by holding POWER for a few seconds because I can't click "Shut Down" on that menu. So i have to do a hard reboot. Every time. It's very annoying. Any help from anywhere would be greatly appreciated!
Click to expand...
Click to collapse
I don't know if this is the problem, but the new nooks have a new touch screen. In CM9 they had to update the drivers. I don't know if the devs did that on CM7. I have heard of no other complaints from CM7 users though. Don't know of a solution.
J515OP said:
Do you actually see the screen and it won't work or is it just black? If it is just black it sounds like you might be dealing with the "sleep of death" issue.
If you can see the screen but it is just frozen to touch you may want to try a screen calibration app and see if it fixes the issue. Also try cleaning the screen really well.
Click to expand...
Click to collapse
I can see it fine just can't do anything. Could you recommend a good Screen Calibration app? Also the device is 2 days old so I think it's not dirty and the screen works fine until it's waking up from sleep.
You can try this https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en. Unfortunately it sounds like you may just have a hardware issue. Did you have a chance to use it stock?
J515OP said:
You can try this https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en. Unfortunately it sounds like you may just have a hardware issue. Did you have a chance to use it stock?
Click to expand...
Click to collapse
No just nuked that locked down OS the second I got it out of the box.
You might want to go back to stock and return the device if it isn't working. I don't usually recommend that since most issues are user created but it sounds like it might be a legitimately defective device in this case.
J515OP said:
You might want to go back to stock and return the device if it isn't working. I don't usually recommend that since most issues are user created but it sounds like it might be a legitimately defective device in this case.
Click to expand...
Click to collapse
I agree, sounds like a hardware problem to me. You might try installing CM7 on SD first to see if you have the same issue.
Ok, update: I fixed it. The only thing I did was put on JuiceDefender Ultimate. I set it to turn off my Wifi when sleeping to avoid Sleep Of Death®. I did not see then(and do not see now)how that could have solved my touch-recognition problem. But it seems that it has. Before, this was a constant problem. Nearly anytime I woke up the Nook. Hasn't happened now since yesterday. So perhaps this whole issue was somehow Sleep Of Death® related... I don't know if that's even possible. I will leave that to you smart guys to figure out. But my problem does seem resolved now.
Hey Guys,
I apologise for the long Title but I coudlnt figure out a better way to to title the thread...
anyways I went to bed and plugged in my phone as per usual with an alarm set for 1230pm. come 1230pm, alarm goes off, i snooze it until 1pm. The next time it goes off, the alarm sounds for about a split second and then its off - I didnt turn it off.
So obviously i am a bit concerned since this has never happened before. I check the device and its off. Mind you this entire time the phone is plugged into the wallcharger from HTC.
I think its a random reboot (which i have never had before) and try to reboot the phone - nothing happens.
I try the hard reboot - nothing
The lights, both soft keys and LED for power will not even turn on or respond. Plugging it into a computer, it isnt recognized. Its as if the device is just dead. The power was at 100% too.
I would like to add that it is currently plugged in. I am hoping it simply, inexplicably lost power (happened on my Xperia T) and i have to give it some long-term juice. It does get a bit warm while plugged in right now.
it was running CM10.1 nightly 5-20.
does anyone have any insight or advice for this?
Deus_eps_machina said:
Hey Guys,
I apologise for the long Title but I coudlnt figure out a better way to to title the thread...
anyways I went to bed and plugged in my phone as per usual with an alarm set for 1230pm. come 1230pm, alarm goes off, i snooze it until 1pm. The next time it goes off, the alarm sounds for about a split second and then its off - I didnt turn it off.
So obviously i am a bit concerned since this has never happened before. I check the device and its off. Mind you this entire time the phone is plugged into the wallcharger from HTC.
I think its a random reboot (which i have never had before) and try to reboot the phone - nothing happens.
I try the hard reboot - nothing
The lights, both soft keys and LED for power will not even turn on or respond. Plugging it into a computer, it isnt recognized. Its as if the device is just dead. The power was at 100% too.
I would like to add that it is currently plugged in. I am hoping it simply, inexplicably lost power (happened on my Xperia T) and i have to give it some long-term juice. It does get a bit warm while plugged in right now.
it was running CM10.1 nightly 5-20.
does anyone have any insight or advice for this?
Click to expand...
Click to collapse
try putting it in recovery power volume down just keep holding it can take upto a minute unplug it first
Deus_eps_machina said:
Hey Guys,
I apologise for the long Title but I coudlnt figure out a better way to to title the thread...
anyways I went to bed and plugged in my phone as per usual with an alarm set for 1230pm. come 1230pm, alarm goes off, i snooze it until 1pm. The next time it goes off, the alarm sounds for about a split second and then its off - I didnt turn it off.
So obviously i am a bit concerned since this has never happened before. I check the device and its off. Mind you this entire time the phone is plugged into the wallcharger from HTC.
I think its a random reboot (which i have never had before) and try to reboot the phone - nothing happens.
I try the hard reboot - nothing
The lights, both soft keys and LED for power will not even turn on or respond. Plugging it into a computer, it isnt recognized. Its as if the device is just dead. The power was at 100% too.
I would like to add that it is currently plugged in. I am hoping it simply, inexplicably lost power (happened on my Xperia T) and i have to give it some long-term juice. It does get a bit warm while plugged in right now.
it was running CM10.1 nightly 5-20.
does anyone have any insight or advice for this?
Click to expand...
Click to collapse
This is the 3rd incident that I know of a phone dieing. Mine was one, then there was another, and now you. All running CM 10.1. When Mine died I was transferring files via usb with the computer so I figured something fried in there (weird but the only explanation at the time). I came here for help too. That phone is long gone at this point. The thing is that I was told it's very very hard to brick a phone like that with S-on.
I don't know. I do love CM but i'll be waiting for a stable build before I go back again. GL to you. I had it it returned under the pretense that it was a hardware failure.The other guy who's phone also bricked said that there is some sort of issue with the batteries or something. I haven't confirmed that with anyone.
jaythenut said:
try putting it in recovery power volume down just keep holding it can take upto a minute unplug it first
Click to expand...
Click to collapse
I have, and am currently trying this as i type...No response from LEDs, No vibrations, No screen on, nothing.
Bonely said:
The other guy who's phone also bricked said that there is some sort of issue with the batteries or something. I haven't confirmed that with anyone.
Click to expand...
Click to collapse
Do you think you could find the thread or topic you read this?
Deus_eps_machina said:
I have, and am currently trying this as i type...No response from LEDs, No vibrations, No screen on, nothing.
Do you think you could find the thread or topic you read this?
Click to expand...
Click to collapse
You can try to scan the cm 10.1 forum. they are pretty unforgiving if you brick your phone. Try to get a logcat to them so they can take a look at it (sarcasm). They completely ignored my post (I had the alpha when it crashed and burned). He the other guy also posted there and they did go back and forth for a few post, but they squashed it pretty quickly. I haven't checked any of the AOSP forums, so it may not be CM 10.1 at all. It could very well be hardware issues. Either way, with S-off its very hard to do something like this and I'm really more convinced its hardware. But unless it can be confirmed that AOSP didn't cause the issue, then i'll hang on to my doubts and wait for something more stable. I give maybe a month or 2.
---------- Post added at 04:59 PM ---------- Previous post was at 04:56 PM ----------
custom kernals running sense based roms and a launcher should tide me over till then. With desense version coming out and s-off soon, it should make AOSP roms more solid.
Bonely said:
You can try to scan the cm 10.1 forum. they are pretty unforgiving if you brick your phone. Try to get a logcat to them so they can take a look at it (sarcasm). They completely ignored my post (I had the alpha when it crashed and burned). He the other guy also posted there and they did go back and forth for a few post, but they squashed it pretty quickly. I haven't checked any of the AOSP forums, so it may not be CM 10.1 at all. It could very well be hardware issues. Either way, with S-off its very hard to do something like this and I'm really more convinced its hardware. But unless it can be confirmed that AOSP didn't cause the issue, then i'll hang on to my doubts and wait for something more stable. I give maybe a month or 2.
Click to expand...
Click to collapse
Thanks, I am dead certain its hardware related myself. I am going to leave this plugged in, maybe it really needs to get properly charged (its happened to me with my old Xperia T where it went into deeeeeep sleep due to power loss), so i will be keeping it plugged in until Monday and then taking it Rogers, thankfully i bought a warranty for just this sort of crap happening.
Deus_eps_machina said:
Thanks, I am dead certain its hardware related myself. I am going to leave this plugged in, maybe it really needs to get properly charged (its happened to me with my old Xperia T where it went into deeeeeep sleep due to power loss), so i will be keeping it plugged in until Monday and then taking it Rogers, thankfully i bought a warranty for just this sort of crap happening.
Click to expand...
Click to collapse
after you let it charge for a few hours unplug it put it under a bright light and hold power+volume down and see if it boots to bootloader. i know a few people have had this issue and the phone came back on. all said there was no charging led and wouldnt do anything
skinsfanbdh said:
after you let it charge for a few hours unplug it put it under a bright light and hold power+volume down and see if it boots to bootloader. i know a few people have had this issue and the phone came back on. all said there was no charging led and wouldnt do anything
Click to expand...
Click to collapse
were those guys running their batteries down?
Bonely said:
were those guys running their batteries down?
Click to expand...
Click to collapse
yes, but a couple said they were on cm10.1 and the battery dropped fast and turned off. or had it plugged in overnight and woke up to the phone dead
---------- Post added at 06:47 PM ---------- Previous post was at 06:42 PM ----------
people are thinking that its a built in safety against accidental button presses in a pocket or bag. i dont know if thats true but people have said it works
skinsfanbdh said:
yes, but a couple said they were on cm10.1 and the battery dropped fast and turned off. or had it plugged in overnight and woke up to the phone dead
---------- Post added at 06:47 PM ---------- Previous post was at 06:42 PM ----------
people are thinking that its a built in safety against accidental button presses in a pocket or bag. i dont know if thats true but people have said it works
Click to expand...
Click to collapse
well when I had mine I tried leaving it plugged in for a day, but I didn't put it under bright light. I didn't notice a fast discharge with mine either. It was plugged into the usb port to my computer and I was transferring files. I could have missed it though, I mean I was around 90% at the time and wasn't too worried about the charge.
skinsfanbdh said:
after you let it charge for a few hours unplug it put it under a bright light and hold power+volume down and see if it boots to bootloader. i know a few people have had this issue and the phone came back on. all said there was no charging led and wouldnt do anything
Click to expand...
Click to collapse
i have read this before somehwere...WHY the bright light? just curious...i will try it.
Deus_eps_machina said:
i have read this before somehwere...WHY the bright light? just curious...i will try it.
Click to expand...
Click to collapse
something to do with the proximity sensor or ambient light sensor
skinsfanbdh said:
something to do with the proximity sensor or ambient light sensor
Click to expand...
Click to collapse
yep. not working...
I want to take it in to Rogers tomorrow see what they say.
My first one had the same problem I only had it for 6 days it was rooted and it wouldn't come on at all so I took it to at&t and they gave me a new one... Hope it doesn't happen again with this new one...
Sent from my HTC One using Tapatalk 2
Deus_eps_machina said:
yep. not working...
I want to take it in to Rogers tomorrow see what they say.
Click to expand...
Click to collapse
Any update on this ? The thread title explains my phone completely. It just simply died and won't accept a charge. 100 percent unresponsive in every aspect.
tugesius said:
Any update on this ? The thread title explains my phone completely. It just simply died and won't accept a charge. 100 percent unresponsive in every aspect.
Click to expand...
Click to collapse
I'd try all the tips first. especially the bright light trick. Other than that it's off to your carrier or HTC for repair/exchange
Sent from my HTC One using Tapatalk 4 Beta
OP here...
I have a new one in the mail for a swap...I have had no luck whatsoever with any tricks.
...and they sent me a device with a scratched up screen :/
does anyone know if a similar issue to mine was fixed? either on XDA or somewhere else? i really just want to get back to my own One
I had this happen to mine. No fix I've seen works, they just replaced mine with new one. If they sent you scratched replacement all I can say is complain and demand another one.
tugesius said:
Any update on this ? The thread title explains my phone completely. It just simply died and won't accept a charge. 100 percent unresponsive in every aspect.
Click to expand...
Click to collapse
saibogu009 said:
I had this happen to mine. No fix I've seen works, they just replaced mine with new one. If they sent you scratched replacement all I can say is complain and demand another one.
Click to expand...
Click to collapse
So you guys have cm10.1 installed when it happened? just want to confirm it occurs only with phones with cm10 installed, and not with Stock rooted sense! I don't want to end up like this, so I'll avoid cm roms for now, I'll stick with Sense only, and If the problem occured with Stock rooted sense, I will not even root my phone
Can you guys confirm this?
Thanks in advance,
cheers