yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] s4goa:
with ubiquitous censorship on www, people tend to not believe those postings saying "all is fine". Rather the opposite is true.
[Samsung Galaxy S 4 Unified Development] Achsel:
@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!

Axel
[Samsung Galaxy S 4 Unified Development] s4goa:
so magisk behaves the usual way, Axel? have trouble with magisk on a RasPi where magisk kinda behaves oddly.
[Samsung Galaxy S 4 Unified Development] Achsel:
I have no problems with Magisk on Samsung S4! No reboots on both devices!
[Samsung Galaxy S 4 Unified Development] s4goa:
that's a plus. Does the S4 reboot often times?
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
what people tend to not believe is up to their own (and/or maybe up to their "filter-bubble").

I tend to believe what I can see (in this case: on my phone) and verify (in this case: in this thread here).

just read comment #214.

cit.: "It runs great on both devices."

... :cool:
[Samsung Galaxy S 4 Unified Development] npjohnson:
There was an edge case issue with accessibility apps causing delayed input. If it's fine for you. No worries, enjoy it :)

See above.

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!
[Samsung Galaxy S 4 Unified Development] Achsel:
@npjohnson

I am available for any tests. I have two different combined USB 2.0 HUB 3-way Ethernet adapters (UGREEN with ASIX Ax88772 chipset, displayed driver: asix and JSDOIN with Corechip SR9000 chipset, displayed driver: cdc_ether). Both adapters work automatically on my Samsung Galaxy Tab4 (SM-T530) with LinageOS 18.1:

https://xdaforums.com/t/rom-unofficial-matisse-millet-lineageos-18-1.4292943/

In addition to the three options mentioned above, these six other options are activated on the Tab4 (The activated USB drivers are displayed in the "/ sys / bus / usb / drivers" folder):

"CONFIG_USB_ASIX", "CONFIG_USB_NET_CDC_NCM", "CONFIG_USB_NET_SMSC75XX", "CONFIG_USB_NET_SMSC95XX", "CONFIG_USB_NET_NET1080", "CONFIG_USB_NET_CDC_SUBSET" and "CONFIG_USB_EHSET_TEST_FIXTURE".

I have just loaded the driver for the AX88772 chip at ASIX, which should be suitable for all Android versions, and attached it below, but is apparently not needed on the Tab4 (just installed and used) and would have to be compiled accordingly.

https://www.asix.com.tw/en/support/download
[Samsung Galaxy S 4 Unified Development] Marko97IT:
I am correcting what has been said only for the GApps. The problem was in the /data partition which I fixed. For the rest, the ROM is laggy and makes the phone heat up a lot.
[Samsung Galaxy S 4 Unified Development] Achsel:
@npjohnson

New insights: The JSDOIN USB 2.0 HUB Ethernet adapter definitely does not work on the S4 because of the missing "cdc_ether" driver. I had only tested the UGREEN adapter with "ASIX" chipset once without success. Today I looked again in the "/sys/bus/usb/drivers" folder and found that only the "ASIX" driver is activated. So I started a new test with the UGREEN adapter, and lo and behold, it works on both S4 devices (GT-I9505/GT-I9515). I don't know why the connection failed the first time.

I recommend the UGREEN adapter with 3x USB 2.0 ports (Ships from China, third choice, model no. 20264, ASIX AX88772 chipset), because the S4 only supports USB 2.0, and "not" the USB 3.0 version (model no. 20265, ASIX AX88179 chipset), because there may be dropouts in the transmission. It may be too fast for the S4 phone).

https://de.aliexpress.com/item/3240...earchweb0_0,searchweb201602_,searchweb201603_

In order for the "cdc_ether" driver to work, all three of the following options should be activated (internet infos):

"CONFIG_USB_NET_CDCETHER", "CONFIG_USB__NET_RNDIS_HOST" and "CONFIG_USB_USBNET" (Multi-purpose USB Networking Framework).

Activation of the drivers for other chipsets:

"CONFIG_USB_NET_SMSC75XX", "CONFIG_USB_NET_SMSC95XX" and "CONFIG_USB_NET_NET1080".

Additional options that are activated on the Tab4:

"CONFIG_USB_NET_CDC_NCM", "CONFIG_USB_NET_CDC_SUBSET" and "CONFIG_USB_EHSET_TEST_FIXTURE".

Special tip:

