Develop Bugs

[Q] Tab Pro 12.2: Screen and Button Issues

I just got this tablet (to replace the garbage SGH-I467) a few days ago (Thu., May 15th). For the first couple of days it worked like a dream. However, the last 4 nights/3 days, I have been encountering some strange issues. What I will do here is describe the issues I've been having, what I have done in attempts to fix them, list some of the things I think may have caused it, and include any additional info/questions.
Before all that though, I would like to mention that I am not a developer, but I am a bit 'tech savvy' and am more familiar with/knowledgeable of technology than the average user. Also, I have spoken with Samsung tech support and even had the support guy access my Tab Pro 12.2 remotely (I will explain what I learned from that below). So, without further ado (I apologize in advance for the long winded nature of this post, but I want detailed):
The Issues:
1) Screen "flickering"—By flickering I mean that it is shutting off and turning on rather rapidly and sporadically, though inconsistently.
I first encountered the problem 3 days ago (the 18th).
Four nights ago (the 17th), before going to bed, I plugged the device into the same outlet I have used for all my mobile devices, when I woke up (on the 18th) the screen was doing exactly what I described. I hit the home button a few times and it stopped.
That night (the 18th) I plugged it back in to the usual spot before going to bed. The next morning (yesterday, the 19th), the screen was "flickering" again. I tried to press the home key a few times, as well as both the soft keys, nothing. In between "flickers" you can see the lock screen, where I have to enter a pin, but even while visible I can't type anything. So this time, to try to solve the problem, I held the power button + volume up to get to recovery and wiped the cache partition, rebooted the device, and viola, it worked again. Thinking that I may have to factory reset the device if the problem persists, I used Kies to backup all my data. I used the tablet the rest of the day, even plugged it in (in a different outlet than the one next to my bed) for a while and had no issues.
Last night (the 19th) I did pretty much the same thing, but this time, thinking that it might be an issue with the device getting too much power (the Quick Start Guide says: "Note: Connecting the travel adapter improperly may cause serious damage to the device."), I used a travel adapter from one of my other, USB 2.0 devices (the only difference between the adapters is the output: 2.0 = 5.0V—2.0A vs. 3.0 = 5.3V—2.0A, and output was specifically what I was concerned with). This morning (the 20th) the problem has returned, but now includes my second issue: the hard home button and both soft keys, back and recent apps, no longer function. So I immediately tried to wipe the cache partition and reboot, but this time it didn't work. Thankfully I had anticipated this yesterday and had that Kies backup, so I wiped the entire device back to factory settings. But alas, it was unsuccessful and the problem persists, including the loss of button functionality, with the exception of the power and volume buttons.
It is important to note that when I first got the Tab Pro 12.2 and set up the lock screen, I used the option that delays the actual locking of the device 10 minutes after screen timeout, but set it so that if I lock the screen with the power button it ISN'T delayed and immediately locks. That being said, a couple of times when the "flickering" stopped long enough to momentarily use the device, I was able to enter my pin and unlock. But when the screen starts flickering again, it locks the device, so the power button must be affected as well. Though since the first factory reset of the device, I haven't set up a pin. I have done several factory resets and none of them have worked. The best result has simply been limited (no back, recent apps or home key) and momentary functionality. I tried using Kies to do emergency firmware recovery, but every time I click the option it disconnects the device.
When Samsung tech support remotely accessed by device (I used one of the momentary functionality windows to download the required application) the agent was able to utilized soft and home key functionality, even though I couldn't. This tells me that it was hardware related, not related to UI/software.
So there are a couple of things I think may have caused/contributed to the problem:
The first, which I vaguely touched on above, is the power issue. Perhaps I have shorted the device out somehow. The outlet I use to charge things while I'm sleeping is on the wall behind my bed, so I have to use a common extension cord, one that has 3 outlets at the end. I have a light plugged into that and in the past have charged both my SGH-I467 (AT&T Note 8.0) and my SGH-I747 (AT&T S4 Active) with that cord and outlet. That is the only place I have charged the SM-T900 overnight, but none of the other power sources I have used have caused these issues.
The second possibility is a virus some sort. I have never used the Samsung app store on any of my other devices, but in order to update the Hancom Office suite I had to. Since I had an enjoyable time using it to that end, I decided to see what else I could find on Samsung's store. I downloaded a couple of things (the "Official Captain America game" and a couple wallpaper/theme apps) and was looking around the store to see if there was anything else I wanted to download. I found several apps that had reviews claiming they were trojans, so I immediately checked the reviews for the apps I had downloaded, but none of them had similar reviews. However, that does not mean they didn't have viruses.
So, what do the resident Android gurus of XDA think about these issues?
I tried searching all over the forums and elsewhere online for people having the same issues, but couldn't find anything. Have any of you ever encountered something similar to this?
Until recently, I hadn't ever heard of anyone getting a virus on an Android device. Are they common? What is the nature of Android viruses?
If these issues do have something to do with overcharging/shorting the device, how can I mitigate that problem? Tonight when I charge the tablet, instead of using the USB 3.0 charging cable, I am going to try just using the 2.0 cable. As I understand it, that can be done by simply plugging it into the right side of the port. Hopefully that will stop exacerbating the problem.
Again, I apologize for such a long winded post. I would like to thank you all in advance. If ever I have problems with an Android, you guys are the ones to ask!
*UPDATE* Before I started typing this I was attempting to run the Kies 'Firmware Upgrade and Initialization', as opposed to 'Emergency Firmware Recovery', to see if that too would disconnect the device. Unfortunately it said that my device needed to be charged first. So I shut it down and plugged it into a surge protected strip and began typing this post. Occasionally I would go over an check the charge. While it was shut down and charging I was able to use the home key to bring up the green battery. Once the charge looked like it was about 75% complete I turned it back on and lo and behold, the "flickering" issue looks resolved and so does the button issue. I can go back, enter the recent apps and task manager, and use the home key functions. For how long this will last, however, is unknown. I guess we'll see in the morning. I'll post what happens tomorrow.

