Related
I'be been dirty flashing the CM10.1 Nightlies for a couple months now - but not nightly. (I do a dalvik/cache wipe following flashing of the new nightly ROM & gapps, of course - just no "factory reset" in TWRP).
Flashed the 20130518 nightly and developed strange touchscreen errors after a couple hours - dropped screen touches, phantom-touch zooming behavior in Chrome.
Freaked out and immediately flashed back to the prior version I had flashed - 20130504 - and no problems since.
Wondering if anybody else experienced anything similar in the 0504-0518 interval. The kernel gets rebuilt with every nightly. I have to imagine this is a kernel issue, but haven't checked the kernel commit history (yet).
Just wondering if any one has experienced this in recent nightlies.
Did you actually try a clean flash?
Sent from my SGH-I747 using Tapatalk 2
peneoark said:
Did you actually try a clean flash?
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yes and no. The kernel (boot image) is always a clean flash
I've been rolling along with dirty flashing for a while with no artifacts other than gapps FC'ing a fair amount, but that seemed to be true right out of the gate.
FWIW the rollback which resolved the problem was also a dirty flash.
TBH there is all sorts of stuff which could be done to investigate (e.g. binary search for the trouble in the 0504-0518 interval, etc) but I thought I'd ask if anybody else experienced similair issues recently... before I invest a bunch of time in it.
But a clean install is probably due.
So that's a no then. Please try a clean flash.
Sent from my SGH-I747 using Tapatalk 2
I poked around on the CM site.
It is unambiguous that they do not want problem reports about nightly builds.
I guess if someone experiences a problem with a nightly, and then goes to the trouble of trying to track it down, they need to wait until a M build is made, and then see if the problem can be reproduced in that ("stable" release candidate) - and only then open an issue in the CM issue tracking system.
As it took 5 or 6 hours after installation for the problem to show up, I think I'll just stop flashing nightlies and wait for the next stable RC. For the moment I have what I need out of earlier nightlies (Ad-hoc WiFi for tethering purposes).
FWIW, I did do a clean install last night for the 20130504-Nightly. gapps jb-20130301 still seems to FC a lot. Anyone on CM nightlies notice the same?
.
What is actually FC'ing?
peneoark said:
What is actually FC'ing?
Click to expand...
Click to collapse
My bad for using FC terminology - it is not a failure of a foreground task.
I get a toast-like popup dialog that says
"Unfortunately, the process com.google.process.gapps has stopped"
(This dialog has a single "OK" button to dismiss it.)
As fate would have it, I read your question on my phone, and thought - maybe I can find something in a logcat... picked up the tablet, turned the screen on, and it happened. So I generated a logcat.
If you are curious, I can post an excerpt. The preceding 20 seconds or so have several error conditions, starting with an exception in com.google.android.gms, and then a problem with a sync adapter, and finally a sandboxed thread failure in Chrome (the fg task). Nothing that is definitive - to my eye anyway.
bftb0 said:
My bad for using FC terminology - it is not a failure of a foreground task.
I get a toast-like popup dialog that says
"Unfortunately, the process com.google.process.gapps has stopped"
(This dialog has a single "OK" button to dismiss it.)
As fate would have it, I read your question on my phone, and thought - maybe I can find something in a logcat... picked up the tablet, turned the screen on, and it happened. So I generated a logcat.
If you are curious, I can post an excerpt. The preceding 20 seconds or so have several error conditions, starting with an exception in com.google.android.gms, and then a problem with a sync adapter, and finally a sandboxed thread failure in Chrome (the fg task). Nothing that is definitive - to my eye anyway.
Click to expand...
Click to collapse
Have you tried updating G Play Services?
peneoark said:
Have you tried updating G Play Services?
Click to expand...
Click to collapse
It apparently updates itself automatically - without asking me. As a matter of fact, immediately prior to the crash that I captured the logcat for, I noticed (in the logcat) it had just finished updating. When I say "prior", I mean less than 10-20 seconds earlier. (The installation process takes a while.)
Perhaps the pop-up is a red Herring, as the existing service needs to be stopped at some point during the installation of the new .apk. But I don't think that's what is going on here. If that really is the explanation, it means that .gms must be auto-updating rather often.
Dunno. As I said, I can post up an excerpt of the logcat.
***TL;DR***I know now that 4.3 has this bug and it is something we will deal with. I understand the causes, but the problem is buried in the kernel vs the ROM, you can still read my semi adventure but I wanted to make this edit to save you time if you think I found an answer. Overall WIFI is a huge trigger for screen wakes along with shotty or chattery reception.***
First off SlimBean is pretty much the best ROM I've dealt with, so many options, faster then I've ever experienced, and sharp looking. I've been sharking around these forums for 2 years afraid to ever make a name and post due to my lack of knowledge. I love the search options for finding answers that this forum offers to visitors and I've surely used it to root an old AT&T Atrix 4G and now my current DD the Glacier. Now I feel as though I have a little bit of sense of what the heck I am doing and would like to share my path to figuring out how to make SlimBean 4.3 work for me. Who knows maybe this may help some people that have similar problems.
The problem::: On a SEMI clean install of [UNOFFICIAL]SlimBean 4.3 \\ Nightly \\ 22.08.2013 I noticed the Glacier in standby would suddenly illuminated with light although the screen was black. It was enough to light to catch my eyes as I was starting to fall asleep. I ignored it until morning then paid attention to it happening all day at work on and off constantly with the WIFI off and just mobile network, then mobile network off, reboot, nothing seemed to help and I couldn't bare the thought of the phone's screen just on all the time.
After reading threads about HTC's possibly having bad screen made from Taiwan I was in disbelief that it was the Hardware as coming from a year old version of MIUI, I never had a problem with the screen. Leading to the idea it must be a software issue / user issue in which I must of rushed the install of the ROM or it's a quirk in 4.3.
Prior to reinstalling the same ROM, I went with trying other similar ROM's finding [UNOFFICIAL] Carbon 4.3 \\ Nightly \\ 26.08.2013 literally was just released, also a super customizable fast ROM. Everything went smooth until I played music through headphones and the illuminated black screen was back. Now I'm definitely convinced it's the software so I move on to the source code of these ROM's ev_glacier-nightly-2013.08.27.
Ev_glacier-nightly-2013.08.27 Had no screen wakes after 2 hours idle on mobile network only. I wasn't in a location with WIFI as I believe a network with a lot of information chatter may be causing these standby black illumination wakes. Back to SLIM.
SUPER clean install. 1) Format SD card completely 2) fresh download w/ checked md5 of Slimbean 3) Full Wipe "wipe data factory reset" "wipe cache" 4) format/system & format/cache manually just in case 5) Clear Dalvik 6) And fix permissions since although I believe it has no point but it's just so easy to click just in case. Probably doing things double.
Here I am now.. Slimbean is back and nothing but the .zip has been installed along with updating Nova Launcher. I am waiting to reinstall GAPPS so I can first isolate this problem within the ROM itself. What I am noticing is on just mobile network 2g/3g/2g+3g I do not get the phantom wakes, but with WIFI on it so far is only happening about 20-30 seconds after the phone drops into Standby and at least now it's not long lasting, just a few screen black flashes and it's gone. The entire 20 minutes or so I've been typing this, keeping an eye on the screen it's been quiet. Progress is being made.
Now I have thoroughly read up on and used Better Battery Stats, Wakelock detector, and Greenify to help isolate problems prior to the clean install and am waiting to install any Google apps (play store) up until tomorrow so I can pay more attention to my phone and make sure it's just a WIFI wake lock causing the screen to illuminate black. Also was toying with the idea of installing 3.0.64 kernel. I'm curious as to see if it's not just the WIFI wake lock, but all wake locks that actually wake the screen. Once I'm ready to install the play store I'm going to start combing through the device using these fantastic guides and the aforementioned apps...
[GUIDE] The Total Newb's Guide to Wakelocks ::: [HOW TO] Fix Your Skyrocket's Battery Life ::: [GUIDE] Insanely Better Battery Life When Idle
My goal with this long post is to share my experience and also commended these developers on these awesome ROM's. I will post much shorter updates on how I fixed or found the exact problem. Mainly after searching I saw similar issues but not this direct "random black illuminated screen" problem. Thanks, and be sure to call me out on anything contained in this post.
the waiting game
At 9 hours from 100% charge, I'm at 40% battery with on 1.5 hours of screen time. I went through all my settings and disabled all sounds and haptic feed back. I have yet to install any apps and am running off the bare bones of just the ROM. WiFi & 4g mobile data were on all night with the screen flashing only if I used it then locked it with the power button.
Thinking I can live with these timeout 2-5 flashes, I start browsing the forum from my phone, put it down to get ready for work, look back at the phone as it is flashing black screen rampantly on it's own. Then it holds the black screen for a solid minute or two.
WiFi chatter wake lock must be doing this... Reboot to recovery - wipe dalvik - wipe cache - reboot phone. Now to test just 4g network, flash happens on first screen lock, but not as rampant. Hmmm. My next step will be to wait for full battery drain / charge then I want to try the kernal I mentioned above. 3.0.64 kernel.
Funny stuff
Realizing the Kernel I wanted to flash doesn't work with 4.3, I hope at least some of the 86 people that viewed my post got a laugh. Even the older version of SlimBean causes the random screen flashes and the screen on while charging even with the ROM settings for such off. WiFi seems to be the greatest cause. It's as if wakelocks are actually being represented as screen flashes since the kernel is so powerful.
I just don't want to use the CM ROM...
I'm going to dig around the forums further and type in different key words of my problem just to make sure I didn't miss someone already answering this question. Slim has all the functions I always wanted out of my droid and I'm dead set to make it work...or just live with screen flashes I guess.
Hope this is a comedy for someone.
only other link
I've found on the issue I have.
http://forum.xda-developers.com/showthread.php?t=1148057
Non-Stop ROMS
1) SlimBean 4.2 & 4.3 Both have this black screen flicker / black screen wake / black screen on while charging.
2) Carbon 4.3 Had it black screen on while listening to music / black screen constant while charging
3) Evolve 3.3 based of 4.3 seemed to work fine, but I wasn't a fan of the larger Icons and screen, similair to CM 4.3 so I didn't leave it long enough to test...
4.3 CM 4.3 black screen wake almost constant / black screen on while charging... also didn't last long to really test everything.
I am down the river if I want this to just go away. I have installed all these ROM on a completey clean formated SD card each time
I'm sticking with SlimBean as it has the looks and reacts like I expect my phone to. After doing some more searching and after a little time has passed for more 4.3 development there may be a kernel that will work better for me.
Oh here is another dead end I've found... http://forum.xda-developers.com/showthread.php?t=2185747&page=3 [KERNEL] Fixed the flickering screen problem,CM10,CM10.1,SENSE3.6 4.0 4.1 That goes no where...
wifi
WiFi is the biggest culprit for the random screen wakes. I've just been living with it since I dig the slimbean 4.3 ROM so much. Thought I might pop back on here to make some closure. I worked on removing some apk's from the already minimal gapps I installed and will soon start a separate thread on just that. As long as after searching I don't find the same info I figured out.
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
thanks for the response
N_otori0us_ said:
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I see you all over the place when it comes to Glacier threads. Today at work I was searching around for a download link. I read through a ton of other ROMS threads hoping it was buried in the comments somewhere. So far I only turned up and old thread with a dead link and a couple of other threads you mentioning to other people to download the .69 KERNEL which I am guessing the full version number is 3.0.69, if it's not then there may be my first problem in finding the link...
*edit
this is the main thread I keep finding, you have so many other kernels on there
http://forum.xda-developers.com/showthread.php?p=43983635&highlight=+69#post43983635
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
reading about kernals
N_otori0us_ said:
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
All the Kernels in the Glacier Bible page you have been keeping up seem old. I'm nervous to try one since they obviously seem like they won't work. I'm game to try what ever and post on here my progress so if anyone else stumbles upon the issue they can guide their way through it.
I've been searching "kernel 3.0.69", "kernels 4.3 roms", "jb rom kernel", "4.3 jb kernel", sometimes including the term "glacier" or "MT4G" with little to no luck between XDA and just google itself. I always just find ROMS that just mention the kernel but have no downloads.
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
K is for kernel
N_otori0us_ said:
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I tried 3.0.64 kernel, not this mysterious .69 kernel you have mentioned. If you have a link or mirror of it I'll be glad to give it a go.
___________________________________________________________________________________________________
Found how you added the 2 kernels to the Bible page, I just flashed .64 again and I'm nothing but bootloops. I'll give .62 a chance since now I'll have to re-flash Slim.
___________________________________________________________________________________________________
make the double bootloops with either of those 2 kernels. I waited like 5 minutes, restarted the phone to see if it would boot and it just stayed on the slim splash screen. Of course I wiped dalvik and cache before installing either.
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
addiction
N_otori0us_ said:
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Oh yes, I head that already downloaded on the SD but the name CM_SENSE made me think it was a ROM not a kernel. The .66 kernel link is dead, but the .58 flashed & works but there is still the flicker on 4.22 SlimBean. 4.22 is so lame compared to 4.3. Even if there wasn't a flicker on 4.22 I don't think I'd keep it. Those big ICONS are just too much. I think that's why I like Carbon also. Anywho...
My addiction to messing with my phone is always in conflict with work. As if I don't have enough problem solving to deal with outside of cell phones.
I am going to try out the recovery I see in your signature, Recovery : 4EXT 1.0.0.5 RC8, just to see if it makes a difference. If you have the same phone without the same problem I must then eliminate the different variables to find the true problem. I found a "how to" and am either going to put in the time in a couple of hours or tonight. Then I'm going to start the rounds of testing ROMS / KERNELS all over again and I'll post my findings here.
I appreciate the back and forth, I actually got a can't thank anymore message because I used up my 8 yesterday~
Living with it
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
tonyMEGAphone said:
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
Click to expand...
Click to collapse
Have fun man, and If you ever need help or guidance just tell us, we'll be here
While there are several threads announcing the release of Android 5.0.1, in regard to the Nexus 6, most of them seem to be filled with posts relating to the availability, instructions for sideloading, etc.
This thread is to discuss the CHANGES that you have noticed between 5.0 and 5.0.1, and as this is the Nexus 6 section, it should really relate to changes on that device only. You may list changes you've personally noticed, or published changes, but please indicate the source. I, like many of you, no doubt, am very curious to see what is new, fixed, broken, etc.
http://aosp.changelog.to/aosp-LRX21V-LRX22C.html
On 5.0 I kept having the cloud print service or whatever keep crashing, on 5.0.1 I had the Amazon kindle app keep showing a notification Amazon kindle stopped for about 12 hours and had to reboot my phone. (Kept throwing the notification up about every 20 minutes on 5.0.1)
My phone has also been unable to chromecast netflix for the last week and I have to use my gf's nexus 6 to chromecast netflix. Weird little problems with applications on both operating systems.
Edit: Finally re-installed netflix and it fixed chromecasting.
It would be nice to see a list of changes (In language a typical person speaks rather than the jumbled mess that those AOSP changes look like)
I agree. Those AOSP changes are not that easy to understand. Also, they are just to the Android Operating System but doesn't the OTA also contain a new Modem and possibly other driver updates that would fix other issues with our phones? Those fixes and changes would not be in the AOSP list.
On a second note, why does Google do this? They obviously know whats changed. How hard is it to publish a simple list?
Is 5.0.1 fixing the slow text/multiple texts sent issue for Sprint users? People are getting my texts like 10 times quite frequently, I read somewhere that this version fixes that.
agentfazexx said:
Is 5.0.1 fixing the slow text/multiple texts sent issue for Sprint users? People are getting my texts like 10 times quite frequently, I read somewhere that this version fixes that.
Click to expand...
Click to collapse
It doesn't.
Hell, I'm on AT&T and have the slow text issue. It'll stay stuck on "sending" for 3-4 minutes sometimes. Not sure if it sends multiple times or not, haven't had anyone complain to me that they got the same message several times.
I think I saw there is a new radio... Would be interested to know if signal reception is any better
Sent from my Nexus 6 using XDA Free mobile app
banzaiwolfe said:
It doesn't.
Click to expand...
Click to collapse
What does?
Sent from my Nexus 6 using XDA Free mobile app
On 5.0 I could not connect to my company’s Wi-Fi (it would show as ‘Saved’ but no connection).
On 5.0.1 I have no issues connecting to the same Wi-Fi.
fdan100 said:
On 5.0 I could not connect to my company’s Wi-Fi (it would show as ‘Saved’ but no connection).
On 5.0.1 I have no issues connecting to the same Wi-Fi.
Click to expand...
Click to collapse
sweet, thanks for letting me know that this works now.
digging in a little deeper
https://android.googlesource.com/platform/external/wpa_supplicant_8/+/1d13911
Work around AP misbehavior on EAPOL-Key descriptor version
It looks like some APs are incorrectly selecting descriptor version 3
(AES-128-CMAC) for EAPOL-Key frames when version 2 (HMAC-SHA1) was
expected to be used. This is likely triggered by an attempt to negotiate
PMF with SHA1-based AKM.
Since AES-128-CMAC is considered stronger than HMAC-SHA1, allow the
incorrect, but stronger, option to be used in these cases to avoid
interoperability issues with deployed APs.
This issue shows up with "WPA: CCMP is used, but EAPOL-Key descriptor
version (3) is not 2" in debug log. With the new workaround, this issue
is ignored and "WPA: Interoperability workaround: allow incorrect
(should have been HMAC-SHA1), but stronger (is AES-128-CMAC), descriptor
version to be used" is written to the log.
Bug: 18411110
Change-Id: I9ae12e8882adc9e785f6e4cef9f30b89bf72dcd2
Signed-off-by: Jouni Malinen <[email protected]>
Click to expand...
Click to collapse
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1 I was roughly 34%, which was not really bad, after 12 hours of my normal use. Today, 50%, same time as yesterday. I will keep an eye on it, but thats what I'm seeing. Everything else seems about the same to me.
The issue with the face unlock camera is fixed.
5.0 is had huge problems in dim rooms buy now no issues
jackpollard said:
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1
Click to expand...
Click to collapse
I was kinda seeing this too.
N6
land2634 said:
Hell, I'm on AT&T and have the slow text issue. It'll stay stuck on "sending" for 3-4 minutes sometimes. Not sure if it sends multiple times or not, haven't had anyone complain to me that they got the same message several times.
Click to expand...
Click to collapse
FWIW I'm on AT&T and have not had this happen to me even once.
jackpollard said:
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1 I was roughly 34%, which was not really bad, after 12 hours of my normal use. Today, 50%, same time as yesterday. I will keep an eye on it, but thats what I'm seeing. Everything else seems about the same to me.
Click to expand...
Click to collapse
Now that's more like it!
Not sure if it was 501 or the gplay music update, but my music sounds much more clear now. No more cloud print crashes.. Hoping my signal issue was fixed (sprint) but as im deployed right now i only use wifi.
Is anyone else having issues adding an exchange email account using the Gmail app? BTW, I flashed my phone to the stock 5.0.1 (LRX22C) version. After returning to complete stock I rooted and flashed TWRP but the issue was present before I made those changes.
cavalier11 said:
Is anyone else having issues adding an exchange email account using the Gmail app? BTW, I flashed my phone to the stock 5.0.1 (LRX22C) version. After returning to complete stock I rooted and flashed TWRP but the issue was present before I made those changes.
Click to expand...
Click to collapse
i am not having that issue with my exchange account and gmail app
OK, I know this is a pretty old tablet but I'd at least like to be able to get a smooth browsing, email, and streaming experience out of it; I'm not looking to be able to play games or multitask on it.
I'm running the latest version of lollipop and the N7 is rooted. Experiencing frequent serious intermittent lags/crashes, I mean like 60+ seconds can pass before the screen responds, apps hang, and the device occasionally will reboot itself. Other times, the tablet runs smoothly. Was hoping that update to lollipop would resolve some of this but, if anything, it's gotten worse. I've tried the usual "fixes" of clearing the cache, forcing TRIM, closing apps manually, and even did a factory reset + cleared all caches and still the problem persists. The problem seems to occur more frequently when I run apps like the Chrome browser, which I now avoid using. Not really sure if there is a decent process documented on how to troubleshoot these types of issues to find the root cause but the tablet is presently very annoying to use at best.
What I'd like is either: a) getting some help in determining what the root cause of the issue is, or b) switching to a ROM that doesn't have these problems.
Any thoughts, suggestions, or pointers to an in-depth troubleshooting article/thread?
If you find a solution, let me know.. I've tried combos of lollipop and kernels, kit Kat and kernels.. f2fs etc.. I keep mine as a docked alarm clock and ereader for bed.. but even that takes forever.
- Sent from Spaaaaaaaaace
I don't know if this will help, but I book marked it for when I update.
http://forum.xda-developers.com/nex...ndroid-5-0-t2999635/post58567333#post58567333
I gave up and went back to 4.4.4. I can FINALLY use my tablet again...
It's the flash memory in them. It's just degraded over time. I went back to 4.4.4 and it was excellent for about a week. Then it turned useless again.
That guide posted above seems to be a placebo other than the animation's being turned off. The n7 is absolutely fine after a fresh wipe, or a factory reset. For a week... I went through the guide and the only things it had that would make a real difference was animation speeds. I'll see how it does in a week.
- Sent from Spaaaaaaaaace
hi! I was having the same problem, my n7 was super laggy and sometimes rebooted itself. that was just after uprading to lollipop 5.0.2. it kinda solved after rooting, doing a factory reset and installing lollipop 5.1. I hope it helps!
4.4.4 stock with all-f2fs rom. M-kernel r69. Both can be found here on xda.
This is how I got mine running smoothly again, even after trying several lollipop roms including 5.1.
Sent from my Nexus 7 using XDA Free mobile app
CM12 is not doing any better, I hope 5.1 could make a difference.
Stock 5.1 + Franco kernel with /data and /cache formatted to f2fs works beautifully for me. No problems at all.
I had all the same problems (and more) you and other spoke about when (a structure that holds back water and sounds like Ham) Google hounded and hounded me to install LolliCrap 5.02 (I ignored 5.0, which somehow disappeared). I HATED my #1 Nexus 7 16GB v2012. I also have a #2 Nexus 7 32GB v2012 (running HAPPILY 4.4.4) which I am still ignoring for "ham" good reason to install 5.02, an I never will install it or the latest 5.1!!
I have been exploring reinstalling the stock 4.4.4, but first I want know how to turn OFF future Google OEM Android updates and stop the "ham" badgering that there is a "new update available. But in the mean time, want to make #1 N7 useful again, I bite the bullet, backed up everything and did a factory reset and reinstalled everything. Even though I still HATE LolliCrap, my #1 N7 16GB is running pretty snappy again though some apps absolutely DON'T LIKE LolliCrap OS and are hanging and hanging and slow and crash (lazy Devs that aren't fixing whatever is causing that with 5.x). Apps I've noticed that are horribly slow with 5.x are Outlook, Skype, Yahoo Mail, Weather Underground, Drop Box, others
So, do a full reset and reinstall after backing up your data. You're gonna lose everything anyway when you Root and Boot Unlock to install an older version of Android or a custom ROM.
Hope this helps.
Glad to see another post here on the very topic I'm looking for. I'm currently running stock 5.1, completely stock, and it's just as bad as 5.0 was. I've read up enough to realize the issue is a flaw with the device, but am going to try and devote an evening or 3 to making this thing work before I completely give up on it. My goal is a minimal, feature poor but reasonably fast device for browsing, email, and some specific apps (a game or 2 and the Harmony Remote app)
Below are the areas I'm looking at, if anyone has advice or tips on any of these I'd really appreciate it:
Custom Kernel- Franco or MKernel r69? Need to investigate
F2FS - This is probably the best shot
Custom ROM - May stay stock, but if anyone knows of a lean, limited feature bloat ROM let me know!
Lightweight Browser - Can we get the original "Browser" App to install? Other options?
Basic EMail Client - not sure about this one..
The moment I saw the thread title, I knew I was not alone on this.
I remember the behavior first started with 4.4.4 actually, refusing to turn the screen on sometimes etc. I tried CM12+f2fs+mkernel 69 and it went well for a few days, then stuff broke again. I first suspected it's a RAM issue because I have two users running, but it constantly has about 150-200MB free (counting the cached apps, 400+ otherwise).
I guess I'll try slimkat 4.4.4 + f2fs modification, hope it can get the tablet running again.
Reapman said:
Glad to see another post here on the very topic I'm looking for. I'm currently running stock 5.1, completely stock, and it's just as bad as 5.0 was. I've read up enough to realize the issue is a flaw with the device, but am going to try and devote an evening or 3 to making this thing work before I completely give up on it. My goal is a minimal, feature poor but reasonably fast device for browsing, email, and some specific apps (a game or 2 and the Harmony Remote app)
Below are the areas I'm looking at, if anyone has advice or tips on any of these I'd really appreciate it:
Custom Kernel- Franco or MKernel r69? Need to investigate
F2FS - This is probably the best shot
Custom ROM - May stay stock, but if anyone knows of a lean, limited feature bloat ROM let me know!
Lightweight Browser - Can we get the original "Browser" App to install? Other options?
Basic EMail Client - not sure about this one..
Click to expand...
Click to collapse
1. For some reason Franco never boot my tablet for me...I've been using mkernel r69 and that's working really well.
2. Yep, a must.
3. Tried several custom roms and came back to stock.
4. Opera
5. Stock email, the one can be downloaded via playstore?
Rastapop with Franco kernel runs great to me. Keeping this thing alive.
VintageGuitarz said:
[...] I have been exploring reinstalling the stock 4.4.4, but first I want know how to turn OFF future Google OEM Android updates and stop the "ham" badgering that there is a "new update available [...]
Click to expand...
Click to collapse
To remove the update questions you got to root the device and disable the SystemUpdateService service of Google Service Framework and Google Play Services applications (don't know, maybe only Play Service one is really required, but better block both of them).
To do that use this application http://play.google.com/store/apps/details?id=cn.wq.disableservice
Reapman said:
Glad to see another post here on the very topic I'm looking for. I'm currently running stock 5.1, completely stock, and it's just as bad as 5.0 was. I've read up enough to realize the issue is a flaw with the device, but am going to try and devote an evening or 3 to making this thing work before I completely give up on it. My goal is a minimal, feature poor but reasonably fast device for browsing, email, and some specific apps (a game or 2 and the Harmony Remote app)
Below are the areas I'm looking at, if anyone has advice or tips on any of these I'd really appreciate it:
Custom Kernel- Franco or MKernel r69? Need to investigate
F2FS - This is probably the best shot
Custom ROM - May stay stock, but if anyone knows of a lean, limited feature bloat ROM let me know!
Lightweight Browser - Can we get the original "Browser" App to install? Other options?
Basic EMail Client - not sure about this one..
Click to expand...
Click to collapse
In my experience best custom ROM is Resurrection Remix.. I tried all tilapia Lolllipop ones except AICP, which now I'm very curious to try.. but I flashed Paranoid Android 4.6 BETA 6 yesterday and I will not change it until Google releases 5.1 firmware for tilapia too and people say this build is finally smooth and nice (well, too much hope, I know.. Lollipop will never be smooth on Nexus 7 2012, I fear )
Sofar I'm about 24 hours in using SlimKat with F2F2 (followed this post here - http://forum.xda-developers.com/showthread.php?t=2678142) using "Browser" that it comes with, and so far just GMail. Initial findings are very positive, it's quite fast, but I'm sure that could change.
Next steps (thanks for the ideas all!):
Install Opera
There's actually an update to SlimKat, but i'm waiting to see how the tablet performs as is without touching anything
Install and configure EMail client from Play store
Kernel - looks like this version of SK already uses the M Kernel so should be good there
There is an updated, F2FS modified version of Slimkat in that thread around page 90 or something.
I'm using that at the moment and it's been fine I guess.
Word of warning: recents menu is bugged to secondary user acounts. Only shows apps if they have been also installed for the primary user.
Yeah, I'm going to give myself a week or so on this older build and make sure it's stable before doing that. Definitely some stuff I miss from Lollipop in this, but if this is enough to breath new life into the tablet.. I'm willing to accept that loss :good:
Hello.
I enjoy my Nexus 7 2012 (Wi-Fi 32GB) tablet very much, when it is working properly and, unfortunately, that hasn't been often for some time. Android 5.02 helped a bit and the tablet is currently running 5.1 from a OTA update, which seemed to help a bit more. Android 5.1.1 has been mentioned however, I am not sure my issues will be helped by an update. For this reason, I am here to ask for advice or suggestions as to what I should do next (if anything!)
My first issue was the battery. The battery only lasts four hours per charge and since it is the original from 2012, I have ordered a new one and am awaiting its arrival. This tablet was a gift and whatever warranty it had has most likely expired so I am not concerned about invalidating a warranty. I hope that a new battery will make a big difference.
However, it is the second problem that is really annoying. The screen on my tablet freezes often, in any program and at any time. After charging the tablet, I've learned that it is best to restart the tablet to prolong the amount of time before the tablet freezes for the first time. Reading an article, for example, is a problem as I can read the first page but when it is time to slide the screen up to scroll to the next page, I am at risk of the screen freezing and it definitely freezes before page three. When typing a comment on Facebook or Twitter, etc. either they keyboard freezes while typing or if I can type the comment, the screen freezes before I can press the send key. I have other ways that are less portable to access these types of programs however, portability is the reason for a tablet. Using the tablet as a reader, I usually do not have any problems swiping page to page for usually as long as I'd like (although the swiping motion is a potential problem outside of the reading app.)
I backed up the tablet just prior to the 5.1 update and reset it to factory settings and for almost a week the difference was amazing. However, even with 5.1, the tablet is back to freezing again. Regarding the 32 GB internal storage; the actual available space after the OS is 28.17 GB and my available 23.90 GB. Due to the tablet's lack of response, I only reloaded a small number of apps and then, with the screen freezing multiple times in the four hours the battery allows, I uninstalled even more apps to get where I am now; I have never exceeded 50% at any time. In a browser, I often have more than one window open, yet it is the only program open. Sometimes, Facebook and Messenger are open at the same time but not always. If I get an incoming update, such as CNN, etc. if I open that for a few minutes, I'm risking another freeze. I am continuously aware of what programs are open and close them with the bottom square icon on my tablet. I have two frequent errors: SYSTEM UI is shutting down and the Process System is shutting down and they happen often. I am using Nova Launcher and the other Launcher on the tablet has been force stopped. I should probably note that I did the cache cleaning process two different times before I reset the tablet to factory settings.
Would going to something like the Cyanogen Mod be of assistance with this situation? There is an Official CM12 Mod available for this tablet however, the article I am referencing is from January 2015, written by Vinod Yalburgi titled, "Update Nexus 7 2012 (grouper) to Android 5.0.2 with CyanogenMod 12 official ROM." The tablet is already at 5.1 though and, as you have surmised correctly, I am not fluent in Mods of any type so I am unable to determine which mod is the best in this situation or if a mod is not going to be the right answer. I am open to rooting the tablet; the huge benefit I'd appreciate is the ease of creating a full back-up.
Is there another, more appropriate solution? My main concern is that if I wait for Lollipop 5.11, whenever that might be, it will not improve the issue with the screen freezing and I will have waited longer and ultimately gotten nowhere. Going back to KitKat 4.4 as I have read others have done is not appealing but if is the best solution . . .
Thank you for your patience with all of these details. I am hoping that with this info and all of the experience here, you can help me move in the right direction. Your time and any and all of your helpful suggestions are appreciated! This tablet can still work very well and as it was a gift, I want to make it work (on the days I do not want to hit it with a hammer!)
CShirey
I had the same freeze ups after the 5.1 update. I reset it 3 times to no avail! So I went back to KitKat 4.4.4. This lollipop is a big SUCKER, if you ask me... Google has screwed the pooch on this one.
? Take me to your Leader ?
Not the option I was hoping for but maybe the solution!
eLCruz said:
I had the same freeze ups after the 5.1 update. I reset it 3 times to no avail! So I went back to KitKat 4.4.4. This lollipop is a big SUCKER, if you ask me... Google has screwed the pooch on this one.
Take me to your Leader
Click to expand...
Click to collapse
Thank you for your suggestion! Does your tablet work well with KitKat 4.4.4? Any problems with freezing and battery drain? I have continued on with my research on this trying to determine what other owners have done in a similar situation. Lots of complaints but not a lot of answers, so far!
CShirey
General surprise at the lack of helpful replies!
I am grateful for the reply I received however, I am disappointed in the general lack of interest. Whenever I come to review posts here, I see that generally, most posts receive multiple answers. I am in the right forum . . . Is my question considered to be too simple . . . or did I miss an unwritten rule? Thanks.
CShirey
Sorry, had turned notifications off and forgot. It's working smoothly on 4.4.4! Should have never updated, IMO. I believe lollipop will be Google's windows vista... Hope every thing works out.
?Here, there be Whales...?