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

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

Search This thread

am2013

Member
Dec 27, 2012
26
2
@Awesometic: Have to report another issue related to non main/admin users. Basically installing the latest build did reset/delete all settings/data of the secondary user except the google account itself. So the user account is still available but all apps are gone and have to be reinstalled. Also amaze file manager will just crash for the secondary user. Would be cool if you could fix this.
 

TheLBall

New member
Apr 7, 2015
1
0
Samsung Galaxy Tab S3
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. :)
It appears that this update has turned the orientation of the arrow keys roughly -90° on the official Keyboard Cover for me. Nice rom btw!
 
Just trying it out.
Thx very much for your work and time.
Powered off charging info and start are working.

User info: contrary to the version before only a clean (incl "Fornat Data") made it possible to install on my T825.
Data restore made all as it was before.
I actually installed the ROM and GApps a second time without wiping anything and it booted.

Initially just wiped system and both caches.
 
Yeah, thanks for the report again. Another issue I almost forgot :unsure:
I thought I could bypass the freezing by letting Wi-Fi always on but encountered a black screen after a 20h pause.
Only possible things to see were lighted buttons when using any button and attached photo when using pwr button.
That menu is different to normal pwr button menu in 2nd pic and I only get it in frozen state.
I chose report but couldn't find where it was saved to.
Had to restart it anyway.
 

Attachments

  • signal-2021-09-30-171922.jpg
    signal-2021-09-30-171922.jpg
    224 KB · Views: 55
  • signal-2021-09-30-172919.jpg
    signal-2021-09-30-172919.jpg
    50.5 KB · Views: 56
Last edited:

yanmirc

New member
Oct 4, 2015
2
0
Awesome job! Thanks for the rom updates, this is a great device that should last years if not for the manufacturer forced early obsolescence.

I managed to install on 2nd time without issue (not sure why the first time the twrp did not flash right and I was stuck on samsung recovery, not managing to copy any files or to restart it. Had to install oem rom again and redo it). Did try to make it work with nikgapps without success (NikGapps-am271-reloaded-arm64-10-20211002-signed.zip), it ended up crashing on that initial configuration.

I then went with opengapps, but now it seems to be rebooting automatically or something, it gets stuck on the lineage animation and I have to manually force a reboot as nothing but power button works.
 

ker0zene

Senior Member
Feb 27, 2007
205
31
Awesome job! Thanks for the rom updates, this is a great device that should last years if not for the manufacturer forced early obsolescence.

I managed to install on 2nd time without issue (not sure why the first time the twrp did not flash right and I was stuck on samsung recovery, not managing to copy any files or to restart it. Had to install oem rom again and redo it). Did try to make it work with nikgapps without success (NikGapps-am271-reloaded-arm64-10-20211002-signed.zip), it ended up crashing on that initial configuration.

I then went with opengapps, but now it seems to be rebooting automatically or something, it gets stuck on the lineage animation and I have to manually force a reboot as nothing but power button works.

Have you installed the version of TWRP listed on the first page? If you've already done that, try booting into TWRP, wipe everything (data, system, cache, etc.) and then flash the ROM, and then immediately flash opengapps (for 11.0), afterwards boot into the OS. Hope this works, I've flashed a few versions of this amazing ROM and haven't had any issues using this procedure.
 

yanmirc

New member
Oct 4, 2015
2
0
Have you installed the version of TWRP listed on the first page? If you've already done that, try booting into TWRP, wipe everything (data, system, cache, etc.) and then flash the ROM, and then immediately flash opengapps (for 11.0), afterwards boot into the OS. Hope this works, I've flashed a few versions of this amazing ROM and haven't had any issues using this procedure.
Yes, that's what I did! Perhaps it's another app having conflicts, not sure. I'm gonna test it out a bit more and later make a clean install to see how it goes. It could also be the gapps version as I'm having some issues with chrome as well (I used open_gapps-arm64-11.0-pico-20210925.zip btw)
 
Last edited:

alisonjalel

New member
Jun 12, 2015
2
0
I thank you very much for your effort and time, everything is great, but there are some notes, regarding the high processor temperature during charging and use and even without charging as well, and it reaches a rate ranging between 85 to 94 Celsius and this is very large, and I think that you need to modify the code and reduce the voltage in the cpu So that the temperature does not rise in such a large way, especially in games, and suffocation occurs, the neck of the bottle, so the voltage must be reduced so that the mobile can be used normally,
 
...... high processor temperature during charging and use and even without charging as well, and it reaches a rate ranging between 85 to 94 Celsius and this is very large,....
Which device do you refer to?
Can't confirm that on my T825 but I admit that I lowered the max CPU frequency one step with "kernel adiutor".
Which Gapps did you flash?
 
