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
I've got Joe's DU right now, will this affect me?
kingbri said:
I've got Joe's DU right now, will this affect me?
Click to expand...
Click to collapse
Check his git to see if he pulled the fix in or not
Updated trees today I'll push tomm
Just installed on latest lineage .. it's perfect!! Thank you so much
Any word on a fix for the sound bug on 8.1? After a couple of hours the phone stops playing ringtones and notifications (while other sounds work ala YouTube Spotify). A reboot fixes it temporarily.
Related
Their website states they have or are releasing an android version for xbmc. I can't seem the find the beta apk or zip file to install it (if there is one that works for it yet.) This to me is the "killer app" any help here would be greatly appreciated. thanks.
rp201 said:
Their website states they have or are releasing an android version for xbmc. I can't seem the find the beta apk or zip file to install it (if there is one that works for it yet.) This to me is the "killer app" any help here would be greatly appreciated. thanks.
Click to expand...
Click to collapse
Look around a bit. There's a thread for this already.
Hey XBMC fans just a head up the dark screen isue in cm7 has been fixed, devs had an issue with touchscreen aswell but it has just been fixed too:
http://www.xbmcandroid.com/forums/xbmc-android-compatibility/47-6.htm
Check the page it is now the oficial web page for XBMC Android, enjoy!
Running XBMC on my nook tablet right now...
~ V
To bad videos arent working with this right now on the nook tablet. I am running CM7 and the updated version runs but videos arent playing so its sorta useless to me right now. Will be keeping an eye on it tho.
I am working on getting an updated build completed with the black screen fix. However, the main XBMC project has merged a few large changes that are causing my builds to fail right now. If you keep an eye on the main XBMC XDA thread or www.xbmcandroid.com/forums I will be posting a link once a build is known working.
The black screen issue is fixed in the version that lavero.burgos linked to. The issue is that videos wont play weather they are from video addons or over a dlna server so the app is pretty much useless right now even tho you can mess around with it.
Montisaquadeis said:
The black screen issue is fixed in the version that lavero.burgos linked to. The issue is that videos wont play weather they are from video addons or over a dlna server so the app is pretty much useless right now even tho you can mess around with it.
Click to expand...
Click to collapse
The video playback problem should be addressed in a more recent patch. The problem is the patch was completed shortly after the upstream sources broke and we've not been able to get a successful compile with the new patch in awhile. An updated version is forthcoming, just with an unknown release date currently.
kemonine96 said:
The video playback problem should be addressed in a more recent patch. The problem is the patch was completed shortly after the upstream sources broke and we've not been able to get a successful compile with the new patch in awhile. An updated version is forthcoming, just with an unknown release date currently.
Click to expand...
Click to collapse
I managed to get a few stable builds with djeman's black screen fix included. Below are the links, if you meet with or success or failure let us know.
NEON
xbmcapp-armeabi-v7a-debug-2012-09-26-neon-test-black-screen-b1760a3e0ee716d6efe7dbc9a3829441410dead8
No NEON
xbmcapp-armeabi-v7a-debug-2012-09-26-no-neon-test-black-screen-9f7d08d890c550e8fff349532f1d0a7d2b7a279f
The black screen issue has been fixed for a while for me on the Nook Tablet running CM7 the issue was with videos not playing at all and I have been watching for a fix for that and from what I gather there is a patch but it hasn't been implemented yet becuase the source was broken upstream from what I read.
Montisaquadeis said:
The black screen issue has been fixed for a while for me on the Nook Tablet running CM7 the issue was with videos not playing at all and I have been watching for a fix for that and from what I gather there is a patch but it hasn't been implemented yet becuase the source was broken upstream from what I read.
Click to expand...
Click to collapse
That is true. I held an updated build with a fix for video playback until upstream was stable again.
My previous post with the links is an updated build that should address the black screen problem 100% including video playback.
Video playback seems to be fixed with the new neon version but I still get a black screen when I minimize the status bar in CM7 which is getting annoying since the status bar overlaps the bottom of XMBC and the default theme sort of doesnt flow well. Meaning would it be possible to get some more themes added to it?
Montisaquadeis said:
Video playback seems to be fixed with the new neon version but I still get a black screen when I minimize the status bar in CM7 which is getting annoying since the status bar overlaps the bottom of XMBC and the default theme sort of doesnt flow well. Meaning would it be possible to get some more themes added to it?
Click to expand...
Click to collapse
There is a touched skin included in the default builds that is setup better for touch screen devices. If you want another skin, the xbmc wiki has good information on where to find skins and how to install them. The android version of XBMC is generally the same as the non-android versions. If you need further information the xbmc wiki is a really good starting point. There is also a main thread on XDA that has more information about things beyond the black screen issue.
Running Sgt7 with 1.2 ghzcpu performance. Quality over WiFi is still lacking. Any recommended settings like gpu2d, hardware overlay etc to boost performance. I also am assuming nt is neon build. Thanks
hi its aonly something small but my phone just started doing it
im trying to take screen shots to help with bug squashing
it was fine but now when i press the volume controls together i get a volume control at the top of the page with the screen shot
is there a way of disabling the volume showing up or am i pressing the wrong buttons!
see attached
thank you for help i can help get some more bugs squashed when ive fixed this
That's a known problem but it has just been fixed in the latest vivid-proposed images. The fix has also been in the RTM images for a while.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
im running 14.10 r16
is this the best version to run you think?
i dont get facebook notifications aswell is this fixed on other versions ...
wayneward said:
im running 14.10 r16
is this the best version to run you think?
i dont get facebook notifications aswell is this fixed on other versions ...
Click to expand...
Click to collapse
Yes, it's definitely the best version to run if you want to use it as a daily driver. You should get an update about next week which fixes the screenshot issue.
Regarding the notifications: Yes, there's a real problem with that.
Actually, I submitted patches for that issue some time ago, but nobody has been reviewing them for more than two months. I've almost lost hope that this will ever happen...
If you want to increase the problem's importance, please select that the following 4 bugs affect you:
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405645
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405646
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405649 (Leaving a comment here stating how annoying you find the bug would definitely help as well!)
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405651
You can use the Ubuntu One account from your phone to log in.
Maybe that creates some pressure so that the patches will eventually be merged.
thats great what will the update come down as a update to the system?
nikwen said:
Yes, it's definitely the best version to run if you want to use it as a daily driver. You should get an update about next week which fixes the screenshot issue.
Regarding the notifications: Yes, there's a real problem with that.
Actually, I submitted patches for that issue some time ago, but nobody has been reviewing them for more than two months. I've almost lost hope that this will ever happen...
If you want to increase the problem's importance, please select that the following 4 bugs affect you:
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405645
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405646
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405649 (Leaving a comment here stating how annoying you find the bug would definitely help as well!)
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405651
You can use the Ubuntu One account from your phone to log in.
Maybe that creates some pressure so that the patches will eventually be merged.
Click to expand...
Click to collapse
@wayneward Yes, it will be an OTA update. You'll receive a notification once it's available.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Now we have 14.10 r21 great improvement from r20, and screenshot works fine (vol+ and vol -)
Working a treat
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Nice! I just flashed UT on my N4 two days ago and everything online says screenshot isn't functional yet. Glad I found this.
Sent from Ubuntu Touch via Forum
Let us get back once the CM14 nightlies start
Unofficial CM14 builds based on CyanogenMod + Grarak + Cherry-pick from CyanogenMod review stream
Facts:
Added 1 blob from OOS 3.1.0 to get the build working (Grarak is aware of it)
No extra features added, please do not request (still a n00b here)
Focus is more on debugging and hopefully help Grarak
Why is it not my daily driver though it is stable enough for a daily driver:
Unable to deactivate a SIM (just my itch)
Video recording does not work (Footej works but I want the stock camera to work: Will debug)
Busy to be able to spend more time debugging (especially with many other components changing rapidly)
Note:
Thank you all for being nice on this thread
hackworks said:
Unofficial builds of CM13 & AOSPA for OnePlus 2 with rotation vector fix. Please feel free to test it *only* for rotation vector bug (missing arrow in Google maps). Both builds are updated to latest source from their corresponding repositories.
AOSPA: https://www.androidfilehost.com/?w=files&flid=101343
CM13: https://www.androidfilehost.com/?w=files&flid=101350
CM13 changeset in review: http://review.cyanogenmod.org/#/c/157838/
AOSPA change (could not submit for review): http://pastebin.com/x9mMHzaq
Since this problem plagued us for a long time, I thought of sharing the builds for wider testing. Please be gentle, this is the first time I have shared a ROM that I have built
[All credits to the awesome hackers working on CM & AOSPA]
Click to expand...
Click to collapse
i would say, your hack is working just like your username..
Is it possible for you or anyone to make a flashable zip of the fix...!?
Would be much better and convenient
We can use it on any ROM and will not restricted to use above 2 ROMs only
Mohit31 said:
Is it possible for you or anyone to make a flashable zip of the fix...!?
Would be much better and convenient
We can use it on any ROM and will not restricted to use above 2 ROMs only
Click to expand...
Click to collapse
The change is in the framework. The part of the code calls into proprietary Qualcomm sensor service process to get a list of hardware sensors. In theory, this can be intercepted and filtered to ignore rotation vector sensor from hardware. This will let existing code in framework use the AOSP fusion sensor based implementation to get the values.
I have done something similar by intercepting IO requests to speed up IO over network
hackworks said:
The change is in the framework. The part of the code calls into proprietary Qualcomm sensor service process to get a list of hardware sensors. In theory, this can be intercepted and filtered to ignore rotation vector sensor from hardware. This will let existing code in framework use the AOSP fusion sensor based implementation to get the values.
I have done something similar by intercepting IO requests to speed up IO over network
Click to expand...
Click to collapse
Lol... It all went above my head
I think the answer is, it's not possible, right?
Thank you very much. It's working for me.
(I guess next/about next will have the fix, too. The existing commit only has to be merged)
Great work! This bug has been present since ever.
Sent from my ONE A2003 using Tapatalk
Todays build doesn't have the fix already. Am I right?
PeterImmel said:
Todays build doesn't have the fix already. Am I right?
Click to expand...
Click to collapse
Getting a patch merged is a slow process especially with almost all of CM devs focussing on 'N'. I will make a new build available with patch to hide signal for deactivated SIM in the status bar (when I get back home from work). There are/were 2 issues bugging me for a long time.
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Build updated with latest changes as on 24th Aug 2016 (21.00): https://www.androidfilehost.com/?fid=24686680535466503
hackworks said:
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Build updated with latest changes as on 24th Aug 2016 (21.00): https://www.androidfilehost.com/?fid=24686680535466503
Click to expand...
Click to collapse
That's awesome
Great work
Thanks a ton..!!
hackworks said:
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Click to expand...
Click to collapse
You 're the man! Back to CM13 because of your fixes. Many thanks!
hackworks said:
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Build updated with latest changes as on 24th Aug 2016 (21.00): https://www.androidfilehost.com/?fid=24686680535466503
Click to expand...
Click to collapse
Any chance of fixing loudspeaker echo, WhatsApp voice note not loud and random vibrations due to dt2w?
With these fixed, CM will be bug free.
Sent from my ONE A2003 using Tapatalk
@hackworks Has the rom been built with latest aospa code?
You have fixed some of the very irritating bugs..
I wonder if you can do your magic on this issue as well..
http://forum.xda-developers.com/showpost.php?p=67812802&postcount=1554
Yea. :/
This has still not been fixed.
http://forum.xda-developers.com/showpost.php?p=67812802&postcount=1554 @hackworks Please have a look.
P.S. This issue isn't present on AOSPA. So maybe that'll help.
Can i flash Xposede Framework?
Gesendet von meinem ONE A2003 mit Tapatalk
John-J.Hammy said:
Can i flash Xposede Framework?
Gesendet von meinem ONE A2003 mit Tapatalk
Click to expand...
Click to collapse
It is just CM13 with the 2 fixes. All that applies to CM13 or AOSPA remains valid on these builds
Mohit31 said:
You have fixed some of the very irritating bugs..
I wonder if you can do your magic on this issue as well..
http://forum.xda-developers.com/showpost.php?p=67812802&postcount=1554
Click to expand...
Click to collapse
n00b here. No magic, just learning. I am working on using a cleaner approach to hide the SIM signal icon. Once done, will explore other areas
raburs said:
@hackworks Has the rom been built with latest aospa code?
Click to expand...
Click to collapse
Sorry for not responding earlier, I have uploaded a new build which is based on latest source as on today 26th Aug 2016 (night) for both CM13 & PA.
I tried my hands in Java code by implementing an event based mechanism to disable the SIM icon when it is disabled - Just ended up in flickering display and a SystemUI crash! Guess, I should just stick to C/C++ where I have spent most of my programming life (~18 yrs)! Summary: Will pick areas/bugs based programming language, no time to learn Java
Hello everyone ,
So this will now be one of the most important place for you guys
This is going to be the QnA thread where you guys can ask any doubts or questions or place a review or anything that some how relates to Xiaomi Redmi 5 development then Simply post it here I will come and answer all the questions
It maybe of my roms , or kernels or it maybe developed by someone else but if you faith me and expect some good solutions to your doubt then come on and start posting your questions
Even if I get some good tips to optimize your device then I will post those here
So let's get started
Pixel Experience Calling Issue
Shreejoy Dash said:
Hello everyone ,
So this will now be one of the most important place for you guys
This is going to be the QnA thread where you guys can ask any doubts or questions or place a review or anything that some how relates to Xiaomi Redmi 5 development then Simply post it here I will come and answer all the questions
It maybe of my roms , or kernels or it maybe developed by someone else but if you faith me and expect some good solutions to your doubt then come on and start posting your questions
Even if I get some good tips to optimize your device then I will post those here
So let's get started
Click to expand...
Click to collapse
Hi, I loved using the Pixel Experience ROM. I faced a couple of issues, and had to revert back to rooted stock rom.
Issues:
1. FM Radio doesn't work. Minor issue.
2. Camera: I understand that Camera2API is enabled by default in this ROM. All is good except when I use the camera built in Whatsapp. If the flash is not enabled, the capture comes with a green overlay which is not at all usable; this happens in both front and rear camera. The photo is fine when flash is enabled. No issues in the stock camera included in the rom and opencamera app.
3. When I call someone, the in-call timer doesn't start when they answer the phone, also the Hold & Add Call buttons are not available and call waiting is not functional. It is as if the device would not register if the call has been answered. I use Jio as my only sim so I could not tell if it is an issue specific to Volte calling. Things are fine in case of incoming calls. This is a major issue and I had to revert back to stock rom with Magisk because I was not getting calls. I saw other posts on the forum with this issue.
Thanks.
Same issues here PE with nano kernel 3.1 beta
Tried the April build of PE
himodyuti said:
Hi, I loved using the Pixel Experience ROM. I faced a couple of issues, and had to revert back to rooted stock rom.
Issues:
1. FM Radio doesn't work. Minor issue.
2. Camera: I understand that Camera2API is enabled by default in this ROM. All is good except when I use the camera built in Whatsapp. If the flash is not enabled, the capture comes with a green overlay which is not at all usable; this happens in both front and rear camera. The photo is fine when flash is enabled. No issues in the stock camera included in the rom and opencamera app.
3. When I call someone, the in-call timer doesn't start when they answer the phone, also the Hold & Add Call buttons are not available and call waiting is not functional. It is as if the device would not register if the call has been answered. I use Jio as my only sim so I could not tell if it is an issue specific to Volte calling. Things are fine in case of incoming calls. This is a major issue and I had to revert back to stock rom with Magisk because I was not getting calls. I saw other posts on the forum with this issue.
Thanks.
Click to expand...
Click to collapse
I tried the April build of PE and unfortunately, these issues are still there. I cannot shake the feeling that I am doing something wrong. Are we supposed to flash anything else along with the ROM so that these issues would go away?
I have a little doubt.
Shreejoy Dash said:
Hello everyone ,
So this will now be one of the most important place for you guys
This is going to be the QnA thread where you guys can ask any doubts or questions or place a review or anything that some how relates to Xiaomi Redmi 5 development then Simply post it here I will come and answer all the questions
It maybe of my roms , or kernels or it maybe developed by someone else but if you faith me and expect some good solutions to your doubt then come on and start posting your questions
Even if I get some good tips to optimize your device then I will post those here
So let's get started
Click to expand...
Click to collapse
I have a little doubt. Does Lineage OS 14.1 will still be able to boot on our Rosy?
Lineage
Deathalw4ys said:
I have a little doubt. Does Lineage OS 14.1 will still be able to boot on our Rosy?
Click to expand...
Click to collapse
Yes you can but I don't think there is an official Lineage ROM for Rosy. There is an unofficial available on XDA. There are a couple of other options that you can try. E.g. Resurrection Remix, crDroid, Pixel Experience, CyanogenMod etc.
why I can't flash gsi roms?
everytime I flash a gsi it boots to bootloader..
and another problem..
I cannot connect my device to my pc..
when i connect to pc it charges but doesn’t show the Notification light and in my pc it says unknown device..
I tried to update device driver but it says driver is upto date.. I tried installing drivers from online but still same problem..
and in my phone there shows no option to choose mtp or anything like that too...
any solution?
Hey all, I have been unable to use the front camera in any video chat app (Viber, messenger, duo) since I got the phone a couple months ago.
The front camera turns itself off during the call and you have to manually turn it back on continuously.
If you search the OnePlus Nord 2 forums you will find many references to this issue.
I have also submitted a support ticket and provided all the debugging information that was requested from me, but the problem just remains there without any solution for 5 months (from initial user references)
Does anybody else face the same issue or have any ideas?
No problem here , front facing camera calls (teams, whatsapp, telegram, etc...) works correctly even for long time periods
Pouic said:
No problem here , front facing camera calls (teams, whatsapp, telegram, etc...) works correctly even for long time periods
Click to expand...
Click to collapse
Hi! Could you share some info regarding model number and build version?
Same thing here on EU vers. A15 , front camera functionality is flawless
I also have the version DN2103_11_A.15 but I am heavily experiencing the issue.
Have you tried for testing a 5 min call with Duo?
More people also report it in the forums:
eg:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
I am surprised that nobdy here has this front-camera problem, while it is the most frequently reported problems in the OnePlus forums...
After a chat with support, it also seems that they admitted that it is a known hardware issue and device needs repair
I have the same issue. When using messenger camera it's stop working all the time. It's really annoying. Phone it's new. Do You think I can return device at is factory issue ?
zawiszak85 said:
I have the same issue. When using messenger camera it's stop working all the time. It's really annoying. Phone it's new. Do You think I can return device at is factory issue ?
Click to expand...
Click to collapse
Hey, sorry for the late reply but just saw the message.
I eventually had mine returned and motherboard replaced, which solved the issue.
However, I can't tell you whether in recent OS updates it was also resolved somehow from software...