Database Develop

Build camera/camcorder/video for eclair/froyo.

I need a straight answer as it's possibly the one thing I can't figure out.
For eclair, NCommander fixed camera, but camcorder and video were broken from a straight build from AOSP.
CM later fixed these, but I never quite figured out how. Then everybody else started getting the camera fixed on their roms (by pulling a couple libs, I assume), but I myself couldn't figure out how the heck it was done, where an alternate source was available, or even an explanation of exactly what was broken/how it was fixed, etc. Same went for video playback/hw acceleration.
Now, on froyo, camera is broken again and NCommander's camera won't work either. It's been fixed by other people, but when I ask around, there seems to get a reluctance and I never really get an answer (and don't give me the "you're not asking the right question" line, I'm being pretty straightforward).
I need somebody here who has some knowledge as to why/how camera/hw is not working and how to fix it. I don't need libs. I need to know how to get the thing built from AOSP, why it breaks, and what I should look out for in the future, should it break again.
As far as I can tell, the problem is that the qcomm proprietary parts are outdated (for dream, last were 1.6 and eclair/froyo break compatibility with those libraries). Those libraries have to be linked-to at compile time of other hardware-libs and without the correct library, it won't build right.
What I don't get is: 1. which parts are missing, 2. where are people getting them from, 3. how do you add them to AOSP (other than PRODUCT_COPY_FILES) to get camera and all hw working right (including 3d acceleration).
Or maybe the project aurora community is better able/willing to help...

Bump. Totally interested. If OP already got an answer, please share.

Jubeh sorry I can't help you out I'm not a dev or a chef so I can't really give you any help. But I am interested in how your progress is going with this rom?

I found two sources for hardware files for the msm7k on our phones, including the camera and hw3d driver for dream. Also, building camera for AOSP seems to be fixed now. I'm just waiting from my battery to get here so that I can test. ebay parts from hong kong take forever.

[ROM] [Project ] Pure AOSP 5.0.2_plus Google Updates (2/1/2015) Mako Beta