Last edited:

alisonjalel

New member
Jun 12, 2015
2
0
Which device do you refer to?
Can't confirm that on my T825 but I admit that I lowered the max CPU frequency one step with "kernel adiutor".
Which Gapps did you flash?
Thanks for your quick reply..
My device…SM-T825
lineage-18.1-20210922-UNOFFICIAL-gts3llte
open_gapps-arm64-11.0-pico-20210925
And yes, I have tried a lot with kernel, adiutor and other applications a lot without finding any solution,
Actually, I understand and know how these pieces work in detail, that's my job,
But I am not IT, and I know perfectly well that the imbalance in the voltage is higher than it should be in the frequencies, and I did intensive tests and the same result was obtained.
Volt consumption should be reduced, not lowered frequencies.
I would like to lower the voltage, but I don't know how, actually?
And thank you again for such a great IT job.
 

am2013

Member
Dec 27, 2012
26
2
@Awesometic: Did check logcat and I think that this is related to the issue for the secondary user when I try to install new apps:

10-09 20:57:14.556 17409 17449 I Finsky : [19268] nty.a(16): Installer::DLP: Downloading compressed for com.microsoft.office.officelens
10-09 20:57:14.561 17409 17449 I Finsky : [19268] kwe.e(1): enqueue()
10-09 20:57:14.565 17409 21872 I Finsky : [19534] exq.run(5): Wrote row to frosting DB: 1321
10-09 20:57:14.579 17409 17449 I Finsky : [19268] nwy.a(17): Installer:🇮🇹 Already sent resource request for com.microsoft.office.officelens, adid: com.microsoft.office.officelens,
10-09 20:57:14.581 17409 17409 W Finsky : [2] nxt.x(1): Installer:🇮🇹 Cleanup running installation of com.microsoft.office.officelens (com.microsoft.office.officelens)
10-09 20:57:14.587 579 611 E vold : Failed to find mounted volume for /storage/emulated/10/Android/data/com.android.vending/files/
10-09 20:57:14.588 17409 21872 I Finsky : [19534] exq.run(5): Wrote row to frosting DB: 1322
10-09 20:57:14.590 17409 17409 W ContextImpl: Failed to ensure /storage/emulated/10/Android/data/com.android.vending/files: android.os.ServiceSpecificException: (code -22)
10-09 20:57:14.591 17409 17409 E Finsky : [2] aeye.a(2): EFD: external files dir not available
10-09 20:57:14.592 17409 17409 I Finsky : [2] nwe.U(1): Installer: stopping tracking of task: com.microsoft.office.officelens
10-09 20:57:14.595 17409 17530 I Finsky : [19313] tnr.B(4): PackageInstaller: Abandoned the session for com.microsoft.office.officelens, sessionId: 1115209189
10-09 20:57:14.596 17409 17409 I Finsky : [2] nwe.U(1): Installer: stopping tracking of task: com.microsoft.office.officelens
10-09 20:57:14.598 17409 17409 I Finsky : [2] nwe.N(18): Installer: Notifying status update. package=com.microsoft.office.officelens, status=DOWNLOAD_ERROR
10-09 20:57:14.604 17409 21872 I Finsky : [19534] exq.run(5): Wrote row to frosting DB: 1323
10-09 20:57:14.615 17409 21872 I Finsky : [19534] exq.run(5): Wrote row to frosting DB: 1324
10-09 20:57:14.619 17409 17409 I Finsky : [2] sin.a(19): Showing notification: [ID=com.microsoft.office.officelens, Tag=null, Title=Nicht genügend Speicherplatz, Message=Gib Speicherplatz frei, indem du nicht benötigte Apps und Inhalte entfernst, channelId=setup, targetType=1, returnCode=-1, uiElementType=933]
10-09 20:57:14.625 17409 17409 I Finsky : [2] nwe.M(7): Installer: found apps to install. isMultiUserMode=true, apps=[]

It looks like it cannot mount a volume. Maybe thgis helps. I still get the messge that there is not enough space availble.

BTW, in the latest version I was able to install chrome for the secondary user. So this seems to be fixed somehow.
 

LedgendaryEpics

Senior Member
Jun 14, 2018
83
22
@Awesometic: Did check logcat and I think that this is related to the issue for the secondary user when I try to install new apps:

