Despite setting the WiFi sleep policy to "never", HD2 becomes unpingable when the screen goes off, causing applications such as Fring/Skype/etc to lose connection. After turning the screen back on, the WiFi reconnects, and does it rather quickly, but having it off while the screen off meaning no incoming Fring/Skype calls possible on WiFi.
Any ideas ?
NOTE: i am currently using this build.
Same problem. Wi-Fi goes to sleep when screen goes off, even if Wi-Fi tethering is running. It's a reason of losing connection via Wi-Fi tethering. BUT! If at least one network service is active (ping, for example), Wi-Fi doesn't goes to sleep. I think that some of background services (Wi-Fi routing!) stops or becomes idle when screen goes off. It's a priority or policy bug, maybe... Not in a particular ROM, but in Android OS.
Using MDJ's CyanogenMod 7 NAND ROM (Android 2.3.2 Gingerbread).
or may be in power saving option check there .it looks like it saving your battery power.
shahnowaz said:
or may be in power saving option check there .it looks like it saving your battery power.
Click to expand...
Click to collapse
It is not power saving options because it also happens to my mdj 2.6 build with battery full. Power saving starts on 15% on my battery and also wifi and background data has been unchecked.
When this happens, no email updates, voip, and other app updates that needs data(because mobile data is intermittent in my area).
yeah, actually happens with all builds
I solved with this app, enabling all workarounds
http://www.appbrain.com/app/wi-fi-keep-alive/com.shantz.wifikeepalive
Enabling all workarounds would keep the device fully awake, this is not really a solution.
Tbh, this issue smells like a power management related bug in a wifi module/driver.
Also, if you google a bit, you can see it being talked about on nexus one, mentioning cyamogen roms as ones not having this issue.
Any idea what module/driver is responsible for wifi ? Is it a part of the kernel ? Or is it a module we may try replacing ?
rafpigna said:
yeah, actually happens with all builds
I solved with this app, enabling all workarounds
http://www.appbrain.com/app/wi-fi-keep-alive/com.shantz.wifikeepalive
Click to expand...
Click to collapse
Thanks much, just installed.
The offending driver seems come in a separate module, "bcm4329.ko". Here is a Nexus One thread mentioning the issue on one of the Nexus One stock builds, and actually presenting an updated module for that stock build.
Since HD2 uses the very same BCM4329 chip, it should be possible to compile the updated module for an HD2 kernel.
Any kernel guys up to the task ?
InfX said:
The offending driver seems come in a separate module, "bcm4329.ko". Here is a Nexus One thread mentioning the issue on one of the Nexus One stock builds, and actually presenting an updated module for that stock build.
Since HD2 uses the very same BCM4329 chip, it should be possible to compile the updated module for an HD2 kernel.
Any kernel guys up to the task ?
Click to expand...
Click to collapse
We need the commit used to do the change. I looked at the thread and found a commit but I dont think that is the right one.. Anyway I will try to see if can be included in my kernel asap and check if the situation improves.
rafpigna said:
We need the commit used to do the change. I looked at the thread and found a commit but I dont think that is the right one.. Anyway I will try to see if can be included in my kernel asap and check if the situation improves.
Click to expand...
Click to collapse
I checked, and the fix is already there... So at this point I think this is not our problem. I will try to address this to markinus or danijel that are far more experienced than me in kernel stuff
rafpigna said:
I checked, and the fix is already there... So at this point I think this is not our problem. I will try to address this to markinus or danijel that are far more experienced than me in kernel stuff
Click to expand...
Click to collapse
Maybe, just maybe, it's already fixed in your latest kernel, that uses the latest code base ? Note that i did NOT try & check it with every kernel available, i've only checked this with one that came with the build i am using (i think it was MDJ there, newer version uses yours, but i am not yet running it).
Anyone using latest rafpinga kernel, can you please test and respond ?
Update, rafpigna 1.7 installed, identical WiFi behaviour.
Looks like this is the solution for Desire:
http://forum.xda-developers.com/showthread.php?t=752856
Hopefully someone could adopt this to HD2.
Nice... Rafpigna, the diffs are at this post, can you apply and compile the patched "bcm4329.ko" for us to try ?
Sorry for being too dumb to do it myself, i just never ever happened to compile a linux kernel, not even once in my entire life
InfX said:
Nice... Rafpigna, the diffs are at this post, can you apply and compile the patched "bcm4329.ko" for us to try ?
Sorry for being too dumb to do it myself, i just never ever happened to compile a linux kernel, not even once in my entire life
Click to expand...
Click to collapse
It's not our problem
Note: This isn't related to the sleep mode wifi disconnections caused by MAC addresses that don't begin 00, so far as i'm aware that's been patched for a while now. Wifi remains connected fine in standby mode, but the throughput is only suitable for very light traffic.
Click to expand...
Click to collapse
I know its not our problem, but this may still be our solution. Our problem, seemingly, starts when the driver it going down into the deepest power saving state it can. It is supposed to sustain connectivity in it, though, but it seemingly doesn't. Avoiding this deepest state (PM_MAX) may solve the problem while having little to no side effects. Well, obviously, i do understand it's going to consume more power with WiFi on, but its better than being unable to keep it on at all.
Again, i know this is not exactly our problem, but again, this CAN be our solution anyway.
InfX said:
I know its not our problem, but this may still be our solution. Our problem, seemingly, starts when the driver it going down into the deepest power saving state it can. It is supposed to sustain connectivity in it, though, but it seemingly doesn't. Avoiding this deepest state (PM_MAX) may solve the problem while having little to no side effects. Well, obviously, i do understand it's going to consume more power with WiFi on, but its better than being unable to keep it on at all.
Again, i know this is not exactly our problem, but again, this CAN be our solution anyway.
Click to expand...
Click to collapse
I think it's definitely worth a try...
mishik said:
I think it's definitely worth a try...
Click to expand...
Click to collapse
Hello!
Unfortunately, I have tried this (to my detriment; I have code due tomorrow still!), and basically replaced the equivalent of this in the RAF 1.7 code (dhd_cdc.c and wl_iw.c have the PM_MAX vs PM_FAST thing).
My zImage came out almost a whole MB smaller (probably a toolchain thing), but the wifi problem while sleeping still exists, at least the symptoms that are linked in http://code.google.com/p/cyanogenmod/issues/detail?id=2403 with the similar fix of PM_MAX vs PM_FAST. That is to say, if I open the terminal and ping google.com, when the screen is off I get 300ms pings and when the screen is on I can get 3ms pings.
This happens whether I change PM_MAX or PM_FAST.
So this isn't the fix for what it's supposed to fix (or maybe I'm doing it wrong, toolchain's wrong, something), but I'll give it a few days to figure out whether my wifi drops more or less. Hopefully less.
(My symptoms are that, on campus, I have no problems with wifi, but sometimes if I leave the wifi zone and then come back, it'll report still having an IP lease and everything, but all pings and connectivity-type things such as web browsing will time-out. Not sure if this is what is being discussed here, but I thought it might help!)
Thanks,
Jeff
PS If you want the zip just to give it a spin, pm me or I might attach it here. That said, it might break everything! No obvious problems on my phone yet, though, so...
EDIT!: Of course, I invite anyone (especially rafpigna; perhaps you've tested this already?) to double check my work. It's possible I might've misplaced something!
I didn't do anything advanced; just pick up the CodeSourcery toolchain (free) for ARM (not GNU/Linux) and then install it on a Linux machine (it's possible with Windows, probably, but it'll be harder with the RAF build.sh). Then, make sure you have make and gcc packages on your Linux machine and then put your sources in the right directory and then try running the build.sh! rafpigna documents his work very well. Thanks rafpigna!
Did you remember to actually replace the .ko module, not just zimage ?
Hello,
Did you remember to actually replace the .ko module, not just zimage ?
Click to expand...
Click to collapse
Of course.
Related
Hi Everyone,
This is a recompiled version of Hastarin’s HD2 Android kernel that can be applied to most HTC HD2 RAM Android builds including DarkStone’s SuperRAM 1.5 build. The additional benefits over most existing builds is the inclusion of CIFS, or the ability to use CIFSManager to mount and unmount shared folders on your local network.
Download, installation instructions, and FAQ
If anyone needs any other version, non-oldcam, etc, just let me know and I'll add it to the downloads.
Thanks,
B.
will try this asap
Nice, cifs is very useful for me.
Thank you for compiling.
I should also point this out just in case, though I don't think it had anything to do with a kernel switch, as I was changing a million different things as I built the kernel. When I started using SuperRAM 1.5, my HD2 idled at about 7MA. Once I updated the kernel, and did a million other things, I was idling at about 60MA. After resetting back to the original data.img from SuperRAM 1.5, it dropped back to 7MA. All of this was using the same, attached, kernel.
So, as stated, it's obviously not anything to do with the active kernel, but in case anyone else has the problem, I would recommend going back to the original data.img and re-setting up.
Thanks,
B.
this work for Cedesmith new Initrd?
Thanks heaps ^_^
Sent from my HTC Desire using XDA App
Thanks! I do have something to ask, though - could cifs be compiled as a module so we could load it externally via insmod?
I don't know whether this is related to kernel or not.
I love the latest RAM builds, but with all these builds, my SE Bluetooth stereo headset hard buttons aren't working. Can u fix this issue.
Because of this small issue I cannot use these builds. Thanks in advance
Sent from my HTC DesireHD2 using XDA app
Good job !
This is useful for me, and how about "nls_utf8.ko" module?
We need utf8 for CIFS manager.
Is this build the same as darkstone superram
Sent from my HTC Desire using XDA App
Fmstrat said:
I should also point this out just in case, though I don't think it had anything to do with a kernel switch, as I was changing a million different things as I built the kernel. When I started using SuperRAM 1.5, my HD2 idled at about 7MA. Once I updated the kernel, and did a million other things, I was idling at about 60MA. After resetting back to the original data.img from SuperRAM 1.5, it dropped back to 7MA. All of this was using the same, attached, kernel.
So, as stated, it's obviously not anything to do with the active kernel, but in case anyone else has the problem, I would recommend going back to the original data.img and re-setting up.
Thanks,
B.
Click to expand...
Click to collapse
I have been testing SuperRam 1.5 with current kernel patch from original thread last couple of days, and I have been monitoring current usage since yesterday evening with different options. From what I have seen so far it will stay 6/7/8amp for some time and if you use the HD2 (browser/maps) for few minutes and put it in standby again, it might go back to 60amp. I reproduced this several times.
The most reliable I got was when I disabled mobile data, auto sync, GPS, BT, Wifi, but 3g is on. it consistently gives 7amp so far.
Current widget is set to log every 180sec.(if you set lower this widget might itself will interfere with readings as it has to write to SD card)
I think there is a bug in sync or mobile data which is causing this, it can't be just any change in data.img.
windroidHD said:
I have been testing SuperRam 1.5 with current kernel patch from original thread last couple of days, and I have been monitoring current usage since yesterday evening with different options. From what I have seen so far it will stay 6/7/8amp for some time and if you use the HD2 (browser/maps) for few minutes and put it in standby again, it might go back to 60amp. I reproduced this several times.
The most reliable I got was when I disabled mobile data, auto sync, GPS, BT, Wifi, but 3g is on. it consistently gives 7amp so far.
Current widget is set to log every 180sec.(if you set lower this widget might itself will interfere with readings as it has to write to SD card)
I think there is a bug in sync or mobile data which is causing this, it can't be just any change in data.img.
Click to expand...
Click to collapse
+1 to this. I have the exact same experience after days of testing. If I leave the phone alone in airplane mode with only wifi enabled, the phone lasts for like 5 days, and keeps 3-7mA idle readings. If I refresh the browser, it stays at 60mA for a while, but then eventually lowers back to 6/7mA after a while.
I'm also on Froyo RAM edition 1.5.
Is extended battery supported in this kernel?
windroidHD said:
I have been testing SuperRam 1.5 with current kernel patch from original thread last couple of days, and I have been monitoring current usage since yesterday evening with different options. From what I have seen so far it will stay 6/7/8amp for some time and if you use the HD2 (browser/maps) for few minutes and put it in standby again, it might go back to 60amp. I reproduced this several times.
The most reliable I got was when I disabled mobile data, auto sync, GPS, BT, Wifi, but 3g is on. it consistently gives 7amp so far.
Current widget is set to log every 180sec.(if you set lower this widget might itself will interfere with readings as it has to write to SD card)
I think there is a bug in sync or mobile data which is causing this, it can't be just any change in data.img.
Click to expand...
Click to collapse
In regular SuperRam (and other builds i think) I notice 60ma or 20ma standby drain after using the browser for a few minutes, especially if I was watching flash content, but it eventually settles down to 7ma. I have not added this kernel or tried it yet, I am just mentioning this because what you described there is what I see with my config normally.
will try this out! Thanks!
Can you also post the non-oldcam version? cifs supports works ver well.
Thanks!
pablo71 said:
In regular SuperRam (and other builds i think) I notice 60ma or 20ma standby drain after using the browser for a few minutes, especially if I was watching flash content, but it eventually settles down to 7ma. I have not added this kernel or tried it yet, I am just mentioning this because what you described there is what I see with my config normally.
Click to expand...
Click to collapse
Agreed, I noticed this running SuperRAM 1.5 prior to changing kernels as well.
Renegade_Rulez said:
Is extended battery supported in this kernel?
Click to expand...
Click to collapse
Yes. oldcam_eb stands for "Old camera library files with extended battery support."
Renegade_Rulez said:
Can you also post the non-oldcam version? cifs supports works ver well.
Thanks!
Click to expand...
Click to collapse
What build would this be for? Just want to make sure I include the right things.
Thanks,
B.
Heyo bros so I'm experiencing what I'm afraid might be a problem:
I've been getting watchdog alerts regarding the "Base System" process. It notifies me that the CPU % at the time of the captures range from 40% to 60+%. Coincidence or not, it usually happens when I wake my phone from sleep- not when I unlock it, just when I press the power button. The moment the lock screen pops up, the phone's already vibrating and the watchdog notification is up in the status bar.
Battery life so far is:
9h 22m @ 74%; Phone Idle- 56% | Cell Standby- 22% | Display 17% (40m) | Android OS 3% | Voice calls- 3%
Who knows, maybe this^ looks normal. I just want to be sure.
I've heard talk of 'wakelocks' but I don't know exactly what they are, what might cause them, and how I can track them.
I'm currently running:
Atrix 4G (not 2, just for clarification)
CM7 xB^xN
Baseband reads: N_01.77.30P
Kernel version reads: 2.6.32.39-MB860-GB-Faux123-v0.2.1 [email protected] #14
Build number: GWK74
Totally honest, I don't know if that might be able to help diagnose the problem, but for what it's worth, I want to check two things:
1) I flashed Faux's enhanced stock CM7 kernel, and am pretty sure it took, but does that look to be the proper kernel version? I just want to be sure.
2) While I also flashed the "latest radio" in the CM7 xB^xN thread, I was certain there was an xx.97 radio (vs the x.77 radio that mine appears to currently have). Am I indeed on the latest radio version?
Would it hurt to reflash these two? Could either one, or maybe both, be the cause of this?
It also occurs to me: I've been using SetCPU and have ONE profile set up that forces my CPU to min/max 216/216 when the screen is off. Could that be causing it?
Thanks so much for any and all insight bros. Also, please let me know if there's any more info you might want to help diagnose what the dealio is.
Heyo guys,
I hate to bump this kinda soon, but this is definitely a problem.
It's getting to be that I don't even have to wake the phone up for the Base System to spike. I was woken up a couple times in the middle of the night by notifications saying it was really high.
You guys have any thoughts? I'd really like to get this resolved as CM7 is AWESOME.
Yes, you guessed it- I'm not anal about the fingerprint scanner or webtop. Just a stable and fully functional release.
Thanks for any help bros I really appreciate it.
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
AX-MA said:
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
Click to expand...
Click to collapse
Thanks for the insight bro. For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Looks like a couple of us are having problems then, though. We'd both really appreciate any info, advice, or help.
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
xyrovice said:
For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Click to expand...
Click to collapse
AX-MA said:
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
Click to expand...
Click to collapse
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
WiredPirate said:
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
Click to expand...
Click to collapse
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
xyrovice said:
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
Click to expand...
Click to collapse
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
WiredPirate said:
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
Click to expand...
Click to collapse
Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
Also, is there any reason CM7 would have the minfree set to a default that causes this?
Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Thanks so much for saying this bro. Who knows, this might be the problem.
PS: I just tried this and am going to see if it works. Post #13 is the one that would really sum up my reaction of successful.
Hopefully maybe this helps my other bros.
xyrovice said:
1Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
2Also, is there any reason CM7 would have the minfree set to a default that causes this?
3Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Click to expand...
Click to collapse
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
possible solutionary steps I've taken:
So Update:
I actually ended up checking out my (partial) Wakelocks with betterbatterystats, and I think I may have found a problem (diagnosed with alarmdump.txt from the Alarm Manager):
1) When I first flashed CM7 I thought, "Oh well why not really get comprehensive about keeping apps up to date" and I actually, for every single app, checked the "Automatically update" box in each one's market page. This led to a CATACLYSMIC wakelock that I'm now pretty sure could be the problem.
2)Google talk also seemed to be a little active with the screen off so I unticked the "sign me in auto..." box and made sure I signed out.
Lastly (not related to wakelocks), I checked on my TTS settings (see my last post about that).
Oh also LASTLY lastly I froze the modem fastdormancy manager in TiBU (kinda just for ****s and giggles). That said though, is the consensus on this that it's pretty harmless?
So, other bro who was having a problem, check and see if this might help you at all AYY
WiredPirate said:
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
Click to expand...
Click to collapse
Thanks for posting this. I checked ROM toolbox and it does indeed have the capability. That said, if my aforementioned possible solutions don't work, I'm turning here. Thanks for the info bro.
Watchdog is flagging the "base process" app because IT IS using over 60% of your CPU BUT it is using 60% of your CPU that is running at 216MHZ.
It's your screen off setcpu profile of 216/216, if you bump up the max to 456 the alert will go away. When you have it set as 216/216 Watchdog (I believe) thinks that is the actual max cpu speed and bases its percentages off of that. I got that warning before and after a bit of troubleshooting (actually tried several different things) found that was the problem.
I am not sure but if you "whitelist" a app in watchdog it might ignore it as well. However my alert level was set at 80% and it would still set it off, so I think the higher speed might just be better.
Hi,
Was wondering if anyone else with a Nook Color sees any SODs on the latest cm10.1 nightlies?
Have tried to read through a fair number of threads, but most of them are concerned with SODs on earlier versions, and no one seems to have talked about having them on cm10.1.
I can't find a way to get a log of when it happens, because it doesn't happen when plugged in, and when it does happen, adb doesn't report any device being attached.
Anyone with a good idea, or who also experiences SODs even now?
cinaeco1 said:
Hi,
Was wondering if anyone else with a Nook Color sees any SODs on the latest cm10.1 nightlies?
Have tried to read through a fair number of threads, but most of them are concerned with SODs on earlier versions, and no one seems to have talked about having them on cm10.1.
I can't find a way to get a log of when it happens, because it doesn't happen when plugged in, and when it does happen, adb doesn't report any device being attached.
Anyone with a good idea, or who also experiences SODs even now?
Click to expand...
Click to collapse
First question: are you overclocking? If you're seeing SODs with the max CPU speed set above 1000 MHz, dial it down to 1000 MHz and see if they still occur. If you're seeing SODs at 1000 MHz, try 800 MHz. (If you're crashing at 1000 MHz, but not at 800 MHz, please let us know ASAP!)
steven676 said:
First question: are you overclocking? If you're seeing SODs with the max CPU speed set above 1000 MHz, dial it down to 1000 MHz and see if they still occur. If you're seeing SODs at 1000 MHz, try 800 MHz. (If you're crashing at 1000 MHz, but not at 800 MHz, please let us know ASAP!)
Click to expand...
Click to collapse
Yeah, I was at 1100MHz.
When I was on 1100MHz, I didn't think it would be the overclock, because SODs would not occur if I had wifi turned off.
I'll see if it still happens at 1000MHz.
So far, on a clean install of the latest nightly, nothing yet. Will see how it goes for the day.
Thanks!
Still happening
Hm.
I've now tried 1000MHz and 800MHz, and I have had SODs on both.
Was a clean install of 20130605.
Formatted system, data and cache before install.
No other settings that I know of changed, other than moving from 1000MHz to 800MHz.
Connected to wifi, signed into to gmail account, so far have only done store update, installed xda app, and KeePassDroid.
Have noticed that when I'm away from my wifi (at work) where it is connected to nothing, it doesn't SOD.
Only SODs after I get back home, perhaps an hour after turning it on to see if it's okay.
Makes me think it's related to that wifi thing mentioned about older firmwares, but wasn't that built in, starting from cm9 or something?
I suppose it's good that it's SODing on both frequencies and not just one?
How should I be trying to get (hopefully) helpful info off this?
cinaeco1 said:
Hm.
I've now tried 1000MHz and 800MHz, and I have had SODs on both.
Was a clean install of 20130605.
Formatted system, data and cache before install.
No other settings that I know of changed, other than moving from 1000MHz to 800MHz.
Connected to wifi, signed into to gmail account, so far have only done store update, installed xda app, and KeePassDroid.
Have noticed that when I'm away from my wifi (at work) where it is connected to nothing, it doesn't SOD.
Only SODs after I get back home, perhaps an hour after turning it on to see if it's okay.
Makes me think it's related to that wifi thing mentioned about older firmwares, but wasn't that built in, starting from cm9 or something?
I suppose it's good that it's SODing on both frequencies and not just one?
How should I be trying to get (hopefully) helpful info off this?
Click to expand...
Click to collapse
Mine does the same thing. Not over clocked and only occurs when WiFi is on and connected. Running cm10.1 rc4. Did the same thing on rc3.
cinaeco1 said:
I suppose it's good that it's SODing on both frequencies and not just one?
Click to expand...
Click to collapse
Welllll ... define "good" -- it means that we can rule out the clock speed as a cause, but it also means we have no other candidate causes that immediately come to mind ...
cinaeco1 said:
Have noticed that when I'm away from my wifi (at work) where it is connected to nothing, it doesn't SOD.
Only SODs after I get back home, perhaps an hour after turning it on to see if it's okay.
Makes me think it's related to that wifi thing mentioned about older firmwares, but wasn't that built in, starting from cm9 or something?
Click to expand...
Click to collapse
Some potentially useful data points to collect:
If you haven't filled out the hardware survey already, please do so.
If you can, please try out a clean install of the April 14 CM10 nightly. (To be clear, I don't expect a difference, but I do want to rule out a couple of things as potential causes.)
Can you connect to the tablet via adb while it's SODing? If so, get dmesg and logcat output from the device while it's doing that. If not, then try this: while the tablet is hooked up to a computer via USB, hold down the power button until it shuts off, turn it on again, and grab the contents of /proc/last_kmsg (if the file exists) and post them. (If there's no /proc/last_kmsg after doing that, let me know.)
Have now done the hardware survey, and will be testing out the cm10 rom.
When SOD happens, I can't get adb to see the device, so yeah, I'll try that which you've mentioned.
CM10 april nightly also SOD'd.
No device found by adb during SOD.
Connected NC to computer with USB cable and forced power off as suggested.
When NC booted, used Terminal to have a look at `/proc`, but didn't see a `last_kmsg` file.
Will flash back to CM10.1 anyway, and see if I can get a `last_kmsg` file
cinaeco1 said:
CM10 april nightly also SOD'd.
No device found by adb during SOD.
Connected NC to computer with USB cable and forced power off as suggested.
When NC booted, used Terminal to have a look at `/proc`, but didn't see a `last_kmsg` file.
Will flash back to CM10.1 anyway, and see if I can get a `last_kmsg` file
Click to expand...
Click to collapse
Hm, very puzzling ... I'm afraid we're sort of operating blind then. Can you try the new wifi firmware I've just put up in the CM10.1 thread and see whether that helps your problem?
Hmm... CM10.1 didn't give me a `last_kmsg` either.
Okay, I shall try the wifi driver a couple of weeks later, after we come back from a trip Thanks!
I still had an SOD on the new wifi driver. Have updated to a later nightly that seems to have this driver built in anyway (think I saw it in the change log?). I'll be half-trying to figure out if there is a pattern to how these SODs are happening... but in the mean time, I guess just using the device as it is.
My phone shuts down on 4.3 and 4.4 based roms.
It happens much less often on 4.2 and stock based roms.
It seems to happen when the screen is off. It doesn't shut down when I'm in the middle of doing something. I've seen that on other phones.
If the screen is off, but I'm listening to the music player or Pandora, it does not shut down.
It does not seem to be overheating.
I'm on my 3rd sim card in 2 months and my second class 4 SD card. I only bought a new one b/c used the one from my old phone and thought it was best to start fresh.
Currently I'm running the first CM11, but this has been happening on CM 10.2, AOKP, and a variety of other roms.
My recovery is TWRP 2.6.3.0
I use the regular GAPPS, not PaGAPPS and the appropriate GAPPS for the given AOSP base; 4.2/3/4
I flash SuperSu-v1.65 after a full wipe when installing new roms.
The current apps I have installed in addition to what comes with CM are:
Evernote
Freecell
Google Voice
gReader Pro
Pandora
Quickoffice
Rom Toolbox Pro
Scanner Radio
Shuttle+
SMS Backup+Restore
Solitaire
Tapatalk Pro
UPM - Universal Password Manager
Xposed Installer - I don't have any modules installed at the moment and the last time today it shut down by itself was before I installed Xposed.
I know that logcats are good for tracking down errors for apps that FC, though I don't know yet how to read logs.
Is there an app I can use that can show me activity before the last shutdown?
How can I track down what's causing it?
TIA
please delete
On 2nd thought I did not feel I could contribute well.
Sounds like S.O.D's (sleep of death). It's a kernel problem and I believe they're cause by qcom's hot plugging. You could rename MPdecision to MPdecision.bak and reboot. That will keep the second core on and it should help. I used to get them as well until I updated to the two latest updates. But SOD's are a well known issue with the RAZR M.
Sent from my XT907 using Tapatalk
EDIT:
Code:
system \ bin \ MPdecision
aviwdoowks said:
please delete
On 2nd thought I did not feel I could contribute well.
Click to expand...
Click to collapse
Thanks for trying though.
ATTACK said:
Sounds like S.O.D's (sleep of death). It's a kernel problem and I believe they're cause by qcom's hot plugging. You could rename MPdecision to MPdecision.bak and reboot. That will keep the second core on and it should help. I used to get them as well until I updated to the two latest updates. But SOD's are a well known issue with the RAZR M.
Sent from my XT907 using Tapatalk
EDIT:
Code:
system \ bin \ MPdecision
Click to expand...
Click to collapse
Attack,
Thanks for the response and thanks for the clarification.
I found two instances of MPdecision, so that narrows it down.
Sorry, but answers always do tend to lead to more questions.....
What functionality do I lose by "disabling" it?
If it keeps the second core on, does that have a significant impact on battery life?
Does the governor have any impact on that?
Would other kernels make a difference?
FirePsych said:
Attack,
Thanks for the response and thanks for the clarification.
I found two instances of MPdecision, so that narrows it down.
Sorry, but answers always do tend to lead to more questions.....
What functionality do I lose by "disabling" it?
If it keeps the second core on, does that have a significant impact on battery life?
Does the governor have any impact on that?
Would other kernels make a difference?
Click to expand...
Click to collapse
MPdecision is qcomm's hot plugging service that keeps the second core off when its not needed by the system and turns it on when it is needed. By disabling MPdecision, you'll have better performance and slightly higher battery usage, but it's not very noticeable (battery usage will very on how you use your phone). Governor's have no impact on SOD's and all kernels for the Razr M are basically the same either stock or CM's both use the same MPdecision (which I believe to be the problem).
I could be totally wrong and you could have a hardware / software problem. But I know that when I was having this issue, I disabled MPdecision and the SOD's stopped.
Thanks,
I had read that the SOD had been reported elsewhere, but never saw any solutions. Just lots of folks replacing their phones.
I haven't had one in the last 24 hrs on the 12/08 CM nightly and flashed the 12/09 this morning.
I also made the MPdecisions change. We'll see if it sticks. I assume since it's a system file, I'll have to make the change every time I flash a new nightly or or new rom, but that's not a big deal.
Oh, and yes SOD is probably more accurate than "shutdown" because I've noticed that the led will flash if I've received a message, but I can't revive the phone, so obviously it's not complete shut down.
ATTACK said:
MPdecision is qcomm's hot plugging service that keeps the second core off when its not needed by the system and turns it on when it is needed. By disabling MPdecision, you'll have better performance and slightly higher battery usage, but it's not very noticeable (battery usage will very on how you use your phone). Governor's have no impact on SOD's and all kernels for the Razr M are basically the same either stock or CM's both use the same MPdecision (which I believe to be the problem).
I could be totally wrong and you could have a hardware / software problem. But I know that when I was having this issue, I disabled MPdecision and the SOD's stopped.
Click to expand...
Click to collapse
@ATTACK.
Thank you!
I hate to jynx myself, butthis seems to have done the trick. Only had 1 or 2 BSOD since your response and I think both times were because I forgot to make the change after flashing a new rom.
Happy Holidays
FP
This thread may have saved my phone. I keep waking up to find my phone with a blinking LED notification and me being unable to get the screen to turn on. I renamed the MPdecision file and I'll hope for the best. (^^)
Now that I've got the Moto X Pure Edition activated, I've been able to work out some of the kinks inherent using it as a daily driver. One noteworthy issue that remains is an odd bug where the device will completely lose connection to the Internet on both a WiFi and cellular data connection, usually after transitioning between types of connections. When this happens, an exclamation point is displayed next to the icon representing whichever connection is currently active and nothing is able to transmit data to or from the Internet or even my local network.
Rebooting the device always fixes the problem, but this issue is materializing a bit too often for my liking, which is usually once every time that I return to a WiFi network after being disconnected from one for some time (more testing may have to be done to confirm exactly what triggers it).
The device is running the stock rom (rooted) and the stock kernel along with the usual tweaks (ad-blocking, Xposed framework, audio fixes, etc.). Anybody seen this before or know what might be causing it?
UPDATE (3/1/2017)
Figured it out! The problem appears to have been caused by my failure to whitelist certain applications in PowerNap. After following the instructions found in the Moto X Pure Edition power optimization thread, the problem appears to have vanished. I don't know if it was the Google Services Framework, JavaTcmdHelper, Android System, or some combination of those that needed to be whitelisted, but the problem has vanished. At least one of those must be responsible for verifying the validity of an Internet connection in sleep mode, which would cause the device to become confused when it would wake up with a different connection that it hadn't verified (that's my theory at least).
At any rate, it is no longer an issue.
Update (Later on 3/1/2017)
Well, it looks like it might not be fixed so well after all. A couple hours after arriving home today, I went to use the device and saw the dreaded "!" next to the network indicator. Still, two days is longer than it's ever lasted before. I've cleared the cache and dalvik/ART cache to see if something in there might be gumming it up and will add another post to this thread if the problem returns.
Still an issue
Looks like it might not be fixed after all. I lost connection again the other day in a parking lot and once more today after getting home. Any ideas as to what could be causing this?
I just recently got my x pure. I've seen this issue on mine too.
Another one!
inkdaddy66 said:
I just recently got my x pure. I've seen this issue on mine too.
Click to expand...
Click to collapse
Interesting. Are you running the stock Rom? Rooted? Amplify/Greenify/PowerNap?
Bill720 said:
Interesting. Are you running the stock Rom? Rooted? Amplify/Greenify/PowerNap?
Click to expand...
Click to collapse
I'm unlocked and rooted. Running validus 7.1.1 ROM.
does your configuration look anything like this?
inkdaddy66 said:
I'm unlocked and rooted. Running validus 7.1.1 ROM.
Click to expand...
Click to collapse
That too is interesting. I'm running the stock Rom, (rooted) so we can probably eliminate that as a potential cause. Given how little reference there is to this on the web at large, the problem is probably caused by a common app or setting (or some kind of unfortunate combination) running on both of our phones.
All we need to do is figure out what kind of "unusual" stuff our devices have in common. I'll rattle off a list of software and settings that might be out of the ordinary or network-related; you tell me if you're running anything like it on your phone.
AdFree
A.R.I.S.E. audio
FolderSync
Ice Box (Motorola Update Service is the only frozen app)
TOTAL Wireless My Account App
Pebble, MyTracks, and Pebble MyTracks
SlingPlayer (this one sometimes wakelocks)
Titanium backup (I tried restoring some WiFi access points once, but it didn't work)
Xposed Framework with Amplify, Greenify, and Power Nap installed and configured as instructed in the Moto X Pure Edition battery life guide thread OP. I've also got MinMinGuard and YouTube AdAway.
As far as settings go, I've not got much in the way of unusual configurations. I enabled the system UI tuner to get the battery percentage and the extended developer options to try out multi-window, (and to change the animation scales to .5X) but everything in there is still pretty much stock.
Does your configuration have anything in common with mine?
Close, but no cigar
It got almost 8 days this time before it happened again. I thought that maybe switching to the legacy DHCP client had done the trick, but that was apparently not the case. Any ideas as to what could be causing the issue or how to fix it?
Or, if you're having the same problem, can you look at my list in the previous post and tell me if any of the software or settings are similar so that we can narrow down the cause?
I have had this problem appear about three times over my 13 months of ownership and all three times was when my bootloader was still locked (obviously running stock not rooted). Never found a solution except to reboot.i only unlocked and rooted my device about a month ago.
Anything familiar?
aybarrap1 said:
I have had this problem appear about three times over my 13 months of ownership and all three times was when my bootloader was still locked (obviously running stock not rooted). Never found a solution except to reboot.i only unlocked and rooted my device about a month ago.
Click to expand...
Click to collapse
Interesting. Between that, my findings, and the fact that @inkdaddy66 was having the problem on a non-Motorola Rom, I want to think that we can eliminate the Rom software as a cause. Did you see any familiar software on my "potential troublemakers" list up in post 6? I'm thinking that if we can find a common program or workflow, then we'll be able to narrow down the cause of the problem.
In the meantime, I'll try posting in the general Android troubleshooting forum here on XDA and see if anybody there has seen the problem or has any troubleshooting tips.
Bill720 said:
Interesting. Between that, my findings, and the fact that @inkdaddy66 was having the problem on a non-Motorola Rom, I want to think that we can eliminate the Rom software as a cause. Did you see any familiar software on my "potential troublemakers" list up in post 6? I'm thinking that if we can find a common program or workflow, then we'll be able to narrow down the cause of the problem.
In the meantime, I'll try posting in the general Android troubleshooting forum here on XDA and see if anybody there has seen the problem or has any troubleshooting tips.
Click to expand...
Click to collapse
Nothing used from your list except system UI tuner when I experienced the problems. That would leave either a ROM and/or hardware issue IMO.
Cause and effect differential diagnosis
aybarrap1 said:
Nothing used from your list except system UI tuner when I experienced the problems. That would leave either a ROM and/or hardware issue IMO.
Click to expand...
Click to collapse
Hmmm... That's also interesting, but I just don't see how system UI tuner could be harming anything. Do you have any other apps or settings at all that you think could be causing the issue?
If this were anything other than my primary, I'd hard reset and troubleshoot that way, but I don't exactly have the time to pull the rug out of an otherwise-working setup right now, so this is going to have to be done the hard way (or, in the case of hardware glitch, lived with).
At any rate, I discovered a new symptom earlier in the week. This time, Internet connection was lost, but only for WiFi, so the connection would actually fall back to Cellular and still continue to work. As before, toggling the connection had no effect, but rebooting the device "fixed" it. I thought maybe it was a fluke, since we'd had an AP hiccup over the weekend, (I refuse to reboot that thing because I'm going for an uptime record) but it happened again on Wednesday, so I'm not sure what to make of it.
Side-issue aside, I'm beginning to wonder if it's some kind of combination of network behavior and usage pattern that brings the issue about. It seems like if I stay within range of the WiFi network, no issue develops, but if I move out of its coverage and don't touch the phone for a while, that allows for ideal conditions under which to replicate the problem (sometimes). I haven't nailed down a consistent pattern yet, but the problem does emerge more often when I'm returning home than at other times. Any thoughts?
Update (3/24/2017; 12:32PM)
Scratch that last part about the issue only being triggered upon "arriving home." The problem happened again this morning, in the same general area. First, no WiFI, then, after resetting the connections, no cellular either. I captured a LogCat before rebooting this time though. Anyone want to take a crack at sifting through that to see if it offers any clues?
I lose cellular data, from time to time, I don't kow if I'm losing WiFi capability also, because I'm on the road when this happens.
It takes a reboot or switching in and out of airplane mode to regain data.
I have had this happen on TruPureXMM ROM and stock-rooted Marshmallow.
I have not spent much time on stock-unrooted, so i don't know if it would happen then, also.
Possible fix
Just to follow up on this again, I have finally reached the eighth day of uptime without the problem materializing, which is the longest that I was able to go before without it happening. This time, I went in to the developer options and disabled "Cellular data always active." I'd give it another couple days to know for sure, but if this sticks, then I think we might've found the fix!
pizza_pablo said:
I lose cellular data, from time to time, I don't kow if I'm losing WiFi capability also, because I'm on the road when this happens.
It takes a reboot or switching in and out of airplane mode to regain data.
I have had this happen on TruPureXMM ROM and stock-rooted Marshmallow.
I have not spent much time on stock-unrooted, so i don't know if it would happen then, also.
Click to expand...
Click to collapse
If your trouble is isolated to just one connection and/or cycling the connection brings it back, then the issue you are experiencing is unrelated to the one described in this thread.
Bill720 said:
Just to follow up on this again, I have finally reached the eighth day of uptime without the problem materializing, which is the longest that I was able to go before without it happening. This time, I went in to the developer options and disabled "Cellular data always active." I'd give it another couple days to know for sure, but if this sticks, then I think we might've found the fix!
If your trouble is isolated to just one connection and/or cycling the connection brings it back, then the issue you are experiencing is unrelated to the one described in this thread.
Click to expand...
Click to collapse
Cellular data always active should never be on (it's disabled in stock rom), except if you have VoLTE only with no fallback to 3G or 2G (Jio is the only provider that comes to mind, but this phone doesn't support their service anyway) or otherwise unusual scenarios I can't really think of.
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
Always on is not necessarily a good thing. Reality is that when you lose or turn off WiFi, mobile data should only be delayed only by a second or two. There is no real benefit to having it on except for maybe VOLTE.
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
Actually, it's a battery killer more than anything else... It keeps cellular data active even when on WiFi.
It is possible it's a tower thing though. I have noticed at this one hotel I stay at frequently people tell me they call and it rings or just goes to voicemail even though I have good signal. After investigating it a bit, I'm in a spot that has nearly identical signal strength from 3 towers and it's a metro area so there are 4+ bands accessible... I've seen times watching LTE Discovery where it keeps switching bands and towers for 30 to 120 seconds or so, like it can't make up it's mind what to talk to because it's confused, then it locks on for a while before it starts it's cycle again. During those cycles I think is when people can't call me, can't really say if it affects internet or not since I tend not to use my phone too much in the evenings when I'm on the road (usually on laptop).
Uptime record, but... it's back
acejavelin said:
Cellular data always active should never be on (it's disabled in stock rom), except if you have VoLTE only with no fallback to 3G or 2G (Jio is the only provider that comes to mind, but this phone doesn't support their service anyway) or otherwise unusual scenarios I can't really think of.
Click to expand...
Click to collapse
Interesting. I thought for sure that I had the default settings checked in there, but maybe I did change it early on and just forgot. Either way, waiting an extra five seconds to establish a data connection isn't that huge of a deal for me, so I'll leave it off anyway in exchange for battery life when the signal's poor.
At any rate, however, the problem has returned. I was just a few hours short of 9 days of uptime and really thought that I was out of the woods with this problem, but it has returned once again upon returning into range of the home access point. Looks like we're back to the drawing board on this one.
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
So you're having the same problem too? That makes at least four of us now. Do you mind sharing what Rom and flashed tweaks (Xposed Framework, A.R.I.S.E. audio, root, etc.) you're using as well as any unusual software or settings? Anything in common with my list on page 1?
Bill720 said:
So you're having the same problem too? That makes at least four of us now. Do you mind sharing what Rom and flashed tweaks (Xposed Framework, A.R.I.S.E. audio, root, etc.) you're using as well as any unusual software or settings? Anything in common with my list on page 1?
Click to expand...
Click to collapse
I think we've established that my issue is different, but it has occurred on TruPureXMM and stock but rooted Marshmallow, both with Substratum, Xposed (Gravity Box only) and Viper Atmos.
Same as you =Titanium Backup
*another* new strategy (sigh)
For this week's shot in the dark, I'm going to try manually switching WiFi off before I leave anyplace covered by an access point. Since the problem seems to occur most often when connected to WiFi or when connecting to it, maybe this will make some kind of a difference.
pizza_pablo said:
I think we've established that my issue is different, but it has occurred on TruPureXMM and stock but rooted Marshmallow, both with Substratum, Xposed (Gravity Box only) and Viper Atmos.
Same as you =Titanium Backup
Click to expand...
Click to collapse
I see now; my mistake.