unable to update #82

myliyifei · 2019-03-27T00:59:14Z

按照之前复杂的方法（多步破解，而不是现在的刷两个pkg包）破解之后，可以root，带adb和mass storage，可以安装apk。

但是现在无法在刷入其他任何pkg, 比如支持蓝牙的pkg，也包括basic pkg ， no mass storage pkg等

刷任何pkg, 自动重启之后都是提示 unable to update error code 900001 实际上也应该没有起效。

按照之前一个issue的提示，刷了5遍以上也没用。

py连接ip，用private key和不用，都试过。

HappyZ · 2019-03-27T03:06:33Z

hmmm what makes you think it didn't work? If you go into diagnosis mode, cat the files under /root/updater_<timestamp>.log. it should tell you what happened to each pkg Can you paste the latest one here?

…

On Tue, Mar 26, 2019, 20:59 myliyifei ***@***.***> wrote: 按照之前复杂的方法（多步破解，而不是现在的刷两个pkg包）破解之后，可以root，带adb和mass storage，可以安装apk。但是现在无法在刷入其他任何pkg, 比如支持蓝牙的pkg，也包括basic pkg ， no mass storage pkg等刷任何pkg, 自动重启之后都是提示 unable to update error code 900001 实际上也应该没有起效。按照之前一个issue的提示，刷了5遍以上也没用。 py连接ip，用private key和不用，都试过。 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#82>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEdSKgunTibQR3_M05YBw2oIBPnEyoyxks5vasJigaJpZM4cMvNu> .

myliyifei · 2019-03-27T14:32:08Z

挑选出来了两段日志，看起来是刷成功了，但是现在插入usb，还是有mass storage，打开蓝牙，还是搜索不到我的Logitech craft，我的手机可以搜索到这个键盘的蓝牙模式。

[anim] displaying /tmp/FwUpdater/images/status01.bmp
[anim] displaying /tmp/FwUpdater/images/status02.bmp
[updater.sh] writing boot.img..
BLK08=59b13192d3972fa17046aeb9a0b9b42c
BOOT=59b13192d3972fa17046aeb9a0b9b42c
Verify OK
[updater.sh] verify check OK
[anim] displaying /tmp/FwUpdater/images/status03.bmp
[anim] displaying /tmp/FwUpdater/images/status04.bmp

[anim] displaying /tmp/FwUpdater/images/status01.bmp
[anim] displaying /tmp/FwUpdater/images/status02.bmp
[updater.sh] run gethid.sh
[gethid.sh] system partition mounted
[gethid.sh] stock bluetooth files already exist..
[gethid.sh] copying new bluetooth files..
[gethid.sh] copy from /tmp/FwUpdater/bluetooth/Bluetooth.apk to /tmp/FwUpdater/systmp/app/Bluetooth/Bluetooth.apk w. perm 0.0 0644
[gethid.sh] set perm 0.0 0644 for /tmp/FwUpdater/systmp/app/Bluetooth/Bluetooth.apk
[gethid.sh] copy from /tmp/FwUpdater/bluetooth/Bluetooth.odex to /tmp/FwUpdater/systmp/app/Bluetooth/arm/Bluetooth.odex w. perm 0.0 0644
[gethid.sh] set perm 0.0 0644 for /tmp/FwUpdater/systmp/app/Bluetooth/arm/Bluetooth.odex
[gethid.sh] un-mount the system partition
[anim] displaying /tmp/FwUpdater/images/status03.bmp
[anim] displaying /tmp/FwUpdater/images/status04.bmp

myliyifei · 2019-03-27T14:45:42Z

我是进入到android的系统设置-蓝牙里面去（adb shell am start -a android.settings.SETTINGS）

可以发现我的mix手机，但是找不到蓝牙键盘。

HappyZ · 2019-03-27T15:33:47Z

can you use adb and go into the /system/app/Bluetooth/ and see if there are Bluetooth.apk as well as Bluetooth.apk_bak. If so, it should be succeeded.

If you flashed the one without mass storage, but yet somehow you reboot and still have mass_storage, something is wrong. What's the result when you run adb shell getprop | grep persist.sys.usb.config?

myliyifei · 2019-03-27T16:27:10Z

我刷的是这个commit里面这个目录下面的
dpt-tools/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img_no_mass_storage

commit f8410b6 (HEAD -> master, origin/master, origin/HEAD)
Author: HappyZ zhuyanzi@gmail.com
Date: Sat Mar 23 11:35:26 2019 -0500

add a boot img mod without mass storage

这是结果
adb shell getprop | grep persist.sys.usb.config
[persist.sys.usb.config]: [acm,hid,adb,mass_storage]

关于蓝牙
root@FPX-1010:/system/app/Bluetooth # ll
-rw-r--r-- root root 35673 2019-03-27 01:16 Bluetooth.apk
-rw-r--r-- root root 57102 2018-04-10 18:26 Bluetooth.apk_bak

可以看到备份文件，但是试过两个蓝牙键盘不同品牌的，手机都可以发现该键盘，但是RP1不可以。

myliyifei · 2019-03-30T13:33:26Z

happyz老师请指导一下

yefeiyu · 2019-03-31T14:38:56Z

挑选出来了两段日志，看起来是刷成功了，但是现在插入usb，还是有mass storage，打开蓝牙，还是搜索不到我的Logitech craft，我的手机可以搜索到这个键盘的蓝牙模式。

