[ROM][OFFICIAL][gta4xl/gta4xlwifi][11] LineageOS 18.1 for Galaxy Tab S6 Lite

Search This thread

Linux4

Recognized Developer
1607247455067.png


LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Instructions:
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.

Downloads:

Reporting Bugs
  • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
  • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
  • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
  • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:

Did you--
wipe:
restore with titanium backup:
reboot after having the issue:

Are you using--
a task killer:
a non-stock kernel:
other modifications:

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:


Support
Telegram group

Contributors
Linux4, haggertk
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl
 
Last edited:

flitzjoy

Senior Member
Sep 17, 2008
330
44
São Paulo
the golden question:
  • its possible to came to official build from unofficial without formatting data?
  • if not. do you plan to continue making builds for the unofficial branch?
 
  • Like
Reactions: SGH-i200

Linux4

Recognized Developer
Whats the difference between official and unofficial then? Thanks for your effort btw :)
Unofficial might less stable because I'll release builds with new stuff that isn't yet merged Into official (I thought that would be a good idea for testing stuff)
Still won't release something completely untested for unofficial tho
 
  • Like
Reactions: sieghartRM

berlinerbaer

Member
Feb 27, 2021
6
3
wanted to upgrade how it's described on the lineageOS wiki, however I got an error message, followed by being stuck at a "entering fastboot..."-screen.
I will try install stock Rom and repeat install from there.

Edit:
Restarting the process with stock rom helped.
 
Last edited:

julesism

Senior Member
Aug 31, 2008
287
33
North Little Rock AR
I'm trying the get the first offical nightly build installed and it gets stuck on the blue lineage os loading arch. Anyone else get it to boot to setup? I'm using lineage recovery now. I was going to go back to unofficial and twrp but twrp builds were removed from the twrp thread.
 
I'm trying the get the first offical nightly build installed and it gets stuck on the blue lineage os loading arch. Anyone else get it to boot to setup? I'm using lineage recovery now. I was going to go back to unofficial and twrp but twrp builds were removed from the twrp thread.
Installed yesterday without any problems. I was running the unofficial los prior. Make sure to use the matching los recovery.
 

Bracher

Senior Member
Sep 18, 2009
220
50
Hello,
as the developpement of 17.1 has stopped I'll try in the next days with 18.1. But I have a question:
after wipe in Recovery can I update the LineageOS Recovery than reboot into Recovery and flash the LOS18.1 via LOS Recovery from my external SD-Card and after that Magisk? That's the procedure I did in the past with TRWP but as I never worked with LOS Recovery before (as well as a decrypted internal SD-Card) I wanted first be sure about the procedure.
 

Linux4

Recognized Developer
Hello,
as the developpement of 17.1 has stopped I'll try in the next days with 18.1. But I have a question:
after wipe in Recovery can I update the LineageOS Recovery than reboot into Recovery and flash the LOS18.1 via LOS Recovery from my external SD-Card and after that Magisk? That's the procedure I did in the past with TRWP but as I never worked with LOS Recovery before (as well as a decrypted internal SD-Card) I wanted first be sure about the procedure.
Sure, you could also sideload lineage and magisk but external sdcard should work too.

Is it safe to dirty flash official 18.1 over the unofficial?
Thanks so much for all your hard work on this!

I already answered this, see this post
 
  • Like
Reactions: sieghartRM

Bracher

Senior Member
Sep 18, 2009
220
50
Sorry I have another urgent question how can I update LOS Recovery (from 17.1 to 18.1)? In TRWP you can change into "install an image" than the recoveries are recognised in LOS Recovery there is no such possibililty you can only flash .zip files no other files are recognised.
Should I transform the image file into a zip file or how do you do that? Sorry I'm only used to TRWP
 

Linux4

Recognized Developer
Sorry I have another urgent question how can I update LOS Recovery (from 17.1 to 18.1)? In TRWP you can change into "install an image" than the recoveries are recognised in LOS Recovery there is no such possibililty you can only flash .zip files no other files are recognised.
Should I transform the image file into a zip file or how do you do that? Sorry I'm only used to TRWP

If you are still on 17.1 recovery you'll have to flash 18.1 recovery with Heimdall/Odin like you did when installing lineage for the first time.
Starting with 18.1 you are also able to flash it via fastbootd in recovery.
 
  • Like
Reactions: sieghartRM

Bracher

Senior Member
Sep 18, 2009
220
50
Thank you very much for your advice! But after my successfull update to official 18.1 including LOS Recovery I have a new problem, in devellopper modus is no longer the possibilitiy for enlarged reboot, so I can't reboot in recovery. Is this intended and if so why and is there a possibility to circumvent that? All in all I'm not very happy with 18.1 so I'm thinking going back to 17.1 which is unfortunately no longer maintained.
 

Bracher

Senior Member
Sep 18, 2009
220
50
By the way is there a possibility to support your work - at least with some spending? I found no possibility yet
 

Linux4

Recognized Developer
Thank you very much for your advice! But after my successfull update to official 18.1 including LOS Recovery I have a new problem, in devellopper modus is no longer the possibilitiy for enlarged reboot, so I can't reboot in recovery. Is this intended and if so why and is there a possibility to circumvent that? All in all I'm not very happy with 18.1 so I'm thinking going back to 17.1 which is unfortunately no longer maintained.

Advanced reboot setting was moved to System -> Gestures -> Power Menu -> Advanced Restart
Do you have any other problem with 18.1?

By the way is there a possibility to support your work - at least with some spending? I found no possibility yet

There's a paypal link in my profile if that's what you mean, thanks for considering to support me!
 

Bracher

Senior Member
Sep 18, 2009
220
50
Thank you very much - for both information, as I said I suppose I'm getting old (72 year old grandmother...). as for the other problem I'm stuck with Nanodroid it's not possible to flash via Magisk, but that's not a ROM problem it's linked to Nanodroid. Your ROM is fine thanks a lot!!!
 
  • Like
Reactions: usb47

Top Liked Posts

  • There are no posts matching your filters.
  • 22
    1607247455067.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions:
    Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.

    Downloads:

    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:


    Support
    Telegram group

    Contributors
    Linux4, haggertk
    Source Code: https://github.com/LineageOS
    Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl
    5
    Should this tablet be supported by Lineage for some time or is it impossible to know?

    Generally, when it comes to custom ROMs, it's impossible to say just how long a device will be supported. Sometimes, the device maintainer moves on and no one is available to take up the slack; other times, official support from the device developer (Samsung, in this case) stops, and though future Android updates can often be made to work with the last available code, sometimes it reaches a point where nothing further can be done. Can't speak to how long Linux4 will remain "on the job," but it doesn't look like he's going anywhere any time soon. Also, the Tab S6 Lite is supposed to officially get Android 12 some time next year, so device support should continue for a good while longer (in fact, an unofficial A12-based Lineage 19.0 is currently available, and will probably move to "official" status at some point when Lineage 19.0 builds become officially available [at the moment, 19.0 is still in the "bring-up" stage, with the software evolving day by day as its features are slowly being brought up]).
    4
    This was said multiple times already, this is caused by samsung having released two new harware revisions with new light sensor and new audio lately.
    Support for these is already fixed and just waiting for some review/testing to be merged into official 18.1, for now you could use unofficial 19.0 tho which already contains everything needed for your hardware revision.

    @Mr.Yindo This applies to you as well.
    Support for these new hardware revisions will be included in the next build on Wednesday.