Random reboot with lollipop 5.1 - Nexus 7 Q&A, Help & Troubleshooting

I installed loillipop 5.1, from scratch using the factory image. All went smooth and the performance was much better than with 5.0.2 (which was my previous version), but I have random reboots unless I stay connected to the wall. This can be easily reproduced by putting the tablet to sleep (i.e., I pressing power button). Immediately my nexus reboots (99% of times).
I tried everything possible. Factory reset. Reistalled after formatting every possible partition. Reistalled starting from scratch without using my google backups. Nothing helps.
The only solution was to come back to 5.0.2 (again through the factory images, flashing and formatting everything).
Last test I am going to do is to use the OTA to go from 5.0.2 to 5.1 but I do not have much hope.
Anyone else experiencing similar problems?
It looks like an hardware issue put in evidence by the new kernel that is part of 5.1, but it could eb enything else.

Greetings.
Have you tried using any other kernel, eg. franco kernel?

Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Thanks for the suggestion, I didn't know Franco had released a version of his kernel for 5.1. I tried latest M-Kernel but it is not working with 5.1. Now I am sideloading the OTA from a stable 5..0.2, just to see if going to 5.1 using OTA helps. Will report if I succeed and in case I didn't will try with FK (and report).
Meanwhile, any other suggestion is welcome

Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Current situation after some more tests:
5.0.2 from factory image (full wipe): works
5.0.2 -> 5.1 via OTA: reboot each time goes to sleep (unless wall powered or attached to PC USB)
5.1 from factory image (full wipe): same as above
rastapop 5.1 (full wipe): same as above
5.1 + franco kernel R82: same as above
I would try to increase CPU voltage: any suggestion how to do? Which kernel to use? Which app to adjust voltages? I am going to try with franco kernel and trickstermod (which I already bought) but I am not sure this combination will allow me to adjust voltages.
EDIT: no way to adjust voltages with FK for 5.1. Reverting back to 5.0.2 and waiting someone gives suggestions or has similar issues (or releases new kernels)

Sideload 5.1, same issue. Even worse than 5.0.2.
Sent from my Nexus 7 using XDA Free mobile app

killerfrank said:
Sideload 5.1, same issue. Even worse than 5.0.2.
Click to expand...
Click to collapse
Even in your case the device reboots just after entering sleep mode? Please confirm, I thought I was the only one, but if this happens to others then it must be a software issue, not hardware.

This does not happen at all to me(using stock 5.1 with Franco Kernel).

This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.

_Hobbz said:
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
Click to expand...
Click to collapse
It looks like a mixed hw/sw problem. It is indeed clear that 5.1 works on most N7, either being installed from factory images or after an OTA upgrade, but for some of us it results in rebooting when the machine goes to sleep.
I attached last_kmsg (/proc/last_kmsg) just after the problem manifested. This is exactly what happens every time I put the device to sleep (pressing the power button or leaving it alone for a couple of minutes) and it repeats always the same (with the same kmsg).
Anyone knows how to extract other information that could be useful to isolate the source of the problem? Notice that I cannot do a catlog since the device doesn't go to sleep if it is connected to a PC (so I cannot recreate the problem).

Your battery is dying, I've been getting the same problem until I replaced the battery today.

richarddwyer10 said:
Your battery is dying, I've been getting the same problem until I replaced the battery today.
Click to expand...
Click to collapse
A hardware problem related with the power unit of the device was also my first hypothesis, but under 5.0.2 i everything works perfectly and the battery has the original duration. Under 5.1 also everything works... until the device goes to sleep. Only then it reboots.
Was this the behavior in your case?

I've been getting the same issues on my N7 since updating.

regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....

ondoy1943 said:
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
Click to expand...
Click to collapse
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.

gianpaoloc said:
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
Click to expand...
Click to collapse
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.

_Hobbz said:
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
Click to expand...
Click to collapse
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks

I've given up on LP for the N7. I've gone back to KK. Stability is awesome, performance is great. LP was a disaster on the N7. Performance issues, lock ups, etc. No matter how many times I clean installed it, etc, it just wasn't good.
I'm now officially calling it Lollipoop (at least for the 2012 N7). But, it is an old device. I'm still waiting to see how it turns out on my LG G3 phone. I'm sticking with KK on that phone as well for now until I know for sure it runs well on it.
Stability over bleeding edge.

