Related
Anyone else experiencing this? In the 24 hours I've been using my nexus 10, this has happened at least 10 times. All of a sudden the device becomes unresponsiv, the screen dims until it turns off, and the only way to get the device back on is holding down the power key multiple times until it boots back up. Needless to say, quite frustrating. Otherwise, love this device.
Anyone else experiencing this?
Sent from my Nexus 10 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1998496
Sent from my Galaxy Nexus using Tapatalk 2
Not quite sure how one loves a device that forces you to reboot ten times in the last 24 hrs. It's like buying a new Honda and loving it even though it stalls ten times a day.
Too many people apparently buy their device to adoringly stare at like a trophy or a collectors item than actually use.
Those all seem like pretty legitimate apps to me. This would suck but I would suggest deleting one app and using the tablet till it happens then rinse repeat till you find the offending program.
Try the secret magic spell: a full wipe
Sent from my GT-N7100 using xda app-developers app
Add me to the list of people with random freezes and reboots. It's happened to me 3 times since I've gotten the tablet a few days ago, and I was using a different app each time. I suspect it's an OS bug rather than an app that's causing it. It's a little disheartening that Google let their new flagship 10" device get released with such a bug. Hopefully they release an OTA update sooner rather than later.
For the record, I rooted using the flashable CWM SuperSU file - I did not use the toolkit.
I have had my 16gb 10 now for almost a week - currently stock and non rooted. No problems whatsoever and I have been working it pretty hard.
Mine has frozen 2-3 times in the past few days. No idea why either. Audio continues to play, and the device responds to button use, but the display stops altogether.
Sent from my Nexus 10 using Tapatalk HD
I got mine like a week ago and it's been frustrating. I debated whether to return it or not. I really like the Nexus 10 but this has been really inconvenient. Does CM10.1 have the issue coz I am planning on rooting and flashing CM10.1 if it resolves the issue. Just trying to get an input.
ralphconrad91 said:
I got mine like a week ago and it's been frustrating. I debated whether to return it or not. I really like the Nexus 10 but this has been really inconvenient. Does CM10.1 have the issue coz I am planning on rooting and flashing CM10.1 if it resolves the issue. Just trying to get an input.
Click to expand...
Click to collapse
In another thread someone said it slowed the issue but didn't stop it.
Sent from my Nexus 4 using Tapatalk 2
Thanks man, now I'm debating if I should just get the transformer infinity. I really don't need root that much because I only use my tablet for school...
Sent from my Nexus 10 using xda app-developers app
Happened to me several times as well. Last time the screen went black (not off) and the tablet was extremely hot, to the point of burning my hand when I touched it! Seems it was stuck that way for several hours and didn't reboot itself.
I've been having random rebooting and freezes since getting this tablet i've replaced it three times already so i'm tired of calling google about it don't even think they have a solution because we've been waiting since November for them to fix this problem so i decide to turn off location and took HD widgets out and so far my tablet has not frozen or rebooted in two weeks it been working really well hope it continues to perform this way.
Chrome has major stability issues as far as I can tell. It crashes very frequently and causes a complete system lock-up when it does. I've resorted to Firefox. To me, this is absurd on a core first party app. Google: get your act together on Chrome.
I recently noticed this issue and have been reading what a lot of others here have had to say and so far it seems to be related to wifi. I would bet it's a software / kernel / driver issue because others have reported not having the problem before the latest update.
If I think about it, I probably had the lockup/reboot happen once before now and I can't really tell you what I was doing at the time. But I thought nothing of it. I have however found a way to force it to happen. All it takes is a large download (1gig'ish) in uTorrent, the download works fine for about 10 minutes and then the tablet either just restarts, or it first becomes unresponsive to input (screen or buttons) but is still functioning, followed by a hard lock up that can only be fixed with a forced power off.
It may be a buffer issue, or memory leak, I've been able to prolong the lockup by throttling the uTorrent download speed and minimizing the number of active apps running. As suggested in other threads I've disabled location discovery and it may have bought me a little more time but if so it's not much. I can't tell if it's because of the amount of constant data flow coming in, or the number of active connections to different seeders, or more likely a combination of the 2. I can also say that if I attempt to browse the web with either chrome or Dolphin while downloading in uTorrent the freeze or reset happens much quicker.
So for now I'm hoping that in the next update they resolve the issue and will just use my pc for torrent downloading.
T.D.K,
It may help Google resolve this issue if you reported your obvervations in this bug report thread:
https://code.google.com/p/android/issues/detail?id=39879
I think the wording you used in your post would be sufficent. Nothing helps identify where a bug is more than a repeatable instance of the issue.
Turning off the location services and uninstalling HD widgets sorta worked for me... I still get random reboots though but mostly when I'm using Chrome. Google should have just left the stock android browser and made Chrome optional.
Sent from my Nexus 10 using xda app-developers app
3DSammy said:
T.D.K,
It may help Google resolve this issue if you reported your obvervations in this bug report thread:
https://code.google.com/p/android/issues/detail?id=39879
I think the wording you used in your post would be sufficent. Nothing helps identify where a bug is more than a repeatable instance of the issue.
Click to expand...
Click to collapse
Thanks, ya that had crossed my mind but wasn't sure which defect to post it to so thanks for the link.
HELP!!
I am experiencing the same problem.
3DSammy said:
T.D.K,
It may help Google resolve this issue if you reported your obvervations in this bug report thread:
https://code.google.com/p/android/issues/detail?id=39879
I think the wording you used in your post would be sufficent. Nothing helps identify where a bug is more than a repeatable instance of the issue.
Click to expand...
Click to collapse
Nope, the problem was submitted to Google months ago and is listed to only receive medium priority. A total system failure that affects every single Nexus device is only given medium priority. Makes me ponder what in glory be would be considered high priority. Maybe if the tablet reached out and kicked you in the balls whenever you looked away from it
Hoping someone can help me out with a serious ongoing problem I've been having with my N7.
I'm getting random reboots where the screen will go blank - all black, or one colour with lines, will be completely unresponsive and will either stay like this until I do a reset with a long press of the power button, or reboot itself after about 30 seconds. The reboot is often accompanied by a loud buzzing from the speaker.
It will then get caught in a bootloop between the Google screen and the boot animation.
It seems to be related to the battery somehow because it doesn't happen when I'm plugged into the charger or connected to an external battery pack.
I'm almost certain it's a hardware rather than a software issue as I've tried a full wipe and ROM restore to no effect.
I'm wondering if someone could help me out with diagnosing or some advice.
Is this a warranty case or something I could fix easily, etc?
Thanks in advance for your help.
Sent from my Galaxy Nexus using xda premium
Are you overclocking, undervolting, or using a non-stock kernel?
If so, restore stock to your N7 for a while and see if the problem persists.
If the problem persists after that it probably is hardware as you suggest. (Even mildly-overclocked/undervolted default settings in a kernel could theoretically cause instability problems for a small fraction of processors - so you need to eliminate that as a possibility by running stock for a while.)
You might actually want to go so far as to restore the lock state of the bootloader after you restore to stock; that way, if things get worse and your warranty period has not yet expired... well, you get the idea...
good luck
Running the latest 'stable' PA and M kernel with default settings as far as clocking and volting AFAIK.
I will try returning to stock unlocked though to eliminate the possibility of some incompatibility between my device and custom kernel.
Thanks for the suggestion.
Sent from my Galaxy Nexus using xda premium
I am facing same issue with me but since its in under warranty i am going to RMA it with asus, but i lives in india its not yet launched in india & bought from USA so i dont know i may or may not get battery replacement.
Does anyone know if popping off the back to look inside would break warranty?
Sent from my Galaxy Nexus using xda premium
heccubusxda said:
Does anyone know if popping off the back to look inside would break warranty?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No unless & untill you open it without letting them know so open it carefully , There are various videos on youtube on how to open back cover of Nexus 7 .
Hey guys, I was wondering if anyone may know if the new 4.4 Kit Kat will fix all of the Nexus 7 2013 touch screen problems.
Maybe Asus and Google knows it fixes the issue. That's why they didn't rush to help us in the last few months.
Cross your fingers people and hope this fixes all of our issues. That would be sweet.
Oct 28 4.4 I'm thinking.
I hope that... it's been a headache, and that's the only flaw mine has, the fix here fixes it just temporally.
Can't say whether it will or won't but I can say I really doubt they have the fix already in hand and are holding it back waiting for kit kat.
They've never been shy about putting out releases to fix things and a touchscreen fix is very contained and isolated, not something that touches many areas requiring long code reviews.
Can I just ask what kinde of problems you are reffering to? Multitouch problem has been fixed with the latest update. At least mine was. With a multitouch program I placed all 10 fingers on screen and was moving it arround, and it registrated all fingers and arrows were moving very very smoothly. 60fps+. Also, there is no problem with GPS anymore. The only problem which is actually not a problem, is smal buzz from speakers when watching of listening to something at very low volume, but that is reported for all nexus 7 devices because that is how the speakers are made.
You are saying like nexus 7 2013 is forgotten and this 4.4 is our last hope for the device otherwise its useless to use. Which is far from truth. I have absolutely no problems with it.
I don't know, maybe I use the device too much? But I can definitely say ghost touchs and some multi-touch issues are there and persistent. In fact right now as I was writting this the keyboard went crazy, it's really annoying and I don't even want to start with the horrible experience I'm getting with PS Touch(which I use a lot) thanks to this problem. Sometimes I have to reboot the device when it goes crazy zooming while navigating the internet.
For you guys that your tablet is "perfect", fascinating, good for you, but that doesn't mean the problem doesn't exists anymore, you just got lucky.
I personally have no more touchscreen issues since JSS15Q, but if there is another touchscreen fix in KitKat that would be good to the few unlucky ones still having issue with theirs..
neo5468 said:
Can I just ask what kinde of problems you are reffering to? Multitouch problem has been fixed with the latest update. At least mine was. With a multitouch program I placed all 10 fingers on screen and was moving it arround, and it registrated all fingers and arrows were moving very very smoothly. 60fps+. Also, there is no problem with GPS anymore. The only problem which is actually not a problem, is smal buzz from speakers when watching of listening to something at very low volume, but that is reported for all nexus 7 devices because that is how the speakers are made.
You are saying like nexus 7 2013 is forgotten and this 4.4 is our last hope for the device otherwise its useless to use. Which is far from truth. I have absolutely no problems with it.
Click to expand...
Click to collapse
The few that had touchscreen problems initially were fixed. 75% of working units were broken in the process. Its a big issue. We have a fix but nothing from Google. There are several screen variances which make it impossible for a single 1 fix all solution.
Google will have to detect each variance and patch accordingly. Probably why it hasn't been released yet because it probably will take a larger testing period then previously mentioned. Even using the XDA fix, some versions can cause several FCs and bugs. Similar to the specific pattern freakout.
With 4.4 on the horizon, it would be best to include it in that. Google probably isn't going to create an OTA and then another one in a few weeks.
Just cross your fingers and hope for an official fix.
GPS was fixed though. I'm not sure about the kernel reboots though. I haven't used the stock kernel nor had reboots since I flashed CM Kanged.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
player911 said:
The few that had touchscreen problems initially were fixed. 75% of working units were broken in the process. Its a big issue. We have a fix but nothing from Google. There are several screen variances which make it impossible for a single 1 fix all solution.
Click to expand...
Click to collapse
Any source for that 75% number? Without a proper source it is hard to not consider that as a case of the loud minority.
If it were that serve of a problem we would hear the tech press clamoring about it by now. But nothing was said about N7 touchscreen by the tech press since JSS15Q.
I can't tell you what the real percentages are, but the touchscreen issue is definitely a much bigger problem than your standard problems.
Standard run-of-the-mill issues get a thread with maybe 20 posts. Touchscreen is producing 1000 post threads. So relative to normal problems it is a big problem, but whether that is a 5% vs 1% problem or a 75% vs 1% problem I could not tell you.
There are at least 3 huge threads on Google support forums about this problem:
Multi-touch - reports of improvement, no improvement, and some worse
Multi-touch (continued) - more reports of fixed / not fixed for JSS15R
Multi-touch (continued 2) - more reports of touchscreen issues
BTW I created the xda fix for touchscreen so I'm very familiar with the fixes Google put out and whether they have fixed the issue. JSS15R fixed it for some screens but made it much worse for others.
That's the main reason I haven't sent my Nexus for repair, is not hardware related, or at least that's what I think, please someone correct me if I'm wrong.
NekroWolfen said:
That's the main reason I haven't sent my Nexus for repair, is not hardware related, or at least that's what I think, please someone correct me if I'm wrong.
Click to expand...
Click to collapse
Well, actually it is hardware related, but you can't tell if your hardware is one type or another without using Sfhub's process.
Well, thanks for confirming
I personally don't think that all of the touchscreen issues will be fixed with Kit Kat. I feel that Google will he focusing more on a fully operational OS, and that we'll need a dedicated fix to solve our problems.
But I surely hope that I'm wrong.
______________________________
HTC Evo 4G LTE
any word of usb audio coming via kitkat. ive been waiting for this feature to come to the nexus 7 forever because its keepingme outof my car
Lockeskidney said:
any word of usb audio coming via kitkat. ive been waiting for this feature to come to the nexus 7 forever because its keepingme outof my car
Click to expand...
Click to collapse
At this point, questions to me are almost meaningless to ask. We night as well wait for tomorrow. It took long enough to arrive.
It just sucks that I don't have my tablet. I went back to Radio Shack and ordered the 32gb through them, since none of their stores had that version on their shelves, and 16gb was not working out for me. At least I'll get to download it as soon as I get my new device!
______________________________
HTC Evo 4G LTE
GPS isn't solved to me.
diogobuique said:
GPS isn't solved to me.
Click to expand...
Click to collapse
That's a hardware issue, I suggest you to send it back to Google.
Kitkat gave me phantom touch issues, have none before kitkat. :-\
Sent from my SM-N900P via TapaTalk PRO
Elite Tester
This process doesn’t wipe the tablet, so your settings, apps and everything else should stay in tact whenever you get back to the system. Remember that you will have lost root at this point, but it’s easy enough to get that back.. Cool resource!
But before kitkat my GPS worked very well
So I updated to 4.4 yesterday with adb sideload. Since that I was using my Nexus 7 "heavily" and I always had "buttons stucked" on keyboard, but now it's gone and I havent experienced any other touchscreen bug.
I don't think I have had any buttons sticking since I updated as well. That was my only issue with my Nexus 7 when in was still running 4.3. It would usually have a keystroke stick several times while typing things and I haven't experienced it once while typing this entire post, which is also why it keeps going because I'm trying to keep typing to see if it'll happen, and instead I just keep making spelling mistakes.
It did not fix the touch issues that may be related to grounding. In a case or stand, both Nexus 7 devices I have still fail to see any touch on numerous occasions, even single finger touch events. Manufacturing issue I guess, but we all know how G & Asus deal with those.
Let's hope it lasts... some issues are fixed temporally.
touchscreen is definitely improved for me too.
Yeah but multitouch still fails, playing dead trigger 2 could be an impossible mission.
bokoy said:
Yeah but multitouch still fails, playing dead trigger 2 could be an impossible mission.
Click to expand...
Click to collapse
Never had multitouch issues, only single touch problems like quad touches innstead of one etc. (As u can see it happened again lol)
They poped up after the R update, and im waiting for CM11
I had single touch issues even after sending my tablet in for service. I had called yesterday to send it back again when I noticed the update was available for side loading.
After the update my screen is behaving!
I'm going to hold off on claiming that my issues are completely resolved but it is looking promising.
Sent from my Nexus 7 using Tapatalk 4
I was going to make a thread about this same thing my keyboard is good now.
Sent from my Nexus 7 using XDA Premium 4 mobile app
So i am about 3 weeks into my LG G2 i went custom AOSP from the very start. never even touched stock. I had weird graphical glitches which i chalked up to the AOSP stuff. I also had weird touch screen issues. like double clicks when i was dragging my finger. I also had odd shaking. like if i would drag from one screen to the next and stop in the middle instead of the panes being static they would shake way way worse then i have even seen on a phone. after about 3 weeks it got to much. i went back to stock to see how it felt. i have the same graphics issues. and i think some of the same touch screen issues. Although i didn't stay long enough to really test, but the graphical glitches are there. I can reproduce anytime i want on AOSP or Stock.
Did i get a lemon?
I can post a video if anyone wants to see any of the symptoms.
JustusIV said:
So i am about 3 weeks into my LG G2 i went custom AOSP from the very start. never even touched stock. I had weird graphical glitches which i chalked up to the AOSP stuff. I also had weird touch screen issues. like double clicks when i was dragging my finger. I also had odd shaking. like if i would drag from one screen to the next and stop in the middle instead of the panes being static they would shake way way worse then i have even seen on a phone. after about 3 weeks it got to much. i went back to stock to see how it felt. i have the same graphics issues. and i think some of the same touch screen issues. Although i didn't stay long enough to really test, but the graphical glitches are there. I can reproduce anytime i want on AOSP or Stock.
Did i get a lemon?
I can post a video if anyone wants to see any of the symptoms.
Click to expand...
Click to collapse
What are the graphics and touch screen issues? Care to elaborate? I've had 3 g2s in about 2 weeks and have experienced the high pitched buzzing in the ear piece when making a call and the touch screen issues when the phone is used playing video or games after 45 minutes or so the touchscreen becomes erratic and the scrolling goes crazy. There's a couple videos on here showing the touchscreen issues when writing in a quick memo (looks like an EKG). Maybe a little more info on your part will give us a better idea on your problems though.
Sent from my VS980 4G using Tapatalk
Why did you wait 3 weeks before you came to the conclusion you have a lemon? And with all those issues why you even asking that stupid question?
Sent from my LG-D801 using xda app-developers app
Sounds like 4.4 issues with the graphical stuff. Its common because we don't have a proper port yet.
I suggest you ALWAYS use your phone stock for a week or else you have no idea if its software or hardware when things go wrong.
I suggest you flash back to stock and waiting it out and see for yourself.
-sent from my LG G2 using XDA Premium 4
I will see if I can make some videos to show of what I mean.
Sent from my LG-VS980
The touch screen issues are present in all G2s, it's whether or not a user "triggers" it that's the question. I've seen it in both AOSP and stock. So your touch screen is "fine." The other issues are not normal though.
Sent from my LG-G2 using Tapatalk
To conclude if anything is normal or no...you need to have your phone completely stock...What player911 said is the right thing to do.
So i swung by verizon and sure enough the demo model showed no signs of what my phone is doing...
btw i did say i went back to stock to test it and both the graphic issues and the touch screen issues have been present. I cant always reproduce the touch issues but the graphic glitches is some sore of faulty unit. I will try to get the to replace it on monday.
Koopa777 said:
The touch screen issues are present in all G2s, it's whether or not a user "triggers" it that's the question. I've seen it in both AOSP and stock. So your touch screen is "fine." The other issues are not normal though.
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
This is not true! I have the Verizon variant and I have no issues with the tough screen at all...ever?? In fact, for whatever reason (maybe because Verizon is more closed/careful/anal/controlling) I read of more issues with other carriers than I do with Verizon. So either it's Verizon, or maybe Verizon's version got a better batch of hardware while the others got a bad batch??? :crying:
Return it and get a new one. If you were at the store, I would have already done this. Its under warranty regardless.
Touchscreen is very responsive on mine. Maybe too sensitive. Sometimes I don't even feel my fingers touching the screen.
Sent from my Nexus 7 using XDA Premium 4 mobile app