ok basically i bought the phone second hand with lite'ning 1.4 on it and the wifi worked perfectly ok all the time. Since it was very old i updated it to 6.1. ever since then I have had issues with the wifi. it will connect perfectly fine to the router but i have no connectivity from it, nothing will get any net access at all. This is also not 100% of the time, its MOST of the time but not all, i do have moments where it does work fine. very very odd.
I have since tried updating the kernel to ninpho 2.1.3 from the 2.0.5 that comes with lite'ning 6.1, but that made no difference.
Someone suggested i try a wifi fix app from the market so i downloaded "FXR wifi fix and rescue" and ran that. It ran ok, wiped all my wifi settings and i restarted, but it has not solved the problem at all.
i find it very very odd since if it was a problem with the kernel OR the rom then everyone would surely have exactly the same problem. I know some people report wifi issues but most dont seem to.
anyone have any other ideas?
The odd thing is that it worked before the update. That means that it will most likely be software related.
You could try flashing something totally different like MIUI or CM. They provide kernels too, so this might resolve it, if your kernel and rom don't "like each other". This usually shouldn't happen, but updates breaking wifi shouldn't too. So it might be worth a try.
Sent from my GT-I9100 using XDA App
if i went to something completely different i assume i would have to factory reset the phone to wipe it first? (or factory reset it AFTER installing the new rom?)
was trying to avoid wiping it as i dont want to spend endless hours setting up everything again. i have backed it up with the free titanium but id still like to not have to find out whether the restore actually puts everything back properly
its very odd as its not completely broken, sometimes it does actually work, and it always connects to the router itself without any problem.
Probably wrong modem for you, flash another one. You can find modems in the developement section.
ok thanks I will have a look at that. It is currently on XXKH3 which is what came with lite'ning 6.1. i am confused though, all SGS2 hardware is identical so if this modem in 6.1 is causing this issue, wouldnt it affect every sgs2 that uses that modem?
I found the "shipped modem collection" post in the original development thread so have asked in there which modem i should try.
ok apparently i should try XXKI3. for o2 UK provider.
although i have now read that wifi is not managed by modem but by kernel only. if this is true then modem will not help me
Well, if the wifi is not managed by the modem, try what I proposed you earlier. The simplest would be to flash CM. Make a backup of your current rom, then do a full wipe and install CM.
As for your data:
1. Titanium backup restores your apps with their data (if you wish). That means that, for example, your games will keep their saves, other apps their settings and so on.
2. Assuming that you have a google-account, you don't have to worry about your contacts, calender,... Just sync it before you flash.
3. The backup you make in CWM will backup everything in case CM doesn't work for you.
In case it does work and you'll want to keep it, the other two other parts of your backup will minimize the remaining work. Note that you shouldn't restore "standard"-apps like the media-player or the SMS-app if titanium backup tells you that the app is not currently installed on your fresh CM. This means that CM uses it's own media player or SMS app. It could lead into problems to mix TouchWiz apps with CM.
A side-note:
Don't use the "stable" version. It had more bugs than expected and they made it a RC again. However, it is still in the stable folder. Get the latest nightly.
Sent from my GT-I9100 using XDA App
yep i think it is kernel. just noticed that 1.4 had cf-root, 6.1 had ninph 2.0.5 and i then tried ninph 2.1.3 and both ninph's have had the issue. i just tried speedmod k2-13 as i already had that downloaded and so far the wifi has been ok so hopefully thats it fixed. i guess it was something to do with ninph (i am thinking that because i have it set to sleep the wifi when the screen is off that somehow ninph is not handling this properly).
possibly one good thing to come of it all, ive updated the modem to KI3 which is supposedly the best one for o2 UK so i may even save more battery and speedmod is meant to be really good for battery too. I still have lite'ning on it at the moment.
i might have a look at CM anyway but i do kinda like lite'ning (although i havent actually used anything else since the phone came with it!)
also need to look at wakelocks to see if i can save some more, although not sure how i go about 'fixing' them at the moment
The choice between CM, MIUI and the stock mods is the choice between three different UI's.
I've had all three of them for some time. As you got CWM, you can just create a backup and do a sightseeing tour through the world of custom roms. Believe me, it's absolutely worth it. To get an idea of the main differences, I've written a short overview for you:
Stock mods use Samsung's TouchWiz. The default user interface that you get when buying a Samsung Android phone. So it mostly looks and "feels" the same and you can't do much about it.
CyanogenMod gives you the pure Android user interface. It's the closest to the Nexus phones by google, but gives you some extras. It is much more customizable than stock roms. It's sleek and fast.
MIUI is a whole different story. They're "Redefining Android". I think calling MIUI an "Android custom rom" is an understatement. It's an entire OS. The result of putting the best from iOS and Android into one powerful OS. It adds tons of useful(!) features. If you've ever used Windows Phone 7 or an iPhone, you know what a big step forwards Android is when it comes to features. Switching from Android to MIUI is just like that. There is just so much more. It is BY FAR the most customizable Android you can get.
Wow. If I look at how long the texts are, I see that I'm pretty biased. :O
Well maybe because I've switched so often between them. The stock roms had no chance, because after I used one of the others I found out that TouchWiz doesn't cut it anymore. I hate how "iPhone-ish" MIUI is, but if I flash CyanogenMod I just miss so much. Giving you a list of what MIUI adds would be another long post of this length.
Sent from my GT-I9100 using XDA App
cool thanks will have a look at MIUI at some point.
spoke too soon earlier, the wifi is maybe slightly better on this speedmod kernel BUT when i wake the phone from sleep, it takes about 30 seconds before i can connect to the net with anything. the phone connects to the wifi straight away, but i have no connectivity for a good 30 seconds and then it starts working. (its not the router, i am getting a connection and an IP pretty much as soon as i wake the phone). also the 30 seconds or so only STARTS once i try to connect to something. if i wake the phone and do something that does not want net access for a few mins and THEN try to get on the net via wifi (which shows as connected the entire time) then again i have to wait about 30 seconds from when it first tries to connect before it will start working.
ok slightly confused again.
I have lite'ning 6.1, speedmod k2-13 kernel and XXKI3 modem. I am trying to get cwm installed so i can make a full backup image of the entire phone while i try to sort out the wifi issues. i downloaded rom manager from market, and selected the firstion option in the app 'flash clockworkmod recovery'. it brings up a menu saying 'confirm phone model' with AT&T galaxy S2, a coulpe of i9000s and a plain "Samsung Galaxy S2" which is the one i selected. it downloads something and says successfully downloaded clockwork mod recovery.
i then choose reboot into recovery. when rebooting it attemps to install something but then says "failed to verify whole-file signature" and aborts. so im just stuck with the standard recovery instead.
so now im confused, have i missed something?
Ehhhhm, you don't need to do it.
Have a look at the features of the speed-mod-kernel:
Current features:
Root and CWM:
- Automatically installs root (su)
- CWM 4.0.1.5 recovery
It already installs it right away.
Just in case you messed something up. You should flash the kernel again.
Besides that you don't need the RomManager at all. Just shut your phone down and boot into the recovery with the key-combo. Create and restore backups from there.
Sent from my GT-I9100 using XDA App
a) Random reboots. We've all experienced them; Mine seem to come up quite often, no matter what rom I have installed. Whether it be CM7, CM9, MIUI, etc... it usually happens after returning from "sleep mode" (locking the screen)
b) Also, is there a way to make the nook run SMOOTH (for christ's sake...)??
I've tried V6 supercharger, and I haven't felt that much of a difference.
As for specs, I have my nook overclocked to 1200mhz, with the governor on "interactivex".
c) BATTERY LIFE. I've heard people using there nooks for quite a long period of time before needing to recharge.. is there any trick to this? I'm getting 3-5 hours of use on a normal day. It's supposed to have the same battery as the Nook Tablet... and same screen resolution.. sigh..
solutions anyone?
Thanks in advance.
Well, I'm currently running the MiRage rom and it runs fine. No random reboots. Do you use a time/weather widget? Sometimes these can cause occasional problems. I wouuld think it might be an app that is causing these problems, as I've used many roms on my nook, including MIUI, without the problems you are describing.
As for low battery, how high is your display brightness set? I have found that to be a big battery hog. Or again, it could be due to certain apps.
I would also suggest doing a clean install of your rom - wipe and reformat. If you are not sure of the procedure, please post.
My nook gets very heavy use on a daily basis and I get a full day after a nightly charge. Look for a thread in the general section for the nook by mr72 - a guide for CM 7.10 setup. Lots of useful info there.
Sent from my NookColor using xda premium
How many updates have you installed on your nook color? I have found that you should only update a few times before you will start seeing problems with your cyanogenMod builds.
CyanogenMod uses modified kernels so you should wipe both your data and your caches after a few updates to keep from corrupting your kernel base. Make sure to backup first with a nandroid backup so you can restore your apps and settings afterwards. Constantly re-flashing and updating your cyanogenmod builds just leads to problems without doing a full data wipe once and awhile. ALWAYS wipe your dalvik caches on each update.
The easiest way to wipe both your data and caches is to use clockworkmod in your included ROM manager.
~~~~~~~~~~~~~~~~
I have not experienced any of the issues you are claiming with the latest stable of cyanogenMod 7.2 on the nook color, but I make it a issue with myself to wipe both the data and the caches on the eMMC of my nook color , which is the way I am using cyanogenMod, after a couple of updates. YOU will especially will have to wipe both the data and caches when you upgrade from gingerbread ported versions of cyanogenMod to the ICS versions, those kernels are way modified. I have worked on some through the github.
I tried many CM7 nightlies and newer CM9 also.
Very rarely to have a restart (freeze up are bit more often) and battery lasts for 9–10 hours with full use.
Something might be wrong with your hardware or no good install of Roms.
How long do you have it? Did you get it new or used?
Produced by NookColor at ICS 4.0.4
Hi XDA,
As there ar eno recent thread about 'no deep sleep' (aka on CM13/13.1) I'm opening one here inh ope someone can help me troubleshoot what's wrong...
I've had my OPO for 1.5 yr now, and overall it's doing great. Except since CM13.0, I've been having troubles with deep sleep and therefore my battery time hardly make it through the day.
It all began after the April upgrade, when I decided to encrypt my phone. I did a clean full wipe and installed the zip from TWRP recovery, then proceeded to encrypt the phone... Turns out the boot.img patched by SuperSU is incompatible with the encryption process so I reverted the boot.img ti the original and encrypted my phone, then flashed SuperSU back. Since then, the phone would never enter deep sleep mode, except when data connexion and wifi are disabled.
I've since flashed the latest build (ZNH2KAS1KN) in hope that would solve the problem. The flash was the cleanest I ever took (wipe data, system, dalvik, cache ; reboot to recovery, flash full zip, boot to system and restore all app through the 'play store restore' function, reboot to bootloader, flash TWRP with AtAm fix for CM13 encryption support). Yet, my battery keeps drainign blazing fast and I have no deep sleep at all even with the phone sitting indle on a table for hours. See screenshots.
The only strange thing I see are those 'fd440000.qrypto' kernel wakelocks. Any ideas ? I'm assuming it has something to do with the phone being encrypted, but why would deep sleep be achievable when the phone has no data/wifi ?? It's really puzzling and I can't figure out what to do. I had exactly the same problem on the previous 13.0 release (including the qcrypto wakelock).
edit: the only slight deep sleep period is because my SIM card was not detected for a short period of time (probably bad contacts, I took it out, wiped it a bit and everything was back in order)
Any help appreciated, thanks!
Strange. I haven't had much battery drain issues on Sultan's build. Are you using the official cm13 builds or unofficial builds?
Sent from my A0001 using Tapatalk
CoinCoin88 said:
Hi XDA,
As there ar eno recent thread about 'no deep sleep' (aka on CM13/13.1) I'm opening one here inh ope someone can help me troubleshoot what's wrong...
I've had my OPO for 1.5 yr now, and overall it's doing great. Except since CM13.0, I've been having troubles with deep sleep and therefore my battery time hardly make it through the day.
It all began after the April upgrade, when I decided to encrypt my phone. I did a clean full wipe and installed the zip from TWRP recovery, then proceeded to encrypt the phone... Turns out the boot.img patched by SuperSU is incompatible with the encryption process so I reverted the boot.img ti the original and encrypted my phone, then flashed SuperSU back. Since then, the phone would never enter deep sleep mode, except when data connexion and wifi are disabled.
I've since flashed the latest build (ZNH2KAS1KN) in hope that would solve the problem. The flash was the cleanest I ever took (wipe data, system, dalvik, cache ; reboot to recovery, flash full zip, boot to system and restore all app through the 'play store restore' function, reboot to bootloader, flash TWRP with AtAm fix for CM13 encryption support). Yet, my battery keeps drainign blazing fast and I have no deep sleep at all even with the phone sitting indle on a table for hours. See screenshots.
The only strange thing I see are those 'fd440000.qrypto' kernel wakelocks. Any ideas ? I'm assuming it has something to do with the phone being encrypted, but why would deep sleep be achievable when the phone has no data/wifi ?? It's really puzzling and I can't figure out what to do. I had exactly the same problem on the previous 13.0 release (including the qcrypto wakelock).
edit: the only slight deep sleep period is because my SIM card was not detected for a short period of time (probably bad contacts, I took it out, wiped it a bit and everything was back in order)
Any help appreciated, thanks!
Click to expand...
Click to collapse
looks like you are having weak or no signal. this is likely to cause this issue!
Bac0nator said:
Strange. I haven't had much battery drain issues on Sultan's build. Are you using the official cm13 builds or unofficial builds?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Only the official builds for CM13/13.1, and with the cleanest install as possible... Never tried Sultan's build, is that a kernel, a full rom...?
hellcat50 said:
looks like you are having weak or no signal. this is likely to cause this issue!
Click to expand...
Click to collapse
Definitely not the cause. This happens every day, everywhere, independently of signal strength (i.e. color of bar in graph). I've confirmed with a friend of mine who also encrypted his phone a while ago and he also never goes to deep sleep.
CoinCoin88 said:
Only the official builds for CM13/13.1, and with the cleanest install as possible... Never tried Sultan's build, is that a kernel, a full rom...?
Definitely not the cause. This happens every day, everywhere, independently of signal strength (i.e. color of bar in graph). I've confirmed with a friend of mine who also encrypted his phone a while ago and he also never goes to deep sleep.
Click to expand...
Click to collapse
sultan's rom is cm13 with caf kernel. it is known to be very battery friendly.
Here is the link: http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700
and here I was hoping not to have to full wipe/reflash/restore again.... I've also posted on CM jira in hope of a comment on whether there is a known bug on ecnrypted devices or not. If nothig comes from there I'll try sultan's rom...
Sultan's builds are optimized for battery on the one plus one. They tend to be better than official cm13 builds, most of the time.
Another option is downloading an app called nap time on the play store, which forces your phone to go into deep sleep the moment the screen shuts off.
CoinCoin88 said:
and here I was hoping not to have to full wipe/reflash/restore again.... I've also posted on CM jira in hope of a comment on whether there is a known bug on ecnrypted devices or not. If nothig comes from there I'll try sultan's rom...
Click to expand...
Click to collapse
Steve included some kernel commits recently that address the crypto wakelock. They should be fixed on current nightlies.
I know it fixes it as I had that fd000.crypto kernel wakelock until very recently and I'm encrypted.
I have the same issue on Sultan's Rom. First 20 days battery life was awesome and now all the time phone is awake. I am reflashing sulatn build again
Thanks for this info, this is going in the same direction I observed and somewhat reassuring. Are you talking about CM nightlies then ?
edit: that was inteded for @tiny4579
Sent from my A0001 using XDA Free mobile app
tiny4579 said:
Steve included some kernel commits recently that address the crypto wakelock. They should be fixed on current nightlies.
I know it fixes it as I had that fd000.crypto kernel wakelock until very recently and I'm encrypted.
Click to expand...
Click to collapse
By any chance, would you happen to have SuoerSU as root binary/manager? I recall it patches boot.img which prevented encryption from being run in the first place (to encrypt, I had to reflash the stock boot.img, encrypt, then reflash SuoerSU). I'm wondering if the altered boot.img couldn't be part of the problem.
Sent from my A0001 using XDA Free mobile app
Some heads up: there was indeed a wakelock issue that has been fixed by a commit on the 4th of June.
See associated bug on JIRA: https://jira.cyanogenmod.org/browse/BACON-4987 (and appreciate how it's easier to blame the user than to try to replicate a bug). Hopefully we'll have a 'future OTA' before the end of the year...
I still have this wakelocks issues right now...
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: