Database Develop

[Q] Sleep/Charge of Death

I been wondering if the phone never had sleep/charge of death before can a kernel and/or ROM be the culprit to it? I been trying to look more into it and haven't found a definite answer to it so I ask you guys what is causing it. I've tried different kernels and ROMs and some do it other don't is there anyway to just know? Or a good way to narrow it down?

I was able to track mine down to a kernel that supported Overclocking. Once I switched to a ROM that had a kernel that wasn't OC supported (older version of same ROM) my charging death went away. I think it has to do with the OC settings, the idle clock speed is too slow, but no matter what settings I used I got sleeping death every other night until I swapped for the other version.
Sent from my Captivate running GR-12

Only time I have encountered the Sleep/Charge of death was when I was OCing the phone and UVing it also. Having too much of a variance in the UV was my problem. Wants I started to UV the same amount across the board or close to it my problems were solved. For instance the most I UV is 75 and the least is 25. if you had a gap like 150 to 0 that could be what is causing your problem. At least that is what I noticed for myself. Now I am perfectly fine for over a month.

The phone boots up to 1/2 way through the kernel when charging in off mode... IBL, PBL, SBL, Params, Kernel... If it hangs, then it's likely hung at a custom kernel.

If the ROM craps out it soft reboots and/or goes into a boot loop. I don't think that a ROM can cause your phone to randomly shut down.

Bootloop issue

I'm running CM7 on my droid and when i run the battery flat, plug it in to charge it. it then boot loops for like 5 mins and works just fine.. also does anyone have any OC'd kernal suggestions, right now im using one of the chevyno1 kernels but the phone still seems a bit laggy at times what are some good tips to speed this thing up a bit. and does anyone know how to fix the bootloop issue?
any suggestions would be greatly appreciated.

I had the same problem until I eventually pulled the battery while it was looping and it never did it again.
As far as OC'ing your phone, rom toolbox is a free app that has options to OC your phone. You can give that a try.

[Q] Phone switches off in standby.

My captivate shuts itself down randomly on standby. Does anyone else have this problem and is there a known solution?

Are you overclocking your phone? That is one possibility. The other could be a dying battery. Does that happen even if phone is connected to charger? If yes then your battery might be okay.
What rom are you using? Is it a stock or a custom one? If you are running any not so stable version of custom rom then that could be another possibility.

uhm said:
Are you overclocking your phone? That is one possibility. The other could be a dying battery. Does that happen even if phone is connected to charger? If yes then your battery might be okay.
What rom are you using? Is it a stock or a custom one? If you are running any not so stable version of custom rom then that could be another possibility.
Click to expand...
Click to collapse
Firstly, thanks for your reply.. It was happening with the stock rom as well.. I custom flashed a Jelly Bean ROM.. Same result.. Never happened with phone connected to charger and it happens like one in 2-3 days or something..

I'm not sure if all the JB ROMs offer this in the same way, but I'm on SlimBean 2.7 with Semaphore kernel, and it allows you to change the minimum clock speed of the processor when it's in standby and the voltages it uses at different speeds. These are under the main settings->performance. Others have reported that setting the minimum clock speed to 200MHz rather than 100, or slightly upping the voltage when it's in sleep mode, can cure these sleep death issues. I've never had the problem, but search the development forum and you should find other people's recommended settings.

Captivate shuts down in standby
My phone does the same thing. It's a Captivate running Jelly Bean 4.2.1 (Slim-4.2.1.Beta.1-OFFICIAL) on a Semaphore kernel. It works perfectly when it's plugged into a computer through USB. Otherwise, it shuts down, or restarts, every single time it goes into standby, even when it's on a charger. I've tried raising the CPU speed, uninstalling SetCPU, re flashing the ROM, and nothing helps.
Is this a hardware issue, app issues, or does it have to do with the ROM or kernel? I had CyanogenMod 10.0 with a devil kernel running on it previously, and it did the same thing.

[Q] Phone Shuts Down when Chargıng after Flashıng CM9 & CM10

I purchased my Captivate in July 2010, used it for a year without rooting, flashing, etc. Had no problems with random shut off.
After moving overseas, I had to flash a ROM, long story. Used Serendepity ROM for a year with no problems.
At the end of July this year I flashed CM9. At this point, I begin to have problems with the phone shutting off while charging. This did not happen except when charging. In order to turn the phone back on I have to disconnect it from the power cable. This happened rather frequently at first, but gradually began to happen every night.
A couple of days ago I flashed CM10 and it still happens. Two days ago I downloaded SetCPU and set the minimum speed to 200 Mhz when charging. However, this did not solve the problem.
Any ideas on a fix?
Thank you in advance for any help.