What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk

RE: Case?
dodo99x said:
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I am not using a case or cover at all...

same issues here
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.

VeinkWiles said:
So, what do the resident Android gurus of XDA think about these issues?
Click to expand...
Click to collapse
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.

Mike Austin said:
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Click to expand...
Click to collapse
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537

VeinkWiles said:
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
Click to expand...
Click to collapse
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk

Re: developer settings; display touches
dottat said:
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Damn! That's an outstanding idea! The only downside is that last night I sent the tablet to Samsung's repair department, so I can't test that out. But once I get it back, if the problem persists I will definitely be doing that first. Thanks for the advice dottat.

Fw:Re: developer settings; display touches
mikegbg said:
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
Click to expand...
Click to collapse
Hey dude, check out dottat's reply. He's got a really good idea that may shed some light on the source of the problem. Unfortunately, I can't try it out. If you do it, let me know how it goes. Maybe you can take some screenshots? Either way, hopefully you can get something out of it.

[Q] Touchscreen behaves erratically when charging

Hey All
Today I picked up an HTC One M8.
Have set it up and only had it up and running for a few hours.
I plugged it in to charge using the charger that came with it and noticed that the screen would become erratic. Phantom touches would register making it very hard to use. Have tried it in different sockets but the issue remains.
I have tried a spare charger that I have in the house and the issue is not present.I know the HTC charger is a little different in that it supports some kind of quick charger, so its not really a like for like swap I guess.
Is there a chance that the included charger is faulty? Or could the phone be at fault?
I really don't want to have to return it but will it it looks like its the phone that has an issue.
Thanks

Well, at this point its hard to guess from here. Can you upload some snaps/videos ? It would be helpful for anyone who visits the thread. It doesn't take much time either. :good:

Is it a brand new phone? if not I think the digitizer is going bad.

scorror said:
Is it a brand new phone? if not I think the digitizer is going bad.
Click to expand...
Click to collapse
Yeah it's brand new. Phone is fine off charge and when using other charges. It's just the stock charger tat seems to cause issues.

warpkid said:
Hey All
Today I picked up an HTC One M8.
Have set it up and only had it up and running for a few hours.
I plugged it in to charge using the charger that came with it and noticed that the screen would become erratic. Phantom touches would register making it very hard to use. Have tried it in different sockets but the issue remains.
I have tried a spare charger that I have in the house and the issue is not present.I know the HTC charger is a little different in that it supports some kind of quick charger, so its not really a like for like swap I guess.
Is there a chance that the included charger is faulty? Or could the phone be at fault?
I really don't want to have to return it but will it it looks like its the phone that has an issue.
Thanks
Click to expand...
Click to collapse
Do you have a case on your phone? I have a UAG case and the charger sometimes doesn't fully click leading to that behaviour. Without the case there is no problem using the phone while charging.

Maybe the stock charger is faulty. Probably the wires has lost continuity.

I have the same issue with a unofficial charger (2.0A).
No issue with original charger (1.5A)

You are not alone
I also have a HTC One M8 with the same problem!
I have to disconnect the USB cable so that I can use the phone correctly without 'phantom touches' activating things I didn't want.
A classic example is pressing the back button will more often than not take me to google now. It's not supposed to do that. It only ever does this when charging.
Also when using any app the phantom touches will activate things I didn't want it to. Some apps will indicate which button you clicked and this is the perfect way to see this problem in action, because buttons will be clicking that you didn't even touch.
It's almost like the touch screen becomes ridiculously sensitive and even just a touch of breeze from a fan can activate a phantom touch.
My phone has done this since brand new. I've had the phone for around 3 months now. There was a software update since I had the phone and it didn't fix the problem.
It does this for me with the stock USB cable, samsung USB cable, generic USB cable, charging from AC/PC/Car it doesn't matter.
It even has the problem when the battery is at 100% with the cable connected.
The only way to accurately use the phone is to unplug the cable!
I'm in Australia on the Telstra network
Android: 4.4.3
HTC Sense: 6.0
Software: 2.23.841.1
HTC SDK API 6.25

