had same here with lineage 19.1
if i want to go back to twrp then i have to flash it again via odin
after first reboot its gone
since 19.1 -> dirty flash 20.0 , i can start twrp normal via tablet reboot and power+volUP
[ROM][UNOFFICIAL][13][EAS][OTA][SM-T820][SM-T825][2023-11-16] LineageOS 20.0 for Galaxy Tab S3
- Thread starter Awesometic
- Start date
if i want to go back to twrp then i have to flash it again via odin
after first reboot its gone
since 19.1 -> dirty flash 20.0 , i can start twrp normal via tablet reboot and power+volUP
Send an other 15€. Hope it helps for a new device
- Jul 30, 2017
- 252
- 728
Finally I got a new one. Will upload the new version soon.
Thank you all for supporting me!
Thank you all for supporting me!
Thank you Awesometic for your work.
Just discovered this ROM as bought the tablet a few days ago.
1- Volume in earphones is way too low compared to Android 10 -if I'm not wrong this is something present since Android 12, but does somebody have any tip? I use the tablet for drumming and can barely listen the music in the background...
2- Reading the known issues - any hope the microphone will ever work on videocalls?
Again, thank you for your dedication.
Just discovered this ROM as bought the tablet a few days ago.
1- Volume in earphones is way too low compared to Android 10 -if I'm not wrong this is something present since Android 12, but does somebody have any tip? I use the tablet for drumming and can barely listen the music in the background...
2- Reading the known issues - any hope the microphone will ever work on videocalls?
Again, thank you for your dedication.
- Jul 30, 2017
- 252
- 728
To fix the Bluetooth earphones working (and more that I don't remember), I changed it to build audio HAL from the source. Before that, we're using the prebuilt audio HAL from the OTA firmware.
This makes us use the main features of the Android audio system, but at the same time it also breaks some tunes like volume or some features such as voice calling since we can't use the same configuration file that in the firmware. We need to re-write that file to use all the audio scenarios flawlessly..
Consequently, the audio issues like volume and voice calling are caused by moving from the prebuilt file to the built one, and I need to find the correct line and name, and the value in that config file to fix them.
Yeah, I wrote this to inform for those who wonder why the audio has been broken since Android 12.
Thank you very much for your explanation.To fix the Bluetooth earphones working (and more that I don't remember), I changed it to build audio HAL from the source. Before that, we're using the prebuilt audio HAL from the OTA firmware.
This makes us use the main features of the Android audio system, but at the same time it also breaks some tunes like volume or some features such as voice calling since we can't use the same configuration file that in the firmware. We need to re-write that file to use all the audio scenarios flawlessly..
Consequently, the audio issues like volume and voice calling are caused by moving from the prebuilt file to the built one, and I need to find the correct line and name, and the value in that config file to fix them.
Yeah, I wrote this to inform for those who wonder why the audio has been broken since Android 12.
In my noob understanding... Does this mean that eventually both issues could be fixed? Because that would be just AMAZING!
- Jul 30, 2017
- 252
- 728
Hopefully, as Android 11 (LineageOS 18.1) could do.
But don't expect too much
I'm going to try my best, but still there is a possibility that I couldn't fix them.Of course won't blame you if you can't, but got my faith in you after seeing your work! Can't really help you with anything technical besides testing builds if that helps you on anything... Thanks again!Hopefully, as Android 11 (LineageOS 18.1) could do.
But don't expect too much
@Awesometic, the Calxy-Team had the same problem (LTE not working) when migrating to CalyxOS 4.2 > CalyxOS 4.2.7 (Android 13). They were able to solve it with the help of LineageOS and PixelExperience.
- Jul 30, 2017
- 252
- 728
Thank you for the information. It seems like the patch is already on the LineageOS side then.
Currently I'm working on fixing the boot loop problem with TWRP Android-9.0 build. From my understanding, it should not be stuck even if there is no support for FBE. It seems something unsupported thing is there in our device tree. I doubt that is mdfpp Keymaster thing for now..
Edmondo Occhipinti
Senior Member
unfortunately bootloop (twrp, android 12, crdroid) at first boot after instructions
will wait for next revision
will wait for next revision
Are you getting the boot loop with just the LineageOS ROM? Or did you try to put GApps of some kind with it?unfortunately bootloop (twrp, android 12, crdroid) at first boot after instructions
will wait for next revision
I've often found it to be kind of finicky to make it work with GApps (sometimes requiring that I modify the GApps ROM to resolve), but I've never encountered a boot loop with just LineageOS on its own.
Edmondo Occhipinti
Senior Member
the first time i tried with gapps. Then i formatted everything again and tried without them. Unfortunately, same problem
So far, dirty flashing over 19 seems to be the best workaround, when you encounter a bootloop. I believe, Awesometic is working hard to enhance the stability of this ROM. Unfortunately, that's not an easy job, and he seems to be quite alone in maintaining the S3.
- Jul 30, 2017
- 252
- 728
Thank you all for understanding. It is right, I'm trying hard to fix the boot loop problem, which is the top priority at this moment.
I tried many cases about encryption and keymaster thing, but nothing has succeeded yet.
Wokring on both LineageOS system and TWRP.
After a few more shots, I think I may need to leave it as broken, and need to write installation instructions about that workaround for using Android 13 ROM.
Currently dirty-flashing from LineageOS 19.1 is the best workaround. Sorry for this inconvenience.
Plus, I think I can upload CrDroid 9 ROM too. I built one, and will test it tomorrow with CrDroid 8 for the dirty flashing. It is too late today
Coming from stock, I first started with TWRP 3.6.x which refused to start. Reflashing with 3.2.x solved the problem. As far as I remember then I flashed first successfully again the 3.6 followed by the Lineage 20 with no bootloop. Maybe there are files or structures which the older versions have and the newer ones not? Therefore a dirty flashing keeps some essential data, which are not included in the newer versions??
@Awesometic, yes, please do it!
Official crDroid ROM supports signature spoofing. Will your UNOFFICIAL crDroid 9 ROM support the installation of MicroG?
Signature spoofing support for your LineageOS 20.0 ROM would also be a nice addition for all users who don't want to install NikGapps or other GApps.
Very nice Rom, thank you for your work, tablet got new life. Installed dirty over Android 12. Used twrp 3.7.0_9. Waiting fix for microphone.
Definitely, hopefully @Awesometic is able to fix the audio/microphone thing because this tablet would have reborn.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
22Code:
/* * 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
- Hotspot
- WiFi
- WiFi display
- Bluetooth
- DRM
- Widevine L1
- USB ADB/MTP
- Samsung Doze
- S-Pen
- Palm rejection
- SD Card
- Power-off mode charging
- LTE (SM-T825)
- USB OTG
- SELinux permissive
- Data encryption
- FDE deprecated since Android 13
- FBE unsupported
- Please see the "Known issues" part of this post
# Downloads
## LineageOS 20.0
## Google Apps
- NikGapps
- The other Gapps will work too, but I only confirmed that NikGapps working
## TWRP Recovery
- You must use this version of TWRP, don't try another version out there
- TWRP 3.7.0 with no encryption
- After updating TWRP to this version, please do 'format data' that the menu requires enter 'yes', which clean up your current data
# How to install
- Unlock the bootloader.
- Download TWRP 3.7.0 with no encryption and flash the recovery image via Odin.
- Download LineageOS 20.0 for Galaxy Tab S3.
- Be aware of the board name.
- Download GAPPS for Android 13 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
- On webcam chat apps, there is a vertical green bar and the color is not properly displayed
- Audio bugs
- No sound for the microphone and speaker in voice calls, such as the regular phone call or voice chat with a meeting app
- 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
- Fast charging works (15W) but currently the kernel reports the wrong charging voltage and current
- 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
- LOS17.1) @Valera1978 for his amazing previous work including his MSM8996 kernel
- LOS18.1) @supermike86 and @samsuffit for testing LineageOS 18.1 for T820, which is I don't have one
- LOS18.1) @bmwdroid and @cherepanov for confirming the LTE works
- LOS18.1) @sebmue for letting me know that the useful information for palm rejection, and @ghostwheel for sharing its working source codes on Android 9
- General) @switchgott for helping me in the development discussion and creating Telegram groups
- General) All from our Telegram discussion channel, @EonOfBlack , Sands, David Becker, ...
- LOS18.1) @LuK1337 for giving me a hint to fix the quad-speakers
- LOS19.1) @followmsi , @html6405 , @ThE_MarD for giving me a hint to bring up Android 12
- LOS19.1) @masdaster for the fix of MDFPP Keystore on our device
- LOS20.0) LineageOS-UL
12Finally I got a new one. Will upload the new version soon.
Thank you all for supporting me!10Currently this is my plan for our tablet.
1. MAC address randomization
2. Android 14, which may be LineageOS 21 (-UL)
- Some notes on LOS 21, I could build without error but it doesn't boot at all, even the system is not initialized. This was about 1 or 2 months ago, so I think it is worth to try it again soon.
And I hope we can use kernel 4.4 on our device. But I can't promise it
By the way, recently I have tested a few things on my WSL, which is running on Windows so I could migrate my AOSP development environment from Linux to Windows, even with my EXT4 formatted SSD data storage. That is so cool since I wanted to use some apps during development that are only on Windows or macOS.
I hope I can do everything related to AOSP development in the WSL environment.
Happy New Year!10Hello all, it's been a long time.
Last few months, I tried to fix the boot-loop problem first but I couldn't succeed.
So for now I give up to fix that, and I will look into fixing the existing problems first such as the audio one.
I uploaded the new LineageOS 20 ROMs, which are synced with the latest LineageOS source codes.
Please see the new instructions too for clean installation.
Code:# How to install To fix the boot-loop problem, we need to install the previous custom ROM at least once. Unlock the bootloader. Download TWRP and flash the recovery image via Odin. Download any Android 11/12 based custom ROM, such as LineageOS 19.1 for Galaxy Tab S3. Download LineageOS 20.0 for Galaxy Tab S3. Be aware of the board name. Download GAPPS for Android 13 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. Install Android 11/12 based custom ROM, such as LineageOS 19.1. Boot once, and if the initial setup screen appears then reboot and enter the TWRP again. Erase the partitions using the advanced wipe option. It'd be the system, data, caches, and internal storage. Flash the images, including LineageOS 20. If you're going to install GApps or something, you have to install the LineageOS first. Reboot the system. Done.
The point is, if you have installed my Android 11 or 12 based custom ROMs at least once and haven't formatted the partitions using TWRP's format menu, you can install the Android 13 base custom ROMs only with wiping system, data, caches, and internal storage partitions using advanced wipe menu in TWRP.
And, I will upload CrDroid 9 soon.
PS. Keep in mind that you should make a backup of the current system/data partitions before updating. It's on the ALPHA stage yet.8
Yes, funny that a single hobbyist working during spare time can do updates faster than big corporations. Nicely done, @Awesometic! - Display/Touchscreen
