Related
Hi folks, I have a Qetk 9090, the rom is WWE 1.22 the Ext rom I don't remember but I it is not the latest one. Anyway
Before the 1.22 rom, I tried Skype on Wifi no problems everything went well, not if I receive a call or make one after 30 seconds the call crash, the Wifi seems to crash as well, if I stop it and restart it, the Wifi software won't work but the wifi light will blink... I need a soft reset to make it work, if I do the same test at thome calling my PC with my PPC, no problem... what is going on? Is that a Wifi Issue or Skype ?
Thanks
My XDA IIs has always done this. Skype know about this issue, and there is a thread here about it as well. They (skype) say that its the Blue Angel, not skype. It does not appear to be only the blue angel either.
Interestingly, for me it works if I stand next to my AP while using it. Hardly convienient!
Nigel
i use mine over bluetooth activesync on my xdaII (no wifi) and encounter the same problem.... only happens when i use skype though.
I have had major problems with Skype before version 1.1.0.6. This version doesn't have a problem on my IIs. As a matter of fact, I leave Skype and FWD on for more 48hrs without it crashing. I have had experinces with having Wisbar advance installed and random application would crash. These voip apps would not have the chance of being installed if I didn't have a wifi network.
I also have 1.1.0.6 but experience the same symptoms. I've read some skype-related issues on xda-dev and believe it could very well be the wifi's subpar quality.
Just now I tested a skype call sitting right next to the router - no problems at all. moved into the living room - other party reported distortions in my voice. moved further away, into my room - distortions worsened, until finally the wifi connection dropped to nearly "zero" (no curved lines around the wireless lan manager icon on Today screen). immediately following, connection totally terminated, and the pda's internet will not WORK at all, despite still showing status of "connected". only solution is a soft reset. :evil:
nomadman, did you find that the 1.40 ROM upgrade helped at all? as a last ditch effort, I will probably try migrating over to 1.40/1.12radio to see if things improve. ( see http://forum.xda-developers.com/viewtopic.php?t=22429&highlight=skype )
kia do not upgrade the rom counting that it will increase the range of wifi or bt. i have not noticed any distance increase upgrading from 1.33 and the last radio version. i upgraded because i wanted to learn how to upgrade the rom. i can get 10 to 12 meters from my AP. thats with a hallow wall and a cement exterior walled home.
nomadman said:
kia do not upgrade the rom counting that it will increase the range of wifi or bt. i have not noticed any distance increase upgrading from 1.33 and the last radio version. i upgraded because i wanted to learn how to upgrade the rom. i can get 10 to 12 meters from my AP. thats with a hallow wall and a cement exterior walled home.
Click to expand...
Click to collapse
Thanks for the warning. I seem to consistently get BAD reception from the router to my room, which is less than 8 meters away
I just confirmed that the Skype that comes with ROM 1.40 is 1.1.0.7... so I may just give THAT a go afterall as I'm all out of options..
Are you getting good distance with a desktop PC? I wasn't aware that Skype is included in any ROM. At least it wasn't included in my 1.40 upgrade.
good news to report: I finally took the plunge and upgraded to 1.40ROM, and my Skype via Wifi issues seemed to have dissappeared!
Very prelim info and will need further testing tonight at home, but just now at the office I was able to talk for over 8 minutes with NO disconnections. veletron and others who have this problem, this may just be the fix!!!
Skype is definitely included in 1.40, at least in the 1.40 I-mate rom that I upgraded to today. The version included is 1.1.0.7.
Great news m8. can you extract the 1.1.0.7 cab and upload it. the skype site only has 1.1.0.6 available for download.
Skype 1.1.0.7
Try here:
ftp://xda:[email protected]_ROM_140176_WWE/Default_SkypeForPocketPC.CAB
Please post the version number and I will update the wiki page for that EXT Rom. Thanks
Thanks for pointing the right direction m8. Indeed this is Skype 1.1.0.7.
Anytime dude. Be sure to post your experiences with 1.1.0.7.
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
I have an interesting situation with my Orbit. This never occurred with WM5, but only since WM6.
Description:
After a fresh boot, the device works perfect, and connects to GPRS when needed, and I am able to direct push my email all day long. Now, if I go into Comm Manager, and stop the phone radio, and then start it again, I am no longer able to connect to GPRS, and neither are any other applications. ActiveSync and DP don't work anymore, neither does IE.
The only solution to the above is to soft reset the device again, and things go back to normal.
Troubleshooting:
I've tried the regkey to keep GPRS always on. I've also tried to disable any today plugins that could be causing this issue. I've even tried a hard reset, but the same behaviour occurs. Oddly enough, this problem also occurs on a WM6 based Hermes device, and never did before when using WM5.
Something weird is going on with GPRS and WM6 in general. Sometimes, I will be on the train without reception, and when my phone gets signal again, GPRS will say it is connected, but it is not. I have to soft reset.
Needless to say this is annoying. Can somebody confirm that this issue exists with the base O2 WM6 rom? What about some of the other ROMs here that you guys/girls have? Does the same behaviour occur? My ROM and radio are just the defaults, no upgrades, etc.
N.
Hi There,
I am well aware of the problem, I currently work in a telecoms company and the main device we ship out is the XDA Orbit (Artemis).
Currently we are downgrading all devices so as to ignore the problem, but a permanent solution is being worked upon.
The HTC Touch's radio is identical to that of the Artemis, this problem does NOT exist on the Touch (Thanks for testing Pof!) So I atleast have ground to work upon, it is not related to the radio itself but the RIL (Radio Interface Layer) driver.
I'll let you all know if (or rather WHEN) I find a solution.
i've had loads of trouble with this issue and here are my findings:
the dopod sea 3.7 rom and and anything else based on it are the worst affected.
the o2 wm6 rom isn't too bad
tom and meschle's roms are both pretty much fine
I do a 20 minute tube journey every day so i have tested this quite well!
cheers
alex
I'm having the same issue in the Artemis Touch 2.1 Rom.
I found that when I disabled the Phone option, the Flightmode-option would enable. Now, when I want to enable the phone, I tab the Flightmode option to disable Flightmode. It then enables the phone automatically and successfully opens the GPRS connection.
Just done this a couple of times but for now this seems to be a workaround.
Read 'seems'
GuyBrush1978 said:
I'm having the same issue in the Artemis Touch 2.1 Rom.
I found that when I disabled the Phone option, the Flightmode-option would enable. Now, when I want to enable the phone, I tab the Flightmode option to disable Flightmode. It then enables the phone automatically and successfully opens the GPRS connection.
Just done this a couple of times but for now this seems to be a workaround.
Read 'seems'
Click to expand...
Click to collapse
The times I have had the issue with the O2 rom and the v.occasional times I have it with Tom/Meschle roms restarting the radio via flight mode always fixes it. With the Dopod and other 3.7 roms the whole radio seems to crash and you can't even get it into flight mode so soft reset is the only option.
This has been tested on all versions of the Artemis radio that are available.
same problem here on prophet. can connect. if i go ffline due to no signal, i cannot connect. after i switch to flightmode and activate phone again gpry works again. any patch?!.
holzzelt said:
any patch?!.
Click to expand...
Click to collapse
No patch, just better roms.
Hello there,
What I Have: Att 8525 Herm100
Rom: Att's Mobile 6
Everything is stock but the extended life battery
The problem I am having is when ever I try to activate my WiFi the phone doesn't do anything. I am not sure if there is a wifi card or not but that's want I want to know. I have tried everything from activating it in com manager to going into the settings and activating it manually and nothing happens it acts like I didn't even hit the button to activate it. Is there a wifi card in the phone or is it integrated on the motherboard in the phone. Note: I bought this phone off e-bay and the wifi never worked when I received the phone.
I am new here and if there is a post about this already I am sorry.
I hate it when that happens.
To begin, there were two ATT OEM WM6 roms relevant to the 8525 that I noticed deep in the bowels of XGA.
I chose the later file (higher revision numbers) I found it here:
http://wiki.xda-developers.com/index.php?pagename=Available Original Shipped WM6 ROM Versions
From comm manager when I click the tower button on within a second the spinning windoze icon shows something is happening. It then starts "sniffing" for my preset wifi connection (ATT supplied 2wire portal 802.11g).
Now, if yours does not show the spinning windoze working icon when you turn on wifi? There obviously is a problem. This could be software, or hardware related (duh). If there is no error message related to "wifi is not an option, unavailable, or screwed" then my first guess is there is something missing or damaged in the ROM update that was applied to your device. As far as I know all 8525 (herm100) were shipped with wm5. It had been mentioned in the volumes of xda that the first AT&T WM6 rom was a little buggy. Try the later released AT&T WM6 update.
It was a run file so no muss no fuss. Sync the phone run the update from the pc, three minutes later the phone is flashed to ATT WM6 professional.
You could take it to a ATT shop? But, I think that without a doubt they would hand it back and say you need a new phone with a 20 year contract and 3g data plan even Obama would blush at.
Try the hard reset. take a picture of the startup screens so you have the numbers and see if the wifi startup is working after the reset. If not then compare the numbers to the above mentioned roms. If the indications are you have the first issue of WM6 from ATT try flashing the second release. If that still fails then your device could indeed have a hardware problem.
The wifi is indeed built into the system and if that chip on the board is not working it could be a overly expensive problem. Possibly a shop has a working board they would swap out cheap? Otherwise, it is a fun phone you can keep notes on, run gps software if you have a bluetooth gps receiver and software like tomtom.
To be honest the wifi on my 8525 has been convenient when around the house to check the local weather radar when I hear a thunder outside, or browse headlines from the porcelain room or even leave messenger turned on incase a gamer friend is looking for someone to get shot up in a game.
I have used the live search voice thing to amaze the neighbors once. But, the limited range of wifi is a real drawback to how truly wonderful that addition could be.
HELP Please! Wi-Fi not working!!!
Hi to XDA all users !!!
MY Hermes - HTC TyTN [Herm200]
I bought HTC Hermes myself year ago.
there was flashed a WM5.0, I've just downloaded from here HARD SPL & WM6,1 (Custom) Flashed.
Wi-Fi will works on WM5.0.
Well here I am at 6.1 flashed and now is not working Wi-Fi. When i pressed Power ON - loading long and nothing happens.
Other methods are also tried on Commanager and Settings - but did not help.
What do I need to do my dear.
HELP!
Thank you for your attention!
Hi Nurk.
Since the wifi worked on wm5 but failed after the 6.1 flash. I would guess the problem is in the 6.1 components. You might start with contacting the kitchen rom you employed for WM6.1 thread and see if this has happened to others. Next step would be to check the radio rom version. I did see on xda an assortment of Radio roms.
If your not totally in love with the current rom you have flashed? Try another 6.1 or even a 6.5 and see whats poppin.
and what you have in HKLM\Software\HTC\CommManager\WLAN\DeviceName?
utak3r said:
and what you have in HKLM\Software\HTC\CommManager\WLAN\DeviceName?
Click to expand...
Click to collapse
I have get this from registry:
HKLM\Software\HTC\CommManager\WLAN\DeviceName - {98C5250D-C29A-4985-AE5F-AFE5367E5006}\TIACXWLN1
Hello everyone,
I'm having a problem with the RCD 510 Premium Bluetooth kit that is installed on the new VW Scirocco and its been troubling me for over 2 months now.
When I first got my Scirocco the Bluetooth connection was working fine (for 3-4 months). One day out of a sudden the Touch Pro II was not pairing anymore with the car's bluetooth kit.
At the time I was using Windows Mobile 6.1 that originally came along with the phone. I tried the basics - deleting the connection, re-pairing - with no success.
So I gave a shot at phone's factory reset - still no luck. The phone is recognized when I use the "Device Search" function on the car, it prompts me to enter the pass code provided, I do so, the phone loses the GSM signal (which of course is normal) but then suddenly I get a message on the RCD510's main screen "No bluetooth connection to phone" that lasts for about 2 seconds.
Since the problem began, I tried factory reset the phone (as I mentioned before), and tried pairing before installing even a single software, still no luck.
I tried multiple ROM's in the meanwhile (I mean third-party ROMs from this forum) and now I am using the official Windows Mobile 6.5 from HTC for my phone.
I also did many tests using third-party applications for the rSAP protocol (JetWare hands-free extension, SAPSettings, some patches and drivers found around the net here and there) even though there is native support for rSAP since the first firmware that came along with the device.
As I mentioned before, the phone was pairing fine the first 3-4 months.
Please note that this phone uses the Widcomm Bluetooth Stack - not the Microsoft one.
Any help/ideas would be greatly appreciated.
PS: I apologize for the big length of the post, but I believe the more the information I provide, the more the chances to get proper help
Sorry i cant help you but.. I want your CAR...
Any pics?
Well.. try this
Unhook the cars battery. Let it reset the radio (make sure you have the radio code if any) and try again.. maybe the radio is holding some sort of setting. Resetting to default (like with the device) might do the trick..
.
Thanks for the idea. I'm kind of worried though plugging out the battery, because there are many settings besides the radio that probably will be lost if I do so.
You know all these new cars and their complicated electronic sensors...I don't mind losing minor settings for the car that I have adjusted, my main concern is that if anything goes wrong, I will probably have issues with the car's warranty. I still have 2 and a half years of warranty.
I' will probably have a talk with the dealership before doing that.
Many thanks for your thought though
hi i like to know if pairing went okay with the 6.1 rom because if so maybe when you switch back to this rom problems are solved
Nop
Unfortunately no
It was one of the first things I tried. Switching back to the official 6.1 ROM. I actually kept it saved on my hard disk and I tried it a couple of times - I mean when I tried other ROMs from time to time - hoping it would resolve the issue.
And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
First logical thought would be that something has changed in the car's settings. But I have an Athena X7500 that pairs fine with the car up to this day. My car's dealership isn't much of a help...
Second thought - phone settings mess-up. But as stated in my original post, no factory reset helped, no switching to other ROMs, no playing around with settings.....
I'm really desperate. I'm thinking to switch to another phone, but besides this problem I'm quite satisfied with the TP2. And I do "need" Windows Mobile based phones, because I sync with Thunderbird's Lightning via BirdieSync for a long time now, and I am not willing to revert back to the horror days of MS Outlook. I carry my TB profile for over 2 years now and its customized the way it suits me for manipulating my 10+ email accounts.
Thank you very much for your reply though
Any other thoughts/recommendations?
i downloaded firmware 1.20 from volkswagen hope this will help me will try tomorrow with my laptop i am with a touch adapter connected to rns 510 no pairing with tp 2 at the moment for me the only workable solution is a duo sim with my old blackberry bold meanwhile i love he TP2 so hope i can get it to pair with my premium touch adapter volkswagen carkit any other suggestion or solutions are very welcome cheers
And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
what radio where you on first couple of months
Nice thought about the radio....but unfortunately I don't remember.
Currently I am using v4.49.25.17 that was upgraded with the latest official HTC firmware of WinMo 6.5 if I am not mistaken.
I am 90% positive though that the problem started before even upgrading, back when I was using the first release of WinMo 6.1 and the unknown version of radio, and everything was working ok at the beginning.
I know, I am not helpful at all but frankly, this problem surprises me as much as you.
You mentioned a firmware upgrade - for the RNS right? Not the RCD....
Do you by any chance happen to know if there is a firmware upgrade for the RCD510 and where can I get it from?
Thanks for your help.
looking-g:
I just realized that you are having a problem with the RNS.
Did you had this all along? I mean, did you ever managed to get it working and then it stopped, or you never had it paired?
I am just asking to see if I can be of any help...
well the problem is not with the rns 510 but with the touch adapter which come delivered as premium carkit i use to pair everything with it blackberry,s nokia,s and also a touch dual (niki) without any problem but now with my new phone the tp2 its not pairing it also never did after i fill in the pincode it gives an error message it should connect with the touch adapter my car by the way is a golf gti mk6 cheers, mark
You kind of lost me there.
What do you mean "touch adapter"? Is this a component of the RNS 510? Because I have never heard of it...
Have you determined a solution?
I just picked up a new VW Jetta with premium bluetooth and it worked the first time and not since.....
You guys are scaring me -- I have an Audi A3 TDI scheduled for delivery in January, and it'd be a bummer if its Bluetooth didn't work. FWIW, my current car has a Sony MEX-BT3700U headunit and the Tilt 2 pairs with it in both handsfree & A2DP modes.
3waygeek: You will be probably fine. I think Audi does not have anything to do with Nokia regarding building their units.
Wish you best luck with that.
Extra info
Some more information regarding the whole subject:
I found out that when I press the "Emergency Call" option on the touch screen of the RCD510 (i.e. try to call the international emergency number - 112) and then immediately end that emergency call, the next time I try to pair the Touch Pro 2, it does pair!!! But it has no signal at all, and if you try to make a call you get a "Dial up error" (or something like that, can't remember exactly)!
Any ideas what could be the reason for that?
Thanks.
Your problem is common to VW/Audi's. Chances are the car kits have the rSAP Bluetooth unit. I had exactly the same issue in my A6 using rSAP, as soon as i upgraded to wm 6.5 the problem went away.
Yes, indeed the car kit uses the rSAP profile, as well as the Phonebook Access Protocol (PBAP), but both of these protocols are supported by the TP2. Actually the rSAP functionality I believe is support in Windows Mobile 6.1 and above - I mean besides the fact that your phone's BT radio must support it in order to work correctly. (Without being entirely sure for the above comment).
And some more info for those who are willing to give an opinion:
I did eventually decided to remove the car's battery. I left the car without battery for approximately 40 minutes. Now here's the strange part: All the settings of the card indeed reset (window settings, light settings, etc) BUT the RCD510 was not affected at all by the battery removal! Yes, as weird as it might sound, the station list was there, bass/tremble customizations were there also, everything in place (regarding the radio unit always).
Side note for all those who might remove the battery from a similar VW car:
As soon as I plugged the battery back on, I had somewhere 15+ warning indicators on my dashboard turned on. From ABS malfunctions, air pressure, EPS malfunctions etc. But after rolling the car for 3m or so everything turned off. Back to normal. Probably had something to do with the electronic sensors giving proper signal to the car's "brain". Just my opinion.
Now, besides that - the fact that removing the battery didn't perform a reset of the radio (RCD510) unit, I also tried reverting my Touch Pro II to a WM 6.1 cooked ROM - don't remember which one exactly - but that didn't helped either. Same stupid error message after pairing for 2 secs: "No bluetooth connection to mobile phone".
And to confirm again: My X7500 (Athena) with a cooked WM6.1 ROM from michy still pairs and works fine. (Tested it last night, just to make sure that battery removal didn't had any side-effects)
PLEASE help me if you can. Any suggestion/recommendation will be greatly appreciated.
PS: I decided to contact the car's dealership to inform them about the whole problem. I will post soon regarding how that went...
Thanks for your time everyone...
By the way, does anyone knows the proper way to reset the RCD 510 to it's factory default settings? Besides the function that is given inside the menu itself - I already tried that. I was just wondering if there was a "hidden" way that will entirely wipe all settings/customizations from the unit....
Hi guys! I m in the same situation: Sirocco + TP2 with 6.5 from Orange. Any progress from your side? Ideas would be greatly appreciated!! Cheers, P
Unfortunately!
No friend, sorry. No news yet.
I do keep the post open hoping that someone will give me a new year's present
It's nice to know that I am not alone though