Erratic Touch on Verizon HTC One M8
This has been driving me mad.
Got Verizon Variant Red HTC One M8 near the beginning of August.
I bought a spigen clear case, a longer usb cable, and a 2AMP charger to use at work. I was chewing through the battery while playing Clash of Clans on it at work.
I pretty much always turn on visual feedback for touch on my smartphone now and noticed sometimes while playing Clash I would see multiple touches go in a horizontal line across my screen (if you do not know you play clash of clans in a horizontal position so technically the lines would run vertically down the phone)
I also have a tempered glass screen on my phone so I figured it was some kind of freak nuance with the case pushing the glass or something.
Bought a UAG Case for my phone, few days later I notice the same behavior, bought cases have a small "lip" to protect the screen if you drop the phone face down, I again figured this must be the culprit and bought a new case.
Barely there Clear case by casemate, I have had the case for 3 days and today is my first day at work since, immediately upon connecting my charger I noticed the erratic touch behavior.
At this point I realized it was never the case, it has to be something with charging in general or the specific charger I am using.
Anyone got any clue what is actually causing this issue?
Links to all of the hardware I mentioned in this post for clarification:
iXCC-SMART-Capacity-Travel-Charger/dp/B00HPTU0OU/ref=sr_1_16?ie=UTF8&qid=1410767078&sr=8-16&keywords=2+amp+charger
Hi-Speed-Braided-Tangle-Free-Charging-Motorola/dp/B00HZXYYQ6/ref=pd_cp_cps_2
Case-Mate-Barely-There-Case-HTC/dp/B00IZFYI28/ref=sr_1_1?s=wireless&ie=UTF8&qid=undefined&sr=1-1&keywords=barely+there+htc+one+m8
Spigen%C2%AE-STRONG-FLEX-Release-Capsule-Premium/dp/B00IF5B218/ref=sr_1_6?s=wireless&ie=UTF8&qid=1410767095&sr=1-6&keywords=htc+one+m8+case
URBAN-ARMOR-GEAR-Case-HTC/dp/B00IEFUB3E/ref=sr_1_1?s=wireless&ie=UTF8&qid=1410767120&sr=1-1&keywords=uag+htc+one+m8
EDIT: not enough posts to post links, but if you just insert the standard amazon address in front of all of those you'll get to the items in question.

Hi guys, any news?
I'm experiencing the same issue and this is driving me mad.
Experiencing this with different chargers. My cover is a Spigen Ultra Hybrid Metal Slate...if I put it off, theres no problem while charging
Greetings from Switzerland

Hi guys,
I have faced the issue as well. In my case, if I charge the phone using the dot view case then the touchscreen behaves wrongly. However, if I charge the phone with no case at all it works fine.
Anyway after I flashed the latest firmware (.401.6) the problem is gone. What firmware do you have?
Cheers.

Hi Guys,
For anyone interested, I have just noticed that it happened depending on the charger also.
Cheers.

I have the same problem
Using htc one m8 developer edition 4.4.2. This issue comes with every charger. With or without case or screen protection.

Yep, I've noticed this issue as well. Any solution?

warpkid said:
Yeah it's brand new. Phone is fine off charge and when using other charges. It's just the stock charger tat seems to cause issues.
Click to expand...
Click to collapse
If it's brand new, take it back for a replacement. The sooner the better because the longer you wait, the more they may think it is user caused.

I just got my phone replaced due to bad mic. I had a brand new one on release day and now I got a refurb both suffered the same issues. It's not always that it does it but it certainly pisses you off. Same symptoms as the op describes, I have yet to find a permanent solution.

This is so super irritating. I feel you. I just found out though that it occurs when I have my case on.. So whenever i use the phone when I'm charging I have to pull the case off. It really doesn't make any sense lol but this is my workaround for this bug.

I also have the same problem
It seems to occur when the phone is close to full charge. Every app goes crazy. When I unplug the charger it returns to normal.

jaycaplan said:
It seems to occur when the phone is close to full charge. Every app goes crazy. When I unplug the charger it returns to normal.
Click to expand...
Click to collapse
I have the same issue with mine; I found a website which said to do the following:
Using two fingers swipe down on the status bar then touch the gear icon > Display & Gestures > G-Sensor calibration
Place your phone on a flat surface then touch Calibrate.
After the calibration process has finished tap Ok.
You should also calibrate the finger touch on your screen to deal with the keyboard issue.
Open “Settings” and go to “Language and Keyboard”
Tap “HTC Sense Input”
Tap “Advanced”
Tap “Calibration tool” (Calibrate your screen for a better touch experience)
Now you are asked to type the given sentence
One done, Calibration Complete message appears
Hit “Reset Calibration” to reset screen to factory default
Click to expand...
Click to collapse
It's still present, but it hasn't been as bad - I turned on the visual feedback in the developers settings, and you can watch the cursor fly all about the screen like it's possessed!

Same issue here, on the latest software. This is my second m8 with the same issues.

Pixel XL Overheating issue?

