Related
Guys, I was all set to get a new 32gb Nexus 7....the reviews are great, and then I start reading about the issues.
After a bit more reading, I'm left wondering if its such a good idea? I read that Google released an update, then I also read that it didn't always fix things for people?
So the questions I guess are, Do you own one? Have you had a problem? Is it now fixed by the update? Maybe you've never had any problems?
Would you recommend getting one? I don't wanna spend out on something that I'll regret.
Thanks guys.
I've had mine since the first weekend of availability and it's lived up to all my expectations and then some, you're just buying the usual support vocal minority, sume have legit issue, noisy are just being nitpicky
Sent from my HTC One using Tapatalk 4
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Thanks for your reply.
Mine worked 100% out of the box, no light bleed, no multi-touch issues, no GPS issues. Updates have installed perfectly. I am running stock deodexed + root + TWRP + Elemental X 1.1 Kernel. Couldn't be happier with my purchase. :good:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
madpete said:
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Click to expand...
Click to collapse
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
I bought the 32gb. Works flawlessly, I got it a week and half ago.
Sent from my Nexus 7 using xda app-developers app
GET ONE
I would say go for it, you are always going to have issues with most anything. Just buy from a retailer with a good return policy, I own the nexus 7 2012 and the nexus 7 2013 , no issues here, awesome devices.
Thanks guys. Sfhub, you make some good points....think I will buy from a large high street store, rather than online.
Sent from my GT-N7100 using XDA Premium 4 mobile app
sfhub said:
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
Click to expand...
Click to collapse
i think mine is definitely, hardware, maybe , cuz of user error, ie, bad dirty flashing of zips, i dont' want to start all over fresh again, too many apps/settings to revert back (yes call me lazy sob)
most of the reboots happen when im clicking on an app with wifi on , but one of my last reboots, it just just rebooted out of the blue, i didn't even touch the tablet, but i seen it reboot!
Not sure, really, whether I have/had problems or not. Got mine over the weekend. During my initial playing, I did not notice any touch issues. The GPS would lock, but I didn't have time to take it anywhere for long enough to be sure if it would stay locked for a long period of time. Almost immediately (1 day) I got the JSS15Q OTA update. The GPS DOES seem to lock a bit faster, and I seem to be seeing more satellites than before -- it could be my imagination, though. Still no touch issues that I can see.
New Nexus 7 (then) past issues, (now), Cool TAB!
phab3k said:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
Click to expand...
Click to collapse
I HAD issues out of the box. Waited for the first update from Google, rebooted once after. Took forever to get the screen to respond to any kind of tap. Rebooted a couple of times and was able to get somewhat R E A S O N A B L E response out of the screen. GPS would work for all of 2 minutes and then shut down. No problems with Wi-Fi.
That was then, along came update: JSS15Q! All is happy in Nexus land. GPS is strong and works flawlessly even in the darkest center of my house! Screen is responsive my fingers are happy.
APPS? That is another matter, remember, even with a stock Nexus 7 fhd you are on the bleeding edge meaning that many apps found on Google Play may fail. Live with it until either the app is updated, ***** at the (no don't *****, contact the developer and kindly tell him/her your problem; or find another app that works for now.
Games? Heh, that is a real crapshoot. If it won't function, move on.
This is one hell of a tablet with excellent video, good sound, fast processing. Short of it not being the size of my 60" monitor (TV) I can read everything with these 78 year old eyes!
[email protected]@dog!
Google Nexus 7FHD
Kindle Fire Rooted Android 4.3
Kindle Fire HD 8.9 Rooted 2nd boot loader Android 4.2.2
Droid Bionic stock Android 4.1.2
Guys, just wanted to say thanks for all the posts. You help me make up my mind, and gave some sound advice.
I've took the plunge and brought the 32gb model (from a big high street retailer), and I have to say....what a cracking little tablet this thing is, I am really impressed with it. I have not had any issues with it, so I seem to be one of the lucky ones....either that or they have fixed the issues by the time we got them in the UK.
I do feel for all the people who had problems though, its a nightmare when these thing happen. Theres no doubt there has been or are some issues out there, one thing with a Nexus device I guess is it is patched fast if its sw...obviously hw is a different issue.
Looking forward to enjoying this device now, if I can get on it....have to wrestle it off the wife and kids first!
......thanks again guys.
Pete.
Just got my 32gb Nexus today in the UK. Only thing I have noticed is that tap and hold on screen is slow to react. Can take a couple of trys before it works. Sometimes taping an app is slow to open. Running stock and latest update. Only change made is to use Nova as the launcher.
Sent from my HTC One S using Tapatalk 4
To Wugfresh Re: Toolkit
This is a followup to my 2 confusing Twitter's I made it worse by referencing Nexus 4 and 7 so I will stick to 7 (mostly). I now realize that lurking has its penalties since I need 9 posts after this before I can post this in the relevant thread (with a nostalgic tear for the days we welcomed all comers and left our doors unlocked).
I bought an N7 FHD (2nd gen) and rooted it after the 4.3 auto update soft bricked (right term of art?) it. I used the other toolkit to restore it to JDQ39 factory unrooted. Then it installed JSS15J. Today it tried to do an update and (presumably) it failed because of rooting. That build is no longer on the developer's website and has been replaced by JSS15Q. I would never presume to call myself a developer but my first modem was a 300 baud acoustic coupler and I have a 5 1/2" floppy disks older then most of you and it's actually floppy. ROFL.
Back to reality, on the Nexus 4, I could not discern how to upgrade to the latest Y build but I did manage to restore it to factory settings and Google handled the rest, You were kind enough to add JSS15J to your toolkit for the Nexus 4 but it is not available (in your drop-down) for the Nexus 7. I figured that if you made JSS15J available for the N7 I could restore the N7 to a factory fresh un-rooted one and Google could update it to JSS15Q. In the alternative you might guide me to how I could go from JSS15J to JSS15Q. I am certainly not in your league but this is not my first rodeo and I cannot tell you how grateful I am for your efforts. Your toolkit saved my Nexus 4 from the 2 week wait during which Google might have told me rooting voids the warranty or just have left me phone-less till they returned it.
Again thank you especially, and to all the others here who light candles in the darkness for each other and the rest of us pilgrims. A tip of my fedora to ya. Never forget one definition of a pioneer is someone with an arrow in their back.
Much of the time I am as confused as a baby in a topless bar who said, "What do you mean this is not a lunchroom, what else could it be?"
My suggestion is to keep root, grab the latest carbon ROM, the elemental 1.1 kernel and you should be all set. They already have the updates From G in them and they work superb.
Sent from my Nexus 7 using Tapatalk 4
Do you own one?
Yes, from day one.
Have you had a problem?
Yes, GPS and the touchscreen grounding issue.
Is it now fixed by the update?
Yes, GPS seems fixed.
No, grounding issue may be worse. Works fins as long as I'm holding it. Placing it causes touches to become sporadic.
Maybe you've never had any problems?
I wish...
Would you recommend getting one?
Yes, it still a FANTASTIC device and many have no issues. If you do return it right away until you get one without issues.
I spoke too soon....at first I thought everything was ok....then I began to notice when I was typing that sometimes it would come out as gibberish. I thought nothing of it as we all make typos now and then, then I noticed that press and hold didn't always register (sometimes takes a few goes). I downloaded the multi-touch test from play and to my horror it's all over the place (compared it against my note 2), this is with the latest update. After reading around a bit more, I'm beginning to think these touch screen issues are hardware....and that it's more widespread than people think. Will be exchanging it for another one, hopefully fair better second time.
Sent from my GT-N7100 using XDA Premium 4 mobile app
madpete said:
Will be exchanging it for another one, hopefully fair better second time.
Click to expand...
Click to collapse
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
sfhub said:
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Hey man, thanks for the reply.
I opted for the swap out because I don't want to loose the warranty, which I believe you would if you unlocked it?
I bought from PC World / Currys so the swap was no hassle.
Using the new one now, its testing better and typing and "hold and drag" is working much better (although hold and drag still isn't 100%, it's now acceptable to me).
I tested before and after the update, the observation I made is that the update seems to dull down the touch screen a little. It became slightly less responsive after the update than before, but hasn't really affected the usability on this one....although I think I prefered it pre update.
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.
Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
l2yangop said:
The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
I had it happen once with an unrooted phone near the end of December.
I guess I'm going to send it in... but don't want to bother flashing back to stock if I dont have to. thoughts?
l2yangop said:
Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
Was the phone cold? There is extensive conversation about this on the Nexus 6P forum, and it is much worse when the phone is cold. I had it happen cold and warm, but it happened often when it was below 30 degress F.
thacounty said:
Was the phone cold? There is extensive conversation about this on the Nexus 6P forum, and it is much worse when the phone is cold. I had it happen cold and warm, but it happened often when it was below 30 degress F.
Click to expand...
Click to collapse
no, i live in FL haha
l2yangop said:
no, i live in FL haha
Click to expand...
Click to collapse
Haha. I've been in FL when it was 35!
I was just wondering if it was the same scenario. Not that it would be acceptable.
l2yangop said:
Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
You could try flashing February stock rom, then doing factory reset, in case anything is out of kilter in software causing this.
l2yangop said:
Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
This is now widely reported and seems to be major problem affecting lot of pixel phones. Check out the number of entries in the product support page and in the android code tracker.
https://productforums.google.com/fo...!msg/phone-by-google/QiGBJRx9oxg/Xy5_pkJZDAAJ
https://code.google.com/p/android/issues/detail?id=230806 - Google has marked it as fixed and status is updated as future release which means that it is a software bug.
I also had this issue but i dont have it right now. Mine got resolved by using a non-stock and non-quick charger to charge the phone. I havent faced this issue for the past couple of weeks now. Some people had success doing it and some did not. So its more of a hit and a miss. My guess is that this is a software bug caused by the battery reporting percentage
I have this bug at the moment too. Some users are reporting that a factory reset solved it for them so I have done one yesterday. Can't say yet if it fixed the problem for me too.
You can read more here:
https://forum.xda-developers.com/showthread.php?t=3530040
Gesendet von meinem Pixel XL mit Tapatalk
lalit79 said:
This is now widely reported and seems to be major problem affecting lot of pixel phones. Check out the number of entries in the product support page and in the android code tracker.
https://productforums.google.com/fo...!msg/phone-by-google/QiGBJRx9oxg/Xy5_pkJZDAAJ
https://code.google.com/p/android/issues/detail?id=230806 - Google has marked it as fixed and status is updated as future release which means that it is a software bug.
I also had this issue but i dont have it right now. Mine got resolved by using a non-stock and non-quick charger to charge the phone. I havent faced this issue for the past couple of weeks now. Some people had success doing it and some did not. So its more of a hit and a miss. My guess is that this is a software bug caused by the battery reporting percentage
Click to expand...
Click to collapse
Thanks for you reply. I have seen reports of people sending their phone (usually the 6p but even a couple pixels) back for repair under warranty . If its a software bug and we're on the latest version of software, what could they be doing to fix it when they send it back I wonder? Make me think its hardware.
This could be indicative of a malfunctioning battery. Flashing back to bone stock would be the best troubleshooting method.
[email protected] said:
I have this bug at the moment too. Some users are reporting that a factory reset solved it for them so I have done one yesterday. Can't say yet if it fixed the problem for me too.
You can read more here:
https://forum.xda-developers.com/showthread.php?t=3530040
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Factory reset on stock? I'm running Pure nexus and elemental x
l2yangop said:
Factory reset on stock? I'm running Pure nexus and elemental x
Click to expand...
Click to collapse
yes, on stock rom. But I think it's not rom related.
Edit, you can try 7.1.2 beta, someone wrote there should a fix in it for that problem
Gesendet von meinem Pixel XL mit Tapatalk
Had this start the last couple of days at 30%. Very annoying. Completely stock as well.
I had this problem and attempted the trouble shooting tips from Google without success. I managed to get a replacement and not had any issues since.
firephoenixctk said:
I had this problem and attempted the trouble shooting tips from Google without success. I managed to get a replacement and not had any issues since.
Click to expand...
Click to collapse
Was the replacement directly from Google? Or from your service provider.
Apparently google made a fix to this issue in upcoming updates.
AznRico said:
Was the replacement directly from Google? Or from your service provider.
Apparently google made a fix to this issue in upcoming updates.
Click to expand...
Click to collapse
The replacement was directly from Google.
Coming up to 30% soon so I'll see if it does it again. Apparently it's still happening in 7.1.2 so god knows what update it's fixed in.
I have been reporting in the Pixel community and bug report. My phone was purchased in November from the Google Store, has never been rooted, and always use the OEM charger. My phone ran great until the February patch and then began encountering the abrupt power off around 30% battery.
Android OS, Android System, and Google Play Services are always the top battery consumers. Turning off various things has had no impact. I finally contacted Google and they are giving me the run around about a replacement. The Support staff did confirm they are aware and are replacing some phones but working on a fix, which implies it is software as noted above.
I am still pushing for a replacement and will see what happens.
jonathon1289 said:
I have been reporting in the Pixel community and bug report. My phone was purchased in November from the Google Store, has never been rooted, and always use the OEM charger. My phone ran great until the February patch and then began encountering the abrupt power off around 30% battery.
Android OS, Android System, and Google Play Services are always the top battery consumers. Turning off various things has had no impact. I finally contacted Google and they are giving me the run around about a replacement. The Support staff did confirm they are aware and are replacing some phones but working on a fix, which implies it is software as noted above.
I am still pushing for a replacement and will see what happens.
Click to expand...
Click to collapse
If its happening continuously this is probably something wrong with the battery. I have two Pixel XLs and had this happen once at around 35%! I left it powered off and recharged and this seemed to do the trick. Its clearly a software problem in that instance. So this could be two distinct issues IMO.
Hi all,
I have recently been noticing ghost scrolls, where I would be slowly scrolling downwards, say, in the XDA app or reddit app, and randomly it would scroll quickly upwards when I lift my fingers. I was thinking this was a hardware issue so I got a replacement device on the way. However, I saw this https://www.reddit.com/r/GooglePixel/comments/7rczu2/scrolling_up_when_scrolling_down/.
Has anyone else been experiencing the same thing? I posted a vid and pic https://imgur.com/a/ny8fT. The second pic is touch input trace enabled in developer options, you can see there was a ghost long fast drag down to the bottom below the navbar.
Have been away from XDA for a while, please let me know if I am going against any rules about posting images hosted on other sites.
I wonder if something like this is what causes Twitter to randomly show me a different tweet when I tap on one. (maybe it's doing a phantom scroll briefly).
Sent from my Pixel 2 XL using Tapatalk
Devhux said:
I wonder if something like this is what causes Twitter to randomly show me a different tweet when I tap on one. (maybe it's doing a phantom scroll briefly).
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
yep, thats happened to me a few times before as well. Not twitter specifically, but in reddit I would click on a post, and somehow I would end up on some random other post like 2 post below it, and if I hit back once, I get to the post I originally intended to click on instead of the subreddit list.
So there must be some sort of ghost touches/scrolls on finger release, causing the unintended post to be queued up just before the intended one.
I'm surprised there hasn't been more people bringing up this issue (assuming this is indeed a software 8.1 issue and not an isolated issue in the touch panel).
Reddit has done that to me too, come to think of it.
Agreed that it's surprising we aren't hearing more of this. Makes me wonder if I should do a warranty swap.
Sent from my Pixel 2 XL using Tapatalk
Devhux said:
Reddit has done that to me too, come to think of it.
Agreed that it's surprising we aren't hearing more of this. Makes me wonder if I should do a warranty swap.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
ethantarheels123 said:
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
Click to expand...
Click to collapse
definitely doesnt sound like a hardware issue.. ive experienced this on more devices than the p2xl and more so on stock.. u also might get it when ur data lags..
on the available custom roms i cant say i remember the last time it occurred.. either way, it cant be that bad to even remotely consider replacing it
elliwigy said:
definitely doesnt sound like a hardware issue.. ive experienced this on more devices than the p2xl and more so on stock.. u also might get it when ur data lags..
on the available custom roms i cant say i remember the last time it occurred.. either way, it cant be that bad to even remotely consider replacing it
Click to expand...
Click to collapse
Oh really? Have you only experienced this on 8.1 only, or also 8.0? I had the pixel 2 xl back in October/November on 8.0 and didn't experience any of this. I just repurchased the 2 xl several days ago and immediately noticed it within the first few hours of playing around with it.
I think it definitely is a software bug, if not a hardware issue. The touch input trace shows a ghost drag of a perfectly straight line to the bottom of the touch panel with an incredibly high Yv, I got one as high as 179. Normal hard flick scrolling would top out at around 30 or 40, so definitely something fishy going on here, whether it's software or hardware.
It happens for me like between 5 and 10 times within half an hour to an hour, and they are usually annoying enough where I lose my place where I was scrolling.
ethantarheels123 said:
Oh really? Have you only experienced this on 8.1 only, or also 8.0? I had the pixel 2 xl back in October/November on 8.0 and didn't experience any of this. I just repurchased the 2 xl several days ago and immediately noticed it within the first few hours of playing around with it.
I think it definitely is a software bug, if not a hardware issue. The touch input trace shows a ghost drag of a perfectly straight line to the bottom of the touch panel with an incredibly high Yv, I got one as high as 179. Normal hard flick scrolling would top out at around 30 or 40, so definitely something fishy going on here, whether it's software or hardware.
It happens for me like between 5 and 10 times within half an hour to an hour, and they are usually annoying enough where I lose my place where I was scrolling.
Click to expand...
Click to collapse
prolly 8.1.. i got mine around december late nov. pretty sure its software related.. they had an issue with touch on the lockscreen right?
It seems like so many touch issues with 8.1 release. For this reason, I am still using 8.0.
https://productforums.google.com/forum/#!msg/phone-by-google/FfzV1578L8Q/1HcWw3CCAQAJ
https://issuetracker.google.com/issues/70344455
ethantarheels123 said:
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
Click to expand...
Click to collapse
Any update with the replacement device? I am having the same sporadic ghost scroll: I'll be scrolling down a page on reddit or slickdeals app (happens with other apps as well), and randomly it'll perform a strong up-scroll... I notice it more often when I lay in bed on my side, and have the screen orientation locked to portrait, resting the phone on the bed horizontally...
ayoraider07 said:
Any update with the replacement device? I am having the same sporadic ghost scroll: I'll be scrolling down a page on reddit or slickdeals app (happens with other apps as well), and randomly it'll perform a strong up-scroll... I notice it more often when I lay in bed on my side, and have the screen orientation locked to portrait, resting the phone on the bed horizontally...
Click to expand...
Click to collapse
Replacement device has the same issue, so this is definitely a software bug. Hopefully Google fixes it soon in the next patch update.
Nexus 6P here. I started getting these ghost touches with the last security update. 8.1 is the problem, not a solution.
My mom has the same issue of touch on places she doesn't touch, on Pixel XL.
Could it be the same?
Here is a video about it that I took, just by scrolling in the settings screen:
https://drive.google.com/file/d/1JCsTuMDvMNHh0CO7sF7yoLFT26uNIhUp/
It's a bit hard to reproduce, but it occurs eventually.
Has anyone tried to use Android P, and see if it helps?
Anyway, I've reported about this here too:
https://forum.xda-developers.com/pi...h-pixel-xl-t3807188/post76879468#post76879468
Any fixes yet?
I know this is old, but I wanted to know if anyone found a fix for this. I eventually found an Oreo 8.1 Rom that I like and this is the only issue that's bothering me.
Been using my phone consistently for 24 hours. No root. Set it down after a messenger message, and couple seconds later, random rebooted. When it came back up, the gesture pill was flashing. Rebooted properly, and no more flashing. Weird. Anyone been having this?
There are several threads on the topic, and yes it seems to be quite the widespread issue. Some where able to fix this by doing a factory reset WITHOUT a backup from another device, some (like me) needed a replacement device.
We still do not know if its a software or hardware issue, or if these are two separate issues that are similar in symptoms but differ in cause (hardware failure/bug caused reboot & software/backup problem).
I'd suggest you either contact Google and get a replacement immediately or try a factory reset and manual setup (I assume you copied over your files from another phone?).
Wow, that is unsettling. Yes, I copied from an S21U backup. I've only seen this once so far, how extreme does it get? I searched before posting but did not see any discussions. I will look more. Thank you.
Replacement device ordered. More issues arose beyond the reboots, slow charging (6 hours from dead!), apps crashing, settings crashing, wifi issues. I love the phone, but not these issues from a 1k phone!
Have you tried a factory reset, then not restoring from backup (or if you did a cable backup/restore, try a cloud restore instead)?
I hate to suggest it because I restored my Note 10+ cloud backup with no issue, but enough other folks have suggested factory reset and not restoring a backup at all. Worth a shot. Good luck, whatever route you take.
pre4speed said:
Replacement device ordered. More issues arose beyond the reboots, slow charging (6 hours from dead!), apps crashing, settings crashing, wifi issues. I love the phone, but not these issues from a 1k phone!
Click to expand...
Click to collapse
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Morgrain said:
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Click to expand...
Click to collapse
Ugh, I am not liking hearing that. First pixel phone.
pre4speed said:
Ugh, I am not liking hearing that. First pixel phone.
Click to expand...
Click to collapse
That is some bad luck. Sorry to hear that. But the Packers won today so that's good
TrustAugustus said:
That is some bad luck. Sorry to hear that. But the Packers won today so that's good
Click to expand...
Click to collapse
Is what it is. I should know better than to adopt a new release anything lol. And GO PACK GO!
Morgrain said:
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Click to expand...
Click to collapse
I am on beta One UI 4 on my s21u currently, and the bugs on that are not the same bugs as the pixel, that's for sure. At least not the random reboots. But Samsung so heavily skins android, that is not a surprise. One of the main reasons I want to go pixel. Tired of Samsung putting their trash over vanilla Android