Database Users

Sleep of death: possible solution?

A question:
Those of you who are using nook color and CM 7.1 and having sleep of death issue, even adjusting wi fi sleep.
Have you ever tried to disable mobile data?
In Wireless & Networks > Mobile Networks > Uncheck "Data enabled".
I think the problem is that when the system tries to switch from Wi Fi to (non existing) mobile, it causes the sleep of death.
This solved the problem, at least for me!

The sleep of death issue was a known issue where the wifi was having a wake lock break where the resume handler hung up with the wifi driver for the nook color. This issue has now been addressed and fixed in more recent builds of cyanogenMod for the nook color. You can research the fix we did a few months ago in this thread here. This fix is now included with more recent builds for cyanogenmod. http://forum.cyanogenmod.com/topic/32316-sleep-of-death-debugging/
You should update to a newer cyanogenMod build for your nook color, the latest stable build is 7.2. To fully rid yourself of this problem do not layer in your new build over the top of the last build you have on your SD card or on your eMMC, however you are running cyanogenMod on your nook. Other-words you will need to wipe both the data and the dalvik caches. Make sure to back up your settings and applications with a backup app like nandroid or with another back up app, like Titanium backup before you do this so you will not lose your apps and settings.

So what you'really saying is that I have to wipe my *perfectly functioning* version to a new one? Did I get it right?
Because as I said, with that method in place,there's no issue right now.

As long as your happy. :silly: You do know that a nandroid backup will give you your settings exactly they way you had them on your earlier build don't you? Right down to your launcher screen and icons, and all of your widgets on it, just takes 5 minutes.
It take a perfect snapshot of your launcher and all of its settings and other apps on it through clockworkmod. Plus cyanogenMod 7.2 is soooo smooth and snappy, no wi fi problems after you wipe and reinstall that nandroid backup.

I find that SoD happens when I test development on it. Sometime it just stops loading right in the middle and it freezes. The only way I've found to get out of it is to reboot the nook.

meteorrock said:
As long as your happy. :silly: You do know that a nandroid backup will give you your settings exactly they way you had them on your earlier build don't you? Right down to your launcher screen and icons, and all of your widgets on it, just takes 5 minutes.
It take a perfect snapshot of your launcher and all of its settings and other apps on it through clockworkmod. Plus cyanogenMod 7.2 is soooo smooth and snappy, no wi fi problems after you wipe and reinstall that nandroid backup.
Click to expand...
Click to collapse
i've been having SOD on the 7/30/12 (and previous) mirage kangs, which include the fixed kernel (right?). i'll try what you said, i'll create a nandroid backup, format system/data/cache, restore from backup, and see if i continue to get SOD.

jeff.p said:
i've been having SOD on the 7/30/12 (and previous) mirage kangs, which include the fixed kernel (right?). i'll try what you said, i'll create a nandroid backup, format system/data/cache, restore from backup, and see if i continue to get SOD.
Click to expand...
Click to collapse
still getting SOD

Archbob said:
I find that SoD happens when I test development on it. Sometime it just stops loading right in the middle and it freezes. The only way I've found to get out of it is to reboot the nook.
Click to expand...
Click to collapse
That is not SOD. That is just a normal lockup. SOD means Sleep of Death. It is when the device will not wake up properly after being in deep sleep with wifi left on.
BTW, for those still experiencing SOD even with the fixed kernel, you may want to install the patched wifi module found here:
http://d01.megashares.com/?d01=8VPCE7N
For more information about SOD, look at item A5 in my tips thread linked in my signature.

leapinlar said:
That is not SOD. That is just a normal lockup. SOD means Sleep of Death. It is when the device will not wake up properly after being in deep sleep with wifi left on.
BTW, for those still experiencing SOD even with the fixed kernel, you may want to install the patched wifi module found here:
http://d01.megashares.com/?d01=8VPCE7N
For more information about SOD, look at item A5 in my tips thread linked in my signature.
Click to expand...
Click to collapse
thanks for the links. i will check them out. i'm beginning to think that one of my apps is causing my SOD, bc i left the nook (fresh install of cm 7.2 mirage) overnight with wifi on and it woke right up.

meteorrock said:
As long as your happy. :silly: You do know that a nandroid backup will give you your settings exactly they way you had them on your earlier build don't you? Right down to your launcher screen and icons, and all of your widgets on it, just takes 5 minutes.
It take a perfect snapshot of your launcher and all of its settings and other apps on it through clockworkmod. Plus cyanogenMod 7.2 is soooo smooth and snappy, no wi fi problems after you wipe and reinstall that nandroid backup.
Click to expand...
Click to collapse
After MONTHS of battling without updating to 7.2, I finally followed your advice and now I'm restoring the backup. Hope it works! Sorry if my answer wasn't very polite! :fingers-crossed::good:

[Q] KitKat to Lollipop - the phone is unusable (huge battery drain and sys errors)

