Database Info

CyanogenOS 13 and V4A

Hello peeps! A longtime lurker, first time poster here.
Straight to the point. I upgraded my rooted OPO with the COS 13 ZNH0EAS2JK by Manudroid19. My kernel is the boeffla one for COS13. The user experience is smooth as all hell but i encountered a huge problem. I can't get Viper4Android to work at all, hell, even the built-in AudioFX didnt do anything. The apk works fine and it installs the driver without any problems. I've tried the phone speakers and a headset but any of the options in V4A don't do anything.
Has anyone got V4A to work on COS 13? Or even AudioFX? I've tried flashing V4A and tried the Play store version without any luck. What am i missing? Didn't have any problems with V4A on 12.1. Any ideas?
Thanks in advance!

Can't call

I recently installed Lineage OS 14.1 from https://forum.xda-developers.com/20...o-root-moto-g-2015-android-t3320113?nocache=1 on my Osprey, along with GApps. Everything works great, but I just realised a serious issue - Calling.
I can't hear anything, and neither can the other person. I've tested both the speaker and the microphone, and tried a different app, but nothing works. Help?

mercuryprobe said:
I recently installed Lineage OS 14.1 from https://forum.xda-developers.com/20...o-root-moto-g-2015-android-t3320113?nocache=1 on my Osprey, along with GApps. Everything works great, but I just realised a serious issue - Calling.
I can't hear anything, and neither can the other person. I've tested both the speaker and the microphone, and tried a different app, but nothing works. Help?
Click to expand...
Click to collapse
Clean flash your ROM again. Make sure you haven't installed any sound modding apps like Dolby or V4A. If it still persists, try other ROMs. If you're having this problem on all ROMs, then pretty surely the hardware is the source of trouble.

adityak1303 said:
Clean flash your ROM again. Make sure you haven't installed any sound modding apps like Dolby or V4A. If it still persists, try other ROMs. If you're having this problem on all ROMs, then pretty surely the hardware is the source of trouble.
Click to expand...
Click to collapse
I did, in fact, install V4A before I tried calling. Maybe that was the problem. Anyway, I'm re-flashing right now (also installed a kernel lmao), and I'll update ASAP

Update: Well, that didn't work, though I can verify that it worked with the stock firmware *sigh*. Anyway, for now I'm downloading the latest 'stable' build of Resurrection Remix.
Double Update: RR sucks, installed the Offical LOS nightly, everything is great now. Thanks for the help guys!

Bluetooth Phone Profile in Nougat roms

