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.
Related
Apologies ahead of time for the wall of text...
I got my wife the Prime for Christmas. It took her a couple of days to finally open it, as I gave her the choice of going with it or the iPad2. After a couple of days, she seems to like it and is slowly getting the hang of the OS.
I've played with it some. For the most part, it seems smooth. I've managed to make it glitch (lag) a time or two by going in and out of apps and even had the launcher itself FC on me forcing me to reboot.
That was while checking out Alice in Wonderland in MyBooks, which by the way, is not exactly usable. The page animations worked at first, then stopped, then the pages stopped turning altogether and the app FC'd. Not that I care or am surprised. I'm used to included software being half-baked.
Browser experience has been fine using stock and Opera. Dolphin doesn't seem to work as well on the TF201 as it does on my Atrix. Perfect experience? No. I have a $4,500 i7 2920-XM workstation with an SSD and 16gigs of RAM at work and even with it, the browsing experience (or OS experience in general) can lag/glitch from time to time. Nature of the beast.
I can't really comment on battery life. She took it off the charger Monday night at 100%. It hasn't been used steadily for more than 1-2 hours at a time. It's down to about 15% this morning. I can't really say how many hours of use she's gotten out of it but it doesn't seem to drain much overnight, even with Facebook, email and other notifactions. It felt like it was draining pretty quick when in use but I'll have to pay closer attention.
There's minor light bleed around the edges but I had to turn the lights off during boot up to notice. I haven't attempted to watch an entire movie in the dark with it to tell if it's something that will be bothersome. I'll tell you, I went through THREE Sony XBR2 LCDs a few years ago. They suffered from horrible "clouding" (blotchy white areas all over the panel) and light bleed in the corners. That was noticeable under normal use and since I primarily watched movies in pure darkness, it was bothersome. I don't think it's going to be an issue w/ the TF201 unless I'm being nitpicky.
WiFi seems OK. I have yet to compare it to the laptop, but compared to my Atrix (CM7) it's getting the same signal. It fluctuates some, even staying in the same spot, but it's never caused a problem.
I haven't tested GPS. Something tells me it's not going to operate properly though It's low on my list of concerns and I'll use it as an excuse to return the thing to Gamestop in the next 15 days (for exchange only, which is irksome), but otherwise, I'm not too concerned. If it turns out to be hardware, I imagine an RMA will correct it. It would be cool to use the thing for GPS but I own an actual GPS and rarely use it. I would still prefer the device have its features work, of course.
Aside from the launcher FC and subsequent reboot and the occasional glitchiness/lag using the stock launcher and jumping through apps, the only other issue I've noticed happened this AM. I woke up to the room filled with light. The TF201 was on. I didn't wait long to see if it would go back to sleep so maybe it would have. However, when I got up to see what it was doing, I noticed it had rebooted. Hopefully that doesn't happen often and hopefully not while in use!
I'm confident that a lot of these issues can be fixed with firmware updates and hopefully those are pretty quick to release. Overall, I'm pretty happy with the device. Hopefully ICS will only make the experience better. And hopefully it will come soon so all of the speculation, etc can end! I know my Atrix went from all right to pretty frickin' awesome when I put CM7 on it.
Decided to try to call Verizon and again inquire about heat. I was very specific in the inquiry ... basically that I was just checking to see if Verizon had any notes about heat, now that the phone has been out for a while.
The CSR said she did see something about exchanging batteries and would pass me on the tech support as a warranty issue.
The tech support person, after a seriously long hold time, said she reviewed the Verizon trouble database, checked with a teir 2 analyst, and even called HTC.
Not surprisingly (once HTC was involved) she came back with:
1) We recommend people with heat issues use a Vinyl case to help with heat [I guess Vinyl has heat-dissipation capabilities I was not previously aware of]
2) Hard reset the phone
3) If you are streaming and your phone gets hot, stop streaming for a while
4) Buy an extended battery [did that, still gets hot]
5) This is a very powerful processor, so it will get hot.
#5 is the key. It means"we have found the excuse that will get us out of this".
The tech rep said she saw nothing about battery exchange. She acknowledged MANY internet reports about heat, but said that Verizon can only do what HTC says they can do; and that hopefully HTC would take all these reports and develop a software fix that manages the heat better.
So no joy from Verizon, which is killing me because I really want to unlock and root, but am staying away in case the phone is no good. Of course, for all I know, I don't have heat issues, but too many people saying things like "I never go above 105" have me paranoid about my phone (which can get to 115 in regular game play, and once got to 120 in a car). If I knew that "Relocked" wouldn't be an issue if I ever had to warranty in the future, I would go ahead, but ... ugh.
Anyway, in case anyone wanted to know.
Damn talk about a run-around. Normally my phone doesn't get warm until I really start using it...for example...One day just cleaning up the house and streaming Pandora for hours allowed my phone to get fairly warm.
It's never shut down on me or anything but it still is worrisome. Makes me wonder if there is an issue with all these phones but not many people REALLY use them to find out.
Well
My phone has never rebooted on me, and perhaps too many people claiming their usage never gets the phone above X degrees is simply too specific to each person to actually mean anything to anyone else (and all these stories have done, is F'd with my mind, making me think my phone runs hot when maybe it actually doesn't) ...
but, I'll tell you this ...
This is all well and good for a phone released in November. When summer rolls around, and the ambient temperature is no longer low, I think we are going to see a lot of problems and fast. If the standard user gets to 105 in a room that's 70, that means the standard user will start seeing 135 when it is hot out. Those that can get to 115 right now, that's an explosion waiting to happen come July.
I have had two Rezound's. I stream audio all day long at work, either iheart radio or sirius radio online.
Both these services cause ANY phone to get rather warm. I'm not sure what temp my first one went to, but it got so hot in my pocket I thought it was going to burn me. Even using a 2750 batt it was going dead in like 4 hours.
The phone was two weeks old. I called VZ & they wanted to send me a refurb. I told them NFW & they finally agreed to send me a brand new phone. The new phone barely gets warm in the same conditions & that same 2750 battery lasts all day now.
My phone on average use gets about 100-105, 110 if the screen is on and on full brightness for a while. Highest I've seen is 125 when I was using an MHL adapter for over an hour, then the phone shut down. Other than that I haven't seen any shut downs related to heat. I do agree though that come summer, this IS going to be a problem, but hopefully by then they'll have figured out a way to better manage heat... I hope.
Ya know, I think people are losing sight of the fact that the power of these cpus has increased dramatically in only a couple of years. I'm typing this on a dual core 2.2GHz lenovo laptop that has cooling fans, and is running 109f doing very little. Why should we expect a dual core 1.5 jammed into a metal and plastic brick without vent holes, much less fans, to run cool?
Well ...
kierandill said:
Ya know, I think people are losing sight of the fact that the power of these cpus has increased dramatically in only a couple of years. I'm typing this on a dual core 2.2GHz lenovo laptop that has cooling fans, and is running 109f doing very little. Why should we expect a dual core 1.5 jammed into a metal and plastic brick without vent holes, much less fans, to run cool?
Click to expand...
Click to collapse
I agree with that no issues. I suspect a lot of my concerns comes from various people at XDA saying "I stream 1080P while playing Reckless Getaway while listening to Pandora over 1x while on the telephone and my phone never gets any warmer than 32°F/0°C".
Unfortunately, without someone with one of those magic Rezounds standing right next to me, running the same game (for example), there is no way to REALLY know if a phone is operating normally or not.
jdmba said:
This is all well and good for a phone released in November. When summer rolls around, and the ambient temperature is no longer low, I think we are going to see a lot of problems and fast. If the standard user gets to 105 in a room that's 70, that means the standard user will start seeing 135 when it is hot out. Those that can get to 115 right now, that's an explosion waiting to happen come July.
Click to expand...
Click to collapse
I welcome this problem coming in at summertime as they may be forced to replace my rezound with one of the new quad cores or somethin.. dont get me wrong I love this phone but if a defect got me the latest/greatest I'd be all over it..
Hi
Recently my UK TF201 has begun making an intermittent croaking noise. It does this at totally irregular timings and often without any user activity occurring at the time.
My Prime is stock and not rooted. It is not associated with any particular program or app running in the background and is becoming very annoying. I'm writing this now after having been woken up by one of the croak sounding noises.
Look forward to your recommendations.
firefox73 said:
Hi
Recently my UK TF201 has begun making an intermittent croaking noise. It does this at totally irregular timings and often without any user activity occurring at the time.
My Prime is stock and not rooted. It is not associated with any particular program or app running in the background and is becoming very annoying. I'm writing this now after having been woken up by one of the croak sounding noises.
Look forward to your recommendations.
Click to expand...
Click to collapse
Please post a video
I'd love to be able to, as this would have saved me having to write the description as best I could. Unfortunately though, it makes the noise only a couple of times a day. Often just the one chirp/croak sound but occasionaly it will put out a couple within a second or two of the first. I don't have the time or a memory card large enough to sit with recording, waiting for it to croak before editting it down for a video I'm afraid.
It isn't exactly like a frogs "ribbit", its more or a deep "ugggh" but my children refer to it as croaking.
I've heard an identical sound before from a friends laptop, which he brought round to show me. It made these random noises a couple of times a day for about a fortnight, before it crashed and died. I hope these symptoms are not an indicator of a similar fate for my lovely Prime.
firefox73 said:
I'd love to be able to, as this would have saved me having to write the description as best I could. Unfortunately though, it makes the noise only a couple of times a day. Often just the one chirp/croak sound but occasionaly it will put out a couple within a second or two of the first. I don't have the time or a memory card large enough to sit with recording, waiting for it to croak before editting it down for a video I'm afraid.
It isn't exactly like a frogs "ribbit", its more or a deep "ugggh" but my children refer to it as croaking.
I've heard an identical sound before from a friends laptop, which he brought round to show me. It made these random noises a couple of times a day for about a fortnight, before it crashed and died. I hope these symptoms are not an indicator of a similar fate for my lovely Prime.
Click to expand...
Click to collapse
Yea I was thinking it was probably random, so it'd be hard to catch on film. That's so odd though. Doesn't look like anyone has any idea, since no one has posted. Does it come out of the speaker, or resonate out of the whole device? Does it do it if it's completely shut off?
Thanks for the reply Jay.
I'm darned if I can tell where the noise comes from. It's occurred a number of times whilst I've been using it but unfortunately with the speaker located on the back it is difficult to know whether it's from within the unit or speaker generated. Personally, I'm 99% confident it's from the speaker, it's just the 1% I can't fully confirm.
With regard to whether it happens with the unit shutdown, I rarely do a full shutdown other than once a week and then only for a full restart. It hasn't been left off for a long period to monitor. However it does this random chirping when in use and when in standby (screen switched ogg). Sorry can't be any more descriptive.
Mine does it some times. Nothing to be worried about tho...
That sound is typical from CPUs. Some laptops/desktops do that sound too.
There was a case from some Dell XPS that were doing that sound so loud that you could hear your CPU even with the internal fan at full speed.. they were offering a free CPU change for these users.
Sometimes my laptop does that sound too (AMD Phenom II X4) and my gfs laptops (Intel i5). I have yet to find what triggers it... but all my machines have done it.
Thanks Zephyrot
Yes that's exactly the noise. The laptop that my friend had was a Dell XPS 1210. Perhaps it was just a coincidence then that the laptop died a couple of weeks after it starting making this noise.
The noise that occurs usually at least once an hour has not occurred in the 2 hours that I have had it totally down powered for investigation. This therefore also lends itself to your theory that it could be CPU based.
The problem I'm having though is that it is loud enough to wake me up when it erupts with one of these chirp/croaks. If someone actually knows why the internals make this noise and more importantly what can be done to stop it from occurring, I would be grateful.
I appreciate that down powering is an option but this is not something that I had intended to do with a tablet. I use my table at work and need to get access to it within 15 seconds of picking it up. Turning the screen off and with such a good battery life, I can readily access information on the fly, whereas having to turn it on would mean waiting up to 2 minutes which is just too long I'm afraid.
Is there anything else you can add Zephyrot with regard to describing the noise, or diagnosing that you have done for the rest of the community to be able to comment on?
firefox73 said:
Hi
Recently my UK TF201 has begun making an intermittent croaking noise. It does this at totally irregular timings and often without any user activity occurring at the time.
My Prime is stock and not rooted. It is not associated with any particular program or app running in the background and is becoming very annoying. I'm writing this now after having been woken up by one of the croak sounding noises.
Look forward to your recommendations.
Click to expand...
Click to collapse
There is obviously an animal stuck in your tablet, probably small frog or bird. I would RMA immediately before the animal dies.
Sent from my myTouch_4G_Slide using XDA Premium App
firefox73 said:
Thanks Zephyrot
Yes that's exactly the noise. The laptop that my friend had was a Dell XPS 1210. Perhaps it was just a coincidence then that the laptop died a couple of weeks after it starting making this noise.
The noise that occurs usually at least once an hour has not occurred in the 2 hours that I have had it totally down powered for investigation. This therefore also lends itself to your theory that it could be CPU based.
The problem I'm having though is that it is loud enough to wake me up when it erupts with one of these chirp/croaks. If someone actually knows why the internals make this noise and more importantly what can be done to stop it from occurring, I would be grateful.
I appreciate that down powering is an option but this is not something that I had intended to do with a tablet. I use my table at work and need to get access to it within 15 seconds of picking it up. Turning the screen off and with such a good battery life, I can readily access information on the fly, whereas having to turn it on would mean waiting up to 2 minutes which is just too long I'm afraid.
Is there anything else you can add Zephyrot with regard to describing the noise, or diagnosing that you have done for the rest of the community to be able to comment on?
Click to expand...
Click to collapse
Put an SSD into the tablet, 2 second boot time. Either that or you've got aborked speaker.
Sent from my tf9001 with XDA XD.
I bought two Nexus 10 when they were first released and I've scrapped one because the battery failed and a huge screen area went yellow and I was getting multiple annoying random reboots every day.
Now my second Nexus 10 is going the same way.
What a load of crap this tablet is, I'm not surprised Google is not updating it for no-one would buy it.
That's interesting....I have a few mates who have the Nexus 10 and none of them have had those problems. They have had theirs since they were released...Maybe you dropped them once?
You just might be an isolated incident. Another mate if mine has the N7 but the only issue is the charger port issue that many other people have.
I have a N4 and the only issue I have is that the camera stops working at times and to fix that I just restart the phone.
Sent from my Nexus 4 using XDA Free mobile app
Project:Frankenphone said:
That's interesting....I have a few mates who have the Nexus 10 and none of them have had those problems. They have had theirs since they were released...Maybe you dropped them once?
You just might be an isolated incident. Another mate if mine has the N7 but the only issue is the charger port issue that many other people have.
I have a N4 and the only issue I have is that the camera stops working at times and to fix that I just restart the phone.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
No misuse at all and another annoying bug is the way it deletes part of the pin number after a reboot so you have to re-do the pin number.
Gaugerer said:
Now my second Nexus 10 is going the same way.
What a load of crap this tablet is, I'm not surprised Google is not updating it for no-one would buy it.
Click to expand...
Click to collapse
I am sorry to hear you are having troubles with both N10s. I would surely have the same frustrations were I you.
We have two N10s, his and hers, for about a year and half. They are used for several hours every day, because we are retired and have lots of time to be online or reading books. My wife's N10 runs Purity ROM and is rock solid for her word games and eBay, facebook, shopping, email and all the other stuff. Mine is rock solid for banking, bill pay, surfing and videos. It usually runs CM11, but could be temporarily running something else while playing around with ROMs. We charge our tablets every day, and try never to get below 50% before plugging in.
I do plan to buy at least one N9 when released, not out of need, but, instead, out of curiosity for an Android 3x4 screen format. Fun times ahead for us Nexus fans.
everybody screaming at me that i m trolling when i was saying about problems with this device few months ago
yellow screen
too many lemon batterys
hdmi problems
buzzing speakers
reboots
no original accesories
you name it ...
I m still in waranty ... i m lazy to go in service with it but after i will repair it ( i hope ) or change it i will sell it and buy a sony . I m not buying a google device again .
nexus fun boys ... what can I say
Sent from my Nexus 10 using XDA Free mobile app
Don't forget nexus 10 is a two years old tablet but it was a gem in its own time. After 2 years we still don't have any tablets with a higher screen resolution than nexus 10. Which makes it perfect for media consumption. I think only galaxy tab s has a better screen nowadays.
It has had its own shortcommings but most of them are by rectified by software updates, like memory leaks or random reboots.
I have purity ROM on my nexus 10 and I have zero reboots or problems. Everything works like a charm after 2 years of heavy usage. The only thing that I envy now is a super amoled screen on my tablet.
fifthelement said:
Don't forget nexus 10 is a two years old tablet but it was a gem in its own time. After 2 years we still don't have any tablets with a higher screen resolution than nexus 10. Which makes it perfect for media consumption. I think only galaxy tab s has a better screen nowadays.
It has had its own shortcommings but most of them are by rectified by software updates, like memory leaks or random reboots.
I have purity ROM on my nexus 10 and I have zero reboots or problems. Everything works like a charm after 2 years of heavy usage. The only thing that I envy now is a super amoled screen on my tablet.
Click to expand...
Click to collapse
Software updates have not stopped random reboots on my two Nexus 10 and I still suffer from system freezes and sometimes with a loud horrible noise from the speaker and I need to do a hard reset to stop it. So bad.
Gaugerer said:
Software updates have not stopped random reboots on my two Nexus 10 and I still suffer from system freezes and sometimes with a loud horrible noise from the speaker and I need to do a hard reset to stop it. So bad.
Click to expand...
Click to collapse
Try to install Purity ROM on them :
http://forum.xda-developers.com/showthread.php?t=2336101
Gaugerer said:
I bought two Nexus 10 when they were first released and I've scrapped one because the battery failed and a huge screen area went yellow and I was getting multiple annoying random reboots every day.
Now my second Nexus 10 is going the same way.
What a load of crap this tablet is, I'm not surprised Google is not updating it for no-one would buy it.
Click to expand...
Click to collapse
I agree, the Nexus Tablet line was literally one of the biggest POS. I owned a Nexus 7 tablet for about six months and never dropped it or anything. The problem started out with ghosting/ghost input touches then later on progressed to half the touch screen not working at all... Although I initially loved it literally became one the biggest let downs ever...
On top of this, I had also read many articles on XDA and elsewhere of people with the same problem trying to send their tablet's in to ASUS for the warranty and they basically just sent the tablets back to them as is with a software upgrade, which didn't help at all since it was a hardware problem.
Gaugerer said:
I bought two Nexus 10 when they were first released and I've scrapped one because the battery failed and a huge screen area went yellow and I was getting multiple annoying random reboots every day.
Now my second Nexus 10 is going the same way.
What a load of crap this tablet is, I'm not surprised Google is not updating it for no-one would buy it.
Click to expand...
Click to collapse
Mine had worked flawlessly since the week it was released.
I got mine when they released the tablet and I've never had one problem with it.
I got mine first month of release and it was great for about a year. It's still good now but my siblings abused it so now the battery drains quick (used to last all day and some of the next now I'm lucky if it reaches the end of the day) and speakers are chipping paint.
Other than that there no issues though and those are pretty much our fault. The battery problem could be from not using official charger or just charging all night
Sent from my LG-VS980
I bought my shortly after release and have not experienced any problems with it. I have almost exclusively been using the Franco kernel with AOKP. I use it every day in place of my laptop. I can watch movies, youtube, internet, social media, etc. all day on a single charge.
I bought mine around feb/mar 2013.
It's a piece of crap.
Yellow/brownish tint on the screen that is getting bigger as we speak, battery shutdown at 30% (workarounds exist!), overheating, slow response, slow R/W speeds, etc. I have to do a factory reset pretty much every month.
On top of that: Gergle being a b*tch about it because they've deactivated my account (inactivity). Really funny guys.
I don't know what to do.
I guess I'll throw it away, as soon as I have something new. I'll never buy anything touched by Samsung again. No phone, tablet, TV, you name it. The only thing they're good as is NAND.
IRKONIK said:
I bought mine around feb/mar 2013.
It's a piece of crap.
Yellow/brownish tint on the screen that is getting bigger as we speak, battery shutdown at 30% (workarounds exist!), overheating, slow response, slow R/W speeds, etc. I have to do a factory reset pretty much every month.
On top of that: Gergle being a b*tch about it because they've deactivated my account (inactivity). Really funny guys.
I don't know what to do.
I guess I'll throw it away, as soon as I have something new. I'll never buy anything touched by Samsung again. No phone, tablet, TV, you name it. The only thing they're good as is NAND.
Click to expand...
Click to collapse
Can you please tell me a workaround for 30% battery shutdown ? i have the same problem .. step by step battery die more faster ... first at 4%, 8% 10% and now 30%...
Sent from my Nexus 10 using XDA Free mobile app
samwheat said:
Can you please tell me a workaround for 30% battery shutdown ? i have the same problem .. step by step battery die more faster ... first at 4%, 8% 10% and now 30%...
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
The problem is: I force the system NOT to shutdown. The battery stays at 0%, but the device keeps running.
This is dangerous. When the CPU ramps up and the voltage is too low it'll cause instability, which you can see by the backlight flickering, the speakers making weird noises, all that bad stuff.
I am not sure how this affects the battery (or the device) physically, since Li-Ion is not very happy when it's "too" discharged. But it'll wear out the battery even faster, I fear. (This is unfunded. I have not enough knowledge about electronics that advanced. But I've read it somewhere. :silly
But, that out of the way: There's an xposed module. I DO NOT recommend using it. It's called DisableCriticalBatteryShutdown, by the user zst123.
You WILL run into fc's of the systemui when plugging the device back in. But the process should restart by itself.
There's a thread on XDA. AGAIN, I DO NOT RECOMMEND USING THIS MODULE.
I got my Nexus 10 shortly after they were released, and though I love it because it's screen is gorgeous and it has front-facing speakers, it is really buggy, and has been since day one.
It freezes and restarts on me probably daily, and always has since it was brand new. In the early days it always happened while using Chrome, and at the time I remember reading that it was a Chrome-specific issue, so I just switched to Firefox in hopes of a better experience.
It was better, for the most part, but eventually it started freezing at other times as well. I still like the tablet, but it definitely has never been a great performer.
I got my Nexus 10 at release, after 1.5 months of Google not shipping it, losing it, telling me that it was coming, etc... Worst customer experience I ever had. I was on the phone with them daily.
When I finally got it it worked fine for a little while but as I put more and more on it and actually tried to use it to stream video, I would get random reboots, freezing, etc...
I've tried relentlessly to talk my wife into letting me unlock it and put a custom ROM on it hoping it would fix things but she would never let me. Now that it's almost two years old, and I barely use it do to all the reboots, etc..., she might finally let me unlock it.
I was really looking forward to getting this tablet when they announced it but with all the problems, for me it pretty much became a $500 paperweight. I use my GS4 so much more than I every used this tablet, even when I'm home.
IRKONIK said:
The problem is: I force the system NOT to shutdown. The battery stays at 0%, but the device keeps running.
This is dangerous. When the CPU ramps up and the voltage is too low it'll cause instability, which you can see by the backlight flickering, the speakers making weird noises, all that bad stuff.
I am not sure how this affects the battery (or the device) physically, since Li-Ion is not very happy when it's "too" discharged. But it'll wear out the battery even faster, I fear. (This is unfunded. I have not enough knowledge about electronics that advanced. But I've read it somewhere. :silly
But, that out of the way: There's an xposed module. I DO NOT recommend using it. It's called DisableCriticalBatteryShutdown, by the user zst123.
You WILL run into fc's of the systemui when plugging the device back in. But the process should restart by itself.
There's a thread on XDA. AGAIN, I DO NOT RECOMMEND USING THIS MODULE.
Click to expand...
Click to collapse
So there s no solution ...
Sent from my XT1033 using XDA Free mobile app
I have 2 Nex10's. Both bought at launch. One is stable as a rock (thank god it's the wife's or else) but mine is a bit of a dud. Instabilities and crashes since day one.
Not a day goes by that I don't have to do the 3 finger salute to restart because it has frozen solid.
Tried factory resetting, flashed factory images whenever a new one was around and tried different kernels. No change whatsoever.
I believe Samsung's soc is the culprit here, which was also the issue with the chrome chrashes in the early days (GPU drivers that fixed the issue where delayed by Samsung, which was silly as it's a stock Mali GPU).
Never mind the USB connectivity issues that only Samsung devices do. I had no problem connecting any of my other tablets and phones (Nexus 7, 4, 5, Xperia Z, various HTCs, even Nokia Lumias) to my PC. The Nex10? No dice. I had to manually remove any and all USB drivers, do 3 rain dances and pray to the lord of shadows before I got it to work.
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.