I have an unbranded SX66, the AT&T version.
Rom info as follows:
Rom: 1.32.10 WWE
Radio: 1.02.10
Protocol: 1337.35
Ext Rom: 1.32.115 WWE
My only real issue is the crackling that occurs with my recently acquired Jabra 250 headset. The audio seems to be ok as long as the phone is close by and in line of site. Even then it can still be crackly though.
I updated the bluetooth stack to 3900 from 3500. I didn't update the radio stack, even though it was suggested. I guess I'm wondering if installing the v1.33 update from Siemens is worth it. Some posts seem to say it is. Others say it's not. There doesn't appear to be much documentation as to what was fixed in the bluetooth stack other than connectivity problems, which I'm not experiencing.
Anyway..any thoughts and/or suggestions are appreciated.
I've found the site informative and helpful.
Thank you.
Never mind...found some other threads on the subject
Appears I can not use this update becuase I have the AT&T varriant of the phone.
Thanks all. Guess I'm stuck with the crackling audio.
If you haven't been there yet, the SX66 Standardization Project has AT&T versions of the most recent ROMs.
I have looked some. It appears that i have no turning back if I move forward with one of those roms, because I have the AT&T version.
Being new to this, I guess I'm slightly paranoid that I will lose my device on a hiccup.
Can't complain then, I suppose.
I'm investigating GPS now with the device to see if there are known issues using a bluetooth receiver with this device.
Thanks again..
Related
Hi gentlemen,
I have a QTEK 2020 and have a very annoying problem: Every few days my phone loses its connection to the cellular network. When it happens - nothing is seen; everything looks perfectly normal (even shows GSM reception), however no-one can call me. When this happens, I can't initiate outgoing calls either. Only a soft-reset fixes the problem.
I'm using ROM version 1.72.00WWE and Radio 1.17.00.
I saw in this forum that there's a newer Radio version - 1.17 and I was thinking maybe it will solve the problem I have.
However I'm seeing updates to MDA II and XDA II.
Can anyone advise me what to do? Is there an upgrade to QTEK as well? If not - can perhaps someone "compile" a neutral version (no branding)?
And another question - is it possible to upgrade just the Radio?
Any help would be very much appreciated!
Thanks,
Ariel Cattan
When I turn on Bluetooth on XDA IIs, I got this error message :
"The bluetooth radio radio failed to turn on due to insufficient driver memory available. You must perform a normal reset before you can turn on the bluetooth radio."
Anyone can advise how to resolve this ? Soft reset does not cure the problem. Thanks.
have you upgraded to bluetooth stack version 3900 ???
if you have then im fresh outta ideas, if you havent find this at our FTP site,
ftp://xda-developers.com/
login and password = xda
got the same problem when i installed one of the bluetooth upgrades on its own. then i installed the new rom and everything was fine. not sure where the connection is but thought id share my problem
Problem solved.
By the way, what is the latest version of ROM for XDA2s, and where to get it from ?
Thanks.
So I was wrong.
After upgrading the BT upgrade, things was OK yesterday. But this morning i got the same error again.
Went to ftp://xda-developers.com/ as suggested, can anyone mentioned the filename of the ROM mentioned by thakkergaurav above ?
Thanks.
The latest ROM is 1.40
You can find it here: http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel
Hmmm..... :?
This BT issue is really getting to be NOT FUNNY! :evil:
Running the new ROM 1.40 and BT 3900 I'm now getting the "no sound" problem on the handset and caller cannot hear me on a HS801!
I use the turn on/turn off BT trick or soft re-set and the handset is OK for a couple of hours but the HS801 still does not work even though its OK with my old PocketPC,a nokia and a Motorola V3!
Is there any consistancy with this problem? It seems the different ROMs, Radio Stacks and BT versions are being effected.
Well, emailed the tech support, and all they can say was ...
"There is a ROM upgrade in development which is in the final stages.
We request your patience as we are trying to release the upgrade as soon as possible."
And that was 2 weeks ago.
even my bluetooth is upgraded to 3900,
i get the same error message also..
i cannot believe a 96mb memory is still not enough
i never get this kinda nonsense when i was using the 5450 ipaq
my today plugins was all over the screen and I had never encountered low memory...
I had the same problem but I have a Harrier not a BA so I thought it was related to that and you BA guys wouldn't get it.
Anyway, the solution on the harrier was to
-turn flight mode on
-soft reset
-turn bluetooth on
-turn flight mode off
Hope this helps
Here is a possible solution from wiki:
The ExSenetoR wrote:
Delete Run_BTTrayCE_10.lnk from your Windows\Startup folder and soft reset. Now you wont have the BT icon on the tray bar, but you wont have the no sound problem. If you still need bluetooth you can start it from the Windows directory as BTTrayCE.lnk.
Have fun.
Click to expand...
Click to collapse
Have not tried this myself, but I believe others have had success with it. You may want to save the file somewhere else, in case you want to reinstate it later...
Hope this helps
Chris
I posted this in another thread.
It really does look like a combo of the 1.40 ROM and 1.12 Radio Stack that is causing this problem (in this case, anyway. See sig). After trolling various forums, it seems that both BT build 3900 and 3500 are having the same issues.
IMHO it seems that the Blue Angel is trying to send the call to my HS801 even when BT is not activated.
Has anyone had a good look at the current radio stack? I've tried contacting Broadcom (BT chipset supplier) but it has been 3 weeks with no answer.
I've done the Run_BTTrayCE_10.lnk workaround but this is only a bandaid and I don't really have enough experience to attempt to cook the ROM. Any ideas?
I have a Motorola HS801 as well and I can receive calls just fine but when I make calls the other party can't hear me. I'm giving up on the HS801 - it's a cheapie anyway and I don't know of anyone else who's got it working either. Running BT3900
Had my m2000 for just over a week now and what a crock of poo. No volume out of speaker (well documented problem) and bluetooth connection that is turnip (might as well be two bean cans and a bit of string). I can get it paired with my bluetooth (in built in BMW) but every time a call comes in it drops it. Is there a patch for the bluetooth if so where do I get it ??
The other thing that winds me up is that orange UK will not acknowledge the above well documented problems but having mentioned "fit for purpose etc" they are sending me out a replacement and if this does not work I will change the phone completely. I did not change it earlier as I got a brilliant car mount from PDAmods and I will be out of pocket if I change the phone
To sum things up please advise should I ditch the phone and go back to my ipaq 4150 or are there software patches out there --- "somewhere" ????????
just checked rom 1.40
radio 1.06.02
if that helps anyone
FWIW, ROM 1.40 is OK, but I'd advise an upgrade to Radio ROM 1.13 & check if bluetooth version is 3500 or 3900.
I now use 3900 & make sure bluetooth is permanently on. Since then, I have not had the problem with "no Volume"
FWIW, ROM 1.40 is OK, but I'd advise an upgrade to Radio ROM 1.13 & check if bluetooth version is 3500 or 3900.
Click to expand...
Click to collapse
I've used the 1.13 radio ROM on my Orange M2000 - it worked fine for normal phone calls but GPRS went a bit mad with long, long connect times and frequently wouldn't connect at all. Dropping back to the 1.06.02 ROM put everything right.
What are they doing with their rom upgrades either cooking in kitchen or warming in microwave.
In this competitive environment, still checking and checking. Despite all, roms will be having bugs as always so what's the point to keep customers waiting.
T-Mobile already have released a new rom, so that makes 3 which includes orange and imate.
Still no word from qtek and o2... wonder what's taking them so long. Maybe they will release with stereo bluetooth?
T mobile
I think it is not an upgrade as it is the same which was released in french language now is in WWE.
It does not have A2DP and MSFP which is now the part of imate and orange.
Sorry,
I based my assumption on version number and rom date which is newer but I guess that wasn't enough to be cosidered an upgrade.
my mistake
cheers
This is exactly what they are trying to play smartly
Although I've never tried an old T.Mobile ROM., i found their newest to run as fast as the orange and Imate ROMS generally speaking.
Also the screen rotations are at par with the other 2 ROM's....
Re: T mobile
rikram said:
It does not have A2DP and MSFP which is now the part of imate and orange.
Click to expand...
Click to collapse
??? None of them have A2DP.
I thnk the T_Mobile has some own version of Stereo over bluetooth so I'm lead to believe.
I don't have my own stereo headset so can't really say
I'm running the T-Mobile ROM on my JasJar at the moment, purely because I want Stereo Bluetooth, and I'm not too bothered about push e-mail...At the moment, I've gotten used to my phone checking every 60 minutes, which is enough for my personal e-mails (and I have a company B****berry).
I've upgraded the Radio to 1.09.00, so my details are as follows:
ROM Version: 1.20.32 WWE
ROM Date: 11/16/05
Radio Version: 1.09.00
ExtROM Version: 1.20.120 WWE
I'm happy. I have no problems streaming all of my stereo ogg files with the latest version of Conduits Pocket Player, and as far as I can tell, the OS is no slower than it was when I was using the latest imate ROM. The fact that I happen to be on T-Mobile UK helps, because all my connection details etc. are already loaded after a hard reset.
What I can't believe is that this ROM has been around since November... Stereo Bluetooth works without a hitch, and yet: a) I hadn't heard about it until last week, and b) no other numb-nuts OEM's have managed to implement a stereo Bluetooth protocol of any description yet.
I will of course upgrade to an AKU2 ROM when someone (i-mate) finally pulls their finger out and puts push e-mail and stereo bluetooth on the same ROM!!!
Actually, the ROM has been available since last year but they first released it in GERMAN!!!! hehehe
THey just released the english one....
Now before anyone goes bashing me for not searching the forum, lemme tell everyone, I've done just that. I just haven't found the answer to my problem.
I recently acquired an 8525 (which I'm loving BTW ). I have a Jawbone headset that pairs up fine with all of my phones (BB Pearl, 8125, & 8525). Only problem is, I can actually *use* the Jawbone with my Pearl and my Wizard, just not my Hermes.
I've paired, deleted, and re-paired again but to no avail. I've tried to get an actual conversation going using 3 different ROMs: AT&T's official WM6, Schaps 4.30 Full, and vp3G's 3.62 Full, but nothing works. I've reset the Jawbone more times than I can count, and I still can't use it.
ANY input on this would be GREATLY appreciated, since I actually *need* to use it for work...
BombaMyte said:
Now before anyone goes bashing me for not searching the forum, lemme tell everyone, I've done just that. I just haven't found the answer to my problem.
I recently acquired an 8525 (which I'm loving BTW ). I have a Jawbone headset that pairs up fine with all of my phones (BB Pearl, 8125, & 8525). Only problem is, I can actually *use* the Jawbone with my Pearl and my Wizard, just not my Hermes.
I've paired, deleted, and re-paired again but to no avail. I've tried to get an actual conversation going using 3 different ROMs: AT&T's official WM6, Schaps 4.30 Full, and vp3G's 3.62 Full, but nothing works. I've reset the Jawbone more times than I can count, and I still can't use it.
ANY input on this would be GREATLY appreciated, since I actually *need* to use it for work...
Click to expand...
Click to collapse
I am currently using my Jawbone with Schnaps 4.01 Lite rom and no problem. Before that I have been using all of Matt's Pandora Kitchen roms, right up to the latest and never had a problem. I ran Schnaps 4.30 Full rom too, but really can't remember if I used the Jawbone during the testing time. If someone else can't help I can flash that rom again and test the Jawbone with it too. Let me know ho wit goes.
works with vp3g3.62. no issues, didnt require anything special. Does bt radio on your 8525 work?
I have an 8525 running Schaps 4.30 with radio 1.48.00 and mine is working. I did however have to return one Jawbone because it would connect and I could hear the conversation but the mic didn't pick up my voice. I tried that one on my wife's razor and it had the same symptoms though. What radio are you running?
Using with TNT's latest ROM and no problems, however not real impressed with Jawbone so far. Most people I call say it sounds "tinny".
mthomas said:
works with vp3g3.62. no issues, didnt require anything special. Does bt radio on your 8525 work?
Click to expand...
Click to collapse
AFAIK, the BT radio works. Like I said, I can pair up with it just fine, and even see the other BT-enabled phones/devices at my job. I just can't get any type of audio from my JB. I'm currently using vp3G as well.
UPDATE: Well to be on the safe side, I tested my Jawbone on a couple other phones; sure enough it's working fine, so it's got to be something up with my poor Hermes... Any advice?
Mine Jawbone Works fine also. I remember when I first got it I was having trouble with my sound. I remember changing the audio bitrate from 48 bit to 44 bit in the advanced config utility 1.1 Also try changing the stereo setting to mono.
May help you out, hope so.
Just a quick update: I reflashed vp3G's 3.62 ROM, reset my JB and repaired it; same effect, nothing. Just to be on the safe side I paired the JB with my Wizard, BB Pearl, and a couple of phones at my store and it works as it should.
@ mthomas: I'm using 1.48.00 for my radio. Since you and I seem to have the same type of setup, did you install any other cabs that help your BT out?
Do you have another Bluetooth headset to test. Even thought it can pair ok, it only means the "data" channel is working. The problem could easily be the voice channel which is not working. If possible, may be borrow another headset to try.
That's my next idea. I think I have an old Plantronics I can charge up and test out...
*BUMP!*
Gotta keep this fresh. Funny thing I noticed though: when I have the Jawbone connected and the phone rings, I still hear it's little tone in my ear, but no audio comes or goes through. No registry edits have been made; I've even done a hard reset, re-paired and tried again, to no avail.
C'mon you guys! Why am I the only 8525/Jawbone user around here that *can't* use his Jawbone??? Help me out here...
wish i had the answer. im using the most current att radio 1.54.07.00. how did your device work w/ another headset?no additional tweaks
Okay, now I'm getting pissed.
I tried using my old Plantronics 320. It pairs fine with the Hermes, but making phone calls is a no-go.
The only thing I removed (from anyone using vp3G's 3.62 Full) was Sleuth's PTT Fix; I need PTT more than being able to re-map the button. So I doubt this is the culprit.
WTH can't I use my good Jawbone with this thing?!?!
Quick *bump*
Same Problem
I have tried everything, I can hear the calls just fine but no sound from my mic. I have paired with other phones & it works fine. Please let me know if you find a fix!!
UPDATE: I tried using a Moto H700 and a Plantronics 340-no dice. Now I'm starting to think if it's a BT stack issue...
Now I'm completely stumped. I just flashed back to the original ATT WM5 rom, paired up, SR, then made a phone call to my 8525 from my house line. Jawbone rang in my ear, sure. I answer the call, no sound.
Could there be a problem with my BT radio? And if there is, how can I be sure/troubleshoot it?
Just throwing someting into the pot. have you tried unpairing it with your other phones? I know i was trying to pair my to my wifes and it would work because it was paired to my phone. Try deleting the relationship between the other phones. Other than that if its new enough just take it back and get another
myv6mustang said:
Just throwing someting into the pot. have you tried unpairing it with your other phones? I know i was trying to pair my to my wifes and it would work because it was paired to my phone. Try deleting the relationship between the other phones. Other than that if its new enough just take it back and get another
Click to expand...
Click to collapse
Good thought... But I already did that, still no joy. In fact, I just flashed over to HTC's official TyTN rom, and still nothing. I'm going to call a friend of mine and see if I can get it to work on their 8525. Here's a good ? tho: Should it matter if it's Cingular or AT&T branded? Are there any differences in hardware between the two types? Or could it be a faulty BT radio? I'm racking my brain trying to figure this out.
Worse comes to worse, I'm sure I could exchange my Jawbone; I *do* work for AT&T so it should be okay...
Okay, here's another question: If I were to flash *ALL* the way down to the original Cingular shipped ROM, RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship, would this have any effect on the BT stack? I'm only asking because I can't seem to find any type of information about replacing the built-in stack (outside of the Widcomm project and that's too beta for me ATM), and I still can't understand why so many headsets that I've tried with this damned 8525 don't seem to work, but so many people here @ XDA can use theirs. There's no differences between the Cingular branded and AT&T branded models (at least hardware/software-wise), and if I pair up my trusty Jawbone with another 8525 (AT&T branded, btw), it works fine.
I know I've been going back and forth with this, but I did pay a good amount for my 8525 and I don't want it to be partially or mostly functional. Hell, if my poor Wizard can handle my Jawbone, why can't my Hermes?
BTW, thanks for all of the suggestions you guys have given me to help me with this problem. Even though none of them have worked, I still need to give props where they're due.