Fixed
Status Update
Comments
jd...@gmail.com <jd...@gmail.com> #2
Correction: I meant mysid/toro, not yakju, in the subject line. But this affects yakju, as well.
al...@gmail.com <al...@gmail.com> #3
I want this.
ov...@gmail.com <ov...@gmail.com> #4
I wan't this too! And I want't all Android 4.1+ devices to have it, not only the Nexus.
db...@gmail.com <db...@gmail.com> #7
I would love to see BT4 support. Seems to be the only other option to ANT+ when it comes to fitness sensors.
to...@gmail.com <to...@gmail.com> #8
Why is this considered an enhancement? The fact that Android doesn't support the latest standards and is behind iOS will run developers to iOS. Unfortunately my company cannot wait for Google to include this "enhancement" in their OS and with great sadness we are moving to iOS.
BLE is not a nice to have, it's the next big thing in short range networking.
BLE is not a nice to have, it's the next big thing in short range networking.
jd...@gmail.com <jd...@gmail.com> #9
@tomer...
I don't think it fair to say "Android doesn't support the latest standards." The fact that both ICS and Jelly Bean fully support BT4.0, which includes BLE, is well-documented. Other ICS devices like the One X and the Galaxy SIII support BLE. It is just the Nexus that is crippled in this regard, with a compatible stack but no driver support.
I don't think it fair to say "Android doesn't support the latest standards." The fact that both ICS and Jelly Bean fully support BT4.0, which includes BLE, is well-documented. Other ICS devices like the One X and the Galaxy SIII support BLE. It is just the Nexus that is crippled in this regard, with a compatible stack but no driver support.
ov...@gmail.com <ov...@gmail.com> #10
@jdavidmo...
So what you say is that it's up to the phone manufacturer to supply a driver? And this is why the S3 and Motorola RAZR has this support?
How come it's so har to supply a driver for this? There aren't that many different BT chipsets around...
So what you say is that it's up to the phone manufacturer to supply a driver? And this is why the S3 and Motorola RAZR has this support?
How come it's so har to supply a driver for this? There aren't that many different BT chipsets around...
jd...@gmail.com <jd...@gmail.com> #11
Well, I said driver, but I don't know if that's the case. I don't know who is responsible for it in this instance. It could be Google, Samsung, or Broadcom for all I know; my point is that the chip and ICS/JB support BT 4.0, so the Nexus should have it. It is not that Android doesn't support BT4 or BLE; it is just this phone for some reason.
According to iFixIt, the Nexus contains a "Samsung SWB-B42 BT 4.0 Dual Band Wlan FM Tx/Rx. Chipworks says the module is actually manufactured by Murata, and houses a Broadcom BCM4330 die inside."
http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/2#s30574
If it is the BCM4330, it supports BLE:http://www.murata-ws.com/wi-fi.htm
According to iFixIt, the Nexus contains a "Samsung SWB-B42 BT 4.0 Dual Band Wlan FM Tx/Rx. Chipworks says the module is actually manufactured by Murata, and houses a Broadcom BCM4330 die inside."
If it is the BCM4330, it supports BLE:
to...@gmail.com <to...@gmail.com> #12
Sorry, but I disagree with the statement that Android supports BLE. There's no API for GATT, no way to receive advertisement data, no way to control the device's role, basically no support for any of the new features introduced with BLE. That's why Motorola and Broadcom came up with their own (very limited) BLE stacks for Android. There may be some support down under at the BlueZ level but if there's no framework support and no API it cannot reasonably be considered as supported.
sa...@gmail.com <sa...@gmail.com> #13
[Comment deleted]
sa...@gmail.com <sa...@gmail.com> #14
i'd love to see my gnex with Low Energy profile in BT 4.0.
ni...@gmail.com <ni...@gmail.com> #15
please add this!
sh...@gmail.com <sh...@gmail.com> #16
* Can't develop BLE apps.
* Existing Android phones (particular make/model) that supports BLE have different API(s).
* From app developer perspective, the landscape is fragmented.
Requesting to support BLE officially in AOSP (both GATT client and GATT server).
* Existing Android phones (particular make/model) that supports BLE have different API(s).
* From app developer perspective, the landscape is fragmented.
Requesting to support BLE officially in AOSP (both GATT client and GATT server).
ju...@gmail.com <ju...@gmail.com> #17
as a google flagship phone, we deserve bluetooth 4.0
is...@gmail.com <is...@gmail.com> #18
I would love to use it with many of the BT 4.0 smartwatches coming out.
ju...@gmail.com <ju...@gmail.com> #19
This is really an essential feature. If android is not responding to this feature request our company will shift our app development to iOS. Can we at least get an estimate on when it will be available?
sr...@gmail.com <sr...@gmail.com> #20
iOS provides a very flexible framework to work on BLE. We hacked the code for testing the extent of support and were happy that it only needs android app framework support. Bluez support is all there. But without knowing any time limit on when to expect official support we have only iOS to work on right now.
je...@gmail.com <je...@gmail.com> #21
Bluetooth Smart / Low Energy has become a mandatory feature (Smartphone will be the PAN center for all those devices which are coming very soon). Luckely the HW is prepared. Android needs to enable this feature (fast to prevent fragmentation). I can't wait! (so i already start). @Google/BT-BLE suppliers, please come with some indications and make us happy!
m1...@gmail.com <m1...@gmail.com> #22
Us developers WANT to design BLE products for the Nexus. The hardware is there Google, please get your software together!
ke...@gmail.com <ke...@gmail.com> #23
Ditto...there are two 3rd party APIs that are needed currently:
https://developer.motorola.com/docs/bluetooth-low-energy-api/
http://code.google.com/p/broadcom-ble/
And to make it worse, 3rd parties sometimes don't include the required shared library like the bestselling Samsung Galaxy S3!
http://innovator.samsungmobile.com/bbs/discussion/view.do?boardId=1132&boardName=AndroidBoard&messageId=157757&messageNumber=&messageCategoryId=4&startId=zzzzz~&startPage=1&curPage=1&rowsPerPage=30&searchType=TITLE&searchText=&searchDays=0&searchTitleFlag=false&searchContentsFlag=false&searchRegisterNicknameFlag=false&lastPageFlag=&categoryId=800&parentCategoryId=4&platformId=1&selectOrder=REGISTER_DATE&selectOrderDirection=DESC&searchParameters=/bbs/discussion/thread.list.do?listLines=30|searchType=title|curPage=1|selectOrder=REGISTER_DATE|selectOrderDirection=DESC|messageCategoryId=4|&nacode=&listLines=30&searchTextForm=&searchTypeForm=TITLE
And to make it worse, 3rd parties sometimes don't include the required shared library like the bestselling Samsung Galaxy S3!
jd...@gmail.com <jd...@gmail.com> #24
Google, let's make this happen! My cookoo watch is practically in the mail. I bought it on faith. Don't let me down!
he...@gmail.com <he...@gmail.com> #25
[Comment deleted]
vi...@gmail.com <vi...@gmail.com> #26
Seconded! My Polar H7 is waiting for it!
te...@gmail.com <te...@gmail.com> #27
[Comment deleted]
te...@gmail.com <te...@gmail.com> #28
we really need this feature to develop many interesting apps,and service.
su...@gmail.com <su...@gmail.com> #29
Same with me.. The cookoo watch should be coming within the next month.. I really wanted to be able to use my gnex with it...
ni...@gmail.com <ni...@gmail.com> #30
i've an alpha coming too which needs this!
dn...@gmail.com <dn...@gmail.com> #31
Let's make this happen! We need BLE support on Android. We can use for numerous cases and its low battery impact is really a good thing to have.
st...@gmail.com <st...@gmail.com> #32
Would use it instantly too for our products.
za...@gmail.com <za...@gmail.com> #33
Bluetooth 4 support in Jelly Bean would be nice.
[Deleted User] <[Deleted User]> #34
We already have the hardware. Want to use it with Android.
do...@gmail.com <do...@gmail.com> #35
Come on Android/Samsung, we need all BLE. I'm currently working on a project where I have to connect with the Texas Ins. cc2540. Come on...stop smoking!!!!
rb...@gmail.com <rb...@gmail.com> #36
Come on Sammy/Google. Please!! It seems you just want to make products good enough. We the people are shooting for great. Why have the hardware there, but not make use of it?
is...@gmail.com <is...@gmail.com> #37
Has Google acknowledged this post yet? Just let us know whether we will need a new phone or not.
dn...@gmail.com <dn...@gmail.com> #38
You do not need a new phone...some high end phones already come with Bluetooth 4 which includes BLE. We need official SDK support.
gu...@gmail.com <gu...@gmail.com> #39
No acknowledgement yet from Google. This issue despite ~200 stars does not yet have an owner.
It matters not whether individual manufacturers include a proprietary BLE API with their android skin - this is just fragmentation and puts developers off producing Apps as they have to write code for every new API that comes along.
A standardized API within the stock Android SDK is the only way make developing an App to use BLE a realistic undertaking for all but the biggest developers or those subsidised by a manufacturer.
One other thing. Please stop the "I too am interested in this issue" posts. If you want to support this, star it. That is all you need to do to raise the profile of the issue. Adding a comment simply emails ~200 people who already know about it.
It matters not whether individual manufacturers include a proprietary BLE API with their android skin - this is just fragmentation and puts developers off producing Apps as they have to write code for every new API that comes along.
A standardized API within the stock Android SDK is the only way make developing an App to use BLE a realistic undertaking for all but the biggest developers or those subsidised by a manufacturer.
One other thing. Please stop the "I too am interested in this issue" posts. If you want to support this, star it. That is all you need to do to raise the profile of the issue. Adding a comment simply emails ~200 people who already know about it.
ph...@gmail.com <ph...@gmail.com> #40
Found this: https://github.com/android-btle/framework It might be useful. I'm considering buying a Galaxy Nexus and a matching BLE watch in a near future. I hope it'll work in the low-energy mode.
ck...@googlemail.com <ck...@googlemail.com> #41
Hard to believe this. I just got a Galaxy NOTE II partly because it claims BT 4.0 compatibility. Now I have to find out I cant use the BT device because there is NO APP ON ANDROID because there's NO API to WRITE the APP in this "bleeding edge" Android version (4.1.1).
Calling this an "Enhancement" is quite a shame too, after all it's the OS having to catch up with fully specified and standardized hardware.
6 months for a key connectivity feature API missing...
Way to disappoint, Google.
Calling this an "Enhancement" is quite a shame too, after all it's the OS having to catch up with fully specified and standardized hardware.
6 months for a key connectivity feature API missing...
Way to disappoint, Google.
ro...@gmail.com <ro...@gmail.com> #42
Google is ignoring thousands of developers and the big promise of a bright Android ecosystem future.
Even Apple, the most closed and totalitarianism company ever has the damn Bluetooth 4 BLE working partially. I have application on (the terrible) iOS using it. And Android is neglecting this huge potencial, market and already available tool and hardware.
There are no like to comments, but let's start putting pressure.
Google MUST ADD support to Bluetooth 4 BLE. Develpers can't accept that hardware already exists without support to it.
I'm in a long time campaign to counter word of mouth everything in iOS and it's damned MFi spec. I've been converting people to Android only to harm and hurt, in my (utterly limited) capacity, Apple. Now there comes Android with the same kind of problems?
We also need WIFI direct and WIFI AdHoc connections supported across devices.
Tags: Bluetooth Low Energy, Bluetooth Low Power, Wibree successor, Bluetooth 4
Even Apple, the most closed and totalitarianism company ever has the damn Bluetooth 4 BLE working partially. I have application on (the terrible) iOS using it. And Android is neglecting this huge potencial, market and already available tool and hardware.
There are no like to comments, but let's start putting pressure.
Google MUST ADD support to Bluetooth 4 BLE. Develpers can't accept that hardware already exists without support to it.
I'm in a long time campaign to counter word of mouth everything in iOS and it's damned MFi spec. I've been converting people to Android only to harm and hurt, in my (utterly limited) capacity, Apple. Now there comes Android with the same kind of problems?
We also need WIFI direct and WIFI AdHoc connections supported across devices.
Tags: Bluetooth Low Energy, Bluetooth Low Power, Wibree successor, Bluetooth 4
ja...@gmail.com <ja...@gmail.com> #43
Did google announce if Android 4.2 will support BT 4 BLE? I believe they announced BT 4 in 4.2, but I never saw anything regarding the low power profile.
I have high hopes that next Monday we will all be pleasantly surprised to see full support of BT 4 in android 4.2!
I have high hopes that next Monday we will all be pleasantly surprised to see full support of BT 4 in android 4.2!
gu...@gmail.com <gu...@gmail.com> #44
ch...@gmail.com <ch...@gmail.com> #45
It also just says "Bluetooth" though.
ro...@gmail.com <ro...@gmail.com> #46
Exactly. Saying "Bluetooth" is not enough. Developers need professional, committing attitude from Google Android team.
So doesn't Google clearly need to address this and be professional towards the expansion of the Android ecosystem? This reminds me of Nokia phones: Full of capabilities that almost "no developer" could use because Nokia "liked" to "respect" their partners like operators. See what happened to Nokia?
Should I stop ranting here? This is a dev list... but where else to request this feature hardly?
So doesn't Google clearly need to address this and be professional towards the expansion of the Android ecosystem? This reminds me of Nokia phones: Full of capabilities that almost "no developer" could use because Nokia "liked" to "respect" their partners like operators. See what happened to Nokia?
Should I stop ranting here? This is a dev list... but where else to request this feature hardly?
ja...@gmail.com <ja...@gmail.com> #47
Other sites (such as Engadget and The Verge) report BT 4.0 on their spec listings for the Nexus 4.
The lack of any affirmative statement on Google Play for bt 4.0 is offset by the lack of an affirmative statement on Google PLay for bt 3.0 :)
As I said, I'm hopeful that it'll be there in Android 4.2. I haven't found it confirmed yet, though, not even among those who have a nexus 4. Maybe I'll go ask them!
The lack of any affirmative statement on Google Play for bt 4.0 is offset by the lack of an affirmative statement on Google PLay for bt 3.0 :)
As I said, I'm hopeful that it'll be there in Android 4.2. I haven't found it confirmed yet, though, not even among those who have a nexus 4. Maybe I'll go ask them!
sk...@gmail.com <sk...@gmail.com> #48
One version I heard was that google deliberately went the other way when apple started looking into BLE and put their money and effort into NFC instead, thinking it would be a competing technology. Too bad they failed in foreseeing all these cool gadgets that will not be able to work with NFC technology..
Sorry, just another unproductive comment, but perhaps a possible back story? For what its worth, I guess we are more likely to get both NFC and BLE eventually than the iOS guys =)
Sorry, just another unproductive comment, but perhaps a possible back story? For what its worth, I guess we are more likely to get both NFC and BLE eventually than the iOS guys =)
jo...@gmail.com <jo...@gmail.com> #49
Don't hold your breath. I've been following this closely and there's no indication that 4.2 will have anything BLE related. I seriously doubt that we'll see anything until the 5.0 timeframe at the earliest.
I don't think it's a coincidence that the two manufacturers that have shown some movement on this front (Broadcom & Moto) have all but stopped development/progress. I strongly suspect that they know something we don't about Google's intentions.
Samsung is also playing dumb -http://developer.samsung.com/forum/board/thread/view.do?boardName=GeneralB&messageId=157757
I would *love* to be wrong. I have several projects that are stalled waiting for BLE GATT support in Android!
I don't think it's a coincidence that the two manufacturers that have shown some movement on this front (Broadcom & Moto) have all but stopped development/progress. I strongly suspect that they know something we don't about Google's intentions.
Samsung is also playing dumb -
I would *love* to be wrong. I have several projects that are stalled waiting for BLE GATT support in Android!
ch...@gmail.com <ch...@gmail.com> #50
It irks me that you can see things like the Samsung S3 featured on http://www.bluetooth.com/Pages/Bluetooth-Smart-Devices.aspx . Samsung even links on it's page to this article, which promotes the idea that it's 'ready' for Bluetooth 4.0.
"SMART READY" is seeming to me to be just like the first wave "HD READY" televisions that came out in the 90's that. Misleading and frustrating.
On the other hand, Bluez does seem to be developing with updates regularly having "LE" in the title.http://git.kernel.org/?p=bluetooth/bluez.git;a=shortlog ,http://www.bluez.org/profiles/ , but I suppose that doesn't mean they're making anything specifically for google or samsung
Finding anything concrete, other than misleading advertisement or ^companies playing stupid, appears to be next to impossible.
Google and Samsung were noticeably absent from this blog by the Bluetooth SIG CMO:
http://blog.bluetooth.com/bluetooth-smart-ready-product-announcements-piling-up/
I can hear my iOS buddies laughing.
"SMART READY" is seeming to me to be just like the first wave "HD READY" televisions that came out in the 90's that. Misleading and frustrating.
On the other hand, Bluez does seem to be developing with updates regularly having "LE" in the title.
Finding anything concrete, other than misleading advertisement or ^companies playing stupid, appears to be next to impossible.
Google and Samsung were noticeably absent from this blog by the Bluetooth SIG CMO:
I can hear my iOS buddies laughing.
ro...@gmail.com <ro...@gmail.com> #51
Completely agree with comments 49, 48 and all. And "API specific" solutions won't help. To support new BLE devices for the millions of new Android devices, we need support for Bluetooth 4 BLE from Android Core.
Google Android team: you need to clarify the message and work on it, present the roadmap and be fair with us developers. Help the world in not having another shameful iOS.
Google Android team: you need to clarify the message and work on it, present the roadmap and be fair with us developers. Help the world in not having another shameful iOS.
ro...@gmail.com <ro...@gmail.com> #52
Completely agree with comments 49, 48 and all. And "API specific" solutions won't help. To support new BLE devices for the millions of new Android devices, we need support for Bluetooth 4 BLE from Android Core.
Google Android team: you need to clarify the message and work on it, present the roadmap and be fair with us developers. Help the world in not having another shameful iOS.
Google Android team: you need to clarify the message and work on it, present the roadmap and be fair with us developers. Help the world in not having another shameful iOS.
mi...@gmail.com <mi...@gmail.com> #53
According to the recently updated Android 4.2 changelog (http://developer.android.com/about/versions/jelly-bean.html ), the Bluetooth stack was rewritten: "Android 4.2 introduces a new Bluetooth stack optimized for use with Android devices. The new Bluetooth stack developed in collaboration between Google and Broadcom replaces the stack based on BlueZ and provides improved compatibility and reliability."
me...@gmail.com <me...@gmail.com> #54
Sadly, this doesn't seem promising. It should have explicitly mentioned bluetooth 4.0, low energy, or smartdevice. Additionally I see no changes to the android.bluetooth API
jd...@gmail.com <jd...@gmail.com> #55
According to the email I got from the folks making the cookoo watch, they are not able to release an Android app for the watch as they had hoped due to "Android support of BT 4.0," but they are "working closely with Google and other interested parties to resolve this as quickly as possible."
Sad state of affairs indeed, but this at least gives me some small measure of hope. I hope they don't develop a solution that is specific to the cookoo watch, though.
Sad state of affairs indeed, but this at least gives me some small measure of hope. I hope they don't develop a solution that is specific to the cookoo watch, though.
ch...@gmail.com <ch...@gmail.com> #56
"BLE will be the next major feature we are going to add."
https://groups.google.com/forum/#!msg/android-platform/CYtxCmtZ-WI/aIzBq7KbKVUJ
No word on schedule, but it seems to be the most concrete acnowledgement I've seen thus far from someone at google/android or related hardware companies.
No word on schedule, but it seems to be the most concrete acnowledgement I've seen thus far from someone at google/android or related hardware companies.
ch...@gmail.com <ch...@gmail.com> #57
Sadly, it seems from the discussion in the link in 55 that it means sometime after 4.2, since the source was answering questions about 4.2. Seems to support what 53 was alluding to.
jd...@gmail.com <jd...@gmail.com> #59
Peter Hauser, who is making the upcoming cookoo watch that relies on BLE, yesterday sent a very informative letter to Android backers of the cookoo project. Very interesting read on spotty BLE support in Android 4.0+ devices and how their phone-specific workarounds were obliterated by Google's switch from BlueZ stack to Broadcom stack -- which still lacks BLE. Take a look, and I'd encourage interested devs to take him up on his call for help -- any likely solutions would probably bear fruit for apps beyond just the cookoo app.
http://cookoowatch.com/images/Letter%20to%20Android%20users%20of%20the%20COOKOO%20watch%2020121121.pdf
jo...@gmail.com <jo...@gmail.com> #60
With so many newer devices having the hardware why is the software so behind?
jm...@pop.net <jm...@pop.net> #61
Another request for BLE support on the Nexus platform, from a developer who wants to build Android-based industrial/laboratory control applications.
Google: get your act together on this. Seriously. NFC is not a competitive technology; they are completely different standards meant for completely different purposes.
Google: get your act together on this. Seriously. NFC is not a competitive technology; they are completely different standards meant for completely different purposes.
ro...@gmail.com <ro...@gmail.com> #62
In reply to comment 60: NFC is also very important. All connectivity technologies, including WIFI direct, WIFI AdHoc and Bluetooth 4 are very important. This is where Google can prove to be ahead of other weird control freak manufacturers.
Perfect Bluetooth 4 is a must.
Perfect Bluetooth 4 is a must.
mo...@gmail.com <mo...@gmail.com> #63
bring it! ....please!
mu...@gmail.com <mu...@gmail.com> #64
BLE is required functionality. It is driving us to iOS. Get with it google.
ty...@gmail.com <ty...@gmail.com> #65
[Comment deleted]
ty...@gmail.com <ty...@gmail.com> #66
What's stopping the dev community like the guys at xda from finding a way to enable it themselves? Is there a different bluetooth driver that is needed to activate the BLE feature of the chip?
dm...@gmail.com <dm...@gmail.com> #67
My admittedly limited understanding is that part of the problem is that the different chip sets in the different handsets cause grief, each one needs its own driver. And apparently there's something about Android that doesn't support the BLE , at least not readily.I'm told that Motorola has found a half-baked workaround that works intermittently. I think it falls on the OEMs to offer drivers for the BT hardware that's currently just sitting in their devices but not being used to its full, or *ugh* even iOS-level potential.
mo...@gmail.com <mo...@gmail.com> #68
There are two things that bother me the most:
1.- Even though you can find threads everywhere on the Internet about the
lack of BLE on Android, Google fails to give a straight answer on the
matter. What's more, I keep reading phone reviews that menting BLE
support... When there is none.
2.- And then comes industry juggernaut Samsung and markets the SGS3 as Bt
Smart Ready (It says so on the box) and it is as smart ready as the Earth
is flat. No developer support whatsoever from Samsung. False advertising
anyone?
BLE environment seems to be even more fragmented than Android and unless
Google finally makes a move it will stay this way. Disappointing.
1.- Even though you can find threads everywhere on the Internet about the
lack of BLE on Android, Google fails to give a straight answer on the
matter. What's more, I keep reading phone reviews that menting BLE
support... When there is none.
2.- And then comes industry juggernaut Samsung and markets the SGS3 as Bt
Smart Ready (It says so on the box) and it is as smart ready as the Earth
is flat. No developer support whatsoever from Samsung. False advertising
anyone?
BLE environment seems to be even more fragmented than Android and unless
Google finally makes a move it will stay this way. Disappointing.
ri...@gmail.com <ri...@gmail.com> #69
I have confirmed a functional ble stack on the HTC DNA on Verizon using the
open ble API from broadcom. Its not a final holistic solution for all of
android... but it is a start for a good development platform.
Given the new ble stack implemented as part of 4.2 in conjunction with
broadcom, there is also a good potential chance that this API could grow
into the final solution as part of key lime pie.
open ble API from broadcom. Its not a final holistic solution for all of
android... but it is a start for a good development platform.
Given the new ble stack implemented as part of 4.2 in conjunction with
broadcom, there is also a good potential chance that this API could grow
into the final solution as part of key lime pie.
sh...@gmail.com <sh...@gmail.com> #70
Is there any other phone other than HTC DNA that works with broadcom apis? This phone is not available in Canada.
je...@gmail.com <je...@gmail.com> #71
Here's another vote from the FAE for Bluegiga here in the US. This is a feature that many customers are looking for and it would certainly make the Nexus (and Android in general) WAY more appealing, especially since Android allows permission-based access to call, email, and SMS info via open APIs (iOS locks this down horribly). You still have a chance to get ahead of Apple on this front! Please don't pass it up!
fu...@gmail.com <fu...@gmail.com> #72
Try samy s3 or notes2
Am 01.12.2012 17:23 schrieb <android@googlecode.com>:
Am 01.12.2012 17:23 schrieb <android@googlecode.com>:
dm...@gmail.com <dm...@gmail.com> #73
No, Samsung also does not provide a driver for the BLE platform, despite having the hardware and explicitly stating on the box that the GS3 is 'smart bluetooth ready'.
sg...@gmail.com <sg...@gmail.com> #74
ke...@gmail.com <ke...@gmail.com> #75
The S3 does not support BLE. I have one...It's missing a library for
Broadcom library support but that doesn't work with the new stack
anyways...
Comment #71 on issue 36949180 by fury...@gmail.com: Support for Bluetooth 4.0
Low Energy Profile on Galaxy Nexus (yakju)
http://code.google.com/p/**android/issues/detail?id=33371 <http://code.google.com/p/android/issues/detail?id=33371 >
Try samy s3 or notes2
Am 01.12.2012 17:23 schrieb <android@googlecode.com>:
Broadcom library support but that doesn't work with the new stack
anyways...
Low Energy Profile on Galaxy Nexus (yakju)
Try samy s3 or notes2
Am 01.12.2012 17:23 schrieb <android@googlecode.com>:
do...@gmail.com <do...@gmail.com> #76
Is there even a BLE Chip in SGS3? I'm beginning to think that isn't the case :(
do...@gmail.com <do...@gmail.com> #78
Ok, then I will not give up the hope.
dm...@gmail.com <dm...@gmail.com> #79
Just want to say that Smart Scanner actually works, it can see my BTLE device (variable tech NODE) so is obviously able to tap into my SGS3's BTLE hardware. Can't do anything with it of course, but at least it sees it. Certainly cause for hope.
mu...@gmail.com <mu...@gmail.com> #80
When Google traded the BlueZ stack for the Broadcom stack LE support became impossible without rooting your phone. At AnDevCon today the BT expert said the only Android phone that supports LE is the Motorola Razor. LE needs to be standard functionality before BT developers can invest in supporting Android. The entire room of developers were disappointed, and many walked out in disgust. You're not only alienating customers, you're losing developers. Seriously. This needs attention. The only realistic answer is to use iOS.
dm...@gmail.com <dm...@gmail.com> #81
Thanks for this news from AnDevCon. How far does this need to go before we can finally get this basic functionality?
ch...@gmail.com <ch...@gmail.com> #82
I've understood, and I can't pin down which places I've read this, that the Razor only has BTLE functionality for the LE HRM profile... I guess I'm saying that even the razr solution isn't by any means complete... Again, this is all second hand, so don't quote me, though I wrote it as a statement, I'm kind of looking for confirmation on the matter.
da...@gmail.com <da...@gmail.com> #83
@Murray: And if you had attended AnDevCon the evening before, you would have heard how all mainline HTC devices launching now and after this quarter will support BLE starting with the HTC One X+ and Droid DNA.
eb...@gmail.com <eb...@gmail.com> #84
@Chris: So if i start working for BLE based Android Application would you suggest using a Motorola RAZR for testing the capability? i am working for the HRM profile.
Can i try integrating the Broadcom BLE on the Nexus 7 with Android 4.2 since it already has the Broadcom stack and the silicon by them.
@Dario: Is there any tablet that can be used to for my work on the app?
Can i try integrating the Broadcom BLE on the Nexus 7 with Android 4.2 since it already has the Broadcom stack and the silicon by them.
@Dario: Is there any tablet that can be used to for my work on the app?
[Deleted User] <[Deleted User]> #85
This is not a Nexus issue, but needs to be resolved in Android. Want it for my Galaxy S3 & S3 Note.
jd...@gmail.com <jd...@gmail.com> #86
All I knew at the time I started this thread was that my Nexus had all the right hardware but no software capability. I would change the title if I could, but I can't.
410 stars, and no acknowledgment from Google. Shameful.
410 stars, and no acknowledgment from Google. Shameful.
jr...@gmail.com <jr...@gmail.com> #87
Just got my MIO ALPHA HRM watch from Kickstarter. Been waiting the better part of a year only to find out that my HTC EVO 4G LTE (which I bought specifically for its advertised Bluetooth 4.0) won't work with the ALPHA. Simply a lie. Time to get an iPhone 5.
no...@gmail.com <no...@gmail.com> #88
Please enhance the Bluetooth capabilities of Galaxy nexus and Stock Android over all by adding support to 4.0 and AVRCP 1.3 or 1.4.
co...@gmail.com <co...@gmail.com> #89
Please support Bluetooth 4's Smart profile for connecting Heart Rate Monitors like the Wahoo or Polar.
da...@gmail.com <da...@gmail.com> #90
Same issue with the MIO Alpha here, not being detected by my Nexus 4...
da...@gmail.com <da...@gmail.com> #91
To clarify a bit, the Bluetooth 4.0 spec consists of the high speed and low energy subsets so devices that claim BT 4.0 support may not necessarily include BLE. I'll check with bluetooth.org spec leads on this point as this has been a source of confusion re: which devices support BLE regardless of OEM. For HTC phones, as previously mentioned BLE support is included only starting with the One X+ (note the '+') and the Droid DNA. Btw, HRM profile verified with Wahoo and Polar (haven't yet tried MIO).
@ebin (and others) please contact me off list or post on stackoverflow instead. I'm only posting here because of specific devices mentioned. It's unfortunate that the original poster cannot rename the issue to "Support for Bluetooth 4.0 Low Energy Profile" as this issue should not be about specific devices or chipsets but about a standard Android API.
@ebin (and others) please contact me off list or post on stackoverflow instead. I'm only posting here because of specific devices mentioned. It's unfortunate that the original poster cannot rename the issue to "Support for Bluetooth 4.0 Low Energy Profile" as this issue should not be about specific devices or chipsets but about a standard Android API.
vi...@gmail.com <vi...@gmail.com> #92
Re:90
This thread has been completely about BLE and Smart devices. Can you clarify what you mean by HTC devices only supporting from HOX+ as the hardware in the One X, S and I believe V all have a Qualcomm device which supports BLE. Have HTC included BLE support in the BT stack within sense for the HOX+ or are you implying some difference in the hardware?
This thread has been completely about BLE and Smart devices. Can you clarify what you mean by HTC devices only supporting from HOX+ as the hardware in the One X, S and I believe V all have a Qualcomm device which supports BLE. Have HTC included BLE support in the BT stack within sense for the HOX+ or are you implying some difference in the hardware?
no...@gmail.com <no...@gmail.com> #93
Please take quick action.
ow...@gmail.com <ow...@gmail.com> #94
Re:90, I think it's important to clarify that this thread is about Bluetooth Low Energy (BLE), aka "Bluetooth Smart", rather than other features of Bluetooth 4.0. However, we should avoid the confusing term "Profile", which has a specific meaning in Bluetooth (see "Headset Profile (HSP)", "Health Device Profile (HDP)", etc). HSP has been part of Bluetooth since 1.0, A2DP came in with EDR in v2.0, and (I think) HDP depends on the GATT features of BLE.
Some are asking for AVRCP updates etc, which should be a separate thread, since they do not depend on Bluetooth v4.0 *or* BLE. They are related to the BlueZ or Broadcom Bluetooth stack revision.
It gets confusing, of course, given that the GNex apparently has the same Broadcom chip that implements BLE in the iPhone (and, supposedly, in the S3), but we need to remember that it takes more than a chip to implement a protocol -- there's firmware as well, and I'm assuming that Samsung did not license the BLE firmware from Broadcom for the GNex, so instead of using a non-BLE Bluetooth chip in the GNex, Samsung/Broadcom just used the same chip as the S3 with a non-BLE firmware "blob". Therefore a software upgrade isn't as simple as it seems, because Broadcom would never agree to it without Samsung paying the extra licensing fee, which isn't going to happen (where's the revenue going to come from? There's no mechanism for users to pay for a software/firmware upgrade).
The issue with the S3 being marketed as "Smart Ready", and then appearing to not work with Smart devices, is also a separate issue. It needs addressing, but not on a thread about BLE on the GNex.
Some are asking for AVRCP updates etc, which should be a separate thread, since they do not depend on Bluetooth v4.0 *or* BLE. They are related to the BlueZ or Broadcom Bluetooth stack revision.
It gets confusing, of course, given that the GNex apparently has the same Broadcom chip that implements BLE in the iPhone (and, supposedly, in the S3), but we need to remember that it takes more than a chip to implement a protocol -- there's firmware as well, and I'm assuming that Samsung did not license the BLE firmware from Broadcom for the GNex, so instead of using a non-BLE Bluetooth chip in the GNex, Samsung/Broadcom just used the same chip as the S3 with a non-BLE firmware "blob". Therefore a software upgrade isn't as simple as it seems, because Broadcom would never agree to it without Samsung paying the extra licensing fee, which isn't going to happen (where's the revenue going to come from? There's no mechanism for users to pay for a software/firmware upgrade).
The issue with the S3 being marketed as "Smart Ready", and then appearing to not work with Smart devices, is also a separate issue. It needs addressing, but not on a thread about BLE on the GNex.
ag...@gmail.com <ag...@gmail.com> #95
I wonder if this problem though somebody decides it again or not recognize the problem?
dm...@gmail.com <dm...@gmail.com> #96
Uh, either we've missed something, or the Verge has their facts incorrect, but the first paragraph of this story out of CES states that the new FitBit Tracker will connect with the SGS3 and Galaxy Note II through BT 4.0.
http://www.theverge.com/2013/1/7/3840106/fitbit-flex-wireless-fitness-bracelet#_=_
ke...@gmail.com <ke...@gmail.com> #97
This also uses BLE: http://www.indiegogo.com/sticknfind/
They mention that the SGS3 support is bad so they wrote their own Bluetooth "drivers". Maybe we can bug them to open source that portion. Still, that only addresses two devices.
They mention that the SGS3 support is bad so they wrote their own Bluetooth "drivers". Maybe we can bug them to open source that portion. Still, that only addresses two devices.
an...@gmail.com <an...@gmail.com> #98
Hi,
i've wrote samsung as well,
it drives me crazy that there is no news about a full BL 4.0 support or what#s going on.
I love android and my s3, but maybe i got the wrong device, all new BL4.0 are not supported, like any Sport-Gimigs from Polars wearlink-belt, nike+, garmins products, carradios, headsets - when ever i ask a product-support they always tell me "Sorry not supported- if you want to use this ... "You must have or buy an iphone, ipod and so on. Andronid isn't supported yet"
This can't be that everybody get's to hear sorry only for apple-products... or is there somebody working for apple at google-development or samsung? It's the best advertising apple can ask for.
i've wrote samsung as well,
it drives me crazy that there is no news about a full BL 4.0 support or what#s going on.
I love android and my s3, but maybe i got the wrong device, all new BL4.0 are not supported, like any Sport-Gimigs from Polars wearlink-belt, nike+, garmins products, carradios, headsets - when ever i ask a product-support they always tell me "Sorry not supported- if you want to use this ... "You must have or buy an iphone, ipod and so on. Andronid isn't supported yet"
This can't be that everybody get's to hear sorry only for apple-products... or is there somebody working for apple at google-development or samsung? It's the best advertising apple can ask for.
ma...@gmail.com <ma...@gmail.com> #99
All of this is probably a result of all the patent wars going on
da...@gmail.com <da...@gmail.com> #100
Can't believe this issue hasn't been addressed yet...
ck...@googlemail.com <ck...@googlemail.com> #101
Nothing to do with patent wars. The SGS 3 and Note2 use the same chip as the iphone5. The trouble is that Google has not included drivers and functionality for this (and other chipsets) in Android, allowing the developers to access the required functions through a defined operating system interface (API).
Until Google starts caring to do so, developers only option is to add the driver code for EACH CHIPSET into their APP, bloating the app and restricting functionality to specific devices using that very chipset the drivers are for.
Of course most devs dont want to put in that amount of work for a limited selection of devices.
Until Google starts caring to do so, developers only option is to add the driver code for EACH CHIPSET into their APP, bloating the app and restricting functionality to specific devices using that very chipset the drivers are for.
Of course most devs dont want to put in that amount of work for a limited selection of devices.
[Deleted User] <[Deleted User]> #102
As I see 4.2 is already released? And as I see, there still no BLE support?
Did someone checked that? Please advise...
Did someone checked that? Please advise...
re...@gmail.com <re...@gmail.com> #103
I use Nexus 4 with Android 4.2.1 and want to now if Bluetooth 4.0 is supported in this Version. Before buying Bluetooth 4.0 devives I want to be sure they are supported by 4.2.1 before wasting money.
gi...@gmail.com <gi...@gmail.com> #104
Unbelievable - I would never have thought that I need to recommend Apple / IOS but for sport sensors Bluetooth 4.0 /smart /BLE offers a significant better solution (in particular in terms of stability and energy consumption).
Google - get these driver /fw update out asap.
Google - get these driver /fw update out asap.
ca...@gmail.com <ca...@gmail.com> #105
Can't believe this issue hasn't been addressed yet...
an...@gmail.com <an...@gmail.com> #106
And i can't believe there is no official google-statement for this problem or any big press about it.
It isn't a small problem like if the led can#t display green - it's a full function with is missing.
But i hope when the spring comes and the spring will be coming and some press-people want to run with their SGS3 - this prob will be get public and maybe google will fix it.
It isn't a small problem like if the led can#t display green - it's a full function with is missing.
But i hope when the spring comes and the spring will be coming and some press-people want to run with their SGS3 - this prob will be get public and maybe google will fix it.
ne...@gmail.com <ne...@gmail.com> #107
Please address this. I want to purchase the fitbit flex which utilizes Bluetooth 4.0 and I cant because my Galaxy Nexus doesn't have the drivers?....Come on..please fix
ki...@gmail.com <ki...@gmail.com> #108
It is urgently needed.
Please fix this.
It is simply annoying not to have it.
Do you want us to use I phones? ??????
Please fix this.
It is simply annoying not to have it.
Do you want us to use I phones? ??????
sh...@gmail.com <sh...@gmail.com> #109
i have issues with bluetooth too
al...@gmail.com <al...@gmail.com> #110
omg, common guys...
ca...@googlemail.com <ca...@googlemail.com> #111
More and more BLE devices are coming on the market,
but with Android they can't be used yet. Why?
Are there any technical problems?
Apple already supports BLE.
Do i really need to replace my great Android phone by an iPhone?
but with Android they can't be used yet. Why?
Are there any technical problems?
Apple already supports BLE.
Do i really need to replace my great Android phone by an iPhone?
no...@gmail.com <no...@gmail.com> #112
This needs to year a year and a half ago, it's crazy Android is behind in this area, is it a licensing issue?
ki...@gmail.com <ki...@gmail.com> #113
Wow, somebody at google should get fired for this.
ca...@googlemail.com <ca...@googlemail.com> #114
Question to all:
Is there any page of any vendor of Android (!) phones/tablets,
(perhaps beside Motorola phones (Razr))
which says more than "Bluetooth 4.0", mention perhaps Smart or Smart Ready?
Is BLE mentioned in any of the webpages, datasheets or advertisements?
I just had a quick look, but it seems the pages i have visited
only mention "Bluetooth 4.0"...
I also want BLE with Android, but was it said, it is coming?
Is there any page of any vendor of Android (!) phones/tablets,
(perhaps beside Motorola phones (Razr))
which says more than "Bluetooth 4.0", mention perhaps Smart or Smart Ready?
Is BLE mentioned in any of the webpages, datasheets or advertisements?
I just had a quick look, but it seems the pages i have visited
only mention "Bluetooth 4.0"...
I also want BLE with Android, but was it said, it is coming?
ma...@googlemail.com <ma...@googlemail.com> #115
I develop devices for battery powered access control systems.
In my current project I want to control the system with a smartphone or tablet.
Therefore I think BLE now is the best solution.
But if i say "you have to use iOS" to my devolpers, they kill me.
I'm also not a friend of apple and love android.
Please let me know if we can do something to accelerate the BLE support.
In my current project I want to control the system with a smartphone or tablet.
Therefore I think BLE now is the best solution.
But if i say "you have to use iOS" to my devolpers, they kill me.
I'm also not a friend of apple and love android.
Please let me know if we can do something to accelerate the BLE support.
ma...@gmail.com <ma...@gmail.com> #116
There must be a reason Google is not implementing support for Bluetooth Low Energy. I suspect a legal issue is at play here as well. Android has NFC and iOS has BLE.. But what exactly is going on here is sketchy to say the least
da...@gmail.com <da...@gmail.com> #117
If Google doesn't implement Bluetooth 4.0 I'll have to go get an iPhone. (Boooo!) The fact of the matter is, there's just too many cool new devices that make use of this technology.
da...@gmail.com <da...@gmail.com> #118
(Running a Samsung Galaxy SIII by the way) Which as far as I understand it, has the hardware and simply needs the software support.
aj...@gmail.com <aj...@gmail.com> #119
Please add support for bluetooth 4.0!
ro...@gmail.com <ro...@gmail.com> #120
Un-be-liev-able that there still is no roadmap/news for when this will be implemented.
st...@gmail.com <st...@gmail.com> #121
Would like to see it implemented.
sh...@gmail.com <sh...@gmail.com> #122
Unbelivable that this issue has been discussed so long time! What is the reason if Google do not support it.
u....@gmail.com <u....@gmail.com> #123
I would like this to be implemented too.
so...@mylocalsocial.com <so...@mylocalsocial.com> #124
Please add! We want to add BLE Android Support to LocalSocial. We can already work with iOS - want to do Android asap - thanks!
fr...@gmail.com <fr...@gmail.com> #125
please Google add this already.
os...@gmail.com <os...@gmail.com> #126
Another vote to ask Google for implementation of BT 4.0 + LE on Android. I can't believe that if I want to use a pulsometer I have to switch to iPhone.
an...@gmail.com <an...@gmail.com> #127
I am working as an engineer and i´m developing apps for smartphones. our newest device uses bt 4.0 to communicate. although i hate ios we have to go that way because btle implementation for android is missing. please hurry up, or let us know about google´s future plans, because we have to make a decision which way to go. it´s already implemented in nearly all other os for smartphones (windows phone 8, blackberry, ios6), it can´t be too hard to catch up to the competitioneers.
lu...@gmail.com <lu...@gmail.com> #128
This is insane, Google's flagship nexus devices that have Bluetooth 4.0 chips still do not have this feature implemented.
nw...@gmail.com <nw...@gmail.com> #129
Please send out drivers for this Google. It's very frustrating having the hardware and not being able to use it to its full capacity. Almost like owning an apple product.
we...@gmail.com <we...@gmail.com> #130
C'mon Google!!!!!!!
ne...@gmail.com <ne...@gmail.com> #131
Support for BLE is in latest BlueZ stack. So it will be
nice to port it into Android.
nice to port it into Android.
ya...@gmail.com <ya...@gmail.com> #132
Please add Bluetooth 4.0 support for Android, esspecialy for communication with TI's CC2541 device
in...@gmail.com <in...@gmail.com> #133
ku...@gmail.com <ku...@gmail.com> #134
I'm just founding a new BTLE startup and we are forced to implement a stupid IOS app although I would prefer Android so much! Please google don't let us down!
vi...@gmail.com <vi...@gmail.com> #135
Ble is the wave of the future :)
ju...@gmail.com <ju...@gmail.com> #136
Although I also want this functionality, Google will not respond to this feature request as it is device specific.
This is the issue tracker of the Android project and only issues concerning AOSP will be addressed, as far as I know.
This is the issue tracker of the Android project and only issues concerning AOSP will be addressed, as far as I know.
a....@gmail.com <a....@gmail.com> #137
[Comment deleted]
a....@gmail.com <a....@gmail.com> #138
Do you mean that people should visit http://www.samsung.com/us/support/owners/product/SPH-L700ZKASPR or http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW and ask from Samsung there? Will Samsung respond?
The issue has been identified to be related to the Android's generic bluetooth stack, not to do with the chip in the handset specifically. There is no interface to the hardware for software developers. This issue is shared with even the most recent Android phones.
Even if this wasn't universal, here are some issues that are specific to phone components but are acknowledged and have an owner. Some have been been released:
http://code.google.com/p/android/issues/detail?id=43224
http://code.google.com/p/android/issues/detail?id=6914
http://code.google.com/p/android/issues/detail?id=17119
As an AOSP device, Galaxy Nexus users can count on a closer working relationship with the AOSP team. That's one of the major benefits of purchasing a Nexus-series device.
We can only pray that Google will address this in Key Lime Pie which should come out at Google I/O in May. This is likely given the advice BLE is a "top priority". It is extremely disappointing however that Google treats their issue tracker with complete disdain and does not inform us here.
The issue has been identified to be related to the Android's generic bluetooth stack, not to do with the chip in the handset specifically. There is no interface to the hardware for software developers. This issue is shared with even the most recent Android phones.
Even if this wasn't universal, here are some issues that are specific to phone components but are acknowledged and have an owner. Some have been been released:
As an AOSP device, Galaxy Nexus users can count on a closer working relationship with the AOSP team. That's one of the major benefits of purchasing a Nexus-series device.
We can only pray that Google will address this in Key Lime Pie which should come out at Google I/O in May. This is likely given the advice BLE is a "top priority". It is extremely disappointing however that Google treats their issue tracker with complete disdain and does not inform us here.
sc...@gmail.com <sc...@gmail.com> #139
Add BLE support. PLEASE!
se...@gmail.com <se...@gmail.com> #140
I love my Android phone, but the lack of BTLE and a BT4.0 stack (due to Googles ignorance) is really annoying!!!
ca...@gmail.com <ca...@gmail.com> #141
+1 for adding BT4.0 to Android. This is ridiculous
da...@gmail.com <da...@gmail.com> #142
[Comment deleted]
da...@gmail.com <da...@gmail.com> #143
I have an S3, and I can connect my Polar H7 Bluetooth smart HRM to my phone with this app: http://bit.ly/W203bY . Why can't any other apps work?
an...@frtk.ru <an...@frtk.ru> #144
I want to create an app for Polar H7 device... i wish you could add support of BTLE to android very soon.... I have HTC One S and can't find any native firmware or API for Qualcomm Bluetooth LE chip which is used on this device.
It would be super cool if you add a support of BTLE to Android by May, 2013...
It would be super cool if you add a support of BTLE to Android by May, 2013...
na...@gmail.com <na...@gmail.com> #145
I al the guy behind the API cookowatch was going to use, the problem is not the luck of drivers, the problem is the lack of exposing it to the developer, I made a working solution you can install on <4.2 based on broadcom api available on Github, but as 4.2 dropped BlueZ I had to drop the project as well.
I'm very upset my self I got in touch with Google team and even they were aware of the issue they couldn't even provide a time frame when 4.2 got released, IMHO switching stack was a very stupid decision, the new stack is way more unstable than BlueZ.
I'm very upset my self I got in touch with Google team and even they were aware of the issue they couldn't even provide a time frame when 4.2 got released, IMHO switching stack was a very stupid decision, the new stack is way more unstable than BlueZ.
cy...@gmail.com <cy...@gmail.com> #146
BLE ! BLE ! BLE ! my god how can google sucks on this and be awesome about the rest
sc...@morrisonlive.ca <sc...@morrisonlive.ca> #147
Got my vote, I really hope this isn't a legal thing.
no...@gmail.com <no...@gmail.com> #148
Well the lack of this officially puts android behind blackberry and iOS. Some response would be nice to hear...
mi...@gmail.com <mi...@gmail.com> #149
I agree -- I am developing the next generation of a medical device with companion app and website. It is a body worn patch that currently communicates with BT 2.1. Current application is on Android, but will likely migrate to iOS because of lacking BLE support and need to run patch on coin cell.
Would love to know the BLE roadmap for Android -- at least for product planning purposes.
Would love to know the BLE roadmap for Android -- at least for product planning purposes.
dc...@gmail.com <dc...@gmail.com> #150
It's ridiculous that Google hasnt support BLE yet, Google please support this
dj...@gmail.com <dj...@gmail.com> #151
Very disappointing. TI has SensorTag for $25 with nice built in sensors and I find out that I have to have an IPhone to try it out. I hang my head in shame! I used to make fun of how inept Msoft was with their implementation of Bluetooth. My guess is the guy that screwed up their Bluetooth is now working for Google.
mo...@gmail.com <mo...@gmail.com> #152
BLE support would be nice.
wi...@gmail.com <wi...@gmail.com> #154
Android 4.2.2 which does fix some bluetooth problems, but still no BLE?? So we have to wait for yet another release?? So by the time it reaches mainstream phones such as the One X or S3 we're well in 2014...
Embarrassing!
Embarrassing!
ro...@gmail.com <ro...@gmail.com> #155
Support for this appears to be one of the major factors in the Nike Fuelband App not being released for Android.
Really sad to see this still isn't available.
Really sad to see this still isn't available.
wo...@gmail.com <wo...@gmail.com> #156
Please update android in general for all phones so it supports the bluetooth low energy profile!!!
wg...@gmail.com <wg...@gmail.com> #157
Yup. Got my Android 4.2.2 update on my galaxy nexus yesterday. STILL can't talk to my Fitbit One.
WHAT THE HECK'S THE DANG DEAL HERE ANYWAYS????
Google: why are you doing your best to turn me into an Apple customer???
WHAT THE HECK'S THE DANG DEAL HERE ANYWAYS????
Google: why are you doing your best to turn me into an Apple customer???
dm...@gmail.com <dm...@gmail.com> #158
Give it up guys! Google obviously doesn't care about the current crop of Galaxy Nexus owners.
This is just another let down from Google. This is an enhancement that could easily be done by google that would put them in good graces with their loyal fan base. Nice to see how much they care about their customers / fans.
Might have to try that Firefox phone after all. Google is doing everything they can to push their most loyal fans away.
This is just another let down from Google. This is an enhancement that could easily be done by google that would put them in good graces with their loyal fan base. Nice to see how much they care about their customers / fans.
Might have to try that Firefox phone after all. Google is doing everything they can to push their most loyal fans away.
ma...@gmail.com <ma...@gmail.com> #159
Could you confirm that the Polar H7 Bluetooth 4.0 Heart Rate will not work without BLE? If not when will BLE be available? Please sort this out Google.
sz...@gmail.com <sz...@gmail.com> #160
We asked, we pleaded, we threatened, we cried. No use.
How about organizing a little revolt: lets all ask every user of all our apps combined in our next updates to star this issue! Maybe having an issue which several million people star would help bring Google to AT LEAST SAYING WTF WAS THE PLAN WITH BLE?!
I don't know if I should cry over, or laugh at Google's silence when it comes to this issue.
I couldn't care less about the new features of JB over ICS (e.g. the spherical photo stitching camera software)! I salute to whoever made the decision to invest manpower into that kind of cr*p instead of BLE support: congratulations Google, it makes us android developers really proud of you!
How about organizing a little revolt: lets all ask every user of all our apps combined in our next updates to star this issue! Maybe having an issue which several million people star would help bring Google to AT LEAST SAYING WTF WAS THE PLAN WITH BLE?!
I don't know if I should cry over, or laugh at Google's silence when it comes to this issue.
I couldn't care less about the new features of JB over ICS (e.g. the spherical photo stitching camera software)! I salute to whoever made the decision to invest manpower into that kind of cr*p instead of BLE support: congratulations Google, it makes us android developers really proud of you!
al...@eps-uk.co.uk <al...@eps-uk.co.uk> #161
How could this possibly be a medium enhancement? Get on it Google, you've already lost a deployment across a large company because of this.
[Deleted User] <[Deleted User]> #162
This is ridiculous - I just bought the nexus 4 and 7 knowing that they had a BT4 chip and now I find out I can't use them with my Fitbit because there's no driver... WTF? Transferring to iphone now,
pe...@gmail.com <pe...@gmail.com> #163
I'll add to the noise. I'm frustrated that Google isn't supporting an industry-wide standard that has many existing applications/devices. Google, as so many others have said: We love Android because you don't do the same crap Apple does. Please don't start now, or Android will quickly be a thing of the past as we all jump ship to the next open platform that comes along.
rr...@gmail.com <rr...@gmail.com> #164
I just purchased a Polar Bluetooth smart HRM and just assumed both my Iphone 5 and Nexus 4 would support it. I was shocked to learn I was wrong. Apple has had the low power bluetooth out for a while. What is the holdup?
ch...@gmail.com <ch...@gmail.com> #165
Dear Google,
Go fuck off for ignoring this issue.
Sincerely,
stopxwatch
Go fuck off for ignoring this issue.
Sincerely,
stopxwatch
kc...@gmail.com <kc...@gmail.com> #166
It's a trend! Pls support BLE.
ly...@gmail.com <ly...@gmail.com> #167
It is well known that the hardware inside the Galaxy Nexus complies with the Bluetooth 4.0 specification. New devices are being created every day that take advantage of the Low Energy profile in the 4.0 specification. There is no reason that the Galaxy Nexus should not support this profile. Please add this functionality.
ro...@mobhi.com <ro...@mobhi.com> #168
I assumed the latest release would address this, I'm very shocked. Photo stitching vs. BLE? No contest. Google has been "trimming the fat" in every other area - how about applying it to the flagship product. I am surprised that Google is not embarrassed that iPhones/iPad/S3 all work with fitbit and Nexus devices don't. Form should follow function! So less photo stitching, and more BLE!
di...@gmail.com <di...@gmail.com> #169
I purchased a Nexus 4 and a Fitbit One, and I was hoping that I could sync the Fitbit One on my Nexus 4, I won't leave the Android ecosphere for this but it's a pitty that I now have to start my Ubuntu 12.10 desktop, launch Virtual Box 4.2.6 and start the virtual windows 7 machine, just because I would be able to sync the fitbit one.
ps...@gmail.com <ps...@gmail.com> #170
This is very poor from Google will now have to ask work for an iPhone 4s or 5 just so I can use a polar H7 heart rate monitor.
el...@gmail.com <el...@gmail.com> #171
Support BLE!!!
ke...@gmail.com <ke...@gmail.com> #172
Guess I'll stick with my iphone. I was moments from clicking "BUY" on a Nexus 4, but not being able to use my Polar H7 with my phone is a deal break for me.
pa...@gmail.com <pa...@gmail.com> #173
This is crazy!
an...@gmail.com <an...@gmail.com> #174
Priority-Medium ... i could cry
i think it'd Priority should got to high !!!
BT4.0 for S3 is written big on it,but BLE isn't supported because of a little driver issue? Isn't it time to fix this bug GOOGLE?
I already ready to pay for such a BLE-DRIVERSAPP if necessary.
At least give us a statement google.
i think it'd Priority should got to high !!!
BT4.0 for S3 is written big on it,but BLE isn't supported because of a little driver issue? Isn't it time to fix this bug GOOGLE?
I already ready to pay for such a BLE-DRIVERSAPP if necessary.
At least give us a statement google.
mi...@gmail.com <mi...@gmail.com> #175
Need it for my fitbit on my Motorola atrix hd lte
[Deleted User] <[Deleted User]> #176
Come on Google, this is crazy. Please add BLE support asap. The company I work for can't release an Android offering because of this issue. We currently only offer an IOS solution and it's killing me.
an...@infusedtech.net <an...@infusedtech.net> #177
need it for my wallet trackr
rn...@whidbey.com <rn...@whidbey.com> #178
+1 for OS support for Bluetooth LE. The project I'm working on for small medical hardware device requires it, which right now means application is hosted on iOS.
da...@gmail.com <da...@gmail.com> #179
PLEASE FIX THIS!! I do not want to get an iphone you are making me consider it!!!!!
ma...@gmail.com <ma...@gmail.com> #180
Waiting for BLE support more than 2 months
pa...@gmail.com <pa...@gmail.com> #181
given my sgs was used as key part to my fitness monitoring, i regret staying with android if they not going to make 4.0 available. Nordic Semiconductor have an app that will tell you if the device can be read. My Note 2 can read my Wahoo Blue HRM but no sports app can utilise 4.0.
ca...@gmail.com <ca...@gmail.com> #182
Our health-related projects chosen Android as their main platform, that was the worst decision ever and forced us to change to iOS and everything runs smooth since then.
We also tried ANT+ via USB host, which is a nice placeholder, until BLE is exposed to develop.
Google pretends to be a big player on the market, but their lack of support and ignorance shows that their main focus is on their core bussiness. They are years behind iOS stability and support, and guess what, they don't care!! :)
We also tried ANT+ via USB host, which is a nice placeholder, until BLE is exposed to develop.
Google pretends to be a big player on the market, but their lack of support and ignorance shows that their main focus is on their core bussiness. They are years behind iOS stability and support, and guess what, they don't care!! :)
ri...@gmail.com <ri...@gmail.com> #183
Dear Google. You sucks.
Six Months wainting for a single piece of software!!! YOU REALLY SUCKS!!!
Microsoft already since 2010 has for Bluetooth 4.0.
Six Months wainting for a single piece of software!!! YOU REALLY SUCKS!!!
Microsoft already since 2010 has for Bluetooth 4.0.
[Deleted User] <[Deleted User]> #184
Type-Enhancement
Priority-Medium
???
I guess if you consider catching up with your biggest competitor, months after the fact a 'medium priority enhancement,' and I'd like to use devices and apps that require BLE, my decision to wait for android or jump ship for iOS (for the first time, I've been a loyal android user since the orig moto droid) is pretty obvious.
Priority-Medium
???
I guess if you consider catching up with your biggest competitor, months after the fact a 'medium priority enhancement,' and I'd like to use devices and apps that require BLE, my decision to wait for android or jump ship for iOS (for the first time, I've been a loyal android user since the orig moto droid) is pretty obvious.
st...@stedaniels.co.uk <st...@stedaniels.co.uk> #185
I bought my Nexus 4 after seeing it had Bluetooth 4 BLE hardware in it, never did I imagine that Google had crippled the device. I made a significant financial investment in the device and I can't use it with what I bought it for.
ya...@gmail.com <ya...@gmail.com> #186
COME ON GOOGLE!!!!!!!!!!
st...@gmail.com <st...@gmail.com> #187
Please fix.
ja...@gmail.com <ja...@gmail.com> #188
After waiting several months for a fix to this issue, I recently returned my Galaxy S3 and my partner's Galaxy Nexus and got iPhones instead. Too bad that Google don't give a sh**
Bye bye Android.
Bye bye Android.
do...@gmail.com <do...@gmail.com> #189
I want my Nexus to support Polar H7 Bluetooth..NOW...
ma...@gmail.com <ma...@gmail.com> #190
Please - i have a fitbit and i want to be able to use it with generic android
sv...@gmail.com <sv...@gmail.com> #191
Please fix it, google
lu...@gmail.com <lu...@gmail.com> #192
PLEASE FIX IT!!!
I need to connect to my just bought heart rate sensor. I don't want to change my phone to buy an Iphone.
I need to connect to my just bought heart rate sensor. I don't want to change my phone to buy an Iphone.
ma...@android.com <ma...@android.com>
da...@gmail.com <da...@gmail.com> #193
Issue has been adressed! Gogo android give us offical BT 4.0 support in the android API!
jd...@gmail.com <jd...@gmail.com> #194
@193 david.go...
More information, please. Gogo?
More information, please. Gogo?
al...@eps-uk.co.uk <al...@eps-uk.co.uk> #195
@david.go - any further information? Is there documentation/API version etc?
da...@gmail.com <da...@gmail.com> #196
#194 look at #192:
Project Member #192 ma...@android.com
(No comment was entered for this change.)
Owner: ma...@android.com
The issue now got a owner! Someone in the android team is looking into this issue, right? (:
Project Member #192 ma...@android.com
(No comment was entered for this change.)
Owner: ma...@android.com
The issue now got a owner! Someone in the android team is looking into this issue, right? (:
ob...@gmail.com <ob...@gmail.com> #197
This is welcome news, indeed!
al...@eps-uk.co.uk <al...@eps-uk.co.uk> #198
Definitely welcome news, as a developer I hope my company and our BT 4.0 clients will be able to put down the !~!@#pad before we travel too far down the road and find ourselves locked into the iPlatform filled with objective-c gibberish, ambiguity and high prices.
tj...@gmail.com <tj...@gmail.com> #199
Great news. But a little to late as for my part. Just sold the N4 and returned to an iPhone.
kj...@gmail.com <kj...@gmail.com> #200
Great news! Want to make sure this works out across the board! Just let us know when!
yv...@gmail.com <yv...@gmail.com> #201
We all need this very soon, we want to use it for new device, like fitbet one...
If you don't do it, is it because you are going to make new device your self like a wacht ?
I all thinks that android word is open and this is why I bouht my nexus 4 (my threed phone under android)...
If you don't do it, is it because you are going to make new device your self like a wacht ?
I all thinks that android word is open and this is why I bouht my nexus 4 (my threed phone under android)...
to...@gmail.com <to...@gmail.com> #202
Please get this fixed/implemented asap!
vi...@gmail.com <vi...@gmail.com> #203
I can't buy a sticknfind.com and neither use my heart rate band because lack of support from Google to BLE even the device suppports it. Very sad. Thinking seriously to switch to Iphone (3 years using and defending android)... :(
ge...@brisco.org.uk <ge...@brisco.org.uk> #204
This is sorely missed
kr...@kr105.com <kr...@kr105.com> #205
There is a LARGE amount of users wanting this feature on Android, why ignore them? WHY GOOGLE WHY?!
kh...@gmail.com <kh...@gmail.com> #206
My sister bought a fitbit and it doesn't work with her top of the line Nexus 4 because lack of BTLE. My iphone found and synced with it immediately....
pa...@gmail.com <pa...@gmail.com> #207
i've decided to sell my note 2 and my wifes sgs iii. moving to windows mobile. Will not move to android again if they going to disable some of the key technologies. What a waste of money.
ke...@gmail.com <ke...@gmail.com> #208
Folks, if you hit the play store, there are various applications that do work with BT4, for example, those from nFR and Simlink.
I have successfully connected to BLE 4 on my Galaxy S 3 with code that I have written. The key was doing a little reflection to call various methods that are hidden (using reflection). There are several libraries that you may need to detect (based on phone). Here is the code to do the detection:
public enum HardwareEnum {
Motorola("android.server.BluetoothGattService"), Broadcom(
"com.broadcom.bt.le.api.BleAdapter"), Csr(
"com.csr.bluetooth.BluetoothExt"), Htc(
"com.htc.android.bluetooth.le"), Samsung(
"com.samsung.bluetoothle.BluetoothLEClientProfile"), None("");
private final String value;
HardwareEnum(String value) {
this.value = value;
}
public String getClassName() {
return value;
}
}
public static HardwareEnum detectHardware() {
HardwareEnum result = HardwareEnum.None;
for (HardwareEnum item : HardwareEnum.values())
try {
Log.i(TAG, "testing:" + item);
Class.forName(item.getClassName());// , false, null);
result = item;
Log.i(TAG, "found:" + item);
return result;
} catch (Exception exc) {
Log.w(TAG, exc.toString());
}
return result;
}
A little more complex, but nothing a serious developer cannot handle.
I have successfully connected to BLE 4 on my Galaxy S 3 with code that I have written. The key was doing a little reflection to call various methods that are hidden (using reflection). There are several libraries that you may need to detect (based on phone). Here is the code to do the detection:
public enum HardwareEnum {
Motorola("android.server.BluetoothGattService"), Broadcom(
"com.broadcom.bt.le.api.BleAdapter"), Csr(
"com.csr.bluetooth.BluetoothExt"), Htc(
"com.htc.android.bluetooth.le"), Samsung(
"com.samsung.bluetoothle.BluetoothLEClientProfile"), None("");
private final String value;
HardwareEnum(String value) {
this.value = value;
}
public String getClassName() {
return value;
}
}
public static HardwareEnum detectHardware() {
HardwareEnum result = HardwareEnum.None;
for (HardwareEnum item : HardwareEnum.values())
try {
Log.i(TAG, "testing:" + item);
Class.forName(item.getClassName());// , false, null);
result = item;
Log.i(TAG, "found:" + item);
return result;
} catch (Exception exc) {
Log.w(TAG, exc.toString());
}
return result;
}
A little more complex, but nothing a serious developer cannot handle.
ke...@gmail.com <ke...@gmail.com> #209
Oops. you do need to include this in your manifest:
<uses-library
android:name="com.broadcom.bt.le"
android:required="false" />
<uses-library
android:name="com.csr.bluetooth.BluetoothExt"
android:required="false" />
<uses-library
android:name="com.htc.android.bluetooth.le"
android:required="false" />
<uses-library
android:name="android.server.BluetoothGattService"
android:required="false" />
<uses-library
android:name="com.samsung.bluetoothle.BluetoothLEClientProfile"
android:required="false" />
<uses-library
android:name="com.broadcom.bt.le"
android:required="false" />
<uses-library
android:name="com.csr.bluetooth.BluetoothExt"
android:required="false" />
<uses-library
android:name="com.htc.android.bluetooth.le"
android:required="false" />
<uses-library
android:name="android.server.BluetoothGattService"
android:required="false" />
<uses-library
android:name="com.samsung.bluetoothle.BluetoothLEClientProfile"
android:required="false" />
la...@gmail.com <la...@gmail.com> #210
Ken, I'm going to attempt what you have suggested on my Galaxy Nexus running 4.2.2 . I can't imagine its really that simple, being that products like the Cuckoo watch have completely abandoned their android clients because of this issue. Their claim was that they could only accomplish using low energy with root. Hopefully this works!
la...@gmail.com <la...@gmail.com> #211
Unfortunately, none of the classes are found on my Galaxy Nexus running android 4.2.2 (paranoid rom). What a shame man... Talk about creating a fork in the road for hardware developers such as I. If I don't use bluetooth low energy, I have to pay for Apple's proprietary "authentication" chip for classic bluetooth. If I use bluetooth low energy, I don't have to have any special "authentication" chip for Apple products, but it won't work on the majority of Android phones. Even if Google does take care of this in Android 4.2.3, most devices still won't be upgradeable to 4.2.3 anytime soon... What a conundrum.... Any suggestions anyone?
sc...@googlemail.com <sc...@googlemail.com> #212
google please implement the support for bluetooth 4.0 at last! I want to go running.
jd...@gmail.com <jd...@gmail.com> #213
@ #208: I can't find anything by or mentioning a developer called "nFR", so I can't comment on that. By Simlink I assume you mean Semilink, but if you look in the thread you'll see that many folks have tried the the BT Smart Scanner and it does not work on their device. Eg, the Galaxy Nexus and Nexus 4. It only works for the Samsung devices listed in the app profile because Samsung added the necessary resources to their builds. Stock Android is left out in the cold.
At this point, I've moved on. My Verizon nexus doesn't even have 4.2.2 yet - by the time any solution gets implemented in time to reach my device, I'll have bought a new phone and melted this one down into rage art.
Fail, Google.
At this point, I've moved on. My Verizon nexus doesn't even have 4.2.2 yet - by the time any solution gets implemented in time to reach my device, I'll have bought a new phone and melted this one down into rage art.
Fail, Google.
d1...@gmail.com <d1...@gmail.com> #214
[Comment deleted]
d1...@gmail.com <d1...@gmail.com> #215
What a shame. My company is going to forget about the S3 for the iphone.
Hurry up google!
Leaving bluez is not the best way as bluez 5.0 and 5.1 are working pretty well.
Hurry up google!
Leaving bluez is not the best way as bluez 5.0 and 5.1 are working pretty well.
ma...@gmail.com <ma...@gmail.com> #216
This is sad. Bluetooth 4.0 has been around since 2010 and google can't implement it in its flagship phone. What a disgrace. I'll give it 1 month before I change all my family's phones to ios.
we...@gmail.com <we...@gmail.com> #217
F U Google!
ti...@gmail.com <ti...@gmail.com> #218
I also want BLE, and I have a Nexus Galaxy. I want a HRM that talks to a watch and the phone. Only the BLE ones do that.
ia...@gmail.com <ia...@gmail.com> #219
Its *probably* Apple that you should be annoyed at. They could have "suggested" to the hardware (silicon) providers to not support other OSs. It is conceivable that they would do that as they have significant sway when you are talking about almost 40 million chips.
ro...@gmail.com <ro...@gmail.com> #220
It is honestly stupid that we can not get support for this. Not only doe it not support the 1.3 profile for metadata when streaming to car receivers and I could not use a fitbit if I would want to or any other nice accessories. This is a reason why companies create accessories for iOS first as they are willing to put in software and hardware support. Get this in.
bo...@gmail.com <bo...@gmail.com> #221
Agreed, this should have happened a long time ago. It's crap like the that makes it har the keep waving the android flag. as much as i dislike the closed system of iOS. their stuff works, while mine doesn't.
cs...@gmail.com <cs...@gmail.com> #222
hey Google - more and more devices are being released that require BLE for syncing. this is a place where you're falling behind iOS and not because the hardware doesn't support it!
c9...@gmail.com <c9...@gmail.com> #223
this issue is still at the status of NEW after 9 months? I'd call that as unbelievable!
bk...@coastsystems.net <bk...@coastsystems.net> #224
Star for ble support asap. Whats the hold up?
la...@gmail.com <la...@gmail.com> #225
Yepp Yepp, Google wake up! This should be an easy one to fix
an...@sambade.com <an...@sambade.com> #226
BLE on Galaxy Nexus and Nexus4... please!
fa...@gmail.com <fa...@gmail.com> #227
I agree it's unbelievable (and unacceptable) Android doesn't have BLE support yet... And, supposing they implement this support just on version 4.3 or 5.0, there will be a whole generation of cell phones with the BLE hardware present and without BLE support. I have a Galaxy S3 Mini, and just bought a Polar H7 HRM, which is useless for me now...
no...@gmail.com <no...@gmail.com> #228
Its hard to believe that we will soon be coming up on a year for this issue to be open and still there is no indication if this is even being considered for key lime pie. The big switch on bluetooth stack was horrific enough but it is ludicrous to hold back information like this as it affects your community of developers.
ma...@gmail.com <ma...@gmail.com> #229
Missing also the support for BLE by Android. I do not understand what is going on there. Please at least give us a rough timeline when it will be available!!!!
la...@gmail.com <la...@gmail.com> #230
I've been following this thread for a long time now and it has become very apparent that no one at Google is interested in supplying us with any information concerning their development (or lack of it) of LE support. As a hardware developer, trying to develop a Bluetooth Low Energy product, this is extremely frustrating. But we also have to face the fact that even if Google does provide compatibility in the next Android update, unless you are a GSM galaxy nexus user or load custom roms on your device (provided you rooted it), it will not be instantly available for most users. Google's lack of interest in adding support for this, FOR SO LONG, means that, as a hardware developer, it really doesn't matter if Google released an update tomorrow (because the majority of my users won't be able to update until their carriers provide an update.) Sure, I can have fun tinkering on my own device, since I of course play with custom roms, but thats merely a novelty from a business perspective. This means, if I want to support LE and Android, I will have to use a Dual Mode BT 4.0 radio in my hardware, and those costs get passed onto my customer. What a shame...
si...@gmail.com <si...@gmail.com> #231
It's really a shame! I do hope that BLE will be soon supported in Software!
sm...@gmail.com <sm...@gmail.com> #232
I have a Galaxy Nexus and Nexus 7. I'll never part with them as they are amazing products. I hope BLE will be added eventually!
th...@gmail.com <th...@gmail.com> #233
So sad to see my gshock gb-6900 waste away with no BLE support/api for my razr maxx...
fa...@gmail.com <fa...@gmail.com> #234
If you have a Galaxy S3 or other phone that's not running stock Android, OEMs like Samsung have enabled BT 4.0 on your devices. That's why you see BT syncing with the Fitbit for example on the GS3/Note 2.
ro...@tracygov.org <ro...@tracygov.org> #235
Google I want to sync my fitbit... First Motorola jacks me on my atrix with no updates and now I find out my Nexus 4 doesn't support BLE... Flagship phone??????
ol...@gmail.com <ol...@gmail.com> #236
Maybe there are some "licensing issues" preventing Google to make use of the Samsung SWB-B42 BT4- capable chip built into the now deprecated Galaxy Nexus phone. Fair enough.
But the lack of any BT4 capable API in the current Android implementation is out of all reason. As such it fosters platform fragmentation with OEMs providing their own native extensions.
This puts customers in the unpleasant situation to weigh the benefits of not having to wait for OEM updates on the most recent Android versions (not seldom getting no updates at all) versus getting full access to all the hardware goodies which we are carrying around anyway.
For us developers, a decision has to be made between supporting every (contemporary) Android device - which directly translates into potential bigger markets - versus OEM locked in versions which may or may not work on our customers devices after the most recent vendor update.
Which - in the specific case of fitness- related software - may lead us to settle with a competing platform from Cupertino with standardized HW and Software and BT4 access.
But the lack of any BT4 capable API in the current Android implementation is out of all reason. As such it fosters platform fragmentation with OEMs providing their own native extensions.
This puts customers in the unpleasant situation to weigh the benefits of not having to wait for OEM updates on the most recent Android versions (not seldom getting no updates at all) versus getting full access to all the hardware goodies which we are carrying around anyway.
For us developers, a decision has to be made between supporting every (contemporary) Android device - which directly translates into potential bigger markets - versus OEM locked in versions which may or may not work on our customers devices after the most recent vendor update.
Which - in the specific case of fitness- related software - may lead us to settle with a competing platform from Cupertino with standardized HW and Software and BT4 access.
og...@gmail.com <og...@gmail.com> #237
This is really frustrating since more and more BLE devices are pushed to the market; Fitbit Zip, Fitbit One, Fitbit Flex, Pebble Smartwatch, Jawbone Up.. Let's hope someone over Engadget or The Verge covers this, i bet they will support it within a month if that happens.
la...@gmail.com <la...@gmail.com> #238
Oliver, you repeat my stated comments from above almost verbatim. I'm obviously not the only person who has run into these various implementation issues...
wo...@gmail.com <wo...@gmail.com> #239
It's simple, modern phones need BLE support, ESPECIALLY flagship devices like the Nexus brand!!!
Google, get your act together and fix this, ASAP!
Google, get your act together and fix this, ASAP!
na...@gmail.com <na...@gmail.com> #240
This really needs to be fixed soon, as a lot of developers are creating cool BLE apps...
ch...@gmail.com <ch...@gmail.com> #241
we need Nexus4 BT4 with BLE, Bluetooth Smart and Bluetooth Smart Ready !!!!!!
ro...@googlemail.com <ro...@googlemail.com> #242
Just pledged on RFDuino Kickstarter. It ses BTLE and surprised and disappointed to find my Galaxy Nexus doesn't support it.
Coming across this thread dents the Google brand for me. Connected objects is one of the most exciting things to happen to computing in the last 20 years and Google has to catch this wave.
Coming across this thread dents the Google brand for me. Connected objects is one of the most exciting things to happen to computing in the last 20 years and Google has to catch this wave.
cj...@gmail.com <cj...@gmail.com> #243
As annoying as it is that I can't sync my Fitbit to my Gnex, I guess I understand that BT4 is sort of a new feature and all that. But what is unforgivable is the total silence from Google on this issue. Can we get an update at least? An ETA? Heck, even empty assurances that someone, somewhere, has acknowleded the issue and sees it as a priority would be appreciated at this point.
ma...@longhome.co.uk <ma...@longhome.co.uk> #244
The worst aspect of this is that, should BLE be supported in Key Lime Pie, as developers we will still need to include separate implementations for HTC, Samsung, Moto (and other) devices which haven't or will never upgrade their software to Key Lime.
This means I'm going to forever need this kind of rubbish (no offence to the developer, we shouldn't HAVE to do this):
Motorola("android.server.BluetoothGattService"), Broadcom(
"com.broadcom.bt.le.api.BleAdapter"), Csr(
"com.csr.bluetooth.BluetoothExt"), Htc(
"com.htc.android.bluetooth.le"), Samsung(
"com.samsung.bluetoothle.BluetoothLEClientProfile"), None("");
We all know that 12 months down the line, after KLP has been released there are still going to be a bunch of phones with BLE support, that are still running <=4.2.
On top of that, heart rate monitors, for example can be really tricked to develop and test for. To develop and test this, small indie developers who only earn a few bucks a month would need to buy 6 phones, just to develop and test this functionality. It's an utter joke.
This means I'm going to forever need this kind of rubbish (no offence to the developer, we shouldn't HAVE to do this):
Motorola("android.server.BluetoothGattService"), Broadcom(
"com.broadcom.bt.le.api.BleAdapter"), Csr(
"com.csr.bluetooth.BluetoothExt"), Htc(
"com.htc.android.bluetooth.le"), Samsung(
"com.samsung.bluetoothle.BluetoothLEClientProfile"), None("");
We all know that 12 months down the line, after KLP has been released there are still going to be a bunch of phones with BLE support, that are still running <=4.2.
On top of that, heart rate monitors, for example can be really tricked to develop and test for. To develop and test this, small indie developers who only earn a few bucks a month would need to buy 6 phones, just to develop and test this functionality. It's an utter joke.
se...@gmail.com <se...@gmail.com> #245
sticknfind has started shipping. Sad when hardware manufacturing moves faster than software updates.
sc...@googlemail.com <sc...@googlemail.com> #246
Really Google.... Really?
[Deleted User] <[Deleted User]> #247
Comeon Google, I've got my Pebble Watch paired with my GNex, but it isn't doing my phone's battery life any favors. My wife's GS3 on the other hand, barely notices any drain.
ss...@gmail.com <ss...@gmail.com> #248
I really need this feature so my Fitbit ONE will sync with my Motorola Electrify M.
thanks,
Shannon
thanks,
Shannon
tr...@prasser.com <tr...@prasser.com> #249
[Comment deleted]
bi...@gmail.com <bi...@gmail.com> #250
I was hoping to use Bluetooth Smart with my Samsung Galaxy Note 2. But, was disappointed to see it was not implemented. I wanted to use a Polar H7 Smart heart rate sensor with my fitness app. I almost moved to an Apple device for this functionality. But, at the last moment decided to try the Zephyr HxM standard bluetooth product and it worked out for me. Google ... please get this low energy bluetooth working ... thanks for listening.
ka...@gmail.com <ka...@gmail.com> #251
This is extremely frustrating! Why isn't the lack of this specified clearly in the product specs ?
I wanted to buy a Polar H7 and it's ridiculous that a phone that allegedly supports BT 4.0 (Nexus 4) doesn't actually do it in full. And one have to find it out by digging deep in the issue repository.
I wanted to buy a Polar H7 and it's ridiculous that a phone that allegedly supports BT 4.0 (Nexus 4) doesn't actually do it in full. And one have to find it out by digging deep in the issue repository.
sh...@googlemail.com <sh...@googlemail.com> #252
I'd like to have this too Bluetooth maybe old tech but its as essensial to me as wi-fi is,as I have several Android devices just bought a Nexus 4 and it advertises Bluetooth 4 and its not fully implemented so my heart rate monitor won't function.
bi...@gmail.com <bi...@gmail.com> #253
Just purchased the Wahoo KICKR which uses Bluetooth Smart Energy to connect to it. Would like to see this working on Android, weird that it doesn't given the datasheets all say that it's supported!
lo...@gmail.com <lo...@gmail.com> #254
Please fix the BT-stack Google.
jo...@gmail.com <jo...@gmail.com> #255
Waiting for it!
kb...@gmail.com <kb...@gmail.com> #256
Come on google. This should really be supported properly...
ed...@gmail.com <ed...@gmail.com> #257
As a personal trainer, I recommend my clients monitor their Heart Rate Variability (HRV) with a monitor like the Polar H7. Unfortunately, I can only do this for clients with an iPhone. There are other, more complicated routes, one can use with an android device, but bluetooth smart Heart Rate Monitors are the future, and Android is being left behind.
ha...@gmail.com <ha...@gmail.com> #258
WTF Google. You disappoint. Even the Microsofties managed to implement a (lousy) BT40 Stack...
vi...@gmail.com <vi...@gmail.com> #259
As developer of new technologies ... WE NEED Bluetooth Low Energy WORKING ON ANDROID 4.2
THANKS
THANKS
ra...@gmail.com <ra...@gmail.com> #260
Google Kindly Fix this issue and release an API for bluetooth 4.0 BLE .. Kindly to do it at the earliest possible Markets are flooded with device using Bluetooth 4.0 . Owning a nexus 4 shouldnt be a curse in this repect
yu...@gmail.com <yu...@gmail.com> #261
I need!
ya...@gmail.com <ya...@gmail.com> #262
Ridiculous, I buy the Nexus 4 with bluetooth 4.0 and android does not support it, this sucks ... google ..
jo...@gmail.com <jo...@gmail.com> #263
Just bought Polar H7 HR monitor and seeing I have a BT4 phone... the flagship Nexus 4 I didn't even research this thinking this was no issue... Guess I was wrong... PLZ fix...
dh...@gmail.com <dh...@gmail.com> #264
The only thing I can't believe is how silent Google sits after I read all these comments. Quite disturbing. I am glad to see that someone is assigned to the ticket, but still. It would be nice to know where this sits (timeline estimates). There are developers out here wondering at this very moment if we need to roll our own native libraries based on devices we'd like to support, should we use open source BTLE projects, or wait a month or two and invest our time in other endeavors with hopes that an upcoming Android OS fix/version will support this out of the box in the API. Perhaps abandon this platform altogether if we need BTLE and don't have the resources to support the effort?
Innovation in secret, fine. However, you are behind the game on this one Google, and being silent on this particular issue is like forcing all your customers to take a bitter pill.
Innovation in secret, fine. However, you are behind the game on this one Google, and being silent on this particular issue is like forcing all your customers to take a bitter pill.
la...@gmail.com <la...@gmail.com> #265
I continue to be stunned by the silence on Google's part concerning BLE. I won't blab on, as I've already given my 2 cents several times in this thread, but man Google. You have always had my respect, but after MONTHS of silence on this issue, I've finally realized you guys aren't quite as down-to-earth and consumer-oriented as I thought. Ill never go to Apple, so i wont make that threat, but you have damaged your reputation in my mind. A single response from anyone at Google would suffice. If not just to tell us all to screw off...
al...@gmail.com <al...@gmail.com> #266
Kindly support BLE so we can start using our personal trackers the way they were meant to be! Thanks.
to...@gmail.com <to...@gmail.com> #267
[Comment deleted]
be...@gmail.com <be...@gmail.com> #268
Need this feature for HRM on Nexus 4
ki...@gmail.com <ki...@gmail.com> #269
Are there any states attorneys listening out there? Seems reasonable that so many of us purchased devices expecting BTLE, that class action suits ought to be filed. Sorry, but some or any feedback from Google would have gone a long way to quell this type of unrest and sentiment.
st...@gmail.com <st...@gmail.com> #270
I want this!
be...@gmail.com <be...@gmail.com> #271
Bought the Nexus 4 under the impression that it had BTLE accessible to me. Please consider implementing this feature in your next update!
re...@gmail.com <re...@gmail.com> #272
Bought the Samsung note 2 under the impression that it had BTLE accessible to me. Please consider implementing this feature in your next update so my Mio Alpha stapless heart rate monitor can feed data to my running app
mi...@gmail.com <mi...@gmail.com> #273
My Polar H7 is not working with my Nexus 4.
My old iPhone had no problems with it.
I am really happy with my nexus, but I think about returning to Apple because nothing happening.
My old iPhone had no problems with it.
I am really happy with my nexus, but I think about returning to Apple because nothing happening.
mi...@gmail.com <mi...@gmail.com> #274
enhancement?
priority = medium?
sorry, that is unacceptable.
either remove 4.0 compatibilty from all documentation or do what you claim.
selling a product that does not live upto its description makes you liable, puts you in a bad light and just makes people buy apple...
neither of which you canafford or want.
fix it
priority = medium?
sorry, that is unacceptable.
either remove 4.0 compatibilty from all documentation or do what you claim.
selling a product that does not live upto its description makes you liable, puts you in a bad light and just makes people buy apple...
neither of which you canafford or want.
fix it
ha...@gmail.com <ha...@gmail.com> #275
Please add this feature
al...@gmail.com <al...@gmail.com> #276
Same as others : I want to use a Polar H7 with my Nexus 4.
Should by a high priority if you keep claiming BT4 support.
And PLEASE, pretty please, do comment and tell us the status of this enhancement, target version, etc.
Should by a high priority if you keep claiming BT4 support.
And PLEASE, pretty please, do comment and tell us the status of this enhancement, target version, etc.
gi...@gmail.com <gi...@gmail.com> #277
Please add this feature....
ju...@gmail.com <ju...@gmail.com> #278
We are all idiots meekly 'asking' Google to fix this - this thread has been open for nearly a year and...NOTHING! Time to hit their facebook wall and a tweet like mad.
ra...@gmail.com <ra...@gmail.com> #279
I was really disappointed to learn that my N4 can't sync wirelessly with a fitbit or my HRM. It's crazy that the iphone can do it but the N4 can't! After looking at this thread it is shocking that google isn't doing anything.
Does anyone know if I can sync a fitbit to my N4 using a USB & still use the android app?
Does anyone know if I can sync a fitbit to my N4 using a USB & still use the android app?
mi...@googlemail.com <mi...@googlemail.com> #280
Bluetooth Low Energy HeartRate is supported by this Android-App --> googlePlay-store.
ONLY for Bluetooth 4.0-smartphones (e.g. MOTOROLA RAZR) with Bluetooth 4.0 (=Bluetooth Low Energy) Hardware AND Software-SUPPORT!!
Bluetooth Low Energy HeartRate Monitor: Stable Version
Bluetooth Low Energy = Bluetooth 4.0 = Bluetooth Smart.
Successfully tested with:
- Motorola RAZR-XT910
AND
- chest strap Polar H7.
ONLY for Bluetooth 4.0-smartphones (e.g. MOTOROLA RAZR) with Bluetooth 4.0 (=Bluetooth Low Energy) Hardware AND Software-SUPPORT!!
Bluetooth Low Energy HeartRate Monitor: Stable Version
Bluetooth Low Energy = Bluetooth 4.0 = Bluetooth Smart.
Successfully tested with:
- Motorola RAZR-XT910
AND
- chest strap Polar H7.
ol...@gmail.com <ol...@gmail.com> #281
Just wanted to let you know that I finally fixed my ongoing N4 & GaNe BT4 LE issues w/ the Polar H7 Sensor even without any Google intervention: bought an iPhone5 and it simply works.
pe...@gmail.com <pe...@gmail.com> #282
Why is this feature missing in Android? There must be a good reason.
do...@gmail.com <do...@gmail.com> #283
WTF Google?
wi...@gmail.com <wi...@gmail.com> #284
So many low energy devices are going to be released this year. Please update to support LEP for Bluetooth! I'm using a Nexus 4.
an...@gmail.com <an...@gmail.com> #285
seems google doesn't care.... pretty piss poor... maybe tizen will be better.
br...@gmail.com <br...@gmail.com> #286
Just received my IndieGoGo perk of 6 Stick-n-Find stickers, and I can't use them even with a flagship device like the nexus 4. Because of BLE missing in Android, I'm left holding the bag on some useless electronics.
What is the hold up on this?
What is the hold up on this?
es...@gmail.com <es...@gmail.com> #287
I also got my 6 pack of Stick-n-find devices delivered this morning and I am now discovering that I don't have any android devices that I can use them with :(
This is ridiculous.
This is ridiculous.
de...@gmail.com <de...@gmail.com> #288
Ditto, received stick-n-find stickers today and discovered it doesn't work on a Nexus phone. I have to use my iPad instead. Too bad I don't carry a bloody tablet with me everywhere I go.
al...@gmail.com <al...@gmail.com> #289
Please include this in AOSP, a lot of manufacturers are making their own libraries for BLE and making it a nightmare for products like Stick n Find to support.
lu...@gmail.com <lu...@gmail.com> #290
Please add support for Bluetooth LE.
It can makes a difference when using things like strava/endomondo and heart rate monitors.
It can makes a difference when using things like strava/endomondo and heart rate monitors.
rr...@gmail.com <rr...@gmail.com> #291
Could someone from Google please update us on the status of this? If this will be fixed in a month or two I am good to hold off using my HR monitor, if it is going to be longer I will just switch to an Iphone. Please give us an Update!
da...@gmail.com <da...@gmail.com> #292
Google - My FitBit is useless syncing on trips where I can't bring my laptop everywhere. What the hell? I just bought a Nexus 4 and am already thinking of switching back to my iPhone 4S. GIVE US BLE!
mi...@googlemail.com <mi...@googlemail.com> #293
forget iPhone :-) --> here is the first Android-App for BLE (Android 2.3 ... Android 4.2):
this Android-APP with Name "Bluetooth Low Energy HeartRate Monitor" is the 1st worldwide unique stable HRM-App, also supporting Polar H7 --> look googlePlay-store.
BUt ONLY for Bluetooth 4.0-smartphones (e.g. MOTOROLA RAZR) with Bluetooth 4.0 (=Bluetooth Low Energy) Hardware AND Software-SUPPORT by ble-stack!!
Successfully tested with Motorola RAZR-XT910 AND chest strap Polar H7.
this Android-APP with Name "Bluetooth Low Energy HeartRate Monitor" is the 1st worldwide unique stable HRM-App, also supporting Polar H7 --> look googlePlay-store.
BUt ONLY for Bluetooth 4.0-smartphones (e.g. MOTOROLA RAZR) with Bluetooth 4.0 (=Bluetooth Low Energy) Hardware AND Software-SUPPORT by ble-stack!!
Successfully tested with Motorola RAZR-XT910 AND chest strap Polar H7.
de...@gmail.com <de...@gmail.com> #294
My Nexus 4 isn't compatible with Stick-n-find because you haven't added the driver support. Fix this please. There is no reason you should be behind like this.
dh...@gmail.com <dh...@gmail.com> #295
I have a question for anyone who was successful in establishing an LE connection using the Samsung Galaxy SIII and their undocumented API.
My question is this:
Is bonding necessary prior to scanning a profile for characteristics?
If I do not create a bond first, then onGattConnect is never invoked, so my profile/services are never initialized appropriately. The createBond method is available through reflection only. I dislike createBond() because it's flaky for me; sometimes it works, sometimes I get auth rejected (for the pairing attempt) and then it works, and sometimes I get auth rejected and it never bonds/connects. In some cases I have to toggle bluetooth on and off, or turn on airplane mode, to clear the connection state (BOND_BONDING) and try again.
In an event where I do establish a bond, the gatt connection remains open, and I can discover characteristics. Usually the first pass comes back with NULL values, and then the second discovery onward I start seeing all values for each characteristic for a given UUID. If I do not establish a bond, connectLE fails, or I can try to discovery characteristics, but I get a failure from the GATT proxy that DiscoverCharacteristics is an UnknownMethod.
So once again, is bonding necessary to perform a discovery scan, or is there some other means used to establish a target (GATT server) in which I can perform a discovery without using the createBond() method, which is unreliable for me and probably because something isn't set up right because this API is completely undocumented (and as far as I can tell, unsupported).
Many thanks.
My question is this:
Is bonding necessary prior to scanning a profile for characteristics?
If I do not create a bond first, then onGattConnect is never invoked, so my profile/services are never initialized appropriately. The createBond method is available through reflection only. I dislike createBond() because it's flaky for me; sometimes it works, sometimes I get auth rejected (for the pairing attempt) and then it works, and sometimes I get auth rejected and it never bonds/connects. In some cases I have to toggle bluetooth on and off, or turn on airplane mode, to clear the connection state (BOND_BONDING) and try again.
In an event where I do establish a bond, the gatt connection remains open, and I can discover characteristics. Usually the first pass comes back with NULL values, and then the second discovery onward I start seeing all values for each characteristic for a given UUID. If I do not establish a bond, connectLE fails, or I can try to discovery characteristics, but I get a failure from the GATT proxy that DiscoverCharacteristics is an UnknownMethod.
So once again, is bonding necessary to perform a discovery scan, or is there some other means used to establish a target (GATT server) in which I can perform a discovery without using the createBond() method, which is unreliable for me and probably because something isn't set up right because this API is completely undocumented (and as far as I can tell, unsupported).
Many thanks.
[Deleted User] <[Deleted User]> #296
no...@gmail.com <no...@gmail.com> #297
Re:Sweani
Good link, but this level of support MUST be in the AOSP, if it is only implemented at the manufacturer level you will kill any development for it since that will be impossible to support.
I thought android was all about being open, if something as simple as this cannot be acknowledged from a Google rep then this is a bad road we are following and I for one will be moving on (there are other OS's then this)..
According to Sticknfind "The App for the Nexus will be ready at the end of May pending Google’s I/O v5 conference announcements" Now if they know some insider information about what will be announced at google IO that google has not told the general public remains to be seen, this could simply be speculation on their part as well.
Good link, but this level of support MUST be in the AOSP, if it is only implemented at the manufacturer level you will kill any development for it since that will be impossible to support.
I thought android was all about being open, if something as simple as this cannot be acknowledged from a Google rep then this is a bad road we are following and I for one will be moving on (there are other OS's then this)..
According to Sticknfind "The App for the Nexus will be ready at the end of May pending Google’s I/O v5 conference announcements" Now if they know some insider information about what will be announced at google IO that google has not told the general public remains to be seen, this could simply be speculation on their part as well.
ad...@obledesign.com <ad...@obledesign.com> #298
I too have a Fitbit one and am very disappointed that I can't sync it with my Nexus 4 even though it has the required hardware.
Please make this a priority for the next version of Android.
Please make this a priority for the next version of Android.
an...@gmail.com <an...@gmail.com> #299
What in the.... Android seriously doesn't support BLE? I'm just stunned that this is even possible. iOS devices have had it for over a year. There is really no excuse for this, MANY new devices are taking advantage of BLE. This is essentially a required feature.
ol...@gmail.com <ol...@gmail.com> #300
Still now news from Google...come on. I saw the inital google glass from the FCC filling, bluetooth 4.0..but the final specs bluetooth 2.1 COME ON!!!!!! So i think we will not have BLE in Android 5.0.
ks...@gmail.com <ks...@gmail.com> #301
Please blue tooth 4.0BLE !!!
to...@gmail.com <to...@gmail.com> #302
My first smart phone was a G1, my second an iPhone, my third a Samsung Galaxy, then a Nexus 4. My next one won't be an Android device if Google doesn't bring BLE to Android. Hint to Google, I will be selecting my next phone in about a month and I'm tired of waiting for Google to get onboard the BLE ship.
th...@googlemail.com <th...@googlemail.com> #303
!!! Please address this issue. Currently using Google's flagship device Nexus 4 and the lack of BLE is not acceptable! If google wants to be a real player in the market they need to step up their mark! Apple integrated this tech over 18 months ago !!!
fo...@gmail.com <fo...@gmail.com> #304
As an avid cyclist, it pained me to have to switch to the iPhone for my Wahoo Cadence sensor, which uses BLE. As I understand it, a lot more peripherals, such as fitness, watches and more are looking at BLE. I would love to be able to switch back to my GS3 and use them!
ad...@gmail.com <ad...@gmail.com> #305
I can't believe there has been no word on this from Google let alone any update. Not a good feeling when the details just get left behind in the rush.
ph...@gmail.com <ph...@gmail.com> #306
I
be...@gmail.com <be...@gmail.com> #308
Signed. Galling that Google is so far behind on this issue, especially when the Nexus 4 has the hardware to support it. My purchase of the Nexus was strongly influenced by the inclusion of Bluetooth 4.0 (for use with the Stick N Find tags), only to discover that it doesn't work with them.
ap...@gmail.com <ap...@gmail.com> #309
Android needs to support the full range of Blutooth 4.0 capabilities, including Bluetooth Low Energy (BLE), which supports devices in the areas of consumer wellness, Home Automation, Security & Proximity, Sports & Fitness (heartrate monitors), Entertainment (remote controls), and smart energy. These bluetooth smart functions are one of the few technologies where the iPhone has surpassed Android devices, and will continue to do so until Google makes bluetooth smart technology standard on its devices. To remain competitive in this market, such technology must be incorporated AND usable in Google devices.
bu...@gmail.com <bu...@gmail.com> #310
please enable this so we all can use the same equipment all those Apple fellas can...
ro...@gmail.com <ro...@gmail.com> #312
I've got a Sensordrone, a Thermal Imaging device and a Pebble Smartwatch, they all support BT4.0 and could allmprofit greatly it Android fully supports BT4.0 with BLE
sa...@stowgood.com <sa...@stowgood.com> #313
The lack of support for this really shocks me.
jz...@gmail.com <jz...@gmail.com> #314
I'd like this feature for my Fitbit One
ce...@gmail.com <ce...@gmail.com> #315
BT LE is becoming more and more popular with sport/fitness equipment. It is ridiculous that there is no support for this in android. Seriously...
bi...@gmail.com <bi...@gmail.com> #316
Galaxy S4 still does not support BLE despite packaging stating it does. My Polar H7 is still of no use. C'Mon Google. Lift your game.
dh...@gmail.com <dh...@gmail.com> #317
@bigm
The Galaxy S4 *does* support LE, but it's probably not going to read the Polar H7 until Polar releases an updated HRM application for the S4 running Android 4.2. The reason for this is Samsung's BLE SDK is different on the S4 so the old app is probably no longer compatible.
The Galaxy S4 *does* support LE, but it's probably not going to read the Polar H7 until Polar releases an updated HRM application for the S4 running Android 4.2. The reason for this is Samsung's BLE SDK is different on the S4 so the old app is probably no longer compatible.
bi...@gmail.com <bi...@gmail.com> #318
dh.LoTan. Thanks for that. My understanding was that BLE devices would be visible under the bluetooth device list once BLE was natively supported in Android. Or if the manufacturer released their own working BT4.0 stack. ala Motorola Razr
I also understand manufacturers can write apps using the Samsung BLE SDK and yes, Polar should/could do this for SGS3/SGS4 but it requires developers to write different applications for each Android piece of hardware rather than just for the operating system.
My feeling is that Google should a. include the native support as per this change request and b. Samsung should provide a bluetooth stack which replaces the Android one so that all Bluetooth Smart devices work straight away as per the marketing on the boxes. Smart ready.
I could be wrong on all this though. cheers
I also understand manufacturers can write apps using the Samsung BLE SDK and yes, Polar should/could do this for SGS3/SGS4 but it requires developers to write different applications for each Android piece of hardware rather than just for the operating system.
My feeling is that Google should a. include the native support as per this change request and b. Samsung should provide a bluetooth stack which replaces the Android one so that all Bluetooth Smart devices work straight away as per the marketing on the boxes. Smart ready.
I could be wrong on all this though. cheers
bj...@gmail.com <bj...@gmail.com> #319
[Comment deleted]
es...@gmail.com <es...@gmail.com> #320
Today I was really shocked when I found BLE is not supported in Android. I have a Nexus 4 and wanted to develop an app using the cool Bluetooth SensorTag from Texas Instruments. The number of BLE devices is rapidly growing, and it's just stupid the most open mobile platform (at least until Ubuntu/FirefoxOS prove to be valid platforms) can't deal with them in a standard way.
Please add BLE support!!! Or at least clarify if there will or will not be BLE support in the near future!!!
Please add BLE support!!! Or at least clarify if there will or will not be BLE support in the near future!!!
da...@gmail.com <da...@gmail.com> #321
VERY DISAPPOINTED to learn that my Google Flagship NEXUS 4 won't work with the Flexbit health monitor. This is my first smartphone purchased in part, because I wanted the benefits of a health monitor peripheral device. I assumed that buying Google's Flagship device with the latest operating system and guaranteed Android OS updates would ensure compatibility. Wow. I am an Apple / Mac user for many years who decided to give Google / Android a try. I have been mostly pleased with my Nexus 4 / Android Jelly Bean experience thus far. But this lack of response to you an obvious issue makes me think I may have made a mistake. Please Google, let us know that you are at least aware of this issue and tell us what your intentions and timeframe are to remedy it !!!
ea...@gmail.com <ea...@gmail.com> #322
Please add support for this as I am looking forward to all the new devices coming out - specifically using the fitbit flex with my nexus 4. I vowed never to buy an iPhone, but if there is no support soon (~1-2 months) for this, I may have to.
jo...@gmail.com <jo...@gmail.com> #323
Matthew Xie, responsible for Bluetooth at Android will speak on this matter at I/O may 15th.
He says it in this thread:
"Hi
You will get updated during Google IO on the support of Bluetooth Low Energy of next Android release. I cannot reveal more information at this time.
Thanks
Matthew"
https://groups.google.com/forum/m/#!msg/android-platform/CYtxCmtZ-WI/aIzBq7KbKVUJ
So there is some hope. My polar h7 wants to be put to good use...
He says it in this thread:
"Hi
You will get updated during Google IO on the support of Bluetooth Low Energy of next Android release. I cannot reveal more information at this time.
Thanks
Matthew"
So there is some hope. My polar h7 wants to be put to good use...
an...@gmail.com <an...@gmail.com> #324
as soon as the fitbit flex arrives, I'm going to buy a Samsung phone as they have BLE support (and fitbit support Samsung's BLE implementation)
Guess this is the first and last nexus device I buy :(
Guess this is the first and last nexus device I buy :(
jj...@gmail.com <jj...@gmail.com> #325
I have several devices-stick n find, dive sensors (scuba), fitbit flex all of which use BT 4.0
am looking at switching over to iphone if can't use any of them on my android devices
Will Nexus 7 support BT 4.0?
Thanks
am looking at switching over to iphone if can't use any of them on my android devices
Will Nexus 7 support BT 4.0?
Thanks
pa...@gmail.com <pa...@gmail.com> #326
This should be standard, not something that needs to be requested.
pe...@gmail.com <pe...@gmail.com> #327
From sgs3 with android 4.1.2. I want to see ble support in one of next android versions as well.
Peter
Peter
jp...@gmail.com <jp...@gmail.com> #328
My Nexus 4 and my new Fitbit Flex would really like to play together. Cmon folks :)
gr...@gmail.com <gr...@gmail.com> #329
Please add Btle asap!
an...@gmail.com <an...@gmail.com> #330
Please please please enable BLE!
ma...@gmail.com <ma...@gmail.com> #331
I managed to find a Fitbit Flex at a Target when shopping for something else.
Now I would love to be able to get it syncing with my Nexus 4!
Come on Google!
Now I would love to be able to get it syncing with my Nexus 4!
Come on Google!
rr...@gmail.com <rr...@gmail.com> #332
Any news on this from Google IO? This has got to be a priority at this point. It has been months. Google, I would have thought with the talent of your developers you could get this done within days, NOT MONTHS.
jo...@gmail.com <jo...@gmail.com> #333
Not yet. There is a bluetooth session later today. Hopefully some news comes from that.
https://developers.google.com/events/io/sessions/326240948
la...@gmail.com <la...@gmail.com> #334
Hardly authoritative but I ran across this a little while ago:
Huge: Android 18+ will support Bluetooth low energy profiles!
https://plus.google.com/115694705577863745195/posts/PN7fEbBTQCb
Did anybody attend the session?
Huge: Android 18+ will support Bluetooth low energy profiles!
Did anybody attend the session?
ro...@gmail.com <ro...@gmail.com> #335
The session was not live streamed. I also have not been able to find out anything about what went on in there.
The session ratings are not great though...
The session ratings are not great though...
la...@gmail.com <la...@gmail.com> #336
It's official. BLE is coming!
No video yet. No word on timeframe.
https://plus.google.com/116110604589325140832/posts
Sara Sinclair Brody
Shared publicly - 4:28 PM
#io13
During today's #io13 talk we announced that Android API version 18 (which will be landing in a few short months) will have developer APIs for Bluetooth Low Energy and AVRCP 1.3.
The video of the talk should be posted soon, so you can see a preview of the APIs we shared.
https://developers.google.com/events/io/sessions/326240948
No video yet. No word on timeframe.
Sara Sinclair Brody
Shared publicly - 4:28 PM
#io13
During today's #io13 talk we announced that Android API version 18 (which will be landing in a few short months) will have developer APIs for Bluetooth Low Energy and AVRCP 1.3.
The video of the talk should be posted soon, so you can see a preview of the APIs we shared.
je...@gmail.com <je...@gmail.com> #337
I need this ASAP, please!!!
ro...@gmail.com <ro...@gmail.com> #338
A few short months does not sound too promising, but better than never... ;)
ma...@gmail.com <ma...@gmail.com> #339
Please let it not become a few long months !!!
rr...@gmail.com <rr...@gmail.com> #340
Its absolutely shocking to hear that it may be months away. WTF have they been doing since this thread started IN JUNE of 2012??????????????????????
Google is dropping the ball big time on this.
Google is dropping the ball big time on this.
jo...@gmail.com <jo...@gmail.com> #341
ne...@gmail.com <ne...@gmail.com> #342
Yea. She replied to me and said it wont receive the update. Looks like I will be upgrading to nexus 4
mm...@cpntr.com <mm...@cpntr.com> #343
Google, don't be evil. Come on.
jo...@gmail.com <jo...@gmail.com> #344
Nexus driver support for ble4.0 plz
ch...@gmail.com <ch...@gmail.com> #345
If anyone is look for the Bluetooth Low energy solution for Galaxy S3 specifically, here is mine to share at github: https://github.com/cjhuo/Android-Samsung-Ble-APIs-Bluez . Sample source code included there.
This is really a vendor specific issue from my understanding at this point. They may use the same BLE stack that Google provided, but question is that whether google will provide a standard API for it. At least for now it doesn't looks like Google will do it since Samsung release their own API for S4 (4.2.x) and HTC is still developing their own API probably with a different stack since it's running on 4.1.1.
As for Nexus 4, sorry, no clue on what Google is think. Hope Google can make use of human resources like us who would like to contribute for their benefits in future.
This is really a vendor specific issue from my understanding at this point. They may use the same BLE stack that Google provided, but question is that whether google will provide a standard API for it. At least for now it doesn't looks like Google will do it since Samsung release their own API for S4 (4.2.x) and HTC is still developing their own API probably with a different stack since it's running on 4.1.1.
As for Nexus 4, sorry, no clue on what Google is think. Hope Google can make use of human resources like us who would like to contribute for their benefits in future.
no...@gmail.com <no...@gmail.com> #346
We can only ponder why the Bluetooth LE announcement was not on main stage, my thoughts are either google wanted to avoid the backlash of not supporting the Galaxy Nexus or hide the fact that it is almost a year since this was logged as a bug or that it has been well over a year since iPhone users has had these feature and we have not or perhaps it was the fact that they really do not have anything to show for it ATM..
https://plus.google.com/u/0/116110604589325140832/posts/VsF1BcaFY1g
jb...@android.com <jb...@android.com> #347
[Comment deleted]
jb...@android.com <jb...@android.com> #348
[Comment deleted]
jb...@android.com <jb...@android.com> #349
[Comment deleted]
ma...@android.com <ma...@android.com>
mi...@gmail.com <mi...@gmail.com> #350
Still no smart Bluetooth low energy on Nexus 7?
ei...@gmail.com <ei...@gmail.com> #351
the nexus 7 is not supported anymore as far as I know
On Thu, 14 Jan 2021 at 14:12, <buganizer-system@google.com> wrote:
On Thu, 14 Jan 2021 at 14:12, <buganizer-system@google.com> wrote:
mi...@gmail.com <mi...@gmail.com> #352
I don't know why this comment appeared only know, but it certainly is old.
mi...@gmail.com <mi...@gmail.com> #353
but yes, true, I am old too, more then my Nexus 7
ei...@gmail.com <ei...@gmail.com> #354
I tried installing a custom rom to my nexus 7 the other day, however my
bluetooth controller stopped working, was hoping to try fortnite on it, not
that fortnite would run anyway.
On Thu, 14 Jan 2021 at 14:36, <buganizer-system@google.com> wrote:
bluetooth controller stopped working, was hoping to try fortnite on it, not
that fortnite would run anyway.
On Thu, 14 Jan 2021 at 14:36, <buganizer-system@google.com> wrote:
bw...@gmail.com <bw...@gmail.com> #355
mi...@gmail.com <mi...@gmail.com> #356
I would just like to be able to connect to a fitness machine, a Concept2 indoor rower ergometer with ErgData app
da...@gmail.com <da...@gmail.com> #357
It's ridiculous that someone resurrected a 7-year-old thread on a phone that was considered EoL in 2015.
mi...@gmail.com <mi...@gmail.com> #358
Why? Don't you use anything at home that is older the 5 years? The hose itself? Anyway it is not a phone.
gr...@gmail.com <gr...@gmail.com> #359
Staaaaaaaaaaap the emails. The Nexus 7 is dead, let's just let it sleep in
the ground.
On Thu, 14 Jan 2021, 14:05 , <buganizer-system@google.com> wrote:
the ground.
On Thu, 14 Jan 2021, 14:05 , <buganizer-system@google.com> wrote:
da...@gmail.com <da...@gmail.com> #360
Excuse me, tablet, if you want to be pedantic. If we are being precise, the Nexus 7 was released in 2013, making it ~8 years old.
Yes, I have plenty of things older than 5 in my home. However, to expect an 8+ year lifespan and support from a consumer-grade electronic device is again, ridiculous.
Yes, I have plenty of things older than 5 in my home. However, to expect an 8+ year lifespan and support from a consumer-grade electronic device is again, ridiculous.
gl...@gmail.com <gl...@gmail.com> #361
Why is it ridiculous? Apple releases iOS updates for devices for 5-6 years (feel free to Google that). The fact that Google and most other Android suppliers only offer supports for 2 (if you're lucky) is ridiculous! Because of that we are all running around with insecure devices which are easily hackable.
ge...@gmail.com <ge...@gmail.com> #362
This issue thread, which is fixed since 2014, is about Android natively supporting BLE. Android supports BLE since version 4.3. Nothing to talk about here anymore.
For your (obsolete 😉) device issue you can get official support here:https://support.google.com/nexus/gethelp
For your (obsolete 😉) device issue you can get official support here:
mi...@gmail.com <mi...@gmail.com> #363
I don't get this, BLE is not working on my Nexus 7 in any Android version 4.* or 5.* so what is the solution to fix it?
da...@gmail.com <da...@gmail.com> #364
The solution is to buy a newer device
Dan Baxter
-------------------------------------------------
Quis custodiet ipsos custodes?
"A sword never kills anybody; it is a tool in the killers hands."-Lucius
Annaeus Seneca, c.4BC-65AD
On Thu, Jan 14, 2021 at 1:15 PM <buganizer-system@google.com> wrote:
Dan Baxter
-------------------------------------------------
Quis custodiet ipsos custodes?
"A sword never kills anybody; it is a tool in the killers hands."-Lucius
Annaeus Seneca, c.4BC-65AD
On Thu, Jan 14, 2021 at 1:15 PM <buganizer-system@google.com> wrote:
al...@gmail.com <al...@gmail.com> #365
What a step backwards to live in a world where upgrades need to be
supported by the hardware vendor. PCs could be updated almost indefinitely
from the get go.
BTW, love this thread! Nexus 7 was a great device, ble or no ble :)
Den tors 14 jan. 2021 19:17 <buganizer-system@google.com> skrev:
supported by the hardware vendor. PCs could be updated almost indefinitely
from the get go.
BTW, love this thread! Nexus 7 was a great device, ble or no ble :)
Den tors 14 jan. 2021 19:17 <buganizer-system@google.com> skrev:
ei...@gmail.com <ei...@gmail.com> #366
Custom rom?
Sendt fra min iPhone
Sendt fra min iPhone
az...@gmail.com <az...@gmail.com> #367
Please stop replying all I no longer need assistance with my device I switched to iPhone thanks
ei...@gmail.com <ei...@gmail.com> #368
Ive also switched to an iphone, but the nexus 7 isnt a phone as someone
earlier stated.
On Thu, 14 Jan 2021 at 19:31, <buganizer-system@google.com> wrote:
earlier stated.
On Thu, 14 Jan 2021 at 19:31, <buganizer-system@google.com> wrote:
mi...@gmail.com <mi...@gmail.com> #369
Hi
Someone had commented on this using my email and it wasn't me.
Can you please remove my email from this thread?
On Fri, 15 Jan 2021, 06:35 , <buganizer-system@google.com> wrote:
Someone had commented on this using my email and it wasn't me.
Can you please remove my email from this thread?
On Fri, 15 Jan 2021, 06:35 , <buganizer-system@google.com> wrote:
dh...@gmail.com <dh...@gmail.com> #370
To unsubscribe, look for the "Default" notification bell at the top (next to 'Hotlists'). Click that, and select "None" at the bottom. Hopefully that stops the alerts for anyone that doesn't care :)
az...@gmail.com <az...@gmail.com> #371
I love this just like a typical reply all work email doesn’t to the how to ignore future emails guys!
bw...@gmail.com <bw...@gmail.com> #372
Or just click unsubscribe at the bottom of this email like any other.
On Thu, Jan 14, 2021 at 3:43 PM <buganizer-system@google.com> wrote:
On Thu, Jan 14, 2021 at 3:43 PM <buganizer-system@google.com> wrote:
ei...@gmail.com <ei...@gmail.com> #373
One might miss out on smt while unsubscribing.
Sendt fra min iPhone
Sendt fra min iPhone
ge...@gmail.com <ge...@gmail.com> #374
You just need to uncheck the star for this specific issue to not receive notifications about it anymore.
dj...@gmail.com <dj...@gmail.com> #375
Considering you have the wrong email address, i have no clue what you are
talking about. So thus no "star" to uncheck.
On Fri, Jan 15, 2021, 16:56 <buganizer-system@google.com> wrote:
talking about. So thus no "star" to uncheck.
On Fri, Jan 15, 2021, 16:56 <buganizer-system@google.com> wrote:
ma...@gmail.com <ma...@gmail.com> #376
Open the email, scroll down and click "Unsubscribe from this issue."
Description