Archive for the android Category

Note: GATT service with Bluetooth Low Energy

Posted in BLE, Bluetooth, Bluetooth Low Engery with tags , on 2018 年 01 月 18 日 by Kun-Yi

傳統的Bluetooth Device 透過 SDP service 使用Profile UUID 去讓兩者相連, 但是BLE則擴充了這個方法, 透過提供 GATT (Generic Attributes) Profile 去取代 SDP的功能,使用GATT Service 內的 Service/Characteristics 功能可以更方便跟分類各種服務跟屬性值, 並且透過GATT 可以自我宣告特定應用的Service與Characteristics 去創建自己的特殊應用 常見有iBeacon/Eddystone Beacon 或是 像是 TI SensorTags 可以參考這個 Andorid Source 去使用Ti 自定義的Barometers service

官方說法 from https://www.bluetooth.com/specifications/profiles-overview
For two Bluetooth devices to be compatible, they must support the same profiles. And while profiles generally describe the same use case behaviors, they are different for Bluetooth BR/EDR and Bluetooth Low Energy (LE) implementations. Compatibility between Bluetooth BR/EDR and Bluetooth LE implementations requires a dual-mode controller on at least one. For BR/EDR, a wide range of adopted Bluetooth profiles describe many different, commonly used types of applications or use cases for devices. For Bluetooth LE, developers can use a comprehensive set of adopted profiles, or they can use Generic Attribute Profile (GATT) to create new profiles. This flexibility helps support innovative new applications that maintain interoperability with other Bluetooth devices.

廣告

Example: Android BLE example to connection Multi-TI SensorTag Device

Posted in android, Bluetooth, Bluetooth Low Engery with tags , on 2017 年 12 月 29 日 by Kun-Yi

The demo app use RxAndroidBle Library to concurrent connection multi Ti SensorTags, suggestion apply on Android 5.0 and later, the code still have more bugs

https://github.com/KunYi/SensorTag2Testing

Note: Modular Kernel

Posted in android, Treble with tags , , on 2017 年 12 月 05 日 by Kun-Yi

官網看來需要把module driver 放到專屬的partitions (vendor/odm) 而且要可驗證的 並且ReadOnly, 而且Google 會強制你必須要用v3.18 (2017年以前出品的SOC 的最低要求), 而之後的SoC 則是不能低於v4.4 這應該是GMS/VTS 強制認證規範才是

然後Module file 不應該在/system 之下

/vendor or /odm 是被建議的Partition 裡面建立起 /lib/modules

然後透過early mount (VBoot v1 or VBoot v2)載入 /vendor and /odm

這幾個規範加起來就感覺到有很多裝置被判死刑

Note: Wifi Country code in AOSP

Posted in android with tags , on 2017 年 11 月 15 日 by Kun-Yi

WIFI Country code follow ISO 3166 defined , see “WIFI_COUNTRY_CODE" in Settings.java
the Country will auto change when USIM insert with Telecom signaling, see “setWifiCountryCodeFromMcc" in MccTable.java

Tips:
MCC mean Mobile Country Code

Note: Tethering provision for Telecom operator config on Android

Posted in android with tags , on 2017 年 11 月 15 日 by Kun-Yi

use jgrep to search the below keywords, will got detail information, just need to change string resource, may to use override method like this

  • config_mobile_hotspot_provision_app
  • config_mobile_hotspot_provision_response
  • config_mobile_hotspot_provision_check_period
  • config_mobile_hotspot_provision_app_no_ui

And you need to check system property “net.tethering.noprovisioning" value

Note: How to make Android O v8.0.0_r4 for Hikey960

Posted in android with tags , on 2017 年 08 月 28 日 by Kun-Yi
  1.  ref .  Using Reference Boards step to download source code, but change branch name to android-8.0.0_r4, like the below
    repo init -u https://android.googlesource.com/platform/manifest -b android-8.0.0_r4
  2.  repo sync -jN (#N for your Host machine, Normally use 8~12, dependency network, SSD/HDD state)
  3. change the below projects to master branch and checkout with special commit hash
    device/linaro/bootloader/OpenPlatfprmPkg — “ca8a8eeb"
    device/linaro/bootloader/arm-trusted-firmware — “d2baddd"
    device/linaro/bootloader/edk2 — “99d893a"
    device/linaro/hikey-kernel — “7517d7dbe"
    device/linaro/hikey — “0ac1c5c5c41
  4. modify device/linaro/hikey/hikey960/BoardConfig.mk
    diff –git a/hikey960/BoardConfig.mk b/hikey960/BoardConfig.mk
    index 00598e7..92321b4 100644
    — a/hikey960/BoardConfig.mk
    +++ b/hikey960/BoardConfig.mk
    @@ -3,8 +3,20 @@ include device/linaro/hikey/BoardConfigCommon.mk
    TARGET_BOOTLOADER_BOARD_NAME := hikey960
    TARGET_BOARD_PLATFORM := hikey960
    -TARGET_CPU_VARIANT := cortex-a73
    -TARGET_2ND_CPU_VARIANT := cortex-a73
    +TARGET_ARCH := arm64
    +TARGET_ARCH_VARIANT := armv8-a
    +TARGET_CPU_ABI := arm64-v8a
    +TARGET_CPU_VARIANT := generic
    +
    +TARGET_2ND_ARCH := arm
    +TARGET_2ND_ARCH_VARIANT := armv7-a-neon
    +TARGET_2ND_CPU_ABI := armeabi-v7a
    +TARGET_2ND_CPU_ABI2 := armeabi
    +TARGET_2ND_CPU_VARIANT := generic
    +
    +#TARGET_CPU_VARIANT := cortex-a73
    +#TARGET_2ND_CPU_VARIANT := cortex-a73
  5. make -jN (dependency your build machine, for me, the value is 8)
  6. waiting build success, then to ref. Using Reference Boards, for update your hikey960 board
  7. enjoy the play

Note: Hikey960 with Android v8.0.0_r1 boot success!

Posted in android with tags , on 2017 年 08 月 25 日 by Kun-Yi

終於把Hikey960 with Android O v8.0.0_r1 弄開機啦!

https://plus.google.com/u/0/photos/115270660462348164673/album/6458121557908343953/6458121562021074946?authkey=CIHysdm7oNflwQE

https://plus.google.com/u/0/photos/115270660462348164673/album/6458121557908343953/6458121565094052034?authkey=CIHysdm7oNflwQE

https://plus.google.com/u/0/photos/115270660462348164673/album/6458121557908343953/6458121562288292002?authkey=CIHysdm7oNflwQE

https://plus.google.com/u/0/photos/115270660462348164673/album/6458121557908343953/6458121565165748434?authkey=CIHysdm7oNflwQE