Related
Hope it could be fixed soon!!!!
lihaokingkong said:
Hope it could be fixed soon!!!!
Click to expand...
Click to collapse
Did you really need to create a new thread for this...? Probably not.
There's a messy workaround that breaks all other audio; it's been mentioned several times already.
Google Finally Acknowledges Volume Bug issue and has a fix in place for release according to this........
http://www.bbc.co.uk/news/technology-15870020
oka1 said:
Google Finally Acknowledges Volume Bug issue and has a fix in place for release according to this........
http://www.bbc.co.uk/news/technology-15870020
Click to expand...
Click to collapse
isnt that the same news as yesterday?
oka1 said:
Google Finally Acknowledges Volume Bug issue and has a fix in place for release according to this........
http://www.bbc.co.uk/news/technology-15870020
Click to expand...
Click to collapse
Google has acknowledged this quite a while ago. BBC is just catching up.
let's just hope samsung, under the pressure of google actually has a fix.
remember their supposed "fix" for the Galaxy S's GPS issues? yeah right
until this major flaw gets a 100% fix, not forking out my cash
terencec said:
let's just hope samsung, under the pressure of google actually has a fix.
remember their supposed "fix" for the Galaxy S's GPS issues? yeah right
until this major flaw gets a 100% fix, not forking out my cash
Click to expand...
Click to collapse
Same here. Needs fixed.
Sent from my HTC Desire using XDA App
kristovaher said:
Google has acknowledged this quite a while ago. BBC is just catching up.
Click to expand...
Click to collapse
not only are the BBC late, but they're also incorrect. Well done BBC
BBC is WOLS...
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
I'm on Android P and today I noticed an update for Google photos app. So I downloaded it and it turns out to have broke something. When u roll up or down the screen flickers now. I have since then went back before the update. Is it just mines or anyone else on P can comfirm.
same here.
3.19.0.194452507
Must be an Android P issue. I don't notice a flicker when scrolling. I even changed from days, months, etc.
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
Must be an Android P issue. I don't notice a flicker when scrolling. I even changed from days, months, etc.
Click to expand...
Click to collapse
That's what I was thinking. Hopefully in DP2 it will be fixed
Same here, I made a bug report linked below. Please add your comments.
https://issuetracker.google.com/issues/78905843
TonikJDK said:
Same here, I made a bug report linked below. Please add your comments.
https://issuetracker.google.com/issues/78905843
Click to expand...
Click to collapse
Done
Me too
Yup, me too. Total display corruption when scrolling in Google Photos 3.19 . Android P dp1. Pixel 2 XL. DP2 should be days away!
I expect the fix will come from photos no P. And I hope I'm wrong.
---------- Post added at 01:16 AM ---------- Previous post was at 01:12 AM ----------
TonikJDK said:
I expect the fix will come from photos no P. And I hope I'm wrong.
Click to expand...
Click to collapse
Changing my answer. I now see several app compatibility issues as closed pending next update. So maybe it's will too.
Good job gang. They noticed our issue and asked me for more info, which I have provided.
TonikJDK said:
Good job gang. They noticed our issue and asked me for more info, which I have provided.
Click to expand...
Click to collapse
Hell yea that's good to hear
holla420 said:
I'm on Android P and today I noticed an update for Google photos app. So I downloaded it and it turns out to have broke something. When u roll up or down the screen flickers now. I have since then went back before the update. Is it just mines or anyone else on P can comfirm.
Click to expand...
Click to collapse
Came here to check if anyone else had this issue. I deleted the data/cache. That didn't fix it, like you, I deleted the update, and it did fix it.
dratsablive said:
Came here to check if anyone else had this issue. I deleted the data/cache. That didn't fix it, like you, I deleted the update, and it did fix it.
Click to expand...
Click to collapse
I'll give that a try. Thanks for sharing
holla420 said:
I'll give that a try. Thanks for sharing
Click to expand...
Click to collapse
I had to rollback to version 3.18.0.192689168 to get it working.
uicnren said:
I had to rollback to version 3.18.0.192689168 to get it working.
Click to expand...
Click to collapse
Yup that's what I did. The above method didn't work for me.
have the same problem
but i deleted the update apk and it works again.. the last update broke the app.. i hope they will fix the issue soon
i starred the issue
I loaded up DP2(Beta Update) and let the Google Photos update, problem is gone.
dratsablive said:
I loaded up DP2(Beta Update) and let the Google Photos update, problem is gone.
Click to expand...
Click to collapse
Hmm. I had this same issue with DP2 yesterday. I actually use the camera frequently, it was bothersome enough for me to revert to Oreo.
dratsablive said:
I loaded up DP2(Beta Update) and let the Google Photos update, problem is gone.
Click to expand...
Click to collapse
Same here, it is working fine now.
Very nice and the ambient service is now fully downloading. I'm enjoying dp2 how about u guys?
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?