Related
About LineageOS
LineageOS is a free, community-built, aftermarket firmware distribution of Android 10.0 (Ten) which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS GitHub repo and if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website
Downloads Links
begonia | begoniain
Google Applications (optional) :
OpenGapps (Use packages for ARM64, Android 10.0, Nano)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
LineageOS clean install :
- Boot into the LineageOS recovery.
- Format data and install the latest LineageOS build
- Install OpenGAPPS package, if you want GAPPS otherwise skip this step
- Wipe Dalvik/Cache and Reboot into System
About the builds
- Device Side Sources are on official org
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error and steps to reproduce it
You can also join and help me debug your issues in the following Telegram Group: https://t.me/xiaomi_begonia | Not required but donations are welcome: Paypal
XDA:DevDB Information
LineageOS-17.1, ROM for the Redmi Note 8 Pro
Contributors
TheImpulson
Source Code: https://github.com/LineageOS/android_kernel_xiaomi_mt6785
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 17.1
Stable Release Date: 2020-08-11
Created 2020-03-26
Last Updated 2020-08-12
Current Bugs include:
The camera doesn't have full resolutions support yet
SELinux is Permissive
Don't report bugs related:
to CTS failures (LineageOS does not tamper with CTS results)
with Magisk (It sets a number of props on boot like changing build type to the user resulting in broken adb root etc)
with Custom Kernel, MODs (Report that to MOD maintainer)
with non-recommended vendor or builds (Use what is told in instructions)
Reserved
Reserved
Amazing to see this around. Thanks for your hard work. Will probably play around with this for a while
This rom willl be good for daily driver?
L1nx99 said:
This rom willl be good for daily driver?
Click to expand...
Click to collapse
Please, it's just 3 posts above, read. See BUGS and decide if this can be a daily driver for you.
For ME, when Wifi is fixed, it will be a daily driver. And I will wait patientily until then, helping the dev whenever I can testing releases.
wifi working fine
Reserved !
Is USB tethering work?
when NFC will be working ?
Is it even possible for NFC to make it to working?
Ask it another time in the same page please. If it was possible it would've been done already. Probably working on it, figuring out how to do it or just busy with other stuff. Be patient and be glad that some of these devs are working in this device.
korbielow said:
when NFC will be working ?
Click to expand...
Click to collapse
Asking for ETA is against XDA forum rules and disrespectful to the developer.
It will be done when it's done. If you can't wait, use stock.
I must downgrade Android 10 to 9,to be able to flash this ROM,or any other?
tze_vitamin said:
I must downgrade Android 10 to 9,to be able to flash this ROM,or any other?
Click to expand...
Click to collapse
If you are on MIUI 11 - Android 10, you WILL need to downgrade to Android 9! This method will not work if you're on Android 10. Use MiFlashPro or fastboot to flash all partitions to a compatible MIUI 10 or 11 Android 9 build.
copypasta from megathread.
L1nx99 said:
This rom willl be good for daily driver?
Click to expand...
Click to collapse
L1nx99 said:
Is USB tethering work?
Click to expand...
Click to collapse
korbielow said:
when NFC will be working ?
Click to expand...
Click to collapse
Pushed a new update on GitHub Releases. Here is the changelog:
- Updated safe media volume warning level
- Hided sRGB toggle in developer options
- Fixed Ambient display and enabled Always on Display
- Fixed brightness issues by importing overlays from Google Pixel (marlin)
- Added Trust Hal, see it in Privacy Settings
- Enable option for full-screen aspect ratio
- Added notch overlay, this makes center clock and network speed indicator unavailable as they are unsupported with notched devices
- Added led notification and battery led customization options, see it in Notifications settings
- Turned on WiFi MAC randomization
- Hex-edited MTK RIL lib to fix incoming calls
- Upstreamed kernel to v4.14.158
The hotspot is also working, however, it's buggy. You need to remove SIM cards to make it work. That will be fixed in future builds (hopefully).
TheImpulson said:
Pushed a new update on GitHub Releases. Here is the changelog:
- Updated safe media volume warning level
- Hided sRGB toggle in developer options
- Fixed Ambient display and enabled Always on Display
- Fixed brightness issues by importing overlays from Google Pixel (marlin)
- Added Trust Hal, see it in Privacy Settings
- Enable option for full-screen aspect ratio
- Added notch overlay, this makes center clock and network speed indicator unavailable as they are unsupported with notched devices
- Added led notification and battery led customization options, see it in Notifications settings
- Turned on WiFi MAC randomization
- Hex-edited MTK RIL lib to fix incoming calls
- Upstreamed kernel to v4.14.158
The hotspot is also working, however, it's buggy. You need to remove SIM cards to make it work. That will be fixed in future builds (hopefully).
Click to expand...
Click to collapse
Thank you for the update!
video bug in instagram,whatsapp,facebook etc
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress. It boots and seems to work fine on my SM-T350, but I have only tested it for 24 hours. Problems will likley surface later?
BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.
What works.
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. Google play store - use pico apps
8. flip flap smart cover
9. audio over bluetooth
Note: first initial boot takes a bit longer, be patient.
Known problems.
1. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
Rootless Pixel Launcher | F-Droid - Free and Open Source Android App Repository
F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.
f-droid.org
OR you can use nubianprince's crdroid 10.0 build for this tablet. He used his 9.0 repos and has no problems with fuzzy fonts/text. See
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
OR you can use a fairly recent 16.0 build which doesn't have the problem.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. FM Radio is not support since this device doesn't have the LTE functionality.
4. Stock camera does not take picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work.
Open Camera | F-Droid - Free and Open Source Android App Repository
Camera App
f-droid.org
5. BOE panel
For people who get black or blank screens when trying to flash TWRP 3.3.1 or LineageOS or crDroid SM-T350 roms, it's likely you have a BOE sourced panel.
Code:
adb root
adb shell cat /proc/cmdline
The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,
mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none
There is a fix as documented at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
Thanks/Credits
Thanks to @nubianprince and @lividhen99 for ideas and suggestions on getting this build to work. I used one of nubianprince's repos for this build.
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Does the build work on xyz?
A1) I have no idea. I only have the SM-T350. You can try it on variations, but don't be surprised if you get bootloop or bricked hardware. In addition, I won't build it for the 355 (LTE) version.
Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then try 16.0 or going back to the last rom that worked for you.
Q3) My tablet hangs or crashes with 17.1. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.
Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q5) What TWRP should I use?
A6) TWRP 3.3.1 or 3.5.0.9. Get it from
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
Q6) What is the difference between this rom and crdroid?
A6) Use this rom, crdriod or stock. It's not a popularity contest, so use whatever fits your needs. I only offer this as an option for those who want or need a new rom. Most of the code is the same between this rom and crdroid, however, the way we implemented the fixes might be slightly different. In addition, if there is a bug in this rom, it may not be in crdroid due to coding differences and how it's fixed.
Q7) Can I turn off the on screen navigation keys?
A7) To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation.
Q8) Can I build this rom? Where are the source and kernel source files?
A8) Yes. I have uploaded the repo diff and roomservice.xml file. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
The repo diff is what I changed compared to "stock" msm8916 code. The majority of the repo diff is because there's a bug in 17.1 WiredAccessoryManager.java and I reverted back to the 16.0 code. The bug prevents audio through the headphone jack. See
https://forum.xda-developers.com/showpost.php?p=83445681&postcount=13
Q9) Where can I download this rom?
A9) You can find the 2020 17.1 and 16.0 builds at
Downloads for : Samsung Galaxy Tab A 8.0 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.
2021 builds found at
retiredtab - Browse /SM-T350/17.1 at SourceForge.net
sourceforge.net
TODO
1. document and upload long list of fixes you need to build 17.1 if you want on your own.Done.
2. mirror nubianprince's repo in case it gets deleted.Done.
3. upload some files, fixes and documentation to github for future.Done.
Dec 13, 2021 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:Q_asb_2021-12
2. Whatever LiineageOS changed since last November release (about 4,400 files had to be recompiled).
Nov 8, 2021 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318647
2. Whatever LiineageOS changed since last October release (about 5,100 files had to be recompiled).
Oct 10, 2021 release notes
1. Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317410
2. Whatever LiineageOS changed since last Sept release (about 4,700 files had to be recompiled).
Sept 17, 2021 release notes
1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083
2. Whatever LiineageOS changed since last August release (about 49,500 files had to be recompiled).
Aug 7, 2021 release notes
1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572
2. Whatever LiineageOS changed since last July release (about 4500 files had to be recompiled).
July 12, 2021 release notes
1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448
2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).
June 15, 2021 release notes
1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240
2. Whatever LiineageOS changed since last May release (about 5400 files had to be recompiled).
May 10, 2021 release notes
1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564
2. Whatever LiineageOS changed since last April release.
April 12, 2021 release notes
1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454
2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.
Release notes for March 7, 2021
1. Mar 5 security patches.
2. Whatever LiineageOS changed since last February release.
3. Stock camera does not save picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work. I never use the camera or video recording on the tablets.
Release notes for Feb 10, 2021
1. Feb 5 security patches.
2. fixed audio over bluetooth. Huge thanks to @nubianprince for helping with suggestions and his repos. The problem was that some of the audio xml files weren't being copied over in 17.1 because of some directory changes to hardware/qcom.
3. Whatever LineageOS changed since last Jan 2021 update.
Release notes for Jan 14, 2021
1. Jan 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Dec 2020 update.
4. For some reason after flashing the rom, TWRP 3.3.1 now says "unable to mount storage". I had never seen that before. Nevertheless, if you reboot, the rom will work fine. I test all my builds before uploading.
Release notes for Dec 14, 2020
1. Dec 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Nov update.
4. Add timekeep functionality since SM-T350 has no real time clock. This allows the tablet to keep time when not used with a NTP (network time protocol) server. It works in Android OS and TWRP.
Nov 8 release
- Nov 5 security patches
Oct 8 release
- Oct 5 security patches
Sept 13 initial release
- Sept 5 security patches
- initial release for testing and help fixing bugs
- CPU and GPU overclocked to 1.6Ghz and 650 respectively - built into 17.1 kernel code
- based on stock github MSM8916 T350 code with a LOT of bug fixes and using one of nubianprince's repos
Oct 8 build released. See post #4 for changes.
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
See this logcat:
Code:
01-18 08:52:10.608 680 680 I SystemServer: StartAlarmManagerService
01-18 08:52:10.611 680 680 D AlarmManagerService: Kernel timezone updated to -480 minutes west of GMT
01-18 08:52:10.611 680 680 I AlarmManager: Current time only 1471930611, advancing to build time 1602188073000
01-18 08:52:10.611 680 680 D AlarmManagerService: Setting time of day to sec=1602188073
10-09 04:14:33.001 680 680 W AlarmManagerService: Unable to set rtc to 1602188073: Invalid argument
10-09 04:14:33.006 680 680 D SystemServerTiming: StartAlarmManagerService took to complete: 10ms
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them. The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Hope it could be solved.
Which TWRP image are you using? I've seen a couple different ones, but since there's no official support over at http://twrp.me/ I'd prefer to use the same one you're using to test this ROM installation...
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
I'll take a look, but right now I have a big project that I need to get finished by mid November so my time for building and troubleshooting roms is limited right now.
reukiodo said:
Which TWRP image are you using?
Click to expand...
Click to collapse
TWRP 3.3.1
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
These messages
D modemanager: Panel Name: S6D7AA0_LSL080AL03_BOE_wxga_video_mode_dsi_panel
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: instantiateModeMgr: Failed to update default cache!
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: in applyDefaultMode fail to retrieve default mode!
I modemanager: in applyDefaultMode ret = 0 mCurMode = -1
are from the proprietary module (which is why I couldn't find them in the AOSP code)
system/vendor/lib/libmm-qdcm.so
If you search for those keywords above, they all appear in this module.
At this time, I have no idea what the libmm-qdcm.so does and how it controls the backlight, if at all.
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
spiramedia said:
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
Click to expand...
Click to collapse
From
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
TWRP 3.3.1 is at
https://drive.google.com/file/d/14T99LQaKtEhGeglFxrUm0kMRw_RKopP5/view
me t350 just shut's down on his own. clean install.
spiramedia said:
me t350 just shut's down on his own. clean install.
Click to expand...
Click to collapse
Works fine for me and others.
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Hexrotor said:
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Click to expand...
Click to collapse
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
spiramedia said:
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
Click to expand...
Click to collapse
@spiramedia, when asking for help, it helps us if you provide maximum information. For example,
1) What are you running when the tablet shuts down? High performance gaming? Watching youtube?
2) How long does the tablet run before shutting down?
3) Maybe your battery is really old and weak especially if you used it daily for 5 years?
4) If you think it overheats, you can download several CPU apps that tell you the temperature of the CPU like
https://f-droid.org/en/packages/com.kgurgul.cpuinfo/
5) If the battery is old and weak, does it shutdown when you have the AC microusb adapter plugged in all the time?
6) When it shuts down, what is the battery percentage at?
7) Is your battery guage calibrated properly? If it says 30%, maybe it's really 0% and you have to discharge/recharge 2 or 3 times to recalibrate?
As you can see, I asked a lot of questions. The more info you can give, the better.
PS. If you have a BOE panel and backlight works, then I have no idea why my rom works with yours and not Hexrotor.
Hexrotor said:
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
Click to expand...
Click to collapse
@Hexrotor, does this happen if you date and time setup to "use network provided time".
If I turn "use network provided time" off, then yes, the tablet doesn't keep time properly. I think it's due to the Qualcomm RTC being read only? Searching the Internet, a possible fix might be
https://github.com/LineageOS/android_hardware_sony_timekeep
I might try incorporating that into the next rom build which will likely be sometime mid Nov when the next security patches are released.
I think it's defaulting to Oct 9 because the build date is Oct 8, but in your timezone, it might be Oct 9.
Hexrotor said:
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them.
Click to expand...
Click to collapse
The error messages for the BOE panel are just before the system stops the boot animation and gives the 3 dots and says LineageOS. I find that to be confusing because I would think the kernel would enable BOE backlight at the very beginning so you can see what is on the display. It makes no sense to have the backlight completely dark and then enable it just before the 3 dots that says LineageOS.
And if spiramedia's BOE backlight works with my rom, then I don't know why it doesn't work with yours. Maybe there is something persistent in one of the persist partitions where a prop is set?
Hexrotor said:
Backlight problem is still in my BOE device.
Click to expand...
Click to collapse
@Hexrotor, you didn't specify in this thread or the original crdroid thread whether you tried downgrading the stock to marshmellow and then try crDroid 10 or LineageOS 17.1.
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
retiredtab said:
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
Click to expand...
Click to collapse
Nope, I tried this way but no help. I flashed marshmallow firmware then Crdroid6.9 without clean, it was no display but heated up at boot. I waited for about 10min but it didn't boot complete. Edit: I tried again just now, it booted successfully but still no backlight. Now I'm using official marshmallow.
I don't know why this ROM works with spiramedia's BOE device. I have some friends who have T350/P350 BOE devices and all they have backlight problem with 3-part ROMs, that’s why I am sure that the backlight problem is related to BOE.
For Los 17 and Crdroid, my device has no backlight after the "Samsung Galaxy Tab A", but official marshmallow works fine.
PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
9. camera
Thanks
1. LineageOS team for source code.
2. Pre alpha testers for the Samsung Tab A/E roms who provided valuable feedback: lpedia, Schaagi, katochwa, Henrick Grimler
3. nubianprince for helping fix audio over bluetooth on SM-T350 on 18.1.
4. Huge thanks to Henrick Grimler https://github.com/Grimler91 for helping me reproduce a major bug in 18.1 which led me to find a solution. Henrick also helped fine tune some of the sepolicy as well.
5. Sebastiano Barezzi https://github.com/SebaUbuntu for giving the msm8916 repo some 18.1 code updates in March 2021.
6. Exynos5420 team for sharing it's knowledge in building roms.
7. msm8916 team for their repos
8. dylux for suggesting a fix for the front camera photo/record crashing by using stock SM-T350 media_profiles.xml.
FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2020 to March 2021 running into bug after bug. The least you can do is spend a few minutes reading everything before posting.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
GitHub - Galaxy-MSM8916/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.
MSM8916/MSM8929/MSM8939 kernel for Samsung devices. - GitHub - Galaxy-MSM8916/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.
github.com
The device tree files are at
GitHub - retiredtab/android_device_samsung_msm8916-common: Common MSM8916 tree for Samsung devices
Common MSM8916 tree for Samsung devices. Contribute to retiredtab/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
GitHub - retiredtab/device_samsung_gt58wifi
Contribute to retiredtab/device_samsung_gt58wifi development by creating an account on GitHub.
github.com
GitHub - retiredtab/device_samsung_gte-common at lineage-18.1
Contribute to retiredtab/device_samsung_gte-common development by creating an account on GitHub.
github.com
The vendor tree files are at
GitHub - retiredtab/vendor_samsung_msm8916-common
Contribute to retiredtab/vendor_samsung_msm8916-common development by creating an account on GitHub.
github.com
GitHub - retiredtab/android_vendor_samsung_gt58wifi
Contribute to retiredtab/android_vendor_samsung_gt58wifi development by creating an account on GitHub.
github.com
In addition, there is a repo diff file for device specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself.
Q2. Is this BETA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid March 2021 with no major issues.
Q3. What if my app, xyz, doesn't work?
A3. I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use TWRP 3.5.2_9. Get it from
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-11.0][v7.10][ANDROID 11] Galaxy Tab A 8.0
I am not responsible for bricked devices, or any other hardware malfunctions that comes as a result of flashing this ROM, Please do some research if you have any concerns about features included before flashing it, this ROM was built for the...
forum.xda-developers.com
Q6. Why should I use this rom?
A6. You don't. If you don't like this rom, then don't use it. Yes, it's that simple.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. Do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
Q10. Will you still build 17.1 for this device?
A10. Yes, for now, but I will probably discontinue building 17.1 at the end of 2021. I will likely be trying to build 19.0 once it's released so I don't want to maintain 3 releases.
Q11. Do I need to erase everything and format my data?
A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Q12. What gapps should I use?
A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary. It's reported that opengapps does no testing on their daily builds and some version results in bootloops, bitgapps may run out of disk space will installing apps and Mindthegapps as causing overall slowdown of the system.
The only recommendation I can make is to use the SMALLEST version of gapps which is PICO or equivalent naming convention. DO NOT use anything other than PICO. That is, do not use nano, mini, stock, etc.
If you are going to install gapps, flash the rom first, reboot into system/OS, reboot to recovery, flash gapps, reboot into system/OS. That is, do not flash/install the rom and gapps at the same time.
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
Q14. Why isn't my post answered?
A14. It's probably because it's answered in the FAQ or not relevant to the rom. Again, I do not run Windows OS or use gapps. Questions already answered in the FAQ will be completely ignored.
Q15. Can I turn off the on screen navigation keys?
A15. To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation. It's enabled by default because I find it useful. If you don't like it, you only need to disable once and your preference will be remembered. If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout
Q16. What speed up/optimization tips do you suggest?
A16.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
4. Use a web browser like Brave that has built in adblock and privacy features.
5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
6. Look for apps that are open source, ad free and lightweight.
Q17. Does this rom support Magisk?
A17. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.
Q18. Will this rom ever become official?
A18. Never. I don't want the responsibilities that come with being an official maintainer. In addition, I know my device trees, code organization and git commits will NOT meet LineageOS standards. Remember, I'm an unpaid volunteer doing this in my free time and sharing my work with you for free so you can get hundreds of hours of enjoyment from this tablet.
Q19. What is the difference between this rom and others?
A19. This rom tries to be pure LineageOS with little to no modifications. Other roms may have different UI, different bundled apps, etc. Use whatever meets your requirements.
Q20. Will there be any major 18.1 code modifications in the future?
A20. I don't anticipate any major modifications. There may be some slight tweaking to the sepolicy, small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 18.1 is working. Any major changes will be done in 19.0.
Q21. Why did you fork the device and vendor trees for 18.1?
A21. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.
In addition, since I'm building SM-T350, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not. I still have not figured out the best way to manage all my repos and it's a work in progress.
Q22. Can you build a variant of this device? For example, a LTE or S-pen version.
A22. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.
Q23. Can I load this rom on a variant devivce like LTE or S-pen version?
A23. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q24. Will this run on the SM-T355 or SM-P355?
A24. No. Someone has tried and it will result in a bootloop.
Q25. How do I know if I have a BOE panel?
A25. Some ST-350 tablets have a BOE display panel. In order for it to work with TWRP and any custom rom, you must have the correct bootloader installed on a BOE panel otherwise you will see a black/blank screen. To check to see if you have a BOE panel, open a terminal and
Code:
adb root
adb shell cat /proc/cmdline
The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,
mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none
There is a fix as documented at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
Q26. What is a GO build?
A26. A GO build uses less DRAM, disk space and supposed to be better suited for devices with 2GB DRAM or less. I have no idea whether it's true or not vs a NON GO build, but I figured I would try a GO build.
Some of the features removed in a GO build are documented in post #46 in this thread in addition to work profiles. If you need these features, you can edit a property in the build.prop as documented in post #49.
Q27. Okay, I understand the consequences and that this is BETA rom and willing to take the risks outlined, now where can I find the rom?
A27. Downloads are at
retiredtab - Browse /SM-T350/18.1 at SourceForge.net
sourceforge.net
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
June 9, 2023 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-06
2. Whatever LineageOS changed since last May release (about 5,500 files had to be recompiled).
May 7, 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-05
2. Whatever LineageOS changed since last Apr release (about 7,200 files had to be recompiled).
Apr 15, 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-04
2. Whatever LineageOS changed since last Mar release (about 28,000 files had to be recompiled).
March 20, 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-03
2. Whatever LineageOS changed since last Feb release (about 20,000 files had to be recompiled).
Feb 12, 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02
2. Whatever LineageOS changed since last Jan release (about 12,500 files had to be recompiled).
Jan 8, 2023 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
2. Whatever LineageOS changed since last Dec release (about 4,400 files had to be recompiled).
Dec 11, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
2. Whatever LineageOS changed since last Nov release (about 5,000 files had to be recompiled).
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
2. Whatever LineageOS changed since last Oct release (about 5,000 files had to be recompiled).
Oct 7, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
2. Whatever LineageOS changed since last Sept release (about 5,500 files had to be recompiled).
Sept 12, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Whatever LineageOS changed since last Aug release (about 12,500 files had to be recompiled).
Aug 5, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Whatever LineageOS changed since last July release (about 4,000 files had to be recompiled).
July 8, 2022 release notes
1. July 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
2. Whatever LineageOS changed since last June release (about 1,500 files had to be recompiled).
June 11, 2022 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
2. Whatever LineageOS changed since last May release (about 9,500 files had to be recompiled).
May 7, 2022 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
2. Whatever LineageOS changed since last April release (about 11,000 files had to be recompiled).
3. Selfie camera and video no longer crash with stock camera. Thanks to @dylux for suggesting these fixes which are commits
https://github.com/retiredtab/devic...mmit/c9ac11147f83d611e006731aad7c14108f293d64
and
https://github.com/retiredtab/devic...mmit/cfa55e0478b59821f3d16501104b51ceeef8b010
April 10, 2022 release notes
1. Arpil 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
2. Whatever LineageOS changed since last March release (about 11,000 files had to be recompiled).
Mar 12, 2022 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-03
2. Whatever LineageOS changed since last Feb release (about 5,700 files had to be recompiled).
Feb 12, 2022 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-02
2. Whatever LineageOS changed since last January release (about 34,500 files had to be recompiled).
Jan 20, 2022 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-01
2. Whatever LineageOS changed since last December release (about 10,000 files had to be recompiled).
Dec 10 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2021-12
2. Whatever LineageOS changed since last November release (about 11,000 files had to be recompiled).
Nov 7 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318560
2. I enabled zram swap with size 512MB. I noticed that the last couple of months that Clash Royale would crash/close and logs showed
Code:
10-28 14:26:01.412 0 0 I [2: kswapd0: 91] lowmemorykiller: Killing 'ell.clashroyale' (6730), adj 0,
Hopefully, by enabling zram, that will stop Clash Royale from crashing/closing.
Zswap is enabled on stock Nougat SM-T350 (part of the Samsung Tab A/E family that uses same msm8916 kernel code)
https://github.com/retiredtab/andro...mmit/2a6bf385e6dfe6073fe328b7b1c563ccd60a5ede
https://github.com/retiredtab/andro...mmit/438d5d3ad20cbc98f0f8c18eb610b6268de19395
This code uses the in kernel low memory killer (lmk). I tried using the Android OS lmk, but it doesn't work very well and shows this in the log.
Code:
E lowmemorykiller: /proc/zoneinfo parse error
E lowmemorykiller: Failed to get free memory!
3. Whatever LineageOS changed since last Oct release (about 7,200 files had to be recompiled). One of these changes has removed the built in terminal program from LineageOS as AOSP deprecated this app as per
https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/304043
Oct 10 release notes
1. Oct 1 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317001
2. Added https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/316839 to fix landscape mode system UI. This patch is not yet officially merged as of Oct 10 release.
3. Whatever LineageOS changed since last September release (about 6,100 files had to be recompiled).
Sept 10 release notes
1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
3. Whatever LineageOS changed since last August release (about 6,200 files had to be recompiled).
Aug 8 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
3. Whatever LineageOS changed since last July release (about 11,500 files had to be recompiled).
4. 18.1 continues to be my daily driver since March 2021.
July 10 release notes
1. Initial public release to XDA. This is an ALPHA build.
2. July 5 security patches as per https://review.lineageos.org/q/topic:"android-11.0.0_r39"+(statuspen OR status:merged)
Reserved.
New build called lineage-18.1-20210718-UNOFFICIAL-gt58wifi.zip
July 18 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added
Code:
allow hal_health_default sysfs_charger:dir search;
allow hal_health_default sysfs_charger:file r_file_perms;
to the hal_health_default.te file.
Other than that, there are no other changes. So if you already downloaded the July 10 release and don't mind this small bug, you can wait until the August security patches before updating the rom. The August security patches and all future versions will have this bug fix incorporated.
New build called lineage-18.1-20210808-UNOFFICIAL-gt58wifi.zip
Aug 8 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
3. Whatever LiineageOS changed since last July release (about 11,500 files had to be recompiled).
4. 18.1 continues to be my daily driver since March 2021.
@retiredtab
Thanks for your work on this rom. It's been working very well.
It seems BiTGApps can no longer be downloaded.
ovalseven said:
It seems BiTGApps can no longer be downloaded.
Click to expand...
Click to collapse
Use opengapps then. Remember, this is not the correct place to ask gapps related questions. It's only for the rom. This will be the last time I mention gapps.
FAQ 13
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
retiredtab said:
Q15. Can I turn off the on screen navigation keys?
Click to expand...
Click to collapse
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
retiredtab said:
Use opengapps then. Remember, this is not the correct place to ask gapps related questions. It's only for the rom. This will be the last time I mention gapps.
FAQ 13
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
Click to expand...
Click to collapse
I was just letting you know your links didn't work.
ovalseven said:
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
I was just letting you know your links didn't work.
Click to expand...
Click to collapse
@ovalseven, the link in this thread's FAQ still works (for me, anyway) but the download link on that BiTGapps site appears not to be working. The BiTGapps thread [CUSTOM][GAPPS] BiTGApps for Android might have more information / an alternative download site.
ovalseven said:
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
Click to expand...
Click to collapse
Now added to FAQ.
If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout
Thanks for the info and for your work on this rom. Been using it all afternoon and it's running smoothly.
lpedia said:
@ovalseven, the link in this thread's FAQ still works (for me, anyway) but the download link on that BiTGapps site appears not to be working. The BiTGapps thread [CUSTOM][GAPPS] BiTGApps for Android might have more information / an alternative download site.
Click to expand...
Click to collapse
Thanks to @lpedia letting me know, but it seems the developer of bitgapps has removed his links because of some "disagreement" with some users. I'm not involved in this and don't want to be, but if people want bitgapps, they should check the link daily to see when/if the developer will re-enable his links.
So I have now removed all gapps links from my FAQ and it's up to the user now to use their favourite search engine to find whatever gapps or Aurora Store they want. And THIS will be the FINAL word I say on gapps again.
New build called lineage-18.1-20210910-UNOFFICIAL-gt58wifi.zip
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
18.1 continues to be my daily driver since March 2021.
Sept 10 release notes
1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
3. Whatever LiineageOS changed since last August release (about 6,200 files had to be recompiled).
This rom runs fantastic to anyone wondering. Easily the best running rom for t350 (i've tried them all). Thank you for your work on this.
Wikdclown said:
This rom runs fantastic to anyone wondering. Easily the best running rom for t350 (i've tried them all). Thank you for your work on this.
Click to expand...
Click to collapse
I totally agree with you! I just installed the Sept. 10th version on the 10th and it has made my tablet usable again. I will be sticking with this ROM from now on!
The ROM works very well, thank you @retiredtab !
All essential functionality works without caveats. Experimented with enabling pip and split screen and went back to this rom's default setting of being a "low memory" device, as it runs *much* smoother. Good choice of rom's default.
I ran into a couple of crashes in non-essential areas (setting a certain wallpaper crashed the settings, but then worked after reboot; turning on the hotspot then turning it off crashed settings, yet that was a pure curiosity, since there is no utility in the hotspot).
Have a question, pls. How to enable "Phone Ringtone" selection on the "Sound" page in Settings? Something in build.prop? [I use google voice as the voip app on other wifi-only tabs with same lineage version, works well, ringtone selection is there, just need to enable it in the rom for this t350 tab somehow].
Yxo 6o6uka said:
Have a question, pls. How to enable "Phone Ringtone" selection on the "Sound" page in Settings? Something in build.prop? [I use google voice as the voip app on other wifi-only tabs with same lineage version, works well, ringtone selection is there, just need to enable it in the rom for this t350 tab somehow].
Click to expand...
Click to collapse
Which wifi-only tabs give you that ringtone selection? I checked all my wifi 18.1 tablets msm8916 family, exynos 5420 and 5433 and none of them show the phone ringtone selection.
Samsung Tab Pro 8.4 SM-T320. Rom by Valera1978.
This is LineageOS 19.1, which is based on Android 12L, for variants of the Samsung Galaxy Tab A 10.1" (2016), which have models and codenames as follows:
SM-T580, with codename gtaxlwifi
SM-T585, with codename gtaxllte, along with SM-T585N0 and SM-T585C
SM-P580, with codename gtanotexlwifi, along with SM-P583
SM-P585, with codename gtanotexllte, along with SM-P585M, SM-P585Y, SM-P585N0, and SM-P588C
LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android distribution.
Some useful information for devices from China (SM-P583, SM-T585C, SM-P588C, and SM-T580 on the CHN CSC) - For unlocking the bootloader before installation, an app, "CROM Service", would need to be opened and the prompt from it accepted so that it can be unlocked, after enabling the "OEM unlock" setting in developer options. It should be available from the Galaxy Store, although I can't be 100% sure about it. In any case, an APK of it should be easy to find.
As was the case with LineageOS 18.1, I've taken over maintaining 19.1 for gtaxlwifi from @followmsi, and my 19.1 builds continue on from his 19.1 builds that were intended for use by users. To update from his builds, my builds can simply be installed on top of an existing install from his builds without doing anything further (or "dirty flashed").
For those running 18.1 or 17.1, upgrading to 19.1 is possible through the procedure I've explained before here and here (except with 19.1/Android 12 and 18.1 rather than 18.1/Android 11 and 17.1 for that second post). I highly suggest backing up any important data before trying to upgrade. In the unlikely case the upgrade fails, and it doesn't boot, data would need to be formatted.
For those who used WiFi-only variant builds on an LTE variant device, installation of a proper LTE variant build on top of an installation from a WiFi-only variant build is possible, except for a small issue you may encounter after doing so. See issue 3 in the "known workarounds and issues" section below for it.
LineageOS 19.1/Android 12 usability fixes
For those wanting to disable the widely disliked taskbar (the grey bar at the bottom with the 3 navigation buttons and shortcuts for apps docked at the launcher): Instructions for doing so are in the first section of my post here.
For enabling lockscreen rotation: Instructions for doing so are in my post here.
For those needing Google apps: Do not use heavy Google apps packages, as otherwise, you WILL have severe performance issues. Instead, use the most minimal variant of your chosen package. For example, for OpenGapps (no longer maintained officially, with no Android 12L packages, so use @ipdev's latest unofficial build available here), that is the pico variant, and for NikGapps (note that it now seems to more often be problematic, probably better using something else), that is the core variant.
Build downloads - All from 20230603 with security patch level 20230505
For gtaxlwifi: https://drive.google.com/file/d/15f1R3z-pbBTxhix8d_fBzwI1NOPHN6Bl/
For gtaxllte: https://drive.google.com/file/d/1Ba3whNROBXFn7vnpIHlWi9e9pkWR5BbA/
For gtanotexlwifi: https://drive.google.com/file/d/1MMhxvs1jNPHAgU5kDy4kaJ7AZ3MSXcLg/
For gtanotexllte: https://drive.google.com/file/d/1aDGexOX56dazYwAclICju977NAqYpAPH/
Note: If you have a revision 7 gtaxllte device (which are apparently exclusively for 2020 students in Egypt), for the current gtaxllte build to boot, the boot image here is required. It won't be needed for future builds.
For all other revisions, which are 99.9% of all devices (with the 7th revision having just that exclusive usage), the current gtaxllte build will work fine as-is.
Recoveries to use
Use my unofficial TWRP builds:
For gtaxlwifi: Image here, tar for Odin for AP slot is here.
For gtaxllte: Image here, tar for Odin here.
For gtanotexlwifi: Image here, tar for Odin here.
For gtanotexllte: Image here, tar for Odin here.
Folders for builds
Along with current builds, these contain text files with SHA256 checksums for builds, and folders containing few previous builds.
For gtaxlwifi: https://drive.google.com/drive/folders/1S3NRiTP2jr9gRtSMKoKoaoMu75g_FJM4
For gtaxllte: https://drive.google.com/drive/folders/1ZFkGkVkIohsNFDi0jNF2-Yhz7Sbg5GT4
For gtanotexlwifi: https://drive.google.com/drive/folders/11pcp9NZf0ovelvT7oxfhoem6-utpSao8
For gtanotexllte: https://drive.google.com/drive/folders/1AICJ1UcnZ5a-slcgd-iGQ9mpk9J8Evmd
Changelogs
Builds for 20230603:
Latest changes from LineageOS, including the 20230505 Android security updates.
Support for revision 7 gtaxllte devices, which were apparently exclusively for 2020 students in Egypt, has been added. (Note: Boot image here required for a change needed to boot on the 7th revision for the 20200603 build, the change will be included in all future builds making it unnecessary for them.)
Previous releases
Builds for 20230419:
Latest changes from LineageOS, including the 20230405 Android security updates.
Linaro's new SLSI BSP (Board Support Package, containing sources for HWC and some other stuff) sources are now used - Much more up-to-date than the previously used sources, and there's possibly a small improvement in performance.
The OMX hardware video decoder and encoder libs are now built from the new Linaro BSP sources - With that, playback of HEVC videos is fixed in Chrome and other Chromium-based browsers.
Some updates from the 4.9 Android common kernel as of March have been applied to the kernel.
The wireguard kernel module has been added back - I silently removed it in the previous builds since it was unusable due to a now fixed device lockup bug that caused almost total unresponsiveness after enabling a wireguard VPN.
Builds for 20230128:
Latest changes from LineageOS, including the 20230105 Android security updates.
[LTE variant-specific] Issues with mobile networking not working have been fixed.
[gtanotexllte-specific] Additional issues with bootlooping and rebooting during the boot animation have been fixed.
Open source aptX encoder libraries, from sources adapted from Qualcomm's recently upstreamed to AOSP open source code, are now used.
Builds for 20221231 and 20230101:
Latest changes from LineageOS, including the 20221205 Android security updates.
Some more miscellaneous cleanups have been done.
Initial builds for gtaxllte and gtanotexllte.
Many updates from the 4.9 Android common kernel have been applied to the kernel.
Builds for 20221127:
Latest changes from LineageOS, including the 20221105 Android security updates.
Builds for 20221020:
Latest changes from LineageOS, including the 20221005 Android security updates.
Performance of animations has been improved slightly further.
Configuration files for media codecs and profiles have been updated from Samsung's M105FDDS4CVG1 firmware, and audio codec support might be improved slightly (as the Codec 2.0 media codec framework has been fixed and is now used).
Some updates from the 4.9 Android common kernel have been applied to the kernel.
Builds for 20220929:
Latest changes from LineageOS, including the 20220905 Android security updates.
The torch has been fixed.
Performance of animations and responsiveness has been improved slightly.
Some updates from the 4.9 Android common kernel have been applied to the kernel.
[SM-P580/gtanotexlwifi only, already fixed in T580 builds long ago] An issue where the displays backlight would be turned off completely when setting very low brightnesses, causing nothing to be visible on the display (unless very faintly if you shine a torch or a different bright light source on it), has been fixed.
The WiFi drivers RX wakelock feature has been disabled - Heavy battery drain that occurred in sleep when connected to certain WiFi networks due to "qcom_rx_wakelock" wakelocks has been fixed.
Builds for 20220824:
Latest changes from LineageOS, including the 20220805 Android security updates, and a fix for "Intent Filter Verification Service" crashes that occurred in few/some cases with no Google apps or with MicroG.
Some things that appeared that are only relevant for devices with mobile networking (such as the baseband version and SIM status sections in About tablet in settings) no longer appear.
The ZRAM size has been increased to 2GiB, and the swappiness is now set to 100.
A higher frequency (1246MHz, was 902MHz previously) is now set for the interactive CPU governors "hispeed_freq" value - This improves responsiveness slightly.
The sepolicy containing device-specific SELinux rules has been improved slightly.
Yet more miscellaneous cleanups have been done.
Some updates from the 4.9 Android common kernel have been applied to the kernel.
Builds for 20220724:
Latest changes from LineageOS, including the 20220705 Android security updates.
Some updates from the 4.9 Android common kernel have been applied to the kernel.
Builds for 20220620:
Latest changes from LineageOS, including the 20220605 Android security updates.
Network traffic monitoring now works (as some changes reverting the removal of the old, non-eBPF, method of doing it that the old 3.18 kernel only supports have been applied, thanks to @rINanDO for them!).
One of Lineage's changes to the default keyboard, likely to be causing a problem where the keyboard appears full screen with no keys in very few cases, has been reverted.
Many updates from the 4.9 Android common kernel, and some from a few other sources, have been applied to the kernel.
The issue where trying to power off, or reboot to recovery or download mode, would sometimes cause a normal reboot has been fixed.
A small fix to the kernel has been applied that fixes occasional soft reboots, that were caused by a change I made a very long time ago that had only started causing such soft rebooting problems with Android 12.
Builds for 20220523:
Latest changes from LineageOS, including the 20220505 Android security updates and an option for disabling the taskbar.
The problem where enabling the "Enable on-screen nav bar" option at Settings -> System -> Buttons caused touchscreen input to be disabled has been fixed.
Native support for IPsec tunnels has been enabled.
Support for Vulkan compute is now declared.
A new custom version of the open source Samsung audio HAL from Lineage's android_hardware_samsung repository is now used, rather than the stock, heavily-patched, proprietary Samsung audio HAL, with some fixes for a problem that made it unusable before where occasionally, audio would get outputted from both the speakers and the headphone jack.
The playback and low-latency capture period sizes have been reduced to 128 in the open source audio HAL, which reduces audio latency.
Pro audio support is now declared, since with the reduced period sizes, as well as with the use of the open source audio HAL, round-trip audio latency has been reduced enough for it.
Many updates from the 4.9 Android common kernel have been applied to the kernel.
Several fixes to the Sony HID driver in the 4.9 Android common kernel have been ported over to the kernel - Sony DualShock 4 controllers should now work properly.
Initial builds for 20220416 (This changelog continues on from @followmsi's last 19.1 build that was intended for use by users):
Latest changes from LineageOS.
SELinux is now set to be enforcing after having addressed new SELinux denials with 12.
Assisted GPS has been fixed.
ADB is no longer enabled by default or on boot.
The tablet product characteristic has been added back after being mistakenly removed - Places where the device was referred to as a phone (such as the "About phone" section in settings) will now refer to it as a tablet again.
The Widevine DRM blobs have been updated to 1.4 blobs from the latest stock firmware for the Google Pixel 3a XL.
A new wcnss_filter binary built from sources is now used to properly fix an issue where Bluetooth couldn't be re-enabled after enabling and disabling it once, and the old workaround for it has been removed.
Some other miscellaneous cleanups have been done.
There are a few updates from the 4.9 Android common kernel and Samsung's A600FNXXU9CVB1 kernel sources to the kernel.
An issue where the displays backlight would be turned off completely when setting very low brightnesses, causing nothing to be visible on the display (unless very faintly if you shine a torch or a different bright light source on it), has been fixed.
Known issues and workarounds/fixes (if any)
Issue 1 - Squashed (rear) camera previews, and videos at some resolutions: Camera previews for images to be taken at resolutions with aspect ratios other than 16:9 using the rear camera are squashed from 16:9 (while final saved images at any resolution are unaffected by any squashing), and videos taken at some resolutions are affected by similar issues with squashing in previews, and, in a smaller set of resolutions, also in final saved video files. (Note that these issues don't affect the front-facing camera)
Somewhat of a workaround: Use resolutions at which there are no issues with squashing from 16:9.
Issue 2 - LTE variants - In-call echo: There may be echoing that can be heard by the person you're calling while using speakers.
See my post here for more on this issue.
(Temporary) Issue 3 - APN issues on LTE variant devices - after installation of a proper LTE variant build on top of an installation previously from a WiFi-only build: On an LTE variant device, after installing a proper LTE variant build on top of an existing installation from a WiFi-only build, when going to APN settings, at Settings -> Network and Internet -> SIMs -> Access point names, an error is displayed that APN settings cannot be changed by the current user (or something similar).
Fix: Tap the 3-dot menu at the top right, and select "Reset to default", and then select the relevant APN.
(Minor cosmetic) Issue 4 - Incorrect model displayed on devices with region-specific model numbers
I'll take a look at fixing this issue up later on.
Issue 5 - LTE variants - Bluetooth calling doesn't work: There isn't any call audio over Bluetooth audio devices. Any call audio with a Bluetooth audio device connected will be routed to the built-in speakers.
Issue 6 - LTE variants - No VoLTE support: VoLTE currently can't work on any Samsung devices due to Samsung's proprietary implementation in stock firmwares not working on AOSP.
Something notable is that with Android 12, encrypted data can't be decrypted in TWRP recovery. That problem can only be fixed within TWRP, but with the fixes only being in Android 12L TWRP sources, which we can't build our TWRP builds from due to issues, it continues to exist.
To report further issues, get a log from logcat and dmesg. If you're unsure on how to get either, there's good documentation out there for how to do so.
Sources
A manifest containing all of the necessary repositories to make builds for all of the variants is in the repository here on branch lineage-19.1.
Thanks to:
@Valera1978 - for all of the previous work for the T580 and T585 long ago.
@followmsi - for fixes to various issues and other improvements, for useful information, and for working with me on much of this stuff.
Anyone who has previously tested anything new I've put up for testing, reported results, and provided information needed for me to get it working if it was necessary.
The Lineage team - for the Android distribution itself.
...and everyone else who has worked on anything that is in use.
TALUAtXDA said:
Changelogs:
Initial releases for 20210416 (This changelog continues on from @followmsi's last 19.1 build that was intended for use by users):
The tablet product characteristic has been added back after being mistakenly removed - Places where the device was referred to as a phone (such as the "About phone" section in settings) will now refer to it as a tablet again.
The Widevine DRM blobs have been updated to 1.4 blobs from the latest stock firmware for the Google Pixel 3a XL.
Click to expand...
Click to collapse
That's great news TALUtXDA! Congrats on 19.1!
I had been hoping for the Widevine L1 on 18.1. And I was also noticing the "About phone" thing, on 18.1
I guess those fixes were only possible on 19.1
Just curious, does 19.1 fix that crash when we click on settings from the quick pulldown?
Gorilla Daddy said:
That's great news TALUtXDA! Congrats on 19.1!
I had been hoping for the Widevine L1 on 18.1. And I was also noticing the "About phone" thing, on 18.1
I guess those fixes were only possible on 19.1
Just curious, does 19.1 fix that crash when we click on settings from the quick pulldown?
Click to expand...
Click to collapse
Thanks!
It isn't possible to have the L1 Widevine security level. It would be possible to get L1 to appear to work (meaning L1 is reported to be the security level), but it would actually just get dropped down to L3.
For that "About phone" thing, that small problem was just caused by a mistake I made. For 18.1, it only exists in my last builds since only those are affected by it. It'll be fixed in the same way I've fixed it in my new 19.1 builds in my next 18.1 builds.
Yes, the crashes that happened when tapping on the settings button or holding the quick settings tiles on the notifications pulldown once after boot in 18.1 no longer occur under 19.1.
TALUAtXDA said:
It isn't possible to have the L1 Widevine security level. It would be possible to get L1 to appear to work (meaning L1 is reported to be the security level), but it would actually just get dropped down to L3.
Click to expand...
Click to collapse
I think stock Android 6 on the tablet had Widevine L1. Didn't it? I don't know how it all works, but I do wonder what is missing. When you posted that you had used the Pixel 3a blobs, I had thought that was whatever blackbox did the widevine L1. I see I was wrong. I guess whatever blobs and whatnot from Android 6 aren't compatible with our LineageOS setups?
If you could explain a bit more of the Widevine internals as it relates to L1 on these tablets, just to cure my ignorance, I'd appreciate it. I've been wondering about it for a while. I can program in assembly language and C, so don't pull any punches.
This is great, thx so much!
One question for installation: you described how to switch from followmsi's 19.1 build to your's but if coming from your last 18.1 (!) build what steps are needed to upgrade to your 19.1 build?
Happy Easter!
I am new to these ROM but am looking for one that will run games better. I play Final Fantasy Brave Exvius and the game continues to need more power to run it. I have a Samsung Galaxy Tab A T580 and was wondering if this ROM will run the game faster? The only app I installed is the game. Besides that, I use Chrome for web browsing but nothing else. In the past, resetting the tablet to factory would help a little but not anymore. Will this help for what I am looking for? If not, I am open to all suggestions short of buying a new one at this time. Thanks
Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
What is this bottom bar?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rapidm said:
Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
What is this bottom bar?
View attachment 5590777
Click to expand...
Click to collapse
Hi rapidm, could you describe plz how you exactly updated from 18.1?
Uluru25 said:
Hi rapidm, could you describe plz how you exactly updated from 18.1?
Click to expand...
Click to collapse
See https://forum.xda-developers.com/t/...d-sm-p580-gtanotexlwifi.4274293/post-86744403
Uluru25 said:
Hi rapidm, could you describe plz how you exactly updated from 18.1?
Click to expand...
Click to collapse
I did those steps: https://forum.xda-developers.com/t/...rdroidandroid-12-1-v8-4.4190313/post-86754819 but with the lineage os 19 build.
Gorilla Daddy said:
I think stock Android 6 on the tablet had Widevine L1. Didn't it? I don't know how it all works, but I do wonder what is missing. When you posted that you had used the Pixel 3a blobs, I had thought that was whatever blackbox did the widevine L1. I see I was wrong. I guess whatever blobs and whatnot from Android 6 aren't compatible with our LineageOS setups?
If you could explain a bit more of the Widevine internals as it relates to L1 on these tablets, just to cure my ignorance, I'd appreciate it. I've been wondering about it for a while. I can program in assembly language and C, so don't pull any punches.
Click to expand...
Click to collapse
It would also work on the Android 8.1 stock firmware.
The Widevine DRM HAL, which is what I updated, is part of it. There's also a liboemcrypto.so blob, and Mobicore/the Trustonic TEE, along with relevant "trustlets" for it. WIth a working combination of the Widevine DRM HAL, liboemcrypto blob, Mobicore blobs, and "trustlets", it would be possible for the Widevine security level to be reported as L1. But, still, it would be dropped down to L3.
The commit message for the commit here removing the liboemcrypto blob and also replacing two other DRM-related blobs for Exynos 7580 devices describes, in actuality, Samsung as disabling L1 on devices that are modified in any way. Who knows how that happens or where along the line it does, seeing as all low-level device-specific stuff is, of course, undocumented.
I don't think it's worth continuing discussion on that topic. It's dead-end and I personally have a very poor understanding of it all, as I imagine almost everyone else does. There's no getting back the L1 security level.
rapidm said:
Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
What is this bottom bar?
Click to expand...
Click to collapse
That's the new, pretty intrustive and seemingly also buggy, taskbar in Android 12L.
The only way to somewhat get rid of it is to switch to gesture navigation. Oddly, there's no three buttons for navigation on your taskbar there, so I'm not sure if you have it enabled already, and just need to hold down on it to switch to a navigation "pill".
That can most easily be done by running this command in an ADB shell or a shell with root access otherwise (run `su` in any other type of shell, such as one through an app, to get root access):
Code:
cmd overlay enable com.android.internal.systemui.navbar.gestural
With it, a small white pill, along with some space around it, replaces the taskbar for navigation. Holding it down would switch back to a taskbar, and holding it down again would switch back to that pill. Note that as it's gesture navigation, you'd have to get used to either using the gestures or ignoring that they're there, especially since they interfere with some gestures in some apps.
Unfortunately, at the moment, we don't have anything else besides switching to gesture navigation to get around it. This all came down from Google/AOSP (the Android Open Source Project) itself. Here's hoping Lineage makes improvements or improvements are made under AOSP to this navigation stuff.
TALUAtXDA said:
See https://forum.xda-developers.com/t/...d-sm-p580-gtanotexlwifi.4274293/post-86744403
Click to expand...
Click to collapse
Hi TALUaAtXDA, might be beneficial for other users to have this very valuable info already given or at least linked in your very first post, don't you think so?
Uluru25 said:
Hi TALUaAtXDA, might be beneficial for other users to have this very valuable info already given or at least linked in your very first post, don't you think so?
Click to expand...
Click to collapse
My Sam Galaxy Tab A T580 is totally stock and updated. Will this ROM work for me? Also, will it help with gaming? Sorry I am a newb when it comes to this stuff. Sorry, I am confused by all the bulds and if I need to install a certain one before I can install the newest build.
@ TALUAtXDA and @followmsi thank you for your hard work for this tablet, i hope lineage find a way to remove this nav bar, everything seems to work for the moment
rapidm said:
Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
What is this bottom bar?
View attachment 5590777
Click to expand...
Click to collapse
This is a big problem for me too. I've already tried using the command with su in a terminal and it doesn't work at all.
charcutero said:
This is a big problem for me too. I've already tried using the command with su in a terminal and it doesn't work at all.
Click to expand...
Click to collapse
Long click makes it a line but if you click the hardware buttons then it returns to the default full form.
rapidm said:
Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
What is this bottom bar?
View attachment 5590777
Click to expand...
Click to collapse
I guess that's the taskbar which was introduced in Android 12L. Android 12L is designed for foldables and devices with large screens, so with a taskbar, you could speed up multi-tasking.
I found a way to remove the taskbar. Go into Developer Options, go to Minimum Width, and set it to any value below 600 dp, which is the minimum value to trigger the taskbar. Please post the outcome.
SupremeKing5810 said:
I found a way to remove the taskbar. Go into Developer Options, go to Minimum Width, and set it to any value below 600 dp, which is the minimum value to trigger the taskbar. Please post the outcome.
Click to expand...
Click to collapse
400 dpi 640 dpi
It does not save any DPI data for me, it returns to 640.
Even if you hide the bar, it reappears randomly.
The ROM is going great, but android 12 is a bit cumbersome. Buttons and slide very large.
PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom. If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. camera
What doesn't work
1. selinux is permissive. I have tried to make this build enforcing for weeks, but when I do, the OS doesn't boot and there is no adb logcat output despite making an "eng" build. Without adb logcat output, it's virtually impossible to determine what is wrong and I'm not spending anymore time on it. If having enforcing mode is important to you, use my 18.1 builds.
2. keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
3. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread. As a courtesy to gapps users, if you want to talk about gapps, I have opened a new thread at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
so you may discuss gapps wrt to the msm8916 platform. I will NOT be participating in that thread as I do NOT use gapps.
Source Code
Links and instructions on how to build this rom from source are in post #2 FAQ 1.
Thanks
1. LineageOS team for source code.
2. Kyle Harrison
- looking through the adb logcat and suggesting that my binder code was too old to work with Android 12's keystore2 code
- for the graphics and legacy camera patches to allow msm8916 to work with Android 12
- for his Motorola LineageOS 19.1 device trees so I could use his patches as a template for msm8916
3. @tarkzim
- adding back audio hal 2.0 and legacy camera hal 1.0 into the LineageOS trees
- helping me think through the msm8916 random reboots which was due to the TCP/IP patches
- maintaing and updating his repos so I can study them for learning purposes
4. @lpedia
- testing gapps, video conferencing, stability, reliabilty, paid apps
- helping verify my 19.1 repos are buildable by anyone
FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2021 to Aug 2022 running into bug after bug. The least you can do is spend a few minutes reading everything before posting.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
https://github.com/retiredtab/android_kernel_samsung_msm8916
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8916-common/tree/lineage-19.1
https://github.com/retiredtab/android_device_samsung_gt58ltebmc/tree/lineage-19.1
https://github.com/retiredtab/device_samsung_gte-common/tree/lineage-19.1
The vendor tree files are at
https://github.com/retiredtab/android_vendor_samsung_gt58ltebmc
https://github.com/retiredtab/vendor_samsung_msm8916-common/tree/lineage-19.1
The manifest.xml (or roomservice.xml) and build instructions for 19.1 are at
https://github.com/retiredtab/LineageOS-build-manifests
Q2. Is this ALPHA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid March 2022 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this 19.1 ROM BY ITSELF (no gapps, magisk, etc) and see if you like it. If you do like it and want to add gapps then see FAQ 12.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps. You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use TWRP 3.5.2_9. Get it from
https://forum.xda-developers.com/t/...-0-v7-10-android-11-galaxy-tab-a-8-0.4293577/
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. I don't have the time to help newbies, so please do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Will you still build 18.1 for this device?
A10. Yes, for rest of 2022, but I will make a decision in January 2023 on how 18.1 and 19.1 will be maintained. If you like to help by building 18.1/19.1, please let me know.
Q11. Do I need to erase everything and format my data?
A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 19.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Q12. What gapps should I use?
A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
In addition, some of the gapps may not install properly when using TWRP and say "cannot /mnt/system". For those cases, please use the LineageOS recovery.img you can download from
https://sourceforge.net/projects/retiredtab/files/SM-T350/LineageOS-recovery/
By flashing the LineageOS recovery.img, it will overwrite the existing TWRP and you will get a different UI.
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I WILL NOT answer any questions regarding gapps. This thread is about the rom, not gapps. Android does not depend on gapps in order to work.
Questions about gapps, for your courtesy, should be asked at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
Q14. Why isn't my post answered or ignored?
A14. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q16. What speed up/optimization tips do you suggest?
A16.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
4. Use a web browser like Brave that has built in adblock and privacy features.
5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
6. Look for apps that are open source, ad free and lightweight.
7. Remove all unused quick setting "bubbles" from the quick pull down menu. I only need and have 6.
Q17. Does this rom support Magisk for root?
A17. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.
Q18. Will this rom ever become official?
A18. With 19.1, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/
Also, I don't want the responsibilities that come with being an official maintainer.
Q19. What is the difference between this rom and others?
A19. This rom tries to be pure LineageOS with little to no modifications.
Q20. Will there be any major 19.1 code modifications in the future?
A20. I don't anticipate any major modifications. There may be some small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 19.1 is working.
Q21. Why did you fork the device and vendor trees for 19.1?
A21. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.
In addition, since I'm building SM-T350, SM-T357W, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not.
I have completely decommonized and rearranged the 19.1 msm8916-common tree so it's easier for me to maintain and build.
Q22. Can you build a variant of this device? For example, a LTE or S-pen version.
A22. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.
Q23. Can I load this rom on a variant devivce like LTE or S-pen version?
A23. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q24. How do I know if I have a BOE panel?
A24. Some ST-350 tablets have a BOE display panel. In order for it to work with TWRP and any custom rom, you must have the correct bootloader installed on a BOE panel otherwise you will see a black/blank screen. To check to see if you have a BOE panel, open a terminal and
Download an app called devcheck by flar2. In the hardware tab, scroll down to the display section and look at the panel.
If you see BOE anywhere in that string, then you have a BOE panel.
There is a fix as documented at post #41
https://forum.xda-developers.com/t/...galaxy-tab-a-8-0.4158163/page-3#post-83488241
This fix loads the Android 6.0 stock rom bootloader so that it works with TWRP and the custom rom.
Q25. Why is this NOT a GO build when 18.1 was a GO build.
A25. A GO build uses less DRAM, disk space and supposed to be better suited for devices with 2GB DRAM or less. I have no idea whether it's true or not vs a NON GO build, but I figured I would try a GO build for 18.1.
With Android 12L, the settings panel requires a split screen feature which is not in the GO build. When I made a 19.1 GO build in March 2022, half the setting screen would not show up so. When I made a NON GO build, then both sides the settings panel showed up on the screen.
Q26. What major code changes are in 19.1 vs 18.1.
A26.
- iptables has been removed in favour of ebpf
- keystore v1 has been replaced with keystore v2 which requires that the binder calls have some built-in security
- audio hal 2.0 has been deprecated
- legacy camera hal 1.0 and snap app have deprecated
Q27. I don't like the taskbar, how do I turn it off?
A27. Choose settings, type task into the search bar. Choose enable taskbar and disable taskbar. This will leave the on screen nav bar. If you want to disable that, go to settings, system, gestures, system navigation, gesture navigation.
Q28. Okay, I understand the consequences and that this is ALPHA rom and willing to take the risks outlined, now where can I find the rom?
A28. You can download it from https://sourceforge.net/projects/retiredtab/files/SM-T350/19.1/
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
19.1 has been my daily driver since March 2022.
May 6, 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-05
2. Whatever LineageOS changed since Apr 5 patches. About 7,400 files had to be recompiled.
Apr 13, 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-04
2. Whatever LineageOS changed since Mar 5 patches. About 23,000 files had to be recompiled.
March 18, 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-03
2. Whatever LineageOS changed since Feb 5 patches. About 24,000 files had to be recompiled.
Feb 12, 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-02
2. Whatever LineageOS changed since Jan 5 patches. About 12,500 files had to be recompiled.
Jan 7, 2023 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-01
2. Whatever LineageOS changed since Dec 5 patches. About 4,400 files had to be recompiled.
Dec 9, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-12
2. Whatever LineageOS changed since Nov 5 patches. About 4,700 files had to be recompiled.
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11
2. Whatever LineageOS changed since Oct 5 patches. About 5,400 files had to be recompiled.
Oct 6, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-10
2. Whatever LineageOS changed since Sept 5 patches. About 7,200 files had to be recompiled.
Sept 11, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
2. Switched to different timekeep repo that works with Android 12 and up.
3. Whatever LineageOS changed since Aug 5 patches. About 9,500 files had to be recompiled.
Aug 9, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-08
2. Initial ALPHA release to public.
Reserved.
Thanks for making this! So far I haven't found any other issues than the ones you have listed. Stability so far is pretty solid too. Had no idea a12 had a taskbar until today, I quite like it.
One thing, the twrp you have listed does not seem to work by default, as the install script thinks its a different device. I stuck with using nubianprince's build and it worked fine. If people do the research they're supposed to though they can probably noodle around that .
lividhen said:
Thanks for making this! So far I haven't found any other issues than the ones you have listed. Stability so far is pretty solid too. Had no idea a12 had a taskbar until today, I quite like it.
Click to expand...
Click to collapse
I like the taskbar, but disabling it is a FAQ in many 19.1 threads.
lividhen said:
One thing, the twrp you have listed does not seem to work by default, as the install script thinks its a different device.
Click to expand...
Click to collapse
Oops, that's a cut and paste error. I put the T357 TWRP in T350 thread and vice versa. Thanks I have fixed that now. That's what I get for announcing 7 (yes, seven) 19.1 roms in a 24 hour span.
lividhen said:
I stuck with using nubianprince's build and it worked fine. If people do the research they're supposed to though they can probably noodle around that .
Click to expand...
Click to collapse
Yes, my FAQ now correctly points to @nubianprince's TWRP build. I've been using that one as well. It works so I haven't bothered to make an updated version. It's the same build that I recommended in my 18.1 FAQ as well.
Thanks for catching my cut and paste TWRP error and glad you find the 19.1 build working well so far.
Holy crap! 7?!
You have been very busy.
Also I don't know if this was you or if this was the lineage team, but thank you to whoever made the lowest android setting brightness actually be 1 on the soc lcd block instead of 5.
(I swear there is a name for when a device is mounted like that but I can't remember, eg /sys/devices/soc.0/1a00000.qcom,mdss_mdp/qcom,mdss_fb_primary.132/leds/lcd-backlight/brightness is the hardware brightness value I think)
Just saw it, will flash and will reply with an update later
John007778 said:
Just saw it, will flash and will reply with an update later
Click to expand...
Click to collapse
There are definitely bugs but the name says it but it booted
Why is the file size displayed as 558.8MB on the download page, but only 533MB when it is actually downloaded? Is this normal?
uOySsElNu said:
Why is the file size displayed as 558.8MB on the download page, but only 533MB when it is actually downloaded? Is this normal?
Click to expand...
Click to collapse
Yes it is. Source forge is funky. I am not sure if they somehow calculate the file size differently, or store it different. I think androidfilehost.com does this too. If you want to check it, click the (i) on the right side of the file on source forge to get some checksums.
uOySsElNu said:
Why is the file size displayed as 558.8MB on the download page, but only 533MB when it is actually downloaded? Is this normal?
Click to expand...
Click to collapse
Do "man ls" and you know why.
Bash:
gt58wifi:/sdcard $ ls -alh lineage-19.1-20220809-UNOFFICIAL-gt58wifi.zip
-rw-rw---- 1 root everybody 533M 2022-08-09 18:00 lineage-19.1-20220809-UNOFFICIAL-gt58wifi.zip
gt58wifi:/sdcard $ ls -al lineage-19.1-20220809-UNOFFICIAL-gt58wifi.zip
-rw-rw---- 1 root everybody 558839729 2022-08-09 18:00 lineage-19.1-20220809-UNOFFICIAL-gt58wifi.zip
lividhen said:
If you want to check it, click the (i) on the right side of the file on source forge to get some checksums.
Click to expand...
Click to collapse
The above is the correct answer. Each time I upload a file, I check the sha1sum on my local drive to make sure it matches with the uploaded sha1sum. While sha1sum takes longer than md5, it's more "tamper" resistant.
The build process also includes a sha256sum file, but based on other rom download stats, very few people download that sha256sum file to check the integrity of the download. And yes, doing a sha256sum takes longest of the three.
To anyone wondering how this performs compared to the 18 build, it runs just as good. So dont let the alpha scare you off. I have been using for 3 days now and haven't encountered any issues.
Thank you for your continued work on these ROMS.
tried turning it on today and it's bootlooping, will try to send the log
my tab boot looped when i was using ur other custom lineage 18.1 rom, and when i tried to re-flash using this new rom it is still boot looping, what do you think the problem is??
Tested dirty flash update from your last LineageOS 18.1 build to your 19.1 build on a T355Y device.
Confirmed working.
F-Droid will lose privileged extension and Aurora services will be gone though, but I easily re-installed via adb root.
Root manager (Lygisk) is also lost but is easily re-installable via TWRP 3.5.2_9-0 recovery. Now confirmed working with Lygisk version 25.1
In Aurora Store, I reviewed the blacklist because upgrading to Android 12 has a few extra bits and pieces which are sometimes "updatable" via Google Play Store but I didn't want to be interfered with during automatic app updates.
Nova launcher required permission confirmation again for notification badges and my custom keyboards needed permissions again too, so maybe other apps with permission requests might need to be granted again.
Thanks for supporting this device. I don't really use it for much other than as an occasional ebook reader, but it is fun to show friends that it is running Android 11 (now 12) when they see it on the coffee table and that old devices can have an extended life.
Hi @retiredtab
First of all, thanks for all your help and hardwork in keeping Galaxy Tab A devices alive.
I am trying to build your sources to start development for my SM-P555 device and following the instructions detailed in your https://github.com/retiredtab/LineageOS-build-manifests/blob/main/191-build-instructions.txt
While executing https://github.com/retiredtab/LineageOS-build-manifests/blob/main/191-build-instructions.txt#L43, I am hitting this prompt and seeking your advice on what needs to be done.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Many thanks!
psuryatej said:
While executing https://github.com/retiredtab/LineageOS-build-manifests/blob/main/191-build-instructions.txt#L43, I am hitting this prompt and seeking your advice on what needs to be done.
Click to expand...
Click to collapse
Please start a new thread called "How to build 19.1 for SM-P555" in the Q&A subforum.
New build called lineage-19.1-20220911-UNOFFICIAL-gt58wifi.zip
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
19.1 has been my daily driver since March 2022.
Sept 11, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
2. Switched to different timekeep repo that works with Android 12 and up.
3. Whatever LineageOS changed since Aug 5 patches. About 9,500 files had to be recompiled.