Hi everyone,
Until recently I've been using a KitKat based ROM and I was pretty OK with how my NOTE 3 SM-9005 was performing. However, a few days ago I decided to try a Lollipop based ROM and the problems started. I had similar problems with 3 different ROMs with great reviews. My battery went, for example, from 100% to 15% in ONE HOUR while streaming from YouTube. It never did that before. Also, It sometimes gives a "system stopped responding" error or something like that (it's like the equivalent of explorer.exe crashing on Windows) and after a few seconds it starts working again. Other system apps crash as well every now and then and sometimes the phone just decides to restart by itself.
I initially used Philz recovery and after the initial errors I switched to TWRP and started from scratch. I completely wiped my system internal space before flashing and, of course, I wiped dalvik cache and cache before and after flashing the ROM. I only used recommended gapps. Also, I did not restore any system apps. I started from scratch after the installation and the problem is the same.
To be more exact, I tries flashing so far the following ROMS, experiencing more or less the same problems on each:
temasek's UNOFFICIAL CM12.1
AryaMod V5.4 TW Lollipop Official BOB6
BlissPop 3.5 Unofficial
I also tried the Dirty Unicorns v9.4 ROM from the Original Android Development section but this one went on a reboot loop initially after the first restart so it never really even installed.
At this point I believe I might have done something that I should't have, but it seems strange because this is not the first time I am flashing a new ROM and I never had problems in the past. Also, my NOTE 3 SM-9500 did not have any problem on my previous KitKat ROM. Did I miss something? Should I have used another kernel? If I understood correctly, the ROMs come with a recommended kernel already. If this is not the problem, what could it be? Should I have done any additional thing before flashing a Lolipop ROM after using a KitKat ROM?
I now installed an app for trying to find out what exactly drains my battery but this is not the only problem. The system itself is really unstable.
I would really appreciate some help, suggestions, or opinions. I really don't know what else should I be doing at this point.
Thanks a lot!

Apparently is the media server eating all that battery (currently 68%).
I will format the SD card hoping this fixes the issue.....but could this have something to do with the system error and, sometimes, restarts?

Well I really don't know what to say! A lot of people report battery problems on 5.0 just because they didn't wipe the phone while coming from KK! But you did, so that's no go. Battery life on LP is much better than KK for me, at least 20% better if not more. And I didn't face any system crashing issues either! Don't really know what's going on with you mate.

Someone suggested that maybe I shoud update the bootloader and modem to a Lollipop version but I really couldn't find any info on how to do that.
Formatting the SD card just slightly reduced the battery drain. The phone is still discharging like crazy. Any suggestion on how to update the bootloader and modem?
Thank you.

Most stable Lollipop/Marshmallow ROM?

