[Q] What is the state of Bluetooth Low Energy support for Galaxy Nexus GSM? - Samsung Galaxy Nexus

I remember reading sometime back that Galaxy Nexus has hardware capable of supporting both Bluetooth 4.0 stacks, but that BLE (Low Energy profile) was not enabled via driver/SDK. I wonder if there was any progress in this direction or at least clear indication from Google on the support. There is a binder full of BLE devices getting on the market in Q1 that jump on support from iPhone 5 and some of them are extremely attracting but I would hate to get rid of my Nexus if I could.
Is there a ROM that can provide compatibility?

Ive been trying to post everywhere and anywhere about this topic but noone seems to care. More and more devices are being launched use BLE and developers wont make an android app because android doesn't support BLE at the moment. I dont know why more websites are making this an issue yet..phones are being launched saying they are 4.0 capable..which is correct but we cant use that technology. Its sad because i want the new FITBIT flex band but they are only making the app available to sync with the S3 and note 2 because samsung is helping then with the Bluetooth drivers for the app.

In addition to your post, a ton of devices are coming with AVRCP 1.3+ on stock devices. However only a select few ROMs have it enabled at all.
Sent from my Galaxy Nexus using xda premium

newtonfb said:
Ive been trying to post everywhere and anywhere about this topic but noone seems to care. More and more devices are being launched use BLE and developers wont make an android app because android doesn't support BLE at the moment. I dont know why more websites are making this an issue yet..phones are being launched saying they are 4.0 capable..which is correct but we cant use that technology. Its sad because i want the new FITBIT flex band but they are only making the app available to sync with the S3 and note 2 because samsung is helping then with the Bluetooth drivers for the app.
Click to expand...
Click to collapse
Thanks, I am personally waiting for these devices (StickNFind, BluTracker) to hit the market in March and April respectively and I more and more inclining to get an iPhone because of the better support there. For Newtonfb, did you look at BodyMedia FIT LINK Armband? This is what I use and it has all the same features plus more of Fitbit and is fully supported on GNEX via regular Bluetooth.

I'll look into that. Thanks.
Sent from my Galaxy Nexus using xda app-developers app

Related

Wifi Display will be coming to Galaxy Nexus

