Database Info

[Q] Touch+display dead

The display stopped working 2-3 days ago. On booting i can see the google logo for 2-3 seconds before the screen goes dark. The phone works and i can hear dings of messages, but i cant access any of it. Once i kept shut it for a day i was able to see the screen for 10-15 seconds( i used this window to remove the screen lock so that i can use the usb transfer ). Now keeping the phone shut for long duration has no effect.
I can see the fastboot screen but not the recovery screen throught it.
I also bought a slimport so that i could see the screen on my pc. It works (not for the fastboot or recovery), however the touch doesn't work and the volume and power buttons response is too sluggish. I can connect the mouse but it is of no use as i can't see the screen on PC and use the mouse at the same time. I tried adb ( i have no experience of it ) but i cant touch the allow pernmissions key on the screen for the above reasons. Also what advantage would adb be in this case?.
Any advice ?
PS: i have cyanogenmod

I think ram is your only option. It definitely sounds like it's hardware and not software related.
Sent from my Nexus 5 using XDA Free mobile app

Sorry, i don't follow. U mean a ram replacement is needed ?
jd1639 said:
I think ram is your only option. It definitely sounds like it's hardware and not software related.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse

nexmus said:
Sorry, i don't follow. U mean a ram replacement is needed ?
Click to expand...
Click to collapse
It was a typo.. He meant RMA
- Sent from an IceCold Hammerhead!

Oh, you mean sending it to LG for servicing? I am a bit hesitant since i have cyanogenmod and also am in india and i doubt they will give a replacement. I think going back to stock rom and then sending it for repairs might help but i have no idea how to go about doing that in this situation.
vin4yak said:
It was a typo.. He meant RMA
Click to expand...
Click to collapse

nexmus said:
Oh, you mean sending it to LG for servicing? I am a bit hesitant since i have cyanogenmod and also am in india and i doubt they will give a replacement. I think going back to stock rom and then sending it for repairs might help but i have no idea how to go about doing that in this situation.
Click to expand...
Click to collapse
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature

How can i do it using fastboot ?
rootSU said:
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
Click to expand...
Click to collapse

nexmus said:
How can i do it using fastboot ?
Click to expand...
Click to collapse
I do t understand the question. Is this question one you're asking having already read the fastboot return to stock guide?

Same issue I had pretty much, it died about 2 months ago. I was still able to copy all of my files, phone worked perfectly but the screen was black. Had it replaced it no time. Is that by any mean a 311k? I've seen another thread like that pop up lately.

vnvman said:
Same issue I had pretty much, it died about 2 months ago. I was still able to copy all of my files, phone worked perfectly but the screen was black. Had it replaced it no time. Is that by any mean a 311k? I've seen another thread like that pop up lately.
Click to expand...
Click to collapse
What does the month it was made have to do with anything?

rootSU said:
What does the month it was made have to do with anything?
Click to expand...
Click to collapse
I don't know yet, I'm just trying to figure out whether it's a particular batch that started failing or it's completely random, just curious. The two replacements I was sent were 403K. Build is perfect, but they both had some light bleed issues. Looks like every batch comes with some good and some bad, QC definitely hasn't been too great on this phone.

vnvman said:
I don't know yet, I'm just trying to figure out whether it's a particular batch that started failing or it's completely random, just curious. The two replacements I was sent were 403K. Build is perfect, but they both had some light bleed issues. Looks like every batch comes with some good and some bad, QC definitely hasn't been too great on this phone.
Click to expand...
Click to collapse
They're not really built in batches. Manufacturing was continuous. They just changed the serial number every time the month changes so I dont think this would actually mean anything

I know but I'd still use it as a milestone more than anything, I mean there have been some differences in the units (eg bigger speaker holes), this way it's easier to track them along the timeline, because they definitely do change something in the manufacturing process from time to time if they have to make up for issues or something. They also did it with the N4 if I remember well.

