8125 QUESTION BT, AND ROM 2.24.10.1 - 8125, K-JAM, P4300, MDA Vario Software Upgrading

IS THERE A NON STERIO BT HEADSET THAT WILL WORK WITH THE VOICE ACTIVATION, LIKE THE 820 STERIO ONE DOES.
I AN RUNNING ROM 2.24.10.1
WORKS GOOD BUT DROPS CALLS HERE AND THERE.
WHAT DOES CLOCK 240, CLOCK 200, AND CLOCK252 DO, AND IS ALL YOU HAVE TO DO IS TAP AND HIT OK?

colorall said:
IS THERE A NON STERIO BT HEADSET THAT WILL WORK WITH THE VOICE ACTIVATION, LIKE THE 820 STERIO ONE DOES.
I AN RUNNING ROM 2.24.10.1
WORKS GOOD BUT DROPS CALLS HERE AND THERE.
WHAT DOES CLOCK 240, CLOCK 200, AND CLOCK252 DO, AND IS ALL YOU HAVE TO DO IS TAP AND HIT OK?
Click to expand...
Click to collapse
Wow, you and your stuck caps lock just don't give up do ya?
I figure we'll all see this same message from you for the next month if someone doesn't answer, so...
1 - most BT headsets work with voice dial, whether you mean MS Voice Command or one of the Cyberon variants.
2 - clock240, etc, are shortcuts to the OmapClock overclocking utility that set the CPU to the indicated speed. So, Clock240 sets the cpu at 240 Mhz, clock250 sets it to 250 Mhz, etc. There is no feedback - it just does it's work quietly. The CPU will revert to stock speed when the device is put in standby.
Do you by chance drink a lot of mountain dew?

bluetooth and active sync on this ROM
Any chance of getting steps to get BLUETOOTH SYNC with my windows XP?
I've had no success and it worked before ths latest ROM upgrade.
I must be doing something wrong.

Related

A *LONG* WM5 ROM summary for (relative) noobs like me :)

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!

if i am impatient, which is best

OK, I am in no way asking Tuatara to hurry (yes I am)
but I am using 1.3 since when I used 1.4, I had all those bugs.
My main frustration is that I can not get my bluetooth headset button to work with voice dialing.
So, in the mean time until Tuma 1.5 Alpha is out do I:
(1) go back to Tuma 1.4
(2) try a different ROM (perhaps IVAN)
(3) stay with TuMa 1.3
my main objective is to use Bluetooth headset (platronics discovery 640)
with some sort of voice dialer, and correct interaction with my holix bluetooth GPSlim 236
(obviously I want the phone to work, and GPRS connectivity)
thanks in advance for your opinions
Also, yes I know a similar poll exists here
http://forum.xda-developers.com/viewtopic.php?t=56003
I say take the oportunity to try them all. If you have editfix.bat ready to copy into the rom folder it takes all of 20 minutes to upgrade, sync and install all your programs.
Give logout's a shot, It's basically an updated tuma 1.4. Beware it's fairly heavy and sluggish. But coming from tuma 1.3 you might not mind as much.
Then stop off at Ivan w / ramdisk v1.11. It's amazingly fast compared to the others. I'm sure you'll enjoy it. The main quirk i have with it is that network computer browsing crashes it (for me at least) I can't speak for the Bluetooth because i don't use it.

T-Mobile Wing with MS Voice Command - Are you having problems too!

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.

MS Voice Command on the Fuze

