• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Troubleshooting wifi problems on S2 exynos5433 tablet ONLY discussion for users running any version of Android 10

Search This thread

lpedia

Senior Member
Sep 18, 2020
160
77
Samsung Galaxy Tab S2
HTC 10
Want to also quickly confirm in here that the S2 Blobs are working real fine for me as well.
I did some testing today and found that (at least on my device) the wifi instability with S6 blobs might be because they're not coping with a dual-band network (2.4GHz and 5GHz bands in the same SSID).

I found S6 blobs choose the 5GHz band, don't switch to 2.4 GHz if the 5GHz signal quality is poor or missing, and don't always automatically reconnect to 5GHz when the signal improves. S2 blobs also prefer the 5GHz network, but don't drop out as quickly if its signal quality is poor, and can switch to 2.4GHz if the 5GHz signal is low or missing.

I also found that both S6 and S2 blobs are quite stable if the network is single-band, whether that is 2.4 or 5. Both of them reliably reconnect automatically on reboot to a single-band network, and stay connected.

Have other people who've had problems with unstable wifi also been using dual-band networks?
 
  • Like
Reactions: Yogi555

Yogi555

Member
Jul 21, 2021
16
5
I think I know what's going on now.

I've just uninstalled Magisk, and (after the enforced reboot) I can now see the "Rooted debugging" setting in Settings > System > Developer Options > Debugging.

Mine was ON, but had been hidden by Magisk's presence, as I suspected.

If you uninstall Magisk, I think you will find that your "Rooted debugging" is OFF. If so, turn it on, then try "adb root" etc. You don't need to root the device in order to use adb root functions. If you want the device to be rooted, by all means re-install Magisk - but with that setting still ON.

I'll be very interested to hear what happens. :)
Confirmed! I did what you suggested - activated rooted debugging after Magisk deinstall, installed magisk again => adb root works now and the flag disappeared again in the developer settings.
 
  • Like
Reactions: lpedia

Yogi555

Member
Jul 21, 2021
16
5
I did some testing today and found that (at least on my device) the wifi instability with S6 blobs might be because they're not coping with a dual-band network (2.4GHz and 5GHz bands in the same SSID).

I found S6 blobs choose the 5GHz band, don't switch to 2.4 GHz if the 5GHz signal quality is poor or missing, and don't always automatically reconnect to 5GHz when the signal improves. S2 blobs also prefer the 5GHz network, but don't drop out as quickly if its signal quality is poor, and can switch to 2.4GHz if the 5GHz signal is low or missing.

I also found that both S6 and S2 blobs are quite stable if the network is single-band, whether that is 2.4 or 5. Both of them reliably reconnect automatically on reboot to a single-band network, and stay connected.

Have other people who've had problems with unstable wifi also been using dual-band networks?
I think you are right - i noticed the preference for 5GHz as well some time ago with S6 blobs. I had a 2.4 GHz only repeater very closeby, but the tablet decided to connect to the weak 5GHz signal and dropped continuousely ...
 

T_I

Senior Member
Mar 22, 2012
906
1,269
I have to admit I had the wifi issue in the old image (0307), but in the last one (0718) it seems to be resolved.

Edit: Nop, still dropping here, dual AP dual band, single SSID.
Edit 2: the lineage-16 blobs for wifi seem to work, testing more.
 
Last edited:

lpedia

Senior Member
Sep 18, 2020
160
77
Samsung Galaxy Tab S2
HTC 10
Hi, @T_I. We now know a little more about the dual-channel behaviour, namely, that the S6 blobs seem unable to use the highest 2.4GHz channels. The channels I tested were 11 and 13. It works with 11, but can't communicate with the access point on 13 (and might apply to 12 as well). So if your dual-channel network is using 13 for 2.4GHz, it would still seem flakey when the 5GHz signal is poor and the device can't switch to 2.4.

One difference from the previous roms, at least on my device, is that auto-connection at boot / wakeup and auto-transition between bands are working with this latest version. Neither function was working on a dual-band network with the earlier versions - even if the 5GHz signal was strong, it wouldn't reliably auto-connect.

I haven't yet checked whether the S2 blobs can handle channel 13. Perhaps you could test that?
 

PaulK.