10-09 20:57:14.556 17409 17449 I Finsky : [19268] nty.a(16): Installer::DLP: Downloading compressed for com.microsoft.office.officelens
10-09 20:57:14.561 17409 17449 I Finsky : [19268] kwe.e(1): enqueue()
10-09 20:57:14.565 17409 21872 I Finsky : [19534] exq.run(5): Wrote row to frosting DB: 1321
10-09 20:57:14.579 17409 17449 I Finsky : [19268] nwy.a(17): Installer:🇮🇹 Already sent resource request for com.microsoft.office.officelens, adid: com.microsoft.office.officelens,
10-09 20:57:14.581 17409 17409 W Finsky : [2] nxt.x(1): Installer:🇮🇹 Cleanup running installation of com.microsoft.office.officelens (com.microsoft.office.officelens)
10-09 20:57:14.587 579 611 E vold : Failed to find mounted volume for /storage/emulated/10/Android/data/com.android.vending/files/
10-09 20:57:14.588 17409 21872 I Finsky : [19534] exq.run(5): Wrote row to frosting DB: 1322
10-09 20:57:14.590 17409 17409 W ContextImpl: Failed to ensure /storage/emulated/10/Android/data/com.android.vending/files: android.os.ServiceSpecificException: (code -22)
10-09 20:57:14.591 17409 17409 E Finsky : [2] aeye.a(2): EFD: external files dir not available
10-09 20:57:14.592 17409 17409 I Finsky : [2] nwe.U(1): Installer: stopping tracking of task: com.microsoft.office.officelens
10-09 20:57:14.595 17409 17530 I Finsky : [19313] tnr.B(4): PackageInstaller: Abandoned the session for com.microsoft.office.officelens, sessionId: 1115209189
10-09 20:57:14.596 17409 17409 I Finsky : [2] nwe.U(1): Installer: stopping tracking of task: com.microsoft.office.officelens
10-09 20:57:14.598 17409 17409 I Finsky : [2] nwe.N(18): Installer: Notifying status update. package=com.microsoft.office.officelens, status=DOWNLOAD_ERROR
10-09 20:57:14.604 17409 21872 I Finsky : [19534] exq.run(5): Wrote row to frosting DB: 1323
10-09 20:57:14.615 17409 21872 I Finsky : [19534] exq.run(5): Wrote row to frosting DB: 1324
10-09 20:57:14.619 17409 17409 I Finsky : [2] sin.a(19): Showing notification: [ID=com.microsoft.office.officelens, Tag=null, Title=Nicht genügend Speicherplatz, Message=Gib Speicherplatz frei, indem du nicht benötigte Apps und Inhalte entfernst, channelId=setup, targetType=1, returnCode=-1, uiElementType=933]
10-09 20:57:14.625 17409 17409 I Finsky : [2] nwe.M(7): Installer: found apps to install. isMultiUserMode=true, apps=[]

It looks like it cannot mount a volume. Maybe thgis helps. I still get the messge that there is not enough space availble.

BTW, in the latest version I was able to install chrome for the secondary user. So this seems to be fixed somehow.
chrome is literal spyware dont download.
 

Hoerli

Member
Oct 18, 2014
39
19
www.hoerli.net
Hello Forum,

wanted to leave my feedback here.
I have the T820 - so only WLAN - and the device currently runs well.
- No GApps installed, only F-Droid and Aurora-Store.
- All hardware buttons work
- Camera works, just no 2160p video possible > I have the same problem with my Galaxy Note 8 as well
- WLAN, Bluetooth and GPS work
- Battery lasts several days
- Brightness sensor, gyro sensors work fine
- All speakers work
- All LineageOS standard apps work without problems
- SD card (32GB) is recognized without problems, speed is only very slow for data transfers
- UI is a bit sluggish from time to time, after closing all apps it's ok again

Up to here already respect for the work :)
Hope there are also diligent updates.
 
  • Like
Reactions: n2f

didier_w

Member
Apr 18, 2016
23
3
Hello,

I tried to format sdcard as adoptable, on the SM-T820, but at best the card finish in corrupt state, and at worst the rom is broken and the tablet needs to be reinstalled. I've even got to reflash twrp, cause the tablet wouldn't enter in recovery mode anymore nor go on.
Also tried to format the card from twrp, no better success in having the OS recognize it or want to work with it.

Looking on gitlab about official LOS 18.1 shows that this problem occurs also on other hardware phones. I'll try to format the card as external and check if it's more stable doing so.
 

didier_w

Member
Apr 18, 2016
23
3
Hello,

I tried to format sdcard as adoptable, on the SM-T820, but at best the card finish in corrupt state, and at worst the rom is broken and the tablet needs to be reinstalled. I've even got to reflash twrp, cause the tablet wouldn't enter in recovery mode anymore nor go on.
Also tried to format the card from twrp, no better success in having the OS recognize it or want to work with it.

Looking on gitlab about official LOS 18.1 shows that this problem occurs also on other hardware phones. I'll try to format the card as external and check if it's more stable doing so.
I tested different cards, differents size, and eventually some cards are able to complete formating and be used, and some not. So I guess it's more a speed/quality problem than something else.
 