I use a modified OTG adapter with additional female micro USB socket for external power supply. The micro USB male connector of the OTG Adapter has usually a solder bridge between PIN 4 (ID PIN) and PIN 5 (ground) to detect the OTG mode. Then you can only supply the USB device with power. Without the additional micro USB female socket the power directly comes from the phones (tablets) akku. If you solder in a resistor instead with approx. 65kOhm (specially for the Samsung Galaxy S4 phone, for the Samsung Galaxy Tab 4 tablet 80kOhm) between PIN 4 and PIN 5 of the micro USB male connector, then you can supply the USB device and the phone (tablet) with power at the same time.

Because there is no solderable PIN 4 in the micro USB male plug of the ADAPTARE OTG adapter, I bought individual micro USB male plugs with all 5 pins for soldering.

https://www.amazon.de/40228-Adapter...icro-USB-2-0-gerade-Extra-Strom/dp/B00EJP5XR2

https://www.amazon.de/dp/B01G6OYTS2...88ad-322db71d5961&ie=UTF8&qid=1513864976&sr=1

Many Greetings, Axel
[Samsung Galaxy S 4 Unified Development] npjohnson:
do me a favor, enable the options you need, tell me exactly the list you need, then please compile test it, AND (the big one) make sure recoveryimage still fits with those built in please.

If you do all those, I'll merge it into official builds. I'm super low on time atm.
[Samsung Galaxy S 4 Unified Development] Achsel:
@npjohnson

I have great respect for your work customizing the builds for the S4 and I understand that this is very time consuming. As already mentioned, my knowledge and the hardware available to me are not sufficient to decompile the defconfig file of the kernel implemented in a ZIP file for the installation of LineageOS 18.1, edit it and then recompile it and integrate it back into the ZIP file. For me personally it would be enough if these 3 driver options were activated in the defconfig file, which are set by default for a functioning Ethernet:

"CONFIG_USB_NET_CDCETHER", "CONFIG_USB__NET_RNDIS_HOST" and "CONFIG_USB_USBNET" (Multi-purpose USB Networking Framework).

I could then install such a modified ZIP file on a GT-I9505 and GT-I9515 as a test before you officially offer it. But if you think that this is too time consuming, I can understand that. The whole thing is in no hurry, however!

At least I'm lucky that the only Ethernet driver that is activated ("ASIX") happens to support the UGREEN adapter and your customized LineageOS 18.1 runs wonderfully on the S4, even better than the stock ROM with Android 4.4.2.

Thanks for your great job, Axel
[Samsung Galaxy S 4 Unified Development] Achsel:
@npjohnson

For further information only! I hope I don't annoy you too much with this!

I guess you used this "lineageos_jf_deconfig" file as the basis for your builds. Because "CONFIG_USB_USBNET" is apparently already activated ("y"), in my opinion only the standard Ethernet driver "CONFIG_USB_NET_CDCETHER" ("is not set ") needs to be activated to support many other chipsets. Unfortunately, I am unable to do this job.

https://github.com/LineageOS/androi...-18.1/arch/arm/configs/lineageos_jf_defconfig

318 CONFIG_USB_USBNET=y

319 # CONFIG_USB_NET_CDCETHER is not set

The option "CONFIG_USB__NET_RNDIS_HOST" is probably no longer available. In addition, I couldn't find a suitable entry for the only activated "ASIX" Ethernet driver in the defconfig file. This may be enabled elsewhere. But that doesn't matter anymore.
[Samsung Galaxy S 4 Unified Development] npjohnson:
Done, and merged: https://review.lineageos.org/c/LineageOS/android_kernel_samsung_jf/+/314488 - nex build should have what you need.
[Samsung Galaxy S 4 Unified Development] Achsel:
@npjohnson

Thank you for activating the "cdc_ether" standard Ethernet driver in the "lineageos_jf_deconfig" file. After installing the next update on my two S4 devices (GT-I9505/GT-I9515), I will report whether this driver works as expected with my other very inexpensive JSDOIN 3x USB 2.0 HUB Ethernet adapter with Corechip SR9000 chipset.

https://www.amazon.de/dp/B08JCJL4Y1...j1jbGlja1JlZGlyZWN0JmRvTm90TG9nQ2xpY2s9dHJ1ZQ
[Samsung Galaxy S 4 Unified Development] sjamie:
You're amazing!
[Samsung Galaxy S 4 Unified Development] zyhk:
My tp-link UE300 (1000BASE-T) adapter (cdc_ether) is working on the latest ROM. Probably its data rate is comparable to that of S4's wifi.
[Samsung Galaxy S 4 Unified Development] Gerdje_:
I have a question, not directed to the dev, but to everyone who is using magisk with this build. But first a big thank to npjohnson!

