I like the dark theme... maybe I don't need substratum anymore. Everything works well... thanks.
Did you try the onscreen keyboard with override force-dark enabled (developer options)I like the dark theme... maybe I don't need substratum anymore. Everything works well... thanks.
don't find this dev. option. I use Gboard.Did you try the onscreen keyboard with override force-dark enabled (developer options)
Oof! Try flashing this in TWRP.BT not working in Car, for calls and music. Try latest built... hope you could fix it Arco. I try to sen Log later.
Edit: After reboot music play fine on Car BT, but call faild...
Log file
Try the Zip, reboot, flashed zip again, no success to make s call. No one hear each other. Permission issue? Make or end a call works btw.Oof! Try flashing this in TWRP.
http://www.mediafire.com/file/b51tszt2oio6d6d/audio_bluetooth_fixup.zip/file
I'm not seeing any unusual long install times here.Los 17 "installer" takes a very long time to install user applications and this is annoying...
My bad. The file fails to copy due to me using wrong path. Try re-downloading the updated fix.
Many thanks, improved performance. But I'm still getting endless bootloops after restoring a TWRP backup image.New builds with March security fixes available ...
In my definition a bootloop is boot process that repeatedly stops before it finishes, then starts again from Samsung logo.Many thanks, improved performance. But I'm still getting endless bootloops after restoring a TWRP backup image.
I've tried clean flash (wipe dalvik, cache, data, system) and I've tried dirty. I've tried with and without gapps. I've tried with TWRP v3.3.1-0, all 3 steps (install, backup, restore). And I've tried with @arco68 provided TWRP v3.2.3-0 for all 3 steps. Have been getting same bootloops result since the first 17.1 through and including 17.1-20200309.
Has somebody been able to boot a restored TWRP backup? Am I missing something that is required?
If restoring 16.0 backups is working fine, then most likely TWRP don't support system as root which is used in 17.1Has somebody been able to boot a restored TWRP backup? Am I missing something that is required?
Confirmed. Backup of 16.0 can be restored with twrp serranoltexx from OP.If restoring 16.0 backups is working fine, then most likely TWRP don't support system as root which is used in 17.1
Support for it has to be implemented in TWRP, but I don't know what the status for that is. As I understand the developer has stopped working on it for the moment.
Thanks a lot, works well...My bad. The file fails to copy due to me using wrong path. Try re-downloading the updated fix.
http://www.mediafire.com/file/xq0ly9hddr8ux0l/audio_bluetooth_fixup.zip/file
FYI!If restoring 16.0 backups is working fine, then most likely TWRP don't support system as root which is used in 17.1
Support for it has to be implemented in TWRP, but I don't know what the status for that is. As I understand the developer has stopped working on it for the moment.
Thanks, tried TWRP v3.2.1-1 for serranoltexx; got the same endless LOS boot animation. The only joy is turning phone upside-down (arc becomes a smile, with tongue licking lips). If that version of TWRP will restore an Android 10 backup that boots on Mega, then there must be something very special about the ROMs structure and/or Mega's TWRP version.FYI!
On Galaxy Mega (meliusltexx), same platform as S4 mini (msm8930), the restoration of Android 10 works very well. Since Oreo Silesh has not changed TWRP, its version is 3.2.1.1
OK, thanks !Thanks, tried TWRP v3.2.1-1 for serranoltexx; got the same endless LOS boot animation. The only joy is turning phone upside-down (arc becomes a smile, with tongue licking lips). If that version of TWRP will restore an Android 10 backup that boots on Mega, then there must be something very special about the ROMs structure and/or Mega's TWRP version.