Related
I decided to open a new thread for Lineage 13 MarshMallow for LeECO 1 PRO.
The Lineage 14.1 Nougat remain in its own thread
Mainly it will be for CN version that i own, but I will try to find some solution for US model also, maybe will get some succes.
Everything work except IR blaster.
Download CN Version:
Ver. march10:
http://www.mediafire.com/file/fzpq2dc53hyxkz8/CM13_X800_CN_ABM30_10-mar17-02.zip
Ver. 2017 jun 04
https://mega.nz/#!twVXBQjZ!6m9CdTMgWq91emxqCr0L8YYujl_mEQ0BnF7rjpGr-Ms
[URL=http://www.mediafire.com/view/fndjsikn4een632/X800-LinOS_13_-_Android_6.0.1._2017jun4.jpg]
[/URL]
DOWNLOAD US Version
Ver. march11: give a try:
http://www.mediafire.com/file/995cs583q09x4m6/CM13_X800_US_ABM30_11-mar17-01.zip
ver. 2017jun12
http://www.mediafire.com/file/5361ukny8i41s6u/X800_US_linOS_13_2017jun13_ABM30-x1.zip
Do you have any issues my friend?
How do you compare to CM14?
Camera works OK?
I can install on US version, or wait ?
freiserk said:
I can install on US version, or wait ?
Click to expand...
Click to collapse
You can install, but I think the sound problem will be there. The kernel is the Crisbal one but the Ramdisk in boot.img has some changes so, let see....
THX
There is problem with Samsung camera - the same as in 14.1. But I've found, that standard camera app in 13 works OK. The problem is with Open Camera and Google Camera (this three apps I've tested so far).
Maybe there's no camera v2 support? It should just take a prop file edit, probably build.prop IIRC.
did anyone tests the CN version for daily use?
Kaizen_pl said:
THX
There is problem with Samsung camera - the same as in 14.1. But I've found, that standard camera app in 13 works OK. The problem is with Open Camera and Google Camera (this three apps I've tested so far).
Click to expand...
Click to collapse
Standard camera in Lineage OS 13 MM in camera2, it seems that samsung camera need camera2 api to be activated.
Open camera has a switch in settings with this you can activate cam v2 api. Try and tell me if something goes better.
You can try also this:
How to enable Camera2 API?
1) install buildpropeditor
2) Open build.prop, make string 'persist.camera.HAL3.enabled=1' (without cotes), save, reboot.
has this helped somehow?
P.S. BTW how is the sound on this latest MM 13 ROM?
@ABM30 , did you receive message from me? It could help with camera (i am not sure if in this ROM too, but..who knows)
ABM30 said:
Standard camera in Lineage OS 13 MM in camera2, it seems that samsung camera need camera2 api to be activated.
Click to expand...
Click to collapse
No change. Neither switching in Open Camera camera2 helped, nor editing build.prop and restarting. Nothing changed.
KUKU159 said:
@ABM30 , did you receive message from me? It could help with camera (i am not sure if in this ROM too, but..who knows)
Click to expand...
Click to collapse
Yes, I received your message, thank you.
Any help is welcomed!
Good job!
So no sound in the phone speaker too?
Dual tap to wake don't work?
I activated both options and only dual tap to sleep in notification bar worked.
Cagixxx said:
Dual tap to wake don't work?
I activated both options and only dual tap to sleep in notification bar worked.
Click to expand...
Click to collapse
Unfortunate DTW not working, yet
ABM30 said:
I decided to open a new thread for Lineage 13 MarshMallow for LeECO 1 PRO.
The Lineage 14.1 Nougat remain in its own thread
Mainly it will be for CN version that i own, but I will try to find some solution for US model also, maybe will get some succes.
Everything work except IR blaster.
Download CN Version:
Ver. march10:
http://www.mediafire.com/file/fzpq2dc53hyxkz8/CM13_X800_CN_ABM30_10-mar17-02.zip
DOWNLOAD US Version
Ver. march11: give a try: http://www.mediafire.com/file/995cs583q09x4m6/CM13_X800_US_ABM30_11-mar17-01.zip
Click to expand...
Click to collapse
Is there any chance to get the sound working on the US version?
galulex said:
Is there any chance to get the sound working on the US version?
Click to expand...
Click to collapse
We need a new kernel, the Crisbal one used in previous attempt for CM13 US (AND ANOTHER ROMs to) have the speaker problem.
question, have you tried the version from march 11, it is booting up? what is working and what not (including GPS, SCREENCAST, WIFI TETHERING)?
A new try for US VERSION: http://www.mediafire.com/file/lavevxn25ief5d2/CM13_X800_US_ABM30_21-mar17-01_-_noROOT_-.zip
Install in TWRP after wiping cache, Dalvik/ART, DATA and system. (AT YOU OWN RISK AS USUAL!)
After flashing wipe cache and DALVIK/ART
Let see if it is booting up!
Tested on my X800 CN since you created this thread. This ROM can be used in production ! Well done ABM30 !
- WiFi : Ok
- 4G : Ok
- GPS : With LineageOS 14 I thought I had a hardware problem. With this version, it's perfect (5 to 10 sec to get a clear signal in my car)
- Phone Call : Ok
- Tethering : Ok ! That's a great news !
- Sound : Ok. Tested with internal, external (perhaps too loud), bluetooth and wire headphone
- Bluetooth : Ok
- Battery consumption : Ok
- Camera : Ok
- Automatic on/off while covering screen : Doesn't work
- Other sensors : As usual
ABM30 said:
A new try for US VERSION: http://www.mediafire.com/file/lavevxn25ief5d2/CM13_X800_US_ABM30_21-mar17-01_-_noROOT_-.zip
Install in TWRP after wiping cache, Dalvik/ART, DATA and system. (AT YOU OWN RISK AS USUAL!)
After flashing wipe cache and DALVIK/ART
Let see if it is booting up!
Click to expand...
Click to collapse
Hi.
The system flashed well but remained in the circular logo and did not start.
Thank you for trying to make it work.
EDIT
I'm looking at recovery and it does not install system.
The installation process does it in a few seconds
I have installed this ROM at my Le One X800 US but I have no information abou the battery. It is 0%.
So as requested a new initial post with an updated link. This is not my work, neither am I involved in this project.
You can download the newest version from here: https://download.mokeedev.com/?device=nx563j
Thanks, I have downloaded and upload to Mega:
https://mega.nz/#!tBZCgRrQ!UIwhGOKrfHvIIZ4SMyVaWzTagpth7K17kVHey-h644w
I think file is damaged
I think that I found the font: http://blog.beizihulian.cn/post-23.html
Did you try to install this rom?
The Rom is super smooth. Haven't experienced any bug so far.
MacLaughlin said:
The Rom is super smooth. Haven't experienced any bug so far.
Click to expand...
Click to collapse
Hows the camera and video quality compared to stock? Have you noticed any bugs yet?
Stupid qn - do we need the ADT toolbox like the site says, or can we just flash with twrp? Could I also ask if Google Apps work fine with this custom rom? Currently away from home with work with limited data, but can't wait to try a custom rom out!
ım downloading now ı will ınstall ın a bıt and write down here lıttle guıde how ıt is.
sewkanteam said:
ım downloading now ı will ınstall ın a bıt and write down here lıttle guıde how ıt is.
Click to expand...
Click to collapse
So you want to try it?
I've just installed. Everything seems fine so far, including working gapps. Except Bluetooth audio. My bluetooth headsets connect successfully, but no sound.... I never used Mokee firmwares before, how often they bring new updates (nightly, weekly)?... I hope they'll fix bluetooth problem very soon....
ermacwins said:
Hows the camera and video quality compared to stock? Have you noticed any bugs yet?
Click to expand...
Click to collapse
Maybe I found a bug on camera app. The image quality is at 12mp. Seems only to be one of the sensors. I don't know if it's the same on stock camera app from nubia. Maybe someone on stock can try to pull the apk and I will try to install it.
dorkozoid said:
Stupid qn - do we need the ADT toolbox like the site says, or can we just flash with twrp? Could I also ask if Google Apps work fine with this custom rom? Currently away from home with work with limited data, but can't wait to try a custom rom out!
Click to expand...
Click to collapse
Adt isn't needed at all.. Google services work fine. No problems.
rasimyagubov said:
I've just installed. Everything seems fine so far, including working gapps. Except Bluetooth audio. My bluetooth headsets connect successfully, but no sound.... I never used Mokee firmwares before, how often they bring new updates (nightly, weekly)?... I hope they'll fix bluetooth problem very soon....
Click to expand...
Click to collapse
Mokee is pretty big. But more popular in Eastern countries. They have the same build policy as aicp f.e.
Thank you, working awesome, and gapps work. So quick and much better, I hope Nubia release an international ROM because I like their camera suite. Bluetooth is not working, but everything else is. To get into Fastboot mode it is Vol - and Power button, not Vol +/Pwr button as per the unlocking instruction in the other thread. This is just for other newbies like me that don't know no better.
How's the camera and video quality compared to stock? Better or worse?
ermacwins said:
How's the camera and video quality compared to stock? Better or worse?
Click to expand...
Click to collapse
they have more options but ıts not better.
rasimyagubov said:
I've just installed. Everything seems fine so far, including working gapps. Except Bluetooth audio. My bluetooth headsets connect successfully, but no sound.... I never used Mokee firmwares before, how often they bring new updates (nightly, weekly)?... I hope they'll fix bluetooth problem very soon....
Click to expand...
Click to collapse
No idea, it's unofficial, so it depends on the developer...
arceoxis said:
No idea, it's unofficial, so it depends on the developer...
Click to expand...
Click to collapse
Zip for debloat ROM: https://mega.nz/#!MdomCAwB!538ZJoNHosKh_viZ6lu1qy70Eko00Ay75MmNL48t-M4
ROM is working really good, could be perfect if Nubia Camera is added to it.
Disclaimer:
* You flash this ROM at your own risk and responsibility.
* This ROM is provided without ANY WARRANTY WHATSOEVER, not even the warranty that it works.
* None of the developers of this ROM will be held accountable for any damages, complaints or anything.
This rom is pre pre pre pre alpha, almost nothing is working! Just for everybody who want see Oreo look. I'm out of free time but I will update each time when I get some free time. Whats working, whats not working...etc? You tell me! You fix something, you tell me! You found something, you tell me! Adb somehow is not working, you need to change ro.build.type from userdebug to eng and adb will start working. If you have idea about whats going on with adb, you tell me! Somehow managed to boot this rom, a lot of work and time I spent to get Oreo boot, got also credentials working but somehow camera is fail to work, probably we must use Snap camera instead of the Camera2? You can try snap camera and tell me. You can try other cameras too and tell me!
Enjoy!
Source code && how to build:
https://forum.xda-developers.com/showpost.php?p=74724831&postcount=1008
Download:
https://mega.nz/#!ZB4ilbrL!nI_YV54IMBmKpA1BE4L9VYcwm3nsuLXAGKOu35NJdyQ
Can you post some screenshoots? Whats working? Whats not working? Etc? I'm so lazy
risk
while it is very risky to put this firmware.
munjeni said:
Can you post some screenshoots I'm so lazy Whats working? Whats not working? Etc?
Click to expand...
Click to collapse
Not a risky, just some more things is not working! Bugs need to be identified and fixed one by one.
Mobile data and camera are not working.
Viktor245 said:
Mobile data and camera are not working.
Click to expand...
Click to collapse
Wifi ok?
munjeni said:
Wifi ok?
Click to expand...
Click to collapse
Do not have the opportunity to check it out.
munjeni said:
Wifi ok?
Click to expand...
Click to collapse
Wifi can't be opened
Waoo, I changed my phone, now I can use my z1c to test all lol
In the afternoon I'm going to install it!
i will wait for working mobile data and wifi build
omkarmahananda said:
i will wait for working mobile data and wifi build
Click to expand...
Click to collapse
Me too I'm opened source code ppublic, everybody if free to use it and try fix something.
munjeni said:
Me too I'm opened source code ppublic, everybody if free to use it and try fix something.
Click to expand...
Click to collapse
actually i have no idea how this thing work.
but can you help learning ?!
any thread or any website or anything?
thank you
Did you have think include magisk for this version?
Sorry for being late:
Audio doesn't work
Wifi doesn't work
I'm not able to test cell data
Camera doesn't work, neither footej
ADB doesn't work, no usb at all, the device isn't listed neither with adb devices and devices control panel in windows
Bluetooth yes
Vibrating yes
@hackintosh5 here
Heyho. I just tested building from @munjeni 's sources. Unfortunately TWRP throwed an error 6. I checked the updater script and found some strange lines. With them removed I was able to install and boot
I'm really up for doing some fixes, but for me it's learning by doing which can be a time intensive process.
BTW: USB transfer works by disabling ADB in developer options... I just copied the screenshots off the device.
115ek said:
Heyho. I just tested building from @munjeni 's sources. Unfortunately TWRP throwed an error 6. I checked the updater script and found some strange lines. With them removed I was able to install and boot
I'm really up for doing some fixes, but for me it's learning by doing which can be a time intensive process.
BTW: USB transfer works by disabling ADB in developer options... I just copied the screenshots off the device.
Click to expand...
Click to collapse
But ADB works to you? Can you see the phone if you do adb devices?
@munjeni can I try to replace the libs just like as porting a custom rom from the N builds? Or it is wasted time?
-totonio- said:
But ADB works to you? Can you see the phone if you do adb devices?
Click to expand...
Click to collapse
Yes, adb works. But only if you revert this commit https://github.com/munjeni/android_device_sony_amami/commit/e0cde4386d51ad2b45d7700f495a85fdb75dc8d2.
Adb from the 8.0 tree seems to be broken, but maybe it's a problem with our devicetree.
Nevertheles, as Munjeni already did, replacing the adbd with a prebuilt one (I used one from an Android 7 tree i had lying around) works quite fine.
@munjeni : Is adb built from 8.0 source working for you? Or is it a permission problem?
Hey. I've got some news. Wifi was working for me. I just installed a new build and was able to connect
I can't test data connection - the sim reader is broken in my test device.
I think we should move ahead to lineage 15.1 (android 8.1) because support for lineage 15.0 was already dropped.
Unfortunately there are several build issues - let's see what the time brings.
*Edit: adb is fixed now
Booted 15.1 some minutes ago.
Working
adb
MTP
brightness slider
not working
wifi
automatic brightness
audio
camera
LEDs
everything else...
So I have been trying to get LDAC or apt-X working on my razer phone but it has not worked. I am on the latest stock ROM rooted with magisk (via ADB not TWRP) and with the rayglobe magisk module installed but it just stays on AAC. My headphones are Sony WH-1000XM2 and LDAC was working when using the resurrection remix ROM from the development thread but I had to uninstall the ROM due to instability and no sign of progression. Any help would be appreciated.
Firebuster said:
So I have been trying to get LDAC or apt-X working on my razer phone but it has not worked. I am on the latest stock ROM rooted with magisk (via ADB not TWRP) and with the rayglobe magisk module installed but it just stays on AAC. My headphones are Sony WH-1000XM2 and LDAC was working when using the resurrection remix ROM from the development thread but I had to uninstall the ROM due to instability and no sign of progression. Any help would be appreciated.
Click to expand...
Click to collapse
They locked it down somehow I think. I have 2 threads in here asking for help but no one seems to be able to help me. For added reference, here is the error produced even when all the files are added with root to enable aptx or ldac
I installed the magisk aptx&aptxHD module and modified /system/vendor/build.prop then aptx got working.
(I couldn't test with aptxHD or LDAC cos I have no compatibe device with them.)
Code:
persist.vendor.bt.a2dp_offload_cap=sbc-aac
to
Code:
persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptXHD
This is the same parameter the magisk module set to /system/build.prop.
To guess, LDAC will may work if an appropriate value set to the prop.
ClubRaptor said:
I installed the magisk aptx&aptxHD module and modified /system/vendor/build.prop then aptx got working.
(I couldn't test with aptxHD or LDAC cos I have no compatibe device with them.)
to
This is the same parameter the magisk module set to /system/build.prop.
To guess, LDAC will may work if an appropriate value set to the prop.
Click to expand...
Click to collapse
This worked to enable switching to them however now Bluetooth just crashes. I changed it to persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-ldac
Edit:
Some interesting notes. I tried a few steps to debugging including readding AAC to the list which did nothing but if I only add aptx then the Bluetooth app no longer crashes however no sound plays so I'm guessing it's the lib files that are not correct? I just used the aptx package in magisk so if there's any other that I'm missing or other suggestions that would be useful
Firebuster said:
This worked to enable switching to them however now Bluetooth just crashes. I changed it to persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-ldac
Edit:
Some interesting notes. I tried a few steps to debugging including readding AAC to the list which did nothing but if I only add aptx then the Bluetooth app no longer crashes however no sound plays so I'm guessing it's the lib files that are not correct? I just used the aptx package in magisk so if there's any other that I'm missing or other suggestions that would be useful
Click to expand...
Click to collapse
I still can't get it to switch to aptx (the one I want) or ldac. It still falls back to SBC usually or aac if I'm on a different speaker. Any idea what I'm doing wrong? I'm on slot a on my device, rooted with magisk and I have tried multiple aptx modules. Is there a specific build.prop editor you use? Both my speakers and headphones support it and work with other devices and I'm still getting the error I replied with above (page one)
I'm an experienced rooter, so don't be afraid to fully explain any steps I may be missing out!
manor7777 said:
I still can't get it to switch to aptx (the one I want) or ldac. It still falls back to SBC usually or aac if I'm on a different speaker. Any idea what I'm doing wrong? I'm on slot a on my device, rooted with magisk and I have tried multiple aptx modules. Is there a specific build.prop editor you use? Both my speakers and headphones support it and work with other devices and I'm still getting the error I replied with above (page one)
I'm an experienced rooter, so don't be afraid to fully explain any steps I may be missing out!
Click to expand...
Click to collapse
I used root explorer and changed the build.prop entries in system\vendor\. In the first place I used the root essentials build.prop editor which shows a different build.prop. other than that I literally just edited that line and that allowed me to change it. I can't think of anything else I did other than install a bunch of library files which I'm guessing you found the same ones as me because it was very limited on what was available and up to date
Firebuster said:
I used root explorer and changed the build.prop entries in system\vendor\. In the first place I used the root essentials build.prop editor which shows a different build.prop. other than that I literally just edited that line and that allowed me to change it. I can't think of anything else I did other than install a bunch of library files which I'm guessing you found the same ones as me because it was very limited on what was available and up to date
Click to expand...
Click to collapse
OK, awesome. You rock. That got it to select aptx - now my 2nd problem, no audio! I can see in dev options and bt settings that it's showing aptx, but I get no audio (well, I get an almost click click click noise) then my Bluetooth adaptor for my headphones crashes. And it forces my headphones to turn off. I tried 3 different magisk modules for the library files, any ideas - I was getting SBC audio before
manor7777 said:
OK, awesome. You rock. That got it to select aptx - now my 2nd problem, no audio! I can see in dev options and bt settings that it's showing aptx, but I get no audio (well, I get an almost click click click noise) then my Bluetooth adaptor for my headphones crashes. And it forces my headphones to turn off. I tried 3 different magisk modules for the library files, any ideas - I was getting SBC audio before
Click to expand...
Click to collapse
Sounds like the same problem I am having. Aptx doesn't work and aptx HD and LDAC just crash Bluetooth. Genuinely have no idea where to go from here. It must be a driver or library file. Real shame it's not working.
Edit: seems to be looping these messages in catlog
Firebuster said:
Sounds like the same problem I am having. Aptx doesn't work and aptx HD and LDAC just crash Bluetooth. Genuinely have no idea where to go from here. It must be a driver or library file. Real shame it's not working.
Click to expand...
Click to collapse
OK, so last night and this morning I have been just messing with things. I no longer crash my headphones and force them to turn off, but I still have no audio over aptx - though at least it's not crashing my headphones (Bluetooth in the phone was always OK). There is one error I'm getting and I'm not sure if its related of not, but is to do with a buffer failing to release. See my screenshots of logs (just documenting here for reference)
so basically i went your path a few days ago and dropped that idea. please post updates if you manage to get aptx\aptx hd\ldac working (Razer Phone + Sony WH-1000 XM2)
hatemosphere said:
so basically i went your path a few days ago and dropped that idea. please post updates if you manage to get aptx\aptx hd\ldac working (Razer Phone + Sony WH-1000 XM2)
Click to expand...
Click to collapse
Cc @Firebuster
So, I might be an experienced rooter (no 1 click toolkits here) I am NOT a developer. I've tried a combination of a bunch of things to try and get this to work, and nothing has!
I did however get it to work by installing a GSI (basically a rom) to the device, but even that was painful to get working (well, installed). Now running AOSP 8.1 GSI w/gapps and I flashed magisk for root. I then installed the Aptx magisk module from the built in repo and it works perfectly fine. Not sure if It's something in razer software as I'm technically more up to date now so it's not like I was using the wrong drivers.
Can't find a decent dolby atmos I can install that will work along side v4a, all the magisk modules are for android 7 or 6.
Otherwise that's the only way I have found so far, sorry guys! - benefit is, other than AOSP's ****ty camera app (use the gcam port instead), literally everything works fine, and I even get stronger vibration on a GSI
manor7777 said:
Cc @Firebuster
So, I might be an experienced rooter (no 1 click toolkits here) I am NOT a developer. I've tried a combination of a bunch of things to try and get this to work, and nothing has!
I did however get it to work by installing a GSI (basically a rom) to the device, but even that was painful to get working (well, installed). Now running AOSP 8.1 GSI w/gapps and I flashed magisk for root. I then installed the Aptx magisk module from the built in repo and it works perfectly fine. Not sure if It's something in razer software as I'm technically more up to date now so it's not like I was using the wrong drivers.
Can't find a decent dolby atmos I can install that will work along side v4a, all the magisk modules are for android 7 or 6.
Otherwise that's the only way I have found so far, sorry guys! - benefit is, other than AOSP's ****ty camera app (use the gcam port instead), literally everything works fine, and I even get stronger vibration on a GSI
Click to expand...
Click to collapse
Yeah I might move onto that too. To try to fix the Bluetooth issues. I can only assume razer excluded some of the functionality but since it's baked into android 8 I don't see why they would remove it.
Razer and their development team is already informed about this issue, and they have correctly addressed it, and all the Bluetooth issues (which were a few), in the upcoming update MR2. No ETA.
linuxct said:
Razer and their development team is already informed about this issue, and they have correctly addressed it, and all the Bluetooth issues (which were a few), in the upcoming update MR2. No ETA.
Click to expand...
Click to collapse
so i've just got a new update and now i'm wondering if we should try this again...
hatemosphere said:
so i've just got a new update and now i'm wondering if we should try this again...
Click to expand...
Click to collapse
Go ahead, I can't since I'm on a Pie GSI.
If anyone has an LDAC BT Headset please give this a try.
cc @Firebuster
Great news, I just spent 2 hours updating my phone, with flashing back to stock because the OTA did not want to update me since I had Magisk, then putting everything back like before.
The update did not change anything.
Tried to do my research on issues with the Razer phone before getting it, but I guess this is just one of those things you don't comprehend until actually having the device in your hands. I came from a Oneplus One on Lineage OS and am comfortable with flashing (but no experience with GSI yet).
My razer phone is stock and not rooted. Anything I can do to contribute to test getting Apt-X working? The settings says my phone is up to date (build number OPM1.171019.011-RZR-180803.6033).
Got the official Pie installed - no LDAC nor AptX still.
cubeover said:
Got the official Pie installed - no LDAC nor AptX still.
Click to expand...
Click to collapse
you installed the official pie update for the razer phone 1?
I've tried all treble pie roms and in all are the same problem with Bluetooth in call sound. First I thougt it's a problem with my elephone u pro, but in the meanwhile I've recognized that the same problem exist in many phones.
I'll hope that we can support the developers with a payment if they fix this problem.
I am willing to pay up to 50$ if someone is able to fix this problem for the elephone u pro.
If there's someone else who wants to get the problem solved then please write here your payment offer.
But it would be a shame if people make an offer here and do not stick to it later.
Root first, then go to Vendor/Overlay/BluetoothResCommon.apk
delete it,then reboot,
a05haiji28 said:
Root first, then go to Vendor/Overlay/BluetoothResCommon.apk
delete it,then reboot,
Click to expand...
Click to collapse
I'll try in the bext days....
a05haiji28 said:
Root first, then go to Vendor/Overlay/BluetoothResCommon.apk
delete it,then reboot,
Click to expand...
Click to collapse
Hi, I've tried today but in my elephone u pro there isn't a Vendor/Overlay/BluetoothResCommon.apk
Other ideas?
Laptapper said:
I've tried all treble pie roms and in all are the same problem with Bluetooth in call sound. First I thougt it's a problem with my elephone u pro, but in the meanwhile I've recognized that the same problem exist in many phones.
I'll hope that we can support the developers with a payment if they fix this problem.
I am willing to pay up to 50$ if someone is able to fix this problem for the elephone u pro.
If there's someone else who wants to get the problem solved then please write here your payment offer.
But it would be a shame if people make an offer here and do not stick to it later.
Click to expand...
Click to collapse
1. You have to extract stock /vendor/etc/audio/audio_policy_configuration.xml and delete A2DP related section like this:
https://github.com/PixelExperience-...mmit/977444af69f10fc135d07e19f1e5f1183e73e9ff
then replace it (by root explorer or creating magisk module).
2. You also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
NOTE: This works only on CAF based custom roms. It doesn't work on AOSP.
AndroPlus said:
You have to extract stock /vendor/etc/audio/audio_policy_configuration.xml and delete A2DP related section like this:
https://github.com/PixelExperience-...mmit/977444af69f10fc135d07e19f1e5f1183e73e9ff
then replace it (by root explorer or creating magisk module).
Click to expand...
Click to collapse
Hi
I've tried, but the changed and saved file
/vendor/etc/audio/audio_policy_configuration.xml
will be automatically deleted at restart.
The folder is empty after restart.
Any ideas?
Laptapper said:
Hi
I've tried, but the changed and saved file
/vendor/etc/audio/audio_policy_configuration.xml
will be automatically deleted at restart.
The folder is empty after restart.
Any ideas?
Click to expand...
Click to collapse
Oops, you also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
AndroPlus said:
Oops, you also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
Click to expand...
Click to collapse
Great job! Bluetooth In call is working.
I'll think it's not your development but for your know how to, I've send you 15 Euro.
Do you know also how to get Bluetooth audio music working?
By any chance did you get fully functional Bluetooth on the gsi rom or anyone else?
[email protected] said:
By any chance did you get fully functional Bluetooth on the gsi rom or anyone else?
Click to expand...
Click to collapse
I'll hope so.
@AndroPlus has already fixed in call and may be he's on the way to solve audio also.
Has it been rectified in all builds
so is it safe to say that we can install the latest version of GSI provided by rom providers made in and released in march.
I would like to know that before i go ahead and transition over from stock to custom rom... mainly called PixelDust Pie rom version march
Laptapper said:
Great job! Bluetooth In call is working.
I'll think it's not your development but for your know how to, I've send you 15 Euro.
Do you know also how to get Bluetooth audio music working?
Click to expand...
Click to collapse
Thank you, but BT music works fine on my phone (Mi 9).
I don't know how to fix it...
[email protected] said:
so is it safe to say that we can install the latest version of GSI provided by rom providers made in and released in march.
I would like to know that before i go ahead and transition over from stock to custom rom... mainly called PixelDust Pie rom version march
Click to expand...
Click to collapse
No, the fix needs device specific path and not all GSI has it.
I have the Razer Phone and have got either audio working or in call but never both... I am in the process of going through both audio routing files and see if I can combine them to get it to work, but I haven't messed with Android in years so it's taking more time than I anticipated to get caught up on all the changes you guys have made. The last time I built a rom was when treble was just on the discussion table. It really amazes me this bug has gone on this long, but maybe there's more to it than I'm seeing so far. I have seen some good devs working on this.
Enlighten me Please
AndroPlus said:
Thank you, but BT music works fine on my phone (Mi 9).
I don't know how to fix it...
No, the fix needs device specific path and not all GSI has it.
Click to expand...
Click to collapse
Hey @AndroPlus , could you possibly explain how to go about it. I would appreciate the help. I have got a nokia 7 plus with pixel dust pie rom on latest version running. Where and what do i need to do to get it up and running on my phone. I need to get in call bluetooth running. Thats the only thing stopping me from using this amazing blazing rom
Bluetooth music also does not work with me. However bluetooth calls work, so its weird that music/audio is not working.
Bluetooth music also does not work for me, but bluetooth calls work fine. I'm using Arrow GSI with Mi Mix 3.
Laptapper said:
Great job! Bluetooth In call is working.
I'll think it's not your development but for your know how to, I've send you 15 Euro.
Do you know also how to get Bluetooth audio music working?
Click to expand...
Click to collapse
That's on my AOSP ROM?
phhusson said:
That's on my AOSP ROM?
Click to expand...
Click to collapse
It's on resurrection remix pie, also headset over usb c is working. Only audio sound over Bluetooth is a problem. Do you've got a solution ir an idea what should I can try?
Btw do you have any idea how to control the led colours?
i still have no bluetooth calling on Mi Mix 3 on the @AndroPlus rom's so his solution definitely doesn't work for all devices.
furthermore there is still a bounty to get bluetooth working perfectly on vanilla android gsi's
AndroPlus said:
Oops, you also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
Click to expand...
Click to collapse
Thank you sooo much! That´s all, I needed to do to fix my incall audio problem!
No changes in audio_policy.xml were needed - only removing this line from rw-system.sh