• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][UNOFFICIAL][11][SM-T820][SM-T825][BETA][20211116] LineageOS 18.1 for Galaxy Tab S3

Search This thread

Siddhartha Valmont

New member
Jun 29, 2010
4
0
Thank you very much Awesomatic for putting together this ROM and helping keep our S3s relevant and safe :)

I ran into a weird problem reinstalling (or trying to) Catan Universe: the download of 247MB progress fine and when it is time to move to the install phase it resets to uninstall and sends a notification of a problem (no tech details). I know this app works on 11 as I was able to install it on my Galaxy S5 without problem (using opengapps pico on both).

Any idea of where the Playstore app stores its tech logs? Or if there is a way to trigger an install that would provide more information about the error (as there is plenty of space left and all the other apps reinstalled without problem)?

Thanks !
 

realIK1724

New member
Oct 28, 2021
3
0
Can I install it on my SM-T827V? I know it says 820/825, but what will hapen if I install it on 827V?
 

eddie-77

Member
Aug 25, 2021
7
2
Hello everyone!
First of all, many thanks to Awesomatic for the wonderful firmware, my old tablet just came back to life! I installed the recovery recommended by the author and flashed only the Lineage 18.1 file itself. I didn't flash anything else. The tablet works fast as a bullet. I just don't understand where I should put the cache from downloaded applications now? The "obb" folder is now missing in the "Android" folder. Am I the only one with this problem?
Thanks!
 
.... where I should put the cache from downloaded applications now? The "obb" folder is now missing in the "Android" folder. Am I the only one with this Problem?...
Afaik you don't have to worry as apps care for that by themselves.
My T825 doesn't have that folder either but every app works as it's supposed to.
 

eddie-77

Member
Aug 25, 2021
7
2
Afaik you don't have to worry as apps care for that by themselves.
My T825 doesn't have that folder either but every app works as it's supposed to.
This is reasonable for an application that does not have a cache. And then what should I do with installing an application that has a cache? I don't have gapps installed. I downloaded the .apk and the cache attached to it. Where should I move its cache?
 
This is reasonable for an application that does not have a cache. And then what should I do with installing an application that has a cache? I don't have gapps installed. I downloaded the .apk and the cache attached to it. Where should I move its cache?
I use apps from f-droid as well which do have a cache but these were one file apks and they manage their cache themselves.

Gotta admit I've never had an app which consists of an apk and an additional cache file which has to be installad/saved separatly.
Which apk do you mean btw.
 

F1Fanatic27

Senior Member
Mar 23, 2013
157
64
King's Lynn
Games. For example: Syberia, Machinarium and any other large-size games.
Is this still regarding obb files? Presumably you can just create the necessary folders yourself if they don't exist already. First the 'obb' folder obviously, then inside that folder, another folder named after the package name of the app (normally com.something.something), then the obb file goes in there.
 

eddie-77

Member
Aug 25, 2021
7
2
Is this still regarding obb files? Presumably you can just create the necessary folders yourself if they don't exist already. First the 'obb' folder obviously, then inside that folder, another folder named after the package name of the app (normally com.something.something), then the obb file goes in there.
Thank you for your answer. I'm sorry, I probably don't understand some simple things. Before android 11, I could install a game with a cache. I downloaded the apk itself and separately downloaded the cache to this file in the zip archive. After unpacking the zip, I just put the cache folder on the path internal memory/android/obb. On android 11, Google has closed access to this obb folder. Now, following the path internal memory/android, I see only the folder "data" and "media". Access to the "data" folder can be obtained only in a third-party file manager and only for viewing the contents. There is no application cache. I still don't understand how to properly install a game that has a cache as a separate file. I'm sorry if I'm asking stupid questions.
 

F1Fanatic27

Senior Member
Mar 23, 2013
157
64
King's Lynn
Thank you for your answer. I'm sorry, I probably don't understand some simple things. Before android 11, I could install a game with a cache. I downloaded the apk itself and separately downloaded the cache to this file in the zip archive. After unpacking the zip, I just put the cache folder on the path internal memory/android/obb. On android 11, Google has closed access to this obb folder. Now, following the path internal memory/android, I see only the folder "data" and "media". Access to the "data" folder can be obtained only in a third-party file manager and only for viewing the contents. There is no application cache. I still don't understand how to properly install a game that has a cache as a separate file. I'm sorry if I'm asking stupid questions.
Ah I was not actually aware of the Android 11 changes until now.
I've looked into it though and I got a solution. Go to the root of the system, then the path /data/media/0/Android, then you should be able to see the obb folder and modify things inside as necessary.
You'll need a file manager with root permissions for this to work. I tried MiXplorer and Total Commander and they both seemed to work.
 
  • Like