New member
Jan 7, 2016
3
1
Hamburg
Strangely the setting seems not there in my system. But I remember that in some system its available. Can the installed Magisk be the reason?
Magisk ist the reason. But there is no need to uninstall Magisk. You probably have 'Magisk Hide' enabled. Disable this in the Magisk setting and reboot the tablet. Now the 'Rooted debugging' option should be available in Developer options. You can enable Magisk hide again after you are done.
 

lpedia

Senior Member
Sep 18, 2020
160
77
Samsung Galaxy Tab S2
HTC 10
Magisk ist the reason. But there is no need to uninstall Magisk. You probably have 'Magisk Hide' enabled. Disable this in the Magisk setting and reboot the tablet. Now the 'Rooted debugging' option should be available in Developer options. You can enable Magisk hide again after you are done.
You're right @PaulK.

An important point I missed is reboot after turning off Magisk Hide. Magisk Hide was the first thing I thought of when I noticed that the option was missing. But I don't think I rebooted after turning it off. I would not have thought it necessary, because Magisk doesn't ask for or advise a reboot to make the setting take effect, and the SafetyNet test passes immediately after enabling Magisk Hide.

It seems the setting does hide "Rooted debugging", but that doesn't take effect until reboot. When Magisk Hide is turned off, the effect isn't reversed until reboot.

I have seen "Rooted debugging" disappear without Magisk Hide, though. With Magisk v23 installed as an update from v22 via the app (and after all the mandated reboots), the option had disappeared. No Magisk Hide or any Magisk modules installed. [It had stayed visible with v22.] And this is not consistent. Some rom flashes and numerous boots later, Rooted debugging is visible with Magisk v23 installed.

So I'd say the advice should be: disable Magisk Hide and reboot. If that doesn't work, uninstall Magisk.
 

PaulK.

New member
Jan 7, 2016
3
1
Hamburg
It has been only 1 day with the new/correct drivers, but I am already really delighted. Our apartment is a Wifi killer any day. Overall reception strength seems to have improved and - more important - I have had no a single Wifi disconnect. I had regular Wifi losses before, especially when wandering around switching between APs.
What can I say? Great! Thanks a lot for this fix.
 
  • Like
Reactions: lpedia

zed011

Senior Member
Jan 18, 2011
542
106
Nothing happens when I do adb push wifi /system/vendor/etc it just hangs there. I'm in /temp/proprietary_vendor_samsung/gts28wifi/proprietary/system/vendor/etc. Any ideas?
 

zed011

Senior Member
Jan 18, 2011
542
106
Did the preceding commands work? "adb root", "remount", deleting the files in /system/vendor/etc/wifi?
I redid it and when I get to deleting the files, rm * shows no such file or directory

This is from the terminal
MINGW64 ~/temp/proprietary_vendor_samsung/gts28wifi/proprietary/system/vendor/etc (lineage-16.0)
$ adb root
restarting adbd as root

MINGW64 ~/temp/proprietary_vendor_samsung/gts28wifi/proprietary/system/vendor/etc (lineage-16.0)
$ adb remount
remount succeeded

MINGW64 ~/temp/proprietary_vendor_samsung/gts28wifi/proprietary/system/vendor/etc (lineage-16.0)
$ adb shell
cd /system/vendor/etc/wifi
rm *
rm: *: No such file or directory
ls -all
total 8
drwxr-xr-x 2 root shell 4096 2021-08-01 23:16:29.895000013 -0700 .
drwxr-xr-x 9 root shell 4096 2008-12-31 16:00:00.000000000 -0800 ..
 

zed011

Senior Member
Jan 18, 2011
542
106
I am using lineage 17 to be more specific, using lineage-17.1-20210718-UNOFFICIAL-gts28wifi.zip

Tried again on another computer, I managed to push but everytime after reboot, wifi refuses to turn on. I did reflash of lineage to restore wifi and tried again same thing. This is my terminal. How many files should be there before and after push?

C:\Users\Family\Downloads\temp\proprietary_vendor_samsung\gts28wifi\proprietary\system\vendor\etc>adb root

C:\Users\Family\Downloads\temp\proprietary_vendor_samsung\gts28wifi\proprietary\system\vendor\etc>adb remount
remount succeeded

