Discussion:
Realtek RTL8723BS Bluetooth on Android
spin877
2016-02-04 04:32:45 UTC
Permalink
Android Marshmallow and kernel version 4.4.0 Vanilla Bluetooth works

here source <https://github.com/sfumato77/rtl8723bs_bt>

give command


*rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5*

on my tablet the dev is /dev/ttyS1
for you could be another dev

attached compiled 32 and 64 bit

Now the question is:
how to integrate the Rom and initialize it in the script init.rc?
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mario Holzinger
2016-02-04 06:58:32 UTC
Permalink
Thank you for that will try it when I get home today and will also provide
a patch for everithing needed (init.sh,...) if I get it working

best regards
Mario
Post by spin877
Android Marshmallow and kernel version 4.4.0 Vanilla Bluetooth works
here source <https://github.com/sfumato77/rtl8723bs_bt>
give command
*rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5*
on my tablet the dev is /dev/ttyS1
for you could be another dev
attached compiled 32 and 64 bit
how to integrate the Rom and initialize it in the script init.rc?
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mario Holzinger
2016-02-05 11:34:59 UTC
Permalink
May I ask for a little bit of extra information.

I am working on lollipop sources
take your precompiled binary (x32) and copy it to /etc/
take your start_bt.sh from sources and copy it to /etc/ (it allready has a
auto detection for the hopfully correct dev)
take the firmware from the sources and place it according to the Makefile
in /lib/firmware/rtk_bt/

manual start do not work ==> autodisabling BT when I try to activate the
BT-Module
autostart by init.sh also not working same situation

do I miss somthing important?

thx
Mario
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
spin877
2016-02-05 12:58:04 UTC
Permalink
In my pre-compiled , firmware, and config files they have been integrated .
each time you start rtk_hciattach he writes in /data/local/tmp/rtlbt_fw
etc.... . and then charging .
I know it 's stupid and redundant , but I'm not a professional programmer .
I was difficult to enter the firmware in ROM , I put the firmware in the
executable :-p

I tried I start_bt.sh script but does not work for me.
It reveals two ports com " MMIO " and locks .

the orignal code I took from here https://github.com/lwfinger/rtl8723bs_bt
Post by Mario Holzinger
manual start do not work ==> autodisabling BT when I try to activate the
BT-Module

give command

*rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5*

should respond

*Realtek Bluetooth :Init Process finished*
*Realtek Bluetooth post process*
*Device setup complete*

do not touch.
open a new shell

give command

*hciconfig*

should respond

*hciconfig*
*hci0: Type: BR/EDR Bus: UART*
* BD Address: 00:1A:13:6B:32:C5 ACL MTU: 1021:8 SCO MTU: 255:16*
* DOWN*
* RX bytes:1290 acl:0 sco:0 events:29 errors:0*
* TX bytes:789 acl:0 sco:0 commands:29 errors:0*


It means that the drivers side is ready . Lollipop is interfering with
marshmallow works on the first try