vnvman said:
I know but I'd still use it as a milestone more than anything, I mean there have been some differences in the units (eg bigger speaker holes), this way it's easier to track them along the timeline, because they definitely do change something in the manufacturing process from time to time if they have to make up for issues or something. They also did it with the N4 if I remember well.
Click to expand...
Click to collapse
Speaker holes is a bad example because even the latest built devices it was still a lottery whether you got bigger or smaller holes. That's down to what you mentioned earlier, QC

rootSU said:
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
Click to expand...
Click to collapse
I was able to unroot and flash the stock image. The problem still exists though, so it has to be a hardware issue. Fortunately the phone is still in warranty.
Thanks for all the support.

Impromptu update?

10.0.0 (QP1A.190711.020.C3, Sep 2019)
Seems like it was posted today..
Anyone flash it or know what it's for?
https://developers.google.com/android/images

Perhaps a fix for sensor issue?

I'd flash and see but ugh.. I have my phone set up perfectly including Google Pay.. May still do it, I'm sick like that!

i know right i didn't wanna flash it since we are a week away from the October build but will there even be an october build now?

masri1987 said:
i know right i didn't wanna flash it since we are a week away from the October build but will there even be an october build now?
Click to expand...
Click to collapse
Pretty sure there will be. The C3 indicates it's a hotfix release so that shouldn't impact the normal schedule.

So....did anyone flash it yet? Lol

Got it via OTA toda, 1335 MB on C3.
haven't seen anything different, lol.

Can confirm that this build has fixed the swipe up issue for unlocking not working properly - but still suffering from the screen goes blank when on a call (to ear) and then does not turn on again when viewed unless various buttons pressed!.

Got a new update as well

I got it this morning. I have not noticed anything new.

jimjamyaha said:
Can confirm that this build has fixed the swipe up issue for unlocking not working properly - but still suffering from the screen goes blank when on a call (to ear) and then does not turn on again when viewed unless various buttons pressed!.
Click to expand...
Click to collapse
I have that issue, and I'm still on 9.0.

I was chatting with the Pixel team yesterday about something unrelated and was trying to get any info about the C3 update. Instead, I got very evasive runaround about how there is no approved communication. He didn't act like he didn't know what I was talking about but just wanted to change the subject since he wasn't going to say what the "hotfix" was for. I guess this their new strategy after still not disclosing the difference between .19 and .20.

sliding_billy said:
I was chatting with the Pixel team yesterday about something unrelated and was trying to get any info about the C3 update. Instead, I got very evasive runaround about how there is no approved communication. He didn't act like he didn't know what I was talking about but just wanted to change the subject since he wasn't going to say what the "hotfix" was for. I guess this their new strategy after still not disclosing the difference between .19 and .20.
Click to expand...
Click to collapse
Yeah, they used to be very up front with what the differences are in the builds. Usually they were carrier specific. If I had to guess, this new update fixed some huge security issue that they needed to fix ASAP before the bad guys could take over our phones.

jmartin72 said:
Yeah, they used to be very up front with what the differences are in the builds. Usually they were carrier specific. If I had to guess, this new update fixed some huge security issue that they needed to fix ASAP before the bad guys could take over our phones.
Click to expand...
Click to collapse
Just take the OTA like good "sheeple." Don't worry about when it will get there, and of course you'd never need to root and block all of those glorious ads.

I flashes this new release yesterday and I may say it is big...I'm still going deep into what's new but haven't found anything relevant yet.

mgp53 said:
I have that issue, and I'm still on 9.0.
Click to expand...
Click to collapse
Is that the issue of swiping, or the proximity sensor info not causing the screen to reactive during a call?

jimjamyaha said:
Is that the issue of swiping, or the proximity sensor info not causing the screen to reactive during a call?
Click to expand...
Click to collapse
Proximity.. I wish that while on a call, no other involuntary touch action could activated... Until hanging up or pressing a deliberate action.

Apparently a hotfix for the sensor bug went out 5.5MB for other pixels... (see the stickied sensor bug thread) Makes you wonder if someone made an oopsie in our case?

I noticed my phone a little bit colder after this update.

