[GSI][10] LineageOS 17.x GSI (all archs)

Should I build *vS variants (with PHH-SU)?

  • Build *vS (SU), replacing *vN (no SU)

    Votes: 6 33.3%
  • Build *vS alongside *vN

    Votes: 8 44.4%
  • Keep things as is

    Votes: 3 16.7%
  • Don't care

    Votes: 1 5.6%

  • Total voters
    18
  • Poll closed .
Search This thread

gnomiik

Member
Jun 7, 2021
43
3
Can I install this LOS 17 gsi which is based on android 10 on a newer phone like Xperia 10 iii which the initial stock rom is based on android 11. Or do i need to install LOS 18 which is based on android 11?
 

xoisnic

Member
Jan 14, 2021
11
0
640px-Lineage_OS_Logo.png


Background:
This is a natural continuation/extension of the LineageOS 16.0 GSIs I've been making since March 2019.
If you clicked in here, I bet you know what LineageOS is already, but just to fill the blank:


Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.

Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
  • Modifications needed to make it build/boot/feature-complete, see below
  • Revived navbar layout tuning via sysui_nav_bar tunable
  • Disabled "vendor mismatch" warning on boot
  • Signature spoofing support from MicroG (preliminary patch for Android 10)
  • Default stretch-to-fullscreen (force apps to render in 18:9)

Extra tip:
If you have a relatively low-end device and experience UI stutters, try this simple build.prop trick (technically a debug property, so use at your own risk). Thanks @SnapTheRipper for bringing it up!

Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out the scripts/patches, where most things should be self-explanatory: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.

Donate?
https://paypal.me/AndyCGYan
i use lineage os16 microg on my redmi go and all works ok.i install your rom 17 gsi. all works ok but viber cant get activation code. is like account dont exist. by going bac to lineageos 16 microg, i can activate viber. what is diferent between the 2 vertions??
 

Rgodoy8080

Member
Jan 6, 2021
42
4
hello to all could you please because transmit wireless screen does not work in the rooms gsi
because I tried several and none of them managed to connect or link with my tv.
while the room stock Oreo 8.1 that comes by default on my phone does it work?
thanks
 

Top Liked Posts

  • There are no posts matching your filters.
  • 102
    640px-Lineage_OS_Logo.png


    Background:
    This is a natural continuation/extension of the LineageOS 16.0 GSIs I've been making since March 2019.
    If you clicked in here, I bet you know what LineageOS is already, but just to fill the blank:
    LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
    All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.

    Disclaimer:
    This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
    No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
    No guarantees that everything would work. This is a GSI, bugs are bound to happen.

    Download:
    https://sourceforge.net/projects/andyyan-gsi/files/
    Compressed as .xz archives - extract first.
    Vanilla except for these changes:
    • Modifications needed to make it build/boot/feature-complete, see below
    • Revived navbar layout tuning via sysui_nav_bar tunable
    • Disabled "vendor mismatch" warning on boot
    • Signature spoofing support from MicroG (preliminary patch for Android 10)
    • Default stretch-to-fullscreen (force apps to render in 18:9)

    Extra tip:
    If you have a relatively low-end device and experience UI stutters, try this simple build.prop trick (technically a debug property, so use at your own risk). Thanks @SnapTheRipper for bringing it up!

    Stuff on GitHub (builders-only):
    Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out the scripts/patches, where most things should be self-explanatory: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.

    Donate?
    https://paypal.me/AndyCGYan
    32
    Reserved

    Couple of things to note:
    • Even on a device that runs Pie GSIs nicely, it's still possible to get broken media, camera, RIL or even flat-out no-boot on Android 10 ones. You are strongly advised to try PHH's AOSP first and identify/report issues there, before moving onto other GSIs that are based on his work. Please report bugs here only if it's specific to this GSI.
    • LineageOS 17.x has lost some features in the process of transitioning to Android 10, e.g. Privacy Guard and built-in SU.
    • If using Magisk on an A-only device, a modified Magisk is required.
    • exfat SD cards still don't seem to work. Any help related to this would be appreciated.
    • The feature "Re-enabled lockscreen shortcuts by default" has been dropped - not that it can't be done, but Google again made ugly changes to the lockscreen, and with the shortcuts turned on it looks asymmetric and adds to the ugliness. Lockscreen shortcuts themselves might still come back with a future upstream update, just like how it did in 16.0.
    • In the 16.0 GSIs I've included changes that allow for automatic front camera actions for Xiaomi Redmi K20 Pro, but these have to be reworked for Android 10, and I'm not interested in doing so (in fact I prefer manual controls). Consider these changes abandoned for now.
    18
    Updated all variants with July security patches and in sync with PHH v221. [Insert obligatory backup-and-test warning here]

    It's been a quiet month on both AOSP and PHH fronts...
    17
    Updated all variants with February security patches and in sync with PHH v212. [Insert obligatory backup-and-test warning here]

    All good and healthy here despite the coronavirus situation (naturally, I just stay indoors all day). Thanks for your concerns :)
    16
    Updated all variants in sync with PHH v208. [Insert obligatory backup-and-test warning here]
    Skipped r18 (December patch) for aforementioned instability.
    No more updates for the rest of 2019! (lol)

    BTW, here's a tip straight from PHH's TG channel, for those who are having trouble with GAPPS setup wizard:
    In ADB:
    adb shell settings put secure user_setup_complete 1
    adb shell settings put global device_provisioned 1
    This should skip the wizard entirely while also setting the proper flags.