The idea behind this project is to compile a Pure AOSP ROM. The difference is I have been little by little including and testing new commits added to the for the most part unstable staging master branch code from Google AOSP that has not yet been tagged for a future Lollipop update., hence the reason for 5.0.2_Plus name. The only change added to the code that was not committed first by Google is that the ZIP can be flashed in TWRP without replacing TWRP with the Stock Recovery and that is it. At the moment because of limited testing as I do not own a Nexus 4 and all changes have been tested on the Nexus 5 felt untill a few return performance reports best to call this a beta version. With that said the same changes have made some improvments and fixed a few issues experienced by Nexus 5 users using the oficial 5.0.1 update or compiled from the AOSP android-5.0.2_r1 branch. So if start receiving comments that all has been well on the Mako build or see say 100 download without a complaint reported will remove the beta tag. I suspect this will be the case as the commits are not device related.
I honestly started the project for the Nexus 5 with the idea that maybe as a community a few developers could help work on the project so everyone had an updated version of the latest release version that included the latest fixes and had not intended on compiling for the Nexus 4. After my second release another XDA member had asked if it would be possible to make a Nexus 4 port for a friend. At that point as there had been little interest in the project by other Nexus 5 Developers I would post the Mako ota package I compiled for the user who had asked for one. I also have my own Starship Rom and am part of a new developer team so again was meant as a community project and not intended to be released as my Rom or really even released at all with the intention of being a resource for other developers to either use as the base of whatever new AOSP Rom they may intend on developing or selectively picking pieces or fixes. So going with the same idea after compiling the asked for Mako version thought why just limit the idea to just the Nexus 5 as all Nexus devices share the same code from AOSP with exception of needing to add a different set of propriety vendor blobs and choosing a different lunch command for building. So the same goes as intended for the Nexus 5. If any Nexus 4 developers would be interested in joining in on the project Just let me know and I will grant full access to the Github account and create a new branch so we can test and insure the master branch is always %100 stable if it is going to be used by other Nexus developers..
A few examples of the commits that have been added.
https://github.com/Android-AOSP/And...mmit/20063610490eabc91db5ef13a550ecbdcdc6dc1a
https://github.com/Android-AOSP/And...mmit/16c0cfd5920c6d09824d13b7ee94436de87b37e3
https://github.com/Android-AOSP/And...mmit/b9e7a844fc751b9fdda7d452dee361f15815199b
https://github.com/Android-AOSP/And...mmit/18cca2773e4f3890e2ff9ca416400d48f62b98f5
https://github.com/Android-AOSP/And...mmit/a05556633ae5a6d1db164597b93f8b6cbbdf2608
https://github.com/Android-AOSP/And...mmit/e6beb1369165f97a4df24a1d1966c41e392c44e7
https://github.com/Android-AOSP/And...mmit/be42994b5a42914071adddfd5d989950e8e47bd9
https://github.com/Android-AOSP/And...mmit/0c89e1b9395093f71cf73508553d5e4058093ec0
https://github.com/Android-AOSP/And...mmit/4c53a7872b1f37ec184801f16d39584ca3b9bcce
https://github.com/Android-AOSP/And...mmit/9d2f14442f2e1d1507dbdc6cc7b9348513a907f9
https://github.com/Android-AOSP/And...mmit/905c6e72ecdc6e170744649b78e8fbb919f71efd
https://github.com/Android-AOSP/And...mmit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/And...mmit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/Android-AOSP_bionic/commit/eaf5aa7d22bd2f6b2eae4c81a60950f89e2d7df4
https://github.com/Android-AOSP/And...mmit/74574e8aa5a2de32e10364fd2f495023fff2a267
https://github.com/Android-AOSP/Android-AOSP_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
https://github.com/Android-AOSP/Android-AOSP_build/commit/1df3707a04651966ca17796f321d23ab3ed6ed2e
https://github.com/Android-AOSP/And...mmit/6fe9c73738e9da0192971576d120802d4c094556
https://github.com/Android-AOSP/And...mmit/44c1c3235d29095c4d987d19155c7260d1a33e0f
https://github.com/Android-AOSP/And...mmit/33baf53861712c3f84606a017943e36bdc680b50
https://github.com/Android-AOSP/And...mmit/a975a08cfb30ad6b2994647c0c6f09e2abd20e28
https://github.com/Android-AOSP/external_protobuf/commit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/external_protobuf/commit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/frameworks_base/commit/cc50afe3bdcc3adfa0f4121bf461996996e69a3e
https://github.com/Android-AOSP/frameworks_base/commit/1be740dd60f4d95e1f9ac4aac7e4d6148e3b2dd1
https://github.com/Android-AOSP/frameworks_base/commit/1cca2282dc9a3b7ecc08729af201923842ddfc86
https://github.com/Android-AOSP/frameworks_base/commit/7db1192e72b45111556631dba125a635edff3235
https://github.com/Android-AOSP/frameworks_base/commit/b29136581cc3181e59193e0b6448f0c3f5990081
https://github.com/Android-AOSP/build/commit/de655233a4308340fc71490e86fd0f218cc7fec4
https://github.com/Android-AOSP/build/commit/ab6f841841a0930c7e178a949ada39152e24540f
https://github.com/Android-AOSP/hardware_libhardware/commit/9ede7f730bca338cd3ccad8962e253f28ae17976
https://github.com/Android-AOSP/hardware_libhardware/commit/d4f431fec4136f6eeee919ac3190762fba832942
https://github.com/Android-AOSP/hardware_libhardware/commit/898bcd96e3d80e99d9200cceb4af754bae6d5f4a
https://github.com/Android-AOSP/bionic/commit/d90f39af35c1f2a9972198f92e803e3ca73ac910
Downloads
Download Rom
aosp_mako-ota-ota-5.0.2_plus_r2.0_test.zip.zip - 184.51 MB
aosp_mako-ota-ota-5.0.2_plus_r1.0_test.zip - 184.52 MB
PA-Gapps
http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
So far I have been using the "Mini Modular package" for testing without any issues.
Root
Root is optional but recommend SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053
Have had version 2.37 in storage and had been using without issue but updated to 2,40 with last test without any issues. What can I say Im lazy that way so unless having an issue just used what works but figured most would grab the latest so thought it best to give it a test before posting.
Kernel is %100 Stock but going with past experience if mrg666 has a Kernel availible for your device it should be the Kernel you are using.
Mirage Kernel for Stock Nexus 4
http://forum.xda-developers.com/nex...el-mirage-nexus-4-stock-rom-06-04-14-t2485368
Change Log 5.0.2_plus_r2
Removed the below commit "Add ip6-localhost to /system/etc/hosts."
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
Looks like a few apps are not fans of having an ip6 entry for localhost. Transparent Weather Widget for example can not find the device location with the enty included.
In looking for the cause of the above issue also reverted.
https://github.com/android/platform_frameworks_base/commit/e4ec09da0b4a31e23f1a19bdd1ea99e0f87cadac
Honestly reverted looking for the cause and did not remember to restore once identifying the cause. Overall is an old commit and dont think will make any difference whatsoever or would have been tagged for use in a past release so not going to bother.
As usual I am not responsible for your device and you are using anything posted in this thread at your own Risk.
This is %100 AOSP with no extra theming at all including bootanimation so no screen shots, as a Nexus User are probably aware what AOSP looks like at this point.

