Any other options available for the OP7P fingerprint unlock animation? - OnePlus 7 Pro Questions & Answers

I was wondering if there are other options available for the OP7P fingerprint unlock animation? I know that the McLaren animation became available for the OP6T through a settings hack, but the McLaren (or other animations) don't seem to be available for the OP7P.

Something like this? https://forum.xda-developers.com/oneplus-7-pro/themes/fingerprint-nfl-fingerprint-team-logo-t3942407

¿GotJazz? said:
I was wondering if there are other options available for the OP7P fingerprint unlock animation? I know that the McLaren animation became available for the OP6T through a settings hack, but the McLaren (or other animations) don't seem to be available for the OP7P.
Click to expand...
Click to collapse
There's four options in Android Q Developer Preview 4. The fourth, to the right and not in the screenshot, is no animation at all

Hi, @docnok63 - Yes, I have those options as well on the stock OOS 9 (Pie) ROM.
Is there a way to get the McLaren animation on the OP7P?

¿GotJazz? said:
Hi, @docnok63 - Yes, I have those options as well on the stock OOS 9 (Pie) ROM.
Click to expand...
Click to collapse
A quick Google search tells me you can try the Magisk module here

docnok63 said:
A quick Google search tells me you can try the Magisk module here
Click to expand...
Click to collapse
I got the impression that the Magisk module only enabled the hidden McLaren animation on the OP6T. I had tried enabling the McLaren animation using one of the other (non-Magisk) methods, and it didn't work on the OP7P.

¿GotJazz? said:
I got the impression that the Magisk module only enabled the hidden McLaren animation on the OP6T. I had tried enabling the McLaren animation using one of the other (non-Magisk) methods, and it didn't work on the OP7P.
Click to expand...
Click to collapse
The only thing McLaren I found working was the boot animation in the xXx Magisk mod. He doesn't have any options for the fingerprint animation, though.

Related

[SOLVED] with Magisk installed is missed some gestures

