hi guys
For those that haven't heard of or seen an Sleep of Death (SoD) in action , it is where your phone does not respond to any user input whilst it's in sleep mode thus making the phone unusable since you are unable to wake the phone. The only way to recover is to either force reboot the phone, receive a call or call yourself from another phone.
I have encountered SoD four times til now, on KE2, KE7 and Now KF2 .
I don't think its got anything to do with the ROM, this has happened for me on Cognition, VillainRom , CF-root on stock Roms.
looking around the web it seems it might be a kernel/driver issue and remains unfixed (not sure)?
Anyone knows workarounds? Any Devs that are working on this?
Thanks
I haven't encountered this yet and I've also tried a bunch of different ROMs. Are you by chance overclocking or underclovking/UVing at all? If so, that could be the culprit. If not, then its hardto say what may be causing it other than an app the phone may not respond well with.
I had this happen once. I tried many ways to wake it up even charging, the charging sound comes up but the screen wont wake. Had to reboot.
Havent happened again though.
I haven't under/over clocked the CPU at all but from what I understand it has nothing to do with CPU frequency but more so a bug in kernel or in one of the drivers.
Its not easy to reproduce but its definitely there, I'm hoping it'll be addressed in cyanogen rom when its out given the fixed SoD somewhere in 7.0rc I think.
Sent from my GT-I9100 using XDA Premium App
ke3pup said:
I haven't under/over clocked the CPU at all but from what I understand it has nothing to do with CPU frequency but more so a bug in kernel or in one of the drivers.
Its not easy to reproduce but its definitely there, I'm hoping it'll be addressed in cyanogen rom when its out given the fixed SoD somewhere in 7.0rc I think.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
On my ace this issue occured when the wifi was on. The phone goes into "sleep mode" and needs a reboot (press the power key for 10 seconds).
I was not able to find the exact conditions but it was more promient when 3g was also switched on.
Does your issue occur only when the wifi is on?
This has happened 4-5 to me
as well. I have found that a putting the phone on charge can free it. But its a real pain if it happens out and about, I had to take the battery out to get it to work
i got it 2-3 times while using "Green Power" app.
Again this has nothing to do with an app/rom..etc. you may think a certain app you installed its causing it but in case of SoD that's highly unlikely. The source of problem is else where.
"@cyanogen: @Bradart @1000hams try a nightly build if you are on 7.0. Google fixed bugs for 2.3.4 that can cause that (7.0 is 2.3.3)."
Click to expand...
Click to collapse
The above is a quote in response to SoD question (don't know which device, but android < 2.3.4) which to me suggests another bug in 2.3.3 that has been fixed in 2.3.4.
http://forum.xda-developers.com/showthread.php?t=1238478
Here's the solution I hope it helps... it worked for me
Bug Report - SGS2 (Sleep of Death)
Please use this link to report the bug:
code.google.com/p/android/issues/detail?id=21607&thanks=21607&ts=1320690472
I think I found a way to avoid SoD (Sleep of Death)
I'm new on the forum And that SoD problem annoyed me for so long and I kept searching.... But I think I finally found why we kept getting SoD.
Ok so I'M NOT SURE, but Try following those steps and be sure of every single thing and then tell me if you guys keep getting SoDs..
1- "Do not use two governors as screen-on & screen-off govs, if they both have an upper frequency limit for screen-off state." - droidphile
2- I think some of us don't do "clean flash of our ROM", so you guys need to follow those exact steps from that link
http://forum.xda-developers.com/showpost.php?p=28395322&postcount=3
Or I will just write them again...
1- Reboot into recovery (Turn off your phone then press and hold the keys: Volume Up + Power + Home)
2- Wipe Data / Factory Reset
3- Install the Main ROM file
4- In AROMA installer select "Custom Installation"
5- Choose depending of your taste
6- When AROMA installer finish untick the "Reboot Now" option
7- When you're back on the recovery go to Advanced
8- Wipe Dalvik Cache
9- Fix Permissions
10- Wipe Cache Partition
11- Reboot
12- When you get the step for add your Google Account, if you don't have a WiFi enabled or you can' add it, skip it
13- When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot the phone
14- When you boot again into the system, the data will be enabled and you can do the configuration of Google Account (if you don't do this step before)
This is the moment for install all the extras like themes, mods, fixes, kernels, etc.
3- ok and NOW After your "CLEAN Flash of ROM" When you use Titanium backup Root application to restore your applications, DONT restore the things with RED text color. Restore ONLY the things with green text color.
In other words, restore only apps with their data and NOT all system data.
4- Ok and Once you did that. About the Governor you use, I think we push the limits of the CPU and the phone just can't resist the tweaks we did and a SoD appears. So try these settings if you have Siyah Kernel
Minimum CPU frequency: 200 Mhz
Maximum Frequency: 1000 Mhz
Governor: luzactive
Default I/O sheduler: SIO
So try THAT and tell me if you guys keep getting SoD ...
lol I didn't get SoD since 2 days And I hope it could help. Because installing Wake My Android Pro, or WakeLock or Load Monitor just DIDN'T work for me -__-
i stumble upon this problem whenever i use too harsh UV settings(depends from kernel to kernel). also my device SoDs whenever i use 100mhz as the lowest step- again with some kernels it tolerates it. my guess is: every phone is slighty different, so you just have to experiment with yours and find the best settings for your specific hardware (you dont say xD)
screenager said:
i stumble upon this problem whenever i use too harsh UV settings(depends from kernel to kernel). also my device SoDs whenever i use 100mhz as the lowest step- again with some kernels it tolerates it. my guess is: every phone is slighty different, so you just have to experiment with yours and find the best settings for your specific hardware (you dont say xD)
Click to expand...
Click to collapse
I understand your point of view, but by the way, I read a lot of that forum, and putting minimum frequency at 100Mhz might be Bad for your phone for 4 reasons:
1) When you receive a call, the call might lag because it needs absolutely a minimum of 200Mhz, so setting your CPU minimum frequency at 100Mhz might cause probs for phone calls.. ( i read that somewhere on XDA but dont remember where...)
2) Moreover, "It seems 100 mhz uses more power than 200 mhz. According to tests, 100 mhz accounted to 1 W / GHz and 200 mhz to 0.7 W / GHz, when both the cores were online."
3) "200 mhz can finish same task faster compared 100 mhz and thus hit deep idle soon."
4) "200 mhz is the 'sweet spot' of frequency in SGS II. ie, the frequency used in the calculations based on the optimal energy to run (Ex: In Milestone it's 550 MHz). So , 'energetically efficient' frequency for our CPU is 200 mhz."
Those 3 last reasons came from droidphile I'm not the author of this, but minimum frequency should stay at 200Mhz
i want reactivate this thread, because I think there are some users who still have this problem like me.
As far as I recognized there seems to be more reasons for SoD.
All seems to have begun with Android 4.1.2 and just keeps on until now.
I have tried some kernels and runs now Dori 9.33 and see how it works.
It seems that there are some kernel issues as well as some apps and some constellations of SD-cards.
But no one has a real solution.
I read about a "indish kernel" for the i9100g models, but also some who reported SoDs with this kernel.
But I found no real solution for our i9100.
I have attached a logfile (catched with Catlog) which I recorded until my last SoD.
In my case, I can also call my phone and the caller hears it ringing, but my phone stays black without sound and unresponible.
The only thing is to hold the power button for 10 seconds and reboot it.
just to tell:
nearly 24h without a SoD with my combination
BUT: I have not used my camera so far! And I think camera & media scanning has something to do with it.
If everything is running until tonight, I will try my camera and see the result.
after nearly 2 days
:good: nearly 48h working, so I will keep my combination.
But it is interesting, that nobody has any problems although you can read a lot about this problem.
after more than 2 days:
and here we go. SoD :crying: but 48h is better than nothing
a lot of things might come from corrupt files.
There are 2 scripts which will clean your partitions and try to fix broken files
1. GS2ROMclean made by hawkerpaul
2. Fix_Partitions_v1.0.2.zip made by Computoncio
you can run out of CWM and install as a zip.
So far it is recommended to run 1. GS2ROMClean, reboot, then 2. Fix Partitions to ensure you have clean partitions
Be patient! 2. runs very long, up to 2 hours and the phone becomes very hot. So I think power connection is absolutely recommended
BUT NOT TESTED COMPLETELY BY ME
what I do not know is, how often these scripts shall be used
You could run the ROM clean as often as you want. If the other doesn't fix it after one time, no point running it again. In saying that, I'm not sure if there would be any benefit from running the first one more than once anyway.
Sent from a galaxy far, far away
lavemetoo said:
a lot of things might come from corrupt files.
There are 2 scripts which will clean your partitions and try to fix broken files
1. GS2ROMclean made by hawkerpaul
2. Fix_Partitions_v1.0.2.zip made by Computoncio
Click to expand...
Click to collapse
1. runs very fast, took round about 10 seconds. Reboot was successful afterwards. All was working.
Now I run 2. - info will follow - would be great, if there were a kind of progress bar or a kind of information. So you don not know if it hangs or not.
script 2. ended after 1h with a warning. Now run again?
Code:
/dev/block/mmcblk0p10: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p10: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p10: 11854/131072 files (5.4% non-contiguous), 524288/524288 blocks
Checking preload partition:
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p12: 544/32768 files (0.0% non-contiguous), 29992/131072 blocks
Automatic Fix Partitions finished at 30-07-2013 14:10:33
attached is the complete logfile
ATTENTION: My phone was connected to USB and lost 10% battery during this script operation!
Related
My device has started to completely lock up randomly about five or six times a day and I desperately trying to find the cause.
I'm running a clean install of Checkrom Revolution v2 and Siyah v2.2 final. The problem I'm having is that I'm unable to identify exactly when the problem started to isolate the cause. As such, I've spent quite some time returning the phone to a state that I knew worked - I.e. older kernel (b16), stock voltages, re-enabled the second core, stock gpu settings and restored frequency thresholds, but to no avail.
The phone still crashes, particularly under heavy load such as running a stress test, using sat nav or playing games. However, I can still get a freeze when say I lock the device. The most frustrating part is I cannot perform a titanium backup, as it will crash during the process, with it being quite processor hungry.
So, I'm a bit stuck. Is there any way I can properly trace the cause of the lockup, in a hope to fix it?
Thanks in advance
Any ideas with this? Is there some inbuilt event log that I can read possibly?
Try a different governor (smartassV2) and make sure no UV or profiles, not needed. SetCPU set to only 100-1200mHz.
My CheckROM 3.1.1 and sirahkernel V2.2 in this configuration is flawless.
Sent from my GT-I9100 using xda premium
I'm a noob so I can't ask a question in the dev forum on this thread (where it would be more appropriate):
http://forum.xda-developers.com/showthread.php?t=1362961
I've got the ROM installed and I'm not going to complain about the lag because I've read that it clears up. However, I haven't seen any comments about 2 problems I have.
1) I'm on the east coast of the US and I've got the settings to auto-update over the network, but my phone thinks it's 5hrs ahead of my actual time.
2) When I try to download anything through the market or using apps (like SMS Backup +), it just crawls at a tiny fraction of my previous speeds.
Are these more "just wait for it" issues that will clear up or is there something I can do?
I've already installed CWM's Rom Manager and used it to fix permissions and rebooted a couple of times. THANK YOU!
For the time, it's better to just select your time zone. I've never had the time be accurate when set to automatic. As for the lag, I believe it just takes time. I'm flashing it now so I'll let you know if I notice the same thing and if it seems unusual.
Edit:
After flashing and letting the phone sit, the biggest thing I noticed was it running slow and the battery dropped from 98% to 30% in the 2 hours it sat. I hadn't tweaked my settings yet and CPU Spy revealed that my system was running at 1200 MHz for the majority of the time. Here's what I've been doing with previous versions of ICS that I feel makes a huge difference. In Rom Toolbox, set CPU from 1200 MHz to 1000. Then go to settings > developer options > Don't keep activities. This seems to kill activities more efficiently than a task killer/manager. I also don't allow any other stuff in the background like google getting my location. I also keep gps off unless I need it. With these settings and v6.5 I was getting an average of 10 hours on a charge with frequent use. I'll keep updating as the rom settles.
I set it manually and that seems to stick fine. As a test, I then set it back to auto-via-network and it's still right after a couple of reboots.
The slow internet downloads are KILLING me.
Prior to following the instructions in the ICS passion v7 OP, I dd a ClockworkMod backup of my CyanogenMod7-Kang setup.
Now, I've done a CWM backup of this ICS setup. Can I use CWM to go back and forth from one backup to the other?
...well, I guess I'll find out as I'm about to give it a shot.
Edit: didn't have any problems going from the clean ICS install back to my CM7-kang backup! (whew)
On the other hand, when I tried to go forward from the CM7-kang backup to the ICS backup, it was craptacular and I had to flash the ICS rom again. Not too awful, I guess.
Also, holy crap it's faster now that I let it sit, turned on, while I slept! Yeehaw!
Even the market-downloading is blazing.
a fellow noob with a problem on ics v7
for some reason I can't see the external sd on the phone. I CAN access the external sd on my pc and write files to it. I just cant get the phone apps to SEE the external sd. Help? Should I get back to stock then go for ics v7? (I tried a few mods in-between, might not be ics v7 fault - otherwise everything great with it!) Well, I am going to go back to stock via odin now (sigh) and then to v7 to see if that's the problem.
I've had similar problems. I think the fix is to format everything, but I'd rather not so I'm must accepting things as they are for now. Just a layperson guess, though.
The time zone needs to be set manually.
The slow 3G connection is the only noticeable problem. Wifi speeds are the same as always. Toggling the wifi on/off seems to help my 3G speeds at first. I used the speedtest app in the market to test.
Good luck!
update to v8
I had the same snail download speeds on v7 and am not sure why, but now I'm up to v8 and it is back to the crazy fast downloads!
I feel like a bug list that was easily accessible and organized woud have made it a little easier for me to make a decision in regard to a rom.
I recently just flashed sense 4.0, and even though I though I knew all there is to know about flashing, unlocking, wiping .... I still ran into an issue I never ran into before. Now many thanks later to some members here on the community, I managed to finally go back to my nandroid restore.
Bottom Line: I wish there was a simple bug list thread with current roms for ppl to see what they are about to get into and whether its worth it or not.
My problems are: 1-I dont want the developer to think for one second that their efforts are not HIGHLY appreciated
2- I didnt think it was valuable to start a thread over it.
But against my better judgment; I went ahead and made one anyway.
These are the bugs I found in: Newts OnE XxX RC 2.1 *LIVE!!!* (Sense 4 ICS 4.0.3) 4/17/2012
Aside from the developers statement " pic messages causes sim to unmount rebooting will fix it (wip)
animations need to be turned off in developer settings (need kernel source to fix)"
Here is my own bug list :
1- Rotation is very lagy with multiple crashes. This was imp to me since I always use navigation and I keep switching back and forth between both modes. I had to constantly wait for my phone to unfreeze and press somewhere on the screen to help unlock the freeze.
2-Launcher ( rosie) had random lock ups and freeze ups. Lots of noticeable hot reboots.
3-brightness is very laggy. SOmetimes it just dimmed in day light , forcing me to go indoors to see how to get back to full brightness.
4- When I attempted to restore, here is what happened : http://forum.xda-developers.com/showthread.php?t=1610566
========================================
Bug list for Clean rom DE 1.2 (ics rom ):
1- wifi tether : when I enable security , I lose connection after 10-15 mins of activity
2- Phone is a hot potato! I hit high temps constantly
3- All cpu programs fail to keep settings intact for long periods of time. Putting the governor on conservative helps a bit, but I still find my cpu with min and max speeds set to 1.5 ghz without me doing it
4- go launcher is seriously laggy on all ics roms
5-very hi-def videos are not as smooth as they were on gb roms.
Well the roms are based on a leaked rom so bugs would be expected.
ya you can't expect anything less then a few bugs here and there but they'll also get worked out in the end or most of them
Hi I got this phone couple of days back. It came flashed with latest Android 4.0.3 (20120608-154131)
I have rooted it using zopoROOTby_Jaynes_android4.0.
It's working fine, but seems the battery life is ridiculous and the battery information is also not reliable, especially after restarting the device
(Sometimes it suddenly decreses a lot and vice-versa).
Also GPS, I tried it out in the open for like 15-20 mins it finds 4-6 sats but DOESN'T lock on.!
And then the market had some incompatible apps, I did the XML trick, didn't work...removed the 5 files again and then gave up, all of a sudden after a restart, market is fully accessible!! (Weird!)
I have backed-up my apps using Titanium free but I want to install CWM recovery. I do not know the exact procedure to follow for the same.
I just want to have the CWM recovery and not want to flash whole ROM again...How to do it???
Also please give me any important suggestions, tips if you have regarding this phone.
Thank you!
Anyone have anything to say?
NHS2008 said:
Hi I got this phone couple of days back. It came flashed with latest Android 4.0.3 (20120608-154131)
I have rooted it using zopoROOTby_Jaynes_android4.0.
It's working fine, but seems the battery life is ridiculous and the battery information is also not reliable, especially after restarting the device
(Sometimes it suddenly decreses a lot and vice-versa).
Also GPS, I tried it out in the open for like 15-20 mins it finds 4-6 sats but DOESN'T lock on.!
And then the market had some incompatible apps, I did the XML trick, didn't work...removed the 5 files again and then gave up, all of a sudden after a restart, market is fully accessible!! (Weird!)
I have backed-up my apps using Titanium free but I want to install CWM recovery. I do not know the exact procedure to follow for the same.
I just want to have the CWM recovery and not want to flash whole ROM again...How to do it???
Also please give me any important suggestions, tips if you have regarding this phone.
Thank you!
Click to expand...
Click to collapse
Is the phone going in deep sleep? (install cpu spy to check). This could be your battery problem. WiFi/3G/Bluetooth and some apps can keep the phone from going into deep sleep. You can try to edit build.prop to help it go into deep sleep.
The gps - theres some things you can edit in gps.conf and secgps.conf to get a faster fix (like changing time servers and how a-gps works).
kevinlekiller said:
Is the phone going in deep sleep? (install cpu spy to check). This could be your battery problem. WiFi/3G/Bluetooth and some apps can keep the phone from going into deep sleep. You can try to edit build.prop to help it go into deep sleep.
The gps - theres some things you can edit in gps.conf and secgps.conf to get a faster fix (like changing time servers and how a-gps works).
Click to expand...
Click to collapse
Thanks for your helpful reply! I installed CPU Spy and here's what I found!
Seems, it's keeping at 1001 Mhz all the time!! Am I right??
Are there any other ways around it than editing system files??
Thanks again!! About GPS I got it to work today, albeit not accurately...
NHS2008 said:
Thanks for your helpful reply! I installed CPU Spy and here's what I found!
Seems, it's keeping at 1001 Mhz all the time!! Am I right??
Are there any other ways around it than editing system files??
Thanks again!! About GPS I got it to work today, albeit not accurately...
Click to expand...
Click to collapse
Yep, looks like it is staying at 1ghz, you can install an app like setcpu to manage the cpu frequency. You will probably be limited by the kernel when it comes to governors (no undervolting either).
If you are not comfortable editing the gps.conf/secgps.conf there are apps for that I think. But it is quite easy with a file manager (root browser for example), the gps.conf tweak is to change the " NTP_SERVER= " to the closest server to where you reside from this site :
http://www.pool.ntp.org/en/
For example if it says NTP_SERVER=0.europe.pool.ntp.org , (edit: noticed you live in India, so you would do it like this):
NTP_SERVER=1.in.pool.ntp.org
NTP_SERVER=0.asia.pool.ntp.org
NTP_SERVER=2.asia.pool.ntp.org
If you want to see more on these gps tweaks(I would just do the time server tweak since it works on all phones, I'm not sure if the secgps.conf tweak works with your phone), check out this thread (it's been updated at the bottom of the first post) : http://forum.xda-developers.com/showthread.php?t=1320626
I'm not sure about CWM, I think it has to be tailored to the phone itself because of the location of the recovery partition.
Edit2: I noticed in the picture that your phone has 1ghz , 500 mhz 250mhz and 166mhz. You can add a profile to setcpu to set the CPU to max 250mhz while the screen is off for example. This wouldn't fix your deep sleep issue, but would save battery. (Deep sleep is some parts of the CPU turned off, while some parts stay on)
Thanks again! I have set it to 250-1001 ondemand and apply on boot now. But 'deep sleep' is still unused as per CPU spy, Any clues as to how can it be enabled?
About GPS, I can do that. Just that I could live without it for now, but thanks for elaborating it! I will do it tomm. Morn, its 2:39 am.
NHS2008 said:
Thanks again! I have set it to 250-1001 ondemand and apply on boot now. But 'deep sleep' is still unused as per CPU spy, Any clues as to how can it be enabled?
About GPS, I can do that. Just that I could live without it for now, but thanks for elaborating it! I will do it tomm. Morn, its 2:39 am.
Click to expand...
Click to collapse
I posted second edit after you posted, will repost here in case you missed:
Edit2: I noticed in the picture that your phone has 1ghz , 500 mhz 250mhz and 166mhz. You can add a profile to setcpu to set the CPU to max 250mhz while the screen is off for example. This wouldn't fix your deep sleep issue, but would save battery. (Deep sleep is some parts of the CPU turned off, while some parts stay on)
Click to expand...
Click to collapse
The deep sleep issue is probably related to some apps keeping the phone on (could be kernel problem also, but I'm not an expert on that so can't say). You can check wake-locks with betterbatterystats. Also, rebooting the phone helps(rebooting after charging also helps I noticed). Edit: Some tips on wake-lock : http://forum.xda-developers.com/wiki/Wakelocks
kevinlekiller said:
I posted second edit after you posted, will repost here in case you missed:
The deep sleep issue is probably related to some apps keeping the phone on (could be kernel problem also, but I'm not an expert on that so can't say). You can check wake-locks with betterbatterystats. Also, rebooting the phone helps(rebooting after charging also helps I noticed). Edit: Some tips on wake-lock : http://forum.xda-developers.com/wiki/Wakelocks
Click to expand...
Click to collapse
Thanks for your reply. I think it is more of a Kernel problem only.
ust found out using Batterystats that As soon as I get a message or notification, It triggers LED light and a WAKE LOCK (Called 'Leds Wakelock' ) Which prevents phone from going into deep sleep, and it remains that way hogging battery! Only solution is to REBOOT and hope you don't get any notification!
BEFORE REBOOT
AFTER REBOOT
If your phone has a cyanogenmod rom (I haven't looked into the popularity of it), there is an option to turn off the LED notification in the cyanogenmod settings. Does Zopo release the source code for the kernel / rom?
I read in the other thread about the phone having issues when not in the performance governor, that is a shame, maybe the voltage is adjusted lower at lower frequencies causing the reboots.
kevinlekiller said:
If your phone has a cyanogenmod rom (I haven't looked into the popularity of it), there is an option to turn off the LED notification in the cyanogenmod settings. Does Zopo release the source code for the kernel / rom?
I read in the other thread about the phone having issues when not in the performance governor, that is a shame, maybe the voltage is adjusted lower at lower frequencies causing the reboots.
Click to expand...
Click to collapse
I don't know whether it is cyanogenmod (I don't even know what that is..) But my phone doesnt have ANY option regarding that. But
Here's a good thing, since I restarted to take screen shot I've had several notifications LED flashes, and the 'LEDS Wakelock' hasn't reared it's ugly-head!
ALSO I have again set the Governor to 'On demand' and now it seems doing better no Hang up for a good time played AB space. going good!
I think that LEDS Wake lock was root of all troubles. Will have to keep a lookout for it.
Thanks a lot for your guidance!
Have you come up with a solution that can kill that wakelock other than reboot? From my observation that leds wakelock only happen when the battery's going low (<15%) and it won't go away after that.
Dirty solution is to patch framework-res.apk and modify the level of battery low notification.
I am using a newer custom ROM 100500 v2 and no longer have any issues with wake locks!
Sent from my XT910 using Tapatalk 2
Firstly an introduction to my problem - I've been having problems with high cpu usage whenever I enable my wifi. I've gone to stock [I9100DXLSD_I9100OLBLSD_XME.zip], tried different kernels [Apolo, siyah, speedmod, dorimanx], tried different roms [slimkat, neatmod, jellysnap], done factory resets for each, flashed quite a few modems [dx's,xx's, currently trying radio-cm-9-SGS2-LP6-signed.zip, there's a whole bunch that I'm still going through as well - can't post urls yet]. I had no luck with all of these methods so far.
Since that approach didn't work I have also been looking at wakelock detector,gsam and betterbatterystats to find out what was chewing up cpu and causing battery drain. I initially thought it was something caused by google play services (SystemUpdateService), wlan_rx_wake, or a pc/router on network with a configuration conflict or something like ipv6 causing bizarre behaviour but so far I have been able to get rid of wlan_rx_wake problems but those were minor on the battery drain problems I was having. Using a static ip also did not improve anything. Wakelock detector/gsam/betterbatterystats were now all showing either android os or android kernel as the culprit but would not show exactly what process was causing it. Once I enabled 'show cpu usage' in developer options I was able to see that dhd_dpc process was causing all this havoc. There does not seem to be much information on the net about this process and problem. When I switch wifi on, I'll be able to use the net fine for a few seconds to a minute before dhd_dpc decides to kick in and using a high amount of cpu causing insane drains and I have to quickly switch wifi off before it locks up requiring a reboot.
What I have found out through all of this by accident is that if I enable wifi and then quickly copy a file from my phone to a pc on the network, I am able to use internet on my phone without any lockups and the speed (cpu) is fine and fluid as usual but only while the file is still copying over the network. During this time dhd_dpc seems to consume cpu like it normally should as I've seen on the other devices I have. Why is this? This has to be a software issue since it works flawless when I do this? Not sure why it would require some sort of lan traffic in order to get wan traffic working without sending the cpu usage to orbit. The battery of course drains but not as bad since it's busy copying files over. Maybe possible that it doesn't like the routers on my network that might be sending arps and copying files over the network makes it ignore that traffic (just shooting in the dark here)?
I hope someone can shed light on this and perhaps give me some other things I can try. Btw, cell radio/mobile data are all fine, except for one or two of the modems that I tried. So is this kernel, rom or modem related? Please help! This is the only thing not working properly on this phone. Thanks for all those that took the time to read and answer.
Currently on my phone:
Rom: I9100XWMS3_NeatROM_v6.4
Kernel: Apolo-4.15b_Regular
Modem: LP6 (this is just what I am currently testing out of the dozens of modems I have)
PS- yes I use kernel wipe and rom wipe scripts. Maybe the problem is somewhere in dhd.ko?
Anyone mind uploading their dhd.ko that doesn't have this dreaded dhd_dpc cpu pegging purge business just so I can rule it out?