Don't mean to be rude, but you're still living in 2014, apparently. LOL . Classic mistake, I guess. Check the title dude.

Its cool, such a classic XDA first comment though. Could discover the holy grail and receive 15 comments about a spelling error. Adding I guess makes it that much better. Going to leave it in and see how many times your comment is over looked by someone so proud to have noticed it first, lol.

This is exactly what i have been looking for, we need more Roms like this. Thanks OP downloading now:good:

chairshot215 said:
Its cool, such a classic XDA first comment though. Could discover the holy grail and receive 15 comments about a spelling error. Adding I guess makes it that much better. Going to leave it in and see how many times your comment is over looked by someone so proud to have noticed it first, lol.
Click to expand...
Click to collapse
I hope you don't think it was something personal, man. Your title made my day. With all these exams, I've been all stressed out, and your title made reminded me of the time when I was sitting in bed with the laptop in front of me, thinking it's a long time till the exam session. LOL

Good rom so far, only thing was that data roaming was enabled by default.

dragos281993 said:
I hope you don't think it was something personal, man. Your title made my day. With all these exams, I've been all stressed out, and your title made reminded me of the time when I was sitting in bed with the laptop in front of me, thinking it's a long time till the exam session. LOL
Click to expand...
Click to collapse
I was just joking but still think it will be amusing to see how many skip past your post to point out the same. I actually test software for a living after it has been installed on an energy management diagnostic system both for new version testing and quality control before shipping and need to sign off that each system was checked out including the date. Had just recently worked on my birthday and was a highly unusually busy day but ended up signing off the date as 1976 (my birth year) on about forty systems. What is even more humorous is the amount of complaints from technicians who thought they received a system using a Nexus 7, now 9 for use as a portable User interface believed they had received software that had not been checked out since 1976. With that said most installers come from an HVAC technical school background and still use AOL as their contact email address. Lol!