C:\Users\Family\Downloads\temp\proprietary_vendor_samsung\gts28wifi\proprietary\system\vendor\etc>adb shell
gts28wifi:/ # cd /system/vendor/etc/wifi
gts28wifi:/system/vendor/etc/wifi # ls -al
total 4472
drwxr-xr-x 2 root shell 4096 2008-12-31 16:00 .
drwxr-xr-x 9 root shell 4096 2008-12-31 16:00 ..
-rw-r--r-- 1 root root 515800 2008-12-31 16:00 bcmdhd_apsta.bin
-rw-r--r-- 1 root root 538432 2008-12-31 16:00 bcmdhd_apsta.bin_a1
-rw-r--r-- 1 root root 508081 2008-12-31 16:00 bcmdhd_ibss.bin
-rw-r--r-- 1 root root 539757 2008-12-31 16:00 bcmdhd_ibss.bin_a1
-rw-r--r-- 1 root root 535297 2008-12-31 16:00 bcmdhd_mfg.bin
-rw-r--r-- 1 root root 556890 2008-12-31 16:00 bcmdhd_mfg.bin_a1
-rw-r--r-- 1 root root 589216 2008-12-31 16:00 bcmdhd_sta.bin
-rw-r--r-- 1 root root 608047 2008-12-31 16:00 bcmdhd_sta.bin_a1
-rw-r--r-- 1 root root 20 2008-12-31 16:00 cred.conf
-rw-r--r-- 1 root root 4269 2008-12-31 16:00 nvram_mfg.txt
-rw-r--r-- 1 root root 3235 2008-12-31 16:00 nvram_mfg.txt_a1
-rw-r--r-- 1 root root 3813 2008-12-31 16:00 nvram_mfg.txt_b85_a1
-rw-r--r-- 1 root root 4649 2008-12-31 16:00 nvram_mfg.txt_murata
-rw-r--r-- 1 root root 4378 2008-12-31 16:00 nvram_mfg.txt_murata_a1
-rw-r--r-- 1 root root 4378 2008-12-31 16:00 nvram_mfg.txt_murata_b85_a1
-rw-r--r-- 1 root root 3984 2008-12-31 16:00 nvram_mfg.txt_semco
-rw-r--r-- 1 root root 3984 2008-12-31 16:00 nvram_mfg.txt_semco3rd
-rw-r--r-- 1 root root 3786 2008-12-31 16:00 nvram_mfg.txt_semco3rd_a1
-rw-r--r-- 1 root root 3786 2008-12-31 16:00 nvram_mfg.txt_semco3rd_b85_a1
-rw-r--r-- 1 root root 3786 2008-12-31 16:00 nvram_mfg.txt_semco_a1
-rw-r--r-- 1 root root 3786 2008-12-31 16:00 nvram_mfg.txt_semco_b85_a1
-rw-r--r-- 1 root root 3984 2008-12-31 16:00 nvram_mfg.txt_wisol
-rw-r--r-- 1 root root 3786 2008-12-31 16:00 nvram_mfg.txt_wisol_a1
-rw-r--r-- 1 root root 3786 2008-12-31 16:00 nvram_mfg.txt_wisol_b85_a1
-rw-r--r-- 1 root root 4285 2008-12-31 16:00 nvram_net.txt
-rw-r--r-- 1 root root 3234 2008-12-31 16:00 nvram_net.txt_a1
-rw-r--r-- 1 root root 3812 2008-12-31 16:00 nvram_net.txt_b85_a1
-rw-r--r-- 1 root root 4649 2008-12-31 16:00 nvram_net.txt_murata
-rw-r--r-- 1 root root 4378 2008-12-31 16:00 nvram_net.txt_murata_a1
-rw-r--r-- 1 root root 4378 2008-12-31 16:00 nvram_net.txt_murata_b85_a1
-rw-r--r-- 1 root root 4027 2008-12-31 16:00 nvram_net.txt_semco
-rw-r--r-- 1 root root 4027 2008-12-31 16:00 nvram_net.txt_semco3rd
-rw-r--r-- 1 root root 3814 2008-12-31 16:00 nvram_net.txt_semco3rd_a1
-rw-r--r-- 1 root root 3814 2008-12-31 16:00 nvram_net.txt_semco3rd_b85_a1
-rw-r--r-- 1 root root 3814 2008-12-31 16:00 nvram_net.txt_semco_a1
-rw-r--r-- 1 root root 3814 2008-12-31 16:00 nvram_net.txt_semco_b85_a1
-rw-r--r-- 1 root root 4026 2008-12-31 16:00 nvram_net.txt_wisol
-rw-r--r-- 1 root root 3813 2008-12-31 16:00 nvram_net.txt_wisol_a1
-rw-r--r-- 1 root root 3813 2008-12-31 16:00 nvram_net.txt_wisol_b85_a1
-rw-r--r-- 1 root root 44 2008-12-31 16:00 p2p_supplicant_overlay.conf
-rw-r--r-- 1 root root 81 2008-12-31 16:00 wpa_supplicant.conf
-rw-r--r-- 1 root root 60 2008-12-31 16:00 wpa_supplicant_overlay.conf
gts28wifi:/system/vendor/etc/wifi # rm bcm*
gts28wifi:/system/vendor/etc/wifi # rm nvr*
gts28wifi:/system/vendor/etc/wifi # ls -al
total 24
drwxr-xr-x 2 root shell 4096 2021-08-03 12:30 .
drwxr-xr-x 9 root shell 4096 2008-12-31 16:00 ..
-rw-r--r-- 1 root root 20 2008-12-31 16:00 cred.conf
-rw-r--r-- 1 root root 44 2008-12-31 16:00 p2p_supplicant_overlay.conf
-rw-r--r-- 1 root root 81 2008-12-31 16:00 wpa_supplicant.conf
-rw-r--r-- 1 root root 60 2008-12-31 16:00 wpa_supplicant_overlay.conf
gts28wifi:/system/vendor/etc/wifi # exit