I've only had my Pixel XL for about 5 weeks. Yesterday was the first hot summer day when I used it in my non-air-conditioned car with the GPS navigating and music playing via Spotify and the Pixel XL shut down 3 times because of extreme overheating. Is this an issue with the phone? I've never owned any phone that ever did this before. If the Pixel XL is going to do that all summer it's going to be pretty useless.
Pixel support made me downgrade from Android O to Nougat because if there is anything wrong with your phone and you are running Android O they use that as an excuse to get rid of you and move on to the next sucker who bought one of these things. I seriously doubt that Android O had anything to do with it.
Support sent me a long and ludicrous list of ways to keep the Pixel XL from overheating. If you spend 900.00 on a premium phone you shouldn't need to baby it to keep it running. I'm thinking about getting a One Plus and just canceling my Fi Service if this keeps happening.
Anyone else have experience with the Pixel XL shutting down because of overheating?
Here are the tips from Pixel Support if the phone keeps overheating on Nougat:
Hi Joe,
Thanks for contacting Google Support!
This email is in regards to the chat conversation we are having right now, as discussed, once you roll back to Nougat update, please follow the recommendations below if the issue persists.
Your device may warm up with use. Letting the device ‘take a break’ from use or limiting/turning off features (even those running in the background) could remedy the situation. Here are some tips/suggestions:
Media apps (music, video games)
1) Close or turn off other apps and features that you're not using; they may be running in the background.
2) Discontinue using the media temporarily until the temperature normalizes.
User-installed apps
1) Put the device in safe-mode to disable 3rd party apps and see if the issue improves.
2) Try uninstalling recently installed apps to pinpoint the app causing the issue.
Display brightness
1) Manually setting the brightness to be very bright may contribute to higher device temperature.
2) Consider setting to auto brightness to manually reducing the brightness setting.
GPS / 3G / WiFi - prolonged data connectivity
1) Turn off feature when not in use.
2) Stop or limit use and allow device to cool down if it gets warm.
Exposure to direct heat
1) Remove from heat and keep away from direct heat or excessive sunlight.
Poor ventilation
1) Expose the device rather than keeping it tucked away in poor ventilated/tight areas (layers, small pockets, bags).
Cases
1) Don't use a case that covers the front and back of the device.
2) Use official case (available on Google Store in some countries).
Chargers
1) Don't use unofficial chargers which can overcharge and degrade the battery.
2) Use official charger (available on Google Store in some countries).
Daydream View
1) Daydream View requires high performance from the device. The device's temperature should stay within safe limits.
2) Remove any protective cases from the device to improve thermal ventilation.
3) If your device feels too hot, stop using Daydream View and allow the device to cool down.
Android Wear
1) Power off the device for 5-10 minutes and turn it on again.
2) Try using the watch for another day to see if your issue improves. If your watch is still warm after a day, reply to this email and let us know.
Thanks,
Madasu
The Google Support Team - Supervisor

Why are you complaining exactly?
You were beta testing O when this occurred right?
Ish happens when you beta test.
thats what beta testing is for.
We should all be thanking you because when we all finally install the release for O we will probably not have that issue.
Thanks

I'm complaining because the current version of Android O is stable enough not to cause the phone to repeatedly overheat and Pixel support has tried to blame Android O for problems I had with this phone when I was still on Nougat--like awful phone reception in many parts of the city, which wasn't a problem with the same carrier on my Nexus. Is that clear enough? I did some research and Pixels overheating is frequently mentioned as a problem for this phone before Android O was ever released. If this is a premium phone it should behave like one.

Applications available from the play store may not have been optimized for O yet, so while it may seem like a stable build it is marked as a beta because it is still a WIP. It's like asking for support here on a custom ROM, would you go complaining to the dev about their latest nightly not playing nice with whatever? No, the dev would ask you to try replicating the issue on the last known stable build so they can begin to determine where from there things went wrong.
With all that said, I also recommend trying this using Nougat and see if your issue persists before anything else. All the overheating issues I have seen are either from using daydream or a defective device that needed to be RMA'd

Phone overheated and shut down again --on Nougat this time. Pixel support says that doesn't mean there is anything wrong with my phone--they consider this acceptable and normal behavior for their 900.00 phone.

Yes well regardless of the price there are conditions in which electronic devices cannot survive.
You seem to be subjecting your phone to one of those conditions.
You arent the first one to experience overheating.
Many people have experienced over heating with devices a lot more expensive.
I for instance blew a hose on my jeep and drained the radiator, thank god it was a steel block and I didn't do any irreparable harm.
Jeeps dont have the luxury of a cut off system for over heating like your phone does.

parakleet said:
Yes well regardless of the price there are conditions in which electronic devices cannot survive.
You seem to be subjecting your phone to one of those conditions.
You arent the first one to experience overheating.
Many people have experienced over heating with devices a lot more expensive.
I for instance blew a hose on my jeep and drained the radiator, thank god it was a steel block and I didn't do any irreparable harm.
Jeeps dont have the luxury of a cut off system for over heating like your phone does.
Click to expand...
Click to collapse
You're making excuses for Google which makes you either an employee or a moron. It's June. If Summer is a condition that this phone can't function under then it's crap. No excuses are possible --its just crap.

jhs39 said:
You're making excuses for Google which makes you either an employee or a moron. It's June. If Summer is a condition that this phone can't function under then it's crap. No excuses are possible --its just crap.
Click to expand...
Click to collapse
This is where I leave you.
Good luck.

like I mentioned earlier, you may have to RMA. Complain all you want, until you contact Google to get your device replaced you're beating a dead horse. Dude, we're people just like you trying to help you figure out what's up if you want to act like that go for it. It's your problem, not mine. Good luck.

I've contacted Google. This phone is 6 weeks old and was purchased from the Google Store. I not only have the standard warranty but I purchased the extended warranty because of the shabby way owners of the Nexus 6P were treated by Google and Huawei. I thought I was protecting myself by paying extra for the extended coverage--but if Google maintains that my phone is operating normally no warranty on the world will do me any good.
I've owned 100 dollar phones and 300 dollar phones and the Nexus 6p was a 600 dollar phone. I have lived in Chicago all my life and used all of these phones in the same city under the same exact conditions. I have never owned a phone before the 900 dollar Pixel XL that repeatedly overheated and shut down under the same conditions. And its only June! What is this phone going to do in July when it gets hot out every day?
It's disappointing that this XDA thread seems to be filled with Android fanboys who think it's a-ok for a 900 dollar phone to overheat and shut down as soon as the first hot summer days come along. I would have thought no reasonable person could possibly find that acceptable. Instead nobody on XDA offers useful suggestions, nobody on XDA offers support, understanding or empathy and as far as I can tell nobody on XDA seems to think the way my phone is behaving is unacceptable.
My conclusion is that the Pixel XL was only purchased by Android fanboys because of its prohibitive price, unlike previous Nexus devices that I owned, and that Android fanboys are every bit as useless and annoying as those of the Apple variety.
The XDA threads for Nexus devices are filled with smart people who provide useful feedback and help. The XDA threads for the Pixel XL are something different altogether. Dealing with people here is no better than dealing directly with Google.

