yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Unlike to other ROMs/kernels you are not able to switch between "permissive" and "enforcing" mode.

Right now you can not switch yourself via "setenforce 1" .. you always stay "permissive".

https://github.com/followmsi/androi...m64/configs/lineage-gtaxlwifi_defconfig#L4410

We need to change kernel first .. to "allow" enforcing mode.

There were done a few code changes to prevent enforcing mode.

Needs to be checked and tested ..

This is just the kernel part here .. Once done we need to work on the sepolicies itself .. this will take some time as well.

To answer your question .. it will take longer to get "enforcing" mode on RR for SM-T580/585.

Sorry, I am not able to tell you more details now.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Most probably it will work to update via Magisk app .. needs to be tested.

The problems seems to be related to the changed magisk scripts since version 14.6 .. the unpack and repack of certain boot.img is not working anymore.

The reason why it's bootlooping .. the (newer) magisk binary seems not to be the problem in this case.

Not sure if anybody did inform Magisk team about this problem ? .. I did not either !

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] okij:
Thanks for your detailed answer!

The reason I was asking is that I'm thinking about updating my wife's SM-T580 tablet from stock rooted 6.0.1 to RR 5.8.5 and I'd like to be sure that everything is working so she won't be angry at me after the update ;). From what I read on your thread, all features should be fine for the SM-T580 model, but I was wondering if the performance is on par with the stock rom.

Actually I didn't benchmark the SM-T580 yet, but now I did, using Geekbench 4. On the overview page interestingly it says "Cluster 1: 4 Cores @ 0.00 Hz" and "Cluster 2: 4 Cores @ 1.59 GHz", so probably four of the cores also aren't used or aren't shown correctly on stock 6.0.1 ROM.

Anyway, could you do me a favour and run the CPU benchmark of Geekbench 4 on RR 5.8.5, so that we can compare the scores? The results I got were "Singe-Core: 727" and "Multi-Core: 3615". Thanks in advance. :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
As I want to know the results myself .. :)

Pls find results from latest "unmodified" RR version attached !
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] okij:
Great, thanks for testing! So it's even a bit faster than on stock 6.0.1, also on multi-core. :cool:

I'm wondering if enabling HMP would double the multi-core score. :D I guess that it will rather not, but could you test this with your HMP-enabled kernel if you have some time?

Edit: For comparison, I now did a test run of Geekbench 4 on my phone (Sony Xperia Z3 compact) which has a Snapdragon 801, so only 4 cores. The results were "Single-Core: 1040" and "Multi-Core: 2785", so less than 4 times the single-core result, which seems quite logical to me. On the other hand, on the SM-T580 the multi-core result was more than 4 times the single-core result, so IMO more than four cores are working at the same time under heavy load on the SM-T580. :good:

Thanks for your detailed installation instructions on the OP. I'm not sure if I have enough time left today to do the update and restore all apps again via TitaniumBackup. However, I'd like to ask you these questions just to prevent screwing something up:

The TWRP version on the tablet is 3.1.0-0 - is this OK?

I will first take a full backup of the system and data partitions of the working stock 6.0.1 installation. Just in case, will it be possible to easily revert to stock by restoring the 6.0.1 system and data backups and wiping cache and dalvik?

