LineageOS 20.0 64-bit for Samsung Galaxy Tab A 10.5 (2018) WiFi
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
By using this ROM, you acknowledge that you understand what running work-in-progress software means. You might lose all your data stored on the device due to a bug, the device might freeze / crash at any time, nothing is guaranteed; you are basically a beta tester. Also, this is my personal project which I decided to share here, I'm not a developer but an average user like you. Most likely I can't and will not solve your issues with VoLTE not working, Angry Birds crashing, etc.
Installation:
-----
Notes for SM-T595 users
The ROM has been modified to work on the LTE variant too, with the same level of functionality as the WiFi-only variant. This means that the LTE modem will not be usable in this ROM, and the device will appear as SM-T590 everywhere.
Also, SM-T595 has lots of hardware versions with different partition sizes, so there is a possibility that the installer will fail with one of the following error messages: E1001: Failed to update system image / E2001: Failed to update vendor image.
In case it fails, I will need the output of the following commands to make the installer compatible with that specific version too:
adb shell blockdev --getsize64 /dev/block/by-name/system
adb shell blockdev --getsize64 /dev/block/by-name/vendor
-----
- Reboot the tablet in download mode
- Flash TWRP in the AP slot using Odin
- Right after Odin finished flashing, hold Volume Up while the tablet is rebooting to get into TWRP
- Skip the warning by swiping to allow modifications
- Wipe -> Format Data -> type yes and confirm
- Reboot -> Recovery
- Skip the warning again
- On your PC, open a command prompt and copy LineageOS to the device using adb push lineage-20.0-20230514-UNOFFICIAL-gta2xlwifi.zip /sdcard/
- Alternatively, you can use a Micro SD card or USB OTG, MTP isn't recommended- In TWRP, select Install -> lineage-20.0-20230514-UNOFFICIAL-gta2xlwifi.zip and swipe to confirm
- Optionally, you can install Magisk now, make sure to use the latest version from GitHub
- Optionally, you can install GApps now but Aurora Store with MicroG is a better alternative, they use way less RAM than Play Services
Downloads:
LineageOS 20.0:
https://github.com/UDPSendToFailed/OTA/releases
TWRP 3.7.0:
https://github.com/UDPSendToFailed/twrp_device_samsung_gta2xlwifi/releases
Changelog:
2023. 05. 14.
Edit: Not recommended to download. This build has issues with WiFi after reboot because of the in-kernel WLAN driver change which I did as an attempt to fix the randomly occurring kernel panics. As it turned out, the WLAN kernel driver has nothing to do with the random reboots, so I will revert to the previous configuration in the next build.
- Switched to in-kernel WLAN driver
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-04-17+before:2023-05-14)
- May security patch
Spoiler: More changelogs...
2023. 04. 17.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-04-05+before:2023-04-17)
- April security patch
2023. 04. 05.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-02-27+before:2023-04-05)
- Switched to LineageOS-UL for frameworks_av and frameworks_base
- March security patch
2023. 02. 27.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-01-24+before:2023-02-27)
- February security patch
2023. 01. 24.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2022-12-28+before:2023-01-24)
- January security patch
2022. 12. 29.
- Synced with the latest LineageOS sources
- December security patch
2022. 11. 15.
- Synced with the latest LineageOS sources
- November security patch
2022. 10. 05.
-----
!TWRP update and data wipe is required to enable FBE!
Steps to update from previous versions:
- Download TWRP 3.7.0
- Update TWRP using Odin
- Boot into TWRP -> Wipe -> Format Data -> type yes and confirm
- Reboot -> Recovery
- Flash the latest ROM zip (20221005)
-----
- Enabled FBE (File-Based Encryption)
- Fixed some Bluetooth-related issues
- New camera app with video recording support
- Synced with the latest LineageOS sources, most of the features from 19.1 have been merged
- October security patch
- TWRP: Updated to the latest 12.1 branch
- TWRP: FBE decryption support
2022. 09. 30.
-----
LineageOS 19.1 (Android 12L) builds are now discontinued as it would be complicated to keep testing an older version, and I don't have a build server to store and update the source code either. Personal builds can still be done by anyone who wants to keep using 19.1, all the required sources are available on my GitHub.
-----
- Added Signature Spoofing support, LSPosed and FakeGApps aren't required anymore for MicroG
- Added Natural and Boosted display color profiles
- Extended Night Light color temperature range
- UI and color flickering has been fixed
- The Restrict USB option under Settings -> Privacy -> Trust is now working properly
2022. 09. 16.
- Significantly improved multitasking performance with proper ZRAM setup
(Random reboots might still happen, please report them with a description of what caused the crash and /proc/last_kmsg & logcat output attached)
- Added KTweak script (more info here and here)
- Added Dolby Settings
- Added Memory Usage stats to App Info in Settings
- Added audioloader
(Experimental quad speaker mode, can be enabled with running audioloader in Terminal Emulator or adb shell. To revert the temporarily set parameter, restart the tablet. Ideas on how to fix the sound quality are welcome)
- Fixed Network Speed indicator and Data Usage stats
- Disabled ALAC codec support as it had a critical CVE vulnerability
- Reverted to SkiaGL renderer as SkiaVK had issues with WebView v104+
- Removed some LTE-only features
- September security patch
2022. 08. 14.
- Added System Navigation options under Settings -> System -> Gestures
- Added theme color customization under Settings -> Wallpaper & Style
- Merged changes from various msm8953-based device trees
- August security patch
2022. 07. 12.
- Added CRT screen off animation
- Added tinymix (in case anyone wants to experiment with fixing the quad speakers)
- Added hidden and protected apps feature to the launcher
- Added pure black theme option
- Light theme changes
- Removed Audible app (Samsung bloatware from the odm partition)
- July security patch
2022. 06. 12.
- Headphone jack fixed
- Microphones fixed
- Double Tap to Wake should work reliably now
- Switched to Vulkan renderer to improve the smoothness of the UI
- June security patch
2022. 05. 29.
- MTP fixed
- Widevine DRM fixed
- Removed the "internal problem" warning on boot
- TWRP updated to 3.6.2
2022. 05. 25.
After a long time without updates, a new, non-GSI version is here!
- Freezes and crashes have been eliminated
- Keystore is fixed so you can use a screen lock
- This update will give your device an extra 106MB of RAM (by freeing up the memory that was allocated for the non-existent modem)
- MSM hotplug is enabled by default to improve the battery life by dynamically powering down cores based on CPU load
- May security patch
2022. 04. 08.
- Device type changed to tablet
- April security patch
Known issues:
- WiFi hotspot crashes
- Bluetooth audio
- 2 of 4 speakers are working
- GPS
- Freezes / crashes with some SD cards, in case the ROM installation fails with black screen or the setup process keeps freezing, try removing the SD card
- SELinux permissive
32-bit vs 64-bit mode performance comparison:
https://browser.geekbench.com/v5/cpu/compare/15116230?baseline=14600296
Thanks to:
lsswizard for the 64-bit kernel, this all wouldn't be possible without his work
lsswizard for the TWRP tree
@quent1du58 for the commits to the device tree
LineageOS team for the base ROM
LineageOS-UL team for keeping the camera HALv1 patches alive
Sources:
Kernel: 3.18.140
64-bit vendor libraries from Galaxy A20s firmware (A207FXXU2BUD4)
https://github.com/UDPSendToFailed/
https://github.com/LineageOS
https://github.com/LineageOS-UL
https://github.com/TeamWin/android_bootable_recovery
looking forward to see flashable zip for deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw
aIecxs said:
looking forward to see flashable zip for deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw
Click to expand...
Click to collapse
They are already removed from the provided vendor.img but sadly that didn't fix the problem, I will look for a solution.
{
"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 for all your work. My SM-T590 is running on it for almost a day now (with MicroG and Magisk). Installation was not straightforward (I've had to factory reset after flashing LineageOS since the setup process kept freezing), but definitely easier than with the other GSI images. Not really sure if it is also related to the 32 vs 64 bits kernel, but the tablet definitely feels snappier than with BloatUI OneUI.
I've found only three problems so far:
The tablet does indeed randomly freeze from time to time. It does seems related to Magisk, but definitely not a huge deal since it rarely happens. I'll try to pinpoint the problem with a logcat if I have some time.
Only half of the speakers are working (but still not a deal breaker).
My book cover does not wakes up or put the tablet into sleep. It seems that one of the sensors is not working properly.
quent1du58 said:
Many thanks for all your work. My SM-T590 is running on it for almost a day now (with MicroG and Magisk). Installation was not straightforward (I've had to factory reset after flashing LineageOS since the setup process kept freezing), but definitely easier than with the other GSI images. Not really sure if it is also related to the 32 vs 64 bits kernel, but the tablet definitely feels snappier than with BloatUI OneUI.
I've found only three problems so far:
The tablet does indeed randomly freeze from time to time. It does seems related to Magisk, but definitely not a huge deal since it rarely happens. I'll try to pinpoint the problem with a logcat if I have some time.
Only half of the speakers are working (but still not a deal breaker).
My book cover does not wakes up or put the tablet into sleep. It seems that one of the sensors is not working properly.
Click to expand...
Click to collapse
Thanks for the feedback!
I'm working on a non-GSI variant since I couldn't fix the keystore errors and other issues on GSI.
However I have no previous experience on Android builds, and our device has no custom ROMs or device trees to begin with, so it might take a long time to fix everything. Also the 3.18 kernel is really old for Android 12.
Currently basic functionality like WiFi, Bluetooth, OpenGL, sensors, and lock screen are working, but there is still a lot more left like DRM, cameras, audio, GPS, etc.
As for your 3rd issue, I would suggest enabling double tap to wake in Phh Treble Settings.
That's some great news. I've also tried to port LineageOS to this device (mostly as a way to learn new things, since Android/LineageOS/kernel aren't really my areas of expertise) using both Rupansh and heavily customised Xiaomi Redmi 5 (Rosy) sources trees without any success.
Have you managed to boot a non GSI build? I've tried to compile LineageOS 19 Using your device and kernel trees, plus Rupansh vendor tree. Build went fine, I've even managed to flash and to boot into recovery (which needs fstab fixes), but no way to boot a freshly flashed zip for now. I'm going to continue my research and will share any progress.
quent1du58 said:
Have you managed to boot a non GSI build? I've tried to compile LineageOS 19 Using your device and kernel trees, plus Rupansh vendor tree.
Click to expand...
Click to collapse
Yes, currently my tablet runs a build based on my device tree on GitHub but it's highly experimental. Basically I use GitHub only to have some revisions of the device tree for backup and testing purposes, that's why all the commits are named asd.
I guess your issue will be that you use vendor files from Rupansh (since that's missing 64-bit stuff from Galaxy A20s vendor), here I have uploaded the ones I'm using: https://mega.nz/folder/zXZzVZaL#95t8V7DSr0rX7W0lTZmhHQ
Copy them to a folder named ~/system_dump for example, create a subfolder named system and another subfolder named vendor under the previously created system folder. Then you can use the commands below to extract the required proprietary files from system.img and vendor.img. Assuming you have everything in ~/system_dump folder:
sudo mount -o loop,rw system.img system
sudo mount -o loop,rw vendor.img system/vendor
Then go to your downloaded LineageOS source/devices/samsung/gta2xlwifi and run:
chmod +x extract-files.sh
chmod +x setup-makefiles.sh
bash extract-files.sh ~/system_dump/
Also you will need to apply some patches to the LineageOS 19.1 source to bypass eBPF requirement which is not available on our 3.18 kernel. Download Treble patches from here: https://github.com/phhusson/treble_...ases/download/v413/patches-for-developers.zip
Apply patches/platform_system_bpf/0001-Support-no-bpf-usecase.patch to system/bpf and patches/platform_system_netd/0001-Support-no-bpf-usecase.patch to system/netd in the source using git apply /path/to/.patch. You can also apply the Camera2 API patches mentioned in the first post but the camera doesn't work anyway currently.
The resulting build is barely usable, working stuff are mentioned in my previous comment. Feel free to try different versions in device.mk and add / remove stuff in proprietary-files.txt, I guess I messed up lots of things since I never built a device tree before.
Thank you for all those details, I've managed to build a working image. I still experience the same problems so far:
UI crashes a lot shortly after rebooting
Inserting a SD card freezes the system
But since I now have a way to build my own releases, I'll try to fix things. Since I've forked your repositories on Github, I'll send you pull requests when needed.
Glad you managed to get it work!
Yep, the UI hangs and crashes are happening here too, haven't found the cause yet. Logcat shows a blocked state and dumps tons of lines from the kernel. The interesting part is that sometimes, like in 2 of 10 reboots it starts up correctly without any freezes.
If I have some time I will continue fixing the tree as there are lots of randomly added and unfinished stuff which I did for testing purposes.
I tried to flash twrp in the download mode but it showed "only official binaries are allowed to be flashed". What's wrong?
seeiu said:
I tried to flash twrp in the download mode but it showed "only official binaries are allowed to be flashed". What's wrong?
Click to expand...
Click to collapse
You need to flash TWRP using a patched version of odin.
Thanks for the great tutorial. The Rom runs so far quite well.
But when I want to flash microG_Installer_Revived with TWRP I get a 235 error.
When I connect the tab to the PC, the internal memory and SD card is not shown to me on the PC.
Although, the tab is recognized by the PC.
Is there a trick or do I have to live with it.
DerSammler said:
But when I want to flash microG_Installer_Revived with TWRP I get a 235 error.
Click to expand...
Click to collapse
I just updated the first post with some instructions about MicroG. Basically you will have to flash it as a Magisk module, also use FakeGApps to have Signature Spoofing support.
DerSammler said:
When I connect the tab to the PC, the internal memory and SD card is not shown to me on the PC.
Click to expand...
Click to collapse
Yea, that's a known issue with both GSI and non-GSI variants, it'll be fixed as I find the cause. Alternatively you can use adb or some wireless file transfer app like AirDroid.
What do I do if I want to go back to stock Rom?
Can I simply flash with Odin original Android 10? Or is there anything else I need to consider.
Thank you very much.
DerSammler said:
Can I simply flash with Odin original Android 10?
Click to expand...
Click to collapse
Exactly, it's enough to flash the latest stock ROM with Odin to revert the changes.
I have installed lineage-19.1-20220525-UNOFFICIAL-gta2xlwifi according to the new instructions
unfortunately, when I start the tab, I get a red message—kernel is not seandroid enforcing -.
Afterwards, when the tab is started, I also get the following message on the home screen
Android System
There is an internal problem with your device. Please contact the manufacturer regarding this.
Are these two messages normal? Or am I doing something wrong. I have now installed LOS_19.1_64 again. Thank you very much.
DerSammler said:
Are these two messages normal?
Click to expand...
Click to collapse
Yes, these messages are completely normal in the ROM's current state and can be ignored, they won't cause any further issues.
The kernel message is related to the SELinux permissive state which is listed under known issues, the other one shows up simply because I haven't patched the LineageOS source code to hide it.
Disable AVB check · phhusson/[email protected]
This avoids the message "There's an internal problem with your device. Contact your manufacturer for details." on some AVB 1.0 devices. Change-Id: Ia54b857a3e98e2639d6bcc0ba713809704...
github.com
Thanks a lot for your help.
I find the Rom really great, super work you do. The system is really faster.
To transfer data I have MyPhoneExplorer and that works very well with it.
I'm curious what there will be updates for this Rom.
Wish you a quiet Sunday.
Greetings: Dirk
DerSammler said:
I find the Rom really great, super work you do. The system is really faster.
Click to expand...
Click to collapse
Thanks for the feedback!
DerSammler said:
I'm curious what there will be updates for this Rom.
Click to expand...
Click to collapse
Yea, I'll try to improve things but as I stated in my previous posts, I'm just an average user with no Android porting experience, so it might take a while. I'll post new releases with monthly security updates from Google and maybe some fixes.
Also please note that the ROM isn't secure yet, the lock screen can be easily bypassed with TWRP since encryption isn't enforced, and adb with root access is enabled by default for debugging purposes.
I have a question about the GSI Roms?
Which roms can I flash on the Galaxy Tab A (T-590).
The roms must be Binder compatible, I know that.
Can I only flash Binder a64, or can I also use the Binder arm 64 Rom?
Thank you very much.
Related
{
"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"
}
CyanogenMod 12.1 for Samsung Galaxy Note II
GT-N7100 (t03g)
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Have questions? Feel free to ask in the Q/A thread http://forum.xda-developers.com/galaxy-note-2/help/qa-cyanogenmod-12-unofficial-t2976843
Installation Guide:
For beginners:
Make sure to backup your data first!All files will be lost after this process!
1. Make sure your device is rooted. If not, download these files from here:
Odin
CF-autoroot (unzip it, you will need CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5)
TWRP (make sure you download twrp-x.x.x-x-t03g.img.tar)
How to root:
- Reboot your phone into Download Mode,(turn off device and press these buttons: Volume Down+Power+Home, then pres Volume Up to continue).
- Connect the phone to your PC.
- Open Odin.
- Now Odin should recognize the device showing a different color under "ID:COM".If it doesn't after like a 5 minutes, download the Note II drivers from here.
- Find "AP" and click on it. A search box will appear: Search for CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5 in your computer and select it.
- Click on "Start" and wait for the phone to reboot, (a screen with a red text will appear on your phone - all normal, wait until the phone boots into system and search for SuperSU app, should be in your App Drawer).
2. We recommend TWRP recovey. So flash it with Odin just like you did with the CF autoroot before.
3. Turn off device. Press Volume Up+Power+Home so the phone will boot in Recovery Mode
TWRP will boot and you can now see different buttons, please notice "Install", "Settings", "Reboot" and "Wipe".
First, open "Settings" and make sure "Use rm-rf instead of formatting" is checked. Then, open "Wipe" and select "Advanced Wipe" (Note! We recommend you to wipe everything if you come from a different ROM. This is called a "clean install" and it's strongly recommended. ). Check "Dalvik/ART Cache", "Cache", "System", ""Data", "Internal Storage" and then "Swipe to Wipe". Now go back and select "Reboot" and "Recovery" after that,(the reboot again in Recovery Mode).
4. Now your device is clean and we can proceed! Make sure you have the latest version of ROM downloaded and Gapps,(these two will be the only files you need).
Connect your device to your PC and copy the files directly into Internal Memory or SD Card,(you PC will recognize your device while it's in TWRP Recovery Mode and you can find it named as "t03g").
When the files are finally copied into your device, go and select "Install" and search for them. Make sure you install the ROM first and Gapps after. After this you will have two buttons down "Wipe Dalvik/Cache" and "Reboot System". Select "Wipe Dalvik/Cache" and when it's done reboot into your fresh new Lollipop Android by selecting "Reboot System".
5. Wait for the system to boot and optimize the apps for the first time, it usually takes a few minutes!
6. ENJOY!
For experienced users:
Wipe everything!
Flash ROM and after that flash the Gapps;
Wipe Dalvik/Cache;
Reboot.
Working:
EVERYTHING
- OpenGL (CPU rendering)
- MALI blobs (GPU rendering)
- HWComposer and MALI R3P2 drivers
- Rotation
- Camera
- WiFi
- Bluetooth
- NFC (Android Beam)
- Sensors (ALL!)
- Internal / External SD Card
- Vibration
- Home Button wake
- Simlock
- RIL
- GPS
- Signal Icon
- Soft Keyboard on first boot
- Mouse pointer
- H/W Video playback
[EOL] CyanogenMod 12.1 (Android 5.1.1) Download:
(mega.nz)
Gapps: Slim Gapps (recommended)
TK Gapps
Open Gapps
Based On Android 5.1.1 Lollipop (LP)
Changelog
25.08.2016
-Removed OTA;
-Synced with CyanogenMod Source;
11.08.2016
- OTA Support Enabled
- Synced with CyanogenMod Source;
- Updated Kernel.
09.08.2016
- ROM upgraded to CM12.1.1
- Synced with CyanogenMod Source;
- Framework Updates;
- Latest security patch (01 aug 2016).
02.08.2016
-Synced with CyanogenMod Source;
-Minor bugs fixed.
28.07.2016.
-Updated security patch (1 july 2016)
-Synced with cm source
-Build compiled by @andrewKode
12.11.2015.
-more hwc updates
-kernel updates
-synced with cm source
-Using HW layers for preview of recents
-misc
05.11.2015.
-HWC Updates
-Synced with CM source
-Misc updates
02.10.2015.
-Cyanogenmod updates (should fix launcher issues)
29.09.2015.
-Proper selinux implementation
-Stock CM bionic
-CM Updates
-Updated GPS and RIL blobs
05.09.2015.
-Synced with cm source
-Bionic updates
-Misc
31.08.2015.
-CM updates
-Misc device updates
15.08.2015.
Selinux updates
Synced with cm source
20.07.2015.
Sound config updates
Cyanogenmod updates
06.07.2015.
Cyanogenmod updates
Kernel updates
17.06.2015 Build 2
Resolved bluetooth issues
Resolved issues with ota updater app
17.06.2015
Enabled audio dock
Fixed some video playback related issues
Bluetooth improvements
Synced with CM source
30.05.2015 Build 2
Resolved video seeking issues
WiFi display updates
Screen recording should be more fluide now
30.05.2015
Youtube issues resolved
CM updates
OTA app is now using openrecovery script
Code rebase
Few kernel changes
Meh... this list would be too long if I continue.
09.05.2015
First public build with ota built in
General code cleanup
Increased led brightness from 200 to 255
Synced with cm source
[to-do]
-Fix youtube-
27.04.2015
Synced with CM source
Switched to N7100XXUFND3 fingerprint
Misc device side audio updates
22.04.2015
android 5.1.1
Kernel changes rolled back to last stable point
misc tweaks in frameworks av ti enable coexist with some mtk code
misc changes
synced with cm source
05.04.2015
Fixed HW video playback
Synced with cm source
Misc updates
01.04.2015
Non-pie executables enabled (again)
Bcopy is implemented again (Should fix some apps like chrome and firefox)
...
14.04.2015.
This build wasnt compiled by me because i had no time
There are misc cm changes implemented and few small device and kewrnel side changes i have made
29.03.2015
Package installer fixed
Clock app fixed
Few small improvements
Synced with cm source
26.03.2015
Fixed settings fc
Fixed GPS
Some other small changes and fc's patched
25.03.2015
Based on android 5.1
Performance improvements
small device side improvements
Touch Pointer (Also s-pen mouse pointer)-
are now visible if enabled in settings
19.03.2015
Synced with CM source
small device side improvements
11.03.2015
Resloved issues with themes
Synced with cm repo
08.03.2015
O3 flags set on some parts of system
Kernel and System compiled with SaberMod Toolchain
App2SD fixed
Synced with CM repo
03.03.2015
Fixed USB-OTG under settings
Added support for non pie executables
Implemented Lollipop kernel wakelock tracking api
Synced with cm source
19.02.2015
Netflix on device playback fixed
Few small kernel changes
Synced with cm source
15.02.2015
DRM blobs updated
Kernel improvements
general device/platform side improvements
Synced with cm source
12.02.2015
Using open source sensors again
Fixed small audio issues
Synced with cm repo
10.02.2015
imroved batery life with screen doze
Synced with cm repo
08.02.2015
Fixed bluetooth sound issues
implemented spen gestures
Fixed video streaming on some devices
Synced with CM source
06.02.2015
Implemented Device power profiles into device and platform tree
CM misc updates
27.01.2015
Synced with cm source
Misc device changes
30.1.2015
Fixed in call mute
Fixed headset microphone in calls
Misc CM updates
21.1.2015
Theme engine is working now
16.1.2015
Theme engine...
15.1.2015
Synced with cm source
misc updates
11.1.2015
Synced with CM repos
05.01.2015
Synced with CM source
Small HWC updates
Using open source sensors again
03.01.2015
Synced with CM source
27.12.2014
source updated
added HWC
cm upstreams
wifi improvements
hw keys improved
new kernel based on latest n7100 source
Offline mode charging
and many more improvements
22.12.2014
Fixed key layout
Misc updates
22.12.2014
Fixed issues with microphone
misc wifi updates
synced with cm repo
21.12.2014
Rebased Device Tree
Synced with cm repo
Improved Mali400 drivers
improved battery life
Fixed most of the wifi issues
Fixed stock camera
Fixed video playback
Many more minor changes
27.12.2014
Hwc
wifi and hw keys improvements
cm upstreams
new kernel from latest n7100 source
many more
17.12.2014
Init.d is fixed that means you wont have to execute 80cfw from terminal anymore
Many cm apps are also updated like new gallery,on device side few stability improvements
are included in this build and also i am starting to remove unused code from device tree
14.12.2014
Microphone improvements
Stability improvements
Synced with cm repo
14.12.2014
Music FX shouldnt FC anymore
Volume should be louder
Keyboard will now work from first boot on clean install
Cyanogenmod updates..
10.12.2014
Updated music Fx app
Updated Music Player
Fixed Signal Bug
Sync with CM sources
Screenshots:
Link 1
Link 2
XDA:DevDB Information
[EOL][ROM][STABLE][LOLLIPOP][5.1.1] CyanogenMod 12.1 - 25.08.2016, ROM for the Samsung Galaxy Note II
Contributors
Ivan_Meler, andrewKode
Source Code: http://github.com/ivanmeler
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: XXUFND3 or later baseband
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 1.0.1.M
Stable Release Date: 2016-08-25
Created 2014-11-24
Last Updated 2016-11-10
6.0 builds
So here it is Haxynox 6.0 build https://mega.nz/#!AJYGjYBA!uTdWxY3Daqhxi-fp9UXZieCiZn9As8yQsbqg6Pmj3pI
Do not report bugs on this just yet
So far sdcard mounting is broken (also pc wont recognise hone as media device because of that and device wont boot with sdcard)
and GPS is broken but it should be okay for first build and it can sort of be used as daily driver (Its fast and stable if you exclude those 2 bugs)
Enjoy
I will sort off those 2 issues soon
(cm build comming soon(ish))
awesome! I would like to try this. just one question, you mentioned that there was a problem with the mobile data, I wonder, is there any problem with calls or sms's? If not, I would gladly give this a try and send any feedback or logcats you wish
P.S. Can't wait for a stable version
waggygee said:
awesome! I would like to try this. just one question, you mentioned that there was a problem with the mobile data, I wonder, is there any problem with calls or sms's? If not, I would gladly give this a try and send any feedback or logcats you wish
P.S. Can't wait for a stable version
Click to expand...
Click to collapse
Calls Work I Didnt test sms But if you want jou can try it just remember this is proof of concept and not a daily driver yet
Cm12.. sounds interesting [emoji57]
Ivan_Meler said:
Calls Work I Didnt test sms But if you want jou can try it just remember this is proof of concept and not a daily driver yet
Click to expand...
Click to collapse
cool. Yes, I get that its not daily driver yet. but I am excited about getting it to daily driver stability and dont mind giving it a spin while providing info to help get it closer to that
Awesome
Awesome.....Thanks.....
Cool Cm12 is here
Sent from my SM-N910C
finally!!
hopefully this rom will boot up without much fuss
Can I make call and SMS?
Woah CM12 ! I have spent entire last week refreshing dev sections, looking for anything with lollipop .
Thanks for this dev Installing this soon and will report back.
Sent from my GT-N7100 using Tapatalk
Google Play service keeps force closing
keyboard issue fix
for anyone having the issue where no keyboard comes when you want to type, heres the fix:
go to Setting>Language&Input>Current Keyboard
Then flip the "Hardware" switch
---------- Post added at 05:09 AM ---------- Previous post was at 04:38 AM ----------
I'm facing the same issue with play services. I think Ill wait a bit till that bug is sorted out before I try the rom again
Yes, Google play Service keeps Force Closes so I can't use Google servicies like play Store etc etc
Dirty flash over CM11 solves problem of google service FC. But all other apps giving FC at that time. Wifi working perfect.
Need to test sd card.
Call working normal. SMS giving fc during send, but it get delivered.
Did anyone try this to fix camera:
http://forum.xda-developers.com/showthread.php?p=56823931
Im on nameless 5 and that fix my camera
If possible please upload to site other than mega, as it's blocked in India
Any chance you could make a version for N7105?
I tried to flash cm12 over cm11 with a dirty flash, but i have still google play service FC
Mega.co.nz works is accessible in India
fyh said:
If possible please upload to site other than mega, as it's blocked in India
Click to expand...
Click to collapse
Mega is not blocked in India, Me & a lot of other people i know can access it.
Your ISP is the culprit, call & ask your ISP to add the Global DNS for your connection & then you should be able to access it.
This worked for me, Hope this helps. :good:
This is only for SM-P605 (lt03lte)! Even loading an custom recovery will irreversible trigger Knox to 0x1!
LineageOS/CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS/CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (GApps). LineageOS/CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
How to flash:
-Be sure you are on 5.1.1 Bootloader and Modem (Flash 5.1.1 firmware via Odin) !
-Flash TWRP (version 3.0.0-0 or newer recommended)
-Make Nandroid backup (optional)
-Wipe > Advanced Wipe > select data, system, ART/Dalvik Cache, Cache, Internal Storage > Swipe
-Install > select Lineage14.1 Zip > Swipe, optional: flash GAPPS, SU Addon (before rebooting!)
-Reboot
Please read full OP before posting or flashing anything. Please don't report any bugs, if you use Xposed, any mod or modified the system.
Please report no issues, if you
using the official builds (or others than mine)
flashed Xposed
or modified the system
What is working
Everything
No major issues/bugs
Download
Other Builds
GAPPS
Notes:
- If SIM is not detected/RIL not working, flash 5.1.1 firmware again!
- Enable root: flash SU Addon, Settings > About tablet > tap 5x at build number. Settings > Developer options > Root Access
- just ignore E: Unknown Command errors in TWRP
- Flash GAPPS before reboot first time after flash!
- If using MTP/PTP shows no files, please tap one more at transfer files in notifications
- If something not listed ist not working, please test it also with SELinux permissive (setenforce 0 via Terminal Emulator/ADB Shell or use SELinuxModeChanger)
Changelog:
20210320: Synced sources
20200913: Synced sources, added midi support, disabled 5 GHz AP
20200318: Synced sources
20200124: Synced sources, a few kernel changes
20191101: Synced sources, small changes
20190801: Synced sources, slightly higher volume on speaker and Headset, small changes
20190303: Synced sources,smaller changes
20181226: Synced sources, changed SEPolicy, updated HID driver, small changes
Older
--Lineage--
20181217: Synced sources
20181029: Synced sources, small changes
20180816: Synced sources
20180618: Synced sources (Security Patch Level 2018-05-05), switched to 2048 heap/hwui memory map, sepolicy
20180524: Security Patch Level 2018-05-05
20180424: Synced sources
20180326: Synced sources, small things
20180307: Synced sources, kernel security patches, a few things
20180124: Synced sources, removed libsecril and legacy sd symlink, kernel updates
20171205: Synced sources, RIL changes, implemented stylus gestures
20171026: Synced sources, fixed magnet cover, switched to source built CAF ril, some kernel changes
20170925: Synced sources, fixed camera, kernel updates, sepolicy updates
20170829: Synced sources, switched to msm8974-common kernel (with some changes for our device), CLOCK_BOOTTIME_ALARM support, some smaller changes (Note: Please flash boot.img from post #643 to fix camera!)
20170803: Fixed MpDecision
20170802: Synced sources, only activate button light if they are pressed, added missing low latency record (-->for Skype etc.), updated init and sepolicy, some small improvements and changes
20170723: Synced sources, grant proper unix permissions for netmgrd and rmt_storage, updated sepolicy and init, smaller changes
20170703: Synced sources, removed buggy timekeep (fixes wifi problem), RIL updated (fixes Autotimezone), disabled live display per default, some minor changes
20170626: Synced sources, switched to Sony Timekeep (experimental), added SamsungDoze, enabled sdcardfs, enabled CIFS/NFS, mac access fixed, some kernel changes
20170614: Synced sources (Android 7.1.2_r17), quiet "KERNEL IS NOT SEANDROID ENFORCING"
20170604: Synced sources, fixed a bunch of kernel leaks
20170518: Synced sources, Only expose su when daemon is running
20170507: Synced sources (android-7.1.2_r8, Jelly...), correct keylayout config, enabled volume wake settings, added missing liblight defines, fixed prefered network setting, fixed rotation problem
20170422: Synced sources (Android 7.1.2), F2FS support, changed keylayout again, some kernel changes, IR changes from Lineage, dex preopt (not prerooted, flash SU Addon)
20170320: Synced sources, prerooted again, enabled Miracast/WiDi overlay, added missing SEPolicys for s-pen third party apps
20170301 #2 : Fixed tethering/hotspot (not prerooted, flash SU Addon)
20170301 #1: Synced sources, improved macloader related stuff (not prerooted, flash SU Addon)
20170203: Synces sources, fixed telehony fc after Nandroid restore, enhanced off charging mode
20170126: Synces sources, enabled Blur, a few kernel changes
20170114: Synced sources (Android 7.1.1_r9)
20170104: Synced sources, removed some deprecated stuff (dhcpcd entries, legacy symlinks)
20161231: Synced sources, Bluetooth disabled per default, unknown sources enabled per default
20161227: Synced sources, first Lineage build
--CyanogenMod--
20161215: Synced sources (Android 7.1.1_r6), disable notification LED for now (until I find a better solution), switched to common IR/lights HAL, last build from CyanogenMod Sources
20161207: Synced sources (Android 7.1.1), reduced power consumption, add missing SELinux rule
20161202: Synced sources, fixed magnetic cover, fixed VOIP mic
20161128: Synced sources, fixed off charging Mode, changed keylayout: Menu button: menu, longpressmenu: splitscreen view, doubletaphome: recent Apps
20161115: Synced sources, fixed camcorder, mapped longpressmenu as menu
20161110: Synced sources, Setup Wizard fixed, updated SEPolicy
20163010: first xda release, sync with cm 14.1 sources
Credit: LineageOS/CyanogenMod Team, Maintainer and Valera1978
Kevin F. Haggerty, Paul Keith
Sources:
Device
Kernel
Kernel since 20170829
Vendor
XDA:DevDB Information
Unofficial LineageOS (CyanogenMod) 14.1 for SM-P605, ROM for the Samsung Galaxy Note 10.1 (2014 Edition)
Contributors
davidmueller13
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 5.1.1 bootloader and modem
Based On: LineageOS
Version Information
Status: Stable
Created 2016-10-30
Last Updated 2020-09-17
FAQ - Frequently Asked Questions
FAQ
Please read before posting anything!
Will this work/can you make it work on P600/P601?
Short answer: No! Only SM-P605 is supported.
But there are other projects for your device. For P600 (n1awifi) you can just download the latest official nightly.
Can you add xy feature?
It is and will stay a build straight from LineageOS sources, not a fork, so no. And also afaik there is no feature request way for LineageOS atm.
My SIM card is not recognized. What can I do?
As RIL blobs are from 5.1.1 firmware package, you need to be on modem from 5.1.1 firmware. The easiest way: just get an firmware package from Sammobile, Updato... and flash it via Odin. If it's still not working after that, do the same again (sometimes this is necessary).
Something is not working (correctly) / I found a bug? What should I do?
Make sure there are no potential courses for that issue like installed Xposed or system modifications. Also look, if it's listed in the OP or somebody already mentioned it. If not, just post about it and all information about it you have (circumstances, steps to reproduce it...).
Of course only for my builds you found in that thread, not for other/offical builds.
Amazing work!
Running your 10-27 build since yesterday night and working great so far on my T-Mobile P-607T.
Only thing noticed so far are that can not change the battery style and display battery % on the statusbar.
That's purely cosmetic, the build is fast and stable. Weather location service works, have not tested GPS
nav yet.
Setup wizard worked for me on the 10-27 build.
Will download and test this build.
Thanks for keep supporting the Note 10.1 2014.
Thanks
Thanks for making this sweet build. Everything works well on my P607-TM except for the fact that it thinks the SIM card is not inserted. I came from a aosp 6.0.1 build and did an advanced format of everything except for external SD card. I tried formatting a few times and reinstalling a few times with no luck.
iandy1 said:
Only thing noticed so far are that can not change the battery style and display battery % on the statusbar..
Click to expand...
Click to collapse
Yes, some stuff for that is not fully ported and implemented yet.
iandy1 said:
Setup wizard worked for me on the 10-27 build.
Click to expand...
Click to collapse
Thats the SetupWizard App, that comes with GAPPS. I had to remove the CyanogenMod SetupWizard, because of a FC while Wifi Setup. (I think, it uses the deprecated SETUP_WIFI_NETWORK.)
temijun said:
except for the fact that it thinks the SIM card is not inserted. I came from a aosp 6.0.1 build and did an advanced format of everything except for external SD card. I tried formatting a few times and reinstalling a few times with no luck.
Click to expand...
Click to collapse
Make sure, you are on the latest modem (e.g. by flashing latest firmware).
Also an LogCat would be useful (How to do this).
Yeah you're absolutely right about the radio firmware once I upgraded baseband from P607TUVUBOI2 to P607TUVSBPH1 and reflash everything works as expected! thanks again for this awesome rom!
davidmueller13 said:
Yes, some stuff for that is not fully ported and implemented yet.
Thats the SetupWizard App, that comes with GAPPS. I had to remove the CyanogenMod SetupWizard, because of a FC while Wifi Setup. (I think, it uses the deprecated SETUP_WIFI_NETWORK.)
Make sure, you are on the latest modem (e.g. by flashing latest firmware).
Also an LogCat would be useful (How to do this).
Click to expand...
Click to collapse
firmware is very smooth, but
- Sometimes crash settings app
- Does not work the microphone during a call through Skype
Does this version fix the bug that I saw with rotation?
Edit. Isn't a bug. Settings disabled rotation for certain orientation by default. Need fix by changing in settings.
it cant read my sim
Does it support exfat or ntfs file system with write rights?
great rom..sometimes a little bit stuttering, but finally great to have 7.1
how do you use your stylus? do u have a special app for that?
Thank you again
ameenkhaled said:
it cant read my sim
Click to expand...
Click to collapse
I flashed back to the default TMobile P607TUVUBOI2 firmware and then did an internal update to P607TUVSBPH1 which updated the radio baseband. This solved the missing SIM issue for me.
Hooray! One more of my devices could hop on CM14.x! I think imma start building myself starting next month...
Are MTP and ADB connections working too? Those aren't present in official CM13 nightlies and are the most irritating I found in them.
Sent from Google Nexus 6P @ CM13
AndyYan said:
Are MTP and ADB connections working too? Those aren't present in official CM13 nightlies and are the most irritating I found in them.
Click to expand...
Click to collapse
Yes, they work.
In the CM13 Nighlys the kernel driver for MTP is failing. If you want to fix/add some things to your CM13 Builds:
Fix camera failing while SELinux Enforcing: http://review.cyanogenmod.org/#/c/165576/
Fix MTP-driver: https://github.com/davidmueller13/k...mmit/4785cabeb9047e8d9e5e19e3f3f5c4f4e3a59ceb
enable adoptable storage: https://github.com/davidmueller13/d...mmit/5ed5e71080c366e3e35ee23f032b86da74db2dba
And if you want to build CM14, it's important that you know that i use the common graphic binaries:
https://github.com/TheMuppets/proprietary_vendor_qcom_binaries
temijun said:
I flashed back to the default TMobile P607TUVUBOI2 firmware and then did an internal update to P607TUVSBPH1 which updated the radio baseband. This solved the missing SIM issue for me.
Click to expand...
Click to collapse
Does PH1 update the baseband? I extracted modem.bin from PH1 tar and flashed, and later flashed the whole PH1 package from Odin, but baseband stays at OI2...
Sent from Google Nexus 6P @ CM13
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
davidmueller13 said:
Yes, they work.
In the CM13 Nighlys the kernel driver for MTP is failing. If you want to fix/add some things to your CM13 Builds:
Fix camera failing while SELinux Enforcing: http://review.cyanogenmod.org/#/c/165576/
Fix MTP-driver: https://github.com/davidmueller13/k...mmit/4785cabeb9047e8d9e5e19e3f3f5c4f4e3a59ceb
enable adoptable storage: https://github.com/davidmueller13/d...mmit/5ed5e71080c366e3e35ee23f032b86da74db2dba
And if you want to build CM14, it's important that you know that i use the common graphic binaries:
https://github.com/TheMuppets/proprietary_vendor_qcom_binaries
Click to expand...
Click to collapse
Do the patches works for TWRP too? Last I recalled TWRP also doesn't have ADB/MTP, if those could fix it I might consider syncing TWRP and do a patched build...
Sent from Google Nexus 6P @ CM13
AndyYan said:
Do the patches works for TWRP too? Last I recalled TWRP also doesn't have ADB/MTP, if those could fix it I might consider syncing TWRP and do a patched build...
Click to expand...
Click to collapse
I think, it's the same issue. If you want to build TWRP you should use a OmniROM source tree (i change the device tree for that a bit :https://github.com/davidmueller13/device_lt03lte_nougat/tree/omni ).
Is it common that the menu button calls up the recent apps?
I tried editing it in options but no matter if short press or long press are changed to any option available it still uses recent apps.
Cirno5 said:
Is it common that the menu button calls up the recent apps?
I tried editing it in options but no matter if short press or long press are changed to any option available it still uses recent apps.
Click to expand...
Click to collapse
Yes, that is normal. I don't know how to fix it myself without gravitybox. That option won't work because 7.0/7.1 has no xposed support yet.
Sent from my LG-H850 using XDA-Developers mobile app
Cirno5 said:
Is it common that the menu button calls up the recent apps?
I tried editing it in options but no matter if short press or long press are changed to any option available it still uses recent apps.
Click to expand...
Click to collapse
Manually edit the .kl file in /system/usr/keylayout (can't remember which, but should be obvious).
Sent from Google Nexus 6P @ CM13
Cirno5 said:
I tried editing it in options but no matter if short press or long press are changed to any option available it still uses recent apps.
Click to expand...
Click to collapse
Change in sec_touchscreen.kl in system/usr/keylayout "APP_SWITCH VIRTUAL" to "MENU VIRTUAL".
I think, i will change it in the next build and set the app switch to "long press home" and disable "double tap home".
Good news for camcorder: I fixed recording, but we have to wait for some changes in CM14.1. But at least it works for our device finally in CM13.
This is LineageOS 17.1, which is based on Android 10, for the WiFi-only variant of the Samsung Galaxy Tab A 10.1" (2016), codenamed gtaxlwifi. LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android distribution.
I started these builds because the LineageOS builds from @Valera1978 had 2 particular significant bugs in them that were always being mentioned in posts in that thread: display backlight brightness not changeable from full brightness and the touchscreen appearing to not respond after putting the tablet to sleep. Those bugs had existed for quite a long time. @followmsi has some changes in his 17.1 device tree that fixed those 2 bugs.
These builds really became a continuation of Valera's builds after he unfortunately discontinued work on this device due to an (understandable) lack of interest, with many improvements and additional features.
I've now discontinued these 17.1 builds.
I've long ago moved onto LineageOS 18.1 and 19.1.
Very important note for those upgrading from the releases from 20210523 and 20210413 in this post: https://forum.xda-developers.com/t/lineageos-17-1-for-sm-t580-gtaxlwifi.4059571/post-85106105
Note: I've never had any builds for the LTE variant. However, builds for the WiFi-only variant boot and work on the LTE variant, only without mobile networking (of course), GPS and vibration, so since I've allowed installation on the LTE variant in the last several builds, you can try to use my builds on it if you can go without any of that functionality.
Downloads:
Latest build from 20211116 (with security patch level 20211105):
https://drive.google.com/file/d/14ZCYYcT5b6E9zWiFNgwUP3Kxlvf-dyVn
Folder for these builds (which includes text files with MD5 and SHA256 checksums for the final build, and another folder within it containing some previous builds): https://drive.google.com/open?id=1UiUlSbfj3agDvt-4f_YLIS0Xyuz5RtFC
Changelog:
Final release for 20211116:
Latest updates from LineageOS, including the 20211105 Android security updates.
The WiFi driver has been switched from being a kernel module to being built into the kernel. This may improve reliability for enabling and disabling WiFi and the WiFi hotspot very slightly.
The rewrite of the sepolicy containing all of the SELinux rules that I did for 18.1 has been ported over to 17.1, and so it's now of much better quality.
The audio outputted from the audio jack while playing media will now be noticeably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.
An issue where there was additional extremely quiet high-pitched noise from the right speaker has been fixed.
The ZRAM size has been increased to 768MiB.
The BSP sources have been redone to closely match what has been done with the new exynos7880-specific part of Lineage's BSP sources, and with that, there are now more exynos7870-specific changes to the open source gralloc that is in use.
Some miscellaneous cleanups have been done.
The qcom_cfg.ini configuration file for WiFi has been imported from Samsung's A720SKSU5CTL2 firmware - A change within it appears to have made WiFi more reliable.
The system image size has been increased from 3072000000 bytes to 3145728000 bytes, which is the size of the system partition on Korean and Chinese variant T580s and T585s, and the smallest system partition size out of all T580s and T585s.
Some proprietary blobs have been updated as follows:
WiFi and Bluetooth firmwares from Samsung's T390XXS9CUG1 firmware
libexynoscamera3.so library from Samsung's P580ZSS1CTI1 stock firmware - This improves the situation with the issues with stretched/squashed camera previews for images and stretching/squashing in videos at some resolutions
MFC (Multi-Format Codec) firmware from Samsung's A305FDDU6CUI3 firmware
sensors.universal7870.so library from Samsung's P580ZSS1CTI1 stock firmware
As the oldest proprietary blobs are now as in Samsung's P580ZSS1CTI1 stock firmware (with a few exceptions), the vendor security patch level has been increased to 2020-09-01, which is the security patch level that firmware has.
The 32-bit wcnss_filter binary, used for Bluetooth, that was used previously has been replaced with the 64-bit wcnss_filter binary from Samsung's A520FZTU4BRB1 firmware.
Configuration files for media codecs and profiles have been updated from Samsung's T580XXS5CTK1 stock firmware.
There are many (final) updates from the (unfortunately now deprecated so no longer updated) 3.18 Android common kernel, many updates from Linux 4.4, and some updates from a few of Samsung's newer kernel sources to the kernel, and also some other various changes.
A few changes have been imported to the MMC block device driver in the kernel from Samsung's M105GDXS6CUD4 kernel sources that specifically fix extremely rare kernel panics that occurred when there was an error with a MMC device (mainly with SD cards).
Some unnecessary drivers have been disabled in the kernel.
The sdfat driver in the kernel, which is used for exFAT filesystem support, has been updated to version 2.4.5.
The fix for an issue where the duration of videos that are taken is lengthened by the time spent in deep sleep/suspended that was previously used has been replaced with a better fix in the Exynos fimc-is2 driver in the kernel.
Previous releases:
Release for 20210530:
Latest updates from LineageOS.
File-based encryption has been disabled after I left it enabled by mistake after testing FBE before moving onto LineageOS 18.1.
Release for 20210523:
Latest updates from LineageOS, including the 20210505 Android security updates.
Some changes have been imported to libbt-vendor from https://github.com/LineageOS/android_hardware_qcom_bt on branch lineage-18.1-caf (same as branch lineage-17.1-caf).
The rampatch_tlv_tf_1.1.tlv firmware for Bluetooth has been updated from Samsung's stock T585XXS6CTJ7 firmware.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
A workaround that was used to get USB tethering and Bluetooth tethering to work is no longer used, and has been replaced with a proper fix (enabling CONFIG_NETFILTER_XT_TARGET_CT in the kernel).
Release for 20210413:
Latest updates from LineageOS, including the 20210405 Android security updates.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
Release for 20210313:
Latest updates from LineageOS, including the 20210305 Android security updates.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel, many changes to the rcu, locking and btrfs code from 4.4, and a few changes from Samsung's M105GDXU6CUA1 kernel to the kernel.
The exynos part of the BSP has a few changes from Lineage's 18.1 branch for HWC and memtrack.
Release for 20210207:
Latest updates from LineageOS, including the 20210205 Android security updates.
SELinux denials that caused the torch feature to not work have been addressed.
The issue where videos that are recorded have a duration that is lengthened by the time spent in deep sleep has been worked around - It looks like Samsung did something wrong in the camera HALs for Exynos 7870 devices.
There are some more updates from the 3.18 Android common kernel and Linux 4.4 to the kernel, and a few changes from Samsung's M105GDXU6CTL3 kernel.
Release for 20210116:
Latest updates from LineageOS, including the 20210105 Android security updates.
The custom camera provider HAL has been removed, and the camera provider HAL has been binderized - this fixes camera glitches when there is motion.
Quota support has been enabled on userdata, so that storage usage statistics can be gotten more quickly.
The Widevine DRM blobs from the Pixel 3 XL's last Android 10 firmware are now used.
The MFC (Multi Format Codec) firmware has been updated from Samsung's M105FDDU3CTK3 firmware, and the camera.vendor.universal7870.so library has been updated from Samsung's latest stock firmware (version T580XXS5CTK1).
There are some more updates from Linux v4.4 and the 3.18 Android common kernel to the kernel.
Release for 20201223:
Latest updates from LineageOS.
Address hal_graphics_composer_default SELinux denials on video_device - fixes issues with video playback with SELinux set to enforcing. (Thanks to @Kostareka for providing logs with the SELinux denials)
Release for 20201221:
Latest updates from LineageOS, including the 20201205 Android security updates.
I've prepared new BSP sources, based on Lineage's SLSI BSP sources, and the BSP libraries are now built from those sources. (Thanks to @Valera1978 for providing his old BSP sources! Without them, this wouldn't have been possible.)
Samsung's proprietary audio libraries, adapted by @Valera1978, are now used, to workaround an issue where audio will be outputted to both the 3.5mm audio jack and the speakers quietly when something is connected to the audio jack.
The build fingerprint has been changed to an older Android 8.1 fingerprint for the Google Pixel C. (For information on why we can't use the fingerprint from the stock firmware, see: https://github.com/TALUAtGitHub/android_device_samsung_gtaxlwifi/issues/1 )
Installation on the LTE variant (SM-T585, codenamed gtaxllte) is now allowed - apparently, builds for the WiFi-only variant boot and work on the LTE variant, only with no mobile networking (of course) and GPS.
There are a few minor cleanups.
Version 2 of the AOSP bluetooth audio HAL has been enabled.
FIFO UI scheduling has been enabled.
The camera libraries have been updated from Samsung's latest stock firmware, version T580XXS5CTK1.
There are a few other miscellaneous improvements.
There are some updates to the kernel from the Android 3.18 common kernel and Linux v4.4, and there are updates to some of the drivers from Samsung's M105GDXU5CTI3 kernel.
Release for 20201121:
Latest updates from LineageOS, including the 20201105 Android security updates.
The sepolicy has been improved - many unnecessary SELinux rules have been removed and a few SELinux denials have been addressed.
The init.power.rc script is now actually used to set some parameters for the interactive CPU governor to make it less aggressive.
The GNSS and sensors HAL are now compiled from source in the device tree with necessary modifications. (Thanks to @followmsi for some very useful information regarding this!)
As many vendor blobs as possible have been updated from Samsung's T580XXS5CTD1 and A520FXXUGCTI9 stock firmwares, the gpsd shim has been removed as it's no longer necessary after updating gpsd from T580XXS5CTD1 and a few unused vendor blobs have also been removed.
cbd/cpboot-daemon has been removed, because it, along with the modem_v1 driver in the kernel, no longer works with the latest bootloader and spams the kernel log with error messages, I have very little idea of what it does for the WiFi-only variant and it's unnecessary.
Made a few other miscellaneous improvements.
Many more updates to the kernel from Linux v4.4 and the 3.18 Android common kernel, some miscellaneous improvements and many changes to the f2fs filesystem driver from newer Android common kernels and mainline Linux.
The kernel is now compiled using the clang compiler after having applied the many necessary changes to it to do so.
Release for 20201022:
Latest updates from LineageOS, including the 20201005 Android security updates.
Enable config_setColorTransformAccelerated - LiveDisplay colour calibration and reading mode is now available. (Thanks to @followmsi for finding this fix.)
Add FlipFlap for flip covers. (Note that FlipFlap only works if the timeouts in Settings -> Connected devices -> Connection preferences -> Smart cover are set to 'immediately')
Fix a typo in the power profile.
More updates to the kernel from Linux v4.4 and the 3.18 Android common kernel.
Apply/backport some changes to zram and the lz4 compression algorithm from mainline Linux for faster compression and decompression, and add a backport of the zstd compression algorithm from the 4.9 Android common kernel which can be used as the compression algorithm for zram (lz4 is still the default compression algorithm).
Release for 20200915:
Latest updates from LineageOS, including the 20200905 Android security updates.
Increase microphone gains.
Many more updates from Linux v4.4 and android-3.18 and a few improvements to the kernel.
Release for 20200821:
Latest updates from LineageOS.
A few more updates from Linux v4.4 and android-3.18 and improvements to the kernel.
Revert 2 changes to the kernel related to hotplugging - should fix an issue where the device doesn't wake up after a while of deep sleeping in certain cases, and a hard reset is needed.
Release for 20200814:
Latest updates from LineageOS, including the 20200805 Android security updates.
Update the Mali graphics blob to r28p0 from r22p0.
Make a few changes for GPS that fix Assisted GPS, and switch to different XTRA servers with HTTPS.
Fix OpenCL.
Symlink libGLES_mali.so to libOpenCL.so, libOpenCL.so.1 and libOpenCL.so.1.1 instead of copying - saves a significant amount of space in /system and makes the installation zip slightly smaller.
Change media volume control to be in 25 steps rather than 15 steps.
More updates from Linux v4.4 and android-3.18 to the kernel and some improvements.
Release for 20200711:
Latest updates from LineageOS.
Android security updates from 20200705, manually applied to skip the wait for them to be merged. ('repopick -t android-10.0.0_r40')
Disable window rounded corner animations.
Reduce ZRAM size to 512MB.
Enable debug.sf.disable_backpressure.
A few more updates to the kernel from Linux v4.4 and android-3.18.
Port over/import zsmalloc, zram, zswap, zbud and zpool from Linux v4.4.
Fix the issues with hanging/freezing that were present in the previous release.
Release for 20200703:
Latest updates from LineageOS.
Enable support for using USB for MIDI.
Fix/workaround issues with USB tethering.
Remove sswap and use ZRAM.
Latest update from @Valera1978 - "update audio_policy_configuration.xml from SM-A600FN q stock"
Many more updates to the kernel from v4.4, android-3.18 and a few from v3.16.
Disable the Exynos hotplug governor again. (in the kernel)
Release for 20200608:
Latest updates from LineageOS including the 20200605 Android security updates.
Use userspace lmkd.
Enable Always On Display. (Thanks to @followmsi)
Address a few more SELinux denials.
power_profile: change names as per pie naming changes.
Switch to [email protected]g. (Thanks to @followmsi)
Fix freeform window moving/resizing doesn't work (In my new fork of LineageOS' android_frameworks_base repository).
Add back support for Miracast using the changes from https://review.lineageos.org/q/topic:%22ten-aosp-wfd%22 (In my new fork of LineageOS' android_frameworks_av repository).
More updates to the kernel, including many updates from Linux v4.4 and v3.16 and general updates. There are also improvements to downstream drivers.
Release for 20200512:
Latest updates from LineageOS including the 20200505 Android security updates.
Address more SELinux denials.
Remove the ro.enable_boot_charger_mode property and revert "gtaxl: workaround for offline charging".
Remove some useless services for non-existent binaries in init files.
Hide sRGB toggle in developer options.
More updates to the kernel, including many updates from Linux 4.4 and to the kernel-based wireguard implementation.
Release for 20200411:
Latest updates from LineageOS including the 20200405 Android security updates.
Update the cpu.speeds array in the power profile for 1.69GHz, 449MHz and 343MHz frequencies.
Make the power profile aware of the big.LITTLE cluster.
Address more SELinux denials and remove duplicate rules.
Use an up-to-date Samsung hardware repository based on LineageOS' repository, and make changes to the device tree for it. ((Thanks to @followmsi for changing the sepolicy to accommodate for modem/macloader having been moved to /vendor and mentioning that the Exynos hidl power HAL has to be used after the old power HAL was removed)
Enable secure ADB and set persist.sys.usb.config to none.
Use pool.ntp.org for the NTP servers.
ramdisk: cleanup the init files and fstab for readability.
ramdisk: init.samsungexynos7870.rc: only start gpsd after booting - fixes GPS when encrypted.
More updates to the kernel, including many updates from Linux 4.4, general updates (such as updates to the wireguard kernel module) and fixes.
Use sdfat for exFAT support.
Add toggle for disabling newly added USB devices.
Release for 20200309:
Latest updates including 20200305 security patches
Upgrade android.hardware.keymaster to 4.0.
lineage-gtaxlwifi_defconfig: disable CRYPTO_FIPS to get encryption partially working.
sdfat: update to version 2.3.0.
Update the BFQ IO scheduler to v8r12 using a port.
Release for 20200303:
wireless: add back Samsung's 'temporary' workaround due to qcacld-2.0 page allocation errors. Looks like this is actually necessary. Works around issues with WiFi not being possible to be enabled after some time again due to page allocation failures that still exist.
Revert duplicate "signal/ptrace: Don't leak unitialized kernel memory with PTRACE_PEEK_SIGINFO". We already had this commit as in Linux v3.18, the content of this reverted commit are useless.
Release for 20200301:
Fix a few SELinux denials. (including app_zygote denials, sepolicy in post 5 no longer needed for this build at all and also shouldn't be used anymore as more denials beyond just the app_zygote denials have been fixed)
Release for 20200229:
Initial release.
Known issues and workarounds (if any):
Issue 1: adoptable storage is reported to not work correctly.
Somewhat of a workaround to issue 1: format and use your micro SD card with the exFAT filesystem.
Issue 2: 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 to issue 2: Use resolutions at which there are no issues with squashing from 16:9.
Issue 3: the on-screen navigation bar feature that can be enabled with the option at Settings -> System -> Buttons -> "Enable on-screen nav bar" doesn't work properly.
To report issues, get a log from logcat and dmesg. If you are unsure of how to get both, there is good documentation out there for how to do so.
Sources:
A manifest containing all of the necessary repositories to make a build is in this repository on branch lineage-17.1: https://github.com/TALUAtGitHub/gtaxlwifi-manifests
Thanks to:
@Valera1978 - for all of the previous work for these devices, and for providing his old BSP sources without which the previously used open BSP sources wouldn't have been possible.
@followmsi - for fixes to various issues and other improvements, for useful information, and for working with me on much of this stuff.
LineageOS - for the Android distribution itself.
...and everyone else who's worked on anything that is in use.
No build for sm-t585?
Echo_2000 said:
No build for sm-t585?
Click to expand...
Click to collapse
Unfortunately not, as I mentioned in the original post.
Sorry.
Edit on 2020/12/22: for anyone who is reading this post and has missed my new note in the original post, installation is now allowed on the LTE variant in my latest build, so you can try my build on it.
TALUAtXDA said:
Unfortunately not. As I mentioned in the original post:
Sorry.
Click to expand...
Click to collapse
Too bad, bad no problem.
I installed this, mostly seemed to work OK, but although I could install Chrome from Play Store it would simply disappear (no error) every time I opened it. Tried Chrome Beta instead and same issue.
I don't know if Gapps related. I used Bit gapps for what it's worth.
Gone back to old build.
Thanks anyway.
Glenn2 said:
I installed this, mostly seemed to work OK, but although I could install Chrome from Play Store it would simply disappear (no error) every time I opened it. Tried Chrome Beta instead and same issue.
I don't know if Gapps related. I used Bit gapps for what it's worth.
Gone back to old build.
Thanks anyway.
Click to expand...
Click to collapse
Hi,
The issue was caused by SELinux denials. I've fixed these denials in this commit: https://github.com/TALUAtGitHub/and...mmit/0ec43a448795230a3d2d8576cd93c5b156468e21
I was able to get the SELinux denials you were experiencing as you told me how you encountered them. Attached is a zip archive named 'sepolicy_and_precompiled_sepolicy.zip' containing 2 files: 'sepolicy' and 'precompiled_sepolicy'. This is a new sepolicy containing the rules to fix the denials. If you decide to use my builds again, extract the zip archive and copy the 'sepolicy' file to /system/ and 'precompiled_sepolicy' file to /system/system/vendor/etc/selinux/ in TWRP with system mounted. You may want to run SELinux as permissive for now, though keep in mind that this will ignore denials. To set SELinux to permissive, run:
Code:
setenforce 0
I never caught these denials as I don't use Chrome, and use Bromite web browser which doesn't seem to trigger these denials. I'll probably upload a new build tomorrow containing a sepolicy with the new rules. Also, I've put this in the original post for reporting SELinux denials:
TALUAtXDA said:
There maybe more issues due to SELinux denials. If something doesn't work, test it with SELinux set to permissive:
Code:
setenforce 0
If the issue is no longer reproducible, it's due to SELinux denials. Get logs by running:
Code:
dmesg | grep "avc: denied" > dmesg_selinux_denials
logcat | grep "avc: denied" > logcat_selinux_denials
while SELinux is permissive after doing whatever triggered the denials in a shell and upload the files 'dmesg_selinux_denials' and 'logcat_selinux_denials'. It would also be preferable to report what triggered the denials. In some rare cases, SELinux has to be set to enforcing to get certain denials, which would unfortunately mean that every denied action isn't logged and it takes multiple tries to get every denied action causing issues. Don't report any random denials that don't cause any issues. I won't fix some denials (such as proc_version denials, which should be denied and it causes no real issues) and I'll only fix denials that cause unintended issues.
Click to expand...
Click to collapse
Thanks I will try it again soon.
Did as suggested, seems ok now! Thanks.
Good evening,
God bless you and thank you very much for fixing this beautiful rom.
I have a request and a question.
Request: I am using sm-t580. When I was using stock rom, I was able to cast my screen to my Samsung TV. I am aware that LOS and Pixel have removed this ability. Would you consider please to re-enable "smart cast". I would love to enjoy your ROM on my sm-t580 and be able to cast to Samsung TV.
Question: I am unable to edit build.prop or other system files. I tried to re-mount root but probably doing something wrong. Not very good with this. Could you walk me through how to remount and what do I need to use (what terminal inside your rom). I have root access with Magisk and in twrp used shell terminal with your command "mount -o rw,remount /" without success. Then I downloaded some some terminal app and tried. No use... I get "/dev/block/platform/13540000.dmmmc0/by-name/system" not user moutable in fstab. Thank you.
Thanks for building a rom with selinux enforced. I used encryption on 14.1 but it doesn't seem to work here. Some more denials to add, or maybe I need a newer recovery to format data with first?
Jet T said:
Good evening,
God bless you and thank you very much for fixing this beautiful rom.
I have a request and a question.
Request: I am using sm-t580. When I was using stock rom, I was able to cast my screen to my Samsung TV. I am aware that LOS and Pixel have removed this ability. Would you consider please to re-enable "smart cast". I would love to enjoy your ROM on my sm-t580 and be able to cast to Samsung TV.
Question: I am unable to edit build.prop or other system files. I tried to re-mount root but probably doing something wrong. Not very good with this. Could you walk me through how to remount and what do I need to use (what terminal inside your rom). I have root access with Magisk and in twrp used shell terminal with your command "mount -o rw,remount /" without success. Then I downloaded some some terminal app and tried. No use... I get "/dev/block/platform/13540000.dmmmc0/by-name/system" not user moutable in fstab. Thank you.
Click to expand...
Click to collapse
Hi,
You're welcome, though kudos to followmsi of course.
Smart cast seems to be a Samsung specific, proprietary feature. But we do have the generic casting feature available in Settings -> Connected devices -> Connection preferences -> Cast. Casting to wireless displays can be enabled through the 3 dot menu and then the "Enable wireless display" option and your TV should be detected. However, this doesn't work. A TV either doesn't connect or there's a soft reboot. I also have a Samsung smart TV with which I could test it with. The TV gets detected as "[TV] Samsung", and selecting it makes it say that it's connecting but it either stops trying to connect or it soft reboots and the TV displays an "loading" message that's infinite.
I found this while searching for "MediaPlayerService: listenForRemoteDisplay is no longer supported!" (this seems to be the main error): https://pastebin.com/s4utSi6c It seems like this issue has been reported before and existed at least a few months (though most certainly more) before my builds. I'll try finding a way to fix this, but my knowledge is unfortunately quite limited at this moment.
To do a mount command like that, you need to be root. To get a root shell, run "su", grant your terminal app root access and then run any commands needed to be run as root in that shell, such as that mount command.
EDIT: found this: https://forum.xda-developers.com/galaxy-tab-a/development/rom-t4006261/post81782081#post81782081 The replies say that you need to go back to Android 8 to use Miracast. I'm not sure if that's true but that's apparently how it is. There's probably nothing that can be done. Since smart cast is proprietary and Samsung specific, you'd only find it in Samsung ROMs. Also found this: https://forum.xda-developers.com/showpost.php?p=81369313&postcount=143 saying that support for Miracast is no longer available in Android 9 and 10.
I had another device where encryption didn't work. Turned out to be twrp writing incorrect (encryption?) footer when formatting data partition. But here encryption on 14.1 worked. Maybe encryption changed 14.1 to 17.1 with different footer, or maybe encryption on the los 17.1 base is broken on all devices. Difficult.
TALUAtXDA said:
Hi,
You're welcome, though kudos to followmsi of course.
Smart cast seems to be a Samsung specific, proprietary feature. But we do have the generic casting feature available in Settings -> Connected devices -> Connection preferences -> Cast. Casting to wireless displays can be enabled through the 3 dot menu and then the "Enable wireless display" option and your TV should be detected. However, this doesn't work. A TV either doesn't connect or there's a soft reboot. I also have a Samsung smart TV with which I could test it with. The TV gets detected as "[TV] Samsung", and selecting it makes it say that it's connecting but it either stops trying to connect or it soft reboots and the TV displays an "loading" message that's infinite. I captured a logcat at a time when it soft rebooted:
I found this while searching for "MediaPlayerService: listenForRemoteDisplay is no longer supported!" (this seems to be the main error): https://pastebin.com/s4utSi6c It seems like this issue has been reported before and existed at least a few months (though most certainly more) before my builds. I'll try finding a way to fix this, but my knowledge is unfortunately quite limited at this moment.
To do a mount command like that, you need to be root. To get a root shell, run "su", grant your terminal app root access and then run any commands needed to be run as root in that shell, such as that mount command.
EDIT: found this: https://forum.xda-developers.com/galaxy-tab-a/development/rom-t4006261/post81782081#post81782081 The replies say that you need to go back to Android 8 to use Miracast. I'm not sure if that's true but that's apparently how it is. There's probably nothing that can be done. Since smart cast is proprietary and Samsung specific, you'd only find it in Samsung ROMs. Also found this: https://forum.xda-developers.com/showpost.php?p=81369313&postcount=143 saying that support for Miracast is no longer available in Android 9 and 10.
Click to expand...
Click to collapse
I appreciate your answer!
I have now installed EX Kernel Manager as I had previously purchased it anyway when I (briefly) used the ElementalX kernel on my Pixel 3a.
I can see that we lose half the CPU permanently after the device goes to sleep, as you described, by looking at the dashboard.
Under Tools/User Settings I added a setting for /sys/devices/system/cpu/cpuhotplug/enable with a value of 0 as you suggested (to apply on boot) and this has cured the issue. It explains why I sometimes had smooth and sometimes not so smooth performance on the old rom! Now it's just always smooth.
Interestingly, I could not write to this value once the problem had occurred and the CPU was half disabled. The '0' value would not save, it stayed at '1'. It was not writable - is that a clue to the cause? I had to reboot and put the setting in EXKM before the device had been to sleep. Now it is fine even after reboot.
Thanks.
Thanks for your work and contributions to this device.
Many thanks for your work. Your ROM is working perfectly. No screen freeze.
Thank you for the rom!
I flashed it because it should have signature spoofing, but actually microG self-check doesn't tick signature spoofing permission and correct signature for play services and play store. Can anyone help me?
Jamess27 said:
Thank you for the rom!
I flashed it because it should have signature spoofing, but actually microG self-check doesn't tick signature spoofing permission and correct signature for play services and play store. Can anyone help me?
Click to expand...
Click to collapse
Hi,
It should be possible to select the "System grants signature spoofing permission" option in the MicroG self-check menu to get a dialog asking if you'd like to allow signature spoofing. Otherwise, you can grant the signature spoofing permission using a root shell or ADB with these pm commands:
Code:
pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
TALUAtXDA said:
Hi,
It should be possible to select the "System grants signature spoofing permission" option in the MicroG self-check menu to get a dialog asking if you'd like to allow signature spoofing. Otherwise, you can grant the signature spoofing permission using a root shell or ADB with these pm commands:
Code:
pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
Click to expand...
Click to collapse
Thanks for the fast response! I got the permission with the dialog in MicroG, but apps still don't find google play services
Jamess27 said:
Thanks for the fast response! I got the permission with the dialog in MicroG, but apps still don't find google play services
Click to expand...
Click to collapse
You're welcome. Now, the signature spoofing permission is granted to microG, but from what you describe, it's likely that play store (or fake store) doesn't have the signature spoofing permission. You can check if this is the case by opening the MicroG self-check menu and checking if the "Play Store (Phonesky) has correct signature" item is checked. If play store doesn't have the signature spoofing permission granted, you need to run this one pm command in a root shell or using ADB:
Code:
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
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.