Database Info

ROOT disables Samsung Pay

I just updated my Samsung Pay for my gear S3 Classic. Just a heads up doing so on a rooted device you will no longer be able to use it. Unless someone knows a workaround. Currently using S4 Verizon.

eddyo1993 said:
I just updated my Samsung Pay for my gear S3 Classic. Just a heads up doing so on a rooted device you will no longer be able to use it. Unless someone knows a workaround. Currently using S4 Verizon.
Click to expand...
Click to collapse
same here need help finding a workaround

Device: Nexus 6 on Verizon, unencrypted, unlocked bootloader, Lineage OS based ROM (Android 7.1.1).
Magisk hide does get it to at least run without the root error message.. A tip from @candiesdoodle : If you are on a custom ROM, try setting *ro.build.tags=release-keys * instead of *ro.build.tags=test-keys* in build.prop.
However, even though SP runs without the root error, I am unable to add cards, even if I unroot and uninstall Magisk hide.

Amazing guy got it fixed awhile back
https://forum.xda-developers.com/an...d-samsung-gear-app-android-n-samsung-t3547035

SovPanda said:
Amazing guy got it fixed awhile back
https://forum.xda-developers.com/an...d-samsung-gear-app-android-n-samsung-t3547035
Click to expand...
Click to collapse
That post has nothing to do with Samsung Pay. His mod is a fix for issues people were having issues running the main Gear app on custom roms.
The fix for Samsung Pay is to use Magisk Hide. I am using Magisk Hide on my rooted HTC 10. I can add cards and make payments without issue.

MehStrongBadMeh said:
That post has nothing to do with Samsung Pay. His mod is a fix for issues people were having issues running the main Gear app on custom roms.
The fix for Samsung Pay is to use Magisk Hide. I am using Magisk Hide on my rooted HTC 10. I can add cards and make payments without issue.
Click to expand...
Click to collapse
And that's with the latest update ? Which got released a day ago?

candiesdoodle said:
And that's with the latest update ? Which got released a day ago?
Click to expand...
Click to collapse
Yep, joined the rewards program and everything

MehStrongBadMeh said:
That post has nothing to do with Samsung Pay. His mod is a fix for issues people were having issues running the main Gear app on custom roms.
The fix for Samsung Pay is to use Magisk Hide. I am using Magisk Hide on my rooted HTC 10. I can add cards and make payments without issue.
Click to expand...
Click to collapse
SP wasn't working for magisk for awhile as well on my HTC 10 so that became the solution and probably the best if magisk is ever detected again with an update

MehStrongBadMeh said:
Yep, joined the rewards program and everything
Click to expand...
Click to collapse
Any way you can use Magisk on S4 Verizon using Flashfire

Which version did you guys update it to? It still works on my rooted note 4, so I turn off the auto update for spay just in case.

gpmg762 said:
Which version did you guys update it to? It still works on my rooted note 4, so I turn off the auto update for spay just in case.
Click to expand...
Click to collapse
version 1.3.1703

Got samsung pay to work on watch!
after looking at what version of Samsung pay had on the watch which was 1.3.1703, I was able to find an apk from sammobile for version 1.2.5202. After downloading that version and I had to manually uninstall Samsung Pay through your phone settings and application manager or installing the older apk on top of the newer one would fail, I was able to access Samsung pay with no problems on my phone and was able to add back my card like i was able to do before. after adding my card I was able to blanch Samsung pay on my Watch but due to my watch Samsung pay version being higher than my phone version due to when Samsung pay updated before, it wouldn't let me use Samsung pay until my phone version was back to version 1.3.1703. but I was able to access Samsung pay on my watch with my cards showing up now. I haven't tried to see if it works but I assume that since the card is on the watch now It should work now. ill attach the older apk for anyone else to try.

Looks like we'll have to stick with version 1.2 5202 for spay to work properly for now, especially with rooted and non spay supported phones like my note 4.
Sent from my SM-N910G using Tapatalk 4

