Hello.
Based on these findings and this commit, I've made a patch to fix the noise cancellation issue. You don't need this if your ROM already has the fix built-in.
This is an universal patch. It is meant to work on every custom ROM
Tested:
-Official CM13
-AOSParadox
-...
If, for some reason, you want to go back to initial state, just flash revert zip
Thanks:
@ashwin007
@saurabh40629
Report back mentioning the ROM you're using.
Downloads
Thank you very much
If I've already done this fix, is it worth flashing the zip in this thread?
Shinr3x said:
If I've already done this fix, is it worth flashing the zip in this thread?
Click to expand...
Click to collapse
I've added a modified audio_platform_info.xml as seen in the ashwin's latest commit.
But if the build.prop alone fixes the noise cancellation issue, then you don't need to flash this.
In the fix from @saurabh40629 the "persist.audio.fluence.speaker" is set to false and here you set it to true. What's the difference? Saurabh40629's fix worked good for me
Rom: official cm13
Honestly, I haven't tested that much.
I wanted to keep inline with the ashwin's commit, since that's the one that will merge on official CM device tree.
Op indicated custom rom. So oss cannot?
Tiongkia said:
Op indicated custom rom. So oss cannot?
Click to expand...
Click to collapse
Oxygen OS does not have the noise cancellation bug.
Loureiro said:
Honestly, I haven't tested that much.
I wanted to keep inline with the ashwin's commit, since that's the one that will merge on official CM device tree.
Click to expand...
Click to collapse
I think what @phoberus meant was that you changed more than Ashwin did.
Ashwin's changes:
Code:
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.mode=endfire
Your changes:
Code:
ro.qc.sdk.audio.ssr=false
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.mode=endfire
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true
Firefly1337 said:
I think what @phoberus meant was that you changed more than Ashwin did.
Click to expand...
Click to collapse
Yes, the script overrides the values already present on build.prop, making it compatible with any custom ROM.
Ashwin's commit just changed what was missing for CM13.
Loureiro said:
Yes, the script overrides the values already present on build.prop, making it compatible with any custom ROM.
Ashwin's commit just changed what was missing for CM13.
Click to expand...
Click to collapse
Nope, if you look at the full file you'll see that your additional lines aren't there.
Firefly1337 said:
Nope, if you look at the full file you'll see that your additional lines aren't there.
Click to expand...
Click to collapse
You're right.
I might got those from AOSParadox or OOS. But if they have no effect, there's no need to include them.
I'll update with the most recent commit
Loureiro said:
I might got those from AOSParadox or OOS. But if they have no effect, there's no need to include them.
Click to expand...
Click to collapse
That's the problem with these things, we don't know. They might have no effect at all but they could have a negative effect aswell. That's why I wrote my comment in the first place.
Thanks for changing it and thanks for your work
I'm running AOSParadox .Other party , while calling, after flashing the provided zip, reported that the echo was present whenever Loud speaker option is turned on.
After flashing the "revert" zip, the problem got solved.
Sent from my ONE E1003 using XDA-Developers mobile app
sankarshan said:
I'm running AOSParadox .Other party , while calling, after flashing the provided zip, reported that the echo was present whenever Loud speaker option is turned on.
After flashing the "revert" zip, the problem got solved.
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
thanks for reporting.
I'll look into it
i think the patch on ashwin's github is still in testing phase as this commit is different
https://github.com/ashwinr64/androi...mmit/857d8cae45731813859f3afa07fae0bbb3bf9200
well done with the zip anyways, thank you
phoberus said:
In the fix from @saurabh40629 the "persist.audio.fluence.speaker" is set to false and here you set it to true. What's the difference? Saurabh40629's fix worked good for me
Rom: official cm13
Click to expand...
Click to collapse
Yes I had better results when speaker set to false. I used @saurabh40629 fix on Purity Rom . Phone and hands free speaker where 100% better when noise present in background . (I tested in bathroom with exhaust fan on.) Thanks for taking the time to make a flashable zip. Gives some people who are not comfortable editing a good starting point.
That was the main purpose for doing the zip file, to make it easier to apply the patch until ROM devs do the commit. It is easier to apply between nighties
All the credit goes to saurabh40629.
By the way, you can easily edit the zip at your will. Just open it and edit the "patch/fluence_config" file.
I've tested a phone call on speaker mode and persist.audio.fluence.speaker set to true causes echo on the other party. Better leave it off
I'll update the 1st post as soon as I get to my laptop.
1st post updated with these build.prod edits:
Code:
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.mode=endfire
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=false
It is also included the updated audio_platform_info.xml from here
Hey, thanks for your investigation. What's the difference to ashwin's changes.
I did some testing and it was always a little noisy or the sound was little crappy. Wondering why...
Gesendet von meinem ONE E1003 mit Tapatalk
Related
Discontinued/Deleted
..
Thanks for extending material love to Viper. Now look in line with material look of Poweramp
n1729m said:
Thanks for extending material love to Viper. Now look in line with material look of Poweramp
Click to expand...
Click to collapse
There is already one available Here.
http://forum.xda-developers.com/showpost.php?p=62468476&postcount=1158
?
guitardedhero said:
http://forum.xda-developers.com/showpost.php?p=62468476&postcount=1158
?
Click to expand...
Click to collapse
What exactly is your question?
EDIT: Oh I see, I didn't notice at first, looks like someone shared my links, thanks for letting me know.
Nice! DragonFi just doesn't work with my M9. So glad this does, definitely a noticeable improvement in sound quality.
I tried the APK version first and every time I tried opening it, it'd open another app of mine asking to import a database. Not sure what that's all about but the ZIP flashed fine.
Alcolawl said:
Nice! DragonFi just doesn't work with my M9. So glad this does, definitely a noticeable improvement in sound quality.
I tried the APK version first and every time I tried opening it, it'd open another app of mine asking to import a database. Not sure what that's all about but the ZIP flashed fine.
Click to expand...
Click to collapse
What in Dragon-Fi is not working? the Dolby app? if so you may need Permissive for your kernel? unsure also the APKs do work but I guess something could be goofy if your ROM, which ROM are you using? but regardless if ZIP worked fine then I guess you may be happier about that sense V4A is now a system app
I use Dragon-Fi for the system files only, I skip all the Dolby stuff and I notice a good difference in audio quality, so it should be working for you, but I am on the M8, I never tried it on M9 personally.
Just for your convenience I have updated the thread to confirm that Marshmallow is indeed supported! :good:
hi nice app
can you add the ViPER4Android-supolicy.zip into this zip if possible so that Viper4Android work with SELinux enforced mode
question on driver status
Viper4713 said:
There is already one available Here.
Click to expand...
Click to collapse
I had to do the whole 9 yards with my Sprint HTC One m7 last time I put Viper4Android for lollipop on it (5.0.2). Selenix fix and flashing the zip, all I did was install the dark (had to RUU the device to get 6.23.651.10 on it) and driver status reads:
Driver Version : 2.3.4.0
NEON Enabled : Yes
Enabled : Yes
Status : Normal
Audio Format : Supported
Processing : Yes
Sampling Rate : 48000
Do not believe I have ever had the NEON enabled, just trying on phone speakers now............. WOW
cannot wait until the bluetooth cubes come off charge
zach
Viper is the make or break for staying on MM for me. Neither APK nor ZIP flash working for me.
J_awn said:
Viper is the make or break for staying on MM for me. Neither APK nor ZIP flash working for me.
Click to expand...
Click to collapse
Try the zip attached below.
guitardedhero said:
Try the zip attached below.
Click to expand...
Click to collapse
Is it for enforcing or permissive kernel ? And is it thr dark or light version ? Thanks
Sent from my Nexus 5
[Gorgasm] said:
Is it for enforcing or permissive kernel ? And is it thr dark or light version ? Thanks
Sent from my Nexus 5
Click to expand...
Click to collapse
Enforcing
Dark
guitardedhero said:
Enforcing
Dark
Click to expand...
Click to collapse
Do you think that it is possible to fix the light theme too ?
[Gorgasm] said:
Do you think that it is possible to fix the light theme too ?
Click to expand...
Click to collapse
Absolutely.
guitardedhero said:
Absolutely.
Click to expand...
Click to collapse
Does not work here.Gives error flashing this..Android mm gpe..
altetaube said:
Does not work here.Gives error flashing this..Android mm gpe..
Click to expand...
Click to collapse
What error?
It only works in FX Compatibility Mode for me on my N4 using the APK method.. I use Google Play Music, haven't tried Spotify or Pandora yet.
EDIT: It worked normally after flashing the ZIP. Thanks!
Hello
I got tired waiting for an official fix, so I came up with this workaround.
twrp-flashable_OPX2.2.0_camera_patch.zip - This zip with apply the OPX front camera configuration.
twrp-flashable_OPX_camera_patch_imx214.zip - This zip will apply the OPO rear camera configuration
You'll be able to record 1080p at night without worrying about the fps drop issue.
I am not responsible for any damage on your device when applying this patch.
EDIT: Added a revert flashable zip.
EDIT2: Added zip file with imx214 libchromatix_default_video.so
Sweet. Thanks
Swapped my Recent and Back buttons.
Edit:
A couple reboots might've fixed this, but I also messed with Gravity Box a bit as well. There's two options to fixing that problem, potentially.
RJMacReady said:
Swapped my Recent and Back buttons.
Edit:
A couple reboots might've fixed this, but I also messed with Gravity Box a bit as well. There's two options to fixing that problem, potentially.
Click to expand...
Click to collapse
This patch shouldn't mess with buttons layout. You might had a pending operation that took effect on reboot when you flashed this zip.
try hydrogen os.
does your phone need to be rooted or will it work fine with stock?
Does this patch works also with custom roms like cm13?
Sorry. This patch is for default camera only? Or its for any camera apps running on oss 2.20?
It works perfect now, thank you so much for this mod. Where did this libs came from?
Shame on One Plus btw.
#E1005
Loureiro said:
This patch shouldn't mess with buttons layout. You might had a pending operation that took effect on reboot when you flashed this zip.
Click to expand...
Click to collapse
Maybe, maybe not. Just letting people know a few reboots might help.
Thank you for the patch!
Great work mate, Oneplus have to work really hard about software
Loureiro said:
This patch will replace the binary file libchromatix_s5k3m2_default_video.so
Click to expand...
Click to collapse
did you take it from s4 or hydrogenos?
do you think any more improvements are possible by replacing the blobs?
Can anybody upload a sample on YT? Please I wan't to see what is this beauty capable of in low light video. Maybe I'll pop the cherry of my OPX and root it tomorrow OP thanks for the fix!
Loureiro said:
Hello
I got tired waiting for an official fix, so I came up with this workaround.
This patch will replace the binary file libchromatix_s5k3m2_default_video.so
You'll be able to record 1080p at night without worrying about the fps drop issue.
This has been tested on my device only.
I am not responsible for any damage on your device when applying this patch.
Do a system backup if you're worried.
EDIT: I've added a revert flashable zip.
Click to expand...
Click to collapse
Great job! What did you need to change in that file to get it done?
5star02707 said:
does your phone need to be rooted or will it work fine with stock?
Click to expand...
Click to collapse
No. You just need a recovery to flash the zip file
logan99 said:
Does this patch works also with custom roms like cm13?
Click to expand...
Click to collapse
I should work if the custom rom uses the same BLObs as Oxygen OS.
It means that, for now, it works on cm12.1 and cm13
Tiongkia said:
Sorry. This patch is for default camera only? Or its for any camera apps running on oss 2.20?
Click to expand...
Click to collapse
This patch is system wide. Any camera app will work with this.
ChavitoArg said:
It works perfect now, thank you so much for this mod. Where did this libs came from?
Shame on One Plus btw.
#E1005
Click to expand...
Click to collapse
ckret said:
did you take it from s4 or hydrogenos?
do you think any more improvements are possible by replacing the blobs?
Click to expand...
Click to collapse
I've tested other s5k3m2 binaries from other devices but they all miss some needed instructions.
This is the front camera binary
tested the imx214 file but it pushes iso way too high.
Awesome. Thank you OP
Loureiro said:
No. You just need a recovery to flash the zip file
I should work if the custom rom uses the same BLObs as Oxygen OS.
It means that, for now, it works on cm12.1 and cm13
This patch is system wide. Any camera app will work with this.
I've tested other s5k3m2 binaries from other devices but they all miss some needed instructions.
This is the front camera binary
tested the imx214 file but it pushes iso way too high.
Click to expand...
Click to collapse
Wait it does not require root and a custom recovery?
alabama20 said:
Wait it does not require root and a custom recovery?
Click to expand...
Click to collapse
root =! custom recovery
You need custom recovery to flash this.
ChavitoArg said:
root =! custom recovery
You need custom recovery to flash this.
Click to expand...
Click to collapse
I know what is what, I was just asking -.-"
alabama20 said:
I know what is what, I was just asking -.-"
Click to expand...
Click to collapse
Sorry, I forgot to say that custom recovery is needed
Hello,
this thread is only for development discussion about enabling camera2 api on xperia camera. If you have anything useful, it's the right place, however, it's not for non-dev things.
What are we going to do ?
The best way for enabling camera2 api is porting camera hal from sony aosp camera.
So I have attached sony aosp camera hal at this thread. We should do some modifications on kernel to make it working on stock rom.
Current Status : CSID needs to be updated on kernel
This can help us :
https://github.com/sonyxperiadev/ke...rch/arm/boot/dts/qcom/msm8974-camera.dtsi#L63
*Before testing camera hal, you should do 2 important works :
1. Remove following line from default.prop located at ramdisk : (At the moment, this is optional)
camera2.portability.force_api=1
2. Go to system>lib>hw and delete camera.qcom.so (This one is necessary)
Thanks To:
@davidteri91
@aquaboy11
works with cm12? or only with stock?
brickhayabusa said:
works with cm12? or only with stock?
Click to expand...
Click to collapse
This is dev only thread bro :laugh:
EugenStanis said:
This is dev only thread bro
Click to expand...
Click to collapse
i know, but if you read, he wrote "Need some testers to test attached camera hal on Z1/Z1C"
PS: you're not a dev too
I will get myself multirom to run stock, if it works I will start testing and try to edit the kernel. If we do it properly, we could maintain BIONZ right?
brickhayabusa said:
i know, but if you read, he wrote "Need some testers to test attached camera hal on Z1/Z1C"
PS: you're not a dev too
Click to expand...
Click to collapse
Well it doesnt need to have the physical RD or SRD title to have the privilege to post in DEV-ONLY thread, as long as you are contributing to the project on DEV basis.
aquaboy11 said:
I will get myself multirom to run stock, if it works I will start testing and try to edit the kernel. If we do it properly, we could maintain BIONZ right?
Click to expand...
Click to collapse
Thanks.
Nope, we can't have Bionz and a new camera hal at the same time
Everyone is asking for camera2 api and raw
But
No one has tested this after 1 month
So don't ask me again for raw!
mkdmc said:
Everyone is asking for camera2 api and raw
But
No one has tested this after 1 month
So don't ask me again for raw!
Click to expand...
Click to collapse
when i wanred to test it i dont understand this "Before testing camera hal, you should do 2 important works :
1. Remove following line from default.prop located at ramdisk : (At the moment, this is optional)
camera2.portability.force_api=1
2. Go to system>lib>hw and delete camera.qcom.so (This one is necessary)"
and i forgot about it)
mkdmc said:
Everyone is asking for camera2 api and raw
But
No one has tested this after 1 month
So don't ask me again for raw!
Click to expand...
Click to collapse
I don't have a z1/z1c ...but i can try it on z2 mm if you want. If this mod was for z2 i'm the first who became your betatester. If you extend the compatibility with z2 or you want a betatester for one of your mods for z2 variant...just contact me
mkdmc said:
Everyone is asking for camera2 api and raw
But
No one has tested this after 1 month
So don't ask me again for raw!
Click to expand...
Click to collapse
I tried so:
I removed the line as noted in Step 1
I extracted the file and copied to the folder "system" (with overwriting files)
Result: bootloop
I dont have a z1/z1c. I can became your tester on my z2.
mkdmc said:
Everyone is asking for camera2 api and raw
But
No one has tested this after 1 month
So don't ask me again for raw!
Click to expand...
Click to collapse
Hey, I could not get multirom to work. I also had quite some stuff to do for school so I could not test either. Today I switched back to stock rom and will have more time the coming weeks.
I did as you said, except for the default.prop. Put all the right permissions, copied over the files, and rebooted. The camera, as expected, does not work, so I captured a logcat and dmesg.
Sorry for taking so long .
aquaboy11 said:
Hey, I could not get multirom to work. I also had quite some stuff to do for school so I could not test either. Today I switched back to stock rom and will have more time the coming weeks.
I did as you said, except for the default.prop. Put all the right permissions, copied over the files, and rebooted. The camera, as expected, does not work, so I captured a logcat and dmesg.
Sorry for taking so long .
Click to expand...
Click to collapse
Thanks a lot for testing
It seems csid is incorrect
Kernel needs to be updated
mkdmc said:
Thanks a lot for testing
It seems csid is incorrect
Kernel needs to be updated
Click to expand...
Click to collapse
Which HAL did you use? Also, could you explain a bit more about csid, and how we should fix it? Would getting drivers from the AOSP kernel be any good, or should the stock code itself be updated?
aquaboy11 said:
Which HAL did you use? Also, could you explain a bit more about csid, and how we should fix it? Would getting drivers from the AOSP kernel be any good, or should the stock code itself be updated?
Click to expand...
Click to collapse
Latest AOSP 5.1.1 camera HAL.
I'm not sure how we can update csid btw we should use aosp kernel drivers.
This can help us :
https://github.com/sonyxperiadev/ke...rch/arm/boot/dts/qcom/msm8974-camera.dtsi#L63
mkdmc said:
Latest AOSP 5.1.1 camera HAL.
I'm not sure how we can update csid btw we should use aosp kernel drivers.
This can help us :
https://github.com/sonyxperiadev/ke...rch/arm/boot/dts/qcom/msm8974-camera.dtsi#L63
Click to expand...
Click to collapse
I'll play around with the kernels a bit to see if I can get something to work.
EDIT:
Doesn't seem like I can .
EDIT 2:
Is it safe to have Cyberian installed? Or should I reflash stock every time before testing?
In first place I would like to thank user Miroslav, author of this Youtube guide on how to fix this problem con 4x user DartJabba9 for providing the very first flashable zip and Zile995 for keeping up with the hard work!
This is the latest version: https://forum.xda-developers.com/showpost.php?p=73914743&postcount=188
Just flash with TWRP and enjoy!
Is it possible to create a flashable zip?
Honestly I don't know how. Could someone help us?
I can confirm it's working. I just replaced the two system files you suggested, using Root Explorer. I set the permissions, replaced, rebooted.
Sound is definitely better when recording music, but one must use the front microphone as audio source (can be found in the settings of HI-Q MP3 Recorder, and other audio recording software I guess).
NicolasMMM said:
I can confirm it's working. I just replaced the two system files you suggested, using Root Explorer. I set the permissions, replaced, rebooted.
Sound is definitely better when recording music, but one must use the front microphone as audio source (can be found in the settings of HI-Q MP3 Recorder, and other audio recording software I guess).
Click to expand...
Click to collapse
Glad it's woking!
LordR3tard said:
Is it possible to create a flashable zip?
Click to expand...
Click to collapse
You can use "zip me" application
Sent from my Redmi 3 using XDA-Developers Legacy app
LordR3tard said:
Is it possible to create a flashable zip?
Click to expand...
Click to collapse
See the attached. It works for me, but, as usual, all disclaimers apply.
BTW: this does not include any changes to build.prop, since the OP says that the change to build.prop should not be done.
DarthJabba9 said:
See the attached. It works for me, but, as usual, all disclaimers apply.
BTW: this does not include any changes to build.prop, since the OP says that the change to build.prop should not be done.
Click to expand...
Click to collapse
Are you on MIUI?
DarthJabba9 said:
See the attached. It works for me, but, as usual, all disclaimers apply.
BTW: this does not include any changes to build.prop, since the OP says that the change to build.prop should not be done.
Click to expand...
Click to collapse
I'll try it as soon as possibile and I will put it in the first post. Thanks!
LordR3tard said:
Are you on MIUI?
Click to expand...
Click to collapse
No. I am on OctOS. The files seem the same though.
In-Call low mic volume
gianluca212 said:
-this procedure is based on THIS GUIDE that YOU HAVE TO FOLLOW!
Click to expand...
Click to collapse
Well my major problem is in-call low mic volume. I have to literally shout at phone to make other person understand what I say. As stated in the description of given video guide, is there a way to fix in-call voice quality?
My current settings, might fix your in call voice quality:
For handset-mic put DEC1 at 96 and DEC2 at 0 (DEC2 is noise cancelling upper mic, I think).
For "handset-stereo-dmic-ef" put "DEC1 Volume" value="105" and "DEC2 Volume" value="105" for higher recording signal.
In build.prop, change these:
ro.qc.sdk.audio.fluencetype=fluence persist.audio.fluence.voicecall=true persist.audio.fluence.voicerec=false persist.audio.fluence.speaker=false
Click to expand...
Click to collapse
My device is Redmi Note 4 (not 4X) SD Global version with latest Stable ROM MIUI 8.2.10.0.
mirfatif said:
Well my major problem is in-call low mic volume. I have to literally shout at phone to make other person understand what I say. As stated in the description of given video guide, is there a way to fix in-call voice quality?
My device is Redmi Note 4 (not 4X) SD Global version with latest Stable ROM MIUI 8.2.10.0.
Click to expand...
Click to collapse
Well, I don't know how to help you. I took a month to solve the problem of bad audio because I'm a newbie and I don't know anything about Android. But, in some ways, I managed to solve that problem. Luck I guess
I don't really understand. I just got my Redmi today. Does the Redmi have a bad audio recorder? So it means people I call with experience a bad audio quality from my part? And this fixes it?
Hootix said:
I don't really understand. I just got my Redmi today. Does the Redmi have a bad audio recorder? So it means people I call with experience a bad audio quality from my part? And this fixes it?
Click to expand...
Click to collapse
No. It means that, depending on your ROM, trying to record some kinds of audio with the phone's microphone may not produce the best quality recording.
DarthJabba9 said:
See the attached. It works for me, but, as usual, all disclaimers apply.
BTW: this does not include any changes to build.prop, since the OP says that the change to build.prop should not be done.
Click to expand...
Click to collapse
Have you used "zip me" application to create flashable zip?
Sent from my Redmi 3 using XDA-Developers Legacy app
complicazio said:
Have you used "zip me" application to create flashable zip?
Click to expand...
Click to collapse
No, I did it manually.
1 - Does this method work for Note 4X?
2 - Just I flash this zip in the twrp of my Note 4X to solve the audio problems in the recording, right?
3 - I have the xiaomi.eu weekly version, whenever I manually install an update, will I have to flash this "fix" again?
Kolor13 said:
1 - Does this method work for Note 4X?
2 - Just I flash this zip in the twrp of my Note 4X to solve the audio problems in the recording, right?
3 - I have the xiaomi.eu weekly version, whenever I manually install an update, will I have to flash this "fix" again?
Click to expand...
Click to collapse
1. I don't know if it's working con 4x, you have to try to tell; Try but do a nandroid backup first
2. Yes, it is;
3. I don't know.
Kolor13 said:
1 - Does this method work for Note 4X?
2 - Just I flash this zip in the twrp of my Note 4X to solve the audio problems in the recording, right?
3 - I have the xiaomi.eu weekly version, whenever I manually install an update, will I have to flash this "fix" again?
Click to expand...
Click to collapse
3) yes you must flash fix whenever you flash an update of xiaomi.eu rom
Sent from my Redmi 3 using XDA-Developers Legacy app
complicazio said:
3) yes you must flash fix whenever you flash an update of xiaomi.eu rom
Sent from my Redmi 3 using XDA-Developers Legacy app
Click to expand...
Click to collapse
And does this fix work on my Redmi Note 4X?
...
I want you delete this thread tonight . Can you check does treble work? https://play.google.com/store/apps/details?id=com.kevintresuelo.treble
Thanks
Thanhtho96 said:
I want you delete this thread tonight . Can you check does treble work? https://play.google.com/store/apps/details?id=com.kevintresuelo.treble
Thanks
Click to expand...
Click to collapse
I highly doubt it is since getting Treble for bacon means a quite hard work with partitions and such. I am not professional but having custom OREO ROM does not mean Treble is supported.
Do ypu know if bacon is getting oficial support this week?
[deleted]
Thanks for your build!
Unfortunately camera in third apps doesn't work (like Snapchat or Messenger)
nienic said:
Thanks for your build!
Unfortunately camera in third apps doesn't work (like Snapchat or Messenger)
Click to expand...
Click to collapse
Work! You should change SELinux to Permissive
[deleted]
[deleted]
[deleted]
gavinchappell said:
Nope - see the screenshot
SafetyNet passes, although I always install a patch to turn off the ro.debuggable flag because I know I need that for one of my banking apps. So that might be why SafetyNet checks are OK.
What patch did you install? Can you explain?
Click to expand...
Click to collapse
[deleted]
If you merged this commit https://review.lineageos.org/#/c/209767/, camera in 3rd apps will work well without change selinux to permissive
[deleted]
Best lineage 15 build in my opinion. Everything works as expected, thanks a lot
gavinchappell said:
I don't think that commit on its own is enough to fix it because Snapchat runs under another context - however as the comments state, that patchset has now been abandoned anyway. It'll be included in a more common area (I guess it's a thing that could affect multiple Qualcomm SoCs) and there's a comment on the new patchset with the "correct" fix. I compiled myself a build with the latest proposed fix and Snapchat is working fine so once 209960 is merged and 15.1 is building, Snapchat users should be just fine.
I've updated the link in the first post to point to the latest version I've built, signed with test keys and has the SELinux change in which fixes Snapchat/Messenger.
Click to expand...
Click to collapse
What is your opinion about this https://www.reddit.com/r/Android/comments/87keoj/google_nexus_player_and_oneplus_2_receive/dwesq8h/? I think we won't have it in next week
[deleted]
Thanks a lot for the build @gavinchappell, I couldn't wait anymore. It also works flawlessly! :good:
EDIT: For all those having games crashing I solved changing vm.heapsize to 512 in build.prop.
Hello every One! I'm succesfully installed lineage-15.1-20180121-UNOFFICIAL-bacon on my OnePlusOne and the important thing for me which is NOT working it's routing audio input to the external audio interface connected via OTG (i'm using Lexicon Alpha). OTG actually works well with usb-midi interface and I can play my keyboard for example, but external audio interface is not working (it is connected well, the led is on, but problem with routing i guess) Maybe I should try ROM from this thread but, anybody knows some terminal commands for doing that? THANKS:fingers-crossed:
@gavinchappell, could you update this rom, please?))