Tracking Android support about react-native-ble

[Shakarang]

@TrySpace I'm building the Android support on my fork of the repo. I've continued iOS development to read characteristics valued and it will be the same for Android

[jacobrosenthal]

not from me

[NishanthShankar]

You can have a look at https://github.com/axemclion/react-native-cordova-plugin to integrate cordova pugins with react-native android

[niftylettuce]

+1

[niftylettuce]

@NishanthShankar Do you know how to get it to work with RN 0.18+? See axemclion/react-native-cordova-plugin#14 when I try to use it in combination with https://github.com/randdusing/cordova-plugin-bluetoothle

[rclai]

@Shakarang, would you like to collaborate together to get our changes to this repo? I noticed you've done a lot on the Android side. I've dealt mostly on the iOS side and was able to remove a lot of the noble code and just directly depend on the noble library.

[Shakarang]

@rclai I'll be really pleased to collaborate with you. Where did you code it? I can't find it in any branch..

[rclai]

It's here https://github.com/Profab/react-native-ble/tree/updates

[jacobrosenthal]

@Shakarang let us know if you get something that can be PR'ed

[Shakarang]

@jacobrosenthal Yep but currently I have no time with my work and school..

[rclai]

@Shakarang would you mind if I pick up from where you left off with the Android implementation?

[Shakarang]

@rclai Hey ! You can do it if you want. I will work on it on Saturday morning too.

[Shakarang]

@rclai Can you contact me on my email address please? It will be easier to exchange together.
It's [email protected]

[rclai]

Sure. I've been pretty busy lately so I don't know how much time I'll have to work on this, I'll let you know.

[jacobrosenthal]

Can you guys check out @Shakarang's PR?
#11

[eriihine]

There's also following fork of react-native-ble for Android:

• https://github.com/eriihine/react-native-ble/tree/android

Most of the functionality is there (although not all) and it is still work in progress.

This one uses the newer Android BLE API (API level 21 and up only). It also uses ScanRecord to parse scan result in more detail (e.g. includes manufacturerData, advertisement service data and characteristic properties on characteristic discovery). I have tried to keep the API as close noblejs as possible

Just thought to mention this as well, in case someone is looking for API level 21 based solution. Would have pitch in here earlier, but noticed this thread just now.

edit: There's also support for Android lifecycle events (onPause/onDestroy). Although this might still require more work. Currently BLE connection disconnected automatically on pause.

[eriihine]

I probably will be working on the above android fork still on June and in August (bug fixes and remaining missing features). The target is to have it more or less ready at the end of august.

Would be happy to contribute this as well if needed.

[jacobrosenthal]

@eriihine Thanks for posting, Ill check yours out as well when I get a chance.

[jacobrosenthal]

Any android people want to check these out. We have 2 competing options apparently

• @eriihine https://github.com/eriihine/react-native-ble/tree/android
• @Shakarang #11

Can we turn them into separate bindings and load the appropriate one based on a version check?

[ferologics]

@jacobrosenthal isn't https://github.com/eriihine/react-native-ble/tree/combined the latest version? I'm thinking of testing it

[jacobrosenthal]

@eriihine could clarify

[eriihine]

@ferologics You should checkout the android branch:
https://github.com/eriihine/react-native-ble/tree/android

The combined branch contains one minor tweak for iOS + android changes (ble.write event is sent out when writing to characteristic using withoutResponse parameter i.e. no response is needed from BLE but the event is send out in immediately after the write request has been processed). The iOS change is not needed necessarily.

The android branch contains only android specific changes.

[Shakarang]

@jacobrosenthal ?

[jacobrosenthal]

I presume your question is, have I looked at your fork yet? I havent and I havent got reports back from anyone else here either sadly. Have you looked at @eriihine's?

Ive got a nex5 here though in preparation but mainly Im working with @sandeepmistry to build tests around bindings layers so I can verify functionality (especially since Im not an android or java guy)

[Shakarang]

@jacobrosenthal Yes it was it, sorry.

I've looked @eriihine's branch and it seems better than mine. I'm not specialised in Android so I may have some issues.

Do you think it will be available in the next weeks?

[jacobrosenthal]

Do I understand that you would prefer his merged over yours? Is there some features or anything about your branch that should be kept?

[franrios]

Is android support available yet?

[jacobrosenthal]

In the forks seen here. We need testers.

On Thu, Sep 8, 2016 at 12:57 PM, Fran [email protected] wrote:

Is android support available yet?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#3 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAb0dIPbYd5TU2EbSK8LlNMCxNuDxE06ks5qoD5pgaJpZM4GDwOm
.

[jacobrosenthal]

I merged @eriihine's work for now as 1.0.7 and have a very simple example 'working' called advertisement_discovery. Im sure there are outstanding issues though, so please do try it.