Hi! I think I've tried every Lollipop/Marshmallow ROM out there, but I haven't found one as stable as KitKat ROMs (CM11/Stock). I just want a Lollipop/Marshmallow ROM that doesn't hang every time I open YouTube from recents (many apps suffer of that too), and with working WiFi (had this problem with CM13), and with decent battery life. CM13 is actually one of the most stable ROMs I've tried, but it had serious WiFi problems (it simply disconnects from the WiFi and then reconnects saying it doesn't have internet access, very annoying), some kind of TV-like static when booting and sometimes when unlocking the phone, and the recents cards sometimes got cut off (though this is not really a deal breaker). The only Marshmallow ROMs I haven't tried are BeanStalk and Mokee because they are based on CM, so I supposed they have the same problems. So, what's the most stable Lollipop/Marshmallow ROM you have tried? And can that ROM be used as daily driver?
Thanks!
Sorry for my English lol.

Which other Roms have you tried?

MuhammadBilal said:
Which other Roms have you tried?
Click to expand...
Click to collapse
Exodus (5.0, will try 5.1), BlissPop, DirtyUnicorns, dhacker's unofficial CM12, Mokee (5.1), ResurrectionRemix, unofficial CM13...
EDIT: Tried Exodus 5.1, really slow.

MoKee
So far, so good (It's only been 24 hours since I've installed it) on the 17-01-29 build of Mokee here
Wifi has been solid with no issues, rom seems stable, and YouTube ran fine from recents.
Update: Had strange problem with downloading email attachments with both gmail and Yahoo mail. Back to stock KK for the time being.
Update: Turns out the above email problems had to do with permissions.

beeewell said:
So far, so good (It's only been 24 hours since I've installed it) on the 17-01-29 build of Mokee here
Wifi has been solid with no issues, rom seems stable, and YouTube ran fine from recents.
Update: Had strange problem with downloading email attachments with both gmail and Yahoo mail. Back to stock KK for the time being.
Click to expand...
Click to collapse
It doesn't even boot here, first time it booted but it said that encrypting my device failed (WTF?) and then rebooted to do a factory reset, and it wiped the system partition. xD
I installed it again without Gapps and now it won't do anything, it justs sits there in the bootanimation for several minutes and then reboots. Perhaps​ I didn't downgrade correctly? How did you downgrade? I used RSD Flasher, and it has worked fine for me in the past.

trivialPotato said:
It doesn't even boot here, first time it booted but it said that encrypting my device failed (WTF?) and then rebooted to do a factory reset, and it wiped the system partition. xD
I installed it again without Gapps and now it won't do anything, it justs sits there in the bootanimation for several minutes and then reboots. Perhaps​ I didn't downgrade correctly? How did you downgrade? I used RSD Flasher, and it has worked fine for me in the past.
Click to expand...
Click to collapse
It took me awhile to find the procedure and files that I used to downgrade/upgrade, but I finally did. Thanks to Nobe1976, this method of going back and forth from KK to JB doesn't require a PC; There are 2 zip files that you can flash w/ TWRP to go back and forth. Here's the procedure and file links: http://www.droidrzr.com/topic/50096-how-tomobile-downgrader-flash-back-10-09-14-14/
I too thought Exodus was stable, but slow. I liked using MoKee 5.1, but I had an annoying problem with it that I couldn't solve: Every time I picked up my phone, there was a notification to sign back onto my WiFi network. It did so without asking for any credentials, but it got too annoying for me.
Right now, I'm using PacMan Rom (4.4.4), and it's been performing very well and is stable. Here's the link in case you wanna try: https://s.basketbuild.com/devs/pacman/moto_msm8960/KK/release

beeewell said:
It took me awhile to find the procedure and files that I used to downgrade/upgrade, but I finally did. Thanks to Nobe1976, this method of going back and forth from KK to JB doesn't require a PC; There are 2 zip files that you can flash w/ TWRP to go back and forth. Here's the procedure and file links: http://www.droidrzr.com/topic/50096-how-tomobile-downgrader-flash-back-10-09-14-14/
I too thought Exodus was stable, but slow. I liked using MoKee 5.1, but I had an annoying problem with it that I couldn't solve: Every time I picked up my phone, there was a notification to sign back onto my WiFi network. It did so without asking for any credentials, but it got too annoying for me.
Right now, I'm using PacMan Rom (4.4.4), and it's been performing very well and is stable. Here's the link in case you wanna try: https://s.basketbuild.com/devs/pacman/moto_msm8960/KK/release
Click to expand...
Click to collapse
Thank you so much! That will save me so much headaches lol.
I'm using lastest CM11 snapshot, working fine, but I find the battery doesn't last as much as in CM12.1.
EDIT: I'm writing from Mokee 6.0! That method for downgrading works flawlessly!
Mokee feels better than CM12.1 except by that TV-like interference when you unlock the device, and I haven't tried the WiFi, but it looks okay.

Thing to remember while reading all of the below, I have an XT905, with a JBBL.
I'm currently using "cm-13.0-20161205-ilichva-xt907_jbb.zip" for my daily. The only repeated "fails" I have is where WiFi will disconnect, however, it only happens if I am not using it and the phone is asleep. One thing I have noticed is that this is the only ROM that actually does go into deep sleep for me. I'm only on Wifi at home for extended periods (ie when phone goes to sleep). This may be the reason the other ROMs don't loose WiFi, because they don't go into deep sleep for me. My Wifi disconnects, and never is connected without internet. I just go into Wifi, select my network and say connect, and its all good again.
Previously (a few years back) I was using BlissPop (Lollipop), but did not use the latest build. I had better luck with "BlissPop-v3.9-moto_msm8960_jbbl-OFFICIAL-20150829-1751.zip"
Others I have used (Lollipop) and found pretty stable (ie used as daily for some time) were:
CARBON-5.1.1-Final-moto_msm8960_jbbl.zip
Resurrection-Remix-LP-v5.5.8-moto_msm8960_jbbl.zip
and for KitKat
LS-KK-MileStone-3.2-moto_msm8960_jbbl.zip
With the CM13 ROM I have a 64GB SDCard, F2FS cache partition, Xposed, Viper, a Linux Swap Partition (512mb) and personally find it to be the most stable ROM I have used (apart from WiFi) on the phone. Some of the Lollipop (bliss pop included) could not run my live wallpaper (Celestial Bodies). I have also noticed that at least one app using the CPU (a Solitaire game attempting to find a winnable deal manually) actually runs a lot faster in CM13 than in the others.
If YouTube bothers you, maybe you should try the alternatives such as New Pipe or OGYouTube etc etc. Actually, I just tried YouTube from the recents,and it worked fine for me.
As for the TV Static on boot (just before animation) I have had that since I first unlocked the bootloader; I thought It was normal. It has been independent of any ROMs and it happens for me on every ROM.

Mokee 5.1
Sorry for going off-topic but would any of you guys happen to have a copy of the last LP Mokee build that was released on 4PDA ?
MK51.1-xt907_jbbl-20160420-ilichva.zip
The link is unfortunately dead and I can't find a mirror anywhere. I'd like to save a copy just in case anyone asks in the future. If any of you have, would you please share privately with me? Thanks a lot!

DiamondJohn said:
Thing to remember while reading all of the below, I have an XT905, with a JBBL.
I'm currently using "cm-13.0-20161205-ilichva-xt907_jbb.zip" for my daily. The only repeated "fails" I have is where WiFi will disconnect, however, it only happens if I am not using it and the phone is asleep. One thing I have noticed is that this is the only ROM that actually does go into deep sleep for me. I'm only on Wifi at home for extended periods (ie when phone goes to sleep). This may be the reason the other ROMs don't loose WiFi, because they don't go into deep sleep for me. My Wifi disconnects, and never is connected without internet. I just go into Wifi, select my network and say connect, and its all good again.
Previously (a few years back) I was using BlissPop (Lollipop), but did not use the latest build. I had better luck with "BlissPop-v3.9-moto_msm8960_jbbl-OFFICIAL-20150829-1751.zip"
Others I have used (Lollipop) and found pretty stable (ie used as daily for some time) were:
CARBON-5.1.1-Final-moto_msm8960_jbbl.zip
Resurrection-Remix-LP-v5.5.8-moto_msm8960_jbbl.zip
and for KitKat
LS-KK-MileStone-3.2-moto_msm8960_jbbl.zip
With the CM13 ROM I have a 64GB SDCard, F2FS cache partition, Xposed, Viper, a Linux Swap Partition (512mb) and personally find it to be the most stable ROM I have used (apart from WiFi) on the phone. Some of the Lollipop (bliss pop included) could not run my live wallpaper (Celestial Bodies). I have also noticed that at least one app using the CPU (a Solitaire game attempting to find a winnable deal manually) actually runs a lot faster in CM13 than in the others.
If YouTube bothers you, maybe you should try the alternatives such as New Pipe or OGYouTube etc etc. Actually, I just tried YouTube from the recents,and it worked fine for me.
As for the TV Static on boot (just before animation) I have had that since I first unlocked the bootloader; I thought It was normal. It has been independent of any ROMs and it happens for me on every ROM.
Click to expand...
Click to collapse
The TV-like static seems to be something with the JBBL, it happens even in recovery for me (when the recovery locks and turns off the screen). About the WiFi, it disconnected even if I was playing a game or using the internet, but I live in a place where I don't have WiFi anymore, so it's not a problem.
Indeed, Mokee 6.0 and CM13 are the most stable ROMs I've tried, even more than CM11, except for the bugs said above, even the battery lasts more.
BTW, how do you increment swap? I've tried several methods, but it still shows 256MB.

trivialPotato said:
The TV-like static seems to be something with the JBBL, it happens even in recovery for me (when the recovery locks and turns off the screen).
Click to expand...
Click to collapse
I only get it when I reboot, but get it every time.
trivialPotato said:
About the WiFi, it disconnected even if I was playing a game or using the internet, but I live in a place where I don't have WiFi anymore, so it's not a problem.
Click to expand...
Click to collapse
I personally have only seen it happen when the I wake the device up. Never has it occurred while I am using it.:angel: Last night I was searching for another thing in Xposed, and I saw a lot of Wifi type modules. Though most were about turning wifi off when the screen goes off; but I wasn't looking for Wifi stuff, so maybe you could find something that helps.
trivialPotato said:
Indeed, Mokee 6.0 and CM13 are the most stable ROMs I've tried, even more than CM11, except for the bugs said above, even the battery lasts more.
Click to expand...
Click to collapse
I tried Mokee, and I cant remember why, but it wasn't OK as a daily for me. To be honest, I would find it hard to go back to a ROM (ie less than MM) that does not have privacy guard. I also forgot to mention on my phone I have Adaway and Lucky Patcher and > 10 boot scripts (such as swap, IO optimisations, trim command, disabling media scanner on boot ... etc etc etc)
trivialPotato said:
BTW, how do you increment swap? I've tried several methods, but it still shows 256MB.
Click to expand...
Click to collapse
I am guessing by "increment" you really mean implement? Assuming that, I use a boot script. Currently I use a swap partition, so, for that I:
1. create a linux swap partition on the SDCard using Minitool Partition Wizard
2. Put the card into my phone, boot it and Find out the partition details (eg "/dev/block/mmcblk1p2" on my card now)
3. create a boot script to enable it on boot. The meat of the script is:
Code:
swapon /dev/block/mmcblk1p2;
Previously I have used a swap file, which is actually more complex. Something like:
Code:
location=/mnt/media_rw/sdcard1/data/local/tmp;
file_name=swapfile.dat;
desiredsizemb=512;
dd if=/dev/zero of=$location/$file_name bs=1048576 count=$desiredsizemb;
swapon -p 16000 $location/$file_name;
Hope the above helps, and let me know if you get it working.

DiamondJohn said:
I only get it when I reboot, but get it every time.
I personally have only seen it happen when the I wake the device up. Never has it occurred while I am using it.:angel: Last night I was searching for another thing in Xposed, and I saw a lot of Wifi type modules. Though most were about turning wifi off when the screen goes off; but I wasn't looking for Wifi stuff, so maybe you could find something that helps.
I tried Mokee, and I cant remember why, but it wasn't OK as a daily for me. To be honest, I would find it hard to go back to a ROM (ie less than MM) that does not have privacy guard. I also forgot to mention on my phone I have Adaway and Lucky Patcher and > 10 boot scripts (such as swap, IO optimisations, trim command, disabling media scanner on boot ... etc etc etc)
I am guessing by "increment" you really mean implement? Assuming that, I use a boot script. Currently I use a swap partition, so, for that I:
1. create a linux swap partition on the SDCard using Minitool Partition Wizard
2. Put the card into my phone, boot it and Find out the partition details (eg "/dev/block/mmcblk1p2" on my card now)
3. create a boot script to enable it on boot. The meat of the script is:
Code:
swapon /dev/block/mmcblk1p2;
Previously I have used a swap file, which is actually more complex. Something like:
Code:
location=/mnt/media_rw/sdcard1/data/local/tmp;
file_name=swapfile.dat;
desiredsizemb=512;
dd if=/dev/zero of=$location/$file_name bs=1048576 count=$desiredsizemb;
swapon -p 16000 $location/$file_name;
Hope the above helps, and let me know if you get it working.
Click to expand...
Click to collapse
Mokee has be running pretty solid here, I'll try CM13 and/or BeanStalk in a few days, though.
About swap, if I run "free" in the Terminal it shows it has swap memory, and I tried several methods (well, apps) to increment it but no luck. I'll try yours in a few days.
About the WiFi and the TV-like static, I bet is some difference between xt905 and xt907.

trivialPotato said:
Mokee has be running pretty solid here, I'll try CM13 and/or BeanStalk in a few days, though.
About swap, if I run "free" in the Terminal it shows it has swap memory, and I tried several methods (well, apps) to increment it but no luck. I'll try yours in a few days.
About the WiFi and the TV-like static, I bet is some difference between xt905 and xt907.
Click to expand...
Click to collapse
Well, the swap you currently see is ZRam, which is a compressed partition of memory used as a swap partition. ie not a file or physical partition on an sdcard (as I use above, in addition to ZRam). To increase ZRam, you loose available memory. That can be simply changed with the following lines:
Code:
echo 1 > /sys/block/zram0/reset;
OR
swapoff /dev/block/zram0;
echo "201326592" > /sys/block/zram0/disksize;
mkswap /dev/block/zram0;
swapon /dev/block/zram0;
The number is 1024*1024*target_size (MB eg 600). I think you have to do it at boot time or you end up with device or resource busy messages.
Or you could use Kernel Adiutor - Virtual Memory
That actually reminds me, one bug I have noticed on all the CM13 ROMs I tried, was that the init.d did not work, I had to use Kernel Adiutor to implement it; and I have a lot of scripts.

Currently running the new Lineage ROM http://forum.xda-developers.com/showthread.php?t=3577746. Thanks to Ilichva...
So far, so good !!! Performing very well with no issues found yet. :thumbup:

It still has the WiFi disconnecting when asleep for me.

beeewell said:
Currently running the new Lineage ROM http://forum.xda-developers.com/showthread.php?t=3577746. Thanks to Ilichva...
So far, so good !!! Performing very well with no issues found yet. :thumbup:
Click to expand...
Click to collapse
Performing well here, too! It has the same bugs CM13 had, but I feel is a bit snappier.

Is it just me, or is the default swappiness set at 100? (cat /proc/sys/vm/swappiness)
I actually tried lowering it to the android default of 60, and the ROM felt less "snappy", so put it back at 100

DiamondJohn said:
Is it just me, or is the default swappiness set at 100? (cat /proc/sys/vm/swappiness)
I actually tried lowering it to the android default of 60, and the ROM felt less "snappy", so put it back at 100
Click to expand...
Click to collapse
Indeed, is set at 100.

Possible Wifi fix?
trivialPotato said:
I just want a Lollipop/Marshmallow ROM ... and with working WiFi (had this problem with CM13), and with decent battery life. CM13 is actually one of the most stable ROMs I've tried, but it had serious WiFi problems (it simply disconnects from the WiFi and then reconnects saying it doesn't have internet access, very annoying).
Click to expand...
Click to collapse
DiamondJohn said:
...I'm oly on Wifi at home for extended periods (ie when phone goes to sleep). This may be the reason the other ROMs don't loose WiFi, because they don't go into deep sleep for me. My Wifi disconnects, and never is connected without internet. I just go into Wifi, select my network and say connect, and its all good again.
Click to expand...
Click to collapse
I have made a change to build.prop, which APPEARS to have bettered my Wifi stability.
Now, its only been a few hours, so its pretty early to say :fingers-crossed: it has definitely fixed it, but normally within this time, I would of expected to loose my Wifi connection, but it hasn't. :highfive:
Also, the change I made, I have read is actually only set at build time and thereby built into the ROM and not read from the build.prop.
The build.prop setting is: wifi.supplicant_scan_interval. My RAZR had it set to 30, while my N5 was set to 15. I have set it down to 5 (for testing purposes ) Searching the net will bring up heaps of explanation of what the setting is for (and also info saying its only a build time property)
So in summary, I have set the following build.prop
Code:
wifi.supplicant_scan_interval=5
And my WiFi has been solid for the past 3 hrs (normally in sleep except for being woken every 10 minutes to check its still ok ). Let me know if it works for you.

