Question Screen weirdness on me the other day. - Google Pixel 7 Pro

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!

Related

[Q] Why is every unit different?

With EVERYTHING android (at least here) it seems like, "Well this may or may not work for you, because everyone's device is different" "It works for me just fine!! (but then you try and doesn't work, or vica-versa)
What about the devices in the Same chain, is different enough to break software so easily, as opposed to something like.. linux desktop or windows, where almost everything that works for one person works for all.
Is it just poor quality control? do they change hardware everytime a new B* series is released?
Just my two cents and pondering.
At least 50% of the time the person who it does not work for has done something wrong or does not have the right prerequisits on their device.
Other than that all chips are slightly different and have different faults that would not show up in normal use but here where the devices are pushed to the limit those flaws come out.
And the thing about the different devices is that asus changed the secure boot key in the B70-80's making some things not work. And the 101g has different hardware causing even further problems
No 2 microchips are the same. One might be able to handle higher voltage than the other, while the other might be able to handle higher frequency than the first etc etc.
So from what I take it's nearly impossible to get 2 CPU chips exactly the same, plus different bootkeys and hardware plus user error = Different experience.
Where I take this from is, when on HC my tf was disasterous, never held a charge through sleep, randomly froze, rebooted, deleted things.. Etc.. When I got ICS update. Blam! Fixed everything, but everyone else seems to have had everything broken.
Thing O Doom said:
When I got ICS update. Blam! Fixed everything, but everyone else seems to have had everything broken.
Click to expand...
Click to collapse
Considered yourself lucky...
Perhaps you have the perfect match between hardware and software(ICS)..
Love made in heaven..
Truly Truly. Can anyone else report that ICS Fixed anything?
Well, everything is slightly smoother, and netflix doesn't lag anymore for me..
but my transformer has always kicked ass compared to the transformers reported here.. (except for the ****ty speaker which i normally don't use anyway).
asdfuogh said:
but my transformer has always kicked ass compared to the transformers reported here..
Click to expand...
Click to collapse
What B# series do you have, mabye there's a sort of connection. I have a B70 Tablet and it's screamin good.

Possible input lag/ Ghost Touches once again

A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.
I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.
hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again
What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.
ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.
Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.
hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x
I have the same frustrating issue
Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)
I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.
This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.
I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...
HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!
The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version

Nexus 5, Experiencing Random Reboots across ROMS. Last_KMSG Will donate $5 to EFF

Hey everyone! My Nexus 5 is experiencing random reboots and does so regardless of which rom I have installed. I started by pulling logcats and didn't find anything interesting (not an expert though), so I moved on to pulling the last_kmsg and saving it to a txt file. It says the reason for the last reboot was "kernel panic," but I assume there is more to it. There has to be a message in there explaining what caused it, but to be honest, I'm not really knowledgeable enough to pull it out of what looks like 50% gibberish to me.
http://pastebin.com/315jSBZt
I would be more than happy to provide needed logs or run tests, just let me know what you need. If someone can give me a good answer that is corroborated by someone else in the community, I'll make a $5 donation to the EFF in your honor.
Possible power button issue?
audit13 said:
Possible power button issue?
Click to expand...
Click to collapse
Unlikely. Power button feels good and this phone hasn't really even been used very much. If it's a hardware issue, I think we'll find a clue in the logs. Kernels shouldn't just panic of their own accord, right?
I looked at the log you posted and I do see a kernel panic on the last line.
Does this happen with a stock ROM too?
audit13 said:
I looked at the log you posted and I do see a kernel panic on the last line.
Does this happen with a stock ROM too?
Click to expand...
Click to collapse
Yes, I've experienced this problem on the stock ROM, Cataclysm, and Chroma (what I'm using now).
Some observations that might help:
- Sometimes it reboots more frequently than others. I've had it reboot several times within 10 min. I've also say in front of my computer with logcat running, purposefully trying to make it crash, and for 30min. it didn't do anything. (I got it to eventually, but didn't find anything useful)
- I recently reflashed everything to stock including the bootloader and recovery to see if it would help. I also updated the radio to see if that would do anything.
- It boots up fairly quickly. There are no real performance issues while using the phone
- Before it crashes, it freezes for a few seconds with whatever is on the screen. You can't use any of the buttons or do anything.
- It does not require screen-on or user interaction to prompt a reboot. I've had it reboot while sleeping before and I can hear it vibrate when it hits the "google" screen.
Is there any way to identify the cause of a kernel panic? I assume that the kernel logs what it does or what it's trying to do somewhere. I'd love to be able to pull some intel out of the logs to figure out exactly what's causing it. Any other logs I should be pulling?
Sorry, this is way beyond my analytical skills. You've gone a lot further than I would.
Could the reboots be an indication that the on-board memory is starting to fail? I'm not sure.
audit13 said:
Sorry, this is way beyond my analytical skills. You've gone a lot further than I would.
Could the reboots be an indication that the on-board memory is starting to fail? I'm not sure.
Click to expand...
Click to collapse
Good call. That was one of my possible guesses too. I keep looking for evidence of that in the logs, it's gotta leave a trace somewhere! The phone is "certified refurbished" one that I bought off Amazon fairly cheap ($160-180ish). I think I'm just going to flash it back to stock and return it. Not sure what I want to get as a replacement. I might be able to beat my old Moto G (original) back into submission and use it for a while. It had some problems too, and it was worse when it comes to specs, but it was a really well thought out put together device. Never noticed the little things mattered so much until I bought my Nexus 5. I love it, don't get me wrong, but the positioning of the speaker, the slow-focusing camera, and a few other things keep it from hitting 100% for me. It's odd that two phones from the same manufacturer could be so different feeling when it comes to polish. Maybe I should buy a Moto X just so I can experience them all!
I used to have a Moto g as well. It as a great phone until I damaged the sim reader.
Although Google used to own Motorola, the nexus was made by LG which probably explains the different approaches to building a phone.
I'm okay with my lg which is a frankenphone that I clobbered together using spare parts I salvaged from cheap used nexus 5 phones I bought over a period of a few weeks.

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 Horizontal line flashing @ top ⅓ of screen when changing apps