Reactions: eddie-77

eddie-77

Member
Aug 25, 2021
7
2
Ah I was not actually aware of the Android 11 changes until now.
I've looked into it though and I got a solution. Go to the root of the system, then the path /data/media/0/Android, then you should be able to see the obb folder and modify things inside as necessary.
You'll need a file manager with root permissions for this to work. I tried MiXplorer and Total Commander and they both seemed to work.
Thank you for your desire to help! My obb folder is visible only on the sd card. It is not in the internal memory. If I want to create it, the file manager writes that there is already such a folder. If I want to write something to the obb folder on the sd card, then I see a message that recording is prohibited. I've tried installing recommended gapps and I can't install large apps from the play market. I just get an error that the application is not installed. This applies to applications with a cache. Small apps are being installed. It feels like I'm doing something wrong. Can you try installing a Pubg game from the play market, for example? I'm wondering if you can do it. I don't have this game installed. I tried the installation using different file managers: solid, mixplorer, total commander, x-plore, etc.
 

F1Fanatic27

Senior Member
Mar 23, 2013
157
64
King's Lynn
Thank you for your desire to help! My obb folder is visible only on the sd card. It is not in the internal memory. If I want to create it, the file manager writes that there is already such a folder. If I want to write something to the obb folder on the sd card, then I see a message that recording is prohibited. I've tried installing recommended gapps and I can't install large apps from the play market. I just get an error that the application is not installed. This applies to applications with a cache. Small apps are being installed. It feels like I'm doing something wrong. Can you try installing a Pubg game from the play market, for example? I'm wondering if you can do it. I don't have this game installed. I tried the installation using different file managers: solid, mixplorer, total commander, x-plore, etc.
Well, I did try to transfer a few random files and folders and they worked fine.

Just to be clear, you want to access the obb folder through the root path that I specified above (/data/media/0/Android), not the standard internal storage location. Then the obb folder will be visible.

So for example. in MiXplorer, open the sidebar on the left (will be visible by default if you're using the tablet in landscape), press 'Root', grant root permissions if it asks, then go the path above.
Or in Total Commander, on the homepage press 'File system root', then go to the path.
 

eddie-77

Member
Aug 25, 2021
7
2
Well, I did try to transfer a few random files and folders and they worked fine.

Just to be clear, you want to access the obb folder through the root path that I specified above (/data/media/0/Android), not the standard internal storage location. Then the obb folder will be visible.

So for example. in MiXplorer, open the sidebar on the left (will be visible by default if you're using the tablet in landscape), press 'Root', grant root permissions if it asks, then go the path above.
Or in Total Commander, on the homepage press 'File system root', then go to the path.
I devoted last night to experiments))). You're right, I was able to access some folders, including the obb folder. This did not solve my problem with installing games with a cache, but this is already a problem for android 11. Google has changed the destination folders for application files and so far I do not really understand which files should be put in which folders. I'm trying to at least install games from playmarket right now. Applications larger than 100mb are not installed. That is, even the play market itself cannot install applications from itself))).
 
  • Like
Reactions: Siddhartha Valmont
D

Deleted member 11883955

Guest
Hello, I'm new to the forum and hope that I can explain my question to you in an understandable way.

You use quite a few insider abbreviations here :)

First a big THANK YOU to @Awesometic. Because of your ROMs, my T820 runs better and faster than on the first day !!

For 2 weeks I have been dealing with the Custom Roms, because the T820 can no longer be used with the Stadard rom.

