you're talking about *your* phone.
what people tend to not believe is up to their own (and/or maybe up to their "filter-bubble").
There was an edge case issue with accessibility apps causing delayed input. If it's fine for you. No worries, enjoy it
You must have done something wrong. It runs great here with GApps. It old hardware, but things run well.
Well, all is fine for real, lol
I'll take a look!@npjohnson
As already described in my post 193, I have successfully installed LineageOS 18.1 on a GT-I9505 and a GT-I9515 VE (flashed via TWRP, rooted via Magisk). It runs great on both devices. Thanks a lot for this! Due to the missing Ethernet driver I cannot activate Ethernet through a behind a OTG Adapter connected USB 2.0 3-way HUB with integrated Ethernet adapter, even via shell commands (on rooted stock ROM Android 4.4.2 it was possible). No "eth0" device is displayed after the shell command "ifconfig -a". As I have read on the Internet, you would have to activate the following options in the kernel "defconfig" file for the S4 for a USB Ethernet Adapter to work:
"CONFIG_USB_NET_CDCETHER", "CONFIG_USB__NET_RNDIS_HOST" and "CONFIG_USB_USBNET" (Multi-purpose USB Networking Framework).
Because my knowledge is far from sufficient to compile a "defconfig" file from a LineageOS installation file, I wanted to ask whether you could activate the three options mentioned with the next update.
Another possibility would be the manual activation of the modules "cdc_ether.ko", "rndis_host.ko" and "usbnet.ko" via the "insmod" command, if this is still possible with LineageOS 18.1. But these compiled modules would then have to come from the current kernel too.
Thanks in advance!
I wouldn't release it if OTA's didn't work lol@pocketrule
The key question, however, is which recovery do you use, TWRP or Lineage recovery?
@Retrial and @pocketrule
As I wrote in my longer posts 249 and 256, I used the smaller "BiTGApps" package + the "BiTGApps" add-on "Google TTS" for the first clean installation via TWRP on both of my S4 versions, which ran through without any problems. But after installing the OTA updates from August (error message when backing up/restoring "BiTGApps" during installation), the system could no longer boot and it went back to recovery mode, as described. So the "BiTGApps" or parhaps only the "BiTGApps" add-on "Google TTS" (I need for a navigation app) don’t seem to be combatible to OTAs via TWRP, but perhaps via Lineage recovery.
So I made a new clean installation with the August updates on both S4 devices (GT-I9505 and GT-I9515), a reduced "MindTheGapps" (see my instructions and attachement in post 249) and "Magisk-v23.0.zip" via "TWRP 3.5.2_9-1", because I don’nt want to be without root.
The crazy thing is that with otherwise the same installation on a Samsung Galaxy Tab 4, the "MindTheGapps" lead to an error when mounting "/mnt/system" just during a first clean installation via TWRP, but with the "BiTGApps" + "Google TTS" also work OTAs on the Tab 4.
@npjohnson and @Retrial and @pocketrule
Good news: 30 minutes ago I made via "Settings/Advanced/Updater" on the GT-I9515 (S4 VE) the update from today and everything runs automatically now and booting works without problems.
So I can say: My reduced "MindTheGapps", "Magisk-v23.0.zip" and "TWRP 3.5.2_9-1" are compatible with OTAs. When the next update for the GT-I9505 is out, I will also test the updater there. But I am sure that it will also work with this device.
I use MindTheGApps but it should work with other GApps bundles too.@Retrial
You said in your Post 260:
I use OTA fine with the latest Official TWRP (twrp-3.5.2_9-1), it automatically Download the new build > Reboot TWRP > Flash new build > Reboot system.
Did you use "MindTheGapps" or another Gapps bundle? Do you have "Magisk" installed for root access too?
Thanks in advance
After you and Retrial have written about flashing with TWRP (at least to my regognition) - it was clear to me, we're all talking about flashing with TWRP. But you're right. Thinking about it, I should have mentioned that. My devices are I9505.
I don't flash updates that often, so I didn't have this specific problem.
It's alway hard to say, where exactly the error is, when you have different components working together.. But that's great news, glad it worked for you 👍️
- Your warranty is now void. - You have been warned. - Use at your own risk.
the recovery image updates the second you check the box.