I,m getting this tablet today , It will be for your projects , good work your on channel48 soon ,.
[ROM][UNOFFICIAL][12L][EAS][SM-T820][SM-T825][2022-07-15] LineageOS 19.1 for Galaxy Tab S3
- Thread starter Awesometic
- Start date
Oh its you!! , ive seen your vids on different devices a few times, always enjoyable and funny.
As it happens I just got my Tab s3 recently, so far impressed, that is also on stock 9.
Much improved over my old S2, did not think would be such a nice upgrade, but it is.
The 18w charging very welcomed over 10w. The hdr is nice, and the sound is no comparison really, mmiles ahead.
Will be looking forward to your review and usual banter for this tab
Keep up the good work, be nice to see how it performs over stock.
- Jul 30, 2017
- 186
- 478
For the users who are waiting for the next release,
I'm sorry that the fixing camera and Bluetooth audio are too late.
I have no personal time on my working days, so I looked into that only on the weekend, which is easily unavailable to develop something with my computer.
Where I am stuck is this, it does work with the current camera configuration (libs, props, ...) on my LOS 18.1 but it doesn't on my LOS 19.1. And it seems like there should be not that many things I can edit more. The camera driver is loaded so that the sensors of the front and rear camera are recognized, but it doesn't do more.
It means, we can see the camera sensors but can't see their information including supported resolutions, ISO range, or something else. So I need to investigate this part.
Hope that I can fix it soon. After fixing the camera part, I will remove that Alpha mark and attach Beta.
I'm sorry that the fixing camera and Bluetooth audio are too late.
I have no personal time on my working days, so I looked into that only on the weekend, which is easily unavailable to develop something with my computer.
Where I am stuck is this, it does work with the current camera configuration (libs, props, ...) on my LOS 18.1 but it doesn't on my LOS 19.1. And it seems like there should be not that many things I can edit more. The camera driver is loaded so that the sensors of the front and rear camera are recognized, but it doesn't do more.
It means, we can see the camera sensors but can't see their information including supported resolutions, ISO range, or something else. So I need to investigate this part.Hope that I can fix it soon. After fixing the camera part, I will remove that Alpha mark and attach Beta.
So nice reply Headzy thanks bro , I,m also having a bid on the T713 s2 , because it has some official development by e.foundation , so I want that tab to , guy is asking 100 box , so I just messaged him that 2017 device was obsolete and that I can give him about 60 eur for it , I hope he bitesOh its you!! , ive seen your vids on different devices a few times, always enjoyable and funny.
As it happens I just got my Tab s3 recently, so far impressed, that is also on stock 9.
Much improved over my old S2, did not think would be such a nice upgrade, but it is.
The 18w charging very welcomed over 10w. The hdr is nice, and the sound is no comparison really, mmiles ahead.
Will be looking forward to your review and usual banter for this tab
Keep up the good work, be nice to see how it performs over stock.
Video is uploaded I came to get the links etc , i,m gonna Link Android 11 as well just in case Alpha is to much , but all installed fine , camera failed I think on 12 , but hey , it's in Alpha so we must have patients. stay blessed bro
Great vid, just seen it, at the end was sad you are getting a bit disheartened by negative people's comments on your vids, ignore them and do it for the positive folk that appreciate your vids.So nice reply Headzy thanks bro , I,m also having a bid on the T713 s2 , because it has some official development by e.foundation , so I want that tab to , guy is asking 100 box , so I just messaged him that 2017 device was obsolete and that I can give him about 60 eur for it , I hope he bites
I always find it staggering when I see some roms have had 5 thousand plus downloads and there are only 1% of them that come to the forums and drop a thank you message to the devs. Such has human nature, it would seem they think they are entitled to all this hard work without even giving some common courtesy back, I mean they spend the time and small amount of hassle to install roms but they don't have 30 seconds to say thank you. No wonder you feel pissed off sometimes. Who can blame you.
I say keep making rom instal videos for those of us that do like them as long as you also are getting at least some enjoyment from it which is the most important factor.
All the best buddy,
Thanks bro , I will but i,m also busy with something else now that is taking off and give allot of inspiration , I did not say that I got bad comments , not at all , but little comments on uploads and that made me decide to maybe better shut off the whole comment section , that's what i said , and that's demotivating me and then I go look for other things to doGreat vid, just seen it, at the end was sad you are getting a bit disheartened by negative people's comments on your vids, ignore them and do it for the positive folk that appreciate your vids.
I always find it staggering when I see some roms have had 5 thousand plus downloads and there are only 1% of them that come to the forums and drop a thank you message to the devs. Such has human nature, it would seem they think they are entitled to all this hard work without even giving some common courtesy back, I mean they spend the time and small amount of hassle to install roms but they don't have 30 seconds to say thank you. No wonder you feel pissed off sometimes. Who can blame you.
I say keep making rom instal videos for those of us that do like them as long as you also are getting at least some enjoyment from it which is the most important factor.
All the best buddy,
Ill do a poll tonight !Any luck on headphone jack??? Loving your los18 rom, but love to use los19 if headphone jack works. Thanks again!For the users who are waiting for the next release,
I'm sorry that the fixing camera and Bluetooth audio are too late.
I have no personal time on my working days, so I looked into that only on the weekend, which is easily unavailable to develop something with my computer.
Where I am stuck is this, it does work with the current camera configuration (libs, props, ...) on my LOS 18.1 but it doesn't on my LOS 19.1. And it seems like there should be not that many things I can edit more. The camera driver is loaded so that the sensors of the front and rear camera are recognized, but it doesn't do more.
Hope that I can fix it soon. After fixing the camera part, I will remove that Alpha mark and attach Beta.
- Jul 30, 2017
- 186
- 478
Finally I think I found which thing I should look into to fix the camera and the remaining audio things including Bluetooth audio, headphone jack and the audio when screen recording.
Currently I managed to fix the camera working, which comes with some bugs yet but we can use it.
But I couldn't fix the audio yet. I found the root cause but don't know how to fix that.
So, the new one will come and I think it is not so far. If I can't fix the audio for a few days, then I will upload the new release including the working camera.
Currently I managed to fix the camera working, which comes with some bugs yet but we can use it.
But I couldn't fix the audio yet. I found the root cause but don't know how to fix that.
So, the new one will come and I think it is not so far. If I can't fix the audio for a few days, then I will upload the new release including the working camera.
This are great news. I would test the beta version right away. Keep up your amazing work. 
- Jul 30, 2017
- 186
- 478
Hello all,
After numerous tries, I could fix the camera and the Bluetooth/Headphone jack audio working.
The camera is back, but still has some bugs, unfortunately.
First, we can't use the default camera app, Camera2. It takes a shot but the result is cracked. But we can use a third party app like OpenCamera.
And, there is something weird on the Torch. After using the camera with the flashlight, sometimes the Torch tile on the quick settings is broken, it just said "camera in use". But we still can use the camera.
Lastly, sometimes the camera doesn't work at all after rebooting. Fortunately, it is easily fixed by rebooting again. I don't know why it is well.
Now our audio HAL is built from the source. Previously, we were using audio HAL version 4.0 which is for Android 9 but now we're using version 6.0 which is for Android 11. I can move on to version 7.0, yeah, which is for Android 12, but from this version the configurations have to be modified in many ways so I just pended it.
I had to supplement some audio configurations because of the compatibility of each version, maybe some audio scenarios were broken compared to our LineageOS 18.1. But I confirmed for most used scenarios like the quad-speaker, Bluetooth audio, headphone jack, and wireless display audio, so in most cases it will work well.
I think, we can deprecate our LineageOS 18.1 now because our LOS 19.1 has no fewer features than LOS 18.1.
After numerous tries, I could fix the camera and the Bluetooth/Headphone jack audio working.
The camera is back, but still has some bugs, unfortunately.
First, we can't use the default camera app, Camera2. It takes a shot but the result is cracked. But we can use a third party app like OpenCamera.
And, there is something weird on the Torch. After using the camera with the flashlight, sometimes the Torch tile on the quick settings is broken, it just said "camera in use". But we still can use the camera.
Lastly, sometimes the camera doesn't work at all after rebooting. Fortunately, it is easily fixed by rebooting again. I don't know why it is well.
Now our audio HAL is built from the source. Previously, we were using audio HAL version 4.0 which is for Android 9 but now we're using version 6.0 which is for Android 11. I can move on to version 7.0, yeah, which is for Android 12, but from this version the configurations have to be modified in many ways so I just pended it.
I had to supplement some audio configurations because of the compatibility of each version, maybe some audio scenarios were broken compared to our LineageOS 18.1. But I confirmed for most used scenarios like the quad-speaker, Bluetooth audio, headphone jack, and wireless display audio, so in most cases it will work well.
I think, we can deprecate our LineageOS 18.1 now because our LOS 19.1 has no fewer features than LOS 18.1.
Hi awesometic thanks a lot all works fine for me. Google play needed a few reboots. Camera is working, Audio is fine as well. Starting recovery works only with odinHello all,
After numerous tries, I could fix the camera and the Bluetooth/Headphone jack audio working.
The camera is back, but still has some bugs, unfortunately.
First, we can't use the default camera app, Camera2. It takes a shot but the result is cracked. But we can use a third party app like OpenCamera.
And, there is something weird on the Torch. After using the camera with the flashlight, sometimes the Torch tile on the quick settings is broken, it just said "camera in use". But we still can use the camera.
Lastly, sometimes the camera doesn't work at all after rebooting. Fortunately, it is easily fixed by rebooting again. I don't know why it is well.
Now our audio HAL is built from the source. Previously, we were using audio HAL version 4.0 which is for Android 9 but now we're using version 6.0 which is for Android 11. I can move on to version 7.0, yeah, which is for Android 12, but from this version the configurations have to be modified in many ways so I just pended it.
I had to supplement some audio configurations because of the compatibility of each version, maybe some audio scenarios were broken compared to our LineageOS 18.1. But I confirmed for most used scenarios like the quad-speaker, Bluetooth audio, headphone jack, and wireless display audio, so in most cases it will work well.
I think, we can deprecate our LineageOS 18.1 now because our LOS 19.1 has no fewer features than LOS 18.1.
bmwdroid
Senior Member
- Mar 8, 2014
- 1,616
- 1
- 683
@Awesometic thx again.
Great work.
Just flashed it plus FlameGApps + Magisk onto previous version.
(wiped only sytem+caches before)
Magisk of course needed to patch boot.img again.
All other apps, settings and Data survived.
Booting into recovery with pwr button works.
OpenCamera as well.
Jacks didn't try yet.
Great work.
Just flashed it plus FlameGApps + Magisk onto previous version.
(wiped only sytem+caches before)
Magisk of course needed to patch boot.img again.
All other apps, settings and Data survived.
Booting into recovery with pwr button works.
OpenCamera as well.
Jacks didn't try yet.
bmwdroid
Senior Member
- Mar 8, 2014
- 1,616
- 1
- 683
Didn't say, sorry.
Mine is T825 on twrp_3.6.0_9-0-gts3llte.img right now.
Nevertheless that shouldn't imo have anything to do with restart option to recovery.
any idea why PayPal crashes. An other problem I have with the android keyboard, switching to numbers it crashes
bmwdroid
Senior Member
- Mar 8, 2014
- 1,616
- 1
- 683
- Jul 30, 2017
- 186
- 478
I found a way to hide the bottom taskbar.
LOS team implemented this feature a month ago, but their patch doesn't consider the old devices which has the hardware buttons. So, it should be an option in the "Settings - Buttons" menu, but it only shows up for us when enabling the soft navigation bar.
I updated the Special Notes. Here's the instruction for that.
LOS team implemented this feature a month ago, but their patch doesn't consider the old devices which has the hardware buttons. So, it should be an option in the "Settings - Buttons" menu, but it only shows up for us when enabling the soft navigation bar.
I updated the Special Notes. Here's the instruction for that.
Code:
You can hide the bottom Taskbar. This is the workaround.
1. Go to "System -> Buttons" and check "Enable on-screen nav bar" to enable soft nav bar temporarily
2. Go back using navigation bar and go to the "Buttons" menu again
3. Then we can see the "Enable taskbar" option that we couldn't see before. Disable that option.
4. And disable "Enable on-screen nav bar" option again to use the hardware buttons back.Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
7The new version is uploaded.
With this version, I have added support for Sony DualShock 4 gamepad. I confirmed it's working, simply using the touchpad on it and the buttons and it is quite interesting.
And I increased the headphone jack volume too. I think now it gets enough to listen to something but I need feedback from the users.
Check out changelogs, and enjoy the new ROM.3Hi,
a few days ago I managed to fixed hardware encryption. I've encrypted my own tab and it's performing well. Additionally I applied a patch regarding palm rejection. When using the pencil with a handwriting keyboard, sometimes the keyboard closes because the pencil was not close enough to the display to get recognized. This should be better now.
My compiled version is based on the sources mentioned in the first post and on changes from these repos: https://gitlab.com/android229
Here is the link to my cloud with the build: https://1drv.ms/u/s!AgBELbH5Ycnt0RKSPGXy2r0FXd_i?e=F4OVNL
Of course all credits go to @Awesometic! He did a great job! For future builds we will merge our sources. But for now you can also use my build. The sources are mostly the same (based on Android 12 R11). So dirty flashing should be fine.3
@Awesometic , I don't have this device, but this should let users increase/decrease the volume themselves instead of you having to build new image.
Code:# boot into TWRP # click on mount, touch system # on pc with usb cable plugged in, let's get mixer_paths_tasha.xml adb pull /system/vendor/etc/mixer_paths_tasha.xml # bring up text editor on PC and edit mixer_paths_tasha.xml # users should look at # https://github.com/awesometic/android_device_samsung_gts3l-common/commit/ae49ee8c3859d0f378688611a4f4ffbcb68fbdb7 # to see what lines of code were modified and make modifications as desired to headphones # save file in PC # push back to tablet adb push mixer_paths_tasha.xml /system/vendor/etc/mixer_paths_tasha.xml # reboot back into OS
For those who want to increase speaker loundess, you probably need to change
"RX1 Mix Digital Volume"
"RX2 Mix Digital Volume"
from 76 say to 82.2
I'm also interested in this question. Running with selinux=permissive is high risk, and it seems irresponsible that such a large proportion of unofficial ROMs disable selinux. LineageOS makes it mandatory to run selinux in enforcing mode in their official ROMs for good reason.
With selinux disabled, it is trivial for malicious code in an app to permanently root the device and gain full control over it, giving malicious actors the ability to access and exploit your personal information that exists within your other apps or perform other malicious activity without the user knowing. Given that there is a PoC on github that shows how to do this, you can bet that this exploit is already out in the wild.
@Awesometic, I appreciate and respect that you put a lot of your personal time and effort into this (it's a lot more than I do), but I think this concern is valid. Can you eli5 why you haven't set selinux=enforcing in your builds, and if it is possible, what it would take to achieve this?2
I've had the same issue since installing the alpha, these instructions helped. Thanks! -
20Code:
/* * 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
- Dolby Atmos
- Headphone/Headset
- Quad speakers
- Video playback
- HDR
- Camera
- Microphone
- Sensors
- Fingerprint sensor
- GPS
- LTE (SM-T825)
- Hotspot
- WiFi
- WiFi display
- Bluetooth
- DRM
- Widevine L1
- USB ADB/MTP
- Samsung Doze
- S-Pen
- Palm rejection
- Hardware Encryption
- MDFPP
- SD Card
- Power-off mode charging
- FBE for userdata
- USB OTG
- SELinux permissive
- Please see the "Known issues" part of this post
# Downloads
## LineageOS 19.1
## Google Apps
- NikGapps
- The other Gapps will work too, but I only confirmed that NikGapps working
## TWRP Recovery
- You can use mine, please visit this thread.
# How to install
- Unlock the bootloader.
- Download TWRP and flash the recovery image via Odin.
- Download LineageOS 19.1 for Galaxy Tab S3.
- Be aware of the board name.
- Download GAPPS for Android 12L and the others you want to flash.
- Enter TWRP recovery.
- The first boot to TWRP might be very slow because of the unmatched file systems.
- Format the whole system, data, cache partitions using the format menu.
- You will type `yes` to do that.
- Flash the images.
- If you're going to install GApps or something, you have to install the LineageOS first.
- Reboot the system.
- Done.
# Known issues
- Camera somewhat buggy
- The built-in camera application (Camera2) is not working well. You can use another camera application like OpenCamera.
- Sometimes the camera doesn't work after booting. You can fix that back by just rebooting.
- After using the camera application, the Torch tile on the quick settings not working. But you can use the camera anyway.
- Thank all of you for the feedback
# Sources
- Device Tree
- Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
- Vendor: https://github.com/awesometic/proprietary_vendor_samsung
# 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
- If you like my efforts or would like to support me, please don't hesitate to buy me a cup of 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
- @followmsi , @html6405 , @ThE_MarD for giving me a hint to bring up Android 12
10Hello all,
After numerous tries, I could fix the camera and the Bluetooth/Headphone jack audio working.
The camera is back, but still has some bugs, unfortunately.
First, we can't use the default camera app, Camera2. It takes a shot but the result is cracked. But we can use a third party app like OpenCamera.
And, there is something weird on the Torch. After using the camera with the flashlight, sometimes the Torch tile on the quick settings is broken, it just said "camera in use". But we still can use the camera.
Lastly, sometimes the camera doesn't work at all after rebooting. Fortunately, it is easily fixed by rebooting again. I don't know why it is well.
Now our audio HAL is built from the source. Previously, we were using audio HAL version 4.0 which is for Android 9 but now we're using version 6.0 which is for Android 11. I can move on to version 7.0, yeah, which is for Android 12, but from this version the configurations have to be modified in many ways so I just pended it.
I had to supplement some audio configurations because of the compatibility of each version, maybe some audio scenarios were broken compared to our LineageOS 18.1. But I confirmed for most used scenarios like the quad-speaker, Bluetooth audio, headphone jack, and wireless display audio, so in most cases it will work well.
I think, we can deprecate our LineageOS 18.1 now because our LOS 19.1 has no fewer features than LOS 18.1.8## Changelogs
- 2022. 7. 15
- Synced with the latest LineageOS 19.1 repositories
- android-12.1.0_r11
- Security patch by July 5, 2022
- Added support for Sony DualShock 4 gamepad
- Increased headphone jack volume by about 20%
- Updated USB HAL to v1.3
- Synced with the latest LineageOS 19.1 repositories
- 2022. 6. 11
- Synced with the latest LineageOS 19.1 repositories
- android-12.1.0_r7
- Security patch by June 5, 2022
- Fixed camera working
- It is somewhat buggy, you can see the notes on the original post
- Fixed Bluetooth/headphone jack audio working
- Now it builds the AOSP audio stack from the source
- Fixed arrow keys orientation on the S3 Book cover keyboard in landscape mode
- Synced with the latest LineageOS 19.1 repositories
- 2022. 4. 16
- Synced with the latest LineageOS 19.1 repositories
- android-12.1.0_r4
- Fixed the boot failure issue for some users
- It is related to the Keystore of the Android system, I did a little compromise to make it work for all users
- If you are using the first version (220320),
you have to clean install to this version or you may fail to unlock the screen ,you have to boot into TWRP and remove the file `locksettings.db` under `/data/system` directory. This will resolve the unlock failure issue after dirty-flashing it.- Thanks for this information, David Becker.
- Thanks for this information, David Becker.
- Synced with the latest LineageOS 19.1 repositories
- 2022. 3. 20
- Initial release
8## Special Notes
- You must do clean-install if you are willing to upgrade from another ROM such as an Android 11 based one
- I have tested Magisk 24.3 working
- You can fix SafetyNet using Magisk modules, SafetyNet Fix and PropsConfig
- You can hide the soft nav buttons on the bottom bar. This is the workaround.
- 1. Go to "System -> Buttons" and check "Enable on-screen nav bar" to enable soft nav bar temporarily
- 2. Go to "System -> Gestures" and set "System navigation" to "Gesture navigation"
- 3. Go back to "System -> Buttons" and check "Enable on-screen nav bar" again to disable soft nav bar and enable hardware key.
- You can hide the bottom Taskbar. This is the workaround.
- 1. Go to "System -> Buttons" and check "Enable on-screen nav bar" to enable soft nav bar temporarily
- 2. Go back using navigation bar and go to the "Buttons" menu again
- 3. Then we can see the "Enable taskbar" option that we couldn't see before. Disable that option.
- 4. And disable "Enable on-screen nav bar" option again to use the hardware buttons back.
8Finally I think I found which thing I should look into to fix the camera and the remaining audio things including Bluetooth audio, headphone jack and the audio when screen recording.
Currently I managed to fix the camera working, which comes with some bugs yet but we can use it.
But I couldn't fix the audio yet. I found the root cause but don't know how to fix that.
So, the new one will come and I think it is not so far. If I can't fix the audio for a few days, then I will upload the new release including the working camera. - Display/Touchscreen