I have TA-1046 with Pie and unlocked bootloader...
After install (via TWRP) Magisk (official zip release (tested 17.1 and 17.2)), then is missed:
From Settings/System/Gestures:
- Swipe fingerprint for notification
- Swipe up on Home button
- Lift to check phone
From Settings/Display:
- Double tap to wake
After uninstall Magisk, then all this gestures is available again, this is not (direct) related to unlocked bootloader, still have unlocked and without Magisk installed is all Gestures here...
I try following:
- enabled Magisk hide
- activated MagiskManager
- installed Magisk module "MagiskHide Props Config" (but not manualy changed anynthing in prop files)
Anyone have any tips for fixing this?
btw: screenshots is from DP4.1, but in Stable Pie is same problem...
UPDATE: thanks to Doktaphex, workaround found, confirmed with screenshot here
UPDATE2: actual version (1.7.4) not working, i not have installed other version before than 1.4.3, reinstalled this older version manualy from Download folder working
Where did you get TWRP for pie? Please guide me to the correct place
Broadcasted from Zeta Reticuli
I had the same issue! I'm on Official Android 9 (version 00WW_3_22C) TA1046, and i root it with magisk by following this method:
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-root-ab-partition-scheme-t3792509
When i remove Magisk Module, Gesture navigation, Lift to check and Double tap to wake are available again!
Gravemind2015 said:
Where did you get TWRP for pie? Please guide me to the correct place
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I think he didn't flash TWRP, he booted into it and flashed Magisk. That's what I did too.
---------- Post added at 12:07 ---------- Previous post was at 11:35 ----------
I am on Oreo September and I keep getting a blank screen on Smart Lock. every time I enable it somehow (Settings>Lockscreen>Trust Agents>Disable Smart Lock>Reboot>Enable Smart Lock), it gets blank again after some time.
k3dar7 said:
I have TA-1046 with Pie and unlocked bootloader...
After install (via TWRP) Magisk (official zip release (tested 17.1 and 17.2)), then is missed:
From Settings/System/Gestures:
- Swipe fingerprint for notification
- Swipe up on Home button
- Lift to check phone
From Settings/Display:
- Double tap to wake
After uninstall Magisk, then all this gestures is available again, this is not (direct) related to unlocked bootloader, still have unlocked and without Magisk installed is all Gestures here...
I try following:
- enabled Magisk hide
- activated MagiskManager
- installed Magisk module "MagiskHide Props Config" (but not manualy changed anynthing in prop files)
Anyone have any tips for fixing this?
btw: screenshots is from DP4.1, but in Stable Pie is same problem...
Click to expand...
Click to collapse
I just got the OTA today and had the exact same problem. Initially i thought it was just a bug from the update and did a factory reset, and it worked and had the gestures back until I installed Magisk again. Did you find how to fix it?
Gravemind2015 said:
Where did you get TWRP for pie? Please guide me to the correct place
Click to expand...
Click to collapse
i not flash TWRP, install Magisk via ONLY BOOTed TWRP(Oreo version)
@siberflyers, @TheWing still no have sollution
Same problem here on TA1062.
Do we suspect it's the phone or magisk to blame?
@k3dar7 Need your help guys. I have switched back to Oreo after my brief stay on Pie. I have made a Github issue regarding this here https://github.com/topjohnwu/Magisk/issues/668
The dev has replied and is asking for the value of
cat /proc/mounts
Click to expand...
Click to collapse
on an UNROOTED (Magisk uninstalled) Pie. Could someone perhaps provide this info to the ticket contained above, to get a resolution to this issue?
braveheartleo said:
@k3dar7 Need your help guys. I have switched back to Oreo after my brief stay on Pie. I have made a Github issue regarding this here https://github.com/topjohnwu/Magisk/issues/668
The dev has replied and is asking for the value of on an UNROOTED (Magisk uninstalled) Pie. Could someone perhaps provide this info to the ticket contained above, to get a resolution to this issue?
Click to expand...
Click to collapse
info added: https://github.com/topjohnwu/Magisk/issues/668#issuecomment-433522871
braveheartleo said:
@k3dar7 Need your help guys. I have switched back to Oreo after my brief stay on Pie. I have made a Github issue regarding this here https://github.com/topjohnwu/Magisk/issues/668
The dev has replied and is asking for the value of on an UNROOTED (Magisk uninstalled) Pie. Could someone perhaps provide this info to the ticket contained above, to get a resolution to this issue?
Click to expand...
Click to collapse
Here is the output in a text file. Had one of my friend pull it out from his TA-1046 Global ROM Pie Stable, September patch.
I hope it helps (◕‿◕)
Edit: Commented on github with pastebin link. There already was one but I saw more lines on mine who decided to post it anyway
@k3dar7 @Gravemind2015 Many thanks Hopefully, this will lead to a fix so that Magisk properly supports our device on Pie sans the glitches.
If you use the PIX3LIFY mod, it will re-enable all missing gestures.
Doktaphex said:
If you use the PIX3LIFY mod, it will re-enable all missing gestures.
Click to expand...
Click to collapse
I install and active this module.... And nothing happens.... Gesture Navigation is still missing...
siberflyers said:
I install and active this module.... And nothing happens.... Gesture Navigation is still missing...
Click to expand...
Click to collapse
Strange. It worked for me, not that I was searching for a solution, so I thought that I would share my experience
Doktaphex said:
If you use the PIX3LIFY mod, it will re-enable all missing gestures.
Click to expand...
Click to collapse
You are a WIN, thx Work for me, missed gestures is back with Magisk/MagiskManager installed...
edit: add screenshot of Magisk/Modules
braveheartleo said:
@k3dar7 @Gravemind2015 Many thanks Hopefully, this will lead to a fix so that Magisk properly supports our device on Pie sans the glitches.
Click to expand...
Click to collapse
your issue be closed, but if i try magisk canary build 9592a69 then see problem not fixed, can you please try?
and if too have still problem with missed gesture (without forkaround with PIX3LIFY), then please reopen issue?
k3dar7 said:
your issue be closed, but if i try magisk canary build 9592a69 then see problem not fixed, can you please try?
and if too have still problem with missed gesture (without forkaround with PIX3LIFY), then please reopen issue?
Click to expand...
Click to collapse
Unfortunately, I can't do that atm. I'm on Oreo right now and I'm not moving up to Pie. I'm afraid you'll have to ask the others to try it out, and if they too concur with your experience, then I'd gladly reopen the issue. ?
braveheartleo said:
Unfortunately, I can't do that atm. I'm on Oreo right now and I'm not moving up to Pie. I'm afraid you'll have to ask the others to try it out, and if they too concur with your experience, then I'd gladly reopen the issue. ?
Click to expand...
Click to collapse
i think if you not have now Pie, then i wait if someone confirm/disprove and i reopen own issue
btw: actual (1.7.4) version Pix3lify stop working (=not enable missed gesture), i not have installed other version before than 1.4.3, reinstalled this (1.4.3) manualy from Download(if have installed this version before) folder working
With Pie Nobember update is now NOT need workaround using Pix3lify 1.4.3 mod...
now gestures is simply not blocked with installed Magisk (17.3 which is version BEFORE (not working for me) patch on Magisk side)

