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.
Related
Hello all,
before anyone yells at me I did search and didn't find anything that makes sense cause this does seem common.
My battery life is still decent not as good as before rooting but I could live with that and not even over clocking is set to max of arround 990 or so but my thing is does seem like I am even just reading a book or the screen is on the bottom part of the phone gets warmer then it did before I rooted my phone.
I have tried different roms like modacos r22 desire r19 froyo, cyan 5.0.8, and rodreigez style and all seemed to have done it.
Seems ok when locked and not used for a while but with screen running for about 10 mins or so I can feel it getting warm. The stock unrooted frf50 i was on did not do that. Maybe recovery you think? Or should I just completely unroot put back stock recovery and all. Will be official then since I didn't unlock bootloader.
I am using setcpu from market and that is set to profiles
sleep 245-460 on demand
charge 245-883 on demand
fail 245-245 on demand
any ideas if I just did something wrong or do I need to flash a different kernel?
*edit*
also may be relevant since I live in 3g coverage I used to have the phone plugged in and download files and never leave 100% battery. Even with it undervolt kernel and not over clocked it drains now when I do this.
Anyone? And something else I noticed, if I plug in with more then 90% power to the pc it wont charge even though shows is charging till gets below 90% till 89 then will start charging. Any ideas?
Hello xda!
Lately my phone has been acting real crazy. I've been on Cognition rom for about a month and I never experienced any issue. However, after flashing SpeedMod k12t, my phone kept freezing while on sleep after 1-2 hours of use. I decided to reflash firebird 2 to make sure it wasn't the new kernel, but my phone recently froze in screen off. I am now sure this has nothing to do with a specific kernel. I have been trying to figure out what's wrong with my phone. I am pretty sure it has nothing to do with my modem either, since I have been using jk4 for about a week or three and this issue never came up until now.
All I'm really thinking of would be my setcpu settings. I recently started to use profiles with the following settings :
Screen off : 200-200 performance (now 400)
Charging : 1000
Battery < 101% : 800 - 1000 conservative
Battery < 39% : 400 - 800
I am thinking the screen off settings are causing all of this trouble. I only started using these a day or two before all of this started. Back then I was testing out a couple different kernel (suckerpunch, gb's kernel, firebird, speedmod). I had a rather poor uptime with suckerpunch because it took a while for me to find the correct settings, and when I did, I remember getting a sleep death that I blamed on the kernel because of the history of charge death it had back then.
Also, my original kernel was firebird and my phone was quite stable during the 3 weeks I've used it. I'm leaving the possibility of a bad kernel away because of this.
So here's my question, xda : What's up with my phone? Is reflashing back to stock and back to Cognition the only possible fix for this? Could me flashing kernels without disabling voodoo be the cause of all of this? Could disabling voodoo and reflashing the kernel fix this? Can set cpu be the cause of all of my trouble (i disabled it for now).
Thanks,
I have the same exact problem and it drives me insane. I have no solution for it except if your last 4 IMEI numbers (under your battery) are below 6000. Mine is 8355 so i dont know.
The last four numbers under my battery are 6, 5, 5, and 9. 6559. This only started a day or two ago. I've only had this phone for a month. So far the problem seems gone, but I've noticed my battery went from 67% to 80 after rebooting my phone to check the numbers under my battery. I recently wiped my battery stats though.
I've only had my phone for about a month too, so i don't know any more than you do. The only thing different for me is the shutdowns were already happening, and the the ROM I flashed just increased it.
Yeah, my phone also seems to freeze when alseep but only if its charging. Sometimes if i disconnect it, it will freeze or if i get a phone call while its charging.
My Captivate had sleep death (randomly) and charge death on some ROMs. After flashing several combinations of ROM/kernel/modem, it seems ok now. I think I will keep on finding a better combination.
SetCPU has some issue with OC/UV kernel on my Captivate, so if you have the same problem try to disable SetCPU first and see if the problem goes away.
So why is it that even when I running a 1.3Ghz phone sometimes games like Dungeon Defenders run REALLY smooth and no issues, but then later I will try to play it and it will run like a bag of spanners, and is completely unplayable?
Rebooting phone often sorts this out, but why should I have to? The GPU has dedicated RAM, all unnecessary applications have been shut down, even put into flight mode.. and still it freezes for seconds (sometimes for a LONNGGGG time), and just generally stutters badly on the screen.
I thought maybe it was to do with the stock rom, but a factory reset proved that the stock rom is fine, but later it screws up. So I try the V20Q rebuilt rom, and stefans's gueste kernel and it still does it.
What is going on? Is the phone running out of resource? Is the second CPU not starting up? What is going on, and how can I find out?
Does it happen after at least 24h of runtime?
No. I've not measured it, but can happen within 8 hours I imagine. I have tried different batteries to rule out a voltage problem.
Is there a memory and dual CPU monitor tool I can use in the back ground to try and find out the problem.. or at least get a head start on the issue?
Oh forgot to mention, whilst it's lagging, even on the initial Dungeon Defenders start up screen... it's very unresponsive, and can take several seconds to identify I pressed something.
Scougar said:
No. I've not measured it, but can happen within 8 hours I imagine. I have tried different batteries to rule out a voltage problem.
Is there a memory and dual CPU monitor tool I can use in the back ground to try and find out the problem.. or at least get a head start on the issue?
Oh forgot to mention, whilst it's lagging, even on the initial Dungeon Defenders start up screen... it's very unresponsive, and can take several seconds to identify I pressed something.
Click to expand...
Click to collapse
If you want a monitor tool, use system panel pro version.
However if the phone begins to be unresponsive after some time, it is because there is memory leak. It is a common problem in stock-based roms. ATM only reboot can solve this issue.
If you flash CM-based roms, the phone will be always smooth.
I did download system panel lite, but will grab 'pro' on Wednesday to help monitor the cpu usage (both cores) and free memory etc.
I actually like the stock V20Q rom... real shame :-(
markop90 said:
If you flash CM-based roms, the phone will be always smooth.
Click to expand...
Click to collapse
wrong. It happens in CM roms too I have to reboot every day to avoid starting to experience lagginess which becomes unbearable on day 3
I will buy the system tool tomorrow and try and monitor what the heck is going on.
It should easily be running this program, there is no reason why it's performing so badly and causing the phone to be unresponsive.
Interesting... whilst running Antutu today, I only got 4900 to 5000 points @ 1.2Ghz. I can get about 7000 at this speed so I wondered what was going on. I checked out systempanel, and it appears to only be using 1 core. Hmm...
@-sandro-
What kernel do you use?
With ironkrnL 32 or 48 there is no lag. Not even after a week without switching the last reboot.
As per sig, using Stefan's gueste v1.1 kernel for stock rom's (V20Q).
(My setup is his kernel + the rebuilt V20Q italian rom from LG with the 'tweak' pack).
Is the ironKRNL compatible with V20Q stock?
-sandro- said:
wrong. It happens in CM roms too I have to reboot every day to avoid starting to experience lagginess which becomes unbearable on day 3
Click to expand...
Click to collapse
You just have an unstable setup, I haven't rebooted in days and I'm running smooth
IRASadPanda said:
You just have an unstable setup, I haven't rebooted in days and I'm running smooth
Click to expand...
Click to collapse
I could say my phone runs "smooth" but then I bench it (The bench will show bad results), or play a game and it can be a stuttery mess.
-sandro- said:
wrong. It happens in CM roms too I have to reboot every day to avoid starting to experience lagginess which becomes unbearable on day 3
Click to expand...
Click to collapse
NEVER happened to me with CM7...it has an excellent memory management
Please, I don't want to discuss different ROM's. I would like help diagnosing the cause
I have now put on gueste v1.2 release candidate, and can see the 2nd core activating earlier. However, I'm still getting random results, and I can't say for sure whether or not the CPU 2 is activating as system panel isn't historically recording the CPU level of CPU 2 individually :-(
In Antutu.. you can see the FPS is down as well even after running a 2nd time. It's all very wierd. (I got 7250, then the next run I got 4900(ish) !)
EDIT: Upon testing, what I noticed the most was that CPU Floating point scores and 2D graphics were at least half of what they should be, whilst 3D score was barely affected at all. This to me points to an issue with the CPU side of things.
Hi all,
I'm currently running AOKP milestones 6 with the Devil Kernel, and everytime I activate the DeepIdle option with NSTools or with the Devil Kernel manager app I get Bsods.
It's not specific to AOKP rom because I had the same problem when I was running CyanogenMod 7. I tried to use Glitch Kernel or Semaphore Kernel but it's everytime the same thing : I get one Bsod after a few hours, and after they come every 10min or so. If I pull off the battery or keep pressing the power button the phone reboots normally but until I deactivate the Idle option I have always this same problem.
I tried using smartass V2 governor or modifying the voltages, doing fresh installs but I can't solve this problem. I also used the BT killer script to see if it changes anything but it didn't solve my problem.
Could it be my phone or am I doing something wrong?
I'd say its probably just the DeepIdle. I do remember reading that DeepIdle support is kinda... weird. In my own experience I've had trouble getting it to work. Had SoD's only a couple of times but actual DeepIdle state won't be used much. It has improved a lot from the Cyanogenmod7 days though.
Is the phone very hot on such an event?
I'd say just don't use DeepIdle if you've had such a long history of problems with it.
I put devil Idle option permanent and I didn't have Sods since this morning, maybe you're right and the Deep idle doesn't work. It's quite sad because it seemed awesome on the paper
And about your question the phone doesn't get hot when this happens, it just stop responding but I have no memories that this happened when I was using the phone only when the screen was off. I'm not sure if it's important but it happened when the phone wasn't used for some minutes or if quickly press power button multiple times.
How did you managed to get it working?
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.