Database Info

Wavy/Rollling Lines

I've noticed, particularly on lower brightness (which I do often for battery life reasons) I get a wavy/rolling line that is very visible (see YouTube link below).
Anyone else seeing this or could it be a bad display? Unfortunately, it's very noticeable to me. I came from a Vibrant so I don't think its sensitivity to pentile.
https://www.youtube.com/watch?v=X7HrFRcVNVA&feature=youtube_gdata_player
Sent from my HTC One S using Tapatalk 2.

I think I have a better way to describe this. It seems like a refresh rate issue.
Sent from my HTC One S using Tapatalk 2.

I get this on my Vibrant occasionally, more often if I'm using a non-OEM battery (obviously not your problem), but I'm convinced it's the digitizer dying. Turn it in now for a replacement before you get stuck with a refurb later.
Swyped, not typed, from my Digital Brick

Thanks for the info. Was thinking I was just nuts after no one had replied for a while. Definitely noticeable enough it hurts my eyes after a while. I'll get it replaced tomorrow or Saturday and hopefully that resolves my issue. Otherwise, loving it!
Sent from my HTC One S using Tapatalk 2.

An update in case anyone ends up at this thread because they are having similar issues. It appears this was just a bad display on the phone as I got a replacement and thus far I haven't seen any display issues at all.

had someone exchange their phone with me today for the exact same issue.
unless that was you....ha.

I think that was me.
I came in around 4pm and you were talking to me about yours being a dev phone.

My S have the same problem

DigitalMonk said:
I think that was me.
I came in around 4pm and you were talking to me about yours being a dev phone.
Click to expand...
Click to collapse
I have the same issue with my phone, just unboxed it. I don't have a T-Mobile store in my town, just a stand at the mall, how do I get them to look at this long enough to notice it?

Well, suhailtheboss may be able to answer this better then I since he works at the T-Mobile store I bought mine from...
But, mine was most obvious on greys so I just brought up the grey battery usage graph full screen and they could all see what I was talking about as it was very obvious.
No issues getting it swapped out at all after showing them that and the replacement one has not yet displayed any issues like this.