Would it be possible to not wipe the data partition when going from stock to RR 5.8.5? I know that dirty flashing usually is not recommended, but could it work? (I know that if it doesn't work, I will have to wipe data and restore everything with TitaniumBackup anyway.)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 4929york:
I guess you didn't read the article I posted. NO ROM EVER has both sets of CPUs on at the same time. The whole purpose of the BIG/little design is that one set of cores is high speed (the set that shows in the benchmark) and the other has low battery drain and is the one on most of the time. The high speed cores only turn on during high CPU demand. This is true of ALL tablets using this SoC. The SoC itself doesn't allow for both sets to be on at once. If it did, the battery wouldn't last very long at all.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Cybertom3000:
I just tried to update via Magisk app from 14.5 to 15.3 and it ends with bootloops. I flashed 14.5 again and (nearly) everything is fine. I still have (and had this before reflashing) an issue with Magisk superuser. It doesn't remember the permits and the superuser section in magisk is always empty. After rebooting Magisk aks again for su permissions.

I came from Ultra Lean Rom with Magisk 15.3 before flashing this awesome ROM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ROM-mer:
Same
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Cybertom3000:
Same bootloops or same su Problem? :confused:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
This is related to magisk manager version .. I still use version 5.4.3 and the Su settings/permits are kept.

Pls inform magisk team and let them know about bootloop problems on sm-t580/585.

This will help all of us ..

Thanks

EDIT:

Ulta lean ROM is using stock samsung kernel ?

Does magisk 15.3 fully work on this ultra lean Rom ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
I did want to test the HMP kernel .. but the geekbench app needs internet access to perform a test :(

Anyway .. backup your current data partition and start playing with RR.

And why not using latest official 3.2.1 TWRP ?

Just install via TWRP itself and reboot into recovery again to use the new version.

I own this tablet since 2 months and I had stock firmware installed for one day.

Can't help you better .. you need to test dirty installation.

If you know how to use TWRP and Odin you will always find a way to proceed. ;)

Good luck !
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Cybertom3000:
It works! :good: THX :)

I will do this and report here later

I never checked the kernel in my tablet running with Ultra lean ROM. But following the Ultra lean change logs it came always with samsung stock kernel. But I definitely can confirm magisk 15.3 was fully working on Ultra lean Rom v10.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Interesting .. 15.3 works on stock kernel.

Will make another test kernel in the next days .. maybe we can fix it for RR too.

Thanks !
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Cybertom3000:
Done! Just posted here.

You're very welcome. It's much more work to develop a ROM than to answer your questions :highfive:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ROM-mer:
Both:)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] okij:
How stupid! :( In this case, a different benchmark app might help. I don't know if e.g. Basemark would be OK, at least it also has single- and multi-core tests.

Yeah, I already started before you posted this and everything went fine and is up and running now. :)

Do you mean the one from this link?

No worries! I actually tried it, but it just throws "Error 7" because it says the data partition isn't compatible. So I erased it and restored all apps via TitaniumBackup.

Thanks for your help and this ROM! :cool: My first impressions are really good and I haven't even looked through all the customisation options yet.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Magisk 14.6 / 15.x !

UPDATE:

New instructions to install latest Magisk .. for 580 and 585 !

Just made a new kernel today .. this way you can upgrade to latest Magisk version.

As well I have removed the "forced" permissive mode.

The root cause seems to be related to "TIMA/KNOX" implementation in samsung kernels.

Since Magisk 14.6 the kernel binary seems to get changed/patched by the Magisk installer.

As it looks like - this will cause the bootloop.

I have added TIMA/KNOX to kernel config and latest Magisk is not bootlooping anymore.

Maybe Magisk installer assumes it's a stock Samsung kernel and will do hexpatch which results in bootloop.

Needs to be checked in detail.

But the super-strange wifi module does not like the TIMA/KNOX config change .. it stopped working. :(

For this reason we need to apply the "normal" kernel binary after Magisk installation.

Until this wifi module stuff is sorted out - if ever - you can use the following workaround to install latest Magisk version.

Pls install in correct order .. via TWRP !

Initial Magisk installation:

1. unpack latest RR boot.img from latest RR ROM and install it via TWRP -> to clean current Magisk/SuperSU installation!

2. install latest Magisk version via TWRP

3. install either 580 or 585 kernel.zip - pls see below

4. reboot into system

After ROM upgrade and automatic magisk installation thru ROM installer:

1. install either 580 or 585 kernel.zip - pls see below

2. reboot into system

You will have to do this step after each ROM update !

580 -wifi

rros-kernel-gtaxlwifi-20180205.zip

585 - lte

rros-kernel-gtaxllte-20180205.zip

Changes:

- Kernel: removed "forced" permissive selinux mode -> you can change to enforcing mode via "setenforce 1" now.

Found an issue by mistake .. this change will be moved into next release

- Changed DRM service groups -> to fix DRM service start

Not sure how to proceed with this wifi module .. blocking HMP, custom kernel, TIMA .. etc.

No time for further analysis !

Cheers

EDIT:

- Pls use latest Magisk 16.0 !

- The boolop problem is fixed since BETA 15.4.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BADA 187:
[MENTION=5480152]followmsi[/MENTION]

hi there, i could not get a response in the LOS thread, i guess it was not important enough for them to even acknowledge this issue, so ill just copy paste the issue here since it affects everyone using the twrp that is found in the LOS thread.

Whats wrong with this twrp? For T585, it just will not restore a nandroid (twrp) backup..

And gives me a red warning at bootlogo something with "recovery not enforcing seandroid"

can anyone else confirm this?

my knowledge does not go that far yet to make/port twrp for the t585.

all i can do is compile roms etc etc that direction. twrp is still on my to-do list.

i see this bug as a major issue since people rely on a backup with all their data to be safe.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
This is common error in TWRP 3.2 .. for all devices .. the reason for the quick hotfix release 3.2.1.

TWRP needs to be compiled again - using 3.2.1 sources.

Nevertheless .. as the fstab is identical with wifi version why not using official 3.2.1 for wifi version on your lte version ?

If you want to remove the seandroid warning .. just type.

echo "SEANDROIDENFORCE" >> name_of_recovery.img

Flash the changed recovery file and reboot .. the warning will disappear.

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bytetemplar:
Was wondering why Netflix quality was looking poor and did a test of DRM.

https://play.google.com/store/apps/details?id=com.androidfung.drminfo

It seems Security Level of Google Widevine DRM is only L3 on this ROM thus only giving 480p on Netflix :(

I dont know if its possible to get it to L1 on custom ROMs though, need to search more info, unless someone here knows more about it and if its possible for "fix". Id like to watch HD on Netflix...

And regarding TWRP, when I was installing RR, I had wifi version installed first and it refused to install 585 ROM cause of wrong device ID and had to flash the one from LOS thread to even install ROM. Has this changed?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Depends on the widevine blobs .. on some devices L1 is possible .. what is stock ROM ..?

How do you verify if it's 480p only ?

Yes .. the ROM installer is checking the device.

It's the first line inside the update scripts.

You need to unzip and remove the line manually .. this will allow you to install the LTE ROM via WiFi TWRP version.

I know it's not the ideal solution .. when time is left we can compile a 585 TWRP version.

EDIT:

Remove this line .. and zip the ROM again .. and flash via TWRP.

assert(getprop("ro.product.device") == "gtaxllte" || getprop("ro.build.product") == "gtaxllte" || abort("E3004: This package is for device: gtaxllte; this device is " + getprop("ro.product.device") + "."););
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bytetemplar:
It seems Netflix is bit stupid on mobile devices

https://help.netflix.com/en/node/23939 (Netflix in HD -tab)

This tablet isnt even officially supported, so there is that too.

But its easy to modify Netflix APK to bypass that restriction

https://xdaforums.com/showpost.php?p=65001865&postcount=12

But wont help if we cant get Widevine L1 DRM to work in ROM. Someone with official ROM (or any other) maybe can run that test app to see if it is supported? Never came in my mind to check such a thing when using official ROM for first few weeks, but video quality on same TV serie seemed much better then, but might be placebo (most probably).

To see what resolution Netflix is giving on mobile devices, search for " test patterns" in Netflix app and start watching desired format. There is yellow text on upper right corner that shows you current info regarding stream quality, just wait it to adjust for a moment. Max I get is 720x480p on this tablet...

And thanks for the tip regarding that TWRP id check, might aswell flash wifi version ffor now and do that little tweak when needed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
TWRP 3.2.1

Fresh compiled TWRP versions for sm-t585 and sm-t580.

Based on latest twrp (oreo 8.1 branch) and RR (Nougat) sources.

No Odin versions available - recovery.img only !

twrp-3.2.1-0-gtaxllte-RR.img

twrp-3.2.1-0-gtaxlwifi-RR.img

Installation:

1. Pls download new TWRP version onto your tablet or sdcard and reboot into TWRP

( If you don't have any TWRP version installed pls use official WiFi version via Odin - as intermediate step. )

2. Install the new twrp-3.2.1-0-gtaxl***-RR.img as "install image" onto your recovery partition.

3. Enter TWRP reboot menu and reboot into recovery again.

Not blue anymore .. it's orange now.

Enjoy :p
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BADA 187:
Thanks for this really appreciate the effort!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Feb 2018 ..

RR-N-v5.8.5-20180210-gtaxlwifi-Unofficial.zip

RR-N-v5.8.5-20180210-gtaxlwifi-Unofficial.zip.md5sum

RR-N-v5.8.5-20180210-gtaxllte-Unofficial.zip

RR-N-v5.8.5-20180210-gtaxllte-Unofficial.zip.md5sum

(Upgrade) Installation -> to prevent bootloop due to Magisk issue:

1. Copy new ROM onto your tablet,sdcard or usb-stick and reboot into TWRP

2. Install the new ROM -> Magisk installation should start automatically afterwards

3. Install either rros-kernel-gtaxlwifi-20180205.zip or rros-kernel-gtaxllte-20180205.zip

( Pls look here for more details: https://xdaforums.com/showpost.php?p=75456987&postcount=231 )

4. Wipe cache/dalvik

5. Reboot into system

Changes:

- Google February 2018 security updates

- Changed DRM service groups -> to fix DRM service start

- Kernel: removed "forced" permissive selinux mode -> you can change to enforcing mode via "setenforce 1" now.

Enjoy .. :p
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ajsmsg78:
What would it take for me to port this over to the SM-P580? It bootloops on my SM-P580.. I've tried replacing the firmware and the kernel but i still can't get it booting. I figured since it was almost the same device it would be simple as I've ported in the past but I can;t get this booting.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Which kernel did you try ?

And how ?

You may unzip the kernel file and replace image and dtb.img with your pen version.

How did you port your last ROM to pen version ?

Just repacking boot.img ?

Did you install magisk as well ?

You did follow instructions and did install the kernel zip as last step ?

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ajsmsg78:
Yeah, I followed the OP but couldn't get it to boot. I'll try again in a few days.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BADA 187:
need to have your device specific blobs to if im right. there is enough tuts on howto pull/extract blobs from your device or from a existing rom.zip
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] -WhiteHawk-:
This installs Magisk 14.5, are we free to install the latest version afterwards??
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dorf18:
Does magisk install automatically now? I like when you can choose to install magisk or supersu yourself
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
No - magisk is not included, but the Rom installer detects your existing magisk installation and does reinstall automatically.

Same like before.. just the new kernel zip is new .. to be applied as very last step.

To be able to use latest magisk version, without bootloops.

No known issues with SuperSU.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] -WhiteHawk-:
Ah I understand now, thanks for clearing that up.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] okij:
Thanks a lot for the new build! :good:

I first installed Magisk 15.3 according to your instructions in post #231, then I updated to the new 20180210 build. Everything went fine, thanks again for your detailled instructions! :)

One question: Is there a way to make the enforcing selinux mode survive reboots? Using "setenforce 1" works fine, but after a reboot it's set to permissive again. Edit: There's an app called SELinuxModeChanger which allows to automatically set the desired selinux state again after reboot. I'm using this app now, but is there an easy way without using an extra app?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Yes .. using another kernel :)

We can make an enforcing kernel - but if you face any problems pls don't complain.

Any issues after switching manually via setenforce 1 ?

As said a few threads above .. the kernel is just one part - the sepolicies may still block certain functionality.

It will take longer to validate the sepolicies before enabling enforcing selinux in monthly RR ROM.

But with the kernel.zip files you will be able to switch between permissive and enforcing kernel thru TWRP.

As we switch the default value from permissive to enforcing It's reboot-persistent too.

This week I will find a time slot to build the enforcing kernel .. for 580 and 585.

Will let you know ..

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] okij:
I didn't have any issues yet, but will now let my wife use her tablet on enforced mode and see if she runs into any issues. :D

Edit: It turned out that the device didn't enter deep sleep with enforced mode turned on, besides this I saw that Simple System Monitor force closed. Both issues got fixed after setting permissive mode again.

Great! Thanks in advance!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
I did warn you .. :)

Anyway .. made 2 enforcing kernels now .. if you still like to play.

You can switch to permissive with "setenforce 0".

Since Magisk 14.6 there were some "samsung" related changes .. no need to do the reinstall on 14.5 version.

If you use newer Magisk version you will need to re-install Magisk if you switch from permissive to enforcing kernel.

And vice versa - otherwise you will get bootloop.

kernel installation with magisk 14.6/15.x:

1. unpack latest RR boot.img from latest RR ROM and install it via TWRP -> to clean current Magisk/SuperSU installation!

2. install latest Magisk version via TWRP

3. install either 580 or 585 kernel.zip - pls see below

4. reboot into system

You will have to do this step after each ROM update !

If you use Magisk 14.5 or SuperSU you just need to install the kernel.zip file and reboot into system.

580 -wifi

rros-kernel-gtaxlwifi-20180212-enforcing.zip

585 - lte

rros-kernel-gtaxllte-20180212-enforcing.zip

Again .. it will take longer until the sepolicies/selinux stuff is fixed.

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dibbie666:
hallo first of all thx for this rom. I am comming from the extremely rom also good but this rom i like more because i also have rr rom on my phone i9515ve. no problems with instal and every thing is working wel . grz Jan
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Sometimes the issues get fixed automatically :)

