I assume the "systemless" root method does not change the system partition of the rom and leaves it mounte read only.
After the first failed attempt and a short logcat-review, I mounted the system partition (/system) as read-write, double checked the /system/lib/hw permissions (rwx r-x r-x) and the root access.
The error message within the app was "Failed to install Bluetooth drivers" with Generic and Generic (old) method.
Choosing the "recovery installation" results in a return to the home-screen without further messages, neither popup nor toast.
Uninstalled the installer app, as the logcat told me "no file permission granted, as the app was installed without the permissions before". Reinstalled it and tried again.
Now the error message has no additional "Bluetooth driver installation failed" message, but simply says "Failed".
The logcat indicates a problem linking the patched .so file from the rsap_install cache folder to the /system/lib/hw folder.
Code: Select all
12-28 13:11:18.490 E/InstallCopyTask(13680): java.lang.Exception: cat /data/user/0/com.android_rsap.rsapinstall/cache/bluetooth.patched.so > /system/lib/hw/bluetooth.msm8974.so failed
12-28 13:11:18.490 E/InstallCopyTask(13680): at com.android_rsap.rsapinstall.at.b(Unknown Source)
12-28 13:11:18.490 E/InstallCopyTask(13680): at com.android_rsap.rsapinstall.k.d(Unknown Source)
12-28 13:11:18.490 E/InstallCopyTask(13680): at com.android_rsap.rsapinstall.k.a(Unknown Source)
12-28 13:11:18.490 E/InstallCopyTask(13680): at com.android_rsap.rsapinstall.k.doInBackground(Unknown Source)
Changing this to "root" leads to an earlier error, as the app now has no permission to access the lib in the cache folder

For testing purpose, changing the permission of the cache file to 777, the old error message is back, as shown in the logcat below.
changing the /system/lib/hw/ folder permissions to 777 is not allowed apparently.
As ES is on a decending path, I chose to buy root explorer and chose mount r/w directly in the /system/lib/ folder -> Installation works!
But now, an old problem is back: "SIM status" is telling me "socket error" in the rSAP app

