yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Sjll:
#include <std_disclaimer.h>
/*
* 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.
*/

About LineageOS

LineageOS is a free, community built, aftermarket firmware distribution of Android 10.x (Q),

which is designed to increase performance and reliability over stock Android for your device.

All the source code for LineageOS is available in the LineageOS GitHub repo.

And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

Official LineageOS website : http://lineageos.org

About LineageOS Legal : http://lineageos.org/legal/

Important Information

1. This ROM will never work with any versions of Google Camera (GCam)!

2. You need to flash Stock Android 10 before flashing this ROM.

3. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!

4. Do not flash odm image from SODP.

Downloads Links

LineageOS 17.1:

Unofficial-build: Link

Sony Camera: Link

Google Applications (optional):

OpenGapps: http://opengapps.org/ (ARM64->Android 10.0->Pico, Nano or Micro)

Information: Flash the GApps before the first boot. If not, a clean flash is recommended.

Flashing and updating

How to flash

Make sure you are upgrade to Official Android 10.0 from Sony

Unlock bootloader is necessary.

To disable AVB 2.0 using fastboot:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Sideload LineageOS in Lineage Recovery

You can refer to XZ2's wiki

Warning: If you stuck at boot animation, you need to unplug your TF card.

Root access:

Sideload Magisk in recovery.

Issues and reports

Report issues only if you are using the ROM kernel

If an additional mod is installed, make sure it's unrelated, and mention it

Make sure the issue wasn't discussed earlier in the threads

Share a log of the error with CatLog for example

Also thanks to:

Luk1337

The LineageOS Team

The CyanogenMod Team

Everyone involved in working and testing

XDA:DevDB Information

Lineage 17.1 for Xperia XZ3, ROM for the Xperia XZ3

Contributors

Sjll, Olivier

Source Code: https://github.com/sony-sdm845

ROM OS Version: Android 10

ROM Kernel: Linux 4.9

ROM Firmware Required: Official Android 10.0 firmware

Based On: LineageOS

Version Information

Status: Stable

Created 2021-05-09

Last Updated 2021-05-12
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Sjll:
Here is the rebase kernel for LineageOS 17.1/18.0/18.1, which tag at LA.UM.9.3.r1-01700-sdm845.0. You can try and feedback to us. Some wired issues like TF card reading should be fixed.

Steps: Flash dtbo in fastboot and sideload the Anykernel3 in LineageOS Rec.

Device:

akari > XZ2

apollo > XZ2C

akatsuki > XZ3

Downloads for : Sony Xperia XZ2 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Artemian:
Nope, still restarting, and boot-freezing :/
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Sjll:
What was restarting? new kernel?
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Artemian:
I was flash the new kernel, start the phone... everythin goes well. I put the SDCard int phone and phone starts to scanning that card. After few minutes phone gonna restart yourself and stuck on the LineageOS logo (after few animation repeats it freezes). Back of the phone was hot as hell.
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Artemian:
NEXT ISSUE is with Google WEAR app. I cant copy my Google account into my watches. Everytime a want to copy that acc into watches, tha app gonna crash. I tried that on STOCK rom, and it was OK. Back on the L.OS it's not.
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Sjll:
I already said. this kernel is for testing, if you met any issue, try to back to default kernel please.

About Android watch, no idea. I do not have one, and LineageOS did not provide any Gapps, not sure if this is related with Gapps.
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Artemian:
I tried this... but That app isn't working. UNKNOWN ERROR says 🤷🏻‍♂️
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Sjll:
Download Lineage OS 0513 version.
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Artemian:
Before i try LineageOS18, i try install, latest update of v17 from you, and give you a feedback. :)
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Artemian:
LineageOS 17.1 20210514

I was made FACTORY RESET before i started to test latest release

XPERIA XZ3 Dual (H9436)​

During welcome setup >> Wi-Fi preferences *tap* (blakscreen)

During welcome setup >> Wi-Fi won't start to run (the slider just slide to off position itself)

In the system >> Wi-Fi won't start to work (button just goes grey [off] again)

When i put the SDCard, when system start to scan that card, OS reboot and freeze on the bootlogo
[Sony Xperia XZ3 ROMs, Kernels, Recoveries, & Other] Sjll:
Comfirmed this issue, already removed 0514 version.

Thanks.
[Touch Diamond, MDA Compact IV General] Ximoon:
Hello there, I haven't found any info on this so I post here...

Opera 9.5 auto zoom out of any internet page when it loads it, and what bothers is it doing that even when the webpage is optimized for VGA display... Any idea to prevent that (whether it should be something to add to the HTML code of the page, or a setting in opera) ?
[Touch Diamond, MDA Compact IV General] Ximoon:
Going menu>settings>display>activate mobile display (or whatever is the name of the option in english) sortof fixes the problem, since the page is not zoomed out, but it disables most of the CSS and stuff.