It's a pretty big update! It's the same size as the official Android 10 image. Weird.
Any of the 10 features that we haven't gotten yet in there? Like the customization app or whatever? New AOD clocks? I can't remember what all else we were supposed to get. I don't have time today to check it myself.

Android 11 October Update is out

Has someone already upgraded and could perhaps share his patched magisk file?
Btw: It seems the random crashes/blackscreen ploblems that plagued alot of people here, including me, were at least to some degree Googles own fault (screenshot).

No fix for face unlock "clean the top of your screen, including the black bar"?

Morgrain said:
Has someone already upgraded and could perhaps share his patched magisk file?
Btw: It seems the random crashes/blackscreen ploblems that plagued alot of people here, including me, were at least to some degree Googles own fault (screenshot).
Click to expand...
Click to collapse
You don't need to upgrade to create a magisk_patched.img
Edit: You can grab it here - https://rb.gy/0wijwp

Morgrain said:
Has someone already upgraded and could perhaps share his patched magisk file?
Btw: It seems the random crashes/blackscreen ploblems that plagued alot of people here, including me, were at least to some degree Googles own fault (screenshot).
Click to expand...
Click to collapse
Could anyone share the OTA file as well?
Thanks in advance.

Rotten Ross said:
No fix for face unlock "clean the top of your screen, including the black bar"?
Click to expand...
Click to collapse
RMA, only fixable with new device. even downgrading to A10 didn't help, A11 beta seems to f+cked up something, got new device, A11 and face unlock works fine again

DeeZZ_NuuZZ said:
RMA, only fixable with new device. even downgrading to A10 didn't help, A11 beta seems to f+cked up something, got new device, A11 and face unlock works fine again
Click to expand...
Click to collapse
My face unlock works fine for the most part but every now and then I get this error. I reboot the phone and all works fine for a couple of days then it pops up again. I bought my phone from Carphone Warehouse so not sure where I stand.

Rotten Ross said:
My face unlock works fine for the most part but every now and then I get this error. I reboot the phone and all works fine for a couple of days then it pops up again. I bought my phone from Carphone Warehouse so not sure where I stand.
Click to expand...
Click to collapse
yea this was too annoying for me. either carphone needs to replace it within warranty or google themselves, but I'd rather ask google

DeeZZ_NuuZZ said:
yea this was too annoying for me. either carphone needs to replace it within warranty or google themselves, but I'd rather ask google
Click to expand...
Click to collapse
Will most likely have more luck with Google. Not sure how well CPW online are for warranty claims, unless they are going to replace for a new unit I won't trust them.
I'm going to see if the new update works out before I speak to either of them. I rebooted yesterday after installing the October update so I will most likely find out tomorrow of it is resolved.

Delay when pressing notifications

Hello guys, I recently got my new Oneplus 8T, and, whilst the device is amazing from what I could use it, it has an annoying flaw that I couldn´t find any information of.
When I press a whatsapp, telegram, etc notification, there´s a bit of delay inbetween the press and the start of the app opening. The phone does it the majority of times, as you can see in the video below (at the 10 second mark it opens it right):
Do you have an idea on what could be causing this? Does any of you have the same issue I do? I tried turning off everything related to battery saving, even factory reseting. Any help is much appreciated, thank you in advance!

Avrammm said:
Hello guys, I recently got my new Oneplus 8T, and, whilst the device is amazing from what I could use it, it has an annoying flaw that I couldn´t find any information of.
When I press a whatsapp, telegram, etc notification, there´s a bit of delay inbetween the press and the start of the app opening. The phone does it the majority of times, as you can see in the video below (at the 10 second mark it opens it right):
Do you have an idea on what could be causing this? Does any of you have the same issue I do? I tried turning off everything related to battery saving, even factory reseting. Any help is much appreciated, thank you in advance!
Click to expand...
Click to collapse
I have exact same issue and I guess all might be having same issue, just that they don't notice it..quite annoying to be honest...