[anim] displaying /tmp/FwUpdater/images/status01.bmp
[anim] displaying /tmp/FwUpdater/images/status02.bmp
[updater.sh] writing boot.img..
BLK08=59b13192d3972fa17046aeb9a0b9b42c
BOOT=59b13192d3972fa17046aeb9a0b9b42c
Verify OK
[updater.sh] verify check OK
[anim] displaying /tmp/FwUpdater/images/status03.bmp
[anim] displaying /tmp/FwUpdater/images/status04.bmp

[anim] displaying /tmp/FwUpdater/images/status01.bmp
[anim] displaying /tmp/FwUpdater/images/status02.bmp
[updater.sh] run gethid.sh
[gethid.sh] system partition mounted
[gethid.sh] stock bluetooth files already exist..
[gethid.sh] copying new bluetooth files..
[gethid.sh] copy from /tmp/FwUpdater/bluetooth/Bluetooth.apk to /tmp/FwUpdater/systmp/app/Bluetooth/Bluetooth.apk w. perm 0.0 0644
[gethid.sh] set perm 0.0 0644 for /tmp/FwUpdater/systmp/app/Bluetooth/Bluetooth.apk
[gethid.sh] copy from /tmp/FwUpdater/bluetooth/Bluetooth.odex to /tmp/FwUpdater/systmp/app/Bluetooth/arm/Bluetooth.odex w. perm 0.0 0644
[gethid.sh] set perm 0.0 0644 for /tmp/FwUpdater/systmp/app/Bluetooth/arm/Bluetooth.odex
[gethid.sh] un-mount the system partition
[anim] displaying /tmp/FwUpdater/images/status03.bmp
[anim] displaying /tmp/FwUpdater/images/status04.bmp
您是在哪里找到这个log文件的？我无论如何打不到它。

myliyifei · 2019-03-31T14:39:59Z

挑选出来了两段日志，看起来是刷成功了，但是现在插入usb，还是有mass storage，打开蓝牙，还是搜索不到我的Logitech craft，我的手机可以搜索到这个键盘的蓝牙模式。
[anim] displaying /tmp/FwUpdater/images/status01.bmp
[anim] displaying /tmp/FwUpdater/images/status02.bmp
[updater.sh] writing boot.img..
BLK08=59b13192d3972fa17046aeb9a0b9b42c
BOOT=59b13192d3972fa17046aeb9a0b9b42c
Verify OK
[updater.sh] verify check OK
[anim] displaying /tmp/FwUpdater/images/status03.bmp
[anim] displaying /tmp/FwUpdater/images/status04.bmp
[anim] displaying /tmp/FwUpdater/images/status01.bmp
[anim] displaying /tmp/FwUpdater/images/status02.bmp
[updater.sh] run gethid.sh
[gethid.sh] system partition mounted
[gethid.sh] stock bluetooth files already exist..
[gethid.sh] copying new bluetooth files..
[gethid.sh] copy from /tmp/FwUpdater/bluetooth/Bluetooth.apk to /tmp/FwUpdater/systmp/app/Bluetooth/Bluetooth.apk w. perm 0.0 0644
[gethid.sh] set perm 0.0 0644 for /tmp/FwUpdater/systmp/app/Bluetooth/Bluetooth.apk
[gethid.sh] copy from /tmp/FwUpdater/bluetooth/Bluetooth.odex to /tmp/FwUpdater/systmp/app/Bluetooth/arm/Bluetooth.odex w. perm 0.0 0644
[gethid.sh] set perm 0.0 0644 for /tmp/FwUpdater/systmp/app/Bluetooth/arm/Bluetooth.odex
[gethid.sh] un-mount the system partition
[anim] displaying /tmp/FwUpdater/images/status03.bmp
[anim] displaying /tmp/FwUpdater/images/status04.bmp
您是在哪里找到这个log文件的？我无论如何打不到它。

要进入这个模式 diagnosis mode

yefeiyu · 2019-03-31T14:44:54Z

    `patch-updater-bash`-- patch the updater bash to bypass sig validation
    `push-file`         -- transfer file to DPT at 800bps (=100Bps)
    `pull-file`         -- transfer file from DPT
    `backup-bootimg`    -- backup the boot img and download it to local device
    `restore-bootimg`   -- restore the boot img (use `boot.img.bak`)
    `restore-systemimg` -- restore the system img (use `system.img`)
    `get-su-bin`        -- enable `su` (root) in adb
    `exit`/`quit`       -- leave the tool
    and many unix cmds (do not support less/head)

how should I do?

yefeiyu · 2019-03-31T14:45:43Z

I found these:

boot.img.bak            updater_1551789725.log  updater_1551861912.log
updater_1551789191.log  updater_1551789904.log
updater_1551789394.log  updater_1551859431.log

HappyZ · 2019-03-31T14:56:16Z

mass storage isn't disabled may be it's cached? I'm not very clear what went wrong for now. When you enable Bluetooth, and try to connect with your keyboard, what does it say in adb logcat?

…

On Wed, Mar 27, 2019, 12:27 myliyifei ***@***.***> wrote: 我刷的是这个commit里面这个目录下面的 dpt-tools/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img_no_mass_storage ------------------------------ commit f8410b6 <f8410b6> (HEAD -> master, origin/master, origin/HEAD) Author: HappyZ ***@***.*** Date: Sat Mar 23 11:35:26 2019 -0500 add a boot img mod without mass storage -------------------------这是结果 adb shell getprop | grep persist.sys.usb.config [persist.sys.usb.config]: [acm,hid,adb,mass_storage] -----------------关于蓝牙 ***@***.***:/system/app/Bluetooth # ll -rw-r--r-- root root 35673 2019-03-27 01:16 Bluetooth.apk -rw-r--r-- root root 57102 2018-04-10 18:26 Bluetooth.apk_bak 可以看到备份文件，那么就是不支持我这个蓝牙键盘了吗？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEdSKvJV8rMsvSHmd6Vh1UIAZWdxmUXBks5va5vfgaJpZM4cMvNu> .

