Related
Hi everyone
does anyone know how to get TomTom Navigator 6 to run on the Lobster 700TV?
I have managed to get the application lock sorted now but not TT N6. I know that TT N6 lists in its code the phones that it will run on but the Monet is not one of them. I have used a hex editor to overwrite another HTC phone in the code in the hope that this may work. Although the phone now starts to run TT N6, it stops with the error: "not digitally signed ...". There must be something else that needs changing but I am not sure what.
Has anyone got any ideas?
Regards ...
I got it working, but it would not find the map, or should I say it crashed when it got to that stage.
TomTom MOBILE (v5.2) works fine
I know that this may not help, but I've got TomTom MOBILE (App Version 5.200 (4450)) working on the Lobster.
I think you've found out that version 6 does not work.
ringp3ace said:
I know that this may not help, but I've got TomTom MOBILE (App Version 5.200 (4450)) working on the Lobster.
I think you've found out that version 6 does not work.
Click to expand...
Click to collapse
Thanks for that.
It seems that TomTom Navigator 6 is a step backwards. I have had to do a lot of hacking with the software but without success so far although a breakthrough seems close.
Lobster 700TV
Hi ringp3ace
I have now tried TT Mobile 5.2 and yes, it works. I went on eBay and found this software for sale at £22 including PP. If anyone is intrested, there are 4 more left so be quick.
All the best,
Bluetooth GPS
Well, thanks to ringp3ace, I now have fully functional Tomtom Mobile working on my Lobster. Problem is, my bluetooth GPS device (GRB-288), wont play ball. I can pair and connect ok but there's no communication going on. I know there are some bluetooth devices that sulk when they are used with some phones but does anyone know which bluetooth GPS will work with the Lobster?
Regards
I'm having problems installing 5.20 on my Monet - using the download from the tomtom site it instals successfully up to the Jane voice then fails saying it isn't compatible with this device and backs out all the previous instals. Any ideas? I have a proper product key as I bought tomtom 6 for my pda and I can move tomtom 5 to the monet. Cheers
GPS Receiver
leadweight said:
Well, thanks to ringp3ace, I now have fully functional Tomtom Mobile working on my Lobster. Problem is, my bluetooth GPS device (GRB-288), wont play ball. I can pair and connect ok but there's no communication going on. I know there are some bluetooth devices that sulk when they are used with some phones but does anyone know which bluetooth GPS will work with the Lobster?
Regards
Click to expand...
Click to collapse
Leadweight,the Holox BT-321(Ebay)Works brilliant with my Lobster 700TV and TomTom 5.2
Sorry, finger trouble... now working fine using a Haicom HI-303III.
Many thanks to all!
Bluetooth GPS
prusling said:
Sorry, finger trouble... now working fine using a Haicom HI-303III.
Many thanks to all!
Click to expand...
Click to collapse
Thanks for your input but I have already found that the BT GPS 77 device also works well. I now have TT 5.2 running well on the Lobster.
Thanks to all those who helped to bring about this happy event.
Regards,
TomTom6 working (sort of)
I managed to install TomTom6 onto the Monet. It runs OK, but the lack of a touchscreen is the killler though - just too difficult to use without one.
Certain screens require the touch screen (setting up the GPS, selecting a postcode). The fakecursor/touch screen emulator is not an ideal solution either as I can't see how to assign the fakecursor program to a hardkey on the Monet.
I went back to 5.2 which runs fine. 5.0 doesn't as the screen goes garbled.
Can anyone help, I keep getting "set up is not a valid windows ce application" when trying to run tomtom mobile 5.2
hard to say without more info.
sounds like you are trying to run a .exe file on the monet that should really be run on the PC (if its the setup file)
The executable file that should be run on the monet is TomTom Mobile.exe
Can anyone help me,
when trying to install tomtom mobile 5.2 it freezes on the voice selection.
Anyone any ideas
Thanks in advance
ALi
alictait said:
Can anyone help me,
when trying to install tomtom mobile 5.2 it freezes on the voice selection.
Anyone any ideas
Thanks in advance
ALi
Click to expand...
Click to collapse
I have exactly the same problem - freezes on the voice selection. Thanks for any help. Love to get this working
Help with TT Navigator 5.2
To all those how are still trying to get Lobby to play with TT.
First, make sure your Lobster is 'application unlocked' (see start of this thread)
Next, ensure that you are trying to install version 5.2 of TT Navigator and that it is a Windows Mobile version (there are several versions). The Symbian version for some phones will load but not run.
Once loaded correctly, TT Navigator 5.2 will self install from the software loaded to the phone using the HOME application on your PC. This application will 'see' the connected Lobster and memory card.
I have spent hours trying to find the 'secret' and I can tell that it does work. If you read through this thread you will find others that have too.
If you still have problems, let me know
Regards
Thank you for the help Leadweight
When you say HOME application on the PC, what do you mean?
Many thanks again
Elbow
Thanks again Leadweight
Reading what you said and some of the other posts I now have it working on the Lobster - taken me hours but it is pretty impressive...
Cheers
Elbow
Well done
Elbow777 said:
Thanks again Leadweight
Reading what you said and some of the other posts I now have it working on the Lobster - taken me hours but it is pretty impressive...
Cheers
Elbow
Click to expand...
Click to collapse
Well done. Yes I was very pleased to get it up and running. Its very handy thing to have on a phone.
Regards
Elbow777 said:
I have exactly the same problem - freezes on the voice selection. Thanks for any help. Love to get this working
Click to expand...
Click to collapse
Needed to create a tomtom folder within my documents section of the phone and install the data.chk file.
Sorted !
I decided to open this new thread in order to spread this new updates amongst us. There are at least two of these roms working on our prophets.
The names:
Prophet_WM6_17944_TrueNeytral_1.6clean
KOSTER V3. Build 17944
More info here
HERE THE LINKS TO MOST OF THE ROMS
TRUENEYTRAL 1.1 http://www.savefile.com/files/586280
K0ster v2rapidshare.com/files/30153373/wm6wwerus17217v2.rarv
TRUENEYTRAL 1.2 clean http://www.savefile.com/files/689350
TRUENEYTRAL 1.3 (WIFI not working)
TRUENEYTRAL 1.4 widcomm bluetooth, camara 4... and other superb features...
TRUENEYTRAL 1.4 with MS Bluetooth Stack (instead of Widcomm) Not incl. camera 4. If you don't want russian keyboard to perform just follow DEVILDUCK's procedure here in post #180 THANKS!
SOLUTION for keyboard in latin font: ..##just for older ver. than 1.2##
Install wwe cab from post
Dialer in latin typo (see attac)
THANX 2 scooby1, trueneytral1983, nostramo, tiggerbcn and other fellas
Hello, I as you know also have the TrueNeytral and the charge of battery for usb me works perfectly and in the car also, in the PC it charge me between 210 - 280mA. The only problems are the Russian characters, for the rest it goes very thin. Greetings
Please post installation instructions/link to install info (Must downgrade? etc.)
Thanks, Eladio
To install TRUE follow normal procedure to WM6
That's:
-Downgrade to aku 2.20... If you previously had a WM6 or aku 3.3..
-Activesync 4.5
-Conect prophet via USB in normal status (not necessary to place it in -BOOTMENU)
-Execute upgrade utility (a .bat file)
-Wait no longer than 15'
-Dont touch anything, i recomend turning communications or phone off
-Anything happens in appearence but after pc message in MSDOS, hard reset -must be done.
-Now you are done.
It would be great if a russian speaker could give some info from 4pda.ru forums to change .dll in order to switch language typography in this rom.
Thx dudes
tiggerbcn said:
The only problems are the Russian characters, for the rest it goes very thin. Greetings
Click to expand...
Click to collapse
It's not a problem, it's a feature
cesardeluxe said:
-Wait no longer than 15'
Click to expand...
Click to collapse
Sure? Normally you schould wait 15-30 minutes till upgrade process is complete.
redandr said:
Sure? Normally you schould wait 15-30 minutes till upgrade process is complete.
Click to expand...
Click to collapse
This is the stimated time i have been experiencing, anyway is i wrote, and many others did... You should not unplug usb until system tells you to.
cheers
I've installed TrueNeytral a couple hours ago. Registry change of Keyboard is not working for me, but Resco Keyboard yes.
If i change registry of IR my Prophet restarts each time switch on . Original values are '15' (not '14' as you say).
Also some original ring tones (setup/personal/phone) are not recognized as valid wma files.
Eladio.Linares said:
one) are not recognized as valid wma files.
Click to expand...
Click to collapse
Check if they're called like filename .wma and remove the space.
redandr said:
Check if they're called like filename .wma and remove the space.
Click to expand...
Click to collapse
Thanks, it works.
Hi all.
I've been using TrueNeytral WM6 two days. Actually for me is the best WM6
implementation I've flased to my dear prophet. Things I've used:
-USB, Wallet and car charge, all work fine (car charger required software
reset with cable plugged to works).
-WiFi: I've wireless router to internet, with no problems starting/stopping WiFi.
Windows Live, Google Mail, everything OK. Configuration resists software
resets.
-GPRS: OK, corporate mail (Lotus Notes) working perfect.
-Bluetooth: Stereo Sony HBH DS970, handsfree Jabra bt-150, freedom bt
keyboard, parrot ck 3000, GPS Zaapa. Multiple connections (parrot & GPS)
work, tomtom returns after receiving a call (this is the first ROM to do this)
ActiveSync over BT to my desktop working also (TrueConnect over BT!)
-IR: NoviiRemote working with no tweaks. Changing registry as stated at top
of this thread for IR gets my prophet to shutoff completely when hibernate,
so i cannot use file and vcard transfers over IR, but I think this is a OBEX
problem, because IR port is working for NoviiRemote.
-I have no incompatibility at all. WisBar and SPB Backup is supposed to get
into trouble, but not for me.
-Finally, battery drain is correct. I've been monitoring two days, and
consumes 4-5% at night and 30-35% with normal use; checking once an
hour mail with GPRS and 30-40 min. call.
-Cannot map HW buttons 1 and 2.
It seems to be near RTM...
Thanks for posting this ROM, and of course to the author.
Eladio.
How did you get rid of the Russian characters?
floepie said:
How did you get rid of the Russian characters?
Click to expand...
Click to collapse
Setting Regional info (Spain) and installing Resco Keyboard... I'm not sure what you mean...
Hope this help.
Eladio
...from the 1st post here. Russian in keyboard, contacts, and dialer. So, just changing the region corrected that issue?
floepie said:
...from the 1st post here. Russian in keyboard, contacts, and dialer. So, just changing the region corrected that issue?
Click to expand...
Click to collapse
Ah!
Russian Keyb: Install Resco Keyboard and SPB Full Keyboard with dictionary completition. These are apps I use normally.
Contacts: Again Pocket Informant & Pocket Breeze, I don't use standard apps from M$. Pocket Informant traps links to std apps, so 'contacts' is hidden for me.
Dialer: I've installed cabinet from first post, but normally use voice command over bluetooth handsfree to dial.
I'm trying to isolate me from lang/reg issues. The cost is to have to install these apps...
I have come across with a post in a spanish forum where they got rid of russian characters. It has to do with a .dll. i think they succed. I will post the how to ASAP
This one also has the problem of turning itself on constantly with an Exchange account.
One more: cannot control volume of incoming call. It is set to maximum, and volume indicator seems to work but there is no real effect over volume.
Eladio.Linares said:
One more: cannot control volume of incoming call. It is set to maximum, and volume indicator seems to work but there is no real effect over volume.
Click to expand...
Click to collapse
Yeah! I've got the same problem... But this problem happened to all Crossbow ROM as i've been trying around many ROMs. Nothing can be solved... i guess.. it's bcoz incompatible sound driver...
cesardeluxe said:
I have come across with a post in a spanish forum where they got rid of russian characters. It has to do with a .dll. i think they succed. I will post the how to ASAP
Click to expand...
Click to collapse
Is there any news for the russian characters in keyboard & contacts?I'm with Prislav V3 now... Sound problems...
WLM not working (Device model name PM320)
No Windows Update
Anyone "in the know" on what is going on with Microsoft Voice Command?
For those not up to date heres the brief bio:
Microsoft released a rocking WM program that offers true voice recognition on pocketPCs and smartphones. If it didn't come with your carrier's build, it's a $40 upgrade, and well worth it. The latest version is 1.6. Unfortunately, it's been fraught with little issues, mostly related to Bluetooth headset compatibility, but most people still find it indispensable in spite of these challenges. I'm one of those people. The dial by number, and recognition of any name in the address book is invaluable to me, and a "must have" app for my 6800, no matter how badly it works.
The program is at version 1.6, and hasn't been updated in 2 years now.
What's the skinny?
jtg
I agree. I have had the same problems and have searched the net for any info about an update. Like you, I have not been able to find anything about a projected release of a new version. I guess that is just the microsoft way...only 2 years..
I heard a rumor that it was goint to be built into the next version of Windows mobile, but I hope that's not true.
If that happens, hoppefully it will be DCD to the rescue with a port for use all!!!
The real deal:
Ok, to those who haven't been following:
Microsoft DID update the VC software, but it was never released. It seems the Windows Mobile version went to the back burner since they made a deal with Ford Motors to start including the VC technology in the new Ford in-dash stereo systems (que up your mp3's, make calls via your bt phone, etc).
However, there was a test rom floating around for another WM device that had a greatly improved new VC version, which fixed 99% of the problems everyone was having.
This version was extracted and made available as an OEM to load into a kitchen to build into your ROMs.
There is NO .cab installation that I've seen for this version, so you're stuck with either cooking it in, or just replacing the files (there's a zip floating around here somewhere of the files u need to replace to make it the new version, but I don't recall where I saw it).
The OEM can be found in the excellent new PPCGeeks kitchen (ppckitchen.org), which incidentally supported Titan roms now.
For you DCD fans, it seems he hasn't made his rom compatible with the new kitchen GUI, but its relatively simple to make it a basekit. If enough of you push dcd, he might consider doing it... otherwise, you can always copy the OEM directory into DCD's kitchen OEMs.
Try Dutty's Voice Commander
This works for me, it is the best of both versions I have seen of the voice software. There are a couple versions out there, this is the most recent I have found. It is a cab.
I've got VC almost completely working. I cooked it into the DCD ROM. One reg key needs to be changed to get the button on your headset to work. The part I don't have working is the prompt and confirmation comming to the headset. The prompt and confirmation come out of the phone. It takes commands fine through the headset, just no audio until the call is started. Anyone know how to fix that? I'm using a Jawbone.
Dishe said:
Ok, to those who haven't been following:
Microsoft DID update the VC software, but it was never released. It seems the Windows Mobile version went to the back burner since they made a deal with Ford Motors to start including the VC technology in the new Ford in-dash stereo systems (que up your mp3's, make calls via your bt phone, etc).
However, there was a test rom floating around for another WM device that had a greatly improved new VC version, which fixed 99% of the problems everyone was having.
This version was extracted and made available as an OEM to load into a kitchen to build into your ROMs.
There is NO .cab installation that I've seen for this version, so you're stuck with either cooking it in, or just replacing the files (there's a zip floating around here somewhere of the files u need to replace to make it the new version, but I don't recall where I saw it).
The OEM can be found in the excellent new PPCGeeks kitchen (ppckitchen.org), which incidentally supported Titan roms now.
For you DCD fans, it seems he hasn't made his rom compatible with the new kitchen GUI, but its relatively simple to make it a basekit. If enough of you push dcd, he might consider doing it... otherwise, you can always copy the OEM directory into DCD's kitchen OEMs.
Click to expand...
Click to collapse
i prefer the functionality of dcd's kitchen over ppcgeeks.... except for the splash screen thing... but it's all opinion
serfboreds said:
This works for me, it is the best of both versions I have seen of the voice software. There are a couple versions out there, this is the most recent I have found. It is a cab.
Click to expand...
Click to collapse
Does this version require you to set tags for contacts?
Thanks
roninld said:
Does this version require you to set tags for contacts?
Click to expand...
Click to collapse
No, it doesn't require you to set tags, but provides that as an option. The tags are useful for frequently called numbers as they should reduce errors somewhat.
This version also works properly through my bluetooth headset including confirmations.
-dwdoc
ok, here is what I did to get it working with DCD:
1. Take the voice command folders from ppckitchen and put them in the OEM folder. There are two folders for the newest version
2. Cook your rom
3. Change the button assignment to VC if you want (settings -> buttons)
4. HKLM\Software\OEM\VoiceCommand change "path" to "\windows\voicecmd.exe"
5. HKLM\Software\Microsoft\Bluetooth\AudioGateway change "BTAGExtModule" to "vcbthag.dll"
Hope that helps you guys!
P.S. On the handset the initial voice prompt beep doesn't work.(the first time you press the button)NOT USING HEADSET
When you dial by the headset the little dial tones come out the handset.
This also lets the phone send ring tones to your headset when it is ringing.
Dishe--thanks for the tip, I googled and found a cab--I have voice command 1.6.17913, and it is a significant improvement over the one I purchased. I can now use my BT headset like I did with my old 6700!! Can anyone confirm this is the most recent build?
jtg
1.9.19209 is available as an OEM in the PPCGeeks Kitchen, but I don't know if there is a CAB of it anywhere.
JimSmith94 said:
1.9.19209 is available as an OEM in the PPCGeeks Kitchen, but I don't know if there is a CAB of it anywhere.
Click to expand...
Click to collapse
I just went through the Kitchen process described above and I get a version number of 1.6.19209. Perhaps just a typo?
whbell said:
I just went through the Kitchen process described above and I get a version number of 1.6.19209. Perhaps just a typo?
Click to expand...
Click to collapse
The Tip in option.xml for this version says, "Microsoft Voice Command - Latest version from kaiser". No2Chem shows as the author, so maybe he will chime in.
JimSmith94 said:
The Tip in option.xml for this version says, "Microsoft Voice Command - Latest version from kaiser". No2Chem shows as the author, so maybe he will chime in.
Click to expand...
Click to collapse
This is what I see also.
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="Microsoft Voice Command" group="Voice Control" checked="True">
<Tip>Microsoft Voice Command - Latest version from kaiser</Tip>
<Guid type="p">410788f1-acd5-457b-b9ea-df86ac7f990e</Guid>
<OEMDate>3/30/2008</OEMDate>
<AppVersion>1.6.19209</AppVersion>
<AppAuthorURL>http://www.microsoft.com/windowsmobile/</AppAuthorURL>
<ButtonType>GroupRadioNone</ButtonType>
<OEMAuthor>No2Chem</OEMAuthor>
<Require>93f31b6d-078b-4dae-a335-8ea8c3b22c97</Require>
</Item>
</Items>
I believe it was just a typo and he meant a newer build of 1.6. I have the 1.6.19209 installed from the kitchen and can not seem to get voice dialing to work when I dial by name though. It recognizes the command and will ask me if I want to dial work, home, cell, etc. However, when I confirm it never actually dials. It will work fine if I tell it to just dial a number though. Anyone else experiencing this and know of a fix?
djlenoir said:
I believe it was just a typo and he meant a newer build of 1.6. I have the 1.6.19209 installed from the kitchen and can not seem to get voice dialing to work when I dial by name though. It recognizes the command and will ask me if I want to dial work, home, cell, etc. However, when I confirm it never actually dials. It will work fine if I tell it to just dial a number though. Anyone else experiencing this and know of a fix?
Click to expand...
Click to collapse
There are 3 olders in the PPCKitchen. Voice Command 1.6 (which is the 1.6.17 version), VoiceCommand (version 1.6.19), and VoiceCommand_Lang_0409 (supports files for 1.6.19). I threw the VoiceCommand_Lang_0409 into the SYS folder in DCD kitchen, and VoiceCommand into the OEM. Cooked with no problems.
Have no issues with VC not dialing a contact.
roninld said:
There are 3 olders in the PPCKitchen. Voice Command 1.6 (which is the 1.6.17 version), VoiceCommand (version 1.6.19), and VoiceCommand_Lang_0409 (supports files for 1.6.19). I threw the VoiceCommand_Lang_0409 into the SYS folder in DCD kitchen, and VoiceCommand into the OEM. Cooked with no problems.
Have no issues with VC not dialing a contact.
Click to expand...
Click to collapse
Sorry, which kitchen? I can't find those files...
88fingerslukee said:
Sorry, which kitchen? I can't find those files...
Click to expand...
Click to collapse
After you install the ppcgeeks buildos and update, there is a kitchens folder. In there, PPCGeeks_OEM.rar has these folders.
.NET CF 3.5 is required.
UPDATE (3/29/10): Version 0.10 Released - See Post 77 for Change Log.
UPDATE (3/11/10): Version 0.9 Released - See Post 67 for Change Log.
UPDATE (3/8/10): Version 0.8 Released - See Post 63 for Change Log
UPDATE (3/3/10): Version 0.7 Released - Only changes are some registry settings that I missed earlier. With this, both Caller ID Announcements and Voice Dialing should work with this installer.
UPDATE (3/3/10): Version 0.5 Released - See Post 55 for Change Log - Device List below updated ... Updated v0.6 with auto start on device boot attached ... If you are using v0.5 (or v0.5_autostart which I screwed up ... sorry), uninstall it and install the v0.6.
Device List (Updated 3/8/10)
Known Working Devices
HTC Titan
HTC RhodiumW (Touch Pro 2)
HTC Rhodium (Tilt 2)
NOT Known Working Devices - If anyone uses a device listed here and my app, please let me know if it works.
HTC HD2 - I think this is similar to the TP2 - Should work, but I need someone to confirm this
Sony Ericsson XPERIA X1 - I have no idea ... Does this device use the WIDCOMM Bluetooth stack? Can someone test the latest app?
If you install this app, and have problems, uninstall msvcFix and install "revert_msvcFix.cab"
UPDATE (8/11/09): I have fixed the native app (now referred to as v0.3) and attached. I will leave the v0.1 attached as well.
UPDATE (8/10/09): Sorry, but there is something wrong in the native v0.2 ... I have posted the orig v0.1 in the mean time.
Not sure what devices this effects/fixes, but on my Titan, Voice Command incoming caller ID announcements don't work correctly. The work-around I use is ...
To enable caller ID announcements:
Set HKCU\ControlPanel\Sounds\TTSAnnounce\Category to "Ring"
Set HKCU\ControlPanel\Sounds\RingTone0\Category to "_Ring"
Set HKCU\ControlPanel\SoundsCategories\Ring\initVol to 15
To disable caller ID announcements:
Set HKCU\ControlPanel\Sounds\TTSAnnounce\Category to "_Ring"
Set HKCU\ControlPanel\Sounds\RingTone0\Category to "Ring"
Set HKCU\ControlPanel\SoundsCategories\Ring\initVol to 5
I have written a program to address these "fixes". My program checks the MSVC "Announce incoming caller ID" option, and checks to see if bluetooth is paired and headset service is active. If all these checks pass, I set the "enable" registry settings ... If not, set the "disable" registry settings.
Currently, the default interval is 5 seconds. I intend to make the interval a setting in the registry in the next version. Attached is a CAB install for version 0.3. The CAB will install the EXE to \Program Files\dj13241\ and create a shortcut in \Windows\Startup\ (it will auto-run on device boot). Version 0.1 was written in VB .Net, and took up to ~1.5 MB after running for some time. This version (v0.3) was written entirely in native C and compiled with cegcc-mingw32ce-gcc on Linux, and takes up 32 KB! Quite a memory improvement!
Feedback anyone?
Anyone have any feedback on this? Should I spend the time to improve it? Any feature requests? Anything?
Tilt2
Tried it on Tilt 2 and does not work. Caller ID still gets announced thru handset speaker
I am interested in your success...
186227 said:
Tried it on Tilt 2 and does not work. Caller ID still gets announced thru handset speaker
Click to expand...
Click to collapse
I think I know what the problem is ... I don't have my earpiece with me to test it though. Are you comfortable using a registry editor? If so, please post the values for the following keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]
"BTAGExtModule" =
"Capability" =
Also, please look in your \Windows\ directory for a file called "vcbthag.dll" ... You will have to check off 'Menu->Show all files' in order to see dll files.
Thank you for the constructive feedback!
howdykeith said:
I am interested in your success...
Click to expand...
Click to collapse
Good to know that someone is!
Do you use this on your phone?
I too, am interested in your success.
dj13241 said:
If so, please post the values for the following keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]
"BTAGExtModule" =
"Capability" =
Click to expand...
Click to collapse
Here are the values requested:
"BTAGExtModule" = BTRilProxyOEM.dll
"Capability" = 0x65 (101)
I am VERY interested in getting incoming caller ID to announce over BT on my Tilt 2. If you get this, you are officially the ruler of the universe!!!
I'm interested, will give it a try on my HD2
Hi and thanks for all the great info.Please forgive me (newby) to winmo,i installed ms voice commander and installe the Voice Command Announcement Fix and it still wont announnce the caller calling.Has anyone got any insight to the problem.
Thankyou
Sorry, not working on HD2 either
pity.. does not work on xperia x1 either..
I'm on it ...
I have a Touch Pro 2 and with some registry mods (quite a hack job at this point), I got it to the point of announcing Caller ID without playing a ringtone, but it announced from the phone's external speaker and my earpiece played its internal ringer. It looks to me like a timing issue ... VC creates a file \Application Data\Volitle\TTSCallerID.wav which is the caller ID announcement ... I think that the delay involved with creating that file is causing the issue, and by the time the file is created, my earpiece is already ringing with its ringtone.
On another note, my original program is (apparently) dependent on a different Bluetooth stack that the TP2 (which uses the wildcomm stack) ... If anyone knows how to check for a BT headset via native API, I would love to know!
I will be editing the first post when I have some time later tonight ... I will add "known working" and "known not working" phone lists ... Looks like the "not working" list will be longer for now
Thanks for all the feedback so far.
The Tilt 2 also uses the Widcomm BT stack. We've been blaming everything on the Widcomm stack, but I've begun to suspect that the aging MSVC software is really more to blame as it doesn't know how to play nice with newer software. Of course, I remember all of us soundly denouncing MSVC a few years ago about not being very compatible with the MS BT stack either!
I think you are definitely on to something. Yes, the hacks you have may be a bit kludgy but accurate. A suggestion: forget the checks to see if BT enable or not for the time being; leave BT enabled and do all reg changes, etc with the assumption that BT is enabled and connected. Forgive me if that sounds condescending -- I lost all my programming skills about the time Turbo Pascal died, if anyone here even remembers that from the early 80s -- but sometimes an outside view can make a small difference.
Always willing to try any hacks you suggest to see how they work on my stock Tilt 2; feel free to PM fi there's anything I can do to help.
Hi,
I have a TP2 with Stock ROM and have no problems with announcing phone calls, but..
You may already know about the bug when an "unknown caller" calls. VC does three things choosing randomly:
- 1. Does not announce anything, phone does not ring
- 2. does not anonunce anything, phone rings for a sec.
- 3. does announce the LAST CALLER - and this is really annoying, when you think you have a call from a friend or something, and it turns out VC just scammed you badly.
So my question is can you fix at least the 3rd behavior?
mydexterid said:
Hi,
I have a TP2 with Stock ROM and have no problems with announcing phone calls, but..
QUOTE]
So your TP2 announces your incoming caller ID over your BT headset? Really?
Click to expand...
Click to collapse
jlmwrite said:
mydexterid said:
Hi,
I have a TP2 with Stock ROM and have no problems with announcing phone calls, but..
QUOTE]
So your TP2 announces your incoming caller ID over your BT headset? Really?
Click to expand...
Click to collapse
I have a wired headset.
Is this thread only about the BT headset bug? Then the title should be modified. It is not really clear from the title/1st post that what announcement fix is this.
Click to expand...
Click to collapse
mydexterid said:
I have a wired headset.
Is this thread only about the BT headset bug? Then the title should be modified. It is not really clear from the title/1st post that what announcement fix is this.
Click to expand...
Click to collapse
Its good to know this info though ... Do you have a BT headset you could try it with? Has anyone else tried with a stock ROM, or is everyone using custom ROMs?
I'm going to dump the stock ROM registry and compare it to what I am running (which is a ROM built from Calkulin's 1.5 Beta Kitchen with a few of my own MODs).
Nope. The device itself gives me enough radiation I don't need more from a bluetooth device
dj13241 said:
Its good to know this info though ... Do you have a BT headset you could try it with? Has anyone else tried with a stock ROM, or is everyone using custom ROMs?
I'm going to dump the stock ROM registry and compare it to what I am running (which is a ROM built from Calkulin's 1.5 Beta Kitchen with a few of my own MODs).
Click to expand...
Click to collapse
For inspiration on MSVC you could also read my thread
My old Nokia N95 had a feature that announced via the speaker the name of the person making an incoming call (provided name was in contacts). It was not brilliant and it had difficulty with some names (my friend doug sounded more like dog). However it was a good method of screening calls remotely especially if you are on the top a a ladder! Is this feature available on my HTC HD2 (virgin mobile) ?
New to XDA apologies if this has already been covered
I am sure MS Voice command will do that. You can download the cab from here http://www.energyroms.com/Addons/
ms voice command
Thanks R12srw - does ms vc work out of the box or are there still bugs with it?
jeeem said:
Thanks R12srw - does ms vc work out of the box or are there still bugs with it?
Click to expand...
Click to collapse
jeeem, you will be disappointed to note that there are still bugs reported with MSVC, however you can be glad that it will be announcing the respective incoming caller's names / numbers.
If you havn't installed the .cab yet please note 2 things:
First: during installation, you will be prompted (and WARNED!!!) to install the MSVC on your device instead of the storage card. It actually doesn't matter even if you install it on your storage card instead of device, so install it at your desired location. (I prefer to install it on the card as I am extremely miser to save every bit possible, on the device!!!).
Second: After the installtion, you will be prompted with a WARNING saying the installation was UNsuccessful. This is BUG!!!. Ignore it. Restart and enjoy...
Ravindra9 said:
jeeem, you will be disappointed to note that there are still bugs reported with MSVC, however you can be glad that it will be announcing the respective incoming caller's names / numbers.
If you havn't installed the .cab yet please note 2 things:
First: during installation, you will be prompted (and WARNED!!!) to install the MSVC on your device instead of the storage card. It actually doesn't matter even if you install it on your storage card instead of device, so install it at your desired location. (I prefer to install it on the card as I am extremely miser to save every bit possible, on the device!!!).
Second: After the installtion, you will be prompted with a WARNING saying the installation was UNsuccessful. This is BUG!!!. Ignore it. Restart and enjoy...
Click to expand...
Click to collapse
i installed but cant seem to get it to work.
jeeem said:
My old Nokia N95 had a feature that announced via the speaker the name of the person making an incoming call (provided name was in contacts). It was not brilliant and it had difficulty with some names (my friend doug sounded more like dog). However it was a good method of screening calls remotely especially if you are on the top a a ladder! Is this feature available on my HTC HD2 (virgin mobile) ?
New to XDA apologies if this has already been covered
Click to expand...
Click to collapse
couldn't you just make ringtones of their names with a recording software and then assign that ringtone to the appropriate contact?
when i recieve a call it dosent say the callers name any idea how to fix this.
however the calendar and statues works fine.
adamo86 said:
when i recieve a call it dosent say the callers name any idea how to fix this.
however the calendar and statues works fine.
Click to expand...
Click to collapse
Hi Adamo86,
Did you ever get MSVC to work?
Jeeem
jeeem said:
Hi Adamo86,
Did you ever get MSVC to work?
Jeeem
Click to expand...
Click to collapse
Jeeem, MSVC does work, and as I mentioned in my last post to you, you have to install in accordingly. However as you mentioned in your reply, it seems you are not able to get it done, which to me it appears you might not be having teh APPROPRIATE VERSION or the correct .CAB file. Should you wish, I can mail the correct working cab on your email.