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 !
Greetings fearless leader. I cooked up a VZW ROM with 3.0.0 after taking the OEM from 2.3.1 over for the MMS and that worked fine, but I lost the Voice Recorder app that I do use a lot. It was in 2.3.1 although I did have to map it back to 'press and hold button 5' function, but it is totally gone from 3.0.0 . I looked for it in the 2.3.1 but thru my sleepiness or just blindness I just can not find it. Do you know where and what it is called so that I might get it back ??? I downloaded one for another model but it looks like it is working but no matter how long you let it record you get a 6b file that will not play, so i guess i need the right one, thanks.
Here's the OEM
View attachment 75350
gcincotta - is there a link to more OEM's that would be available for download?
Thanks for the help
if you are referring to the press+hold voice button app, i never used it and mistakenly thought it was another part of cyberon, so i removed the button mapping. it is fixed now in 3.0.1.
gcincotta - is there a link to more OEM's that would be available for download?
Thanks for the help
Click to expand...
Click to collapse
What OEM's do you need?
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.
So I just flashed my Cingular 8525 with Schaps_WM6Pro_WWE_3.54b-0804_Full and now I'm experiencing some issues.
Most importantly my keys dont work properly. When I press the alternate button (the little dot to pic alternate characters) I dont always get the right alternate character. For example if I try to use the question mark(?) I get the dash(-) instead. This is the case for several keys.
Secondly I'd like to know how to enable the GPS.
I tried to search for both questions, but GPS doesn't come up because it's too small to search, and I'm not sure if the alternate button is actually called the alternate button.
I really like this ROM so I want to keep it, so please help me solve these issues. The keyboard miscues are a much bigger issue than GPS.
Nomar1245 said:
So I just flashed my Cingular 8525 with Schaps_WM6Pro_WWE_3.54b-0804_Full and now I'm experiencing some issues.
Most importantly my keys dont work properly. When I press the alternate button (the little dot to pic alternate characters) I dont always get the right alternate character. For example if I try to use the question mark(?) I get the dash(-) instead. This is the case for several keys.
Secondly I'd like to know how to enable the GPS.
I tried to search for both questions, but GPS doesn't come up because it's too small to search, and I'm not sure if the alternate button is actually called the alternate button.
I really like this ROM so I want to keep it, so please help me solve these issues. The keyboard miscues are a much bigger issue than GPS.
Click to expand...
Click to collapse
You need to use advanced configuration and set the keyboard to Cingular.
There is NO GPS on a HERMES. There is a chip that is disabled and no one in over two years has found a way to activate it.
Though you can use a bluetooth reciever but you still need to purchase software & maps. I use Tomtom 7. Works great. Make sure you get a reciever with as many channels as possible. Mines 54, I had a16 channel reciever and found that it could take up to 10 minutes to actually get reception. 54 channel is under a minute.
Cheers...
thank you very much, but how would i go about "advanced configuration"?
Nomar1245 said:
thank you very much, but how would i go about "advanced configuration"?
Click to expand...
Click to collapse
Here:
http://www.touchxperience.com/en/ad...vanced-configuration-tool-33-cab-install.html
parleyp said:
Here:
http://www.touchxperience.com/en/ad...vanced-configuration-tool-33-cab-install.html
Click to expand...
Click to collapse
Good stuff thanks alot
parleyp said:
Here:
http://www.touchxperience.com/en/ad...vanced-configuration-tool-33-cab-install.html
Click to expand...
Click to collapse
thanks again
Nomar1245 said:
thanks again
Click to expand...
Click to collapse
Glad to help.
Massive thanks to jerpelea (wouldn't have gotten anywhere close without him).
I'm back! This new version is based on the fantastic Insomnia NIKI Kitchen, using WM6.5 Build 21500 and OEM Iolite/mishmash. As I made this version for my personal use, it is FULL of applications - if you don't like applications installed from the start, don't download it!
Warning: This ROM is for testing only and has been prepared by a complete cooking noob (me). I cannot guarantee any results for you or your phone and this may end up screwing things up COMPLETELY . Install at your own risk.
Having said that, it works very well on my NEON200 (Touch Dual 850), much better than any other ROM I have tried and even better than the old 6.1 version.
Make sure you have installed the Neon Hardspl (thanks Olipro) before you even remotely consider installing this.
Known Issues:
- DEVICE ID Reports as NIKI100 (I am still trying to figure out the XIP stuff)
- The camera hardware button does not work
- The camera autofocus doesn't work properly (messed up the some of the files I copied I think) so it takes a few seconds to shoot.
- Hardware keyboard doesn't work properly. It thinks that it is a 16key version.
Anyway, give it a go if you are game and let me know how it goes. It is a hundred times more finger friendly than the WM6.1 ROMs (which is the whole point of the touch phones).
I only do this in my *very* spare time, so I'm sorry in advance if I don't update often. I can say that I am very happy with the ROM as it is (never use the keyboard or camera), so it may be quite while before I update.
Download the new WM6.5 ROM here.
Old version (WM6.1 Build 21109) can be downloaded here if you want it for some reason.
Well done, looks nice. Everything works. Camera is good, text works, after calling t-mobile internet connects. Reception is fine, battery does not get hot. Although, instead of having a box with an x in the middle of it at far right corner, i have just an x. It takes a little more effort closing out of an application. Good job again.
ajb303 said:
Well done, looks nice. Everything works. Camera is good, text works, after calling t-mobile internet connects. Reception is fine, battery does not get hot. Although, instead of having a box with an x in the middle of it at far right corner, i have just an x. It takes a little more effort closing out of an application. Good job again.
Click to expand...
Click to collapse
Great stuff.
Are you having any other issues? Does the keyboard work 100%?
maximus007 said:
Great stuff.
Are you having any other issues? Does the keyboard work 100%?
Click to expand...
Click to collapse
I was just about to edit my post Keyboard does not work at any time. Also when recieving a voicemail, i tap and trys to connect. But says that phone call cannot be made at this time.
I've had no issues with voicemail...
Have you tried installing the latest Ezinput from the first post? Do you have 20-key device?
Perhapsthe Voicemailis something i need to set up with T-mobile.Yep, got the touch keyboard working with the install No keypad though.
Edit: Yes, camera button does not work.
I'm gonna load it up now and give it a shot.
I can't find the SIP task in task manager to kill it before installing the .cab.
Also can't get online because it is configured for Telestra (I imagine I can fix that easily). The "Setup Connection" app in settings closes immediately. That is how I used to setup my internet/phone provider stuffs.
Edits.
Ok...oddly enough after I updated my internet settings the 'task manager' and a few other apps showed up. That allowed me to kill the SIP and load the keyboard.
Overall this ROM is fast! Very happy with it so far. Can't wait till it is finished.
PS - I can't use my hardware keyboard either. Even with the SIP update. On screen works perfect.
I have NEON300 US version. If I decide to upgrade, can I reset back to factor default? Or is once upgrade, no turning back? I have Build 19209.1.0.2 version now on my phone.
mafirst said:
I have NEON300 US version. If I decide to upgrade, can I reset back to factor default? Or is once upgrade, no turning back? I have Build 19209.1.0.2 version now on my phone.
Click to expand...
Click to collapse
I haven't found a packaged default ROM. You might wanna see if he releases one once he gets this build worked out. I would love to get a copy of your default rom before you upgrade it. I think I lost mine 2 laptops ago. Once you load the HardSPL you can go back, however you need the default ROM to do so. There isn't a backup / restore utility as far as I know.
mafirst said:
I have NEON300 US version. If I decide to upgrade, can I reset back to factor default? Or is once upgrade, no turning back? I have Build 19209.1.0.2 version now on my phone.
Click to expand...
Click to collapse
wait! haha, before you do can you dump your stock rom? That would be very useful
I'm new to this site. How do I get my ROM backup?
mafirst said:
I'm new to this site. How do I get my ROM backup?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2254400&postcount=7
Let me know if you need help with this.
Voice Mail (T-Mobile)
I havn't been able to figure out how to change the voicemail number from the Telestra default, but if you dial "123" with a T-Mobile sim card, it will send you to your voicemail account. Just a little tip I thought might help.
big papa rich said:
I havn't been able to figure out how to change the voicemail number from the Telestra default, but if you dial "123" with a T-Mobile sim card, it will send you to your voicemail account. Just a little tip I thought might help.
Click to expand...
Click to collapse
Interesting, I didn't know that. I thought it was just an issue I had to call t-mobile about. Thanks
SMS
I have een having issues with SMS. When I try to send a text, I get an error message saying that my message can not be sent, that I need to subscribe to the service. I flashed back to Seths V2 rom and every thing worked fine. Any ideas?
BTW, don't know if any one needs it, but here is a cab that works great for reconfiguring internet stuff for T-Mobile or AT&T
I Just found this link. Says it is for the Neon 200 US, but my device still says 300. Any how, looks exactly like the Ship Rom as I remember it.
http://forum.xda-developers.com/showthread.php?t=395384
maximus007 said:
- DEVICE ID Reports as NIKI100 (I am still trying to figure out the XIP stuff)
Click to expand...
Click to collapse
You can change it by editing:
1) Modelname.txt in OEM/OperatorPkg
2) nbhgen.txt in Tools/Htools
I've Changed nbhgen.txt to NEON200 and a different version number, but when I flash it still says NIKI100 and the old version number. I have also changed the CID in OS.nb.payload, still no luck.
maximus007 said:
I've Changed nbhgen.txt to NEON200 and a different version number, but when I flash it still says NIKI100 and the old version number. I have also changed the CID in OS.nb.payload, still no luck.
Click to expand...
Click to collapse
Change the name in modelname.txt in oem/operatorpkg
Also change mixupdate_oemversion_100.provxml in same folder.
os.nb.payload content will get overwritten when the ROM is built.
Thanks for mixupdate_oemversion_100.provxml - that has the version info in it (also edited easily via registry). It was missing from my kitchen.
modelname.txt simply has "Touch Dual" (which is OK) in it. That file doesn't let me change NIKI100 to NEON200.
If you check my .nbh in a hex editor it displays "NEON200", yet upon flashing it still displays the device as NIKI100...