yefeiyu · 2019-03-31T15:00:07Z

mass storage should be disable? Which step can do this?
How should I do the adb logcat?

yefeiyu · 2019-03-31T15:01:09Z

In updater_1551859431.log

  2 [anim] displaying /tmp/FwUpdater/images/status01.bmp
  3 [anim] displaying /tmp/FwUpdater/images/status02.bmp
  4 [updater.sh] run gethid.sh
  5 [gethid.sh] system partition mounted
  6 [gethid.sh] backing up stock bluetooth files
  7 [gethid.sh] copying new bluetooth files..
  8 [gethid.sh] copy from /tmp/FwUpdater/bluetooth/Bluetooth.apk to /tmp/FwUpdater/systmp/app/Bluetooth/Bluetooth.    apk w. perm 0.0 0644
  9 [gethid.sh] set perm 0.0 0644 for /tmp/FwUpdater/systmp/app/Bluetooth/Bluetooth.apk
 10 [gethid.sh] copy from /tmp/FwUpdater/bluetooth/Bluetooth.odex to /tmp/FwUpdater/systmp/app/Bluetooth/arm/Bluet    ooth.odex w. perm 0.0 0644
 11 [gethid.sh] set perm 0.0 0644 for /tmp/FwUpdater/systmp/app/Bluetooth/arm/Bluetooth.odex
 12 [gethid.sh] un-mount the system partition
 13 [anim] displaying /tmp/FwUpdater/images/status03.bmp
 14 [anim] displaying /tmp/FwUpdater/images/status04.bmp
~

yefeiyu · 2019-03-31T16:04:43Z

Terminal Saved Output.txt

yefeiyu · 2019-03-31T16:07:25Z

When I enable Bluetooth, and try to connect withmy keyboard, the result is above after I used the command of adb logcat.

myliyifei · 2019-03-31T16:19:41Z

mass storage isn't disabled may be it's cached? I'm not very clear what went wrong for now. When you enable Bluetooth, and try to connect with your keyboard, what does it say in adb logcat?
…
On Wed, Mar 27, 2019, 12:27 myliyifei @.> wrote: 我刷的是这个commit里面这个目录下面的 dpt-tools/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img_no_mass_storage ------------------------------ commit f8410b6 <f8410b6> (HEAD -> master, origin/master, origin/HEAD) Author: HappyZ @. Date: Sat Mar 23 11:35:26 2019 -0500 add a boot img mod without mass storage -------------------------这是结果 adb shell getprop | grep persist.sys.usb.config [persist.sys.usb.config]: [acm,hid,adb,mass_storage] -----------------关于蓝牙 root@FPX-1010:/system/app/Bluetooth # ll -rw-r--r-- root root 35673 2019-03-27 01:16 Bluetooth.apk -rw-r--r-- root root 57102 2018-04-10 18:26 Bluetooth.apk_bak 可以看到备份文件，那么就是不支持我这个蓝牙键盘了吗？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKvJV8rMsvSHmd6Vh1UIAZWdxmUXBks5va5vfgaJpZM4cMvNu .

1 这个cache是哪种cache，按照这个结果
这是结果
adb shell getprop | grep persist.sys.usb.config
[persist.sys.usb.config]: [acm,hid,adb,mass_storage]

看起来mass_storage 没有被关闭啊？我想关闭的目的是为了释放出这个空间。

2 Bluetooth里面无法搜索到蓝牙键盘，更不用谈连接了。应该怎么排除错误呢？

myliyifei · 2019-03-31T16:26:52Z

这个是LOGCAT的日志，开启蓝牙开关的时候，蓝牙驱动是对的吗？看起来好像还是原来的DPT。

D/marvellWirelessDaemon( 1788): insmod:/lib/modules/mbt8897.ko,args , size 116356, ret: 0
E/marvellWirelessDaemon( 1788): File name: /dev/mbtchar0
E/marvellWirelessDaemon( 1788): Permissions:rw-rw-rw-
E/marvellWirelessDaemon( 1788): User-id: 1000,Group-id: 3008
I/marvellWirelessDaemon( 1788): version=SD8897-15.28.18.p1-C3X14113-(FP28)
I/marvellWirelessDaemon( 1788): drvdbg=0x7
I/marvellWirelessDaemon( 1788): Received signal 17.
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L109): bluetooth_enable, ret: 0x0
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 3
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L154): open /dev/mbtchar0 successfully
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 1
D/bt_userial( 4808): Entering userial_read_thread()

