Related
I have a nexus 5, I had Android 5.0.1 (rooted) I think and had a lot of apps and data so I really didn't want to lose it all while upgrading. But then a discovered a way to flash Android 6.0.1 without loosing anything, it was basically by doing it totally manually (I followed this tutorial : eladnava(.com)/update-rooted-nexus-5-marshmallow-without-wiping-data. As I can remember everything went well except that I wasn't able to update SuperSU (I tried many times, but didn't work, and didn't have any impact on anything else). Then I noticed that the battery level was like 4000% so I thought it was a graphical issue so I tried to update it by charging, rebooting... But nothing, in the settings, in general info, the same, 3000%-4000%, moreover it was increasing and decreasing all the time, it s totally f**ked up ! Then I begun downloading all the battery stats apps of the play store but it was always showing the same percentages. So I lived with it for about two weeks, I couldn't find anything related on the internet, I didn't want to do the process again but it is so boring I never know when my phone's gonna die. Therefore I'm begging for your help ! I m lost !
Thx
Hello, Merry Christmas, and thanks for using XDA Assist!
I am going to have your post moved to the Nexus 5 Help Forum, where there will be experts with your device that can give you the assistance that you need.
Good luck!
are you using a custom kernel?
Many kernels have this issue on android Marshmallow
You have to flash the factory boot.img from fastboot, that will get rid of the 3000% battery. No, you won't lose anything. Then flash SuperSU in recovery to get root back.
weissbierdood said:
You have to flash the factory boot.img from fastboot, that will get rid of the 3000% battery. No, you won't lose anything. Then flash SuperSU in recovery to get root back.
Click to expand...
Click to collapse
Still f**ced up after reflashing boot.img... damn
I am having the exact same problem I did my root via kingroot through the computer battery is showing up currently 3,618 but goes up and down all the time tried installing battery apps from the play store but the battery percentage is still showing as wrong and I don't really know what I'm doing as it's the first time I have ever rooted any android phone. I was running stock android 6.0.1 decided to root the iPhone emoji onto my nexus 5 I now have that on my device but the battery problem is unusual never know how much battery I have must be an easy fix. Phone works perfectly apart from that any help would be appreciated
Added screenshot
For what it's worth, I've just installed MMB29S on my wife's N5 and the battery percentage has gone haywire in the pull-down settings and in the battery icon on the status bar (configurable in System UI Tuner in Settings) - the pull-down shows 3987 and the icon shows 98, the two middle digits.
Maybe it's a Nexus 5 problem? My Nexus 6 on MMB29S is absolutely fine.
BUT... (come on, get to the point... ) Battery Bot shows 100% correctly on the top left of the status bar. It's clearly reading something differently or correctly. It may be a short-term fix for those suffering from this, but I've been using Battery Bot Pro for years because seeing the percentage on the status bar at a glance is really useful. The attached screenshot is from my Nexus 6 shows 88% top left (and also in the battery icon on the right).
Well I managed to get my stock android back by using flashify and my battery has gone back to normal and it's all working I'm worried now that if I root it again I'll get the same thing happening I only want to root to change the emoji and thats it. Can I just re root or will it give me the same problem?
Assuming that we're talking about stock Android.
Battery is shown correctly, if either the complete factory image is flashed (with loss of data)
or the corresponding partitions are flashed:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Had the same problem when I only flashed the system.img, then my battery got weird.
After also flashing the boot image, everything is shown correctly.
rolex0815 said:
Assuming that we're talking about stock Android.
Battery is shown correctly, if either the complete factory image is flashed (with loss of data)
or the corresponding partitions are flashed:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Had the same problem when I only flashed the system.img, then my battery got weird.
After also flashing the boot image, everything is shown correctly.
Click to expand...
Click to collapse
So the steps would be root the phone again
Then go on to to flashify and then flash boot image
ccfcjme said:
So the steps would be root the phone again
Then go on to to flashify and then flash boot image
Click to expand...
Click to collapse
Just flash a recent SuperSU version after flashing the images.
By now it has autoroot and patches the boot.img.
rolex0815 said:
Just flash a recent SuperSU version after flashing the images.
By now it has autoroot and patches the boot.img.
Click to expand...
Click to collapse
Just a quick update to let everyone know how I'm getting on I'm glad to say I finally fixed the problem. I unrooted my phone and used the nexus tool kit and rooted my phone that way installed all the relevant items I needed and I downloaded emoji switcher from the play store and flashed it now I have ios emoji running on my nexus 5 with my battery showing how it should be. I've also learnt more about the process of rooting an android phone as before I didn't really know only wanted to root my phone to get ios emoji on my phone really don't like the android emojis this reason alone was enough for me to want to root I'm so happy I managed to it successfully
ccfcjme said:
Just a quick update to let everyone know how I'm getting on I'm glad to say I finally fixed the problem. I unrooted my phone and used the nexus tool kit and rooted my phone that way installed all the relevant items I needed and I downloaded emoji switcher from the play store and flashed it now I have ios emoji running on my nexus 5 with my battery showing how it should be. I've also learnt more about the process of rooting an android phone as before I didn't really know only wanted to root my phone to get ios emoji on my phone really don't like the android emojis this reason alone was enough for me to want to root I'm so happy I managed to it successfully
Click to expand...
Click to collapse
did you loose your data ??
---------- Post added at 12:04 PM ---------- Previous post was at 11:59 AM ----------
rolex0815 said:
Assuming that we're talking about stock Android.
Battery is shown correctly, if either the complete factory image is flashed (with loss of data)
or the corresponding partitions are flashed:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Had the same problem when I only flashed the system.img, then my battery got weird.
After also flashing the boot image, everything is shown correctly.
Click to expand...
Click to collapse
This 3000% battery just happen to me on 6.0.1 M4B30Z when i rooted my phone from Kingroot. :|
Then i unroot, installed twrp and super su., but the issue is still present
what you are suggesting is to flash stocked boot.img and system.img from M4B30Z OTA images and it should get fine, without loosing the data ?
Or
you are telling us the reason why 3000% battery may occur when someone only flashes the 2 images only ??
Get it while it's hot :
http://en.miui.com/download-320.html
Anyone have tested this? Is there any improvements from V8.2.1.0 or still prefer the old V8.1.2.0? So, here i am waiting for feedback.
Sent from my Redmi 4 Prime using XDA-Developers Legacy app
I'm on it since this morning, pretty much the same I'd say, the change-log has a few things like swipe to dismiss notifications on lockscreen and a few bugfixes.
Flynhx said:
Anyone have tested this? Is there any improvements from V8.2.1.0 or still prefer the old V8.1.2.0? So, here i am waiting for feedback.
Click to expand...
Click to collapse
senseii said:
I'm on it since this morning, pretty much the same I'd say, the change-log has a few things like swipe to dismiss notifications on lockscreen and a few bugfixes.
Click to expand...
Click to collapse
How is your experience with the temperature & battery life? Can you share some screenshots of your SOT? Did the bugs at V8.2.1.0 finally fixed in V8.2.4.0?
Sent from my Redmi 4 Prime using XDA-Developers Legacy app
Bet this rom weighs more than an average car....
I was using stock 8.2.1 Global Stable. After auto-updating to 8.2.4, had sound glitches, unlock lag and Telegram bugs I've never seen before. I don't recommend to migrate to this version from 8.2.1.
I haven't had any sound glitches or unlock lag (I don't use telegram).
As for battery life it's great, 2 days use, 6 hours SOT so far and I have 50% battery left (4G on all the time).
Flynhx said:
How is your experience with the temperature & battery life? Can you share some screenshots of your SOT? Did the bugs at V8.2.1.0 finally fixed in V8.2.4.0?
Sent from my Redmi 4 Prime using XDA-Developers Legacy app
Click to expand...
Click to collapse
5th day with the phone. i got it update it to 8.2.4, charged it, unlocked bootloader, installed twrp/root and i had about 10 hours sot during a 3 day period on 2g and a little 3g and wifi disable when screen is off. those 10 hours included a lot of restarts that consume energy a lot of copying things via wifi browsing messenging and a few calls. no problems so far hope i helped.
This update don't bring big changes. Don't understand why you afraid of update. All work's fine including battery life and performances.
Upd:
1. Sound issues and Telegram bugs - no more. One-time glitch?
2. Usual Xiaomi micro-lags when switching apps seem to disappear. So 8.2.4.0 feels way more smooth for me.
3. Battery life - no noticeable changes.
4. MiPicks app added along with annoying ads.
I wonder Why eu version not yet published ?
Sorry for this silly question, how can i update to 8.2.4 if I have TWRP recovery? Can I just take OTA update or do I need to flash the zip file via TWRP?
BadHappiness said:
Sorry for this silly question, how can i update to 8.2.4 if I have TWRP recovery? Can I just take OTA update or do I need to flash the zip file via TWRP?
Click to expand...
Click to collapse
You'll have to flash via TWRP cause the OTA uses the built in Xiaomi recovery (which you dont have anymore since you installed TWRP).
sas_sas said:
I wonder Why eu version not yet published ?
Click to expand...
Click to collapse
xiaomi.eu is based on the china rom, not the global. they won't release until there's an official release for the CN rom.
senseii said:
You'll have to flash via TWRP cause the OTA uses the built in Xiaomi recovery (which you dont have anymore since you installed TWRP).
Click to expand...
Click to collapse
Thanks for your reply. Another question, do I need wipe anything before flash this rom? And also do ineed to root it again after flash the rom?
BadHappiness said:
Thanks for your reply. Another question, do I need wipe anything before flash this rom? And also do ineed to root it again after flash the rom?
Click to expand...
Click to collapse
Yeah you should wipe the cache and davlik cache at least before flashing the new rom. Full wipe would be best.
To get root you'll have to re-flash the super su zip file after you flash the rom.
Re' 8.2.4.0 global
Just did a clean full wipe and flashed epic zip again for another try, though I still have noticeable battery drain.
Thinking of going 8.2.4.(and then uninstalling a few apps n' make a few minor mods for better battery life)
I have twrp installed, read somewhere I can not get rom updates via OTA due to this. (As MIUI recovery is needed for update?) Is that true?
In which case does that mean when there is a new global rom update, and I flash zip in twrp(if that's the case) I would lose my settings and aps? (Guess I would) Or as it's newer/similar global update could I get my settings back from mi cloud or Titanium back up?
Tired of changing roms and then setting up all the apps.
Sorry if this a newbie type question.
Thanks for any info (=
Tried to delete my last post, without luck, found answer/s in other threads (=
The zip file is corrupt
I have a rooted s6 with custom recovery(TWRP) and custom rom(THE GRIFFIN) and my phone is draining really fast.
U can see in the picture that i attached below that at 1AM the phone was at 100% and i left it aside cz i went to sleep, i woke up at 7:40AM and the phone was at 53% and all the drain was because of ANDROID OS.
What should i do??
Try a clean flash of that ROM. (you will lose all data, so make a backup)
Also you can try Noble Nougat Experience... i'm experiencing 4,5h/5h screen on time & 3% battery drain over night.
niektk said:
Try a clean flash of that ROM. (you will lose all data, so make a backup)
Also you can try Noble Nougat Experience... i'm experiencing 4,5h/5h screen on time & 3% battery drain over night.
Click to expand...
Click to collapse
When i flashed the rom using twrp i made a clean flash (all data were wiped..). And nougat nouble experience is a good rom ( i had it before) but my question is xposed comoatible with it yet?
If yes i'm gonna switch back
@[email protected]@[email protected] said:
When i flashed the rom using twrp i made a clean flash (all data were wiped..). And nougat nouble experience is a good rom ( i had it before) but my question is xposed comoatible with it yet?
If yes i'm gonna switch back
Click to expand...
Click to collapse
Hmm, i dont know. You can ask in the telegram group.. (join it by clicking the link in the NNE post.)
I'm getting the same issue with stock nougat as well as noble nougat experience 3.0.
install wakelock detector or battery stats and check, what do not let your phone go into deep sleep
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Harshseth said:
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Click to expand...
Click to collapse
None of STOCK ROM or OTA updates can be flashed/updated by TWRP, you need to be on stock recovery as well everything stock (unmodified system, boot and all).
I faced this problem too, but I fixed mostly of the battery drain tweaking the kernel with the ElementalX app to ~0,80/h. I had to set the little cores working like big cores do, because all little cores and one big were in use always; and applied LightingBlade profile.
Harshseth said:
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Click to expand...
Click to collapse
In order to use the OTA path you have to be on stock recovery, boot and kernel, not on TWRP. Otherwise you get the error that you experienced.
xAnkris said:
I faced this problem too, but I fixed mostly of the battery drain tweaking the kernel with the ElementalX app to ~0,80/h. I had to set the little cores working like big cores do, because all little cores and one big were in use always; and applied LightingBlade profile.
Click to expand...
Click to collapse
I went that path but it didn't seem to help much. Besides, I am happy with this stock setup. It is much better than when I was on Marshmallow stock and went over to custom ROMs. I can do anything I want to do and install any app I desire to use. Good performance, great battery life, and customizable as much as I want. No need to be on custom.
pastorbob62 said:
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
Click to expand...
Click to collapse
Are you able to root the stock nougat build npjs25 14-8.?
If yes how you rooted your phone. Plzz guide me. I also want to root my stock nougat
ADITYA_KUMAR said:
Are you able to root the stock nougat build npjs25 14-8.?
If yes how you rooted your phone. Plzz guide me. I also want to root my stock nougat
Click to expand...
Click to collapse
Before you can root stock Nougat you must first unlock you bootloader, install TWRP then flash Elemental X kernel 1.04 from TWRP.
pastorbob62 said:
Before you can root stock Nougat you must first unlock you bootloader, install TWRP then flash Elemental X kernel 1.04 from TWRP.
Click to expand...
Click to collapse
What is elemental x kernel. I have a unlocked bootloader.
ADITYA_KUMAR said:
What is elemental x kernel. I have a unlocked bootloader.
Click to expand...
Click to collapse
Instead of asking questions that have been answered numerous times (ad nauseam) you should try reading through the forums. I realize you are a raw noob, but if you wanted to learn Calculus, would you ask a bunch of questions without doing any reading and studying? It's no different when you are modifying your smart phone.
Here is a link to a thread that will guide you to rooting stock Nougat. It works for all versions of stock Nougat.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
But don't do anything until you have read through the procedures and fully understand. Above all, make a backup of your system from TWRP before you do anything else.
pastorbob62 said:
Instead of asking questions that have been answered numerous times (ad nauseam) you should try reading through the forums. I realize you are a raw noob, but if you wanted to learn Calculus, would you ask a bunch of questions without doing any reading and studying? It's no different when you are modifying your smart phone.
Here is a link to a thread that will guide you to rooting stock Nougat. It works for all versions of stock Nougat.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
But don't do anything until you have read through the procedures and fully understand. Above all, make a backup of your system from TWRP before you do anything else.
Click to expand...
Click to collapse
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
pastorbob62 said:
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
Click to expand...
Click to collapse
Very true.
Also try LightningBlade tunables(v 1.2.3 ; the newer version does not work that well for me..).
Stock rom provides the best balance between Performance and Battery life.
siddhesh9146 said:
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
Click to expand...
Click to collapse
If you're rooting on stock Nougat, you must have a custom kernel flashed (or used the temporary dm-verity disabler on the stock kernel) before you root. Else, without the mentioned modifications, you'll trip the anti-rooting protection built into the stock kernel, and you'll have bootloops unless you reflash your stock ROM as you experienced.
Easiest way, as per the guide is to:
Flash/boot TWRP.
Backup.
Flash ElementalX or vegito (any custom kernel will do, as these kernels do not have the anti-rooting protection).
Reboot to test.
Boot back to TWRP
Flash SuperSU v2.79 or newer, or magisk 13 or newer
Reboot.
You should be rooted, on stock, and if you've flashed magisk, Safetynet should be working It's working well on NPJS25.93-14-8 and it's stable. Granted, a few apps now seem to detect root/magisk (and fail to download/update from the Play Store, with an error 0), but nothing that a sideload from a legitimate source wouldn't solve...
champsp said:
Very true.
Also try LightningBlade tunables(v 1.2.3 ; the newer version does not work that well for me..).
Stock rom provides the best balance between Performance and Battery life.
Click to expand...
Click to collapse
True that! :good:
siddhesh9146 said:
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
Click to expand...
Click to collapse
If you had followed the link I supplied you would have had your answer as to why you had problems and also how to fix it.
echo92 said:
If you're rooting on stock Nougat, you must have a custom kernel flashed (or used the temporary dm-verity disabler on the stock kernel) before you root.
Click to expand...
Click to collapse
Hi, sorry for ask, do you know where can i find the temporary dm-verity disabler?
I tried with a script named "no-verity-opt-encrypt-5.1" (this works for the G5 Plus 'Potter') but i haven't had any success. Even i unpacked the stock boot.img and i tried to manually patch it, but i failed here too.
Honestly i would like to test the stock kernel, because i never used it, i am always attached to flashing EX to get root access. Thank you in advance.
moonlightdrive said:
Hi, sorry for ask, do you know where can i find the temporary dm-verity disabler?
I tried with a script named "no-verity-opt-encrypt-5.1" (this works for the G5 Plus 'Potter') but i haven't had any success. Even i unpacked the stock boot.img and i tried to manually patch it, but i failed here too.
Honestly i would like to test the stock kernel, because i never used it, i am always attached to flashing EX to get root access. Thank you in advance.
Click to expand...
Click to collapse
I don't know if this will still work on later builds than the November/December 2016 builds, but here's the kernel with dm-verity disabled: https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556 Seems to cause bootloops though on the later builds however
Strictly speaking, I misspoke - it's not really a dm-verity disabler, more a stock kernel with dm-verity disabled. I think EX kernel is still the more stable and more reliable option. It would be nice to be able to root the stock kernel though...
echo92 said:
I don't know if this will still work on later builds than the November/December 2016 builds, but here's the kernel with dm-verity disabled: https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556 Seems to cause bootloops though on the later builds however
Strictly speaking, I misspoke - it's not really a dm-verity disabler, more a stock kernel with dm-verity disabled. I think EX kernel is still the more stable and more reliable option. It would be nice to be able to root the stock kernel though...
Click to expand...
Click to collapse
Oh, i see, thanks for your response. I'll look into it to see how he did to by-pass the dm verity, and try to modify the last boot.img that we have.
I mentioned earlier in this thread about getting Error 0 whilst updating apps in Google Play. As it turns out, thanks to this tip here https://forum.xda-developers.com/showpost.php?p=73552496&postcount=57 it appears to be an error with permissions on the /data/media partition.
I managed to fix it with osm0sis' script:
Download from here https://forum.xda-developers.com/showthread.php?t=2239421 the sdcard Fix Permissions script http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
You may wish to back up your data with TWRP or ensure you have your photos and videos somewhere safe prior to flashing this.
Reboot to TWRP and backup your device.
Flash the above script.zip in TWRP and wait for it to complete. (it should be fixing the permissions in /data/media)
Reboot and you should be able to download/update apps again from Google Play afterwards. You may have to uninstall the app and re-install the app if it keeps failing.
I've got this working on a XT1642 running June 2017 stock ROM, rooted with magisk 13.3 and apps including Snapchat and Google Chrome update without issue now.
echo92 said:
I mentioned earlier in this thread about getting Error 0 whilst updating apps in Google Play. As it turns out, thanks to this tip here https://forum.xda-developers.com/showpost.php?p=73552496&postcount=57 it appears to be an error with permissions on the /data/media partition.
I managed to fix it with osm0sis' script:
Download from here https://forum.xda-developers.com/showthread.php?t=2239421 the sdcard Fix Permissions script http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
Click to expand...
Click to collapse
Useful info, this happened to me a couple of days ago. I thought it was something related to the integrated Chrome WebView in conflict with the system WebView, because it only happened when i tried to update Chrome, or any of his variants (dev, beta, canary, etc). Thanks.
This is a list of Nougat ROMs for this device and it's clones.
The list will be in the following format:
ROM : Version : Device : Tested/Untested
LineageOS : 14.1 : MMXC5 / E481 : Untested
Resurrection Remix : 5.8.4 : MMXC5 / E481 : Tested
crDROID : v3.5 : MMXC5 / E481 : Tested
AOSGPX : 7.1.2 : MMXC5 / E481 : Untested
There are also ROMs for the Elephone P8000, however the first time I tried one I got into a bootloop. It could just have been that I didn't wipe my caches, or it could have been a fault in the ROM; nonetheless I haven't tried any others from that device.
I couldn't find any for other devices, let me know if you see others.
Here is the factory firmware, as according to this post (Direct Download).
Also, the stock recovery: Original Post | Direct Download.
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
elbastardo1 said:
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
Click to expand...
Click to collapse
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
BereiBlue said:
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
Click to expand...
Click to collapse
Only bug so far is the kill app button not working (long press the back button) and sometimes after reboot sim cards not being detected. Usually it corrects itself after a few minutes. If not, I'll just re-flash the fix
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
elbastardo1 said:
Only bug so far is the kill app button... and sometimes after reboot sim cards not being detected...
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
Click to expand...
Click to collapse
Happy to hear only minor bugs. I'm waiting on black Friday SD card to ship and then I'll be able to test too.
On lollipop all I needed to use was power nap to kill unwanted wake locks. I'll definitely try to get it to work because batter life is important to me. Only reason I'm upgrading is because of older exploits that stock didn't get updates for. Other than that stock with xposed is extremely stable for me.(30-60 days between reboots)
Do you know if crDroid is using stock lollipop kernel or is it a ported kernel? That would effect battery life greatly I suppose.
review of roms
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me a part of this rom was made by another group of people that were not given credit.. Default browser loads the homepage of the other group. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
BereiBlue said:
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me this was made by some Russians. Default browser loads RU homepage. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
Click to expand...
Click to collapse
Just wondering with the ROM testing, did you disable the LiveDisplay nonsense? It drops my FPS to about 10, and is enabled by default.
Sorry, didn't read your whole post. I didn't find UI stuttering unless I enabled weird kernel stuff, or had L Speed installed.
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
tinpanalley said:
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
Click to expand...
Click to collapse
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
elbastardo1 said:
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
Click to expand...
Click to collapse
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
tinpanalley said:
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
Click to expand...
Click to collapse
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
elbastardo1 said:
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
Click to expand...
Click to collapse
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
tinpanalley said:
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
Click to expand...
Click to collapse
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
elbastardo1 said:
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
Click to expand...
Click to collapse
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
tinpanalley said:
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
Click to expand...
Click to collapse
You could flash a lollipop twrp backup, if anyone uploaded one or if you made one before. But if you don't have it, only way is by sp flash tool and original firmware (which is not a recovery flashable zip).
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Teblakuda4o4 said:
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Click to expand...
Click to collapse
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
tinpanalley said:
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
Click to expand...
Click to collapse
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Teblakuda4o4 said:
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Click to expand...
Click to collapse
I'd just not use the radio. [emoji4]
tinpanalley said:
I'd just not use the radio. [emoji4]
Click to expand...
Click to collapse
But the thing is you don't know what else has been tampered with.