C:\Users\Family\Downloads\temp\proprietary_vendor_samsung\gts28wifi\proprietary\system\vendor\etc>adb push wifi /system/vendor/etc
wifi\: 23 files pushed. 13.1 MB/s (8893609 bytes in 0.648s)

C:\Users\Family\Downloads\temp\proprietary_vendor_samsung\gts28wifi\proprietary\system\vendor\etc>adb shell ls -al /system/vendor/etc/wifi
total 8752
drwxr-xr-x 2 root shell 4096 2021-08-03 12:30 .
drwxr-xr-x 9 root shell 4096 2008-12-31 16:00 ..
-rw-r--r-- 1 root root 516920 2021-08-03 12:16 bcmdhd_apsta.bin
-rw-r--r-- 1 root root 523556 2021-08-03 12:16 bcmdhd_apsta.bin_4356_a2
-rw-r--r-- 1 root root 524900 2021-08-03 12:16 bcmdhd_apsta.bin_4358_a1
-rw-r--r-- 1 root root 538640 2021-08-03 12:16 bcmdhd_apsta.bin_a1
-rw-r--r-- 1 root root 508081 2021-08-03 12:16 bcmdhd_ibss.bin
-rw-r--r-- 1 root root 601992 2021-08-03 12:16 bcmdhd_ibss.bin_4356_a2
-rw-r--r-- 1 root root 537038 2021-08-03 12:16 bcmdhd_ibss.bin_4358_a1
-rw-r--r-- 1 root root 539757 2021-08-03 12:16 bcmdhd_ibss.bin_a1
-rw-r--r-- 1 root root 535906 2021-08-03 12:16 bcmdhd_mfg.bin
-rw-r--r-- 1 root root 557107 2021-08-03 12:16 bcmdhd_mfg.bin_4356_a2
-rw-r--r-- 1 root root 543354 2021-08-03 12:16 bcmdhd_mfg.bin_4358_a1
-rw-r--r-- 1 root root 556942 2021-08-03 12:16 bcmdhd_mfg.bin_a1
-rw-r--r-- 1 root root 590905 2021-08-03 12:16 bcmdhd_sta.bin
-rw-r--r-- 1 root root 590725 2021-08-03 12:16 bcmdhd_sta.bin_4356_a2
-rw-r--r-- 1 root root 585966 2021-08-03 12:16 bcmdhd_sta.bin_4358_a1
-rw-r--r-- 1 root root 608547 2021-08-03 12:16 bcmdhd_sta.bin_a1
-rw-r--r-- 1 root root 20 2021-08-03 12:16 cred.conf
-rw-r--r-- 1 root root 6320 2021-08-03 12:16 nvram_mfg.txt
-rw-r--r-- 1 root root 6320 2021-08-03 12:16 nvram_mfg.txt_4356_a2
-rw-r--r-- 1 root root 3992 2021-08-03 12:16 nvram_mfg.txt_4358_a1
-rw-r--r-- 1 root root 6315 2021-08-03 12:16 nvram_net.txt
-rw-r--r-- 1 root root 6312 2021-08-03 12:16 nvram_net.txt_4356_a2
-rw-r--r-- 1 root root 3994 2021-08-03 12:16 nvram_net.txt_4358_a1
-rw-r--r-- 1 root root 44 2008-12-31 16:00 p2p_supplicant_overlay.conf
-rw-r--r-- 1 root root 81 2008-12-31 16:00 wpa_supplicant.conf
-rw-r--r-- 1 root root 60 2008-12-31 16:00 wpa_supplicant_overlay.conf