I/bt-btu ( 4808): btu_task received preload complete event
I/marvellWirelessDaemon( 1788): Wrote 0,OK to client.
I/ ( 4808): BTE_InitTraceLevels -- TRC_HCI
I/ ( 4808): BTE_InitTraceLevels -- TRC_L2CAP
I/ ( 4808): BTE_InitTraceLevels -- TRC_RFCOMM
I/ ( 4808): BTE_InitTraceLevels -- TRC_AVDT
I/ ( 4808): BTE_InitTraceLevels -- TRC_AVRC
I/ ( 4808): BTE_InitTraceLevels -- TRC_A2D
I/ ( 4808): BTE_InitTraceLevels -- TRC_BNEP
I/ ( 4808): BTE_InitTraceLevels -- TRC_BTM
I/ ( 4808): BTE_InitTraceLevels -- TRC_GAP
I/ ( 4808): BTE_InitTraceLevels -- TRC_PAN
I/ ( 4808): BTE_InitTraceLevels -- TRC_SDP
I/ ( 4808): BTE_InitTraceLevels -- TRC_BTAPP
I/ ( 4808): BTE_InitTraceLevels -- TRC_BTIF
E/bt-btif ( 4808): Calling BTA_HhEnable
E/bt-btif ( 4808): check_cod: remote_cod = 0x5a020c
E/bt-btif ( 4808): check_cod: remote_cod = 0x1a0110
E/bt-btif ( 4808): check_cod: remote_cod = 0x08043c
E/bt-btif ( 4808): check_cod: remote_cod = 0x1a0110
E/bt-btif ( 4808): check_cod: remote_cod = 0x1a0110
E/bt-btif ( 4808): check_cod: remote_cod = 0x08043c
E/bt-btif ( 4808): check_cod: remote_cod = 0x5a020c
E/bt-btif ( 4808): check_cod: remote_cod = 0x5a020c
E/bt-btif ( 4808): check_cod: remote_cod = 0x5a020c
E/bt-btif ( 4808): check_cod: remote_cod = 0x5a020c
E/bt-btif ( 4808): check_cod: remote_cod = 0x5a020c
E/bt-btif ( 4808): check_cod: remote_cod = 0x1a0110
E/bt-btif ( 4808): btif_storage_get_adapter_property service_mask:0x2140040
E/bt-btif ( 4808): btif_storage_get_adapter_property service_mask:0x2140040 - add A2DP Sink UUID..

D/BluetoothAdapterProperties( 4808): Address is:A8:1D:16:03:90:0C
D/BluetoothAdapterProperties( 4808): Name is: DPT-RP1_6207886
D/BluetoothManagerService( 2134): Bluetooth Adapter name changed to DPT-RP1_6207886
D/BluetoothManagerService( 2134): Stored Bluetooth name: DPT-RP1_6207886
D/BluetoothAdapterProperties( 4808): Scan Mode:20
D/BluetoothAdapterProperties( 4808): Discoverable Timeout:120
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 2
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 6
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/bte_conf( 4808): Device ID record 1 : primary
D/bte_conf( 4808): vendorId = 054c
D/bte_conf( 4808): vendorIdSource = 0002
D/bte_conf( 4808): product = 0be5
D/bte_conf( 4808): version = 0100
D/bte_conf( 4808): clientExecutableURL =
D/bte_conf( 4808): serviceDescription =
D/bte_conf( 4808): documentationURL =
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/bte_conf( 4808): bte_load_did_conf no section named DID2.
D/BluetoothAdapterState( 4808): CURRENT_STATE=PENDING, MESSAGE = ENABLE_READY, isTurningOn=true, isTurningOff=false
D/BluetoothAdapterProperties( 4808): ScanMode = 20
D/BluetoothAdapterProperties( 4808): State = 11
D/BluetoothPanServiceJni( 4808): control_state_callback(L61): state:0, local_role:3, ifname:bt-pan
D/BluetoothAdapterProperties( 4808): Setting state to 12
I/BluetoothAdapterState( 4808): Bluetooth adapter state changed: 11-> 12
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
I/BluetoothAdapterState( 4808): Entering On State
D/BluetoothManagerService( 2134): Message: 60
D/BluetoothManagerService( 2134): MESSAGE_BLUETOOTH_STATE_CHANGE: prevState = 11, newState=12
D/BluetoothManagerService( 2134): Broadcasting onBluetoothStateChange(true) to 9 receivers.
D/BluetoothA2dpSink( 4091): onBluetoothStateChange: up=true
D/BluetoothAdapterProperties( 4808): Scan Mode:21
D/BluetoothAdapterProperties( 4808): Discoverable Timeout:120
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/BluetoothPan( 4091): onBluetoothStateChange(on) call bindService
E/bt_h4 ( 4808): vendor lib postload completed
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/BluetoothA2dpSink( 4091): Proxy object connected
D/BT_A2DP_SNK : A2dpSinkProfile( 4091): Bluetooth service connected
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/BluetoothHeadset( 2134): onBluetoothStateChange: up=true
D/BluetoothManagerService( 2134): Creating new ProfileServiceConnections object for profile: 1
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/BluetoothPan( 4091): BluetoothPAN Proxy object connected
D/PanProfile( 4091): Bluetooth service connected
D/BluetoothA2dp( 4091): onBluetoothStateChange: up=true
D/bluedroid-mrvl( 4808): bt_vnd_mrvl_if_op(L88): opcode = 7
D/BluetoothMap( 4091): onBluetoothStateChange: up=true
D/BluetoothA2dp( 4091): Proxy object connected
D/A2dpProfile( 4091): Bluetooth service connected
D/BluetoothInputDevice( 4091): onBluetoothStateChange: up=true
D/BluetoothMap( 4091): Proxy object connected
D/MapProfile( 4091): Bluetooth service connected
D/BluetoothMap( 4091): getConnectedDevices()
D/BluetoothPbap( 4091): onBluetoothStateChange: up=true
D/BluetoothInputDevice( 4091): Proxy object connected
D/HidProfile( 4091): Bluetooth service connected
D/BluetoothA2dp( 2134): onBluetoothStateChange: up=true
D/BluetoothA2dp( 2134): Proxy object connected
D/BluetoothHeadset( 4091): onBluetoothStateChange: up=true
D/BluetoothManagerService( 2134): Bluetooth State Change Intent: 11 -> 12
W/LaunchApplication_BluetoothReceiver( 2759): onReceive:
D/BluetoothMapService( 4808): onReceive
D/BluetoothMapService( 4808): STATE_ON
D/BluetoothMapMasInstance( 4808): Map Service startRfcommSocketListener
W/LocalBluetoothProfileManager( 4091): Warning: HEADSET client profile UUID is missing.
W/SettingManagerService:LocalBluetoothManager( 2134): handleStateChanged 12
D/BluetoothMapMasInstance( 4808): MAS initSocket()
D/BluetoothManagerService( 2134): Message: 30
D/BluetoothAdapterProperties( 4808): Name is: DPT-RP1_6207886
D/BluetoothManagerService( 2134): BluetoothServiceConnection: com.android.bluetooth.gatt.GattService
D/BluetoothManagerService( 2134): checkIfCallerIsForegroundUser: valid=true callingUser=0 parentUser=-10000 foregroundUser=0
D/BluetoothPan( 2134): BluetoothPAN Proxy object connected
W/SettingManagerService:LocalBluetoothManager( 2134): enableBtTethering onServiceConnected
D/BluetoothPan( 2134): setBluetoothTethering(true)
D/BluetoothManagerService( 2134): Message: 40
D/BluetoothManagerService( 2134): MESSAGE_BLUETOOTH_SERVICE_CONNECTED: 2
D/PanService( 4808): setBluetoothTethering: true, mTetherOn: false
W/BluetoothAdapter( 4808): getBluetoothService() called with no BluetoothManagerCallback
D/BluetoothManagerService( 2134): Message: 31
D/BluetoothMapMasInstance( 4808): Accepting socket connection...
D/BluetoothManagerService( 2134): Bluetooth Adapter name changed to DPT-RP1_6207886
D/BluetoothManagerService( 2134): Stored Bluetooth name: DPT-RP1_6207886
W/bt-btif ( 4808): bta_dm_check_av:0