MehStrongBadMeh said:
Yep, joined the rewards program and everything
Click to expand...
Click to collapse
What all needs to be checked in the Magisk Hide list?
I have all the obvious ones checked like Samsung Pay, Gear S, etc, but SPay still says it detects root.

coolhandz said:
What all needs to be checked in the Magisk Hide list?
I have all the obvious ones checked like Samsung Pay, Gear S, etc, but SPay still says it detects root.
Click to expand...
Click to collapse
I did the entirety of Samsung Gear Apps:
Cell Provider
Gear S Plugin
Samsung Accessory Service
Samsung Gear
Samsung Health
Samsung Pay
Samsung Push Service
SASystemProviders
Basically, Search "Samsung" in Magisk Hide and go ham.

MehStrongBadMeh said:
I did the entirety of Samsung Gear Apps:
Cell Provider
Gear S Plugin
Samsung Accessory Service
Samsung Gear
Samsung Health
Samsung Pay
Samsung Push Service
SASystemProviders
Basically, Search "Samsung" in Magisk Hide and go ham.
Click to expand...
Click to collapse
I did all that and it still doesn't work. I even downloaded Root Checker and hid that and it worked so I know I Magisk Hide is working. Any other ideas?
What version of Magisk are you on? What version of the manager are you on too?

coolhandz said:
I did all that and it still doesn't work. I even downloaded Root Checker and hid that and it worked so I know I Magisk Hide is working. Any other ideas?
What version of Magisk are you on? What version of the manager are you on too?
Click to expand...
Click to collapse
Can't think of anything else. Maybe try clearing the Samsung Pay app data (maybe once it sniffs root it won't forget until you wipe its memory)
Magisk v12.0
Magisk Manager 4.3.1

So is there any way to use SPay on Nougat rom with root? Does Magisk+suhide work?

I'm livid, the latest update no longer allows Samsung pay to work even downgrading to 1.2.1xxx which I had done. Called Samsung, no help what so ever, now this watch is paperweight to me

arf8 said:
I'm livid, the latest update no longer allows Samsung pay to work even downgrading to 1.2.1xxx which I had done. Called Samsung, no help what so ever, now this watch is paperweight to me
Click to expand...
Click to collapse
The watch works fine with a rooted phone, just get that damn nag screen on the samsung pay app. I hope someone figures out a fix for it.

[ROM] [UNOFFICIAL] Lineage OS 17.1 | Unihertz Jelly 2

roms - Google Drive
drive.google.com
This ROM is built using binaries from non-european (TEE) version of Jelly 2. Theoretically it should work on european (EEA). If it won't - contact me, I'll prepare ROW based on EEA binaries.
ROM can be installed via TWRP. How to install TWRP - https://forum.xda-developers.com/t/recovery-twrp-3-5-2-unihertz-jelly-2.4281493/
Source code - https://github.com/Meetoul/android_device_Unihertz_Jelly2
UPD. Experimental version of Lineage OS 18.1 (Android 11) is also available by the attached GDrive link.

Hi, would you be willing to share the source repo and build instructions? Thanks!

lakkimsetty.baba said:
Hi, would you be willing to share the source repo and build instructions? Thanks!
Click to expand...
Click to collapse
Here you go https://github.com/Meetoul/android_device_Unihertz_Jelly2

Meetoul said:
roms - Google Drive
drive.google.com
This ROM is built using binaries from non-european (TEE) version of Jelly 2. Theoretically it should work on european (EEA). If it won't - contact me, I'll prepare ROW based on EEA binaries.
ROM can be installed via TWRP. How to install TWRP - https://forum.xda-developers.com/t/recovery-twrp-3-5-2-unihertz-jelly-2.4281493/
Source code - https://github.com/Meetoul/android_device_Unihertz_Jelly2
Click to expand...
Click to collapse
Thanks for developing the room
But unfortunately it does not work
After burning in twrp it constantly makes a boot loop
I tried several times
I'll be happy if you can fix that
(Sorry for my obscure language, I use translation,)

