Hi there! I just got a Tab S7 (the "basic" LCD model. not the plus). I update to Android 11, factory resetted it, debloated like crazy with ADB. I'm coming from a Tab S4 that had the exact same debloat and optimizations steps.
I use this tablet ONLY to play some games. I mostly play Rules Of Survival.
Well, I'm really disappointed. The game still lags with the same graphical settings I was using on the tab S4. I was expecting to get a decent amount of free ram after debloating it but it's not that better if compared with the S4. Don't get me wrong, the game runs smoother than on the S4, but from a Snapdragon 865+ I was expecting a lot more. The super crowded scenes now are pretty playable, but it still hangs a bit quite often. I have tested it with different internet connections, same results. Lowering the graphis did not help on the S4 and it does not help on the S7.
A weird issue is related to the touch screen sensitivity. It's usually pretty good but sometimes when I have to aim precisesly with my right thumb, the whole movement of the crosshair feels super slow and inaccurate.
You know what's strage? I have tested the same game on my OnePlus Nord and I had no issues at all. A friend of mine on the latest and crappiest iPad has a bettere gaming experience than mine, for half the price.
Any hint before returning it?
I'm having some strange issues with my Galaxy Tab S7+ as well, mostly touch-related. But in overall, the tablet's performance is really disappointing. I was expecting much more from this SD865-based tablet compared to my previous one, Pixel C.
Taps are not being registered accurately. Sometimes it gets registered prematurely (before my finger actually landed), and in other cases late or not registered at all.
From time to time, the tablet would suddenly lose responsiveness, dropping or delaying a good amount of touches, that even holds and drags may break into several separate taps. In rare cases, the tablet would stop responding to touches and generates a few taps on its own at the edge of the screen (the taps are generated at one particular spot and the spot is random, but it tends to be near the navbar if brought up).
As I mostly play rhythm games in which every touch matters, such issues can be devastating. The issue is becoming more frequent since Android 11 update, with average frame rate being much worse compared to Android 10. It seems these touch-related issues become more apparent when the games start to stutter (lower frame rate).
I suspect the issue might have something to do with System UI. On Android 10, when the touch issue happens, it affects everything as I can also reproduce the ongoing issue inside Multi-Touch Test app. On Android 11, things become a bit different, as when the touch issue starts to happen in a game, it seems to affect only that game and the System UI (that it takes about 2-3 swipes just to bring out the navbar), and the impact to other apps, including Multi-Touch Test, is less than before.
I don't know what might be contributing to the touch-related issues. But the tablet's stock firmware is often seen spamming logcat at an incredible rate implying a huge amount of processing is going on behind the scenes, and from the looks of it, a good amount of the logs were audio effect related so it's possible that certain audio enhancements might be very demanding.
EDIT: I also suspected Game Optimization Service might be involved in this. However, that service is part of the core system components, with related code inside system_server, that it's not possible to disable it completely. Although I've taken out the apks systemlessly through Magisk modules (root), it only made sure the service would never be able to launch again, yet its usual routines (scanning apps and detect whether the app is a game) continues in the background, which is done by system_server on behalf of GOS.
PS: It appears Samsung is indeed not happy with people disabling these services, that they're going great lengths to deter people from doing so.
LSS4181 said:
I'm having some strange issues with my Galaxy Tab S7+ as well, mostly touch-related. But in overall, the tablet's performance is really disappointing. I was expecting much more from this SD865-based tablet compared to my previous one, Pixel C.
Taps are not being registered accurately. Sometimes it gets registered prematurely (before my finger actually landed), and in other cases late or not registered at all.
From time to time, the tablet would suddenly lose responsiveness, dropping or delaying a good amount of touches, that even holds and drags may break into several separate taps. In rare cases, the tablet would stop responding to touches and generates a few taps on its own at the edge of the screen (the taps are generated at one particular spot and the spot is random, but it tends to be near the navbar if brought up).
As I mostly play rhythm games in which every touch matters, such issues can be devastating. The issue is becoming more frequent since Android 11 update, with average frame rate being much worse compared to Android 10. It seems these touch-related issues become more apparent when the games start to stutter (lower frame rate).
I suspect the issue might have something to do with System UI. On Android 10, when the touch issue happens, it affects everything as I can also reproduce the ongoing issue inside Multi-Touch Test app. On Android 11, things become a bit different, as when the touch issue starts to happen in a game, it seems to affect only that game and the System UI (that it takes about 2-3 swipes just to bring out the navbar), and the impact to other apps, including Multi-Touch Test, is less than before.
I don't know what might be contributing to the touch-related issues. But the tablet's stock firmware is often seen spamming logcat at an incredible rate implying a huge amount of processing is going on behind the scenes, and from the looks of it, a good amount of the logs were audio effect related so it's possible that certain audio enhancements might be very demanding.
EDIT: I also suspected Game Optimization Service might be involved in this. However, that service is part of the core system components, with related code inside system_server, that it's not possible to disable it completely. Although I've taken out the apks systemlessly through Magisk modules (root), it only made sure the service would never be able to launch again, yet its usual routines (scanning apps and detect whether the app is a game) continues in the background, which is done by system_server on behalf of GOS.
PS: It appears Samsung is indeed not happy with people disabling these services, that they're going great lengths to deter people from doing so.
Click to expand...
Click to collapse
I have deeply read thru your thread this morning. This is ways beyond disappointing. I have ordered and iPad air 4. But guess what? I cannot transfer my rules of survival account from Android to iOS. I will have to return that as well.
The only tablet with at least 6gb of ram available is the Lenovo something pro blabla but it spots a lower Snapdragon with a higher price tag than the galaxy S7.
I will have to stick my galaxy Tab S4 still for a while. I have debloated it like crazy (I just did not remove the game crap system). It will be still kind of bearable for some more time.
Any hint on some alternative android tablets?
exnokiafan said:
I have deeply read thru your thread this morning. This is ways beyond disappointing. I have ordered and iPad air 4. But guess what? I cannot transfer my rules of survival account from Android to iOS. I will have to return that as well.
The only tablet with at least 6gb of ram available is the Lenovo something pro blabla but it spots a lower Snapdragon with a higher price tag than the galaxy S7.
I will have to stick my galaxy Tab S4 still for a while. I have debloated it like crazy (I just did not remove the game crap system). It will be still kind of bearable for some more time.
Any hint on some alternative android tablets?
Click to expand...
Click to collapse
If it's not about 120Hz display I think some other tablets, including older generation ones, might be good choices.
It's just that I don't think I'll ever pick another Samsung product anymore thanks to the GOS fiasco (app/service apks that would be automatically re-enabled by watchdogs placed deep inside system core processes by Samsung themselves).
As for going for an iPad... sadly, thanks to g00g13 & 4pp1€ intentionally placing barriers on doing cross-platform account transitions (at least losing access to paid/non-paid in-game currencies), it certainly won't be easy to switch.
(PS, nowadays it's not even easy to migrate on the same platform. Restoring a backup, such as those done using Titanium Backup or Migrate from an old device to a new one would not work and I still need to go through the usual transfer procedures from the old device, which varies among games).
Honestly, I don't think gamers are the main audience of Samsung devices, considering how much efforts they put on security stuffs such as Knox (actually, Knox was what led to Google introducing the Safety Net, and all the problems that stemmed from it). The tablet itself appears to be more focused on office/productivity works, as features like S-Pen, air gestures, DeX are more useful for those tasks than gaming.
EDIT: As for touch issues, if you're rooted this thread (from Essential Phone forum) might be interesting. CPU and GPU governors, as well as affinities, might play a role in the issues we're having. Turned out the stock kernel has a good amount of options to tweak via SmartPack Kernel Manager.
Here I don't have any problem. When you update it, you already enter on recovery mode, wipe data, cache and fix apps ? I get little issue with my battery after update, but I perform recovery mode and do wipes and fix apps, finally all problems I get is solved.
Related
Using a 6+ at the moment, but I need android as well. I am holding out for the note edge (owned every note gen), but in the mean time I am thinking of picking up a g3 second hand (very cost effective for what you get). Now I have read all about the lag, overheating etc followed by "you can fix it if you root and tweak". I am all down for tweaking, romming etc. I just need honest opinions about the end result. Not the fanboy defense or defending the phone because you have one etc. Thanks
I do like mine quite a bit. I have gone the rooting route of course, but it wasn't too bad before that either. There's a few things that still bug me, such as not being able to trigger Google Now via my Bluetooth headset and the AUX issues. Then screen is a bit dim and the battery life is amazingly average, but beyond those the phone is pretty awesome.
nycdarkness said:
Using a 6+ at the moment, but I need android as well. I am holding out for the note edge (owned every note gen), but in the mean time I am thinking of picking up a g3 second hand (very cost effective for what you get). Now I have read all about the lag, overheating etc followed by "you can fix it if you root and tweak". I am all down for tweaking, romming etc. I just need honest opinions about the end result. Not the fanboy defense or defending the phone because you have one etc. Thanks
Click to expand...
Click to collapse
Honestly I've never had any of the mentioned issues, I've had G3 2 days before it was released. I love the phone, used to be Samsung person myself, got tired of Knox. I get at least 2 days battery, with no lag or overheating.
Maybe its my coverage area or the fact that incant stand a dim screen, but I've never been able to get "good" battery life in about any phone.
I was initially anxious when I purchased the phone. But with Xposed, Greenify, Tasker, Root, Bump!, Nova Launcher, and a variety of other tweaks, apps and freezing of bloatware, the phone just rocks now. I don't even need a custom ROM any more.
I also enjoy the look, feel and size of the phone. And I really like having the buttons on the back rather than the side. Qi charging has also been a nice frill.
The one remaining deficiency that can never be fixed is the screen in direct sunlight. Even with Lux IPS will never look as good or clear as Retina or Amoled.
I picked up the g3. I rooted and rommed, installed greenify etc. So far battery idle is great, haven't really tested usage. However, I notice there is a lag, not always but there seems to be a stutter that's almost predictable and constant. Any ideas?
nycdarkness said:
I picked up the g3. I rooted and rommed, installed greenify etc. So far battery idle is great, haven't really tested usage. However, I notice there is a lag, not always but there seems to be a stutter that's almost predictable and constant. Any ideas?
Click to expand...
Click to collapse
If you search around the forums you'll see that this is a persistent concern for a lot of G3 owners. Here are some solutions/workarounds that I think I've seen the most often:
(1) Change your launcher to something better like Nova.
(2) Switch from Dalvik to ART (and sometimes vice versa).
(3) Uninstalling, freezing or at least Greenifying an app that just isn't working well with your phone. Top candidates include Facebook Messenger, LG Keyboard and Google Play Services.
(4) Go into developer options and completely turn off Windows animation scale, transition animation scale, and Animator duration scale.
A fifth idea which I don't personally recommend is to go into the hidden menu of the phone and reduce or eliminate the built-in slowdown that triggers when your phone reaches a certain temperature.
There's a wealth of discussion regarding this topic on the XDA forums. Take some time and look around.
Personally my phone has always been lag-free so it can be done!
Henri Blanche said:
If you search around the forums you'll see that this is a persistent concern for a lot of G3 owners. Here are some solutions/workarounds that I think I've seen the most often:
(1) Change your launcher to something better like Nova.
(2) Switch from Dalvik to ART (and sometimes vice versa).
(3) Uninstalling, freezing or at least Greenifying an app that just isn't working well with your phone. Top candidates include Facebook Messenger, LG Keyboard and Google Play Services.
(4) Go into developer options and completely turn off Windows animation scale, transition animation scale, and Animator duration scale.
A fifth idea which I don't personally recommend is to go into the hidden menu of the phone and reduce or eliminate the built-in slowdown that triggers when your phone reaches a certain temperature.
There's a wealth of discussion regarding this topic on the XDA forums. Take some time and look around.
Personally my phone has always been lag-free so it can be done!
Click to expand...
Click to collapse
I've done everything you have take the time to list, with the exception of art. I guess I will try that now. Thanks
nycdarkness said:
I've done everything you have take the time to list, with the exception of art. I guess I will try that now. Thanks
Click to expand...
Click to collapse
Also switch to a different keyboard. The stock LG keyboard seems to be a lag fest, too.
So I love this little phone but some of my biggest complaints are slowness/jankiness at times and bad signal. I have the international version of the z5c and I'm using straight talk on ATT network. So here are my fixes for slowness and battery issues:
1. Turn your data off when connected to WiFi. I know this kinda stinks cause you cannot automate the data switching on/off without root but it REALLY helps with speed. The phone struggles to hold strong signal in both LTE and 3g. So turn it off when possible.
2. Use Rbrowser or RSbrowser. They were made for snapdragon devices and they are incredibly fast. I prefer rsbrowser since it has ad blockers.
3. Don't use a case. Yeah this one really sucks cause I love cases but this phone gets too hot at times thanks to the 810 processor. Having a case on just doesn't allow the heat to dissipate quick enough.
4. Remove all apps that run constantly. Use Gsam battery to find out the main problems. Also, use greenify to hibernate problem apps (Skype, wear mini launcher, textra, etc...).
5. Disable photo analyzer. This really helps with opening and using the camera app.
6. Nova launcher. Nuff said.
7. Reboot once every three days. This helps with clearing cache and opening back up some usable ram. Sucks to do, but really does work.
8. In developer options, check on the force GPU rendering. It didn't help much, but every little bit helps. Also, scale your animations down to 0.5.
That's all I have. It helped my phone tremendously. It sucks that a flagship phone needs so much help but then again, it isn't a nexus.
I haven't noticed any slowness other that with demanding apps in my current z5c. You may just have bought a faulty unit. I had 3 different ones before I settled with 007 Spectre, Rev2, Orange-branded version. There is a HUGE difference in performance among units. Maybe try getting a refund and try another one? (As I said, I did it three times before finally deciding to stay with this little cutie: ))
I'll have a detailed review of problems with the phone and the way of resolving them in a bit so stay tuned
So I've had this update for almost more or less than 2 months now, and the speed has improved just a little bit. As we all know, typical samsung software, has some glitches and stutter and all that still occurs, for some reason that I and every users don't know why this still exist. Sometimes I'm watching on Youtube, and the damn video just freezes but you can still hear the audio. But I thought maybe it's just the app so i reset the app by force stopping and clearing the data but the thing still occurs. Camera overtime, has slowed down. I don't know why but this specially occurs on lowlight situations that whenever but not always, i launched my camera, it just lags and stops and gos and it's so annoyingly slow. But most of the time, it is snappy. On the other good side of this story, i like the minimalistic Camera app. It's really just their software. Overall it is indeed snappy, but the consistency is their problem. My storage isn't even full yet, for all we know storages slow down as you're taking it all up. I've scheduled automatic restarts, i think it helped. The fingerprint, ugh i don't even wanna talk about it. I don't know how a oneplus 3 has better fingerprint than samsung's flagship. I mean it's just unreliable, i don't know maybe it's just mine??? I literally had 3 fingers assigned on my one and only right thumb just so that the phone won't have excuses lol. But no, im disappointed. It always has to be two damn tries, thats the least. Bluelight filter is now baked in, which is a very nice feature, atleast for me. Battery, i personally didn't notice any change, but thumbs up to that cos im more than satisfied with it. And as we all know, snapchat camera still sucks not only on this phone but with every android phone. The modes, man are they helpful for those times we really need to save battery. You can customize the resolution of you're desire., well not really but three choices is a lot. 720p,1080p,1440p. Now on the update, I don''t know if you noticed, my resolution is set to 1080p because the mode that is chosen after the update will automatically choose the "optimized" mode which adjusts the resolution and cpu speeds and all that according to the activity you're currenty doing. Which is another good thing. Also, google assistant arrived as well, which great! Interface has some major color and look and design changes. The status bar along with the pull down menu in my opinion has become cleaner and better looking than the previous version. The settings has been better, way way better organized than before. Samsung Pay hasn't yet to come in Canada for some goddamn reason (i know it's not suppose to be here but maybe just maybe someone from samsung reads this ****). I'll leave it here, overall, again, it's faster and snappier, app switches are better almost perfect. But you know, stutters and lags will be there. This is my review for the nougat update on my Sprint Samsung Galaxy S7. Thanks for reading!
I purchased a refurbished Nexus 9 a year and a half ago. I've used ROMs to get it to 7.x and get all the regular updates OTA, currently on the May 5th security update. I've been playing CSR Racing 2 on it for about 9 months. The game has many known issues on Android of all versions and all devices, including crashing to "desktop". This problem is more unique. At almost any given moment in-game I can get a whited out or nearly opaque white, blocky screen overlaying the game image. At the same time, usually, an ear-piercing squeal kicks off. I have the volume at zero at all times, btw.
I've done everything except wipe the thing and re-install. Interestingly, I've had the problem outside the game once, although I can't recall what I was doing at the time. I'm inclined to believe it's the hardware. I actually ordered a Shield, and should be receiving it tomorrow, believing that it's the hardware. Once that is received and the game is up and running - unless I have the same problem on the Shield (meaning the problem's in the game or my profile itself) - I will be wiping the Nexus 9 and finding out once and for all if the thing's toast. In that vein, I have two questions.
One, is there some type of diagnostic I could run to check the limits of this tablet? CSR2 is very taxing on hardware, especially Android, and pushes it very hard. I'm wondering if there's a diagnostic that is a stress tester of sorts that I could use to see if there is any specific problem with the hardware.
Secondly, is there a ROM folks think may have better hardware interfacing for the memory, CPU/GPU, than stock Android? Obviously, I'd like the diagnostic to test the hardware while the new tablet will test whether it's the game/profile. What I won't have tested is the Android OS itself. Any recommendations?
Thanks for your time and any help that you may be able to offer!
Kazz5 said:
I purchased a refurbished Nexus 9 a year and a half ago. I've used ROMs to get it to 7.x and get all the regular updates OTA, currently on the May 5th security update. I've been playing CSR Racing 2 on it for about 9 months. The game has many known issues on Android of all versions and all devices, including crashing to "desktop". This problem is more unique. At almost any given moment in-game I can get a whited out or nearly opaque white, blocky screen overlaying the game image. At the same time, usually, an ear-piercing squeal kicks off. I have the volume at zero at all times, btw.
I've done everything except wipe the thing and re-install. Interestingly, I've had the problem outside the game once, although I can't recall what I was doing at the time. I'm inclined to believe it's the hardware. I actually ordered a Shield, and should be receiving it tomorrow, believing that it's the hardware. Once that is received and the game is up and running - unless I have the same problem on the Shield (meaning the problem's in the game or my profile itself) - I will be wiping the Nexus 9 and finding out once and for all if the thing's toast. In that vein, I have two questions.
One, is there some type of diagnostic I could run to check the limits of this tablet? CSR2 is very taxing on hardware, especially Android, and pushes it very hard. I'm wondering if there's a diagnostic that is a stress tester of sorts that I could use to see if there is any specific problem with the hardware.
Secondly, is there a ROM folks think may have better hardware interfacing for the memory, CPU/GPU, than stock Android? Obviously, I'd like the diagnostic to test the hardware while the new tablet will test whether it's the game/profile. What I won't have tested is the Android OS itself. Any recommendations?
Thanks for your time and any help that you may be able to offer!
Click to expand...
Click to collapse
Hi, Kazz5...
I can't comment on CSR Racing 2, having never played it myself, however the crash symptoms you describe - a largely white, blocky, garbled pixelated screen accompanied with a loud, high pitched banshee like squealing or shrieking noise (it scared the crap out of me the first time it happened ) is certainly something I've experienced myself several times on my Nexus 9.
I've had this spectacular and very noisy crash happen whilst playing Minecraft and whilst playing old (1990s) pinball games via video game emulator apps. But it's also happened when doing something no more taxing on the hardware than checking my emails with Inbox or browsing the web using Chrome.
There doesn't seem to be any logically consistent reason why it happens or under what circumstances are required in order for it to happen. It just happens, suddenly and unexpectedly, and then I find myself hurriedly scrambling around for the power button and long pressing it in order to make the ear piercing howl go away!
I've noticed when it happens my battery is on the low side, usually less than 25%, although I'm uncertain whether this is the actual cause.
----------------------------------
A Possible Solution...
Recently I flashed the Fire-Ice kernel , primarily for the purpose of improving the thin, weedy audio that Andoid Nougat 7.1.1 suffers from on the Nexus 9. (See my post here.)
Now it could just be a complete coincidence or maybe the unique circumstances required to trigger this crash haven't yet arisen on my Nexus 9 since I flashed it - in other words, perhaps I haven't been running it long enough yet, but since flashing Fire-Ice eight days ago, I've had no recurrence of this hard and spectacular crash as you and I have described.
Flashing this kernal though, will cause complications (but not insurmountable ones) when the June OTA security patch is due from Google in around three weeks or so.
----------------------------------
Sorry I couldn't provide a more definitive solution to this problem... or suggest any diagnostics of the type you allude to or suggest solutions regarding CSR Racing 2. If this game is as cutting edge as you suggest, it may be asking more than the now two and half year old Nexus 9 can deliver.
Minecraft, old pinball games and Solitaire card games are about as high octane as it gets for me these days .
Good luck with your Shield and I hope you have a better experience playing CSR Racing 2 on it than on the Nexus 9, and which I suspect you probably will. The Nexus 9 has been riven with a variety of problems ever since it was released back in November 2014, and this seemingly random, complete crashing of the device is unfortunately one of 'em .
Rgrds,
Ged.
I read this reply via email before taking the time to come here and I just want to say thanks for such a thorough sharing of your experience and perspective! You made it clear to me that ordering a Shield was the right thing to do in my case. Interestingly, my Nexus 9 did the squeal/crash in another app soon after I posted this.
My Shield came in, upgraded painlessly, OTA, to 7.0.0 and seems to run much smoother than the Nexus 9 in every way. Yes, the screen is a bit smaller. But, frankly, I'm seeing less pixelation - I have to assume - due to the smaller screen size. The Shield runs cooler (I used to blow on the hot end of the Nexus 9 when holding it in my hands, in it's case, for longer periods of time) and the battery definitely lasts longer.
I will finish moving everything over to the Shield in the coming few days and make up my mind what I want to do with the Nexus 9. With it's large size and 4:3 aspect ratio, I may relegate it to electronic magazine reading - of which I have a few. I saw a reference to running some flavor of *nix on it. That could be interesting. A touch panel for security cameras is a thought, if do-able, as well. I'm sure more thoughts will come up, including getting a more stable Android installed on it.
Please keep me/us posted on your experiences with the Fire-Ice kernel! And thank you again!
GedBlake said:
Hi, Kazz5...
I can't comment on CSR Racing 2, having never played it myself, however the crash symptoms you describe - a largely white, blocky, garbled pixelated screen accompanied with a loud, high pitched banshee like squealing or shrieking noise (it scared the crap out of me the first time it happened ) is certainly something I've experienced myself several times on my Nexus 9.
I've had this spectacular and very noisy crash happen whilst playing Minecraft and whilst playing old (1990s) pinball games via video game emulator apps. But it's also happened when doing something no more taxing on the hardware than checking my emails with Inbox or browsing the web using Chrome.
There doesn't seem to be any logically consistent reason why it happens or under what circumstances are required in order for it to happen. It just happens, suddenly and unexpectedly, and then I find myself hurriedly scrambling around for the power button and long pressing it in order to make the ear piercing howl go away!
I've noticed when it happens my battery is on the low side, usually less than 25%, although I'm uncertain whether this is the actual cause.
----------------------------------
A Possible Solution...
Recently I flashed the Fire-Ice kernel , primarily for the purpose of improving the thin, weedy audio that Andoid Nougat 7.1.1 suffers from on the Nexus 9. (See my post here.)
Now it could just be a complete coincidence or maybe the unique circumstances required to trigger this crash haven't yet arisen on my Nexus 9 since I flashed it - in other words, perhaps I haven't been running it long enough yet, but since flashing Fire-Ice eight days ago, I've had no recurrence of this hard and spectacular crash as you and I have described.
Flashing this kernal though, will cause complications (but not insurmountable ones) when the June OTA security patch is due from Google in around three weeks or so.
----------------------------------
Sorry I couldn't provide a more definitive solution to this problem... or suggest any diagnostics of the type you allude to or suggest solutions regarding CSR Racing 2. If this game is as cutting edge as you suggest, it may be asking more than the now two and half year old Nexus 9 can deliver.
Minecraft, old pinball games and Solitaire card games are about as high octane as it gets for me these days .
Good luck with your Shield and I hope you have a better experience playing CSR Racing 2 on it than on the Nexus 9, and which I suspect you probably will. The Nexus 9 has been riven with a variety of problems ever since it was released back in November 2014, and this seemingly random, complete crashing of the device is unfortunately one of 'em .
Rgrds,
Ged.
Click to expand...
Click to collapse
I wanted to follow-up with you on an experience. I moved to the Shield K1 and have been using it since May. Something's happened with it's charging (I suspect the mini-USB port's connection as it seems to be a weak spot for many). In a pinch, to keep playing my game of choice, I picked up my Nexus 9 and gave it a full charge. I was thrilled since it was working so well. But once it hit 58% charge the weird screen and shrill shrieking returned. Now cornered, I did my best google-fu and uncovered a couple of threads that claimed I could fix my Nexus 9!
It seems many people were having success with removing the back panel (easy), gently prying a small, metal cover off of the battery's connection at the circuit board, unplugging the cable, cleaning connections with isopropyl alcohol, and re-assembling. I found a Youtube link (ifixit, I think?) there that showed how to disassemble the Nexus 9 and I was off! It seems some folks have had this clear up the problem for months and some have had it recur, fixing it again with the same procedure.
I've been using it for days in all states of charge with no return of the problem so far. It's given me plenty of time to get my warranty-replacement Shield enroute. The Shield is still much quicker. But I'm thrilled that there's not some odd gremlin with the Nexus 9. I knew I needed to track this post and your reply down in order to let you know. I hope it helps you and/or someone else!
And thanks again!
Just wanted to bump this thread as I am having the same problem with my N9 and it is steadily getting worse. When this problem first started, it would happen once every 2-3 weeks, usually when I was in Instagram. Now it is happening daily, or multiple times in a day, and sometimes it occurs right after reboot.
I have gotten frustrated enough that I am going to do a clean (reflash) of Pure Nexus, ElemX, etc and see if that has any effect.
Did you read my reply? Cleaning the connector to the battery has fixed my issues - which were constant - for weeks now!
I just got one of these Nexus 9 32GB giving to me by a family member as they upgraded to something else due to the issues with the Nexus 9 . It had the whole deal going on with the white pixelated screen freezing followed by a loud ear busting screeching noise at roughly 50% and 20% battery. I factory reset the tablet and cleaned the cache in recovery then popped back off the tablet and disconnected battery for a min or two, hooked it back up and it runs like butter so far for the last week through the whole cycle of the battery without freezing or screeching. Strange indeed but that fix works for whatever reason.
OK. So I'm sure as this tab gets out there more and more, there will be rumblings and grumblings with this generally awesome device. I've had mine (SHT-AL09) for three weeks here in the U.S. and while overall I am very happy, nothing is above some criticism and there are some things I could use some help with.
I've already mentioned in another thread having issues with the position of the volume rocker and power button as well as the overall shape. This device is not boxxy like the X2 I'm replacing and it takes some getting used to.
With this, I am deathly afraid of dropping it because of the shape. I did buy a folio wallet; but ultimately, I want a semi stiff gel case to absorb some shock. I have ordered one from China; but it looks like it could take up to 6 weeks to get it here in the US. So, I can use any advice or links for a gel case for this tab in the US. Also any recommendations for a quality gel case is likewise desired.
Secondly, this tab annoyingly begins playing music ANY TIME it connects to a blue tooth device (not sure if this is Huawei or Android.) This is real annoying when I get into my car first thing in the morning and I am met with Ronnie James Dio blaring at me before I've had my coffee. Anyone know how I can stop this from happening? My sanity demands it (BTW, deleting RJD from my library is not an option.)
Otherwise, I'm loving this tab and totally psyched to have a giant screen with LTE capability and a dialer!! Hopefully, this will set a trend and show the world we are a market best not ignored.
I had been having trouble getting Aquamail to activate the LED indicator on new messages. Supposedly, Huawei is known to make it hard for non-stock apps to activate the LED. However, in this case I eventually realized that the issue was that the LED didn't support the light blue color that was set by default in Aquamail. I changed it to red and new e-mails now trigger the LED.
I have noticed that when I adjust screen brightness via a 3rd party app - i.e. HD Widgets or Setting Profiles Lite - the screen brightness reverts to something different after I turn the screen off and back on again. This might not turn out to be an annoyance, as I kind of like the way auto brightness works on this device.
Is this thing supposed to be VOLTE capable? If so, I imagine it can be enabled via the build.prop file. I don't get VOLTE, nothing I care about too much but it would be nice.
I'd love to be able to customize the appearance/structure of the notification bar and quick settings. I used 'Color Status Bar' for this on my Sony Z3TC and it worked really well. It doesn't seem to work with Oreo.
What opens up automatically to play music when you connect a bluetooth device? That has gotta be an easy problem to solve. Also, I think it has to do with your car stereo more than anything else.
Hey, it's the stock music player. I tried changing the default music player but the stock one still starts playing every time I connect to my car radio. I heard there is a third party app to address this but I'd prefer to stay within the stock system if possible.
What I really find annoying is the bug with keyboard attached: Brightness Controll pops up randomly, interrupting my typing ... really annoying ...
(M5 Pro, Germany)
There are some differences between emui 8 on the M5 and emui 8 on the Mate SE. Didn't expect that. Not pleased about it, as they are things that get used frequently. An AOSP rom would change that of course.
I didn't find the sharp edges very comfortable when typing. Found a soft tpu case that makes things a lot better. Not a fan that the main camera sticks out a bit which seems like it would get damaged when putting the tablet down on a hard surface. Again, the case helped with that.
Didn't like that the navbar was eating up screen space but found an option to use the finger print scanner as the nav bar, which I prefer after getting used to it.
Overall I'm enjoying the tablet, love the display.
Okay, since we're airing grievances
I think the design of their hardware for phones is awesome, works perfectly. I don't think the same design translates to tablets. Tablets are held and used differently than phones, thus need an appropriate sized bezel, weight etc.
Just my .02
AsItLies said:
Okay, since we're airing grievances
I think the design of their hardware for phones is awesome, works perfectly. I don't think the same design translates to tablets. Tablets are held and used differently than phones, thus need an appropriate sized bezel, weight etc.
Just my .02
Click to expand...
Click to collapse
I generally agree - but really the only thing I would change on the 8.4 version is the placement of the fingerprint sensor, which is too easy to press on accident when holding the tablet in landscape orientation and typing or what not. It should be nearly to the far right of the tab's bottom area, not dead center.
And really, this would be obvious to any ux designer testing the product, the problem is there is too much emphasis on blindly copying Apple and Samsung. Apple is a cult and Samsung makes extremely high quality hardware that isn't always user friendly.
My two issues right now is that 3rd Party Music apps don't show the album cover and stuff on the lockscreen. And that my device vibrates like twice after rebooting it.
Couldn't find a workaround so far
Here's a minor annoyance - try sending a text message to a number without typing a '1' before the number...you'll get an error message: '(555) 555-5555' is not a valid recipient.' Instead, you have to type out 1-555-555-5555.
Just checkng in. Brought this up when I started the thread, but has anyone found a way to stop the stock music player from starting up every time the tab is connected to any bluetooth audio device?
steveyal said:
Just checkng in. Brought this up when I started the thread, but has anyone found a way to stop the stock music player from starting up every time the tab is connected to any bluetooth audio device?
Click to expand...
Click to collapse
Music doesn't start playing automatically for me when I connect bluetooth headphones. Maybe it has to do with my config.
Here are some threads that might help you:
https://forum.xda-developers.com/mate-10/help/bt-auto-plays-music-t3700769
https://forum.xda-developers.com/mate-10/help/disable-stock-music-player-stop-auto-t3718770
No updates since March on my M5 8.4" Uk wifi?? WTF Huawei, you never change
@kedge probaly you would like to have a look at HFF, there are several new updates available. Either do a manual update using HFF or wait another few days until the update arrives via OTA.
Only update there seems since the one I have is 151 but not approved.
Still really not a good sign not having monthly security updates.
kedge said:
Only update there seems since the one I have is 151 but not approved.
Still really not a good sign not having monthly security updates.
Click to expand...
Click to collapse
Now it seems that 151 is approved... Then it is probably coming
Inviato dal mio CMR-AL09 utilizzando Tapatalk
Anyone got any opinions on the screen/ratio for reading pdfs and web browsing? I'm on the fence about getting one of these.
I have firmware version .122 i found on FF that there is .123 available and approved for install so i use vpn to force update but during install it fails at few percent that it failed to verify. What to do?
Thanks
Also does the storage option for SD install of apps do something?
Still not able to figure out how to stop the damned music app from blaring every time I connect via bluetooth to my car stereo. I'm thinking the problem may be at the car stereo end as others are not having this issue. My latest nuisance is constantly turning on the screen accidentally. Wondering if there is any way to customize the screen wake up options. Maybe changing the behavior of the front facing button or something else. I was also having problems with applications shutting down mid text while using a third party keyboard. (Swype.) I finally had to delete the keyboard and go back to stock.
So for me the screen density was driving me nuts. Everything was way bigger than my previous tablet, even after setting the view mode to "small".
I fixed this by going into developer options and setting the smallest width to 750. More fits on the screen now. Much better.