I don't think getprop works, I am sure I'm on 12.5.6 but that says 12.5.4 also.As said previously in this thread. I still have audio issues mostly with Spotify and Youtube. Spotify cuts out every few seconds and starts up again and Youtube is very laggy on video load.
I saw the need to update firmware, but I checked with adb shell getprop I already have one of the versions suggested by the developer. 12.5.4.0 Global As you can see here.
View attachment 5436591
I also restarted multiple times and cleared the cache yet the problem persists. Can someone help? This is unusable.
Just read back a few pages on this thread.I just flashed the October 9 update, and now videos randomly pauses in all apps, my internet connection is fine. Is there a fix for this one?
Is there a way to downgrade to the September update?
The adb command merely reads the build.prop file. The contents of which is entirely under the control of the ROM developer and doesn't actually reflect what the firmware version is. A better value to check is the baseband version, as this often gets updated with a firmware flash.EDIT: The update fixed it. Someone with more knowledge should figure out why getprops says the wrong version.
I have been considering the Pixel Experience ROM. Does it include the Dolby Atmos stuff? I really miss the compander in that bit of software.I was on latest MIUI before I tried the rom (EU 12.5.6). I also had the audio and video issues. Also it seemed very sluggish in general.
Now I'm using pixel experience plus and have no issues. It's very fast and no sound problems.y
It does not include Dolby as far as I know.I have been considering the Pixel Experience ROM. Does it include the Dolby Atmos stuff? I really miss the compander in that bit of software.
This is an issue on all AOSP roms as of now. Afaik only helluva has over 600 nits, but haptics don't improve either. MIUI has the best haptics if you care about that...Haptic Feedback doesn't feel as clear and brightness is capped at 600 nits.
You can do this an easier way. Just use the Magisk installable zip file you can find in the internet. To do this, use TWRP (link to detailed instruction is in the first post) via "fastboot boot <twrp img file>", then simply install the zip. I did it this way and... it just works.I'm a bit confused with this one. I need to install magisk, and if i'm not mistaken the F3 has an A/B partition system so
to install the patched magisk img i should do:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
But when i do that, the rom gets stuck on the loading arrow logo.
Should i just patch it with:
fastboot flash boot boot.img ?
Edit: Actually no, that gives the same result, stuck on the loading arrow logo.
Can anyone explain how to install the patched magisk file on this one ?
You can do this an easier way. Just use the Magisk installable zip file you can find in the internet. To do this, use TWRP (link to detailed instruction is in the first post) via "fastboot boot <twrp img file>", then simply install the zip. I did it this way and... it just works.
fastboot flash boot_ab boot_alioth.img
fastboot flash vendor_boot_ab vendor_boot_alioth.img
fastboot reboot recovery
adb sideload name.zip
adb sideload name.zip