Related
This night, I was playing Beach Buggy Blitz and suddently, I began to have graphics glitches. The screen turned kind of violet tinted and was teared apart at the bottom but the game was still playing fine without crashing. So I quit the game and the same problems were present in the Android home screens. Even a complete shutdown and reboot did not had any effect. I thought that my N7 was broken for good.
But, then the screen began flickering between the good and the bad states and finally settled with the normal colors. The N7 never froze while the display was corrupted.
When this occured, I was playing with my N7 inside a leather folio case and I could sense the heat through the case. I then changed the case for a hard shell one with a plastic back and the issue returned after playing a little longer than with the leather case. I finally tried without any case and the problem did not appear although I played for a little less longer.
I had the graphics settings in BBB maxed out and this being a Tegra 3 optimized game, I wonder if this isn't the worst case scenario for the N7 when inside a closed case with a game that sollicit heavily the graphics portion of the ARM chip.
Anyone had similar overheating issues? Should I (again) think about RMAing my tablet or is this just an issue that could affect all Nexus 7 when they are put in the same conditions?
You pretty much answered and solved your own problem.
Sent from my Nexus 7 using XDA Premium HD app
how long were you playing for man? my goodness, if you play for that long to overheat your device i think it's time you get a PSvita or PS3 lol... I know the tablet has a tegra 3 chip but still, I don't think it's totally meant for a 5 hr game session
MRsf27 said:
how long were you playing for man? my goodness, if you play for that long to overheat your device i think it's time you get a PSvita or PS3 lol... I know the tablet has a tegra 3 chip but still, I don't think it's totally meant for a 5 hr game session
Click to expand...
Click to collapse
It's fine.. just the enclosed case was the issue.
My advice is to only use a case when doing light duties, or your battery will suffer for it.
Sent from my Optimus 2X using Tapatalk 2
Mungulz said:
It's fine.. just the enclosed case was the issue.
My advice is to only use a case when doing light duties, or your battery will suffer for it.
Sent from my Optimus 2X using Tapatalk 2
Click to expand...
Click to collapse
yeah, but still; how can you possibly play for that long on the nexus 7? I can't even see myself holding it for more then 1 hr playing games lol
MRsf27 said:
yeah, but still; how can you possibly play for that long on the nexus 7? I can't even see myself holding it for more then 1 hr playing games lol
Click to expand...
Click to collapse
He would have only had to play for maybe 20-30 minutes to cook the nexus.
I just played for 15 minutes and it made my nexus the hottest I've ever seen...
You need to understand though, unless the device is insulated there is no difference in heat between 30 minutes gaming and 30 hours gaming. Phones/tablets/computers get up to temperature quickly.
Sent from my Nexus 7 using Tapatalk 2
Mungulz said:
He would have only had to play for maybe 20-30 minutes to cook the nexus.
I just played for 15 minutes and it made my nexus the hottest I've ever seen...
You need to understand though, unless the device is insulated there is no difference in heat between 30 minutes gaming and 30 hours gaming. Phones/tablets/computers get up to temperature quickly.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
If he has his device rooted and ovrclocked that could be he reason why its overheating.. when I play with my device it doesn't get very hot
Sent from my Nexus 7 using xda app-developers app
I played for about 25 minutes when it first happened. The second time, with the hard back case, I played for 10 minutes. My Nexus 7 is rooted but not overclocked, original ROM and kernel. I reverted to a good backup and the problem was still there.
Since it happened, my N7 seems to be more problematic than before. For example, after being charged in the hard back case, I experienced the problem only 2 minutes after I started playing with it. It's as if something has been damaged by the first overheating and now it overheats pretty easily even with less demanding games.
If I can't use a case with my N7 then I must consider it defective. So, I emailed Google for a replacement this morning. Just as I started to enjoy my tablet after a first replacement (screen lift), this happens...
MRsf27 said:
If he has his device rooted and ovrclocked that could be he reason why its overheating.. when I play with my device it doesn't get very hot
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
External temperatures can affect overall device temps as well (as in, if your sitting in a meat freezer, your Nexus 7 is very unlikely to overheat, whereas if your sitting outside in 100F weather...)
espionage724 said:
External temperatures can affect overall device temps as well (as in, if your sitting in a meat freezer, your Nexus 7 is very unlikely to overheat, whereas if your sitting outside in 100F weather...)
Click to expand...
Click to collapse
Yep.
Although OPs nexus seems to be defective if its overheating now in 2 minutes.
Since reaidng this thread a few days ago I decided to try Beach Buggy Blitz and now im hooked on it, my Nexus can handle hours of gameplay in 25c ambient.. wouldn't wana try on a really hot day because it feels really warm already.
I seem to notice more framerate slowdown as the N7 gets hotter, maybe thermal throttling.
Sent from my Optimus 2X using Tapatalk 2
I'm not a gamer by any stretch of the imagination. However, I experienced random reboots while I was writing a long email using Swype with my Nexus 7 in the Poetic case. When I looked, the temperature was VERY high as reported by System Tuner. I removed the case, cooled the back of the Nexus, and everything went back to normal. I WAS overclocked, so I went back to a kernel locked to stock speeds. I haven't seen any serious issues since. But it's pretty clear that if you're using a case, the Nexus can't shed heat quickly enough the way it was designed to.
I keep a closer eye on it now.
What models/build, gig and first 3-4 characters of your serial number, do you have?
I had a 16 gig (not sure) that was stayed cool. I exchanged it for a 32 gig (CAOK) and that would gets hot at random times of just usual use. It would get hot on the bottom left quarter of the back. The screen would take a huge percentage of the battery also.
I picked up another 32 gig (C9OK) and this one stays cool under normal usage.
Maybe we can isolate this to a certain model/build.
It was a C7O. I don't remember more than that, sorry. I've posted a video of the problem on Youtube and send that link to Google when asking for an RMA on their site. 90 minutes later, I had a response with all the needed info to return the tablet. On this one, I have to give Google a very positive note:good:.
I received another C7O and this one seems to be defect free. After 3 N7s, I finally started to enjoy my tablet...
same issue
same issue here.
i was playing Final Fantasy (so awesome that SquareENix ported this to Android and iOS... i remember the original version from my NES and it was a hoot. the only FF game i ever played) for about 2 hours or so and toward the end my Nexus 7 tablet got very hot, particularly on the "lower" portion of the device (side with the USB charging/tether port) ... of course, this is held in landscape mode for this game so it was my right hand that was hot.
anyway, just before starting one last awesome boss battle (right up at the Kraken with awesomely-decked out party, damn!) the game hung and the whole tablet froze. no home button functionality, no power button to even turn the screen off or on again.
had to hold power for 10 seconds, full reboot. even when the tablet came back up it was still wonky.
powered off, left it off for a while. it came back up just fine afterward, but the game didn't get to save so i'm back many levels before where i had been. no looking forward to that re-work. ah well, live and learn.
I am having issues with my 32 GB tablet. Sometimes the screen stops responding to touch and I either have to leave an app or turn off the screen and back on again to get it back. Occasionally, when I lock the screen to get it unfrozen then it doesn't come back, and restarts.
Anyone else experience anything like this?
Same here. When the screen looses responsiveness I have to reboot.
Sent from my Nexus 10 using xda premium
Sounds like a software issue to me. A very large portion of people seem to be reporting this and I have had this happen to me as well in two instances. I'm sure it will get worked out sooner rather than later.
Same Here
Takes forever to power back on..
mine restarts quite fast... i would know since it keeps on crashing and restarting itself
ShadowVlican said:
mine restarts quite fast... i would know since it keeps on crashing and restarting itself
Click to expand...
Click to collapse
Same here. Happened twice today when my N10 was idle. Screen was frozen on lockscreen. I could turn the screen on and off but it would stay unresponsive.
Meh...
All these restarts, frozen screens, etc are starting to take a toll on my patience.
johno86 said:
Happened twice today when my phone was idle.
Click to expand...
Click to collapse
Did you really mean "phone"?
ContentsMayVary said:
Did you really mean "phone"?
Click to expand...
Click to collapse
Oh, I meant Nexus 10, hahahaha.
I get confused with my nexus devices... =\
On my S3/Note 2, every time I use my phone, both Screen On and Awake will be reflected.
On Nexus 7 however, when I'm using the tablet, even though Screen On is reflected, Awake isn't. Is this a bug or a new thing on Jellybean 4.2 or simply a nexus/stock android thing? If it's a stock android thing, then what does Awake actually mean?
Tried googling but I can't find any answers..
Awake means CPU isn't at idle. Like background processes running.
Sent from my Nexus 7 using xda premium
Gizmoe said:
Awake means CPU isn't at idle. Like background processes running.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh so the Awake only appears strictly for background processes on the Nexus 7?
Seems different from the Note 2. Is this a stock android thing?
kEvinErd said:
Oh so the Awake only appears strictly for background processes on the Nexus 7?
Seems different from the Note 2. Is this a stock android thing?
Click to expand...
Click to collapse
I'm not too sure exactly. On my phone it was always on with screen but may have something to do with 3g radio consuming power. It does seem real low compared to my phone. Even on cyanogen on my phone it shows constant with screen on and off. Maybe since there is no radio the CPU can idle most of the time.
Sent from my Nexus 7 using xda premium
Battery on my new 32 gig sucks. 4-5 he's of use
Same here
If I helped out, hit the thanks button.
My question is not really about the battery life but on how to actually interprete the meaning of Awake on the nexus 7 as it seems different from my Samsung phone..
mrazndead said:
Battery on my new 32 gig sucks. 4-5 he's of use
Click to expand...
Click to collapse
I wonder why that is. I get at least 8 hours screen on time with stock 4.2. Right now I'm at 4 hrs 6 min screen on time with 51% battery left. Also have the 32g version.
Sent from my Nexus 7 using xda premium
---------- Post added at 12:05 AM ---------- Previous post was at 12:02 AM ----------
kEvinErd said:
My question is not really about the battery life but on how to actually interprete the meaning of Awake on the nexus 7 as it seems different from my Samsung phone..
Click to expand...
Click to collapse
I too am curious as to exactly why. I can only guess. I do know awake has to do with the phone doing tasks and pulling the cpu out of an idle state. My inspire seems to always show as awake even when the screen is off. I do notice though when I shut off mobile data on my phone, awake and screen on basically are in sync. The inspire has an old single core snapdragon though so as soon as I use my phone I'm sure the CPU is maxed out. However on the nexus, awake is only little slivers here and there even when the screen is on all the time. Maybe the tegra 3 is just that good Lol.
Sent from my Nexus 7 using xda premium
Gizmoe said:
I wonder why that is. I get at least 8 hours screen on time with stock 4.2. Right now I'm at 4 hrs 6 min screen on time with 51% battery left. Also have the 32g version.
Sent focuses Nexus 7 premium
---------- Post added at 12:05 AM -------- Previous post was at 12:02 AM ----------
I too am curious as to exactly why. I can only guess. I do know awake has to do with the phone doing tasks and pulling the cpu out of an idle state. My inspire seems to always show as awake even when the screen is off. I do notice though when I shut off mobile data on my phone, awake and screen on basically are in sync. The inspire has an old single core snapdragon though so as soon as I use my phone I'm sure the CPU is maxed out. However on the nexus, awake is only little slivers here and there even when the screen is on all the time. Maybe the tegra 3 is just that good Lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Haha same here on the Awake being little slivers here and there on my nexus 7.
Ideally, when the screen is off, the phone shouldn't be Awake for too long a period or too many times. It's an indication of partial wakelocks caused by some apps or processes in the background, which causes unnecessary battery drain. On my phone, comparing the Awake and Screen on allows me to quickly identify if there's any partial wakelocks. I can't do the same on nexus 7..
Hope someone can enlighten us soon on how exactly to interprete Awake on the nexus 7. Still not too sure if it's a stock android thing, a bug or a JB 4.2 thing. Haha
I, not sure why mine is like that. I am not a noon to android tablet and my Acer iconia get 10 hours battery use for a couple year old tab.
My nexus is setup with almost everything off and WiFi NFC of as well. The only thing I can think of is I did not do a factory reset after ota update to 4.2.1. I'm going to do reset after I do a full charge. If that doesn't work then I will flash a new to, and kernel
I believe the whole "awake" under battery is just a 4.2 bug. Because ever since my G'nex updated it's the same way even though it used to have solid lines in accordance with screen on. As long as both my devices continue to get normal (for me) battery life I don't worry about it. Though I do hope Google fixes it because I do find it slightly annoying.
Sent from my Galaxy Nexus using xda premium
95Z28 said:
I believe the whole "awake" under battery is just a 4.2 bug. Because ever since my G'nex updated it's the same way even though it used to have solid lines in accordance with screen on. As long as both my devices continue to get normal (for me) battery life I don't worry about it. Though I do hope Google fixes it because I do find it slightly annoying.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for confirming! Haven't been able to get anyone else's confirmation I was starting to think it's a stock android/nexus thing. Battery life wise I'm unable to compare because I got my nexus 7 with 4.2 out of the box.. No points of comparison.
kEvinErd said:
Thanks for confirming! Haven't been able to get anyone else's confirmation I was starting to think it's a stock android/nexus thing. Battery life wise I'm unable to compare because I got my nexus 7 with 4.2 out of the box.. No points of comparison.
Click to expand...
Click to collapse
I also think it is a 4.2 issue. My friend told me that his Nexus 7 suffers from poorer battery life since he flashed a 4.2 ROM, he reverted back to 4.1.x for his daily driver.
Maybe it only shows partial wakelocks called from applications (not screen)?
Silverspitz said:
I also think it is a 4.2 issue. My friend told me that his Nexus 7 suffers from poorer battery life since he flashed a 4.2 ROM, he reverted back to 4.1.x for his daily driver.
Click to expand...
Click to collapse
I don't think this is causing any extra battery drain though.. Battery drain when idle is very minimal which is a good thing..
haha123 said:
Maybe it only shows partial wakelocks called from applications (not screen)?
Click to expand...
Click to collapse
That's what I'm more inclined to thinking too. Was it like this before on 4.1 or earlier versions? This is my first nexus device so I can't tell if its a android OS version thing or nexus device thing.
Hi,
my screen is set to turn off in 30 seconds but is not happening. Stays on.
Noticed that some time ago but thought was one off but it isn't.
Any ideas???
If i turn the phone off and on, it works again but don't know for how long?
There's an option in the developer settings to keep screen on when charging. Is that ticked?
Sent from my Nexus 4 using Tapatalk 2
ackliph said:
There's an option in the developer settings to keep screen on when charging. Is that ticked?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Happens when not charging????
I have the same issue. Hopefully someone can help
Oh not just me.
Happens when not charging, it is random.
Had like 5 android phones and always end up asking for problems
Is there any android phone without problems?
Sent from my Nexus 4 using Tapatalk 2
5 android phones with problems, really...
I've had 4, not a single one. I think you're something to them.
calanizzle said:
5 android phones with problems, really...
I've had 4, not a single one. I think you're something to them.
Click to expand...
Click to collapse
Believe me there is always something
Own two devices atm :
nexus4 - this screen problem, rattle, camera became unresponsive more then once and there is something with the network signal (don't know yet what is it)
nexus 7 - the lag, that's not butter for sure.
Must be me.
I had this problem too. But for now it's back to the 30 seconds. No idea how it started and how it stopped. Pretty sure after I tried a reboot, that it still happened.
Hello I have this weird screen problem on my nexus 4 appears after screen is turned on from a standby state.
Screen goes dark with horizontal lines, but appears to be responsive. can be fixed by putting the phone (display) on standby and waking it back up.
If the display is left in this 'dark' state for a min or more a screen burn in-like image stays on screen but is gone after a reboot.
--attached photos--
nx4 said:
Hello I have this weird screen problem on my nexus 4 appears after screen is turned on from a standby state.
Screen goes dark with horizontal lines, but appears to be responsive. can be fixed by putting the phone (display) on standby and waking it back up.
If the display is left in this 'dark' state for a min or more a screen burn in-like image stays on screen but is gone after a reboot.
--attached photos--
Click to expand...
Click to collapse
Seems to be a hardware problem. What kernel are you using?
luiseteyo said:
Seems to be a hardware problem. What kernel are you using?
Click to expand...
Click to collapse
using 3.4.0 from cyanogenmod, problem also exists on Stock 4.2 and 4.3
nx4 said:
using 3.4.0 from cyanogenmod, problem also exists on Stock 4.2 and 4.3
Click to expand...
Click to collapse
Then you have the answer. It is a hardware problem.
luiseteyo said:
Then you have the answer. It is a hardware problem.
Click to expand...
Click to collapse
so sad, this a common problem of nexus 4?
I had this problem 3 days after I got the nexus 4 from google, I should have RMA'd it but the problem was very interment back then now its getting frequent.
nx4 said:
so sad, this a common problem of nexus 4?
I had this problem 3 days after I got the nexus 4 from google, I should have RMA'd it but the problem was very interment back then now its getting frequent.
Click to expand...
Click to collapse
Well, If I saw it I could tell u if happens to me too or not, to tell u if it is common... but I cannot see it properly