Anybody is aware whether Kaiser's WM6 build directly from HTC will include VoIP application?
Hi
Not sure yet as no one has seen the final release of the software however it's easy enough to add back in.
However the Kaiser like other devices pushes the VoIP sound out the rear speaker and not the earpiece
Regards
Phil
PhilipL said:
However the Kaiser like other devices pushes the VoIP sound out the rear speaker and not the earpiece
Click to expand...
Click to collapse
Since when? From the very first WM6 version I've had on my Hermes, it worked through earpiece, not the speaker. Also, it works completely seamless, so placing and receiving calls works just like regular GSM/UMTS calls.
I mean the 'core' WM6 VoIP application, not Skype or such which actually works only through the speaker (unless sth has changed recently, I've last tested Skype quite long time ago).
Hi
Since when? From the very first WM6 version I've had on my Hermes, it worked through earpiece, not the speaker. Also, it works completely seamless, so placing and receiving calls works just like regular GSM/UMTS calls.
I mean the 'core' WM6 VoIP application, not Skype or such which actually works only through the speaker (unless sth has changed recently, I've last tested Skype quite long time ago).
Click to expand...
Click to collapse
You were lucky then.
Yes I do mean the core VoIP application, however it doesn't work correctly on lots of devices including the Kaiser going by Paul's review at http://www.modaco.com/Paul-Reviews-HTC-P45-t256569.html
There is very long thread in these forums about VoIP and plenty of devices not pushing the sound out of the earpiece but the speaker, this includes other HTC devices.
I tried the core WM6 application on a Toshiba G900 and the sound came out the speaker not the earpiece, and I spent many hours trying to find a solution and couldn't.
I'm not saying it doesn't work correctly on any device, just that the Kaiser seems to suffer the same problem as other devices by pushing sound out the speaker, even with the integrated WM6 VoIP application.
Don't shoot the messenger
Regards
Phil
With regards to VoIP, I have a question for WM6 experts.
What has always bothered me of Windows Mobile 5 (and earlier) in comparison to Symbian phones is the implementation of WiFi. What I mean is that in Symbian you can create various access points, and they can be GPRS/3G or WiFi with no difference in usage. Hence, an email program or any other program can be configured to use a WiFi access point, or a 3G access point, all automatically. And in many cases, apps can try WiFi first and then go with 3G if that fails.
With WM on the other hand, it always comes to having to switch WiFi on "MANUALLY", and the really irritating thing is that WiFi always switches itself off when the device goes in standby. By doing so, email checks will automatically use 3G (as WiFi won't be ready), and VoIP use is impossible, as WiFi is disconnected when the phone goes in standby, hence it cannot receive calls.
On Nokia smartphones, on the other hand, VoIP is left always on (using WiFi). And the interesting thing is that a Nokia phone can have VoIP active on WiFi for the whole day, and still be very good on battery levels at the end of the day. While with WM devices, WiFi normally drains the battery after an hour or two.
Now the question is: has all this changed with WM6? Meaning, can WiFi work in standby, and can Outlook Mobile perform email checks using WiFi (waking up from standby)? And can the device automatically try your WiFi access point, and then fall back to 3G if that is missing?
Thanks!
Hi
Now the question is: has all this changed with WM6? Meaning, can WiFi work in standby, and can Outlook Mobile perform email checks using WiFi (waking up from standby)? And can the device automatically try your WiFi access point, and then fall back to 3G if that is missing?
Click to expand...
Click to collapse
You set the Wi-Fi to always ON. It is set to turn off by default to save power.
Regards
Phil
PhilipL said:
Hi
You set the Wi-Fi to always ON. It is set to turn off by default to save power.
Regards
Phil
Click to expand...
Click to collapse
Thanks Phil, that is nice to know.
What I am interested to know, though, is also if the WiFi connection gets turned on and off automatically as needed, as in all Symbian smartphones.
Meaning, when the phone needs to check emails (like every 30 min for example), it will automatically switch on WiFi, check emails, and then turn it off, all while in my pocket. What really annoys me of Windows Mobile (ver. 5 and earlier) is that the use of WiFi always implies a manual switch on, which makes it very impractical to use.
On top of that, can WM6 automatically check WiFi coverage, and if that is missing, connect to 3G/GPRS, all automatically like all Nokia/Symbian devices? I have read posts about the G900 being able to do so, apparently, but I would like to know if this is a new feature of WM6.
Thanks!
sirox said:
What I am interested to know, though, is also if the WiFi connection gets turned on and off automatically as needed, as in all Symbian smartphones.
Meaning, when the phone needs to check emails (like every 30 min for example), it will automatically switch on WiFi, check emails, and then turn it off, all while in my pocket. What really annoys me of Windows Mobile (ver. 5 and earlier) is that the use of WiFi always implies a manual switch on, which makes it very impractical to use.
On top of that, can WM6 automatically check WiFi coverage, and if that is missing, connect to 3G/GPRS, all automatically like all Nokia/Symbian devices? I have read posts about the G900 being able to do so, apparently, but I would like to know if this is a new feature of WM6.
Click to expand...
Click to collapse
Unfortunately WM6 does not bring any difference in terms of WiFi connection. You still need to switch it on manually, I'm afraid.
Actually, I've been using Nokia E61 for a while now, and I must admit I have underestimated Symbian platform before. It still has some glitches and WM seems to be a little bit better in overall, but some bits are still much better in Symbian. WiFi/GPRS/3G connectivity (and battery life while on WiFi!) seems to be one of that bits.
eva_d said:
Unfortunately WM6 does not bring any difference in terms of WiFi connection. You still need to switch it on manually, I'm afraid.
Actually, I've been using Nokia E61 for a while now, and I must admit I have underestimated Symbian platform before. It still has some glitches and WM seems to be a little bit better in overall, but some bits are still much better in Symbian. WiFi/GPRS/3G connectivity (and battery life while on WiFi!) seems to be one of that bits.
Click to expand...
Click to collapse
Oh, that is bad news really. How can Microsoft (or anyone else) talk about VoIP when the devices don't keep WiFi on all the time without draining the batteries?!? I find WiFi completely pointless on WM devices...
I am also surprised that there is apparently no third party software yet which can manage connections in a Symbian-like fashion, automatically trying Wifi and fall back to 3G in case of no WiFi. It sounds something totally obvious to me... Or is it just me?
sirox said:
Oh, that is bad news really. How can Microsoft (or anyone else) talk about VoIP when the devices don't keep WiFi on all the time without draining the batteries?!? I find WiFi completely pointless on WM devices...
Click to expand...
Click to collapse
This is true, actually. I suspect integrated VoIP application is not in quite 'final' stage of development, and that's why we cannot find it in official WM6 releases. Possible reasons for that might be also lousy WiFi implementation and connection management, and once this is improved, VoIP might get go-ahead for commercial use.
WiFi adapters in HTC devices (at least in Wizard and Hermes, which I've got) have also poor signal quality/reception. I experience WiFi connection drops while being in the room just one wall away from my home wireless router, and where I have pretty strong connection on laptop and Nokia E61 phone! My first palmtop ever, which was HP iPaq rx3715 had damn good WiFi signal strength. It was really really great! Obviously HTC cannot cope with that issue properly.
sirox said:
I am also surprised that there is apparently no third party software yet which can manage connections in a Symbian-like fashion, automatically trying Wifi and fall back to 3G in case of no WiFi. It sounds something totally obvious to me... Or is it just me?
Click to expand...
Click to collapse
Well, as I said - some things are much better done in S60 platform, but some others in WM. It could be good to have connection management improved in WM, but I don't suppose it will happen anytime soon.
Hi
Oh, that is bad news really. How can Microsoft (or anyone else) talk about VoIP when the devices don't keep WiFi on all the time without draining the batteries?!? I find WiFi completely pointless on WM devices...
Click to expand...
Click to collapse
In order for VoIP to work for receiving calls the WiFi needs to be on continuously in order to act as a server for inbound connections.
You can't have Wi-Fi on and the PDA off (or in standby) as Wi-Fi needs a functioning CPU and operating system to respond to packets as they arrive, it also needs the OS for housekeeping tasks such as encryption and polling the base station to keep the air link live.
Providing you don't have any bad being having applications battery life isn't impacted as much as you might think by leaving the PDA on using Wi-Fi (obviously the back light should time out to stop a major drain on the battery and so it may look off but it will still be running). SmartPhones (ones without touch screen) don't ever turn off (no standby mode) and remain fully powered up, it's only PDA's that standby, the reason for this is they are generally more powerful and allow you to install your own applications. An application that animates a weather symbol on the Today page could make the battery go flat very very quickly by keeping the CPU busy. A PDA uses standby to ensure no application can drain the power like that, and that they aren't expected to be quite as responsive as a normal phone, i.e. an incoming call needs to wake the device first so it may take a few seconds longer to ring.
If you get lots of calls and text messages on your Windows Mobile PDA it may actually use less power leaving the device on rather than allowing it to standby, this is because it takes quite a few CPU cycles to wake the phone up and make itself functional after standby so that in itself uses some power.
Lots of interesting info here: http://blogs.msdn.com/windowsmobile/archive/2006/08/16/702833.aspx
Regards
Phil
PhilipL said:
Hi
In order for VoIP to work for receiving calls the WiFi needs to be on continuously in order to act as a server for inbound connections.
You can't have Wi-Fi on and the PDA off (or in standby) as Wi-Fi needs a functioning CPU and operating system to respond to packets as they arrive, it also needs the OS for housekeeping tasks such as encryption and polling the base station to keep the air link live.
Providing you don't have any bad being having applications battery life isn't impacted as much as you might think by leaving the PDA on using Wi-Fi (obviously the back light should time out to stop a major drain on the battery and so it may look off but it will still be running). SmartPhones (ones without touch screen) don't ever turn off (no standby mode) and remain fully powered up, it's only PDA's that standby, the reason for this is they are generally more powerful and allow you to install your own applications. An application that animates a weather symbol on the Today page could make the battery go flat very very quickly by keeping the CPU busy. A PDA uses standby to ensure no application can drain the power like that, and that they aren't expected to be quite as responsive as a normal phone, i.e. an incoming call needs to wake the device first so it may take a few seconds longer to ring.
If you get lots of calls and text messages on your Windows Mobile PDA it may actually use less power leaving the device on rather than allowing it to standby, this is because it takes quite a few CPU cycles to wake the phone up and make itself functional after standby so that in itself uses some power.
Lots of interesting info here: http://blogs.msdn.com/windowsmobile/archive/2006/08/16/702833.aspx
Regards
Phil
Click to expand...
Click to collapse
Hi Phil,
What you say is only partially correct. Symbian smartphones do not go on standby, this is true, but in terms of operating system, power, and third-party applications they are no "weaker" than WM devices. And UIQ-based Symbian phones also provide touch screen functionality with an interface and capability which is pretty much the same as Windows Mobile. For example, a heavy application like TomTom Navigator 6 runs equally well, and with exactly the same speed and features on WM and Symbian devices.
CPU's on Symbian devices go anywhere between 200Mhz and 330Mhz, and do not need standby to save power. And a Nokia E61 can keep WiFi on (with VoIP in "always on" and listening) for two days with no interruption, and the battery won't be flat yet. So there is something wrong in the WiFi management of WM devices.
Also, Symbian devices allocate CPU cycles based on software demand, so the concept of putting the device in standby to save power is not at all necessary with current chips.
Another point that you make is that according to you the CPU on a Windows Mobile stops in standby. This is untrue. In standby mode background applications still run. For example, try any Instant Messaging application on Windows Mobile, and it will run also in standby (with the screen completely off). Same happens with push email solutions. Even Activesync runs in standby mode (screen completely off) during synchronisation with an Exchange server. I have experimented this many times with my Tytn.
The end result is that on WM devices, the only connection that "always on" applications like VoIP and push-email can use is 3G/GPRS, as they cannot automatically check WiFi coverage as needed. Which is something that Symbian devices do since ages. In fact, on Symbian devices you cannot switch WiFi on manually, it gets switched on by applications as needed, without manual intervention. And when WiFi is not available, then they go with 3G/GPRS.
As I said before, WiFi management and power management (I still don't understand why WiFi drags the battery so quickly on all WM devices) are the two things that really put me off with Windows Mobile devices, and frankly I do not understand why such a fundamental matter has not yet been addresses by Microsoft, HTC and the other vendors...
Or is the Qualcomm chip found in the Kaiser the solution?!?
Hi
You need to read the article I posted a link to.
Windows Mobile 6 is working exactly the same as Symbian with one exception, on PDA devices there is an additional power saving mode, that is standby, where the CPU clock stops, nothing is running. Applications have no idea they have been suspended, time just stops. Yes there is a separate chip that is still on running the radio for the mobile phone part, and that can bring the device out of standby to service a call when needed, but the main CPU and OS is stopped dead.
For Windows Mobile Professional 6 which is only used on PDA type smartphones (i.e. have touch screen, Windows SmartPhones use Windows Mobile Standard 6), standby mode is the default power saving method, on Windows Mobile Smartphones, they don't use standby and are considered always on, so Windows Mobile Smartphones work very similar to the Symbian OS you describe. It's just Windows PDAs have the advantage of an extra powersaving mode.
Windows PDA devices don't always uses standby as they have an "unattended mode" where a program can tell the device it needs to constantly run, so while the device looks completely off, it will not be in standby in that instance. Also timers can be set to wake the device every few minutes, for example collecting email, where it will bring itself out of standby, do what it needs to do then back into standby again, but to the user the device will appear to be completely off.
I haven't said there is anything wrong with Windows Mobile power management. They can remain on like a Symbian device with Wi-Fi working if you set it that way and will run for as long as the battery will allow, that maybe a few hours or a few days, it depends what other software you have running and how much RAM needs to be kept alive.
If want to receive VoIP anytime over a Wi-Fi link then the Wi-Fi part has to remain constantly on, that's the rule of networking in order to maintain an open link and keep it's same IP address. A Wi-Fi device can't magically sense a call is coming in then turn on.
These devices are always trade offs, sounds to me like you want a Symbian device and not a Windows Mobile device, I don't think anyone has a problem with that and it's lucky we have a choice of what to go for.
Regards
Phil
PhilipL said:
Hi
Providing you don't have any bad being having applications battery life isn't impacted as much as you might think by leaving the PDA on using Wi-Fi (obviously the back light should time out to stop a major drain on the battery and so it may look off but it will still be running).
Click to expand...
Click to collapse
How practical is this? How do you get key lock functionality so that when the phone is in your pocket there are no unwanted touchscreen/key presses?
And can a WM device really cope with staying on (backlight off) from morning to evening with WiFi on plus the usual daily activity (calls, SMS, email, etc.)?
From my experience with Magician and Tytn this is totally impossible, unless the Qualcomm chip finally takes WM close to the performance of Nokia/SE devices.
One answer could be the fact that Symbian is a real-time operating system, meaning that it is capable of running on single-chip devices, while WM probably isn't.
I just can't believe that no 3rd-party software is there to solve such an obvious issue on WM devices...
PhilipL said:
These devices are always trade offs, sounds to me like you want a Symbian device and not a Windows Mobile device, I don't think anyone has a problem with that and it's lucky we have a choice of what to go for.
Click to expand...
Click to collapse
I do have a Nokia E61i, in fact, and I have had an HTC Tytn until a short while ago. And I am considering the new Kaiser now. So, as you can see, I am quite neutral. In fact, I keep switching between WM and Symbian about every three months!
But I was hoping that WM6 would finally solve this connectivity issue with WM devices, as I have become increasingly dependent upon VoIP, and therefore a good management of WiFI/3G connections is a key feature for me. The only reason why I got into this thread is that I was trying to find out if WM6 had finally implemented WiFi in a usable way (meaning without requiring me to manually switch it on).
The doubt came to me as I read some threads about the Toshiba G900, and someone was suggesting that the G900 was connecting to WiFi first and then to 3G automatically. I think someone mentioned an option in the 3G connections settings for this. It was a bit "between the lines", but I was hoping that WM6 had finally implemented this...
Thanks anyway for your time and for the good and informative dialogue.
Hi
How practical is this? How do you get key lock functionality so that when the phone is in your pocket there are no unwanted touchscreen/key presses?
Click to expand...
Click to collapse
There is a key lock.
And can a WM device really cope with staying on (backlight off) from morning to evening with WiFi on plus the usual daily activity (calls, SMS, email, etc.)?
Click to expand...
Click to collapse
I first got a Toshiba G900 and due to a now well publicised bug it would often refuse to come out of standby! A popular work around was to disable standby so it was on constantly and it worked fine. Providing you have well behaving applications it will still throttle right down to save power when it's not being used.
Don't forget that Windows SmartPhone devices are "always on" and don't seem to have a problem.
One answer could be the fact that Symbian is a real-time operating system, meaning that it is capable of running on single-chip devices, while WM probably isn't.
Click to expand...
Click to collapse
Windows Mobile is based on Windows CE, this is a real time embedded operating system used in a wide range of devices from barcode scanners, point of sale and up to ATMs.
I just can't believe that no 3rd-party software is there to solve such an obvious issue on WM devices...
Click to expand...
Click to collapse
There are programs out there that allow you to tweak various settings regarding Wi-Fi and the priority it's given over other connections. For many people it's not an issue anyway, if it is, the Kaiser will be a popular device and the developer community for Windows Mobile is very large and solutions will appear.
Regards
Phil
sirox said:
And a Nokia E61 can keep WiFi on (with VoIP in "always on" and listening) for two days with no interruption, and the battery won't be flat yet. So there is something wrong in the WiFi management of WM devices.
Click to expand...
Click to collapse
My Nokia E70 (some software as the E61), only connected to wifi when the screen was on. Or only when trying to connect to the Internet.
It never kept the wifi on all the time ...
battery life was much better than on the kaiser though, I'd be happy if it lasted more than a day with wifi on
jyavenard said:
My Nokia E70 (some software as the E61), only connected to wifi when the screen was on. Or only when trying to connect to the Internet.
It never kept the wifi on all the time ...
battery life was much better than on the kaiser though, I'd be happy if it lasted more than a day with wifi on
Click to expand...
Click to collapse
I am sorry, but I don't think you have actually ever used a Nokia E70. There is no screen-off mode on Nokia smartphones. And you can't switch on or off the WiFi radio, it can only be switched on automatically by an application that needs it. And it will be shut off ONLY when no application needs it anylonger.
Anyway, if you really have a Nokia E70, just charge it fully, then configure a VoIP account (linked to your WiFi router) using the internal VoIP facility, and leave it on like that. It will make and receive VoIP calls of course, and it will stay like this for well into the second day. And WiFi will be always on of course, otherwise it would not receive VoIP calls...
And if you take a Nokia E61i, it stays with WiFi on and VoIP activated for at least three full days, with no pause!
So there is something wrong in the WiFi power management of all WinMo devices...
And in any case, I have yet to see a reliable way of using SIP-based VoIP on a WinMo device. Reliable means: conversation quality like a normal call, stays in my pocket like any other cell phone, and rings when my VoIP line gets called, and can do this for at least a full day without draining batteries... So far, I have only seen this type of functionality on Nokia smartphones.
The Kaiser is one of the supported devices in AGEphone Mobile 2.5 Speakerphone Edition!
Subject says it all.
AS works (usually) for a while after reset, but then it just hangs saying "Synchronising" but gets nowhere.
Sometimes killing and restarting AS works, but usually I have to reset the damn thing.
Anyone else having this problem/found a solution? Not sure I'll get any sense from Orange (in fact, I am sure I'll get sod-all sense from them!)
Ferg.
P.S. Got HTC Home, iMate WMP Today, Live Search, Voice Command and many other apps installed. Perhaps it doesn't like Home or so.
More likely its a connection thing.
Try disabling advanced functionality in Start, settings, connections, USB-to-PC
That will make it try a USB connection instead of an IP based one.
Sorry, I should have said I was referring to AS on the device itself - it's Direct Push that's mucked up.
I meant on the device... but that was based on AS with pc
However, if you have an exchange server in the mix, then I would guess it either is losing the connection to the server. What happens if you leave it until it errors? (ie what error code)
Can you sync with the server OK when you do connect with USB to an internet enabled pc?
Well, the funny thing is it doesn't give me an error (or I've not waited the hours required for it to time-out).
The TyTN I have works a lot better under the same circumstances (same Exch, same account, sam SIM card etc, so it would deffo point towards the TyTN II itself.
The only thing left to do, I supose, is to ramp up the Exch logging and see what that says, but I wouldn't hold out too much hope of that.
Thanks for your assistance, unwired.
F.
Ok so its definitely the device...
Do you have signal issues on 3g where you are? Is your network allowing simultaneous voice and data? Have you installed the server certificate OK on your device?
Yeah, all the Exchange stuff is configured correctly - that's my job after all.
No 3G issues (since I use the TyTN from the same place.
Although I did notice recently that I can't actually have adata connection and a call at the same time (with 3G coverage). I guess I should be able to...
F.
sorry to bring up an old post,
having same sort of problem, but only when trying to get attachments. seems to take forever, (5-10 mins stuck on syncing then looks like it gives up) but the attachment is then there, which is crazy as its a 30k word doc which should take seconds.
did you work out any kind of solution?
edit: this is on a clients kaiser
Firstly, a big thank you to all contributors here, for the first time I thought I would contact HTC re problems with the diamond and believe me, I won't ever bother again with HTC support.
Over the years I've had many HTC devices and like many people here, have a strong understanding on subjects like push email. I just can't believe how difficult it is to talk to anyone from support areas regarding issues. I just thought HTC technical dept may be different, but sadly they are not.
The issues I have are (they have been discussed before but the threads have died with no solution)
1) Bluetooth headset, when disconnecting causes the Diamond to loose abilty to make any sound, be it ringing, alarm or music. This is random and only a soft reset cures the problem.
HTC response, Only HTC branded bluetooth devices are supported, tough!
2) Push E-mail, randomly forgets to check back with the server to see if their is a conenction and if not re-establish one. Logs show the device goes into sleep mode and is woke say 8 mins later (does change due to heartbeat interval changing) to ping server. however, its not waking. So I had a situation when the last server communication was 6am, and by the time I noticed I wasn't getting any mail 6 hours had past! Activesync on the device still show connected!!!
HTC response, clearly its your connection settings with your email. Hard reset and try again. Cant be our software.
Any ideas guys, I'm loosing the plot here. The handset is so much smaller and lighter than my kaiser, but I never had these issues.
P.S. I would never have bought another HTC device again if it wasn't for XDA. This forum has helped me so much over the years and also tought me the joys of WinMob!! HTC should be paying you guys!!
Bump:
Anyone else suffering from these problems? Push email is particularly frustrating.
I have this problem too. The answer from HTC is wrong because bluetooth is an universal standard and , is no reason to say to use only HTC bluetooth devices. Bluetooth should mean compatibility with all bluetooth devices . Another stupid answer from HTC.... Anybody to help us ...?
flashflash said:
Firstly, a big thank you to all contributors here, for the first time I thought I would contact HTC re problems with the diamond and believe me, I won't ever bother again with HTC support.
Over the years I've had many HTC devices and like many people here, have a strong understanding on subjects like push email. I just can't believe how difficult it is to talk to anyone from support areas regarding issues. I just thought HTC technical dept may be different, but sadly they are not.
The issues I have are (they have been discussed before but the threads have died with no solution)
1) Bluetooth headset, when disconnecting causes the Diamond to loose abilty to make any sound, be it ringing, alarm or music. This is random and only a soft reset cures the problem.
HTC response, Only HTC branded bluetooth devices are supported, tough!
2) Push E-mail, randomly forgets to check back with the server to see if their is a conenction and if not re-establish one. Logs show the device goes into sleep mode and is woke say 8 mins later (does change due to heartbeat interval changing) to ping server. however, its not waking. So I had a situation when the last server communication was 6am, and by the time I noticed I wasn't getting any mail 6 hours had past! Activesync on the device still show connected!!!
HTC response, clearly its your connection settings with your email. Hard reset and try again. Cant be our software.
Any ideas guys, I'm loosing the plot here. The handset is so much smaller and lighter than my kaiser, but I never had these issues.
P.S. I would never have bought another HTC device again if it wasn't for XDA. This forum has helped me so much over the years and also tought me the joys of WinMob!! HTC should be paying you guys!!
Click to expand...
Click to collapse
I currently don't use BT headset anymore. However, before using Diamond, I use the HTC Touch Elf with A2DPTOGGLE http://www.teksoftco.com/forum/viewtopic.php?t=1626
It can switch between BT headset or speaker. I tried beforeWM will not automatically switch between them. I know there is problem using the same A2DPTOGGLE in Diamond, because it is a Today plug-in and Diamind hide the Today from TouchFLO 3D. You may try to use "Second Today" together with the A2DPTOGGLE to fix your issue.
Another issue with your pushmail (via GPRS), I constantly working with pushmail and there is no missing mail. there are 2 things you may need to take into account.
1) check your peak or non-peak time. if you need to constantly receive mail immediately in 7x24, you need to set non-peak time also "arrive immediately". something like that.
2) apperantly, WM will save battery when device in sleep mode, WI-FI will deactivated. if you use WI-FI to work with pushmail, you may need some registry settings (i dunno which registry to control this) to disable such energy saving capability. Or, use normal GPRS or 3G data connectivity to test.
P.S. I hate to be the support of HTC product, but seems HTC have well-known bad after sales service.
Using adv. config. I disabled ,,joint stereo'' . I have no problems with ''no sound'' after using BT headset anymore. Can somebody else to confirm this ?
emilceteras said:
Using adv. config. I disabled ,,joint stereo'' . I have no problems with ''no sound'' after using BT headset anymore. Can somebody else to confirm this ?
Click to expand...
Click to collapse
I've tried but doesn't work, this problem's still here
Hmmm, not sure this is the best place, but it is a problem with my TD2 and certainly any searches so far have yielded little in the way of result.
So we begin - I've had my TD2 since May '09 until last weekend it has been recieving outlook items perfectly via GPRS/3G and Wi-fi all through Activesync/Direct Push without any problems. In fact normally quicker than the same item appearing in Outlook on my laptop via the VPN.
Last weekend we changed broadband supplier and upgraded our router at Head Office. Since then updates through Activesync have been sporadic at best but are normally non-existent. This is despite installing the new self-generated certificate for the new VPN/OWA IP number.
When plugged into my laptop and passing through to the Exchange Server via desktop Activesync the items will update on the phone. Unplug from the laptop and use GPRS and it takes an age to synhcronise before finally saying "Waiting for Network" and not actually downloading anything. Equally using the Wi-Fi at home gets similar results, though this is sometimes mixed up with a Server Temporarily unavailable actual error message rather than the meaningless "Waiting for Network".
Our IT support contractor is flummoxed (they got one of their iPhones to access my account and it worked perfectly and timeously). I have even done a hard reset of the TD2 and rebuilt the settings from scratch and we're still back to the same place.
I can only assume that it is something server side that is upsetting the process, but don't know what. Really annoying as it has all worked perfectly for 11 months and has now stopped working without me actually changing the device settings in any way whatsoever.
I went with a WM over an iPhone to get best MS integration, so why should this wobble give my phone problems when an iPhone can work away just fine?
So, any ideas from the great XDA font of knowledge of all things WM?
Many thanks,
Niall
Turns out the new router that was part of the broadband upgrade didn't have Port Routing configured correctly. One tick of a box and all is sorted for OTA syncing.
Still not working over Wi-Fi at home though so some work still needed somewhere.
Niall
If only it was that easy. Still get the Waiting for Network error.
I even did a hard reset, again, and got the "Waiting for Network" error on the first sync.
Only way to solve it seems to be to turn off SSL, but even that falls down after a while stating that:
Exchange Activsync has encountered an error. If this condition persists, please contact you Exchange Administrator.
Support Code 0x80830002
If I then desktop sync the device to Activsync on the laptop via USB (which passes through to our server Exchange anyway) it seems to "reset" the sync and OTA syncing will work again - for a time, normally failing sometime between 5 and 7am in the morning when I check Activsync on the TD2.
Our IT support contractor has washed their hands of it saying it must be the phone because they've had it working fine for several days on an iPhone and old WM6.1 HTC device syncing with SSL to my account. Having not changed anything on the device I don't understand what is wrong with it to behave so differently. Given that the phone is only 12 months old this a real downer.
Prior to the hard reset I was having intermittent filesys.exe crashing errors but these have gone now. Could it be related?
Flummoxed.
Niall
The IT bods have lent me the WM6.1 device (a Touch HD - man I love Sense 2.5 over Touchflo 3D.....). I have swapped SIMs so my TD2 is temporarily on Vodafone whilst the Touch HD has my T-Mobile SIM in it - both are currently syncing. Will see which one stops working first - so for those who are interested, watch this space!
Niall
For those that are interested here's where we are.
Niall M said:
Still not working over Wi-Fi at home though so some work still needed somewhere.
Click to expand...
Click to collapse
Got a new router a while back. Opened Port 80 and 443, all sorted. Obviously when the TD2 was working in the past I just wasn't noticing that Activsync wasn't working over WiFi, which is understandable given that Wi-Fi at home is normally for a bit of Facebooking and Casual Web Browsing and wherever the phone had the tiniest bit of T-Mobile signal it would still get push e-mail.
Niall M said:
The IT bods have lent me the WM6.1 device (a Touch HD - man I love Sense 2.5 over Touchflo 3D.....). I have swapped SIMs so my TD2 is temporarily on Vodafone whilst the Touch HD has my T-Mobile SIM in it - both are currently syncing. Will see which one stops working first - so for those who are interested, watch this space!
Click to expand...
Click to collapse
This appears to be a carrier problem. After working flawlessy OTA with SSL for 5 days (Wednesday to Monday) the Touch HD finally stopped at "Waiting for Network" whilst my TD2 with SSL carried on fine on Vodafone.
After a rather tiresome call to T-Mobile to try and explain the problem and have them tell me they've downloaded the manual for the TD2 and can I check the Activsync settings, settings, etc, I got put on hold for a while before they came back and said they've enabled Mobile E-mail on my account. They had no explanation as to why this had been disabled.
So the TD2 is back on T-Mobile with SSL. As of yesterday there was no improvement in that it would still fail. However I do appreciate that it can take a while for settings to take effect and so far "touch wood" today all is working as it should following a "Wi-fi reset" yesterday afternoon. Will probably update the thread further to confirm all is well or moan!
So in my case this was a carrier issue that caused the intermittent functioning of Activesync OTA. Changing to a different connection type e.g. Wi-Fi or Pass through via Desktop Activsync on USB would allow a successful sync and reset the OTA syncing (I guess it cleared the previous "dead/jammed/FUBAR'd" OTA Activesync connection) for a limited period of time. I am surprised that having Push E-mail blocked by the carrier allowed for intermittent functionality rather than a YES/NO it either works or it doesn't result!?!
So the lesson here is that the ability to receive Push E-mail may be a slightly different function from your Phone provider which can fail despite your data connection appearing to work fine (Web Browsing OTA on the TD2 was consistent throughout). I just hope this saves someone 4 weeks of phonecalls and hassle!
Niall
On one laptop I have Office2003 which refuses to sync with my Topaz, just sit there constantly trying to synch. PDA connects to laptop, is visable to edit the storage.
Another laptop has Office2010, this sync perfectly but will not allow checkboxes to be checked for contact, calender etc, only allows Mobile Favourites and OneNote...
Going to try a 3rd laptop [friends] that has Office2007 to see if that will fully sync...
T-Mobile phone monkey lied - Didn't make any difference.
The good news is that the problem is sorted. I've been reliably receiving push-email via Activsync OTA since last Thursday (5 days now).
Again it seems to have been a new router problem server side as we were also starting to experience VPN problems at work. The IT contractors contacted Draytek who told them that in one other instance (also on an LLU line) reducing the MTU value on the router solved the problem. Since doing this (maybe unconnected, the IT bods won't be drawn on it) the connection seems to work again. I've done some googling on MTU and the basic premise of reducing the value seems to make sense to me, smaller packets are harder to drop.
http://www.kitz.co.uk/adsl/MTU.htm
Any super techs that actually understand this stuff like to comment?
I can only hope this record of woes shorterns the inconvenience for others in the future!
Thanks,
Niall