Hi, new here but I've been lurking for a while.
I followed Powerpoint's guide to instal CM10 on my KF2
http://forum.xda-developers.com/showthread.php?t=2105077
Everything was running great and has been since I first loaded version 3 a few weeks ago, and last week i went to version 4 of powerpoint's rom with no problems. Then a couple days ago after i had been browsing the internet on it for maybe 30 minutes, I set it down and when i came back the screen was off and wouldn't turn back on. so i figured the battery was just dead, so i plugged it in to the wall charger. At first the charge/power light wouldn't come on at all. Then after several plugs and unplugs the orange light started to come on but would only stay illuminated for 30 seconds-ish. So I tried it on my phone charger and the orange light came on and stayed on, so i decided to let it charge overnight. The next morning the light was still glowing orange so I unplugged it and tried turning it on, but still nothing happens. But when I plugged it back in afterwards the light came on green. now it has been plugged in for almost a day with the green light on but it still wont turn on.
Anyone else have this problem? Any ideas what i can try? for obvious reasons i can't exactly ship it back to amazon lol
p.s. I have a final on friday and the text book for that class is on the kindle. So urgent responses will be greatly appreciated.
Nevermind guys, I figured it out. Power button for 20 and it booted right up
Sent from my EVO using xda app-developers app
docnougat said:
Nevermind guys, I figured it out. Power button for 20 and it booted right up
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I've had this a couple of times on both 10.1 ROMs. As you stated the only way I got it working was to hold the power button for 20 secs, then power on normally.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?
on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?
docnougat said:
It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?
on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?
Click to expand...
Click to collapse
Wow, for once I can completely and knowledgeably help with almost no guess work!
The issue is Sleep of Death.
The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.
It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.
TO FIX
You guys were right on fixing it mostly.
If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.
I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.
I would say....in a few weeks with the device, I've had the issue around 5-6 times.
I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.
agreed, if it was happening while i was trying to do stuff it would be problem. As it is though, I just consider it a minor inconvenience. Glad to know I'm not the only one experiencing this though.
iytrix said:
Wow, for once I can completely and knowledgeably help with almost no guess work!
The issue is Sleep of Death.
The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.
It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.
TO FIX
You guys were right on fixing it mostly.
If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.
I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.
I would say....in a few weeks with the device, I've had the issue around 5-6 times.
I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.
Click to expand...
Click to collapse
I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..
fmkilo said:
I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..
Click to expand...
Click to collapse
I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
or you could have kmsg being written to a file during it...
the hard reset (power button for 20s) clears memory
Related
Issue: Power button won't turn screen off. Either it doesn't respond to the button push at all or it treats it as a long press and will pop up the phone options menu. Power button wakes phone just fine. Also, if I boot into recovery while experiencing this, not all power button pushes register within recovery (ouch).
It's weird because I experienced this for the first time like 2 months ago a few hours after flashing a Tiamat kernel (actual kernel may have had nothing to do with it), but after fiddling around with my phone it started working again.
Well, it started happening again on Saturday using CM 7.0.3.1 w/ GoDm0dE v5. I got it to work again by doing a factory reset, then restoring a backup. Well, it came back last night and persisted after another factory reset. It was very consistent today -- for hours it would either do nothing after pressing power or it would pop up phone options. Finally, a did a factory reset within CM7 and also within Amon-RA 2.3 and then restored a backup from yesterday and the power button functioned properly for about 1.5 hours.
Has anyone experienced anything similar?
ROM: CM 7.0.3.1
Kernel: Stock
Recovery: Amon_Ra 2.3
HW: 003
Never had that experience. Could be a number of things. It might be the Kernel/ROM mix, the Kernel itself, the ROM itself...But I would think that if it was any of these things, I would have heard about it by now from other users.
It could be something as simple as a short in your power button or the connections underneath it. Might just short out at the right times to make you think it is something you are flashing. Try shooting some compressed air in there (might help).
drgonzo712 said:
Never had that experience. Could be a number of things. It might be the Kernel/ROM mix, the Kernel itself, the ROM itself...But I would think that if it was any of these things, I would have heard about it by now from other users.
It could be something as simple as a short in your power button or the connections underneath it. Might just short out at the right times to make you think it is something you are flashing. Try shooting some compressed air in there (might help).
Click to expand...
Click to collapse
Thanks -- I actually tried the compressed air. I'm thinking it's hardware. It seems to have gotten worse in the past hour.
im having the same issue. i googled it earlier and it seems like theres alot of people have that same problem. its looking like a hardware issue. I can tell you one thing tho its pissing me off.
shdwboy said:
im having the same issue. i googled it earlier and it seems like theres alot of people have that same problem. its looking like a hardware issue. I can tell you one thing tho its pissing me off.
Click to expand...
Click to collapse
I unrooted and it actually started to do the same, but when waking the device. Brought it into Sprint and getting a replacement on Wednesday.
Had this exact same issue up until a few days ago. I took a needle and went around the power button front and back, something unjammed I guess and now it works like a charm. I've also had this with a software problem. My power button wouldn't work, even in recovery. I restored a nandroid and this fixed it. Hope this helps! Best of luck.
I had the same issue. Sprint said it wasn't the button but the board not responding to the button. Got a new phone.
Sent from my PC36100 using XDA App
i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible
wondering if anyone can help me...
frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.
Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks
A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!
Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia
same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.
This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.
I highly doubt they even CARE when sending these in. They will void for physical damage most likely.
tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.
I literally have never had a problem like this with this phone, but just recently I flashed the new AOKP jb 8-29 build and after a day or two of using it I started getting random reboots where the phone would crash and then start vibrating in intervals. I couldn't get it to stop unless I pulled the battery. Thinking this was just a bug with the rom, I just rebooted to recovery and wiped and flashed the latest jedi mind trick v7. I let the phone sit for a little bit after first boot, but when I then tried to go through the setup I got the exact same problem. Now the phone crashes like this every time I boot up and even while I'm in recovery mode! Someone please help if you know what might be causing this.
EDIT: Now it's doing this every time I put the battery back in; I can't turn on the phone or go into recovery while it's vibrating like this
Sound like a faulty power button. I've seen many, many threads like yours. Almost certain that's the case. Mobiletech offers a power button service. Check them out
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-t-mobile/
Sent from JMT Goodness
LoopDoGG79 said:
Sound like a faulty power button. I've seen many, many threads like yours. Almost certain that's the case. Mobiletech offers a power button service. Check them out
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-t-mobile/
Sent from JMT Goodness
Click to expand...
Click to collapse
I think you're right because before every time I put in the battery the phone would turn on, but I tapped the power button a few times to loosen it up and put the battery in and it didn't turn on. Is there any way to remote start without having to touch the power button that you know of? Thanks for the advice btw
This same scenario happened to me just yesterday morning. I researched it and this issue does seem to be popping up more frequently among Samsung phones. Maybe power button design is faulty and they're starting to wear out now after a year plus of use? I sent mine off to MobileTechVideos today to be fixed. I feel so lost without my phone!
jmariconda said:
I think you're right because before every time I put in the battery the phone would turn on, but I tapped the power button a few times to loosen it up and put the battery in and it didn't turn on. Is there any way to remote start without having to touch the power button that you know of? Thanks for the advice btw
Click to expand...
Click to collapse
What I've read is no. Its not the button its self, but the circuits behind the button that mess up. Unless you are really skilled at soldering and can re wire the board, I don't see that happening.
Sent from JMT Goodness
Hello guys,
I tried to search for a similar issues but I couldn't find anything similar so please bear with me.
My KF sometimes shuts down overnight. In the morning then I have troubles to switching it on again (clicking the power button, holding it for longer periods of time...). It usually helps for the tablet being connected to the charger, but it takes a few tries to turn it on. After I managed to turn it on again, for example yesterday, it had 80% of battery left.
I am using CM nighties and this is happening already for some time.
I am also using juice defender, I am not sure if that is relevant.
Do you have any suggestion, what could be the cause of this? Maybe a suggested alternative rom? Or some logs I can check? I think the powering on troubles bother me more than the shutting off overnight since I always think it won't come back on anymore.
Also, not sure if relevant. If I try to turn it on and it doesn't, sometimes the button flashes orange. After a few tries it turns green and powers on. Not sure if I am now not only confusing times, when it was simply out of juice.
P.S. On a different note, just curious, does anyone know how if there is a rom with working mic already?
Thanks in advance.
jkb
Yes, I sometimes have the same issue with the power button - in fact it happened to me this morning where I went from about 60% charge to 16% with a sudden power drop.
Not sure why this happens. I thought it was a bad battery so I changed it but am still getting the problem every now and then.
Sent from my Nexus 7 using xda premium
the only thing that i can think of is that during the middle of the night a soft-reboot happens and it cant boot back up into the system. this would cause it to sit there and continually try to boot up. this would use a lot of cpu and a lot of power. as for why that drains battery while being plugged in, well i cant help you on that.
Thanks for the input. I've wiped dalvik, cache and the system and installed hashcodes AOSP Jelly Bean (http://forum.xda-developers.com/showthread.php?t=2041694) and at least it survived this night without shutting down so maybe this helped. If I come across the same issue, I will update this thread with new info.
Thanks again,
jkb
Check this out:
amazon.com/gp/help/customer/forums/kindleqna/ref=cm_cd_pg_pg139?ie=UTF8&cdForum=Fx1GLDPZMNR1X53&cdPage=139&cdThread=Tx2JSJNEOWHGOIT
Sounds like a hardware issue, and Amazon has been replacing those of customers who buy new from them.
Mine has this issue too. I KNOW it has battery power, and is still on, but the screen won't turn on. Only solution is to plug in power, then hold down the power button until it shuts down hard. Then turn back on.
I'm returning mine because of it.
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
jokob.sk said:
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
Click to expand...
Click to collapse
Try going to the WiFi settings and selecting 'never' for keeping WiFi on during sleep. This seemed to work for me.... So far it hasn't happened again.
Sent from my Nexus 7 using xda premium
I think this is the bug I am experiencing:
Shutdown bug stalls out the shutdown. Looks like the device is off, but it's still powered draining battery. Currently requires long power button press to fully shutdown after the screen is black (about 15-20 seconds).
from the 3.4 kernel thread (http://forum.xda-developers.com/showthread.php?t=2264563). I am not sure if cm 10.1 nighties contain this kernel, but the description is pretty much spot on.I couldn't test the fix (holding the button for 15-20 seconds), since I already changed roms, but if someone experiences the issue again, he can post if this works and which rom and kernel they are using.
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
pwrdbykimchi said:
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
Click to expand...
Click to collapse
Yes, it happened again to me with the same ROM, but it happens less often. I will try the updated kernel once it is finished.
On May 27, 2013, Hashcode listed the known issues of the current kernel on his website:
Sound / MIC debugging
Deep sleep issues with “omapdss_dpi” device
SmartReflex shutdown loop fix.
Charging driver / OTG improvrments
Click to expand...
Click to collapse
Looks like they've been identified and are being resolved. :good:
Hey Guys,
I have a S3 AT&T and it just keeps turning on and off by its self about every 20 seconds. I have looked around and many people have this issue and there are a few solution out there but all of those solutions need my phone to stay on for a while. I can't do a hard reset and I can't do any kind of flash because it stays on for such a short time. Also the phone does not have water damage.
Below are the steps I have tried so far.
-Tried a new battery but same issue
-Thought maybe the power button was stuck but it looks fine.
-Tried to do hard reset and flash but does not stay on long enough
Not sure what else to do. Its killing me that I cant figure out how to fix it!! THERE MUST BE A WAY!
Thanks everyone!
PhoneHutSJ said:
Hey Guys,
I have a S3 AT&T and it just keeps turning on and off by its self about every 20 seconds. I have looked around and many people have this issue and there are a few solution out there but all of those solutions need my phone to stay on for a while. I can't do a hard reset and I can't do any kind of flash because it stays on for such a short time. Also the phone does not have water damage.
Below are the steps I have tried so far.
-Tried a new battery but same issue
-Thought maybe the power button was stuck but it looks fine.
-Tried to do hard reset and flash but does not stay on long enough
Not sure what else to do. Its killing me that I cant figure out how to fix it!! THERE MUST BE A WAY!
Thanks everyone!
Click to expand...
Click to collapse
Does it also happen in download mode and/or recovery?
x0ne215 said:
Does it also happen in download mode and/or recovery?
Click to expand...
Click to collapse
Yes it even in the download and recovery menu it does this.
I'm having this exact same problem. Even in download mode it'll reboot. In fact, even while rebooting it reboots. I was lucky in that it stayed in download mode long enough for me to ODIN back to stock, but it's still rebooting. Completely unusable because it never stays on long enough. Can anyone help?
Did it ever take a dive off the table or your hands?
It wouldn't surprise me if something internally was loose....
x0ne215 said:
Did it ever take a dive off the table or your hands?
It wouldn't surprise me if something internally was loose....
Click to expand...
Click to collapse
For myself, not recently. The phone was in perfect working condition, until I updated my ROM. Then when I woke up this morning, this problem occurred.
---------- Post added at 10:26 PM ---------- Previous post was at 10:22 PM ----------
hbk19 said:
For myself, not recently. The phone was in perfect working condition, until I updated my ROM. Then when I woke up this morning, this problem occurred.
Click to expand...
Click to collapse
Honestly, it seems to me as if the power button is stuck somehow. It doesn't look stuck to me, but the behaviour of the phone is like that. The constant rebooting, the way the screen turns on, and even how the power off menu randomly comes up by itself.
x0ne215 said:
Did it ever take a dive off the table or your hands?
It wouldn't surprise me if something internally was loose....
Click to expand...
Click to collapse
Mine has fallen before but nothing serious I'v dropped phones way worse then this. But I do think something is definitely loose. If I just leave the phone alone it doesn't power on or off. But as soon as I pick it up and move it, it powers on then in 20 seconds just goes off again.
Anyone have any idea what could be loose maybe?
Thanks
PhoneHutSJ said:
Mine has fallen before but nothing serious I'v dropped phones way worse then this. But I do think something is definitely loose. If I just leave the phone alone it doesn't power on or off. But as soon as I pick it up and move it, it powers on then in 20 seconds just goes off again.
Anyone have any idea what could be loose maybe?
Thanks
Click to expand...
Click to collapse
your best bet is too open up the phone and look at the connectors from the batter to the phone and make sure that those have a solid connection.
99% it is a power button failure. I as well as many others are suffering from this.
Try to avoid using the power button as much as possible. Use the home button to power on and find a softkey to turn your screen off. Easiest way is use quick toggles to turn off screen.
Sent from my Galaxy S3 on CM10.1 using XDA App