As it looks like .. Magisk 15.4 does not generate bootloops anymore.

No need for any special kernel anymore.

Pls test yourself ..

Cheers

EDIT:

To prevent confusion .. :)

Pls install boot.img from latest RR ROM first -> to have a clean start !
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] :
Hello,

Maybe a strange question: after installing this rom, I am experiencing that the screen is a bit too blue. I have turned off livedisplay. Anybody same problem?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dorf18:
Yeah I had same issue. Calibrate blue setting to 95 or play with the settings to your liking.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] JoostA:
Yikes,:( I did try. I got into a horrific bootloop on my T-580 (wifi). So I quickly put back Magisk 14.5. Probably I did something wrong. That is something I am going to find out later. What I did is flash the newest (021018) version. Today I just flashed the new Magisk via TWRP without removing or re-installing anything. *That* doesn't work..... Tips welcome of course :fingers-crossed:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BADA 187:
eztracts the boot.img from the rom and flash that, so you have a clean boot.img, then flash new magisk right after see if that works
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ajsmsg78:
I got the new build booting on my SM-P580 by replacing those two files. (zimage and dtb) It seems like everything is working except for wifi. I've tried replacing the wifi modules in system/etc and system/lib with the ones from my stock rom but it still doesn't work. This happens on the stock RR kernel and the rros kernel. There is something in the kernel that needs to be changed correct? Do you have any suggestions?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Seems to be the "famous" wlan module (qca_cld_wlan.ko) .. no fun.

Pls have a try with this kernel below .. to be installed via TWRP.

rros-kernel-gtanotexlwifi-20180214.zip

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ajsmsg78:
Thanks. The new kernel bootloops at the Samsung logo.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Did you try with fresh boot.img and kernel.zip afterwards ?

The kernel is just using PEN config on existing kernel T580/585 sources.

If stock P580 kernel binary and dtb.img is booting you may try to build kernel based on PEN kernel sources.

And testing again the wlan module from your stock rom.

You can try to load it manually after boot ..

insmod /system/lib/modules/qca_cld/qca_cld_wlan.ko

This should show you the reason why the module is not loading.

dmesg | grep wlan

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dorf18:
Anybody else experiencing lag when scrolling through web pages/apps don't think the previous version did this that much. Went back to extremely seems a lot smoother.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ajsmsg78:
Yeah, I tried a fresh kernel, boot.img, i tried doing them in a different order. It's weird how that kernel bootloops but the original one doesn't. The stock boot.img and kernel that I modded from RR seems to work too except for wifi. I also noticed that my stock rom also has a wlan.ko file.