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.
Related
Hi,
yesterday I was on racetrack Nürburgring and tried my new OnePlus One.
Everything was cool except one thing.
Most time, when I took the OPO out of my trousers, the screen was on and an app was open?
Is there a setting for that, that this never happens? Don't want to share battery lifetime to my pockets and don't want to place calls to the whole world.
Is anyone having same problems or could someone help me?
Settings/Interface/Gesture Shortcuts, disable everything.
Transmitted via Bacon
You forgot display -> double tap to wake
It is scheduled to be fixed by OTA-update xnph28s; before unlocking the proximity sensor checks if the device is currently in a pocket.
See bugreport: https://jira.cyanogenmod.org/browse/BACON-16
Good to see, d4fseeker.
Do you know, when this update is ready for download?
Don't want to disable the Oppo features on opo
They say the update should be released in the next week or two.
Transmitted via Bacon
Where can i see the gerrit of cm11s??
Any news on the date of the next OTA update ?
aka_ronin said:
Any news on the date of the next OTA update ?
Click to expand...
Click to collapse
Typically when its ready, it was posted a week ago in 2 weeks time but no promises as they want to get it right in this OTA.
If you can't wait, you can flash custom ROMs as they already have this commit where it checks the proximity sensor. If the proximity sensor is blocked then gestures will be disabled until the proximity sensor is not blocked.
zephiK said:
Typically when its ready, it was posted a week ago in 2 weeks time but no promises as they want to get it right in this OTA.
If you can't wait, you can flash custom ROMs as they already have this commit where it checks the proximity sensor. If the proximity sensor is blocked then gestures will be disabled until the proximity sensor is not blocked.
Click to expand...
Click to collapse
Thanx for the tip :good: ...but I think I will wait.
d4fseeker said:
It is scheduled to be fixed by OTA-update xnph28s; before unlocking the proximity sensor checks if the device is currently in a pocket.
See bugreport: https://jira.cyanogenmod.org/browse/BACON-16
Click to expand...
Click to collapse
Does paranoid android fix this?
jameslfc5 said:
Does paranoid android fix this?
Click to expand...
Click to collapse
I don't use paranoid android but go into their thread and search for the keyword proximity. Chances are they probably did include it.
Sent from my One using Tapatalk
zephiK said:
I don't use paranoid android but go into their thread and search for the keyword proximity. Chances are they probably did include it.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Does paranoid android have the lockscreen gestures then?
Thanks
jameslfc5 said:
Does paranoid android have the lockscreen gestures then?
Thanks
Click to expand...
Click to collapse
Like I said before, I don't use Paranoid Android. Go into the thread and search for the keyword "lockscreen" ... if the ROM is based on CM for the OPO then it will have the gesture controls.
Edit: Heres your answer, http://forum.xda-developers.com/showthread.php?p=53677403&highlight=gesture#post53677403 next time just search
Not only as stable as CM is, it includes all device specific features of CM like offscreen gestures, Quickboot, Soft/hard buttons...
Click to expand...
Click to collapse
FormelLMS said:
Hi,
yesterday I was on racetrack Nürburgring and tried my new OnePlus One.
Everything was cool except one thing.
Most time, when I took the OPO out of my trousers, the screen was on and an app was open?
Is there a setting for that, that this never happens? Don't want to share battery lifetime to my pockets and don't want to place calls to the whole world.
Is anyone having same problems or could someone help me?
Click to expand...
Click to collapse
You either need to upgrade the trousers or keep your hands where they belong - in someone else's trousers.
Mike
mhannigan said:
You either need to upgrade the trousers or keep your hands where they belong - in someone else's trousers.
Mike
Click to expand...
Click to collapse
Or just disable the "Double tap to wake" feature like I did... ...and wait for the next OTA update.
aka_ronin said:
Or just disable the "Double tap to wake" feature like I did... ...and wait for the next OTA update.
Click to expand...
Click to collapse
That is a FIX and not a full-fledged semi-effective workaround. Unacceptable, but thanks for trying.
Mike
This is CM inc's chance to show what they can do.
You know they have a One Plus as a test phone but they let it go out with low call volume and sub par signal strength. As well as touch screen problems and more. Just look at the bug reports. There no hiding them.
Software makes the phone work so to me that is what I have to look at.
All in all its a great phone I just expect more from CM inc.
Vortex1969 said:
This is CM inc's chance to show what they can do.
You know they have a One Plus as a test phone but they let it go out with low call volume and sub par signal strength. As well as touch screen problems and more. Just look at the bug reports. There no hiding them.
Software makes the phone work so to me that is what I have to look at.
All in all its a great phone I just expect more from CM inc.
Click to expand...
Click to collapse
To be fair the phone is still in its infancy stages and is invite only. So in a way you can say we paid for the phone to be "internal beta testers" and when the phone is not invite only thats when its out for the masses.
I agree with you though, these major problems should have been addressed in a hotfix rather than having users wait for the next OTA. Luckily for the most of us, we're able to fix it in our own hands but for those who aren't then they'll just have to wait.
zephiK said:
To be fair the phone is still in its infancy stages and is invite only. So in a way you can say we paid for the phone to be "internal beta testers" and when the phone is not invite only thats when its out for the masses.
I agree with you though, these major problems should have been addressed in a hotfix rather than having users wait for the next OTA. Luckily for the most of us, we're able to fix it in our own hands but for those who aren't then they'll just have to wait.
Click to expand...
Click to collapse
I agree with that and thank you for one of the fixes.[emoji3]
Has anyone else had an issue where characters are repeated when typing (like in the title)? Had the phone for a week now and I'm really impressed but this little issue is ddriving me nuts. I thought it was an issue with SwiftKey but swapping for the built in Gboard hasn't resolved the issue. I'm running the current firmware release C432. Happens with sspacees too...So odd?.
tdiboy said:
Has anyone else had an issue where characters are repeated when typing (like in the title)? Had the phone for a week now and I'm really impressed but this little issue is ddriving me nuts. I thought it was an issue with SwiftKey but swapping for the built in Gboard hasn't resolved the issue. I'm running the current firmware release C432. Happens with sspacees too...So odd[emoji20].
Click to expand...
Click to collapse
Your fingers needs learn the new size of device, my fingers needed it [emoji6]
Enviado desde mi BKL-L09 mediante Tapatalk
tdiboy said:
Has anyone else had an issue where characters are repeated when typing (like in the title)? Had the phone for a week now and I'm really impressed but this little issue is ddriving me nuts. I thought it was an issue with SwiftKey but swapping for the built in Gboard hasn't resolved the issue. I'm running the current firmware release C432. Happens with sspacees too...So odd.
Click to expand...
Click to collapse
Same problem here.
This happened to me once or twice. I noticed that it happened when I accidentally swiped over the keyboard instead of typed a letter. Maybe the same happened to you.
Thanks for your responses. I've noticed that it got worse the more quickly I typed. I did a power cycle (AKA Magic Reboot) shortly after I made the post and it doesn't seem too bad now (typing this on a laptop). Doesn't look like it is "an issue" as such as its only a couple of people reporting it here. Hard to tell as it has not been available long so the user-base will be fairly small.
tdiboy said:
Thanks for your responses. I've noticed that it got worse the more quickly I typed. I did a power cycle (AKA Magic Reboot) shortly after I made the post and it doesn't seem too bad now (typing this on a laptop). Doesn't look like it is "an issue" as such as its only a couple of people reporting it here. Hard to tell as it has not been available long so the user-base will be fairly small.
Click to expand...
Click to collapse
There was another thread where a few of us were discussing... The 130 update definitely reduced touch sensitivity so there are missed touch points when typing and also repeating letters when typing fast.. The 100 firmware was fine.. I did send them a message on HiCare and they said they'd pass it over to the dev team.. Hopefully the next update fixes it..
Sent from my BKL-L09 using Tapatalk
That's interesting... I'll try contacting them using that method. Was it the Live Chat facility? It has been doing it all through this message but I've been spell checking as i go. Only served to remind me how annoying this issue is. Bar that. I love this phone?.
tdiboy said:
That's interesting... I'll try contacting them using that method. Was it the Live Chat facility? It has been doing it all through this message but I've been spell checking as i go. Only served to remind me how annoying this issue is. Bar that. I love this phone[emoji7].
Click to expand...
Click to collapse
Yeah HiCare live chat feature.. You can let them kbow.. I also mentioned the lack of a feedback/bug report app/service. Might as well mention that if you think it'll be a good idea..
Next time quote the post so people get notified that you replied
Sent from my BKL-L09 using Tapatalk
+1 for the problem. But getting better day by day
Targaeryan said:
Yeah HiCare live chat feature.. You can let them kbow.. I also mentioned the lack of a feedback/bug report app/service. Might as well mention that if you think it'll be a good idea..
Next time quote the post so people get notified that you replied
Sent from my BKL-L09 using Tapatalk
Click to expand...
Click to collapse
I tried the Live Chat facility and they suggested clearing the Cache Partition. I did that and still get the issue (typing this on laptop). He said that it was the first case he had heard of this happening (funny how they always say that...). I might try the live chat again to see what can be done. I mentioned about the lack of feedback/bug report and he said he would "pass it on" so not much use really.
same here.
enzippo said:
same here.
Click to expand...
Click to collapse
It seems puzzling that if it were a software issue, then everyone running the 130(C432) release would we mentioning it on this forum. As it seems a little quiet with regards to that, this make me think its a hardware issue affecting a limited number of handsets.
I'm hoping that the next update (overdue for Feb and now due for March update) may fix it. If not, I'll be sending it off for repair with John Lewis in the UK where I bought it from.
tdiboy said:
It seems puzzling that if it were a software issue, then everyone running the 130(C432) release would we mentioning it on this forum. As it seems a little quiet with regards to that, this make me think its a hardware issue affecting a limited number of handsets.
I'm hoping that the next update (overdue for Feb and now due for March update) may fix it. If not, I'll be sending it off for repair with John Lewis in the UK where I bought it from.
Click to expand...
Click to collapse
I had no troubles with the earlier b100... i think is software releated.
enzippo said:
I had no troubles with the earlier b100... i think is software releated.
Click to expand...
Click to collapse
I have to say, I think the new 140 update fixed it! I'm not having missed touch events or repeating characters.
Sent from my BKL-L09 using Tapatalk
Targaeryan said:
I have to say, I think the new 140 update fixed it! I'm not having missed touch events or repeating characters.
Sent from my BKL-L09 using Tapatalk
Click to expand...
Click to collapse
i'm waiting the update too, but c432 fw not yet released.
Fellas, the bug is also known as "double tapping" and it software related only. Few years ago Huawei P8 Lite had it and after a several updates it was fixed.
qtoo941 said:
Fellas, the bug is also known as "double tapping" and it software related only. Few years ago Huawei P8 Lite had it and after a several updates it was fixed.
Click to expand...
Click to collapse
I finally did the factory reset as suggested by support a while back and strangely (had no hope that it would fix it), the issue has (so far) not returned .
I'm wondering if the issue occured as a result of the the January 130 update which started to install as soon as I connected the phone to the WiFi when I first set up the handset. Anyone else who are having the issue after the update but have not done a factory reset, I recommend that they try it. If you have done the reset, do you still get the issue?
Hopefully the 140 update (due any day?) will now sort out the dropping bluetooth whilst streaming music.
tdiboy said:
I finally did the factory reset as suggested by support a while back and strangely (had no hope that it would fix it), the issue has (so far) not returned .
I'm wondering if the issue occured as a result of the the January 130 update which started to install as soon as I connected the phone to the WiFi when I first set up the handset. Anyone else who are having the issue after the update but have not done a factory reset, I recommend that they try it. If you have done the reset, do you still get the issue?
Hopefully the 140 update (due any day?) will now sort out the dropping bluetooth whilst streaming music.
Click to expand...
Click to collapse
Any news about this topic? The more I type the more letters tend to repeat... Very annoying
Flyingdaddy said:
Any news about this topic? The more I type the more letters tend to repeat... Very annoying
Click to expand...
Click to collapse
My factory reset seemed to resolve the issue but it came back shortly afterwards but not as bad as it was previously. That or I've become more accustomed to it. EIther way, it is still here. I take it you are not on the C432 (UK?) variant like mine? No sign of the 140 update for me yet which seems to resolve it for some users suffering the same issue.
tdiboy said:
My factory reset seemed to resolve the issue but it came back shortly afterwards but not as bad as it was previously. That or I've become more accustomed to it. EIther way, it is still here. I take it you are not on the C432 (UK?) variant like mine? No sign of the 140 update for me yet which seems to resolve it for some users suffering the same issue.
Click to expand...
Click to collapse
I'm on the European model, see screenshot. Still 130 apparently.
Just posting April update now available.
Screen shot below
So far so good.
Update was successful.
The double tap to wake causing the screen waking issue seems to be addressed. Let's see.
tindersticks said:
The double tap to wake causing the screen waking issue seems to be addressed. Let's see.
Click to expand...
Click to collapse
I take it back. The bug still persists.
Battery life is much better with April update.
Like the Feb stock fw.
Edit
At 52% 5hr 13min sot been on all day 14hrs since last charge.
Amazing.
Any idea when UK BTU will get this? We always get updates after everyone else so annoying
mystertom101 said:
Any idea when UK BTU will get this? We always get updates after everyone else so annoying
Click to expand...
Click to collapse
Today............. in my case. G970FXXU1ASD6/ASD4 installing now.
Anyone else noticed proximity sensor not working since April update?
Haven't got April update. What version you guys using?
Sent from my SM-G970U1 using Tapatalk
April 1st patch
The newest today's update is only 173.4MB, but what's in it? I don't see any specific descriptions beside the security patch.
Now, what about that ASD4 update(in OP post above, 244.55MB) I've never gotten that one in the US, they mention camera software improvements in there, am I still gonna get it? All the different regions create lots of confusion.
mzsquared said:
The newest today's update is only 173.4MB, but what's in it? I don't see any specific descriptions beside the security patch.
Now, what about that ASD4 update(in OP post above, 244.55MB) I've never gotten that one in the US, they mention camera software improvements in there, am I still gonna get it? All the different regions create lots of confusion.
Click to expand...
Click to collapse
I installed the same updates as you. No new feature on camera.
The Google Pill is dark now if you're rocking dark theme.
Sent from my SM-G970U1 using Tapatalk
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.
Alright, so currently im dealing with some Multitouch issues on my Pixel 4a. The repair place i went to UBREAKIFIX said they'll have to do the whole repair they did preciously again and charge me (because of 2 small dents at the side of the screen). Would not recommend. I wanted to get a poll of everyone with this exact issue Here is some steps to test:
1. Enable Developer Options (Go into build number click however many times and get developers options
2. Go to Developer Options in System settings,
3. Scroll down to Input and enable "Show taps" and "Pointer Location.
4. Put two fingers down and see if multiple pointers are shown (If not, Multi-touch does not work)
Also some other Notes:
Downgrading to Android 10, Makes multitouch work for some reason :/
Also would like to know if you've gotten your phone repaired before.
Any help figuring this whole thing out is appreciated
Can I ask what was the repair they did the first time to fix your touch problem?
hammered58 said:
Can I ask what was the repair they did the first time to fix your touch problem?
Click to expand...
Click to collapse
The first time, it was just a broken screen, had to replace it
fbievan said:
The first time, it was just a broken screen, had to replace it
Click to expand...
Click to collapse
Dont know if started happening before or after, but i noticed it recently, and started digging, brought it to the place and they said they wouldnt cover it under warranty because of 2 small dents at the side of screen which have zero relation to the problem at hand
fbievan said:
Dont know if started happening before or after, but i noticed it recently, and started digging, brought it to the place and they said they wouldnt cover it under warranty because of 2 small dents at the side of screen which have zero relation to the problem at hand
Click to expand...
Click to collapse
That's sucks, hard to prove if there right or wrong without putting a known good screen on
hammered58 said:
That's sucks, hard to prove if there right or wrong without putting a known good screen on
Click to expand...
Click to collapse
Also as i noted, for some reason downgrading to andorid 10 has multitouch working. (From flash.android.com)
fbievan said:
Also as i noted, for some reason downgrading to andorid 10 has multitouch working. (From flash.android.com)
Click to expand...
Click to collapse
I honestly cant say if its the hardware or software, maybe it might be a combination of both? I'm not entirely sure, however downgrading to android 10 from googles flash tool does seem to have it work. I had what i would guess is a full screen replacement from UBREAKIFIX, due to shattering the entire screen. Honestly, spending 140 dollars just to see if it might work is not worth it to me, so I'm really not sure what to do.
Even doing it yourself the cheapest I've seen a screen is 110 from AliExpress, which I don't get because I just replaced one on a g7 moto play for 20 bucks off ebay
hammered58 said:
Even doing it yourself the cheapest I've seen a screen is 110 from AliExpress, which I don't get because I just replaced one on a g7 moto play for 20 bucks off ebay
Click to expand...
Click to collapse
Is there any reason why this multitouch would work on android 10? I dont see exactly what is happening here
fbievan said:
Is there any reason why this multitouch would work on android 10? I dont see exactly what is happening here
Click to expand...
Click to collapse
idk,, maybe the sensitivity is setup diff
hammered58 said:
idk,, maybe the sensitivity is setup diff
Click to expand...
Click to collapse
After looking for a while seems the entire drivers are different in the kernel. But that is my brief look at. If anyone who knows kernel drivers would like to take a look at it. Would be helpful
LineageOS 19.1 - multitouch just stopped working today after several weeks without problems. No repairs or damage.
I'm on stock but rooted. I've been slack so still on October patch. Multi touch working fine. Never had a problem with it.
(Finally updated to December patch and it's still working.)
LionDGem said:
LineageOS 19.1 - multitouch just stopped working today after several weeks without problems. No repairs or damage.
Click to expand...
Click to collapse
What fixed it for me was downgrading to android 10 then updating all the way up...
From right here: https://forum.xda-developers.com/t/...ter-apr-security-update.4428089/post-87356703
fbievan said:
What fixed it for me was downgrading to android 10 then updating all the way up...
From right here: https://forum.xda-developers.com/t/...ter-apr-security-update.4428089/post-87356703
Click to expand...
Click to collapse
Wonder how this actually fixes the issue. Sounds strange.
LionDGem said:
Wonder how this actually fixes the issue. Sounds strange.
Click to expand...
Click to collapse
I don't know... As far as I know downgrading has the kernel touchscreen driver seemingly working... from there I know little
fbievan said:
I don't know... As far as I know downgrading has the kernel touchscreen driver seemingly working... from there I know little
Click to expand...
Click to collapse
Multitouch stopped working on my Pixel 4A 5G after updating to android 13.
Maybe a bug caused by an OTA update?
qqBenji said:
Multitouch stopped working on my Pixel 4A 5G after updating to android 13.
Maybe a bug caused by an OTA update?
Click to expand...
Click to collapse
I have LineageOS 19.1 here. So android 12. i'll try that android 10 approach
I can confirm now that downgrading to Official Google Pixel 4a Stock Rom Android 10 fixed the issue. I try to go back to LOS 20 now and see what happens.
PS: Using internal updater to update to Android 13 broke it again. Taking the long route now.
PPS: That chromium based flash tool is really handy. Would be awesome to have something like that for LineageOS.
PPS: As soon as I install anything above Android 10, multitouch stops working. I'll sell this stupid thing as is (will let te buyer know of course). Its a shame.