Obsolete
Status Update
Comments
mi...@michealsuen.net <mi...@michealsuen.net> #2
Correction: I meant mysid/toro, not yakju, in the subject line. But this affects yakju, as well.
ds...@gmail.com <ds...@gmail.com> #3
I want this.
ad...@gmail.com <ad...@gmail.com> #4
I wan't this too! And I want't all Android 4.1+ devices to have it, not only the Nexus.
ma...@gmail.com <ma...@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.
ch...@gmail.com <ch...@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.
ad...@gmail.com <ad...@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.
tr...@gmail.com <tr...@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...
sb...@gmail.com <sb...@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:
co...@gmail.com <co...@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.
sp...@gmail.com <sp...@gmail.com> #13
[Comment deleted]
bd...@gmail.com <bd...@gmail.com> #14
i'd love to see my gnex with Low Energy profile in BT 4.0.
ad...@gmail.com <ad...@gmail.com> #15
please add this!
tr...@gmail.com <tr...@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).
sa...@gmail.com <sa...@gmail.com> #17
as a google flagship phone, we deserve bluetooth 4.0
ma...@gmail.com <ma...@gmail.com> #18
I would love to use it with many of the BT 4.0 smartwatches coming out.
je...@gmail.com <je...@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?
su...@gmail.com <su...@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.
[Deleted User] <[Deleted User]> #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!
su...@gmail.com <su...@gmail.com> #22
Us developers WANT to design BLE products for the Nexus. The hardware is there Google, please get your software together!
ga...@gmail.com <ga...@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!
sp...@gmail.com <sp...@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!
ma...@gmail.com <ma...@gmail.com> #25
[Comment deleted]
mo...@gmail.com <mo...@gmail.com> #26
Seconded! My Polar H7 is waiting for it!
ne...@gmail.com <ne...@gmail.com> #27
[Comment deleted]
ti...@gmail.com <ti...@gmail.com> #28
we really need this feature to develop many interesting apps,and service.
mg...@gmail.com <mg...@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...
mg...@gmail.com <mg...@gmail.com> #30
i've an alpha coming too which needs this!
pe...@gmail.com <pe...@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.
ti...@gmail.com <ti...@gmail.com> #32
Would use it instantly too for our products.
ag...@gmail.com <ag...@gmail.com> #33
Bluetooth 4 support in Jelly Bean would be nice.
pa...@gmail.com <pa...@gmail.com> #34
We already have the hardware. Want to use it with Android.
pa...@gmail.com <pa...@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!!!!
ma...@gmail.com <ma...@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?
[Deleted User] <[Deleted User]> #37
Has Google acknowledged this post yet? Just let us know whether we will need a new phone or not.
wi...@gmail.com <wi...@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.
lo...@gmail.com <lo...@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.
jt...@gmail.com <jt...@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.
ja...@gmail.com <ja...@gmail.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.
jo...@gmail.com <jo...@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
ad...@gmail.com <ad...@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!
ma...@gmail.com <ma...@gmail.com> #44
ju...@gmail.com <ju...@gmail.com> #45
It also just says "Bluetooth" though.
ad...@gmail.com <ad...@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?
ca...@gmail.com <ca...@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!
ri...@gmail.com <ri...@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 =)
za...@gmail.com <za...@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!
ls...@gmail.com <ls...@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.
ri...@gmail.com <ri...@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.
hr...@gmail.com <hr...@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.
to...@gmail.com <to...@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."
ga...@gmail.com <ga...@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
ja...@gmail.com <ja...@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.
ro...@gmail.com <ro...@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.
dt...@gmail.com <dt...@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.
be...@gmail.com <be...@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
sh...@gmail.com <sh...@gmail.com> #60
With so many newer devices having the hardware why is the software so behind?
my...@gmail.com <my...@gmail.com> #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.
ke...@gmail.com <ke...@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.
bo...@gmail.com <bo...@gmail.com> #63
bring it! ....please!
lm...@gmail.com <lm...@gmail.com> #64
BLE is required functionality. It is driving us to iOS. Get with it google.
lm...@gmail.com <lm...@gmail.com> #65
[Comment deleted]
dt...@gmail.com <dt...@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?
dr...@gmail.com <dr...@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.
pa...@gmail.com <pa...@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.
ro...@gmail.com <ro...@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.
lu...@gmail.com <lu...@gmail.com> #70
Is there any other phone other than HTC DNA that works with broadcom apis? This phone is not available in Canada.
ru...@gmail.com <ru...@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!
dt...@gmail.com <dt...@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>:
fr...@gmail.com <fr...@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'.
tn...@gmail.com <tn...@gmail.com> #74
ma...@gmail.com <ma...@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>:
sh...@gmail.com <sh...@gmail.com> #76
Is there even a BLE Chip in SGS3? I'm beginning to think that isn't the case :(
ch...@gmail.com <ch...@gmail.com> #78
Ok, then I will not give up the hope.
ex...@gmail.com <ex...@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.
em...@gmail.com <em...@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.
al...@gmail.com <al...@gmail.com> #81
Thanks for this news from AnDevCon. How far does this need to go before we can finally get this basic functionality?
cl...@gmail.com <cl...@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.
ji...@gmail.com <ji...@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.
cn...@gmail.com <cn...@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?
dr...@gmail.com <dr...@gmail.com> #85
This is not a Nexus issue, but needs to be resolved in Android. Want it for my Galaxy S3 & S3 Note.
al...@gmail.com <al...@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.
al...@gmail.com <al...@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.
al...@gmail.com <al...@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.
gl...@gmail.com <gl...@gmail.com> #89
Please support Bluetooth 4's Smart profile for connecting Heart Rate Monitors like the Wahoo or Polar.
ma...@gmail.com <ma...@gmail.com> #90
Same issue with the MIO Alpha here, not being detected by my Nexus 4...
cn...@gmail.com <cn...@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.
go...@gmail.com <go...@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?
vi...@gmail.com <vi...@gmail.com> #93
Please take quick action.
su...@gmail.com <su...@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.
et...@gmail.com <et...@gmail.com> #95
I wonder if this problem though somebody decides it again or not recognize the problem?
su...@gmail.com <su...@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#_=_
su...@gmail.com <su...@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.
ec...@gmail.com <ec...@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.
sl...@gmail.com <sl...@gmail.com> #99
All of this is probably a result of all the patent wars going on
lu...@gmail.com <lu...@gmail.com> #100
Can't believe this issue hasn't been addressed yet...
co...@gmail.com <co...@gmail.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.
ta...@gmail.com <ta...@gmail.com> #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...
st...@gmail.com <st...@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.
ry...@gmail.com <ry...@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.
pa...@gmail.com <pa...@gmail.com> #105
Can't believe this issue hasn't been addressed yet...
al...@gmail.com <al...@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.
en...@google.com <en...@google.com>
an...@gmail.com <an...@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
th...@gmail.com <th...@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? ??????
ju...@gmail.com <ju...@gmail.com> #109
i have issues with bluetooth too
la...@gmail.com <la...@gmail.com> #110
omg, common guys...
ou...@gmail.com <ou...@gmail.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?
ma...@gmail.com <ma...@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?
ma...@gmail.com <ma...@gmail.com> #113
Wow, somebody at google should get fired for this.
ou...@gmail.com <ou...@gmail.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?
ou...@gmail.com <ou...@gmail.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.
ba...@gmail.com <ba...@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
Description
Wifi keeps disconnecting randomly, sometimes every 30 seconds or so. I thought may be something was with my old Netgear router (updated firmware) so I went ahead and bought Netgear N600. But kept getting random disconnects.
- What happened:
After months of agony, I have observed a few things:
1. Usually the mobile network single goes from blue to gray as well when Wifi dies. I can still see the grey wifi strength but no data packets are received.
2. It mostly happens when you wake up device from sleep. When you press the power button to wake the device up, you can tell the wifi is not connected as the wifi bars are greyed out (I have the "Keep Wifi on during sleep" as "Always").
3. Just to screw with my head more, sometimes it has happened to me while randomly browsing around. One minute it is working, the next minute it just dies. You can see the wifi bar going from blue to grey (sometimes with the network signal as well). And you have to wait for it to turn blue again. Then you can finally reload the page you were trying to look at. Sometimes you have to do this every time you click a link!
4. On the Nexus 7, it worked fine for first few days but since yesterday, it has been disconnecting constantly. I have static IPs for both my Galaxy Nexus and Nexus 7. Both the devices are running 4.1.1
The reason I think it is just Netgear routers is because I have a Netgear router at work, its a really old one and we have been using it for good 5-6 years (latest firmware). None of the Android phones can stay connected to it (no, I'm not making this up, we have a Xperia Arc, Samsung SII and my Galaxy Nexus). We just keep getting disconnected. One of the employees has an iPhone 3GS that works just fine (Grrr!).
In desperation, I even tried running as WEP but still kept getting disconnects.
I must add, I do have an iPhone at home as well, which never disconnects (and by never, I mean never ever!). When the Nexus 7 disconnect started happening, I had no choice but to come here and try to resolve this (I'm sure I had tears in my eyes!).
I am technically aware so I'll be more than glad to run tests in trying to resolve it. I have a feeling this is something exclusive to Netgear routers.