C:\Users\Family\Downloads\temp\proprietary_vendor_samsung\gts28wifi\proprietary\system\vendor\etc>adb reboot
 
Last edited:

retiredtab

Senior Member
Nov 16, 2017
828
401
I am using lineage 17 to be more specific, using lineage-17.1-20210718-UNOFFICIAL-gts28wifi.zip
That's the same version everyone is using when they replace the S6 blobs with S2 and so far no problems connecting with S2.
Tried again on another computer, I managed to push but everytime after reboot, wifi refuses to turn on.
Please describe your wifi setup. Is it single or dual band? WPA2 or WPA3 or a combination? Is your router running stock, dd-wrt or openwrt?
 

zed011

Senior Member
Jan 18, 2011
542
106
That's the same version everyone is using when they replace the S6 blobs with S2 and so far no problems connecting with S2.

Please describe your wifi setup. Is it single or dual band? WPA2 or WPA3 or a combination? Is your router running stock, dd-wrt or openwrt?

WPA2 dual band, stock. Wifi toggle says Turning on... then it changes back to off after a few seconds.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    The stock S2 wifi blobs have been incorporated into the Aug 25 17.1 builds.
  • 4
    The S2 wifi blobs have now been incorporated into the Aug 25 17.1 builds.

    Please take 10 minutes to read all of post #1 and #2. lpedia and I have spent 5 days troubleshooting this together and want to present our wifi findings. DO NOT USE this thread to report any other problems, it's only for exynos5433 S2 tablet wifi. If this is unreasonable, then stop reading. Thank you.


    If your device's wifi is not connecting after a restart and/or wake from sleep, and/or dropping out at random, this could be because the 17.1 code is using Samsung Galaxy S6 wifi blobs instead of its stock S2 wifi blobs. This commit was made in 17.1 at

    gts2: Import Galaxy S6 BCM4358 firmware · universal5433/[email protected]

    @lpedia has confirmed that LineageOS 17.1 on his T710 has the wifi problems when using S6 blobs, but not after the S6 blobs have been replaced with stock S2 blobs. This appears to fix both non-connection at boot and not reconnecting on wake from sleep. Random dropouts are less common and were not seen during the limited testing, so it's not certain that they're gone.

    FAQ

    Q1. Will changing from S6 wifi blobs solve all my wifi no reconnect or disconnect problems?
    A1. This has only been tested on the T710, and there's no guarantee it will help the other devices. If you want to try, follow the instructions below. Before you try, make sure to back up all your data. The following should write the stock S2 blobs to the /system partition only, but if you make a mistake you could lose your data! Back up first.

    It's an easy test to see if the stock S2 blobs will help or not. If your current rom does not connect to wifi after a restart, try our proposed solution. Before you do, reboot your current rom 5 times in a row. After each reboot, see if your wifi connects. After you install stock S2 blobs, reboot your device again 5 times in a row and see if wifi connects. This will easily tell you if the S2 stock blobs have solved this one particular problem or not.

    As for wifi not connecting after long/deep sleep, you should notice over 2 or 3 days if wifi connects or not after deep sleep.

    Q2. Will this work on SM-T710, SM-T810, etc?
    A2. Same answer as A1. It should work on any S2 tablet exynos5433 device that uses the S6 wifi blobs that are the default in 17.1 or Android 10. These instructions are only for exynos5433 devices.

    As the thread grows bigger, you can see who is responding back with either positive or negative feedback and what model they have.

    Q3. Will this work on RR, Havoc or LineageOS (Android 10 or 17.1)?
    A3. The instructions below replace the S6 blobs with the original stock S2 blobs. The instructions provided should work regardless if it's Havoc, RR or LineageOS. All these variant OSes share the same repo (i.e. code and blobs) on github.

    Q4. Is this post relevant to Android 9 or LineageOS 16.0?
    A4. NO. The github repos show that Android 9 or LineageOS 16.0 used the stock S2 wifi blobs. This was changed to S6 wifi blobs in Android 10 or LineageOS 17.1. I don't know why it was changed to S6 blobs as I'm not involved with that change.

    Q5. Why do I need my model and code name?
    A5. In order to follow the instructions below, you need to know your model number and it's code name. The model number or device name is settings, about tablet.

    You can find the code name at (scroll almost all the way down to the bottom)


    For example, SM-T710 is gts28wifi.

    Q6. Does it matter if my wifi is 2.4Ghz or 5Ghz or a mix of both?
    A6. When reporting back to us, please state whether your network is 2.4Ghz only, 5Ghz only, or a mix of 2.4Ghz and 5Ghz. In addition, if its a mix, please let us know if it's one wifi network (same ssid) or two separate wifi networks. That is, 2.4Ghz is one ssid and 5Ghz is another ssid.

    Q7. If this works, how will this be fixed for the next release of code and the future?
    A7. If enough people say it fixes their wifi problems, I can submit a git pull request to Anan to revert the S6 wifi blobs back to S2 wifi blobs.

    Instructions

    1. Make sure adb debugging is enabled in developer options. To enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.

    Note if you are running Magisk, see posts regarding Magisk if you cannot see rooted debugging.

    2. You will need git. There are instructions and download links for installing git on Windows, MacOS, and Linux at Git Guides - install git | GitHub.
    3. After you install git, follow the instructions exactly below.
    Bash:
    # make temporary vendor directory
    mkdir temp
    # cd to that directory
    cd temp
    # git the 16.0 stock drivers
    git clone https://github.com/universal5433/proprietary_vendor_samsung -b lineage-16.0
    # change directory to proprietary_vendor_samsung/<your device>/proprietary/system/vendor/etc
    # or if Windows, to proprietary_vendor_samsung\<your device>\proprietary\system\vendor\etc
    # where "<your device>" is your device's code, for example gts28wifi for the T710:
    cd proprietary_vendor_samsung/gts28wifi/proprietary/system/vendor/etc
    # start adb root
    adb root
    # remount /system as rw (it's read only by default)
    adb remount
    # start adb shell
    adb shell
    # delete S6 blobs from wifi directory
    cd /system/vendor/etc/wifi
    rm bcm*
    rm nvr*
    # There should be only .conf files left now
    ls -al
    exit
    # you should be back at your desktop terminal prompt now
    # now push all stock drivers to /system/vendor/etc/wifi
    adb push wifi /system/vendor/etc
    # check to make sure it got pushed okay
    adb shell ls -al /system/vendor/etc/wifi
    # now reboot Android
    adb reboot

    If the above does not work for you, or if it causes other problems, just reflash the last rom. That will overwrite the /system partition and everything will be restored.

    If you do try this, please report back to this thread about whatever happened and include your device and what wifi network you are running.
    4
    In addition, the reversion back to S2 wifi blobs has been accepted and approved as per

    https://github.com/universal5433/pr...mmit/121da375a368abc6012abc4c054dab49924a5f06

    It should be in the next August security patch build.
    1
    Thanks for the instructions!
    I had to boot my T810 (gts210wifi) into TWRP and mount /system from there before adb root and adb remount was possible. Everything else worked as described.
    Observations after 5 reboots: WiFi available after reboot each time! Much better than before!
    I will observe it now for a while regarding wifi-off after sleep or sporadical wifi-off.
    Btw. for the random reboots of the unmodified linageos17.1 (ripee) I'm pinging my DNS-server all 2mins using Tasker. Fixed reboots since 2 month at least on my system.
    1
    Short update: The S2 wifi blobs are a huge improvement. With S6 blobs I had reliable dropoffs at medium router-signal combined with heavy wifi-load (no dropoffs with full router signal). With the S2 blobs no single dropoff even at weak router-signal and heavy wifi-load for several hours now.
    1
    The stock S2 wifi blobs have been incorporated into the Aug 25 17.1 builds.