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.
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
deleted
This made my phone bootloop. Have you got uninstaller for this module?
MpandAUS said:
This made my phone bootloop. Have you got uninstaller for this module?
Click to expand...
Click to collapse
See the second paragraph from here. Also, really no point in using this anymore anyways since this patch was merged into aosp in May.
Related
Since at lease back in the 4.4 days of AOSP, the nexus 5 (and probably others) has had an issue with the camera when in video mode. There's a nasty green line that appears on the side of the video during playback.
It's an easy fix; just replace the file /system/lib/libmmcamera_interface.so with the one from the factory nexus image.
I have poured over the source code for this library, but I can't find out what it is that causes this anomaly nor why it is fixed in google's image, but not in the AOSP source. How can this have been an issue for so long? Am I the only one who runs self-compiled AOSP on my N5?
Anyway, does anybody have any idea what the cause is, or how to fix it in the source?
Hello!
I started searching to fix that issue this morning and i ran in to your post. Ive been building a while from aosp sources with minimal editing only, and i think this hasnt happened with 5.0.2 for me. Now that ive merged 5.1 into the source, i saw it happening again.
I checked few trusted developers vendors, blobs, etc. And i managed to make this:
https://github.com/sicknemesis/android_vendor_lge/commit/de6831773e3e083cef8d53f344f0a03f6a604268
As i write, im flashing and bootin a rom build with this commit and it seems its working correctly now.
All credits to original authors as seen in original commit! Hope this was the thing we are looking for and i see not lot of people check this Developer Discussion forum . I DO!
Gene Poole said:
Since at lease back in the 4.4 days of AOSP, the nexus 5 (and probably others) has had an issue with the camera when in video mode. There's a nasty green line that appears on the side of the video during playback.
It's an easy fix; just replace the file /system/lib/libmmcamera_interface.so with the one from the factory nexus image.
I have poured over the source code for this library, but I can't find out what it is that causes this anomaly nor why it is fixed in google's image, but not in the AOSP source. How can this have been an issue for so long? Am I the only one who runs self-compiled AOSP on my N5?
Anyway, does anybody have any idea what the cause is, or how to fix it in the source?
Click to expand...
Click to collapse
Wow, so the N5 was never intended to use the AOSP version of that library. I never checked the qcom binaries nor noticed that it was included there.
Thanks for this!
The Boot2Gecko people have a source fix for it:
https://bugzilla.mozilla.org/show_bug.cgi?id=1117662
https://github.com/mozilla-b2g/device-hammerhead/commit/c37663f828891cf7a49451a04f3f1ce7f7e5c054
Thanks. It appears that the same lack of patch exists in the M source. I'll try it when I get a chance.
First off, a little background.
The first few days after buying the Moto X I found MotoDisplay a little too sensitive and, to be honest, a little annoying that it would turn on all the time, but after a while I started getting used to it and subconsciously dependent on the way it works.
A few days ago I remembered using an application on my galaxy nexus which kind of did the same thing, and so I tried replacing MotoDisplay with one of the alternatives from the playstore. I chose AcDisplay and I really liked most of it's features (it's animations are beautiful). Except it doesn't use the IR sensors.
AcDisplay being an open source project, I thought to my self "I could probably implement a feature similar to MotoDisplay's extremely sensitive wave to wake up". So I looked for examples on how to use the IR Sensors and found none. I looked for an SDK/API and found nothing. I've looked at motorola's github and none of the repositories seemed to be what I wanted.
So the question is, how can I make a program that makes use of the Moto Xs IR sensors? Are there any resources on how to use them, or is this feature closed source and I'm not supposed to use it?
Apparently, apart from the official MotoDisplay, the only other project making use of these sensors is CM12 (which I haven't tried myself), which leads me to believe that it's not as simple as using the other, more common, sensors.
bump
evilnoxx said:
First off, a little background.
The first few days after buying the Moto X I found MotoDisplay a little too sensitive and, to be honest, a little annoying that it would turn on all the time, but after a while I started getting used to it and subconsciously dependent on the way it works.
A few days ago I remembered using an application on my galaxy nexus which kind of did the same thing, and so I tried replacing MotoDisplay with one of the alternatives from the playstore. I chose AcDisplay and I really liked most of it's features (it's animations are beautiful). Except it doesn't use the IR sensors.
AcDisplay being an open source project, I thought to my self "I could probably implement a feature similar to MotoDisplay's extremely sensitive wave to wake up". So I looked for examples on how to use the IR Sensors and found none. I looked for an SDK/API and found nothing. I've looked at motorola's github and none of the repositories seemed to be what I wanted.
So the question is, how can I make a program that makes use of the Moto Xs IR sensors? Are there any resources on how to use them, or is this feature closed source and I'm not supposed to use it?
Apparently, apart from the official MotoDisplay, the only other project making use of these sensors is CM12 (which I haven't tried myself), which leads me to believe that it's not as simple as using the other, more common, sensors.
Click to expand...
Click to collapse
You can look at the CyanogenMod CMactions source code. However, you are going to have selinux problems as you need to touch the raw driver to enable wakeups.
crpalmer said:
You can look at the CyanogenMod CMactions source code. However, you are going to have selinux problems as you need to touch the raw driver to enable wakeups.
Click to expand...
Click to collapse
That seems way to hard for me. Thank you anyway for the reply
Stagefright is very serious issue on android devices not known to many android users.
Currently I am using CM12 Nightlies on my N5.
I read about Stagefright sometime back and found that my phone has been sending and receiving thousands of SMS and MMS. So i blocked all access to CM12 Messaging app using Privacy Guard. Privacy Guard is one reason why i love CM12, loved slimrom too...
Attached are screenshots of my Messaging app and a report by Stagefright Detector.
1. How android phones are really hacked by simple SMS/MMS
2. More about Stagefright
3. XDA on Stagefright
Did google really fix this and did CM do anything about this??? I believe majority of the testing is done on N5 and other nexus devices.
this is frightening!!!
How many of you have been exposed to this???
Lordificated said:
Did google really fix this and did CM do anything about this??? I believe majority of the testing is done on N5 and other nexus devices.
Click to expand...
Click to collapse
Yes, it did. With official release of Marshmallow (build MRA58K), all CVE's, that Stagefright Detector is checking, are fixed, and device is not vulnerable. Your issue is on CM side, not Google's.
First of all, blocking MMS access on Messaging will only prevent a small portion of the exploit. Stagefright is a large library, it basically plays *every* media file (based on my knowledge). This includes stuff that browser plays (for example : webm video, like YouTube) all of these are handled by Stagefright and FFmpeg library.
But, the good thing is, the library is not exploited widely. This means there's no wide range attack (based on reports online). No need to worry, the issue is internally fixed on Google side, if you can update to latest CM nightly release the issue might be fixed.
Srandista said:
Yes, it did. With official release of Marshmallow (build MRA58K), all CVE's, that Stagefright Detector is checking, are fixed, and device is not vulnerable. Your issue is on CM side, not Google's.
Click to expand...
Click to collapse
I guess they did, on Android M...
as you said, Stagefright detector says there are no vulnerable CVEs on my N5...
Moved from CM to Stock 6.0... But I am not sure if I love the App Permissions settings of 6.0 over the Privacy Guard in CM12...
still :good:
F4uzan said:
First of all, blocking MMS access on Messaging will only prevent a small portion of the exploit. Stagefright is a large library, it basically plays *every* media file (based on my knowledge). This includes stuff that browser plays (for example : webm video, like YouTube) all of these are handled by Stagefright and FFmpeg library.
But, the good thing is, the library is not exploited widely. This means there's no wide range attack (based on reports online). No need to worry, the issue is internally fixed on Google side, if you can update to latest CM nightly release the issue might be fixed.
Click to expand...
Click to collapse
yes, i read the same about Stagefright... being a large library used for almost all media access, most of the apps we use triggers Stagefright... but as you said, now that nobody knows the extend of vulnerabilities of Stagefright, we can only prepare for what we know!
Hi there, I'm probably overstepping a bit, but at least I know every time I go trying to find ROMs for a device, I'm gonna look at threads in the ROM/Recovery/Kernel Development sub-forum for that device. Not try to find something buried in the guides or Q&A 15 pages deep behind 5732 people posting the same question over & over about whether or not VoLTE works with Jio on that phone.
So none of this is my work, it's just links to a relatively-well-working build of MM + a newer recovery than is typically linked, because I couldn't find those listed in this forum.
So anyway, the ZUK Z2 Pro seems to have an active MM Mokee build going on, which you can find here:
https://download.mokeedev.com/?device=z2pro
If they ever start in on Nougat, I assume it would show up on that page as well. Fingerprint sensor seems to work but customization of actions is GONE (just touch for back, long touch for recent, click button for home), no U-Health, built-in camera app doesn't flash (but other apps using camera API can turn it on), and vibration works through weird "route it through gamepad controller" switch... but on the upside, you can globally disable vibration if you hate it!
Meanwhile, I've seen a lot of back & forth about which version of TWRP to use here & on zukfans.eu, and it seems like with 3.0.2 builds people were getting Error 7 if they used the wrong build for the wrong ROM. Here's a link to the 3.0.3 build I've been using that seems to have solved some of thosee issues (at least I haven't hit Error 7 flashing anything), but curiously, nobody links to. The original is probably buried somewhere on the Lenovo Chinese-language forums where you need to sign in & garbage post for 3 weeks to earn enough virtual currency to unlock a download link; this one was posted by lucaam in the zukfans.eu board while replying to someone about the hardware issue where LineageOS builds will mechanically jam something in the zoom/focus/OIS part of the sensor (long story, BEST FIX EVAR - "use my recovery to install rom, open camera, force close camera app, then HIT THE SENSOR SUPER-HARD to pop it loose again so it'll work on stock roms"). Where were we? Oh yeah; TWRP 3.0.3 by those "LR.Team" guys:
https://mega.nz/#!spJgGI6T!x87tQgLCVYGb18IdaC9KTV4p7vH75KoLBqNQY3nLhrI
Hey all,
Just wanted to share a simple Magisk Module that tweaks the Ambient EQ on our phones to behave more like Apple's True Tone feature. This idea and module was originally created by @MishaalRahman and published here. As you can see the article was published in November 2019, and the structure of Magisk Modules has since changed. So, the module that you can download from that article no longer works. I've simply updated the module to be compatible with the new Magisk Module file structure and function correctly on our phones.
Instructions and Notes:
Note: This module was originally created for the Pixel 4 (Flame). Due to the Pixel 4 XL (Coral) using a different panel, this module may have unintended effects on screen color and gamma that I have not been able to test. Give it a shot if you'd like, but YMMV.
Install via Magisk Manager or flash the .zip using your favorite Kernel Manager and reboot.
The module has been submitted to the Magisk Module Repo, where it will be able to be downloaded directly from the Magisk Manager app, but it is awaiting approval.
Download (AFH)
Original Author: @MishaalRahman
Original Module and Associated Documentation: https://www.xda-developers.com/google-pixel-4-ambient-eq-tweak/
Source: https://github.com/Alcolawl/AmbientEQTweak
Thanks! I really appreciate it.
Like two months without the module working and you fixed it.
After normal installation, the performance of some apps is significantly reduced.
gyuuuu said:
After normal installation, the performance of some apps is significantly reduced.
Click to expand...
Click to collapse
I haven't noticed it
Alcolawl said:
Hey all,
Just wanted to share a simple Magisk Module that tweaks the Ambient EQ on our phones to behave more like Apple's True Tone feature. This idea and module was originally created by @MishaalRahman and published here. As you can see the article was published in November 2019, and the structure of Magisk Modules has since changed. So, the module that you can download from that article no longer works. I've simply updated the module to be compatible with the new Magisk Module file structure and function correctly on our phones.
Instructions and Notes:
Note: This module was originally created for the Pixel 4 (Flame). Due to the Pixel 4 XL (Coral) using a different panel, this module may have unintended effects on screen color and gamma that I have not been able to test. Give it a shot if you'd like, but YMMV.
Install via Magisk Manager or flash the .zip using your favorite Kernel Manager and reboot.
The module has been submitted to the Magisk Module Repo, where it will be able to be downloaded directly from the Magisk Manager app, but it is awaiting approval.
Download (AFH)
Original AuthorMishaalRahman
Original Module and Associated Documentation:https://www.xda-developers.com/google-pixel-4-ambient-eq-tweak/
Source:https://github.com/Alcolawl/AmbientEQTweak
Click to expand...
Click to collapse
Somehow after enabling this module on Android 11 beta 2.5 phone goes crazy.
I get delayed sms, delayed emails, app in the play store don't download and weather doesn't show.
Disabling an restarting fixed it , enable, restart, problem comes again
peikojose said:
Somehow after enabling this module on Android 11 beta 2.5 phone goes crazy.
I get delayed sms, delayed emails, app in the play store don't download and weather doesn't show.
Disabling an restarting fixed it , enable, restart, problem comes again
Click to expand...
Click to collapse
Wild stuff. I'd assume it's because you're using Android 11 beta. The way this works is basically an overlay for System UI, which I'm assuming has seen at least some moderate changes from Android 10 to Android 11. I'm not entirely sure why it would break things like SMS, but I would definitely assume that this isn't compatible with Android 11. This will be something I'll have to work on when Android 11 officially drops.
Alcolawl said:
Wild stuff. I'd assume it's because you're using Android 11 beta. The way this works is basically an overlay for System UI, which I'm assuming has seen at least some moderate changes from Android 10 to Android 11. I'm not entirely sure why it would break things like SMS, but I would definitely assume that this isn't compatible with Android 11. This will be something I'll have to work on when Android 11 officially drops.
Click to expand...
Click to collapse
Yeah it doesn't make any sense but at least with this beta it does that.. and it is totally easy to reproduce for me...
Any update to make it work properly with Android 11? Just asking.
Thanks!
peikojose said:
Any update to make it work properly with Android 11? Just asking.
Thanks!
Click to expand...
Click to collapse
Unfortunately I may just abandon this idea. It turns out that this module was actually responsible for the frustratingly horrible performance I was experiencing when using Snapchat. Like the phone totally locking up for 5-10 seconds sometimes for seemingly no reason. I know Snapchat is a massive piece of ****, but unfortunately, my tries to convince several groups of friends to move to a different app have been unsuccessful. After removing this module, performance was restored. Because of this, along with other reports of sluggish performance when using this module, I'll most likely discontinue working on this for Android 11.
Alcolawl said:
Unfortunately I may just abandon this idea. It turns out that this module was actually responsible for the frustratingly horrible performance I was experiencing when using Snapchat. Like the phone totally locking up for 5-10 seconds sometimes for seemingly no reason. I know Snapchat is a massive piece of ****, but unfortunately, my tries to convince several groups of friends to move to a different app have been unsuccessful. After removing this module, performance was restored. Because of this, along with other reports of sluggish performance when using this module, I'll most likely discontinue working on this for Android 11.
Click to expand...
Click to collapse
Yes. I was one of the ones that reported problems even with sms after using this module.
So sad! Thanks anyway