nibla101 said:
Good rom so far, only thing was that data roaming was enabled by default.
Click to expand...
Click to collapse
Will look into that I'm happy to know it is working out. I basically just took my N5 source added the Mako vendor blobs and compiled using a different lunch command. Will go back and see if data roaming being enabled by default is a result of my updates or is set in general aosp 5.0.2 after work. Even though intention is keeping as pure as can be should still be looked at.
Think it would be nice if we could get a few devs together from across the current Nexus devices lineup and do our best to keep an aosp Rom available adding in the latest updates and bug fixes into the most current release for all Nexus devices. Not just for users but for other devs to use in their own aosp based work. Beleive if we could get something like that going would be pretty sweet and not all that time consuming. Still lots of updates added by Google devs every day. Some a bit more complicated then what I have done that a small group could easily bang out and test. Everything comes from the Master aosp branch that can get messy with constant new commits around the clock but think if selective in adding into latest release could be a beneficial project. So using my phrase of the week with that said I am going to build and post a version for all the Nexus devices in an attempt at gaining interest in the project. Again with that said I am torn for tonight as can try producing thr first N5 version that is sprint compatible or build for my Nexus 9. I am very much looking forwored to trying it out with jusst Simple ol aosp but at the same time feal bad for the Nexus 5 Sprint users who are all stuck on stock because other Roms are missing the aditional files added in for the radio to work. Decitions, decitions, decitions.

chairshot215 said:
I was just joking but still think it will be amusing to see how many skip past your post to point out the same. I actually test software for a living after it has been installed on an energy management diagnostic system both for new version testing and quality control before shipping and need to sign off that each system was checked out including the date. Had just recently worked on my birthday and was a highly unusually busy day but ended up signing off the date as 1976 (my birth year) on about forty systems. What is even more humorous is the amount of complaints from technicians who thought they received a system using a Nexus 7, now 9 for use as a portable User interface believed they had received software that had not been checked out since 1976. With that said most installers come from an HVAC technical school background and still use AOL as their contact email address. Lol!
Click to expand...
Click to collapse
LMAO. That was funny

flashed yesterday with nothing to complain until now
thanks for this build
edit: found first bug (maybe)
whle setting Chronus Weather and also Transparent Clock Widget
the phone couldn't find it's location.
Pop up on the screen stated....
"Cannot retrieve location!"
Network geolocation is disabled
Set a custom location or enable location
already try High Accuracy, Battery saving and Device only but it never show my location
the widget always appear with "Loading weather data"
If i choose Battery saving then Google Location Reporting will turn grey and not clickable, other two option made it clickable again but still my location show "Loading weather data"
maybe someone are having this too?
how to fix it please?
thank you very much

groovepeppy said:
flashed yesterday with nothing to complain until now
thanks for this build
edit: found first bug (maybe)
whle setting Chronus Weather and also Transparent Clock Widget
the phone couldn't find it's location.
Pop up on the screen stated....
"Cannot retrieve location!"
Network geolocation is disabled
Set a custom location or enable location
already try High Accuracy, Battery saving and Device only but it never show my location
the widget always appear with "Loading weather data"
If i choose Battery saving then Google Location Reporting will turn grey and not clickable, other two option made it clickable again but still my location show "Loading weather data"
maybe someone are having this too?
how to fix it please?
thank you very much
Click to expand...
Click to collapse
Think I got the fix and am compiling now. Hopfully have up by tonight if not morning. I am on the N5 though and have no issue with beatifull widgets finding my location or maps with navigation working which is my goto test apps along with GPS test. After reading your post tried Transparent Clock Widget and the app was not able to find my location. I did manage to fix this on my N5 so am rebuilding for Mako using the same source. Now have all the Mako Vendor proprietary blobs set up in vendor so can build either Hammerhead or Mako depending on lunch command. Still though will need testing on N4 as I am on the N5.

chairshot215 said:
Think I got the fix and am compiling now. Hopfully have up by tonight if not morning. I am on the N5 though and have no issue with beatifull widgets finding my location or maps with navigation working which is my goto test apps along with GPS test. After reading your post tried Transparent Clock Widget and the app was not able to find my location. I did manage to fix this on my N5 so am rebuilding for Mako using the same source. Now have all the Mako Vendor proprietary blobs set up in vendor so can build either Hammerhead or Mako depending on lunch command. Still though will need testing on N4 as I am on the N5.
Click to expand...
Click to collapse
will test it later
thank you for responding