HappyZ · 2019-04-02T21:10:17Z

I'll double check it tonight, hopefully can find something useful

HappyZ · 2019-04-03T05:40:51Z

Your bluetooth log looks fine.. it may be your keyboard uses newer Bluetooth protocols which are not supported by the old DPT bluetooth chip.

and regarding the mass storage issue, I have tried multiple times and switching PKGs with and without mass storage will be immediately effective after I reboot. So honestly Im not sure why yours didn't change afterwards.

Even if you disable mass storage, it will not free up more spaces, as the mass storage mounts a separate partition, not the /data/ partition.

myliyifei · 2019-04-03T13:03:15Z

Your bluetooth log looks fine.. it may be your keyboard uses newer Bluetooth protocols which are not supported by the old DPT bluetooth chip.

and regarding the mass storage issue, I have tried multiple times and switching PKGs with and without mass storage will be immediately effective after I reboot. So honestly Im not sure why yours didn't change afterwards.

Even if you disable mass storage, it will not free up more spaces, as the mass storage mounts a separate partition, not the /data/ partition.

非常感谢您的指导，能否在请问一下 DPT RP1的蓝牙驱动使用的协议是哪种呢？我按什么样的标准可以找到合适的键盘？

HappyZ · 2019-04-03T16:26:48Z

It's just my guess.. it's using Bluetooth 4.2, which supposes to be fairly new, but on the other hand it uses a rather old bluetooth lib.. I didn't test it but maybe if you swap a newer bluetooth lib/firmware it could work fine.

yefeiyu · 2019-04-04T02:18:23Z

Terminal Saved Output.txt

Happyz, Could you look at my documents?:)

HappyZ · 2019-04-04T17:50:35Z

@yefeiyu your output doesnt contain much bluetooth info..

I decompiled the DPT bluetooth app and odex, and it is actually just a standard bluetooth from Android.. except hid etc. were disabled. The .so lib might also be a standard one.

I tend to think Android 5.1 does not support FILCO keyboard.

And @myliyifei you may go to /data/dalvik-cache and remove Bluetooth class dex cache to see if Bluetooth works. Or better, just remove all files under that cache folder, and reboot the device.

After you remove the cache, first flash the bluetooth_recover PKG, and reboot, and flash the bluetooth_hid PKG.

If not working, I would think somehow this is related to the mass_storage issue.. I'm not sure how to solve it yet.

HappyZ · 2019-04-09T20:18:48Z

@myliyifei question: were you using Windows?

myliyifei · 2019-04-10T05:37:10Z

@myliyifei question: were you using Windows?

thank you!
I will try your solution tonight, I have both mac and windows, anything regarding OS?

myliyifei · 2019-04-10T13:53:24Z

should I delete below two files?

root@FPX-1010:/data/dalvik-cache/profiles # ll
-rw-rw---- system all_a46 0 2019-03-27 23:02 cn.modificator.launcher
-rw-rw---- system all_a50 0 2019-04-08 00:04 com.amazon.kindle
-rw-rw---- system all_a1 0 2019-02-14 23:59 com.android.backupconfirm
-rw-rw---- system u0_a31002 0 2019-02-14 23:59 com.android.bluetooth

root@FPX-1010:/data/dalvik-cache/arm # ll|grep Blue
-rw-r--r-- system u0_a31002 2779200 2018-04-10 18:26 system@app@Bluetooth@Bluetooth.apk@classes.dex

