Is there a way to force the KF to wake when it senses charging? I get that right now the driver issue is present in 3.0, but I assume that will eventually get worked out by the geniuses that have got the KF this far. The reason I want it to auto wake is so that i can wire the power supply to the ignition of my car so that when i start my car it wakes/charges the KF ( i plan to have the KF replace my factory headunit). Otherwise I have to relocate the Power Button or develop a solution for hitting the power button.
I've tried several apps and nothing. maybe, I'm using the wrong one or not setting it up correctly. Any help would be greatly appreciated.
Thanks.
PS: if this has already been covered i'm sorry, I searched the forums, google, mp3car and several other sites before asking here.
FYI: Played with a KF at Best Buy and determined that yes, like most devices the KF stock does turn on when it senses power. So my conclusion which becomes obvious is that the OS's inability to sense charging (kernel 3) prevents it from waking while charging.
Related
Hello everyone,
having major USB issues on my GNex. It's not charging anymore, but when the phone is off, it displays a charging animation. I could get it to charge once since this occurred, I left it plugged in overnight on my Mac (phone turned off). Did the same thing last night, no charge at all.
Mac OSX does not recognize the device, my Windows machine keeps telling me something like "the connected device is not working properly and can't be used... ". This message pops up every few seconds, so I guess it's constantly connecting and disconnecting. I can't access the internal storage on both systems.
My first guess was a hardware defect. But when I try to boot into recovery mode, a screen instantly pops up that shows Andy and displays a message: "Downloading. Do not turn off target.". In the upper left corner it displays " ODIN MODE" in small red letters.
When I press the power button in this screen (there is a big arrow pointing to the button with "start" written in it) the phone just normally reboots.
I can't get into fastboot mode because of this. I can get into CWM Recovery when i use the reboot into recovery option built in the ROM.
I dunno much about Odin (next to nothing). Has it something to do with Samsungs Kies? Could it be that something has put my phone in this "ODIN MODE" and it constantly tries to download something, making the USB port unusable? The port is not completely broken, as the phone displays a charging animation when it's turned off... so there is some connectivity left!
Thoughts coming up that this could be some kind of software issue. If there is a possibility to get out of the Odin Mode, it may solve the problem.
The phone is unlocked and rooted, running AOKP Milestone 5 and franco kernel.
I tried to restore an older nandroid, but it did not change anything.
Would send it in for exchange, but not able to relock the bootloader due to no fastboot access. If it can be confirmed that this is a hardware problem, I have to pay for the repair, I'm fine with that.
Has anybody any ideas that could be helpful? Any help is much appreciated, thank you in advance!
Do a search and you will find at least 30 helpful threads. Basically you only need to replace your USB charging board and it works again. Should be a warranty issue, but Samsung has really been an ass on handling this issue lately and claiming water damage.
I have mentioned it many times here: this problem can be probably solved by thoroughly cleaning your USB with soft toothbrush.
True, I also cleaned my port but it only fixed it temporarily.
Thanks guys. Tried to clean the port, nothing changed.
Ordered an OEM charging board off ebay, hope changing it will fix the issue.
Only thing I'm wondering about is, that the phone is stuck in Odin Mode when I boot it up with Vol. - and the Power Switch. So I downloaded Odin but it does not recognize the phone...
I am also facing the same problem. I am currently using the phone by charging the battery externally. Can someone confirm that changing the USB flex cable is the solution ?
Just posted in another thread but it is definitely the USB port for me. Using an HTC Vision (Google g2)
Hey All,
I'm currently on the CM11 04/22 nightly, and have made it all the way up to the 04/27 nightly to try and resolve this issue and have not been able to. Basically - the sudden death issue has been hitting me very hard - I can't use my phone at all.
I understand the 04/11 nightly is stable and doesn't have this issue, howevery CyanogenMod does not have this on their website.
Does anyone have this install available? (CM-11-Nightly-20140411-D2LTE.zip)
Thanks so much in advance
SLiK
please explain what you mean by sudden death? thanks
rkant18 said:
please explain what you mean by sudden death? thanks
Click to expand...
Click to collapse
I'll be using the phone (say checking my Instagram or reading a book on Play Books) and the screen may be on for about 5-6 minutes. The phone will suddenly shut off on its own. I'll start it up and then shut down again when the phone is loading. It will also sometimes say it has 1-2% battery when it really has 45% (which is what it shows when I plug the phone in).
Hope this clears it up.
SLiK786 said:
I'll be using the phone (say checking my Instagram or reading a book on Play Books) and the screen may be on for about 5-6 minutes. The phone will suddenly shut off on its own. I'll start it up and then shut down again when the phone is loading. It will also sometimes say it has 1-2% battery when it really has 45% (which is what it shows when I plug the phone in).
Hope this clears it up.
Click to expand...
Click to collapse
I had the same issue a week back. Was the most frustrating thing ever...
I finally narrowed it down to the power button. It actually had to do with the power button switch which is soldered to the motherboard. The power button was super sensative, therefore being engagded at all times, causing the phone to hard shutdown every time I tried to turn the phone on.
How I fixed it:
1. Opened my phone up
2. Broke the switch off
3. Done
Now I use my phone without a functioning power button but it was a quick and free fix so it doesnt bother me.
If I decide to do so in the future, I can also solder a new switch back and get the power button working again.
DO NOTE: This might now be the issue you may be facing, so do your research
Finally, I watched this YT video which showed me how to break the power button switch and eventually fix my phone: https://www.youtube.com/watch?v=3Glllc7bEJs
Good Luck
imcol said:
I had the same issue a week back. Was the most frustrating thing ever...
I finally narrowed it down to the power button. It actually had to do with the power button switch which is soldered to the motherboard. The power button was super sensative, therefore being engagded at all times, causing the phone to hard shutdown every time I tried to turn the phone on.
How I fixed it:
1. Opened my phone up
2. Broke the switch off
3. Done
Now I use my phone without a functioning power button but it was a quick and free fix so it doesnt bother me.
If I decide to do so in the future, I can also solder a new switch back and get the power button working again.
DO NOTE: This might now be the issue you may be facing, so do your research
Finally, I watched this YT video which showed me how to break the power button switch and eventually fix my phone:
Good Luck
Click to expand...
Click to collapse
I'm fairly confident that this isn't the power switch. And if it were I'm not sure how comfortable I would feel breaking the power switch off.
The thing that begs me to think this is a software issue is that I'll have 45% battery, the phone will die, and then I'll try to turn the phone on again only for it to tell me I have 1% battery left. I'll put the phone on charge (after it dies again) and it will say charging - 45%.
Anyway I've rolled back a few updates and it seems to be fairly usable now...
Try cleaning the USB port real well and don't use a cheap cable. Use a needle and make sure there is no lint packed in there. These things can cause the phone to cycle itself even when not plugged in. I've fixed several doing exactly what you describe.
I know there are already a LOT of topics concerning this - I have read through them all frantically, trying to find a solution before turning to asking myself.
So, here's exactly what happened, and what I've tried.
My phone was just fine, running perfectly, nice battery life. I had been running CarbonROM for about 2 months, without any issues, didn't change anything recent to this problem occurring. So one night I was at a party, and didn't have an available charger, so my phone ran out of power completely. The next morning when I came home, I set it to charge, the LED lit up, as far as I remember at least. In the evening I turned it on, and I got to the SIM pin-code unlock screen. I entered the PIN, and my phone turned off. No crash screen or anything, it just went straight out. I figured that maybe it hadn't charged properly, so I let it charge for a few more hours, and then tried again - same thing happened. I instantly tried to turn it on again, but this time nothing happened at all. I held the power button down for at least 1 minute, to no avail. When I put in the charging cable, the LED doesn't light up.
So, as I said, I have been reading around on this forum and other places, trying to find a solution. Some people said holding down the power button and volume up and down at the same time for 2 minutes would fix it, it didn't. I have tried several times. Most recently someone said I should connect my phone to my PC with the USB cable, and then hold down the power button and volume down. This time, something did happen. But not on my phone's end. I have done this 2 times, with the same result. At exactly 7 seconds, my computer turns off, as if I had "choked" it by holding down the power button on the PC. This seems really odd to me, since the phone can't even turn on, so I don't see how there can be any connectivity.
I hope someone here has a solution, knows why it happened, or can at least guide me in replacing any part if needs be. I hope not, though.
Bump
Should I just send it in for a repair? I have an idea that doing so will be very expensive...
I have a first gen kindle with cm11, and wondering if there's a fix for this issue or if anyone else has seen it. Sometimes the Kindle just randomly won't turn it's screen on. After enough fiddling, the workaround is to plug it into power, then hold the power button till it hard shuts down, then turn it back on. If I could get around needing to plug it into power, this wouldn't be as annoying, but I can't.
Looking for ideas if no one knows for sure, outside of having to wipe a bunch of data (it has done this since flashing the rom), but otherwise works well.
The only modification to the OS has been to set the default app drive to the other internal one which actually has a decent amount of space. Can't get around using that change.
Hello all,
after leaving the tablet for 1y I gave it another try and am seeking on one hand some general advice how to proceed, or possibly specific if somebody had that bizarre behavior or something similar.
The problem is mostly described here: https://forum.xda-developers.com/t/my-sm-t800-will-not-boot-normally.4016731/post-82060775
Now I fiddled with it a bit more and the status is:
- switching it on causes it to crash at arbitrary stages: directly after the samsung logo, while showing the lineage os logo, right when ready for using, any time later, sometimes it is even possible to use it for hours
- it works almost reliably when I keep the power button pressed
- entering download mode is possible without problems
- entering recovery mode works only sometimes, in most cases only with power button pressed continuously
- when it works "normally" I can enable dev options, connect adb and do whatever I want (as it seems)
Now since the device is fairly old, I want to avoid major investments, however I still have some hope that there is a way to fix it. However, I'm a bit ouf of ideas ...
Any suggestions how to proceed are very appreciated!
I know this reply is one month late, but I think I know the reason and fix. The exact behavior happened to my T800 but I was able to fix it after viewing this video:
It is the power connector to the motherboard, which is apparently not soldered. Once I have soldered the pins to the motherboard. All is good.