I am looking for users with problems using the MS Voice Command on the T-Mobile Wing/Herald and their fixes or commments.
I have been using WM devices and MS Voice Command for many years. I have had a variety of devices all using voice command; but none have been worse at recognition and speed as my Wing has. How does everyone else with a wing feel about MS Voice Commands performance.
Problems I experience:
Slow response to initialization (1-2 seconds usually)
Slow finding a contact and confirming (2-4 seconds)
Most times with some background noise just gives up and makes that aweful beep.
Always asks to Please try again
Will not understand through bluetooth headset at all.
Commonly mistakes simple names for others i.e. (John Patrick)
Now the voice command can work pretty accuratly in a queit room other than the responsiveness, but I have had it installed on numerous devices and know how it should opperate and the tolerance to noise. I have overclocked my CPU to 273 and doesnt seem to help. I have tried increasing the page pool to 4mb which I have 23mbs for memory and still no luck. Ive even tried the combination of the two but doesnt seem to help. No other progams have been installed for test purposes to see if there is any conflicts and I have about 73 contacts, and sync very little content.
My previous device was a Wizard which respectively is very simular. It did work good with voice command 1.6 both on WM5 & WM6. I have had it installed on a Audiovox PPC4400 (WM2003), Treo 700wx, Blue Angel (WM5), and a Hermes (WM6); all the later devices worked best with no noticable delay or comprehension issues. The Herald will work with the same bluetooth equipment almost flawlessly, the wing will initiate the command but always fail to understand or will pull up something else.
I would like to know if I'm and isolated instance or if everyone has this problem.
Thanks
Jcostanza4
Works fine for me! However, I do speak in a Robotic tone.
Naw, I cant get that thing to do what I tell it.
YES!!!! MS Voice Command on the Wing is almost unusable for me. On my Wizard it was amazing -- fast and accurate. On the Wing frustrating, maddening and worthless.
I have experimented with standard versus overclocking, mic gain settings... everything I can think of. It seems to be a little bit better if I have Bluetooth turned off -- but just a little bit.
I have been reading these forums since the Wing was released and have been surprised that others have not commented on the problems with MS Voice Command on the Wing.
I sure wish there was an answer. Does anyone know what the problem is?
I agree with you, I dont know why more people haven't brought it up.
This is one of the biggest downfalls of the Wing for me. I love everything else even speed when overclocked and the page pool make it quite fast. But I just disable voice command completly because it is so unrelaible. I think it would more likely be along the lines of a hardware compatibility issue that the software would have to overcome or a fix in the OS; but I really dont know.
I wonder if the Herald guys get this problem or if its just an issue with the Wing OS.
Time will tell.
Jcostanza4-
It seems like it's just the crappy microphone on the bottom. It picks up EVERY noise around you and that confuses the voice command. I've noticed that if I use the wired headset that came with my wing it's almost always accurate.
Take a voice note in a semi-noisy environment and you'll see what I'm talking about. It definitely is not a noise canceling microphone.
Well... I can confirm that the audio quality of a voice note is clearly superior on my Wizard than on the Wing... considering that other people do not seem to be up-in-arms about MS Voice Command, I am coming to the conclusion that the microphone on the Wing is at fault.
Has anyone had problems reported with phone calls
Ive asked people if I sound faint or hard to hear and they say it sounds fine/normal. Also bluetooth mics also seem to have the same problems with comprehension when other Window Mobile devices with the same hardware work like they should. Ive tested the Hermes with WM6 on the same bluetooth car kit with MS VoiceCommand over bluetooth and no problems; I know certain bluetooth with VC works and some dont, the Wing seems to operate just like the hermes as far as initiation. This would bypass the poor mic theory on the Wing right?
jcostanza4 said:
Ive asked people if I sound faint or hard to hear and they say it sounds fine/normal. Also bluetooth mics also seem to have the same problems with comprehension when other Window Mobile devices with the same hardware work like they should. Ive tested the Hermes with WM6 on the same bluetooth car kit with MS VoiceCommand over bluetooth and no problems; I know certain bluetooth with VC works and some dont, the Wing seems to operate just like the hermes as far as initiation. This would bypass the poor mic theory on the Wing right?
Click to expand...
Click to collapse
I haven't used a bluetooth headset before on my wing but my wired headset works flawlessly almost every time. It could be that the bluetooth connection wasn't as strong or something (biased towards the wing not working when testing?). I still believe it's the microphone but I could be wrong
I havent really had too much problem with it, I'm using the PDAVIET rom and had to reinstall voice command once i had the rom, and it seems to work fine. Have you tweaked the mic gain?
Tweaking th mic gain.
dcmtnbkr said:
I havent really had too much problem with it, I'm using the PDAVIET rom and had to reinstall voice command once i had the rom, and it seems to work fine. Have you tweaked the mic gain?
Click to expand...
Click to collapse
Is your device a wing or a herald?
Im still using the stock T-Mobile Rom on the wing and Ive enable and disable the mic gain; shows no improvement that I can tell. Now the Wing comes pre installed with Voice Command and does not have a remove from the Uninstall Program options. I did once try to install 1.6 over it to see if i could get back the remove option and when I clicked reset to finish after installing it hard reset on me.
On your PDAVIET rom, does the vioce command launch instantly, respond quickly, and understand you to some degree or is there some trouble in any of these areas?
Thanks for the info
jcostanza4
me, too - very disappointing indeed
Yes, I just got the Wing a couple of days ago after giving my wonderful Imate Jam one too many love taps (the touchscreen has stopped accepting any input)...and I'm experiencing exactly the symptoms you listed with VoiceCommand. It actually does seem to do a little better through the BT headset, so the "poor mike" theory might be on the right track. But without the BT, it can't understand a damn thing--even in perfectly quiet environments--and takes forever.
I've been using the Jam with VC for over two years, and it is fast and damn-near flawless. Indeed, I've been a huge VC zealot; 'never been able to understand why WM-device reviewers don't even mention it but instead say things like "it's too hard to dial calls one-handed when driving." And for years already, while the best that other devices could offer was "voice tags" that users had to manually create, VC has, as you know, seamlessly worked with all my ~500 Outlook contacts. As far as I'm concerned, VC is the killer app that provides a huge part of the value of WM devices. If you ask me for the phone number of any of my friends, family or business clients, I couldn't tell you, 'cuz I haven't dialed them in years.
Now comes the Wing to set progress back five years or so. I have 12 days to make a decision about returning it.
mtn_lion said:
Yes, I just got the Wing a couple of days ago after giving my wonderful Imate Jam one too many love taps (the touchscreen has stopped accepting any input)...and I'm experiencing exactly the symptoms you listed with VoiceCommand. It actually does seem to do a little better through the BT headset, so the "poor mike" theory might be on the right track. But without the BT, it can't understand a damn thing--even in perfectly quiet environments--and takes forever.
I've been using the Jam with VC for over two years, and it is fast and damn-near flawless. Indeed, I've been a huge VC zealot; 'never been able to understand why WM-device reviewers don't even mention it but instead say things like "it's too hard to dial calls one-handed when driving." And for years already, while the best that other devices could offer was "voice tags" that users had to manually create, VC has, as you know, seamlessly worked with all my ~500 Outlook contacts. As far as I'm concerned, VC is the killer app that provides a huge part of the value of WM devices. If you ask me for the phone number of any of my friends, family or business clients, I couldn't tell you, 'cuz I haven't dialed them in years.
Now comes the Wing to set progress back five years or so. I have 12 days to make a decision about returning it.
Click to expand...
Click to collapse
I made all of my contacts store with first name, last name format and the recognition appeared to get a lot better. You shouldn't have to do that but it seemed to help so you could try it. I am temporarily trying the wing overclocked to 273mhz with a boost up to 286mhz and in a quiet environment I haven't had a problem with the voice recognition finding my contacts. I still have trouble with the "play" command and it's VERY difficult for it to understand my "yes" for some reason but contact recognition is good and speedy.
The yes response or correct doesnt pick up well for me either
I did notice this too, but I always forget that thats one of my biggest problems with dailing by name or number. Let's say its a bad mic, even with a headset wired/wireless does it seem to lag in speedy ness or accuracy?
I did mess with page pool on the Wing, I ran 4mb for about 2 months then moved to a 6mb and the device is overall faster than the 4mb or 12mb. The 6mb page pool defenitly responds quick when it can understand you; but 70% of the time it can understand and gives that very long pause before saying "please repeat". It does seam like voice command when enabled eats about 5mb or ram. I have 22.5mb on a soft reset and after using voice comand once it drops to 13mb and then goes to 17mb after about 3 minutes of no use.
I have not read anything from the Hermes users to show that they are having these issues. Could it be an OS problem that translates the mic to the program?
Jcostanza-
kraftey--Thanks for the suggestion, which makes sense, I guess...but I'm not willing to organized my contacts by first name, period. Call me a neo-traditionalist.
As I've posted in the overclocking thread, I can't get my Wing above 228 without the screen flickering.... Ideas?
jcostanza4--Thanks, too. Honestly, in a *perfectly* quiet environment, recognition is not bad, and using either BT headset or not, time from command to response is 5-7 seconds. That doesn't sound like much, but in actual use at work it's an eternity--and made much worse by all of the "Please Repeat"s, additional delays and/or failures.
I've got the pagepool set to 6MB, and I've mucked about with performance-related registry tweaks, but the 5-7 seconds and poor recognition in real-world environments is the best I've been able to get out of VC so far.
Im overclocking the Wing with Battery Status Ver. 1.04.203
I have the device set on dynamic mode so its 201Mhz on minimal load and 273Mhz on Max Load. Battery can last quite a while like this and I havent had screen issues. I hope this helps. I had issues with some other overclocking apps, and eventually tried this one and it worked. No complaints and Ive been using it for about 4 months.
Yes. The darn thing is frustrating. This was supposed to be top of the line. I paid around $250 for the PDA and I paid $100 for a top of the line bluetooth, and the voice mail keeps trying to call my Brother Jeff, regardless of what I say. I paid $140 for a Jawbone, and got the same poor performance. Just how much do I have to pay to get something that works.
Yes, jc, that helps. I had already moved to BS, but now I'll update it with the 1.04 beta. For starters, what OmapClock was calling "228", BS calls "247." With the "released" version of BS, I still get the screen flicker above "247." We'll see if it's any different after I install the beta. Thx.
I solved my Voice Command Problems!
I originally posted all the issues I was having with Voice Command 1.6 on my T-mobile Wing. I now have a working Voice Command to my standards, it works as it has on all my other devices; a little slow at times but not more than a second lag. Recognition is accurate and mic also seems to work better.
Here is the steps I used. (this was completely accidental, as I was trying to get TouchFlo working on the Wing)
I reflashed the T-Mobile Wing RUU found in the Herald wiki section or this thread http://forum.xda-developers.com/showthread.php?t=321717
Then Flashed the Original T-Mobile Rom with Touch Flow found here http://forum.xda-developers.com/showthread.php?t=329456
Then I Ran the Automatic 6mb page pool found here http://forum.xda-developers.com/showthread.php?t=324955
Then I installed Battery Status and overclocked my Wing to 273mhz.
I dont know if the RUU that was released was an update to the original rom, but my mic seems to work great now and recognize with about a 90% accuracy rate.
Please try this at your own risk, This may work for me and may not work for you. By all means I am no programer nor can I assist in a sticky situation.
I suggest reading each of the other threads I have listed before attempting. I will not be responsible if you brick your device. There is alot of information in each thread that is not posted on the first Topic like using ASerg Policies or how the page pool works or common problems.
Thanks-
Jcostanza4
Start > Settings > System > Microphone AGC
I don't use voice dial because I had all the same probs as the original poster. May want to give this a try before all of the steps mentioned in the post before me
for me it is working fine most of the time but not as good as it did with my wizard it is not slow and recognizes commands most of the time, I am using the pdaviet rom build 12 I changed the page pool to 4mb and clocked to 260 with bs , my problem though is that I can't get voice command to work by pressing the bluetooth headset button wich works fine on the wizard.
Related
Hello everyone,
I have generated this post to get some feedback from those of you who may have upgraded your BAs from WM2003SE to WM5.0. I have been following all the updates rather close. All I can say is that Mamaich and Tuatara are 2 absolute heroes in my book. The latest (for those of you who are not sure of what verison of the rom is out there) TuMa v1.3 seems to be the cream of the crop at this point.
Anywho, what I would like to get from this post is feedback on the following (all of these are to be compared to WM2003SE, so keep that in mind when replying):
*Speed of the device
*Overall stability
*Issues (other than the infamous BT disconnect). BTW, we are counting on you for this, Mamaich and Tuatara. 8)
Keep in mind that I want to try to get a good comparison between the OS's. Please remember that the point is to inform people who, very much like myself, does not know squat about programming, but has some knowledge about certain things and want to upgrade to WM5 just because he/she can Personally, my SX66 works like an absolute charm with WM2003SE, but I am really curious as of the new capabilities of WM5 (and at the same time, I do not want to turn it into a brick with a sliding keyboard--- :? . --- --- --- R.I.P. MPx200 (after attempting to upgrade to WM5)
Anyway, any feedback on this will be greatly appreciated.
Thanks guys and may xda-developers live forever!!!!
Personally, I can't see many extra features of WM5 for what I use it for. The only difference for me in all honesty is the fact WM2003 is so ugly when you've used WM5.
Bluetooth is worse, not just the d/c problems but not as feature-full as yet. I miss being able to browse peoples devices etc.
The device becomes really lagged when you use Wi-fi and Media Player
Media Player has trouble with MP3's (not actually tested with wma) for the first minute or so while it buffers.
However, saying all this, I wouldn't go back. Despite WM2003's profound ugliness, the recent TuMa 1.3 works a treat and really feels secure, even securer than I felt with WM2003. The speed is excellent too, except when using Wi-Fi or using Media Player. TuMa 1.3 is also reeeaally easy to patch to your operator, all you need to do is open a command window (Start > Run > type cmd > navigate to the folder > then SetOperator <type your operator value next to it>.
Quite frankly, if you are even slightly eager to try it, you still wont really feel content until you do despite matter what we say. Just go out and try it and you shant want to go back!
Hope this helps!
Leo
now WM5 pack3.1 is very fast,i like it
My opinion is that the Bluengel gets very slow with WM5.. I'm considering to go back to WM2003 again...
My opinion is that the Bluengel gets very slow with WM5.. I'm considering to go back to WM2003 again...
is the keyboard repeating issue resolved?
alex_zou said:
now WM5 pack3.1 is very fast,i like it
Click to expand...
Click to collapse
what pack 3.1????
I guess he meant v1.3. He just got it backwards, By the way, thank you all for the good feedback. Keep it coming though!!!
Hi,
The V1.3 rom is good and it's quite fast but I have had too many problems with the phone side to keep using it. These are the problems that I've peronally had which Have Forced me to go back to 2003:
1) Recieving phone calls. When some calls me it goes through to the voice mail but if they hang up and call me again it comes through.
2) Making phone calls. When I dial someone the call is immeadtly ended then I dial again and it take about 20-30s for the call to be dial and then it end the call after 1 min
3) When i run an application and close it the running tasks tells me it's still running.
These all seem to specific to my device as there are mayeb 1/2 other people with these problems(phone), one of whom has also gone back to 2003.
Just my 2 pence worth.
Thanks
satpal
I agree WM5 is cuttier and more steady. As of the new TuMa 1.3 upgrade, I've never seen my device so glad to run a ROM yet
IT'S REally feature-packed, even when I won't use all of the features. It felt very strong, stable and FAST!! (I don't notice the slowliness some others say, moreover it feels faster than with 2003), more than any other ROM I've tried to date. WOW WHAT A JOB!!
I'm having a problem with the phone where I can not get any sounds from the phone making, nor receiving calls. I can not hear or be heard using the loudspeaker. Using the Bluetooth headphone works, though. But, bluetooth is sooo weeak on this device (my impression) that for me is not really worth it. I was using a Nokia phone (80something) and the Bluetooth stack felts very strong and stable and, at the very least, you could hear the sound clearly, without the scratchs and noises I'm used to sort in a bluetooth conversation using my BA.
That's why I revert my BA to WM2003, to check if the problem was because of WM5 but, now, the problem persists, and I don't have so many other options...
Just a thought: if you wanna better Bluetooth thingie, don't go WM5: M$ stack is a crap... lacks everything...
it's definitelly worth trying... I like the usability and keyboard navigarion better... in 2k3, it is impossible to even close a simple gprs popup without touching screen where as in wm5 you can simply press right arrow key and enter to close it... there are plenty of small things which make it more usable for day to day usage
plus It gives you the courage to upgrade to a more steadier device with wm5 pre installed... like I bought universal after using BA for couple months
[edit] the WM5 version I tested was 1.3 TuMa.
My QTEK 9090 really didn't like WM5.
I love the look and feel, and particularly the MSN integration, but had to go back to 2003SE.
Do tell me if I missed anything that would fix the issues below and allow me to go back to WM5 :-
1 - SLOOOW. Some apps more than others, for example reading an SMS takes 5-6 seconds to open a 30 character message.
2 - Phone. Keypad very slow. Audio cuts out halfway through a call, seemingly at random.
The second point is what forced me to downgrade. If my smartphone is not a phone, then it's no use to me.
The last test I did with WM5 was using the 1.13 radio ROM. I've since updated it to 1.15. Has anyone seen any WM5 improvement with higher radio versions on PH20B hardware? I ask because I've been through the reflashing process so many times, I realise I am pushing my luck and will end up with a brick sooner or later.
Updates are in BLUE
Okay, time for a long post... (and please remember this is all subjective, and personal experiences, your's may be different!)
Preamble:
I've had my BA for a couple of months now, prior to that it has always been PalmO OS devices which I loved, but I wanted a phone enabled device and the Treo was just too expensive to justify it... so ebay beckoned and £100 later I was a proud owner of an O2 XDA IIs...
I'm a fairly heavy user of my PDA's I use them for all my network admin, work documentation, mail on the move, a heavily laden calendar and everything else a busy professional with a family does... with loads, and loads, of travel!!
First thoughts:
I was, to be honest, dreading the move to M$, I have always been a promoter of opensource, Palm, and anything other than the big M, but I was pleasantly surprised... with relativley little pain I got into the WM2003SE way of things, and after a quick read of the Wiki, I cooked my own ROM and had an O2 device which worked really well... I could use my BT headset as stereo headphones or a headset, while connecting to my GPS, I had my Gmail, O2, Hotmail and other accounts set up, I could chat with Skype, GoogleTalk, MSN and ICQ, I had a WiFi sniffer, and all the other trappings as well as a GPRS connection for TomTom Traffic etc... and the media capability was cool, TCPMP worked really well, and with a 1Gig SD card I could take a couple of movies/TV episodes for the journey... in short, I no longer had to worry about taking a laptop on the road.
But that wasn't enough, I was reading about these WM5 ROMS and felt that, after being pleasantly surprised with WM2003SE, it was worth a shot... over the last few days I have tried several ROM's and they all have up/down sides... what follows is a (not so brief) summary of my experiences...
I load up my BA fairly heavily, and I had specific requirements... speed, callerid, space, preferrably A2DP, and again, speed!!
TuMa 1.4 (MS BT Stack):
Some see this as the 'Daddy' of the WM5 ports and I must admit, with one major bugbear, this is an impressive ROM... it includes a lot of stuff in the build which some might prefer was left out, but for the basic user it's helpful to have some of these...
(A Really COOL Boot Logo!!)
TotalCommander
PocketRAR
Extra Games
Cyberon Voice Dialler
GB-Soft Tweak
vBar
pShutXP
IP Utilities
Pocket FTP
SMS Name Notify
ClearVue PDF
BT Headset Today Plugin
BT Stereo Control
Device Lock Today Plugin
and other bits and bobs...
This may well be considered as a 'bloated' ROM (but remember they are all installed in ROM, so no space is taken up from your 'own' space), there is an Ext_ROM option, from SD Card, in this ROM so the memory works out like this... 60MB Storage (- whatever you set up as an Ext_ROM) and 91MB Program Memory... you also get a 32MB Temp_Drive ( I assume this is like a RAMDISK?)... available on a clean install is:
Storage: 57.62MB
Program: 72.53MB
TEMP_Drive: 31.85MB
Total: 162MB (Storage & TEMP_Disk available for app install = 89.47MB)
Out of the Box:
BT: Works very well... including A2DP, I had no problems, whatsoever with this BT Stack/Setup.
WiFi: Again no problems and no reset once I'd applied the Reg Hack.
Base OS: This is where, for me, it all falls apart... even with eveything else working like a dream, the 'Pictures & Videos' app in this build just does not work, at all! This means that the CallerID functionality is kaput... I can't live with this, I love the ability to 'see' who is calling, I have many, many numbers in the work category, and being able to put a face to a number beats having only a name any day... other than that this ROM works really well, and the additional install space means I can have all my apps installed without the 'critical' low storage warning... in addition to this another glitch I have come across is 'sticky' buttons... both the D-Pad and the hardware keyboard can result in stuck keys/repeated entries... BT Voice Dialling works with Cyberon, and even better with MS Voice Command (if you hack a little), and with the A2DP profile the MS option works through the BT headset rather than the PDA speaker,,,
Ivan V4 R3 (WidComm BT Stack):
Built as a 'clean' ROM, this one really comes with no bells or whistles, included are:
BT Headset Today Plugin
Cyberon Voice Dialler (I Think!)
and apart from the Base OS stuff, that's about it!
This is a relatively speedy ROM on first impressions, but it slows dramatically down when loaded with apps... you can setup an Ext_ROM with this one, or use the full 60MB as storage... there is no Ramdisk or Temp_Drive option so you get 60MB Storage (- whatever you set up as an Ext_ROM) and 123MB Program Memory... available on a clean install is...
Storage: 57.64MB
Program: 98.40MB
Total: 156.04MB (Storage available for app install = 57.64MB)
Out of the box:
BT: works okay, although there is no A2DP functionality,but I can connect to my headset and my GPS... (which is a big thumbs-up for me). I have experienced a few of the system restarting glitches, but not the BT not restarting/dropping out with this ROM so that's an upside.
WiFi: Connectivity is okay (typical BA signal strength) and once you apply the 'ResetOnResume' Reg hack then it works very well, I have had no dropouts or non-restarts with it at all.
Base OS: A big upside for this is the Pictures & Video, it works! This means I can use the CallerID function on the WM5 dialler, which I do, extensively!!
Logout V5.4.03 (WidComm BT Stack):
Read great reviews of this on the forum, so thought I'd give it a bash... included are (if you install the Ext_ROM):
Cyberon Voice Dial
ResInfo
Task Manager
Device Lock Today Plugin
TuMa Keyboard (I think, although it looks nicer!)
Just installed this one today... first impressions weren't very good as many of the apps which were meant to be there couldn't be found on startup... then I realised I hadn't cleaned my Registry Hive before the Flash!! The speed in this one is blinding! Compared to both of the others this one is as fast as 2003SE, again, it uses a Ramdisk so you have added space for installs, and it can also use an Ext_ROM, so you have your choice... so you get 60MB Storage (- whatever you use for Ext_ROM), 93MB Program Memory and a 32MB Ramdisk... available on a clean(ish) install (I installed the MMS/Album/Voice Dial and Resinfo Cabs) is...
Storage: 52.8MB
Program: 71.9MB
RAMDISK: 31.8MB
Total: 156.6MB (Storage available for app install = 84.6MB)
Out of the Box:
BT: What there is available works fine... but no A2DP... not experienced any restart issues yet, but it's ealry days
WiFi: Again, all seems fine
Base OS: As stated above this one is blindingly fast... so much so that I actually forget it's a ported WM5 ROM at times, the Pictures & Videos app works, so that's a biggy on the plus side for me, everything seems to be ticking along quite sweetly...
UPDATE 1: Logout ROM seems to lag for a while after installs of S/W... but it settles down again, had one occurrence of s-s-s-stuttering keyboard, but nothing major, and no 3s delay on phone ring, even without reg hack
Artz (WM5_ArtZ_upgrade_WWE_1.7.1.3400_SDCard)
Iloved this ROM at first sight, it had the Stereo Audio BT profile without any updating, it was clean, smooth and fast, but then I tried using it... I'm not sure what went wrong but it just didn't 'gel':
BT: As stated this looked good from the outside, and it did recognise both my GPS and my headset, and it would connect with both, but, andit's a huge but! It wouldn't get any services from my headset on reconnection, it wouldn't recognise my headset as stereo (even though it though it would recognise the profile?) and as vor a 'normal' BT headset, it just sent my i.Tech headset haywire, beeping, pinging and ringing constantly... I couldn't stop it!
WiFi: Again, issues with this... no matter what I did, this ROM would not reconnect to my AP after a reset or power down...
Base OS: At face value this ROM was excellent, it had all I needed to start setting up my BA, and the option for Ext_ROM from an SD card is great... but with the issues above, and the spped at which it 'slowed down' with apps added it was unworkable
Obviously I will update each of these as I continue to 'tinker'... and wait for Logout 5.4.5 or TuMa 1.5, if either of these fix the little issues I've mentioned (A2DP for Logout and P&V for TuMa) then I'll be in BA WM5 Nirvana!
In summary, heres a little overview (TuMa, Ivan, Logout):
Speed: 3, 2, 1 (And then some!)
Apps: 1, 3, 2
A2DP: Y, N, N
P&V: N, Y, Y
Voice Dial: Y*, Y, Y
Available Mem: 162/89, 156/57, 156/84
*TuMa's is the only ROM I tested with MS Voice command, so BT Mic+PDA speaker for the other two, complete headset for TuMa.
So there you have it... a 'brief' insight into a few days of WM5 experience, personally I'm going to stay with Logout's ROM, the speed is unsurpassed, it has ample space for installs, I get my CallerID due to P&V working, and if there's one thing about TuMa's ROM I could do without it's the 'free' installed apps... I don't use TtlCmd, I don't use Pocket FTP and I don't use Pocket RAR (Resco Explorer covers those 3 and then some), I use Tweaks2k2 to apply most of my hacks, so the GB-Soft Tweak is mostly redundant, and I use Wisbar instead of vBar... but it's a personal preference thing... in the end, it's up to you... (I now use Total Commander loads Thx TuMa)
I'll update this as I try other ROM's or find other benefits/problems/fixes...
*** See my other post in this thread dated 23/06/06 for other issues which I have come across with WM5...***
Logout 5.4.05
I had high hopes for this ROM, 5.4.03 was nearly there, and built on the best of TuMa and Ivan's ROM's...
Out of the Box
An incredibly fast ROM, by far the fastest in basic form compared to all the others available... there are many little tweaks in the software and add-ons included as standard which are useful, such as the SMS Alert Fix etc. It's up to you to make the Ext_ROM, but this is good for 'tweakers' as you can build it to your liking.
BT: Basically, a nightmare! I believe this uses the WidComm stack and as such I can't get the A2DP to work, yes it recognises my Headset, and yes it says there is a 'Wireless Stereo' capability, but when you try to enable that profile it says 'No Device Found'... in addition, and I'm not sure if this is due to the BT switching off fix, my device was switching on at least once every two minutes!!
WiFi: I didn't get round to test this for the reason above, and also the power up issue causing me major headaches.
Issues: I had too many issues with this ROM to detail them all, a short list would be:
No A2DP
Random Power Ons
Software Not Installing Correctly
Software Not Removing Correctly
Software Not Running (Tweaks2K2, WiFiFoFum and others)
BT Dropping Out (While Powered Up)
OS Locks Out (Random, No Common Factor)
And the speed once a few 'heavy' apps are installed deteriorates dramatically...
I have now resorted to TuMa 1.4... I know I have stated previously that I couldn't use it, but I have found a workaround to the Caller ID issue, and the BT works very well (including A2DP), with both 1.13 and 1.15 Radio ROM's, and I have not experienced one unwanted power up, and the BT has stayed on for ages regardless, in addition as long as I don't install WisBar the speed of this ROM beats all the others hands down once all my other apps are loaded. Also, I have had the BA on for 7 hours now, using bluetooth for 1 hour solid in the gym for music, making several calls, setting up my software etc and the battery is still at 75%... not bad at all in my books.
As I said earlier, bring on TuMa 1.5!
Now this is useful! Thanks for sharing and I give my thumbs up for updating the first post as you go on trying.
I'm very happy to read your review.
I'm surprised you did not mention the battery drain (false indications that your battery is dead, when in fact it is not) with TuMa 1.4
Great Work!!!!
G8 work. Good detailed description which i am sure a lot of people will appreciate. i
Logout Rom = Speaker phone icon does not disappear after call
WMP 10 crackling noise for first 30 -60 sec of song
@snapper - Can't say I noticed it, but then again, whenever I sit down for more than 30mins, my brick goes on to power anyhow...
Why does everybody forget about ArtZ's ROM? :/
http://forum.xda-developers.com/viewtopic.php?t=48215
Not forgotten, just not used,,,
If you read the last couple of para's I do state that I'll get round to Artz's and update the post...
Yup, missed that (was in hurry, checked only the explicitly enumerated ROMs :| )
The Artz of ROM's
Hmm, d/l'ing this one now... expect an update over the next day ot two... encountered a few 'glitches' with the Logout ROM tday, nothing too major, but enough to get my goat!
Is there any reason why, with certain ROM's, certain apps decide my BA is a VGA device? This has cased me no end of trouble today, and I can't for the life of me, work out the reason...
Anyway, expecting good things from the Artz ROM, just read the forum a few mins ago and notice it's a 'clean' ROM with the BT stack! Could be I get my wishlist... let's just see if P&V works...
Mad props for a very well written article.
I've gone down the wm5 road the last week as well. I tried tuma 1.3, tuma 1.4, ivan, and now i'm on logout. I was wondering how extensively you tested the wifi? I have had problems with it on all the roms.
The issue happens when wifi is ON and the device shuts off after 1 minute. Then the device powers back up when i press the power button and the wifi will continually try to reconnect to the AP that it was just on but will never make a connection. Clearing the settings on the connection doesn't work and it inhibits the ability of the device to detect any new networks.
I was wondering if you had any problems like this and if resetonresume fixes this?
Also i'm a little confused about the location of the storage memory and the programs memory in the file structure of wm5. Could someone explain this or send me in the right direction? (aka. search terms or thread link)
willpower102 said:
Mad props for a very well written article.
I've gone down the wm5 road the last week as well. I tried tuma 1.3, tuma 1.4, ivan, and now i'm on logout. I was wondering how extensively you tested the wifi? I have had problems with it on all the roms.
The issue happens when wifi is ON and the device shuts off after 1 minute. Then the device powers back up when i press the power button and the wifi will continually try to reconnect to the AP that it was just on but will never make a connection. Clearing the settings on the connection doesn't work and it inhibits the ability of the device to detect any new networks.
I was wondering if you had any problems like this and if resetonresume fixes this?
Also i'm a little confused about the location of the storage memory and the programs memory in the file structure of wm5. Could someone explain this or send me in the right direction? (aka. search terms or thread link)
Click to expand...
Click to collapse
I had this problem on my BA with 03se just a couple days ago so I don't think its related to just 05. I used the vx ip utility to release and renew the IP and I believe that fixed it.. I think it has something to do with the DHCP reservation
Great guide, very handy for begginers. Should be sticked :idea:
willpower102 said:
Mad props for a very well written article.
I've gone down the wm5 road the last week as well. I tried tuma 1.3, tuma 1.4, ivan, and now i'm on logout. I was wondering how extensively you tested the wifi? I have had problems with it on all the roms.
Click to expand...
Click to collapse
Using wifi on my BA for over a wk everyday @ work & home, no such problems faced with Ivans ROM, have not tested logout, but will do that this wkend.
Guess its a hardware issue! again, thats just a guess
Yaantra
Great info!
This is great info and was very useful to me. I am on WM2003 and have not yet upgraded. With 2003, my only issues are that MS voice command won't work via the BT headset, the 80211b wireless requires a reboot to turn on and off, and the phone requires a reboot perhaps once a week. Otherwise it works well and I want my 2005 to be equal or better. I thin TuMA 1.5 will be it.
Has anyone actually got a working MMS Client primarily for Logout's new ROM
WiFi Issues...
@ will...
Yes, I noticed on first flashing that, even though I had entered the settings for my AP, when the system resumed then it would not reconect, after using the resetonresume reg hack all was well...
I also noticed this on Artz's ROM which I will be adding to my first post over the next day or two, as well as a few other points/comparisons...
All I will say at the moment is that all has not been a bed of roses in my WM5 world and backward steps may be ahead... (unless Logout 5.4.0.5 or TuMa 1.5 are here soon... and they deliver on our expectations!!)
Tuma / Logout roms
sounds to me that you will be heading back to wm2003. main reason for saying this is how you use your pda. Your demands are high (as they should be) and you use your pda very heavily (wifi, bluetooth etc) hence functionality and speed are your highest priorities.
having said all this i think and hope tuma/logouts new roms will hit the spot (i have faith).
FYI just upgraded to 1.15 radio and the sound quality is good!!!!!!
Issues, concerns and resolutions...
Well, the first post will be updated later today, but just as a heads up, I experienced BT issues with all ROM's except the TuMa 1.4, and various other 'niggles'... issues which I couldn't live with unfortunately:
BT: I like the A2DP functionality, I use GPS heavily and need them to work every time, with the other 3 ROM's I've tried I experienced various problems such as BT not reconnecting to paired devices, BT connecting but causing mayhem with my headset (in Artz' update later), crackly sound, dropouts, no phone, no voice dial, ad infinitum...
WiFi: This worked fairly well in all the ROMs, I managed to get all 4 tested to reconnect after standby/soft reset/battery change etc.
Battery: The experiences I had with battery life weren't actually that bad, yes it was heavier than 2003SE, but that's to be expected... my main issue was that on a couple of the ROM's I experienced the 'no Radio ROM' syndrome after a battery change, not major, but a pain in the butt anyway!
Usage: These are all ROM's that are designed for 'newer' machines at their hearts, and as such, as soon as you load up some heavy apps the whole system starts to drag, I cannot afford to wait over 1 minute for my PDA to boot after soft reset, or 30 secs for an app to open... and I certainly don't like it to be 'hit or miss' if an app opens when I ask it to!
Summary: I really love the WM5 interface, the smoother way that notifications are dealt with, the 'soft-menu' buttons are a godsend, the built in GPS management, and any of the other 'tweaks' MS have included make it a PDA users dream, unfortunately, at the moment it's just that, a dream... the BA is not 'Designed for Windows Mobile 5' and until TuMa, Logout, or Artz [I believe Ivan has left for a new device ] manage to get it 'right' (and major kudos to them all for their perseverence in what must be a most frustrating endeavour) I, as an everyday, heavy, PDA user will remain with WM2003SE... I'm not happy about it, but needs must
Re: Issues, concerns and resolutions...
spkr4thdd said:
Usage: These are all ROM's that are designed for 'newer' machines at their hearts
Click to expand...
Click to collapse
Just FYI that is incorrect, Artz and Ivan's ROMS are based on an actual BA BEAT build of WM5 that was made by microsoft, that has been patched and edited with later versions of the components, whereas TuMa and Logout's Rom are based on a Wizard ROM.
spkr4thdd said:
the BA is not 'Designed for Windows Mobile 5'
Click to expand...
Click to collapse
Read up, Basically every WM2003SE device has a WM5 Version made for it, however the operators in thier infinate wisdom decided that they didnt want people having WM5 on thier 'old' phones and would rather that people brought new ones.
Re: Issues, concerns and resolutions...
Midget_1990 said:
Just FYI that is incorrect, Artz and Ivan's ROMS are based on an actual BA BEAT build of WM5 that was made by microsoft, that has been patched and edited with later versions of the components, whereas TuMa and Logout's Rom are based on a Wizard ROM.
Click to expand...
Click to collapse
I stand corrected... I was under the impression that all the ROM's were 'ported' from different devices, I believe that was the case originally wasn't it?
Midget_1990 said:
Read up, Basically every WM2003SE device has a WM5 Version made for it, however the operators in thier infinate wisdom decided that they didnt want people having WM5 on thier 'old' phones and would rather that people brought new ones.
Click to expand...
Click to collapse
Read my post!! WM5 wasn't released when the BA came out, so it was built around WM2003SE, the fact that a ROM became available, albeit not publicly, doesn't mean they redesigned the handset!
I bought a Kaiser a few months ago, and I've been pretty disappointed to be honest.
I sold my old Mio A701 (WM5) which never gave me any problems... big mistake.
I have a few issues with the Kaiser, two of them are very frustrating.
1. During a call, the microphone volume drops completely so the caller cannot hear me... although I can hear them perfectly. Done numerous microphone tests with voice recorders etc and it only does it during a call. It's not a signal problem either, as I get a full signal in the office. HTC tell me they've come across this issue before, but they can't remember how to fix it. This is a £330 device, touted to be one of the best on the market... if this isn't resolved soon, the whole thing will end up on the front carpark in pieces.
2. Pairing with Parrot 3100 (running 4.16d) is completely unusable. I have complained to HTC & Parrot several times but I'm simply told to wait as they're doing everything they can to resolve the issue. Parrot are quick to tell you "we have a great relationship with HTC so it shouldn't be much longer" but it's been months!!! I'm not sure if it's a problem with the phone or the headset, but it's still not good enough.
Ghost calls (Parrot says "Call....." and takes control of the stereo (it's a Saab 9-3SS with ISO) but the phone isn't dialing anyone. I can only regain control of the stereo by stopping and removing the key... leaving the Parrot to ask "do you want to transfer the call to handset?" WHAT CALL?
Incoming/Outgoing calls sometimes aren't diverted through the Parrot.
3. WM6 seems considerably slower than WM5 for many common tasks. Is there any way to downgrade to WM5?
I've upgraded the firmware several times (now using Schaps) and it seems to be a bit quicker than before but it still suffers from the frustrating mic problem.
Any help would be much appreciated.
For me, the Kaiser is worth the money - I've been like a dog with 2 dicks since getting mine and apart from a few simple problems setting up TomTom I'm more than satisfied.
I was the same with my Wizards (Qtek and HTC) and Hermes (Vodafone). Maybe I'm more tolerant about problems, or more lucky not to get the rogue phones with hardware problems (software stuff can always be resolved) - but my experience of the HTC phones is that they're worth the £300+ upgrade every year.
That said, I haven't had my Kaiser too long yet so I may change my opinion.
I spent months and months researching my new purchase & I can tell you with 100% confidence that YES, IMO the Kaiser is worth the cost.
I chose to go with the HTC TyTN II over the Tilt because I just didn't want to deal with all the stuff AT&T did.
I knew about the driver issues, blue tooth issues etc etc etc and I am still convinced this is the best device for my needs.
It will only get better with time, and thanks to the tech geniuses that lead us in our quest here at XDA, I know many more great things are coming (and this is one of the reasons I donate to the community and support the driver Bounty ).
Nothing in this world is perfect & with that being said I have found that almost every issue has a good workaround. Sometimes that might mean using different hardware or software than we are accustomed to.
IMHO, even with the issues we face this is the best device out there and has so many possibilities for customization.
I love mine and have enjoyed learning about it and what I can do to improve the quality and efficiency of my life, even though i do get impatient
..................................
..................................
..................................
..................................
..................................
..................................
..................................
..................................
holding....
holding....
you write with brilliance
I'm happy somebody made this thread good work.
Fantastic Article Bengalih!
One added request. It would be great to include, perhaps in a text attachment, ms voice command's list of progam files and registry entries.
Seperate by the two primary versions for 1.6.
The information would invaluable for cooks to go back into a clean rom and clean out left over files and registry entries or allow them to strip the full version out if they wish to upgrade it or leave it out entirely.
Left over files/reg entries may as you know cause issues when adding or upgrading the ms voice.
Tayton said:
Fantastic Article Bengalih!
....
Click to expand...
Click to collapse
Added to guide.
List of File and Registry Entries for Voice Command
place holder
Cancel VC announcement while In progress?
Bengalih, Great write up!
Is there a way that you know of to cancel VC's announcement mid stream? That is to say, there are times when VC will start to announce an email, or read SMS while I am on a call and I would like a way to shut it up quickly. It is terrible when you are on the phone with client A and your phone starts to announce a call from client B, or even worse sitting quietly on a conference call and it starts reading an SMS... Some how this always bleeds through my BT headset so the person I am on the phone with hears it.
Thanks!
crussell
crussell said:
Bengalih, Great write up!
Is there a way that you know of to cancel VC's announcement mid stream? That is to say, there are times when VC will start to announce an email, or read SMS while I am on a call and I would like a way to shut it up quickly. It is terrible when you are on the phone with client A and your phone starts to announce a call from client B, or even worse sitting quietly on a conference call and it starts reading an SMS... Some how this always bleeds through my BT headset so the person I am on the phone with hears it.
Click to expand...
Click to collapse
crussell. Thanks for the vote of support. Unfortunately the issue you describe plagues me as well. I don't think there is anything wrong with the software and by this I mean it isn't a bug, just something the developers didn't think through very well.
There are only two ways to stop the incoming announcements:
Turn them off
Check the box in Notifications that says "Only during free time"
What this box means is that if you have an appointment in your calendar that sets your free/busy disposition to "busy" then announcements will not come through.
However, if you get an incoming call you will still get the call waiting beeps which can be just as distracting (if anyone knows how to turn these off please let me know...they are unrelated to MSVC).
So, if you know you are going to be on an important call you can first go into your calendar and make an appointment and set your time to busy.
The only solution I can see, short of a new version which takes these things into account is if someone can figure out how to fool the system into thinking your time is "busy". I don't know if MSVC looks for a registry flag or if there is a free/busy connector (API) that it taps into. If someone could make a little app that would toggle free/busy time that would be fantastic. Unfortunately I cannot code for WM to this degree.
AHA!
I take back what I said...at least the part of me not knowing how to fix it
There does indeed appear to be a registry location that records your current free/busy status.
I have written another script tool which will perform a toggle of your free/busy status effectively turning off any incoming announcements when toggled off.
Check it out here
ROM: 1.62.502.0 (ATT Tilt Shipped ROM)
MSVC Version: 1.6.17913
Bluetooth Headset: Motorola 89199N
Description:
Sorry if this is the wrong place to post this, but I've stopped using MSVC on my Tilt via Bluetooth because 3 of 3 times I've messed with this (getting battery status, call person, etc type commands) I've found later that the phone won't dial out or receive calls anymore! First two times it happened I was a bit puzzled, but the third time it clicked that it only happened sometime after initiating a call or such via MSVC with Bluetooth.
Anyone else noticed this? I find it odd that it'd freeze up the phone portion of the Tilt, but it does 100% of the time for me. IIRC, hitting the Green button shows the Phone titlebar and menus but the screen itself never draws. I can hit the OK button to get back to the Today screen, and the Phone app is listed in the list of applications running I believe, but it won't die and won't work until I do a reset.
I installed MSVC from a CAB here on this forum, and it generally works but this problem with bluetooth is pretty annoying as the main reason I wanted to get the program is to do bluetooth commands for dialing.
The more I think about it, it's possible that using the bluetooth commands then doing "run command suspend" (I think that's the syntax, it's been a few weeks since I tried it last) to turn off the Tilt immediately might also cause it problems. I was doing that because otherwise it stays on for quite a while, when it seems to me it should turn itself off fairly quickly.
I'll try your new version and edit-back
I have never experienced this issue with MSVC. I have tried it out successfully on at least half a dozen ROMS.
Although I am not intimately familiar with the inner working of code in either MSVC or WM in general, I don't know really know how this could interfere.
Other reported issues with MSVC involve:
Audio gateway being left open
Radio going dead
I'm also not sure how MSVC could interfere with the radio....
My first thought is Don't Blame MSVC!
I say this since I (and many other's) haven't had problems with it...it obviously is a program that CAN function properly.
If you are using a cooked ROM that has MSVC built-in or you are installing it from scratch, read through this whole guide and make sure you understand and update/tweak your copy.
I would recommend installing the latest version I have posted 1.6.19290 as I have already had reports of this clearing up some people's issue.
When posting problems regarding MSVC in the future, please refer to the main thread posts, where I will detail the information you should provide.
Let me know what you come up with!
I've got an issue I can't find an answer to. I have MSVC installed on my Tilt and it worked fine up until about a week ago. Since then I can initiate MSVC via my bluetooth headset but get no audio for the prompts (i.e. the ding to tell me it's ready for input, the audio confirmation for who to call).
Also, notifications stopped working via bluetooth. I've checked all the settings and everything is fine, they're exactly as they were when VC was working properly. I've tried uninstalling and reinstalling and deleting and repairing my headset. Nothing seems to work.
Any input on this would be greatly appreciated.
ok so i have a wizard.. a g3, and i've done it all now.. i've tried all the roms (amp, snn, hornet.. brushed)
and with each came it's flaws, whether it was battery consumption, irratic or unintended operation, or missed calls.
i finally settled on a rom (TNT something or other) that i liked, i liked the rainbow at the top giving battery status.. altho it began to chew the battery like a hungry dog on food scraps. and then i checked my voicemail, just arbitrarily.. EIGHT NEW MESSAGES. turns out the whole world was calling, and leaving voicemails, and i was completely unaware! (yet another rom busted)
i'm in the process (actually just finished) reflashin my original cingular rom back on the phone.. i have thrown in the towel.
so i have started this thread, to see, if one of the mega-brains around here has some ideas for me.
i read somewhere that changing radios might help.. but i don't understand why i have to change radios; this one worked before i started dickin with this phone!
so the question is: should i have gone forward with this radio changing, would it have really helped? or is every rom out there just too buggy to deal with? am i really better off attempting to cook my own, or should i just leave the whole damn thing alone and upload HTC home customizer and smartskey, like i had back in 2006..?
i mean i've lost everything at one point or another; stability went away with some roms (crashing everywhere), most every rom lost the MMS capability (could send, never receive), most every rom lost the ability to send an email from an SMS (Which was big for me, but i think it was related to wm6) now the rom i'm using (which is not the one in my signature) doesn't receive calls, missed calls, voicemails, and most text messages.
was all that i have learned on XDA a bust, or is there ONE MORE TWEAK that i needed to perform that would have made my phone... a phone again?
I would just keep looking until you find a rom that suits your needs.
I've used these two roms for some time and both work realy well with my G3 Wizard.
http://forum.xda-developers.com/showthread.php?t=345205&highlight=wm5se
http://forum.xda-developers.com/showthread.php?t=395173
The first if you like cube thingy, the second I use now because it is very very stable, good battery life 2-3 days of use and 5+ days on standby.
Never missed a call, loads of memory and storage I can not fault it at all.
P.s. my radio is 02.07.10
I'm with the original poster, I have a G3 wizard and almost ALWAYS miss phone calls, NEVER get informed of messages, and I can't justify the inability of the phone to work as a phone for the gadget end of the deal. I have the TNT WM 6.1 build 20273.1.3.3, Radio 2.71.11
OS 11.0.4.0
ipl\spl 2.26
I'm with the original poster, I have a G3 wizard and almost ALWAYS miss phone calls, NEVER get informed of messages, and I can't justify the inability of the phone to work as a phone for the gadget end of the deal. I have the TNT WM 6.1 build 20273.1.3.3, Radio 2.71.11
OS 11.0.4.0
ipl\spl 2.26
The general consensus here (this issue has been discussed over and over in this forum) is that radio 2.19.11 is the most stable, and should solve your missed calls/messages problem. It solved mine.
By all means, Cook your own ROM. It's the only way to get the ROM you want and it's not that hard. It only took me downloading and flashing 2 ROMs before I said "to heck with this I'm cooking my own".
so
you say if i were to have gone to the 2.19 radio i would have finally beeen happy? i mean missed MMS messaging and phone calls and voicemails and all?
what about decreased cell phone reception i have read about?
LIke little girls!!!!!
I Think, I saw, I read, PERFORM a HARD WORK AND DO IT THEN post your results!!! crappy thread.
bhhahahahaha
+que PPC:
i have followed this website for a year or two now, and despite having rarely posted any replies or any type of correspondance, i have noticed you tend to reply on most every thread, often with good info. i have also noticed, however, that most readers and junior/noobs take offense to what you say, but i have read so much of your work that i actually do not. i did just find your post to the first (and likely only) thread i've ever started to be terribly humorous! it is truely in line with a comment you might make. thanks for the help!
Hahahahaha
Wow i heard this too much too!
Hehehe maybe if you are a junior not a n00b understand the point!?
Why does the beginers here thinks this kind of sayings about me? cause they dont investigate and obviously becomes Lazy! thats why we are experimenting here lots of threads that dont has much sense why? cause dont search....
as you see it... im memeber since 2006 and im not a knowledge guy! BTW my work is too light for the development here if many people thinks this kind of toughts maybe they need to examinate again their questions.
I help to everybody but this kind of questions have made once...
Be cool men Why you dont join us since 2006or 7 and now 1 or two years ago you do it? heard about people is nothing fare of this site why?
cause there is no a way or a threat that allow to blame somebody imagine that the BLAME THREAD jajaja you have your OWN point of view cause you reed waht you wanted.
I had the same issues... missed calls, voicemail, text message alerts not appearing all due to one thing, wm6 and 6.1. One thing that helped me out was to have data connection (GPRS/EDGE) turn off automatically after a set ammount of time and BAM! no more missed calls. Advanced Config program will do it easily or GB-SOFT Tweak. Hope that helps! Also, 2.19.11 radio only helps a little also....
I had the same issues... missed calls, voicemail, text message alerts not appearing all due to one thing, wm6 and 6.1.
Click to expand...
Click to collapse
Talk about jumping to conclusions. I am using WM6 and since I loaded radio 2.19.11 I NEVER have missed calls or messages....
When I got my phone and it had WM5 it was the worst performing PocketPC I've ever had. Now, with WM6 it is the BEST performing PocketPC I've ever had.
joemanb said:
Talk about jumping to conclusions. I am using WM6 and since I loaded radio 2.19.11 I NEVER have missed calls or messages....
When I got my phone and it had WM5 it was the worst performing PocketPC I've ever had. Now, with WM6 it is the BEST performing PocketPC I've ever had.
Click to expand...
Click to collapse
YUP!
Same goes here for me too!
New Phone
Don't you just wish you had a new phone whenever you wanted? I do.
Every time I flash a new ROM (and I flash OFTEN) I get a brand new phone to play with. (I'm not an addict, I just do it because it's fun )
If I just wanted a phone that worked I could use any non-smart phone. They all have PIM's now and lots of them have QWERTY keyboards.
I agree that there does not seem to be any perfect ROMS and that statement includes the OEM's. A complex device makes it nearly impossible for everything to be perfect (just look at the desktop version of Windows!)
Sometimes I too get frustrated when I flash the latest and greatest and find out it's missing something I "need" and have to start the process all over.
But, when I can afford my new Fuze, I'll still be here screwing with it!
Just my 2 cents.
(Hi! I'm Rob and I'm a ROM flashing addict....)
joemanb said:
Talk about jumping to conclusions. I am using WM6 and since I loaded radio 2.19.11 I NEVER have missed calls or messages....
When I got my phone and it had WM5 it was the worst performing PocketPC I've ever had. Now, with WM6 it is the BEST performing PocketPC I've ever had.
Click to expand...
Click to collapse
Well....... I never had missed calls with wm5 but the os generally performed poorly so it's a matter of what you value more having missed calls or better os performance. No jumping to conclusions here. I have trouble shooted this issue for several months. And I'm not the only one one with missed calls while data connection is active. Do and search and see the countless threads on this repeated issue. Plus, it could be a provider related issue but seems to be with both at&t and tmobile us customers. Glad you don't have issues though...
yeah see
sino8r said:
Well....... I never had missed calls with wm5 but the os generally performed poorly so it's a matter of what you value more having missed calls or better os performance. No jumping to conclusions here. I have trouble shooted this issue for several months. And I'm not the only one one with missed calls while data connection is active. Do and search and see the countless threads on this repeated issue. Plus, it could be a provider related issue but seems to be with both at&t and tmobile us customers. Glad you don't have issues though...
Click to expand...
Click to collapse
i think you are right because.. there's something that is different from 5 to 6. for some reason my gay AT&T needs to switch data connections to do different things. like if you connect to ATT data to surf PIE lets say.. then you decide to send an MMS.. it will have to unconnect then reconnect..? and wm6.1 rarely decides to do that on it's own (like when someone sends you a picture message)
By blaming your problems on WM6, you're jumping to conclusions...You really don't know what's causing your problems. If it was WM6 then I'd be having problems too, but I'm not, so how could it be WM6?
I could say that it must be your connection settings that is causing you problems when ATT switches connections for an MMS, but then I'd be jumping to conclusions even though that's a more likely cause than WM6 having a blanket problem.