I searched the registry to see if the default virtual resolution used by opera was in there, but found nothing.

Still seeking ^^
[Touch Diamond, MDA Compact IV General] Ximoon:
OK, found it :

Change virtual screen width :

Open /windows/opera9/opera.ini

Change value "[Adaptive Zoom]/Virtual Screen" from 960 to 480.

edit :

In fact, it's ok for viewing, but you still have to zoom somehow to click a link, input text or anything. Still searching :D
[General Questions and Answers] _Dayo:
I'm tring to install A305F firmware into A305N device. It's able to do that? I'm not sure that these devices has same processer because I'm not good at searching this... Thanks for help :D
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] randommodule:
Just installed it on a device that was still running stock. Works flawlessly, thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] quantumcog:
Can I get md5 checksum?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
It's 382e0ae70a956deec826c6867cf80614 for lineage-18.1-20210508-UNOFFICIAL-gtaxlwifi.zip. Anything wrong?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Chris_0147:
I have a problem with connectivity since April I only get 2mb / s per second when I pay for one 20mbps

This problem is only in android 11 when I go back to some android 10 ROM there is no problem

there are the results of bliss roms
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] autorage:
Thank you for your (and @followmsi 's) ongoing support for this device!

My T-580 never felt old to me because of you!

A couple of observations:

-onscreen navigation bar works for me, just the "disable hardware buttons" part does not.

For workaround I use Srgrusso's patch from here.

-Safetynet fails where it hadn't before. (no biggie for me, just a thing I noticed)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] n0j0e:
Great rom! 👍

I flashed this + Flame Gapps and Magisk 22.1.

The first custom rom for this device where Ableton Link works!! 🤟✨✨✨
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gechu:
Hi @TALUAtXDA and thanks for your your work ,and the other behind the release

My needs are very basic, I just need something stable, no need for root, sd-card storag etc..

Would this be the preferred ROM? Or is the 17x release a better for my needs?

Regarding Gapps, I noticed that users are using Flame Gapps and NikGapps, but I guess the regular Open Gapps could be an option as well.

What is the recommended Gapps variant?

Kind regards Erik
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jrollf:
Anyone else check this yet? It's working for me on @TALUAtXDA's previous version (202010407). I use this feature quite a bit as internal storage is too small, don't want to lose it if I dirty flash this version.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
I'm referring specifically to the "Enable on-screen nav bar" option at Settings -> System -> Buttons, that doesn't require any system-level changes as made by that package that you've linked. When enabling it, no touch input is accepted anymore for some reason. It needs to be locked and unlocked a few times for it to accept input and the on-screen navbar added through that feature to work temporarily.

I have no idea about this. I'd have thought that it's now more likely to pass.

Hmm, wow.... I didn't expect that to be fixed in this release. That's great. :)

For stability, 17.1 would be slightly better. With 18.1, there are certain occasional crashes (see issue 1) that I'm not sure about at the moment, which you may or may not be able to tolerate.

As for Google apps, it's whichever is the smallest variant. For nikgapps, that would be core, and for opengapps, that would be pico. Something to note is that opengapps seems to often be more problematic for Android 11 than other google app packages, so it could be better to go for something else.

I actually didn't know if adoptable storage was working in my previous release. I just assumed it didn't considering that it never worked properly with 17.1. Knowing that it did in my previous release of 18.1, it would probably(?) also work with my latest release.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] js-xda:
With NikGAPPS core, SafetyNet passes succesfully in my case.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jrollf:
Ok, I just dirty flashed it, SD as Internal Storage seems to still be working. Thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Alright, thanks for the information. I've removed that from the list of issues. You're welcome.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gechu:
One more question, does this rom impact supported widevine level?

Had similar question about safetynet, which at least one user claimed worked using NikGAPPS core. Anyway else with experience related to safetynet?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
The widevine security level is L3, and always will be L3.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Lumito:
Found an issue: system recovery doesn't get overwritten when installing lineage-18.1-20210508-UNOFFICIAL-gtaxlwifi.zip. Might be related with SELinux.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Wouldn't that be what you would want so that you don't lose TWRP? We've specifically disabled that feature by setting the "persist.vendor.recovery_update" property to "false" since we don't want to use Lineage's recovery.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Lumito:
Maybe, it makes sense. TWRP is more powerful, and faster when installing updates.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] quantumcog:
The downloaded build was corrupted

I downloaded it again. Now it is working fine

Anyways, Thank you for such a great rom
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] n0j0e:
..ok i rushed to fast. Ableton Link didn't sync correctly!

My guess there is something broken or missing in the LOS network stack or WiFi driver for the SM-T580 (gtaxlwifi).

