Short of banging it with your shoe heel, i'm not sure if it will work. If you ty the hard reset please let us know where you end up. I returned my HS801 headset yesterday and I think I will send back the Bluetrek G2 (dang i liked that one too) today. I need to order and try the HBH 300 next.
Well, things have quieted down here concerning the firmware update. Yesterday the XV6600 forum was buzzing loud, and some people ran into the same issue I ran into, that is their units froze during the first attempt.
I'm not really happy with the update. My BT headset was better before the update, and I'm now experiecing resets that I did not have before the update. I wonder if there's a way to remove the update to test this theory. I don't think a hard reset would. I'll try it anyway, unless one of you have any ideas.
You upgraded the firmware, so a hard reset won't do it. You'd need the old firmware image and an installer.
Originally posted by Baghwan I called siemens today and complained that my BT connection still had static, he said they have had no problems or complaints with their "siemens" BT headset available on their web site........although they only tested it with a pre-production sx-66. Cripes i was waiting for him to ask if i wanted fries or an apple pie with my order too!
I asked if any other issues were address with the patch other than the BT but he said that was it.......jeepers......i thought i heard 3X5 cards in the background. Maybe he used to work for Compaq previously.
]
35mb download just for a BT fix that some are reporting doesn't make a difference...nice.
I'd already decided to give this one a miss but after reading everyone's experiences here now it's a definite.
I can use BT and wifi at the same time, my moto BT headset works fine (no wakeup or static issues) with BT build 3500 that I installed using the imate patch back in December.
Shame on Siemens for not having release notes with the issues that this ROM update addresses. People who paid for this hardware shouldn't have to be beta testers!
I had a bad experience with Siemens tech support right from the start -- I wanted to find out how to get the MAC address because my campus and my home network both use MAC filtering. Siemens told me (even when I escalated it to a supervisor who called me back) that it was impossible to find that out! Well at least I knew enough that I could find it myself without their help (turned off the filtering on my home router and connected the SX66 and used the admin tools to look up the MAC it was registering). But still!
Although I love my SX66 I haven't really trusted Siemens since that episode
LOL. I don't blame you. I now have a buggy SX66 that was fine before the update. I think the fact that the update did not work the first time around and locked up my device may have corrupted something in ROM.
Oh well. I'm waiting for the return label. I'm debating whether to buy another, or wait for something better.
Originally posted by garfus Even though I had the extendedROM on my SX66 for over 2 weeks, I upgraded last night, and here's what I've noticed:
1. Cannot run Bluetooth and WiFi simultaneously
2. Jabra 250 still sounds like crap
3. Noticed no performance implications
4. Does not have new radio stack (1.06.02) - not sure if I need this.
I am most up set about the inability to run Blutetooth and WiFi concurrently. Does anyone have advice?
Thanks,
Garfus
Luckily, I've had positive experience with the ROM update, although the initial update did fail.
1. I'm finally able to run bluetooth and wifi simultaneously and has stayed on almost continueously since the update. Almost because twice SX66 gave me unable to load error when turning back on from sleep mode. Reset appears to turn it back on. You might want to stop active sync process from memory before turning them on, as I read somewhere here that that might solve your problem.
2. Agreed, Jabra headsets are crap with SX66. Tried both 200 and 250, and returned to using wired headsets until hbh300 arrived. What a world of difference, and the range is good. SX66 did lose signal with the new headset once and had to be paired again, and am not sure if it was the result of ROM update. I experienced similar problem with my moto v551 with other headsets in the past, so I'm going to have to assume it is a common problem using bluetooth.
3. No difference in performance for me, but I did notice that I gained about 3 megs of internal storage memory from it.
It is possible, starting ROM update after hard reset helped in my case. Anyway, no going back for me, not that I have a choice in the matter.
Ok, so here is a question. Has anyone applied the roadcom BT Patch that supports Audio over the new rom yet? I am consider this, but not having a pair of BT stereo headphones, or a BT keyboard, I have no way to test it.
-Chris
__________________
SX66 (PH20B1)
ROM 1.42.00 WWE
ROM date: 09/05/05
Ext ROM 1.42.126 WWE (Beta 1)
Radio 1.15.00
BT 1.0.0.3900
I had a bad experience with Siemens tech support right from the start -- I wanted to find out how to get the MAC address because my campus and my home network both use MAC filtering. Siemens told me (even when I escalated it to a supervisor who called me back) that it was impossible to find that out! Well at least I knew enough that I could find it myself without their help (turned off the filtering on my home router and connected the SX66 and used the admin tools to look up the MAC it was registering). But still!
Your MAC address is shown in the Wireless LAN Manager. I had the same isssue because my school uses MAC filtering as well and I had to look it up this way.
I found this neat networking utility for PPC called VxUtil: http://www.cam.com/vxutil_pers.html . It shows a lot more than your mac address! and has other useful tools like ping or whois.
Today, I applied the new SX66 update. I followed the directions supplied by Siemens. After 45 minutes of just hanging there on the firt attempt I contacted Siemens. The Tech that I spok"toasted" your phone. You can try to disconnect your phone and try it again.
So I disconnted my phone from the computer rebooted the computer and truied again. Second time was a charm, everything went well. No my Moto HS810 is working consistently with my device.
Just wanted to post and let everyone know my problem to hopefully help someone else.
Then it must be only my SX66 whose BT quality degraded with the firmware update instead of improving. I reinstalled that firmware update twice already.
That's okay. The return label should be here soon. I just wish Cingular would send replacements without charging you $650+tax for the replacement. Sprint doesn't. They send you the replacement free, and wait for the old unit to return in a cheap UPS bubble bag.
Originally posted by lvsx66 Luckily, I've had positive experience with the ROM update, although the initial update did fail.
1. I'm finally able to run bluetooth and wifi simultaneously and has stayed on almost continueously since the update. Almost because twice SX66 gave me unable to load error when turning back on from sleep mode. Reset appears to turn it back on. You might want to stop active sync process from memory before turning them on, as I read somewhere here that that might solve your problem.
Replying to my own post regarding this issue. Initially, I could use both the BT and the wifi, but now that I've installed some programs, its back to the old ways Its very discouraging.
As a test, I've reinstalled my first backup which was made after installing few essential programs. With this, both BT and wifi works ok, but with reinstalling subsequent backups, its not good. Anyway, it appears culprit(s) maybe one of the today plug-ins.
Anyone run into similar problem with BT and wifi? Installing 3900 batch didn't help any.
Are you sure you cannot even get into the Bootloader mode?
The combination is Power + Record + Reset.
Once you're in the Bootloader "USB v2.07" or whatever screen, run the update again and it will take over from there.
As a complete moron, I force-applied a CDMA image on my PDA2K GSM and couldn't boot past the splash screen. By going into the Bootloader, I was able to run the proper upgrade and voila, I'm back in again.
As long as the Bootloader is available and you've got a good USB (2.0?) connection, you should be able to recover even the worst of flash mishappenings.
I have been getting frequent flash memory errors requiring hard resets to clear the error. I don't know why. I then did a firmware update using the old Siemens software and it died. All I can see is a black screen that says "Serial" at the top and "USB v2.006" at the bottom. If I'm docked, it says "USB" at the top. I assume this is the Bootloader screen.
The problem is I'm using Vista 64-bit. My device manager identifies the PDA as "Microsoft USB Sync". However, Windows Mobile Sync Center does not recognize the device to be connected. I therefore cannot rerun the firmware update. The update cannot identify the device to be connected.
In need of some help, I tried the update and had an apparent brain fart. Suffice to say the phone is now not working and is displaying 'serial' or 'USB'. I think my Updater Tools may be faulty or I don't understand how to use them properly. Can anyone help with solving this problem? any help will be much appreciated. Thanks.
In need of some help, I tried the update and had an apparent brain fart. Suffice to say the phone is now not working and is displaying 'serial' or 'USB'. I think my Updater Tools may be faulty or I don't understand how to use them properly. Can anyone help with solving this problem? any help will be much appreciated. Thanks.
No worries; happens alot. Go to one of the links below and do a search. You need to provide more info on what you did, your OS, etc. in order to diagnose your problem.
No worries; happens alot. Go to one of the links below and do a search. You need to provide more info on what you did, your OS, etc. in order to diagnose your problem.
Hi ppl,
Just spent the most part of the night 'tinkering' with the Blueangel. The result of which is this,"its alive", the update works fine from a PC running XP and it works better when the battery has life in it. I've found that the 'G' at that top of the screen is absent and replaced with an "X" and I still have the problem of not hearing when in a call. But everything else seems to work well including the media player 10. I will check around to find solutions. Hope this helps someone. Thanks again a_ok2me and chris from the standardization project.