[Guide][Magisk] Dolby Digital Plus-Stock/Custom MIUI PIE AND Q ;)

Many people ask how to install Dolby for Miui Pie.
It's not as easy as Oreo, but still you can do it :angel:
It's my way to work
1. Flash Dolby IN Magisk and reboot
Dolby 2.7
https://forum.xda-developers.com/attachment.php?attachmentid=4709535&d=1550731507
Or Dolby 6.5
https://forum.xda-developers.com/attachment.php?attachmentid=4772941&d=1559901603
2. Find in magisk and Flash Audio Modification Library in magisk and reboot
3. Find in magisk and Flash AUDIO COMPATIBILITY PATCH in magisk
The correct configuration of the installation:
Skip Vol key Test,
Preinstaling (cont) And press successively keys:
down,down,up,down,up and reboot.
4.Enjoy
Now steps for Android Q miui 11!!
So:
1)Flash in Magisk Magisk Selinux Changer to Permissive
a)Flash Dolby 6.8
2)Do 2-3 Steps
3) Run the app without crash!
Screenshots
https://ibb.co/GstFD7b
https://ibb.co/GRPf6FJ
https://ibb.co/516w33Y
Latest Magisk Beta is recommended
Please report bug if you check Both versions dolby And it still doesn't work
****tested on my mi8, K20 pro, CC9 and works
Credits:
@repey6 For Universal Dolby Digital Plus Pie
@Zackptg5 For Audio Modification Mods
@DeveDroid Finding a way for android 10/miui 11
Radzią said:
ooMany people ask how to install Dolby for Miui Pie.
It's not as easy as Oreo, but you can still do it :angel:
It's my way to work
1. Flash Dolby IN Magisk and reboot
https://drive.google.com/file/d/1DLpL6S5rE9XVFB5WXASHAPqtp0rFyhXq/view
2. Flash Audio Modification Library v2.1 in magisk and reboot
https://zackptg5.com/downloads/Audio-Modification-Library_v2.1.zip
3. Flash AUDIO COMPATIBILITY PATCH in magisk and reboot
https://github.com/JohnFawkes/Audio...oad/1.7.3/Audio-Compatibility-Patch_1.7.3.zip
The correct configuration of the installation:
Type a vol key
Type vol up
Type vol down
And type
no,no,no,yes,no,yes and reboot.
4.Enjoy
https://docs.google.com/document/d/1AEyKHZfCmSSlABmtj49_QS4OYqr76UCqKcLjvLvnheA/edit?usp=drivesdk
****tested on mi8 and works
Click to expand...
Click to collapse
I think you should write instead
no,no,no,yes,no,yes and reboot.
as
down,down,down,up,down,up and reboot.
To avoid confusions. Because some choices aren't yes or no.
hahahaha, just a guess.
atrufinibr said:
I think you should write instead
no,no,no,yes,no,yes and reboot.
as
down,down,down,up,down,up and reboot.
To avoid confusions. Because some choices aren't yes or no.
hahahaha, just a guess.
Click to expand...
Click to collapse
Oki, I've improved
@Radzią
What does "type a vol key" means? Do I need to type "a vol key" on some text processor? What is this...
English isn't that hard, come on.
up, down, down, down, down, up, down, up
@Radzią
What does "type a vol key" means? Do I need to type "a vol key" on some text processor? What is this...
English isn't that hard, come on.
up, down, down, down, down, up, down, up
V4LKyR said:
@Radzią
What does "type a vol key" means? Do I need to type "a vol key" on some text processor? What is this...
English isn't that hard, come on.
up, down, down, down, down, up, down, up
Click to expand...
Click to collapse
Improved. I hope that everything is clear now.
Radzią said:
Dolby Atmos
Click to expand...
Click to collapse
It's not Dolby Atmos.
Screenshots plz ?
Sadly doesn't work on PixelExperience CAF with PureCoffee kernel.
pinx said:
Sadly doesn't work on PixelExperience CAF with PureCoffee kernel.
Click to expand...
Click to collapse
because this method only works on miui pie
Force closing on xiaomi.eu
How to install viper on miui pie?
Number 2 "not found"
roncato said:
Number 2 "not found"
Click to expand...
Click to collapse
Number 2 and 3 can be found in magisk
Alfian Firmansyah said:
How to install viper on miui pie?
Click to expand...
Click to collapse
download and install with magisk, i installed on miui eu pie and work.. install how NO SYS APP and work all
Radzią said:
Number 2 and 3 can be found in magisk
Click to expand...
Click to collapse
Thanks
Doesn't work even its installed correctly, Latest miui Pie
Kuato said:
Doesn't work even its installed correctly, Latest miui Pie
Click to expand...
Click to collapse
Yes , but with the latest dolby 6.4 works I noticed that sometimes dolby crash but still It works
Link in the first post
Radzią said:
Yes , but with the latest dolby 6.4 works I noticed that sometimes dolby crash but still It works
Link in the first post
Click to expand...
Click to collapse
Yeah, Dolby will crash upon changing mode or toggle setting, but it still be saved and the effect still work fine
sushuguru said:
Yeah, Dolby will crash upon changing mode or toggle setting, but it still be saved and the effect still work fine
Click to expand...
Click to collapse
Maybe the problem will disappear in new releases Miui Beta Pie :angel::angel:
The most important is that dolby works