Gon112 said:
Thanks for developing the room
But unfortunately it does not work
After burning in twrp it constantly makes a boot loop
I tried several times
I'll be happy if you can fix that
(Sorry for my obscure language, I use translation,)
Click to expand...
Click to collapse
Hi!
What version of Jelly2 do you have? TEE, EEA, JP?

Meetoul said:
Hi!
What version of Jelly2 do you have? TEE, EEA, JP?
Click to expand...
Click to collapse
NONE EEA

Gon112 said:
NONE EEA
Click to expand...
Click to collapse
Sorry, I cannot understand you.
Please put a number that corresponds to the yours Jelly2 version
TEE
EEA
JP

1

Meetoul said:
Sorry, I cannot understand you.
Please put a number that corresponds to the yours Jelly2 version
TEE
EEA
JP
Click to expand...
Click to collapse
1

Gon112 said:
1
Click to expand...
Click to collapse
The ROM is already built on top of the latest TEE binaries and it works on my Jelly2...
Probably, you have faced some issues during flashing the ROM. Please flash your Jelly2 back to stock ROM using SP Flash Tool and try again.

I have been using this ROM for couple of weeks now, it seems solid - didn't crash or had any issues.
The battery life however is very bad. I am using Magisk ACC module to limit the charge to 70% and it dropped from 70% to 34~37% within 8-ish hours (while I am asleep) consistently with all radios off (with regular cell network on for calls and texts, LTE off). The stock ROM used to drop at most 3% while I am asleep.
I think the stock ROM has aggressive app kill/ background process limit. I am going to try with those options enabled (in developer options) to see if there's going to be an improvement.
If anyone had issues like the above and has a conf, do let me know, thanks!
Edit: Forgot to mention that I also use AccuBattery and Greenify. Greenify is set to kill all user apps except for Magisk and AccuBattery.

I have the EU Version of Jelly 2, and yet it seems to work fine
Thank you very much for your efforts.
If i find any bugs ill report them

beck.hannes said:
I have the EU Version of Jelly 2, and yet it seems to work fine
Thank you very much for your efforts.
If i find any bugs ill report them
Click to expand...
Click to collapse
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)

Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Click to expand...
Click to collapse
Hi
How many times have I tried to install LOS 17.1 it did not work,
Now I have tried to install LOS 18.1 and it works fine and perfect
Thanks!!
I'll be happy if you can add support for things you mentioned that are not currently supported,
Thank you good man.

Meetoul said:
AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
Click to expand...
Click to collapse
Would it help for you to have someone test VoLTE (and possibly WiFi calling?)
I'm considering picking one of these up and was just assesing what the community is behind it for custom ROMs. I had the original Jelly and the ROM community for that was very limited, and I was in over my head when trying to build it for myself. I would be glad to help however if you think you'll be using the device for a while

Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software
Click to expand...
Click to collapse
Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Click to expand...
Click to collapse
Hey, as far as i tested everything works for me.
There is one thing i noticed:
When booting, Lineage OS tells that the Build has been signed with Public Key, this seems to be a bit of a security issue. Is it possible to resolve that for the LOS 18 version. (Is that testable yet?)
Im fine with not having VoLTE, i think no Custom Rom is able to support it yet and it will just get important when the 3G network will be disabled...
Also if you need more help for testing specific stuff, i can do it.

beck.hannes said:
Hey, as far as i tested everything works for me.
There is one thing i noticed:
When booting, Lineage OS tells that the Build has been signed with Public Key, this seems to be a bit of a security issue. Is it possible to resolve that for the LOS 18 version. (Is that testable yet?)
Im fine with not having VoLTE, i think no Custom Rom is able to support it yet and it will just get important when the 3G network will be disabled...
Also if you need more help for testing specific stuff, i can do it.
Click to expand...
Click to collapse
@Meetoul I installed the LineageOs 18 now which seems to be fine too.
2 Warnings appear after boot. Again the one with the public key, and a new one: "Serial Console active"