I have an OnePlus 5T with LOS 18.1 (crDroid 7.6) and all apps with Ableton Link are in sync and stable over WiFi.

Here my message from planet-h.com forum:

Hi,

i have a Samsung Tablet SM-T580 WiFi and tried nearly every A10/A11 custom ROM, mostly LineageOS.

I can connect with other devices without trouble but if i start play in G-Stomper the sequencer LED's are flashing absolutely crazy and beats are rumbled.

Same with RemixLive but Snap from Reactable runs rock solid with Ableton Link!

Tried all audio drivers with various latency settings.

Tried switch some network options in the Developer options.

Tried various Devices with WiFi Hotspot or with Wifi AP.

Nothing helped. G-Stomper products & RemixLive connects but didn't sync correctly. Snap plays absolutely stable.

No Firewall, no custom DNS, no AdAway.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] D.u.G.:
@TALUAtXDA -​

First off thank you for compiling an 18.1 rom for this old tablet. Me boy has one, and I badly need to wipe, update it - so may as well make it a fresh, new lineageos 18.1

Apparently, years ago I rooted the stock os with twrp and rooted with magisk. This was back on android 7 however.

So,,,,,, Can you give the proper steps to take to install your new lineageos? AKA, do I need to update twrp? Do I need to update stock OS before flashing lineage?

Also, if I do need to update twrp, as I expect I do, not even sure if there is a twrp for A11 yet, so I may have to use lineage recovery???? If you could include some basic instructions.

Finally, is there a way to go microG on these old devices? I have a new phone I am using the lineageOS + microG rom (easier than figuring out microG install) so I'd like to see if it's possible while this stuff is fresh in my head, but I can do without microG if it's difficult.

AKA< please advise as below.

1- flash "this" recovery via adb or odin (version)

2 - flash "this" rom + magisk+ whatever + profit

This would be very helpful, as this device is so old there is not updated info.....

Thanks,

D
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Uluru25:
I just wanted to switch to your rom but unfortunately I did a dumb mistake (ignoring some Samsung specific problems) and would therefI just wanted to switch to your rom but unfortunately I did a dumb mistake (ignoring some Samsung specific problems) and would therefore highly appreciate your help. Since the help I need is not related to your rom, should I better send you a pm outside this thread?ore highly appreciate your help. Since the help I need is not related to your rom, should I better send you a pm outside this thread?

Solved!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rawwrius01:
The file is not public, i would try it today.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Oops, sorry. I've made it public just now.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
You're welcome.

I would recommend updating to the latest version of the stock firmware before installation. If the stock firmware that you have now happens to be too old, this would be a requirement. Look back to the last several posts for some basic instructions on how to do so and also some other information.

You just need the latest TWRP build from here: https://dl.twrp.me/gtaxlwifi/ Use Odin to install it after updating to the latest version of the stock firmware from the available tar archive (which you need to select for the AP slot).

As for microG, you can get installation packages for it. I'm using Nanodroid microG.

After updating to the latest version of the stock firmware and installing the latest TWRP build, in TWRP, you would just need to format the system and data partitions (Wipe -> Format data to format the data partition), possibly reboot into recovery again after that, and transfer and install my build and any additional packages (Magisk, one for microG and any others) that you need.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rawwrius01:
It's booting fine!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] anderskaseorg:
Thanks for working on this device! I tried this out on my P580 and noticed an issue: if I try to enable encryption (Security → Encryption & credentials → Encrypt tablet), the device warns me that it will take an hour or more, but then just reboots in ~20 seconds without encrypting anything. I found this error in logcat:

08-29 22:44:25.331 2510 2510 D vold : fdeEnable(3, *, 0)
08-29 22:44:25.331 2510 2510 D vold : !fscrypt_is_native, spawning fdeEnableInternal
08-29 22:44:25.334 2510 8668 E Cryptfs : Bad magic for real block device /dev/block/platform/13540000.dwmmc0/by-name/USERDATA
08-29 22:44:25.335 2510 8668 E Cryptfs : Orig filesystem overlaps crypto footer region. Cannot encrypt in place.

which this old issue suggests is a problem with the filesystem size.

(Though shouldn’t an Android 11 device be using FBE rather than FDE, anyway?)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
You're welcome. That issue would indeed be caused by the size of the userdata filesystem. In the userdata partition, there needs to be a small amount (20480 bytes considering 32GB devices) of unallocated space left at the end of it after the actual filesystem for a crypto footer, which is mentioned in that last error message.

Such small amount of space needs to be left during formatting, which is done in TWRP. Therefore, the issue is not actually in my build, but rather the TWRP build that has to be used. Looking at the device tree that was used for @unknowwiiplayer's TWRP build, in the recovery.fstab file, a flag called "length" is not set for userdata: https://github.com/unknowwiiplayer/...cbcfb6293bf4955c46a42c4f4f/recovery.fstab#L18

