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
Related
When I upgrade to ICS, my tablet exhibited all issues everyone was complaining about.
1) Battery drain. - the culprit of this issue is GPS. The GPS was preventing tablet from going into deep sleep. I have disabled GPS but kept Google location service enabled and that fixed the deep sleep issue. Also there were some incomparable software which prevented deep sleep. XDA app was one of them.
2) Random reboots, shutdowns, and lag. - the culprit of these issues is software incompatible. All you have to do is perform full wipe and cold boot using recovery by pressing and holding power and volume down buttons. After reset, all issues are gone.
To troubleshoot use next tools.
1) CPUSpy - it will show of tablet goes into deep sleep.
2)Battery settings in the rom's system setting is helpful to see if the phone sleeps but will not show if it deep sleep.
3) BetterBatteryStates is very useful to see which process keeps tablet awake.
Sent from my SGH-T959 using XDA
If it were that easy Asus wouldn't be working on a fix to push out to us. They have already confirmed there are issues.
My tablet didn't exhibit any of the reboot issues up until a few days ago. Which means even though your "solution " has seemed to help so far it could end up happening again later on
Sent from my Transformer TF101 using xda premium
I have been running for 1d and 20 hours using tablet and still have 60% left. No reboots no lag runs smooth. Also there is an issue with GPS which keeps tablet from going into deep sleep and that is what Asus is working on. If you disable GPS and remove xda app that will solve your battery issue. Also xda might have fixed their app since then. Full wipe will fix other issues.
Sent from my SGH-T959 using XDA
I understand and believe you. I'm saying that the amount of time you have without any issues is not long enough to be 100% certain all issues are gone.
That is why I stated that's I had NONE of the issues for a couple weeks then out of nowhere they started.
Tho I hope your solution works in the long run and helps others as well
Sent from my Transformer TF101 using xda premium
I am just sharing my findings. I think GPS is the biggest contributed. Just disable it and see how the tablet runs.
Sent from my SGH-T959 using XDA
If a full wipe was the solution, then you will not find so many threads about the reboot or other issues.
it is just pure luck, some did all the steps of full wipe, full reset, go to stock HC then stock ICS, in all ways some keep getting issues and some do not have any.....
and as it has been already mentioned above, the issues have been confirmed by asus and they are already working on a solution.
mveksler said:
When I upgrade to ICS, my tablet exhibited all issues everyone was complaining about.
1) Battery drain. - the culprit of this issue is GPS. The GPS was preventing tablet from going into deep sleep. I have disabled GPS but kept Google location service enabled and that fixed the deep sleep issue. Also there were some incomparable software which prevented deep sleep. XDA app was one of them.
2) Random reboots, shutdowns, and lag. - the culprit of these issues is software incompatible. All you have to do is perform full wipe and cold boot using recovery by pressing and holding power and volume down buttons. After reset, all issues are gone.
To troubleshoot use next tools.
1) CPUSpy - it will show of tablet goes into deep sleep.
2)Battery settings in the rom's system setting is helpful to see if the phone sleeps but will not show if it deep sleep.
3) BetterBatteryStates is very useful to see which process keeps tablet awake.
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
My experience: I've done a full wipe, installed few apps from scratch (no restore), disabled GPS and installed autoairplane app. Everything seemed ok, two days and one night in deep sleep with 8% of battery drain per day. The following morning the tablet was switched off with 0% of battery
Great that you have resolved the issues for your TF101 and thanks for sharing the steps you took you to get that far.
It's only a limited set of devices though (1) and a limited amount of time.
I still believe most TF101 ICS issues are related to drivers. Just like it was initially with the first Asus HC release. Updates will improve stability.
the culprit of these issues is software incompatible.
Click to expand...
Click to collapse
I agree, this is just a poor choice of words..and with the title of the thread, you are really just ginning up controversy here now as a thread of this nature has already been closed because of someone insisting that a full wipe solves reboot issues..I would have phrased it more scientifically correct by saying 'the culprit seemed to be software incompatibility', you could even throw in the obligatory 'to me' lol. When you state things with such certainty in a development and electronics forum where terminology and phrasing is very important you are misleading people (noobs and lurkers) who are then going to complain and whine about being misled (and possibly mess up their device in some cases). Safer to state your 'findings' in less certain terms IMO.
And as I already pointed out in another thread, in order to say anything equivocally about a solution to a common problem like random reboots you need to have tested and confirmed the proposed solution on tens and hundreds of units, which very few of us have access to to test with any clarity of results. So anyone *should* take users' proposed solutions with a grain of salt barring they are employed with Asus or Best Buy and could have done such testing. Other users have proposed build.prop fixes for example, only to realize they had reboots and didn't even notice. 1 day is not long n this timeframe- I have one once a week tops..but I still have them..lol
The only problem i had was the apps disappearing from the launcher whenever i exited an app. I thought i solved this by installing a new launcher. But it returned after a few days. I did a full wipe and installed apps from scratch. since then my tablet has been running smooth and fast. no issues. May be it's the apps we install that are causing the problems.
Sent from my Transformer TF101 using Tapatalk
I think it is the graphics acceleration driver. Many games are not working to me, they just exist to launcher and in logcat i can see SIGSERVs because of openGL ( this is from memory, I don't have my tablet here right now).
We must wait until ASUS releases a fix.
I'll come in with another just wait and see like other folks have said. I did my ICS update with a full wipe and then only installed apps I felt comfortable with instead of just doing a full reinstall of everything. For days life seemed grand with everything working just right. Then I got a few reboots and now the constant media converter dying message. So be happy things are working well for you but be prepared for the errors to creep in.
Sent from my HTC Flyer P512 using Xparent Purple Tapatalk
I suffered from random reboots. Whenever my device went to deep sleep it could not come out of it. What I did to remedy this is to root and install set cpu. After installation, i changed my minimum freq to 312mhz and my max at 1ghz. So far, for about a week, i have not suffered any random reboots/freezes. Also, using cpu spy, it does go to deep sleep. I hope this helps.
mveksler said:
1) Battery drain. - the culprit of this issue is GPS. The GPS was preventing tablet from going into deep sleep. I have disabled GPS but kept Google location service enabled and that fixed the deep sleep issue. Also there were some incomparable software which prevented deep sleep. XDA app was one of them.
Click to expand...
Click to collapse
No idea if you're right, but I can't be bothered to try, because...
mveksler said:
2) Random reboots, shutdowns, and lag. - the culprit of these issues is software incompatible. All you have to do is perform full wipe and cold boot using recovery by pressing and holding power and volume down buttons. After reset, all issues are gone.
Click to expand...
Click to collapse
You are *definitely* wrong on this one. There are numerous documented accounts of people having this problem even on stock, unrooted TF101 tablets that have been wiped both before and after the ICS update was applied, and have nothing or next-to-nothing reinstalled. I'm one such person.
A full wipe most definitely does NOT fix or prevent these problems.
knoxploration said:
A full wipe most definitely does NOT fix or prevent these problems.
Click to expand...
Click to collapse
It did for the OP and a vast number of other users. Doesn't work for everyone but it is a viable solution.
I originally suffered from horrible battery life after updating to ICS, but I took a page from the book of the Gnex when it comes to sudden horrible battery life. One of the biggest problems on the GNex with sudden battery drain a lot of the times had to do with Google Maps. I used CPU Spy and Better Battery Stats and sure enough, Google Maps was constantly running in the background, putting the tablet into a wakelock and most likely running the GPS. The tablet wouldn't even last half the day WITH the dock. Went to apps, uninstalled updates and reinstalled the most recent version and since then the battery life has been PHENOMENAL! I've got the tablet with dock and it'll go most of the week, if not all week before the dock starts running low.
Hope this helps others. Can't guarantee it'll fix your problems but it fixed mine.
Speaker Issues after ICS update
Has anyone else had any speaker issues after the ICS update?
Jai1985 said:
Has anyone else had any speaker issues after the ICS update?
Click to expand...
Click to collapse
My volume is low, also been experienced by others. And it seems like left speaker is lower in volume, which I also read issues with. So yea. I have a couple little quirks. Good thing is I don't really use it for music or movies so not huge deal to me
Sent from my SGH-T959 using xda premium
ghost0001 said:
I suffered from random reboots. Whenever my device went to deep sleep it could not come out of it. What I did to remedy this is to root and install set cpu. After installation, i changed my minimum freq to 312mhz and my max at 1ghz. So far, for about a week, i have not suffered any random reboots/freezes. Also, using cpu spy, it does go to deep sleep. I hope this helps.
Click to expand...
Click to collapse
This has been my fix from the start and have only had one self-inflicted random reboot and (Horndroid here is a nod for you) another reboot after I updated Google+. I reverted back to previous G+ build and all is back that way it was before.
If you'd like to read more about the kernel issue and how I solved it for myself, see here.
Since i upgraded to ICS my note randomly shuts itself down to the point I have to longpress the on/Off button tot boot It up again.. there's no sign of low battery after rebooting ...
Very annoying if you're counting on your alarm clock in the morning to get to work in time
I recently flashed stunner 5.0 and am very pleased with this rom.. I dunno if it's stunner-related or not..
Anyone else experiencing this?
Sent from my fabulous GT-N7000 using xda premium
User error, start fresh from gb.
Sent from my GT-N7000 using xda premium
I completely restarted from stock GB before rooting again / flashing ics.. did it twice already .. so I don't think it'll work if I try it a third time...
Nicosch said:
Since i upgraded to ICS my note randomly shuts itself down to the point I have to longpress the on/Off button tot boot It up again.. there's no sign of low battery after rebooting ...
Very annoying if you're counting on your alarm clock in the morning to get to work in time
I recently flashed stunner 5.0 and am very pleased with this rom.. I dunno if it's stunner-related or not..
Anyone else experiencing this?
Sent from my fabulous GT-N7000 using xda premium
Click to expand...
Click to collapse
Sounds like an SOD. It is very common with ICS Roms and currently there isn't really a proper fix for it. Essentially, your phone is still on, but its screen won't come back on until you reboot/pull battery. Look up SOD or screen of death or some other combination to search for tips on how to improve its reliability
Flash basband lp6 that will fix your sods
Yeah its weird prior to lp5/6 release I had nothing but sod. But with new ics leak I haven't had any sod with stock or custom roms and I think majority of the community hasn't had many if any like the old leaks.
Which apps are you installing? Are you restoring backup data from titanium backup or similar.
Sent from my GT-N7000 using xda premium
Yep.. restoring like 170 apps using titanium backup ... including user data ... could that be the cause?
Sent from my GT-N7000 using xda premium
brockyneo said:
Flash basband lp6 that will fix your sods
Click to expand...
Click to collapse
Baseband = modem ? Right.. ?
Any idea where to get only LP6 modem ?
I suppose I have to flash it using mobile Odin?
Thnx in advance ..
Sent from my GT-N7000 using xda premium
Nicosch said:
Baseband = modem ? Right.. ?
Any idea where to get only LP6 modem ?
I suppose I have to flash it using mobile Odin?
Thnx in advance ..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Here you go mate flash via cwm http://www.mediafire.com/?zuicr1120j54vx9
Do wipes too before just to be on safe side
the restoring apps could be the issue also. Remember that stunner rom, has alot of built in root apps that cover setting up the cpu and such. If the modem doesnt fix it I would suggest starting over fresh with your apps, and seeing if your problem goes away.
Flashed modem.. and my note seems to have survived the night ..
If I get a sod today .. I'll restart from stock later this evening, and manually restore my apps and/or userdata..
Thnx for the advice
Sent from my GT-N7000 using xda premium
One hour and fifteen minute later and had my first sod on LP6..
Sent from my GT-N7000 using xda premium
Seems like CPU governors like setcpu and 2nd core combined with energy saving apps tend to mess things up.. removed them all and flashed baseband radio LP6..
Now running a few hours without SOD's..
Keeping my fingers crossed
Sent from my GT-N7000 using xda premium
i would reccomend Stunner 0.5
just for its power saving options you can control 3g data and Wifi at any time to be turned off automaticly so it saves battery though ROM is quite kind with power, anyway install it clean and then just with any CPU managing application set the settings of CPU to 1400 MAX - 200 MIN and ONDEMAND so it doesn't run constantly on full power and then add a profile for Screen Off and set it to 200 MAX- 200 MIN aply at boot of course checked good luck
I've had SoD's and reboots on imilka's CM9v2 and Stunner 5 beta so when Stunner released 1.4.19 I started completely fresh. I reflashed the LP1 repack with wipe, did another full wipe in CWMR before flashing Stunner 1.4.19, flashed the LP6 modem and did another full wipe. I've been using it for about 20 hours, 14 hours since my last manual reboot and I haven't had a problem yet.
Just flashed the new Stunner 1.4.19 this morning over my existing 5.0 version..
And have not had one SOD since..
Let's hope it stays that way..
I think ics is to early in this stage to restore apps with userdata. Im not talking about xda app, slacker or things of that nature. But restoring things like setcpu, rootexplorer and other root apps could lead into problems. Unless you are very strict about backups.
Happy you got your problem situated.
Hey guys, lucky I found this thread.
I followed this guide as literally as I could: http://forum.xda-developers.com/showthread.php?t=1763151
But as far as I can tell I am, too, getting a screen of death every now and then. For example, I went to bed last night and left my phone with 70% battery, this morning, 8 hours later, I found it with 22%. When I checked the battery graph (I would post a SS but I cant use the stylus for that and dont know any apps for the job ATM) I found a "gap" between 70% and 22%, its like nothing was there. So Im tempted to believe that it is, in fact, a SoD.
I've read the experiences of this previous user but I cant really figure out what it is im supposed to do to fix my note. I am using CM9 (latest nightly) and would like to continue doing so, is there a way for me to fix the SoD without changing roms?? I am not a m4d h4xx0r on this subjet, but I manage and I can follow a clearly laid out guide as good as anyone.
I would hate to waste your time, so if you could please be extra clear when explaining whatever procedure I must follow it would be awesome.
If anyone could help me out on this subject you would have my humble thanks!
Galaxy Note 2 shuts off
The issue exists on the Galaxy Note 2 as well and has nothing to do with software.
The problem is hardware related. The phone is flawed and shuts off on it's own under various conditions, all hardware related. Take a look at this video: http://www.youtube.com/watch?v=SjLn2yikYnI
Also, take a look at this site I built that goes in to more detail regarding the issue: www.GalaxyNote2ShutsOff.com
One look at that short video and I am sure there will be some light bulbs going off. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.
swaldrop said:
The issue exists on the Galaxy Note 2 as well and has nothing to do with software.
The problem is hardware related. The phone is flawed and shuts off on it's own under various conditions, all hardware related. Take a look at this video: http://www.youtube.com/watch?v=SjLn2yikYnI
Also, take a look at this site I built that goes in to more detail regarding the issue: www.GalaxyNote2ShutsOff.com
One look at that short video and I am sure there will be some light bulbs going off. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.
Click to expand...
Click to collapse
Well Thank you for REVIVING THREADS that are LIGHTYEARS away from now.........revive it? Really? Every thread that says shut down?
<<<The CRACKS on my NOTE shows how often it KISSES the FLOOR>>>
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...
Apologies if this is covered elsewhere, but I have been struggling to trawl through all 1000 pages on the relevant thread as I can't get the search terms to get the info!
Basically, when I leave the phone overnight charging, in the morning I cannot turn it on unless I press and hold the power button and volume down to reset the device.
Other than this it is great in terms of being able to adjust the colours and the battery life seems better.
I have tried both the nightly and stable versions..
What ROM are you using?
Sent from my Nexus 4 using xda premium
murtezahu said:
What ROM are you using?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I am currently using the stock ROM but could change to a custom... (I am learning as I go at the moment...)
Sounds like your phone is having trouble to wake after a deep sleep. I'm guessing it's caused by a (probably: too) low cpu frequency.
Did you use any app to change the cpu frequencies while asleep, or did you undervolt your cpu?
Also, which version of the kernel are you using? I suggest you stick to M1 for more stable results.
And after all, it might be a bug in the kernel. The people in franco's thread are more than willing to help you if you supply as much information as you possibly can. Kernel version, your adjustments to it if any, etc. I haven't seen this problem happen to anyone before in the last days (oh yea, I read every page of that thread...), so don't be afraid to ask for some help. But for now, I suggest you update to M1. If you're already on M1, feel free to ask your question in the thread.
LOL
Sent from my Nexus 4 using xda premium
sounds like a classical case of sod. do you undervolt?
and rolmply
simms22 said:
sounds like a classical case of sod. do you undervolt?
Click to expand...
Click to collapse
No, I do not undervolt. The only changes I made were to gamma settings. Having said that I did change the power setting but changed it back. I have rebooted the phone so I will see if it happens after the next deep sleep.
Thanks for the help so far, much appreciated!
vindikleuk said:
Sounds like your phone is having trouble to wake after a deep sleep. I'm guessing it's caused by a (probably: too) low cpu frequency.
Did you use any app to change the cpu frequencies while asleep, or did you undervolt your cpu?
Also, which version of the kernel are you using? I suggest you stick to M1 for more stable results.
And after all, it might be a bug in the kernel. The people in franco's thread are more than willing to help you if you supply as much information as you possibly can. Kernel version, your adjustments to it if any, etc. I haven't seen this problem happen to anyone before in the last days (oh yea, I read every page of that thread...), so don't be afraid to ask for some help. But for now, I suggest you update to M1. If you're already on M1, feel free to ask your question in the thread.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently using milestone 1.
As far as I am aware I only made changes to the colour as I am still learning the controls as I go. I have restarted the phone to see if it helps.
The only app that I am using that could be to blame is battery guru, so if it persists, I could try disabling that.
goldeneye243 said:
No, I do not undervolt. The only changes I made were to gamma settings. Having said that I did change the power setting but changed it back. I have rebooted the phone so I will see if it happens after the next deep sleep.
Thanks for the help so far, much appreciated!
Click to expand...
Click to collapse
do you use the pgm slide to wake app?
simms22 said:
do you use the pgm slide to wake app?
Click to expand...
Click to collapse
No, I don't - Should I, or is it possibly what is could have caused the problem?
goldeneye243 said:
No, I don't - Should I, or is it possibly what is could have caused the problem?
Click to expand...
Click to collapse
its a possible cause of sod if you had it installed.
goldeneye243 said:
Thanks for the reply.
I am currently using milestone 1.
As far as I am aware I only made changes to the colour as I am still learning the controls as I go. I have restarted the phone to see if it helps.
The only app that I am using that could be to blame is battery guru, so if it persists, I could try disabling that.
Click to expand...
Click to collapse
You're using the exact same set-up I am, and I'm haven't had any of the trouble you talk of. Disabling battery guru might be a good idea. As it's an app from Qualcomm itself, I wouldn't be surprised if it's set to mess around with the stock kernel's settings. If that's the case, then your kernel is obviously not the kernel that Battery Guru was programmed to mess with! Uninstalling it to see what happens next would be a good step :highfive:. From my experience, you wouldn't need any battery management apps when you're on franco's M1 anyway - using common sense to save your battery should suffice.
vindikleuk said:
You're using the exact same set-up I am, and I'm haven't had any of the trouble you talk of. Disabling battery guru might be a good idea. As it's an app from Qualcomm itself, I wouldn't be surprised if it's set to mess around with the stock kernel's settings. If that's the case, then your kernel is obviously not the kernel that Battery Guru was programmed to mess with! Uninstalling it to see what happens next would be a good step :highfive:.
Click to expand...
Click to collapse
I will do that if I have not already got it fixed with the reboot. Battery guru is still in learning mode so possibly isn't messing with the kernel yet but is the next thing to try...
Alrighty, let's hope it'll get figured out.
vindikleuk said:
Alrighty, let's hope it'll get figured out.
Click to expand...
Click to collapse
Well, it turned on OK this morning, so hopefully fixed...
I guess I will only know in a few days time when I have got more confidence...
I had another SOD so I have reset all settings (installed nightly version 110) and started again -
The only changes I have made are to the gamma settings and changing the governer to conservative to see if that gives me a longer battery life.
Will see how it goes....
I had some more SODs with 110/111 so I changed to 121 and the battery life did not seem as good.
Takes a while to work out what is going on when it only happens once a day...
I still get occasional SODs with battery guru disabled so i guess it is either the kernel or possibly the ROM... I will try on the support thread....
So, I've been running the Milestone release of AOKP for a while and while it's been generally stable, I seem to be having an an issue with reboots when I don't use the tablet for a while. Maybe.
Once maybe every few days, if it's been sitting for a while (or charging), when I unlock, all of my recent apps have been cleared. The stock battery info doesn't indicate any downtime, but GSAM battery monitor will indicate a reboot.
I've seen this on both KToon and Franco's most recent kernels.
Anybody else? Any ideas?
Thanks!
Sent from my Nexus 10 using xda app-developers app
calbruc said:
So, I've been running the Milestone release of AOKP for a while and while it's been generally stable, I seem to be having an an issue with reboots when I don't use the tablet for a while. Maybe.
Once maybe every few days, if it's been sitting for a while (or charging), when I unlock, all of my recent apps have been cleared. The stock battery info doesn't indicate any downtime, but GSAM battery monitor will indicate a reboot.
I've seen this on both KToon and Franco's most recent kernels.
Anybody else? Any ideas?
Thanks!
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
My aokp+franco also falls asleep and I nave to reboot. It's annoying, I'm going to change ROM. I'd like to know if it is related to the ROM or the kernel though.
I'd guess OP is seeing 'surface flinger RAM shell reboot' that's talked about often.
I'd guess europizza has a unit that is having a battery/motherboard/"power" related issue.
Why? - Based on reading these and other N10 help forums for the last 6 months.
europizza said:
My aokp+franco also falls asleep and I nave to reboot. It's annoying, I'm going to change ROM. I'd like to know if it is related to the ROM or the kernel though.
Click to expand...
Click to collapse
While I have had the SOD with AOKP and Franco/KToon kernels, what I'm talking about isn't the tablet not waking up. It's that it's rebooting while charging or not being used for extended periods of time. (But I haven't had any SOD issues with the latest version of either of those kernels, btw.)
bigmatty said:
I'd guess OP is seeing 'surface flinger RAM shell reboot' that's talked about often.
I'd guess calbruc has a unit that is having a battery/motherboard/"power" related issue.
Why? - Based on reading these and other N10 help forums for the last 6 months.
Click to expand...
Click to collapse
Ah, thanks. I've seen talk of this surface flinger business before, but never really knew what it was referring to. Haven't researched it much yet, but it sounds like something I'll just have to deal with for now.
Thanks again.
Sent from my Nexus 10 using xda app-developers app