My apologies for cross posting. But I initially replied in the wrong topic.
I just received my Jelly 2. It was on 2020 and I went straight through your files. Your TWRP does not respond on my European Jelly 2. And after a first reboot to recovery, TWRP was gone. What I mean with not responding is that the touch screen does not respond. But I connected an USB trackball to use as an input device and switched cables in between adb sideloads. So I finally got it working.
For some reason during reboot TWRP warns me that there is no OS installed. But LoS 18.1 (yours) booted fine. Also flashed opengapps 2707 nano.
After a reboot (phone is still restoring apps) there is a "serial console is enabled" message "performance is impacted, check bootloader". Any instructions on how to get rid of that message? Other than that so far so good.

Die Bruine said:
My apologies for cross posting. But I initially replied in the wrong topic.
I just received my Jelly 2. It was on 2020 and I went straight through your files. Your TWRP does not respond on my European Jelly 2. And after a first reboot to recovery, TWRP was gone. What I mean with not responding is that the touch screen does not respond. But I connected an USB trackball to use as an input device and switched cables in between adb sideloads. So I finally got it working.
For some reason during reboot TWRP warns me that there is no OS installed. But LoS 18.1 (yours) booted fine. Also flashed opengapps 2707 nano.
After a reboot (phone is still restoring apps) there is a "serial console is enabled" message "performance is impacted, check bootloader". Any instructions on how to get rid of that message? Other than that so far so good.
Click to expand...
Click to collapse
Touch in recovery
Have you tried the latest release which includes fixes for both available touch panes (at least for TEE Jelly2)? If yes and it doesn't work anyway, could you please provide dmesg output from recovery and from normal boot? Output of dmesg should be collected as soon as ADB available. Also, please collect kallsyms using the following steps:
Code:
adb root
adb shell
echo 0 > /proc/sys/kernel/kptr_restrict
sysctl -w kernel.randomize_va_space=0
cat /proc/kallsyms >/sdcard/symbl.txt
exit
exit
adb pull /sdcard/symbl.txt
Annoying "Serial console is enabled" notification
You can just long press on the notification and disable notifications from Development Settings.