if you purchased the extended warranty, then use it @jhs39 we can't call google for you

jhs39 said:
I've contacted Google. This phone is 6 weeks old and was purchased from the Google Store. I not only have the standard warranty but I purchased the extended warranty because of the shabby way owners of the Nexus 6P were treated by Google and Huawei. I thought I was protecting myself by paying extra for the extended coverage--but if Google maintains that my phone is operating normally no warranty on the world will do me any good.
I've owned 100 dollar phones and 300 dollar phones and the Nexus 6p was a 600 dollar phone. I have lived in Chicago all my life and used all of these phones in the same city under the same exact conditions. I have never owned a phone before the 900 dollar Pixel XL that repeatedly overheated and shut down under the same conditions. And its only June! What is this phone going to do in July when it gets hot out every day?
It's disappointing that this XDA thread seems to be filled with Android fanboys who think it's a-ok for a 900 dollar phone to overheat and shut down as soon as the first hot summer days come along. I would have thought no reasonable person could possibly find that acceptable. Instead nobody on XDA offers useful suggestions, nobody on XDA offers support, understanding or empathy and as far as I can tell nobody on XDA seems to think the way my phone is behaving is unacceptable.
My conclusion is that the Pixel XL was only purchased by Android fanboys because of its prohibitive price, unlike previous Nexus devices that I owned, and that Android fanboys are every bit as useless and annoying as those of the Apple variety.
The XDA threads for Nexus devices are filled with smart people who provide useful feedback and help. The XDA threads for the Pixel XL are something different altogether. Dealing with people here is no better than dealing directly with Google.
Click to expand...
Click to collapse
Whelp with that said. Go pound sand. If you can't get Google to replace you're faulty device because you're a little push over, then that's you're problem. Don't get mad at everyone else for not knowing whether or not you're phone is actually busted.

My pixel gets hot under very specific and limited circumstances. I RMA'ed my first one for this reason and now my second one does the same thing. Also, I got this second one on June 6th, little over a week ago.
So the conditions that make my pixel get very hot, very fast is this. Looking at XDA on Chrome, gets my phone HOT. It stutters, lags, and battery nosedives. A few other non mobile optimized sites warm it up, or sites with alot of ads, but XDA is basically un-browsable on it on Chrome. I'm on the O beta, and also using Chrome beta, but it acted this way on N too. So I just stay off the website and only use the app.
It's kinda annoying but everything else seems to work fine, so I'm not going to RMA another one.

I ride around with my Pixel XL in a black car, connected to my head unit, running Android Auto, Maps, and Spotify. The only thing I'm not doing that you probably are is running the screen at full bright.
I can give that a whirl to see if I can duplicate it, but as of right now I've never had an overheat shutdown.
Some questions:
Where do you have your phone mounted?
What kind of mount?
Is your phone in a case?
Do you have the same overheat problem if you place the phone in a different location with the same apps running? (say, in a cup holder or dash cubby?)
UPDATE: One hour of driving. Black car. Black interior. Mostly sunny. 85F ambient temp. Nougat 7.1.2 (5/17). Verizon network. Cell, WiFi, Bluetooth, and GPS radios enabled. Maps running. Spotify streaming via BT. Phone plugged into quick-charger. Screen full bright (100%). No holder in this car, so it was kept in the center console. No case. White phone. Windows open.
Result - did the phone get hot? Yes, it got hot, but not uncomfortably so. Did it overheat? No. Did it shutdown or display any other thermal alert? No, it did not.
So, either your phone is generating a hell of a lot more heat than mine, or something about where you have it mounted or the mount is causing a lot of heat buildup. If you've window mounted or dash mounted, consider vent mounting. Especially if you've a black phone and the sun's beating on it through the windshield. Also, if your mount either covers a great deal of the phone or has foam padding pressing against the back, consider switching out the mount for one that doesn't. That ****'s just an insulator and lets heat build up.

Mine has been very hot unplugging it from the usb cable for android auto in my vehicle but I haven't experienced anything yet like on the 6P. While I loved the design and some features that it had over the Pixel...that thing was a farking overheating throttling all the timepiece of shiite.

I tried the Pixel XL on Android O and the phone overheated. I tried Nougat and the phone overheated. I tried a custom Rom (DU) and the phone hasn't overheated yet, but the normal temperature of the battery when I'm in my air conditioned apartment iand the phone is completely idle s between 90-100F. Is that normal for this phone or should I press Google for an RMA? The only. othervthing I can think of is taking off the case and seeing if that makes a positive difference but I've been using Spigen cases on my last few phones and never had a problem with them.
Any constructive feedback would be appreciated. Anyone know what the normal operating temperature on this phone should be?