ram4ufriends said:
I have exact same issue and I guess all might be having same issue, just that they don't notice it..quite annoying to be honest...
Click to expand...
Click to collapse
I've come across some people with this specific flaw, I contacted Oneplus and they told me to factory reset the phone and if that didn't help (which did not, since I've gone wayy further with it, installing HydrogenOS and older versions of OxygenOS and didn't solve the issue), it "might" be a software issue and it "might" be solved in the next software update.
For how much have you been with the phone?
What is bugging me is that this problem is too specific for it to be a hardware issue.

Avrammm said:
I've come across some people with this specific flaw, I contacted Oneplus and they told me to factory reset the phone and if that didn't help (which did not, since I've gone wayy further with it, installing HydrogenOS and older versions of OxygenOS and didn't solve the issue), it "might" be a software issue and it "might" be solved in the next software update.
For how much have you been with the phone?
What is bugging me is that this problem is too specific for it to be a hardware issue.
Click to expand...
Click to collapse
I have the phone for a week...I don't remember having this issue in my earlier OnePlus phones..it might be OOS 11 issue...

ram4ufriends said:
I have the phone for a week...I don't remember having this issue in my earlier OnePlus phones..it might be OOS 11 issue...
Click to expand...
Click to collapse
Yes, I still have my Oneplus 7 Pro and it works flawlessly. I think I found something crucial.
The problem lays whitin the "Notifications" apartment. I'll explain myself.
As you can see in this new video I recorded
that weird delay shows when I open a notification coming from the tab "Notifications". BUT, when I open the SAME APP (Play Store) from a notification coming from "Other notifications" there's no delay at all, the phone works flawlessly, see how I press to see how my download is going, there's no lag. It would be wonderful if you could try it yourself, and see if that's the case on you unit too.
Taking this into account, I'm almost 100% sure this is a software related problem, and has nothing to do with hardware, probably a bug.
I'll report it to the bug reporting section of Oneplus and see if they can work on it.

Avrammm said:
Yes, I still have my Oneplus 7 Pro and it works flawlessly. I think I found something crucial.
The problem lays whitin the "Notifications" apartment. I'll explain myself.
As you can see in this new video I recorded
that weird delay shows when I open a notification coming from the tab "Notifications". BUT, when I open the SAME APP (Play Store) from a notification coming from "Other notifications" there's no delay at all, the phone works flawlessly, see how I press to see how my download is going, there's no lag. It would be wonderful if you could try it yourself, and see if that's the case on you unit too.
Taking this into account, I'm almost 100% sure this is a software related problem, and has nothing to do with hardware, probably a bug.
I'll report it to the bug reporting section of Oneplus and see if they can work on it.
Click to expand...
Click to collapse
Were you able to find any fix to this? Quite annoying issue...

ram4ufriends said:
Were you able to find any fix to this? Quite annoying issue...
Click to expand...
Click to collapse
No, I coulnd't. But I confirmed it to be a software related problem. I flashed LineageOS and PixelExperience ROM and the phone worked flawlessly. So we might have to wait for Oneplus to fix the problem in next OTA.

Avrammm said:
No, I coulnd't. But I confirmed it to be a software related problem. I flashed LineageOS and PixelExperience ROM and the phone worked flawlessly. So we might have to wait for Oneplus to fix the problem in next OTA.
Click to expand...
Click to collapse
Yes, I am on Pixel Experience ROM and it doesn't have the problem..I will be on this ROM for sometime..

ram4ufriends said:
Yes, I am on Pixel Experience ROM and it doesn't have the problem..I will be on this ROM for sometime..
Click to expand...
Click to collapse
Yes, I was really satisfied with these ROMS performance, the only downside was getting Widevine security level down to L3, so i can't watch netflix on the phone anymore... Kinda sad we have to do this in order for the phone to work correctly.

Avrammm said:
Yes, I was really satisfied with these ROMS performance, the only downside was getting Widevine security level down to L3, so i can't watch netflix on the phone anymore... Kinda sad we have to do this in order for the phone to work correctly.
Click to expand...
Click to collapse
I remember there was an APK to watch Netflix..

