Related
This really isn't a battery related thread, this is just a bit of history about my issue. I got the Vibrant the day it came out. The battery would drain at a ridiculous pace with absolutely no use. After I rooted my phone and applied RyanZA's OCLF my battery tripled in life. I could go 2 full days or a little more without recharging and using it like I normally do, which isn't much really. An average day is a couple internet searches, a call or two, and several google talk messages.
After the JI6 update my battery is terrible once again. In 3 hours and 31 minutes I have lost %31 from just checking the battery drain. I did make a call earlier today while it was still on the charger and I find it interesting the battery use app included that call in its list of useage because the phone was still on the charger, oh well.. thats a different topic.
I have never done any custom roms or anything crazy. Just root + OCLF. I have tried juicedefender but turning features off completely to save battery is not acceptable to me. I have reconditioned the battery (however I did not clear the batt stats, I didnt have to after the root+lagfix and the battery performed wonderful without doing so.) I apparently still have root because Superuser says its granting SU permission.
I admit several issues I had were fixed in the JI6 update so I don't want the entire thing removed. What I'm finding people say on the forum is that the JI6 update increased the power usage for the radio. I have searched for JI6 radio related topics but I'm finding only pieces of information and other personal opinions plus conflicting information regarding it.
After reading many posts about battery drain I'm concluding an issue with battery drain is real. The people reporting 12-15 hour battery life and considering that good are absolutely insane or dont know what they are saying. Some people are getting lucky though and not having this issue. I used to be in that boat.
I want to try and rollback the radio update to see if this fixes my battery problem. Is there a way to rollback the radio update to what I had previously so I can get my battery power back?
You should do this. Save everything you want off the Internal SD card as well as your External SD card. Or just copy everything from within both so you have everything. I would then erase everything in the Internal SD card by issuing this command by dialing *2767*3855#. This will bring you back to stock state.
Then download Odin v1.3, download the stock ROM file and 512 pit file, put phone into recovery mode, and bring your phone back to stock state.
Then add all the .apk's, mods, etc that you want. Go into recovery and do a NANDROID backup. That way, if you ever do a new modification, you can restore it to your previous state instantly and easy.
If you plan on doing mods or updates to your phone, you should be doing this already Good luck!
I also have been making update.zips of my own with the apps and mods I want to apply after a fresh stock rom install.
Please be aware that nandroid does not restore the kernel or baseband (aka radio aka modem.bin).
I didn't know this before doing a nandroid and flashing a new ROM. There were issues, so I restored. Functionally everything is back to what it was, but kernel and baseband still match the new ROM. Some searching revealed that yes, nandroid does not back up and restore kernel and baseband.
I got the update notice and it didn't change anything; I presume this is because it saw a JI6 baseband, not JFD.
I haven't seen a recommendation on saving/restoring kernel/baseband other than a complete reflash, such as with Odin. It seems like adb-pushing the files back on top of the existing ones ought to work. I know that sounds like a dangerous thing to do to a running OS, but the way Linux filesystems work, the file isn't really overwritten on the fly, a new copy is made, and the old goes away when all processes using it terminate.
I'm not inclined to try it; I doubt if the OTA notice will happen again, anyway. I will just use Odin to get the update, when I feel the need--as it stands, I'm happy with how the phone is running.
For reference, there are at least two situations resulting in a black screen on the VS985.
This thread only addresses the issue of purposely rebooting the phone either with an app or built in reboot menu resulting in a black screen and requiring pulling the battery OR mashing down the power button for long enough to turn the phone off and then back on, at which point the black screen issue is resolved. Discuss the other black screen issue(s) or any other issue elsewhere, please.
I am not looking for further guessing/speculation in this thread. If you want to do an extended, detailed series of tests and post your results here, you're more than welcome.
For further reference, this problem has been with the VS985 since it came out. It has happened to myself and to others on official LG builds ranging from 10C to 35B. It previously happened for me personally about two times on either 12B, 10B or 11C. On my phone, the LED does not blink while on this black screen and in my experience that only coincides with the OTHER black screen issue not covered in this post. Additionally, sometimes the VS985 can take longer to shutdown when you choose to either shutdown or reboot, during which it displays a black screen and a blinking LED during this shutdown process for as long as a minute or so, that I've noticed when it happens.
I'm done trying to narrow this down for now, probably permanently.
Link to my documentation of my process and test results: https://docs.google.com/spreadsheets/d/1l65S1FcU_ngh5q4VcMzZMOxGbzutZPlUoiPhLswj2YE/edit?usp=sharing
Summary of the results:
Things that definitely do NOT make the black screen reboot issue happen more often than it did on any other stock or stock-based VS985 ROMs, from 10B through 35B:
1. 35B in general (ROMs, stock, rooted, unrooted...).
2. 35B bootstack.
3. F2FS.
4. @xdabbeb 's kernel that comes with his VS985 v2.0 ROM.
5. Using either the "adrenoidler" or "disableapps" mods for this ROM.
6. I don't think it's Xposed. If it is, it's in combination with something else that's elusive, because I performed 70 reboots in a row with Xposed installed and configured to varying degrees (detailed below in rounds #s 4-11) with no sign of the problem.
7. A huge list of apps that I restored via the built-in LG Backup from my previous installation - the one represented by the first three rounds of testing which did exhibit the issue.
8. Restoring system data via the built-in LG Backup, admittedly taken from an LG Backup from a few weeks previous.
9. I don't think it's the 3MinitBattery mod posted in @xdabbeb 's VS985 v2.0 ROM thread, since in the last several rounds of testing, I was able to reproduce the problem and I hadn't flashed that mod.
I did something at this point in testing which is commonly done by lots of people including myself, (edit for clarity) and after doing this, the problem started happening again in rounds 12-14. I won't report what it was because I can't determine what, precise part of it would cause the problem - *IF* it in fact had anything to do with it. I won't lead anything else to be rumored.
I just had the black screen reboot issue rebooting from TWRP after restoring a nandroid.
This further eliminates:
10. Any ROM.
11. Any kernel.
12. Charging the phone for long periods of time.
I've rebooted 140 times documented and probably at least another 20 or 40 or so undocumented.
Reserved 1.
Reserved 2.
I just had the black screen reboot issue rebooting from TWRP after restoring a nandroid.
This further eliminates:
10. Any ROM.
11. The kernel.
Added to OP.
What ROM and bootstack are you using. I just know what I experienced. My booting to black screen issues started when I flashed Xdabbeb's ROM and 35B bootstack. Before I was on stock 35B unrooted and didn't have any problems.
Running xdabbeb's 2.0 Rom, I had constant issues with booting. It was really bad on cold boots. I like to charge my phone overnight with power off. I find that it helps save battery life. Every morning, it would take me a couple of tries to finally boot. I tried reflashing rom and bootstack. I redownloaded both, flashed and still had issues.
Finally I flashed Jasmine 9.1 but only on 24B bootstack and I have had no issues. Ever boot from cold, reboot, to and from recovery has had no issues. I was going to flash 35B bootstack to run with Jasmine but at this point, I don't want to mess with it. My phone is running great, no need to tempt fate.
I know you are not finding any root causes for your booting problem. But for me, it was clearly my phone, xdabbeb's rom, and 35B bootstack. Those 3 did not play well together at all.
Look at the documentation I linked to.
Thank you for giving this issue some focus, i would not exactly rule out kernel/rom, using jasmines or skydragon 35b rom on my device does not cause the boot issue, also fulmics rom doesn't do it as often as cloudy 2.5. if you flash the kernel from fulmic over cloudys rom,, it improves the reboot problem. Keeping in mind that the original kernel used in cloudy rom will reliably give the issue on every cold boot.
Is there anybody running a non-verizon rom that does not have this issue, if so could you post your root/recovery method?
based of my reading, and i could be wrong, the issue is with running lollipop on a kitkat boot-loader that may be causing the issue, yet again i can be very wrong about all of this.
bulletbeef said:
Thank you for giving this issue some focus, i would not exactly rule out kernel/rom, using jasmines or skydragon 35b rom on my device does not cause the boot issue, also fulmics rom doesn't do it as often as cloudy 2.5. if you flash the kernel from fulmic over cloudys rom,, it improves the reboot problem. Keeping in mind that the original kernel used in cloudy rom will reliably give the issue on every cold boot.
Is there anybody running a non-verizon rom that does not have this issue, if so could you post your root/recovery method?
based of my reading, and i could be wrong, the issue is with running lollipop on a kitkat boot-loader that may be causing the issue, yet again i can be very wrong about all of this.
Click to expand...
Click to collapse
You're welcome.
It you look at the linked documented specifics of the tests, you'll see that I had 70 consecutive reboots with no issue at all while I was on the KitKat bootloader while running on Lollipop.
In order to do process of elimination tests, you have to change very discreet things between tests. This results in a lot of reboots, relatively minor changes between tests, and occasional backups in TWRP.
It's the closest to a "controlled environment" that I can produce.
I'm not about to add even more variables to the mix with using CM or international stock based ROMs when I was able to produce the problem with statistical reliability on a VS98535B stock based ROM.
Thanks anyway.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
Oh i see, i didnt realise that all tests done were on 35b. My device does not hav the issue at all on vzw stock roms only the d855 based roms and aosp i have the issue.
Thanks again and please dont abandon research on the issue.
bulletbeef said:
Oh i see, i didnt realise that all tests done were on 35b. My device does not hav the issue at all on vzw stock roms only the d855 based roms and aosp i have the issue.
Thanks again and please dont abandon research on the issue.
Click to expand...
Click to collapse
No sweat, you're welcome. We'll see, after a while the tediousness of the testing wears me thin plus I achieved my main goals which was to eliminate certain things which had been rumored by some to be causing it to be worse: the 35B bootstack.
I might actually add Xposed and G3TweaksBox to the list of things eliminated because I had 40 reboots (from memory) without a problem while G3TweaksBox was installed and at least I think 20-30 of those with G3TweaksBox's app data restored the same as it was in the first 30 reboots during my initial setup when I was able to reproduce the issue consistently, so I don't really think Xposed or modules have to do with it either.
My observations:
I've never had this issue on my daily driver setup, SkyDragon 2.0.1 (yes, I prefer KK) running 12B bootstack with Xposed (G3Tweaksbox, App Ops, others).
A few days after xdabbeb's ROM was released, I wiped my device, installed the 35B bootstack, and then the xdabbeb ROM. Without doing any additional customization or setup (before I even installed any additional apps), the black screen reboot issue happened every single time I rebooted my G3, requiring a battery pull.
Due to that and the lack of a compatible G3Tweaksbox at the time, I wiped my device, flashed the 12B bootstack again, and restored my SD2.0.1 backup. Have yet to encounter the black screen reboot issue again.
Data point
I bought my first VS985 in August 2014, and I've never seen this. I was rooted (w/ stock recovery) from 10B through 23C, and then reverted to 100% stock.
The other VS985 has never seen it either, but it's less than a month old.
I did have the Reboot black screen issue happen once tonight with the Quick Reboot app. If I resume any testing of my own I'll probably do separate test runs off the Xposed and Quick Reboot methods in case there's some difference. Last times I had tried reproducing the issue I was only bothering to try the Xposed method. It's also possible this "one off" occurred as part of what we consider the normal rate of this happening, since we still expect this to happen some no matter what we do due to our overall previous experience of this happening at least some on this phone.
I'm not sure if this was discussed or not but I'm just going to throw it out there, I can tell on the vibration when its rebooting whether or not it's going to boot to a black screen! If it's going to boot to a black screen it'll be a short vibration, if it's going to boot normally it will be a longer vibration. Have you noticed this?
---------- Post added at 05:50 AM ---------- Previous post was at 05:49 AM ----------
I am thinking it might be a hardware or twrp issue
davidstjohn1 said:
I'm not sure if this was discussed or not but I'm just going to throw it out there, I can tell on the vibration when its rebooting whether or not it's going to boot to a black screen! If it's going to boot to a black screen it'll be a short vibration, if it's going to boot normally it will be a longer vibration. Have you noticed this?
---------- Post added at 05:50 AM ---------- Previous post was at 05:49 AM ----------
I am thinking it might be a hardware or twrp issue
Click to expand...
Click to collapse
That's interesting regarding the vibration, thanks for the info.
Hardware, yes, that's one of the things that has remained a possibility.
TWRP no. As I indicated in my test details, I went through 70 consecutive reboots without failure (and I had TWRP installed the whole time).
roirraW "edor" ehT said:
That's interesting regarding the vibration, thanks for the info.
Hardware, yes, that's one of the things that has remained a possibility.
TWRP no. As I indicated in my test details, I went through 70 consecutive reboots without failure (and I had TWRP installed the whole time).
Click to expand...
Click to collapse
Well i have noticed a significant difference in the vibration duration when closely watching it go through the the process. Also it has happened to me using cm 12.1 on a regular basis as well.
I have a vs985 (total of 3 all together-counting replacements for the casing crack) . I never had this problem until recently, now it happens very frequently. For me it seems to have started since I started flashing bootstacks. I am a novice, but I am wondering if there is a subtle change in the partitions that is left behind by changing the bootstack? I have tried a factory reset. But still have this issue. Very strange as it just started recently. I have never done an internal sd wipe... Was wondering if that can be done and if it would help? Any thoughts?
tmord1 said:
I have a vs985 (total of 3 all together-counting replacements for the casing crack) . I never had this problem until recently, now it happens very frequently. For me it seems to have started since I started flashing bootstacks. I am a novice, but I am wondering if there is a subtle change in the partitions that is left behind by changing the bootstack? I have tried a factory reset. But still have this issue. Very strange as it just started recently. I have never done an internal sd wipe... Was wondering if that can be done and if it would help? Any thoughts?
Click to expand...
Click to collapse
Did you take a look at the details of my testing? I did 70 tests in a row without a problem, both after and before being able to replicate the problem by changing the things I detail. Flashing KDZs and TOTs changes the same things as the bootstacks - actually more than the boostacks. The only exception is the bootloader (aboot.img) and Download mode (laf.img) partitions, which are kept at an older version in order to still be able to get into TWRP, and to be able to flash any KDZs and TOTs you want.
JasmineROM and SkyDragon change most of the same partitions, and either always have, or have since at least v2 or v3 of both.
I'm sorry if I'm a bit harsh, but it's been speculated so many times that it's the boostacks. Please everyone stop spreading rumors and only report what you have strong evidence for that you tested. That's one of the reasons I did these tests to begin with to show all the things that it can't be. Between items 9 and 10 in the first post, I posted that I did something very common, after which the problem started happening a lot more predictably. I'm not reporting what it was because in order to be at least 99% sure, I need to narrow it down further so that more rumors and speculation aren't spread.
I am not looking for further guessing/speculation in this thread. If you want to do an extended, detailed series of tests and post your results here, you're more than welcome.
Again, I'm sorry for being harsh but hearing the same things over and over being rumored without real evidence is really tiring.
I hope we can find a fix for this issue! Good thing the G3 has a removable battery or this problem would be even more annoying. For my G3 this problems seems to happen more when I try select restart and happens less when I just pick power complete off then power back on. Also this has happened while flashing CM nightlys. I select install update, and my G3 powers down then black screens, and then I pull the battery and boot into TWRP manually and the CM updates starts to install automatically. To avoid this issues as much as I can I usually just select soft reboot in the menu. Either way I am glad no matter what devolves found a way to bypass the boot loader and install TWRP. I Don't think I would still have my G3 is there was no way to run AOSP Roms
Here is a question I have.
Does this happen on other G3 models or just the VS985?
Just wondering
Also on back Friday I bought a MOTO 3 for a backup for $10 at best buy so I may have to try doing some test with my G3 and see what the results are!
clapper66 said:
I hope we can find a fix for this issue! Good thing the G3 has a removable battery or this problem would be even more annoying. For my G3 this problems seems to happen more when I try select restart and happens less when I just pick power complete off then power back on. Also this has happened while flashing CM nightlys. I select install update, and my G3 powers down then black screens, and then I pull the battery and boot into TWRP manually and the CM updates starts to install automatically. To avoid this issues as much as I can I usually just select soft reboot in the menu. Either way I am glad no matter what devolves found a way to bypass the boot loader and install TWRP. I Don't think I would still have my G3 is there was no way to run AOSP Roms
---------- Post added at 07:29 PM ---------- Previous post was at 07:28 PM ----------
Here is a question I have.
Does this happen on other G3 models or just the VS985?
Just wondering
Click to expand...
Click to collapse
You can also hold down the power button for like 10 seconds I think, to force shut it off. I don't know the answer regarding if it happens to other G3 variants.
I was running a custom L ROM until recently... Switched to testing some custom M ROMs... went well, then decided to go stock M. I used a TWRP backup someone posted for the initial upgrade. It completed, and was a laggy mess. I ran that way for three days. No updates.
fast forward to now...
last weekend I flashed full, proper stock M ROM (the DLOAD folder trick)
Within 30 minutes of first boot, I got an OTA- Cust something or other update
I accepted it.
Now, I see a new section in About Phone- it's labeled Custom version
What the heck is this?
Dead_Dude said:
I was running a custom L ROM until recently... Switched to testing some custom M ROMs... went well, then decided to go stock M. I used a TWRP backup someone posted for the initial upgrade. It completed, and was a laggy mess. I ran that way for three days. No updates.
fast forward to now...
last weekend I flashed full, proper stock M ROM (the DLOAD folder trick)
Within 30 minutes of first boot, I got an OTA- Cust something or other update
I accepted it.
Now, I see a new section in About Phone- it's labeled Custom version
What the heck is this?
Click to expand...
Click to collapse
I saw the cust update in my updater and thought it was the result of downloading a custom recovery. However, I downloaded the full firmware package from the Huawei site and extracted it. The documentation also referred to cust. It appears that this update was so minor that rather than change the version/build, they just added in the cust part. Weird. But I went ahead and accepted the update through updater, and it installed just fine without wiping my apps and data. I did revert to stock recovery and unrooted before I did so, of course.
roflofogus said:
I saw the cust update in my updater and thought it was the result of downloading a custom recovery. However, I downloaded the full firmware package from the Huawei site and extracted it. The documentation also referred to cust. It appears that this update was so minor that rather than change the version/build, they just added in the cust part. Weird. But I went ahead and accepted the update through updater, and it installed just fine without wiping my apps and data. I did revert to stock recovery and unrooted before I did so, of course.
Click to expand...
Click to collapse
Noticed anything different? Does it run any smoother? I had to go back to CM13 as it just seems like my phone starts to slow down after a few days on stock MM.
jordant2 said:
Noticed anything different? Does it run any smoother? I had to go back to CM13 as it just seems like my phone starts to slow down after a few days on stock MM.
Click to expand...
Click to collapse
It's only been a day, but I'll say that there seems to be a slight improvement in battery life and memory utilization. Someone mentioned that this patch was supposed to improve the GPS performance but I haven't had a chance to test that. Speedwise, I haven't had any slowdown issues before or after the update. Then again, I'm coming from a 1st gen Moto E so by comparison anything else seems lightning fast. As long as they keep pumping out solid updates, I'm gonna stick with stock.
roflofogus said:
It's only been a day, but I'll say that there seems to be a slight improvement in battery life and memory utilization. Someone mentioned that this patch was supposed to improve the GPS performance but I haven't had a chance to test that. Speedwise, I haven't had any slowdown issues before or after the update. Then again, I'm coming from a 1st gen Moto E so by comparison anything else seems lightning fast. As long as they keep pumping out solid updates, I'm gonna stick with stock.
Click to expand...
Click to collapse
I got this cust update a few days ago and it seems to have fixed my GPS issues. Maps used to take forever to get a GPS fix and frequently lost the fix every few minutes. Now it gets a fix in seconds and I haven't had a dropout yet.
When I first installed the update, the internal storage was showing up as 2GB. Couldn't figure out why so I just did a factory reset and everything is back to normal (internal storage reporting as 16GB), and the GPS still works well after the reset.
Hi all, I have a Z5C E8305, it just updated to 7.1.1 latest release xx.160.
Since then my battery lasts much less, everything is leggy, even whatsapp or camera, and for instance, switching out from chrome and going back again, lost the current page and caused a reload (before it didn't, for example for form completing).
I tried Sony companion for a repair, and it is actually much less leggy, but still slow, higher ram usage, battery drains and chrome cache resets and is slow on window switching (actually any window reloads when switching now) and slow icon loading when hiding all windows.
I read a lot through rooting but it is way too painful (unlocking bootloader, rooting, wrtp or clocked flash boot plus flash new room, too much for me and it didn't really work smoothly when I tried)
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
JeansenVaars said:
Hi all, I have a Z5C E8305, it just updated to 7.1.1 latest release xx.160.
Since then my battery lasts much less, everything is leggy, even whatsapp or camera, and for instance, switching out from chrome and going back again, lost the current page and caused a reload (before it didn't, for example for form completing).
I tried Sony companion for a repair, and it is actually much less leggy, but still slow, higher ram usage, battery drains and chrome cache resets and is slow on window switching (actually any window reloads when switching now) and slow icon loading when hiding all windows.
I read a lot through rooting but it is way too painful (unlocking bootloader, rooting, wrtp or clocked flash boot plus flash new room, too much for me and it didn't really work smoothly when I tried)
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
Click to expand...
Click to collapse
LineageOS is definitely better right now for most things than the official 7.1.1. I actually just switched from LineageOS 7.1.1 to stock 7.1.1, hated it, and actually downgraded to stock 6.0.1 with Xposed. I feel like that gives me the most control, but I might switch back to LineageOS depending on if they start doing nightlies or anything interesting like that.
JeansenVaars said:
Hi all, I have a Z5C E8305, it just updated to 7.1.1 latest release xx.160.
Since then my battery lasts much less, everything is leggy, even whatsapp or camera, and for instance, switching out from chrome and going back again, lost the current page and caused a reload (before it didn't, for example for form completing).
I tried Sony companion for a repair, and it is actually much less leggy, but still slow, higher ram usage, battery drains and chrome cache resets and is slow on window switching (actually any window reloads when switching now) and slow icon loading when hiding all windows.
I read a lot through rooting but it is way too painful (unlocking bootloader, rooting, wrtp or clocked flash boot plus flash new room, too much for me and it didn't really work smoothly when I tried)
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
Click to expand...
Click to collapse
camera not as good without stock roms (unless install&backup DRM\FIX ) which not so easy
BUT you can roll back with fashtool without unlock btloader (im staying witch stock 7.0) untill sony fix(if they'll fix), or warranty is over.. which will comes 1st
cyberwytch said:
LineageOS is definitely better right now for most things than the official 7.1.1. I actually just switched from LineageOS 7.1.1 to stock 7.1.1, hated it, and actually downgraded to stock 6.0.1 with Xposed. I feel like that gives me the most control, but I might switch back to LineageOS depending on if they start doing nightlies or anything interesting like that.
Click to expand...
Click to collapse
I'd love to try it, but unlocking bootloader plus installing a new one (clockwork or the other one), plus the mix up between my non-standard edition E8305 and most current release not being any guides up-to date. Its daunting for a newcomer like me.
I saw on Sony's website forums that a factory reset helped with battery and memory usage. I am going to try that when I have a few days off as the lag is annoying me. But I also have audio stutters when listening to music and audio books now.
sky.walker said:
I saw on Sony's website forums that a factory reset helped with battery and memory usage. I am going to try that when I have a few days off as the lag is annoying me. But I also have audio stutters when listening to music and audio books now.
Click to expand...
Click to collapse
Clean install is your best bet in fixing most issues
Factory reset helped at first but after a week of using it it became slow again
No matter what I did, full wipe in FlashTool included, 7.1.1 never had any free ram and I could only background one, maybe two apps. Everything was slower than I've ever seen in a stock rom in any device I've owned!
Currently I've reverted to 6.0.1 and it provides a pleasing combination of speed, battery life, and tweakability with xposed.
Yesterday I took a gander at patching the one xposed feature I actually need into 7.0, but I gave up after a few hours. Maybe I'll try another weekend sometime, but writing/debugging smali is painful! I think I'll just stay on 6 for now and hope xposed makes it to 7 someday!
cyberwytch said:
No matter what I did, full wipe in FlashTool included, 7.1.1 never had any free ram and I could only background one, maybe two apps. Everything was slower than I've ever seen in a stock rom in any device I've owned!
Currently I've reverted to 6.0.1 and it provides a pleasing combination of speed, battery life, and tweakability with xposed.
Yesterday I took a gander at patching the one xposed feature I actually need into 7.0, but I gave up after a few hours. Maybe I'll try another weekend sometime, but writing/debugging smali is painful! I think I'll just stay on 6 for now and hope xposed makes it to 7 someday!
Click to expand...
Click to collapse
Any chance you can help me revert to 6 or 7.0?
JeansenVaars said:
Any chance you can help me revert to 6 or 7.0?
Click to expand...
Click to collapse
1. Just backup everything you need (backing up whole apps isnt recommended though when you switch android versions).
2. Download and install Flashtool.
3. Open XperiFirm from inside Flashtool, select and download the firmware you need. It will bundle it automatically in a flashable ftf file.
4. Once you are sure you backed up everything, flash away.
Wipe everything. If you have TWRP and dont want to lose it, dont wipe FOTAKernel.
Good luck :fingers-crossed:
try disable Movie Creator app
trax7 said:
1. Just backup everything you need (backing up whole apps isnt recommended though when you switch android versions).
2. Download and install Flashtool.
3. Open XperiFirm from inside Flashtool, select and download the firmware you need. It will bundle it automatically in a flashable ftf file.
4. Once you are sure you backed up everything, flash away.
Wipe everything. If you have TWRP and dont want to lose it, dont wipe FOTAKernel.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks. Im back to 5.1.1 and running smooth. Not sure how long to wait before giving Last version another shot
JeansenVaars said:
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
Click to expand...
Click to collapse
I did this; copied from the sony forums:
"Android 7.1.1 is not the culprit, but the recently updated Movie Creator app!
1: Disable MOVIE CREATOR
2: Reboot in SAFE MODE
(while phone is on, press Power button, hold Reboot option for 1 second)
3: Reboot again to normal mode
4: Enjoy 2 days of standby time"
My phone seems much better now.
I also disabled the Sony music app as I was having audio troubles, but not sure if it was necessary.
mceyhan4 said:
try disable Movie Creator app
Click to expand...
Click to collapse
sky.walker said:
I did this; copied from the sony forums:
"Android 7.1.1 is not the culprit, but the recently updated Movie Creator app!
1: Disable MOVIE CREATOR
2: Reboot in SAFE MODE
(while phone is on, press Power button, hold Reboot option for 1 second)
3: Reboot again to normal mode
4: Enjoy 2 days of standby time"
My phone seems much better now.
I also disabled the Sony music app as I was having audio troubles, but not sure if it was necessary.
Click to expand...
Click to collapse
You guys think the guilty was the movie creator? My phone was barely usable. Full ram usage, battery drain and everything was laggy and hanging
what was firmware just prior to 32.4.A.0.160 (7.1.1) ???
Hello could you kind folks please guide me what was official (not rooted) Sony Z5C firmware prior to the above monster? I want to go back but don't know which one it was? Please link me to official version just before this latest ( 32.4.A.0.160 (7.1.1)) NASTY update! Many Thanks.
JeansenVaars said:
You guys think the guilty was the movie creator? My phone was barely usable. Full ram usage, battery drain and everything was laggy and hanging
Click to expand...
Click to collapse
Yes, surprisingly.
I went from ~15MB of free memory (and the associated problems complained about: laggy transitions, program openings, home page icons, etc). back to ~250-300MB free and typical performance.
Actually usable performance is a little better given they have one of the cortex A57's more aggressively clocked.
I'd try. You can always restore if you desperately want Movie Creator and see no benefit.
BlackFriar said:
Yes, surprisingly.
I went from ~15MB of free memory (and the associated problems complained about: laggy transitions, program openings, home page icons, etc). back to ~250-300MB free and typical performance.
Actually usable performance is a little better given they have one of the cortex A57's more aggressively clocked.
I'd try. You can always restore if you desperately want Movie Creator and see no benefit.
Click to expand...
Click to collapse
What about the issue with browser page reloading every time you switch to a different app and then back again to the browser? OP reported this issue, and I've been having it, too. Did that get resolved for you with the disabled Movie Creator crap?
trax7 said:
1. Just backup everything you need (backing up whole apps isnt recommended though when you switch android versions).
2. Download and install Flashtool.
3. Open XperiFirm from inside Flashtool, select and download the firmware you need. It will bundle it automatically in a flashable ftf file.
4. Once you are sure you backed up everything, flash away.
Wipe everything. If you have TWRP and dont want to lose it, dont wipe FOTAKernel.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Wait. So can you actually downgrade with bootloader locked? I'm asking because I'd like to keep my ta partition untouched.
Sent from my E5823 using Tapatalk
Superrman said:
camera not as good without stock roms (unless install&backup DRM\FIX ) which not so easy
BUT you can roll back with fashtool without unlock btloader (im staying witch stock 7.0) untill sony fix(if they'll fix), or warranty is over.. which will comes 1st
Click to expand...
Click to collapse
can you give link to the official flashtool and where to get ftf 7.0 android file for sony z5c?
Kiers said:
can you give link to the official flashtool and where to get ftf 7.0 android file for sony z5c?
Click to expand...
Click to collapse
Google "Flashtool" - it's literally the first result there. Also, Flashtool has XperiFirm, which can download almost all firmwares for Xperias and pack them into ftf format automatically.
---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------
Tomixxon said:
Wait. So can you actually downgrade with bootloader locked? I'm asking because I'd like to keep my ta partition untouched.
Click to expand...
Click to collapse
Yes, just flash an older version with Flashtool, it's how we got TA backup to be possible
HI, All
I have had Nord 2 three months now. First Nord 2 was in service 3 times. So I got new device. Now this new has been two times at service. I have rooted both with TWRP (denniz) and Magisk of course.
I was wondering if TWRP is causing all the problems or is it just that Nord 2 does not like to be rooted.
And now I am thinking not to root but root has its benefits, so I guess I'll root but which method, TWRP or not.
Have you had problems after rooting? If you have, have you used TWRP and Magisk or just Magisk, no TWRP??
It would be nice if you would share your comments.
Thank you
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
Hi and thank you for reply.
That was new to me but explains a lot. But also I remined that my 1st Nord2 got new motherboard (IMEI and S/N was different) and now my new Nord2 has new motherboard. So after replacing motherboard it should be as totally new. But still with 1st device I end up problems. I have not rooted my new Nord 2 because my intention was to find out if it is TWRP which is causing problems or is it the device - hardware vs OS after root rocess regardless TWRP or not.
Basically is Nord 2 working as "normal" devices after rooting or not.
To tell you the truth, I am fed up with this phone too
Hi jis251: we can shake hands. After the 4th (!) stockrom-flash by a OnePlus-servicecenter and still having strange behaviour (for example I was not able to set a fingerprint, the device-motor just kept shaking when I tried), they "decided" that my motherboard was broken. It was switched under warrantee and after that I messed up something and then a "regular" stock-flash didn't work either. You DO need to flash stock (@servicepoint or by yourself), then REBOOT into STOCK recovery, WIPE EVERYTHING, and flash stock again (with OnePlus-tool only they have).
The problem is that OnePlus (and their servicecenters) are NOT aware of this (and probably don't care). But once rooted with strange behaviour this is a must.
For now, fingers crossed, everything seems to work. I have TWRP 3.6 (Denniz) installed, Magisk 24.1, several modules (AFWall Boot AntiLeak, BuiltIn BusyBox, F-Droid privileged Extension, Magisk Bootloop Protector -not sure if this does anything, not tested-, Shamiko, Universal SafetyNet Fix and Zygisk LSPosed.
Also in LSPosed I have 4 modules activated: AFWall+, Disable FLAG_Seure, XPrivacyLua and GravityBox [R].
This setup works and passes SafetyNet without problem. Banking Apps work. The only thing I cannot get to work (keeps detecting root) is my Cupra App (for my car - same as Volkswagen App) as posted here: Cupra
The setup on my OnePlus 7 pro (A10) and Nord 2 5G (A11) - both stock roms - is the same. Both pass banking apps but the Volkswagen/Cupra app they do not. I can live with that as long as that is the only exception. It sucks, but privacy above all ;-)
after a week no broblem with my rooted nord 2 (twrp+ magisk canary) all working as well!
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
No way. I had my phone serviced at the same place and now I don't get OTA updates anymore and have to install them manually. My Bluetooth is also working less reliably. I had my suspicions but thanks for confirming it.
You DO need to flash stock (@servicepoint or by yourself), then REBOOT into STOCK recovery, WIPE EVERYTHING, and flash stock again (with OnePlus-tool only they have).
Click to expand...
Click to collapse
Just to be clear: is it possible to do by myself? Or is their tool required in this step? But yeah I was really hoping flashing would be as straight forward as with my previous OnePlus phones
Kenaestic said:
No way. I had my phone serviced at the same place and now I don't get OTA updates anymore and have to install them manually. My Bluetooth is also working less reliably. I had my suspicions but thanks for confirming it.
Just to be clear: is it possible to do by myself? Or is their tool required in this step? But yeah I was really hoping flashing would be as straight forward as with my previous OnePlus phones
Click to expand...
Click to collapse
Hi Kenaestic, so you are from The Netherlands as am I? Honestly, I don't know if you can do it yourself. Maybe with the tool from (I mean Pankspoo) you can put back all the partitions etc., get to some kind of "stock-state" and be able to wipe everything in stock recovery. But I am just not sure.
I am kind of "ready" with this phone. I am on version 17 (stock A11) and once rooted I decided to not take anymore OTA's. The phone is just way too unreliable. And it IS my daily driver for work, so I can't risk it. It freaks me out that I can't "normally" flash back a stock rom, an d I am too unexpierenced for ASB, commands, etc. I'm an user, not a programmer.
I got 5 (!) reflashes from The Phone Laband a new mainboard. Once, I got suspicious when a TWRP-folder was STILL THERE after a stock-re-flash. From that moment on, and all the problems with fingerprint and PIN-locks, that something just survives that factory flash (I always managed to mess things up by rooting).
Now the damn thing works (and really I still like it). I came from the OP7pro, but this device is just so much lighter and better in the hand (not top-heavy). It's snappy, it's fast. But in the meantime I will start working on my OnePlus 7 pro to get E/OS running and finally my goal is to de-google. Once that works, the OP Nord 2 will be sold and the OP7 pro will be my back-up phone.
The Nord 2 is good and I love it, but software is a failure. Never a MediaTek-device for me again.
exis_tenz said:
Hi Kenaestic, so you are from The Netherlands as am I? Honestly, I don't know if you can do it yourself. Maybe with the tool from (I mean Pankspoo) you can put back all the partitions etc., get to some kind of "stock-state" and be able to wipe everything in stock recovery. But I am just not sure.
I am kind of "ready" with this phone. I am on version 17 (stock A11) and once rooted I decided to not take anymore OTA's. The phone is just way too unreliable. And it IS my daily driver for work, so I can't risk it. It freaks me out that I can't "normally" flash back a stock rom, an d I am too unexpierenced for ASB, commands, etc. I'm an user, not a programmer.
I got 5 (!) reflashes from The Phone Laband a new mainboard. Once, I got suspicious when a TWRP-folder was STILL THERE after a stock-re-flash. From that moment on, and all the problems with fingerprint and PIN-locks, that something just survives that factory flash (I always managed to mess things up by rooting).
Now the damn thing works (and really I still like it). I came from the OP7pro, but this device is just so much lighter and better in the hand (not top-heavy). It's snappy, it's fast. But in the meantime I will start working on my OnePlus 7 pro to get E/OS running and finally my goal is to de-google. Once that works, the OP Nord 2 will be sold and the OP7 pro will be my back-up phone.
The Nord 2 is good and I love it, but software is a failure. Never a MediaTek-device for me again.
Click to expand...
Click to collapse
Haha ja zeker So this is something I have noticed as well. I'm in the same boat as you. I'm not a programmer and I come from a device where flashing was way easier. But for some reason this phone has persistent data on it that can not be reset or wiped. Maybe it was intended as a security measure. When you flash TWRP you probably noticed you can not boot into it without a commandline on your computer. Otherwise it will completely ignore the volume down + power combination and go straight to booting the OS. So I'm guessing OnePlus made it harder to tamper with the recovery. But for rooting it's only confusing, gives me headaches but most importantly; when you accidentally remove the ADB server authentication you're screwed because there is no recovery to boot into. I'm really hoping the miracle workers in the modding community find a way to work around these things. Because I first just thought it's kinda janky because they used a few work arounds to get TWRP running as fast as possible when the phone came out. But now I just don't know anymore. Anyway, I have an appointment with ThePhoneLab tomorrow and I'll report back if it did anything. Cheers.
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
I agree to some point... When it comes to rooting and updating when rooted this Phone is a p.i.a. If kept stock it is not to bad... But you want root for a reason. I think it is because of the mediatek processor. But I am struggling with it too. I am on A16, with TWRP, not rooted. I want to go back to stock (locked bootloader), but I am having a hard time to understand how to do it. I would appreciate a step by step guide.... The ones on XDA so-far haven't helped me any further...
Ik zit dus in hetzelfde schuitje... (sorry for the Dutch) really curious if "The Phone lab" can fix it
The Phone Lab can only re-flash stock (not repair). You'll loose all data.