Hi
JFYI, I have just updated my 2 sons' N7 2012 (coming from Omnirom) to Lollipop 5.1 (with Nexus Root Toolkit v2.0.4, meaning following the same procedure)
- 1 of them fine
- 2nd one with the issue reported here; which is why I'm on this thread now
updated kernel to franco r82
the issue remains...
will keep checking this thread
thansk
beng

gianpaoloc said:
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
Click to expand...
Click to collapse
So I can't post links yet because of my low number of forum posts but if you google 'nexus help after update to 5.1, it won't wake up after in sleep mode, please help' then it should be the first result that shows up.
Things were running fairly well for me with the slimkat 5.0.2 rom on F2FS so I'll likely switch back to that while this gets sorted out.

I've had my n7 for 2 years now, flashed all kinds of custom Roms, bricked it, fixed it, encrypted it, unencrypted it several times, and It has never ran as slow as it did on lollipop. I tried, 5.0, 5.0.2, and 5.1 I even reset kk to stock and let the ota's do the job and no matter what, LP is still not usable in my opinion. I feel sorry for the people that take the ota and do not know how to revert back to kk.
Sent from my Nexus 7 using Tapatalk

Related

GPS fix that does NOT require OS upgrade, stay on JWR66N/JSS15J/CM10.2

I noticed some folks had perfectly functioning tablets except for the GPS issue and were concerned upgrading to JSS15Q might introduce multi-touch or other issues.
They might currently be on JWR66N or JSS15J and just want the GPS fix and nothing else.
I put together a fix that will accomplish just that.
It has been tested on JWR66N and JSS15J.
I will warn you that I've made my best effort to make sure this doesn't cause additional issues, but you always take a risk when making changes to an otherwise working system, although in this case, I consider it small.
If you are already running custom recovery, ignore the instructions below, just flash as any other update.zip
You need your bootloader to be unlocked.
You need to one-time load TWRP (or CWM) into memory but do NOT need to overwrite your existing stock recovery.
You do NOT need to be rooted.
Downloads
download TWRP custom recovery
rename to twrp.img and place in your adb (platform-tools) directory
copy update-GPS-lock-fix.zip to your tablet's virtual sdcard
Within command prompt in your adb (platform-tools) directory
adb reboot bootloader
fastboot boot twrp.img
Within TWRP
install update-GPS-lock-fix.zip
reboot (do not choose to install SuperSU unless you want it)
I am willing to give it a try in a day or two if you don't get enough people to test this, I'd do it now but I upgraded to JSS15Q already so I'll have to reflash the previous version and I have some assignments to finish first.
Sort of off topic, but as someone who had very good touchscreen response on JSS15J and now has minor issues on JSS15Q, is there any way for me to extract and apply the touchscreen settings from JSS15J update into anything in the future? This is assuming that Google uses the touchscreen settings from JSS15Q in future updates since they appear to consider them a "fix".
Anyway, thanks a lot for creating this patch for us.
I don't know if the touchscreen firmware is flashed onto the tablet by the kernel persistently or loaded everytime it starts, but the touchscreen firmware is contained in the kernel.
Theoretically you may be able to get JSS15J touchscreen behavior by using the JSS15J kernel with your JSS15Q ROM.
However, if the touchscreen firmware is flashed directly into hardware and the versions can only go up, then you are stuck with the JSS15Q touchscreen firmware.
So basically try flashing the JSS15J kernel and see if the touchscreen behavior changes.
If my device is rooted, can I just flash it normally?
Sent from my Nexus 7 using XDA Premium 4 mobile app
It works
Hello sfhub ...
I'm in a unique situation here. I'm on Slimbean beta3 which is based on JSS15Q and the fixes should be in place. However, something
is lost in translation and the GPS issue is still there. So I applied your fixes and (so far) it appears to fix the GPS issue.
I don't know what you did there, can you explain ? Did you just just pull the google fixes off their release ?
Thanks.
chrolmesq said:
If my device is rooted, can I just flash it normally?
Click to expand...
Click to collapse
Yes.
hyperxguy said:
Hello sfhub ...
I'm in a unique situation here. I'm on Slimbean beta3 which is based on JSS15Q and the fixes should be in place. However, something
is lost in translation and the GPS issue is still there. So I applied your fixes and (so far) it appears to fix the GPS issue.
I don't know what you did there, can you explain ? Did you just just pull the google fixes off their release ?
Thanks.
Click to expand...
Click to collapse
I extracted the GPS firmware and made it available to previous releases.
It should theoretically work with any ROM as long as it is based on stock.
sfhub said:
I extracted the GPS firmware and made it available to previous releases.
It should theoretically work with any ROM as long as it is based on stock.
Click to expand...
Click to collapse
You extracted the GPS firmware from JSS15Q?
Yes.
This fix appears to be working well.
Removed testing from title.
Given that the JSS15Q touchscreen firmware is a one-way street, no going back, there may be more interest in this solution to the GPS issue, especially if your touch screen in working acceptably well on JWR66N or JSS15J.
Navigated a couple of long trips today and worked like a charm.
Thanks.
Such a clever idea !
it does work
argh, so the fix worked perfectly, GPS finally works for me!! thank you!
But I am getting spammed with "Bluetooth Share has stopped" messages so the system is unusable. I will reflash the original CM, apparently bluetooth is broken by the fix.
Any ideas?
EDIT: False alarm, it had nothing to do with this fix. It was entirely related to a Bluetooth Audio "Fix".
Wow, so we broke the berardi black cloud curse? Something good happened to your Nexii? That is really something!
sfhub said:
Wow, so we broke the berardi black cloud curse? Something good happened to your Nexii? That is really something!
Click to expand...
Click to collapse
Yes hahaha finally have a working unit GPS and all.. Thank you very much for the GPS fix!!!
I rooted my N7 and kept the stock ROM. I ran the OTA update, no problems, and it fixes the GPS issue. Still on JSS15J.
Sent from my Nexus 7 2 FHD Flo (razor)
So the GPS issue is a software issue? Not a hardware issue?
Sent from my Nexus 7 using Tapatalk 4
Muikkuman said:
So the GPS issue is a software issue? Not a hardware issue?
Click to expand...
Click to collapse
For most people their GPS issue can be resolved in firmware (software).
sfhub said:
For most people their GPS issue can be resolved in firmware (software).
Click to expand...
Click to collapse
I just tried GPS outside and had 11/20 connected.
Sent from my Nexus 7 using Tapatalk 4
Muikkuman said:
I just tried GPS outside and had 11/20 connected.
Click to expand...
Click to collapse
Sorry, are you saying you had no GPS issues prior or are you saying you installed the GPS fix and now have no issues?
If latter, to help others, what OS were you running?