myliyifei · 2019-04-10T16:59:58Z

按以上刷蓝牙的两个PKG之后，打开系统蓝牙提示 "bluetooth share has stoped"

检查 /data/dalvik-cache/arm 并没有这样的 Bluetooth.apk@classes.dex 生成

HappyZ · 2019-04-10T17:03:51Z

hmmm 那你adb进系统把systrm/app/bluetooth apk 和odex的bak还原然后重启呢 dex没生成不该啊

…

On Wed, Apr 10, 2019, 12:00 myliyifei ***@***.***> wrote: 按以上刷蓝牙的两个PKG之后，打开系统蓝牙提示 "bluetooth share has stoped" 检查 /data/dalvik-cache/arm 并没有这样的 ***@***.*** 生成 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEdSKpkEZXaaeS_jWe1awR00kNUgVZJoks5vfhiQgaJpZM4cMvNu> .

HappyZ · 2019-04-10T17:13:32Z

刷了recover还是没好的话用adb进普通系统 ``` mount -o rw,remount /system ``` 然后把备份的bluetooth apk bak重命名换回去然后重启 dalvik cache会生成么

…

On Wed, Apr 10, 2019, 12:05 myliyifei ***@***.***> wrote: hmmm 那你adb进系统把systrm/app/bluetooth apk 和odex的bak还原然后重启呢 dex没生成不该啊 … <#m_-8030969552829008654_> On Wed, Apr 10, 2019, 12:00 myliyifei *@*.*> wrote: 按以上刷蓝牙的两个PKG之后，打开系统蓝牙提示 "bluetooth share has stoped" 检查 /data/dalvik-cache/arm 并没有这样的 @.* 生成 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment) <#82 (comment)>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKpkEZXaaeS_jWe1awR00kNUgVZJoks5vfhiQgaJpZM4cMvNu . 我现在刷了bluetooth_recover PKG，（4.11）的包 MAC下面刷的。您说的是还原是如何还原呢？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEdSKp_QZJrAWekCTqLyKJ1-_qSsgGk_ks5vfhnrgaJpZM4cMvNu> .

myliyifei · 2019-04-10T17:23:51Z

刷了recover还是没好的话用adb进普通系统 mount -o rw,remount /system 然后把备份的bluetooth apk bak重命名换回去然后重启 dalvik cache会生成么
…
On Wed, Apr 10, 2019, 12:05 myliyifei @.*> wrote: hmmm 那你adb进系统把systrm/app/bluetooth apk 和odex的bak还原然后重启呢 dex没生成不该啊 … <#m_-8030969552829008654_> On Wed, Apr 10, 2019, 12:00 myliyifei @.> wrote: 按以上刷蓝牙的两个PKG之后，打开系统蓝牙提示 "bluetooth share has stoped" 检查 /data/dalvik-cache/arm 并没有这样的 @. 生成 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment) <#82 (comment)>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKpkEZXaaeS_jWe1awR00kNUgVZJoks5vfhiQgaJpZM4cMvNu . 我现在刷了bluetooth_recover PKG，（4.11）的包 MAC下面刷的。您说的是还原是如何还原呢？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKp_QZJrAWekCTqLyKJ1-_qSsgGk_ks5vfhnrgaJpZM4cMvNu .

把旧的备份恢复之后，classes.dex生成成功了。

HappyZ · 2019-04-10T17:30:35Z

OK 然后再刷一次hid 的pkg呢

…

On Wed, Apr 10, 2019, 12:23 myliyifei ***@***.***> wrote: 刷了recover还是没好的话用adb进普通系统 mount -o rw,remount /system 然后把备份的bluetooth apk bak重命名换回去然后重启 dalvik cache会生成么 … <#m_-6585408393226438954_> On Wed, Apr 10, 2019, 12:05 myliyifei *@*.**> wrote: hmmm 那你adb进系统把systrm/app/bluetooth apk 和odex的bak还原然后重启呢 dex没生成不该啊 … <#m_-8030969552829008654_> On Wed, Apr 10, 2019, 12:00 myliyifei @.> wrote: 按以上刷蓝牙的两个PKG之后，打开系统蓝牙提示 "bluetooth share has stoped" 检查 /data/dalvik-cache/arm 并没有这样的 @.* 生成 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 <#82> (comment) <#82 (comment) <#82 (comment)>>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKpkEZXaaeS_jWe1awR00kNUgVZJoks5vfhiQgaJpZM4cMvNu . 我现在刷了bluetooth_recover PKG，（4.11）的包 MAC下面刷的。您说的是还原是如何还原呢？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment) <#82 (comment)>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKp_QZJrAWekCTqLyKJ1-_qSsgGk_ks5vfhnrgaJpZM4cMvNu . 把旧的备份恢复之后，classes.dex生成成功了。 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEdSKo1aLP0oVWERCikHHe8p6MjYxy1eks5vfh4ngaJpZM4cMvNu> .

myliyifei · 2019-04-10T17:31:41Z

刷之前，是否删除system@app@Bluetooth@Bluetooth.apk@classes.dex呢？

HappyZ · 2019-04-10T17:33:40Z

不删

…

