[ROM][I9190/I9192/I9195/L520/R890][Unofficial][10.0.0] LineageOS 17.1 for S4 Mini

arco68

Recognized Developer
Oct 11, 2010
2,820
24,313
203
New builds with March security fixes available.

The issues with bluetooth audio seems to have been caused by the mpdecision daemon. This daemon is responsible for hotplugging the cores, which means that when there is no load on the device, it will take all cores offline apart from one, in order to save battery. When this hotplugging takes place, it seems to cause lags in the system, which in turn causes glitches with bluetooth. In this build I've disabled this daemon, so no hotplugging will take place. Since there's only 2 cores, it should hopefully not impact the battery usage too much. Also the device should perform a bit smoother since both cores are immediately available.
 

Thoadi

Senior Member
Jan 8, 2017
159
32
43
Zurich
Did you try the onscreen keyboard with override force-dark enabled (developer options)
don't find this dev. option. I use Gboard.

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
 
Last edited:

MrGoodtunes

Senior Member
Nov 8, 2007
375
139
43
South Florida
Restored backup will not boot

New builds with March security fixes available ...
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?
 
Last edited:

kurtn

Senior Member
Jan 28, 2017
3,609
1,483
233
Small town in Bavaria
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?
In my definition a bootloop is boot process that repeatedly stops before it finishes, then starts again from Samsung logo.
What I see is the lineageOS boot animation for 15 minutes now.
 
  • Like
Reactions: MrGoodtunes

arco68

Recognized Developer
Oct 11, 2010
2,820
24,313
203
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.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.
 

kurtn

Senior Member
Jan 28, 2017
3,609
1,483
233
Small town in Bavaria
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.
Confirmed. Backup of 16.0 can be restored with twrp serranoltexx from OP.
 

carlos974

Senior Member
May 18, 2016
607
686
113
Saint-Denis
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.
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
 

Attachments

Last edited:

MrGoodtunes

Senior Member
Nov 8, 2007
375
139
43
South Florida
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
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.
 

carlos974

Senior Member
May 18, 2016
607
686
113
Saint-Denis
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.
OK, thanks !

For our TWRP the dev has to adapt it from Oreo because for the Mega the TWRP version stops at version 2.8.7.0 at TeamWin-TWRP

Regarding the roms for Mega the dev built lineageos 17.1 and crDroid 10.0 :good: