RTL8723BS Wireless driver issues with Cherrytrail and disconnects after sleep/suspend

164 views
Skip to first unread message

ouija

unread,
Jul 30, 2019, 1:26:12 PM7/30/19
to Android-x86
After trying a million different patches to try and resolve this issue, I'm forced to ask if anyone may have a working solution to this problem:

My Cherrytrail based device (Insignia Flex8) has the rtl8723bs wifi/bt card in it, and it appears to have issues with reconnecting to wifi after suspend/resume.  (cannot re-connect to SSID, will say "saved" next to connected wifi but won't reconnect to it, and need to manually reprobe the r8723bs module in order to fix this).

A similar issue for another device was discussed here: https://github.com/lwfinger/rtl8723bu/issues/91 but it appears that a variation of the patch to resolve it (https://github.com/carlocaione/rtl8723bu/commit/2913f99da92a96364b29291bde84862b2cc5a7db) is already applied to the r8723bs driver.

Something similar to https://patchwork.kernel.org/patch/10660879/ might work as well, which in essence is what I have in place at the moment via a script, where I am removing the module on sleep and reprobing on resume (similar to: https://groups.google.com/d/msg/android-x86/u8fBVUDqIGg/kreyVnkjCgAJ)

If there's a way to fix suspend/resume issues related to the r8723bs driver that doesn't involve unloading/reloading the module itself, I'd much rather go that route instead. 

Thanks!

Daniel Cheung

unread,
Jul 30, 2019, 1:31:23 PM7/30/19
to andro...@googlegroups.com
From my experience, it seems this problem isn't happening in hibernation (kernel config disable suspend). But my device is having problem waking up from hibernation. I'm about to re-compile the kernel and test again using hibernation with additional i915 kernel parameters.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/25cd3c2a-0090-428d-ba59-cfec033c04a3%40googlegroups.com.

Jon West

unread,
Jul 30, 2019, 8:51:44 PM7/30/19
to Android-x86
This piece might be something I'd try to help solve the wifi reconnection issues on many devices. 

ouija

unread,
Aug 3, 2019, 3:16:10 PM8/3/19
to Android-x86
UPDATE:  Made a huge discovery the day a newer patch was put out related to the disconnect issues of the rtl8723bs, and after applying it (along with two other patches I came across), I've noticed quite an improvement.

The network still seems to disconnect randomly sometimes, but now I'm able to re-connect properly (without the network simply saying "saved" and not actually reconnecting), and this additional path has improved signal strength dramtically.

The first patch that seems to resolve the "disconnect/reconnect" issue is here: [PATCH] staging: rtl8723bs: indicate disconnection when disconnecting and was literally just posted last week :)

Then there were a couple other patches I stumbled across that good ol' youling 257 had a hand in providing -- the first being one that improved the wireless connection signal here: https://bugzilla.kernel.org/show_bug.cgi?id=201611#c12 (note that due to the whitespace around this particular patch, you'll need to apply it manually but it simply involves removing a single exclaimation point from line 112 of this ./kernel/drivers/staging/rtl8623bs/hal/rtl8723bs_recv.c file), and the second patch in the same thread at https://bugzilla.kernel.org/show_bug.cgi?id=201611#c18 fixes an issue with this NL80211_STA_INFO_TX_FAILED error that was occurring in the logs

With these three patches, the wireless has certainly shown major improvement for me on Android-x86 81.-r2 and kernel 4.18

On top of this, I managed to get Bluetooth working on the rtl8723bs by applying these patches: https://patchwork.kernel.org/cover/10553793/  (click "show related" and you'll see the 10 related patches need to do the same)

However, I am having issues with bluetooth not seeing any "available devices" when scanning, but other devices can see it, which is strange, but might be related to a change elsewhere in 8.1, as referenced here: https://groups.google.com/forum/#!searchin/android-x86/pairing%7Csort:date/android-x86/2fCWy4ST-g4/qp_wY580AQAJ

If anyone has suggests to fixing this, I'm all ears.   Going to test out 7.2 with the same patches and kernel version to see if indeed it works, and hopefully try and determine what might be different between the two releases that could be causing this.

I also managed to resolve an issue I was having with sleep/hybernation on this cherrytrail device and the system actually freezing or locking up in a sleep state and not responding (I'll post this in my other thread related to the Insignia Flex8)

Enjoy!

Reply all
Reply to author
Forward
0 new messages