On Wed, Apr 10, 2019, 12:31 myliyifei ***@***.***> wrote: OK 然后再刷一次hid 的pkg呢 … <#m_-8475927056440106662_> On Wed, Apr 10, 2019, 12:23 myliyifei *@*.*> wrote: 刷了recover还是没好的话用adb进普通系统 mount -o rw,remount /system 然后把备份的bluetooth apk bak重命名换回去然后重启 dalvik cache会生成么 … <#m_-6585408393226438954_> On Wed, Apr 10, 2019, 12:05 myliyifei @.> wrote: hmmm 那你adb进系统把systrm/app/bluetooth apk 和odex的bak还原然后重启呢 dex没生成不该啊 … <#m_-8030969552829008654_> On Wed, Apr 10, 2019, 12:00 myliyifei @.> wrote: 按以上刷蓝牙的两个PKG之后，打开系统蓝牙提示 "bluetooth share has stoped" 检查 /data/dalvik-cache/arm 并没有这样的 @.* 生成 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 <#82> <#82 <#82>> (comment) <#82 <#82> (comment) <#82 (comment) <#82 (comment)>>>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKpkEZXaaeS_jWe1awR00kNUgVZJoks5vfhiQgaJpZM4cMvNu . 我现在刷了bluetooth_recover PKG，（4.11）的包 MAC下面刷的。您说的是还原是如何还原呢？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 <#82> (comment) <#82 (comment) <#82 (comment)>>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKp_QZJrAWekCTqLyKJ1-_qSsgGk_ks5vfhnrgaJpZM4cMvNu . 把旧的备份恢复之后，classes.dex生成成功了。 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment) <#82 (comment)>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKo1aLP0oVWERCikHHe8p6MjYxy1eks5vfh4ngaJpZM4cMvNu . ***@***.***@***@***.***@classes.dex呢？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEdSKsIksj4IZb37fQirXabXFzMv6PbKks5vfh_-gaJpZM4cMvNu> .

myliyifei · 2019-04-10T17:38:54Z

这次刷完之后，开启蓝牙不报错，但是依旧找不到HID。我如何通过日志或者其他途径判断Bluetooth.APK对HID的当前设置呢？

系统固件版本是 1.4.01.16100

HappyZ · 2019-04-10T17:40:08Z

所以你是连搜索都搜索不到而不是没法connect？

…

On Wed, Apr 10, 2019, 12:38 myliyifei ***@***.***> wrote: 不删 … <#m_7655679980758422521_> On Wed, Apr 10, 2019, 12:31 myliyifei *@*.*> wrote: OK 然后再刷一次hid 的pkg呢 … <#m_-8475927056440106662_> On Wed, Apr 10, 2019, 12:23 myliyifei @.> wrote: 刷了recover还是没好的话用adb进普通系统 mount -o rw,remount /system 然后把备份的bluetooth apk bak重命名换回去然后重启 dalvik cache会生成么 … <#m_-6585408393226438954_> On Wed, Apr 10, 2019, 12:05 myliyifei @.> wrote: hmmm 那你adb进系统把systrm/app/bluetooth apk 和odex的bak还原然后重启呢 dex没生成不该啊 … <#m_-8030969552829008654_> On Wed, Apr 10, 2019, 12:00 myliyifei @.> wrote: 按以上刷蓝牙的两个PKG之后，打开系统蓝牙提示 "bluetooth share has stoped" 检查 /data/dalvik-cache/arm 并没有这样的 @. 生成 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 <#82> <#82 <#82>> <#82 <#82> <#82 <#82>>> (comment) <#82 <#82> <#82 <#82>> (comment) <#82 <#82> (comment) <#82 (comment) <#82 (comment)>>>>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKpkEZXaaeS_jWe1awR00kNUgVZJoks5vfhiQgaJpZM4cMvNu <https://github.com/notifications/unsubscribe-auth/AEdSKpkEZXaaeS_jWe1awR00kNUgVZJoks5vfhiQgaJpZM4cMvNu> . 我现在刷了bluetooth_recover PKG，（4.11）的包 MAC下面刷的。您说的是还原是如何还原呢？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 <#82> <#82 <#82>> (comment) <#82 <#82> (comment) <#82 (comment) <#82 (comment)>>>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKp_QZJrAWekCTqLyKJ1-_qSsgGk_ks5vfhnrgaJpZM4cMvNu <https://github.com/notifications/unsubscribe-auth/AEdSKp_QZJrAWekCTqLyKJ1-_qSsgGk_ks5vfhnrgaJpZM4cMvNu> . 把旧的备份恢复之后，classes.dex生成成功了。 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 <#82> (comment) <#82 (comment) <#82 (comment)>>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKo1aLP0oVWERCikHHe8p6MjYxy1eks5vfh4ngaJpZM4cMvNu <https://github.com/notifications/unsubscribe-auth/AEdSKo1aLP0oVWERCikHHe8p6MjYxy1eks5vfh4ngaJpZM4cMvNu> . @.***@***.*** <https://github.com/BlueTooth>@**@***.***呢？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment) <#82 (comment)>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdSKsIksj4IZb37fQirXabXFzMv6PbKks5vfh_-gaJpZM4cMvNu . 这次刷完之后，开启蓝牙不报错，但是依旧找不到HID。我如何通过日志或者其他途径判断Bluetooth.APK对HID的当前设置呢？系统固件版本是 1.4.01.16100 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEdSKtsnn4yxpaYyueuGtum-WrLIrROJks5vfiGvgaJpZM4cMvNu> .

myliyifei · 2019-04-10T17:49:04Z

是的，我是没有办法搜索到键盘，试过两个键盘都不可以。刚测试了老手机 nexus5 ，Android 6.0.1 蓝牙选项中也可以发现我现在的键盘。