Android 11 beta 2.5 released (display hz fix)

Google dropped an incremental update to address the whole display flicker issue as well as a few other smaller issues. I'm running it now and can confirm its a night and day difference as far as the display. Using the refresh rate overlay, you can see it stays at 90hz indefinitely while the smooth display option is toggled. They didn't just add back the force 90hz display option like I was hoping but this achieved the same result so I won't complain.
Download link for Android 11 2.5 factory image: https://developer.android.com/preview/download
Download link for Android 11 2.5 OTA:
https://redirect.viglink.com/?forma...with Pixel 4 display fix - 9to5Google&txt=OTA
Magisk Canary on my Pixel 4XL running Android 11 Beta 2.5
All good here. Notifications are functioning.
Any idea if flashing this new version will allow me to have face unlocked back on Android 10? No luck with using the magisk module
chazall1 said:
Magisk Canary on my Pixel 4XL running Android 11 Beta 2.5
All good here. Notifications are functioning.
Click to expand...
Click to collapse
Did you update from Android 11 Beta 2.0, or did you go straight from 10 to 11 2.5?
I did flash-all without the -w, then used magisk canary, updated to the latest, and flashed the patched boot.img, and it still boot loops for me. It says there's no valid boot slot. Which options did you use in Magisk when creating the patched boot img?
matt99017d said:
Any idea if flashing this new version will allow me to have face unlocked back on Android 10? No luck with using the magisk module
Click to expand...
Click to collapse
Hi,
With the july update face unlock works just fine.
1dopewrx05 said:
Google dropped an incremental update to address the whole display flicker issue as well as a few other smaller issues. I'm running it now and can confirm its a night and day difference as far as the display. Using the refresh rate overlay, you can see it stays at 90hz indefinitely while the smooth display option is toggled. They didn't just add back the force 90hz display option like I was hoping but this achieved the same result so I won't complain.
Download link for Android 11 2.5 factory image: https://developer.android.com/preview/download
Download link for Android 11 2.5 OTA:
https://redirect.viglink.com/?forma...with Pixel 4 display fix - 9to5Google&txt=OTA
Click to expand...
Click to collapse
The smooth display setting does not fix the refresh rate at 90Hz in low light conditions.
You can achieve the same result like the force 90Hz from developer options with the following adb command:
adb shell settings put system min_refresh_rate 90.0
After this, toggling the smooth display setting will have no effect. The display refresh rate will always be 90Hz.
To disable it again do the following:
adb shell settings delete system min_refresh_rate
Edit:
First seen in this thread: https://forum.xda-developers.com/pi...force-90hz-refresh-rate-t3994149/post83118135
matt99017d said:
Any idea if flashing this new version will allow me to have face unlocked back on Android 10? No luck with using the magisk module
Click to expand...
Click to collapse
It depends how you "broke" face unlock. If it broke from updating to and older Android 11 beta then going back to Q, then yes it should fix that. If it broke due to corrupting your Persist.img then no, the only way to fix that is to have a backup of your Persist from when it was good and manually restoring the old persist.img.
I flashed the incremental 2.5 update and face lock did not work. I then downloaded Android 10 July and that brought everything back to normal as it should. I tried this numerous times before the incremental update to no avail. I'm so glad that they fixed it!
Update:
SDK Platform-Tools: r30.0.4