HI all,
I have setup MS Voice command on my Fuze to announce the name or phone number of the person calling on in coming calls. On my Tilt, it would announce the name either thru the speaker or my BT headset. With the Fuze, it will not. Is anyone else having this problem.
Also, with my Tilt, my ring tones would play thru my BT Headset and it will not on the Fuze. I don't know if this are related. I am using the BT headset on both.
Thanks
billf.
Yes, I'm having this same problem, and it is making me consider returning my Fuze and sticking with my tilt. Unless HTC or someone comes up with a fix within the next 2 weeks, my Fuze is going back. The only other bug I have noticed is that auto-correct does NOT work for the keyboard. It's supposed to automatically add in apostrophes for words, such as "can't, don't, won't" etc. Also, the word suggestion never shows up when I type, like it did on my Tilt. Of course it gives you suggestions with T9 turned on, but that's not the same as word suggestion. It would provide suggestions based on previous typing habits, and even predict entire phrases it thought I was going to type. Anyway....if someone figures out how to fix these problems, please let me know ASAP! Thanks.
I just noticed this tread. I too am having the same problem with it not announcing. My Tilt did it just fine and I have the Fuze VC set up exactly the same way as my Tilt, but all I get is my ringtone and no announcement.
Check your settings. I think you have to announce notifications using bluetooth hands free if available. and uncheck "only durning free time"
I think that may work.
starstreak said:
Check your settings. I think you have to announce notifications using bluetooth hands free if available. and uncheck "only durning free time"
I think that may work.
Click to expand...
Click to collapse
That is the way I have it set up. No go. What is weird is that my ring tone plays over the bluetooth headset, but the computer generated voice doesn't speak.
it has to be a bad version or something.
also..last night i tried to install the cab i've used for over a year on top of the at&t version thinking it would overwrite the necessary files. no go. it corrupted the phone and had to hard reset to fix.
venelar said:
it has to be a bad version or something.
also..last night i tried to install the cab i've used for over a year on top of the at&t version thinking it would overwrite the necessary files. no go. it corrupted the phone and had to hard reset to fix.
Click to expand...
Click to collapse
I'm glad that you decided to be a "guinea pig!" Because I was going to try this today! I was going to re-install the .CAB that came from my Tilt. But I'm glad to see if that doesn't work. In order to find a solution, do you think I should call AT&T or HTC? Which one would give me the solution? Because I only have 25 days left before my Fuze is non-returnable.
Hmm I never tried it yet on the fuze with my BT. I'll try it and report back.
Ok crap. Yeah. It doesnt "voice" announce. I never noticed it because I can dial from headset and even number dial from headset and it'll work. I can hear it repeating the number back.
BUT its not like its not working... If I remove the announce incommming calls, it makes my phone ring, but in my earpiece I hear a tone to tell me I have a phonecall. When I enable announce incomming calls, my phone vibrates and I hear my ringtone in my ear, and faintly I can hear that "tone" I heard before. So it sounds like the voice side of things isnt working.
Ok tried one last thing before my BT headset died. Doh!
When it died, my phone announced the caller. So it does work. Its just not working from the BT headset, you hear a bell sound or something.
Also, I just noticed my cars BT doesn't show battery of the phone. When my Tilt was on the car BT, it would show the battery remaining.
MS Voice Command
Check out the MS Voice Command guide on WinMo-Experts. There might be an answer to your problems in there.
http://www.winmo-experts.com/viewtopic.php?f=11&t=2
Thanks for the link. I dont think it solved anything we're getting. Since Fuze has it built in, I dont think we can overwrite the files.
starstreak said:
Thanks for the link. I dont think it solved anything we're getting. Since Fuze has it built in, I dont think we can overwrite the files.
Click to expand...
Click to collapse
Guess I didn't notice, but dose not work for me either. I do enjoy that on the Tilt, but I more like the Tilt for the message and email voice notification.
Beahcboyde/JON
PS. I'm simply not keeping the Fuze. I'll stick with my Tilt and TF2. love the whole setup and the speed of the touchflo usingHyperDragon Raphael
Signal is average compaired to my Tilt, when testing out T-Mobile connection. On 3G, I'm constantly around 2 bars(but it spurts to full so I know its working) So I think Hawaii is still bad with 3G is some areas.
I use VC ALOT. So I'm amazed I never noticed this issue where it wont say the caller in my ear.
I'm not sure if I'll keep the phone/drop ATT/both.
Please someone fix this! I dunno if it helps, but all you hear is a bell sound in the background of your normal phone ringtone. I know thats from the MSVC. The only thing not working is the announcement of whos calling. I think everything else is working. I can voice dial,recieve calender announcements and appoinments,etc from my BT headset.
Oh, not just BT headset. It won't announce it from the phone either.
I even did a "bloat free" installation.
the fix is on pdaphonehome.com i had the same problem with my sprint touch pro. weird since the diamond doesn't have this problem. you have to edit the registry to use the wav file instead of the default. only side effect with the fix is the phone will ring once and VC will announce the rest of the duration.
sid
Eww,junk fix. I'll check it out tho. While not a problem when I have my headset, it would be if i had my phone sitting on a table.
Reg hack
I copied this from pdaphonehome.com....kuddos to the person that figured this
out. Kind of a hacky way to get it to work though. Perhaps the brains around
here can figure it out.
--------------------------------paste-------------------------------
This isn't a complete solution - but it's an improvement.
With this fix - the ring tone will play for a second and then be cut off by the call announcement. The announcement will be at a lower volume. The announcement will repeat - the ring tone will not be played again.
NOTE THAT YOU SHOULD ATTEMPT THIS FIX ONLY IF YOU ARE COMFORTABLE IN UPDATING YOUR REGISTRY.
Change the following registry keys:
HKCU\ControlPanel\Sounds\TTSAnnounce\Category
change from VoiceCommand1 to Ring
HKCU\ControlPanel\Sounds\TTSAnnounce\Script
change from as5p to v0p (that's v-zero-p) - for vibrate & ring, or p (ring only)
The above fix seems to get the announcements reliably, and doesn't break the set vibrate/set ringer features in the TF3D interface.
Hopefully we can find a better solution - that will restore the full functionality of Voice Command incoming call announcements - and not need this hack.
Another option is to manually overwrite the ringtone file name:
HKCU\ControlPanel\Sounds\RingTone0\Sound
change to \Application Data\Volatile\TTSCallerID.wav
This fix replaces the ringtone with the call announcement - and at full volume.
BUT this solution has several problems, including breaking the set vibrate/set ringer feature in TF3D.
From reading that, if I DON'T use the TF3D ring/vibrate, but use the windows mobile one, I should be fine by doing the second hack listed above? I think I could live with that as I eventually will kill the TF3D just so I can get the calender of my Pocket Informant to show instead. Only thing I like was the Weather and clock of the TF3D anyways and ATT crippled the clock by removing the animation.
Doe anybody know how to do the 2nd option? Not sure if I'm supposed to delete the whole registry line or somehow add to that line?

How to detect if my Kaiser has a cpu problem

Hi,
I try to use skype under WIFI/UMTS/HSDPA, but I hear one word on three/four...I thought it was a Windows Mobile Software block but it is not (http://forum.xda-developers.com/showthread.php?t=474370), I thought it was a carrier lock, but it is not. I tried a Toshiba g900 (wich is slower than Kaiser) with the same carrier and Skype works very very well, have you ever tried Skype with the Kaiser? I have the lastest Hyper Dragon ROM but it is not a ROM issue because it did not work even with its original rom and radio rom, this thing is driving me crazy! I made tests just after an hard reset and with wifi, so it is not a network issue but a device problem, how can I check if everything is ok? Maybe a benchmark to test CPU? Or what else?
I've never been able to run Skype smoothly on the Kaiser regardless of ROM. It's just too slow.
Not happening here. Running Skype 2.5 on WM 6.0 original ROM or WM 6.1 3.02 and it works fine. Just did a test call while connected to WiFi and the voice quality is great.
What's the difference between us? Different Kaiser Model? Wrong radio version? Wrong what? Why me and kilrah cannot use skype smoothly and vcespon can? Someone tells that his KAiser is fast in opening apps etc. but mine it is not fast even to open the start menu...I want to go deeper in this, what can I do to know if our Kaiser has some problems?
Mine is pretty fast doing everything, just skype will always skip very badly, regardless of version. It'll miss sound bits here and there, sometimes even blank completely for several seconds. That is, totally unusable except just for text chat.
vcespon said:
Not happening here. Running Skype 2.5 on WM 6.0 original ROM or WM 6.1 3.02 and it works fine. Just did a test call while connected to WiFi and the voice quality is great.
Click to expand...
Click to collapse
Could you say more? We must solve it
ROM and radio firmware version can make a lot of difference. WiFi performance / RAM available. After trying dozens of ROMs for months, I only use the original WM 6.0 with 1.27.15.32 radio, or the official 3.02 with 1.58.26.20.
WiFi connection works OK for me even in "best battery" setting. I've been streaming music from shoutcast.com for half an hour without problems.
Skype 2.5 does not seem to have any problem with a test call, I have not tested it on long conversations, thoug.
Hmm actually I forgot about that setting, with WiFi on "Best Performance" a test call works fine. I was usually on "Best Battery".
Just need not to be doing other things on the phone at the same time. Can forget about using BT headset as well.

Categories

Resources