The reason of overheating may have to do with the SD821. If that is the case then there is no work around. The reason why I didn't buy the Pixel XL was because of the SD821. However i will buy the Pixel XL 2 with either SD835 or SD836.

dieselhazza said:
The reason of overheating may have to do with the SD821. If that is the case then there is no work around. The reason why I didn't buy the Pixel XL was because of the SD821. However i will buy the Pixel XL 2 with either SD835 or SD836.
Click to expand...
Click to collapse
Well that sucks. I know the processor in my Nexus 6P was supposed to have overheating issues but I thought that had been solved with the processor used in the Pixel.
Pixel Support offered to RMA my phone but they will send a refurbished one in its place and since the phone isn't even 6 weeks old and I paid 900 for this thing at the Google Store getting stuck with a refurb so fast seems like a rip-off. The Pixel XL already seemed like a ripoff at 900 for a new one--but for a refurb?
A replacement might not even be any better if the CPU is to blame like you suggest. I'm tempted to just sell this thing, go back to using my 6P until the inevitable boot loop of death and then get a One Plus. I will definitely never buy another Google device after getting burned twice in a row.

Instead of bashing Google, let's try to resolve this issue.
I would try installing an app to see if you have any wake locks. What's great about Android vs iOS is we have deep sleep. So when that phone shuts off your CPU goes down exponentially. If you are having heat issues, it could be your phone failing to go into deep sleep. I am on a non rooted phone and I get over 7 hours of screen on time and my phone lasts me easily a day and a half. Do you have anything synced? I check all my stuff manually besides Facebook and Snapchat. I would turn everything else off. Also I had a battery case and they all caused my phone to have wakelocks. I have read if you do not use the charger that comes with the device aka car chargers not from Google for the pixel, then I would assume that would give you heat issues. Are you having any other problems besides heat?

Dj21Oh said:
Instead of bashing Google, let's try to resolve this issue.
I would try installing an app to see if you have any wake locks. What's great about Android vs iOS is we have deep sleep. So when that phone shuts off your CPU goes down exponentially. If you are having heat issues, it could be your phone failing to go into deep sleep. I am on a non rooted phone and I get over 7 hours of screen on time and my phone lasts me easily a day and a half. Do you have anything synced? I check all my stuff manually besides Facebook and Snapchat. I would turn everything else off. Also I had a battery case and they all caused my phone to have wakelocks. I have read if you do not use the charger that comes with the device aka car chargers not from Google for the pixel, then I would assume that would give you heat issues. Are you having any other problems besides heat?
Click to expand...
Click to collapse
The primary problem is that the phone seems to run hot even when it's completely idle. Pixel support claims to have no information regarding what an acceptable temperature range is for this phone so I have no way of knowing whether my phone is running warmer than it should. They did offer to RMA my phone but admitted they would be sending me a refurbished one in return. The phone was 900 dollars and I bought it from the Google Store less than 6 weeks ago. I don't think they should be sending me a used phone. Any charger is going to make the phone warmer because that's the nature of the quick charge technology. GPS use according to the list Google sent me will make the phone warmer. GPS use also drains the Pixel battery quickly, so it's pretty much impossible to use the GPS on a long drive without also using a car charger at some point. I'm using the exact same car charger I used with my Nexus 6P and had zero overheating issues with that phone--at least that I'm aware of. The phone definitely ran much cooler than my Pixel does but the boot loop of death that plagues that phone is likely caused by too much heat for the solder to withstand over time--similar to the LG phones that also permanently bootloop. It's possible Google is trying to avoid a similar issue with the Pixels and that they are programmed to shut down before damage can occur. The problem is that I need a phone where I can reliably use the GPS and a car charger simultaneously on a hot day. The Pixel left me stranded because the phone kept overheating and I had to keep pulling off the highway to let it cool down so I wouldn't get lost. Google considers cool down periods for the Pixel normal and says so in the long list they e-mailed me of all the things that can cause the Pixel to overheat. I don't think Google should have sold this phone in the first place if they thought there was a good chance that it would overheat and shut down if you were using the GPS and a car charger at the same time. I'm still thinking about selling this phone and buying something cheaper and more reliable. I didn't pay a fortune for this phone only to be told by Google that it's fragile and needs to be treated with kid gloves.
I've tried to use the phone without a case. I tried a custom rom and kernel. I tried Greenify. I tried Naptime. The phone just continues to run at a high temperature no matter what I do. Maybe I do need to RMA the phone but getting stuck with someone else's used phone after paying so much for this thing really pisses me off. If I had a problem with a Samsung phone they would replace it with a brand new one in full retail packaging. Google should do the same.

Pixel 3 xl Wireless Charging Completely Broken

Wireless charging has recently stopped working on my Pixel 3 xl. It has been fine for about 2 months, but all of a sudden, wireless charging keeps kicking in and turning off intermittently. On my Pixel Stand it will start up for about a second then stop, and an orange notification light pops up on the base of the stand. I have noticed that sometimes, when I lightly shake my phone, it will start up and work again until I move it, so I'm thinking there might be something loose inside.
It is not charger related, as the problem exists on my Pixel Stand, my Anker charger, and multiple other chargers. It is not case related as it continues with or without a case on the phone.
It does not work in safe mode, and a full factory reset has done nothing for the issue.
Has anyone else experienced anything like this, and better yet, has anyone found a solution?

