Develop Bugs

[Q] Galaxy Nexus self typing

Hi there,
first of all i apologize for my poor english. Got my Galaxy Nexus for a week and i'm not very excited about ICS. I expected great battery life and a few bugs but i've seen a lot. There's an annoying one : sometime my phone seem to live without my touch. If i'm with keyboard on it starts to type messages like "dajhfhakjerehk" then it go on the home and start open apps randomly without my touch. Seems like the volume bug but different; anyone experiencing this issue ?
I hope that's only software, otherwise i had to bring the phone back to the seller very soon.. I wish that 4.0.3 will be released soon so i can decide if it's software or hardware problem.
Thank you all in advance.

I have the same problem with mine, it doesn't happen often though and I can't reproduce it on queue but I have had my phone for 3 weeks now and it has happened happened several times so it's not just a one time thing.

guidocioni said:
Hi there,
first of all i apologize for my poor english. Got my Galaxy Nexus for a week and i'm not very excited about ICS. I expected great battery life and a few bugs but i've seen a lot. There's an annoying one : sometime my phone seem to live without my touch. If i'm with keyboard on it starts to type messages like "dajhfhakjerehk" then it go on the home and start open apps randomly without my touch. Seems like the volume bug but different; anyone experiencing this issue ?
I hope that's only software, otherwise i had to bring the phone back to the seller very soon.. I wish that 4.0.3 will be released soon so i can decide if it's software or hardware problem.
Thank you all in advance.
Click to expand...
Click to collapse
If you're running stock software and this happens frequently I think you should return your device for a new one - sounds like a faulty digitiser to me...

Snoemannen said:
I have the same problem with mine, it doesn't happen often though and I can't reproduce it on queue but I have had my phone for 3 weeks now and it has happened happened several times so it's not just a one time thing.
Click to expand...
Click to collapse
So i'm not the only one.. I can't reproduce me as well : sometime not happen for 2 days , sometine twice a day..
djmcnz said:
If you're running stock software and this happens frequently I think you should return your device for a new one - sounds like a faulty digitiser to me...
Click to expand...
Click to collapse
If it was the digitiser i think that it would stop always, not randomly every 2 o 3 day.. That's my opinion

djmcnz said:
If you're running stock software and this happens frequently I think you should return your device for a new one - sounds like a faulty digitiser to me...
Click to expand...
Click to collapse
It only happens every other day or even more rarely and it just for a short period so I'm not sure what is doing it.
I also have the more common multi-touch bug after using some 3D games like Heavy Gunner so I'm more inclined to believe that it is something that triggers it similar to that than for the digitizer to be faulty, but that might just be me trying to convince myself that it will be fixed since I don't want to go through the hassle to replace the phone.
Hopefully google will release the next update again soon, be it 4.0.2 again or .3 or whatever, I'm still on ad yakjuxw with 4.0.1 so I was going to wait untill I get the update before I take any action.

Snoemannen said:
It only happens every other day or even more rarely and it just for a short period so I'm not sure what is doing it.
I also have the more common multi-touch bug after using some 3D games like Heavy Gunner so I'm more inclined to believe that it is something that triggers it similar to that than for the digitizer to be faulty, but that might just be me trying to convince myself that it will be fixed since I don't want to go through the hassle to replace the phone.
Hopefully google will release the next update again soon, be it 4.0.2 again or .3 or whatever, I'm still on ad yakjuxw with 4.0.1 so I was going to wait untill I get the update before I take any action.
Click to expand...
Click to collapse
me too , let's wait

It's all about the 4.0.1. I had that issue before, now it works fine with 4.0.2. Just update and that problem will disappear.
Sent from my Galaxy Nexus using xda premium

I have the exact same problem, and I must say I am so relieved to see it's just a software bug! Thanks, Rilazi

sorry for bumping this thread but the issue it's very annoying.. I can't even use my phone, it start doing things himself!! How can i do ?

[Q] Nexus 7 owners...... problems, fixed or not?

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.

Touch "gets stuck" on letters while typing

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.

