I see from the TWRP site that you are the maintainer for the S5e, so if you say "Unlikely", I'll take it as the "final word". I'll just have to wait. With the amount of storage and RAM this tablet has, the "Samsung Bloat" isn't as big a deal as it was on earlier models, so waiting isn't a problem.Unlikely.
I see from the TWRP site that you are the maintainer for the S5e, so if you say "Unlikely", I'll take it as the "final word". I'll just have to wait. With the amount of storage and RAM this tablet has, the "Samsung Bloat" isn't as big a deal as it was on earlier models, so waiting isn't a problem.
If it will install so that I can then format the data partition and poceed to flash either LOS 17.1 or your cDroid ROM, then that's all I want. :fingers-crossed: The whole point is to get away from stock.Well it'll mostly work but don't expect it to decrypt userdata, also stock rom might hate you for custom recovery.
Also idk what you're going to wait for, I'm not going to invest time into stock rom...
first many thanks @LuK1337 for your amazing work maintaining this great tablet!
I'm using it with a F2FS formatted sdcard (better speed than exfat + some other better stuff).
until 24/08 build all was ok, I could read/write my sdcard without issue.
from 24/08 build, with the firmware update etc, there probably are many kernel changes I suppose (according to your github),
now my sdcard is no longer accessible, logcat shows that F2FS is now unsupported...
same happen with your newest twrp, though I can't remember if I could ever read F2FS in it before
indeed in your kernel repo (and in the lineageos one, which is basically the same)
F2FS is not enabled nor even mentioned in the defconfig files.
is it intentional or just some side effect of a big merge? (in that case there might be other things dropped unintentionally)
could it be enabled again please :crying: ?
Flash correct fw according to post #3.Hi there, after 31 Aug build downloaded and the tablet rebooted, when TWRP asked for the PIN code, I wrongly clicked "cancel", then it still installed the update but the fingerprint reader doesn't work anymore.
What should I do? Should I run the update again using the ADB / Sideload method?
Just try it out. If anything you can always go back to stock and relock the bootloader.hi. i bought this tablet for its great display but am dissapointed in general use responsiveness. every swipe feels slow and juddery. will going from stock to lineage rom solve this issue? it is hard to blame the hardware for this since its decent, so my guess is stock rom might be at fault
Uninstall EdXposed has to be the very first thing any sane person would do. It is known to be the source of endless headaches and badness.Well… It was working. After a few reboots and installing among other things Magisk, afwall and EdXposed, I'm again with no sound and no screen rotation… full logcat from boot until unlock here https://paste.ubuntu.com/p/Cmmbf7kxqp/
looks like /system/bin/audioserver crashes this may explains the sound problem but not the rotation one.
Any one knows how to solve those issues?
You can't flash firmware with twrp.On my end flashing CTK1 did end up with :
- no sound (volume rocker was fine though)
- no rotation
- no video decoding
- long boot time
was still on 17.1.
Flashed 18.1, behavior did not change.
Flashed CTI1, problems aforementioned disappeared. (while keeping 18.1, no userdata format)
Was previously on what seems to be a mix of ATE3 and BTG3.
Now I guess I'm ATE3/CTI1.
Might be because of me flashing manually with TWRP (BTG3 and later) so not everything may be writable.
What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: