Related
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?
Disclaimer: I am not a developer (I don't code), but I have been flashing ROMs for many devices over the years. This is more of a practical guide from an end-user perspective in pursuit of finding the best ROM for this magnificent hardware. This is more of a compilation of all the relevant information I found. I'm very open to suggestions/corrections that could improve this.
Disclaimer: Only tested with RR, PixelExperience, and ArrowOS GSI.
I haven't seen a proper guide to flash GSI ROMs for Mi Mix 3, thus I decided to share what I know that works. I put a brief explanation for each step below.
1. Unlock Bootloader - If you haven't done so yet, I recommend following the instructions in https://www.reddit.com/r/Xiaomi/wiki/bootloader
2. Install TWRP
a) I recommend to use the official TWRP from this link https://twrp.me/xiaomi/xiaomimix3.html or refer to the forum https://forum.xda-developers.com/mi-mix-3/development/recovery-unofficial-twrp-recovery-t3901261.
b) To install TWRP, I recommend to follow the instructions from Xiaomi.eu. For those not familiar, the "twrp.img" in the code should be the full path of the file. Something like "D:\folder\twrp.img"
c) If you have an older version of TWRP, I suggest to update it to the official.
3. Install Xiaomi.eu - Start from this step in case of bootloops or issues (especially caused by Magisk modules by my experience)
a) This is what I do instead of the 'flash vendor.img from Chinese Dev' prerequisite mentioned in other threads. This is an easier step (just one flash in TWRP) and a better fallback (a working ROM) in case things go wrong. I have had no issues (fingerprint, calls, etc..) with this and I've done this thrice.
b) Download the latest MIUIv10.2 Stable for MIMix3 from the link https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/.
c) Wipe > Format Data (prevents problems, and removes encryption if you had it). Also do Factory Reset (idk, just to be sure).
d) Copy xiaomi.eu ROM to internal storage, then Install > Flash. No need to boot/restart, proceed to the next step.
4. Install GSI ROM - wth is GSI? https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
a) We can actually install any GSI in https://forum.xda-developers.com/project-treble/trebleenabled-device-development but there is an issue in installing Google Apps (Open GApps) as many people mentioned in https://forum.xda-developers.com/mi-mix-3/development/9-0-resurrection-remix-v7-0-t3891975 and as confirmed by the official TWRP thread https://forum.xda-developers.com/mi...p-recovery-t3901261/post79035909#post79035909
b) Given the above, the only feasible options are GSI ROMs with built-in GApps and the only 2 I found are PixelExperience GSI and ArrowOS GSI. As GApps is integrated in the system.img, no need to flash Open GApps thus no issues. Having tried both, I personally recommend ArrowOS due to the performance and additional customization options.
c) Download the arm64 AB version (ArrowOS as an example) https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
d) Copy the resulting system.img to internal storage (extract if its a .zip), in TWRP click Install > Install Images > select system.img of ArrowOS > select System partition. You can now boot, or follow next step to root with Magisk.
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-mix-3/how-to/root-magisk-18-2-mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Final Thoughts
ArrowOS GSI seems to be stable enough and I'm using it as my daily driver now. I am so much happier compared to when using MIUI Global ROM. I really like the performance (very fluid), battery life (a lot better than MIUI Global), customizations (like traffic indicator, status bar stuff), unli Google Photos, and everything that makes AOSP/stock android awesome. No more bloatware, annoying non-dismissable notifications, and horrible auto brightness from MIUI.
The only real issue I encountered so far is the bluetooth audio/music issue, but this seems to be a common problem in GSI ROMs. Bluetooth calls work though. There is no app to handle the slider (but I don't care. lol). Lastly, the AI button becomes useless, but see below for the fix.
Optional stuff that makes things better:
1. Remapping AI button - When using GSI ROMs, AI button becomes useless. But to map it back to Google Assistant (or anything actually), follow the instructions from this thread (needs some knowledge about Tasker). https://forum.xda-developers.com/showpost.php?p=78523778&postcount=38 For the Tasker Task, I selected Input > Voice Command. This now assigns the button to open Google Assistant. Does not work well when screen is off though, but its just easy to unlock.
2. Google Camera - The main reason why I bought this phone. Google Camera brings out the best in the awesome camera - Use this version https://forum.xda-developers.com/mi-mix-3/themes/gcam-6-manual-focus-long-exposure-t3885610
3. Stereo Speaker Mod - https://forum.xda-developers.com/mi-mix-3/themes/magisk-stereo-speaker-mod-mix-3-t3900580 Makes the phone earpiece into a speaker, increasing overall volume. I personally use version 3 and I'm very happy.
4. Fluid NG - App in Google Play Store to have the same recents/home/back gestures from MIUI 10.
reasonablebasis said:
Disclaimer: I am not a developer (I don't code), but I have been flashing ROMs for many devices over the years. This is more of a practical guide from an end-user perspective in pursuit of finding the best ROM for this magnificent hardware. This is more of a compilation of all the relevant information I found. I'm very open to suggestions/corrections that could improve this
I haven't seen a proper guide to flash GSI ROMs for Mi Mix 3, thus I decided to share what I know that works. I put a brief explanation for each step below.
1. Unlock Bootloader - If you haven't done so yet, I recommend following the instructions in https://www.reddit.com/r/Xiaomi/wiki/bootloader
2. Install TWRP
a) I recommend to use the official TWRP from this link https://twrp.me/xiaomi/xiaomimix3.html or refer to the forum https://forum.xda-developers.com/mi-mix-3/development/recovery-unofficial-twrp-recovery-t3901261.
b) To install TWRP, I recommend to follow the instructions from Xiaomi.eu. For those not familiar, the "twrp.img" in the code should be the full path of the file. Something like "D:\folder\twrp.img"
c) If you have an older version of TWRP, I suggest to update it to the official.
3. Install Xiaomi.eu - Start from this step in case of bootloops or issues (especially caused by Magisk modules by my experience)
a) This is what I do instead of the 'flash vendor.img from Chinese Dev' prerequisite mentioned in other threads. This is an easier step (just one flash in TWRP) and a better fallback (a working ROM) in case things go wrong. I have had no issues (fingerprint, calls, etc..) with this and I've done this thrice.
b) Download the latest MIUIv10.2 Stable for MIMix3 from the link https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/.
c) Wipe > Format Data (prevents problems, and removes encryption if you had it). Also do Factory Reset (idk, just to be sure).
d) Copy xiaomi.eu ROM to internal storage, then Install > Flash. No need to boot/restart, proceed to the next step.
4. Install GSI ROM - wth is GSI? https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
a) We can actually install any GSI in https://forum.xda-developers.com/project-treble/trebleenabled-device-development but there is an issue in installing Google Apps (Open GApps) as many people mentioned in https://forum.xda-developers.com/mi-mix-3/development/9-0-resurrection-remix-v7-0-t3891975 and as confirmed by the official TWRP thread https://forum.xda-developers.com/mi...p-recovery-t3901261/post79035909#post79035909
b) Given the above, the only feasible options are GSI ROMs with built-in GApps and the only 2 I found are PixelExperience GSI and ArrowOS GSI. As GApps is integrated in the system.img, no need to flash Open GApps thus no issues. Having tried both, I personally recommend ArrowOS due to the performance and additional customization options.
c) Download the arm64 AB version (ArrowOS as an example) https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
d) Copy the resulting system.img to internal storage (extract if its a .zip), in TWRP click Install > Install Images > select system.img of ArrowOS > select System partition. You can now boot, or follow next step to root with Magisk.
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-mix-3/how-to/root-magisk-18-2-mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Final Thoughts
ArrowOS GSI seems to be stable enough and I'm using it as my daily driver now. I am so much happier compared to when using MIUI Global ROM. I really like the performance (very fluid), battery life (a lot better than MIUI Global), customizations (like traffic indicator, status bar stuff), unli Google Photos, and everything that makes AOSP/stock android awesome. No more bloatware, annoying non-dismissable notifications, and horrible auto brightness from MIUI.
The only real issue I encountered so far is the bluetooth audio/music issue, but this seems to be a common problem in GSI ROMs. Bluetooth calls work though. There is no app to handle the slider (but I don't care. lol). Lastly, the AI button becomes useless, but see below for the fix.
Optional stuff that makes things better:
1. Remapping AI button - When using GSI ROMs, AI button becomes useless. But to map it back to Google Assistant (or anything actually), follow the instructions from this thread (needs some knowledge about Tasker). https://forum.xda-developers.com/showpost.php?p=78523778&postcount=38 For the Tasker Task, I selected Input > Voice Command. This now assigns the button to open Google Assistant. Does not work well when screen is off though, but its just easy to unlock.
2. Google Camera - The main reason why I bought this phone. Google Camera brings out the best in the awesome camera - Use this version https://forum.xda-developers.com/mi-mix-3/themes/gcam-6-manual-focus-long-exposure-t3885610
3. Stereo Speaker Mod - https://forum.xda-developers.com/mi-mix-3/themes/magisk-stereo-speaker-mod-mix-3-t3900580 Makes the phone earpiece into a speaker, increasing overall volume. I personally use version 3 and I'm very happy.
Click to expand...
Click to collapse
Not all GSI work ontop of Xiaomi Eu
Flashing magisk and safety net patch also doesn't guarantee safety net passing on a few of the GSI as well. CTS will fail for obvious reasons
Mackay53 said:
Not all GSI work ontop of Xiaomi Eu
Flashing magisk and safety net patch also doesn't guarantee safety net passing on a few of the GSI as well.
Click to expand...
Click to collapse
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
reasonablebasis said:
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
Click to expand...
Click to collapse
Can't remember as it was a while ago, possibly OctoOS and descendant and 1 other, omni ROM maybe.
For the ones that come with SU you need to navigate to the xbin folder in the system and remove the SU file.
Then cause Xiaomi EU uses the wrong fingerprint props you need to use the magisk props config module and manually type in the mix 3 fingerprint (unless the module has been updated to include mix 3).
If you installed the Chinese dev vendor then the props will be there ready to be used so the magisk module can make them active without manually typing it. This will sort out both safety net fails.
If this was sometime ago, the features in China Dev would have already been integrated in the latest China Stable, which is the basis of Xiaomi.EU.
Maybe you can test it now to see if Xiaomi.EU really works. I tried it with RR, PixelExperience, and ArrowOS and I'm facing no issues. So flashing China Dev vendor.img seems to be an outdated instruction.
reasonablebasis said:
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
Click to expand...
Click to collapse
Pixel dust gsi too....
reasonablebasis said:
If this was sometime ago, the features in China Dev would have already been integrated in the latest China Stable, which is the basis of Xiaomi.EU.
Maybe you can test it now to see if Xiaomi.EU really works. I tried it with RR, PixelExperience, and ArrowOS and I'm facing no issues. So flashing China Dev vendor.img seems to be an outdated instruction.
Click to expand...
Click to collapse
The 3 GSI you mention is a very small sample of the GSI available so you can't say it's an outdated instruction. Have you tested them all like I have? No you haven't.
Xiaomi EU does not use the correct mix3 vendor.img, that's what causes the issue.
Mackay53 said:
The 3 GSI you mention is a very small sample of the GSI available so you can't say it's an outdated instruction. Have you tested them all like I have? No you haven't.
Xiaomi EU does not use the correct mix3 vendor.img, that's what causes the issue.
Click to expand...
Click to collapse
Ok, I'll put a disclaimer that this only works on RR, PixelExperience, and ArrowOS. Anyway, I'm sure that the latest stable Xiaomi.EU vendor works without any issues with ArrowOS, else why would I be using it as my daily driver.
[deleted, duplicate post]
Someone know if there is a GSI with gapps and that don't have issue with bluetooth?
SafetyPatch module
reasonablebasis said:
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-...mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Click to expand...
Click to collapse
Mate, I can't find this module via Magisk Manager... Please help!
jonny908 said:
Mate, I can't find this module via Magisk Manager... Please help!
Click to expand...
Click to collapse
You sure? Try searching for "SafetyPatch"
reasonablebasis said:
You sure? Try searching for "SafetyPatch"
Click to expand...
Click to collapse
Strange....
reasonablebasis said:
You sure? Try searching for "SafetyPatch"
Click to expand...
Click to collapse
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
jonny908 said:
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
Click to expand...
Click to collapse
On Arrow ?
Wahoux said:
On Arrow ?
Click to expand...
Click to collapse
Yep! Not sure how to prove that though xD
Android Q GSI !
https://www.xda-developers.com/android-q-gsi-project-treble/
Wahoux said:
Android Q GSI !
https://www.xda-developers.com/android-q-gsi-project-treble/
Click to expand...
Click to collapse
Dare to try? xD
jonny908 said:
Dare to try? xD
Click to expand...
Click to collapse
ahah no xD
Right now i'm about to flash Arrow, I hope I won't have bluetooth issue . On the non-GSI Pixel Experience, some reported issue with bluetooth whereas it was working fine for me... so let's see :fingers-crossed:
jonny908 said:
Mate, I can't find this module via Magisk Manager... Please help!
Click to expand...
Click to collapse
jonny908 said:
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
Click to expand...
Click to collapse
Wow good for you. You flashed xiaomi.eu prior to GSI right? enumerate the steps you did, so that we we hopefully can replicate your success. Hehe
Is there a way to have LDAC bluetooth codec back?
I have Android 9, many months ago was available from Developer Menu, but with latest security patches, it does not work anymore: you can select LDAC from Developer Options but the settings disappear as soon as you get out from the menu.
Before it worked (I have Sony MD-1000X headphone which supports LDAC).
nicosea said:
Is there a way to have LDAC bluetooth codec back?
I have Android 9, many months ago was available from Developer Menu, but with latest security patches, it does not work anymore: you can select LDAC from Developer Options but the settings disappear as soon as you get out from the menu.
Before it worked (I have Sony MD-1000X headphone which supports LDAC).
Click to expand...
Click to collapse
Hello there I am Lacia the official maintainer of posp my latest official build includes the LDAC bluetooth codec so feel free to try it out! you can also join our telegram group over at https://t.me/pospdaisy
I have the same problem, and don't really care about installing a custom rom.
Any help?
nicosea said:
Is there a way to have LDAC bluetooth codec back?
I have Android 9, many months ago was available from Developer Menu, but with latest security patches, it does not work anymore: you can select LDAC from Developer Options but the settings disappear as soon as you get out from the menu.
Before it worked (I have Sony MD-1000X headphone which supports LDAC).
Click to expand...
Click to collapse
On stock, not even AAC Bluetooth can be selectable after like April 2019 update version (my father's Pioneer car system does have AAC BT mode). It can be selected in Dev Opts, but after you exit the option, it will revert back to SBC (normal) mode and also the audio did not changed too. I guess it's another bug by Xiaomeme that haven't fixed.
...and I have moved out to just using custom ROMs long ago, then these modes (AAC, APTX, etc.) works as intended.
RFD80M-75679 said:
On stock, not even AAC Bluetooth can be selectable after like April 2019 update version (my father's Pioneer car system does have AAC BT mode). It can be selected in Dev Opts, but after you exit the option, it will revert back to SBC (normal) mode and also the audio did not changed too. I guess it's another bug by Xiaomeme that haven't fixed.
...and I have moved out to just using custom ROMs long ago, then these modes (AAC, APTX, etc.) works as intended.
Click to expand...
Click to collapse
Could you tell me which custom ROM / ROMs are you using with Mi A2 Lite to have Aptx and LDAC back (and where to find these ROMs)?
Thank you
nicosea said:
Could you tell me which custom ROM / ROMs are you using with Mi A2 Lite to have Aptx and LDAC back (and where to find these ROMs)?
Thank you
Click to expand...
Click to collapse
On POSP (and I think many AOSP-based ROMs), it managed to activate the AAC Bluetooth automatically with my father's car stereo. On virtually any Android Pie custom ROMs, most can switch modes to APTX (when I did have the KZ Earphones Bluetooth module with APTX, now dead due to my KZ BT module's capacitor died suddenly).
Ok, I managed to keep stock rom and add at least aptx support with unlocked bootloader + magisk + magisk modules.
Just hope that Xiaomi will fix this with Android 10 update
Matyt said:
Ok, I managed to keep stock rom and add at least aptx support with unlocked bootloader + magisk + magisk modules.
Just hope that Xiaomi will fix this with Android 10 update
Click to expand...
Click to collapse
Any guide or instructions to do that? I'm not so experience with ROMs and magisk...
If I understood you well I need to:
- unlock bootloader
- install magisk and than magisk modules (I can Google)
But no need for root rights and a full custom ROM like POSP, correct?
And no support for Ldac anyway?
nicosea said:
Any guide or instructions to do that? I'm not so experience with ROMs and magisk...
If I understood you well I need to:
- unlock bootloader
- install magisk and than magisk modules (I can Google)
But no need for root rights and a full custom ROM like POSP, correct?
And no support for Ldac anyway?
Click to expand...
Click to collapse
Magisk is a rooting tool (like SuperSU) and using modules need root (but custom ROM isn't needed if you just want stock). You need an unlocked bootloader, Magisk manager APK, a patched boot.img (should be matched your stock version 10.0.x.0) and some steps to have it rooted.
https://forum.xda-developers.com/mi...gisk-proper-support-ota-t3836952/post77498252
I unlocked the bootloader using this:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-unlock-bootloader-losing-user-data-t4053743
Then installed magisk using this:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952 (scroll until the end of the thread to find the jan 2020 patched .img)
And then, installed a magisk module for aptx.
No LDAC for now.
Hi, I did some experiments with the GSI PIXEL EXPERIENCE ALPHA that might interest some developers.
It works properly as is on nairo (moto g 5g plus) except for a few things.
- TWRP recovery gets broken, i think we need a newer version for this phone to work with android 12.
- The audio doesn't get routed in any way (i've tried with apps) to the aux output (headset).
I would take care of this problems if i had knowledge, if anyone can help it's welcome for sure, thanks in advance!
Tommy0000 said:
Hi, I did some experiments with the GSI PIXEL EXPERIENCE ALPHA that might interest some developers.
It works properly as is on nairo (moto g 5g plus) except for a few things.
- TWRP recovery gets broken, i think we need a newer version for this phone to work with android 12.
- The audio doesn't get routed in any way (i've tried with apps) to the aux output (headset).
I would take care of this problems if i had knowledge, if anyone can help it's welcome for sure, thanks in advance!
Click to expand...
Click to collapse
1 share the gsi twrp is broken for even on a android 11 gsi as for audio
1. Go to developer options, find something like "Disable A2DP offload", turn it on and restart your device.
2. After the restart head back to settings, head to Phh Treble settings, then misc and enable "Force headphone switch" and
wesleyvanneck12345678 said:
1 share the gsi twrp is broken for even on a android 11 gsi as for audio
1. Go to developer options, find something like "Disable A2DP offload", turn it on and restart your device.
2. After the restart head back to settings, head to Phh Treble settings, then misc and enable "Force headphone switch" and
Click to expand...
Click to collapse
Thank you very much, i'll try it, i don't get yor first sentence, is it broken for everyone? (english isn't my first language)
wesleyvanneck12345678 said:
1 share the gsi twrp is broken for even on a android 11 gsi as for audio
1. Go to developer options, find something like "Disable A2DP offload", turn it on and restart your device.
2. After the restart head back to settings, head to Phh Treble settings, then misc and enable "Force headphone switch" and
Click to expand...
Click to collapse
It worked without forcing headphone switch, tysm! Now i'm working to get some padding on the status bar if i'm able to
Tommy0000 said:
It worked without forcing headphone switch, tysm! Now i'm working to get some padding on the status bar if i'm able to
Click to expand...
Click to collapse
if make cutout work send it phhusson
wesleyvanneck12345678 said:
if make cutout work send it phhusson
Click to expand...
Click to collapse
I successfully made one with nonsense notch, idk if i can send phh the apk the module created, i used the customleft script at 240 px
Tommy0000 said:
I successfully made one with nonsense notch, idk if i can send phh the apk the module created, i used the customleft script at 240 px
Click to expand...
Click to collapse
share it with me am waiting for fix to long with gsis
Tommy0000 said:
I successfully made one with nonsense notch, idk if i can send phh the apk the module created, i used the customleft script at 240 px
Click to expand...
Click to collapse
you cant send it to him but i didnt know mudule but can you share it with me
Sure! I've used nonsense notch to create an overlay at 240 pixel from the left of the statusbar, it doesn't work on landscape mode but it's fine for me.
Idk if it works by just inserting it in /system/product/overlay and unzipping it and then maybe installing the apk(?) (Mine it's in a folder that's why i made a zip file)
Overlays are really tricky, i recommend following the guide for the module instead of doing this.
After installation you can go to dev options and under simulate screen cutout you can choose the one you created *DO NOT CHOOSE THE STOCK OPTIONS ON ANDROID 12 THEY WILL SOFTLOCK YOUR PHONE*
I will create a guide on the fixes for gsi roms with your audio tweaks and this one, thank you again, let me know if you succeed!
Again, you shoudl really create one yourself on the custom mode of this module https://forum.xda-developers.com/t/module-n3o-no-nonsense-notch-overlay.4226413/
I created a guide to install everything https://forum.xda-developers.com/t/...s-nairo-and-some-post-install-tweaks.4364963/
Tommy0000 said:
Sure! I've used nonsense notch to create an overlay at 240 pixel from the left of the statusbar, it doesn't work on landscape mode but it's fine for me.
Idk if it works by just inserting it in /system/product/overlay and unzipping it and then maybe installing the apk(?) (Mine it's in a folder that's why i made a zip file)
Overlays are really tricky, i recommend following the guide for the module instead of doing this.
After installation you can go to dev options and under simulate screen cutout you can choose the one you created *DO NOT CHOOSE THE STOCK OPTIONS ON ANDROID 12 THEY WILL SOFTLOCK YOUR PHONE*
I will create a guide on the fixes for gsi roms with your audio tweaks and this one, thank you again, let me know if you succeed!
Again, you shoudl really create one yourself on the custom mode of this module https://forum.xda-developers.com/t/module-n3o-no-nonsense-notch-overlay.4226413/
Click to expand...
Click to collapse
thank you very much it works and it even does my games without a black bar
wesleyvanneck12345678 said:
thank you very much it works and it even does my games without a black bar
Click to expand...
Click to collapse
Ye it's very fortunate it stops working when landscape! I quite like that non-feature
Hello guys. Goodnight. I'm from Brazil. I installed Cherish 13 OS on my cell phone, Lineage, Pixel Experience and AOSP, but none of them work. Can anyone help out there?
follow this
phh treble settings -> misc -> use an alternate way to detect headsets
turn that on and then reboot. should work after that.