HappyZ · 2019-04-10T20:52:27Z

ic.. 我这个hid只是enable了如果你搜到但是连不上你搜都搜不到这。。。我想想

HappyZ · 2019-04-10T21:56:03Z

如果你安装一个bluetooth的软件比如 Bluetooth Pair 能搜到么

yefeiyu · 2019-04-11T14:50:38Z

更改您为rp1制作的蓝牙版本怎么样

yefeiyu · 2019-04-11T14:50:39Z

更改您为rp1制作的蓝牙版本怎么样

yefeiyu · 2019-04-11T14:51:38Z

譬如，升级成更高的安卓系统版本的蓝牙

HappyZ · 2019-04-11T18:01:55Z

譬如，升级成更高的安卓系统版本的蓝牙

我没有制作过新的版本我只是enable了原来apk里面disable了的hid连接

所以如果本来机子里的就是阉割版本的那么很有可能需要重新写firmware 非常小可能你直接换一个原来android上编译好的bluetooth module你就能升级

myliyifei · 2019-04-11T18:08:07Z

Bluetooth Pair

测试了，还是搜索不到。

HappyZ · 2019-04-12T19:03:12Z

能麻烦你去#66 写一下什么键盘型号搜不到么

那你搜别的比如你的手机可以搜索的到吗

myliyifei · 2019-04-13T20:08:59Z

能麻烦你去#66 写一下什么键盘型号搜不到么

那你搜别的比如你的手机可以搜索的到吗

已经补充。

我的手机MIX2S （Android 8）和 nexus 5（Android 6）均可以搜索到该键盘，
RP1也可以搜索到我的手机，但是不能搜索到该键盘。

HappyZ · 2019-04-17T21:10:53Z

这个我就无能为力了。。说明bluetooth本身是工作的但是就是一些特定的键盘连不上感觉跟特定的protocol有关系也就是说很有可能dpt的firmware并没有支持这样的protocol

虽然我并不是很recommend 但是你可以试试把working phone里的bluetooth module拿出来（同一个系统版本）然后放到dpt里看看能不能work

myliyifei · 2019-04-23T09:03:50Z

好的，我先关闭这个issue，有新的发现再分享。

myliyifei · 2019-06-05T01:55:48Z

买了一个新的罗技K380键盘，机器升级到1.6版本，然后也刷了蓝牙HID的包，现在可以使用上键盘了。
如果1.6固件对蓝牙没有任何更新的化，那就是rp1只支持低版本的蓝牙（估计是3.0以下的）

myliyifei closed this as completed Apr 23, 2019

unable to update #82

unable to update #82

Comments

myliyifei commented Mar 27, 2019

HappyZ commented Mar 27, 2019 via email

myliyifei commented Mar 27, 2019

myliyifei commented Mar 27, 2019

HappyZ commented Mar 27, 2019

myliyifei commented Mar 27, 2019 • edited Loading

myliyifei commented Mar 30, 2019

yefeiyu commented Mar 31, 2019

myliyifei commented Mar 31, 2019

yefeiyu commented Mar 31, 2019

yefeiyu commented Mar 31, 2019

HappyZ commented Mar 31, 2019 via email

yefeiyu commented Mar 31, 2019

yefeiyu commented Mar 31, 2019

yefeiyu commented Mar 31, 2019

yefeiyu commented Mar 31, 2019

myliyifei commented Mar 31, 2019

myliyifei commented Mar 31, 2019 • edited Loading

HappyZ commented Apr 2, 2019

HappyZ commented Apr 3, 2019 • edited Loading

myliyifei commented Apr 3, 2019

HappyZ commented Apr 3, 2019

yefeiyu commented Apr 4, 2019

HappyZ commented Apr 4, 2019 • edited Loading

HappyZ commented Apr 9, 2019

myliyifei commented Apr 10, 2019

myliyifei commented Apr 10, 2019 • edited Loading

should I delete below two files?

myliyifei commented Apr 10, 2019

HappyZ commented Apr 10, 2019 via email

HappyZ commented Apr 10, 2019 via email

myliyifei commented Apr 10, 2019

HappyZ commented Apr 10, 2019 via email

myliyifei commented Apr 10, 2019 • edited Loading

HappyZ commented Apr 10, 2019 via email

myliyifei commented Apr 10, 2019 • edited Loading

HappyZ commented Apr 10, 2019 via email

myliyifei commented Apr 10, 2019 • edited Loading

HappyZ commented Apr 10, 2019

HappyZ commented Apr 10, 2019

yefeiyu commented Apr 11, 2019

yefeiyu commented Apr 11, 2019

yefeiyu commented Apr 11, 2019

HappyZ commented Apr 11, 2019

myliyifei commented Apr 11, 2019

HappyZ commented Apr 12, 2019 • edited Loading

myliyifei commented Apr 13, 2019

HappyZ commented Apr 17, 2019

myliyifei commented Apr 23, 2019

myliyifei commented Jun 5, 2019

myliyifei commented Mar 27, 2019 •

edited

Loading

myliyifei commented Mar 31, 2019 •

edited

Loading

HappyZ commented Apr 3, 2019 •

edited

Loading

HappyZ commented Apr 4, 2019 •

edited

Loading

myliyifei commented Apr 10, 2019 •

edited

Loading

myliyifei commented Apr 10, 2019 •

edited

Loading

myliyifei commented Apr 10, 2019 •

edited

Loading

myliyifei commented Apr 10, 2019 •

edited

Loading

HappyZ commented Apr 12, 2019 •

edited

Loading