Develop Bugs

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.

G3 freezes on lock screen

I heard that this problem is very common on touchwiz devices but the g3 is starting to lock up and not let me unlock the phone whether it is pin or pattern lock. basically unresponsive. I will have to wait a minute or so and then it comes back to life.
D851 tmo
rooted on stock rom

F4M0U569 said:
I heard that this problem is very common on touchwiz devices but the g3 is starting to lock up and not let me unlock the phone whether it is pin or pattern lock. basically unresponsive. I will have to wait a minute or so and then it comes back to life.
D851 tmo
rooted on stock rom
Click to expand...
Click to collapse
Try immediately turning the screen off and then back on again. I've talked to a few people who have issues with the screen becoming unresponsive and this has been a work around.

Are you running ART? If so, swap back to Dalvik. Known issue and lots of threads regarding the freezing and lockup. I had it too and once I went back to Dalvik - it all resolved and improved dramatically.

F4M0U569 said:
I heard that this problem is very common on touchwiz devices but the g3 is starting to lock up and not let me unlock the phone whether it is pin or pattern lock. basically unresponsive. I will have to wait a minute or so and then it comes back to life.
D851 tmo
rooted on stock rom
Click to expand...
Click to collapse
I'm having the same freezes on start up. I love the phone but it's almost to the point where I think it is defective. Just got it yesterday. If problem continues I will definitely return it

LaRocKa1158 said:
I'm having the same freezes on start up. I love the phone but it's almost to the point where I think it is defective. Just got it yesterday. If problem continues I will definitely return it
Click to expand...
Click to collapse
Hi, are you still having problems?

F4M0U569 said:
Hi, are you still having problems?
Click to expand...
Click to collapse
Strange story... I ended up using my LG G2 for 3 days then giving the LG G3 a last chance. The first thing I did with it was install nova launcher. I have not experienced the lockscreen freeze up once since then. (Its been 2 days). I still am not 100% sure I am going to keep it, but the problem has stopped so far.

LaRocKa1158 said:
Strange story... I ended up using my LG G2 for 3 days then giving the LG G3 a last chance. The first thing I did with it was install nova launcher. I have not experienced the lockscreen freeze up once since then. (Its been 2 days). I still am not 100% sure I am going to keep it, but the problem has stopped so far.
Click to expand...
Click to collapse
does your randomly freeze? im gonna wait till LG decides to release an update. and if that still does not fix it then I will just return it or sell it

F4M0U569 said:
does your randomly freeze? im gonna wait till LG decides to release an update. and if that still does not fix it then I will just return it or sell it
Click to expand...
Click to collapse
No it doesn't anymore. It did for the first week before I installed Nova.

F4M0U569 said:
I heard that this problem is very common on touchwiz devices but the g3 is starting to lock up and not let me unlock the phone whether it is pin or pattern lock. basically unresponsive. I will have to wait a minute or so and then it comes back to life.
D851 tmo
rooted on stock rom
Click to expand...
Click to collapse
I had an LG G3, loved the camera, the screen, the size, the speed when it was speedy but due to the above I got rid of it, I am older and the phone is my life line it has to be reliable.

vonskie said:
I had an LG G3, loved the camera, the screen, the size, the speed when it was speedy but due to the above I got rid of it, I am older and the phone is my life line it has to be reliable.
Click to expand...
Click to collapse
I've had mine for a month now and have never seen this problem. Standard ROM, no rooting. Mine is encrypted and protected by a 4 digit pin.
Alan

I have one can't get thru it was set in regular swipe now it wants dbl tap n swipe can't get thru. ...HELP

downgrading to kitkat

hi guys. I wanted to downgrade back to kitkat because of the constant rebooting problem and I stumbled upon this warning message. is this true? please peruse the attachment.

You can downgrade back. Ive done it before. But why downgrade when MM is coming? Have you tried disconnecting and reconnecting battery? Or even resoldiering it?

Downgrading to KitKat works just fine. I've done it many times. I wouldn't worry too much about MM coming out soon. I mean, we've only had ONE article saying it's coming soon, but it still technically isn't an official source. A reliable one, but not official. KitKat is easier to deal with than Lollipop though in regards to Xposed and viper4android. The UI looks, and IS, better for the OLED display.

thank you friends. what was the deal with that screenshot of that warning anyway? is it outdated info?

NightShadow02 said:
thank you friends. what was the deal with that screenshot of that warning anyway? is it outdated info?
Click to expand...
Click to collapse
I think it's more of a warning that something could go wrong if you don't know what you're doing. That's the first I've seen any kind of message like that though.
Sent from my SM-T700 using Tapatalk

noxarcana said:
I think it's more of a warning that something could go wrong if you don't know what you're doing. That's the first I've seen any kind of message like that though.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
cool cool. got my tab s back to stock kit kat. oh so stable. what ROM are you currently running on your device noxarcana?

NightShadow02 said:
cool cool. got my tab s back to stock kit kat. oh so stable. what ROM are you currently running on your device noxarcana?
Click to expand...
Click to collapse
I'm on Lollipop right now waiting for Marshmallow. If MM isn't released by the end of August, I'll be going back to KitKat. KitKat is very stable in all ways! For me, viper4android works without issue, Xposed doesn't require you to be deodexed, and it just looks better.
Sent from my SM-T700 using Tapatalk

noxarcana said:
I'm on Lollipop right now waiting for Marshmallow. If MM isn't released by the end of August, I'll be going back to KitKat. KitKat is very stable in all ways! For me, viper4android works without issue, Xposed doesn't require you to be deodexed, and it just looks better.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
is lollipop giving you the random flickering screen then reboot problem? because i'm a sufferer of said problem ever since I updated.

