[Galaxy S III Original Android Development] curiousrom:
Battery Charging Speed & WiFi Disconnecting Problem

Charging is fine for me on stock Official Lineage 14.1 S3 i9300 (my daily driver) for 6 months updated almost every week since then (currently 2018-05-24) using the built-in Lineage Updater + Open Gapps 7.1 ARM Pico (2018-05-28) + Lineage ARM super user add-on but I often have to connect/disconnect the cable a couple of times to achieve the maximum 1000 mAh charging current that the S3 can receive when connected to a power adapter with a 5v 1A minimum output.

Check this S3 Battery Charging Current Monitoring post for explanations about why I am using Galaxy Charging Current to monitor the S3 while charging and especially the app's developer quote in it.

Check also this post and Robert-R's post here about testing the app's data vs. his "usb-current-meter".

BTW [MENTION=7746932]Robert-R[/MENTION] with your battery under 90% and using your USB current meter while charging the phone turned off vs. with the phone turned on is the voltage & ampere the same?

***

Wifi Not Connecting Anymore

Ahh... nice to have proper device troubleshooting info + a filtered Logcat of when the problem occurred. Thanks! :good:

"I've had the issue on this phone with various other build as well..." - So if it's not Lineage specific it could be that you have an old Modem (baseband). What does it say in > Settings > About phone > Baseband version?

Or it could be hardware related. Since you have two S3's you could install on both this free WiFi Analyzer app, go as far as possible from the router w/o loosing signal & check in Access Points the strength of the signal reception which is in dBm so the lower the number, the better.

If the problematic S3 signal reception is not as good as the other one it could be the Wifi chip or that the wifi antenna is not properly connected to the antenna's female motherboard side connector.

See step 20 of this iFixit S3 repair guide (antenna & connector spare part} & my attachment.

You could try this S3 Lineage Crashing Wifi Network Reconnecting Bug Workaround which may give a more stable Wifi connection via static IP.

I'm not a pro on the subject but looking at your logcat it seems that your S3 blacklisted your router :eek: because it took too long to establish a proper connection & a factory reset probably clears that blacklist (E/ stands for Error):

roamingFailureBlackListTimeMilli: 1000

[05-29 21:29:55.124 2374:2472 E/WifiQualifiedNetworkSelector:]

Rickerby Lounge:18:f1:45:24:34:4b is in blacklist.

[05-29 21:29:55.125 2374:2472 E/WifiQualifiedNetworkSelector:]

Rickerby Upstairs:e0:46:9a:16:49:86 is in blacklist.

Maybe you could try > Settings > Wi-Fi > press your network's name > Forget then reboot & connect.

Or > Settings > Wi-Fi > 3-dots > Advanced > and set Wi-Fi region code to the same as your router.

You could try web searches like WifiQualifiedNetworkSelector blacklist Sorry I don't know how to edit that list or to change for longer roamingFailureBlackListTimeMilli timeout.

If rooted look in /data/misc/wifi/config/ for a blacklist file or search in the networkHistory.txt with keyword blacklist maybe?

As usual: please report back if it works for you or not. :cool:

***