Yeah, 20211130 is the latest version now. I'm sorry for the ambiguous titles.
As it's a kernel change I did it like that https://forum.xda-developers.com/t/...-18-1-for-galaxy-tab-s3.4293069/post-86045283
Sorry but I could not find how to update in the post you sent neither in the posts close to it.As it's a kernel change I did it like that https://forum.xda-developers.com/t/...-18-1-for-galaxy-tab-s3.4293069/post-86045283
Sorry was 3 posts higher where I wrote:
At least I did flash them together with the ROM.
Ah okay, will reproduce that issue on my device too.@Awesometic : I still have the same issues with the secondary/non admin user as described in my post https://forum.xda-developers.com/t/...-18-1-for-galaxy-tab-s3.4293069/post-85588047
Will you be able to fix this issue somehow. It looks like a permission issue for non primary users as the system shows that there is unsufficient space. As a hint which may help to localize the issue. When trying to start amaze file manager as a secondary user it will instantly crash with a file I/O exception. Please have a look. I can provide additional information if needed.
BTW, with the last version the WIFI MAC was changed. Not sure if this is on purpose or not.
A "dirty flash" refers to the process of flashing a new version of your ROM over the top of the one you have, without using the "Wipe Data/Factory Reset" option in recovery. Even if you intend to dirty flash the update, you should always wipe cache and dalvik cache.
- Wipe Data/Factory Reset: This option erases all data on the device. Every application, and all data generated by those applications, will be erased. If you do not wipe data, all the data files generated by every app on the system will persist through an upgrade. This includes the data files generated by core system apps, like the phone dialer, the Android UI, its option menus and core features. Remember, everything you do on Android is an application that generates data! NOTE:The storage you see when you connect to USB will not be erased.
- Wipe Cache: Every application on the system, even those that run things like your UI and the options menus, generates cache files. These cache files are more or less unique to the current installation of Android you are using, and are generated dynamically. These cache files help Android load and run faster. When changing ROMs or updating to a new version of a ROM, you should always wipe the cache partition, or you're gonna have a bad time: Force closes, boot loops and sluggish performance are just some of the perils that await you.
- Wipe Dalvik Cache: Android executes programs inside of software system called the "Dalvik Virtual Machine." The DVM interprets and runs APK files for Android. Dalvik maintains its own cache to again improve performance for your device by offering faster app loading and execution. The Dalvik Cache is again unique to the current installation you are running, and it should always be wiped whether you're installing a new ROM or simply updating versions.
Performed dirty flash but kept EXT4. Everything works fine till now.Dirty flashing will work. This means, just flash the new version using TWRP, and wipe caches.
But moving to F2FS requires you to format the current data partition. So please be aware of that before continuing. Currently, F2FS is an option that has better I/O performance but a little bit unstable than EXT4, very relatively.
Quoted here what "dirty flashing" means from a Reddit post.
Yeah, while I was upgrading the kernel to merge the upstream patches seems like I broke that feature. I'm using a flip cover case too, so that is quite an annoying bug
Thank you for the answer, we are all following your progress!)Yeah, while I was upgrading the kernel to merge the upstream patches seems like I broke that feature. I'm using a flip cover case too, so that is quite an annoying bug
I found which function handles that flip cover flips, and checked that function does listen to the status (opened and covered), but the screen is not actually responded by that function. I'd like to fix this issue too.
I found the following in the internet to overcome the OTG problem and be able to use a stick right away. NOTE THOUGH that after this I had the problems with the WIFI that I mentioned in my previous message, only when having the stick plugged though, but I got used to it.... either WIFI or OTG....Was just about to test it but the stick wasn't correctly recognised.
Although just tested as usable in another device.
When trying to copy something onto it from the NAS using Total-Commander it just showed what's in the pic.
Properties rwx were the same as SD (770).
Format vFat might be the cause I thought so sitched to TWRP and formated as ext4.
Reboot - > system says problem with the stick (do I want to format?) so I did - > vFat.
Gave up but no WI-FI probs meanwhile.
Just another info: battery usage in deep-sleep (fmight-mode) turned on is brilliant ~0.1%/h.
Sorry if I mislead you. If you used the approach I have mentioned, then wifi works perfectly as long as you do not use otg at the same time. So, in your case you will have problems with wifi ONLY the two times per year you use the OTG. The rest of the year WiFi will be trouble free.....
/* * Your warranty will be VOID after installing a custom ROM. * * Get notified yourself that 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. */