I experience some lagging when my niece plays candy crush on the device. Other programs run smoothly enough. Anyone else experiencing lagging on apps or games?
Posted via Android Central App
Posted via Android Central App
The Nexus 7 (2013) Android 5.1 Lollipop Thread
- Thread starter Ry
- Start date
Got the OTA update notice a few minutes ago. Downloaded and attempted to install, but got the installation stopped with an Error indicator and the little android robot. It was locked but eventually rebooted on its own back into 5.0.2. Now when I try to check for system updates it says my system is up to date. My N7 was rooted and unlocked. Would this have caused the error? Other than downloading the update from one of the sites hosting, is there another option for getting the system to recognize my N7 needs an update now?
Richard Eagar
Member
- Aug 14, 2013
- 18
- 0
- 0
Got the ota today, Canada, nexus 7 2013 non lte version, running great, very noticeable bump up in performance
Sent from my Nexus 7 using Tapatalk
Sent from my Nexus 7 using Tapatalk
beachfl1
Well-known member
- Aug 13, 2014
- 65
- 0
- 0
Bootloader locked or unlocked makes no difference to the automatic update process, but it will have to be unlocked for any other method.
During the upgrade, if the update finds any system files that have been altered, it will throw an error, stop the install, and undo any changes made up to that point, including changes made by rooting. You could try un-rooting and waiting for the update to appear again, but the update will very likely fail again. No, I've not read of any sure-fire way to get the update to appear again more quickly.
It might be worth it to try to download the OTA update file from the internet and try to "adb sideload" it from within whatever Recovery you have. You can find the OTA update files a lot of places, but do make sure the update file matches both your CURRENT version as well as the TARGET version.
If that fails, there are a few methods of installing the whole factory image without losing data, but the easiest and most intuitive is the Nexus Root Toolkit (NRT) by WugFresh, especially for users that might not be comfortable with the command line.
Keep in mind that version 5.1.1 is already rolling out.
During the upgrade, if the update finds any system files that have been altered, it will throw an error, stop the install, and undo any changes made up to that point, including changes made by rooting. You could try un-rooting and waiting for the update to appear again, but the update will very likely fail again. No, I've not read of any sure-fire way to get the update to appear again more quickly.
It might be worth it to try to download the OTA update file from the internet and try to "adb sideload" it from within whatever Recovery you have. You can find the OTA update files a lot of places, but do make sure the update file matches both your CURRENT version as well as the TARGET version.
If that fails, there are a few methods of installing the whole factory image without losing data, but the easiest and most intuitive is the Nexus Root Toolkit (NRT) by WugFresh, especially for users that might not be comfortable with the command line.
Keep in mind that version 5.1.1 is already rolling out.
Downloaded the update yesterday but have not done anything with the tablet since. Let see today how it performs.
I have upgraded my Nexus 7 to 5.1 in the hope that it would reinstate the camera that 5.0 stopped working. No such luck. Both front and back cameras inoperable and Camera app hangs then announces "Unfortunately, Camera has stopped." Am I the only one that has had no camera since Lollipop?
Graham
Graham
is it difficult to taker her back to 4.4.4? Mine's nothing more than a paperweight about now. . .
YAYTech
Well-known member
- Jul 18, 2012
- 2,371
- 8
- 0
Is it just slow, or another problem? What steps have you taken to try to fix it?
Got my update to 5.1 on Wednesday.
Seems a bit more responsive now, but something is draining the battery excessively.
Will have to investigate it a bit further, clear some caches etc.
Posted via the Android Central App
Seems a bit more responsive now, but something is draining the battery excessively.
Will have to investigate it a bit further, clear some caches etc.
Posted via the Android Central App
maxman1
Well-known member
- Jul 11, 2012
- 677
- 23
- 0
Just an FYI in case it might help someone. Got the 5.1 OTA and all seemed well for a while but after not using it for several days, I noted when a number of apps required updating it was painfully slow completing them. It finally did though and though I didn't do much after finishing the updates, seemed to be OK. Next time I booted up, got the persistent com.google.process.gapps error and none of the traditional fixes had any luck correcting the issue. Finally bit the bullet & did a full factory reset which resolved all problems and restored all the speed & smoothness. Took a bit of time but overall fairly painless and I can honestly say it has never ran better.
I just received the notification to update my device also. Plan on doing it when I get home from work. Can someone please explain how to do a factory reset on the N7 in case I have to do it after I do the 5.1 update. Thanks
Excessive battery drain seems to be a Gremlin that pops up for no reason. When I first got my N7 it was on Jelly Bean and battery life was great. Then I updated to Kit Kat and it went all to hades. A factory reset and system cache clear did nothing. It would dump 30-40% overnight while sleeping and did so with everything Greenified. Then I updated to 5.01 and without doing a reset battery life went back to like was under Jelly Bean. Then 5.02 came out and the device updated itself and the battery drain returned. I now just updated to 5.1 and so far (fingers crossed) battery life seems good again.
There doesn't seem to be any consistency as to why one person gets great battery life out of one version of the OS and another suffers from excessive battery drain. I tried everything including booting into Safe Mode when I was running Kit Kat and nothing helped. You might try a factory reset as some have said that has helped. Otherwise, hang on for 5.2 and hope it helps with your battery problem.
Since 5.1, my battery life is very poor. And another symptom. I have a Qi charger cradle for the thing. Wireless charging.
I put the Nexus 7 2013 of mine on the cradle, the light lights steady, indicating it is charging fine. An hour or so later, the light starts blinking, indicating the Nexus is not soaking up the charge any more. It's failed like that about a half dozen times.
I put the Nexus 7 2013 of mine on the cradle, the light lights steady, indicating it is charging fine. An hour or so later, the light starts blinking, indicating the Nexus is not soaking up the charge any more. It's failed like that about a half dozen times.
Udate went fine. The pros are clearly better functioning and memory management. Very smooth operation. The 5.0.2 had put my tablet in trouble with halting action and occasional lock ups. None of the now. Cons - just battery life. Before update, I could finish the day at 30%, now some says I need to plug in around 4p. Overall grade: B
Battery life is more important to me than any of that other stuff, so I'm going to just stay on KitKat until the tablet dies.
mxrider821
Well-known member
- Jul 8, 2012
- 505
- 0
- 0
beachfl1
Well-known member
- Aug 13, 2014
- 65
- 0
- 0
That's interesting. I'd say that for me, responsiveness and stability are way more important. I can charge my tablet if it's low, but I can't do a darn thing if it's not performing well.
I haven't run any proper tests yet, but 5.1 seems really good on all fronts for me in the couple of weeks it's been in use.
Similar threads
Latest posts
-
-
-
-
Pictures taken with the Pixel 9 Pro and XL
- Latest: BerryBubbles
Trending Posts
-
News Valerion's VisionMaster Pro 2 is the best Google TV projector yet
- Started by AC News
- Replies: 0
-
-
Samsung's new revised Android 15/One UI 7.0 rollout
- Started by ironass
- Replies: 1
-
-
Facebook
Twitter
Instagram