When waking up device, gets black screen, hangs for few secs, then reboots

When attempting to wake up device (SPH-L720) from sleep using power or home button, it doesn't wake up, gets blank screen, the menu and back soft buttons LED lights come on, hangs for few secs on the black screen, then reboots by itself. Issue happens randomly and sometimes once a day or multiple times an hour. It seems like the problem existed before rooting and installing custom ROM but I've just noticed it.
I'm using TriForce 3.0 ROM (Android 4.2.2) w/ baseband L720VPUAMDL and kernel 3.4.0-KT-SGS4-ga23d84c. I've tried wiping/reinstall ROM, reflashing back stock ROM, removing microSD card. Nothing helped. The battery charges properly and is usually fully charged. No wear and tear or damage of any kind. Device is 1 month old.
Any ideas what might be causing the problem and suggestions for possible fix?
its because of the kernal, mine does this aswell..
kyledb said:
its because of the kernal, mine does this aswell..
Click to expand...
Click to collapse
Did you find a fix? Does changing the kernel fix the problem? If so, which kernel did you go with? It's driving me crazy lol. Thanks!
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
beerindex said:
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
Click to expand...
Click to collapse
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
verto8 said:
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
Click to expand...
Click to collapse
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
beerindex said:
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
Click to expand...
Click to collapse
Same situation here. I rooted and flash a custom ROM on mine right after I got it. I believe it had the issue pre-root on stock ROM/kernel, but I'm not a 100% sure. I had same issue w/ the Cyanogenmod ROM, not sure what kernel it was using.
kyledb said:
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
Click to expand...
Click to collapse
Do you remember if you had the issue on stock ROM before rooting? I believe mine has always existed and might be a hardware problem because I tried different ROMs/kernels and issue persisted with all of them.
ParkerParker said:
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
Click to expand...
Click to collapse
Is there a comparison thread of different kernels? I'm wondering what the pros/cons of each and maybe some user experience feedback. I believe mine was rebooting as well when it was on stock before rooting. This seems like it might be a hardware problem rather than software (ROM/kernel). Do you think everyone w/ a Sprint Galaxy S4 (SPH-L720) is having this issue? If so, Samsung should do something about it because it's super annoying!
Update: I've been using latest version of KT-SGS4 kernel 3.4.59 (Aug 25 build) for over a day and it's been pretty stable w/ no occurrence of the problem. I'll keep this thread posted w/ updates if I run into any problem. Thanks to everyone for their help!
2nd Update: it still has the problem.
It's still happening but at a slightly lower frequency with the latest KT-SGS4 kernel. For those who have tried a different kernel, did it fix the problem? I'm trying to narrow down the source and convince myself for certain that it's a software rather than a hardware issue.
Same issues
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
grnerd said:
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
Click to expand...
Click to collapse
Try that and odin back to stock mf9 not mdl. Tri-force is mf9 based so maybe thats why you get those issues because you need firmware kernel modem and such. Also it could be that kt kernel had been reported to cause some of those issues.
i went to a new rom and new kernal and this is still happening to me, i have no idea what it is now.... any solutions from anyone?
UPDATE: BAD MICRO SD CARD!!!!!!!!!!! REMOVED MY SD CARD AND NO ISSUES IN THE PAST 2 DAYS
NEW UPDATE: SPOKE TO SOON..