Hey guys,
I have an annoying problem that prevents me to switch from TS CM13 to any newer roms.
I've tried RR, HnT LOS14, Cozzmy's LOS14 and last night even the newest TS LOS14.1
Every nougat rom doesn't work with the bluetooth phone profile on my Citroen DS4.
(The car's multimedia system is already at the last version)
Even stranger, bluetooth pairing works without any issue and media streaming profile works too. Only the phone profile says "there was a problem, try to reconnect".
Does any of you uses in-car BT with nougat roms? And maybe has a PSA group car?
Is there anything i can do? Even rebuilding kernel with legacy bt it's ok, if you give me some hints i can do it
Because on marshmallow roms everything works smoothly.
Thanks!

Try latest stable rom from miglobe and use DX mod (you ll find it here on xda). Its miui reinvinted
(everything work great cause its the official rom from xiaomi but its debloated and there is no thermal issues.Battery is real good too)
-dont know if it works with your car but if the official rom doesnt i think noone else will-

Thanks @nioonline. The problem is i will have to do the whole bootloader upgrade & downgrade again... but you're right, i guess the official rom it's the only way to be sure.

Bluetooth Absolute volume on miui 11 and Sony WF-1000xm3 doesn't work

Hi all,
When I got the Mix 3 I was running EU MIUI as my daily driver, that was MIUI 10 back then. Bluetooth absolute volume was working fine back then.
I own a pair of Sony WF-1000xm3 and since EU MIUI 11 or the last Sony update of these headphones I can't get bluetooth absolute volume to work on the mix 3 with MIUI. I have been using AOSP based roms for half a year now but the unstability (alarms not functioning because of a soft reboot during the night for example) made me go back to MIUI.
Using any AOSP rom the absolute volume works fine and it was working fine half a year ago on MIUI 10 with the Developer option absolute volume.
I have flashed MIUI 10 from half a year ago but I just can't get absolute volume to function. Since my bluetooth speakers that also support absolute volume don't function like they should aswell on MIUI I'm suspecting something else is wrong in my configuration. Even reflashing using Mi Flash Tool to global rom doesn't solve my issue and different firmwares also didn't solve my problem.
Who can help me?

Don't know about the volume problem, but the reboot overnight is caused by a wireless charging bug in AOSP, although on mine it's a hard reboot all the way back to the bootloader, not just a soft reboot of the rom.

Well, it seems I have magically resolved it.
In what I believe I haven't done anything different this time than previous tries I have done, but these are the steps I have taken (from memory)
Reflashed fastboot global rom using Mi Flash tool and relocked the bootloader.
Booted the rom, unlock bootloader check in developer options
Unlock the bootloader using Mi Unlock Tool
Flash TWRP and flash MIUI 11 EU weekly rom, boot
Format data and wipe all storage options except internal storage in TWRP
Flash pixelexperience rom, boot
Format data and wipe all storage options in TWRP
Flash MIUI 11 EU weekly rom, go to developer options and disable the 'disable absolute volume' check.
Pair bluetooth headphones.
And suddenly it works! It might be that some steps seem unnecesary but I have tried so many times using different patterns that I will keep using above pattern.
Hope this helps someone someday if he/she faces the same issues as I did.
Finally enjoying my mp3 player with phone capabilities again

sjsimon1996 said:
Well, it seems I have magically resolved it.
In what I believe I haven't done anything different this time than previous tries I have done, but these are the steps I have taken (from memory)
Reflashed fastboot global rom using Mi Flash tool and relocked the bootloader.
Booted the rom, unlock bootloader check in developer options
Unlock the bootloader using Mi Unlock Tool
Flash TWRP and flash MIUI 11 EU weekly rom, boot
Format data and wipe all storage options except internal storage in TWRP
Flash pixelexperience rom, boot
Format data and wipe all storage options in TWRP
Flash MIUI 11 EU weekly rom, go to developer options and disable the 'disable absolute volume' check.
Pair bluetooth headphones.
And suddenly it works! It might be that some steps seem unnecesary but I have tried so many times using different patterns that I will keep using above pattern.
Hope this helps someone someday if he/she faces the same issues as I did.
Finally enjoying my mp3 player with phone capabilities again
Click to expand...
Click to collapse
I was looking to get the Sony WF-1000XM3s, is LDAC working properly on Xiaomi.eu in MIUI 11? I'm on MIUI global stable 10.3.2.0 right now and I can't select any codecs aside from SBC (AAC is the only one my headphones support but still) and I'm kind of sick of it. I was thinking of jumping ship to Xiaomi.eu anyway but I'm a little apprehensive about how well it works in the US

Rockmadeofrock said:
I was looking to get the Sony WF-1000XM3s, is LDAC working properly on Xiaomi.eu in MIUI 11?
Click to expand...
Click to collapse
I have enabled LDAC in developer options but it doesn't seem to make a difference in comparison with AAC or SBC.

sjsimon1996 said:
I have enabled LDAC in developer options but it doesn't seem to make a difference in comparison with AAC or SBC.
Click to expand...
Click to collapse
If you look at the device in your Bluetooth settings does it say LDAC next to it, showing it's actually being used? Because I know that has historically been an issue as well, where you select a codec in Dev Options but it doesn't actually change and then reverts back to SBC as soon as you close the settings.
Even if AAC works it would still be a marginal upgrade over SBC which is what I'm stuck with now.

Rockmadeofrock said:
If you look at the device in your Bluetooth settings does it say LDAC next to it, showing it's actually being used? Because I know that has historically been an issue as well, where you select a codec in Dev Options but it doesn't actually change and then reverts back to SBC as soon as you close the settings.
Even if AAC works it would still be a marginal upgrade over SBC which is what I'm stuck with now.
Click to expand...
Click to collapse
No, it still says AAC, so that doesn't seem to be working.

sjsimon1996 said:
No, it still says AAC, so that doesn't seem to be working.
Click to expand...
Click to collapse
Just realized only the over-ear WH-1000xm3's support LDAC so your bluetooth is working as it should.

a14 Beta 3 GSI Available

Android 14 dp1/dp2 are both now available and can be installed. I currently have a14 dp2 installed on my tmob v60. Just to be clear, this is not for everyone as it is very buggy. I'm current having problems with no audion for both phone calls and BT. This was a very well known problem with a13 betas and it the same again with a14.
If anyone knows of a work around (?????), then this would seem to be ready for a daily driver.
BTW, the download if available here.

hooutoo said:
Android 14 dp1/dp2 are both now available and can be installed. I currently have a14 dp2 installed on my tmob v60. Just to be clear, this is not for everyone as it is very buggy. I'm current having problems with no audion for both phone calls and BT. This was a very well known problem with a13 betas and it the same again with a14.
If anyone knows of a work around (?????), then this would seem to be ready for a daily driver.
BTW, the download if available here.
Click to expand...
Click to collapse
I will try later on to work on Audio fixes, It should be easy to fix actually

Kratos574 said:
I will try later on to work on Audio fixes, It should be easy to fix actually
Click to expand...
Click to collapse
Were you the one who worked on getting Treble ROMs to function fully in the previous versions? If so, how well did they work?

Kratos574 said:
I will try later on to work on Audio fixes, It should be easy to fix actually
Click to expand...
Click to collapse
The audio fix is a REALLY big deal. If this were to be fixed I would stay on a14 and never look back. Many now will be focused on the new Tmob a13 40a release for the next coming months but that's the end of the line for the LG V60. It seems Treble based roms are making great strides now and really picking up speed in term of development. For bootloader unlocked phones, such as this one, Treble rom are showing how fast older phones can be without all the bloatware crap loaded on by LG, Tmob, ATT, Verizon and (yes) google.

This is a post in response to my question on the v60 telegram channel about audio problem on this rom. The poster was Zakhmi.
"There are things in phh GSI that needs to be done after first boot
1-Enable Double tap to wake
Go to settings >phh trebble tree > xiaomi features > Enable D2W
2-Bluetooth audio fix
Go to Settings> phh trebble tree> misc features > Force Disable A2DP Offload and then restart phone..done
3-Fix call audio
Settings > phh treble settings > Qualcomn feature > tick mark use alternat audio policy and disable soundvolume effect
4- 90Hz enable
Go to Settings> phh trebble tree> misc features > Force FPS > 90
5- VoLte enable
Go to Settings> phh trebble tree> IMS features > Enable IMS network and force enable 4G calling....install 2nd option of IMS apk for qualcomn vendor...wait for download..then install it"
Item 2 and 3 may help fixing this problem for the V60.

AnnexedOne said:
Were you the one who worked on getting Treble ROMs to function fully in the previous versions? If so, how well did they work?
Click to expand...
Click to collapse
Well, I stopped working due I got a new phone but got back to V60 and started to work again, I am currently working on getting Quad Dac working once again on Treble roms, Fingerprint I already discarded the Idea due I tried most of known fixes but was unable to make it to work and also Dual screen is out of the question

Kratos574 said:
Well, I stopped working due I got a new phone but got back to V60 and started to work again, I am currently working on getting Quad Dac working once again on Treble roms, Fingerprint I already discarded the Idea due I tried most of known fixes but was unable to make it to work and also Dual screen is out of the question
Click to expand...
Click to collapse
Thanks for the effort? Are those the only issues that don't work for GSI roms? Are all GSI roms the same when it comes to what doesn't work?
I wonder if experiences with other treble phones may help with the V60's breakage.

Kratos574 said:
I will try later on to work on Audio fixes, It should be easy to fix actually
Click to expand...
Click to collapse
I now have A14 beta1 up and running. The a14 dp1/dp2 releases did not have any sound what so ever. The new a14 beta 1 has audio on calls and also music on speakers but no BT sound. Wondering whether you've made any progress on a BT audio fix. I've been looking closely at audio.policy.configuration.xml and a2dp.audio.policy.configuration.xml. It seems to be the most likey spot as most fixes/conversation starting with a9 going forward always take about a problem there.

Also, I've been able to double root it. I'm rooted with magisk 26100 and there's a utility that can change the entire OS to RW instead of RO so I can now easily direct copy the above mentioned config xml files to system/vendor/etc.
Too convert to RW see attachec file.

a14 beta2 gsi can be found here. I'm using the pixel 7p gsi.

I've switched to the Pixel 5 version of a14 b2 gsi and everything seems to be working, phone audio, camera, bt both for music and phone calls. This is a first for the v60, a14 and everything working!

hooutoo said:
I've switched to the Pixel 5 version of a14 b2 gsi and everything seems to be working, phone audio, camera, bt both for music and phone calls. This is a first for the v60, a14 and everything working!
Click to expand...
Click to collapse
Have you ever tried the pixel 5 version of say the a12L gsi? (I don't use the bleeding edge on phones I want to use as my primary).

hooutoo said:
Also, I've been able to double root it. I'm rooted with magisk 26100 and there's a utility that can change the entire OS to RW instead of RO so I can now easily direct copy the above mentioned config xml files to system/vendor/etc.
Too convert to RW see attachec file.
Click to expand...
Click to collapse
Did this work completely? I tried this twice (before Magisk 26.1). First time: incomplete RW. Second time: bootloop. My phone is still on A10.

AnnexedOne said:
Have you ever tried the pixel 5 version of say the a12L gsi? (I don't use the bleeding edge on phones I want to use as my primary).
Click to expand...
Click to collapse
Sorry, no. I'm really only interested in a14. As for converting to RO using the utility above I don't have it installed right now but I'm sure there are guides on the internet.

How this for dl speed?
a14 b2 pixel 5 gsi.... LTE only. Now need to work on getting 5g working.

A14 beta 3 gsi rom is now available:
https://sourceforge.net/projects/nippongsi/files/Generic/
I'm using the pixel5 rom and everything works fine, phone audio, bt audio and camera.
And NO, qdaq and fp are not working.

Any procedure step by step to flash A14 Beta 3 Nippon GSI in V60? i am interested to try this on my LG V600VM. Thanks