Currently I only have one problem with the gaps.
Under Settings -> Info -> Play Protect Certification stands "Device is not certified".
Unfortunately, because it is not certified, I can no longer use various apps my daughter has bought :(
I have already tried the following steps to solve the problem, unfortunately without success.

  1. Installation as described in the section "how to install" --> problem still exists
  2. Register "Device ID - GSF ID" at Google.
    I followed the Instructions from this articles: Google now blocks GApps on uncertified devices, but lets custom ROM users be whitelisted, Google is starting to block GApps on 'uncertified' devices, but you can register an exemption for ROMs --> Problem still exists
  3. Install Magisk v.23 with TWRP, tried the steps from How to Fix SafetyNet 'CTS Profile Mismatch' Errors and Question Few noob questions - Magisk Hide, Play Store Certification and Netflix Widevine
    In Magisk -> SafetyNet Check
    - basicIntegrity is passed
    - ctsProfile not passed
    - evalType basic

Do any of you use the Gapps and have the device been certified?
If so, it would be great if you could explain the steps to me how you did it.

Regards Tranceman84
 
D

Deleted member 11883955

Guest
Doesn't anyone have any advice for me?


If someone knows their job very well, I am of course also willing to pay for the help or to donate something somewhere.

I would just find it a shame to have to replace such a well-running device with a new one because of such a problem.

You can also write me a pm.

Regards Transman84
 

mi_guel

Senior Member
Doesn't anyone have any advice for me?


If someone knows their job very well, I am of course also willing to pay for the help or to donate something somewhere.

I would just find it a shame to have to replace such a well-running device with a new one because of such a problem.

You can also write me a pm.

Regards Transman84
Make sure you have magisk hide turned on and I has to use magisk hide props config to change the fingerprint
 
D

Deleted member 11883955

Guest
Make sure you have magisk hide turned on and I has to use magisk hide props config to change the fingerprint
Hi @mi_guel, thank you for your replay.
I use magisk v. 23.0.
MagiskHide is activated for play store and play services with no success.
Then i installed magisk hide props according to the following instructions from How to Pass Magisk SafetyNet on Rooted Android 11.
In the magisk hide props configuration there is unfortunately no model SM-T820, only the model SM-T825 is available.
That's why I chose SM-T825 there.
Unfortunately that didn't work either.
The SafetyNet Check now contains the following:
basicIntegrity: passed
ctsProfile: not passed
evalType: basic

Regards tranceman84
 

mi_guel

Senior Member
Hi @mi_guel, thank you for your replay.
I use magisk v. 23.0.
MagiskHide is activated for play store and play services with no success.
Then i installed magisk hide props according to the following instructions from How to Pass Magisk SafetyNet on Rooted Android 11.
In the magisk hide props configuration there is unfortunately no model SM-T820, only the model SM-T825 is available.
That's why I chose SM-T825 there.
Unfortunately that didn't work either.
The SafetyNet Check now contains the following:
basicIntegrity: passed
ctsProfile: not passed
evalType: basic

Regards tranceman84
Try to erase play services and google play data, it doesn't matter too much if you chance the device fingerprint for another model
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    Long time no see. :)

    I uploaded the new version that contains the November security patch and fixed arrow keys working on the keyboard inputs.
    Yeah, sorry for it isn't a big update, I know there're lots of bugs remaining. 😅

    Currently I have been investigating upgrading our kernel as I said before.

    I did start the Android kernel studying to know what CAF based kernel or AOSP based kernel means, and how the other people merge the latest tags from the official repositories to the vendor-providing kernel base.
    And now I think I'm managed to know the very small piece of that Android kernel world.

    First, I found that there is no problem with using the Bluetooth keyboard on the stock kernel for LOS, which hasn't any patch including the upstream Linux patches and/or any tunes.
    Yeah, this is interesting, it can be small evidence that the current kernel is somewhat broken at least for the Bluetooth.

    My first plan was to migrate Samsung codes to the LineageOS MSM8996 kernel. But after a few weeks, I realized that it isn't for humans. There are so many flags and tweaks they put in. Even some codes are not marked whether this code is from Samsung.

    So I changed my plan, to get CAF tags onto the top of the CTD1 kernel that is the latest kernel base of the T825 model. Fortunately, I could merge some modern CAF tags successfully. But in that progress the camera got broken. :unsure:

    Then, I tried to merge the AOSP tags for getting the proper upstream Android/Linux patches and security patches. I could merge until early 2020, that is also containing 3.18.140 upstream Linux patches. But I couldn't merge the latest patches like the one just published last month. It makes the tablet not boot.

    I think it is quite hard work on our tablet because Samsung puts various un-listed patches onto the top of the 3.18.115 kernel but they didn't apply the upstream Linux patches. So, for example, when I merge the 3.18.116 tag to the current 3.18.115 kernel, I couldn't accept all the incoming changes because some files in the current kernel base are much more modern files. o_O This makes me get frustrated.

    But it doesn't mean it is impossible. Some people out there are doing this job now so there will be something more I don't know yet about the Android kernel development. If someone has experience or knowledge of upgrading vendor kernel, please join our Telegram channel and let's discuss that.
    1
    Thank you for your answer. I'm sorry, I probably don't understand some simple things. Before android 11, I could install a game with a cache. I downloaded the apk itself and separately downloaded the cache to this file in the zip archive. After unpacking the zip, I just put the cache folder on the path internal memory/android/obb. On android 11, Google has closed access to this obb folder. Now, following the path internal memory/android, I see only the folder "data" and "media". Access to the "data" folder can be obtained only in a third-party file manager and only for viewing the contents. There is no application cache. I still don't understand how to properly install a game that has a cache as a separate file. I'm sorry if I'm asking stupid questions.
    Ah I was not actually aware of the Android 11 changes until now.
    I've looked into it though and I got a solution. Go to the root of the system, then the path /data/media/0/Android, then you should be able to see the obb folder and modify things inside as necessary.
    You'll need a file manager with root permissions for this to work. I tried MiXplorer and Total Commander and they both seemed to work.
    1
    Well, I did try to transfer a few random files and folders and they worked fine.

    Just to be clear, you want to access the obb folder through the root path that I specified above (/data/media/0/Android), not the standard internal storage location. Then the obb folder will be visible.

    So for example. in MiXplorer, open the sidebar on the left (will be visible by default if you're using the tablet in landscape), press 'Root', grant root permissions if it asks, then go the path above.
    Or in Total Commander, on the homepage press 'File system root', then go to the path.
    I devoted last night to experiments))). You're right, I was able to access some folders, including the obb folder. This did not solve my problem with installing games with a cache, but this is already a problem for android 11. Google has changed the destination folders for application files and so far I do not really understand which files should be put in which folders. I'm trying to at least install games from playmarket right now. Applications larger than 100mb are not installed. That is, even the play market itself cannot install applications from itself))).
  • 29
    Code:
    /*
    * Your warranty will be VOID after installing a custom ROM.
    *
    * Get notified yourself that I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed.
    * Please do some research if you have any concerns about features included in this ROM
    * before flashing it!
    * YOU are choosing to make these modifications,
    * and if you point the finger at me for messing up your device,
    * I will laugh at you.
    */


    # LineageOS

    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.


    # What's working
    • Display/Touchscreen
      • LiveDisplay
    • Audio playback
      • Quad speakers
      • Headphone/Headset
      • Bluetooth audio
    • Video playback
      • HDR
    • Camera
    • Microphone
    • Sensors
    • Fingerprint sensor
    • GPS
    • LTE (SM-T825)
    • WiFi
    • Bluetooth
    • DRM
      • Widevine L1
    • USB ADB/MTP/OTG
    • Samsung Doze
    • S-Pen
      • Palm rejection
    • SD Card
    • Power-off mode charging

    # What's not working
    • Fast charging
    • WiFi display/hotspot
    • SELinux permissive
    • Hardware encryption
    • Lots of things I couldn't find
    • Please see the "Known issues" part of this post

    # Downloads

    ## LineageOS 18.1

    ## Google Apps

    ## TWRP Recovery

    # How to install
    1. Unlock the bootloader.
    2. Download TWRP and flash the recovery image via Odin.
    3. Download LineageOS 18.1 for Galaxy Tab S3.
      • Be aware of the board name.
    4. Download GAPPS for Android 11and the others you want to flash.
      • Only OpenGApps is tested. (open_gapps-arm64-11.0-pico-20210130-TEST.zip)
    5. Enter TWRP recovery.
      • The first boot to TWRP might be very slow because of the unmatched file systems.
    6. Format the whole system, data, cache partitions using the format menu.
      • You will type `yes` to do that.
    7. Flash the images.
      • If you're going to install GApps or something, you have to install the LineageOS first.
    8. Reboot the system.
    9. Done.

    # Known issues
    • Settings app crashes for the first run
    • SD card may not be recognized for the file system, excepts VFAT (FAT32)
    • OTG drives may show nothing even if it mounted
    • The side button on S-Pen is working but you must use the proper application that can handle the button event
    • Enabling AudioFX may cause a short popping sound when playing a sound
    • Bluetooth inputs are not working, such as a Bluetooth keyboard
    • Fast-charging won't work properly, it sometimes works but most of the time it won't
    • Turning on the flashlight via the quick panel doesn't work after using a camera app
    • Using a camera app may cause reducing the UI performance on a launcher app
    • In a non-primary user, the tablet will not work properly including installing a new app or using a camera app
    • Nightlight mode will not switch automatically with Sunrise/Sunset
    • The tablet rarely reboots with a GMS related error
    • Unlocking the lock screen can make tablets not usable sometimes
    • CTS profile will not be fixed
    • Thank all of you for the feedback

    # Sources

    # Telegram Groups
    • If you are interested in developing this potential machine, please tell me through PM then I will send you the invitation link.
    • If you need a general discussion channel for this potential machine or want to share the news of its Android projects from anyone to everyone, you can join our discussion group chat.

    # Buy me a coffee

    # Credits / Special thanks to
    • Android Open Source Project
    • LineageOS Team
    • @Valera1978 for his amazing previous work including his MSM8996 kernel
    • @supermike86 and @samsuffit for testing LineageOS 18.1 for T820, which is I don't have one
    • @bmwdroid and @cherepanov for confirming the LTE works
    • @sebmue for letting me know that the useful information for palm rejection, and @ghostwheel for sharing its working source codes on Android 9
    • @switchgott for helping me in the development discussion and creating Telegram groups
    • All from our Telegram discussion channel, @EonOfBlack , Sands, David Becker, ...
    • @LuK1337 for giving me a hint to fix the quad-speakers.
    12
    Hi all,

    Finally, I can take a picture with my Tab S3 :)

    But still, there are some annoying bugs about the picture resolution, a flashlight behavior, ... but yeah it is usable when I take something using slightly lower resolution without the flashlight.

    Also, for now, both the LOS camera app and Snap camera are not working well while Open Camera and Google Camera seem to be working well.

    For now, the major problem is that if I use a flashlight in the camera app at least once, the overall GUI animations slow down even I closed the camera app.

    So, when I publish the camera fixed version, at least I will fix this most bothering thing even though I can't fix it all for the camera.
    11
    Hello all.

    I uploaded the new version, including fixing the power-off mode charging.
    I'm using the LPM binary that is from Samsung for the power-off mode charging. When you plug in the charging cable while the tablet turns off, you can see the original charging screen you might see in the stock firmware. :)

    And I tried to fix the Bluetooth inputs and the OTG drives issues but I couldn't. I can reproduce these problems but I cannot find how to fix them for now. But I can confirm that the wired input devices are working such as a keyboard and a Playstation 4 controller.

    Please check out the first post of this thread. :)
    11
    Great news here. The next release will include the fully-working quad-speakers. :D
    And I also have implemented the audio rotation codes for the screen rotation.

    Actually, I already have used it for about 3 days, and I think it looks working flawlessly.
    And, for the alternatives of the Dolby Atmos, I have tested with the Dolby Digital Plus module with Magisk and I can say that it is awesome. :cool:

    The new release will be uploaded before this weekend. :)
    11
    Long time no see. :)

    I uploaded the new version that contains the November security patch and fixed arrow keys working on the keyboard inputs.
    Yeah, sorry for it isn't a big update, I know there're lots of bugs remaining. 😅

    Currently I have been investigating upgrading our kernel as I said before.

    I did start the Android kernel studying to know what CAF based kernel or AOSP based kernel means, and how the other people merge the latest tags from the official repositories to the vendor-providing kernel base.
    And now I think I'm managed to know the very small piece of that Android kernel world.

    First, I found that there is no problem with using the Bluetooth keyboard on the stock kernel for LOS, which hasn't any patch including the upstream Linux patches and/or any tunes.
    Yeah, this is interesting, it can be small evidence that the current kernel is somewhat broken at least for the Bluetooth.

    My first plan was to migrate Samsung codes to the LineageOS MSM8996 kernel. But after a few weeks, I realized that it isn't for humans. There are so many flags and tweaks they put in. Even some codes are not marked whether this code is from Samsung.

    So I changed my plan, to get CAF tags onto the top of the CTD1 kernel that is the latest kernel base of the T825 model. Fortunately, I could merge some modern CAF tags successfully. But in that progress the camera got broken. :unsure:

    Then, I tried to merge the AOSP tags for getting the proper upstream Android/Linux patches and security patches. I could merge until early 2020, that is also containing 3.18.140 upstream Linux patches. But I couldn't merge the latest patches like the one just published last month. It makes the tablet not boot.

    I think it is quite hard work on our tablet because Samsung puts various un-listed patches onto the top of the 3.18.115 kernel but they didn't apply the upstream Linux patches. So, for example, when I merge the 3.18.116 tag to the current 3.18.115 kernel, I couldn't accept all the incoming changes because some files in the current kernel base are much more modern files. o_O This makes me get frustrated.

    But it doesn't mean it is impossible. Some people out there are doing this job now so there will be something more I don't know yet about the Android kernel development. If someone has experience or knowledge of upgrading vendor kernel, please join our Telegram channel and let's discuss that.