I'm using the jfvelte and did a dirty install from Official LOS 17.1 to 18.1, because I'm not willing to setup the entire phone again. I have two identical devices, and my testmachine is updated to 18.1 now. I flashed the newest TWRP on it.

I need root but there lies my problem. Do I first need to upgrade Magisk 22 to 23, and after that do the dirty install of Lineage? I tried to install Magisk 23 on it but it somehow is not working properly. I know this is the Samsung S4 thread, but any idea how to upgrade to the new Magisk on this particular device? Can someone point me into the right direction, because all the information is confusing me too much. Thank you!
[Samsung Galaxy S 4 Unified Development] Achsel:
@zyhk

Thanks for the information! That sounds good! At the moment only the VE version of the S4 is available to me (GT-I9515). So I have to wait for the JFVELTE update to test it. The GT-I9505 (JFLTEXX) will be back in my hands for about a week. Then I will report.
[Samsung Galaxy S 4 Unified Development] sjamie:
You can dirty flash LineageOS before or after upgrading Magisk.

To upgrade Magisk, download the latest Magisk apk. Rename the file extension to ZIP. Flash magisk zip in either the Magisk app or via TWRP. I always flash the latest Magisk zip via Magisk and I haven't had any issues.
[Samsung Galaxy S 4 Unified Development] Achsel:
@Gerdje_

I had previously installed the stock ROM with Android 5 on both S4 versions (JFLTEXX and JFVELTE). Therefore, I first installed the latest version of TWRP via ODIN, then made a total wipe (no dirty install) and then installed LinageOS 18.1, BiTGapps Official ARM and Magisk 23 in one go without any problems. Unfortunately, I can't give you a tip for the Magisk update from 22 to 23.

https://www.pling.com/p/1462973/
[Samsung Galaxy S 4 Unified Development] Gerdje_:
Thanks guys! Magisk 23 seems to work, but uninstalling the old magisk, by renaming the apk to uninstall.zip didn't work well, TWRP is telling me that it is an invallid zip or something and in Magisk itself there is no option to do an uninstall, only restore images.
[Samsung Galaxy S 4 Unified Development] Achsel:
On the start screen of Magisk 23 there is a button with red letters for deinstallation below.
[Samsung Galaxy S 4 Unified Development] Gerdje_:
Yes, I know but thank you. When I tapped on it, there was only the option to restore images. An option to deinstall wasn't showing.
[Samsung Galaxy S 4 Unified Development] kurtn:
Magisk is installed by a modified boot image. Restoring the original one removes magisk.
[Samsung Galaxy S 4 Unified Development] stef2020:
Hi. I have been using LineageOS on my Samsung Galaxy S4 for a years now without problems. A few months ago I opted to make the upgrade to LOS 18.1 & this went without issue & everything was working fine. However last week I opted to update to the latest build using the updater in the settings & this seemed to go without any issue, However upon reboot after the install I began having issues with my wifi.

When I try to enable the wifi It will either work as normal but go offline after a short period or simply search & never find any available networks.

I tried reflashing the update via recovery & also tried flashing back to prior builds yet nothing seems to fix it. Today I went into recovery & did a full data wipe & fresh install of the June 11th build as I know that worked as it was the first 18.1 build I installed yet it's still doing the same thing.

It could obviously be a hardware issue but it just seems weird that it started right after I did an update so I want to cover all possible software solutions before giving up on the phone completely as I can't really afford a new one right now.

So is there anything else I could try to confirm software or hardware?
[Samsung Galaxy S 4 Unified Development] Gerdje_:
Hi stef2020,

I had this issue with an unofficial LOS 17.1 build, at least the search and never find wifi problem: it was a known bug, and you had to reboot it to get the wifi to work again. Not sure if this workaround will help as well. It was definitively not an hardware issue in my case.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
Not here with an continuous weekly updated I9505..

btw.

wifi always has two parts: your device and your router.

any MAC-Filter set ?
[Samsung Galaxy S 4 Unified Development] stef2020:
I'm pretty sure it's not the router as it's not simply losing the connection to my router. It normally picks up a few nearby wifi networks from the neighbours & a BT hotspot out the front, When it goes off it doesn't pick up anything.

What it's been doing after the full factory reset today is connecting to wifi as normal & then randomly completely losing all wifi signals after a few minutes. When it does that if I turn wifi off & on again it will again pick up all nearby connections, Connect to mine & then lose everything again after a few minutes.