Hi, I have a p7p. I've got the animations turned off. I'm NOT using the smooth display. When I do use the smooth display this issue seems to go away. Perhaps it's because my eye doesn't perceive the flash at the higher frequency. The flash most often seems to occur when I'm typing on the Gboard. It's like a glitch ⅓ of the way do the screen and is just a line that flashes across the entire width of the screen. Is there some way to test this? I see mention of "display checker" apps on this forum sometimes.
I am wondering if I have to RMA the phone. The flash is just a line and is for a split second, but I don't like it having paid $1000 for this phone. I don't want it to get worse after the phone is out of warranty. That's what really bugs me. If I let this go and it grows into a screen failure or something I'll be kicking myself in the butt if it fails after the warranty is expired. What even is the warranty on these phones?! I have the 512GB storage version from Google
The standard warranty is 1 year; this may be dependent on your locale.
I have yet to understand why people tend to take to the Internet to complain about problems with a device that they can get fixed for free. Not flaming anyone here, but if you're worried about the longevity of your device and whether a problem may get worse in the future, why wouldn't you just take advantage of the warranty you have?
V0latyle said:
The standard warranty is 1 year; this may be dependent on your locale.
I have yet to understand why people tend to take to the Internet to complain about problems with a device that they can get fixed for free. Not flaming anyone here, but if you're worried about the longevity of your device and whether a problem may get worse in the future, why wouldn't you just take advantage of the warranty you have?
Click to expand...
Click to collapse
Not complaining. Asking if anyone else has it. Sometimes these things are known hardware issues and if it was i have no problem starting a RMA. I was just seeing if anyone else experienced this.
Schroeder09 said:
Not complaining. Asking if anyone else has it. Sometimes these things are known hardware issues and if it was i have no problem starting a RMA. I was just seeing if anyone else experienced this.
Click to expand...
Click to collapse
It most likely is a hardware issue. If it's not happening in a specific app, and you don't have any of the display debug options enabled in Developer Options, it's probably a GPU issue.
Thanks for the help.
try disabling animation, in case it's glitching
what i notice is this phone has that animation during app switching, and other thing, which on some ocassion, doesnt really suit my taste for visual stuff, bit awkward for the eye.
otonieru said:
try disabling animation, in case it's glitching
what i notice is this phone has that animation during app switching, and other thing, which on some ocassion, doesnt really suit my taste for visual stuff, bit awkward for the eye.
Click to expand...
Click to collapse
I have animations off. I thought you hat might be part of the issue too and is why I mentioned it. With animations off a large app icon (for whatever is being switched from) momentarily pops up on the screen.
Schroeder09 said:
I have animations off. I thought you hat might be part of the issue too and is why I mentioned it. With animations off a large app icon (for whatever is being switched from) momentarily pops up on the screen.
Click to expand...
Click to collapse
in my case, it was first app in app drawer (the app doesnt need to be running for it to happen) that will pop up during animation. I think this might be launcher bugs as well.
i stop seeing it after switching to nova btw
Should Google be repairing or replacing for this? I was hoping they'd just swap me a new phone. I don't want em tearing this apart and giving it back to me. What have they been doing for everyone else?
Dude you may have a lemon. In all my years on XDA, I have never seen someone start this many threads for a single phone.
schmeggy929 said:
Dude you may have a lemon. In all my years on XDA, I have never seen someone start this many threads for a single phone.
Click to expand...
Click to collapse
One thread? I've started one thread for suspected hardware issue.

Categories

Resources