Hello all.

Thank you all for all the feedback and review. :)
I was so busy for cleaning up my ordinary jobs first so I couldn't reply to your comments. Sorry.
But I read all of the comments and now I can collect the major issues that can be found so far and now I started to think that the kernel should be upgraded.

I'm not sure but the LineageOS guys can port the Samsung codes to the upstream Snapdragon kernels, so it should be not impossible for us.

As always, I'm not sure I can but currently I'm trying to port them to the LineageOS kernel. This can be abandoned so please don't expect too much. ;)

And, before that, I'm suffering from the "not waking up after fingerprint recognition" problem. It is so annoying... :cautious:
 
Last edited:

Top Liked Posts

  • 1
    is there any prospects for android 12? ... maybe an early look to see if its possible, my n8013 the dinosoar that it is already has an alpha build because only God wished it
    Sure, if I could.
    But as always, please don't expect too much 😅
    1
    I'm still getting the Google drive file from 11-30, not 12-3 when I click the OP link -- or does 11-30 include the new kernel you referred to in the 12.3.2021 update?

    Is everyone using the 20211130 ROM who's posting about it?
    Yeah, 20211130 is the latest version now. I'm sorry for the ambiguous titles.
    Will change them to the same date. 😀
  • 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.
    6
    Hello all.

    I uploaded the new LineageOS ROMs that comes with the new kernel.

    Probably the first seen noticeable change is the Bluetooth keyboard is fixed now. 😀
    And there are lots of improvements on that. I wrote the detailed information to the first post of this thread but firstly, I copied that contents here.

    ## About the kernel

    ### Update on 2021. 12. 3


    Finally the first release including my custom kernel is published, as of December 3, 2021.
    Now all the later releases will have my kernel. :)

    This kernel is based on CTD1 firmware, and I have done the following jobs so far;
    • Merged android-linux-stable/msm-3.18, which is including up to Linux 3.14.140 patches
    • Merged LA.UM.7.6.r1-07800-89xx.0 CAF tag
    • Replaced the built-in WLAN driver into the CAF one from LA.UM.7.6.r1-07800-89xx.0 tag, which is the latest version
    • Disabled most of Samsung-specific flags including TIMA, KNOX, RESTRICT, ...
    • Enabled F2FS file system
    • Added AutoSMP CPU hotplug feature and enabled by default for better battery consumption
    • Added AdrenoBoost and enabled by default for better GPU performance
    • Added Anxiety I/O scheduler for better I/O performance
    • Enabled TCP Westwood congestion window control by default for better network stability
    • Set CONFIG_HZ to 300 which is recommended in Android devices and it improves overall interactivity and UX with no power cost
    • Now the S-Pen palm rejection is implemented in the kernel rather than the Android frameworks
    • Maybe more..?
    But we have still some limitations.
    • It still uses the legacy camera driver from CTD1 firmware so unfortunately there are the same bugs on the camera as before
    • The screen on/off using a flip cover is broken for an unknown reason. The system recognizes how the flip cover status changed but actually not working
    • Cannot upgrade to the next CAF tag because of some old blobs we have, I believe
    • Maybe more..?
    This is the first version of mine, so there might be some more upgrades on later.

    I think the most meaningful thing about this job is now we can edit the kernel on the full Linux kernel commits.

    Enjoy. 😀
    1
    @Awesometic great news. Thx very much again.
    Just downloading.
    Any, to you known, disadvantages from f2fs to ext4?
    I've read that ext4 is more stable.
    What do you think?

    Yeah definitely, EXT4 is the most stable file system for Linux so even the modern Linux distributions use that as a default file system for the root partition.
    I think F2FS is also stable nowadays and it is enough to use on a mobile device. In fact, 3.18 kernel doesn't get the latest patches since 3 years ago but fortunately CAF and AOSP sometimes added some patches on that.
    Yeah, this depends on your choice. Between relatively unstable but faster one and the most stable but a little slower one :)
    1
    @Awesometic so being lazy I've just wiped System and Caches then flashed your new LOS which worked.
    As I undervolt (thought might reduce freezes) my device I don't think it's sense full to switch to a faster fs.
    I will use it like before to test if (probably GMS caused) random freezes still appear.
    If they don't I still can switch to f2fs.
    1
    Hello guys, first of all, this is the best custom rom ever for our tab s3. Many thanks to Awesometic and team !
    I'm trying to activate gestures navigation that i remember can be found at settings > system > gestures > system navigation. In this rom i do not see this option. Can the gestures be activated ? I could not figure out how ... Thanks in advance !!
  • 28
    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
    • 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
    • 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.