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.
Hello..
I'm so tired of theese reboots now and i dont know what to do about it.
I have soon tried every rom and firmware on this forum and its all the same.
It will often work for like 24hrs and then it starts again, if im using spotify or another music player ill get the restarts more frequent.
Sometimes it will work for a day but often it can be up to 5 times /hrs.
I just installed aicp and thought it was fixed... but just as i writes it has restarted 2 times... is this a hardware problem or is it software? And how do i find whats causing?
quazzu said:
Hello..
I'm so tired of theese reboots now and i dont know what to do about it.
I have soon tried every rom and firmware on this forum and its all the same.
It will often work for like 24hrs and then it starts again, if im using spotify or another music player ill get the restarts more frequent.
Sometimes it will work for a day but often it can be up to 5 times /hrs.
I just installed aicp and thought it was fixed... but just as i writes it has restarted 2 times... is this a hardware problem or is it software? And how do i find whats causing?
Click to expand...
Click to collapse
Mate....please describe:
1. Used ROM/kernel/OC/related
2. XPOSED?
3. Used Apps
Have you tried clean flashing, without installing single app for 48 hours? Does it happen then?
jukyO said:
Mate....please describe:
1. Used ROM/kernel/OC/related
2. XPOSED?
3. Used Apps
Have you tried clean flashing, without installing single app for 48 hours? Does it happen then?
Click to expand...
Click to collapse
1.
Garak cm13 from 6.0 so for a couple months with 10-15 updates and reboots from the beginning.
H2OS
Resurrection Remix tried for 2 days..
aicp NIGHTLY, installed yesterday same same.
Always clean install when changing rom, tried diffrent twrp.
2 .
No
3.
Nothing special, spotify tinder chrome whatsup kik bankid sparbanken instagram swish and thermocall
I´ve got the same problem as you do... I tried like every rom which is available for the OP2. Hopefully anybody out there knows a solution :/
Did your get these spontaneous reboots from the beginning of did they start after you played around with other ROMs than Oxygen? If the started after, perhaps some of the system partitions has been partly damaged or the files in them, if so try restoring phone back to basic using the known Qualcomm OxygenOS brick restore method which resets all partitions back to factory ones.
Skickat från min ONE A2003 via Tapatalk
quazzu said:
1.
Garak cm13 from 6.0 so for a couple months with 10-15 updates and reboots from the beginning.
H2OS
Resurrection Remix tried for 2 days..
aicp NIGHTLY, installed yesterday same same.
Always clean install when changing rom, tried diffrent twrp.
2 .
No
3.
Nothing special, spotify tinder chrome whatsup kik bankid sparbanken instagram swish and thermocall
Click to expand...
Click to collapse
Jacksack33 said:
I´ve got the same problem as you do... I tried like every rom which is available for the OP2. Hopefully anybody out there knows a solution :/
Click to expand...
Click to collapse
If anything else fails..... Backup all your apps. Backup your intenal SDCARD to a pc and do a factory reset:
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
Takes a bit of time, but it might be worth.
Did you try to take a logcat of the reboot issue?
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:
Need a little help with my X727, after i got it i flashed emmc_appsboot.mbn to unlock the bootloader, flashed TWRP and the latest lineage build which was the July 21st at the time. Everything was working perfectly and then a few days later i updated to the July 28th build and the battery indicator got stuck at 50% and it wouldn't charge the phone when plugged into the wall charger. If i booted into TWRP it would charge, but when i power it off and plug into the wall charger the battery charge symbol would come up and then orange LED comes on like it's charging but it's not. Now the issue is i foolishly let the battery run down, i left it plugged into the wall charger overnight but can't get enough juice to even get it to boot into TWRP. Any suggestions or should i cut my losses and return it?
Update: I left it charging for a little while with no change, decided to try to power it on again. I held down the power button and vol + button and plugged in the wall charger, held them down for about 15 secs and it finally booted into TWRP and is currently charging.
Now i'm back to my original problem the phone won't charge normally, have to boot into TWRP and is stuck at displaying 50% for battery.
Had any luck with this? Somewhat in the same boat as you.
Got a x727 new recently. Had the 18s software. I went straight to flashing the aBoot with unlock the bootloader file, flashed TWRP and putOmni first. Since then, battery doesn't update in android and just says 50%. Now currently on AICP.
There are times where if I go into TWRP it shows a different number other than 50%.
Thinking I may go back to stock ROM but keep unlockboot loader and somehow update to 21s and then go back to custom ROM .
Anyone got ideas/thoughts?
I have the same problems with nougat roms as you, i was running lineage 21st july update fine and then with 28st july i have that battery problem where the percentage only shows 50% and wont charge.
chuchorra said:
I have the same problems with nougat roms as you, i was running lineage 21st july update fine and then with 28st july i have that battery problem where the percentage only shows 50% and wont charge.
Click to expand...
Click to collapse
Good observation:
I tested that out and your right. I can install July 21st build on a clean install and charging works and battery is displaying anything other 50%.
If I install July 28th's build, charging doesn't work and battery is always at 50%.
Adding @jrior001 to the conversation since he helps maintain Lineage for our device: Any thoughts?
I have x727 FYI
bmac6996 said:
Good observation:
I tested that out and your right. I can install July 21st build on a clean install and charging works and battery is displaying anything other 50%.
If I install July 28th's build, charging doesn't work and battery is always at 50%.
Adding @jrior001 to the conversation since he helps maintain Lineage for our device: Any thoughts?
I have x727 FYI
Click to expand...
Click to collapse
Thanks for your answer, at least i know i'm not alone. Do you have as me the same problem with battery in other nougat roms? I tried omnirom and aicp and had the same problem.
I think it is kernel related because when i flashed blackscreen kernel in lineage 21st july i had the same battery problem as i had with 28th. I can't figure out if it is because we have a hardware or sofware problem.
chuchorra said:
Thanks for your answer, at least i know i'm not alone. Do you have as me the same problem with battery in other nougat roms? I tried omnirom and aicp and had the same problem.
I think it is kernel related because when i flashed blackscreen kernel in lineage 21st july i had the same battery problem as i had with 28th. I can't figure out if it is because we have a hardware or sofware problem.
Click to expand...
Click to collapse
Well so far it's you and me.. no one either has a x727 phone and/or we have the wrong something, somewhere.
I flash AICP or Omni and same issue.
Both AICP and Omni use blackscreen kernel? Lineage 7/28 and after doesn't work for me.
The only thing that works is PA and RR. Assuming they are Lineage base, their latest release predates 7/21 so maybe that's why those two ROMs work for me.
bmac6996 said:
Well so far it's you and me.. no one either has a x727 phone and/or we have the wrong something, somewhere.
I flash AICP or Omni and same issue.
Both AICP and Omni use blackscreen kernel? Lineage 7/28 and after doesn't work for me.
The only thing that works is PA and RR. Assuming they are Lineage base, their latest release predates 7/21 so maybe that's why those two ROMs work for me.
Click to expand...
Click to collapse
From time to time i read here people that have the same problem but they just flash again stock rom and forget about it. I have x720 china version so this could happen in both models.
Reading in internet about this problem some people got it fixed with battery calibration, others with battery replacement and others had to change the motherboard. The problem is we can't try battery calibration because charging is not working so we can't let it dry completly.
About kernel i'm pretty sure AICP use blackscreen but not OMNI, in 28th july lineage update log there were a few changes to kernel and that's what i think it's causing our problem. Regards!
chuchorra said:
From time to time i read here people that have the same problem but they just flash again stock rom and forget about it. I have x720 china version so this could happen in both models.
Reading in internet about this problem some people got it fixed with battery calibration, others with battery replacement and others had to change the motherboard. The problem is we can't try battery calibration because charging is not working so we can't let it dry completly.
About kernel i'm pretty sure AICP use blackscreen but not OMNI, in 28th july lineage update log there were a few changes to kernel and that's what i think it's causing our problem. Regards!
Click to expand...
Click to collapse
Yeah I don't know what else to do.
I even restored to stock again. Went back to x727 19s. reflashed modems to the 19s. Relocked bootloader, did an official OTA update to 21s. unlocked the bootloader, installed official TWRP, and tried flashing latest AICP and still same thing! I know i have 90%+ in battery..
Don't know what else to update and/or change that could affect this? I'm assuming other x727s that were on 21s are not having this issue went trying to flash AICP or Omni.
bmac6996 said:
Yeah I don't know what else to do.
I even restored to stock again. Went back to x727 19s. reflashed modems to the 19s. Relocked bootloader, did an official OTA update to 21s. unlocked the bootloader, installed official TWRP, and tried flashing latest AICP and still same thing! I know i have 90%+ in battery..
Don't know what else to update and/or change that could affect this? I'm assuming other x727s that were on 21s are not having this issue went trying to flash AICP or Omni.
Click to expand...
Click to collapse
I'm starting to think it's hardware problem ( motherboard or battery ) but as we don't have this problem in stock rom we can't use our guarantee. Please tell me if you have any advance.
chuchorra said:
I'm starting to think it's hardware problem ( motherboard or battery ) but as we don't have this problem in stock rom we can't use our guarantee. Please tell me if you have any advance.
Click to expand...
Click to collapse
IMO I don't think it's a hardware fault. I think it could be a hardware incompatibility, maybe a hardware revision that no has anticipated yet.
I can only assume that when I went back to stock x727 19s and relocked bootloader and took the official upgrade to 21s, that my phone IS stock at that point, and re-unlocked bootloader and proceeded with the rest. I haven't flashed anything out of the ordinary afterwards, twrp and just been trying ROMs since.
I know if you go back to Stock Rom or Turbo Rom which is MM, no charging issue there.
As of this post date, AICP, Omni, Lineage 14, Tipsy, Tesla with their latest builds, do not work. I will only assume these ROMs either use Lineage and/or use Lineage as their base and they cherry pick certain things either kernel commits, or fixes (or breaks) and thats why maybe these ROMS don't work for us.
Resurrection Remix and Paranoid DOES work. Not sure what they do different exactly but I would be curious if they update their ROM soon, that it will break charging like the rest.
I also have been reading throughout the forum about within the last 30 days, people have been posting about charging issues or their phone stops charging and it could possibility be a bad charger. I wonder if those folks were on the ROMs listed above and did an OTA update and that broke charging. (FYI the USB-C cable that came with the phone is crap for data connection or at least mines was. Only good for charging. Had to use my own USB-C cable to connect to my PC)
If people have issues with charging, if you can charge your phone with it turned off and at least get it to 15%, get your files prep, jump into TWRP and flash to those other two working ROMs, quick charging should work and battery reporting will work again. I'm personally back to RR again.
We need help/direction from a DEV because this is beyond my skill set. I don't even know where to start or what logs to give.
@chuchorra - Assuming you were using just using plain lineage, you can extract the boot.img from the 7/21 zip file and just flash the file to your phone and that should revert back the kernel or whatever it is that is screwing up charging .
I did a test where i installed the latest build and got the issue, but i was able to fix it but reverting back to the 7/21 boot.img file which kept charging and battery display working.
Had a similar issue of being unable to get over 50% charge but deleting BatteryStat.bin (and other Battery****.bin files) in /data/system/ seemed to fix this problem.
But now have another problem, the phone doesn't seem to charge when switch off! The charging indicator comes on but when I switch the phone on in the morning, the battery's still low.
Nice! But what are the implications to use a boot.img from a previous update? Maybe we should post in lineage official thread to ask what logs are needed.
If it can be useful to someone, the USB c plug of my original stock cable on one side charges fast, turning it on the other side charges slowly I have marked the fast side with a red point, just to known! Cheers!
Sent from my LEX720 using XDA Labs
chuchorra said:
Nice! But what are the implications to use a boot.img from a previous update? Maybe we should post in lineage official thread to ask what logs are needed.
Click to expand...
Click to collapse
None that I can tell so far?? I think tried posting but nothing but crickets there...
Might try erasing that battery bin file on the broken rom
---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------
Mateus109 said:
Had a similar issue of being unable to get over 50% charge but deleting BatteryStat.bin (and other Battery****.bin files) in /data/system/ seemed to fix this problem.
But now have another problem, the phone doesn't seem to charge when switch off! The charging indicator comes on but when I switch the phone on in the morning, the battery's still low.
Click to expand...
Click to collapse
Tried it and no luck. There was only two files in that directory, batterystat.bin and battery(something).xml.. delete one, and then tried deleting both and status didn't change on it.
I tried that, it's manual battery calibration but didn't help. Maybe there are more than those 2 files. About lineage official thread i post there too but anyone had the same problem, but now that you found flashing old boot.img fix the problem they could know where is the conflict. Cheers!
I have a similar issue, was on linage, with no issues, and slowly but surely charging started acting up after 4 months of no issues. First the phone RED LED would be on (charging) but the OS wouldn't see it charging, AMPERE would not show charging even though it showed AC adapter connected. Figured it was rom, updated to latest and now i have no charging or connectivity. Shows 50% charge, then back to ZERO. Still under warranty, not sure what to do as LEECO web site is down, will call on Monday and see what they say.
i have 2 leeco. both the same but from another seller. One have this issue and the second is working perfect.
Not saying this is the solution but I had a problem with fast charge and sometimes wouldn't charge at all, on both PA and LOS roms then I switch to a LG cable re-downloaded everything re-transferred the zip files to the phone with the LG cable and now it fast-charges it with no problem on LOS. I even started a thread warning about the Leeco cable.