Anyone run into this yet. https://www.androidpolice.com/google-pixel-6-and-6-pro-screen-flicker/
"Some Redditors speculate that the flickering might be related to static discharge that's released when hitting the button."
Yeah, nothing like the rocket scientists at Reddit to come up with sound answers
Static electricity would destroy the display.
FET's are very sensitive to over voltage on their gates.
Maybe what they were trying to say was unintentional temporary surge on the gates of the matrix TFT's.
If that's the cause long as that surge doesn't exceed the max specs for the FET's in the matrix it's not damaging. If it does, outlook not so good.
If it's not happening during normal operation once on, it's probably a harmless quirk.
Who knows maybe intentional to give it some character I sort of think it looks cool... but Google isn't cool so yeah, it's a fk up.
I have it on my P6P. Turn phone completely off, quickly tap power button and it'll flicker. I'm guessing it's trying to power up but since you only quickly pressed the button, not full power is given.
I'm not worried about it.
I've seen no noticeable flicker at all. Perhaps I just lucked out on this phone?
By design there is an inbuilt delay so you have to press and hold the power button, this helps prevents accidental power ups and also allows time for the user to press other combination of buttons (i.e. to get the bootloader screen), so on a quick press things are still happening behind the scenes like a pre-flight check, and the screen electronics are probably immediately powered up as part of this pre-flight check.
When the button is released without reaching the timeout period to trigger a full power on, the phone just goes back to being off again, now you have a falling voltage which doesn't always drop immediately due to stored charges in capacitors, and that can cause odd glitches sometimes as components see lower voltages than they are designed to work with. With sensitive chips (like flash memory) there will be brownout detection, so they immediately stop cleanly when they see a low voltage, and before that voltage has dropped so low it starts causing oddities or malfunctions. The glitching might also just be the effect of other devices stopping and magnetic fields collapsing causing some spurious data to get to the screen before the screen itself has powered off.
It certainly isn't a fault or anything to worry about, just a quirk of the design.
is it really an issue? Or just phone geeks looking for something to complain about? What effect does it actually have on the usage of the phone?
skimminstones said:
is it really an issue? Or just phone geeks looking for something to complain about? What effect does it actually have on the usage of the phone?
Click to expand...
Click to collapse
Without knowing what's happening it's impossible to say it's harmless.
See my previous post.
At this price point I would send it back... or not and risk eating the repair latter. It could be mobo hardware related.
Google addressed this today saying to basically power your phone like you normally would, without pressing the power button in quick succession without powering the phone up, and that a fix will be out in the December patch/update.
It's not a hardware issue.
Link (Google community post): https://support.google.com/pixelphone/thread/133351387/pixel-6-pro-display-residual-light?hl=en
I had this happen once where the scrolling on the screen stuttered the entire time scrolling, then after closing the app and opening it again it was fine again, and haven't seen it since. My guess is that phone went into a deep sleep state, and took some time to wake
Ironically, I'm getting it using XDA website!
Related
The subject heading pretty much says it all. I think about once a week I'm coming to my phone, pressing the power button to wake up the screen, and I'm finding that the phone was totally off.
Just the other day it happened twice. Never happened before, and it may be a one off.
But am I just accidentally taping power off (which I'm pretty sure I am) or am I going towards making sure my backups are current and getting a replacement (no doubt referbished) Desire?
Perhaps it's a 3rd party application causing the issue?
I'd suggest you do a hard reset and see if the problem comes back.
It's pretty difficult to accidentally power off your device. You still have to go through 2 screen taps to power off after you long-press the stand-by key.
Get it exchanged if you've ruled out any 3rd party applications.
This happened to me for the first time yesterday. Left my phone in the glove box of my car, came back and it was turned off. It would turn back on either, I tried for ages in a mild panic!
When I got home I removed the battery for a bit and then it suddenly worked.
All been OK since.
ohyeahar said:
Perhaps it's a 3rd party application causing the issue?
I'd suggest you do a hard reset and see if the problem comes back.
It's pretty difficult to accidentally power off your device. You still have to go through 2 screen taps to power off after you long-press the stand-by key.
Get it exchanged if you've ruled out any 3rd party applications.
Click to expand...
Click to collapse
I was thinking about 3rd party applications, but haven't started investigating. Probably because of the frequency it occurs and the amount of apps I have. Though I think I only have pretty popular apps.
I did a post a while ago that I had dropped the phone in a very minor way that would not have broken a Jacobs Cream Cracker (if you don't live in UK, they are very fragile, brittle, biscuit type things). But on each of the two times, one of them being a very cushioned landing, when I picked up the phone, it was off. I was thinking that this must have been what happened. But I'm now thinking it was either a separate issue or coincidence because I don't drop the phone and it still is sometimes off. And I think this occured before even the minor falls.
Hmmmm.....
I just did a test and dropped it from exactly 3cm flat onto my desk and it was instant off. I should add that I have a silicone/gel tight case on my Desire.
Like I said before I don't think this is the main problem, I think this is a secondary issue. And as I've said before, I think the phone going off from this sort of a drop/shock is too sensitive and delicate. Maybe sometime is not quite as tight as it could be in other people's phones.
Perhaps the body of your device is a bit warped such that the battery is a bit loose. That would explain why your device would power off from shock. The battery contacts may have shifted.
Try this. Take off your battery cover. The battery contacts should be on the left (the side without the volume rocker). Try to leverage the right side (the side with the volume rocker) of the battery so that the battery remains in contact with the device. I would try to slip thin strips of paper on the right so that it pushes the battery to the left.
Then try your 3cm drop test again. See if it improves.
If it improves, you can choose to continue using this method (despite how ghetto it is). Or you can see if you can get it replaced under warranty. Don't mention that you dropped the device, of course!
Other issues (like the glovebox fellow) could be related to heat, too. If it's too warm, I wouldn't be surprised if it turns off and doesn't turn back on until it's cooled down.
The phone has never yet failed to turn on the instance I've pressed the power button.
Looking into said ghetto method....
Nope. Contacts on the phone are all sprunt and sticking out nicely to meet the contacts on the battery, which will then compress the sprung contacs. So I doubt pushing any of the contact out further will help.
Is there any sound meant to come from the phone when you shake it? I don't mean furiously shake it, but just a milding shaking by your ear.
I have always heard a small movement but had assumed it was the vibrating mechanism.
Cleargrey said:
Is there any sound meant to come from the phone when you shake it? I don't mean furiously shake it, but just a milding shaking by your ear.
I have always heard a small movement but had assumed it was the vibrating mechanism.
Click to expand...
Click to collapse
Its the camera lens (internal focus part). Its like this on all HTC devices due to the lens they use.
I would like to have the screen power down, but leave the touchscreen active. Then I can tap/swipe the screen to return the display, instead of hitting the power button. [Note: This is only for a "docked" state.]
Also, since "Display" is always the battery killer, this could prove useful for battery savings. With the screen dimmed to 20, I'm drawing about ~500mA. With the display is off, the power draw is ~100mA. Pandora is playing away the whole time. [Note: I'm not checking the power draw often, so take these numbers with a grain of salt.]
I would really like the nitty gritty details on how the power is routed to all the components (i.e. what can be independently powered up/down, and what is on the same power bus).
Any kernel gurus out there?
To be honest, this just sounds like a not-so-good idea.
Why not just flash something that gives your optical button joystick thing an unlock function?
And if you are just using this for when it is docked, why not just leave the screen on?
So, flashing an unofficial rom is a good idea, but tweaking one is not? If people didn't try the "not-so-good" ideas, this site wouldn't exist.
I have CM7, so I have the feature... disabled. The OJ button pushes the phone "dock" across my desk, and unlocks my phone if I pull it out of my pocket the wrong way. Besides, this is only substituting one button for another.
At a minimum, it would be nice to get the backlight to <5 (out of 255, not %), but I assume a full power down is where the real power savings will come from. I just want to tap the screen to bring back the UI.
sealdog said:
And if you are just using this for when it is docked, why not just leave the screen on?
Click to expand...
Click to collapse
Charging + screen on + CPU active = overheating battery. (i.e. It's not good for the battery.)
No need to get defensive but I see your point.
I think he just meant not optimal or efficient but it is your phone and actually sounded like an idea I thought of a while back. I'll be watching the thread.
06stang said:
No need to get defensive but I see your point.
I think he just meant not optimal or efficient but it is your phone and actually sounded like an idea I thought of a while back. I'll be watching the thread.
Click to expand...
Click to collapse
That was more after-work-commute mood than anything he said. I thought I caught the pissy bits (that isn't the original text), but apparently not.
So, sorry, SealDog. I didn't mean to be such an _____.
Anyways, here's another way to think about it, or just more info....
I just plugged in to AC, and the battery is at 23%. This means the charge current is at ~950mA.
With the screen off, it's putting ~800-850mA towards charging the battery (fast charge rate). With the screen on, it's only putting ~500mA towards charging (trickle charge rate), and burning up ~450mA.
Somewhere around 40-42 degrees C, the charge controller drops to ~500mA, because the battery is getting too hot. Yet, I'm still drawing ~450mA, leaving almost no current towards charging.
When it gets hotter (42-44 degrees C), the charger shuts off completely. Now, I'm just discharging the battery.
I have run into this too many times. 6+ hours on the charger, and the battery has only charged up 10-15%. Not cool. (In fact, the phone is freaking hot.)
BTW, I'm trying find every on/off setting I can (e.g. 1x/3G toggle). Mainly, I want to know what each unit's idle power is. I read about lots of battery saving things, but do they really help? Does 1x truly draw less idle current than 3G? Does shutting off wifi, gps, etc. actually save power when idle? Byrong did a nice backlight + CPU frequency examination. I'd just like to go further. I have an incomplete test built in Tasker (I have to fix the stinking task priorities, and remove all "sleeps").
My ultimate goal is to have a set of Tasker profiles that optimize power consumption for my purposes, without sacrificing functionality. For example, my mobile data choice is on or off, but off means C2DM can't reach the phone. I have plans for C2DM, so this isn't something I wish to sacrifice. But, if the screen is off and the network load is near zero, 1x is sufficient.
Try screen stand by root
『Moved by touch™』 ?
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E
This is available on my S3 i9300 with Siyah kernel, but I don't use it for two reasons:
- Accidentally activating the screen and waking the phone
- The digitizer normally turns off, and leaving it on drains your battery.
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.
Hey there. I'm a bit new to this side of XDA. Honestly with how long I've been AWOL from this site nothing is familiar anymore. How time flies. Well my first post back in years couldnt be more unfortunate phone wise, I've had my Z2 for a couple of months now and as a mechanic it's been treated like all my others phones prior, rough. I've been locally recognized as the guy who has a new phone every couple of months because he can't not shatter a phone. An expensive hobby of breaking phones. Well luckily I didn't shatter my Z2. I just water logged it. Gotta change things up right? So here's where the interesting problem comes in, I let the phone sit in rice for 30 hours, switching the rice out half way through. It acted up like you would expect in the first couple of hours but then stopped. When I pulled the phone out I scraped the rice out of all the books and crannies and tried to power it on, to no avail. Dead battery I assume, so I plug it in. Charge icon pops up, a sign of life! How glorious. So I let it sit for a minute as I assume the battery probably dropped below minimum voltage when the LEDs were freaking out. Went back to the phone, held the power button and no screen, but "Hello, Moto!" So at this point I'm convinced the screen is dead, so I force it off with the volume down method and pry off the screen. To find what? More water. Good Lord. This phone is incredibly water resistant just in reverse. So I do the only thing that makes sense at this point, I remove the ribbion connector from the board for the display and put the phone back in new rice as 2 separate pieces. I then leave it in there for another 30 hours switching the rice halfway. Bringing us to now. I took the phone out, cleaned all the rice out of the 2 pieces and off the remaining adhesive and connected the ribbion back to the board. Plug the charger in, and again, charging logo. But then I hold the power button and the TMobile splash screen pops up! Then the screen goes dead and once again, "Hello, Moto!". But whats different is now when the boot sequence is finished I can interact with the phone and it works, shake for flashlight, enter my passcode (just by feel cause I'm good like that, ladies hmu), and the button responds with vibration. The phone is working but no screen. So at this point I'm sure, the display driver is done. I murdered it in cold daylight. So I shut it off and start looking around for new screens, in the midst of this I knock the phone and accidentally hit the power button, and it starts to boot up. T-Mobile spash screen, screen death, "Hello, Moto!", and nothing. Now that seems weird. Why would it work twice on the TMobile splash? So I decide I'll try putting it in fastboot for S&G's. Restart, put it in fastboot and the screen stays on. Beautiful and clear as day, all buttons work, everything reads fine, but, if I go to boot it or do anyother action than "retart bootloader", the cycle continues. T-Mobile, death, hello Moto, nothingness. Now at this point I'm okay with the phone being dead, it's fine, but I'm intrigued now. What would cause the screen to work just fine when in the bootloader and the TMobile splash screen, but die when it boots? The phone is very clearly working in the background. I logged in, used Google assistant, used the flashlight, pressed buttons on the dialer, all without the screen but with haptic feedback and audio. Could the graphical side of the main partition just be corrupt, or maybe the display driver is dead but the main board interacts with it differently during fastboot? I'm far from being knowledgeable on the hardware side of these things but I'm really genuinely interested in getting feedback here from anyone with an idea of what is going on. I'll post a video here in a half an hour or so when I finish up with dinner.
AFAinHD said:
...snip...
Click to expand...
Click to collapse
Well... It sounds like there is a short between the screen and the main board. It could have happened when you plugged it into power while parts were still wet causing a short to ground and frying a chip that controls display but not touch on the screen.
Best way I can describe it for you is if an ECU on a car got wet and shorted out. Everything works but you get an engine code for TPS sensor failure due to said short. (The ECU can't read TPS due to a short). That is what seems like what happened.
Uzephi said:
Well... It sounds like there is a short between the screen and the main board. It could have happened when you plugged it into power while parts were still wet causing a short to ground and frying a chip that controls display but not touch on the screen.
Best way I can describe it for you is if an ECU on a car got wet and shorted out. Everything works but you get an engine code for TPS sensor failure due to said short. (The ECU can't read TPS due to a short). That is what seems like what happened.
Click to expand...
Click to collapse
Well see I would think that as well but the screen does work. Just only in fastboot, and the boot logo.
I got the video here.
Fastboot is a pretty low level and most likely uses basic hardware. I mean really what is there to see but a simple background with some text. Once you load the OS then all the hardware and it's drivers into play. Have you tried booting into safemode? Ultimately you'll probably have to repair or replace, but there could be a slim chance that there's still a little moisture in there and it still has a short somewhere.
Okay, so today I bought a Pixel Xl for 30 bucks off a guy on craigslist. He stated in the post that the phone was continuously rebooting and he couldn't fix the issue. He ended up buying a Pixel 4 XL instead of paying to have a repair done. I fix electronics and all that good stuff so I figured it would be a component on the logic board, most likely some failed solder joints or something along those lines. Well before I went and opened it up a I stated realizing that there were times when the phone would boot into android but only if I was holding the device. I thought it was weird and so I kept reading online and someone mentioned heating the back of the phone up would get it to boot and sure enough they were right but inevitably it would reboot again. Well I eventually realized that if I continuously pressed to power button as follows..... 1 press 1 press, wait 1 press 1 press wait the phone would remain on. Thats when I started seeing the lock screen was not activating at all as I pressed each time which it should've done. So I continued to press the button at that same rate of speed for about 2 minutes and eventually the lock screen began responding as it should've.
Long story short, if your Pixel is stuck in a constant reboot then it looks like a possible cause is the pin on the ribbon cable becoming pushed in and held in place by something. Could be dirt and gunk or something that possibly seeped into the button area and is causing the button to remain in a pressed state regardless of any actual pressure being applied to the button that's meant to activate the pressure point on the power cable. So if you're in the same situation try continuously pushing the button in order to free what's ever loved itself in place being the button and eventually the device will stop rebooting. You should also use a tiny bit of rubbing alcohol on a tip and light apply it around the power button to help free up any dirt that's undoubtedly managed to make its way in there.
HOPE THIS HELPS SOMEONE ELSE!!
Loved your solution. It worked like a charm on my pixel 3XL.
Initially while reading the other articles which clearly stated it's a hardware issue and that you need to go to store, or do some factory reset and stuff, it freaked me out. But with more research I was lucky to have come across your article. I'll be honest here, I didn't think it will work. Sounded like a troubleshoot kind of solution which generally aren't so effective, but, conitinuously pushing the button, worked like a charm and my device switched on.
Thanks for saving my device, my repair cost money, my mental peace.
Greetings from India.
This is a light case scenario, because people who are in this kind of situation don't have a issue with the buttons. You would probably be able to define this behavior if the screen immediately blacks out, or you see a blue line across the display (sign of hard reboot). More common cases are the device sticking through the Google > G animation then crashing, which is often the case of failing UFS, more potential in 128gb models, however I've seen and even owned a 32gb model that had this same exact issue.
Ohhhhhhhh thank you so much!! Thought it was a software failure but it kept rebooting when rebooting into fastboot by holding power down. After hitting it hard on the table multiple times it finally stopped rebooting. Very bad hardware by Google.
djared704 said:
This is a light case scenario, because people who are in this kind of situation don't have a issue with the buttons. You would probably be able to define this behavior if the screen immediately blacks out, or you see a blue line across the display (sign of hard reboot). More common cases are the device sticking through the Google > G animation then crashing, which is often the case of failing UFS, more potential in 128gb models, however I've seen and even owned a 32gb model that had this same exact issue.
Click to expand...
Click to collapse
if that were the case, would it not random or bootloop whether in recovery or fastboot?mine does an infinite bootloop but it wont bootloop in stock recovery or fastboot. sometimes it would crash and reboot then spin to a bootloop from twrp. google pixel
I finally figured out a solution for this as well! I sideload the latest Google OTA for an XL and it fixed the stuck bootloop! It was simply a software issue!