No Charge Without Re-Boot [Un-Solved - It's Baaack]

I've noticed recently (~3 times in last couple weeks), my Pixel XL will not start charging unless I re-boot, from 25%-35% charge. I've swapped chargers (Nexus 5X vs Pixel XL) and USB-C cables without success.
A simple reboot fixes the issue, but is a bit of a pain.
Pixel XL 128
7.1.1, Jan Update
Rooted
TWRP
Verizon SIM
Anyone else seeing this oddity? Any suggestions to correct??
Edit: 1/15 Replacement Device received, unlocked & rooted. The issue returns after just one day! Reboot needed to re-charge.

I have this same problem! I have had it since getting the pixel with root, custom kernel. Thought it was the kernel but the device swears it has nothing to do with it.
I haven't had TWRP very long but it happens still. It's random, and a reboot always fixes.
I wish I knew the cause, but too annoying to run full stock unrooted to test lol.

I've had this issue as well even with stock. Completely random. I've since flashed Pure Nexus since it's release and haven't had the issue anymore.

Happened again this morning. Gah, no overnight charge.

Chatting with Brian at Google.
He jumped to "Sending a Replacement Phone" after about 2 mins of very basic discussion. Seems odd, but whatever. Seemed a pretty quick surrender...
I did inquire if this was a known issue. He said, No, probably just a rare scenario.
I'll probably run stock for a while on the new phone to see if this recurs. Then I'll return to root and monitor.

markp99 said:
Chatting with Brian at Google.
He jumped to "Sending a Replacement Phone" after about 2 mins of very basic discussion. Seems odd, but whatever. Seemed a pretty quick surrender...
I did inquire if this was a known issue. He said, No, probably just a rare scenario.
I'll probably run stock for a while on the new phone to see if this recurs. Then I'll return to root and monitor.
Click to expand...
Click to collapse
Interesting. I don't feel like getting it replaced, because I have a dbrand skin on it that would not transfer.
JagXK8 said:
I've had this issue as well even with stock. Completely random. I've since flashed Pure Nexus since it's release and haven't had the issue anymore.
Click to expand...
Click to collapse
Hmm, how long have you been running on PureNexus? Sounds promising.

xocomaox said:
Interesting. I don't feel like getting it replaced, because I have a dbrand skin on it that would not transfer.
Hmm, how long have you been running on PureNexus? Sounds promising.
Click to expand...
Click to collapse
Since 1/6. I've actually had 3 problems with my pixel. Randomly not charging, volume buttons not working and times call quality. But so far haven't had any issues after flashing pure nexus. I did chat with support but wasn't a quick surrender.
Sent from my Pixel XL using Tapatalk

JagXK8 said:
Since 1/6. I've actually had 3 problems with my pixel. Randomly not charging, volume buttons not working and times call quality. But so far haven't had any issues after flashing pure nexus. I did chat with support but wasn't a quick surrender.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I am almost certain it is a software issue. I am going to flash Dirty Unicorns soon I think which will hopefully fix the problem.

xocomaox said:
I am almost certain it is a software issue. I am going to flash Dirty Unicorns soon I think which will hopefully fix the problem.
Click to expand...
Click to collapse
I am inclined to agree its a software issue, which is why I was surprised "Brian" offered a hardware replacement so quickly. I did very recently do a Factory Reset to address my "Double-Tap-To-Wake" issue (reset fixed it), so maybe this was his queue to not try yet another reset...

markp99 said:
I am inclined to agree its a software issue, which is why I was surprised "Brian" offered a hardware replacement so quickly. I did very recently do a Factory Reset to address my "Double-Tap-To-Wake" issue (reset fixed it), so maybe this was his queue to not try yet another reset...
Click to expand...
Click to collapse
I think Google offering to replace units quickly isn't terribly surprising.
The cost for them to replace a unit is very low. They are probably shipping out a refurb, and are only paying for shipping costs. The unit that will be returned is surely fixable with ease and can be re-deployed to another user. This is a super low cost way of providing what appears to be excellent customer service to the end-user. Apple and other companies have done this for years and have been very successful.
EDIT: I am now on DU so I will let this thread know if I have any more charging issues.

Woke up this morning to charge my phone, didn't start charging. Rebooted to fix. Made a call and the call quality was like I was in a poor reception area. Oh well still happens at random. Think I'm ready for a replacement.
Sent from my Pixel XL using Tapatalk

JagXK8 said:
Woke up this morning to charge my phone, didn't start charging. Rebooted to fix. Made a call and the call quality was like I was in a poor reception area. Oh well still happens at random. Think I'm ready for a replacement.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Well it happened to me last night on DU. I think I might be able to use this as a free replacement card down the road to get a refreshed unit. It's crazy that without touching the phone I can reboot it and it will work.

My replacement devices arrived last night - Pixel XL, 128GB, Black.
They are probably shipping out a refurb...
Click to expand...
Click to collapse
Especially with all the shipping delays, I fully expected this replacement would have been a refurb. By all appearances this replacement is new or at least a pristine refurb. Packaging and accessories were clearly new (that part is easy), but the phone's back, corners, edges and glass are all 100% flawless.
The phone appears to be playing well. Ran it on Daydream for 2:27 last night to watch a NextVR basketball game - no overheating, possibly sightly less drift than my old device.
Edit: My plan to hold-off rooting failed - I am unlocked & rooted, but kept the stock recovery vs TWRP (in anticipation of FlashFire).

Replacement Device received, unlocked & rooted. The issue returns after just one day! Reboot needed to re-charge. Blargh!
I should have used a little more discipline and not rooted right away - for science.
I am doubtful I'll revert to stock to test some more, but who knows.

Odd. Given that not everyone who is rooted has this issue perhaps sharing a list of mods/root apps and other apps that you installed on the new device could help to shed some light on where things to sour.

I seem to have had this issue ever since I rooted and installed ElementalX kernel. So it would appear that either I have a bad device, it's root, it's the elex kernel, or both root+kernel causes this.
I've modded emoji's but only once or twice, definitely had the issue on a fresh DU and PureNexus install with only root and kernel.
I am still questioning the charger, but not much because I also use the USB-a to USB-c cable connected to a cheap 1a chsrger at work with the same problem. So very unlikely it is the cable.

xocomaox said:
I seem to have had this issue ever since I rooted and installed ElementalX kernel. So it would appear that either I have a bad device, it's root, it's the elex kernel, or both root+kernel causes this.
I've modded emoji's but only once or twice, definitely had the issue on a fresh DU and PureNexus install with only root and kernel.
I am still questioning the charger, but not much because I also use the USB-a to USB-c cable connected to a cheap 1a chsrger at work with the same problem. So very unlikely it is the cable.
Click to expand...
Click to collapse
For me, still a most basic configuration:
- rooted (supersu 2.79-sr2)
- stock recovery
- stock kernel
- stock launcher
- no roms
At the moment, the only root-apps that possibly raise a flag as not fully stock. Nothing odd in this list as far as I can see:
- adaway (modified hosts file)
- titanium
- flashfire (not in use)
- rootchecker
- quickreboot
- tasker & autolocation
Next instance of no-charge, I'll try the brand new charger & cable from the replacement packaging.

markp99 said:
For me, still a most basic configuration:
- rooted (supersu 2.79-sr2)
- stock recovery
- stock kernel
- stock launcher
- no roms
At the moment, the only root-apps that possibly raise a flag as not fully stock. Nothing odd in this list as far as I can see:
- adaway (modified hosts file)
- titanium
- flashfire (not in use)
- rootchecker
- quickreboot
- tasker & autolocation
Next instance of no-charge, I'll try the brand new charger & cable from the replacement packaging.
Click to expand...
Click to collapse
It's strange if it is root causing it, why has nobody else mentioned anything? I'm glad you get it on the stock kernel, so that rules that out.

xocomaox said:
It's strange if it is root causing it, why has nobody else mentioned anything? I'm glad you get it on the stock kernel, so that rules that out.
Click to expand...
Click to collapse
I'm not rooted and my bootloader is not unlocked and still have this issue from time to time. So pretty sure it has nothing to do with root. Trying to use some usb-c headphones once (they didn't work) did trigger it immediately. It's likely going to be related to the usb-c port in some way, possibly a firmware issue?

