Stryxus said:

If you have managed to get LineageOS 20 to build for the tablet, im astonished. I spent weeks of trial and error and never got it to work after the code compile.

I never built myself, downloaded them from Sourceforge

kevinco1 said:

I never built myself, downloaded them from Sourceforge

Oh, well that explains why they dont work then. Sourceforge is filled with stuff which doesnt work.

Stryxus said:

Oh, well that explains why they dont work then. Sourceforge is filled with stuff which doesnt work.

kevinco1 said:

You need to understand that this tablet is budget, even for Samsung standards and therefore is quite limited in it's capabilities. Most of all the GSIs with countless customization options that I’ve downloaded from SourceForge work fine on my phone, but do not install on this tablet because of it’s limited system partition.

I’ve posted about this in a different thread, but if you are looking for the latest Lineage OS to run on this particular tablet flash this one:

https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download

I’ve been running it for the last month and besides no compatibility issues it’s much faster than the stock OS. No hate against OneUI 5, but this tablet’s specs handle Samsung’s latest OS poorly.

Click to expand...

Oh its definitely doable, its just that its dealing with a proprietary board from a backwater Chinese chip designer and doesnt conform to standard Android requirements yet it obviously works if Samsung can get it to work.

Also its not the limited system partition, that is fine, its just packaging the code into something which conforms with the board of which not many of us know about.

Stryxus said:

Oh its definitely doable, its just that its dealing with a proprietary board from a backwater Chinese chip designer and doesnt conform to standard Android requirements yet it obviously works if Samsung can get it to work.

Also its not the limited system partition, that is fine, its just packaging the code into something which conforms with the board of which not many of us know about.

First of all, Samsung is NOT a Chinese Co. It is S Korean and is one of the largest co.s in the world. (Guess who makes the Raspberry Pi boards IN ENGLAND) And it IS the size of the system partition that is the problem and that is dynamic and NOT fixed. I've seen the problem on other Samsung tablets where people succeeded in resizing it. The problem is, each tablet has a different partition setup and if you make a mistake you can hard brick your tablet.

IOW, this problem IS fixable. It is just going to take someone with the right expertise to do it. There are even instructions on how to do it by installing a partition manager, looking up the partition info for the device and then knowing what partitions to move to make room for resizing the system. But I don't want to be the first to try it and risk bricking my tablet.

lewmur said:

First of all, Samsung is NOT a Chinese Co. It is S Korean and is one of the largest co.s in the world. (Guess who makes the Raspberry Pi boards IN ENGLAND) And it IS the size of the system partition that is the problem and that is dynamic and NOT fixed. I've seen the problem on other Samsung tablets where people succeeded in resizing it. The problem is, each tablet has a different partition setup and if you make a mistake you can hard brick your tablet.

IOW, this problem IS fixable. It is just going to take someone with the right expertise to do it. There are even instructions on how to do it by installing a partition manager, looking up the partition info for the device and then knowing what partitions to move to make room for resizing the system. But I don't want to be the first to try it and risk bricking my tablet.

Click to expand...

Um, I never said Samsung Is a Chinese company? I said they use a board and SoC from a backwater Chinese company. And yes it is fixable, its just very proprietary and getting the firmware for all of it is going to be very difficult, iv tried and got most if not all of it but there is no telling how much.

And you are over simplifying the processes of partitioning, every board does partitions differently more than they do it the same. This tablet is missing many partitions you would usually find on a Qualcomm board. I forget which ones exactly since I havent tinkered with this in months. This means Android has to be compiled in a specific way to support all the firmware and partition configuration and how? I do not know.

Stryxus said:

Um, I never said Samsung Is a Chinese company? I said they use a board and SoC from a backwater Chinesee company. And yes it is fixable, its just very proprietary and getting the firmware for all of it is going to be very difficult, iv tried and got most if not all of it but there is no telling how much.

And you are over simplifying the processes of partitioning, every board does partitions differently more than they do it the same. This tablet is missing many partitions you would usually find on a Qualcomm board. I forget which ones exactly since I havent tinkered with this in months. This means Android has to be compiled in a specific way to support all the firmware and partition configuration and how? I do not know.

Android is based on Linux and uses the same partitioning. The partition manager app will work on ANY Android device and give you the exact current partition layout. And every device maker uses it's own partitioning schemes. Not just Samsung. And it changes with every new version of Android. There is no such thing as a "standard" PIT. There is no "compiling" needed to resize partitions. It can be done with simple fastboot commands.

lewmur said:

Android is based on Linux and uses the same partitioning. The partition manager app will work on ANY Android device and give you the exact current partition layout. And every device maker uses it's own partitioning schemes. Not just Samsung. And it changes with every new version of Android. There is no such thing as a "standard" PIT. There is no "compiling" needed to resize partitions. It can be done with simple fastboot commands.

You just told me you have absolutely no idea what a partition is. This 'partition manager app' will not work on any device also. Things like TWRP have to be compiled for every device its run on in a very similar way that Android does for so many different configurations.

And no, this has nothing to do with partition size, it has to do with what partitions the board supports and how Android is compiled to utilise what partitions it does support.

Stryxus said:

You just told me you have absolutely no idea what a partition is. This 'partition manager app' will not work on any device also. Things like TWRP have to be compiled for every device its run on in a very similar way that Android does for so many different configurations.

And no, this has nothing to do with partition size, it has to do with what partitions the board supports and how Android is compiled to utilise what partitions it does support.

I built my first computer in 1979 and have been dealing with partitions ever since. And I've been using Linux for 20 years. It appears to be you who doesn't understand them. There is already a working TWRP for the X200 that enables fastboot and fastboot is all that's needed for resizing, creating and deleting partitions. You would ONLY need to recompile TWRP if you modified it to have a button to "Fix System Partition Size".

Edit: You might want to checkout this thread, where the exact same problem was fixed for the Tab A7 using fastboot. Of course it won't work for the X200 because the partition table is different, but it give you the idea of how it's done.