For TWRP builds for gtaxlwifi, the "length" flag is set to "-20480", to leave 20480 bytes at the end of the userdata partition after the filesystem when formatting here: https://github.com/TeamWin/android_...4c161da6608d3cc48c3926d40f2/recovery.fstab#L5

I'll look at getting a working TWRP build out in some way that won't cause that issue slightly later.

These LineageOS builds and I think most others are still setup to use FDE, which is still a thing, but I think is slated for removal for a later Android version (Android 12 will as far as I can tell probably be the last version supporting FDE). I've personally chosen to stick with FDE for now due to some usability issues that currently exist with FBE that I found while testing it out (such as TWRP not being able to mount data filesystems encrypted using FBE).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Alright, awesome! As promised, I'll continue making builds for the P580.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 60Tom:
Wow... I'm really pleased I found this discussion and congratulate those who developed this upgrade for our old Samsung Tablet. Wife said use her old tablet or it was going to our grandson. At 27 he can buy his own tablet!

I've surprised myself that in a week I've been able to install Odin and then use it to install TWRP on the tablet. TWRP installed this ROM onto the tablet and I even managed to root the device by installing Magisk. The old tablet has a new lease on life... like me :)

I hope I'm not in the wrong area but what I'd like to do with the tablet is make it a gps head unit in our 4WD. I want it to automatically power up when the ignition is turned on and have read this is possible by modifying the boot loader. My googling suggests I need to run a command "oem-off-mode charge 0"

Is this possible with this ROM????

Thanks

Tom
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sams_a6:
I'd echo this, a massive thanks to TALUAtXDA for making this rom! I wanted to revive my T580 which was running so slowly on the bloated Samsung (now outdated) firmware, and this has been a massive boost to it's performance and probably saved me buying a new tablet for another few years.

Thanks davemaxd for these great instructions! Just enough detail to get me all up and running! Appreciated!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Sage:
agree. installing this now!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rymaaan:
@TALUAtXDA Wow I've been out of the custom ROM scene for a long time now so was very surprised to see custom roms by you and @followmsi for the T580. Didn't think there would be any for a tablet that is 5 years old anyway and was ready to sell it on until I found your ROM. It has given the 580 a new lease of life and certainly better than the stock rom now its no longer in supported, so thank you and hope you both continue the amazing work on the scene for the T580. 👏
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] VioletViolin:
You have no idea how grateful and excited I am knowing that someone finally ported a aosp rom to this tablet. Been using mine as a digital artbook for 4 years now, frustrated about how sluggish stock Oreo is.

Despite knowing that so far there's only builds for P580, I would install this on my P585 anyway, and I did!

Booted perfectly, S-pen worked with "hover detection", will test pressure sensitivity later. No sim/mobile data of course, but I don't really care about that, rarely ever used it anyway.

Again, thanks a ton!!! Looking forward for P585 build for full functionalities!

Update 1: S-pen pressure sensitivity works, however palm rejection behaves weirdly that pen input frequently became unresponsive.

Update 2: no vibration. Sometimes SystemUI crashes when openning setting from expanded quick toggles.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] skiwarz:
Worked for me...

I spent two straight weeks trying (unsuccessfully) to modify your T580 code to work on my P580... and here you just did it without even owning one... nice job.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] manalishi:
Hey @TALUAtXDA, I like the ROM, however, I'm trying to figure out an annoying issue - the screen locks after each time I adjust the volume. Is there any way that I can diagnose/resolve this?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Uluru25:
Dear @TALUAtXDA, your work to keep this tablet alive by providing a modern rom is fantastic! It works pretty fine and enjoys me every day. Thx!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Thebacklash:
So i’m having a little issue here. I’ve installed CFW in the past on other phones/tablets, but never used TWRP.

Used the files and instructions here and in the “Newbie Friendly” thread that was also posted in this thread. I can get Lineage 18.1 up and running now, but when I check to verify Root it says i’m not rooted. (Root Checker)

I probably don’t need root anyway, it’s the point that I can’t get it to work following the instructions. This tablet is just a test to see if i want to switch my S10+ over to lineage permanently. And from what i’ve been reading root must be done during install and can’t be done afterwards?

Using the TWRP and SuperSU method (SuperSU 2.82 is the newest version i found)

When I do the install in TWRP i select the Lineage zip, then the Gapps zip, then the SuperSU zip.

Is there something i did wrong? wrong order? Missed something?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Uluru25:
I used Magisk (v23.0) instead of SuperSU: download the .apk file, manually rename the extension to .zip, the boot into recovery and install this zip. Secondly, I don't use gapps, but this should not be a concern.