[Q] freezes on 4.4.2 custom roms / kernels

on the latest d802 4.4.2 custom roms and kernels i get a lot of freezes.
it will freeze in the middle of an animation and will take some seconds up to some minutes and then working normal again.
sometimes i have to hard-reboot to get out of freeze / lag.
on older 4.4.2 slimroms i never had this behavior, only since some weeks with new roms / kernels.
i`ve tried every rom / kernel combo but sooner or later i will get a freeze again.
could a revert to stock and re-rooting / flashing custom rom maybe a solution? i`m afraid to do this because of the long time to backup my 32gb data.
what are your experiences with the latest 4.4.2 roms and kernels? did you find a solution for this with any combo or fixes?
help would be appreciated.
push! no one else with same problems? maybe i got a hardware defect?
paratox said:
push! no one else with same problems? maybe i got a hardware defect?
Click to expand...
Click to collapse
The only thing I can say is I own the VS980 version of the device and i've tried every single 4.4 rom offered on this sight and have the same issue with all. Most of the time i'm using the device and it freezes, sometimes reboots, and sometimes comes out of it after a few minutes. Also not being able to wake the device only seeing a black screen and forced to hard reboot device. 4.3 seems to be a much better with these issues but not completely solved for me. I'm hoping the release of 4.4 source from lg will fix these issues but i'm unsure. So at least your not alone in these problems lol. I've tried multiple kernels and governors etc. Bumping up the min freq on the cpu seems to help and changing to interactive governor but doesn't eliminate the issue just help. I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
flyinj54 said:
I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
Click to expand...
Click to collapse
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
paratox said:
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
Click to expand...
Click to collapse
Yea unfortunately it seems very common among these devices so i'm pretty confident it's a software issue although i'm not 100% sure of that. I ran a flex rom for a few days on 4.2.2 and didn't have any of the same issues.
added a poll as a matter of interest.
omni-ROM, Mokee rom, vanir rom etc.freezing problem still continues.
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
lubirdy said:
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
Click to expand...
Click to collapse
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yes, stock cm kernel.
I'm thinking back now and it did freeze once when first signing into the Google account immediately after flashing the ROM, but nothing after that. So.. nearly spotless
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Best of luck! To be specific, I'm using the snapshot release of cm11... still don't trust the nightly releases
i did a lg flash tool stock restore, factory reset and OTA updates. now the freezes did not come back until now *knock on wood*.
when i did a backup of the sd there was one corrupt media file which was not able to transfer.
maybe the media scanner did go crazy and was the reason for the freezes.
using cm11 m3 on my d802... very little freezes compared to previous nightlies, fingers crossed

[Q] last fast (really) android version?

