Hi everyone,
just wanted to make a poll as to see which radio version people are using for their hermes. There are so many different versions, each has its own strength and weaknesses (i.e. reception, battery consumption, call quality, stability, etc) and its all different as to each of us' location, so I guess i made this poll to see which one people seems to pick the most and maybe it means something for some of us
For me 1.54.07.00 is the best. I had some toruble with data connection with 1.54.30.10.
PaY87 said:
For me 1.54.07.00 is the best. I had some toruble with data connection with 1.54.30.10.
Click to expand...
Click to collapse
Yeah it seems like 1.54.07 was pretty good for me as well; tho that the battery life is dramatically lower compared to when i used 1.47.x series (on pandora, schaps, official)
I dont have any data plans; but I do use 3d dialer occasionally, as well as wifidipping and bluetooth for files, keyboard and headset( lol yes, i am using a hermes but i also use a bluetooth keyboard -_-)
1.47.......
This thread could be extended to include the following
Country/Locale
Service Provider
OS/Build/Cook
Radio Version.
for me 1.47.00.10
UK, BT (using VF Backbone) better battery lifetime than the later ones.
Indeed.
I was actually thinking of starting a thread like this. I'm glad you thopught of it, kazuni.
I agree with tonyb, more information is needed, but I don't know exactly how to organize it. I am convinced that the issues are related to:
- Radio version
- How the radio is driven (ROM)
- probably Microsoft's EAS implementation
- how all the above react to low signal strength
At the risk of repetition I'll post some of what I have learned.
My interest in all this began when I got a Sprint 6700 a couple of years ago and was astounded at the terrible battery life, about 10 hours to full discharge. Here's my typical configuration (now on an 8525):
Service provider is AT&T
WI-FI and Bluetooth turned off.
Exchange Active Sync (EAS) is always running
POP3 mail only when requested (rarely, maybe every other day, 5 messages)
Phone is almost never used
Internet access used less than 30 minutes per day
Reading books, maybe 30 minutes per day.
In my office, about 9 hours per day, I have a very weak signal, 1 bar or less.
Elsewhere, 3-4 bars of signal is about average.
I learned from analyzing logs and with some help from Sprint and Microsoft tech reps that EAS seems to be the culprit in battery life. It works like this:
- The server and the pocket PC establish a persistent connection with a defined time to live (TTL) of several hours.
- While the persistent connection is running, they "ping" each other regularly, and in the process notify each other if there is any data to be transferred.
- This persistent connection uses very little power.
- If the "ping" fails, the connection is dropped, and the PPC tries to re-establish a new connection. If it can't (poor signal) it tries again in 3 minutes.
- if the PPC still can't get a connection it tries again in 5,7,12,and 15 minutes, then every 15 minutes until it succeeds.
- This process of trying to re-establish the persistent connection uses a LOT of power!
In the case of my PPC6700, the problem I was having was that the persistent connection was never re-established, even when moving into a 4-bar signal. I had to soft-reset the device to get the connection re-established. This has not happened with the 8525, but occasionally I have had to tell EAS to sync manually if it has lost its connection.
I've used vp3G and Schap's ROMs with radio versions 1.40, 1.48, and 1.54.07. Currently I'm running vp3G 3.62.3 with radio 1.54.07.
I understand that 1.48 and 1.54.07 radios are "good with AT&T". Certainly, and I don't know if this is real or just a fault in the bar-graph program, but I am getting 2 bars in my office with this radio, while I had 1 bar with the others.
I'd be interested to hear some ideas from the ROM and Radio experts.
I'd also like to learn how to interpret the results from the Firld Test program. There seems to ba a lot of info about he cellular signal there.
Walt
Been rock solid with the 1.54.07.00 and battery life is a full day also..
Country/Locale > Toccoa, GA USA
Service Provider > ATT
OS/Build/Cook > vp3g latest
Radio Version > 1.54.07.00
All this was done to my phone the day I got it. But set this way my 8525 gets great battery life as after 24 hours it is only on 70% (normal use).
Currently 1.54.30.10 - good battery life. No noticable reduction in signal strength / connection issues with any radio I've tried - I typically get the latest one available as they are posted.
Might be because I'm near Seattle and there's a tower every 50 friggin feet, so my phone doesn't have to crank up the power to acquire / keep a connection to the tower.
1.54.30.10... I like the speed at which this one finds the signal.
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.
A few people have been having the same issue as me with more recent AKU3.* ROMs, wherein the radio features (GSM/UMTS,GPRS etc) - cease to function. Symptoms include the connectivity icons becoming non-responsive to stylus-press, and phone calls starting, but no call being made (silence) - and calls refusing to end.
This has been driving me nuts, and just when I think a new ROM (CE or Radio) has solved it, it re-appears. I have been playing around with everything I can to either diagnose, or solve this problem, and this is what I have found:
The phone only locks up, when handover between GSM and UMTS has occurred several times. I use the Hutchison 3 network in .au, and the coverage in Sydney is a bit spotty - hence the frequent handover to 'Roaming', and back again. Now that I have disabled the GSM functionality (i.e. just use UMTS, in the 'band' menu in 'Phone' settings) - I haven't had a single phone lockup.
To the other people having this issue: does this pattern of use sound familiar? I.e. is your main carrier UMTS, roaming to GSM? I'd like some feedback to see if we can isolate this, or if this solution works for other people
Hey
Had this problem many times with all kind of roms.
Usually the icons would react to clicks, but internet wouldn't work and also calling.
When I would turn on flight mode, the right icon (your reception) would change and gets a little cross (telling its disabled). But the left one would still be stuck on G/U as connected. It would take a min or 2 before it finally updates to a little cross saying its disabled. Then I can disable flight mode again and the phone would work (most of the time)
I live around 70 km from my work and I drive back and fort every day. In the car my universal is in the charger and I have always live messenger connected and AS for email.
during this trip my reception is lost twice, besides that it switches a couple of times from Umts to Gprs.
I've updated my phone to 1.14 radio en helmi 3.5 aku rom. And have experienced a couple of times what you discribed. The 3G and G/U icons wouldn't react to the stylus and the phone seems to be stuck. The device itself still works. But I have to soft reset to get it going again.
So after reading your story I can say this scenario refers to my experience.
I'm gonna try your solution from off today and let you know
I have only GPRS here and this problem happens to me with all AKU3.x versions even with different radios (1.09 -> 1.14.10) ... I still believe it has nothing to do with ONLY hand-over ... I reverted back to AKU2 and it never happened since then
Same here....
I have similar experiences with UMTS and GSM handover issues. I observed that sticking to one band (in my case GSM since it is more prevalent than the other in countries I go to!) is the way to go. When in M1, I got dropped problematic calls and my SMS were delayed but when I stuck to GSM only then everything was back to normal. I have been trying out the new Radio Rom 1.14.10 with Helmi AKU3.5 for 3 days now and am not having handover issues! Could be the Radio Rom or the Rom itself but if it acts up again then I know what to do then! Hope this helps!!!
The problem is in rilgsm.dll file.
I can tell that it is solved in crossbow.
mamaich said:
The problem is in rilgsm.dll file.
I can tell that it is solved in crossbow.
Click to expand...
Click to collapse
would replacing the file in the current aku3 roms with an older one fix it?
i myself dont have the problem but allot of 3.2 wizard testers do.
Good to know, that I'm not the only one with this problem. I have seen this behaviour in all ROMs, not just the AKU3 and can confirm that it iseems to be related to the switchover between UMTS and GSM.
It also only seems to happen only when you have the internet connection open, which will always be the case when you use push-mail.
I had similar problems with the MDA III, whish I used before. Maybe it will get fixed in Crossbow - but by then we'll likely all have new phones.
^^
My internet connection is also always active. I have now switched from AUTO network to WCDMA (umts).
Going to see if this helps. After that I'll try the GSM band to see if it makes a difference
But it's something my device always had problems with, so I guess it's ROM independent
I'd like to see if that rilgsm.dll can be re-used. Unfortunately, the coverage of UMTS in the area where I live is far too spotty to be comfortable with pinning the radio band to UMTS.
However, I'm interested in your thoughts.
I must say that I agree with biso007. This problem started to occur when I upgraded to AKU3 roms. Before, I was on AKU2 with the exact same radio rom (I didn't flash it!) and never had any issue. Combined with mamaichs comment that it is related to a DLL file, I would say that the problem is indeed not related to a radio-ROM but to the AKU ROM.
Just my 2 cents....
I had same problems with Radio lockups on my UNIVERSAL. I've tried different ROMs with no luck. BUT after changing my Radio rom back to latest from T-mobile (1.10.03) everything back to normal- all day driving with GPRS on - no lockups at all!!! 100% solution is..... use old radio rom.
Would not mind downgrading...
I have lockup issues as well... if this really helps, I will downgrade the Radio ROM without hesitation. Where can I find thsi Radio ROM; is it on the xda-dev FTP site?
Thanks,
-Ireneus
Hi All!
Yes, this issue is the most annoying among all other issues, and it makes UNI impossible to use as the phone for business communications.
I confirm that lockup issue existed on EACH radio version I used and on EVERY ROM version.
I don't think this issue is caused by the GSM Band switch or Internet connection active or anything else specific, because this lockup happend even on networks with no 3G at all and no internet connection active and also BT and WiFi off.
It happens when I start intensivelly use my UNI for calls, sms, open contacts, view appointments (note: No 3-d party software at all).
I also mentioned that the issue happens more often with the battery level below 50% or so and almost rarelly happen on external power.
Another "good news" here is that if you receive an SMS during that intensive operations, you will permanently lose it after the phone lock up.
Thank you,
Dmitry.
I wonder is this is just a Universal issue? Or do other devices have the same issues; I mean as frequently as on the UNI.
If it is just the UNI than indeed it is useless as a phone and nothing more than a beeping, brick with a nice VGA screen. I basically fidn it hard to believe that this is the case and I would like to know if there is anyone out there, who does not have lock-up issues with the UNI and I would also like to know from the people who are testing Crossbow if the lock-ups still happen?
All input appreciated.
-Ireneus
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....
I have finally decided to give WM6 a go on my Vario II and flashed it with latest 1.40 Olipro bootloader, 1.38 Radio and LVSW WM6 OS (btw, BIG thx for MrVanx for really great tutorials!).
In addition, I have installed VoIP application (http://forum.xda-developers.com/showthread.php?t=299950 ) which I found pretty interesting, however it's also pretty unusable as WLAN connection goes down together with VoIP service while Hermes enters standby mode. I have found solution (http://forum.xda-developers.com/showthread.php?t=245773 ) which unfortunately seems to not work with WM6. After applying Default={'0', '1', '2'} values, whole device completely hangs after resuming and the only solution is soft-reset by stylus. I've also set AllowSuspend=0 in HKEY_LOCAL_MACHINE\Comm\Parms, but it also does not keep WiFi on. Basically - I cannot effectively keep WiFi and VoIP up, which make whole VoIP application totally useless.
Did anyone manage to resolve this problem?
eva_d said:
I have finally decided to give WM6 a go on my Vario II and flashed it with latest 1.40 Olipro bootloader, 1.38 Radio and LVSW WM6 OS (btw, BIG thx for MrVanx for really great tutorials!).
In addition, I have installed VoIP application (http://forum.xda-developers.com/showthread.php?t=299950 ) which I found pretty interesting, however it's also pretty unusable as WLAN connection goes down together with VoIP service while Hermes enters standby mode. I have found solution (http://forum.xda-developers.com/showthread.php?t=245773 ) which unfortunately seems to not work with WM6. After applying Default={'0', '1', '2'} values, whole device completely hangs after resuming and the only solution is soft-reset by stylus. I've also set AllowSuspend=0 in HKEY_LOCAL_MACHINE\Comm\Parms, but it also does not keep WiFi on. Basically - I cannot effectively keep WiFi and VoIP up, which make whole VoIP application totally useless.
Did anyone manage to resolve this problem?
Click to expand...
Click to collapse
I wish, I tried the same things you did with the same failures
eva_d said:
I cannot effectively keep WiFi and VoIP up, which make whole VoIP application totally useless.
Did anyone manage to resolve this problem?
Click to expand...
Click to collapse
You'll find that if you kept WiFi on all the time, your battery will last about an hour (or less).. so... it's by design that WiFi shuts off when the phone drops into sleep mode.
I thought that WIFI used less energy output then Bluetooth and I've used a bluetooth headset on a phone call that lasted well over 3 hours and still had plenty of battery to last the rest of the day. Aside from 90% of the day I could easily keep the phone on charge (It's used on charge at home, work and in the car)
jmat said:
You'll find that if you kept WiFi on all the time, your battery will last about an hour (or less).. so... it's by design that WiFi shuts off when the phone drops into sleep mode.
Click to expand...
Click to collapse
Yes, I am aware of that, as in every single topic I've found regarding this problem, there are zillions of posts saying about poor battery, but rarely anyone is coming up with actual solution.
Anyway, battery life is obviously a big downside, however without keeping WiFi on, there is absolutely no point of having VoIP application at all. I would be pleased to have fully working VoIP in my Hermes, as my first tests showed it works quite fine and could be excellent cost-saver international phone calls.
BTW, I'm curious how VoIP app works in official release of WM6 (not xda-cooked ROMs) - I cannot believe that VoIP configuration must be done by preparing XML/CAB file with settings, and WiFi goes down together with VoIP, making it useless. :-o
What about using a Screen Off utility like the ones used to keep Windows Media Player Working while turing the Screen Off. Then you would also need to go to the Battery Applet and unCheck the StandBy option.
.
eva_d said:
Yes, I am aware of that, as in every single topic I've found regarding this problem, there are zillions of posts saying about poor battery, but rarely anyone is coming up with actual solution.
Anyway, battery life is obviously a big downside, however without keeping WiFi on, there is absolutely no point of having VoIP application at all. I would be pleased to have fully working VoIP in my Hermes, as my first tests showed it works quite fine and could be excellent cost-saver international phone calls.
BTW, I'm curious how VoIP app works in official release of WM6 (not xda-cooked ROMs) - I cannot believe that VoIP configuration must be done by preparing XML/CAB file with settings, and WiFi goes down together with VoIP, making it useless. :-o
Click to expand...
Click to collapse
My guess is the official release will be something lame - only enablable by phone companies - i.e. Cingular will start offering Cingular VOIP where for $5/month more you can make unlimited calls within the U.S. (or insert your local country) on Cingular voip without using your minutes or something like that. The VOIP settings will be pre-installed by the carrier and you will be "unable" to change them yourself. I really have no idea if this is actually the way it will work but it tends to be the way that potentially cool things like this pan out :S
eva_d said:
without keeping WiFi on, there is absolutely no point of having VoIP application at all.
Click to expand...
Click to collapse
VOIP is good on 3g as well(we currently use 64KB for a video calls! voice only will be much less, data costs will be much lower then minutes while calling long distance for example).
use it like this:
1. initiate the call yourself(turn on the WIFI)
2. use your DATA plan for long distance calls(out of country)
elivne said:
VOIP is good on 3g as well(we currently use 64KB for a video calls! voice only will be much less, data costs will be much lower then minutes while calling long distance for example).
Click to expand...
Click to collapse
That's right, however any VoIP usage is strictly forbidden in my data plan (T-Mobile UK web'n'walk £7.50 option), and I don't want to risk any fines or anything for misuse of the service...
cyberdrakula said:
What about using a Screen Off utility like the ones used to keep Windows Media Player Working while turing the Screen Off. Then you would also need to go to the Battery Applet and unCheck the StandBy option.
.
Click to expand...
Click to collapse
Why dont you do that Eva_d ?
Also, like mentioned before, wifi will murder your battery, but if you want to use VoIP for home use only, or office desk, then you can simply have a an extra long USB cable to constantly charge the phone. In the "backlight" settings, you can chose to have the phone ALWAYS-ON when plugged into a charger.
That way, you'll have a "home phone". All you'll have to do is unplug the charger if you wanna talk on the phone and walk around the place wireless
alkizmo said:
Why dont you do that Eva_d ?
Also, like mentioned before, wifi will murder your battery, but if you want to use VoIP for home use only, or office desk, then you can simply have a an extra long USB cable to constantly charge the phone. In the "backlight" settings, you can chose to have the phone ALWAYS-ON when plugged into a charger.
Click to expand...
Click to collapse
Well, I found different solution. Using PocketZenPhone I have created 'VoIP' profile, which does not switch device off at all. So, when I plan to make or receive call through VoIP, I just switch that profile on, then WiFi and that's it. Maybe not very convenient, but works fine for me.
eva_d said:
Well, I found different solution. Using PocketZenPhone I have created 'VoIP' profile, which does not switch device off at all. So, when I plan to make or receive call through VoIP, I just switch that profile on, then WiFi and that's it. Maybe not very convenient, but works fine for me.
Click to expand...
Click to collapse
Thats a good idea. Just did the same with mine.
eva_d said:
Well, I found different solution. Using PocketZenPhone I have created 'VoIP' profile, which does not switch device off at all. So, when I plan to make or receive call through VoIP, I just switch that profile on, then WiFi and that's it. Maybe not very convenient, but works fine for me.
Click to expand...
Click to collapse
Just purely out of curiosity, how does your battery life do leaving WIFI constantly on - can you make it through the day? If so what do you have left?
chymmylt said:
Just purely out of curiosity, how does your battery life do leaving WIFI constantly on - can you make it through the day? If so what do you have left?
Click to expand...
Click to collapse
I neved used WiFi for whole day. I only switch it on when I need to call through VoIP. For everyday internet use I have T-Mobile's WnW package.
However, I must say - WiFi drains battery REALLY fast...
Sorry if this has been covered before, I've been searching the threads for quite a while though only came up with those having problems with standby freezing.
So I have a 838pro, running Elf 2.1 - Clean! -- Connected to exchange 2007 (push) 3g/HSDPA. This works great -- except I cannot go far from a charger since my pda will not enter standby mode.....(unless i hit the power button - this works fine, and so does resuming) -- Every thing is great except it drains the battery like no tomorrow.
Not running wifi or bluetooth. 3 Network in Australia.
If I kill the activesync service it will standby as set by my power settings (1min power/30sec screen)
Would my exchange server be playing funny buggers?
I've tried a couple of different roms (black etc) and all seem to have a similar problem.
Running 1.41xxx radio / hard spl v7;
Any ideas?
Cheers.
Since yesterday, I've down graded to my Networks current rom (which is 1.30 vm5) and standby works fine.
Tonight I will re-flash to a wm6 rom and see if it helps (e.g. not changing the radio rom back to 1.41)
The rom I got is specifily for my network so call quality is actually better than 1.41 - with regards to range/data -- too early to tell.
Cheers'
Snoops said:
Since yesterday, I've down graded to my Networks current rom (which is 1.30 vm5) and standby works fine.
Tonight I will re-flash to a wm6 rom and see if it helps (e.g. not changing the radio rom back to 1.41)
The rom I got is specifily for my network so call quality is actually better than 1.41 - with regards to range/data -- too early to tell.
Cheers'
Click to expand...
Click to collapse
My phone has never gone into standy while using Push from the exchange server. Once I make it sync every 15 minutes it seems to be able to turn the screen off.
Rob
Well about half way thru today it started doing the not sleeping thing. So tonight I re-installed elf and tried using push with an exchange 2003 server (I am not sure of services packs etc, as the exchange 03 server isnt hosted locally).
So now it has been running for about 4 hours without any problems. It must be a exchange 2007 thing.. Maybe the keep alive packet??
Any Ideas?
same issue here
I noticed since I set up DeniaL's Exchange 2007 service, my battery life went into the toilet. My bro in law was comparing phones (he has a Hermes too) and asked why mine never went into standby... Battery problem discovered... Ideas anyone?
Does Denials owa access use http or https?
(e.g. when you setup your exchange server do you leave the ssl option ticked?)
After having a little time to play around.. I think (might) of found the issue.. Syncing over a http connection seems to be the problem for me. Switching to ssl seems to fix the issue... -- Will update in a two or two after more testing