Many of the people who had been wondering why Google chose to go with the OMAP 4460 as the processor for the Galaxy Nexus have gotten yet another answer to that question. The Omap4 series of processors are compatible with wifi display. as of right now, besides the Omap4 family the Snapdragon S4 is the only mentioned to be getting wifi display. It looks as if the Tegra 3 isn't going to support it at all according to http://www.androidauthority.com/wifi-display-to-make-your-life-easier-in-2012-47153/ . At this time it looks as though the OMAP4 is going to be the only current gen chip that will support wifi display, and of course with us having a nexus device we will most likely be seeing that update before anybody.
http://androidandme.com/2012/01/new...ay-likely-powered-by-texas-instruments-omap4/
Thanks for sharing this. I hope this actually happens soon!
chino0131 said:
Thanks for sharing this. I hope this actually happens soon!
Click to expand...
Click to collapse
No problem. According to the androidandme article we're looking at a summer release. I am looking forward to this coming to our phones as I think it would be very useful for me. Often times I'll either connect a laptop to the TV or my cell phone and stream kid's shows from a particular site for my son. It would be very nice if I could do that without having to connect my phone directly to the television like I've been doing. I could sit across the room on my computer while he watches his show and still have my phone right next to me. That would be nice.
Is this WiDi?
ushim6 said:
Is this WiDi?
Click to expand...
Click to collapse
From what I understand (and I could be wrong, so anyone correct me if I am) widi is an intel thing and it's for displaying your pc wirelessly to a television. Wifi display involves a "wifi direct" connection between two devices and is actually an emerging standard that the wifi alliance is backing. All in all I don't think it is the same thing was WiDi.
But we need tv that support this wifi display?
I don't have such tv.
Sent from my Galaxy Nexus using xda premium
gogol said:
But we need tv that support this wifi display?
I don't have such tv.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That or just an adapter. Also, from my understanding it works with computers too, and any other wifi display capable device (not sure what other devices that would be).
mysterioustko said:
That or just an adapter. Also, from my understanding it works with computers too, and any other wifi display capable device (not sure what other devices that would be).
Click to expand...
Click to collapse
Maybe it will work better than WiFi Direct? Has anybody managed to figure this crap out?
Maybe hardware supports it, but I think we will need software to handle this. I'm not sure that there is a permission for app to handle access to wifi radio (and any other hardware needed for this), so it will have to be implemented in the OS...
This technology is much lower latency than Intel WiDi, and it's also not proprietary. WiDi is good only for video, whereas WiFi Display is quick enough to support real-time gaming. And as an open standard that's cheap to implement, you can expect it to kill WiDi in short order.
k_myk said:
Maybe it will work better than WiFi Direct? Has anybody managed to figure this crap out?
Maybe hardware supports it, but I think we will need software to handle this. I'm not sure that there is a permission for app to handle access to wifi radio (and any other hardware needed for this), so it will have to be implemented in the OS...
Click to expand...
Click to collapse
Connecting two wifi direct devices isn't too difficult. For example, connecting a galaxy s2 to a Galaxy Nexus works fairly easily. That being said, you are right that wifi display will have to be implemented on the OS level. From what I understand they expect an update to come from Google some time this summer that will implement the feature. We've got something to look forward to this summer lol.
Could the WiFi display work two ways, buy a small 10.1" WiFi display with touch screen, connect to the Galaxy Nexus - instant Nexus Tablet!
StuMcBill said:
Could the WiFi display work two ways, buy a small 10.1" WiFi display with touch screen, connect to the Galaxy Nexus - instant Nexus Tablet!
Click to expand...
Click to collapse
I was wondering the exact same thing! That would be great if that turns out to be possible. There seems to be several different possible applications for this. I'm excited to see what the community comes up with for this.
Something off the top of my head is: Having software installed on the computer to remotely control the phone. Create a nfc tag that starts up wifi display to your tv and launches the computer remote controls. When you place the phone on the tag you will instantly be able to control the phone via the computer and have it displayed on the television. That's just an idea that came to my mind.
This is why i got a nexus
Is there any word on when we might be receiving this?
What I want to know is when we will see the technology on the TV side. Google updating doesn't do much good until we have devices to pair with.
On another note, I'd have trouble justifying purchase of a toggle or $4000 flagship Sony TV exclusively for this functionality. I wonder if we will see this technology utilized in entry-level smart tvs or rokus, google tvs, and xboxes. This feature will really become useful when it is available on most any wifi-connected display around you.
kensingtn5 said:
What I want to know is when we will see the technology on the TV side. Google updating doesn't do much good until we have devices to pair with.
Click to expand...
Click to collapse
I'm just hoping for an adapter box that outputs HDMI.
Looks like the Galaxy SIII is going to beat us to it.
Can't wait to see the first demos of it. Perhaps it's like with iphone.
manore said:
Can't wait to see the first demos of it. Perhaps it's like with iphone.
Click to expand...
Click to collapse
The demos from Texas Instruments I saw looked more appealing than the iPhone's method to me. The latency is also suppose to be much lower. I'm excited, that was the one feature of the iOS ecosystem I was very jealous of.
This is somewhat OT, but Samsung is also releasing a set of cameras with built-in WiFi direct capability. Your phone basically becomes a remote control/viewfinder for the camera and you can control most of its functions. I love where this technology is going.

Bluetooth 4.0 Low Energy and NFC?

I've been hearing great stuff about Bluetooth 4.0 LE ((B)LE), like paring heart-rate sports gear almost without battery draining.
Afaik Bluetooth 4.0 doesn't necessarily mean LE functionality, and the only mention thus far I could find was APT-X is included.
Right now I'm confused on whether or not this is supported on the One X. Does anyone know?
Here's a link with a chart that should explain compatibility between new Bluetooth devices, but I really don't get it
And what about NFC implementation? I haven't seen any mention of Sense 4 using it, while Sony's Experia S has those coins with nice software implementation to let the phone know it's next to your bed and needs to be quiet, is in your car and needs navigation etc.
http://www.cellular-news.com/story/53379.php
According to this site it is Smart Ready. As I understand it: It should be ready for the LE-devices.
NFC ist atleast in the Settings:
Look at 2:40: http://www.youtube.com/watch?v=a-478p9v7T8
Thanks for those links Noneus! Seems like the device is BLE ready while Android 4.0.3 isn't. I really hope xda devs can help with this into the One X roms, however, I guess the wait is for nvidia to update their drivers mostly right?
Sent from my HTC Desire using xda premium
Not necessarily. Most of the time the OS is lacking the Bluetooth features. Not the driver.
Here is a good diagram: https://sites.google.com/a/android.com/opensource/projects/bluetooth-faq
From http://developer.android.com/sdk/android-4.0-highlights.html :
Android 4.0 also introduces built-in support for connecting to Bluetooth Health Device Profile (HDP) devices. With support from third-party apps, users can connect to wireless medical devices and sensors in hospitals, fitness centers, homes, and elsewhere.
Click to expand...
Click to collapse
This look promising, thanks! Will take a closer look as soon as I get back from work!
The HQ for bluetooth 4.0 fix on GS3
there is a lot of information on this thread that may or may not be helpful to you even tho its mostly directed towards the gs3
http://forum.xda-developers.com/showthread.php?p=35322649#post35322649
hope it helps

