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
Related
Currently, Ventriloid and Mangler are non functional for the Android JB firmware. Although the Ventriloid dev has posted a temp fix in the app description, it crashes alot and will not serve much use for me. Is it possible for someone to post a fixed app or a way to access vent on JB?
Store link:
https://play.google.com/store/apps/details?id=com.jtxdriggers.android.ventriloid&hl=en
Temporary fix link:
https://code.google.com/p/ventriloid/downloads/list
Buuump. I totally need this, and many do aswell.
Metal Slug said:
Buuump. I totally need this, and many do aswell.
Click to expand...
Click to collapse
Ventriloid dev here. What issues are you having with the test version on the site? I just finished up my semester at school and will hopefully have an official release out by January, but I need some help testing.
Ventrilo for JB not working?
jtxdriggers said:
Ventriloid dev here. What issues are you having with the test version on the site? I just finished up my semester at school and will hopefully have an official release out by January, but I need some help testing.
Click to expand...
Click to collapse
Just wanted to jump in and mention that I am having issues too. Samsung SII, cm10. When I start ventriloid is initially says connecting, but then very often goes back to mobile's home screen. It then leaves a notification bar entry saying that it is connected. When you click on that, it does its two vibrates and goes off entirely. Sometimes I can get it going again, but is very fiddly. Dont know if this helps. Hope so.
London Lad
LondonLad said:
Just wanted to jump in and mention that I am having issues too. Samsung SII, cm10. When I start ventriloid is initially says connecting, but then very often goes back to mobile's home screen. It then leaves a notification bar entry saying that it is connected. When you click on that, it does its two vibrates and goes off entirely. Sometimes I can get it going again, but is very fiddly. Dont know if this helps. Hope so.
London Lad
Click to expand...
Click to collapse
Hey LondonLad, thanks for the report.
Are you using the Play Store version of the app or the Alpha on my Google Code?
jtxdriggers said:
Hey LondonLad, thanks for the report.
Are you using the Play Store version of the app or the Alpha on my Google Code?
Click to expand...
Click to collapse
Playstore version.
LondonLad said:
Playstore version.
Click to expand...
Click to collapse
Go try out the Alpha at ventriloid.googlecode.com in the downloads section and let me know how it works for you. I apologize for any lack of features in that version but it's a huge work in progress.
jtxdriggers said:
Go try out the Alpha at ventriloid.googlecode.com in the downloads section and let me know how it works for you. I apologize for any lack of features in that version but it's a huge work in progress.
Click to expand...
Click to collapse
Have downloaded and it seems to work well. (Did loose the Ventriloid icon though!) One comment: One must tick the box Enable Global Push to Talk in order to see key. That is fine, but it does cover up part of you keyboard if you, for example, need to type in a password for a channel. Not a problem, but thought I would at least mention it.).:good:
LondonLad said:
Have downloaded and it seems to work well. (Did loose the Ventriloid icon though!) One comment: One must tick the box Enable Global Push to Talk in order to see key. That is fine, but it does cover up part of you keyboard if you, for example, need to type in a password for a channel. Not a problem, but thought I would at least mention it.).:good:
Click to expand...
Click to collapse
I'm glad it's working for you I'm working on a complete UI overhaul and that global push to talk was more or less a proof of concept for being able to talk outside of the app. Android has limitations for hardware key interception that won't allow push to talk while the app is in the background, so hopefully people will enjoy this new button. It will eventually be a bar with other options that can be hidden. Thanks so much for testing, I'm glad the ICS/JB fix is working.
jtxdriggers said:
I'm glad it's working for you I'm working on a complete UI overhaul and that global push to talk was more or less a proof of concept for being able to talk outside of the app. Android has limitations for hardware key interception that won't allow push to talk while the app is in the background, so hopefully people will enjoy this new button. It will eventually be a bar with other options that can be hidden. Thanks so much for testing, I'm glad the ICS/JB fix is working.
Click to expand...
Click to collapse
Thank you for your work on this. It is helping a lot of people! (I will make a donation shortly.)
LondonLad said:
Thank you for your work on this. It is helping a lot of people! (I will make a donation shortly.)
Click to expand...
Click to collapse
I greatly appreciate it I need to get a Bluetooth headset for testing, but Christmas and next semester's tuition has completely drained me haha. Let me know if you have any other issues or feature requests!
Turns your phone into a touchpad mouse for PC! Works with LOS14.1 by bigsupersquid
Changelog:
171116:simulated touchpad support. thx pelya
171127:Now with dt2w support. Goodbye broken power button. thx showp1984
Click to expand...
Click to collapse
Download:
Code:
[URL="https://www.androidfilehost.com/?fid=962021903579495061"]AFH[/URL]
Flash:
Code:
[COLOR=Black]fastboot flash boot <boot_img_here>[/COLOR]
For Keyboard app, always download from Play store/Github
Root required, Magisk recommended.
I'm either trying to port DT2W for this device, but no luck. Done.
Anyway you may give me some feedback, source below.
Source: Github
XDA:DevDB Information
HID-compliant TP/KB kernel, Kernel for the HTC Desire 816
Contributors
Aerotinge, bigsupersquid, pelya, showp1984
Kernel Special Features:
HID-compliant driver,Doubletap2wake
Version Information
Status: Beta
Beta Release Date: 2017-11-16
Created 2017-11-16
Last Updated 2017-11-27
Dammit I finally make dt2w running on this himax touchscreen driver.
No one done this before and I know little about C. That's...awwww
Enjoy!
Hi, Thank you for your work, Do you tell me i can use this for HTC816 DWG or no?
faezehya said:
Hi, Thank you for your work, Do you tell me i can use this for HTC816 DWG or no?
Click to expand...
Click to collapse
As "a5_ul" is there in the title, I'll say no.
But you can have a try. It won't explode (I guess so.)
Aerotinge said:
As "a5_ul" is there in the title, I'll say no.
But you can have a try. It won't explode (I guess so.)
Click to expand...
Click to collapse
The dts might be a little different.
Overall it'll probably work.
I hadn't seen this, nice work!
If you don't mind I'd like to import your changes, both the dt2w and the hid configs.
initial feedback, it works on my DUG
going to test it all day tomorrow
Edit: ok nvm it works for some time then touch screen stops working when the phone goes in deep sleep
bigsupersquid said:
The dts might be a little different.
Overall it'll probably work.
I hadn't seen this, nice work!
If you don't mind I'd like to import your changes, both the dt2w and the hid configs.
Click to expand...
Click to collapse
can this be ported fow dwg/dug?
Roberto Nigel said:
can this be ported fow dwg/dug?
Click to expand...
Click to collapse
If I import the kernel patches and it all works right, it'll be fine when it's built in to LOS.
Roberto Nigel said:
initial feedback, it works on my DUG
going to test it all day tomorrow
Edit: ok nvm it works for some time then touch screen stops working when the phone goes in deep sleep
Click to expand...
Click to collapse
Yes I found that issue recently...
I always connect the phone to charger so I didn't found it at the first time.
It seems to be something about deep doze mechanism, which a noobie like me can't solve alone, sorry.
I would port a fix if someone found a solution on other devices.
Aerotinge said:
Yes I found that issue recently...
I always connect the phone to charger so I didn't found it at the first time.
It seems to be something about deep doze mechanism, which a noobie like me can't solve alone, sorry.
I would port a fix if someone found a solution on other devices.
Click to expand...
Click to collapse
I'll look into it, dt2w is pretty cool and I'd like to incorporate it
No guarantee of fixing anything of course.
bigsupersquid said:
If I import the kernel patches and it all works right, it'll be fine when it's built in to LOS.
Click to expand...
Click to collapse
welp if that helps, after removing android system from battery optimization the touch screen doesnt die but dt2w is not consistant, some times it stops and have to open from the power button for it to work again
Roberto Nigel said:
welp if that helps, after removing android system from battery optimization the touch screen doesnt die but dt2w is not consistant, some times it stops and have to open from the power button for it to work again
Click to expand...
Click to collapse
Excellent observation and a perfect place to post it.
Kudos!
Can we get n overclock kernel...
Hey bro PLEASE make it work for a5 dug/DWG...I f**king love d2tw feature
In exchange can I do something for you ?donations ? Any help? I will do anything XD just please make it work on a5 dug/dwg models
@AnjoVingador sir can u please maintain are pixel experience rom because this rom is quite stable but some of the bugs are there to be solved please sir
+1
+1
I would really appreciate, if it conitnues.
+1
Yes, it will. New build soon
AnjoVingador said:
Yes, it will. New build soon
Click to expand...
Click to collapse
Thank you so much sir...one more request can you please bring always on and ambient display if possible...thanks in advance
AnjoVingador said:
Yes, it will. New build soon
Click to expand...
Click to collapse
Also some gesture and if OTA update could be possible
sonarkrishna said:
Also some gesture and if OTA update could be possible
Click to expand...
Click to collapse
Adding Always on display is ridiculous on our phone as the display is not done for it. Ambiant display is already there if you means the screen showing notifications while on black when receiving. For gestures, what do you mean? It has dt2w and that is the only gesture we do have on this device. For ota I already talked about it with him and he don't know if it will come. It is not up to him but it is the rom creator that must do it
benplay64 said:
Adding Always on display is ridiculous on our phone as the display is not done for it. Ambiant display is already there if you means the screen showing notifications while on black when receiving. For gestures, what do you mean? It has dt2w and that is the only gesture we do have on this device. For ota I already talked about it with him and he don't know if it will come. It is not up to him but it is the rom creator that must do it
Click to expand...
Click to collapse
Okay... Are you using pixel experience rom if yes will you post to arnova8g2 for portrait mode to work because it has a full hardware support to work. And post him with logcat
sonarkrishna said:
Okay... Are you using pixel experience rom if yes will you post to arnova8g2 for portrait mode to work because it has a full hardware support to work. And post him with logcat
Click to expand...
Click to collapse
Yes I'm on PE since its release. But no need to post anything about portrait mod, Mrhacker seems to have resolved it. So it a question of time for us and hard work for him before we do have it on all the other roms. Wait patiently... Also I don't which bugs you're mentioning. I don't have any. Not apparent at least
benplay64 said:
Yes I'm on PE since its release. But no need to post anything about portrait mod, Mrhacker seems to have resolved it. So it a question of time for us and hard work for him before we do have it on all the other roms. Wait patiently... Also I don't which bugs you're mentioning. I don't have any. Not apparent at least
Click to expand...
Click to collapse
More stable I want
sonarkrishna said:
Okay... Are you using pixel experience rom if yes will you post to arnova8g2 for portrait mode to work because it has a full hardware support to work. And post him with logcat
Click to expand...
Click to collapse
Finally finally portrait mode is succeeded to work on lovely Lenovo z2 plus special thanks to @mr.hacker
Now eagerly waiting for portrait mode on pixel experience rom
Pixel Experience is Surely the Best Rom for our device , maybe it's just me who finds it but still I would request the devs to pls maintain it further. BTW by what time should we expect a new build?
You can enable fast charging 3.0 in this pixel experience rom?
Manthanmk1 said:
You can enable fast charging 3.0 in this room?
Click to expand...
Click to collapse
How is it so..?
Finally portrait mode is on its way to Lenovo z2 plus
well hello to everyone
i hope you all loving camera and having good time with it do post your best settings and help guys who having issues with camera settings.
so i have investigated camera hal sources and now it looks like all is okay for releasing and open source for community
so here is the link to camera hal sources https://github.com/omni-zuk/device_z...oid-8.1/camera
all commits are open here and ready for cherry-pick https://github.com/omni-zuk/device_z...0a9787bab45b33 well developers needs to revert this commit because this commit only for omnirom which don;t need project pathmap so reverting it will work for other roms and make hal compatible for other roms without issues.
thanks to everyone i got very positive response from the users on xda and telegram so big thanks to all of you. @AnjoVingador
Okay I'm confused. Who is the new maintainer of PE?
Want development of this rom to continue so bad...
Beepboop_blues said:
Okay I'm confused. Who is the new maintainer of PE?
Want development of this rom to continue so bad...
Click to expand...
Click to collapse
Keep your opinion towards you if u don't want to use it then just stay away
If no one can, I can build?
sonarkrishna said:
Keep your opinion towards you if u don't want to use it then just stay away
Click to expand...
Click to collapse
Hostile
Hey folks!
I guess some of you encountered some weird Wifi bugs on the OP5, espacially delayed notifications and so on. @joshuous found out that this is due to a specific line/value in the /system/etc/wifi/WCNSS_qcom_cfg.ini (Nougat only) | /system/vendor/etc/wifi/WCNSS_qcom_cfg.ini file (Oreo), why he removed this for RenderZenith kernel (go thank him here ). So this Magisk module goes even a step further: It replaced the whole file of OnePlus by the stock Pixel 2 file. This line/value I am speaking of respectively @joshuous has found is not present in the stock Pixel file. Therefore I haven't encountered any delayed notifications. This mod has been tested now for several months, on OOS 4.x.x, OOS 5.x.x, OOS 9.x.x (means on Nougat, Oreo and Pie), on AOSP custom Roms, even back on my former HTC 10, Wifi always has been working fine without issues when this mod has been installed. So try it and enjoy.
Note:
This is for the OnePlus 5/T only, and I can't provide any help if you're using this on other phones. It might or might not work. It will most probably work on Pixel/Nexus devices, too. And it could work on every phone which runs AOSP, or not. It might work on other stock Roms than OOS. Who knows? So don't blame me if it doesn't. That's why I created this as a Magisk module, you can simply uninstall it again.
You have been told.
Update:
Officially confirmed working on the OnePlus 6 (running AICP), too, by @wartomato ! Thanks for the testing!
Thanks and credits:
@joshuous for his findings
@topjohnwu for Magisk
@shadowstep for his findings
Google...for being Google
Source code:
https://github.com/RogerF81/pennygetyourownwifi
Can I use this for the OnePlus 5T?
Interesting. I will give this a try. Too bad nobody knows how to replace all the One Plus firmware with stock Android code. Their firmware still causes issues even if you don't run OOS.
MrPhilo said:
Can I use this for the OnePlus 5T?
Click to expand...
Click to collapse
Yes of course. Generally, it should be universal, but I tested it only on the OP5 and the HTC 10.
jhs39 said:
Interesting. I will give this a try. Too bad nobody knows how to replace all the One Plus firmware with stock Android code. Their firmware still causes issues even if you don't run OOS.
Click to expand...
Click to collapse
Yeah, but for me, this module is an improvement already
Ok, so far so good. Been trying some things out and it seems to definately be better. For example, pushing from the PC to the phone from pushbullet is instantaneous (on stock sometimes the notification only comes 2-10 seconds after the push itself).
Will keep testing.
Thank you very much.
RogerF81 said:
Yes of course. Generally, it should be universal, but I tested it only on the OP5 and the HTC 10.
Yeah, but for me, this module is an improvement already
Click to expand...
Click to collapse
It does seem to be so far. WiFi works much better with screen off.
fjsferreira said:
Ok, so far so good. Been trying some things out and it seems to definately be better. For example, pushing from the PC to the phone from pushbullet is instantaneous (on stock sometimes the notification only comes 2-10 seconds after the push itself).
Will keep testing.
Thank you very much.
Click to expand...
Click to collapse
jhs39 said:
It does seem to be so far. WiFi works much better with screen off.
Click to expand...
Click to collapse
Nice:highfive:
Thank you for this!
Is it just me or this makes my wifi also faster? I'm impressed. Thanks for sharing!
Sent from my OnePlus 5 using XDA Labs
IlD4nX said:
Is it just me or this makes my wifi also faster? I'm impressed. Thanks for sharing!
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
I'm not sure if it's faster, but it should be more stable at least
I am impressed. I had problems behind the wall. Everything is awesome now. Must have module ! Thanks . Screenshot with worse result is before.
Hefko said:
I am impressed. I had problems behind the wall. Everything is awesome now. Must have module ! Thanks . Screenshot with worse result is before.
Click to expand...
Click to collapse
Whoah that's a big difference!
Wrong post...Wrong thread...sorry guys
In terms of speed and latency tests, there is no statistically significant difference on my WiFi network. Not sure about stability and such yet
@RogerF81 The WCNSS_qcom_cfg.ini file for me is located in /system/vendor/etc/wifi/ and not in /system/etc/wifi/ (which is where your module is placing the file at). Can you please check if this is indeed how it's supposed to be?
As a side note, I manually replaced the WCNSS_qcom_cfg.ini file from your module via root explorer in /system/vendor/etc/wifi/, rebooted, and faced no issues with wifi whatsoever.
shadowstep said:
@RogerF81 The WCNSS_qcom_cfg.ini file for me is located in /system/vendor/etc/wifi/ and not in /system/etc/wifi/ (which is where your module is placing the file at). Can you please check if this is indeed how it's supposed to be?
As a side note, I manually replaced the WCNSS_qcom_cfg.ini file from your module via root explorer in /system/vendor/etc/wifi/, rebooted, and faced no issues with wifi whatsoever.
Click to expand...
Click to collapse
Ohhh indeed! Thanks for the heads-up! This must have changed from Nougat to Oreo and I haven't noticed it yet I even haven't noticed that though @joshuous has made his change in WCNSS_qcom_cfg.ini file, but haven't looked at the file path xD Thanks again, I'll change the module accordingly!
Update!
Thanks for the findings by @shadowstep! (see above this post). So actually it seems, in Oreo, the file path for the WCNSS_qcom_cfg.ini has changed, and I haven't noticed it yet and I guess I would have never noticed it without the heads-up by @shadowstep So thank you for your help! From now on, there will be 3 files:
stock Pixel2 Oreo file for users on Nougat (should work without issues)
stock Pixel2 file for Oreo users (correct file path now )
MOD of the Pixel2 file for Oreo users, where I experimentally change some values; for testing only, don't blame me if something doesn't work as it should
Changelog for Mod v1:
enabled Wifi channel bonding for 2,4 GHz
change Phy Mode from 0=Auto to 9=ac
change the Maximum Receive AMPDU size from gVhtAmpduLenExponent=7 to 4 (as 7 isn't even a valid value according Google's description??)
RogerF81 said:
Update!
Thanks for the findings by @shadowstep! (see above this post). So actually it seems, in Oreo, the file path for the WCNSS_qcom_cfg.ini has changed, and I haven't noticed it yet and I guess I would have never noticed it without the heads-up by @shadowstep So thank you for your help! From now on, there will be 3 files:
stock Pixel2 Oreo file for users on Nougat (should work without issues)
stock Pixel2 file for Oreo users (correct file path now )
MOD of the Pixel2 file for Oreo users, where I experimentally change some values; for testing only, don't blame me if something doesn't work as it should
Changelog for Mod v1:
enabled Wifi channel bonding for 2,4 GHz
change Phy Mode from 0=Auto to 9=ac
change the Maximum Receive AMPDU size from gVhtAmpduLenExponent=7 to 4 (as 7 isn't even a valid value according Google's description??)
Click to expand...
Click to collapse
You're most welcome! I've actually been following (stalking? ) your GitHub profile and have been using this wifi configuration file since long now. I remembered looking for it initially in /system/etc/wifi/ location but I couldn't find it there. So I decided to look for the file in the same (parallel) location under /vendor and there it was! Anyway, great you've rectified the location and pushed the update quickly! :highfive:
Always using the modded version and everything is great! :good:
shadowstep said:
You're most welcome! I've actually been following (stalking? ) your GitHub profile and have been using this wifi configuration file since long now. I remembered looking for it initially in /system/etc/wifi/ location but I couldn't find it there. So I decided to look for the file in the same (parallel) location under /vendor and there it was! Anyway, great you've rectified the location and pushed the update quickly! :highfive:
Always using the modded version and everything is great! :good:
Click to expand...
Click to collapse
I see, a really good finding, which I wouldn't have noticed myself I guess :highfive:
And thank you for your feedback, I'm running the modded version now as well and it works well for me, too so far
Here too even if my wifi has up and down performances... But let's try for some days!! Thank you for your efforts!
Sent from my OnePlus 5 using XDA Labs
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