NightShadow02 said:
is lollipop giving you the random flickering screen then reboot problem? because i'm a sufferer of said problem ever since I updated.
Click to expand...
Click to collapse
Only when my battery drops below 50% and it becomes more and more frequent the lower it gets. It becomes unbearable around 30%. Flickers with a green light, random reboots, and false power offs. The false power offs are when the screen goes black but the device is still on and reacts to volume buttons and home button. Pushing the power button would seem to do nothing but it's actually locking the device but you wouldn't know that because the device seems to be off. Pushing the power button again unlocks the device and the screen comes back on but will turn off again randomly within a few minutes.
I'm on my second Tab S right now. The display on my first got a hairline fracture in the digitizer so the screen had this temporary, at first, green/yellow tint which could be temporarily "fixed" by holding the corners and bending inward. Not the best fix as you can imagine. Everything else on it worked just fine but it was going to cost the same price as a new one just to fix the screen so I gave it to a friend and bought myself a new one. I had for just over a year.
Sent from my SM-T700 using Tapatalk

noxarcana said:
Only when my battery drops below 50% and it becomes more and more frequent the lower it gets. It becomes unbearable around 30%. Flickers with a green light, random reboots, and false power offs. The false power offs are when the screen goes black but the device is still on and reacts to volume buttons and home button. Pushing the power button would seem to do nothing but it's actually locking the device but you wouldn't know that because the device seems to be off. Pushing the power button again unlocks the device and the screen comes back on but will turn off again randomly within a few minutes.
I'm on my second Tab S right now. The display on my first got a hairline fracture in the digitizer so the screen had this temporary, at first, green/yellow tint which could be temporarily "fixed" by holding the corners and bending inward. Not the best fix as you can imagine. Everything else on it worked just fine but it was going to cost the same price as a new one just to fix the screen so I gave it to a friend and bought myself a new one. I had for just over a year.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
yes same symptoms! i can't use a tablet which goes crazy when below 50%. I tried an AOSP rom once which limited the CPU to about 400mhz and the flickering and shutdowns are minimized. but. what can you do with such a slowpokey device these days haha. when I was still on stock lollipop, enabling power saving mode helped a bit as well.
people keep saying it is a battery connector issue or something but I've replaced the battery and it still does the same thing. doesn't seem to happen on kitkat so far. so I hope the rumored marshmallow update will get that issue fixed. and I'm surprised samsung didn't develop a patch for this widely reported shutting down issue.
does your second tab S work like a charm on lollipop though? perhaps it's a different batch with a different motherboard or something.

I never believed it to be the battery connector. I'll admit I'm not electrical engineer or anything like that, but I've been playing around with devices since I was 5 by taking them apart and a battery connector just doesn't make sense to me. I think it's a OS and device (a certain batch or something) issue. None of these issues were on KitKat. My first Tab S had NONE of these issues whatsoever! Only this current Tab has shown these issues. It "works like a charm"....as long as I stay above 50%.
Sent from my SM-T700 using Tapatalk

noxarcana said:
Downgrading to KitKat works just fine. I've done it many times. I wouldn't worry too much about MM coming out soon. I mean, we've only had ONE article saying it's coming soon, but it still technically isn't an official source. A reliable one, but not official. KitKat is easier to deal with than Lollipop though in regards to Xposed and viper4android. The UI looks, and IS, better for the OLED display.
Click to expand...
Click to collapse
Do you have to unlock the bootloader to install any custom/stock room?
i'm kinda new with this

IsaacXDA said:
Do you have to unlock the bootloader to install any custom/stock room?
i'm kinda new with this
Click to expand...
Click to collapse
I know nothing of bootloaders. I have a WiFi only device and don't have to deal with a bootloader.

Unable to silence camera in latest N build.

Anyone have any ideas. Used to work no problem. Now if I rename or delete the one files nothing seems to happen.
Sent from my Nexus 5X using Tapatalk

Can you replace the file with a silent sound file? Have the same issue but if you can't even fix it I might not even bother rooting it again.
(Worst phone I've ever bought with this many issues when it was this new)

user2331 said:
Can you replace the file with a silent sound file? Have the same issue but if you can't even fix it I might not even bother rooting it again.
(Worst phone I've ever bought with this many issues when it was this new)
Click to expand...
Click to collapse
That doesn't work either.
Why do you find it the worst phone?
I will say it's the best phone I have ever used. I've had pretty much everything else from Samsung, Apple, LG, BlackBerry.
Best Android just because it's so clean without all the bloatware.
Sent from my Nexus 5X using Tapatalk

milan187 said:
Why do you find it the worst phone?
Click to expand...
Click to collapse
Well mostly because I've never had to root a phone to fix software issues, mostly pissed with LG support about the issue on the camera.
And the fact that it's opened a few times from slight tugs on my headphones(case cracked open), it is the smallest phone on the market while being huge, it resets my options, and not lately (nougat issue not a phone issue) it's locked me out of having volume above 60%.
And though I'm generally happy with a lot of things having this many issues with a new phone isn't fun.

user2331 said:
Well mostly because I've never had to root a phone to fix software issues, mostly pissed with LG support about the issue on the camera.
And the fact that it's opened a few times from slight tugs on my headphones(case cracked open), it is the smallest phone on the market while being huge, it resets my options, and not lately (nougat issue not a phone issue) it's locked me out of having volume above 60%.
And though I'm generally happy with a lot of things having this many issues with a new phone isn't fun.
Click to expand...
Click to collapse
Sucks to hear that. I've had a really gold experience but I guess that's not the case for all.
Sent from my Nexus 5X using Tapatalk

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.