P.S.
try
*hciconfig hci0 up*
excuse my English use google translate :-(
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-03-30 07:00:05 UTC
Permalink
***@android_x86:/ $ su
***@android_x86:/ # rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5
Realtek Bluetooth init uart with init speed:115200, final_speed:115200,
type:HCI UART H5
Realtek Bluetooth :Realtek hciattach version 2.5

Realtek Bluetooth :3-wire sync pattern resend : 1, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 2, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 3, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 4, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 5, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 6, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 7, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 8, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 9, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 10, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 11, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 12, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 13, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 14, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 15, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 16, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 17, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 18, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 19, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 20, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 21, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 22, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 23, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 24, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 25, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 26, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 27, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 28, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 29, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 30, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 31, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 32, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 33, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 34, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 35, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 36, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 37, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 38, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 39, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 40, len: 8

Realtek Bluetooth ERROR: H5 sync timed out

1|***@android_x86:/ #

what mean ?

圚 2016幎2月5日星期五 UTC+8䞋午8:58:05spin877写道
Post by spin877
In my pre-compiled , firmware, and config files they have been integrated .
each time you start rtk_hciattach he writes in /data/local/tmp/rtlbt_fw
etc.... . and then charging .
I know it 's stupid and redundant , but I'm not a professional programmer .
I was difficult to enter the firmware in ROM , I put the firmware in the
executable :-p
I tried I start_bt.sh script but does not work for me.
It reveals two ports com " MMIO " and locks .
the orignal code I took from here https://github.com/lwfinger/rtl8723bs_bt
Post by Mario Holzinger
manual start do not work ==> autodisabling BT when I try to activate the
BT-Module
give command
*rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5*
should respond
*Realtek Bluetooth :Init Process finished*
*Realtek Bluetooth post process*
*Device setup complete*
do not touch.
open a new shell
give command
*hciconfig*
should respond
*hciconfig*
*hci0: Type: BR/EDR Bus: UART*
* BD Address: 00:1A:13:6B:32:C5 ACL MTU: 1021:8 SCO MTU: 255:16*
* DOWN*
* RX bytes:1290 acl:0 sco:0 events:29 errors:0*
* TX bytes:789 acl:0 sco:0 commands:29 errors:0*
It means that the drivers side is ready . Lollipop is interfering with
marshmallow works on the first try
P.S.
try
*hciconfig hci0 up*
excuse my English use google translate :-(
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
spin877
2016-02-07 00:38:41 UTC
Permalink
I modified the script start_bt.sh bluetooth detection.
manually it works.
how do I start it each time you start automatically?
What should I write in /system/etc/init.sh?

-------- cut here script start_bt.sh

#!/system/bin/sh
#
# Shell script to install Bluetooth firmware and attach BT part of
# RTL8723BS
#
RTK_DRV=`lsmod | grep r8723bs`

if [ "$RTK_DRV" != "" ];then
TTY=`dmesg -t | grep tty | grep -m 1 MMIO | cut -b 14-18`
else
echo
echo "No modules r8723bs to be loaded"
echo
exit 1
fi

if [ "$TTY" != "" ];then
TTY="/dev/$TTY"
echo "Using device $TTY for Bluetooth"
/system/xbin/rtk_hciattach -n -s 115200 $TTY rtk_h5
/data/local/tmp/hciattach.txt 2>&1 &
else
echo
echo "No r8723bs BT TTY device has been found"
echo "Either this computer has no BT device that uses
hciattach, or"
echo "Your kernel does not have module 8250_dw configured."
echo "Note: The configuration variable is
CONFIG_SERIAL_8250_DW."
echo
fi
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-03-12 14:39:07 UTC
Permalink
Did you succeed 

圚 2016幎2月7日星期日 UTC+8䞊午8:38:41spin877写道
Post by spin877
I modified the script start_bt.sh bluetooth detection.
manually it works.
how do I start it each time you start automatically?
What should I write in /system/etc/init.sh?
-------- cut here script start_bt.sh
#!/system/bin/sh
#
# Shell script to install Bluetooth firmware and attach BT part of
# RTL8723BS
#
RTK_DRV=`lsmod | grep r8723bs`
if [ "$RTK_DRV" != "" ];then
TTY=`dmesg -t | grep tty | grep -m 1 MMIO | cut -b 14-18`
else
echo
echo "No modules r8723bs to be loaded"
echo
exit 1
fi
if [ "$TTY" != "" ];then
TTY="/dev/$TTY"
echo "Using device $TTY for Bluetooth"
/system/xbin/rtk_hciattach -n -s 115200 $TTY rtk_h5
/data/local/tmp/hciattach.txt 2>&1 &
else
echo
echo "No r8723bs BT TTY device has been found"
echo "Either this computer has no BT device that uses
hciattach, or"
echo "Your kernel does not have module 8250_dw configured."
echo "Note: The configuration variable is
CONFIG_SERIAL_8250_DW."
echo
fi
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
spin877
2016-03-13 09:17:28 UTC
Permalink
in my opinion
only the patch /net/rfkill/rfkill-gpio.c not enough

We must always load the firmware *rtlbt_fw* with

*rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5*
Post by youling 257
Did you succeed 
圚 2016幎2月7日星期日 UTC+8䞊午8:38:41spin877写道
Post by spin877
I modified the script start_bt.sh bluetooth detection.
manually it works.
how do I start it each time you start automatically?
What should I write in /system/etc/init.sh?
-------- cut here script start_bt.sh
#!/system/bin/sh
#
# Shell script to install Bluetooth firmware and attach BT part of
# RTL8723BS
#
RTK_DRV=`lsmod | grep r8723bs`
if [ "$RTK_DRV" != "" ];then
TTY=`dmesg -t | grep tty | grep -m 1 MMIO | cut -b 14-18`
else
echo
echo "No modules r8723bs to be loaded"
echo
exit 1
fi
if [ "$TTY" != "" ];then
TTY="/dev/$TTY"
echo "Using device $TTY for Bluetooth"
/system/xbin/rtk_hciattach -n -s 115200 $TTY rtk_h5
/data/local/tmp/hciattach.txt 2>&1 &
else
echo
echo "No r8723bs BT TTY device has been found"
echo "Either this computer has no BT device that uses
hciattach, or"
echo "Your kernel does not have module 8250_dw configured."
echo "Note: The configuration variable is
CONFIG_SERIAL_8250_DW."
echo
fi
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-03-30 06:58:02 UTC
Permalink
firstI don't know /dev/tty? on my tabletthenhow to load *rtlbt_fw ?*

圚 2016幎3月13日星期日 UTC+8䞋午5:17:29spin877写道
Post by spin877
in my opinion
only the patch /net/rfkill/rfkill-gpio.c not enough
We must always load the firmware *rtlbt_fw* with
*rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5*
Post by youling 257
Did you succeed 
圚 2016幎2月7日星期日 UTC+8䞊午8:38:41spin877写道
Post by spin877
I modified the script start_bt.sh bluetooth detection.
manually it works.
how do I start it each time you start automatically?
What should I write in /system/etc/init.sh?
-------- cut here script start_bt.sh
#!/system/bin/sh
#
# Shell script to install Bluetooth firmware and attach BT part of
# RTL8723BS
#
RTK_DRV=`lsmod | grep r8723bs`
if [ "$RTK_DRV" != "" ];then
TTY=`dmesg -t | grep tty | grep -m 1 MMIO | cut -b 14-18`
else
echo
echo "No modules r8723bs to be loaded"
echo
exit 1
fi
if [ "$TTY" != "" ];then
TTY="/dev/$TTY"
echo "Using device $TTY for Bluetooth"
/system/xbin/rtk_hciattach -n -s 115200 $TTY rtk_h5
/data/local/tmp/hciattach.txt 2>&1 &
else
echo
echo "No r8723bs BT TTY device has been found"
echo "Either this computer has no BT device that uses
hciattach, or"
echo "Your kernel does not have module 8250_dw configured."
echo "Note: The configuration variable is
CONFIG_SERIAL_8250_DW."
echo
fi
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-03-08 18:05:49 UTC
Permalink
Bluetooth

The WiFi drivers indeed are also drivers for Bluetooth, but getting
Bluetooth working is a bit difficult. You need to patch your kernel with this
patch
<https://raw.githubusercontent.com/Manouchehri/vi8/master/Ubuntu_support_files/rfkill.patch>.
Then use this program <https://github.com/lwfinger/rtl8723bs_bt> to add the
firmware to your Linux install and also there is a script that needs to be
run each boot to turn on the Bluetooth module.


https://github.com/Manouchehri/vi8/blob/master/Ubuntu_instructions.md


This patchhow to work on android kernel ?
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-03-10 02:57:29 UTC
Permalink
I see
herehttps://sourceforge.net/p/android-x86/kernel/ci/bb80f724827e49d507ef37a3ca525f6406bafa1e/then
I build 4.4.4 kernelthen where is rt8723bs bt ? how to enable it ?

圚 2016幎3月10日星期四 UTC+8䞊午1:32:59Chih-Wei Huang写道
Post by spin877
Post by spin877
Bluetooth
The WiFi drivers indeed are also drivers for Bluetooth, but getting
Bluetooth working is a bit difficult. You need to patch your kernel with
this patch. Then use this program to add the firmware to your Linux
install
Post by spin877
and also there is a script that needs to be run each boot to turn on the
Bluetooth module.
https://github.com/Manouchehri/vi8/blob/master/Ubuntu_instructions.md
This patchhow to work on android kernel ?
OK, I applied the patch.
Thanks!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-04-04 16:05:20 UTC
Permalink
https://sourceforge.net/p/android-x86/kernel/ci/bb80f724827e49d507ef37a3ca525f6406bafa1e/#diff-3@@
-167,6 +167,7 @@really right ?
I see some place@@ -172,6 +172,7 @@@@ -168,6 +168,7 @@
Chih-Wei Huang

圚 2016幎3月10日星期四 UTC+8䞊午1:32:59Chih-Wei Huang写道
Post by spin877
Post by spin877
Bluetooth
The WiFi drivers indeed are also drivers for Bluetooth, but getting
Bluetooth working is a bit difficult. You need to patch your kernel with
this patch. Then use this program to add the firmware to your Linux
install
Post by spin877
and also there is a script that needs to be run each boot to turn on the
Bluetooth module.
https://github.com/Manouchehri/vi8/blob/master/Ubuntu_instructions.md
This patchhow to work on android kernel ?
OK, I applied the patch.
Thanks!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-03-26 09:43:32 UTC
Permalink
how to load rtl8723bs bt every boot ?
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
spin877
2016-03-26 10:36:51 UTC
Permalink
I think so. I tried with init.sh but I did not succeed.
I do not understand how it works
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-03-30 07:28:34 UTC
Permalink
see herehttps://github.com/lwfinger/rtl8723bs_bt/issues/2
https://github.com/lwfinger/rtl8723bs_bt/issues/7

***@android_x86:/ $ su
***@android_x86:/ # dmesg | grep tty
[ 4.365141] 80860F0A:00: ttyS1 at MMIO 0x9091b000 (irq = 191, base_baud
= 2764800) is a 16550A
[ 4.376313] 80860F0A:01: ttyS2 at MMIO 0x9091d000 (irq = 192, base_baud
= 2764800) is a 16550A
***@android_x86:/ # rtk_hciattach -n -s 115200 /dev/ttyS2 rtk_h5
Realtek Bluetooth init uart with init speed:115200, final_speed:115200,
type:HCI UART H5
Realtek Bluetooth :Realtek hciattach version 2.5

Realtek Bluetooth :3-wire sync pattern resend : 1, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 2, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 3, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 4, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 5, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 6, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 7, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 8, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 9, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 10, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 11, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 12, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 13, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 14, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 15, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 16, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 17, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 18, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 19, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 20, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 21, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 22, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 23, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 24, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 25, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 26, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 27, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 28, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 29, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 30, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 31, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 32, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 33, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 34, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 35, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 36, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 37, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 38, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 39, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 40, len: 8

Realtek Bluetooth ERROR: H5 sync timed out

1|***@android_x86:/ # rfkill list
0: phy0: wlan
Soft blocked: no
Hard blocked: no
***@android_x86:/ #

圚 2016幎2月4日星期四 UTC+8䞋午12:32:46spin877写道
Post by spin877
Android Marshmallow and kernel version 4.4.0 Vanilla Bluetooth works
here source <https://github.com/sfumato77/rtl8723bs_bt>
give command
*rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5*
on my tablet the dev is /dev/ttyS1
for you could be another dev
attached compiled 32 and 64 bit
how to integrate the Rom and initialize it in the script init.rc?
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-03-30 08:06:07 UTC
Permalink
nowsee herehttps://github.com/lwfinger/rtl8723bs_bt/issues/4

“I think I have found the problem. I was using the rtl8723 firmware from
linux-firmware.git instead of the one provided in this repository.

Neither rtl8723a_fw.bin nor rtl8723b_fw.bin work (rtk_hciattach will load
them and say "device succesfully configured" but no device is created.

Also, the configuration speed must be 115200, not the advertised 2764800.”
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-03-30 09:01:59 UTC
Permalink
I try thisstill H5 sync timed outmay be not load *rtlbt_fw*how to load *rtlbt_fw
*

圚 2016幎3月30日星期䞉 UTC+8䞋午4:06:08youling 257写道
Post by youling 257
nowsee herehttps://github.com/lwfinger/rtl8723bs_bt/issues/4
“I think I have found the problem. I was using the rtl8723 firmware from
linux-firmware.git instead of the one provided in this repository.
Neither rtl8723a_fw.bin nor rtl8723b_fw.bin work (rtk_hciattach will load
them and say "device succesfully configured" but no device is created.
Also, the configuration speed must be 115200, not the advertised 2764800.”
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-06-04 16:21:39 UTC
Permalink
https://github.com/lwfinger/rtl8723bs_bt/issues/7
“I added the lines from here
<https://raw.githubusercontent.com/Manouchehri/vi8/master/Ubuntu_support_files/rfkill.patch>.
(had to edit by hand, patch didn't work, since there are other changes on
4.5 kernel in rfkill). Then enabled CONFIG_RFKILL_GPIO=m in kernel config
and recompiled kernel. Re-installed rtl8723bs and rtl8723bs_bt and it
worked.”
need CONFIG_RFKILL_GPIO=m
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-06-04 16:24:25 UTC
Permalink
https://sourceforge.net/p/android-x86/kernel/ci/kernel-4.4/tree/arch/x86/configs/android-x86_64_defconfig
# CONFIG_RFKILL_GPIO is not set
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-06-05 12:08:39 UTC
Permalink
nice
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-06-05 23:17:50 UTC
Permalink
Chih-Wei HuangI see you add CONFIG_RFKILL_GPIO=m to kernel tree
https://sourceforge.net/p/android-x86/kernel/ci/bf3cf2a8dded98d77e4c3ed12c19bedb65c4f955/
I tell youneed system/bin/*rtk_hciattach*please extract rtk_hciattach.tar.gz
and add to source need every boot*rtk_hciattach -n -s 115200 /dev/ttyS1
rtk_h5*please add it to init.sh
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-06-06 03:11:08 UTC
Permalink
看䞍懂䜠英文的意思
劂果同步猖译源码埗到iso对于我的讟倇必须修改system.img倍制进去/bin/rtk_hciattach倍制进去/etc/init.d/2.shcm13支持init.d
2.sh只需芁这样猖蟑
#!/system/bin/sh
rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5


圚 2016幎6月6日星期䞀 UTC+8䞊午10:34:04Chih-Wei Huang写道
Post by youling 257
Post by youling 257
Chih-Wei HuangI see you add CONFIG_RFKILL_GPIO=m to kernel tree
https://sourceforge.net/p/android-x86/kernel/ci/bf3cf2a8dded98d77e4c3ed12c19bedb65c4f955/
Post by youling 257
I tell youneed system/bin/rtk_hciattachplease extract
rtk_hciattach.tar.gz
Please use btattach (fix or modify it if necessary).
Post by youling 257
and add to source need every bootrtk_hciattach -n -s 115200 /dev/ttyS1
rtk_h5please add it to init.sh
Provide a patch for your device.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-06-06 03:21:22 UTC
Permalink
Do not understand the meaning of your English
If compile the source code to get ISO, must modify the system.img, copy
into the /bin/rtk_hciattach, copy into the /etc/init.d/2.sh, cm13 support
init.d,
2.sh, it just needs to be edited.
# /system/bin/sh!
rtk_hciattach -n -s /dev/ttyS1 115200 rtk_h5

圚 2016幎6月6日星期䞀 UTC+8䞊午10:34:04Chih-Wei Huang写道
Post by youling 257
Post by youling 257
Chih-Wei HuangI see you add CONFIG_RFKILL_GPIO=m to kernel tree
https://sourceforge.net/p/android-x86/kernel/ci/bf3cf2a8dded98d77e4c3ed12c19bedb65c4f955/
Post by youling 257
I tell youneed system/bin/rtk_hciattachplease extract
rtk_hciattach.tar.gz
Please use btattach (fix or modify it if necessary).
Post by youling 257
and add to source need every bootrtk_hciattach -n -s 115200 /dev/ttyS1
rtk_h5please add it to init.sh
Provide a patch for your device.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2016-06-06 03:31:29 UTC
Permalink
2.sh, it just needs to be edited.
# /system/bin/sh!
rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5

圚 2016幎6月6日星期䞀 UTC+8䞊午11:21:22youling 257写道
Post by youling 257
Do not understand the meaning of your English
If compile the source code to get ISO, must modify the system.img, copy
into the /bin/rtk_hciattach, copy into the /etc/init.d/2.sh, cm13 support
init.d,
2.sh, it just needs to be edited.
# /system/bin/sh!
rtk_hciattach -n -s /dev/ttyS1 115200 rtk_h5
圚 2016幎6月6日星期䞀 UTC+8䞊午10:34:04Chih-Wei Huang写道
Post by youling 257
Post by youling 257
Chih-Wei HuangI see you add CONFIG_RFKILL_GPIO=m to kernel tree
https://sourceforge.net/p/android-x86/kernel/ci/bf3cf2a8dded98d77e4c3ed12c19bedb65c4f955/
Post by youling 257
I tell youneed system/bin/rtk_hciattachplease extract
rtk_hciattach.tar.gz
Please use btattach (fix or modify it if necessary).
Post by youling 257
and add to source need every bootrtk_hciattach -n -s 115200
/dev/ttyS1
Post by youling 257
rtk_h5please add it to init.sh
Provide a patch for your device.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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 post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Loading...