Thanks, this 'latest' release works! I am curious though, why do I get the message that there is no OS installed when I reboot from recovery? Or is that gonna be a long as reply .Also a few mount errors during flashing and reboot. But, my phone works for 99%.
Only thing not working in my banking app is the fingerprint sensor, also in the Ebay app (which I use once a year). Do you know why this is? Amazon video, Ziggo streaming app, even my banking app works. Fingerprint to unlock the phone also works. Just not in apps. Is this due to it being unlocked?
I come from a qx1000/Pro1 with LoS 18.1 which died on me Wednesday night. That's why I'm asking. That thing was also unlocked, but no error messages there. Also the Corona check app states that the J2 is rooted (which it isn't). Exactly the same configuration as my Pro1. But no warnings on that phone.
Not real complaints, just thought I'd share. This will be my daily driver for the next few months. So if you need a heavy tester, I'm your man.
@Meetoul
The battery drains in 24 hours, is this normal? I can't find any apps draining it. Could the enabled serial console be the culprit?
Edit2:
Hotspot not working for me. It connects but does not provide an IP address to clients. I tried several stock Android devices, without success. All four devices connect, but keep waiting for an IP address.
So now I'm typing this via Bluetooth sharing, which sucks I can tell you.
If you have any suggestions, I am more than willing to try them out...

Question Have to Reconnect watch everytime my phone restarts.

I'm using a Galaxy watch 4 Classic for a month now and it has been working perfectly fine. But the only issue I'm facing is unable to quickly reconnect after my phone restarts. I have to repeat the long first-time connection procedure (which has got quite frustrating TBH). I even have to do this when I turn on Flight Mode on my phone. I know it is not how it is supposed to act normally but I believe there must be some solution to this.
It seems to be something wrong with my Samsung Wearables app. It does not seem to remember any device after a restart.
Also to mention, my phone is rooted if that is causing this.

It is indeed your root that's causing this problem
Install the Bluetooth Library patcher via Magisk or TWRP (whichever you prefer) from here:
https://github.com/3arthur6/BluetoothLibraryPatcher/releases/tag/v2.4.1
And this problem should go away. Reboot and re-pair your device. Should remember them afterwards.

I tried to install the Bluetooth patch file but, the root manager I have installed "EFTSU Manager", does not open any of the Bluetooth patch files I downloaded. I installed Magsik but it does not seem to work on this device. Also my device boots normally. No TWRP from where I can install packages.
Please guide me on how I should make this work... If any additional details are required, ask ill provide them.

If not Top Secret...
Why not tell Model Name of your Phone...
Samsung not Samsung?
For instance I fixed this ugly issue on my Samsung SM-A202F rooted with Magisk...
Best Regards

Here my "Diary"...
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
IMHO only fixed after FukKkKtory Reset Watch again.
Best Regards

Skipping f%$ing useless Intro by tap tap few times on Screen.
This is since Tizen totally stupid feature because in earlier Tizen firmware Intro asked for skip...
Seems Samsung loves to torture user by stupid tasks.
Best Regards

adfree said:
If not Top Secret...
Why not tell Model Name of your Phone...
Samsung not Samsung?
For instance I fixed this ugly issue on my Samsung SM-A202F rooted with Magisk...
Best Regards
Click to expand...
Click to collapse
My Device is Samsung Galaxy S9 SM-G960F. I guess it is not rooted with magisk because magisk app wont work on this device.

ShaDisNX255 said:
It is indeed your root that's causing this problem
Install the Bluetooth Library patcher via Magisk or TWRP (whichever you prefer)
Click to expand...
Click to collapse
As you told, i tried to install the patch file using Magisk for which i installed Magisk. But it did not seem to work. Have a look at the screenshots from the app and log.
What should i do now.

Question Any Magisk Module that can replace system audio files (/media/audio/ui) ?

Hello! currently running Dr. Ketan S09 on SM-S908B/DS and was wondering if there are any modules that can replace system audio files for customization?
I tried older method with this flasher tool that @alessio89g created some years ago. I used my favorite Metal Gear Solid sounds in this pack. however when flashing it complains that magisk needs to be updated to 13 or something.
It's a long shot but maybe someone is knowledgeable enough to fix up this zip and get it working so we can all enjoy?
Thanks for any help and input on this

C3R741N said:
Hello! currently running Dr. Ketan S09 on SM-S908B/DS and was wondering if there are any modules that can replace system audio files for customization?
I tried older method with this flasher tool that @alessio89g created some years ago. I used my favorite Metal Gear Solid sounds in this pack. however when flashing it complains that magisk needs to be updated to 13 or something.
It's a long shot but maybe someone is knowledgeable enough to fix up this zip and get it working so we can all enjoy?
Thanks for any help and input on this
Click to expand...
Click to collapse
Try this

dr.ketan said:
Try this
Click to expand...
Click to collapse
I will update how this goes soon, I unfortunately have to triple wipe and re-setup device. Google Fi support had me boot into safe mode when trying to get my 5g service to stay on (it kept staying on 4g) and doing so wiped the rom when booting back in so I'm going stock , getting my 5g to work correctly, then setting up rom again, and then I will flash this nice module you linked for me and let you know how it goes. Thanks Doc
(as it turns out it was googles network acting up for some devices and is being fixed, made me screw up phone for no reason)
alessio89g also responded in another thread and gave me these also haven't tested them yet but said they can be used in roms, the apk might be helpful for selecting sounds in roms that can't access /media
I will update as soon as I get a chance to test all this stuffs

dr.ketan said:
Try this
Click to expand...
Click to collapse
IT WORKS ALMOST 100% PERFECTLY THANK YOU SOO MUCH!!!!! the only thing I need to adjust is the volume for unlock and lock because it's a tad quiet and the only sound I can't get to play is when using the navigation bar buttons(S_HW_Touch.ogg). I had a sound set to the right file but it's not playing anything.
I realized this file was used back on Note 5 when we used to have physical buttons on the phone but now we have UI integrated buttons on the screen, so not sure if this file even activates a sound for that anymore, or why its still in the system files, but I also don't understand how that's all linked together so maybe we can't assign a sound to those anymore?

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