explodingscotsman said:
Wireless charging has recently stopped working on my Pixel 3 xl. It has been fine for about 2 months, but all of a sudden, wireless charging keeps kicking in and turning off intermittently. On my Pixel Stand it will start up for about a second then stop, and an orange notification light pops up on the base of the stand. I have noticed that sometimes, when I lightly shake my phone, it will start up and work again until I move it, so I'm thinking there might be something loose inside.
It is not charger related, as the problem exists on my Pixel Stand, my Anker charger, and multiple other chargers. It is not case related as it continues with or without a case on the phone.
It does not work in safe mode, and a full factory reset has done nothing for the issue.
Has anyone else experienced anything like this, and better yet, has anyone found a solution?
Click to expand...
Click to collapse
It sounds like a hardware problem like a loose connection at the charging pad that will have to be repaired at a shop. Definitely contact Google if you haven't already, it dose not sound like something that can be fixed on the software side.

Stupid question, but are you using a case while it is on the stand? Does the case happen to have something potentially blocking the middle of the phone where the charging coils are?

dcorrea said:
Stupid question, but are you using a case while it is on the stand? Does the case happen to have something potentially blocking the middle of the phone where the charging coils are?
Click to expand...
Click to collapse
I thought the same but OP said it recently stopped working, which made me think it was a phone issue. Also said shaking the phone can get it to work again, which seems more like an internals issue. Also possible that the case is right on the cusp of being too thick and sometimes it works if it's in just the right spot.

fury683 said:
I thought the same but OP said it recently stopped working, which made me think it was a phone issue. Also said shaking the phone can get it to work again, which seems more like an internals issue. Also possible that the case is right on the cusp of being too thick and sometimes it works if it's in just the right spot.
Click to expand...
Click to collapse
It also says "It is not case related as it continues with or without a case on the phone."

Misterxtc said:
It also says "It is not case related as it continues with or without a case on the phone."
Click to expand...
Click to collapse
Ah, missed that.

Yeah. I took it in to ubreakifix, a Google licensed repair partner in Canada and they confirmed that it is broken. They don't know what is broken, but it's broken. I will need to get it replaced through Rogers since I got it from them, which is a pain because they are super incompetent.

explodingscotsman said:
Yeah. I took it in to ubreakifix, a Google licensed repair partner in Canada and they confirmed that it is broken. They don't know what is broken, but it's broken. I will need to get it replaced through Rogers since I got it from them, which is a pain because they are super incompetent.
Click to expand...
Click to collapse
Just curious, does it happen when you put it on sideways? Sometimes that happens to my phone too, the orange light, but I didn't know what it meant. I would just take it off the charger and put it back on and it was ok but I didn't have to shake it. I sometimes wonder about the employees at ubreakifix. I brought my Pixel 2 in and got completely different diagnosis from 2 people there. And you're sure it's not the stand? Can you test it out on another stand, not a 3rd party one? I'm just offering suggestions since you might have some trouble returning it to a vendor that is not forthcoming in solving problems.

Long story short, I sent my phone in for repair through Rogers. It took them about 3 weeks to get it back to me but they ended up just replacing the device. No word on what was actually wrong with it.

Wireless Charging no longer works after recent update - Galaxy Note 10 Plus

I have a factory unlocked SM-N975U1 Note 10+, using on AT&T's network. It recently had an update pushed to it (early April 2022) that I let install before I went to sleep, then the next day found that wireless charging no longer works. I suspect the update is the culprit - so a software glitch. I have tried everything listed here: https://tinyurl.com/yckk9mmr by The Droid Guy, from rebooting to refreshing the system cache, to no avail. The wireless charger in my truck, on my desk at home, and my husband's wireless charger - all of with which it worked perfectly before the update to charge the phone - all recognize the phone is there but the LED on each begins to flash rapidly, so I am certain it is something with the phone. I am about to try to root the phone so I can install Titanium Backup or try Nandroid then do a factory reset. Short of that option of last resort, do any of you have any idea what else could possibly be the issue here? The only other thing I can think of would be the fact that the back glass is cracked, but has been for a while now, so while I could see correlation, I do not see causation. But I am by no means anywhere close to being an expert, so I may be wrong on that point. Any advice or suggestions would be greatly appreciated! I do not want to incur the expense of a repair from Samsung, and am considering perhaps just getting a Qi receiver - the type you'd add to a phone between the phone and case to add wireless charging to any phone. If nothing else, if you have any recommendations on that point as well they would be most welcome.
Thank you in advance for your time and assistance.

Could be a battery failure. Get the rear cover replaced and the phone inspected for damage.
Replaced battery if it capacity is less than 80% of when new ie SOT.
Updates can break things and make troubleshooting more difficult. This could've been caused by the update or be purely coincidental.

bdh1975 said:
I have a factory unlocked SM-N975U1 Note 10+, using on AT&T's network. It recently had an update pushed to it (early April 2022) that I let install before I went to sleep, then the next day found that wireless charging no longer works. I suspect the update is the culprit - so a software glitch. I have tried everything listed here: https://tinyurl.com/yckk9mmr by The Droid Guy, from rebooting to refreshing the system cache, to no avail. The wireless charger in my truck, on my desk at home, and my husband's wireless charger - all of with which it worked perfectly before the update to charge the phone - all recognize the phone is there but the LED on each begins to flash rapidly, so I am certain it is something with the phone. I am about to try to root the phone so I can install Titanium Backup or try Nandroid then do a factory reset. Short of that option of last resort, do any of you have any idea what else could possibly be the issue here? The only other thing I can think of would be the fact that the back glass is cracked, but has been for a while now, so while I could see correlation, I do not see causation. But I am by no means anywhere close to being an expert, so I may be wrong on that point. Any advice or suggestions would be greatly appreciated! I do not want to incur the expense of a repair from Samsung, and am considering perhaps just getting a Qi receiver - the type you'd add to a phone between the phone and case to add wireless charging to any phone. If nothing else, if you have any recommendations on that point as well they would be most welcome.
Thank you in advance for your time and assistance.
Click to expand...
Click to collapse
What happens when you charge with the usb c cable? Any warning message?

