Has anyone else noticed that updating to 2.3.5 and sense 3 has changed the bluetooth version.
Before the update, m bluetooth version was 2.1, now after the update if i look in the same place (settings, ,about phone, hardware information), it says bluetooth version is 3.0. How is this possible? is this just a mistake or can the software actually upgrade the version of bluetooth that the phone uses, i would have assumed that this was limited by the hardware itself.
BT 3.0
Actually it is possible because the software controls the chip. I did the upgrade to 2.3.5/sense 3 and indeed the BT upgrades from 2.1 to 3.0.
Have you tried any transfers?...cause' you'll probably feel the differences. Although the bt 3.0 is a bit of exaggeration as long as the bt chip was designed to support 2.1. That makes me think that the improvements are made exclusively via software. So if you'll transfer a file from your phone to another device lower than 3.0 the transfer will like in 2.1. You can compare the power of the new improvement only when you send/receive files with a compatible 3.0 BT.
Hope you'll understand my english and my explanation was useful to you.
cheers
Related
Does any have a Widcomm or Broadcom Bluetooth stack for the HTC Touch Pro? Has anyone been successful in using a Widcomm or Broadcom stack on the Touch Pro? The M$ one is insufficient/too difficult to work with for my current needs.
What are your current needs? The stack on the TP is massively improved.
bluetooth needs
I am working on an under cover voice recognition driven data collection program. it uses a nuance voice recognition engine. I need to use a bluetooth headset for audio in and audio out. We are writing it in native c++. now that we have a Touch Pro we finally have a phone with a fast enough processor and enough ram to handle the app, but we are having some difficulty tapping into the ms stack and thought that working with a Broadcom stack might be easier. the app works great with a wired headset but we need a bluetooth one to be more inconspicuous.
Interesting app... I take it you're not planning on a general commercial implementation since having to include a new bt stack would make it less marketable. I'm not aware of any Widcomm development on this device but I'm somewhat new to it myself and not fully up to speed on what's going on in terms of development efforts yet.
will this work with the vogue?
BT Stack upgrade or mod needed.
Please don;t flame me for responding to an older post, but I need help. I have a HTC TP with Verizon with
Long story short, I purchased 2 (Not at the same time) Pioneer GPS units: AVIC F500BT (Later sold it due to this inconvenient problem) and currently have a AVIC X910BT. The problem I had with the older unit (500BT) is that when my phone establishes connection for the 1st tie to the unit, it reboots it. the phone stays on all the while and BT is enabled. After the unit reboots and re-pairs with the phone, it reboots again until the BT is disabled on the phone. Since this happened, I sold the F500BT and purchased a newer, with more features model with a different firmware. However, I'm experiencing the exact same problem. I tried the native WM 6.1 Verizon ROM and 3 different 6.5 ROMS which have the same effect on the unit.
Ok, with that being said, I've been told to come here for a BT Stack for my phone that is compatible with the unit. The Units run WinCE.
Please help...
Whenever I sync my Touch Cruise in the car (BMW) the interface lags! For example pressing the phone button on the steering wheel takes forever to pull up the phone menu on the car display. Also during a call if I press the hang up button on the steering wheel, it doesn't hang up right away. I have to keep pressing it multiple times. The actual sound quality through the car speakers is fine and the pairing is very quick so no problems there.
Is this a specific problem between the car and the phone? The car handles other bluetooth phones very well, such as the ahem..iPhone. The response when hitting the steering wheel buttons is instantaneous.
I currently have udk Syrius R8 Beta2 with radio 1.59.46.12. I read in one of the other forums on xda that it has something to do with TouchFLO. I disabled the Manila TouchFLO, turned off S2U2, still no luck. Any ideas?
I have similar problems with my XDA Orbit2 with WM6.1 and with my Ignito/Diamond with WM6.1 both with my Peugeot car BT and with Motorola BT headset.
An incoming call sometimes takes 10secs for the audio to be re-routed, PITA
I also found that if I'm running Navigon 6 and an incoming call gets picked up by the car BT then Navigon (or any other GPS app like GPSCycleComputer) gets screwed, the internal GPS gets disconnected.
I'm suspicious that the problem is due to the on chip BT and GPS.
My XDA Orbit (1) with WM6.0 doesn't have the same problem but of course it also has a seperate SirfstarIII GPS.
So, who knows, it could be WM6.1 or it could be the Qualcomm integrated chipset?
I'd like to re-install the original Orbit2 WM6.0 to see if that makes a difference but that's not completely simple as there is no full (official) O2 WM6 file available (AFAIK)
Yeah it's pretty annoying. I assume the udk ROM that I have has all the bluetooth patches, etc. I know other phones don't have this issue, so I'm hesitant to say it's the BMW bluetooth firmware. Something is laggy about the device when paired. I must say though I've never tried pairing it to a BT headset so I wonder what that will be like.
No one else having bluetooth performance issues with their car's built in Bluetooth system?
I have carkit trouble, but don't know why.
My problem is as followed:
I Drive a Renault Scenic with a Carminat Navigation System including Bluetooth Carkit
When I connect my HTC TC Everybody complains that quality is poor. Reception is louzy etc.
When I connect my HTC TD2 the problem dowsn't exist.
When I connect my Samsung Omnia the problem doens't exist ( but other problems in the phone appear)
When I connect my Nokia N73 with the current software I have a lot of problems ( even other then with the HTC )
When I connect my Nokia N73 with an old version of the software I have no problems...
All phones run the stock ROMS ( Windows Mobile 6.1 Pro ) / original Software. I first thought It might be a carkit problem, but as some phones work and others don't I tent to believe that it is a ROM problem (Maybe radio not good)
Is it possible to update the bluetooth driver / firmware?
Problem with HTC TC could be in radio driver.
But since there are problems with other devices, it could be problem with Carminat. You should check with Renault is there software update for it.
But first check if those phones are on Carminat's compatibility list...
The strange thing is that I have the problem with the nokia N73 when the software of the phone is higher then 2.69
According to Renault all Windows Mobile devices are supported / compatible.
I think it is the BT driver or Firmware. But don't know if it is possible to upgrade this to a newer version. Or to test this?
Yes,
My Parrot Mki 9100 works perfectly for phone calls, but doesn't play GPS navigation audio instructions.
Anyone know waht is wrong?
speedyb said:
The strange thing is that I have the problem with the nokia N73 when the software of the phone is higher then 2.69
According to Renault all Windows Mobile devices are supported / compatible.
I think it is the BT driver or Firmware. But don't know if it is possible to upgrade this to a newer version. Or to test this?
Click to expand...
Click to collapse
Have an appointment at the car deakership on Tuesday to see if there is an update or quickfix...
I still suspect the TC though
BT, GPS and GSM are controlled by radio driver.
Please check version, since even stock ROMs use different drivers.
So far, my version is flawless...
Polaris WM 6.1 WWE official (3.13.405.0 WWE 2008-08-21; Radio 1.59.42.15; Protocol 25.85.30.07H)
Click to expand...
Click to collapse
This is the same version I am using....
hi,
I have have quite some problems with BT connection with same radio driver see
http://forum.xda-developers.com/showthread.php?t=570153
I sent it for fixing to the dealer.
Hope a solution.
Went to the car dealer today. They updated the software and modified the microphone volume (lowered it) and the sound quality is improved.
At the car dealer they told me that they have a lot of issues with HTC phones in combination with the different carkits, although the newer phones have less problems. There is a new software upcoming before the end of the year which should solve more problems. but for now the problem is less....
I figured out why (but not the underlying cause) of the sluggishness when the phone is paired to the car. My phone shows very high CPU usage (90%) with services.exe when I look in task manager when the phone is paired. I noticed that using the actual device is sluggish, even just typing up a text. I don't know why that is. The moment I turned off bluetooth, it was back to normal.
Any idea what could be causing that?
Maybe radio driver...
I had such problem when I was on WM 6.0, but it was caused by failing radio chip...
The Wikipedia Android Version History says in GB 2.3.5 they 'Fixed Bluetooth bug on Samsung Galaxy S'.
Can anyone relate the details of this BT bug fix? Just wondering how much emphasis i should give (if any) when choosing a rom as to whether its based on 2.3.5.
Still updates for Galaxy S?
I have no idea what the problem is... but this is interesting since this is specific to the Galaxy S and I had in mind that no more update would be apply to this phone... Did Google made that fix to convince Samsung to continue keeping their phone up to date?
The maybe fixed one bug
and created another...
Since upgraded to 2.3.x (4 or 5) I have major bluetooth issues
After reboot, phone connects to car kit and conversation is heard.
However, after leaving the car and comming back, phone seems to connect to handsfree, but audio (both a2dp and mono) is not heard (not from phone and not from car's speakers...)
Serious issue!!!
I would guess it's the voice command thing. This wasn't working in Froyo, but it's working now.
Searched for this problem but couldn't find anything directly related. Is there an advanced search option on the forum?
I just got a Samsung S2 LTE/Skyrocket on the Rogers network here in Canada and love the phone so far. Only problem is when I have the phone in the car, the Bluetooth connects properly when I fire the car up, but it disconnects after a short period of time (2-4 minutes)...then it may reconnect on its own...then disconnects minutes later.
The car is a 2008 Audi RS4 which is basically the same bluetooth system used on the more popular A4, (2005-2008) so hopefully someone else has some input.
Initial thoughts
1. phone software - Maybe the phone needs a software update - this exact scenario happened on a blackberry I had a few years ago and updating the blackberry's system software fixed the issue. There is no 'firmware update' possible for the car for the record. The phone is running GingerBread 2.3.5
2. bluetooth/sleep/battery saver settings - as I've only had an Android for about 5 minutes, this is likely where I'm missing something. Is there a setting on the phone that puts bluetooth to sleep to save battery power? I've not downloaded any apps to interfere with power management yet etc. so I'm just on OEM settings.
Any thoughts would be appreciated!
This is more of a development forum than anything, so most of the folks are running custom ROM's here. But you'll still find knowledgeable folks when it comes to stock ROM.
I would try going to settings and at the bottom of the menu is a software update option. Some folks are getting 2.3.6 rolled out to them so it couldn't hurt to check and see if it's available for you right now.
Otherwise, you might try un-pairing the bluetooth connection, reboot and then try making a new pair?
Good luck.
To OP, sorry I don't have a solution for you. But I gotta tell ya, the bluetooth on this phone is pretty crappy, I'm hoping the ICS will fix a lot of Bluetooth bugs. I have an issue connecting with my Bluetooth Music Reciever (which is plugged into the AUX). I have a 2008 MB C300 and the Bluetooth wors about 95% of the time.
By the way Nice ride. RS4, same engine as the Audi R8.
Jamolah said:
To OP, sorry I don't have a solution for you. But I gotta tell ya, the bluetooth on this phone is pretty crappy, I'm hoping the ICS will fix a lot of Bluetooth bugs. I have an issue connecting with my Bluetooth Music Reciever (which is plugged into the AUX). I have a 2008 MB C300 and the Bluetooth wors about 95% of the time.
By the way Nice ride. RS4, same engine as the Audi R8.
Click to expand...
Click to collapse
thanks for nothing guys. this place sucks
just messing. Sorry, I didn't quite grasp that this was the premier developer forum vs. users shooting the **** about their phones. A buddy referred me over here when I told him about the problem.
Yeah, I've heard a few complaints about the bluetooth similar to yours Jamolah. Some guys complain that it only connects once in a while, so 95% of the time is pretty good! Mine connects right away every time which is nice...but the constant disconnect/connect/disconnect routine gets real old, and results in me turning bluetooth off. Unfortunately then you have to turn it on to use it etc.
Anyway, I'll keep trying for a solution to my seemingly unique problem and will see about an update to ICS when its available. Quite a different world, the android world (vs. blackberry or iPhone where everything's so closed and limited and simple).
Thanks for the input guys.
Hi,
if you keep your android running with the navigation app (preventing standby) do you still experience disconnects? If this helps you can try my app "BluetoothKeepalive" from the market, it automatically prevents android standby when being connected via bluetooth.
Regards
...Alex
I am pleased to report that the phone now works flawlessly with my Audi's bluetooth.
The solution? Ice Cream Sandwich / 4.0, the latest operating system available for my phone.
I upgraded the phone to ICS, and it immediately began co-operating with the bluetooth.
Is there a way to get BT 4.0 LE things working with this phone, I mean i know there might be some hardware limitations but i thought all the radio's (inc BT) were SDR (software defined radio) ? Has anyone been able to pull it off, or is there some hw tweak (or adapter) that would allow this phone to communicate with BT 4.0 LE devices? (ie. tile, etc...).
Now i understand that the stock ROM lacks all support for this but what about Emmanuel U's new KK 1.4 ROM for instance? Would just a new ROM give you added functionality (BT 4 LE) or are we pretty much stuck with due to HW chip (sorry if this is seemingly a stupid question but I thought all the radios' were software defined - and therefore be upgraded via firmware to the latest standards?
steve_77 said:
Is there a way to get BT 4.0 LE things working with this phone, I mean i know there might be some hardware limitations but i thought all the radio's (inc BT) were SDR (software defined radio) ? Has anyone been able to pull it off, or is there some hw tweak (or adapter) that would allow this phone to communicate with BT 4.0 LE devices? (ie. tile, etc...).
Now i understand that the stock ROM lacks all support for this but what about Emmanuel U's new KK 1.4 ROM for instance? Would just a new ROM give you added functionality (BT 4 LE) or are we pretty much stuck with due to HW chip (sorry if this is seemingly a stupid question but I thought all the radios' were software defined - and therefore be upgraded via firmware to the latest standards?
Click to expand...
Click to collapse
I don't use BlueTooth, but it seems to me that if a new standard was to be supported firmware-wise, it would have to show up in the device tree, and those things are usually very static (because things tend to blow up if the device tree gets modified too much).
If a radio update was available, it would have to be by someone who really knows what they are doing (i.e. the original development team). I think Emmanuel U advised someone before to not flash the radio. He probably has his reasons behind that one, and would side with his opinion.
This makes logical sense as i surely don't want to brick my device, by messing with the device tree. So definitely thank you for the advice.
Hopefully if someone ever figures it out (and its reliable) they'll post on the board here.
Thanks again
The Qualcomm MSM8260 platfrom was still Snapdragon S3. It wasn't until Snapdragon S4 that Bluetooth and WiFi were packaged on the SoC.
The Doubleshot uses a Broadcom BCM4329 for its secondary radios. It is most definitely not capable of SDR functionality.