jchadana said:
I purchased my Captivate in July 2010, used it for a year without rooting, flashing, etc. Had no problems with random shut off.
After moving overseas, I had to flash a ROM, long story. Used Serendepity ROM for a year with no problems.
At the end of July this year I flashed CM9. At this point, I begin to have problems with the phone shutting off while charging. This did not happen except when charging. In order to turn the phone back on I have to disconnect it from the power cable. This happened rather frequently at first, but gradually began to happen every night.
A couple of days ago I flashed CM10 and it still happens. Two days ago I downloaded SetCPU and set the minimum speed to 200 Mhz when charging. However, this did not solve the problem.
Any ideas on a fix?
Thank you in advance for any help.
Click to expand...
Click to collapse
Did you make any mods or change any settings?
Also, did you try using a different kernel? (Devil / Semaphore)

You might also flash back to Serendipity and see if the problem persists. If it doesn't then of course it's an issue with CM but if it continues I would say its a hardware problem or potentially a bad charger. Personally I've never used either CM9 or 10 but nearly every rom I've used is based off of them and I've never had this issue. So unless you've done something weird with the settings as BWolf suggested then I would lean towards hardware.

Thank you for the suggestions. I've flashed a couple of kernels (Devil and Semaphore) and the problem continues. I'll test the battery and charger next.

I tried a different battery and charger as well as a couple of other ROMs, with no change. The phone still shut off at night. So, I flashed back to stock 2.1 and the phone did not shut off. I then tried CM10.1 again, but the phone shut off again last night.
So, I've determined that it's not a hardware issue, but so far all Android 4.x ROMs I've flashed have resulted in the phone shutting down at night while charging.
Anyone have any ideas or suggestions?

jchadana said:
I tried a different battery and charger as well as a couple of other ROMs, with no change. The phone still shut off at night. So, I flashed back to stock 2.1 and the phone did not shut off. I then tried CM10.1 again, but the phone shut off again last night.
So, I've determined that it's not a hardware issue, but so far all Android 4.x ROMs I've flashed have resulted in the phone shutting down at night while charging.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
co-ask.
i got the same problem with cm9 and cm10.
thanks in advance.

jchadana said:
I tried a different battery and charger as well as a couple of other ROMs, with no change. The phone still shut off at night. So, I flashed back to stock 2.1 and the phone did not shut off. I then tried CM10.1 again, but the phone shut off again last night.
So, I've determined that it's not a hardware issue, but so far all Android 4.x ROMs I've flashed have resulted in the phone shutting down at night while charging.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
yqren said:
co-ask.
i got the same problem with cm9 and cm10.
thanks in advance.
Click to expand...
Click to collapse
Try upping your minimum voltage to 200Mhz.

BWolf56 said:
Try upping your minimum voltage to 200Mhz.
Click to expand...
Click to collapse
tried it, but it doesn't work.
thanks

Same problem here. CM9 had been doing it fairly regularly. I wiped everything and did a fresh CM10 install before bed without installing any other apps or changing settings and it shut off over night. I'm flashing back to stock now too confirm whether that fixes the issue

Big crash/reboots/bad battery/flickering screen problems

Hello deer peeps!
I have some serious issues with my Gnote. It started months ago and became worse and worse. As the problem is at the moment, it has lousy battery time, it crashes a couple of times per day, when the battery starts getting low, the screen starts flickering more and more and then it freezes. Ive tried several times to install different CM versions, cleaning the cache, total wipeout, nothing really helps. A couple of days ago when the Note refused to work more than a few mins, I wiped it and reinstalled CM9.1 and this time I wont run things like HydraCore and lower DPI. The problem is less but still exists.
My question, this must be a hardware problem? Or can it be a software problem, if so, what can I do? Can it be that the battery is starting to break? Im a student so I really dont want to buy a new battery and find out that the problem doesnt come from the battery.

Could be the battery. Try a different battery to check if possible.

i believe is something to do wif kernel , when i do oc/uv will have such problem too.
check it out maybe i'm wrong.

I second that it may be the battery. I had loss of reception and flickering screen until I switched battery. You may try to rule out kernel issues by maybe going back to stock to see if it still happens
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2

3rd for battery, had exactly the same issues and replaced the battery, all issues resolved instantly. There are a lot of people who've had this issue and battery resolves 9 times out of 10

ah thanx peeps! Ill buy a new battery then It shouldnt be the kernel issue since I havent been running a overclocked kernel for atleast 1 month.