groovepeppy said:
will test it later
thank you for responding
Click to expand...
Click to collapse
Know prob but had been unsuspectingly busy but compiling the what believe will fix the issue for the N4 and it comes down to the smallest commit.
Know prob but had been unsuspectingly busy but compiling the what believe will fix the issue for the N4 and it comes down to the smallest commit.
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e

M8 CM Audio Issues

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Now for the more specific stuff. Let me preface this entire thread by saying that I'm very much out on a limb here. I, as well as many others, have noticed that there are some fairly significant audio issues in CM stretching back to early CM11 builds for the M8. The general fix has always been "install v4a, and it'll work just fine". This isn't really a fix imho, it's a band-aid.
As such, I've created two repos: 4.20.x Sprint Stock, and 02/26 CM Unofficial (NOT NIGHTLY). I've uploaded the various parts that I think are going to be relevant in comparing the two code bases in the hopes that this problem can be tracked to its origin and finally fixed. The repos are on github as Stock and CM.
As far as the problems that have been noticed, it's good to remember that not all problems related to audio issues are what we're trying to address here. As an example, this is not a bluetooth thread, so bluetooth connectivity problems aren't going to be addressed even if it relates to phone calls or music playback. This is by no means a complete list and additional items should be listed as noted in posts. Some of the issues I feel that are actually related to audio problems are as such:
Distortion at loud volumes; speakers sound like crap when played loud, but not on stock or gpe
Improper playback channels; speakerphone volume level activating through phone channel rather than media channel
Sound dropouts during calls; caller can be heard but not hear M8 user (common with V4A Lolli installs)
Problem Submission: If you submit a problem to the list in your responses, please tag it as such;
PROBLEM_ITEM: [my problem description here].​This will allow me to easily search the thread and add additional known issues to the list. If you submit a problem but don't see it in the list, check Post #2 for reasoning as to why the problem wasn't initially added to the list.
Inside the Stock repo is a logcat that I took while performing operations during music playback. Specifically, I started the music playback via Poweramp, opened AudioFx from inside Poweramp, changed the EQ Preset various times,returned to Poweramp, and stopped the music. I'm hoping that starting with the logcat will lead somewhere..... as I mentioned, I'm waayyy out on a limb here.
As for my device, I'm running my own builds of CM12, no cherry-picks, SuperSu, CM kernel w/ no tweaks, NO V4A. Repo sync for this build includes Settings: reorganization merge on Feb 26, 2015 7:35 AM. Anything after is not in the current build, and therefore not in the CM repo.
ALL help is greatly appreciated, unconstructive / disrespectful comments are not. Here's to hoping this goes somewhere.

Saved for Info

It's most likely not possible to fix. Boomsound drivers are closed source. Unless HTC decides to make the drivers open source, then we probably won't be able to get sound fixed on cm. [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80]

Yea... that was a statement I made in another thread responding to one of those "Why can't CM fix the audio issues already" posts. I still think that there might be a channel problem, especially with the way that the speakerphone is operating. So far though, I've not found a direct reference to the boomsound drivers in digging through the stock sources.

Rescue9 said:
Yea... that was a statement I made in another thread responding to one of those "Why can't CM fix the audio issues already" posts. I still think that there might be a channel problem, especially with the way that the speakerphone is operating. So far though, I've not found a direct reference to the boomsound drivers in digging through the stock sources.
Click to expand...
Click to collapse
I'm thinking it could be done through the kernel. But that's beyond my skill level.

probably not relevant , but all i got.lol. just found on beanstalk ROM. of course , i wouldnt know what to do with it. lmao.
"all i can really do , is stay out of my own way and let the will of heaven be done"

mrrocketdog said:
just found on beanstalk ROM. of course , i wouldnt know what to do with it.
Click to expand...
Click to collapse
no worries mrrocketdog. can you verify that you do not have audio issues on beanstalk rom? If so, think you can find mixer_paths.xml, audio_effects.xml, and audio_platform_info.xml and post links?
I found up that mixer_paths.xml is indeed used, unlike what some were saying in the other thread. and I'm starting there.

