Obsolete
Status Update
No update yet.
Comments
go...@gmail.com
Correction: I meant mysid/toro, not yakju, in the subject line. But this affects yakju, as well.
ze...@gmail.com
I want this.
ma...@googlemail.com
I wan't this too! And I want't all Android 4.1+ devices to have it, not only the Nexus.
cs...@gmail.com
I would love to see BT4 support. Seems to be the only other option to ANT+ when it comes to fitness sensors.
da...@gmail.com
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.
ks...@gmail.com
@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.
ks...@gmail.com
@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...
je...@gmail.com
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:
he...@gmail.com
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.
an...@gmail.com
[Comment deleted]
wa...@gmail.com
i'd love to see my gnex with Low Energy profile in BT 4.0.
bp...@panonia.net
please add this!
wo...@gmail.com
* 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).
wo...@gmail.com
as a google flagship phone, we deserve bluetooth 4.0
[Deleted User] <[Deleted User]>
I would love to use it with many of the BT 4.0 smartwatches coming out.
bo...@gmail.com
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?
ch...@gmail.com
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.
hs...@gmail.com
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!
fa...@gmail.com
Us developers WANT to design BLE products for the Nexus. The hardware is there Google, please get your software together!
oh...@gmail.com
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!
hu...@gmail.com
Google, let's make this happen! My cookoo watch is practically in the mail. I bought it on faith. Don't let me down!
vr...@gmail.com
[Comment deleted]
su...@sushi3.com
Seconded! My Polar H7 is waiting for it!
ik...@gmail.com
[Comment deleted]
ik...@gmail.com
we really need this feature to develop many interesting apps,and service.
ik...@gmail.com
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...
th...@gmail.com
i've an alpha coming too which needs this!
co...@gmail.com
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.
ka...@gmail.com
Would use it instantly too for our products.
mu...@gmail.com
Bluetooth 4 support in Jelly Bean would be nice.
Description
I have the Problem that I can't to Connect to my Home VPN (Linksys wrt54gl
+ DDWRT Firmware). The connection stops while authentication. The VPN
Server(Router) isn't the problem. The connection works fine from a PC.
Has anyone seen some thing like this before?? It would be nice if I could
get help in this Point.
Here the Log from my Droid:
I/mtpd ( 1641): Connecting to --.--.--.--(hahaha ) port 1723
I/SProxy_mtpd( 1515): got data from control socket: 20
I/mtpd ( 1641): Connection established (socket = 10)
D/mtpd ( 1641): Sending SCCRQ
D/mtpd ( 1641): Received SCCRP -> Sending OCRQ (local = 57598)
I/mtpd ( 1641): Tunnel established
D/mtpd ( 1641): Received OCRQ (remote = 2)
I/mtpd ( 1641): Session established
I/mtpd ( 1641): Creating PPPoX socket
I/mtpd ( 1641): Starting pppd (pppox = 11)
I/mtpd ( 1641): Pppd started (pid = 1642)
I/pppd ( 1642): Using PPPoX (socket = 11)
E/pppd ( 1642): unrecognized option '+mppe'
I/mtpd ( 1641): Received signal 17
I/mtpd ( 1641): Pppd is terminated (status = 2)
I/mtpd ( 1641): Mtpd is terminated (status = 34)
I/SProxy_mtpd( 1515): got data from control socket: 34
E/VpnService( 1515): onError()
E/VpnService( 1515): com.android.server.vpn.VpnConnectingError: Connecting
error: 34
E/VpnService( 1515): at com.android.server.vpn.VpnService.onError(VpnServi
ce.java:171)
E/VpnService( 1515): at com.android.server.vpn.VpnService.waitUntilConnect
edOrTimedout(VpnService.java:198)
E/VpnService( 1515): at com.android.server.vpn.VpnService.onConnect(VpnSer
vice.java:136)
E/VpnService( 1515): at com.android.server.vpn.VpnServiceBinder$2.run(VpnS
erviceBinder.java:108)
E/VpnService( 1515): at java.lang.Thread.run(Thread.java:1096)
I/VpnService( 1515): disconnecting VPN...
Benni