ram4ufriends said:
I remember there was an APK to watch Netflix..
Click to expand...
Click to collapse
Oh, I might try that one, thank you man! Just updated to the newest OTA that was released today, and didn't fix the issue whatsoever... This is pretty sad.

Avrammm said:
Oh, I might try that one, thank you man! Just updated to the newest OTA that was released today, and didn't fix the issue whatsoever... This is pretty sad.
Click to expand...
Click to collapse
Ah..I was wondering if the latest OTA fixed it...I don't think they will fix it anytime soon

ram4ufriends said:
Ah..I was wondering if the latest OTA fixed it...I don't think they will fix it anytime soon
Click to expand...
Click to collapse
The latest OTA kinda did something for me. I get the delay 5 out of 10 times I press a notification. Used to be 9 out of 10 times lol. It's not completely fixed but it's an improvement. What I did was send a bug report to the Oneplus bug reporting site and they said that they will be working on it.

Touch screen issues

Since swapping a few ROMs, android 11, now 10, screen has ghost touches when navigating.
Flipping annoying as!
Any fix?

badaas said:
Since swapping a few ROMs, android 11, now 10, screen has ghost touches when navigating.
Flipping annoying as!
Any fix?
Click to expand...
Click to collapse
I have same problem, I flashed custom rom for first time in over a year and then went back to stock and now I have same problem, I flashed factory image and wiped data and problem still there, post fix here if you find it please

I installed February stock Android 11.
Fixed it.
I'm now on latest superior and is ok thank fook.

Any one notice multi touch stops working on stock and custom roms?

miko12312 said:
Any one notice multi touch stops working on stock and custom roms?
Click to expand...
Click to collapse
Multitouch is not working at all with my wife's phone. Literally took out of its box three days ago. Google sucks.

joaquincgarcia said:
Multitouch is not working at all with my wife's phone. Literally took out of its box three days ago. Google sucks.
Click to expand...
Click to collapse
How are you guys testing if multi-touch is working or not?
If multi-touch wasn't working, wouldn't that mean that pinch/zoom would not work because it requires two (multi) touch points?

JohnC said:
How are you guys testing if multi-touch is working or not?
If multi-touch wasn't working, wouldn't that mean that pinch/zoom would not work because it requires two (multi) touch points?
Click to expand...
Click to collapse
Yes as I am having issues when trying to zoom or use to touches at once it will only read one, sometimes going into landscape mode and back gets it back working but will do it again at random , I do have a screen protector and a google case ,but only till recently after the march update it

JohnC said:
How are you guys testing if multi-touch is working or not?
If multi-touch wasn't working, wouldn't that mean that pinch/zoom would not work because it requires two (multi) touch points?
Click to expand...
Click to collapse
I have also tried enabling point location in dev options still only reads 1 touch , also going to android 10 does fix all touch issues, but I'd rather have android 11

miko12312 said:
Yes as I am having issues when trying to zoom or use to touches at once it will only read one, sometimes going into landscape mode and back gets it back working but will do it again at random , I do have a screen protector and a google case ,but only till recently after the march update it
Click to expand...
Click to collapse
I am having this issues on my mother's phone, practically since I got it for her (about 1.5 months). Its barely usable for her. Has anything worked for you guys?
Thanks!

Android 11

Having wierd issues with my pixel 2 xl.
Running last Android 11 update.
Currently on custom ROM.
Tried Lineageos 18, pixel experience 11 but same problem.
Sometimes its impossible to text also.
Been happily using my phone from almost 2 years.
Having this issue recently.
Tested without Mobile cover and screen guard.
While typing this, everything seems normal but issue do arises from time to time.
Plz help me out here.
I have uploaded a video name "Pixel 2 XL touch issue" on youtube by username Mohammed Shaikh

msshaikh1717 said:
Having wierd issues with my pixel 2 xl.
Click to expand...
Click to collapse
That is unfortunate, but you are in the wrong subforum since this is for the Pixel 4a.
Your issue belongs to one of the Pixel 2 XL subforums.

Widespread Pixel 4a issue. Uding official Android 10 is the only known workaround that works for multiple users.