Related
Had the following response to o2 as a result of emailing them with a load of bugs in the XDA IIs a while ago. My email to them it still on the end of their response.
Hi Nigel,
Thanks for this detailed and comprehensive report.
Most of your observations relate to the core Microsoft OS or the integration of the WIFI software, and we will pass them on to the right groups.
In response to some of your comments:
- When will O2 be releasing the firmware update that HTC have already made available to resellers?
* A new ROM image is planned for release in the next few months. We cannot advise a specific date at this time.
- Will this update fix the bluetooth issues
* We are looking to include a new version of the Bluetooth software from the Vendor, Broadcom.
- Will this update include mobile media player 10 as recently made available to integrators by MS
* WMP10 is planned for a later release of the software, later in 2005
- Have any of the hardware faults above been fixed on later units, have you managed a software work-around for the microphone issues?
* O2 reviews all customer feedback with it's supplier, and changes to device manufacture are made from time to time. We cannot comment on what changes are made or when, but we are aware of your observations and are actively discussing with our vendor.
Regarding the yellow screen: our experience is that if Cleartype is enabled, this will significantly affect the quality of the screen display. Please disable cleartype if it is enabled. If the screen is still visibly yellow then you should discuss returning the unit for repair under warranty with your service provider.
thanks,
O2 Product Management
-----Original Message-----
From: Nigel Webber [mailto:[email protected]]
Sent: 04 January 2005 11:54
To: [email protected]
Subject: List of issues discovered on O2 XDA IIs
Hi
Having owned an O2 XDA IIs for 6 weeks now, I have discovered a huge number of bugs - its actually the most buggy product I have ever purchaced, and I do buy alot of gadgets. I am a programmer by trade, so you can rest assured that these issues are genuine and not 'finger trouble' on the part of the user.
Anyway, I suspect MS/HTC have fixed most of these by now, I note that both QTEK and IMATE have released firmware updates based on new firmware from HTC for the Blue Angel. We are yet to see the same from O2.
Connectivity Problems
---------------------------------
Add a new profile to connection manager and then add a 'modem' to that connection. Go and fiddle elsewhere for a while. Often when you come back to change the settings for that connection the 'modem' has dissapeared. (its still there, a soft reset will cause it to re-appear).
Skype does not work with the XDA IIs. This is not a skype issue, but rather an issue with the WiFi implementation on the XDA IIs. Using skype with the XDA IIs (more than 10 metres from your AP) will cause the XDA IIs to drop the connection, and worse still, the WiFi system on the 2s locks up completely requiring a soft reset. No app should be able to cause WiFi to crash like this! This is fully repeatable on Skype versions 1.00.14 and 1.00.20 (latest).
Often, after setting connection manager to always use certain profiles, and then encountering a problem, you head into connection manager and find that your selections never stuck
VPN connections do not always stick when set, they dissapear from the menu (aka the modem settings)
I have tried for ages and failed to make a VPN connection over anything GPRS, WiFi etc. VPN was one of the reasons that I bought the device (access to home and work networks), but it just does not work. Additionally, the instructions with the unit offer no help about how to get it working. Perhaps O2 can offer an FAQ on this feature.
IMAP support is very very bad. Its quite common for an IMAP server to not store mail folders in the root. In decent clients you can specify the root imap folder, not in pocket outlook, it ends up pulling the entire dir struct from your home dir!! I rebuilt the imap daemon on my linux box to compile in a default root folder. This solved the previous problem, but the imap support is not suitable for use away from wifi cause its so damned slow. It does not just look for new messages, and there is no way to tell it to do this. Also, when you send an item it ends up in the default sent items, not the imap sent items. Imho, the main reason to use imap is to keep your emails intact (be able to see what you sent from the mobile device from a desktop). I realise that this is an MS issue, but its pretty naff. (Outlook 2K3 on the desktop has the same issue re sent items btw, but at least that supports rules so you can put it right.)
MS wrote pocket outlook for connecting to an exchange server, which, I suspect only 50% of the devices purchaced will ever do. Pocket Oulook *always* starts pointing at the exchange folder structure, not your POP3/IMAP account, and there is no way to config this. Unessesary taps required. Why can I not DELETE the default exchange folders if I dont need them? I have a work-around for this, perhaps O2 should FAQ it. Changing the shortcut for outlook in the appbuttons folder makes the outlook button on the device start outlook in a user specified mail folder. Just change the shortcut to: 19#"\Windows\tmail.exe" -service "ServiceName"
Sending/recieving MMS messages is unrelable. I seem to have to go into the connections manager and manually select 'MMS Network' in the Work and Internet sections, then I can send/recieve MMS messages. After this, I then have to reset Network Connections to what they were before. MMS should automatically select MMS network when the user is sending/recieving an MMS message and automatically put the original setting back afterwards. There is an option in pocket outlook asking the user which connection to use. This is set to MMS network, but it keeps asking for a password all the time, and fails to remember the password when told, and fails to retrieve the MMS message. To get MMS to work, I have to manually select MMS network in the Connections Manager.
WiFi
-----
WiFi Reception is **attrocious** my laptop will tell me that I have a full signal and the XDA IIs will barely register when at the same location. Even holding the 2s 1 ft from the AP does not cause the signal indicator to go past 40%. I have tried the unit with several AP's all with the same result. Did someone forget to fit a WiFi patch antenna on the Blue Angel??!
Refuses to connect to a network that is not broadcasting the SSID. In general, when you want to add a new box, you can set AP to broadcast SSID, it will then find the network, after it has connected, you can hide the SSID. For future connections from 'pre-registered' boxes, no SSID is required. Not so for the XDA IIs, refuses to connect to a base station that is not broadcasting an SSID, or in some cases, creates a new connection with the name "" (i.e nothing) (which again refuses to connect).
Right, now, if you have 2 wifi networks listed in PPC settings, it will sometimes sit there for ever failing to connect, do a soft reset and it connects.
Another one: you have two connections in the 'configure wireless networks' dialogue, one is 'connecting' other is 'unavailable'. The one that is connecting is obviously not gonna connect despite 100% correct settings, so I select 'remove' it does not dissapear!!! If I had written this software, the user would see a dialogue box thus 'This network is connecting/connected, are you sure you wish to remove its settings?' Selecting yes, would either terminate the connection attempt, or terminate the connection and then remove the damned setting with no further agro!
In network settings, I often get some *stupid* status info. It sometimes says that my home network is 'available' or 'connected' when I am at work, and that the AP thats 3 ft away is 'unavailable' Clearly it isn't, wifi does not travel 10 miles! Soft reset solves (it connects to the AP thats 3 ft away).
Sometimes, when Wlan is disabled, and I enable it, it stays disabled. i,e I try and re-enable it and the tick has dissapeared again. This continues until I give up and soft reset the device. This seems to happen more when there are two networks present, and more still when the disable WLan after X mins of inactivity option is used.
BlueTooth
---------------
When you use bluetooth, for network access, all the stuff in connection manager gets reset. If this needs to be changed to facilitate bluetooth network access then I would expect it to return to the old settings once the BT Network access session was ended.
Sometimes bluetooth fails to start complaining about insufficient driver space. I write windows KMD's all the time, I suspect its somet daft like a lack of available stack space, or stack recursion. Soft reset cures
Also, sometimes when I try to start bluetooth, I get a daft message saying that the licence for the bluetooth stack has expired!!! It then starts BT and all is OK.
Most usefull application of bluetooth is the headset. Unfortunately, no headsets work with the XDA IIs. It says it supports bluetooth, but it does not. When will this be fixed and will O2 be releasing a bluetooth stand-alone patch like Imate have?
Applications
------------------
The bundled O2 active stuff is very flaky. Take the end programs applet - it often crashes its self while trying to force an app that is 'not responding' to stop. The built in 'stop app' applet (which they burried in settings) seems to work but...
- If you reconfig your shortcuts (so you can find stuff!) Then the applets 'camera' and 'O2' always seem to copy themselves back out into the root of StartMenu-->Programs again. *why?*
Go into the find applet and get it to do a search that takes some time. Wait for it to get going and then click stop. PDA hangs. It does come back eventually (2-3 mins later), but remains sluggish until you do a soft reset. Trying to suspend while its hung just switches the backlight off!
There are a load more issues as well... I currently do around 10 soft resets/day. My basis is that a wait of more than 10 secs means that the device has crashed. Perhaps if I was willing to wait 5 mins all the time for it to get its arse into gear then the number of soft resets could be reduced!
Hardware Issues
------------------------
Microphone: No one can hear a word I say to them on the phone. This is especially bad with the built in microphone, but also present with the supplied headset. Is this a hardware/software issue? do I need to return my unit to be exchanged for one with a working microphone?
Keyboard slider mechanism: This gets progressively looser until it starts flopping around. Has this issue been solved on later units?
Yellow screen: The screen takes on a yellow hue when view off angle (by say 10 deg). XDA II did not suffer from this problem. Is there a fault with the LCD on the 2s?
Questions
---------------
Since my device is basically a door stop due to the huge number of issues above, I have some questions:
- When will O2 be releasing the firmware update that HTC have already made available to resellers?
- Will this update fix the bluetooth issues
- Will this update include mobile media player 10 as recently made available to integrators by MS
- Have any of the hardware faults above been fixed on later units, have you managed a software work-around for the microphone issues?
If you require any more info on the above problems, let me know. The XDA IIs could be a decent unit, there aint ought else like it which is why I am documenting my problems rather than buying a competitors product. I would like to see these issues fixed.
Regards
Nigel Webber
If you're a chewin' the fat fan, you'll know what I mean when I say I'm taking a seriously big sniff and there's a hint of something in the air.
Sounds to me like they really are just fobbing us off with standard responses and aren't taking complaints seriously.
* O2 reviews all customer feedback with it's supplier, and changes to device manufacture are made from time to time. We cannot comment on what changes are made or when, but we are aware of your observations and are actively discussing with our vendor.
Click to expand...
Click to collapse
Well thats just pish isnt it?
We cannot comment? Why not? Is it because they would have to acknowledge the product has gone to market well before it should have?
The least they can say is that they have gone to HTC with the list, and what HTC are planning on doing about it.
This is what I got:
Hello,
Thank you for yoru email,
Unfortunatley we don't have any dates at present for an upgraded
Bluetooth stack, we are aware of issues with it and are pushing our
products group for an update or at least a timescale.
I will keep this mail, and as soon as any information is released, we
will let you know.
Regards,
Paul
O2 Data Support UK
-----Original Message-----
Sent: 12 January 2005 01:03
To: O2 Data Support (UK)
Subject: XDAIIs Rom Upgrade timetable
Hi
Have you guys got a timetable for rolling out an upgraded ROM for the
XDA IIs?
I'm having quite a few complaints from callers saying they cant really
hear me well and bluetooth isnt working particularly well either.
From what I've read on the web, this is a known fault with the default
ROM version included as standard.
Also, i'm interested in the Blackberry functionality once it becomes
available, but at present, I'd settle for a handset thats not annoying
colleagues and customers.
Thanks
Darren
Click to expand...
Click to collapse
I don't want to seem too critical (after all, if you're really having to reset 6-10 times a day you must be on the verge of killing someone by now) but a lot of the issues you list aren't bugs, they're useability issues. Someone working in a customer complaints department (wouldn't wish it on anyone) is going to take a lookat the list and dismiss most of it as whining because you present personal gripes and subjective observations as bona-fide bugs. It is very tempting when angry to try to oversell parts of a long list of complaints, but this just gives the recipient amo to dismiss the lot.
I also think you should get your unit replaced with a new one ASAP. So few people are having the problems you describe, particularly surrounding the WiFi signal strength and screen, that you do seem to have a barely working unit!
You do have my complete sympathies. To spend so much money on something that SHOULD be as near as dammit perfect, only to end up with a damp squid is hugely frustrating (it has happened to me a couple of times).
I agree, most of this list is not bugs that anyone has. Some are even limitations of the operating system.
If you are soft resetting 6-10 times a day you should hard reset your device because it is 3rd party software, do not restore from backup, do not install software and see how it is. If you still have to reset your xda is defective and its time to send it back!
I would agree with some points mostly that bluetooth is a mess and needs to be fixed, the o2 bt patch resolves the connection issues but there still is static issues! But this is not exclusive to the XDA iis but all blue angels. The siemens model SX66 has no update at all!!!
Oh remember when we had our xda II & imates and wanted to dump the microsoft BT stack and would do anything for the widcomm stack. LOL we sure got what we wished for. Bet most of us would go back if we could.
Indeed, got it all of my chest in one go! Trouble is, with PDA's your only point of contact is with your reseller. I dont have a way of contacting HTC, Broadcom, MS separately as I would if this were a PC with faults in several manufacturers programs/hardware.
I am indeed, not expecting the likes of the mail/imap issues to be addressed for the blue angel, I would like to have some mechanism to tell MS where they are going wrong from me (the user's) point of view.
If we have no mechanism to provide feedback then we just end up with half baked kit in the next iteration as well. Perhaps this is why Windows Mobile 2005 will be the 6th? release of what was originally called windows CE, and why 'CE' is now on its third name? And I still doubt whether they will have got it right!
Nigel
I suspect that I just expect too much!!
Its not third party software cause I have hard reset the device, and installed nothing and I still have to do regular soft resets. I doubt very much whether it is a hardware issue either, and all XDA IIs devices have the same firmware. Most of the time, my soft resets are done to pursuade said device to see the wifi ap thats 2ft from it. I regularly use three different AP's in three different locations. I suspect that this is not the case for most people.
I am also very impatient (a device such as this should be quicker than I am!) The PPC OS suffers from 'pregnant pauses' where the whole thing appears to lock up. If they last longer than 30 secs then I am likely to get bored waiting and do a soft reset. Give me a 3GHz PDA with a 10 hour battery life!
My mate is getting one soon, so I will compare his with mine and return mine if the issues have been fixed. I'd hate to return mine and end up with one thats even worse ;-)
Nigel
veletron said:
MS wrote pocket outlook for connecting to an exchange server, which, I suspect only 50% of the devices purchaced will ever do. Pocket Oulook *always* starts pointing at the exchange folder structure, not your POP3/IMAP account, and there is no way to config this. Unessesary taps required. Why can I not DELETE the default exchange folders if I dont need them? I have a work-around for this, perhaps O2 should FAQ it. Changing the shortcut for outlook in the appbuttons folder makes the outlook button on the device start outlook in a user specified mail folder. Just change the shortcut to: 19#"\Windows\tmail.exe" -service "ServiceName"
Click to expand...
Click to collapse
Could you explain this workaround a bit more. Are you just changing the name of the shortcut within \windows\appbuttons or is this some sort of programing? Sorry if I'm missing something obvious but I'd really like to get this one working.
Thanks, JD
@jdee246
http://forum.xda-developers.com/viewtopic.php?t=13755&highlight=
I agree with Nigel on the issues with the XDA2s some i have not seen because i dont use it to its full. I also rest probly 5-10 times a day. I got my first XDA2s on 5th November i am now on my 5th one and in a few days i will be changing for a new one. I simply ring them and go over the list of faults, and then remind them that the device they send me will be no better than the one i have and i will be calling again soon to change it. They told me as long as its less that 28 days since the last one was sent to me it can be changed. So i will keep swoping it for new ones until they get me a working one ( we know this will never happen) but at least the new ones dont slide open on there one when you pick it up for a couple of weeks. So i asume i will contine to do this untill the XDA2i is released then i return the current XDA2s (probley number 20 by then) and do a up grade to the new XDA2i
veletron said:
@jdee246
http://forum.xda-developers.com/viewtopic.php?t=13755&highlight=
Click to expand...
Click to collapse
Thanks Veletron. That worked like a charm. Thats been hacking me off for ages.
JD
@applecom
How long does O2 take to send you a new unit, and whats this 28 days thing? Surley if its faulty then they are obliged to sort it as long as its within the 1 yr guarantee.
You are saying that apart from the keyboard not sliding open, the new ones are no better? If thats the case then there is no point in my sending mine back cause I'll get one with the same problems.
My screen is only yellow when viewing the unit from an angle, and the keyboard does not fall open (although it is very sloppy).
Any idea if the wifi reception is better on the later units that you have had?
Nigel
XDA IIs Customer Services Response
Hi
As an addition to this subject I contacted the company I bought my XDA from re the poor microphone issue and they asked if I had read up on the issue via any support websites as they (she) did not think the issue had been resolved and I wouldn't gain by receiving a new product.
I agreed that I didn't think it possible yet but wanted to keep within the 28 day replacement window for as when they did.
The response was to:
A) Open up the 28 day replacement window on this problem for a further 3 months and
B) State that if a fix was forthcoming then a recall would take place and I would get a replcement anyway.
On this basis I decided to hold for the moment to see what happens.
In all maybe an easy solution for them but it suits me for the moment! :wink:
veletron
The 28 day window is for an immediate (a few days?) replacement
with a new unit, after this period your unit is taken away for repair with no replacement and no estimate of when it will be returned/replaced.
pvb
they replace it same day, I recieve it by courier the next day and give them my old XDA2s, some times i do a restore from a backup and some i reinstall my software from fresh. But no they are all the same i am hopeing for one that has newer rom and thus might work correctley
Agree with all the problems above, the few that really frustrate me are...
- Floppy keyboard slide, should latch back in?
- Hands Free needs to be louder, could someone build a preamp util?
- Annoying that picture contacts seems to be a separate app to regular contacts?!
- Still slow, thought the faster CPU would mean no delays!!
Cheers, Ash
XDA IIs Battery issue
I have just upgraded from an XDA II to a IIs and other than the normal unlock problem I have just brought a second battery, when I changed the batteries the unit did a hard reset, I thought this was because the new battery was fully discharged.
I did some further testing and found that when ever you remove the battery and replace it the unit does a hard reset (all batteries are fully charged).
Any comments or do I have a unique unit?
Hello to you all.
I have just read all the above with great interest as I am seriously thinking of buying an XDAIIs this week. I will be moving from a Treo 600.
I am very concerned about all the problem you seem to be having and I am starting to think that buying one may not be the best idea. The other phone I am looking at is the Nokia 9500. I already have an HP 4150 and so I really dont need all that the XDA IIs has to offer.
I would be interested in hearing peoples comments on the phone to help me make my mind up. I do have to say that when the Treo came out loads people reported a lot of problems but I had mine for a year and it worked perfectly for 10 months then the screen gave up. It appears that nearly all these "Smart/PDA" style phone have teething problems that are mostly down to the product being shipped before it is really ready.
What do people think? Should I take the plunge?
All the best.
Raymond
XDAIIs Battery Issue
I have two batteries and swap them regularly. Your backup battery is either not charged or faulty if the unit hard-resets when you swap them - I think a warranty claim is likely.
Hi all!
I know this has been discussed before, but it has never really been answered or a *working* solution been found to this problem:
I have the Cingular 8525 and my WAN connection (yes, no matter if it's Edge, 3G or HSDPA and no matter if I use isp.cingular or wap.cingular) just seems to die off after the PDA has been sitting for a while in STANDBY.
After seeing how incredibly stable and reliable all the blackberrys work, I still opted for the PDA because I liked the versatility plus the ADVERTISED push capabilities of it.
Apart from non-working tools like "gprs keepalive" etc, how can anyone REALLY PREVENT programs that are running from being stopped? Is there a Reg-Hack for this?
Here's my setup. Fresh blank WM VI Black 2.0 (great imags jas !!) and ONLY VGSMail (for mailpush) and IM+ for yahoo messenger installed. Rest absolutely untouched. Everything works fine as long as the thing is actually ON (display lit up and everything). Once i either wait for the timeout or manually put it in standby by pressing the power button, the Yahoo IM+ will react for another 5 minutes, but VGSmail almost immediately goes deaf. I have a TCP bridge in front of my IMAP server so I can see all in/out traffic to the IMAP by just accepting connections on port 1430 and routing all traffic to 143 while dumping it into a log. I can see the PDA connect the server and go into IDLE. Every time a new message arrives, the PDA is SUPPOSED to get it, but it just doesn't when it's in standby. Completely defeats the whole purpose of it.
Long story short:
HOW do you prevent the connection/radio/windows/software from "silently falling asleep" when the connection should stay open and new messages (email via VGS or IMs via IM+) should be received?
P.s. I already used the included HTweakC to acticate autoconnect and permanent connect. opens up the connection fine after reboot, but that's it!
THIS HAPPENS WITH EVERY IMAGE I HAVE TRIED! Original Cingular, Cingular Hacked AKU3.3, Black 1.2 and Black 2.0 :-((
Thanks
Ive had the same issues, my internet connection will just randomly quit on me. One second it will be working the next it will disconnect. Seems to be when I bring it out of standby or get a call. Definitely not as stable as WM5 was.
Radio Version?
Which radio version are you running? I have two things different with my configuration, but I had similar issues with my service (T-Mo USA).
My GPRS connection would hang, even when on the charger (not sleeping).
Turns out a radio update caused the behavior to quit altogether. I could drive completely across town, and have 10-15 new emails in my box, whereas before, I had to either press/hold the disconnect button, or soft reset.
My current versions are in my signature.
Hope this helps.
electron73 said:
Hi all!
I know this has been discussed before, but it has never really been answered or a *working* solution been found to this problem:
I have the Cingular 8525 and my WAN connection (yes, no matter if it's Edge, 3G or HSDPA and no matter if I use isp.cingular or wap.cingular) just seems to die off after the PDA has been sitting for a while in STANDBY.
After seeing how incredibly stable and reliable all the blackberrys work, I still opted for the PDA because I liked the versatility plus the ADVERTISED push capabilities of it.
Apart from non-working tools like "gprs keepalive" etc, how can anyone REALLY PREVENT programs that are running from being stopped? Is there a Reg-Hack for this?
Here's my setup. Fresh blank WM VI Black 2.0 (great imags jas !!) and ONLY VGSMail (for mailpush) and IM+ for yahoo messenger installed. Rest absolutely untouched. Everything works fine as long as the thing is actually ON (display lit up and everything). Once i either wait for the timeout or manually put it in standby by pressing the power button, the Yahoo IM+ will react for another 5 minutes, but VGSmail almost immediately goes deaf. I have a TCP bridge in front of my IMAP server so I can see all in/out traffic to the IMAP by just accepting connections on port 1430 and routing all traffic to 143 while dumping it into a log. I can see the PDA connect the server and go into IDLE. Every time a new message arrives, the PDA is SUPPOSED to get it, but it just doesn't when it's in standby. Completely defeats the whole purpose of it.
Long story short:
HOW do you prevent the connection/radio/windows/software from "silently falling asleep" when the connection should stay open and new messages (email via VGS or IMs via IM+) should be received?
P.s. I already used the included HTweakC to acticate autoconnect and permanent connect. opens up the connection fine after reboot, but that's it!
THIS HAPPENS WITH EVERY IMAGE I HAVE TRIED! Original Cingular, Cingular Hacked AKU3.3, Black 1.2 and Black 2.0 :-((
Thanks
Click to expand...
Click to collapse
silverfox0214 said:
Which radio version are you running? I have two things different with my configuration, but I had similar issues with my service (T-Mo USA).
My GPRS connection would hang, even when on the charger (not sleeping).
Turns out a radio update caused the behavior to quit altogether. I could drive completely across town, and have 10-15 new emails in my box, whereas before, I had to either press/hold the disconnect button, or soft reset.
My current versions are in my signature.
Hope this helps.
Click to expand...
Click to collapse
Yeah, I had radio 1.27.00.00 before, now I have 1.38.30.10
Also I do have newest Hard-SPL 1.40 installed. So I'm pretty much cutting edge here. Howewer, the PROBLEM has been annoying me since WM2003SE.
Is it just the way it is with desktops? Micky Mouse Soft dominates the market, releases one pile of **** after another, never really fixing bugs but introducing new ones by the thousands and we users (who in this case have paid $500 for the device) are left in the dust?
If I just imagine delivering buggy crap like this to MY customers, they would kill me!
Anyone have some good ideas or hacks? I definitely need to get this working at least to a somewhat acceptable level. Since having the Hermes with the first "original" WM5 on it, I got used to rebooting that unreliable Micro$hit every morning when I get up, to make it usually just about last for the day. I'm definitely not willing to reboot every hour !!!
I have this problem
I have this problem however I still receive push email. the most annoying thing is that I cannot keep a data session active with a voice call.
I am on Orange UK network. I use 4smartphone's hosted exchange service. I get directpush working 24/7 with Black 2.0 OS. I also receive my pop email whilst on voicecalls.
So its not a WM6 issue. Its either your network or your connection settings.
I must say that it actually improved a lot since installing Black 2.0. However, the connection still silently dies off eventually. I now have a makeshift solution using FlexMail, set to poll emails every 15 min. So what happens is as long as the PDA is ON, I get immediate PUSH mail. Once I put it in standby, it continues to work for a minute or two, then the connection ****s up. Every 15 min Flexmail wakes up and polls for emails, which most of the times seems to work as I can see in my logfile that every 15 min the tcp connection opens up and the server dumps all new mails over to the phone. It then enters IDLE and at some point dies away with "recv(): connection timed out".
So it's all pretty messy still and I'm wondering what you can do to PREVENT the line from silently dying in the first place. Tried tools like GPRS Keepalive with no luck, since the whole program stops being executed in standby and hence it can not keep the connection up = useless. I need some hack/tool/program that stays active during standby! Then I could just have it ping my mailserver once per minute to keep the connection open.
Any ideas would be greatly appreciated
Could my problem be related? - see my post under Treo 750:
http://forum.xda-developers.com/showthread.php?t=324495
I am testing to see if I get the same behaviour with 3G/UMTS as I do with GPRS....
The problem is one of the most annoying ones you can have: it appears only from time to time and you don't know when and even when it does you don't notice.
Simply my phone is not accessible for others even it shows full range and so on. The message "...the phone is switched off...". This problem occurs in as far as I remember 3 releases of ROMS (full, vanillas, etc). The radio ROM was also changed. I don't remember having such issue in early WM6 or in original 2005.
Since it's not related directly to any of the releases I post it as a new thread.
Now I have 3 options:
1. Downgrade to 2005
2. Throw the unit through the window, wait until end of contract and buy an iPhone
3. Try to fight with T-Mobile UK - which is not really an option since I just recovered from fighting with Orange for over a month
Does any of you experienced such problem?
Any known issues with downgrading to 2005 like ISPL required before flashing original ROM?
Any suggestions?
Adigital said:
...
Any known issues with downgrading to 2005 like ISPL required before flashing original ROM?
..
Click to expand...
Click to collapse
Well, I got the answer - couldn't wait and did the downgrade using original ROM. If anyone interested it went without problems. No ISPL needed. Connected, fired-up the exe file and worked OK.
I'll see how about the availability problem.
Ok, seems that it's only me having the conversation ;o)
I apologize for the thread location - it doesn't seem to be related strictly to WM6 anymore as I...
...installed WM5 and did some tests:
(I have voice mail switched off)
- Call waiting enabled = no calls allowed when GPRS active
- Call waiting disabled = no calls when transferring data (large file) but received when no transfer
- Used W660i SonyEricsson handset - could receive calls regardless of GPRS activity
Rang T-Mobile tech support where they told me that this is network feature that when internet connection is active no calls are allowed and since my voicemail is turned off all callers get message that my phone is switched off. In the light of GPRS specification and my tests this is a bull****.
Now I'm asking anyone on UK T-Mobile Web'n'Walk and who wants to help - please do such test. Just try to call your number from different phone when opening a web-page.
This is pretty important to me - I need internet on the move and don't want to get rid of my MDA.
Thanks in advance!
Hi there,
I'm on T-Mobile UK too and I ran some tests myself and found that you are absolutely correct. When you transfer data you cannot receive phone calls.
I've got an O2 device with me I can do some more tests on and I'll also try and borrow my Wife's Samsung and test that too. I'll post my findings here.
Cheers
Alex
ok, i've just tested this on an O2 3G device and there was no problem, next to try a none windows mobile t-mobile phone.
seems this problem has been around for while and on other networks.
http://www.freenfo.net/mobile/archive/index-t-64022.html
ok, final test and conclusion.
I tested the same o2 phone as above but in a NON 3g area (i.e. gprs only) and found the exact same issue.
conclusion: this seems to affect all types of phone and multiple networks but only when using gprs NOT 3g.
I'm suprised we havent heard more about this problem.
cheers
Alex
Thank you Alex very much for your help.
I did some research on the topic last night and found the same info as guys in the thread your linked. It must be that T-Mobile UK operates in NOM-2, which allows to suspend GPRS session only when no data is transferred. When packets are transmitted the device doesn't 'see' incoming calls as it's 'busy' with dealing with the packets. NOM-1 is 'able' to encapsulate information about incoming call into one of the packets and the device is notified about - so it can react, suspend the transmission and pick up the call.
The fact is that our MDA/Artemis uses Class B of GPRS which doesn't allow simultaneous CDA/GPRS at the same time. Even if it can suspend active data transfer it is the network that has to support that feature.
What I must notice is that I had lot more problems wiht this when I was using WM6. It seems that there were some packets transmitted by the system or something. I had my mail set to check servers every 15 mins at the beginning but lately ony once an hour or two. Other soft that could transmit anything was Weather module from SPB or Touch. Now when I'm on WM5 and was checking the issue during loading a page I was unavailable but as soon as a page was completely loaded my phone was accessible back.
My surprise is that if the 'issue' seems to be quite normal and there is nothing to do about it why I couldn't find any info about it here. Doesn't it affect anyone of our community?
I may be wrong with the WM6 expirience but still. If WM6 works fine in that respect it must have happened that someone missed a call when browsing the net.
i hadnt noticed to be honest
mugglesquop said:
i hadnt noticed to be honest
Click to expand...
Click to collapse
Did you try ringing your phone when it was loading a long page or downloading a file?
TBH I think I've noticed it just as much on WM6 as I did (or didn't) on WM5, I think I put these odd voice mails turning up down to weird WM issues! Now I know the truth though.
Obv. there isn't a lot we can do about this and I'm not prepared to turn off my Windows Live Mail or my direct push. I think we just have to wait until our contracts are up for renewal and get over to a 3G device - I'm liking the look of the Touch Cruise myself, or the Touch Dual if I want that keyboard back and by the time my contract is up I think they should be on T-Mob UK.
does the same thing happen in Edge areas or as that rolls out will the problem disappear?
I'm not sure about how EDGE works but the problem affects GPRS rather than 3G due to the fact that GPRS and the incoming call are submitted alongside each other and 3G is seperate. I don't think t-mob uk have edge running yet so I can't test, perhpas some else can test for us.
Bro.. My first 3rd party ROM is the Touch 3.0.. and yes.. my connnection did go off once a while (no bars as well).. that was kinda irritating. I have to go to connection manager and toggle my data connection or something like that, before my phone will get the GSM signal.
And yea.. the original WM5 and WM6 have no such issues.. I wonder if this is because of the new radio version..
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
Hi guys, I have a strange problem.
Sometimes when I try to call someone, the phone cuts off the connection right before it should vibrate to signal that the phone was answered. This means I can hear the other side picking the phone up, but I hear like "H" (sharp, short) when they try to say "hello". No matter whether I have phone by my ear or laying on the table, sometimes it cuts off, other times it doesn't. When I make the call again, it works.
This started to happening to me since I've updated my sw version to 1.21, when it was 1.15, it worked like a charm. For the last 4 days I tried to make 3 calls, every one of them was cut out and worked on the second try.
Anyone has the same problem/knows the solution?
Thank you very much, It's annoying as hell since every call costs me twice
EDIT: I'm using stock ROM, updated with OTA, no root
------------------------------
Sorry for my English, I'm Czech.
Really? No one?
desire drops calls after a few seconds
Hi!
I've the same problem, since today - very annoying. All start with a call from a friend and after I said "hello" the call ends, but network connection was fine (4 bars). After that I tried to call him back 10 times, every time the same thing - call drops after 1-3 seconds.
A Reboot solved the problem for one time, next call same issue. Tried my sim in the HTC Wildfire of my colleague - same network, everything is fine.
Now I started to uninstall all Taskkiller and other apps i recently added - no change. After 30 min try and error I realised that if I turn of the "Mobile Internet" and therefore the 3g connection, it works better.
anyone have a clue what this could cause?
Joint the club.... http://forum.xda-developers.com/showthread.php?t=712030
Mine does exactly the same thing... first of all I thought it was the phone... returned it... new phone, different sim.... same problem.
Geeba have you tried to turn off "mobile internet"?
After my problems yesterday I turned it off and since that no call was dropped!!
Maybe its some sort of concurrent use of 3g Network and the data threads kill the call ... actually I'm no expert in Mobile Networks.
I'm looking forward to Froyo and hope to get rid of the probs.
Minos - yes I have turned off the 3g - but I then have internet connection problems... pretty pointless having a smart phone that has no internet access..
But yes it does help... the Desire I think should be able to monitor the two signals and switch between them accordingly .... but it doesn't. my Mrs has the Hero... it doesn't suffer this problem so personally I think its a problem with the desire.... I'm going to wait till Froyo then if its no better there will be a nice unbranded black Desire gracing ebay!
had the same issue for a few days then i uninstalled juice defender and i havnt had a single dropped call after
I have had the same issue. And then I have read somewhere here what to do.
You must first enter the phone's debug menu: *#*#4636#*#*
Then Choose "Phone Info", scroll down to" Set preferred network type" and set this to GSM auto (PRL). For me it solved all the call drop problem. As you are on different network maybe some other setting will work for you but it might worth to take a try with it.
I am not exactly sure what this sets. One thing is sure I still have 3G and HSUPA connection - and all type of connection works like charm. So nothing changed just no more call drops since then.
benoke: Thanks for your idea, actually my Desire is now beying hospitalized as it had dust under the screen, anyway I reported dropping calls as an issue too while returning in warranty so we'll see what happens
i sent a support question to htc and got that answer:
"Thank you for contacting HTC. In regards to your question, I can help you with that. It does indeed sound like a hardware fault, I would be grateful if you would call our tech-suooprt team and let our agents arrange the return / repair of this device for you. If you could just call 0845 890 0079, we can arrange the collection. I trust that this resolves your query. Please do not hesitate to contact us again if required."
But I don't think its an HW issue.
@benoke: the GSM auto setting worked - four 1h now.
Minos: it is good to hear that it might work for you too. I have recommended it to some of my friends and they all say it works for them.. so it really seems like solution...
Try the new version 5.09x radio in the android development in desire forum to see if that miight help
Sent from my HTC Desire using XDA App
Haven't found a way to solve this issue yet. They told me at the service station that this is unrepairable issue occuring only with some SIM cards and that they would give me a refund.
I'm buying HTC Desire HD when it is available...