Everything else in the house that connects to wifi (Including other android phones/tablets) continues to work fine, It's just this phone since the 5th August update that has had this issue.
[Samsung Galaxy S 4 Unified Development] sjamie:
I'm on last week's build with zero wifi issues.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
did you also check the wifi settings under "Developer Option" ?

there:

- Wi-Fi scan throttling is ON (on my phone)

- Wi-Fi-enhanced Mac randomisation is OFF (on my phone)

Developer Option is available after tapping 8 times on Build number under "About phone"
[Samsung Galaxy S 4 Unified Development] stef2020:
Scan throttling is on & enhanced Mac randomisation is off.

I guess maybe the phone just went bad & it happening just after the update is unrelated as nothing i've tried over the past week has fixed it.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
I would verify that by flashing stock and check with WPA2 (I'm unsure if WPA3 is in stock, if you're running that at all)

I'm running out of idea's, but:

- completely delete your phone from the router and log it on again (maybe with a router reboot)

- wifi-connect 2 devices (phone and a tab (?)) near by each other, let both go to sleep, check on both if wifi connections and/or the DHCP parameter survived (if you're running DHCP and if DHCP parameter could change in a so short time at all)

- with an wifi-connected phone tap the toothed wheel right from your SSID, expand "Advanced":

is "Auto-connect" ON ?

on both ?

- how does your phone appear in the router when the wifi-connection on the phone is gone ?

also gone ?

if not: what'sup with the IP-Address Parameter of the phone in the router ?
[Samsung Galaxy S 4 Unified Development] sjamie:
I would also recommend formatting your device and flashing the stock ROM to verify functionality. That would eliminate any custom ROM related issues.
[Samsung Galaxy S 4 Unified Development] Gerdje_:
Something completely different, does anyone else have a few system apps that are summed up sometimes 4 or even 5 times under: Apps and notifications>>Recently opened apps/see all xx apps>>3 dots>>show system?

Circular for example is shown 5 times.

Is an dirty install the cause? The phone is working normal though.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
no, not here.

don't know !

and

it seems all is fine when the "phone is working normal" so stop "trying to find out" it's not" :cool:
[Samsung Galaxy S 4 Unified Development] kurtn:
Tl;dr?

Some installation guides
[Samsung Galaxy S 4 Unified Development] Achsel:
@kurtn

What should "Tl;dr?" mean?
[Samsung Galaxy S 4 Unified Development] kurtn:
Too long; didn't read. Can you please give a summary so i can decide to work through?
[Samsung Galaxy S 4 Unified Development] Achsel:
@kurtn

Post 249: It's about how to flash "TWRP" recovery or "Lineage" recovery via ODIN (works even with old computer systems and Windows XP 32-bit), how to do a first clean installation with the two recovery versions via external SD card without PC and how to reduce "MindTheGapps" via "7-Zip" and "Notepad++".
[Samsung Galaxy S 4 Unified Development] npjohnson:
Good to hear it works but if you had followed the wiki you would have had compatible GApps and not hit this. I also don't guarantee TWRP will be fully functional for doing OTAs. I try, but who know.

Just follow the wiki guide.
[Samsung Galaxy S 4 Unified Development] Retrial:
I just wanna let you know, so far OTAs works flawlessly with TWRP. 😜
[Samsung Galaxy S 4 Unified Development] Achsel:
@npjohnson

I gained my first experience with the installation of LineageOS 18.1 with an unofficial version for the Samsung Galaxy Tab 4 (SM-T530). The TWRP recovery is recommended there. The "MindTheGapps" package could not be installed even with a first clean installation on the Tab 4 (error when mounting "mnt / system"). With "BitGApps" there are no problems with the Tab 4 either during the clean first installation or with OTA updates.

https://xdaforums.com/t/rom-unofficial-matisse-millet-lineageos-18-1.4292943/

Although I had read the wiki in detail beforehand, I therefore decided on the smaller "BiTGApps" package for the first clean installation on both of my S4 versions, which ran through without any problems. Only after installing the OTA updates from August (error when backing up/restoring "BiTGApps" during installation), the system could no longer boot and it went back to recovery mode, as described.

So I realized that either the TWRP or Lineage recovery or the LinageOS 18.1 for the S4 is not compatible with "BiTGApps" and you actually have to use "MindTheGapps". However, since this bundle contains too many Google apps that I don't need, I have included instructions in my Post 249 on how to remove apps.

The wiki also recommend using Heimdall in conjunction with ADB to flash the Linage recovery and install the LineageOS 18.1. However, ADB is now only offered in the 64-bit version.

Therefore, in my Post 249, I also created instructions for flashing the TWRP or Lineage Recovery via ODIN, for which even an old computer systems with Windows XP 32-bit is sufficient. I also explain there how you can then carry out a first clean installation of the LineageOS 18.1 using an external SD card without a PC via TWRP or Linage Revovery.

The clear advantage of the TWRP compared to the Lineage Recovery is the backup/restore option, which also works great with LineageOS 18.1. You can also set your time zone and language there, among other things.

@Retrial

Thanks for your info to OTA updates!

It greets Axel
[Samsung Galaxy S 4 Unified Development] Retrial:
I have already wrote guides about it at S4 Unified Collection & Guides, in case you need anything else check there.
[Samsung Galaxy S 4 Unified Development] Achsel:
Tip: Simultaneous charging of the Samsung Galaxy S4 phone or Samsung Galaxy Tab 4 tablet and a 3-way USB 2.0 HUB Ethernet adapter (tested on the GT-I9505 and GT-I9515 phones and the SM-T530 tablet with 10.1")

1. Connect a modified OTG adapter:

I use a the OTG adapter ADAPTARE 40228 with additional female micro USB socket for external power supply. The micro USB male connector of the OTG Adapter has usually a solder bridge between PIN 4 (ID PIN) and PIN 5 (ground) to detect the OTG mode. Then you can only supply the USB device with power. Without the additional micro USB female socket the power directly comes from the phones (tablets) akku. If you solder in a resistor instead with approx. 65kOhm (specially for the S4 phone, for the Samsung Galaxy Tab 4 tablet 80kOhm) between PIN 4 and PIN 5 of the micro USB male connector, then you can supply the USB device and the phone (tablet) with power at the same time.

Because there is no solderable PIN 4 in the micro USB male plug of the ADAPTARE OTG adapter, I bought individual micro USB male plugs with all 5 pins for soldering.

https://www.amazon.de/40228-Adapter...icro-USB-2-0-gerade-Extra-Strom/dp/B00EJP5XR2

https://www.amazon.de/dp/B01G6OYTS2...88ad-322db71d5961&ie=UTF8&qid=1513864976&sr=1

2. Connect the USB 2.0 HUB Ethernet adapter:

I recommend the UGREEN adapter with 3x USB 2.0 ports (Ships from China, third choice, model no. 20264, ASIX AX88772 chipset for Ethernet), because the S4 phone (Tab 4 tablet) only supports USB 2.0, and "not" the USB 3.0 version (model no. 20265, ASIX AX88179 chipset for Ethernet), because there may be dropouts in the transmission. It may be too fast for the S4 phone (Tab 4 tablet). The required "ASIX" Ethernet driver is already activated in the LineageOS 18.1 kernel.

https://de.aliexpress.com/item/3240...earchweb0_0,searchweb201602_,searchweb201603_

Alternative the JSDOIN adapter (The required "cdc_ether" Ethernet driver is now already activated in the LineageOS 18.1 kernel.):

https://www.amazon.de/dp/B08JCJL4Y1...j1jbGlja1JlZGlyZWN0JmRvTm90TG9nQ2xpY2s9dHJ1ZQ

3. Important only for the Tab 4 tablet: Connect the charger at the end!

Otherwise the UGREEN or JSDOIN adapter, all connected USB devices and the Ethernet connection will not be recognized. I don't know why that is. Maybe the OTG driver won't load. With the S4 phone, it doesn't matter when you connect the charger.

Goog luck with testing!

Axel
[Samsung Galaxy S 4 Unified Development] vip5912:
TWRP 3.5.2_9-0 is not compatible with OTA of official LineageOS 18.1 (at the time of my test).

After downloading new ROM and reboot to TWRP (by Setup) I can see main TWRP menu (no update script).

JDCTeam TWRP 3.3.1-0 Custom builds - Build 2 worked fine.
[Samsung Galaxy S 4 Unified Development] Retrial:
I remember in the past OTA of Official LineageOS didn't worked with TWRP but has been fixed long ago.

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. 😜
[Samsung Galaxy S 4 Unified Development] Achsel:
@vip5912

To use TWRP 3.5.2_9-0 instead of TWRP 3.5.2_9-1 is perhaps the problem!