Is Samsung replacing these phones for this issue? I am so irritated. Just press the back of the phone hard and it will work again??? I remember the Fonz hitting the jukebox on Happy Days, but seriously on a $1,000 phone? Gimme a break.
I just had the same problem. Is this really a thing? I can't believe this is a known issue. I followed pressing just below the camera to the right of the back and now it works.
(see the post I found below).
There seems to be a problem with the wireless assembly’s contact to the
mother board which has a temp sensor attached. Give your phone a gentle
press on the back just under the camera and a little bit to the right.
This is just a temporary fix as the wireless charger will probably lose
contact again. Hope this helps.
From: https://de.ifixit.com/Antworten/Ansehen/644492/note+10+temperature+too+low
6
Reply
Share
ReportSaveFollow
level 3
BlackberryOne4579
·7 mo. ago
Thanks! This worked for me! Pressed on it a bit and something made a little click and boom it works
2
Reply
Share
ReportSaveFollow
level 4
Beb0p27
·7 mo. ago
No problem! Glad it worked!
1
Reply
Share
ReportSaveFollow
https://www.reddit.com/user/fwmccabe/
level 3
fwmccabe
·7 mo. ago
My Galaxy Note10+ quit wirelessly charging yesterday. I tried this and it worked! Thanks!

If I recall correctly the coil for wireless charging on the N10+ is connected by a ribbon cable. It may have become detached. Unlike the contact points Samsung used for the GPS antenna like on the S4 they should not fail.
Always use a good case to protect the N10+ from high G loading during drops as they can damaged the mobo or knock connectors loose even if there's no apparent outside damage. These are relatively heavy phones that wuv to corner impact when dropped.

Thank you for responding!
Weird, I have never dropped it. Its brand new and I have a good case on it at all times. Maybe it was just loose to begin with? Will this fix it for good as long as it doesn't get jarred loose?
So you are saying the contact points like the S4 would fail and this ribbon cable should not fail, just can come loose?
What does "wuv to corner impact" mean?

Tenacious--M said:
Thank you for responding!
Weird, I have never dropped it. Its brand new and I have a good case on it at all times. Maybe it was just loose to begin with? Will this fix it for good as long as it doesn't get jarred loose?
So you are saying the contact points like the S4 would fail and this ribbon cable should not fail, just can come loose?
What does "wuv to corner impact" mean?
Click to expand...
Click to collapse
The S4 had point contacts that were held in place by pressure and could corrode over time, completely different from a ribbon connector.
Whatever is loose or broken will likely need to be serviced eventually.
I wouldn't sweat, I never used wireless charging on my N10+'s, don't even know if it works. Cable charging is superior, faster and the C port socket on the N10+ is robust. Good for many thousands of cycles.

Tenacious--M said:
What does "wuv to corner impact" mean?
Click to expand...
Click to collapse
Wuv is love with a mean twist added...

Oh, lol!
Would pressing harder on the recommended spot possibly get it to mount down firmly to where it wont have constant problems? Or will it just get worse?

Tenacious--M said:
Oh, lol!
Would pressing harder on the recommended spot possibly get it to mount down firmly to where it wont have constant problems? Or will it just get worse?
Click to expand...
Click to collapse
Have the rear cover pulled and see what you got.
The coil assembly may have failed.
If the battery is near 80% of its original capacity then replace that then too. This phone is too valuable to be mucking with it by pressing on the rear cover... not a good plan.

So guess what? I had recently purchased this unit as NEW, Sealed with 1 year factory warranty with on eBay. Seller had good feedback so I thought I could trust them. I was so perturbed with this charging issue after only have it for two weeks that I got with Samsung Support. I figured I was covered since it was new, sealed and had a 1 year warranty with Samsung. They verified that this phone was activated April of 2020 and the warranty expired April 2021. He also said he can see that the battery life has been used to where it only has about 50% of the potency it had when it was new. Total fraud!!!

Tenacious--M said:
So guess what? I had recently purchased this unit as NEW, Sealed with 1 year factory warranty with on eBay. Seller had good feedback so I thought I could trust them. I was so perturbed with this charging issue after only have it for two weeks that I got with Samsung Support. I figured I was covered since it was new, sealed and had a 1 year warranty with Samsung. They verified that this phone was activated April of 2020 and the warranty expired April 2021. He also said he can see that the battery life has been used to where it only has about 50% of the potency it had when it was new. Total fraud!!!
Click to expand...
Click to collapse
Contact your bank and see if you can return it and have the bank do a charge back. Your state attorney general's office may be able to help as well but I would go with the first option and a full cash refund.
I do know a reliable vendor for new ones if you need that contact. I've used them. A1.

Thank you, I sure do appreciate that. Yes, I would love your contact if you would be so kind.