Rescue9 said:
no worries mrrocketdog. can you verify that you do not have audio issues on beanstalk rom? If so, think you can find mixer_paths.xml, audio_effects.xml, and audio_platform_info.xml and post links?
I found up that mixer_paths.xml is indeed used, unlike what some were saying in the other thread. and I'm starting there.
Click to expand...
Click to collapse
no audio issues confirmed. will look for path and report back.
"all i can really do , is stay out of my own way and let the will of heaven be done"

@Rescue9 , all i could find were these under system-lib-hw.
https://www.dropbox.com/sh/3xaqr8nlr19v6mm/AAD2VdLPQf8ijftOxZQiKmeGa?dl=0
if there is some other folder to check just let me know. i think i went thru them all. (maybe just named different?). will also go thru my cm11 nightly and look for above mentioned files. also can confirm no audio distortion on it. ran for about 2 months.
here is cm11.
https://www.dropbox.com/sh/prv441xo5mu25sj/AAAtGuWro9Jz4y3B2E8dtvm9a?dl=0
again , could not find exact files you requested , but uploaded everything with 'audio' in title.
"all i can really do , is stay out of my own way and let the will of heaven be done"

The discussion in this thread is great and definitely development related with an end goal as the rules say. However, since it's unofficial, we decided to move it to Development. Please PM me if you have questions or concerns.
Thanks,
coal686
Forum Moderator

@Rescue9, found maybe something else. beanstalk - system - media - soundimage.
https://www.dropbox.com/sh/whqk8elvgjbd7jh/AACoqdZrxrNH3C1BMn2IHzXha?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"

Some possible Kernel help.
Not sure if this will help or not, but I'm running the CM12 based rom Resurrection Remix by: Brian Koluch
The Kernel he includes seems to fix a lot of the speaker distortion issues I was having with my M8. The Kernel is: B14CKB1RD v3.4.36 (g1069d49)
Here's his Google+ RR Community Post: https://plus.google.com/115522815889154627721/posts/d9BApKK8nbx
Maybe you guys can review that Kernel and see what's different, it has some audio commits in it.

toknitup420 said:
It's most likely not possible to fix. Boomsound drivers are closed source. Unless HTC decides to make the drivers open source, then we probably won't be able to get sound fixed on cm. [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80]
Click to expand...
Click to collapse
nothing is imposible.

What about using v4a or using a volume limiter ??

fcukmayank said:
What about using v4a or using a volume limiter ??
Click to expand...
Click to collapse
Those are band-aid solutions. The goal is to fix the problem once and for all.

CJ-Wylde said:
The Kernel he includes seems to fix a lot of the speaker distortion issues I was having with my M8. The Kernel is: B14CKB1RD v3.4.36 (g1069d49)
Click to expand...
Click to collapse
This is very informative! After playing around extensively with the config files in /etc/ I'm beginning to think that this is indeed a problem wholely related to the kernel. I remember using Quantum on my GS3 simply because the kernel fixed a number of issues.
Part of the problem that I'm facing is the fact that my M8 doesn't sound all that distorted on the high end. I feel as I'm trying to grease a squeaky wheel when I don't even hear the squeak.

I know that with the build I'm on now with the Kernel I mentioned, things are definitely more clean & clear on the speakers. I'm glad I can help a little bit.

Thanks @CJ-Wylde never knew this Brian guy built Roms for the m8. I see the kernel is a from wyldstallyn using blackbirds git.
OP maybe ask Brian on G+ if he can direct you to who built the kernel and ask them what they changed if anything that is maybe fixing the distortion

krazie1 said:
OP maybe ask Brian on G+ if he can direct you to who built the kernel and ask them what they changed if anything that is maybe fixing the distortion
Click to expand...
Click to collapse
That's a good idea @krazie1. Would you take care of that for the team. I'm still working through lines of code looking for a connection.
I did install the blackbird kernel straight over the 02/28 CM12 build I'm running now and the speakers actually sounded worse. Very distorted at half volume. I didn't even want to increase the volume fie fear of damaging them.