Oneplus 8t cyberpunk

Hi,
I want to buy a cyberpunk edition and i want to know. If it is with hydrogen os or oxygen os ?
If i flash it on oxygen ose, did i loose the special theme and Addons ?
Thanks
OnePlus 8t cyberpunk help.
Hi guy, I'm in the same boat have the opportunity to buy a Cyberpunk edition but have not because I've been told hydrogen os is for China and not a lot can translate to English ? Is this true and I'd loose Google apps ... Editor Dan Lin's latest article says they can all be loaded on is this correct ?
I'm having trouble understanding having a awesome phone like this if you can't upgrade to oxygen os and loose all the cool themes and ui what would be the point ...
So I'd love some in depth clarification of what is going on with these 2 os.
Will you be able to load the cyberpunk ui later in a patch to oxygen os ? So many questions so many review and unboxing but know one is talking about the right topics
Wait for this guy to perfect the conversion
https://forum.xda-developers.com/showpost.php?p=83927241&postcount=83
I just made sure to have my whole phone setup with gapps from the latest global updates. Then when i converted I was able to keep all Google apps. A format nukes them but with root and magisk gapps from flame gapps I was able to get gapps back
g96818 said:
Wait for this guy to perfect the conversion
https://forum.xda-developers.com/showpost.php?p=83927241&postcount=83
Click to expand...
Click to collapse
Yes, but this guy converted a oxygen os to hydrogen os cyberpunk.
Here WE don't want the same...we want a cyberpunk, put oxygen os on it and have all themes...
g4seb said:
Yes, but this guy converted a oxygen os to hydrogen os cyberpunk.
Here WE don't want the same...we want a cyberpunk, put oxygen os on it and have all themes...
Click to expand...
Click to collapse
It needs h2os or it doesn't work. So that won't work for you bro.
FullOfHell said:
It needs h2os or it doesn't work. So that won't work for you bro.
Click to expand...
Click to collapse
In the past, some people extract the oneplus 6t mc laren animations to put it in other 6t.
Perhaps it's possible ?
Or in h2s IS it possible to put gapps ? And other language ?
Staefrosty said:
Hi guy, I'm in the same boat have the opportunity to buy a Cyberpunk edition but have not because I've been told hydrogen os is for China and not a lot can translate to English ? Is this true and I'd loose Google apps ... Editor Dan Lin's latest article says they can all be loaded on is this correct ?
I'm having trouble understanding having a awesome phone like this if you can't upgrade to oxygen os and loose all the cool themes and ui what would be the point ...
So I'd love some in depth clarification of what is going on with these 2 os.
Will you be able to load the cyberpunk ui later in a patch to oxygen os ? So many questions so many review and unboxing but know one is talking about the right topics
Click to expand...
Click to collapse
Where to read dan lin's article
Mine should arrive this week or next, so in the same boat. If English support is optimal and Google Apps can be flashed, I'd like to keep it as close to stock as possible. Has anyone else had experience with HydrogenOS on this phone?
g4seb said:
In the past, some people extract the oneplus 6t mc laren animations to put it in other 6t.
Perhaps it's possible ?
Or in h2s IS it possible to put gapps ? And other language ?
Click to expand...
Click to collapse
I was that guy. I left xda right after that and only returned for 7t Resurrection Remix posts. This will be possible, but won't be done through a mod or it won't be 100%. Yes you can flash magisk gapps. Or with our mod you flash overtop oos and already have gapps. As you can see I'm running latest h2os with cyberpunk resources intact. Locked bootloader and no root. On a normal 8t Global. H2os is normal like oos, but tons of bloat. Once you get rid of it it's ok. But...I don't know about any article, but even with your cyberpunk 8t, it will run h2os and if you flash oos over it you will not keep cyberpunk resources and features.
@FullOfHell : ok so at this time, thé best solution if i buy a cyberpunk edition, IS to have H2Os, put thé gapps, IS this real ?
g4seb said:
@FullOfHell : ok so at this time, thé best solution if i buy a cyberpunk edition, IS to have H2Os, put thé gapps, IS this real ?
Click to expand...
Click to collapse
Yes it only comes with h2os, so if I were you and needed gapps flash these:
https://sourceforge.net/projects/fl....0-basic-arm64-20201108-ALPHA-12.zip/download
Or whatever is recent when you get yours. You install thru magisk. Microg is an option too
Ok thanks
Seems a bad choice from a sales point of view not to be able to run there new Os and keep the cyberpunk themes .. and with new more updated phone coming 2021 the cyberpunk phone will die as everyone will want the latest and greatest not outdated due to a theme. I have a oppo find X2 pro and was ready to swap for the cyberpunk but if you can't get gapps and keep the themes of the phone. Just disappointed.
Is putting the the gapps a simple process or long and tedious ?
FullOfHell said:
Yes it only comes with h2os, so if I were you and needed gapps flash these:
https://sourceforge.net/projects/fl....0-basic-arm64-20201108-ALPHA-12.zip/download
Or whatever is recent when you get yours. You install thru magisk. Microg is an option too
Click to expand...
Click to collapse
What is "Microg" ?
g4seb said:
@FullOfHell : ok so at this time, thé best solution if i buy a cyberpunk edition, IS to have H2Os, put thé gapps, IS this real ?
Click to expand...
Click to collapse
MicroG is a google alternative although I never used it.
FullOfHell said:
I was that guy. I left xda right after that and only returned for 7t Resurrection Remix posts. This will be possible, but won't be done through a mod or it won't be 100%. Yes you can flash magisk gapps. Or with our mod you flash overtop oos and already have gapps. As you can see I'm running latest h2os with cyberpunk resources intact. Locked bootloader and no root. On a normal 8t Global. H2os is normal like oos, but tons of bloat. Once you get rid of it it's ok. But...I don't know about any article, but even with your cyberpunk 8t, it will run h2os and if you flash oos over it you will not keep cyberpunk resources and features.
Click to expand...
Click to collapse
Quick question: how do you flash magisk modules on the canary build? Thanks.
sameog said:
Quick question: how do you flash magisk modules on the canary build? Thanks.
Click to expand...
Click to collapse
The same as you would any other way with magisk. I don't have any modules or root or bootloader unlocked.
Hey guys,
So, I got an 8T Cyberpunk Edition two days ago. And I try to convert Hydrogen OS into Oxygen OS, I downloaded an europe Oxygen OS from here(I did not root the device or unlock bootloader, just download the zip file only), then I copied the zip file to root directory of the device and used "Local Update" to update the phone. After finished, I restarted the device. But I was stuck at booting screen, so I cleaned the "System setting/cache" or even "Format the device". I thought I will see the Oxygen logo after doing those steps, but it never happen. As a result, the Cyberpunk logo came up and still go into Hydrogen OS.
I tried like 5 times using "Local Update", not working at all. I was mad, and then I try to install Qualcomm USB driver(9008 driver?) and then follow the instruction here, and finally it became Oxygen OS, no more Cyberpunk loading screen. I was very happy and then try to apply the latest update from "System Update", it does show me there is a "11.0.4.5" version, so I downloaded it and installed and then restarted. Interesting thing happen again, I saw the Cyberpunk loading screen again. And I was stuck at the loading screen again. In order to pass the loading screen I have to clean "System setting/cache". Then I can access the device again and not seeing any Cyberpunk logo.
So, when I thought everything is finally working now, it wasn't. I went to the "System Update" again and try to see if there is any update, but I saw the same "11.0.4.5" version which I just updated. It seems the update is not working, so I went to "About phone" and confirmed that it was NOT updated. Again I tried several times, not working at all. It just like something under the hood keep resetting the device to the factory status.
Until anyone found a solution for this issue, I think I would have to keep using the version inside the unbrick tool I mentioned above. It will be great if OnePlus release an official Cyberpunk version of Oxygen OS later. Let's wait.
FullOfHell said:
The same as you would any other way with magisk. I don't have any modules or root or bootloader unlocked.
Click to expand...
Click to collapse
@FullOfHell :
So I just need to flash gapps with magisk, Uninstall Chinese applications if i don't need it and all are ok ?
OTA update and all things ??
Or it's better to flash oxygen os, and wait for magisk theme installation ?

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

Categories

Resources