Develop Bugs

LDAC 8.1

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?

[GUIDE] Having a decent Android P GSI experience while Markus works.

So, this is how I PERSONALLY got a pretty decent experience on phhussons P GSI.
I am not responsible if something doesn't work or doesn't work the way you want.
Update: The PixelExperience build over on the Treble section works pretty well and eliminates the need for Overlays_Pr1.zip as well as Bitgapps. It's also including gapps (with SetupWizard as well as the pixel launcher). Same bugs as listed below.
Step 1: Trebleizing your phone
Download the latest trebleized Lineage OS ROM by SGCMarkus here and install it.
Make sure to read his guide to repartition your device carefully, otherwise this won't work.
Step 2: Prerequesites to have a nice time with Android P.
Before we wegin with the GSI stuff, you will have to copy the build.prop [or if you have the device fingerprint for your phone, just copy that] to a safe location.
Step 3: Installing the GSI
Download phhusson's latest Pie GSI from here
Unzip it and load it onto your phone's storage.
Proceed with wiping your /system, /data, /cache and Dalvik. Do not wipe /vendor (duh.)
Then install the image by tapping "Install image" button in the selection screen.
Step 4: Installing GAPPS
Download BitGapps from here. (I do **not** recommend using unofficial OpenGapps, as I run into several issues with them.)
[This version of GApps does not include any SetupWizard, which means you will have to download all your apps manually!]
Step 5: Fixing Device not Certified
While the notification doesn't pop up, it is indeed not certified and is (one of) the reason(s) why the phone gets so hot sometimes.
So what you need to do is download Magisk 16.7 (or later) as well as MagiskPropsHideConfig from here
as well as get any terminal app from the Play Store you like. [I personally like Material Terminal, as you can copy/paste in it]
After doing that, open a terminal window and type "props" (without quotation marks). Then select 1 and enter your device fingerprint (either from the build.prop we saved earlier or the fingerprint you saved somewhere)
Step 6: Makin' it nice.
So most of this besides maybe the Vibrator are purely optional, so you can go and enjoy some Pie if you wish.
Vibration:
- reboot to TWRP
- mount /vendor
- Install SGC's sGSI fix from here
- Install temp_vib_fix_joan_v2.zip from the attached files. Doesn't fix the dullness that occurs after some time.
DT2W:
- reboot to TWRP
- mount /system
- Install dt2w_on_gsi_joan.zip
Proper rounded corners and that new navbar[not required on PE P GSI]:
- Reboot to TWRP
- mount /vendor
- Install Overlays_PR1.zip from the attached files. (not mine, it's from erfanoabdi's Telegram group, will add proper credits if i manage to find the creator)
- Navigate to Settings -> System -> Gestures -> Swipe up to home
Additional System Accents (Yay! Colors!)
- Reboot to TWRP
- Install System_Accents_P.zip from the attached files. (not mine, it's from erfanoabdi's Telegram group, will add proper credits if i manage to find the creator)
Always-on Display (DT2W still works!)[Not required on PE P GSI]
According to phhusson, this does more than just enable AOD apparently, and it does something with the vibration, so installing this is on **your own risk** (not like it wasn't anyways)
-Reboot to TWRP
- Install P_AOD_FIX_-_by_ElHechicero.zip (not mine, credit goes to ElHechicero)
Getting Wellbeing [Not requried on PE GSI]:
-Download the Wellbeing.apk from ApkMirror
-Rename it to WellBeing.apk
-Move it into /system/priv-app/WellBeing/ (create the folder WellBeing)
-Reboot
Getting a nicer launcher with the appdrawer[PE P GSI uses the Pixel Launcher]:
-Download Nokias (HMDs) Launcher from ApkMirror
-Rename it to Quickstep.apk
-Replace /system/priv-app/Quickstep/Quickstep.apk with the Nokia launcher (which you renamed to Quickstep)
-Reboot
Issues:
- A lag when tapping on the "Default Apps" or the Bluetooth/NFC area in Settings
- Can get warmer when in playstore
- Vibration: Gets dull and sounds like static after a while. Hopefully SGCMarkus will be able to fix this or we'll be stuck with the dullness on P gsi's for now.
Not working:
-Hotspot
-NFC (?) [Seemed to work just fine on my device]
- Let me (or others, rather.) know.
Credits go to:
SGCMarkus
the LG V30 telegram group for the pointers
erfanoabdi's telegram group
ElHechicero
phhusson​

FAQs:
Is Launcher <Insert Launcher Name here> compatible?
- Any launcher is but don't expect the new Recents-Appdrawer to work.
Does the DAC work?
- Only in certain apps, as for all AOSP roms.
Screenies in attachments

You did a good job! I'm happy to have android pie on v30 but does its dac still not work?

thanks for the tutorial,
depending on your experience, do you think it suitable as a daily driver (I don't mind with the quad DAC) ?

Panokiaran said:
You did a good job! I'm happy to have android pie on v30 but does its dac still not work?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77389334&postcount=15
Onkyo HF Player
USB Audio Player PRO
both are able to utilize the quad dac,
with the 2nd you can even use it with streaming

dr.guru said:
thanks for the tutorial,
depending on your experience, do you think it suitable as a daily driver (I don't mind with the quad DAC) ?
Click to expand...
Click to collapse
If you don't depend on Hotspot (and maybe NFC) and don't mind the occasional dullness, then yes. It is very daily driver capable. I'm using it.

Saxithon said:
If you don't depend on Hotspot (and maybe NFC) and don't mind the occasional dullness, then yes. It is very daily driver capable. I'm using it.
Click to expand...
Click to collapse
Any comments on battery life ?

Saxithon said:
Update: The PixelExperience build over on the Treble section works pretty well and eliminates the need for Overlays_Pr1.zip as well as Bitgapps. It's also including gapps (with SetupWizard as well as the pixel launcher). Same bugs as listed below.
Click to expand...
Click to collapse
is this the proper image: click ?
So this will eliminatre the need to install bitggaps, but I still need to go through points 5 and 6, right?

Is Nova compatible with this setup?

zacharias.maladroit said:
https://forum.xda-developers.com/showpost.php?p=77389334&postcount=15
Onkyo HF Player
USB Audio Player PRO
both are able to utilize the quad dac,
with the 2nd you can even use it with streaming
Click to expand...
Click to collapse
Thanks your

rdeets said:
Is Nova compatible with this setup?
Click to expand...
Click to collapse
Any launcher is. Just the new Recents Appdrawer will only work with certain devices. As of now those are working: AOSP Quickstep, Nokia Quickstep(Also called Android One launcher), The Pixel launcher (but doesn't work by installing?? [works on the PE P GSI tho]) and sometime in the future Lawnchair V2.
pizmak said:
is this the proper image: click ?
So this will eliminatre the need to install bitggaps, but I still need to go through points 5 and 6, right?
Click to expand...
Click to collapse
Yup and yup.

zacharias.maladroit said:
https://forum.xda-developers.com/showpost.php?p=77389334&postcount=15
Onkyo HF Player
USB Audio Player PRO
both are able to utilize the quad dac,
with the 2nd you can even use it with streaming
Click to expand...
Click to collapse
if the dac not work with jetaudio and spotify than why treble !!! ?
Sent from my LGM-V300S using XDA Labs

seloka180 said:
if the dac not work with jetaudio and spotify than why treble !!!
Sent from my LGM-V300S using XDA Labs
Click to expand...
Click to collapse
Has nothing to do with treble... its aosp in general.

me2151 said:
Has nothing to do with treble... its aosp in general.
Click to expand...
Click to collapse
thank you
Sent from my LGM-V300S using XDA Labs

why can't you just backup your rom and make a zip file?

everything working good and smooth, but i only can not instal MagiskPropsHideConfig from magisk or TWRP,
and camera always force close, but then open camera doing well in PE room.
ahhh so great to taste the sweetest pie
thanks to you and others dev
much love

Arif Ferdian said:
everything working good and smooth, but i only can not instal MagiskPropsHideConfig from magisk or TWRP,
and camera always force close, but then open camera doing well in PE room.
ahhh so great to taste the sweetest pie
thanks to you and others dev
much love
Click to expand...
Click to collapse
Have the same issue. Fixed by going to TWRP, wipe cache & Dalvik and then reflash the Magisk 16.7 zip, then boot to OS and install MagiskPropsHideConfig.

@Saxithon your thread name suggests that @SGCMarkus is working on sth.
Will he make a flashable zip of the Pie ROM that we can flash without treblezing?

FcBayernMinga said:
@Saxithon your thread name suggests that @SGCMarkus is working on sth.
Will he make a flashable zip of the Pie ROM that we can flash without treblezing?
Click to expand...
Click to collapse
Im working on Pie, kinda, but atm im stuck somewhere...
Have to figure out wtf is going on there

Followed the treble parttioning guide, flashed EnesSastim pixel expirience rom, and im happy to report its working fine so far. Left my Ext sdcard in exfat fromat working well so far too. Did not need to recertify my device. And no error after the setup wizard. I will change the apn settign to see if i can get lte, so far i am 4g.
Edit: cant seem to be able to use camera, even with open camera app.

LineageOS 19.1 [S] [12.1] (Unofficial) Mi Pad 4 Plus (clover+)

Latest rom : lineage-19.1-20220928-UNOFFICIAL-clover.zip, see this link :
Changelog :
- Sept Security Patch
- Update cam HAL to LA.UM.10.2.1.r1-03300-sdm660.0.
- Switch to 4.19 Nyx kernel
Installation instructions :
- Perform a backup of your current ROM (optional)
- Use latest 4.19 twrp created by pix106: https://androidfilehost.com/?fid=15664248565197205779)
- Reboot into recovery/twrp, format data, then reboot into recovery/twrp again.
- Flash ROM.
- Flash GApps is optional.
What's not working:
Let me know.
Known issues :
- Disabled Encryption
Please post the bug along with log (use syslog).
Source :
Kernel : clover
Device tree : sdm660

Update : latest version lineage-19.0-20211105-UNOFFICIAL-clover-new.zip pass safetynet.

Tried already in a mi pad 4 (8") and everything working so far.
Great work!

Does it support Monet theming?

Everything works OK, except I cannot change battery indicator (to circle, it just stays battery-shaped) and also can't show battery's %
Just nothing happens when i try to change these

redcord said:
Everything works OK, except I cannot change battery indicator (to circle, it just stays battery-shaped) and also can't show battery's %
Just nothing happens when i try to change these
Click to expand...
Click to collapse
Yes...some features are still not working as it depends on lineage source.

Installed Ok and runs - but with a few issues. Playstore not certified. Android system intelligence crashes regularly. It insisted on formatting my SD card so I let it but now I will have to put back all my music and books. Never mind. I will keep using it and updating for now.
Plus: I just tried my Bluetooth earbuds. They paired fine and are working with aptX
Plus: USB PD charger gives Charging rapidly

Everything works OK, except stop working Android System intelligence
Mi pad 4 (8") Wifi

GregEden said:
Installed Ok and runs - but with a few issues. Playstore not certified. Android system intelligence crashes regularly. It insisted on formatting my SD card so I let it but now I will have to put back all my music and books. Never mind. I will keep using it and updating for now.
Plus: I just tried my Bluetooth earbuds. They paired fine and are working with aptX
Plus: USB PD charger gives Charging rapidly
Click to expand...
Click to collapse
Playstore is certfied using patched boot.img by magisk and magisk hide. I didn't test using android system inteligence...will check later.

It's beautiful and quite stable, but with some minor issues.
1. Android System Intelligence keeps stop working. There's already a workaround by installing "ExtraPixel" module from this channel https://t.me/randomfilezz, but I suggest to make a fix inside the ROM.
2. Yep, Monet theming engine, ported by @kdrag0n , is open-sourced, so maybe consider adding it and makes it a better ROM. https://www.xda-developers.com/android-12-material-you-theming-system-recreated/
3. Always on display feature missing. Maybe you forgot to add it.

And the clock position and size on lock screen without notification is not accurate, compared to other devices.

Ralph Chen said:
And the clock position and size on lock screen without notification is not accurate, compared to other devices.
Click to expand...
Click to collapse
Did you compared to other device that running with lineageos 19.0?

Ralph Chen said:
It's beautiful and quite stable, but with some minor issues.
1. Android System Intelligence keeps stop working. There's already a workaround by installing "ExtraPixel" module from this channel https://t.me/randomfilezz, but I suggest to make a fix inside the ROM.
2. Yep, Monet theming engine, ported by @kdrag0n , is open-sourced, so maybe consider adding it and makes it a better ROM. https://www.xda-developers.com/android-12-material-you-theming-system-recreated/
3. Always on display feature missing. Maybe you forgot to add it.
Click to expand...
Click to collapse
Those features will be on this device once it is available in lineage source.

sabar_op said:
Did you compared to other device that running with lineageos 19.0?
Click to expand...
Click to collapse
I compared with other ROMs such as pixel experience.
Maybe it has to be in the center of the screen.

Ralph Chen said:
I compared with other ROMs such as pixel experience.
Maybe it has to be in the center of the screen.
Click to expand...
Click to collapse
Not sure about that, perhaps it is new style of lineageos 19..or lineage source not implemented yet to center the clock in the lockscreen...

My microphones are not working, via wired or bluetooth connections.
And the internal mic is dead too.

GregEden said:
My microphones are not working, via wired or bluetooth connections.
And the internal mic is dead too.
Click to expand...
Click to collapse
Are you sure? I am test it using mictest...and it works properly.

sabar_op said:
Are you sure? I am test it using mictest...and it works properly.
Click to expand...
Click to collapse
OK it works now. I did a reboot, and that did not help. I went into the recorder settings and toggled autodetect off then back on. And now it is working. I will test again tomorrow with my Duolingo lesson.

Dear all, may I ask for help please? I just manager to load 19.0 by following the above steps. However when it comes to the initial set up page, where it says checking for updates, it goes blank. How do I resolve this?

Btayyyy said:
Dear all, may I ask for help please? I just manager to load 19.0 by following the above steps. However when it comes to the initial set up page, where it says checking for updates, it goes blank. How do I resolve this?
Click to expand...
Click to collapse
I had that issue but I do not remember how I resolved it. I think I just kept swiping up until I could select next and it move on.

Question Viper 4 Android and Pixel 6 Pro

Has anyone gotten Viper 4 Android to work with the pixel 6 pro yet? If not, are there alternatives? Any guides to doing this would be appreciated! I searched but didn't find much.

Android 12 (Viper4Android)
Has anyone managed to get Viper4Android working on the latest beta of Android 12? The usual methods don't work (makes sense, since its a new OS). Just curious. I like Android 12 so far, but might roll back to 11 if I can't get Viper going...
forum.xda-developers.com

Followed the guide in that thread and got it installed and seems to be working, any recommendations on the profiles for the speakers or the pixel buds a?

FabricatorGeneral said:
Seguí la guía en ese hilo y lo instalé y parece estar funcionando, ¿alguna recomendación sobre los perfiles para los altavoces o los botones de píxeles?
Click to expand...
Click to collapse
norteDon't put much Bass on the speakers because they over time deteriorateBass on the speakers because they over time deteriorate

For those that don't want to change their kernel to permissive due to security reasons, I used this method and is working fine for me. Legacy mode needs to be toggled on.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com

Lughnasadh said:
For those that don't want to change their kernel to permissive due to security reasons, I used this method and is working fine for me. Legacy mode needs to be toggled on.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com
Click to expand...
Click to collapse
i didnt have to change to permissive. the 2nd. file is a Android 12 fix, i believe if you use the fix you do not have to change to permissive....

AndroidAddict420 said:
i didnt have to change to permissive. the 2nd. file is a Android 12 fix, i believe if you use the fix you do not have to change to permissive....
Click to expand...
Click to collapse
I was referring to the method linked in Post #2 where they said they changed their kernel to permissive. The Android 12 fix file is from another thread which you started and posted the file it. You might want to add a link to your post so people know what "fix" file you are talking about since it's not in this thread, lest people might get confused about what you are talking about.
Or maybe I'll just link it here...
Interested in a Working Formula to get Viper4Android Working? (ROOT)
Viper4Android for Google Pixel 6/6 Pro and most other devices on Android 12... It the time of testing this Method, it worked in November 2021 and December 2021 builds for my Google Pixel 6.... 1) Make sure your BL is unlocked and you are...
forum.xda-developers.com

I installed by using the method I had to do for OP8T. Install Audio_Modification_Library Magisk Module (DO NOT REBOOT) -> Install Viper Magisk Module (DO NOT REBOOT) -> Open Viper App (this forces a reboot) -> Remove Audio_Modification_Library. It works great for me in apps like AIMP, but in apps like YouTubeVanced have never worked for me.

card13 said:
I installed by using the method I had to do for OP8T. Install Audio_Modification_Library Magisk Module (DO NOT REBOOT) -> Install Viper Magisk Module (DO NOT REBOOT) -> Open Viper App (this forces a reboot) -> Remove Audio_Modification_Library. It works great for me in apps like AIMP, but in apps like YouTubeVanced have never worked for me.
Click to expand...
Click to collapse
Strange it doesn't process with YouTubeVanced for you. It should. Have you tried giving this mod a shot?
EDIT: Actually I think the version located at John Fawkes site is newer than the XDA one, so adding that link.
Audio Compatibility Patch (Formerly Universal deep_buffer Remover) [MMTEx]
This fixes music and streaming apps (Spotify, Pandora, etc) that aren't processing audio effects for various equalizer applications through the modification of audio policy. Starting with v1.6 USB_policy patcher (upp) and Notification_helper...
forum.xda-developers.com
John Fawkes Playground

@Lughnasadh I'm not currently using the Compatibility Patch. It's mainly because last time I did on the OnePlus phones, my Bluetooth audio would get fubar'd and require a Factory Reset to fix.

Thanks to the community, the Viper4android works for me on Pixe6 PRO, BUT I am unable to activate any VIPER-DDC , Headset correction profiles loading takes no effect, tried a few I see them active but no change in sound. Previously my OnePlus 8Pro worked fine with the same version (Android 12). Does anyone experience similar issue ? Can you please try and let me know.

ansher said:
Thanks to the community, the Viper4android works for me on Pixe6 PRO, BUT I am unable to activate any VIPER-DDC , Headset correction profiles loading takes no effect, tried a few I see them active but no change in sound. Previously my OnePlus 8Pro worked fine with the same version (Android 12). Does anyone experience similar issue ? Can you please try and let me know.
Click to expand...
Click to collapse
I don't have answer for your question, perhaps go to their Telegram group to ask for help as you may have more chance there.
I do have something for your consideration. I used V4A for longer than I can remember but it must be over 10 years. However, seems the developer has already quitted the project for quite sometime, the driver has never been updated in the past 7-8 years, we are lucky that it is still working with A12. But everything has an end, I tried it on A13 Beta and it doesn't work with it. If you search the web, you properly going to find that so far no one is able to make it work with A13. The A13 is already in beta 4 and official release could be sometime in next month, unless you are going to give up to update to A13, you better start to find something to replace V4A, my choice is JamesDSP but you may find something better suit your needs.

I prefer presets because I don't know what I'm doing. I ended up moving to PowerAmp and am usually pleased with the sound. If only the developer would enable roor features, man that would be cool.

Thanks acwcanada for the suggestion. I looked at the thread and so far may stick with Android 12 (those crazy audiophiles ) because I could not find 2 key features available in Viper4Android.
1. Headphone frequency response correction (VIPER-DDC or AutoEQ in Wavelet). This feature does not even work for me in Pixel 6 pro A12L , workaround: install wavelet and use its AutoEQ feature.
2. Dynamic System feature of Viper4Android creates bass subharmonics using reference frequencies and algorithm (selectable by choosing headphone type), so it can inject them in the music making it feel much richer and restores lack of low frequencies without "booming" effect created by other bass boosters. So far nothing in this word can beat this Viper4Andoid's feature.
Some good news folks: Viper4Android and Wavelet can be stacked and work in tandem .
Perhaps going to write James to consider the above, unless I missed it.
Cheers and thanks Team !

How To Guide A Complete Guide to Unlocking and Flashing for the A52s 5G.

Disclaimer​
Your warranty will be void
Some carriers' Terms of Service prohibit device modifications
Modifying will trip Samsung Knox and SafetyNet, so be aware that some apps will cease to work
I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FAILED ATTEMPTS AND OTHER CAUSES OF IMPROPER USAGE OF THIS GUIDE!​Now that we got that out of the way, we can continue.
Unlocking the Bootloader​UNLOCKING THE BOOTLOADER WILL ERASE ALL OF YOUR DATA!​
Go into Settings > About Phone > Software Information
Find Build Number and quickly tap it 7 times. This will enable Developer Options
Find OEM Unlocking and USB Debugging options and enable them
Turn off the phone
Hold Volume Up and Volume Down while connecting your phone to a PC to boot into Download Mode
Read the Warning carefully to understand it and then if you want to continue press Volume Up
On the Unlock Bootloader screen, press and hold the Volume Up button one more time (This is the step that erases all of your data, if you don't want to do it, now is the time to turn back!)
After the automatic reboot, repeat steps 1. - 3. and make sure that OEM Unlocking is greyed out and enabled
Congratulations! You bootloader is now unlocked.
Flashing a Custom Recovery​Credit to @BlackMesa123 for this guide.
Rooting your Phone​
Download the latest version of Magisk on your Computer
Follow the Official Installation Guide from Magisk developers
Flashing a GSI (Generic System Image)​
Choose a GSI from this List
Power Off your phone and connect it to your Computer
Hold Volume Up and Power buttons, after the logo appears, release only the Power button, this will boot you into TWRP
Do a Wipe and transfer the GSI file from you Computer to your Phone
Click Install >Image Flashing, find your transferred GSI file and tap on it.
Toggle the System Image option and flash the file.
After flashing Format Data to be able to boot into your new System.
I know your Camera doesn't work, don't worry check out this Post to get it to work again.
Useful Resources​
A52s bootloader/modem collection repository
OrangeFox Recovery
SafetyNet Fix for Magisk (Zygisk)
Custom ROMs: RayOS (One UI 4.1), NcX (One UI 5.0)
Mesa's Custom Kernel
Credit to @BlackMesa123 @Ryzen5950XT @ShaDisNX255 for the additional resources.
That's it! Thank you for following the guide and enjoy your unlocked Samsung.

This is very helpful thanks

Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.

BlackMesa123 said:
Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.
Click to expand...
Click to collapse
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?

kzyx said:
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?
Click to expand...
Click to collapse
You shouldn’t wipe anything when flashing the kernel. If the stock kernel works fine, I don’t see why mine shouldn’t

Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.

Mian-786 said:
Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.
Click to expand...
Click to collapse
I don't know what could be the issue, maybe try to google or try disabling and enabling the fingerprint lock again.

I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.

Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.

kzyx said:
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.
Click to expand...
Click to collapse
Nope, I tried to find a good custom rom for A52s but couldn't find any.

What about volte and hotspot on GSI pixel experience 13?

Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for your summary,
Is there any experience with MicroG on this device with AOSP 13?

7slaper said:
Thanks for your summary,
I'm on AOSP 13 now, but perhabs it's better to go back to 12. I'm very interested in the AOSP with the GAPPs pre-installed. Could you share a link to the file?
Click to expand...
Click to collapse
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.

Zhazhael said:
What about volte and hotspot on GSI pixel experience 13?
Click to expand...
Click to collapse
I think VoLTE was available as an option in one of the ROM I tested but I don't remember exactly. Currently AOSP 12 doesn't support it. Hotspot worked on every ROM just fine.

Mian-786 said:
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.
Click to expand...
Click to collapse
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.

7slaper said:
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.
Click to expand...
Click to collapse
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.

Thx, all worked.

Mian-786 said:
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.
Click to expand...
Click to collapse
I've installed MicroG. But it seems AOSP doen't allaw support system spoofs signature. Play services (GmsCore) is installed but without the spoofed signature it can't do much I guess...

I have been using AOSP Android 12 for the past week or so. Most of the things just plain works but somethings don't. Here is the list of things that are not working so you can decide if the hassle of installing GSI is worth it or not.
- Proximity Sensor is worse than it was in OneUI. Yes, it is a virtual sensor but on OneUI, it worked better. Now, it is worse. More often than not, it turns on the screen during the call. It would have been better if it simply didn't work.
- The viewport of default camera App in the AOSP displays picture in 4:3 but the camera hardware is giving out 16:9, so the viewport was squeezed. After installing GCam everything is good.
- Fingerprint Sensor simply doesn't work in-app like those in banking apps. It works on the lock screen but nowhere else.
- USB Audio Devices don't work. I have a USB-C to A OTG where I used to insert my headphones. On OneUI they used to work but here they don't. Storage devices work.
- 120 Hz felt smoother on OneUI.

Hello everyone
I managed to install LineageOS with working GApps and camera using this guide, so a big thanks to everyone who worked on flashing this phone
If anyone wants to install it, you need to:
Chose a bgN package (I installed this one : https://sourceforge.net/projects/an...UNOFFICIAL-arm64_bgN-vndklite.img.xz/download). It includes the GApps. You won't be able to install GApps after installing a vanilla (bvS / bvN) package. For some reasons, the /system partition is too small.
For unlocking camera and install magisk, just flash this kernel : https://forum.xda-developers.com/t/kernel-12-13-a528b-n-mesas-custom-kernel-r4.4490653/
I also installed magiskhide prop conf module, but I'm not sure it changed anything and the camera fix was probably already in the MCK. You can find it here anyway : https://forum.xda-developers.com/t/...safetynet-prop-edits-and-more-v6-1-2.3789228/