busybox is a fresh install (1.24.1 provided by Stericson), the logcat shows a bunch of "ps output:XXXXX" errors, I assume for any process running, but all logcats categorized within the RSAPUtils part.
just one short example to keep the post small:
Code: Select all
12-28 13:39:52.998 E/RSAPUtils(20553): unexpected ps output: 1233 10011 0:01 {e.process.gapps} com.google.process.gapps
12-28 13:39:52.998 E/RSAPUtils(20553): java.lang.NumberFormatException: Invalid int: "0:01"
12-28 13:39:52.998 E/RSAPUtils(20553): at java.lang.Integer.invalidInt(Integer.java:138)
12-28 13:39:52.998 E/RSAPUtils(20553): at java.lang.Integer.parse(Integer.java:410)
12-28 13:39:52.998 E/RSAPUtils(20553): at java.lang.Integer.parseInt(Integer.java:367)
12-28 13:39:52.998 E/RSAPUtils(20553): at java.lang.Integer.parseInt(Integer.java:334)
12-28 13:39:52.998 E/RSAPUtils(20553): at com.android_rsap.rsap.ld.a(ld.java)
12-28 13:39:52.998 E/RSAPUtils(20553): at com.android_rsap.rsap.jd.f(jd.java)
12-28 13:39:52.998 E/RSAPUtils(20553): at com.android_rsap.rsap.jd.c(jd.java)
12-28 13:39:52.998 E/RSAPUtils(20553): at com.android_rsap.rsap.tc.c(tc.java)
12-28 13:39:52.998 E/RSAPUtils(20553): at com.android_rsap.rsap.tc.d(tc.java)
12-28 13:39:52.998 E/RSAPUtils(20553): at com.android_rsap.rsap.pd.run(pd.java)
12-28 13:39:52.999 E/RSAPUtils(20553): unexpected ps output: 1310 10011 0:10 {gle.android.gms} com.google.android.gms
12-28 13:39:52.999 E/RSAPUtils(20553): java.lang.NumberFormatException: Invalid int: "0:10"
12-28 13:39:52.999 E/RSAPUtils(20553): at java.lang.Integer.invalidInt(Integer.java:138)
12-28 13:39:52.999 E/RSAPUtils(20553): at java.lang.Integer.parse(Integer.java:410)
12-28 13:39:52.999 E/RSAPUtils(20553): at java.lang.Integer.parseInt(Integer.java:367)
12-28 13:39:52.999 E/RSAPUtils(20553): at java.lang.Integer.parseInt(Integer.java:334)
12-28 13:39:52.999 E/RSAPUtils(20553): at com.android_rsap.rsap.ld.a(ld.java)
12-28 13:39:52.999 E/RSAPUtils(20553): at com.android_rsap.rsap.jd.f(jd.java)
12-28 13:39:52.999 E/RSAPUtils(20553): at com.android_rsap.rsap.jd.c(jd.java)
12-28 13:39:52.999 E/RSAPUtils(20553): at com.android_rsap.rsap.tc.c(tc.java)
12-28 13:39:52.999 E/RSAPUtils(20553): at com.android_rsap.rsap.tc.d(tc.java)
12-28 13:39:52.999 E/RSAPUtils(20553): at com.android_rsap.rsap.pd.run(pd.java)
Code: Select all
12-28 13:39:53.008 E/RSAPUtils(20553): unexpected ps output:20553 10088 0:00 {droid_rsap.rsap} com.android_rsap.rsap
12-28 13:39:53.008 E/RSAPUtils(20553): java.lang.NumberFormatException: Invalid int: "0:00"
12-28 13:39:53.008 E/RSAPUtils(20553): at java.lang.Integer.invalidInt(Integer.java:138)
12-28 13:39:53.008 E/RSAPUtils(20553): at java.lang.Integer.parse(Integer.java:410)
12-28 13:39:53.008 E/RSAPUtils(20553): at java.lang.Integer.parseInt(Integer.java:367)
12-28 13:39:53.008 E/RSAPUtils(20553): at java.lang.Integer.parseInt(Integer.java:334)
12-28 13:39:53.008 E/RSAPUtils(20553): at com.android_rsap.rsap.ld.a(ld.java)
12-28 13:39:53.008 E/RSAPUtils(20553): at com.android_rsap.rsap.jd.f(jd.java)
12-28 13:39:53.008 E/RSAPUtils(20553): at com.android_rsap.rsap.jd.c(jd.java)
12-28 13:39:53.008 E/RSAPUtils(20553): at com.android_rsap.rsap.tc.c(tc.java)
12-28 13:39:53.008 E/RSAPUtils(20553): at com.android_rsap.rsap.tc.d(tc.java)
12-28 13:39:53.008 E/RSAPUtils(20553): at com.android_rsap.rsap.pd.run(pd.java)
12-28 13:39:53.009 E/RSAPUtils(20553): unexpected ps output:20572 10088 0:00 su
12-28 13:39:53.009 E/RSAPUtils(20553): java.lang.NumberFormatException: Invalid int: "0:00"
12-28 13:39:53.009 E/RSAPUtils(20553): at java.lang.Integer.invalidInt(Integer.java:138)
12-28 13:39:53.009 E/RSAPUtils(20553): at java.lang.Integer.parse(Integer.java:410)
12-28 13:39:53.009 E/RSAPUtils(20553): at java.lang.Integer.parseInt(Integer.java:367)
12-28 13:39:53.009 E/RSAPUtils(20553): at java.lang.Integer.parseInt(Integer.java:334)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.ld.a(ld.java)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.jd.f(jd.java)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.jd.c(jd.java)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.tc.c(tc.java)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.tc.d(tc.java)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.pd.run(pd.java)
12-28 13:39:53.009 E/RSAPUtils(20553): unexpected ps output:20577 10088 0:00 ps
12-28 13:39:53.009 E/RSAPUtils(20553): java.lang.NumberFormatException: Invalid int: "0:00"
12-28 13:39:53.009 E/RSAPUtils(20553): at java.lang.Integer.invalidInt(Integer.java:138)
12-28 13:39:53.009 E/RSAPUtils(20553): at java.lang.Integer.parse(Integer.java:410)
12-28 13:39:53.009 E/RSAPUtils(20553): at java.lang.Integer.parseInt(Integer.java:367)
12-28 13:39:53.009 E/RSAPUtils(20553): at java.lang.Integer.parseInt(Integer.java:334)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.ld.a(ld.java)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.jd.f(jd.java)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.jd.c(jd.java)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.tc.c(tc.java)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.tc.d(tc.java)
12-28 13:39:53.009 E/RSAPUtils(20553): at com.android_rsap.rsap.pd.run(pd.java)
The logcat tells me the "RSAPBroadcastReceiver" is "##### starting rSAP services ##### but apparently the rSAP app is not able to connect to it because it gets crap from the "ps" command.
If you need help testing a sideloaded fix, just give me short notice, we once had an email discussion about the Google Product forum thread about the removed rsap-interface in the current baseband of LG, which Google ironically marked as "obsolete" during M development and never changed the status back to "open".

Edit: Forgot to mention the reboot during testing after the last action and a manually killed rSAP app in between, did not work out either^^