Rescue9 said:
That's a good idea @krazie1. Would you take care of that for the team. I'm still working through lines of code looking for a connection.
I did install the blackbird kernel straight over the 02/28 CM12 build I'm running now and the speakers actually sounded worse. Very distorted at half volume. I didn't even want to increase the volume fie fear of damaging them.
Click to expand...
Click to collapse
Here is the wyldstallyn's kernel github https://github.com/wyldstallyns
I will be flash testing the resurrection remix 5.3.7 build later when my phone charges up

[8.1] [Magisk Module] Multi-Touch Fix for 8.1 Devices

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.

(DEV-ONLY) discussion about implementing fingerprint when compiling from source code

This thread is so more information about our fingerprint issue when building from source code can reach more devs and enable them to start off without having to research any and all the information that we already have.
The main goal is to share what each one of us knows so far and discuss what may work and won't work.
Share our ideas and thoughts on the subject.
First question is
how many of you still have these files in these locations after flashing source built rom?
system/vendor/lib64/hw/goodix.fingerprint.sdm845.so
system/vendor/lib/hw/goodix.fingerprint.sdm845.so
system/vendor/lib64/hw/goodix.fod.sdm845.so
system/vendor/lib/hw/goodix.fod.sdm845.so
system/vendor/lib/libgoodixfingerprintd_binder.so
system/vendor/lib64/libgoodixfingerprintd_binder.so
system/vendor/lib/[email protected]
system/vendor/lib64/[email protected]
lets start here.

Reserved

This one too

Maybe one more

I'm running the latest havoc, and these are the only fingerprint files I have

To understand the problem you have to understand how it works in the first place. The fingerprint sensor is actually working, so its not a blob issue. The issue(from what I am seeing at least) is that stock aosp source cannot differentiate between the fingerprint sensor touch vs the regular display touch. After digging through oneplus systemui you will notice that there is quite a few proprietary things in there pertaining to the touch system for fingerprint. All of which is missing from aosp source.
We currently have 2 options for getting FP working. Either OP releases the fingerprint source or someone reverse engineers the code from oneplus(like what was done with the slider).
EDIT: Since it will be asked anyway how i know its not a blob issue... If the fingerprint sensor was not working correctly Roms would not even have the fingerprint option available or it would crash on load.

me2151 said:
To understand the problem you have to understand how it works in the first place. The fingerprint sensor is actually working, so its not a blob issue. The issue(from what I am seeing at least) is that stock aosp source cannot differentiate between the fingerprint sensor touch vs the regular display touch. After digging through oneplus systemui you will notice that there is quite a few proprietary things in there pertaining to the touch system for fingerprint. All of which is missing from aosp source.
We currently have 2 options for getting FP working. Either OP releases the fingerprint source or someone reverse engineers the code from oneplus(like what was done with the slider).
EDIT: Since it will be asked anyway how i know its not a blob issue... If the fingerprint sensor was not working correctly Roms would not even have the fingerprint option available or it would crash on load.
Click to expand...
Click to collapse
Thanks for the input.
I believe we have a long road ahead but we have to start somewhere.

me2151 said:
To understand the problem you have to understand how it works in the first place. The fingerprint sensor is actually working, so its not a blob issue. The issue(from what I am seeing at least) is that stock aosp source cannot differentiate between the fingerprint sensor touch vs the regular display touch. After digging through oneplus systemui you will notice that there is quite a few proprietary things in there pertaining to the touch system for fingerprint. All of which is missing from aosp source.
We currently have 2 options for getting FP working. Either OP releases the fingerprint source or someone reverse engineers the code from oneplus(like what was done with the slider).
EDIT: Since it will be asked anyway how i know its not a blob issue... If the fingerprint sensor was not working correctly Roms would not even have the fingerprint option available or it would crash on load.
Click to expand...
Click to collapse
I'm in agreement on this. My LG G5 has a fingerprint sensor and when the battery was getting bloated it was actually lifting the power/fingerprint button off the connector. When it got bad enough the phone just stopped showing the option for the sensor because it no longer detected the presence so even if the files are there Android is smart enough to hide the option if it doesn't see a working sensor.

