I'm semi-back after my weekend, but totally sleep deprived...
Do the SOD`s mainly occur as a result of changing the storage location (tick/untick) in settings?
That seems to be a major cause - it would be why there has been a major spike in SoDs since the storage switch happened. It seems to be:
1) Some people had SoDs with the old wifi driver - not surprising, the old I9100 Update4 wifi driver was ****. Most of these people had them disappear when we went to the N7000 wifi driver/MMC driver.
2) A bunch of people were SoD free until the storage switch - nearly everyone who saw a spike in SoDs after 6/3 have had them go away if they did a wipe/factory reset. My guess is they had some app that was misbehaving.
3) A very small number of people are still having frequent SoDs. I have no idea why.
Can anyone recommend a good alternative to all share? Unless its possible to get all share running on cm9?
Sent from my GT-N7000 using xda premium
Skifta. Skifta rocks. REMEMBER though: Use "Exit" from the menu instead of exiting with Home/Back, as it will hold a wakelock if you don't exit it from the menu.
You might see some clues by looking at dmesg output.
I had a corrupt /system a while ago, and it exhibited the same symptoms, or at least I could not do a "mount -o remount,rw /system". Back then, /system was mounted by recovery, and would not unmount, so had to revert to a GB+CWM kernel/recovery via odin, then booted CWM recovery, then CM install, then partial recovery of latest nandroid. Hopefully you can avoid the last component.
Entropy512 introduced a recent patch where /system is not mounted by recovery by default, allowing it to be wiped from recovery if corrupt. I would exercise this option, probably wiping cache too, and reinstall your current version of CM9, which should preserve your data partition.
If you have partially damadged flash, then I expect things will recur, and possibly get worse, but hopefully that is not the case.
Yup, their description sounded just like /system got corrupted. Some people falsely calling it "lost partial root" - even though the fact is that recovery ALWAYS runs with root privileges, it CANNOT "lose root" unless one of the devs makes a stupid epic mistake.
I `am experencing one SOD a day so far, a bit annoying but i can live with it. Running 09062012, stock kernel, no mods and facing no other issues.
I hope the devs in the future will also add the 1600 Mhz clockspeed option in performance settings.
I eventually might do this, but resolving the last few stability issues takes priority.
Can the development please provide us with some information with these SODs please? And try to fix it or tell us how we can remedy this situation? I've done every possible situation to resolve it. I've formatted both the external and internal storages, taken out the external SD card before flashing the nightly again, complete wipes, and even went back to gb first then flashed cm9 nightly, with every different combinations mentioned above. Still facing SODs and getting very annoying now. I don't know why you would recommend using wake lock because that doesn't resolve the issue, and drains battery. Development need to work on this, and atleast provide us with some information
Sent from my GT-N7000 using xda premium
We've provided all of the information we know. I even provided as much detail as I could about the device configuration I run (installed apps, modem, a few other settings) which is SoD-free for me. The storage switch caused SoDs to spike for some people - those who had SoDs start with the 6/3/2012 nightly that didn't have them before all seem to be OK after wiping.
Some people had SoDs due to the old wifi driver which sucked ass. It was the only SoD I've ever had that wasn't attributable to RCU stalls.
Beyond that - if anyone who has done a wipe is STILL plagued with SoDs, I have no clue why. The problem is that XplodWILD and I *cannot reproduce the problem* - both of our devices are *rock solid stable* - I haven't even had an RCU stall SoD in 2-3 weeks.
One or two people mentioned using some sort of timer app causing SoDs for them - so I'll try using Alarm Clock Plus on my Note in addition to my Tab 10.1 for a few days to see if it makes a difference and causes any issues.
Beyond that, we're basically shooting in the dark as far as attempts to fix this. The fact that it is not a traditional SoD (where the device enters suspend and never comes back) but a somewhat different one (device enters suspend and then resumes into la-la-land) makes it really difficult to debug - because in 90% of the logs people have posted, activity after the trigger event has caused all of the information about the event itself to get dropped from the log.
Right now the only things I can think of are to try and pull the GPIO configurations in from the N7000 sources - they looked identical (just formatted/reordered differently) on first review, but there might be a change hidden in there.
Beyond providing a complete summary of my personal configuration ( a few pages back) including what apps I'm running, which modem I'm running, even my SetCPU settings (which actually might cause SoDs for some people, so be wary of those), there's little more I can do than randomly try and pull stuff in from the N7000 release and hope it fixes the few people who are still having issues.
I've never recommended wake lock myself - it's a poor workaround. Neither has xplodwild or any other developer.
Right now, and these are wild guesses:
If you use any app that automatically enables/disables wifi, don't. Leave wifi on, it uses less power for background syncing than mobile data anyway.
Similarly, set "Keep wifi on during sleep" to "Always"
This is about the only thing I can think of that wasn't in my post a page or two back with my full configuration info. With the above wifi settings, I get around 0.5%/hour battery drain when connected to a wifi network at home and no SoDs for 2-3 weeks.
And obviously - dealing with the fact that our device has defective flash memory that can suffer damage which is currently unrecoverable by anyone outside of Samsung has taken priority.
After using CM9 pretty much since its release, I've gotten my first ever SoD's this week. After testomg, I've found I ONLY get them when using custom governors such as smartassv2, pegasusq and lulzactive - ondemand and the other stock ones run just fine.
Just my 2¢.
Sent from my GT-N7000 using xda premium
Custom kernels are not supported here. pegasusq is not included in the kernel (it's quadcore-optimized), lulzactive will never be included because tegrak loves to violate the GPL, and smartassv2 is included as a module for a reason - putting it in and not using it causes all sorts of stability problems. Therefore you are clearly using a custom kernel.
As to today's nightly bombing in Jenkins - if it happens again I'll take a look at it. The error was REALLY weird and makes me suspect Jenkins glitched out. (Especially since the Note tree itself hasn't been touched in 2-3 days due to me being out of town.)
(A donation in your name to the CM9 devs?)