J_Bot said:
I have the same issue with my phone, just unboxed it. I don't have a T-Mobile store in my town, just a stand at the mall, how do I get them to look at this long enough to notice it?
Click to expand...
Click to collapse
Your best bet is to be able to replicate the issue quickly for the rep, then they should have no issue exchanging it for you.
When I go to work on Thursday I will put a post on our internal site that states this issue, so that it's documented in our system for other all employees to be able to see. As of today this issue was not in the database.
DigitalMonk came in, was very articulate about the problem, and could easily replicate the issue. If he came in and vaguely described the issue without being able to replicate it, most likely we would have not exchanged the phone for him.
(Unfortunately most people who try to exchange phones do so because of user error, assuming that it's the phones fault and not their own. Because of this it is sometimes more difficult to filter the legit exchanges from the unnecessary ones)
Good Luck!

suhailtheboss said:
Your best bet is to be able to replicate the issue quickly for the rep, then they should have no issue exchanging it for you.
When I go to work on Thursday I will put a post on our internal site that states this issue, so that it's documented in our system for other all employees to be able to see. As of today this issue was not in the database.
DigitalMonk came in, was very articulate about the problem, and could easily replicate the issue. If he came in and vaguely described the issue without being able to replicate it, most likely we would have not exchanged the phone for him.
(Unfortunately most people who try to exchange phones do so because of user error, assuming that it's the phones fault and not their own. Because of this it is sometimes more difficult to filter the legit exchanges from the unnecessary ones)
Good Luck!
Click to expand...
Click to collapse
Thanks, I appreciate that. I "tested" my screen on my non-techy roommate and they can see the flicker also...so we will see.

Sounds exactly like what I encountered with my phone. It was obvious to a couple of non-techy co-workers. Zero problems so far with the replacement.
Sent from my HTC One S

suhailtheboss said:
Your best bet is to be able to replicate the issue quickly for the rep, then they should have no issue exchanging it for you.
When I go to work on Thursday I will put a post on our internal site that states this issue, so that it's documented in our system for other all employees to be able to see. As of today this issue was not in the database.
DigitalMonk came in, was very articulate about the problem, and could easily replicate the issue. If he came in and vaguely described the issue without being able to replicate it, most likely we would have not exchanged the phone for him.
(Unfortunately most people who try to exchange phones do so because of user error, assuming that it's the phones fault and not their own. Because of this it is sometimes more difficult to filter the legit exchanges from the unnecessary ones)
Good Luck!
Click to expand...
Click to collapse
Be on the look out... After unlocking / flashing / rooting (not exactly sure when, in the middle of this process, I noticed this), my phone began a flickering in a very different manner.
The entire screen would flicker into a variably brief, yellow tint. First noticed it when using the notification bar.
I hoped it was soft, and not hard, issue -- so I immediately rebooted after seeing it a handful of times in near rapid succession, and haven't seen it since. I'm curious to hear whether this has happened to anyone else, and if so, whether their phone has been modified in any way.

majalo said:
Be on the look out... After unlocking / flashing / rooting (not exactly sure when, in the middle of this process, I noticed this), my phone began a flickering in a very different manner.
The entire screen would flicker into a variably brief, yellow tint. First noticed it when using the notification bar.
I hoped it was soft, and not hard, issue -- so I immediately rebooted after seeing it a handful of times in near rapid succession, and haven't seen it since. I'm curious to hear whether this has happened to anyone else, and if so, whether their phone has been modified in any way.
Click to expand...
Click to collapse
Mine is not modified. I am sending back mine today to get it fixed/exchanged.

Just returned one for the blinking, now i am seeing this error! My local tmobile is going to hate me by the time im done. LOL

My first One S with wavy/rolling lines as described in first post was approved as DOA.
I have now a new One S and it don't have the same problem

Rotating fails :( Only at my device?

I made a video, here is the link:
http://youtu.be/_4KC8wnc_zE?t=23s
It won't rotate correctly, I already tried several apps for setting the wallpaper, but no one worked
This seriously looks sh**
Is it only my device that has this problem?
Greetings

What do you mean it fails? It looks exactly just as it should. I have audio off, so if you said something crucial there, can you repeat it here.
I don't see anything worrying apart from a slight lag, but this may be your camera.
Edit: Sorry, after looking at it for the second time and in the full-screen mode now, I can see what you mean - there's a black bar that gets updated later. It certainly shouldn't be this way. I had similar issues with pdf rendering in the power-saving mode. What settings are you on?

d14b0ll0s said:
What do you mean it fails? It looks exactly just as it should. I have audio off, so if you said something crucial there, can you repeat it here.
I don't see anything worrying apart from a slight lag, but this may be your camera.
Click to expand...
Click to collapse
I dont have mine yet, but compared to my wife's ipad2, with whats in the video, it seems there is a lot of lag?
Shouldnt that thing turn almost a second after you have turned it?

It can take like 2 or 3. It seems slower than iPad, but also have in mind that iPad uses the animation that lasts about a second itself. Anyway, should be faster, I agree, although I think it's only a little worse on this video than what I normally experience, so if there's a speed issue, it's not rotation issue, but a general one. Try different power modes and be sure to update to .26 firmware.
Edit: Sorry, after looking at it for the second time and in the full-screen mode now, I can see what you mean - there's a black bar that gets updated later. It certainly shouldn't be this way. I had similar issues with pdf rendering in the power-saving mode. What settings are you on?
The thing about wallpaper misguided me a bit though.

lardo5150 said:
I dont have mine yet, but compared to my wife's ipad2, with whats in the video, it seems there is a lot of lag?
Shouldnt that thing turn almost a second after you have turned it?
Click to expand...
Click to collapse
No, that is not "real" lag, it has been included to make sure you really want to turn it to landscape for example (as far as I know).
On my galaxy nexus with 4.1 the lag seems to have gone, seems to me like they disabled it there.
So just wait for 4.1 if you don't like the "lag".
But thats not the point. d14b0ll0s, you correctly recognized the black bar, and the picture itself seems to zoom in and out sometimes, aligning itself to the left, to the right and then in the center.
But I don't know what to do, is that definitely not the case on your device? Am I really the only one?
In that case I have to hardreset it

Not only do hard reset, but - what's more important - try re-flashing firmware (you can actually start with it). If the problem remains, return the device. I'm definitely not getting anything like that.
Use Titanium Backup or MyBackup if you have something you don't want to lose and copy the files to your PC.

Problem solved
You'd never guess what caused the problem:
_Wallpaper Wizardrii_
Deleted that and it's gone

paysen said:
Problem solved
You'd never guess what caused the problem:
_Wallpaper Wizardrii_
Deleted that and it's gone
Click to expand...
Click to collapse
Geeze, of all things
Nice job man.

Glad it's solved, but you should've mentioned you're using apps changing your desktop / wallpaper behaviour in any way.
BTW, I knew there was a reason not to like this app in the first place

lardo5150 said:
Geeze, of all things
Nice job man.
Click to expand...
Click to collapse
Luckily I haven't done a hard reset before recognizing the sh***y impact of the app
d14b0ll0s said:
Glad it's solved, but you should've mentioned you're using apps changing your desktop / wallpaper behaviour in any way.
BTW, I knew there was a reason not to like this app in the first place
Click to expand...
Click to collapse
I really should have mentioned this, but forgot it. And it's on the 2nd site of my app-launcher, just started it one time ;D

[RANT] - Lollipop is not great, but tolerable

I was very excited to see this:
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
So, I pushed ahead thinking that Lollipop has already been in the wild long enough, surely the initial kinks like WiFi drops and battery hogging have been resolved. No such luck, and after doing it, it looks like I'm going to have to do this:
http://forum.xda-developers.com/showthread.php?t=2784880
Lollipop is horrible. My phone no longer does one of the most basic things that's been around since the G1: Go (the F) to sleep! Seriously?!?!
Here are my other problems:
-Phone doesn't sleep on its own if timeout set for longer than 30 seconds (and even then, it's not reliable)
-WiFi doesn't reconnect after sleep (when sleep even happens, which is only when I push the button to force it). I have to toggle WiFi off/on to reconnect.
-Battery drain is pretty bad. My first month with the S5 had me barely even thinking about charging. Now, with Lollipop, I feel like I'm back on my old HTC MyTouch!
-The silly way they implemented the lockscreen. Here's my problem: I can ONLY use Settings > Sound and Notification > While locked with the option "Do not show notifications". Why? Any other setting blocks the Owner Information (Settings > Lock screen > Owner Information). If I don't, and if I'm unfortunate enough to have lost my phone, yet fortunate enough to have it found by a good samaritan, I better hope I haven't miss any calls or received any messages in the meantime. This one REALLY GRINDS MY GEARS because it's a horribly-implemented Feature ... at least the others are unintended bugs, but somebody had to give this one the green light.
-I can't adjust the icon sizes anymore. There used to be a choice of large or small icons.
-Oh, and for some bonehead reason, Samsung decided their stock ROM wouldn't have the Lollipop built-in flashlight icon.
-Another intentional feature that I can't disable: the phone keeps a history of recent activity that persists through reboots. YUCK! Why can I not disable this?!?! Again, another bonehead call that somebody had to green-light, without even considering the possibility that I might want to turn it off!
-All the UI "polishing" and improvements don't mean a thing to me, I want it to work.
I found all of the above in less than 24 hours on Lollipop! I might lose my s**t entirely if I keep it for much longer.
Here is my take on why:
Google and Apple are in a heated race to the top. They wrongly assume that what will set each apart from one another is almost entirely dependent on what a few bloggers say about some hot new feature. The paradigm appears to be something like: "Who cares if millions of loyal subscribers lose functionality when we want 100 people to have this one obscure and half-baked feature?"
Latest != Greatest
-----
EDIT:
I've had a change of heart on this. It's not too bad, I just needed to adjust a few settings and live with the other issues.

I too do not like the lolli. Bad battery life, and for some reason the Heart rate monitor led turns on whenever anything is within a half inch of it. I just can't figure that out, but it sucks the battery like a red led vampire!
Sent from my SM-G900V using XDA Premium HD app

Tldnr
Don't start a thread just to complain

Lmfao when I saw that link and clicked it, I actually had that same thread opened moments before opening this thread because I, too, am having to go back to KitKat. I laughed for a good 20 seconds. Lollipop is freaking terrible at the moment. Zero customization and Google + Samsung are forcing too much garbage on us without giving any bit of customization.

mygraine said:
I too do not like the lolli. Bad battery life, and for some reason the Heart rate monitor led turns on whenever anything is within a half inch of it. I just can't figure that out, but it sucks the battery like a red led vampire!
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Heart rate monitor thing was fixed in OC4 I think, but if it still goes off a factory reset will fix it.

Agree
OP, I agree with you. It probably is the first version without the definitely improvement overall for users. It is risky to upgrade and troublesome if it didn't work out well on your devices. Wish Android 5.1 could be better than Kitkat overall.

I have absolutely no problems with the lollipop. I always had it stock from the start and just let the OTAs take over on their own. Have you tried even rebooting into recovery and wipe cache? Even though it's not a custom recovery you can still do that, also even when you dirty flash nightlies that's something that's good practice. My wife's phone had similar issues that I wasn't experiencing, until I did that to her phone and now she's having no problems. Now the general annoyances of how Samsung implemented ****, I understand, it's stupid with not having native flashlight, tethering is annoying having to use foxfi, and the lockscreen.. bleh. But other than that, everything is actually working like it is supposed to

Chiming in, Yes it's bad.
I have two lines with Verizon, both with S5 phones on them. Great device, its actually the first Android phone I've had that I did not do anything with beyond the out of the box experience. That changed when Lollipop was pushed via OTA, the most prominent issue I experienced on both of my S5s is general responsiveness issues, simple things like switching apps or launching apps sometimes would leave me with a white screen for between 5-10 seconds, an eternity especially when the device was lighting fast on 4.4.4 Kitkat. I followed every suggestion from wiping the device in Android, Wiping in recovery, wiping cache, all of these with only marginal improvements. It really is a shame that Google / Samsung did not do a bit better quality assurance on this build before it was pushed out to carriers and ultimately peoples devices. It says something that other carriers skipped 5.0 and that very rapidly 5.1 surfaced on Newer devices / Nexus devices.
As of last night both of my phones are Odin'd back to 4.4.4 and its like having a brand new phone. Sure, there might not be as much polish, but there are no features I will die without having. The only one that I can say I do miss is the feature where the device will disable the lock screen when your smart watch or home WiFi is connected.
Here's to hoping that Google eventually gets Android 5 right in the optimization department and that Samsung picks it up for the S5, and that Verizon gets it ready for OTA before I am ready to move on to a new device. Not interested in the S6 at all for its sealed nature for storage and battery, but that's for another thread on a different day.
-Nate

I Have to agree. I've given it several chances to perform to expectations but it just fails.... ( insert sad puppy face here ) no matter what I have tried it just under-performs and the biggest thing is the horrible battery life. Sooooo yeah like most of the other commentators in this thread, I'm moving back to 4.4.4......

Unfortunately/fortunately, I have found most of my battery issues were solved with a factory reset. I'm more frustrated that Samsung seems to having issues with Android Auto.

ldeveraux said:
Tldnr
Don't start a thread just to complain
Click to expand...
Click to collapse
Observations, not complaints. Getting these points out in the open is an essential stepping stone to getting them fixed. Maybe, just maybe, a Producteer or architect at Google has read this by now so they know what to improve next time. Problems cannot be solved until they are defined.
---
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.

CaptainRewind said:
Observations, not complaints. Getting these points out in the open is an essential stepping stone to getting them fixed. Maybe, just maybe, a Producteer or architect at Google has read this by now so they know what to improve next time. Problems cannot be solved until they are defined.
---
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
Click to expand...
Click to collapse
Yeah, go start a petition, just like the bootloader guys, see how far it got them? No one from google reads your complaint threads and regrets their work...

ldeveraux said:
Yeah, go start a petition, just like the bootloader guys, see how far it got them? No one from google reads your complaint threads and regrets their work...
Click to expand...
Click to collapse
Yeah, I guess that was wishful thinking.
In any case, it seems this thread was a complete waste of time. It made me feel better at the time, but looking back on it and the purpose of this site, it doesn't add any value or help anyone modify their phone. Not only that, one of my primary reasons for the OP was the screen lock issues which turned out to be an app, not the Android version.
So, I stand corrected. Live and learn. Enough said.

My wife would never let me root her phone ever. After this update either I find a way to go back a few with root or it goes against the wall. Looks like I have to start reading and figure out how to do this.

Lol I love how you described it. Sometimes you have to vent. Lol

CaptainRewind said:
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
Click to expand...
Click to collapse
Care to share where this app is?
Sent from my SM-G900V using XDA Free mobile app

dk-v1 said:
Care to share where this app is?
Click to expand...
Click to collapse
This is the one:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
It's a great app, but something about it staying active in the Notification Bar keeps the screen awake. I still use the app, just can't keep the notification active in Lollipop.
And in case it isn't obvious, even though I still have my concerns about Lollipop, I never did go about the procedure of downgrading. It looks like a risky procedure, and I don't want to trip Knox, or worse, have a brick.

CaptainRewind said:
This is the one:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
It's a great app, but something about it staying active in the Notification Bar keeps the screen awake. I still use the app, just can't keep the notification active in Lollipop.
And in case it isn't obvious, even though I still have my concerns about Lollipop, I never did go about the procedure of downgrading. It looks like a risky procedure, and I don't want to trip Knox, or worse, have a brick.
Click to expand...
Click to collapse
Ok, so it's not a stock app. I am still having poor battery life and overheating issues.
Sent from my SM-G900V using XDA Free mobile app

Phone getting slow after some time

My phone is dropping the framerate on touching the screen occasionally, stuttering for a short time. It is fine again after rebooting, but I am facing this problem since I got the phone three weeks ago. Does anyone else experience this? Is there a solution? I am worried this could be a hardware defect.

Try to reinstall the ROM. You can install full ROM without losing data. If that doesn't help, try a clean install.

Yes I see it too. In fact I started a thread on this in Q&A section but nobody seems to be interested
Nothing I seem to do in terms of tweaking the performance parameters seems to help. It can be fine for half an hour and then out of nowhere a few frames are dropped and it looks awful
It's ok 98% of the time but those 2% are making it hard for me to love this phone.

Lownita said:
My phone is dropping the framerate on touching the screen occasionally, stuttering for a short time. It is fine again after rebooting, but I am facing this problem since I got the phone three weeks ago. Does anyone else experience this? Is there a solution? I am worried this could be a hardware defect.
Click to expand...
Click to collapse
It sounds like a rogue app is taking control of your phone. I checked your Profile GPU rendering screenshot against mine, and indeed, mine never goes much higher above one-half length of the green line, which I think may be the 120fps limit (the green line itself is 16ms or 60fps.)
Seems to me that you need to uninstall some custom/rare apps to troubleshoot this issue.
It is definitely not normal behavior.

carlos67 said:
Yes I see it too. In fact I started a thread on this in Q&A section but nobody seems to be interested
Nothing I seem to do in terms of tweaking the performance parameters seems to help. It can be fine for half an hour and then out of nowhere a few frames are dropped and it looks awful
It's ok 98% of the time but those 2% are making it hard for me to love this phone.
Click to expand...
Click to collapse
So my guess is that either people don't notice it, but I think that's quite impossible as even some kernel devs told me they wouldn't experience this. Or it's a fault in oos itself. Or we are using an app or some setting that's causing this. Or it's a kind of defect, which I think is unlikely but not impossible.
I am about to reset the phone completely to stock with msm download tool and start from scratch. Have you already done something similar?
Next idea would be flashing Omni ROM as I believe this is one of the most clean and fluid custom roms. If all of this fails, I would start to believe it's a hardware problem.

Lownita said:
I am about to reset the phone completely to stock with msm download tool and start from scratch. Have you already done something similar?
Click to expand...
Click to collapse
I would suggest you learn adb/ fastboot to do this so you learn to know what, how and why you doing this and that.
Not really difficult but extremly helpful if you face problems.

The large amount of applications and internet uses it may slow. Better cleared all caches and it's working properly.

Question Screen weirdness on me the other day.

My pixel 7 pro freaked out on me the other day and went black on me when I played a game and didn't come back for over 15 minutes then finally was responding again. Any reason why this happened . Hopefully software and not hardware. Hasn't happened since but still concerning .

Anyone ?

Redbeardkevv said:
Anyone ?
Click to expand...
Click to collapse
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.

jaseman said:
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.
Click to expand...
Click to collapse
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.

EtherealRemnant said:
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.
Click to expand...
Click to collapse
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?

Hmmm

jaseman said:
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?
Click to expand...
Click to collapse
That's called a hardware defect if the hardware can't cope. Going blank for 15 minutes is not normal.

Hardware hmm and not software?

Redbeardkevv said:
Hardware hmm and not software?
Click to expand...
Click to collapse
What were you playing? If it was a graphically intensive game, I would definitely lean more towards blaming the hardware. It's very rare that a game can actually make a phone that unstable. In fact I can't remember the last time I've had a game make my phone unresponsive.

Roblox with my nephew

Redbeardkevv said:
Roblox with my nephew
Click to expand...
Click to collapse
I've never played that game but their site seems to suggest some rather low requirements so I would be shocked if an ARMv8 processor like Tensor 2 is going to struggle with it.
Android warning screens
Due to the very large number of Android devices in existence, we cannot be certain that all devices will run optimally even if they are running the correct version of the operating system and do not have a Tegra 2 chipset.
We have 2 levels of unsupported Android devices - skippable and unskippable:
Skippable Devices: These types of devices will get a warning telling you that your device may not be powerful enough to play experiences smoothly. This is just a warning to let you know that while your device isn't specifically supported, experiences might still run though they will likely lag a little (or a lot). Tapping outside the warning box will make it go away and the experience should keep loading.
Unskippable Devices: will get a message that informs you that your device doesn't meet the minimum system requirements. This means the device is not able to play experiences on Roblox. This message usually shows up on devices that use the Tegra 2 graphics chipset or a processor older than ARMv7. These kinds of tablets/phones do not support features that the Roblox needs to be able to function. However, users with these unskippable messages will still be able to access all other parts of the app outside of experiences.
Click to expand...
Click to collapse
https://en.help.roblox.com/hc/en-us/articles/203625474-ROBLOX-Mobile-System-Requirements

Yea I was thinking it had low requirements. Maybe bad coding ??? But then again no other app or game has caused that to happen. Sooo. Yea

I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
I've had a few wonky screen issues that hard locked my phone. Had one go black, but fortunately came back after holding power down. It once went all yellow with weird shapes/sections. And then just had some freezes with artifacts on the screen.
I'm going away for the holidays so I'll send it back when I get home if I'm still having issues. If you're going away, I'd suggest taking a backup phone just in case. Had mine die the first time when I was visiting my folks out of state. It sucked with no backup.
One thing I noticed is the screen does a fuzzy flash whenever I plug in a USB charger. It's only a split second but it is noticeable. Has anyone else experienced that?

Superguy said:
I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
Click to expand...
Click to collapse
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.

V0latyle said:
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.
Click to expand...
Click to collapse
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev

Superguy said:
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
Click to expand...
Click to collapse
Yeah, that's definitely a display issue. I'm talking about when the device doesn't work or respond at all, maybe vibrates on power up but doesn't respond to anything, and usually will come up as "Qualcomm Bulk USB" or something when connected to PC
Superguy said:
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev
Click to expand...
Click to collapse
For sure, active development may or may not have stability issues, it's all a learning process!