Yep. A lot of times when device bringup is being done if you haven't done fingerprint yet android will just not show the fingerprint options(in setup or in settings). Usually won't until it sees the fingerprint hardware actually working and connected.

me2151 said:
Yep. A lot of times when device bringup is being done if you haven't done fingerprint yet android will just not show the fingerprint options(in setup or in settings). Usually won't until it sees the fingerprint hardware actually working and connected.
Click to expand...
Click to collapse
Since you said something about the system Ui I decompiled it.
It looks like everything is in there even the green light.

twinnfamous said:
Since you said something about the system Ui I decompiled it.
It looks like everything is in there even the green light.
Click to expand...
Click to collapse
Yep. Even the code for the face unlock is in there.

me2151 said:
Yep. Even the code for the face unlock is in there.
Click to expand...
Click to collapse
So in a sense all it takes is someone capable enough to take the decompiled files and modify the system ui apk source code in the rom they are building?
I have the files if anybody needs them there on afh

me2151 said:
Yep. Even the code for the face unlock is in there.
Click to expand...
Click to collapse
So in a sense all it takes is someone capable enough to take the decompiled files and modify the system ui apk source code in the rom they are building?
I have the files if anybody needs them there on afh

twinnfamous said:
So in a sense all it takes is someone capable enough to take the decompiled files and modify the system ui apk source code in the rom they are building?
I have the files if anybody needs them there on afh
Click to expand...
Click to collapse
Yes and no. The main problem is the fact that the code is proprietary. If you release it as is or share it as is you could face legal action from one plus. It has to be completely rewritten. Hence the reverse engineering part. But the yes to it is it just needs someone capable.

few Devs have the code already ..
But unfortunately can't post a rom with fingerprint fix , cause is proprietary or get DMCA'd
So they're working on a fix that's open source to share it...

cultofluna said:
few Devs have the code already ..
But unfortunately can't post a rom with fingerprint fix , cause is proprietary or get DMCA'd
So they're working on a fix that's open source to share it...
Click to expand...
Click to collapse
Did any dev even got the fingerprint to work?

Electric1447 said:
Did any dev even got the fingerprint to work?
Click to expand...
Click to collapse
Not yet

cultofluna said:
few Devs have the code already ..
But unfortunately can't post a rom with fingerprint fix , cause is proprietary or get DMCA'd
So they're working on a fix that's open source to share it...
Click to expand...
Click to collapse
Systemui in source built roms have fingerprint files in them. May be easier if someone running a open-source rom pulls the apk and decompiles it then edit and put back in device to test? Just a thought but I've been going through everything the only thing I seen so far we need to add is the fingerprint location values and add files to show on screen.
We shouldn't have to rewrite completely as most files are all ready open source and in systemui of aosp source code.
I've been caught up in building a source code rom and trying things but there are far more people that have more experience than I do at the .apk part.
Hope any of this helps.

twinnfamous said:
Systemui in source built roms have fingerprint files in them. May be easier if someone running a open-source rom pulls the apk and decompiles it then edit and put back in device to test? Just a thought but I've been going through everything the only thing I seen so far we need to add is the fingerprint location values and add files to show on screen.
We shouldn't have to rewrite completely as most files are all ready open source and in systemui of aosp source code.
I've been caught up in building a source code rom and trying things but there are far more people that have more experience than I do at the .apk part.
Hope any of this helps.
Click to expand...
Click to collapse
This what I thought someone should do. Even if someone uses copyrighted code he could still test and see if it works.

I want to continue research on this topic. I'll take a look at systemui and framework-res and try to just test if I can get OP code working on AOSP. Then I'll go from there.
Edit: From a quick glance, FP code seems to be also present in framework-res, so that likely will also need to be worked on.