ok, we have a nexus, so we deserve updates and we have them....that's why we bought a nexus no?....
yes....but every update is a hit for our device's performance...I thought that last one would fix performance issues, but is not .
so...I bought one of these to my gf, sure that it would work well, I owned one a year ago and it was very good! nope....is slow, lags, remembers me a 100$ cheap tablet.
I considered to downgrade....is frustrating...what version do you remember as stunning fast, like a nexus should be?
4.1? damn, is too 2012-ish....
4.2? old but at least we have tiles on notification drawer...
4.3? good, some performance goodies, hw vsync...
4.4? I thought this would be the best choice because in theory is optimised for 512mb ram devices too....but was not performing well
5.0? don't say nothing...pff
I also read about f2fs as a revolution, but is not my tablet and my gf uses it for study and I can't take it to test...
thanks for reading and answering
My 2012 Nexus 7 (wifi) I had been on Android 4.4.4 when I updated to Android 5.0 using Wugs nexus root tool kit.
It had been sluggish on Kit Kat, but got more so when I went to Lollipop, even with a full wipe.
After about a week on 5.0 I rolled back to Android 4.3, and have been happy since.
Everyone is having different experiences and mine personally is that 5.0 is running greater for me then 4.4.4. That was with a complete full wipe (including data) when I flashed the image through wugs toolkit. There were initially bouts of lag (waking up screen, lock screen, etc) but the lags pretty much gone bar a few occasions. 5.0.1 will hopefully make the system more stable and not repeat what happened with 4.4.4 because my n7 ran like a pig after that update.
tabuser said:
My 2012 Nexus 7 (wifi) I had been on Android 4.4.4 when I updated to Android 5.0 using Wugs nexus root tool kit.
It had been sluggish on Kit Kat, but got more so when I went to Lollipop, even with a full wipe.
After about a week on 5.0 I rolled back to Android 4.3, and have been happy since.
Click to expand...
Click to collapse
And how are you with 4.3? Perfect? I'm really considerino a downgrade....
I will try forma the last time a full wipe and factory image, and then downgrade until I'm satisfied.
No words about f2fs?
I have just updated my n7 to Slim rom 5.0.1.
I have been frustrated by not being able to read a simple email using gmail application. Lags, lags, and "gmail is not responding do you want to close it"
I need to have two accounts for me and my wife, so the performance was even more slow.
Now with f2fs it is a rocket. I have installed every toolvI wanted and now also the Godfire game, and I must admit that it was a hit.
So thank you google to slow our machines to force buying the new ones, but my nexus7 from 2012 acts lighning fast now.
remmyhi said:
I have just updated my n7 to Slim rom 5.0.1.
I have been frustrated by not being able to read a simple email using gmail application. Lags, lags, and "gmail is not responding do you want to close it"
I need to have two accounts for me and my wife, so the performance was even more slow.
Now with f2fs it is a rocket. I have installed every toolvI wanted and now also the Godfire game, and I must admit that it was a hit.
So thank you google to slow our machines to force buying the new ones, but my nexus7 from 2012 acts lighning fast now.
Click to expand...
Click to collapse
ok....I have to format on f2fs....that's the only way....
than...con you tell me how to do that? and also, I want to flash stock lollipop, no custom roms...
I read some but guides were outdated...and, FYI I am very experienced on flashing, so I will not take you much time
Not sure if stock can be ran on f2fs.
I installed slim rom and itis close to aosp.
Instruction is provided in the rom thread.
I am no very experienced and I handled without problems.
remmyhi said:
Not sure if stock can be ran on f2fs.
I installed slim rom and itis close to aosp.
Instruction is provided in the rom thread.
I am no very experienced and I handled without problems.
Click to expand...
Click to collapse
wait. are you running kk?
Nope. Lollipop.
Slim f2fs on lollipop?
ConstantineTheGreat said:
Slim f2fs on lollipop?
Click to expand...
Click to collapse
Have you got it? I'm not sure I want to keep lp on that tablet....how is it?
Even on my m8 lp performs bad, considering that is stock and my phone was on the top of benchmarks before nex 6 and 9 came out..
throcker said:
Have you got it? I'm not sure I want to keep lp on that tablet....how is it?
Even on my m8 lp performs bad, considering that is stock and my phone was on the top of benchmarks before nex 6 and 9 came out..
Click to expand...
Click to collapse
No, I don't have it. I just asked is there slim lollipop on f2fs, because I tried rastapop and SleamFreak which are on 5.0 and have f2fs support, but I had problems like rebooting, problem with installing new apps, etc.
So for now, till I get answer from user emmyhi, I back to slimkat KK which run fantastic on our Nexus 7.
SlimPop (f2fs) by Freak is great. very fast.
cosmickamal said:
SlimPop (f2fs) by Freak is great. very fast.
Click to expand...
Click to collapse
Yes, I can agree with you that is really fast, but I had a problem with gapps (downloaded one's give in thread) and I couldn't install Google play store (it wasn't installed with gapps???)
I couldn't resolve my problem with that, and also, even I did clean install I haven't got screen like I first time use this rom. I haven't got possibility to chose language, and everything else. Rom just moved me to homescreen. Maybe this is not for this thread, but, I'll wait some other version of slim on 5.0.
ConstantineTheGreat said:
Yes, I can agree with you that is really fast, but I had a problem with gapps (downloaded one's give in thread) and I couldn't install Google play store (it wasn't installed with gapps???)
I couldn't resolve my problem with that, and also, even I did clean install I haven't got screen like I first time use this rom. I haven't got possibility to chose language, and everything else. Rom just moved me to homescreen. Maybe this is not for this thread, but, I'll wait some other version of slim on 5.0.
Click to expand...
Click to collapse
Did you try SlimGapps Normal one from the op link. That worked fine for me. You first flash the Rom. Boot. Go to recovery again. than flash Gapps. Boot. You will get the initialisation screen.
too much beta, I can't take my gf's tablet everytime she has a problem ahahah
I will try an evening every factory image and a kk f2fs rom to see which one performs better...then I'll let you know!
I'm running stock rooted 4.4.4 kitkat on mine with Lean Kernel 4.1. No lag, no issues with apps not working like on 5.0. Good battery life ,watched over 5 hours of movies last night and still had 49% left from a full charge. Standby time is excellent, I've only lost 2% over the last 9 hours.
ConstantineTheGreat said:
Yes, I can agree with you that is really fast, but I had a problem with gapps (downloaded one's give in thread) and I couldn't install Google play store (it wasn't installed with gapps???)
I couldn't resolve my problem with that, and also, even I did clean install I haven't got screen like I first time use this rom. I haven't got possibility to chose language, and everything else. Rom just moved me to homescreen. Maybe this is not for this thread, but, I'll wait some other version of slim on 5.0.
Click to expand...
Click to collapse
cosmickamal said:
Did you try SlimGapps Normal one from the op link. That worked fine for me. You first flash the Rom. Boot. Go to recovery again. than flash Gapps. Boot. You will get the initialisation screen.
Click to expand...
Click to collapse
riggerman0421 said:
I'm running stock rooted 4.4.4 kitkat on mine with Lean Kernel 4.1. No lag, no issues with apps not working like on 5.0. Good battery life ,watched over 5 hours of movies last night and still had 49% left from a full charge. Standby time is excellent, I've only lost 2% over the last 9 hours.
Click to expand...
Click to collapse
that stock one with f2fs?
No, not here. Pure stock, rooted 4.4.4 KitKat. Removed a few Google apps I don't use, but still ext4. Lean Kennel really make a difference.
and....after a flashing afternoon....
4.2.2 stock was damn fast....
4.3 stock was even faster and smoother than 4.2.2
4.4 was worse......got better with lean kernel, but wasn't just fast and responsive enough.
the winner is....4.3......that's what I left on my gf's tablet....
everything runs good, apps opening instantly, look much 2013 but google launcher and google keyboard help...
this is my suggestion after my tests. good luck and hope next LP ota will fix some performance issues, not only on this one but for every phone which got slower with this update

Stick with PureNexus or update to Oreo?

I'm currently running the latest version of PureNexus and debating installing Android Oreo. Are there any huge downsides? Is it buggy, slow, etc? In other words, is it daily driver ready for someone who uses their phone all day for music, video, games, EVERYTHING and still wants to tweak the os to their needs.
?
Etheralrealm said:
I'm currently running the latest version of PureNexus and debating installing Android Oreo. Are there any huge downsides? Is it buggy, slow, etc? In other words, is it daily driver ready for someone who uses their phone all day for music, video, games, EVERYTHING and still wants to tweak the os to their needs.
?
Click to expand...
Click to collapse
Unless you're worried about the security updates, just stay on PN. PN for Oreo should be out soon as well.
That makes a lot of sense, thanks.
Etheralrealm said:
I'm currently running the latest version of PureNexus and debating installing Android Oreo. Are there any huge downsides? Is it buggy, slow, etc? In other words, is it daily driver ready for someone who uses their phone all day for music, video, games, EVERYTHING and still wants to tweak the os to their needs.
?
Click to expand...
Click to collapse
I was on PN since I got my 6P and updated to Oreo as soon as it came out. I don't regret the decision at all. Battery life is as good or better than PN (I routinely end the day with 4+ hours of SOT and 35-40% left. Your experience may vary depending on usage), performance is wonderful, and I haven't found any major bugs yet. All of my favorite mods work (EX kernel, Pixel mod, Camera NX, WakeBlock, and a few others I'm forgetting).
The only downside is some modifications require a bit more work. For example, to resize the navigation bar and add dynamic coloring I had to extract, modify, and push framework-res.apk instead of having those options built right into the settings menu. There's no custom quick settings tiles and I can't change the number of rows/columns, but that isn't a big deal and I've learned to live without it for now.
As stated above PN based on Oreo should be out within the next month or two. Beans posted an announcement on G+ yesterday explaining that he had a family emergency that slowed down development on PN O, but he is actively working on it as much as he can.
Etheralrealm said:
I'm currently running the latest version of PureNexus and debating installing Android Oreo. Are there any huge downsides? Is it buggy, slow, etc? In other words, is it daily driver ready for someone who uses their phone all day for music, video, games, EVERYTHING and still wants to tweak the os to their needs.
?
Click to expand...
Click to collapse
I went from PN to 8.1. Honestly, stick with PN. I used it for a couple days and I am downgrading right now. My battery life was significantly worse (on 7.1.2 I ended the day at ~40-50% battery. On 8.1 I was at ~20-30). I didn't notice anything great about Oreo and found myself missing PN.
Poebat said:
I went from PN to 8.1. Honestly, stick with PN. I used it for a couple days and I am downgrading right now. My battery life was significantly worse (on 7.1.2 I ended the day at ~40-50% battery. On 8.1 I was at ~20-30). I didn't notice anything great about Oreo and found myself missing PN.
Click to expand...
Click to collapse
Maybe your battery is just getting tired I'm finding the opposite Oreo 8.1 giving me excellent results.
Exodusche said:
Maybe your battery is just getting tired I'm finding the opposite Oreo 8.1 giving me excellent results.
Click to expand...
Click to collapse
Might be Xposed then. My sot dropped by 1.5hrs.
Poebat said:
Might be Xposed then. My sot dropped by 1.5hrs.
Click to expand...
Click to collapse
I'm gonna go back and try Pure Nexus again now that I have a new battery I could use extra 1.5 hours.
Exodusche said:
I'm gonna go back and try Pure Nexus again now that I have a new battery I could use extra 1.5 hours.
Click to expand...
Click to collapse
Good luck.
Not sure aware of this or not, but beans posted in the PN thread he's working on Oreo for the angler. So you'll soon have the best of both.
Poebat said:
I went from PN to 8.1. Honestly, stick with PN. I used it for a couple days and I am downgrading right now. My battery life was significantly worse (on 7.1.2 I ended the day at ~40-50% battery. On 8.1 I was at ~20-30). I didn't notice anything great about Oreo and found myself missing PN.
Click to expand...
Click to collapse
Hey man, how did your downgrading go? I had the intention of downgrading today but somewhere messed up and now my phone is in a bootloop. What steps did you take?
Thanks!
Ritser said:
Hey man, how did your downgrading go? I had the intention of downgrading today but somewhere messed up and now my phone is in a bootloop. What steps did you take?
Thanks!
Click to expand...
Click to collapse
I had that issue too. Spent waaaayyy to long trying to figure it out. I think 8.1 has a different encryption method. You need to wipe the phone completely and then do a nandroid restore (or flash PN)
Poebat said:
I had that issue too. Spent waaaayyy to long trying to figure it out. I think 8.1 has a different encryption method. You need to wipe the phone completely and then do a nandroid restore (or flash PN)
Click to expand...
Click to collapse
Don't mean to sound like a complete noob, but how did you go on about wiping the phone completely? I've now tried so many things, reflashing TWRP, reinstalling stock firmwares, using Wug's Nexus Rooting kit, ... I can acces fastboot, what do I need to do to be able to reinstall TWRP? Because when I try it right now, I can't acces it. It goes back into the boot loop.
Cheers
Ritser said:
Don't mean to sound like a complete noob, but how did you go on about wiping the phone completely? I've now tried so many things, reflashing TWRP, reinstalling stock firmwares, using Wug's Nexus Rooting kit, ... I can acces fastboot, what do I need to do to be able to reinstall TWRP? Because when I try it right now, I can't acces it. It goes back into the boot loop.
Cheers
Click to expand...
Click to collapse
In TWRP, format /Data and the internal storage. I also formatted /system just to be safe.

Categories

Resources