I have bought the one x because I thought it had bluetooth 4.0 but as it turns out there is no implementation for bluetooth 4.0 on android by google and htc doesn't have a stable working api either making the bluetooth 4.0 radio on my phone useless. Should HTC be allowed to sell this phone as a bluetooth 4.0 device without a working implementation for bluetooth 4.0? I feel cheated
Have you tested this?
Sent from my HTC One X using xda app-developers app
jonshipman said:
Have you tested this?
No but i pre-ordered a cookoo watch which has bluetooth 4.0
The makers of the watch said they thought it would be possible to make use of bluetooth 4.0 radio's on android devices because they were being sold with this spec. But they had to give up on this idea. They send a letter to the android backers with a nice timeline on bluetooth 4.0 and android:
http://www.kickstarter.com/projects...tch-for-the-connected-generation/posts/352332
Click to expand...
Click to collapse
martijnpolman said:
No but i pre-ordered a cookoo watch which has bluetooth 4.0
The makers of the watch said they thought it would be possible to make use of bluetooth 4.0 radio's on android devices because they were being sold with this spec. But they had to give up on this idea. They send a letter to the android backers with a nice timeline on bluetooth 4.0 and android:
http://www.kickstarter.com/projects...tch-for-the-connected-generation/posts/352332
Click to expand...
Click to collapse
Just says that 4.2 switches from BlueZ to Broadcom BT stacks. Pity, as I like BlueZ http://www.bluez.org/
Our One X does indeed have 4.0 and supports the low profile through the BlueZ linux stack. It just looks like Cookoo doesn't want to support two BT stacks with their software and will wait until more phones have 4.2.
jonshipman said:
Just says that 4.2 switches from BlueZ to Broadcom BT stacks. Pity, as I like BlueZ http://www.bluez.org/
Our One X does indeed have 4.0 and supports the low profile through the BlueZ linux stack. It just looks like Cookoo doesn't want to support two BT stacks with their software and will wait until more phones have 4.2.
Click to expand...
Click to collapse
Bluetooth low energy isn't supported at all on Android 4.2 and they tried to get bluetooth low energy working with the BlueZ stack but they failed. Its not a question of will on the part of cookoo, its just that they can't. There are currently no bluetooth 4.0 gadgets that work with the HTC One X and the same goes for the SGS3. Google also sells phones with a bluetooth 4.0 capable chip but they don't put that in the specs list because they don't have an implementation for bluetooth 4.0.
If there is a stable API for bluetooth low energy on HTC One X i am sure the cookoo team is very interested.
One X doesn't even use 4.2.
Sent from my HTC One X using xda app-developers app
jonshipman said:
One X doesn't even use 4.2.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes so we are still stuck with a phone sold with bluetooth 4.0 spec but no gadgets for it because there is no (stable) api
martijnpolman said:
Yes so we are still stuck with a phone sold with bluetooth 4.0 spec but no gadgets for it because there is no (stable) api
Click to expand...
Click to collapse
Hell!
I was about to buy the watch from cookoo and own a HTC one x..
Just wanted you guys to know that I finally managed to install the cookoo life beta 8 app on the play store.
It finally worked using cm 10.2.0-RC1 rom with Android 4.3. Watch keeps disconnecting though.
I'll let you know if something changes.
Carmelo
Sent from my EndeavorU using xda app-developers app
---------- Post added at 04:02 AM ---------- Previous post was at 03:48 AM ----------
iksander said:
Hell!
I was about to buy the watch from cookoo and own a HTC one x..
Click to expand...
Click to collapse
And now it's actually working
Sent from my EndeavorU using xda app-developers app
Related
Hey folks,
my Dad just recently got himself a brad new Desire HD and thinks about using it as a regular phone over his iPhone 4.
The thing is: His car radio uses the rSAP protocol to allow hands-free calling within the car and reading SIM contacts and stuff.
Since almost all Android Devices (except for Samsung) have no rSAP support, is there a small possibility to get this stuff working for our Desire HD? I know its possible from the hardware side, but there arent proper drivers included into the Android Software itself. Only Samsung seems to have achieved a rSAP compatibility and functionality.
Any info on that?
Hello
You can take a look to
www.Android-rsap.com
Still beta but one will work
Sent from my Desire HD using XDA Premium App
bouya_k said:
Hello
You can take a look to
www.Android-rsap.com
Still beta but one will work
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Thanks for the reminder Yeah, I know that site. Its just that this approach doesnt work well with the DHD at the moment.
The Project seems very mature, tho, and very promising. Its good to know that he is trying to get that protocol compatible with our devices. Very nice
Hey guys im using htc 2.3 gingerbread and im very happy with it ,but there are few security patches that have been released since our official update. I asked htc but no luck. Or this is final version from htc?
Sent from my HTC Desire using xda premium
Official support is over. Though there was one update for Froyo after the 2.3 release IIRC.
Yeah i could never install it. And 2.3 gives me much better battery life and app2 sd is great
Sent from my HTC Desire using xda premium
For HTC the Desire is dead....
Unfortunate, but true.
FreeWolF80 said:
For HTC the Desire is dead....
Click to expand...
Click to collapse
reason I'm never gonna buy phones made by HTC, or any other manufacturers. My phones from now on will be pure Google devices e.g The Galaxy Nexus/Nexus Prime. Looking forward to the Samsung/Google unveiling of the upcoming Android OS and device.
nasimdejai said:
reason I'm never gonna buy phones made by HTC, or any other manufacturers. My phones from now on will be pure Google devices e.g The Galaxy Nexus/Nexus Prime. Looking forward to the Samsung/Google unveiling of the upcoming Android OS and device.
Click to expand...
Click to collapse
No proprietory UI either.
Hopefully a Moto based device will come out, so we dont have to worry so much about build quality.
nasimdejai said:
reason I'm never gonna buy phones made by HTC, or any other manufacturers. My phones from now on will be pure Google devices e.g The Galaxy Nexus/Nexus Prime. Looking forward to the Samsung/Google unveiling of the upcoming Android OS and device.
Click to expand...
Click to collapse
I think you might find soon that Google consider the Nexus One dead too. Which is a shame. Its still a very powerful phone. Internal specs higher then iPhone 4 as that is under clocked.
Sent from my HTC Desire using Tapatalk
nasimdejai said:
reason I'm never gonna buy phones made by HTC, or any other manufacturers. My phones from now on will be pure Google devices e.g The Galaxy Nexus/Nexus Prime. Looking forward to the Samsung/Google unveiling of the upcoming Android OS and device.
Click to expand...
Click to collapse
Get your grip ffs. No one in the sane state of mind would support device that is more than a year and a half old. I can't think one company in the IT industry that supports legacy devices, so I'm hoping you could enlighten me?
Apple do.
Sent from my HTC Desire using Tapatalk
leenukes said:
Apple do.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Because they make one phone/year, while most Android OEM's make 3-4/year so its hard to keep up updating every single one of em... Besides, Apple cuts most of the newest iOS features from the previous generations of iPhones, and thats something I havent seen happening on Android... You will either get everything from the newest Android versions, or not get it at all...
erklat said:
Get your grip ffs. No one in the sane state of mind would support device that is more than a year and a half old. I can't think one company in the IT industry that supports legacy devices, so I'm hoping you could enlighten me?
Click to expand...
Click to collapse
erklat is right... there so many devices with so many diferent specs to please everyone, that after some time it's unsuportable for then.
Only thing missing from Android devices recently is more compatibility with BT devices using different profiles.
For instance I have a FIAT Bravo car with BT head unit built in. It pairs with the car and makes and receives calls with no issue. However it fails to read text messages due to lack of the MAP profile.
I did some searching and it seems some have stated this code thread has worked.
review.cyanogenmod.com/#dashboard,2210
I just wondered whether any bright spark could help some of us lowly peons and bring this functionality to an already great device?
Cheers in anticipation.
Sent from my Galaxy Nexus using xda premium
Wrong section.
Sent from my Galaxy Nexus using xda premium
I'm with the op. Waiting for the map profile on the galaxy nexus
GeLopez said:
I'm with the op. Waiting for the map profile on the galaxy nexus
Click to expand...
Click to collapse
2013
has this been implemented yet?
SayWhat10 said:
2013
has this been implemented yet?
Click to expand...
Click to collapse
Does any JB ROM have this MAP profile? I tried CM 9.1 and the MAP profile worked but on CM 10.1 this doesn't work.
Android 4.1 ROMs like CM10 should support map. It's not an AOSP feature but many custom ROMs have it.
Sent from my HTC One using Tapatalk 4 Beta
CM has been tried
So if you could name some of those many other custom roms that would be great
what other camera app uses the image sense chip in our HOX
only the sense one uses it as far as I know, as the drivers to use it are closed source.
are there news about the chip?
the new focal application of cyanogenmod work whit this chip?
None. HTC are a pain in the arse
Sent from my HTC One X using xda app-developers app
danyshotbang said:
what other camera app uses the image sense chip in our HOX
Click to expand...
Click to collapse
Drefsab said:
only the sense one uses it as far as I know, as the drivers to use it are closed source.
Click to expand...
Click to collapse
The HTC Imagechip is used exclusive by the Sense camera, which is only compatible within the Sense framework.
There is NO camera for AOSP that makes use of it in any fashion.
Tigerlight said:
The HTC Imagechip is used exclusive by the Sense camera, which is only compatible within the Sense framework.
There is NO camera for AOSP that makes use of it in any fashion.
Click to expand...
Click to collapse
Ok then my next phone will be the nexus.
if a company makes chips without source code then it is a thief
MT88 said:
Ok then my next phone will be the nexus.
if a company makes chips without source code then it is a thief
Click to expand...
Click to collapse
Only android is open source, sense is HTC's work and is not released under the open source licence.
They haven't stole anything, what they are doing is stopping people from steal their work.
Sent from my HTC One X using xda app-developers app
treebill said:
Only android is open source, sense is HTC's work and is not released under the open source licence.
They haven't stole anything, what they are doing is stopping people from steal their work.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Much like ALL of the SoC developers who actually build Android for our devices using closed-source, obfuscated hardware interfaces.
Qualcomm is closed-source. NVIDIA is closed-source. Samsung release parts of it, I believe.
Every company protects their work in one form or another. Can't say I have a problem with it.
Hey guys! So I've run I to an issue streaming over Bluetooth... NONE of my tack I formation shows.. I've seen and talked to numerous people who have my same pioneer touch screen stock head unit who are able to steam album art/track info to the HU. I've seen and iPhone 4s do this as well as a Galaxy s 4. I can't figure it out for the life of me. I'm running the latest stable cm10.1 ROM. Any pointers?
Thanks guys
Sent from my Galaxy Nexus using xda premium
jdbeitz said:
Hey guys! So I've run I to an issue streaming over Bluetooth... NONE of my tack I formation shows.. I've seen and talked to numerous people who have my same pioneer touch screen stock head unit who are able to steam album art/track info to the HU. I've seen and iPhone 4s do this as well as a Galaxy s 4. I can't figure it out for the life of me. I'm running the latest stable cm10.1 ROM. Any pointers?
Thanks guys
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Android 4.x doesn't support media access protocol (MAP). You'll have to hope a developer for CM can implement it, downgrade to cm 10 (someone added it, but it doesn't work in cm10.1), or wait for Google to properly implement Bluetooth.
Sent from my Galaxy Nexus using Tapatalk 2
mwalt2 said:
Android 4.x doesn't support media access protocol (MAP). You'll have to hope a developer for CM can implement it, downgrade to cm 10 (someone added it, but it doesn't work in cm10.1), or wait for Google to properly implement Bluetooth.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Awesome! Thanks for the info.
Sent from my Galaxy Nexus using xda premium
Isn't track information AVRCP related ?
madd0g said:
Isn't track information AVRCP related ?
Click to expand...
Click to collapse
this.
Well in that case, next release should bring AVRCP 1.3 support, but not sure if to GN, or we only won't get BLE.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
madd0g said:
Isn't track information AVRCP related ?
Click to expand...
Click to collapse
I've also read this....
Sent from my Galaxy Nexus using xda premium
madd0g said:
Isn't track information AVRCP related ?
Click to expand...
Click to collapse
I don't think so. Everything I've read about features not working over Bluetooth with car features has pointed to MAP (reading of text messages, track info, etc). For all I know, AVRCP may be part of MAP .
OP, the issue with CM 10.1 has been fixed now that a dev looked into it. Should appear in nightlies soon if it hasn't already. There are multiple reports of it working on various cars now.
https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-41
Sent from my Galaxy Nexus using Tapatalk 2
I see, I remembered about AVRCP because I watched the BT4.0 session from IO2013 where the engineer said something about track info and lack of AVRCP. But I'm not much into the BT area, so I guess that isn't the whole deal. Glad to see it working for you then, hope the same happens with the next Android release :]