I would post this in the Developer forum, in reply to a poster who has the same problem, but I just registered and therefore do not meet the requirements to post there.
I'm wondering if anyone else has observed this behavior. In short, I installed TriForceROM 3.0 (after performing a "Wipe User Data" operation in TWRP 2.6.0.0) and all was well for about 12 hours. During the ROM installation, I chose the "Standard" option, as I believe it's called. (I didn't elect to customize anything.)
After 12-18 hours of having the ROM installed, I noticed that my phone was simply powered-off. I hit the power button and nothing. Then I held-down the power button, which is how I normally power-on the device, and then realized that the device was, in fact, powered-off when I came back to it after a few hours of being in the other room.
After powering-on the device, the same thing happened a few hours later, and the issue seems to be occurring more and more frequently as time passes.
I have not changed any of the ROMs settings, and I haven't installed any type of third-party "tweaking" app.
Another individual has the same problem:
http://forum.xda-developers.com/showpost.php?p=43942167&postcount=1466
Could this be due to kernel, power, or CPU settings? I noticed that when I opened KTweaker for the first time, the application warned me:
"Your KThermal values do not match current, Apply values?"
and
"Your vibration Strength does not match current, Apply Vibration Strength value?" (this one seems unrelated)
The CPU temperature seems to hover around 45 degrees Celsius. (Is this a normal range?)
Another observation is that when I long-press the Home button (to bring-up the app-switcher), I see a little Android icon with the title "MIPErrorActivi...". If I click on it, I'm simply dumped to the Home Screen. I don't know if this is at all related.
Thoughts or suggestions, anyone?
My phone is model SPH-L720.
Thanks in advance!
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
DrRichardQuack said:
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
Click to expand...
Click to collapse
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Lsd-Pulsar said:
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Click to expand...
Click to collapse
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
DrRichardQuack said:
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
Click to expand...
Click to collapse
I would wager that you moved over to AGAT's. Several users reported lag with that kernel, so I stuck with KT.
After more reboots and a lot of tweaking, I've got my issue nailed down. Raising the voltages on the low end cpu frequencies (where a phone would normally be with screen off) has corrected the stability issues. I also had to up the voltages at the high side. That helped Antutu to run for a while, but now that's crashing back to desktop for me. When it does run, I usually hit around 25,000 with the Triforce 3.0 + Ktoons kernel with overclock enabled. I have not overclocked the GPU (yet). Running KTmod, but not crossbreeder.
I may back this all up tonight and reflash with Triforce 3.1. I've been fighting battery issues: Google Location Services and Android Widgets Pro seem to be behaving badly.
I feel like I'm very close to a fast, stable rom install with good battery life. Once I get there, I'll wait a couple months until the existing ROM's and kernels are polished a little more. And now I'm one post closer to being productive in the Dev forum.
That's the one; AGAT's kernel. I haven't noticed any sluggishness with the ROM's (and or kernel's) default settings. So, I'm happy!
No random power-downs or any other abnormal behavior since upgrading to 3.1 and switching to AGAT's three days ago.
I don't know if it was upgrading from 3.0 to 3.1 or switching kernels that fixed the random power-downs; I'm just glad I have a very fast and stable ROM at this point.
My battery life has been good. Moderate usage throughout an 8-10-hour work-day leaves me with about 70% battery when I get home.
My hat's off to the developer. I think I'll kick him a few bucks.
Related
I wanted to post this in the development section as feedback for garyd9's revised kernel for the P6210, but since I am new with fewer than 10 posts, I cannot do so. I PM'd Gary, he suggested I post it here. So here it is:
I have a P6210 and installed your custom kernel_20120101 and it worked beautifully. The tab was very stable, and battery life is better, as you indicated. I then installed kernel_20120105, and the tab immediately started having sleep of death problems. I would shut off the screen, set it down, and next time I came back to it, I had to do a hard reset by holding the power button ~20 seconds and reboot it. This happened consistently. I then tried kernel_20120107, and had charging issues. The tab got very warm while charging from the AC adapter. Uncomfortably warm. I have no idea if this was related to the kernel update, or just a one-time fluke. I am just relaying my experience. Anyway, the heat freaked me out, so I immediately downgraded back to kernel_20120101, and my tab is completely stable again.
Thanks for the work you do on this.... They are cool devices, and it's nice to be able to play with them.
Thanks.
Click to expand...
Click to collapse
I want to add that I am not running setcpu...
I'm willing to try the newer kernel updates again, or provide any other info Gary may need.
Thx
Can you check which version of the samsung firmware you are using? Does it end with "KL1" or something else?
I'm wondering if it might have been a bad flash or some other fluke. Here are the differences (with comments) between the 1st and 5th:
android ram_console support - this could do something unpredictable, but shouldn't. Basically, what this does is on boot up, it asks the kernel to reserve a VERY specific location and size of memory, and writes kernel messages here. On the next reboot, the kernel will check that exact chunk of memory and if certain headers are in place, it will stick a copy in /proc/last_kmsg. In this way, I might be able to see the kernel messages (including any panic) from the previous boot. Of course, the memory often gets trashed between the two boots, so this doesn't always work. Anyway, if something else is trying to use the exact same memory, it could cause problems (but it would cause the same problems for everyone with the same model tablet...)
bootanimation: This isn't actually a kernel change, but a modification to the init script that checks to see if a bootanimation file is present and if so it'll run samsung's own "bootanimation" binary instead of samsung's "samsungani" binary. In either case, the process is killed when the lock screen is first presented.
conservative governor stuff: As you aren't using setCPU, you are still using 'ondemand' so this stuff would have NO impact.
---
Honestly, the issue reported kind of surprises me. The kernel I'd expect to give people problems would be the 0101 one, as I mess with clock speeds and voltages in there. Since then, the changes have been very light. Can you try to delete any copies of Jan07 you might have sitting around, completely redownload it, and reflash it? Let me know if you have the same (or different) issues.
If you do have issues, use the market app called "OS Monitor" to export the dmesg log (while you are having the issue or immediately afterwards, but before rebooting.) Upload the exported log here (or somehow get it to me) with a full description of what was happening, if it was occuring during the time you exported the log (or how long previous to exported it occured), etc.
At that point, go ahead and revert to whichever kernel you are comfortable with and I'll study the log and try to see whats going on over the weekend.
Take care
Gary
Gary,
I flashed "GT-P6210 for US RETAIL" from this thread:
http://forum.xda-developers.com/showthread.php?t=1367478
Here's a screencap.
http://woodsware.aciwebs.com/galaxy_capture_01.png
I'll try the 20120107 kernel again, and let you know. It may be tonight....
Thanks!
i flashed the new kernel last night, and i haven't really had a chance to test it, but i did do some reading on the SOD deal, and i have my wifi set to "sleep when screen off" and i left home an hour ago, just pulled out my tab plus and BAM, fired right up.
I did want to ask you one request, any chance of implementing "smartassv2"? i'm gotten so lazy and spoiled with it...i never got around learning how to set profiles and junk, so this always helped me out...
rswoods said:
Gary,
I flashed "GT-P6210 for US RETAIL" from this thread:
http://forum.xda-developers.com/showthread.php?t=1367478
I'll try the 20120107 kernel again, and let you know. It may be tonight....
Click to expand...
Click to collapse
Okay, that's the older KK3 firmware. Here's what I'd like for you to do (if you could):
1. reflash that from the ODIN thread. That should revert recovery, the kernel, etc. Then attach your tablet to your PC and let Kies run to update the firmware to KL1. It would really be best if your firmware was updated BEFORE changing kernels. There are a couple reasons for this, but most importantly so that we are talking about the same thing (I've only ever tested these kernels with KL1.)
2. Make sure Kies has updated your firmware... settings->about->build number should show something like HTJ85B.UEKL1.P6210UEKL1. If Kies updates the firmware to something beyond "KL1" (if the number is greater than 1 or the last letter is beyond "L") then STOP, reply to this post letting me know the build number. (I'll want to revert my own tablet to stock and get it on the latest build for testing.)
3. Then go ahead and start playing with kernels - you will hopefully be good to go. if not, let me know.
Take care
Gary
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
Thedonk13 said:
i flashed the new kernel last night....
Click to expand...
Click to collapse
Please post this in the proper thread (in the DEV subforum.) I asked rswoods to post his question here in general as he can't post in DEV yet (doesn't yet have 10 posts), but I wanted the "public" to see the troubleshooting steps in case others have similar issues, etc. (I can't complain that people aren't searching for answers if the answers are hidden in PM's.)
Oh, and probably not. The same can be accomplished with SetCPU profiles, and I'm working hard to REDUCE the kernel footprint.
Take care
Gary
Gary,
OK... I reflashed the stock ROM, updated to KL1 through Kies, installed p6210_CWMR_20120107.zip, then flashed your 20120107 kernel. So far so good.
I'll see how it goes the next few days and report back.
Thanks for the help!
Gary,
Things are mostly good, but I'm still getting infrequent SOD's. I never know when it will happen... It will wake successfully several times in a row, but every once in awhile require the long press reboot.
rswoods said:
Things are mostly good, but I'm still getting infrequent SOD's. I never know when it will happen... It will wake successfully several times in a row, but every once in awhile require the long press reboot.
Click to expand...
Click to collapse
SOD's are unsolved. The majority of people having them are using the stock firmware and kernel (and replacing the kernel with mine doesn't seem to help whatsoever.) There's a thread dedicated to the subject here - you might find it interesting reading.
I'm glad the other issues you were experiencing have gone away...
Take care
Gary
Things are running great for me.
So I have the i9020T (from Wind in Canada). I enjoyed running CM9 nightlies on it, but then Jellybean came along and I went nutso over it (like so many others). I flashed back to stock ICS, and then ran the OTA update on it to JB.
My experience has been disappointing. It was unfathomably slow. It was running-Windows-7-on-a-Pentium-III slow. The new UI and features are glorious, but I need a lot of patience if I expected to use them. I'm talking about delays of around 5 seconds to start an app, switch apps, or even open the app drawer, 2-3 seconds lag when bringing up the keyboard, and 5-10 seconds to bring up Google Now.
I automatically decided to nuke everything and start from a clean slate. I grabbed the 4.1.1 stock image from Google, then formatted /system and threw it on. After the initial setup, and before I even got to rooting the thing (never mind restoring from Titanium), it was still muscle-atrophyingly slow.
I ended up just restoring all of my apps and data, and using it as-is, figuring this is what I should expect from an older device. Yet everyone online raves about how much faster JB is than ICS on the Nexus S. Either you're all trolling me really hard, or I'm doing something very wrong.
Here's some more gory details:
Like I said, I wiped /system before loading the new image. I did it on the phone using Clockworkmod recovery, then used fastboot from my computer to load the image. I did not wipe data or cache, because I figured the whole image-writing thing would be obliterating all my stuff anyway, but perhaps I was wrong?
I've been playing with the CPU usage overlay, available in the Developer Options. First off, I have no clue what the different colours mean or what scale those bars represent, but I can tell you my load is typically 2.0 (even just sitting there idle with the screen on), all the way up to 15 or so if I'm trying to do something like use Chrome while listening to Google Play Music. system_server is always the top process, and its bar is always 3-4 times bigger than the next, with the sole exception of loading up Google Play Music, in which case the mediaserver process holds the top spot with a fairly long bar. ksmd, com.android.systemui, surfaceflinger, and com.android.phone are always running, but only ksmd even has a bar long enough to be visible. Other processes pop in and out, and of course they start going willy-nilly when I actually start using apps and switching between them.
There have been a handful of times where an app will die while I'm in the middle of using it, and 2-3 times the phone has outright rebooted itself.
So there's my story. Can someone tell me if I'm just plain doing it wrong? Perhaps there's a guide on how to completely sterilize the phone before loading the stock image? Or perhaps my hardware is broken? :-/
I was with you there, trying to figure out why everyone thought it was so fast and I was being left in the dust. Google Now in particular was painful to interact with. I downloaded and installed Air Kernel, which seemed to help a little bit but then I switched the CPU governor from "ON DEMAND" to "SMARTASSV2" and it was like night and day. It's flying and I'm satisfied.
Cool... I'm looking into it, and can't find any directions whatsoever on what I should download or how to install it. I'll keep digging, though. Thanks!
While I am not sure what is causing your issue I can confirm that stock jb should not be performing like you are describing. Except for loading up Google now. That does take some time but even that once its loaded runs OK.
Did you clear your SD card? If not back that up to a computer and wipe it. That's all that I can think of and it may actually fix it.
At first I noticed painfully slow speeds as well. Changing my min setting to 200 helped so much! I've heard the the Interactive governor is amazing with JB in terms of speed. You could try that out.
Nexus S. (GSM i9020a)
Paranoid (1.97 - 4.1.1)
Matrix (CFS - 22.5)
Ondemmand (1000/200)
Deep Idle (On - Deadline)
I've just flashed Air Kernel (I just picked one of four options, I don't know what the heck "blue color" means), then set the governor to smartassv2, and so far it feels snappier. I'll have to keep using it to see if it's the solution I need. Thanks to all who've made suggestions so far!
Sent from my Nexus S using xda app-developers app
If your phone is going crazy slow it could be a number of things like apps could be slowing down the phone in the background or the phone might be trying to sync. You could backup all of your apps and then wipe your phone fully it should speed it up quite a bit and then you can restore each app 1 by 1 to determine if its a rogue app causing it. But if you can't be arsed to do that and wipe then just try and flash Thalamus kernel and see what its like if you set the governor to interactive on that it should go crazy fast.
Sent from my Crespo using xda premium
Please provide clear advice Nexus S so slow on Jelly Bean
ronnygunz said:
I was with you there, trying to figure out why everyone thought it was so fast and I was being left in the dust. Google Now in particular was painful to interact with. I downloaded and installed Air Kernel, which seemed to help a little bit but then I switched the CPU governor from "ON DEMAND" to "SMARTASSV2" and it was like night and day. It's flying and I'm satisfied.
Click to expand...
Click to collapse
I can see there are many 'fixes' for slow running devices on Jelly Bean. However, I have no idea:
1. how install Air Kernel or where to get it from
2. How to change the CPU governor from "on-Demand" to "SMARTASSV2" or where to download this from
Please can someone give me the complete idiots guide to getting my Nexus S running properly again??
THANK YOU
There are a million guides on this forum for all of this. If you don't know how to flash a kernel or adjust CPU speeds, you need to familiarize yourself with these things and understand the risks. First off, try cleaning your phone up. Take all your important stuff off your external storage, and do a factory reset. My Nexus S never ever ran slow, even on stock.
Have you tried a more simple but fast kernel like marmite 4.2 from bedalus? Give it a try.
I've been running stock 4.1.2 (rooted) for a while now, and after really slow performance, steadily worsening battery life, and general annoyances like random reboots, Blue Screens, and other annoyances like duplicated incoming SMSs, I figure it's time to take the plunge and install a custom ROM and maybe even a fresh kernel.
Unfortunately, I don't have the time to devote to experimenting with all the different ROMs out there for this phone, and was wondering if I were to list out what I usually use the phone for and what apps I run most of the time if it would be possible for people to recommend which one would be a good fit to try as my first.
(I know this'll mean missing out on all the fun of having so many choices, and when I have more time later, I'll see what I can do about exploring the other options.)
I make heavy use of SMS, although often times my messages are laggy to send and receive (I don't know if this is a problem with my phone or T-Mobile). Incoming messages sometimes get repeated multiple times for no apparent reason. My current SMS default is EvolveSMS, but I had similar issues with GOSMS.
I also play Ingress, so any bugginess in the GPS would be a deal breaker.
Voice calling is sometimes problematic as well. When I make outgoing calls, it sometimes take 30 seconds for the phone app to load., With incoming calls, I may get the ringtone, but no screen to accept or reject the call.
I run the xposed framework for a handful of modules (All Notifications Expanded, and Buttered Toast)
I'm using Nova Launcher for my homescreen, because of the ability to set a grid size, use custom icons, overlap icons on top of widgets, and lock the homescreen configuration from accidental changes. A ROM that would do the same things natively without having to run a homescreen replacer would be welcome.
I'm also interested in running on my external SD, Is that something I should set up prior to flashing the new ROM, or can that only be done after the ROM is installed?
Team Apex have done some great work. By now they know the hardware very well, having done the initial dev work back on CM9, all the way up to the current CM11 and now Omnirom systems. Their current efforts are focused on the Omnirom-based Omnitoad project. It's at a point where it works very well. I suggest starting there.
The stock roms and the earlier CM roms all have a bug where the compass reads totally wrong after a reboot until you recalibrate it. This was finally fixed in the CM11-based ROMs. That should help Ingress.
radwolf76 said:
I've been running stock 4.1.2 (rooted) for a while now, and after really slow performance, steadily worsening battery life, and general annoyances like random reboots, Blue Screens, and other annoyances like duplicated incoming SMSs, I figure it's time to take the plunge and install a custom ROM and maybe even a fresh kernel.
Unfortunately, I don't have the time to devote to experimenting with all the different ROMs out there for this phone, and was wondering if I were to list out what I usually use the phone for and what apps I run most of the time if it would be possible for people to recommend which one would be a good fit to try as my first.
(I know this'll mean missing out on all the fun of having so many choices, and when I have more time later, I'll see what I can do about exploring the other options.)
I make heavy use of SMS, although often times my messages are laggy to send and receive (I don't know if this is a problem with my phone or T-Mobile). Incoming messages sometimes get repeated multiple times for no apparent reason. My current SMS default is EvolveSMS, but I had similar issues with GOSMS.
I also play Ingress, so any bugginess in the GPS would be a deal breaker.
Voice calling is sometimes problematic as well. When I make outgoing calls, it sometimes take 30 seconds for the phone app to load., With incoming calls, I may get the ringtone, but no screen to accept or reject the call.
I run the xposed framework for a handful of modules (All Notifications Expanded, and Buttered Toast)
I'm using Nova Launcher for my homescreen, because of the ability to set a grid size, use custom icons, overlap icons on top of widgets, and lock the homescreen configuration from accidental changes. A ROM that would do the same things natively without having to run a homescreen replacer would be welcome.
I'm also interested in running on my external SD, Is that something I should set up prior to flashing the new ROM, or can that only be done after the ROM is installed?
Click to expand...
Click to collapse
to be fully honest though...i do highly recommend flashing my B14CKB1RD kernel on whatever 4.4 kit kat rom you use if you want best stability and battery life...its been proven that at the end of the day your rom will have alot of batterly life remaining compared to stock....whats good about my kernel is that you control how you want the phone to work...where as with TeamApexQ stock kernels you are locked to that one state and also has an mpdec touchboost enabled that boosts your cpu core to 1134mhz minimum speed when you touch the screen thus rapidly draining your battery... I'm in no way saying the work they have done isnt great....theyve done a hell of a job bringing the device to the stability its at today... it just brings that much more stability outta any rom you use
REV3NT3CH said:
to be fully honest though...i do highly recommend flashing my B14CKB1RD kernel on whatever 4.4 kit kat rom you use if you want best stability and battery life...its been proven that at the end of the day your rom will have alot of batterly life remaining compared to stock....whats good about my kernel is that you control how you want the phone to work...where as with TeamApexQ stock kernels you are locked to that one state and also has an mpdec touchboost enabled that boosts your cpu core to 1134mhz minimum speed when you touch the screen thus rapidly draining your battery... I'm in no way saying the work they have done isnt great....theyve done a hell of a job bringing the device to the stability its at today... it just brings that much more stability outta any rom you use
Click to expand...
Click to collapse
mpdec and touchboost are two separate concepts. Touchboost boosts the second core to 1134 Mhz when you are using the display in order to make the phone more responsive. Mpdec turns off the second core when not in use and conserves a huge amount of battery. On OmniToad, with the standard kernel on it, I usually get 60 hours + per charge of medium use. I've been using OmniToad continuously, and since the beginning of it, I have not personally had any reboot that was not initiated by myself.
Um dude you do know your touchboost is mpdecision based right?....look at the defconfig...and to be honest my kernel works just as smooth if not smoother than the stock kernel of omni without it...using omni on stock kernel I wald have 40% battery come 11pm my time when unplugged at 7am...on my kernel I'll have anywhere between 65% and 70% with same usage and hours
Sent from my L1QU1D R3L4Y using xda-developers app
One other thing about touchboost, which will hopefully bring us all out of ignorance of it as I am tired of the constant FUD about it. It is the 'touch responsiveness' portion of Google's "Project Butter" initiative. It is a standard Android/AOSP feature enjoyed by Nexus owners since Android 4.1.x.
One more thing. It is a UI deficiency that the performance settings apps show 1134Mhz as min cpu when using touchboost. In kernel mpdec will run the cpus at 384mhz unless something needs more, or the cores will sleep. Now you know the facts. Let's stop spreading misinformation. Thanks.
Not spreading misinformation...my builds and the community have even spoken of the better battery my kernel and ROMs have with it disabled and removed....even flashing my kernel over omni the phone instantly stopped overheating and lost maybe a percent in 2 hours with moderate use.... I just love how as soon as I came to the relay you guys judged me as a noob and all the name calling and what not....it's your teams loss...all my gain...good luck
Sent from my L1QU1D R3L4Y using xda-developers app
In my opinion, I try all the roms available for relay right now, the better performance I have was with liquid ROM and blackbird kernel. Omni is smooth but the battery its not the best for my phone with my personal use, and with GPS and plugged to the car charger i got overheating. Carbon got better battery than omni and better customization options but not smoother. Liquid have all you need in a ROM, personalization, full control and with the kernel blackbird and Wheatley and sio configuration have the better performance and battery at all ROM I try
Sent from my SGH-T699 using XDA Premium 4 mobile app
So, I tried OmniToad for a bit. Wasn't really impressed with the compass fix mentioned above, because even after flashing it was still quite ill-behaved in Ingress.
I also couldn't get the External 2 Internal SD Card swap to work -- the storage tab kept reporting my internal as 5 gig and the external as 64gig. This was after trying two different microSDs.
So, because of those two issues, and being not too far along in re installing everything, I decided to flash again, with the Blackbird Kernel and Liquid Smooth.
Now, when I try to boot. it hangs on the screen with the ApexQ green penguin. If I try for recovery mode I'll get the blue text that says booting into recovery, and then it goes to the penguin again. Trying to boot to download mode also just gives me the penguin.
Troubleshooting suggestions? Because right now, I'm without any clue as to what to do next, and without a phone for that matter.
[Edit: Just got into recovery, so going to try flashing back to OmniToad]
[Edit 2, Electric Boogaloo: Back on the Toad for now, Seems to be working. Thoughts on how to get things running on my external SD? Is it maybe an issue with KitKat based roms?]
I'll guide you through it...my roms shouldn't show anything teamapexq related ...what recovery were you using...and have you tried heimdall or ODIN
Sent from my L1QU1D R3L4Y using xda-developers app
REV3NT3CH said:
I'll guide you through it...my roms shouldn't show anything teamapexq related ...what recovery were you using...and have you tried heimdall or ODIN
Sent from my L1QU1D R3L4Y using xda-developers app
Click to expand...
Click to collapse
Recovery is TeamWin, and I was finally able to get back into it. Put OmniToad back on it for the time being. If you wanted to put up a step by step for going from Omni to Liquid, I can give it a try, because at this point, I'm pretty sure it was a "ID Ten T "error.
Magamo said:
mpdec and touchboost are two separate concepts. Touchboost boosts the second core to 1134 Mhz when you are using the display in order to make the phone more responsive. Mpdec turns off the second core when not in use and conserves a huge amount of battery. On OmniToad, with the standard kernel on it, I usually get 60 hours + per charge of medium use. I've been using OmniToad continuously, and since the beginning of it, I have not personally had any reboot that was not initiated by myself.
Click to expand...
Click to collapse
Did u just say 60+ hours of use??
How?? What do u mean by medium use?? Are you using the stock battery??
That's only possible with screen off with no use in that 60 hours and the phone going into deepsleep...either that or he's using an extended battery....with very minimal use....also proof or it didn't happen
Sent from my L1QU1D R3L4Y using xda-developers app
@radwolf76 I sent you a pm
Sent from my L1QU1D R3L4Y using xda-developers app
I ended up partitioning my external SD card so I could use Mounts2SD. Seems to be working so far.
Now I just have to get all my stuff put back on this thing and figure out how the extra features of LiquidSmooth are going to fit into my workflows.
One thing that seems to be a minor annoyance, probably because I just haven't found the toggle for it yet: on stock, I used to be able to wake the phone from the home button and the screen would pop on instantly. Under both custom ROMs I've tried, it seems a lot harder to wake the phone. The power button seems to be the only thing that works, and I have to stab at it repeatedly. I almost suspect that I'm waking it up and puttting it back to sleep before the screen comes on, but I can't seem to find anything that consistently works. Like I said, it's probably something I just need to toggle under settings.
The home button's actual switch is in the center of the button, while the design allows the button to tip sideways. So if you press it on a corner instead of the middle, the phone sometimes won't recognize it.
radwolf76 said:
I ended up partitioning my external SD card so I could use Mounts2SD. Seems to be working so far.
Click to expand...
Click to collapse
I may have spoken too soon. Getting all sorts of apps stopping on me now. Launcher3, Hangouts, Ingress, Settings...
Also, Launcher3 seems to 'forget' homescreen layouts every so often... some times I'll be going back to blank homescreens, and then after poking around in other apps, the homescreen will be back to the original configuration.
Ingress also acts like it can't see Location Services most of the time.
Also, sometimes when I reboot, it takes up to 20 minutes before the phone's back up and running.
While I can't discount that it was any of the number of apps I've put back on the thing, I'm pretty sure that Mounts2SD is the smoking gun here. these problems didn't start until after I had started using it. The symptoms seem about right.
I'm wondering if there's a conflict between Mounts2SD and the governor/scheduler I'm running (Wheatley/SIO).
I'd rather not have to troubleshoot this, but one of my main goals with starting fresh on this was to be able to store and run apps on my External SD, preferably without having to fuss with it on a per-folder basis. So if anyone has had any success in that department, I'd love to hear some tips that point me in the right direction.
[Edit: Turns out Mounts2SD overrides the governor/scheduler choices anyway. I think, that when I get off work I'm going to start fresh again over my next few days off, and try using Link2SD instead.]
radwolf76 said:
I may have spoken too soon. Getting all sorts of apps stopping on me now. Launcher3, Hangouts, Ingress, Settings...
Also, Launcher3 seems to 'forget' homescreen layouts every so often... some times I'll be going back to blank homescreens, and then after poking around in other apps, the homescreen will be back to the original configuration.
Ingress also acts like it can't see Location Services most of the time.
Also, sometimes when I reboot, it takes up to 20 minutes before the phone's back up and running.
While I can't discount that it was any of the number of apps I've put back on the thing, I'm pretty sure that Mounts2SD is the smoking gun here. these problems didn't start until after I had started using it. The symptoms seem about right.
I'm wondering if there's a conflict between Mounts2SD and the governor/scheduler I'm running (Wheatley/SIO).
I'd rather not have to troubleshoot this, but one of my main goals with starting fresh on this was to be able to store and run apps on my External SD, preferably without having to fuss with it on a per-folder basis. So if anyone has had any success in that department, I'd love to hear some tips that point me in the right direction.
[Edit: Turns out Mounts2SD overrides the governor/scheduler choices anyway. I think, that when I get off work I'm going to start fresh again over my next few days off, and try using Link2SD instead.]
Click to expand...
Click to collapse
well i use nova launcher.....launcher 3 and google launcher in my opinion isnt the best of launchers...there is other options i mentioned in a pm before to storing apps on sd and is alot easier than fiddling looking for the right app ....what also gives you the assumption it messes with governer or scheduler....i know by default there is settings for sd read ahead write ahead scheduling but that app shouldnt have control in changing any of this
REV3NT3CH said:
what also gives you the assumption it messes with governer or scheduler....i know by default there is settings for sd read ahead write ahead scheduling but that app shouldnt have control in changing any of this
Click to expand...
Click to collapse
This post from another user in the Mounts2SD thread. They might be mistaken, but either way, my problems started cropping up after I installed that app, and if there's a chance that poster is right about it setting those things, that's just another reason for me to uninstall it.
right now Carbon wins
I've tried them all, Liquid smooth is awesome but the latest built gave me some blackscreen issues until the next built go with carbon if you want some nice features or slim for a nice overall rom.
Don't forget to install the Blackbird kernel for a even better result.
Peace!
Hey guys, lately I've been having the eventx-xxxx wakelocks that *seem* to keep my phone awake and drain my battery. These wakelocks are usually event0 ones and followed by a four digit number which I believe to be the Process ID.
The current wake lock I am having is event0-2012 shown by BBS. It changes on every so the PIDs are rarely the same. It also happens that the 4 digit number happens to be the process ID of system_server. So there's something that's keeping it awake.
Lastly, the event0 is the synaptics touchscreen. So I'm guessing that this event0 wakelock keeps track of all the touches you make on the screen. This problem only appeared after the new touchscreen firmware updates so that may be the cause. Anyone have any thoughts on this matter?
Screenshots for proof below
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Alright guys I'm back to share what I have found after doing some research.
Right now I'm using ark kernel with liquid smooth 3.2 milestone
So back to these wakelocks, as it turns out, even though event0 was the most prevalent, most of the time it was on was while the screen was on, so basically you can ignore it.
However, there were two other events that I still had to investigate, event2 and event3. For me event2 is gpio_keys which are the button inputs. event3 is s2w_pwrkey.
First I deleted the event2 file under /dev/input. These files are restored on boot but I would still make a backup before trying this. After deleting this, my volume buttons stopped working, as expected. But my power button still worked. I used it for a couple hours but there was something that was keeping my phone awake still.
Then I rebooted and deleted event3. This is related to the sweep2wake that's implemented in alucard's kernel. I never use it anyway so I went ahead and deleted it. And what do you know, now my phone is sleeping like a baby and even the other events have gone down as well. But the problem is you have to delete the file on every boot. The solution? An init.d script with the following line. Where X is the number of the event you want to remove. You can also just add it to any existing scripts you might have in /system/etc/init.d
rm /dev/input/eventX
How to find out what's causing yours?
1.Download wake lock detector from the
play store and use it for a day
2.check under kernel wakelocks to see if
your phone is being kept awake by an
alarmingly high number of event
wakelocks, if so proceed.
3. Open terminal emulator and type the
following: "su" press enter after each
line
"ps | grep xxxx" where xxxx
is the number
following the event
wakelocks.
4. If system_server doesn't show up,
another app is causing it. Find it and
manage it. Otherwise, proceed.
5. Go back in terminal and type "su" enter
"getevent -c 1" this will give you all
of you events and and what they
are bound to.
6. Make a backup in recovery.
7. Delete one of the problem events and
see if your phone is kept awake, if it.
isn't then congrats! You found the
drain! Else keep testing.
8. Once your are certain which one it is.
Create an init.d or use an existing
one and add the line "rm /dev/input/
eventX" replace X with the event
you want to remove.
You're done.
If you have any problems or questions, I'll be happy to help.
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Thanks alot for this thread, very helpful. :good:
i don't have wakelocks (using @ak kernel and enabled only dt2w) but very useful thread
5 star rated :good:
ak said:
Thanks alot for this thread, very helpful. :good:
Click to expand...
Click to collapse
Cool that means alot coming from you
wizyy said:
i don't have wakelocks (using @ak kernel and enabled only dt2w) but very useful thread
5 star rated :good:
Click to expand...
Click to collapse
Thanks! I've never had a 5 star thread before
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
I am on cm11s and have these same wake locks but all are less than 10 on so far a days worth of battery time. I don't think it's much of a problem for me and probably more for cm12? Anyways thanks for the info now I know where to look if it ever becomes an issue
Cheers
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
tracerit said:
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
Click to expand...
Click to collapse
Agreed, it only started happening recently and I haven't installed any new apps, but newer Roms and kernels. So I really don't know whats causing it
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
tracerit said:
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
Click to expand...
Click to collapse
Update: I flashed AK v30 kernel and the wakelocks seem to be gone now! Prior to this I was on Mahdi with stock kernel which had the wakelocks, and prior to that I was on Mahdi with AK v11 kernel which also had the wakelocks. This is only after an hour of "testing" though, so hopefully no apps I'm going to use will trigger them back :/
Edit: jk, wakelocks returned after a while. Screenshot attached. I rebooted the phone then left it alone for almost two hours.
Getting event0 1585 wakelocks, quite alot , more than 30k wakelocks in 3 hours.
It seems to be related to the synaptics driver, which to my knowledge is the touchscreen so i better not turn that off
Running AK 030 with Paranoid Saber Droid 4.4.4
mumaster20 said:
Getting event0 1585 wakelocks, quite alot , more than 30k wakelocks in 3 hours.
It seems to be related to the synaptics driver, which to my knowledge is the touchscreen so i better not turn that off
Running AK 030 with Paranoid Saber Droid 4.4.4
Click to expand...
Click to collapse
No just ignore that one. Most of the the 30k happens when the screen is on l
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
abhi08638 said:
No just ignore that one. Most of the the 30k happens when the screen is on l
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
mumaster20 said:
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
Click to expand...
Click to collapse
I'll look into it
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Nice investigating and bug hunting OP.
mumaster20 said:
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
Click to expand...
Click to collapse
Alright, unfortunately I couldn't find any information about it. Are you running any auto brightness apps? Autorotation? Accelerator gaming? Magnetic case?
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Flashed the most recent boeffla kernel this morning (had ak 030 yesterday) and this whole day I haven't had any disruptive event wakelocks. Instead of minutes of those wakelocks, they're just St seconds now. Didn't change anything else.
tracerit said:
Flashed the most recent boeffla kernel this morning (had ak 030 yesterday) and this whole day I haven't had any disruptive event wakelocks. Instead of minutes of those wakelocks, they're just St seconds now. Didn't change anything else.
Click to expand...
Click to collapse
That's curious. It might be because of new commits that might have been reverted in the kernels. Right now I'm using Ark kernel
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
abhi08638 said:
Alright guys I'm back to share what I have found after doing some research.
Right now I'm using ark kernel with liquid smooth 3.2 milestone
So back to these wakelocks, as it turns out, even though event0 was the most prevalent, most of the time it was on was while the screen was on, so basically you can ignore it.
However, there were two other events that I still had to investigate, event2 and event3. For me event2 is gpio_keys which are the button inputs. event3 is s2w_pwrkey.
First I deleted the event2 file under /dev/input. These files are restored on boot but I would still make a backup before trying this. After deleting this, my volume buttons stopped working, as expected. But my power button still worked. I used it for a couple hours but there was something that was keeping my phone awake still.
Then I rebooted and deleted event3. This is related to the sweep2wake that's implemented in alucard's kernel. I never use it anyway so I went ahead and deleted it. And what do you know, now my phone is sleeping like a baby and even the other events have gone down as well. But the problem is you have to delete the file on every boot. The solution? An init.d script with the following line. Where X is the number of the event you want to remove. You can also just add it to any existing scripts you might have in /system/etc/init.d
rm /dev/input/eventX
How to find out what's causing yours?
1.Download wake lock detector from the
play store and use it for a day
2.check under kernel wakelocks to see if
your phone is being kept awake by an
alarmingly high number of event
wakelocks, if so proceed.
3. Open terminal emulator and type the
following: "su" press enter after each
line
"ps | grep xxxx" where xxxx
is the number
following the event
wakelocks.
4. If system_server doesn't show up,
another app is causing it. Find it and
manage it. Otherwise, proceed.
5. Go back in terminal and type "su" enter
"getevent -c 1" this will give you all
of you events and and what they
are bound to.
6. Make a backup in recovery.
7. Delete one of the problem events and
see if your phone is kept awake, if it.
isn't then congrats! You found the
drain! Else keep testing.
8. Once your are certain which one it is.
Create an init.d or use an existing
one and add the line "rm /dev/input/
eventX" replace X with the event
you want to remove.
You're done.
If you have any problems or questions, I'll be happy to help.
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
Really a different way to deal with the problem than any other threads I have gone through. I am facing the same issue. Phone being awake when connected to WIFI only. The problem does not persist with Data connection and WIFI Off. Its very strange. I was working around for the solution but different things seemed liked working at different times.
Though I was having Event wakelocks and not wlan wakelocks I followed some solutions from this thread http://forum.xda-developers.com/galaxy-s2/help/puzzle-wlanrxwake-wakelock-sgsii-t2133176
Disabling netbios worked for me and again after an update the problem came back. Next time I tried changing frequency to 2.4Ghz and it worked. Now again after dalvik cache wipe the problem came back. No solution left to try.
I shall try the methodology u hav provided. Finger crossed. Really frustrated with this issue. Unable to keep the phone connected to WIFI.
But what can be the real issue. How can the volume keys or sweepwake issues persist only on WIFI and not on data connection. Should I ask for am exchange from OPO?
abhi08638 said:
Alright, unfortunately I couldn't find any information about it. Are you running any auto brightness apps? Autorotation? Accelerator gaming? Magnetic case?
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
Non of that, next to the standard autorotation and auto brightness of android itself. I did see that all the screen off gestures were turned on in synapse so I turned that off but it didn't seem to help. Its not that big of a deal though, probably some necessary stuff happening in the background. Still getting rock solid battery life! 6+ hours sot over 2 days so you don't hear me complain thanks anyways for sharing your info!
Sent from my One using XDA Free mobile app
kandalamv said:
Really a different way to deal with the problem than any other threads I have gone through. I am facing the same issue. Phone being awake when connected to WIFI only. The problem does not persist with Data connection and WIFI Off. Its very strange. I was working around for the solution but different things seemed liked working at different times.
Though I was having Event wakelocks and not wlan wakelocks I followed some solutions from this thread http://forum.xda-developers.com/galaxy-s2/help/puzzle-wlanrxwake-wakelock-sgsii-t2133176
Disabling netbios worked for me and again after an update the problem came back. Next time I tried changing frequency to 2.4Ghz and it worked. Now again after dalvik cache wipe the problem came back. No solution left to try.
I shall try the methodology u hav provided. Finger crossed. Really frustrated with this issue. Unable to keep the phone connected to WIFI.
But what can be the real issue. How can the volume keys or sweepwake issues persist only on WIFI and not on data connection. Should I ask for am exchange from OPO?
Click to expand...
Click to collapse
Yeah I have noticed this wifi issue as well. Iight be related to the new drivers that were implemented but I haven't been keeping up with that so I don't know if it was reverted or not. I usually keep the wifi sleep policy to never. As I said before, I don't really know why they show up, but this "solution" is very dirty. The best way would be to find the cause of it.
I removes the s2w event because whatever triggered it actually uses power by keeping the capacitive keys on. So stopping that process ultimately saved me some battery.
Sent from my LG-P880 using XDA Free mobile app
Hello World,
I recently purchased a SGN 12.2 Pro - Model Number SM-P900.
I flashed CyanogenMod onto it, and now its Android Version is 5.1.1
The CyanogenMod version is 12.1-20151104-Unofficial-v1aWIFI
The kernel version is 3.4.104-gd233b3f
Now for the most part the system runs smooth and w/o problems, but 7 or 8 times out of 10 when it goes asleep (screen is off and no program is actively running in the foreground, but the system was not shut down), I can not wake the tablet back up again.
Matter of fact, I end up having to perform a hard reboot on the tablet (pressing the power button until I force a reset) to get it to respond again.
I ran a logcat session in the background to catch any error, but the recorded log did not any error when this happened. It just suddenly stopped recording.
For me it seems like the system is going into some sort of hibernation mode, from which it only awakes after a hard reset.
But I don't see any such setting as "hibernation" in my system panel, and I certainly didn't install any such program on my tablet.
Now I am getting afraid that I might end up corrupting the filesystem or some important database by forcing these hard resets all the time.
That is why I need to find out what's going on here - anyone got some constructive ideas about it?
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
ShadowLea said:
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
Click to expand...
Click to collapse
Nice idea, but I need the functionallity of CM, and I also rely on my tablet for work - so I can't play "flashaholic" here.
But I have upgraded my CM Firmware three times in a row by now, and if this is CM related, then all those firmware packages would have to cause the same problem - with me being the only one who suffers from it (because I didn't read anyone else having this problem in the CM comment threads).
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Osama chohan said:
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Click to expand...
Click to collapse
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Masinissa said:
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Click to expand...
Click to collapse
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Osama chohan said:
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Click to expand...
Click to collapse
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Masinissa said:
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Click to expand...
Click to collapse
I'm glad that you fixed the problem and sorry that i couldn't be of any help.