Is gnex Bluetooth 4.0?

I have read that gnex has hardware that supports Bluetooth 4.0, is there a rom or kernel that has enabled it to work or is it even possible?
Thanks in advance
Sent from my Galaxy Nexus using Tapatalk 2
I'm sorry man but i think it's impossible according to the samsung specs, it only has bluetooth 3
http://www.samsung.com/hk_en/consumer/mobile/mobile-phones/smartphone/GT-I9250TSATGY-spec
Thanks. The reason I ask is that I saw this on Wikipedia. It states that it is Bluetooth 4.0 hardware compatible. 2nd reason is I bought those Bluetooth speakers with Bluetooth 4 and apt-x support. I just want to maximize it to it's full potential.
Sent from my Galaxy Nexus using Tapatalk 2
mrm43 said:
Thanks. The reason I ask is that I saw this on Wikipedia. It states that it is Bluetooth 4.0 hardware compatible. 2nd reason is I bought those Bluetooth speakers with Bluetooth 4 and apt-x support. I just want to maximize it to it's full potential.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes. The hardware is bluetooth 4.0 compatible but there's no software support yet. Star the issue to add your vote! ->
http://code.google.com/p/android/issues/detail?id=33371
travellers trolloca
Wait wait wait, one moment, i don't understand. The hardware inside GNeX is bt4 but it has driver that doesn't support that but only bt3, is this what are you saying? It sound really strange to me, maybe that statement on wiki means that GNeX can use other hardware with bt4 even if it's bt3 but not at full power, am i wrong?
[email protected] said:
Wait wait wait, one moment, i don't understand. The hardware inside GNeX is bt4 but it has driver that doesn't support that but only bt3, is this what are you saying? It sound really strange to me, maybe that statement on wiki means that GNeX can use other hardware with bt4 even if it's bt3 but not at full power, am i wrong?
Click to expand...
Click to collapse
It'll be clearer if you check out the link in my previous post. Gnex contains a Samsung SWB-B42 BT 4.0 Dual Band Wlan FM Tx/Rx chip so the hardware is there. The thing is the driver that is currently installed on our gnex only has BT3 coded in. And even if the driver utilizes the phone's BT4.0 capabilities, Android in itself doesn't have native APIs to allow developers to take advantage of the new features.
Sorry if i didn't read the whole link but i was at work so, you can understand... Thank you for the very clear explanation, however it's really really strange this behaviour by google...
Will Google/Android ever get BT4/BLE working on the GNex? Or shall we move on to another device if we need/want it?

Fool app to think phone is S3 or Note 10.1?