I also randomly encounter this problem. I already returned 1 pixel xl that quit charging, completely stock, a reboot did not fix it. On my second device and still occurs occasionally seems like it takes a week or so and a reboot fixes, so not sure what the problem is. Still completely stock.

Google Pixel XL Lags sometimes

What's up guys.
I'm facing occasional lags on my Pixel. Every now and then the launcher and UI overall become unresponsive. It happens with the stock rom and LineageOS. I think it could be caused by an app or something but I haven't had any luck finding the culprit.
I tried disabling Digital Wellbeing, and even though it seems to work at first the lag comes back time after.
How are your Pixels standing up? Do you have any lag on yours?
I have a Verizon Pixel XL with the bootloader unlocked, do you think unlocking the bootloader may cause this issue?
Hope to heard from you, my experienced comrades.

I suppose a fresh flash is needed. However, as you said you are on LOS, so you have already done a fresh installation. In that case I am not sure. Maybe something hardware breaking as the device is old or something? I certainly wish not.

ithehappy said:
I suppose a fresh flash is needed. However, as you said you are on LOS, so you have already done a fresh installation. In that case I am not sure. Maybe something hardware breaking as the device is old or something? I certainly wish not.
Click to expand...
Click to collapse
Hmm, this is my 2nd Pixel. I recently purchased 2 for some friends, I also had a 32gb version before, all of them have the same issue. I just happen to think is caused by Android P.

liriolebron said:
Hmm, this is my 2nd Pixel. I recently purchased 2 for some friends, I also had a 32gb version before, all of them have the same issue. I just happen to think is caused by Android P.
Click to expand...
Click to collapse
I happen to have a stuck-for-few-seconds problem way back when the phone was new, on Nougat. It drove me crazy. Sold the first pixel for that reason alone and moved to the dark side. But then when I came back to another Marlin after couple of months I found that the problem was gone! Sometimes this type of problem happens on some specific Pixel devices I suppose, its not reported as it happens to a very few Pixels I guess! Either wait for an upcoming update to see whether it fixes stuffs, or maybe move to some other device. But I feel you, I remember quite well how that problem made me go total bonkers, probably you will find my threads on it as well. Good luck.