DiamondJohn said:
I have made a change to build.prop, which APPEARS to have bettered my Wifi stability.
Now, its only been a few hours, so its pretty early to say :fingers-crossed: it has definitely fixed it, but normally within this time, I would of expected to loose my Wifi connection, but it hasn't. :highfive:
Also, the change I made, I have read is actually only set at build time and thereby built into the ROM and not read from the build.prop.
The build.prop setting is: wifi.supplicant_scan_interval. My RAZR had it set to 30, while my N5 was set to 15. I have set it down to 5 (for testing purposes ) Searching the net will bring up heaps of explanation of what the setting is for (and also info saying its only a build time property)
So in summary, I have set the following build.propAnd my WiFi has been solid for the past 3 hrs (normally in sleep except for being woken every 10 minutes to check its still ok ). Let me know if it works for you.
Click to expand...
Click to collapse
Will try this next weekend (I don't have WiFi right now). I hope it works lol.
EDIT: It didn't. :crying:

Can't turn wifi on...

Hi, I'm running lineage os, I can't turn wifi on, it is just saying "Turning WiFi on"

Prob a bug. My n5 had similar issue.... Turned out board was bad. I think the wifi chip had a broken solder joint. Because it would say "turning on" and never complete. I reflashed a hundred ROMs, and other recoveries including CAF. I think this happens to a lot of devices after they've been dropped 30 or 40 times there are small micro fractures each time until it causes a break in the connection somewhere.
But you just gave me a good idea I think I'm going to try to Reflow the board in the old oven

Etheralrealm said:
Hi, I'm running lineage os, I can't turn wifi on, it is just saying "Turning WiFi on"
Click to expand...
Click to collapse
Did you have the problem before flashing Lineage? If not its almost certainly a bug in the rom. If they have a support thread you could try getting help there or you could flash a different rom and see if the problem persists.

jhs39 said:
Did you have the problem before flashing Lineage? If not its almost certainly a bug in the rom. If they have a support thread you could try getting help there or you could flash a different rom and see if the problem persists.
Click to expand...
Click to collapse
sorry it took me so long, still having the problem, and no, it was perfectly fine until lineage.

This has happened to me about 7 or 8 times running 7.1.1 lineage. Look and see what your mac address is under configure wifi, mine changes to 02:00:00:00:00:00 when this happens to me. I have found posts about the problem but no real solution. The only way I have gotten it working again is by wiping the data partition and doing a clean flash, or flashing a backup I made while it was working. It drives me mad, I thought it might be a hardware problem at first because it started with a replacement device, but I feel like it must be software as I can fix it with a clean flash.
Sent from my Nexus 6P using Tapatalk

Etheralrealm said:
Hi, I'm running lineage os, I can't turn wifi on, it is just saying "Turning WiFi on"
Click to expand...
Click to collapse
I doubt this is a bug. Are you on the latest nightly? If you are running TWRP, start by wiping both dalvik and cache and reboot. There are LOS dedicated forums here, and this type of Wi-Fi issue would be a complete bust and I just don't see it. It could also be with how you installed LOS. The instructions are clear about fully wiping the device beforehand. I have been running LOS on my N7 for months, updating with weeklies and have never had a WiFi issue. Reddit has some decent forums you could ask around in as well.

ive been running it on my device since about november, worked until about a month ago, just been using data, tried wiping and i did a full wipe when i installed it. I went back to my january 30th build (oldest build i still had on my pc), running fine. No problems.

Here is the January 30th build, ready to flash with TWRP. Hope you have the same luck as me.
https://drive.google.com/file/d/0B9cTDZV2zbsvelUyMHJSXzlSU3c/view?usp=sharing
Cause I'm not taking chances I'm NOT responsible for any damages.

Workaround for stock ROM

I've been using Stock ROM since now and it lags way too much for me, my friends on Stock facing same issues, idk which custom ROM to go to as there's just so many ROMs with different bugs in them. Athene is my daily driver i don't wanna lose it by installing a crappy ROM. Please help.
P.S. I'm just a noob in flashing. Please someone send a link for first time installing of custom ROM. Thanks.

mayank.bhola1 said:
I've been using Stock ROM since now and it lags way too much for me, my friends on Stock facing same issues, idk which custom ROM to go to as there's just so many ROMs with different bugs in them. Athene is my daily driver i don't wanna lose it by installing a crappy ROM. Please help.
P.S. I'm just a noob in flashing. Please someone send a link for first time installing of custom ROM. Thanks.
Click to expand...
Click to collapse
LineageOS is a very stable and well-supported ROM with OTA updates as well.
As for installing a custom ROM maybe try reading the forum.

Try lineage or resurrection remix. They are the most stable. Till early this month I was using rr now shifted to lineage os

mayank.bhola1 said:
I've been using Stock ROM since now and it lags way too much for me, my friends on Stock facing same issues, idk which custom ROM to go to as there's just so many ROMs with different bugs in them. Athene is my daily driver i don't wanna lose it by installing a crappy ROM. Please help.
P.S. I'm just a noob in flashing. Please someone send a link for first time installing of custom ROM. Thanks.
Click to expand...
Click to collapse
Before flashing anything, have you tried the usual troubleshooting steps of wipe your cache and Dalvik in your recovery? Or if that didn't work, a factory reset (which may wipe your apps and app data)? You could also look into reflashing the stock ROM (e.g https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369) but before trying any of this, make sure your data is backed up.
I'm using InvictaOS (unofficial lineage based ROM) https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274 as my daily driver and it's been very stable, of course my usage will be different to yours, so your experience may vary. However, I get good battery life, watch YouTube at 1080p, calls are of good quality and the patched Moto camera works, as well as the system being smooth and responsive.
As with flashing any custom ROM, be aware that you'll have to unlock your bootloader from Motorola, which will void your warranty and also erase your data. Relocking your bootloader will not restore your warranty if you need to visit a service centre. Also, switching to a custom ROM will also result in device wipes so ensure you have a good backup before starting.

echo92 said:
Before flashing anything, have you tried the usual troubleshooting steps of wipe your cache and Dalvik in your recovery? Or if that didn't work, a factory reset (which may wipe your apps and app data)? You could also look into reflashing the stock ROM (e.g https://forum.xda-developers.com/mo...o-g4-plus-xt1640-43-athene-npj25-93-t3549369) but before trying any of this, make sure your data is backed up.
I'm using InvictaOS (unofficial lineage based ROM) https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274 as my daily driver and it's been very stable, of course my usage will be different to yours, so your experience may vary. However, I get good battery life, watch YouTube at 1080p, calls are of good quality and the patched Moto camera works, as well as the system being smooth and responsive.
As with flashing any custom ROM, be aware that you'll have to unlock your bootloader from Motorola, which will void your warranty and also erase your data. Relocking your bootloader will not restore your warranty if you need to visit a service centre. Also, switching to a custom ROM will also result in device wipes so ensure you have a good backup before starting.
Click to expand...
Click to collapse
Yes i wipe cache like once a week and have tried factory reset, but no luck . Stock Nougat still lags, my usage is mostly same as yours, calls and YouTube and texting. The only thing that bothers me is warranty. Thanks for replying.

mayank.bhola1 said:
Yes i wipe cache like once a week and have tried factory reset, but no luck . Stock Nougat still lags, my usage is mostly same as yours, calls and YouTube and texting. The only thing that bothers me is warranty. Thanks for replying.
Click to expand...
Click to collapse
That's fair enough, losing warranty is definitely a consideration. Re flashing the stock ROM as mentioned above shouldn't affect your warranty and may resolve issues with your system (which is possible if your problems are persisting after a factory wipe). What build of nougat are you on (under settings>about phone)?

Invicta os
mayank.bhola1 said:
I've been using Stock ROM since now and it lags way too much for me, my friends on Stock facing same issues, idk which custom ROM to go to as there's just so many ROMs with different bugs in them. Athene is my daily driver i don't wanna lose it by installing a crappy ROM. Please help.
P.S. I'm just a noob in flashing. Please someone send a link for first time installing of custom ROM. Thanks.
Click to expand...
Click to collapse
If you are searching for best custom rom try invictaos rom.
I am using invictaos from past 3 months and only one word I can say for this rom, it is just awesome rom,everything working superb in this rom,better battery 5 hours SOT,very smooth and finally no bug so go and try it.

echo92 said:
That's fair enough, losing warranty is definitely a consideration. Re flashing the stock ROM as mentioned above shouldn't affect your warranty and may resolve issues with your system (which is possible if your problems are persisting after a factory wipe). What build of nougat are you on (under settings>about phone)?
Click to expand...
Click to collapse
It's NPJ25.93-14, I'm waiting for the March Security Patch update, as other people are claiming better battery backup and to see if lag problem sorts out, if it won't hit my phone in 1 week or so then I'll move to one of your mentioned ROMs

I tried Unlocking Bootloader, entered the hex code in Motorola's website and it says my Bootloader can't be unlocked. I bought it from Amazon India (Retail package, no contract of any kind). Help me please.

mayank.bhola1 said:
I tried Unlocking Bootloader, entered the hex code in Motorola's website and it says my Bootloader can't be unlocked. I bought it from Amazon India (Retail package, no contract of any kind). Help me please.
Click to expand...
Click to collapse
Well, maybe that is for the best of your luck! I advise you to go to a service center and complain to them. Why? Because Motorola is BI*** and you are better off keeping your warranty stuck up their faces before trying anything else.
One more thing: when you are a noob, flashing a stock rom is not as safe as it sounds, you might end up without a sim slot or lose some other functionality.
Stick to your warranty and fight back the tedious way.

MK+2017 said:
Well, maybe that is for the best of your luck! I advise you to go to a service center and complain to them. Why? Because Motorola is BI*** and you are better off keeping your warranty stuck up their faces before trying anything else.
One more thing: when you are a noob, flashing a stock rom is not as safe as it sounds, you might end up without a sim slot or lose some other functionality.
Stick to your warranty and fight back the tedious way.
Click to expand...
Click to collapse
Ok I found that the hex code i was writing on, I cut off a string (low key my mistake) i unlocked bootloader, installed TWRP and now on lineage OS 14.1. It's working great, just a little worried for battery life but it's smooth af.

mayank.bhola1 said:
Ok I found that the hex code i was writing on, I cut off a string (low key my mistake) i unlocked bootloader, installed TWRP and now on lineage OS 14.1. It's working great, just a little worried for battery life but it's smooth af.
Click to expand...
Click to collapse
Great, I'm on Lineage OS, too
A generic battery saver: disable adaptive brightness and lower brightness only to the level you need. A full charge that way - with me using both WiFi and LTE - lasts a little more than 48 hours.
One last thing: please do a full backup from TWRP. Select all partitions you see available. Copy the resulting backup folder from SDCard to PC in a safe location. Do not modify further unless you really really can't breathe without it.

echo92 said:
Before flashing anything, have you tried the usual troubleshooting steps of wipe your cache and Dalvik in your recovery? Or if that didn't work, a factory reset (which may wipe your apps and app data)? You could also look into reflashing the stock ROM (e.g https://forum.xda-developers.com/mo...o-g4-plus-xt1640-43-athene-npj25-93-t3549369) but before trying any of this, make sure your data is backed up.
I'm using InvictaOS (unofficial lineage based ROM) https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274 as my daily driver and it's been very stable, of course my usage will be different to yours, so your experience may vary. However, I get good battery life, watch YouTube at 1080p, calls are of good quality and the patched Moto camera works, as well as the system being smooth and responsive.
As with flashing any custom ROM, be aware that you'll have to unlock your bootloader from Motorola, which will void your warranty and also erase your data. Relocking your bootloader will not restore your warranty if you need to visit a service centre. Also, switching to a custom ROM will also result in device wipes so ensure you have a good backup before starting.
Click to expand...
Click to collapse
How much screen on time you get?? I am using Resurrection Remix. It gives me about 3-3.5 hours of sreen on time.

sanjaybaidya said:
How much screen on time you get?? I am using Resurrection Remix. It gives me about 3-3.5 hours of sreen on time.
Click to expand...
Click to collapse
With my usage pattern, I get typically 4-4.5 hours.
This includes:
Calls, texts, and brief Whatsapp usage
Browsing XDA, reddit, instagram
Youtube over 4G/LTE at 1080p (with a slightly weak mobile signal), which is my main usage.
This is with ambient display set to 100 ms wakeup, and 2 sec on time. General brightness at about 25 %. EX Kernel manager used to set maximum number of big cores to 2, I/O manager set to zen with 256 kB readahead buffer.
Of course, your experience may vary, though I've always had good battery life with Invicta.

echo92 said:
With my usage pattern, I get typically 4-4.5 hours.
This includes:
Calls, texts, and brief Whatsapp usage
Browsing XDA, reddit, instagram
Youtube over 4G/LTE at 1080p (with a slightly weak mobile signal), which is my main usage.
This is with ambient display set to 100 ms wakeup, and 2 sec on time. General brightness at about 25 %. EX Kernel manager used to set maximum number of big cores to 2, I/O manager set to zen with 256 kB readahead buffer.
Of course, your experience may vary, though I've always had good battery life with Invicta.
Click to expand...
Click to collapse
Did you underclock your processor??

sanjaybaidya said:
Did you underclock your processor??
Click to expand...
Click to collapse
Nope, stock core speeds (think the big cores run up to 1651 Mhz, little cores at 1200 Mhz), just capped the maximum number of big cores to 2. Besides, the interactive governor will likely pick the speeds appropriate for the task, I imagine. In fact, I recall having good battery life even with the stock kernel settings and all cores available, just with these settings my device runs cooler in my experience. Again, the beauty of EX Kernel Manager and the Invicta kernel (alongside many other kernels and managers) is that you can try and tweak a lot of options, many of which will be subjective and vary depending on your usage

echo92 said:
With my usage pattern, I get typically 4-4.5 hours.
This includes:
Calls, texts, and brief Whatsapp usage
Browsing XDA, reddit, instagram
Youtube over 4G/LTE at 1080p (with a slightly weak mobile signal), which is my main usage.
This is with ambient display set to 100 ms wakeup, and 2 sec on time. General brightness at about 25 %. EX Kernel manager used to set maximum number of big cores to 2, I/O manager set to zen with 256 kB readahead buffer.
Of course, your experience may vary, though I've always had good battery life with Invicta.
Click to expand...
Click to collapse
Wow... my usage is nearly the same and on nearly every ROM I get about 5.5-6.5 hours of SoT. Whether it be LOS, Invicta, GZR Tipsy (slim based), AOSP-CAF, or even MM ROMs (which are even friendlier on battery).
I disable any memory killers, location, bluetooth, set zen/512kb, disable all big cores, default adaptive brightness, and my usage is reddit/Instagram/Chrome/Telegram. This is over a 2 day period too.