Related
Hello all,
I am a little new to installing new mods, and tweaks to the android phone, but i have successfully installed Eugene 2.2, and team whiskeys 2.2 without any prob.
I had superpower running on both no probs, Currently i am running axura 2.0.5m which I really love, but i cant get superpower to work properly on it, it keeps turning off my antenna all together, so i dont even get 2g.
I have tried reinstalling axura, and still i have the same prob.
I would appreciate any advice
thanks
Im totally new as well and put in axura 2.05 and was doing great. After 11 hours I only used up 15% of power, not a lot of use, but still good.
I installed superpower today and in 45 mins I lost 20%. The back was also very hot. I rebooted a couple times, still bad. I removed super power and then it wasnt hot anymore. I hope its a temporary glitch.
2 posts talking about superpower... and I have no clue WTF that is?
s15274n said:
2 posts talking about superpower... and I have no clue WTF that is?
Click to expand...
Click to collapse
Its an app that's supposed to make battery life better I think not sure but I think one of the roms I flashed before had it preinstalled
V5 custom vibrant
I'm running Com Rom 1.3, and was looking for some kernel recommendations. I'm running the kernel that came with Com Rom which I guess is OTB, I never flashed OTB 1.4 so I don't know if I am running it. I was thinking about PeanutButta Jelly Time but was wanting some reviews on it first.
I am running PB&J 50 but found the smoothest is 100 and i will most likely flashing back to that later today.
But i could never get ComRom to run with OTB 1.4 so i cant really compare.
Good Luck!
what are you looking for? with otb you can customize your clock speeds/voltage settings to maximize speed or battery life. with pbj your locked into set values.
I know it doesn't get talked about much, but I've always gotten my best results with times_infinity's ComaVolt kernel.
Im looking for the best stability, speed, and battery life
Sent from this EMT's Fassy runnin' ComRom!
OTB 1.5 running great for me.
Personally, the kernel in ComRom works great for me,so that is what I use. As far as other kernels, I have used some versions of otb which was good... but you have to find the right configuration for yourself.
Posted from my Samsung Fantastinate using Voodoo magic
jptech7 said:
Personally, the kernel in ComRom works great for me,so that is what I use. As far as other kernels, I have used some versions of otb which was good... but you have to find the right configuration for yourself.
Posted from my Samsung Fantastinate using Voodoo magic
Click to expand...
Click to collapse
Amen. You could get 1,000 replies on this and you will eventually get recommendations for every available kernel. Everyone's set up is a little different, and there are even differences in each phone as they leave Samsung. The only way you will know for sure what works best on your phone is trial and error on your phone. A lot of people are having great success with OTB 1.5. For some reason on my phone with my set up on Comm ROM 1.3 and any of the OTB kernels, I get sleep of death. I'm using ComaVolt and having no problems. That's just unlucky for me that I can't get the OTB kernels to work.
landshark68 said:
Amen. You could get 1,000 replies on this and you will eventually get recommendations for every available kernel. Everyone's set up is a little different, and there are even differences in each phone as they leave Samsung. The only way you will know for sure what works best on your phone is trial and error on your phone. A lot of people are having great success with OTB 1.5. For some reason on my phone with my set up on Comm ROM 1.3 and any of the OTB kernels, I get sleep of death. I'm using ComaVolt and having no problems. That's just unlucky for me that I can't get the OTB kernels to work.
Click to expand...
Click to collapse
Same for me. Every OTB I tried give me SOD after about a day a half and I tried all sorts of different voltage combos. Comavolt game me SOD after about a day. I'm trying PB&J now to see how that works. I'm starting to think my phone does not like any UV kernels at all. Hopefully I can find a setup that works.
jpricesd said:
Same for me. Every OTB I tried give me SOD after about a day a half and I tried all sorts of different voltage combos. Comavolt game me SOD after about a day. I'm trying PB&J now to see how that works. I'm starting to think my phone does not like any UV kernels at all. Hopefully I can find a setup that works.
Click to expand...
Click to collapse
I have found the OTB kernels the most stable because you can choose to uv them or oc them, but you don't have to.
My own personal experience is that my phone can be uv'd to a point and then it gets flaky. I can nowhere near uv the way some others can... But I can experiment.
My current setup that seems to work best is OTB 1.3 with uv'd at least -50 everywhere and oc'd using 1200 as the limit at stock 1000 voltages. Gets me quick and responsive phone and seems to give great battery life (because most of the time the phone is spent at the lower steps where it's moderately uv'd).
I've tried imnut kernels and keep coming back to the OTB 1.3 (because 1.4 and 1.5 seem to break other things for me). For me, EVERYTHING seems to work on OTB 1.3.... BT, WIFI, everything...
But like others have said, YMMV. Good luck!
Well the -50 mv PB&J kernel is a no go as well it looks like. I got the SOD already. I would really like to UV, but my phone doesn't like it.
Wow. Just switched to peanutbutta jelly whatever -100v. Battery its invincible, and performance shows no lag. Literally my battery has only gone down about 3% in the past few hours with wifi on and light usage.
Try the comavolt kernel. I just flashed it yesterday after replying to this thread and have been running it nonstop since then without issue.
Battery life on comavolt is ASTOUNDING. I mean like shockingly good- on my phone at least.
I tried comavolt and got SOD on that too within a couple of hours.
I went with PnutButta Jelly Time 100, I like it, great battery and stable.
the otb kernels seem to work the best for me.
Sorry if this is already posted around here somewhere, but I found this yesterday and was surprised that I hadn't seen anything here about it:
http://rootzwiki.com/topic/8853-working-sod-fix-from-dalingrin/
I installed the new kernel on both of my TouchPads last night, cleared both caches and fixed permissions, and set my lower CPU speed to 192MHz (from 384MHz to help prevent SoDs previously). I wasn't using SoftLocker, so I can't comment on that.
I haven't had a single SoD yet, and I left one of the TouchPads unplugged overnight to see what the battery drain looked like with the new kernel. I'm pretty sure it drained <1% overnight, and CPU Spy shows that all that time was spent in Deep Sleep.
Obviously this isn't a long-term evaluation, but initial results look promising.
UPDATE: Some folks have reported that applying this kernel breaks sound for them. I know it's happened to some people on alpha 1 and others on alpha 2.1, and I also know it hasn't happened to others (myself included). There's quite a bit of discussion about this on the linked thread, so if it happens to you, please refer to the existing information there.
Just flashed this clearing cache, dalvik and fixing persmission.
No SoD yet but NO SOUND.
I have no sound on my touchpad.
cleaned everything and flashed the fix again but no luck.
Silenus21 said:
Just flashed this clearing cache, dalvik and fixing persmission.
No SoD yet but NO SOUND.
I have no sound on my touchpad.
cleaned everything and flashed the fix again but no luck.
Click to expand...
Click to collapse
I think that may have happened to some other folks on the rootzwiki thread. Read down a bit and see what they say. I believe some of them reflashed CM7 with the new kernel (toward the end of the thread) and that fixed the issue. Worst-case scenario, someone has uploaded a recovery zip with the original kernel so you can roll back.
For what it's worth, neither of my TouchPads lost sound, so it's definitely possible to apply this without that happening.
SCWells72 said:
Sorry if this is already posted around here somewhere, but I found this yesterday and was surprised that I hadn't seen anything here about it:
http://rootzwiki.com/topic/8853-working-sod-fix-from-dalingrin/
I installed the new kernel on both of my TouchPads last night, cleared both caches and fixed permissions, and set my lower CPU speed to 192MHz (from 384MHz to help prevent SoDs previously). I wasn't using SoftLocker, so I can't comment on that.
I haven't had a single SoD yet, and I left one of the TouchPads unplugged overnight to see what the battery drain looked like with the new kernel. I'm pretty sure it drained <1% overnight, and CPU Spy shows that all that time was spent in Deep Sleep.
Obviously this isn't a long-term evaluation, but initial results look promising.
Click to expand...
Click to collapse
I don't think it's been mentioned much because it isn't a common issue anymore, i've never had sod on my touchpad and a lot of people claimed alpha 2 fixed the issue.
Sent from my HP Touchpad using Tapatalk
Alpha 2 definitely didn't fix the SoD issue (otherwise why would Dalingrin have kept working on it?). I think most folks used some combination of SoftLocker and cranking up the minimum clock speed to avoid it, both of which have significant impact on battery life. Hopefully this kernel (or some subsequent iteration if this one doesn't fully address it) will give stability and good battery life, particularly when the device isn't being used.
I've had the SoD on both a1 and a2. Flashed this fix. No SoD yet. Sound is still there too.
Sent from my ERIS using XDA App
according to the rootzwiki thread the fix is not allowing WIFI to go to sleep mode. This was the cause of most SODs.
You'll find in this fix that your WIFI will not turn off during sleep even if you set it to do so.
so after i installed the update it don´t save my "overclock"
i set up 1512 mhz but after reboot it´s gone and back at 1200
any idea for this?
Im not sure if Im the only one. But since Alpha 2 I have yet to see SOD, was there anyone else who saw SOD vanish completely with Alpha 2?
I had one sod with alpha 1 then none with alpha 2. I haven't installed any apps or changed CPU settings it just has never happened to me.
Sent from my HTC Desire HD using Tapatalk
synapses11 said:
Im not sure if Im the only one. But since Alpha 2 I have yet to see SOD, was there anyone else who saw SOD vanish completely with Alpha 2?
Click to expand...
Click to collapse
Not a single SOD here, but i skipped alpha 1.
After playing with it for a while, no SoD, but now I'm having wifi issues. Won't stay connected. Did a restore back. Now no wifi issues, but as soon as it goes to sleep, it wont wake up. Uggh. Can't wait till this gets stable. Getting bored of webos.
Lolento said:
according to the rootzwiki thread the fix is not allowing WIFI to go to sleep mode. This was the cause of most SODs.
You'll find in this fix that your WIFI will not turn off during sleep even if you set it to do so.
Click to expand...
Click to collapse
Sent from my ERIS using XDA App
mouseym said:
Not a single SOD here, but i skipped alpha 1.
Click to expand...
Click to collapse
I get Sod all the time. I put my cpu to 648mhz and it still does it. I even put it up to 1500 min 1700max and it did it. I'll edit this post to see if flashing works. Im charging my touchpad at the moment.
EDIT: flashed. So far no SOD but its a little too soon to tell. We'll see what a few hours does.
Sent from my DROID X2 using xda premium
EDIT: I seem to have all functionality and I have not SODed yet. Looks good so far
Sent from my HP Touchpad using xda premium
mouseym said:
Not a single SOD here, but i skipped alpha 1.
Click to expand...
Click to collapse
Same here, i started on Alpha 2.1
i think the problem is alpha 1 related
im guessing a clean wipe will fix the problem...
I had sod from hell.. I just kept it on the touch stone to keep it awake in between.
This fix worked though. Whole day without death
Sent from my HTC Glacier using Tapatalk
Try No-Frills from Market. He's on here too. No SoD for me. It has some feature that prevents it.
Alpha 2.1 was already out by the time I got my touchpad, only had 2 SOD on it prior to installing this patch and none since. Currently I am using No Frills CPU with 192 min and 1512 max I think. Running great and no other issues to speak of. Sound is working fine and this has not impacted my battery life at all, may even be better.
Op should be updated to state that this kernel breaks sound on alpha1. Make sure you are on alpha2 before flashing.I posted both a revert and a repackaged alpha2 with the fix already applied in the thread on rootz.
Sent from my Sensation using XDA App
cpittman said:
Op should be updated to state that this kernel breaks sound on alpha1. Make sure you are on alpha2 before flashing.I posted both a revert and a repackaged alpha2 with the fix already applied in the thread on rootz.
Sent from my Sensation using XDA App
Click to expand...
Click to collapse
I just updated my original post in this thread with a disclaimer about the sound issue. I think it's also affected some alpha 2/2.1 folks, so basically I'm just making sure folks know about it and know to consult the original thread for information about how to resolve it.
Ya I'm not sure what the common thread is with no sound then. I only experienced it in relation to alpha1.
Sent from my Sensation using XDA App
Hi Guys,
What would ye recommend for the best kernal to put on with AOKP? Guess im looking for battery life rather than hugh performance, although i dont want it to be really laggy.
ricochet69 said:
Hi Guys,
What would ye recommend for the best kernal to put on with AOKP? Guess im looking for battery life rather than hugh performance, although i dont want it to be really laggy.
Click to expand...
Click to collapse
huh??? theres only one kernel that can used for AOKP and if you're using AOKP you're running it. you gotta do some reading up bro. AOKP is an ICS rom. but anyways. even if you weren't running AOKP there's only one kernel developer (pershoot) so far for the galaxy tab 10.1.
You always have the option of using a popcorn kernel. Not sure how that compares to the stock kernel or pershoot's kernel, but since it's really the only other option, I'd say give it a try. Best with melted butter.
I experienced really fast battery drain on pershoot's kernel. I don't have evidence to prove it and at the same time don't want to diss pershoot's work and there is a big chance that I might be wrong but that is what I witnessed.
that's why I stuck with stock based kernel's right now.
slack04 said:
You always have the option of using a popcorn kernel. Not sure how that compares to the stock kernel or pershoot's kernel, but since it's really the only other option, I'd say give it a try. Best with melted butter.
Click to expand...
Click to collapse
The popcorn kernel sucks until rooted and modded by heat.
sorry couldn't help myself like you couldn't.
As far as seriously, it all depends on how you configure and use Pershoots kernel as to if you'll experience lessened battery life enough to be bothered by it.
If you can read this it was sent using my GT-P7510.
task650 said:
huh??? theres only one kernel that can used for AOKP and if you're using AOKP you're running it. you gotta do some reading up bro. AOKP is an ICS rom. but anyways. even if you weren't running AOKP there's only one kernel developer (pershoot) so far for the galaxy tab 10.1.
Click to expand...
Click to collapse
ya man i know its an ICS rom but just flashed it for the galaxy nexus on friends phone and put a different kernal, was just wondering if there was different ones for the Tab. looking at the comments below it seems best to go with the kernal packaged with AOKP was just wondering if there was a better one. Thanks every one for your help.
kernel hero = Preshoot
ricochet69 said:
ya man i know its an ICS rom but just flashed it for the galaxy nexus on friends phone and put a different kernal, was just wondering if there was different ones for the Tab. looking at the comments below it seems best to go with the kernal packaged with AOKP was just wondering if there was a better one. Thanks every one for your help.
Click to expand...
Click to collapse
At this very moment we only have preshoot's ICS kernel available for GT 10.1 since he is the only one involved in kernel development but we would all love to see more developers jumping into the Kernel Wagon!
But sincerely speaking ......... I think preshoot's kernel would give anyone good battery life if they do not have over-clocking on.
davsarus said:
I experienced really fast battery drain on pershoot's kernel. I don't have evidence to prove it and at the same time don't want to diss pershoot's work and there is a big chance that I might be wrong but that is what I witnessed.
that's why I stuck with stock based kernel's right now.
Click to expand...
Click to collapse
Pershoot's ICS kernel or HC?
I always had good battery life with Pershoot's kernel on HC. Actually, not just good - great.
However, so far, CM9 is a poor battery performer. I've got a suspicion why (I think it's the same wifi power management bug I experienced on the Galaxy S II with some firmwares) but I haven't had time to confirm.
If it's not the bug I'm thinking of, it'll be a ***** to debug - high drain despite good deep sleep percentages is really difficult to solve. (Basically, something is failing to power down in deep sleep.)
Maybe more info this weekend when I have time to get a kernel tree synced and building for the 10.1.
I think there were two reasons no other kernel developers have done much with the 10.1:
1) Until Heimdall supports the 10.1, developing kernels for it is a bit of a pain in the ass (Edit: If you have a retail Tab - the I/O Tabs had fastboot...)
2) Pershoot does a damn good job - if it ain't broke, don't fix it. There's only two features I miss that aren't present in the kernel, and they weren't worth the hassle of maintaining my own fork.
Entropy512 said:
Pershoot's ICS kernel or HC?
I always had good battery life with Pershoot's kernel on HC. Actually, not just good - great.
However, so far, CM9 is a poor battery performer. I've got a suspicion why (I think it's the same wifi power management bug I experienced on the Galaxy S II with some firmwares) but I haven't had time to confirm.
If it's not the bug I'm thinking of, it'll be a ***** to debug - high drain despite good deep sleep percentages is really difficult to solve. (Basically, something is failing to power down in deep sleep.)
Maybe more info this weekend when I have time to get a kernel tree synced and building for the 10.1.
I think there were two reasons no other kernel developers have done much with the 10.1:
1) Until Heimdall supports the 10.1, developing kernels for it is a bit of a pain in the ass.
2) Pershoot does a damn good job - if it ain't broke, don't fix it. There's only two features I miss that aren't present in the kernel, and they weren't worth the hassle of maintaining my own fork.
Click to expand...
Click to collapse
i get good with battery life on CM9 (for tab 10.1). especially so with the new wifi module coming.
this is with no sync on (using new module):
45 hours - 93%
with sync on, just a bit less then that.
another person with 3g + wifi always on (using new module), about 14 hours, lost 13%.
pershoot said:
i get good with battery life on CM9 (for tab 10.1). especially so with the new wifi module coming.
this is with no sync on (using new module):
45 hours - 93%
with sync on, just a bit less then that.
another person with 3g + wifi always on (using new module), about 14 hours, lost 13%.
Click to expand...
Click to collapse
New module? Holy crap, I just revisted your sources. I guess ICS doesn't like the legacy BCM4330 module.
That explains a lot...
45 hours to 93% is consistent with what I got with HC. Right now, I'm intermittently (Sometimes life is great, but at some point it behaves like something is not properly powering down in deep sleep and remains that way until reboot - it can take 2-3 days to break in some cases, in others it breaks almost immediately.) getting around 1%/hour standby which is poor for a 7 AH battery on a wifi-only device (esp because I KNOW it used to do much better). I suspected it was wifi power management, but it's apparently not the specific issue I thought it was (even though it has very similar symptoms)... (As I said - I've been so busy I haven't had time to mess with it myself, I was going to this weekend but now it looks like I'll be changing track.)
I just rebuilt, time to flash!
BTW, which remote do you pull Dmitry Schmidt's patches from? Last time I tried to find upstream for that stuff I failed.
pershoot said:
i get good with battery life on CM9 (for tab 10.1). especially so with the new wifi module coming.
this is with no sync on (using new module):
45 hours - 93%
with sync on, just a bit less then that.
another person with 3g + wifi always on (using new module), about 14 hours, lost 13%.
Click to expand...
Click to collapse
You sir, flat out ROCK!
So far, after repo syncing, rebuilding, and flashing last night - the new wifi driver seems to be doing the trick. I'm now seeing battery life consistent with what I used to see on HC. Went to bed at 95% and it's down to 94% now. Previously, I would've lost at least 10% in that period of time.
Of course, it needs a few days to shake out - previously it took as much as 2-3 days before it flaked out, although even pre-flakeout I don't think I ever saw CM9 on the Tab do this well in terms of standby battery.
I spoke too soon, and it turns out I was wrong with my initial guesses as to the nature of the problem. I haven't been as rigorous with the Tab as with my main devices.
It turns out it is exhibiting the same Broadcom bug with frequent wakeups that I777 UCKK6, I9100 XWKK5, and a few Infuse leaks had - See http://forum.xda-developers.com/showthread.php?t=1308030 , it's the first entry in the list there.
It's annoying because it's a combo of system and kernel - on I9100 and I777 it was usually caused by system changes, but sometimes would surface if a kernel developer started mucking around in the BCM4330 driver...
In the attached zip is:
A dmesg dump
A shot of the battery screen (less useful than I thought it was now that the problem is not what I originally thought it was)
A dump of /proc/wakelocks
A Wireshark pcap of the problem - note the protocol 0x886c packets happening at 1 Hz
Hi All,
I am currently running the Paranoid v0.1 Tablet / Hybrid ROM which is based on CM9 and am one of the unlucky people who have been experiencing SOD's since flashing. I flashed the ROM 2 days ago and have experienced 5 SOD's since.
I want to be of help to those of you who may be experiencing these SOD's as well be it on a CM9 Nightly (I had MANY SOD's when I was running a straight CM9 nightly a couple weeks ago) or on the Paranoid or even any AOSP/AOKP ROM and thats why I started this thread.
What I have done thus far to try and fix this is...
- Flashed the newest Modem - LR1 which did not stop the SOD's
- Increased my minimum CPU Frequency from the default 200Mhz to 500Mhz (I was having similar issues running an AOKP ROM on my Galaxy Nexus and if I remember correctly, this was how I got them to stop) Since doing this I have not yet had another SOD and I will post my progress accordingly.
I hope that this thread will be of help to people so please post your own experiences and thoughts and possible solutions and lets find a fix (even a TEMP one) for this annoying little bug.
Brief update...
It has now been 3 hours since I changed my minimum cpu frequency from 200Mhz to 500Mhz and I have not yet suffered another SOD. I will continually update here on this...
Keep your fingers crossed...
LoL @ 500Mhz mini... Start buying spare batteries
Didn't help for me. As far as I can tell there is an error on which a specific finalizer class isn't included in the project. I saw it a while back on another thread in some user's log, but can't find it anymore.
luminouche said:
LoL @ 500Mhz mini... Start buying spare batteries
Click to expand...
Click to collapse
Actually... I have been using the phone under some mid to heavy usage since I switched the minimum cpu frequency (emails, texts, facebook, etc) and I have not noticed much difference in the battery life... I was at about 85% when I changed it which was approx. 4 hours ago and I am now at 77%... Not too bad I dont think...
Besides... Id much rather trade off a bit of battery if I can keep the device from SOD'ing.
alex3305 said:
Didn't help for me. As far as I can tell there is an error on which a specific finalizer class isn't included in the project. I saw it a while back on another thread in some user's log, but can't find it anymore.
Click to expand...
Click to collapse
Hmmmm... Well I have never heard anything quite like that and everyone I have heard from is telling me that these SOD's are just a very RANDOM occurrence and that there really is no known reason they happen. Apparently they happen to some people but not to others.
My reasoning behind increasing the minimum cpu frequency is based on what I have read others write about CM9, Paranoid, AOKP, etc NOT entering into "deep sleep". Again... This seems to happen for some people but not for others and I am assuming that perhaps me (and others experiencing these SOD's) have devices that ARE entering into "deep sleep" mode and that they are sleeping TOO deeply which is why they wont wake up where perhaps the people who are NOT experiencing the SOD's have devices that do not enter "deep sleep" mode at all.
I'm no technical genius or developer or anything but this just makes sense to me and for myself... I have still NOT had another SOD since I increased the minimum cpu speed. (KNOCK ON WOOD)!!!
I don't want to duplicate posts, but I posted in ParanoidAndroid because I got my first SOD today just a few minutes ago when I got home. Here is the post:
http://forum.xda-developers.com/showpost.php?p=26525255&postcount=1327
I uploaded the last_kmsg file to xda as well.
andreww88 said:
I don't want to duplicate posts, but I posted in ParanoidAndroid because I got my first SOD today just a few minutes ago when I got home. Here is the post:
http://forum.xda-developers.com/showpost.php?p=26525255&postcount=1327
I uploaded the last_kmsg file to xda as well.
Click to expand...
Click to collapse
****ty to hear you got an SOD my friend. My SOD's have happened while on Network data AND only once on wifi so I really don't think that the wifi has much to do with it but I may be wrong.
Unfortunately I have no idea what to look for in the last_kmsg file so I hope that someone who knows what it means will be able to understand and give us some insight.
On a brighter note I have still not had an SOD since increasing my min. CPU frequency to 500 MHz... Perhaps give it a whirl yourself if you start getting frequent SOD's starting now...
Sent from my GT-N7000 using xda premium
yiannisthegreek said:
****ty to hear you got an SOD my friend. My SOD's have happened while on Network data AND only once on wifi so I really don't think that the wifi has much to do with it but I may be wrong.
Unfortunately I have no idea what to look for in the last_kmsg file so I hope that someone who knows what it means will be able to understand and give us some insight.
On a brighter note I have still not had an SOD since increasing my min. CPU frequency to 500 MHz... Perhaps give it a whirl yourself if you start getting frequent SOD's starting now...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I might give it a whirl if I do have more than one SOD. But, I turned my wifi back off and on data and no SODs right now. Maybe it was just a rare bird lol. I might try turning on wifi in a few and see if it will duplicate.
andreww88 said:
I might give it a whirl if I do have more than one SOD. But, I turned my wifi back off and on data and no SODs right now. Maybe it was just a rare bird lol. I might try turning on wifi in a few and see if it will duplicate.
Click to expand...
Click to collapse
Keep me and the thread posted man. Lets see if we can get rid of this bug...
I use to get many SOD's while on CM9, and the only thing that permanently stopped it was using an app called wakelock. It basically didnt let the phone go into deep sleep mode, avoiding the problem entirely. Also battey life was not badly effected. Standby used almost double battery but my phone lasted the entire day regardless.
However, since I do believe its a kernel problem, I think we should get a fix in the near future since the iCS kernel sources have been released by samsung. So maybe some dev will be able to build a proper kernel for these roms which is not effected by the bug.
Well, I have been on data all night and not a single SOD......
The only time I got it was when I turned on the wifi. I haven't tried turning wifi back on now.
I've been using various updates of CM9 since v7, and have had at most 5 SODs in the past few weeks. Only 1 happened while I was using the phone. The only consistent thing about those experiences was that none of them were while the phone was charging.
Setting to 500 min didnt help me.
My phone has been perfect all night running from mains electricity. Within 2 hours of running on battery SOD.
Last KMSG
My List of installed APPS
I don't think it's ROM related. I've had SOD's on most ICS ROMs. Some get it, some don't. So it has to be the way some setup their device and choice of software installed.
Some suggested tests:
1. Uninstall any type of battery optimizer or WIFI switcher
2. Factory reset, and run the ROM for a day without any additional software to see if you get SODs
3, Disable WIFI for a day and see if you get SODs
4. Set WIFI to be on all the time and see if it helps.
5. If all SOD sufferers can dump the list of installed software and see what stuff is in common.
In my case, it was Green Power (other battery optimizers gave the same results) to control WIFI/Data, Once removed over a month ago, SOD's stopped.
Hope this helps.
tamarian said:
I don't think it's ROM related. I've had SOD's on most ICS ROMs. Some get it, some don't. So it has to be the way some setup their device and choice of software installed.
Some suggested tests:
1. Uninstall any type of battery optimizer or WIFI switcher
2. Factory reset, and run the ROM for a day without any additional software to see if you get SODs
3, Disable WIFI for a day and see if you get SODs
4. Set WIFI to be on all the time and see if it helps.
5. If all SOD sufferers can dump the list of installed software and see what stuff is in common.
In my case, it was Green Power (other battery optimizers gave the same results) to control WIFI/Data, Once removed over a month ago, SOD's stopped.
Hope this helps.
Click to expand...
Click to collapse
Not true. I tested a clean CM9 install with 0 apps installed. All I did was link it to my google account. Still had SOD. Wifi turned off all the time. Data connection H+ acticated all the time. As stated before I had exactly the same SOD on imilkas LP1 kernel. When he moved source to LP5 kernel the SODs vanished. So a change in those kernels fixed the SOD.
I have now enabled the smartassv2 CPU gov in CM9. Lets see what happens now. I aint got nothing to lose
Oh and I set a digit password to unlock my phone. Wonder if that has anything to do with it as I have never tested CM9 without a password.
From this morning. Running 24 Nightly with loud speaker fix
Flashing ZCLP1 solved this issue on PA 0.1
I flashed ZCLP1 modem version and I am not getting any SOD's.
off topic
ahh
since you are on CM9 you can always go back to Stock GB
would not that solve the problem ... ?
ahmad zuman said:
ahh
since you are on CM9 you can always go back to Stock GB
would not that solve the problem ... ?
Click to expand...
Click to collapse
I suppose, but that's not worth the price...