I want to use a fitbit device and it only bluetooth syncs with S3 and Note 2 and Note 10.1 because it uses bluetooth 4.0 and Samsung helped them with the code since its not in stock google right now. My question is..my Galaxy Nexus has the same Bluetooth chip in it as the note 10.1 and is also Samsung obviously. I know the 10.1 is obviously a tablet. Would i just have to change the build.prop to note 10.1 for it to fool it? Is there anything else i might have to do or is this impossible? THanks for any input.
newtonfb said:
I want to use a fitbit device and it only bluetooth syncs with S3 and Note 2 and Note 10.1 because it uses bluetooth 4.0 and Samsung helped them with the code since its not in stock google right now. My question is..my Galaxy Nexus has the same Bluetooth chip in it as the note 10.1 and is also Samsung obviously. I know the 10.1 is obviously a tablet. Would i just have to change the build.prop to note 10.1 for it to fool it? Is there anything else i might have to do or is this impossible? THanks for any input.
Click to expand...
Click to collapse
i would think changing the build.prop would work
The Galaxy Nexus has Bluetooth 4.0?
Sent from my Galaxy Nexus using xda premium
DirgeExtinction said:
The Galaxy Nexus has Bluetooth 4.0?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
yes sir. It has broadcom 4330 bluetooth chip. Its BLE compatable but google needs to supply the code to activate the bluetooth 4.0 chips in their software which hopefully is soon. My guess is it will be said somewhere in May at the I/O since google glass uses BLE so it has to activate it soon. Its actually pretty embarrassing for google to leave BLE out of the code still.
Your guess is wrong. The GNex is going to be EOL'd way too soon for it to be worth the effort of writing/releasing the drivers.
063_XOBX said:
Your guess is wrong. The GNex is going to be EOL'd way too soon for it to be worth the effort of writing/releasing the drivers.
Click to expand...
Click to collapse
It should be standard. The bluetooth chip is used in many phones and when they write the code, (im sure they already have, they already said it was going to be released for android 4.3) it will be standard.

[Q] rSAP Bluetooth Protocol

Hello guys...
I want to buy this phone but I have some questions before buying it!
So...I want to use this phone with my Passat CC Bluetooth CarKit.
The CarKit supports only rSAP protocol connection.
Does this phone support this type of connection?
I`m asking this because now I own a Xperia Z1 Compact and unfortunately this phone doesn`t have support for rSAP Bluetooth connection.
Thank you!
aresbv2000 said:
Hello guys...
Does this phone support this type of connection?
Click to expand...
Click to collapse
Regarding to your question I think just making a test with a phone friend can be sure of that.
After a brief search I found this information:
This profile allows devices such as car phones with built-in GSM transceivers to connect to a SIM card in a Bluetooth enabled phone, thus the car phone itself doesn't require a separate SIM card. This profile is sometimes referred to as rSAP (remote-SIM-Access-Profile), though that name does not appear in the profile specification published by the Bluetooth SIG. Information on phones that support SAP can be found below:
Samsung:GT-B7610, GT-B7620, GT-B7350 (OMNIA 735), SGH-i900 ...
And ...
GT-I9000 Galaxy S
GT-I9001 Galaxy S plus
GT-S5570 Galaxy mini(POP)
GT-I9100 Galaxy S II (only to Android 2.3.x, with newest update from 4.04 again possible)
GT-I9300 Galaxy S III
GT-I9305 Galaxy S III LTE
GT-I9505 Galaxy S IV
GT-I8150 Galaxy W
GT-N7000 Galaxy Note
GT-N7100 Galaxy Note II
GT-P1000 Galaxy Tab
GT-I9105P Samsung Galaxy S2 plus
Click to expand...
Click to collapse
So, if you want to be 100% SURE about compatibility, only with test YOU CAN.
LE: Maybe you can ask someone in our dedicated forum vwForum.ro :good:
Thank you so much for your reply. Unfortunately I don`t have any friend or something like that that owns a S4 Mini for direct testing with my car integrated bluetooth. A good idea is to ask on the vw forum what phones do other users connect to their cars. Thank you again! Have a nice day!
In case anybody else digs this thread up (as I did on a Google search), there are a variety of phones that will work IF they are rooted: see Android-RSAP.com, where there is a small-scale (single dev) effort to get phones working.
He's had a reasonable level of success with some phones.
In terms of phones that are supported officially (out the box), this list is kept up to date by Audi, so is reasonably reflective of the other VAG cars (e.g. VW): HERE, make sure you tick "Carphone", otherwise it'll give you all the phones that support handsfree
The general summary is that almost ALL Samsung (Android) and Nokia (Symbian ONLY!) phones should work, there are a smattering of other HTC / Blackberry phones that will also work, but it's pretty limited - I've tested Galaxy S2's, S3's, S4's and S5's.... all worked witdout any fiddling, out the box, first time... likewise with my OLD "Nokia X3-2 Touch"... significantly less luck with the Blackberries, including a 9360Curve and a 9900Bold, that were on the supported list at the time: they would connect once, but needed the entire Bluetooth profile removed and re-added for each time I tuned the ignition off and back on.
I've also have an extensive "fiddle" with a (rooted) HTC One X+ and Nexus 4 and never had a usable connection.

Categories

Resources