Related
Hey guys,
I was just thinking about that nasty little problem with cyanogenmod and our legends and since there was no meaningfull advencment, we could put some money on it. I think from 5 to 10€ for each doner would be enough or what do you think? Of course the developer has to give us an account to send the money to.
I would just like to use the FM radio and since it is working on desire for some time now, why not on legend.
So who is ready to do it?
would support that idea.
It is already stated waaaaaaaaaaayyyy before. The FM radio WILL NOT WORK on the Legend because of it's alien architecture. Don't ask me, I don't know ****. But if you're do want to make a donation then you can donate to Ali Ba which has been the sole reason CM is running on the Legend.
This is a good idea.
Sent from my Legend using XDA App
rajasyaitan said:
It is already stated waaaaaaaaaaayyyy before. The FM radio WILL NOT WORK on the Legend because of it's alien architecture. Don't ask me, I don't know ****. But if you're do want to make a donation then you can donate to Ali Ba which has been the sole reason CM is running on the Legend.
Click to expand...
Click to collapse
here on this link http://forum.cyanogenmod.com/topic/8260-fm-radio-support-for-legend/ ale baba himself says it is possible but that he hasn't got the time for it. So it is possible we just need someone who will do it. But first of all we need more people.
I'd consider doing development on this. I was wondering why there was no FM Radio app on CM7, LOL.
At the very least I can commit to finding all the info I can gather on this issue. I have no (satisfactory) employment at present and want to break into the Android specific field.
I have 14 years experience in embedded Linux development, including lots of low level kernel stuff. In a previous life (more decades ago than I dare admit) I did electronics engineering stuff, and I still love the low level nuts and bolts.
I'm pretty new to Android however, got my first cellphone (ever!) 17 days ago, first Android phone 15 days ago, and my Legend yesterday.
I think I can learn quick, I'm CM7 nightly, S-Off, new radio one day after getting it, LOL.
So my point is I, and this project, could use help in areas of Android specific knowledge.
Does anyone know if the normal FM radio app I've used before is proprietary Google code ?
Are there any generic FM radio apps that would work if standard drivers existed ?
My quick research on this is that only a driver might be needed. A V4L (video 4 linux) driver, which I have already had some experience with.
But there DOES seem to be a V4L driver already for Linux for the TI WL1273 chip apparently used in the Legend, and apparently a number of other phones. So in theory, this job might be as easy as integrating an already written driver in to the CM kernel, as a kernel module or 2. There MIGHT be some copyright issues with any chip firmware though.
Alas, some comments indicate using such a driver might interfere with Bluetooth functionality.
Interesting stuff about the 1273 chip is that it may support an FM transmitter, and it supposedly supports WiFi N. But who knows if needed hardware support might not be on the PCBs.
^ wow! where have you been all our android lives, bro? link on the post above yours answers some, if not of all, of your questions & covers a lot, i guess. cheers!
maxq1 said:
^ wow! where have you been all our android lives, bro? link on the post above yours answers some, if not of all, of your questions & covers a lot, i guess. cheers!
Click to expand...
Click to collapse
Cheers...
I've been reading that there IS an FM Radio app integrated into CM now. It comes from MIUI, a chinese group of some sort that also makes an Android ROM.
The app apparently uses /dev/radio* which is the standard V4L radio interface. I have these also on my Hauuppage PVR boards I used for HTPC before I went completely digital for movies, tv, etc.
So yes, what we need is integration of a driver into CM kernel, but coding may be needed to fix bluetooth driver interference etc. And of course who knows what else might be needed.
I'm reading that FM is much more important to those without data to stream. Not all of us live in wireless data dense cities and countries.
Would be interesting to see what frequency range can be received and maybe transmitted.
Would be MOST cool to stream from video camera to transmitter for local "pirate TV" type functionality, LOL. Actually can't imagine ATSC or even NTSC (or PAL etc.) encoding possible, but wireless streaming will do the job...
@mikereidis
Thanks for joining in, great highly appreciated. If there is any time left it would be nice if you could look into the GPS problem with CM 7 it is currently not addressed.
Anyhow thanks for your participation and contribution.
BR, ojessie
@mikereidis
So are you going to try and port it?? If you will and you'll succeded then you will be the legend in Legend community!
Sent from my Legend using XDA App
ojessie said:
@mikereidis
Thanks for joining in, great highly appreciated. If there is any time left it would be nice if you could look into the GPS problem with CM 7 it is currently not addressed.
Anyhow thanks for your participation and contribution.
BR, ojessie
Click to expand...
Click to collapse
I can keep my eyes and ears open to GPS, but best to concentrate on one issue at a time.
What is the GPS issue ? I thought it didn't work on my phone after new ROM but within a few hours it was working OK for whatever reason. And now I see 2 metre accuracy compared to the minimum of 5 on my Optimus Chic.
qzem said:
@mikereidis
So are you going to try and port it??
Click to expand...
Click to collapse
I'll do whatever it takes.
The userspace FM Radio app shouldn't need any porting work AFAIK. It seems to already be in CM 6.1 ROMs for the Nexus One (any others?). So I'd guess installation would just need to be enabled for other phones.
The tricky part is getting a device driver working that creates a /dev/radio interface for the MUIU FM radio app to use. There IS already a Linux driver for the WL 1273 the Legend uses, but it might need some modifications to run on the Legend.
But there is some complicating factor regarding bluetooth drivers, so it may not be too straight forward. For initial testing at least the bluetooth drivers could be disabled.
What about HTC's kernel source. As I told in cyanogenmod forum the drivers should already be in HTC's kernel source. If the code is there it should be easy to put it into CM7 kernel and use HTC's FM Radio app. Or what do you think?
mikereidis said:
I can keep my eyes and ears open to GPS, but best to concentrate on one issue at a time.
What is the GPS issue ? I thought it didn't work on my phone after new ROM but within a few hours it was working OK for whatever reason. And now I see 2 metre accuracy compared to the minimum of 5 on my Optimus Chic.
Click to expand...
Click to collapse
Yeh, thats the problem. GPS is working on some devices and on others not and nobody knows why. As a matter of fact when I'm running CM 6.1 its working great. Flashing CM 7 no change to get it working. As mentioned others are reporting the same issue with CM 7 on some its working on others not.
ojessie said:
Yeh, thats the problem. GPS is working on some devices and on others not and nobody knows why. As a matter of fact when I'm running CM 6.1 its working great. Flashing CM 7 no change to get it working. As mentioned others are reporting the same issue with CM 7 on some its working on others not.
Click to expand...
Click to collapse
When I get tired of Google maps seeming to take forever to figure out my GPS location, I've downloaded and run the "GPS Test" and "GPS Status" apps. I did so and for some time the status color on one of those showed yellow, meaning no GPS fix, but power on.
Anyway sometime later it was working. One of those apps downloaded data to make cold starts work faster and that may have helped. A few things to try for anyone interested anyway.
ponchofiesta said:
What about HTC's kernel source. As I told in cyanogenmod forum the drivers should already be in HTC's kernel source. If the code is there it should be easy to put it into CM7 kernel and use HTC's FM Radio app. Or what do you think?
Click to expand...
Click to collapse
The problem with running the HTC FM radio app on CM is that it, like many other HTC apps, uses the HTC framework with Sense UI. So CM can't run it, although stock or modded Sense ROMs should be able to.
IMO right now the MIUI app is the way to go, and it's open source so anyone can modify/fork it.
Yeah I think a /dev/radio is likely in HTC source, but it's possible it's something different and/or kind of proprietary.
The Chip manufacturer, TI, and their partners who make RF modules based on the chips, DO have android /dev/radio drivers. So they are definitely out there somewhere.
I think, as usual that "In Theory" this should be a simple matter, in reality there is usually some problems to solve. Otherwise we'd have FM already in CM.
A few pointers:
TI 1273 has a few interfaces for communication. One of them being a (standard) serial via bluetooth, the other one I2C.
HTC did not use I2C because they already had to use the serial interface for bluetooth and it's a lot cheaper that way (that's what all manufacturers do, by the way). The wl1273 driver in the Linux kernel does have support for the FM capabilities, but unfortunately via I2C only.
So basically we already have all the drivers we need in place (tiwlan_drv, sdio), no kernel stuff needed. What's missing is valid documentation about how to enable radio, route it to the headphones, seek/tune, etc.
You could reverse engineer /system/bin/btipsd, which does bluetooth and FM communication in original HTC releases.
Once you are able to control FM stuff (with bluetooth turned on) write a nice summary and I'll ask cyanogen how to implement it. Won't be that hard, given the fact that currently all supported devices use the serial interface via bluetooth.
ali ba said:
The wl1273 driver in the Linux kernel does have support for the FM capabilities, but unfortunately via I2C only.
So basically we already have all the drivers we need in place (tiwlan_drv, sdio), no kernel stuff needed. What's missing is valid documentation about how to enable radio, route it to the headphones, seek/tune, etc.
You could reverse engineer /system/bin/btipsd, which does bluetooth and FM communication in original HTC releases.
Click to expand...
Click to collapse
Thanks ali ba ! Yes I know about cheap manus, I've worked for a few, LOL. Linux VOIP and security appliances mostly though.
By "The wl1273 driver in the Linux kernel" do you mean the TI provided W1273 driver in the CM7 ROM ? I had thought that driver was for WiFi only, or perhaps WiFi + Bluethooth. Or does my seeing an rfkill device mean FM radio is in there too ? Would it create a /dev/radio device ? There are some FM init BTS files that may enable FM.
My understanding is that the WL1273 WiFi driver in the mainline Linux kernel (not the Android kernel) is WiFi only. There's a guy from Nokia trying to get WL1273 FM radio only driver into main Linux kernel but not there yet. That driver will be separate from WiFi driver even though they may both have WL1273 in the name.
I've been finding some HCI commands usable with hcitool to do audio routing stuff at least. RevEng has been a specialty of mine, so I think if it can be done, I have a good chance.
Quickest route to a working FM radio on Legend is to find an existing app for another phone that works.
Phones with the WL1271/1273/1281/1283 chips include original Moto Droid, Droid 2, Droid X, Motorai, Nokia N800 (or N900?), N8 (?), B&N Nook Color.
There's a thread here on XDA about Droid 2 phones using the Droid X FM radio app with success. I tried that app but there seems to be some problem launching the fmradioserver.
I saw a logcat message that may indicate I need to "adb install" the APKs instead of just copying them to /system/app. I tried but got the error that indicates the UID does not match the signature. I guess that's not an issue on Droid 2 (or motorola phones in general?)
Does anyone know if/how to mod/repack an APK to avoid the UID signature issue ?
A few more of my findings for anyone interested. BTW should I or someone create a thread in the dev section at this point ?
As mentioned above a guy from Nokia is trying to get a V4L2/dev/radio driver for WL1273 into mainline Linux kernel. That driver could be integrated into our kernel, but it might take a bit of work. And as mentioned that driver is not in kernel yet and may have lots of changes still coming in the next several months at least.
But TI also has a driver, and it's meant for Android. I haven't been able to grab source code for that driver yet. I think TI driver references WL1283, the biggest baddest version with GPS too. But driver is supposed to work on all 4 variants, down to WL1271.
TI has a command line app for testing fm radio, I think called fmapp if memory serves. It's possible this test app could at least help with exploration.
Unlike the poor original Droid owners, we are lucky that we know our FM receive antenna is connected, since stock Legend has FM radio. But there seems to be a different pin for FM transmit so it's possible we will never be able to transmit FM more than a few inches. But Tx would just be a bonus, but a potentially wonderful bonus.
And, ya know, I'm not even sure if MIUI FM app works with /dev/radio. I was looking at some source and it seems to be hardcoded with Broadcom chip specific stuff.
Oh, and my understanding is that even if we ever managed to get Wireless N working (with a new or improved stack perhaps?), that it will likely kill batteries quickly enough to be effectively unusable. Would be interesting though.
even after the 4.2.2 update bluetooth is still not fully working?
Does anyone here use blueput droid ? Basically turns your phone into a touchpad and keyboard for other devices.. but on every rom, i get "bluetooth stack not supported try a rom like cyanogen" but even on cm10.1 i get this -__-
any help?
I get a different issue. If Bluetooth is enabled the Wi-Fi cuts out on certain streaming apps like Skype, groove ip, and even Google + when scrolling quickly through the feed.
Sent from my Nexus 4 using xda app-developers app
brolic925t said:
even after the 4.2.2 update bluetooth is still not fully working?
Does anyone here use blueput droid ? Basically turns your phone into a touchpad and keyboard for other devices.. but on every rom, i get "bluetooth stack not supported try a rom like cyanogen" but even on cm10.1 i get this -__-
any help?
Click to expand...
Click to collapse
I'm not perfectly clear on the exact reasons, but what I've heard is the BT is wonky because Google switched from a closed source, more compatible BT source to a less reliable open source to be more compliant with the open standard that Android is trying to promote. In doing so, it broke some of the functions. They're trying to fix it and did part-way with 4.2.2. Maybe they'll get there eventually, but not in the near-future, I don't think.
Other manufacturers have a second BT stack that they use that is closed source that makes it more compatible with BT devices.
At least that's what I've heard and what I remember. Maybe I'm completely wrong, but thought I'd like to spread the info. It's not the fault of the devs, it's Google.
HI All,
My Nexus 4 was ota to 4.3 last night. This morning I have been trying to get my H7 to pair via bluetooth, given that both the Nexus 4 and H7 support Bluetooth Smart.
Has anyone managed to pair their H7's over bluetooth? If so what did you do and which app did you use.
I think that the H7 is working as it's sending a t31 signal to my polar f6 watch, so i'm assuming that the bluetooth is also switched on, however I no way to verify this, as i don't have another bluetooth smart receiver to check it with.
Thanks
Satpal
Polar H7 can get paired with android 4.3
schander said:
HI All,
My Nexus 4 was ota to 4.3 last night. This morning I have been trying to get my H7 to pair via bluetooth, given that both the Nexus 4 and H7 support Bluetooth Smart.
Has anyone managed to pair their H7's over bluetooth? If so what did you do and which app did you use.
I think that the H7 is working as it's sending a t31 signal to my polar f6 watch, so i'm assuming that the bluetooth is also switched on, however I no way to verify this, as i don't have another bluetooth smart receiver to check it with.
Thanks
Satpal
Click to expand...
Click to collapse
I just have tried it also without success. But just take the battery of the H7 short out and you will be able after inserting the battery to get paired. So hardware works fine now, but apps aren´t working yet: edemondo pro, runtastic pro. Does somebody have already an app that works?
Same here. I was able to pair after removing the H7 battery and inserting again but is not showing my heart rate.
Sent from my Nexus 4 using xda app-developers app
Same here!
My N4 is able to pair with the H7, but apps don't show my heart rate..
Hi,
I also tried this and my Nexus 4 was unable to find the H& in the BT pairing menu.
I realised yesterday that my wifes S3 also support BT smart, via smasungs own bt stack. I tried to pair via the normal BT menu but failed. However I download an app called NRF (by Nordic Semi) and managed to pair the device directly from there, so atleast i know that my H7 works. I guess it just matter of time before support is introduced by the various apps.
I wonder if manufacturers like Samsung will provide wrappers for the own BT Smart api's to conform with the Android API v18 (the one with BT Smart)
Thanks
Satpal
HI
i tried yesteday to connect the Polar H6 to the Nexus4 using Runtastic app. Didn´t had success i tried to reboot the phone and also released the battery of the polar sensor.
Do you know if there´s other software which i can use to pair them? Or how bluetoot smart pairing works in general?
I am also unable to pair my Bluetooth Smart heart rate monitor to my Nexus 4.
I am using a 60beat Blue and the device is not detected in either the Bluetooth settings menu or the Runtastic PRO V4.0 App.
When I try and connect to a app 'nRF HRM Demo' (the app 60beat support directed me too to test if the device worked) I get a message pop up "Bluetooth Low Energy isn't supported by your phone " Could other users try this app and let me know if they get the same message before I reply to 60beat?
I am running Android 4.3 (stock factory image and I am not rooted) JWR66V
I am waiting for a reply from Runtastic support to see if this device is compatible with their APP.
I do know my heart rate monitor uses the Transmission frequency of 2.4 GHz maybe this is the problem.
I will reply again once I receive a response from Runtastic as I requested a list of compatible hardware.
It does seem strange that I am unable to find much information about this new feature and how to test it.
FIngers crossed we will be able to definitive rundown of what works and does not work on both the Nexus 4 and Android 4.3
After having no luck getting a response out of Runtastic I have finally found an App in the store that reads my 60beat cheststrap (released today);
I am unable to post a link to the Play store but search for BLE Heart Rate Monitor
My device still does not show up in the setting menu but at least I know that 4.3 is working with BLE and it's Runtastic's fault that my monitor does not pair with it's APP.
I will reply again once I hear back from Runtastic with there response to this issue.
Let me know if anyone finds any other apps that work with their devices.
Dichdude said:
After having no luck getting a response out of Runtastic I have finally found an App in the store that reads my 60beat cheststrap (released today);
I am unable to post a link to the Play store but search for BLE Heart Rate Monitor
My device still does not show up in the setting menu but at least I know that 4.3 is working with BLE and it's Runtastic's fault that my monitor does not pair with it's APP.
I will reply again once I hear back from Runtastic with there response to this issue.
Let me know if anyone finds any other apps that work with their devices.
Click to expand...
Click to collapse
Thanks for that Info with BLE
Will try it also and report if its also working for me
Sirbubu said:
Thanks for that Info with BLE
Will try it also and report if its also working for me
Click to expand...
Click to collapse
Tested it out BLE is also working for me so its really a Runtastic issue.
I will also write them.
Sirbubu said:
Tested it out BLE is also working for me so its really a Runtastic issue.
I will also write them.
Click to expand...
Click to collapse
Got a response from Runtastic via Twitter;
"@Runtastic Why do you lock out the use of other BLE HRM from you Android Platform, I thought the point of BLE was for easy implementation?
@Dichdude From now we don't offer support for third-party hardware anymore. Thanks for understanding."
To sum it up Runtastic will only work with there own BLE heart rate monitor. I did reply asking them why and that it looks like a money grab but they have not responded to that question (suprise), so it looks like we will have to wait for other Dev's to implement Smart BT.
We just have to wait for developers to update their apps to be able to make use of BLE. The internal libraries don't yet support that protocol even though the phone does. I'm sure it won't be that long until apps updates start rolling out for the more popular apps. Unfortunetly there is only the one app (BLE HRM that a few have mentioned) that works. Considering 4.3 was released/announced less then 2 weeks ago, we should give the developers some time to get that update out before we start to fully complain.
Sirbubu said:
Tested it out BLE is also working for me so its really a Runtastic issue.
I will also write them.
Click to expand...
Click to collapse
I got an H7 today and downloaded BLE Heart Monitor. As soon as I started scanning I got it in the list of devices. I was able to connect and it seemed pretty accurate. However, I'm not able to connect again and it's not even detected as a device. I tried taking out the battery, re-booting the phone but nothing seems to work. Anything else I can try to get this to connect again with my Nexus 4?
Runtastic says they will only support their Runtastic-branded Bluetooth Smart HRM chest strap. I'm still waiting on Endomondo & RunKeeper to respond to my inquiries. The best thing to do is keep hounding them.
Confirmed working Polar h7 - at least in a basic app that was just updated today.
Sent from my Nexus 4 using Tapatalk 2
jawz101 said:
Confirmed working Polar h7 - at least in a basic app that was just updated today.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Just wondering, can you pair the h7 every time? I can do it once, get to the heart rate screen, see my heart rate but if I close the app it will no longer pair with the H7. It will show it in the list of devices but will hang on the "Connecting" screen. After this I have to clear the data for the app and take out the battery of the H7 to get them to pair again.
Sent from my Nexus 4 using xda app-developers app
I'll check when I get back home.
I tested for a little while tonight. Doesn't seem to handle a reboot nor temporary disconnection. I'd hope it would reconnect if I toggle the Bluetooth radio for a moment. In the event of temporary loss of signal I had to stop the app in android settings and once I restarted the app it would recognize the monitor once more.
My concern with all of that is my phone could reboot for whatever reason mid-run and I'd have to mess with whatever running app again. I'm usually listening to Stitcher radio and using whatever running app in places where phone signal isn't always great. That combination seems to cause my phone to restart on rare occasion which already annoys me so I'd expect reliability.
So I confirmed that turning Bluetooth off and on will resolve the connection issue, it's able to re-connect everytime. I did a ride today running both BLE Heart Monitor and RunKeeper and I had a stable connection throughout. At the end I just entered the average heart rate in RunKeeper. I really wish RunKeeper would release an update already or at least provide an ETA!
You're saying runkeeper saw it? Nm. I just read it
Hi all,
After doing some research on BLE support for Android, I'm somewhat disappointed by the apparent lack of commitment on both Google and Samsung's part to get this sorted out properly, especially given the fact that they advertise BLE support on the product's packaging. By "properly" I mean the ability to find and pair with devices using the device's native Bluetooth Settings menu, not varying support from app to app. There seems to be a bit of information floating around for Nexus and Galaxy S3 devices, but none for the Note 3 - which prompted me to start this thread.
I have a BLE Heart Rate Monitor (Mio Alpha Pro strapless HRM watch) which I have been using to test functionality with my stock, unrooted Galaxy Note 3. Here is a summary of what I've discovered so far:
The Galaxy Note 3 does not find the HRM using the system Bluetooth scan feature,
Samsung's built in "S Health" app does not find/connect to the HRM.
The "BLE Heart Rate Monitor" app in the Play Store finds/connects to the watch fine and receives the HR signal, all without changing the Bluetooth icon's connection status in the notification bar.
Runtastic is the only fitness tracking app that finds and connects to the HRM, with no issue, straight from the app store. Endomondo, Runkeeper, MapMyRun etc have all failed to find and connect to the HRM
xda user dimfish has posted this thread in the Android Software and Hacking General forum, it's a mod that enables BLE conectivity for Fitbit (I am yet to test this, but replies suggest that is working on all 4.3 ROMs).
Given the fact that BLE connectivity works fine on Runtastic (and now Fitbit, with the mod), I am hopeful that native support for all hardware capable Android devices isn't too far away. In the meantime, please share what your thought's experiences are.
Cheers,
BT
bobbytod said:
Hi all,
After doing some research on BLE support for Android, I'm somewhat disappointed by the apparent lack of commitment on both Google and Samsung's part to get this sorted out properly, especially given the fact that they advertise BLE support on the product's packaging. By "properly" I mean the ability to find and pair with devices using the device's native Bluetooth Settings menu, not varying support from app to app. There seems to be a bit of information floating around for Nexus and Galaxy S3 devices, but none for the Note 3 - which prompted me to start this thread.
I have a BLE Heart Rate Monitor (Mio Alpha Pro strapless HRM watch) which I have been using to test functionality with my stock, unrooted Galaxy Note 3. Here is a summary of what I've discovered so far:
The Galaxy Note 3 does not find the HRM using the system Bluetooth scan feature,
Samsung's built in "S Health" app does not find/connect to the HRM.
The "BLE Heart Rate Monitor" app in the Play Store finds/connects to the watch fine and receives the HR signal, all without changing the Bluetooth icon's connection status in the notification bar.
Runtastic is the only fitness tracking app that finds and connects to the HRM, with no issue, straight from the app store. Endomondo, Runkeeper, MapMyRun etc have all failed to find and connect to the HRM
xda user dimfish has posted this thread in the Android Software and Hacking General forum, it's a mod that enables BLE conectivity for Fitbit (I am yet to test this, but replies suggest that is working on all 4.3 ROMs).
Given the fact that BLE connectivity works fine on Runtastic (and now Fitbit, with the mod), I am hopeful that native support for all hardware capable Android devices isn't too far away. In the meantime, please share what your thought's experiences are.
Cheers,
BT
Click to expand...
Click to collapse
up!
no news from app vendors in terms of adding BLE support. Don't much understand why it should be that difficult now that the android 4.3 OS does add support for it. So from the app standpoint it should be quite straight fwd!
It looks like Samsung is backing Ant+ rather than BLE somewhat.
The good news for us competitive cyclists that use Garmin products (Garmin owns Ant+), the Note 3 now ties-in with our heart rate monitors and power meters.
While I don't see me strapping the Note 3 to the handlebars, it can stay in my jersey and record the data.
peakjunkie said:
It looks like Samsung is backing Ant+ rather than BLE somewhat.
The good news for us competitive cyclists that use Garmin products (Garmin owns Ant+), the Note 3 now ties-in with our heart rate monitors and power meters.
While I don't see me strapping the Note 3 to the handlebars, it can stay in my jersey and record the data.
Click to expand...
Click to collapse
From a developer point of view, the ANT+ API is much, much simpler to implement than the BLE API. The ANT+ API already handles device discovery and decoding of data events from sensors into the useful data without even reading the Device Profile. You just request access to heart rate, cadence, etc, and then subscribe to the event handlers which pass the data to you decoded. The BLE API still requires a lot of work to do the decoding properly, handling characteristics, etc
BLE
http://developer.android.com/guide/topics/connectivity/bluetooth-le.html
ANT+
http://www.thisisant.com/APIassets/.../plugins/antplus/pcc/AntPlusHeartRatePcc.html
Any update
bobbytod said:
Hi all,
After doing some research on BLE support for Android, I'm somewhat disappointed by the apparent lack of commitment on both Google and Samsung's part to get this sorted out properly, especially given the fact that they advertise BLE support on the product's packaging. By "properly" I mean the ability to find and pair with devices using the device's native Bluetooth Settings menu, not varying support from app to app. There seems to be a bit of information floating around for Nexus and Galaxy S3 devices, but none for the Note 3 - which prompted me to start this thread.
I have a BLE Heart Rate Monitor (Mio Alpha Pro strapless HRM watch) which I have been using to test functionality with my stock, unrooted Galaxy Note 3. Here is a summary of what I've discovered so far:
The Galaxy Note 3 does not find the HRM using the system Bluetooth scan feature,
Samsung's built in "S Health" app does not find/connect to the HRM.
The "BLE Heart Rate Monitor" app in the Play Store finds/connects to the watch fine and receives the HR signal, all without changing the Bluetooth icon's connection status in the notification bar.
Runtastic is the only fitness tracking app that finds and connects to the HRM, with no issue, straight from the app store. Endomondo, Runkeeper, MapMyRun etc have all failed to find and connect to the HRM
xda user dimfish has posted this thread in the Android Software and Hacking General forum, it's a mod that enables BLE conectivity for Fitbit (I am yet to test this, but replies suggest that is working on all 4.3 ROMs).
Given the fact that BLE connectivity works fine on Runtastic (and now Fitbit, with the mod), I am hopeful that native support for all hardware capable Android devices isn't too far away. In the meantime, please share what your thought's experiences are.
Cheers,
BT
Click to expand...
Click to collapse
Hi BT,
Have you had any success in this since the post. Got the same gear you have and given Alpha MIO says the phone was supported i find this very dissappointing.
Hi mate,
It turns out support for the Alpha is down to application level. I am using it with the latest version of Endomondo and it works as it should. I believe Runtastic works as well, but anything else I can't speak for.
Good luck!
BT
andrewisinchina said:
Hi BT,
Have you had any success in this since the post. Got the same gear you have and given Alpha MIO says the phone was supported i find this very dissappointing.
Click to expand...
Click to collapse
Ignore... i found it, thanks
bobbytod said:
Hi mate,
It turns out support for the Alpha is down to application level. I am using it with the latest version of Endomondo and it works as it should. I believe Runtastic works as well, but anything else I can't speak for.
Good luck!
BT
Click to expand...
Click to collapse
Thanks, I have loaded BLE Heart Rate and can get that to work but was wanting something like MapMyRide as it autolinks to MyFitnessPal. Will take a look at Endomondo.
---------- Post added at 03:58 AM ---------- Previous post was at 03:36 AM ----------
andrewisinchina said:
Thanks, I have loaded BLE Heart Rate and can get that to work but was wanting something like MapMyRide as it autolinks to MyFitnessPal. Will take a look at Endomondo.
Click to expand...
Click to collapse
Hi BT,
Just went endomondo premium but cant get it to hook up the Note 3 and the watch? Do i still need to buy the premium app seperate from the premium account?
thanks for the help
Andrew
It Works
andrewisinchina said:
Ignore... i found it, thanks
Thanks, I have loaded BLE Heart Rate and can get that to work but was wanting something like MapMyRide as it autolinks to MyFitnessPal. Will take a look at Endomondo.
---------- Post added at 03:58 AM ---------- Previous post was at 03:36 AM ----------
Hi BT,
Just went endomondo premium but cant get it to hook up the Note 3 and the watch? Do i still need to buy the premium app seperate from the premium account?
thanks for the help
Andrew
Click to expand...
Click to collapse
UPDATE: I have Endomondo Premium, Linked with MyFitnessPal and this now works well. I have used it for the past 6 weeks no problem. You need to connect in the right order but this does work.
So, Myfitnesspal is linked to Endomondo Premium (needed for the Heart Rate Monitor)
On first application you need to ADD the Heart Rate Monitor in the Endomondo APP itself, with the Alpha in Workout mode. Make sure you turn WIFI off, on your phone for connection. After the first application the following works everytime
1. Alpha on, put into find heart rate
2. Turn WIFI Off and then Bluetooth on and GPS on (if tracking run or ride)
3. Ignore connection from Native Samsung connection
4. Go into Endomondo, after about 10 secs its then connects
5. Press to start workout mode on the alpha (Endomondo will still track the heart rate and zones even if you forget to put it in workout mode as the app is purely using the Alpha as a heart rate input device.
6. Press Go in Endomondo.
At the end of the training session, do the above in reverse order
Hi all,
Mabe you know Garmin Fenix outdoor GPS watch. It has Bluetooth 4 LE. In latest firmware 4.40, its posiible to use this watch like smartwatch (notifications etc). The only one problem is that it works only with Iphone. But i realized i can normally with no problems connect from my LG G2 kitkat android.
My question is, does anybody know, if its possible to make app for managing this smartwatch functions with andoid? I would like to code this app, but if here is anybody more experienced than me, please tell me if its possible or it isnt. Or maybe some hints where to start.
My idea is that if i have paired device, i can normally use android bluetooth api.
tomsi91 said:
Hi all,
Mabe you know Garmin Fenix outdoor GPS watch. It has Bluetooth 4 LE. In latest firmware 4.40, its posiible to use this watch like smartwatch (notifications etc). The only one problem is that it works only with Iphone. But i realized i can normally with no problems connect from my LG G2 kitkat android.
My question is, does anybody know, if its possible to make app for managing this smartwatch functions with andoid? I would like to code this app, but if here is anybody more experienced than me, please tell me if its possible or it isnt. Or maybe some hints where to start.
My idea is that if i have paired device, i can normally use android bluetooth api.
Click to expand...
Click to collapse
This is not relevant to Android Wear. Please consider moving the post to the general forums, or forums specific to this watch. I suspect you will have better success there.