In the "touchMultiTest" tool, the touch sampling rate remains 0, untill the finger is moved quite a bit, the resultant feedback is abrupt and inaccurate.
Noticable while sniping in PUBG and scrolling slowly.
This is an extremely annoying issue which was nonexistent in Android 11 older 0xygen OS
This problem is present in all the Android 12 builds of OOS/color OS.
Can others confirm this and bring it to OnePlus' attention?
What can i do to let OnePlus know about this on their "community" app?
Quite possibly the app needs to be updated for the feature to work with newer API
miravision said:
Quite possibly the app needs to be updated for the feature to work with newer API
Click to expand...
Click to collapse
Not an app specific issue.
1. If you have a thick case on that doesn't let heat out your SOC might throttle
2. If you have a screen protector /tempered glass on, try without it or try RMA
miravision said:
1. If you have a thick case on that doesn't let heat out your SOC might throttle
2. If you have a screen protector /tempered glass on, try without it or try RMA
Click to expand...
Click to collapse
Tried all that, i can confirm that this is an issue with OOS 12 and Color OS 12.
All the other Android 12 custom ROMS that I've tried, does not have this problem.
Its an issue specific to OOS 12.
This problem has persisted from way back, since the DP2 (Developer Preview 2) release.
SillyP said:
Tried all that, i can confirm that this is an issue with OOS 12 and Color OS 12.
All the other Android 12 custom ROMS that I've tried, does not have this problem.
Its an issue specific to OOS 12.
This problem has persisted from way back, since the DP2 (Developer Preview 2) release.
Click to expand...
Click to collapse
Upon further investigation, I think it has something to do with the kernel used in OOS 12 builds
Switch back to OOS11 if it's a problem.
TheKnux said:
Switch back to OOS11 if it's a problem.
Click to expand...
Click to collapse
yes, I have resorted to 11.2.10.10 build, but before I did so, I captured and sent OnePlus a log of what I was facing through the feedback app.
lets see how they respond, they asked me to be patient.
Did you experience the issue I'm talking about?
SillyP said:
yes, I have resorted to 11.2.10.10 build, but before I did so, I captured and sent OnePlus a log of what I was facing through the feedback app.
lets see how they respond, they asked me to be patient.
Did you experience the issue I'm talking about?
Click to expand...
Click to collapse
I experienced a whole lotta jank on all of their A12 builds. I never got around to installing OB3, but I did install the build that apparently broke everyone's data (oddly it didn't break mine). I think OB2 was by far the most stable build they put out for A12.
I tried PA for a bit but I'm a features guy and went back to OOS11.
TheKnux said:
I experienced a whole lotta jank on all of their A12 builds. I never got around to installing OB3, but I did install the build that apparently broke everyone's data (oddly it didn't break mine). I think OB2 was by far the most stable build they put out for A12.
I tried PA for a bit but I'm a features guy and went back to OOS11.
Click to expand...
Click to collapse
Now I'm on Xtended. Had to go back to Monet since OOS doesn't use it. Plus a less jank A12 ROM.
TheKnux said:
Now I'm on Xtended. Had to go back to Monet since OOS doesn't use it. Plus a less jank A12 ROM.
Click to expand...
Click to collapse
What is "monet" ?
Also im currently on the C.44 build of OOS 12 on my LE2125.
Idk what OnePlus did, but the touch "deadzone" issue is non-existent ONLY in PUBG mobile.....things are perfect there.
But its present everywhere else and in all the other games ( PUBG New State, COD Mobile, etc) ...
The touch "deadzone" issue is undeniably apparent now...
Easily observed when switching between "PUBG New State" and "PUBG Mobile"
TheKnux said:
Now I'm on Xtended. Had to go back to Monet since OOS doesn't use it. Plus a less jank A12 ROM.
Click to expand...
Click to collapse
I'm flashing Xtended right now, lets see how things are. Judging from the screenshots from the dev's post, this ROM looks delish.
Can anyone confirm if the issue is fixed in the lastest c.61 update.
They addressed system fluency
smjunaid said:
Can anyone confirm if the issue is fixed in the lastest c.61 update.
They addressed system fluency
Click to expand...
Click to collapse
PUBG/PUBG New State and some other popular games has this issue fixed.
It was indeed an API related issue.
SillyP said:
PUBG/PUBG New State and some other popular games has this issue fixed.
It was indeed an API related issue.
Click to expand...
Click to collapse
I was having the issue in the launcher even. In c.60
Even using Facebook and all other apps. During scrolling and holding the scroll with a finger
The problem very well does still persist throughout c.61.
By "system fluency", OnePlus probably means animation improvements.
smjunaid said:
I was having the issue in the launcher even. In c.60
Even using Facebook and all other apps. During scrolling and holding the scroll with a finger
Click to expand...
Click to collapse
SillyP said:
The problem very well does still persist throughout c.61.
By "system fluency", OnePlus probably means animation improvements.
Click to expand...
Click to collapse
Thanks for the prompt response. I don't know why people don't notice such a huge blunder. Thanks again mate
Related
Not sure if this is a stable build. Should I go ahead and install?
Also got it offered here, Global 8.2.1.0.MAGMIDL on OTA. 706MB. It appeared just after opening the updater app.
I've installed and haven't noticed any major improvements. Fingerprint scanner seems to be working faster but may just be my imagination.
There is an UI imrovements where the text is now black for your 3rd party music player in notification cards. Also, I may be going crazy but my battery lasts longer...
estetico said:
There is an UI imrovements where the text is now black for your 3rd party music player in notification cards. Also, I may be going crazy but my battery lasts longer...
Click to expand...
Click to collapse
What about qfp reader battery drain in previous builds? Is resolved?
deanMKD said:
What about qfp reader battery drain in previous builds? Is resolved?
Click to expand...
Click to collapse
Sorry, I never had that problem before, and I don't have it now
activate fingerprint and use it some time. after that check Android system usage. Also check wake look time for Android system.
estetico said:
Sorry, I never had that problem before, and I don't have it now
Click to expand...
Click to collapse
Please check it installing Wakelock Detector [LITE] from Google Play Store and start it.
Then when it's time to charge the battery start it again, press the first of the three buttons on the top right corner and select "CPU Wakelock".
Tap on "Android System" and post a screenshot.
I've got it installed since Thursday. So far I would say the battery time is the same or slightly better. I do use the fingerprint scanner and I think it's slightly faster than before. Everything else, Bluetooth, Wifi and GPS so far working nice.
Only downside, the Security app had the cleaner function reactivated after the update. I'm pretty sure I had it disabled before. All other functions of the Security app seem to have kept their settings.
patoberli said:
I've got it installed since Thursday. So far I would say the battery time is the same or slightly better. I do use the fingerprint scanner and I think it's slightly faster than before. Everything else, Bluetooth, Wifi and GPS so far working nice.
Only downside, the Security app had the cleaner function reactivated after the update. I'm pretty sure I had it disabled before. All other functions of the Security app seem to have kept their settings.
Click to expand...
Click to collapse
Camera is downgraded, images are blurry. ram menagment is better, but other are the same bugs.
My battery is draining horribly since this update. Going to downgrade and switch to eu rom before qfp bug
Tones1971 said:
My battery is draining horribly since this update. Going to downgrade and switch to eu rom before qfp bug
Click to expand...
Click to collapse
What rom is that mate? since getting my phone from alixpress the phone has had awful battery life. I put the latest xiaomi.eu rom on but to no avail
What do you understand under "awful"?
shakerist said:
What rom is that mate? since getting my phone from alixpress the phone has had awful battery life. I put the latest xiaomi.eu rom on but to no avail
Click to expand...
Click to collapse
Global 8.2.1.0. Battery life was quite good before this update.
Tones1971 said:
Global 8.2.1.0. Battery life was quite good before this update.
Click to expand...
Click to collapse
You are talking about 8.0.3.0?
That's because there was no problem with qfp-service on the previous version.
I think that's caused by a (bad) attempt to fix the fp reader after many complaints on the official forum.
gnazio said:
You are talking about 8.0.3.0?
That's because there was no problem with qfp-service on the previous version.
I think that's caused by a (bad) attempt to fix the fp reader after many complaints on the official forum.
Click to expand...
Click to collapse
Yeah only started with this update. Think im going to have to downgrade. Be waiting a while for a fix for the global rom i would think
patoberli said:
What do you understand under "awful"?
Click to expand...
Click to collapse
This
Indeed bad, much worse than mine.
Frizzel said:
Not sure if this is a stable build. Should I go ahead and install?
Click to expand...
Click to collapse
Better fingerprint reader functionality (Its the only build with a working FP reader for me)
Worse battery life
Slight UI changes.
You decide.
In the meanwhile...
it seems that 8.2 Global Stable has been retired:
http://en.miui.com/download-314.html
After updating to 43 OTA 004, Faceunlock is no longer instant. now you see first the lockscreen flash and then UI slide in. I went back to 43 OTA 003, but same situation.
before it was just press powerbutton/doubletap screen and the screen turned on showing instantly UI whereever you left off. just like all the reviewers showed it. I dont have file to go back to inital firmware 001 .... :/
VERY DISAPPOINTING, it really breaks the "instant" feeling. hope they fix it soon.
meanwhile, no speed increase in fingerprint reader. still slightly slower than OP3.
UPDATE: solved - it is Nova Launcher with a custom wallpaper that caused this -> back to Oneplus launcher, set new wallpaper = FaceUnlock instant again!
Not a terrible trade-off for more security.
FP sensor still fast af.
t2jbird said:
Not a terrible trade-off for more security.
Click to expand...
Click to collapse
what makes you think they inceased security?
t2jbird said:
FP sensor still fast af.
Click to expand...
Click to collapse
coming from OP3, that s not true... at least not for me YMMV
i can upload side-by-side vid tonight.
Hope everyone is reporting these "bugs" to OnePlus instead of just reporting them here.
Baldilocks said:
Hope everyone is reporting these "bugs" to OnePlus instead of just reporting them here.
Click to expand...
Click to collapse
reason for posting it here is to find out if anyone else experiencing this
ewww i hope not, then there is no difference than what was on the OP3/T smart lock, i liked the option that u didn't have to swipe up, i will prob return mine if this is the case.
phynesse said:
what makes you think they inceased security?
coming from OP3, that s not true... at least not for me YMMV
i can upload side-by-side vid tonight.
Click to expand...
Click to collapse
https://www.xda-developers.com/oneplus-face-unlock-oneplus-5t/
Works great for me!
I dont even see the lockscreen!
t2jbird said:
https://www.xda-developers.com/oneplus-face-unlock-oneplus-5t/
Click to expand...
Click to collapse
sooo, not security focused then. also doesnt explain why it now shows the lockscreen, instead of unlocking straight to UI... like with fingerprint
Nick502 said:
Works great for me!
I dont even see the lockscreen!
Click to expand...
Click to collapse
thanks for reply. and you are on which Oxygen version? 4.7.1 or higher?
phynesse said:
thanks for reply. and you are on which Oxygen version? 4.7.1 or higher?
Click to expand...
Click to collapse
Im on 4.7.2
Nick502 said:
Works great for me!
I dont even see the lockscreen!
Click to expand...
Click to collapse
+1 same here it unlocks instantly. I have added a FP too.
gianton said:
+1 same here it unlocks instantly. I have added a FP too.
Click to expand...
Click to collapse
thanks, ok then i did something to cause it... hm too bad
Here on 4.7.2 its also slow.
I had the same problem and factory reset: face unlock is back to being instant, and the finger print reader is noticeably faster. It is troublesome, however, that an OTA forced me to factory reset a 3 day old phone...
I have also reset after update but not solved.
I updated homescreen and lockscreen wallpaper with a custom one and experienced a slight drop on face unlock speed. Meaning that I was able to see the lockscreen for 1/10 of a second before the homescreen was there. I reverted the wallpaper choosing one of oneplus 's and face unlock speed was back to instant. Just a tip.
Works fine for me. I'm on FreedomOS based on Oxygen 4.7.2.
xByt3z said:
Works fine for me. I'm on FreedomOS based on Oxygen 4.7.2.
Click to expand...
Click to collapse
This is the 5t thread and not 5, thanks.
Schrotty35 said:
This is the 5t thread and not 5, thanks.
Click to expand...
Click to collapse
I'm aware. I built FreedomOS myself for the 5T.
Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
https://youtu.be/wgYN5GwIgIc
https://youtu.be/2Vv584tvVyg
https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
It seems devices with oos on 8.1 ( op5/t) cannot use this mod.
AOSP and LOS roms should be okay.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07
@calebcabob
@Myself5
@BDogg718
@sixohtew
@nitin.chobhe
@auras76
you may want to look at this and include it in your april releases.
If not users can just make use of the magisk module.
This causes a bootloop on P DP1.
iaTa said:
This causes a bootloop on P DP1.
Click to expand...
Click to collapse
Thanks for the report.
can anyone confirm this?
In the meantime i removed the p tag from the thread title.
Could be That there are additional changes in p that make this libs unusable and only workable on 8.1.
Unfortunately there is afaik no complete source for p yet. So I can’t compile them specifically for p.
Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!
jbarcus81 said:
Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!
Click to expand...
Click to collapse
Same with me on google fotos!
Glad it’s fixed for you.
Freak07 said:
Same with me on google fotos!
Glad it’s fixed for you.
Click to expand...
Click to collapse
Also fixed for me, thanks for solving this problem!
I can't replicate this problem, but good to know that there's a fix if I ever experience it.
I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks
I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch
Prey521 said:
I can't replicate this problem, but good to know that there's a fix if I ever experience it.
Click to expand...
Click to collapse
sixohtew said:
I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch
Click to expand...
Click to collapse
I also thought at first I didn’t have this issue at all.
But once I triggered it accidentally I experienced it many times. Maybe I just learnt what to look for.
Another fun thing is. A friend of mine also got the pixel XL 2 and I could reproduce it right away on his locked phone which is stock 8.1.
I can also trigger it on my pixel C tablet.
ReapinDevil said:
I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks
Click to expand...
Click to collapse
Either try flashing it in recovery or use the latest magisk?
Freak07 said:
@calebcabob
@Myself5
@BDogg718
@sixohtew
@nitin.chobhe
@auras76
you may want to look at this and include it in your april releases.
If not users can just make use of the magisk module.
Click to expand...
Click to collapse
The mention for the last dev didn't work for some reason, so:
@auras76
mistermojorizin said:
The mention for the last dev didn't work for some reason, so:
@auras76
Click to expand...
Click to collapse
Thanks in the quote from your post of my post it worked tough
Freak07 said:
Thanks in the quote from your post of my post it worked tough
Click to expand...
Click to collapse
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the quote.
Kudos to you,
Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,
Now it all fixed.
The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.
And considering am using full cover glass protector. This is amazing work !
What app did you use for that test?
I've experienced lack of touch response quite often. It's weird and seemingly random. I just flashed this on 8.1 with magisk. I don't have any results yet, but based on what everyone else is saying, this is a solid fix. Thanks for your work!
Do we have to worry about removing this in the future if google updates fix the issue too? Will this being on the system cause conflicts and issues?
mistermojorizin said:
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the Autor.
Click to expand...
Click to collapse
That’s just xda bring xda.
I had this problem a few times when updating the OP for a new release. Sometimes the OP won’t update at all...
otonieru said:
Kudos to you,
Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,
Now it all fixed.
The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.
And considering am using full cover glass protector. This is amazing work !
Click to expand...
Click to collapse
Glad it works out for you!
Enjoy your phone
Apparently even if you were on DP1, it still wipes your phone on the upgrade. I wonder why that's necessary.
Has anyone downloaded / tested this yet?
stuclark said:
Has anyone downloaded / tested this yet?
Click to expand...
Click to collapse
Going to try it this morning. I was unable to root DP1, hopefully it will work on this one.
Gordietm said:
Going to try it this morning. I was unable to root DP1, hopefully it will work on this one.
Click to expand...
Click to collapse
It's no different from DP1 absolutely NO fixes what so ever from what I see, having to revert back, banking apps still don't work, UI is still a mess using dark mode, none of the Google implementations.
It's a DP1 re-release.........?
Duncan1982 said:
It's no different from DP1 absolutely NO fixes what so ever from what I see, having to revert back, banking apps still don't work, UI is still a mess using dark mode, none of the Google implementations.
It's a DP1 re-release.........?
Click to expand...
Click to collapse
Pretty much. Face unlock works now though. And still can't root it.
Face unlock fixed
Bluetooth issues fixed
Screen alignment on qhd fixed
Keyboard issues fixed
Google AR fixed
New approach of PhotoChrom now in DP2
So far that's what I noticed but there must be more fixed
I assume smart things power menu is limited to pixels now?
I am not on the beta program, but received a notice on a pre-update for my 8 pro. It went away and had me wondering, as the updater showed nothing.
I guess it was this beta update. As usual, OnePlus can't keep their ducks in a row.
Sounds like there's not enough to make the "upgrade" worthwhile - could someone please test whether turning WiFi Hotspot on and off via MacroDroid / Taskman etc. still works?
(it is broken in OOS 10.x but was working in 11 dp1)
patensas said:
Face unlock fixed
Bluetooth issues fixed
Screen alignment on qhd fixed
Keyboard issues fixed
Google AR fixed
New approach of PhotoChrom now in DP2
So far that's what I noticed but there must be more fixed
Click to expand...
Click to collapse
Can you please post the camera apk here for testing?
Thanks
I unlocked my boot-loader and wanted to install the DP2 via the system update, but it fails to install. Zip seems to be fine, can open it
golf60 said:
Can you please post the camera apk here for testing?
Thanks
Click to expand...
Click to collapse
It's OnePlus Camera version 5.4.23
You can download it from apkmirror.com
It dint not work on 10.5.10, downgraded to 10.5.8, now I can install the DP.
I'm downgrading to 10.5.11. I'm finding 11 DP2 still too bugging. I thought it would have been a little further along from DP1. I guess I'll wait until a stable version comes along.
DforDesign said:
I assume smart things power menu is limited to pixels now?
Click to expand...
Click to collapse
It's at minimum "not mandatory" for OEMs. But OnePlus could inplement it if they want
Sent from my GM1917 using Tapatalk
Gordietm said:
It's OnePlus Camera version 5.4.23
You can download it from apkmirror.com
Click to expand...
Click to collapse
does camera.apk run on version 10.5.11?
Next with the photocrome feature?
brmbjn said:
does camera.apk run on version 10.5.11?
Next with the photocrome feature?
Click to expand...
Click to collapse
It works on 10.5.11, not sure about the photochrome feature.
patensas said:
Face unlock fixed
Bluetooth issues fixed
Screen alignment on qhd fixed
Keyboard issues fixed
Google AR fixed
New approach of PhotoChrom now in DP2
So far that's what I noticed but there must be more fixed
Click to expand...
Click to collapse
Android Auto not working on DP2 either.
Is dual sim in the us working?
Dear all, I am wondering if anyone could enlighten me as to which third party A11 rom is most stable.
I am not looking for a lot of features, just basic stuff similar to Oxygen OS, which is stuck on A10.
It seems that DerpFest is the most active one, is it stable though?
I used PixelExperience for another device, it was OK with minor bugs, wonder how stable PE for Oneplus 5T is.
Thank you all! Much appreciated!
I have used DerpFest A11 for a while. Haven't had any major problems with it. Calls, Messages and Mobile Data were working fine. Battery life was perfect. In my opinion, that's the most stable one for OP5T atm.
Thank you for sharing it!
Although I have to say "Calls, Messages and Mobile Data were working fine" is such a low bar to set...
Any minor issue you have encountered?
Update for anyone who has similar question:
Just stick with OOS. None of the third party options ever come close to it.
terrytw said:
Thank you for sharing it!
Although I have to say "Calls, Messages and Mobile Data were working fine" is such a low bar to set...
Any minor issue you have encountered?
Click to expand...
Click to collapse
Google maps timeline doesn't work, that's all
terrytw said:
Update for anyone who has similar question:
Just stick with OOS. None of the third party options ever come close to it.
Click to expand...
Click to collapse
try DerpFest 12, you will never return to oos again.
even I had same opinion like you before trying it, now even if volte is broke idc.
sonyD4d said:
try DerpFest 12, you will never return to oos again.
even I had same opinion like you before trying it, now even if volte is broke idc.
Click to expand...
Click to collapse
Volte not working is a deal breaker to me. Beside I heard that dual-sim is not working.
I mean, to each of their own, but these all feel like fundamental flaw to me and you cant put a "stable" label on it not matter how much you like it.
I have tried derp11 and instantly returned to OOS, it is not where near polished as OOS.