yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Themes and Apps] Fury22:
Vlingo on TP2

This app rocks with the exception of when sending a txt message via Vlingo the sent message does not appear in the TF3D messaging area like typed messages do, it however does appear under the TF3D text tab in the contact I sent the message to. I am running VZW TP2 stock WM6.1 rom. Anyone know how to get messages sent with Vlingo to appear in the threaded general text area?
[Touch Pro, Fuze Themes and Apps] ghoch:
I've got same error.
[Touch Pro, Fuze Themes and Apps] pepsi29:
Samsung Omnia

Just clicking on the "vlingo" icon in the programs list doesn't do anything. I had to install it on to the device itself (not storage), after installation you have to use file explorer, click vlmanager for setup. Set button, done.

Nice program. Thanks for all the info!
[Touch Pro, Fuze Themes and Apps] strickzilla:
anyone tried it on the HD2?
[Touch Pro, Fuze Themes and Apps] BlindDude:
Cant get it going on my Alltel CDMA Touch Pro with Twisted/Accessing rom v1.1.

It installs but when going through set up to pick a button, I follow instructions and go to my buttons screen and assign vlingo to my send(hold) key and then click ok, but then vlingo pops up saying "Key not set up, the button ??? is not assigned to vlingo. Click try again and follow the instructions to assign the button ???"

Dammit.

Lol

Any other software that is capable of dictating sms?

Thanks
[Touch Pro, Fuze Themes and Apps] wolvmarine:
Works on Rhodium/Tilt2

It works like a charm on my Tilt2 OEM ROM. I was only able to install it from my gmail sent to my phone and then opened from there for some reason. When I downloaded and tried that way it didn't want to work. Had it installed on device not Storage and now works. I can get it to search but still working out it's full spectrum of its abilities
[Touch Pro, Fuze Themes and Apps] all-in:
hi,i have the touch pro raphael with exquisite rom 4.14e.when vlingo asks for button assign and takes me to settings i assign in button 1-->vlingo but it doesn't save the option.it keeps saying in button 1-->action screen.Some help please...!!!! :)
[Touch Pro, Fuze Themes and Apps] elektrik2001:
Same problem here :(

Edit: email notification
[Touch Pro, Fuze Themes and Apps] thebritons:
Ditto.

I tried installing a seperate button/keyboard mapper and thats done nothing given that the vlingo-program forces you to use the crippled windows version.
[Touch Pro, Fuze Themes and Apps] randommoocow:
Think you could make a fixed cab for nontouch devices?
[Touch Pro, Fuze Themes and Apps] santoshtherock:
it is not working on LG INCITE :(

please give me the File which is compatable with LG INCITE
[Touch Pro, Fuze Themes and Apps] hereticous:
Is there a way i could use programs such as vlingo or tellme without using data connection? I just want to be able to text with my voice, but i get charged when using data connection.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] paalkr:
Hi!

Would it be possible to use a localized version of the EzInput 2.0 in a WWE ROM, either by installing some cab file to a WWE ROM or cook a custom WWE ROM with the EzInout files from for example the Norwegian ROM?

Even though I have a Norwegian branded device I would actually prefer a WWE ROM (the Norwegian translation isn't very good), but I need support for Norwegian xT9 and keyboard layout.

Regards,

PK
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] bram_smulders:
Hey paalkr, do you have a regeditor on your topaz?

Then you can dump the registry under HKLM/Software/HTC/EZinput/ to a .reg file.

And then if you've flashed a wwe rom, you can import that regfile and softreset. Then you;ll have a norwegian t9 on your device.

Gr. Bram
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] paalkr:
Hi!

Thanks, I have dumped the reg already and uploaded the .reg file in this post, but I have not have any chance to try it out yet on a WWE ROM, because of the not yet released HSPL (but that seems to be solved anytime soon now).

Regards,

PK
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] CerB:
did you get it to work ? i am trying to make the same with danish :-D
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] elmalote:
I think you have to dump the contents of HKLM\Software\Tegic
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] OCedHrt:
Does this work for all inputs?
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] speakerphone:
mine doesn't even have HKLM/Software/HTC/EZinput
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] .ViX.:
Edit 0C09.xml and 0D09.xml as you wish.

You only need charmap and notepad.

I made a finnish layout so theres no all norwegian letters, but at least it's a start...

(works at least in ezinput that comes with topaz 2.53 (2_1_19223325_00) and leo 2.10 (2_1_20113225_00))

Somewhere there was swedish layout with direct buttons to öäå, but i didn't like it so made my own...
[Touch HD Themes and Apps] mantrajt:
Hi:

Is there any CAB that allow us to recover circular zoom?

I think this was a very interesting, original and distinctive feature of our phones.(unlike Iphone) Way much better for our 5mpx camera.

Waiting for your help.
[Touch HD Themes and Apps] erdemdengel:
I need this cab file too

Does anyone have this?
[Touch Diamond, MDA Compact IV General] gangstar:
hello.....my diamond touchscreen is broken and i want to send it to warranty but i have updated my firmware version to 2.04.xxx from 1.34 and i have hardspl 1.34 or something installed......

what do i have to do before sending it to warranty?

instal sspl and that's it? or i have to install 1.34 firmware also?

it was bought from vodafone romania and it's network locked(i have;t unlocked it).

please advise me not to have problems with warranty!
[8525, TyTN, MDA Vario II, JasJam General] superultra:
This seems like a fair price to me. Is it? What hardware issues should I be looking for, common wear/tear's etc?

Thanks guys! This will be a nice (slightly heavier) upgrade from my Blackjack2 and 2125.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
There's quite a list of things to look out for. Be aware that there are quite a few being dumped on the net because of pretty serious issues. Having said that, there are good ones around.

You should not buy one that:

1

has ever had a white screen or fading screen problem

2

Shows a "No GSM" error

3

has a screen alignment issue (even a minor one)

4

has a slide out keyboard so loose that holding it up to your ear makes it slide out a little (this fault is fixable - but not entirely straightforward)

5

switches completely off from time to time (may be a minor battery contacts fault, but can be cracked solder joints on the battery connector.)

6

has ever suffered from applications closing for no reason or the start menu opening for no reason. (can be a sign of alignment issues or contamination under the screen bezel)

7

ever had charging problems or other issues with the USB socket. This can be replaced but the cost is probably not worth it unless it's DIY

8

a loose stylus is a hassle. Some are so loose they just fall out. I have instructions to fix this but easier to avoid the issue.

Im sure other folk can think of a few other things.

It may be worth buying one that is cheap if the rear speaker or front speaker is not working. The rear speaker is of just a loose connector and is just under the rear casing. The front earpiece speaker can be faulty due to loose spring connector (fixable, but a major dismantle - it can be replaced if necessary with a relatively cheap motorola alternative)

Mike

PS I am not up on current prices. Just the other day someone got one at $120 which was not thought to be a bargain. However with the Hermes, I'd rather pay a few more dollars for one that works ok rather than one that has one of those white screen or alignment problems.
[8525, TyTN, MDA Vario II, JasJam General] superultra:
That is a great answer. Thanks very much Mike. I'll post here how it turns out.
[8525, TyTN, MDA Vario II, JasJam General] dezaras6:
thats where i found mine, turned out great. this may not seem like the obvious , but one of the main reasons i like craigslist purchases is that they are usually meet face to face affairs. people that are going to scam you by selling you junk are less likely to do so face to face, at least thats been my experience. I think thats price is fair if its in halfway decent shape.
[8525, TyTN, MDA Vario II, JasJam General] galaxys:
go for it, not a bad price if specs check out like Mike said...
[8525, TyTN, MDA Vario II, JasJam General] superultra:
Picked it up, checked for all issues and asked some questions. Seller was mostly tech-illiterate but I dropped her down to $80.

Thanks so much for the advice all. I'll off to upgrade this puppy!
[8525, TyTN, MDA Vario II, JasJam General] galaxys:
Excellent! Happy Flashing :)
[Palm Treo 750 ROM Development] shaunehannen:
Maybe I'm posting this in the wrong place but I don't really know, I'm not good at navigating forums. the problem is, a while back I bought a palm treo 750 off ebay with mobile 6.0 or 6.1 I don't really remember but it had Palms messaging app standard. I love this app but the thing is, the app is sending repeats of the same message to the recipient. I thought it may have been the phone so I sold it to my bud and bought another Palm Treo 750 this time with windows mobile 5.0. it also comes palms messaging app. once again, it is still sending multiple texts to the same recipient. what little information I foun about this on the internet came up with this theory: after sending an sms, I may be closing the application before it can "save/remember/register" that the message had been sent. then when I open the app back up, it thinks it has an unsent sms and resends it. This is my main problem. any information or even a solution would be FANTASTIC. Also I was wondering how to change palms mms settings from 300k to 600k(palms messaging app, NOT ARCSOFT!!). please email any information to me at shaunehannen2009@yahoo.com because I'm not very good at working forums. thanks ahead for any help!
[Touch HD Windows Mobile ROM Development] Digital Outcast:
First of all you will need to download the drivers attached in this post and extract them. Remember where you extract them to!

The main reason for updating these drivers is so that you can use USPL or MTTY. USPL is an alternative to HSPL and is used for flashing roms. MTTY is used for retrieving information from the HTC bootloader as well as setting certain things. One of the more popular uses for MTTY is to clear the rom update error code in the bootloader after a failed flash.

The drivers that come with Windows for the HTC Bootloader are incompatible with USPL and MTTY. Once you update the driver with this guide you will be able to use USPL and MTTY.

Now that you have the drivers downloaded and extracted you need to know which version of Windows you have.

If you have Windows XP go to post 2

If you have Windows Vista or Windows 7 go to post 3

MOD EDIT

If you have previously updated drivers and successfully flashed a rom before you do not need to update drivers again. If 'usb' is not displayed at bottom of bootloader when connected to pc, simply reboot, press F8-key & select option to ignore the signature. Phone should now state 'usb' in bootloader to enable you to flash rom
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Windows XP

Use this method only if you have Windows XP!

Before you start this, put your phone into its bootloader and plug it into your computer via the USB cable. Your phone should show USB at the bottom of the bootloader screen. It is very important not to skip this!

If you have ActiveSync installed, start at step WXP1. Otherwise skip to step WXP4

.

WXP1 - Downloads

(WXP1a) Drivers.zip

(WXP1b) Extract each item to its own folder

WXP2 - Open

ActiveSync

and click

File

,

Connection Settings

.

WXP3 - Uncheck

Allow USB connections

and click

OK

and then close

ActiveSync

.

WXP4 - Press

Start

menu,

Run

, type in

devmgmt.msc

, and press

OK

. Or you can press and hold the

Windows and R keys

. This also brings up the

Run

dialog.

WXP5 - In the

Device Manager

locate

Windows CE USB Devices

and expand it.

Double-click

on

HTC USB Sync

.

WXP6 - In the

HTC USB Sync Properties

click the

Driver

tab and then

Update Driver

.

WXP7 - In the

Hardware Update Wizard

, click the

No, not this time

radio button and then click

Next

.

WXP8 - Continuing in the

Hardware Update Wizard

, click the

Install from a list or specific location

radio button and then click

Next

.

WXP9 - Continuing in the

Hardware Update Wizard

, click the

Don't search. I will choose the driver to install

radio button and then click

Next

.

WXP10 - Continuing in the

Hardware Update Wizard

, click the

Have Disk

button.

WXP11 - In the

Install From Disk

dialog, click the

Browse

button.

WXP12 - In the

Locate File

dialog, browse to where you downloaded the driver. Select the

32-bit

folder if you use the 32-bit edition of Windows, or select the

64-bit

folder if you use the 64-bit edition. Select

wceusbsh.inf

and click the

Open

button.

WXP13 - Back in the

Hardware Update Wizard

, select the

HTC USB Sync

and click

Next

.

WXP14 - Continuing in the

Hardware Update Wizard

, you will see an error:

This device cannot start. (Code 10)

This is totally normal, do not worry. Click

Finish

.

WXP15 - The

Device Manager

will show an exclamation point next to the

HTC USB Sync

.

Unplug the USB cable from your phone

. You will notice the bootloader on your phone change from

USB

to

Serial

.

WXP16 - The

Device Manager

will no longer show the

HTC USB Sync

.

Plug the USB cable back in to your phone

. You will notice the bootloader on your phone change from

Serial

to

USB

. The

Device Manager

will now show the

HTC USB Sync

as fully functional. You are done!
[Touch HD Windows Mobile ROM Development] Kristaps-K9-Lv:
A big noobish question: what are these drivers meant for?? what are the benefits of installing them?? :D
[Touch HD Windows Mobile ROM Development] johnpatcher:
Also interested in this one. Haven't heard of them so far :D?
[Touch HD Windows Mobile ROM Development] Digital Outcast:
If you want to use USPL or MTTY.
[Touch HD Windows Mobile ROM Development] imatrix:
excellent tutorial cRaCKwHoRe. that would save lots of time to answer same questions over and over again.
[Touch HD Windows Mobile ROM Development] coolfire:
cRaCKwHoRe, you are such a wonderful person... :D

Your guide is even better & more comprehensible than the one over at Modaco!

Thank you!
[Touch HD Windows Mobile ROM Development] akash_nu:
Wonderful piece of work bro... another amazingly easy tutorial...
[Touch HD Windows Mobile ROM Development] stonedge:
Thanks, CrAcKwHoRe:)

this thread need a glue :D
[Touch HD Windows Mobile ROM Development] eighty1:
Thanks for your work

GREAT WORK HERE. WISH THIS WAS AROUND WHEN I FIRST HAD TO DO IT.:rolleyes: THANKS FOR YOUR DEDICATION OF HELPING OTHERS AS ALWAYS.:D
[Touch HD Windows Mobile ROM Development] zoltrix3:
I haven't in device manager windows CE USB devices

I tried reinstall ActivSync 4.5 without any results.

How can I fix this problem?

Thanks for the help
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Are you putting your phone in the bootloader before you connect it to your PC via USB?
[Touch HD Windows Mobile ROM Development] zoltrix3:
No;)

That was the reason:)

Thanks
[Touch HD Windows Mobile ROM Development] ModernMuseum:
I'm about to attempt this driver update, but I have a conflict with your instructions.

Your instructions hint that there should be a 32-bit folder and a 64-bit folder inside the drivers.zip file. I just see 6 individual files. Is it okay to proceed with extracting all six files to a single folder and updating the driver with the wceusbsh.inf file?
[Touch HD Windows Mobile ROM Development] Digital Outcast:
I just downloaded the attachment from the first post. When I open the archive in Winrar on Winzip I see two folders, 32-bit and 64-bit. I get the same directory structure when I unzip them...
[Touch HD Windows Mobile ROM Development] ModernMuseum:
I've tried it on two PC's and got the same result: 7 files in one directory - the first five appear to be 32-bit and I extracted those five to a directory on my PC:

WceRndis.cat

WceRndis.inf

wceusbsh.cat

wceusbsh.inf

wceusbsh.sys

(64-bit files wceusbsh.sys and wceusbshx64.inf appear to be the only 64-bit files and I did not extract them)

I believe I updated the drivers successfully, but when using USPL to update the phone to 1.54 SPL (step USPL3), it gets stuck at 0% and then sends me into a Recovery sequence.

Anyone got any ideas? I need to get this done ASAP before I leave the country.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
When you use USPL does it "reboot" your phone and show SPL 1.15.USPL?
[Touch HD Windows Mobile ROM Development] Lilith_v2:
Guys i'm italian and i don't understand this piece and i don't able to install that drivers ._.

Anyone can help me?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Bootloader screen = Tri-colour screen

1. Turn off device

2. Hold down Volume down

3. Turn on device & continue to hold down volume down

You will enter a tri-colour screen. This is bootloader.

You need to be in bootloader before connecting your computer to phone.

Sorry this is not in Itailian. Hopefully you understand
[Touch HD Windows Mobile ROM Development] Lilith_v2:
Man i love you :D

I'm flashing ;)
[Touch HD Windows Mobile ROM Development] lunakirb:
Help.

Sir, on WXP1b what do u mean by that.. what to extract and where? thank you.

and in

Sir I didnt got that error but instead i got this, could you tell me what went wrong?

Thanks:confused:
[Touch HD Windows Mobile ROM Development] zenkinz:
just plug out your phone, and replug it back to the laptop. the drive will be reloaded properly.
[Touch HD Windows Mobile ROM Development] lunakirb:
after restarting or before the restarting sir? do i have to restart btw

and also sir how can i know if my htc sync driver is updated already
[Touch HD Windows Mobile ROM Development] Digital Outcast:
You don't need to restart your computer. If you have gotten to that point then you have updated the driver properly. All you need to do is unplug the cable from your phone and plug it back in.
[Touch HD Windows Mobile ROM Development] Ricco911:
Help!

thank you very much for this post, I really appreciate it! :D

I only have one problem, when I open the device manager,

I dont get "Mobile Devices" and also when I connect my phone

on the bootloader screen, I see the 3 colors, but nowhere does it say

USB like before. can anyone help?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
At the very bottom of the bootloader screen it should say 'Serial' when HD is not connected to pc. This should change to 'USB' after a second or two once you connect HD to PC via usb cable.
[Touch HD Windows Mobile ROM Development] bthelastman:
Hi,

I tried the USPL, and to update my drivers and followed your steps twice, but active sync cannot detect my phone when its in the bootloader. When i have updated the drivers, theres a red x on active syng logo in the corner, and says disabled? So i cannot run the RUU. Please help.

Thanks.
[Touch HD Windows Mobile ROM Development] yin0:
Hi

after i have done this updating.

My laptop cant see my device anymore when i plug it in with USB cable.

so i cant swap my things from my laptop to my device.

how can i set this?
[Touch HD Windows Mobile ROM Development] astryger:
What do I do if these steps don't give me the bootloader?
[Touch HD Windows Mobile ROM Development] anssibragge:
"Turn off" here means "shut down". Not just shutting the display with a short click on the power button.

So either a long click on the power button and a dialog appears asking if the phone should be shut down.

Or use a soft reset utility that come with some apps.

abe
[Touch HD Windows Mobile ROM Development] Zen_mystic:
Any guys able to help me with this ? I'm using vista and i could not see Mobile devices at the device manager.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Have you tried updating vista driver? Follow instructions here. Once complete reboot pc
[Touch HD Windows Mobile ROM Development] Zen_mystic:
I got it ! Thanks a lot for you help !
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
No probs

Rick
[Touch HD Windows Mobile ROM Development] wvz6:
Windows Update comes with update for PPC USB Sync

After I've updated my usb drivers as described in post 3. After a while Windows Update comes up with the following available update: Other Hardware - PocketPC USB Sync.

What must be done with this update? Does it replace the update from post 3?

Thnx
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Yes, it will overwrite the whole point of this thread. You want to ignore/hide that update.
[Touch HD Windows Mobile ROM Development] qtype:
Windows 7 question

I have installed Windows 7 on my laptop...

and have updated my ROM 3 weeks ago...

everything was ok...

today i tried to updated it again and i coulden't...

i followed you instructions, as always, but got stuc on step WV6

my device was not recognized in the device manager and i couldn't update the drivers for HTC sync... you can see that on the picture.

do you have any ideas why???
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Is this Vista 32 or 64-bit? Is your device in the bootloader when you are trying to do this?
[Touch HD Windows Mobile ROM Development] qtype:
it's windows 7 64bit and yes it was in bootloader mode..
[Touch HD Windows Mobile ROM Development] nearlygod:
Hi,

i wanted to try this driver with Windows 7 because, after initial success, Windows 7 refuses to sync with my phone unless i set it to slow sync mode(which needs hours to sync)

So i follow your instructions, then i get this message (attachment1).

I un/replug and check the driver (see attachment 2)

I didn´t change.

thx for your help,

nearly
[Touch HD Windows Mobile ROM Development] sgpoorguy:
Hi,

After I got into the boot loader screen, my phone is showing "loading......" with a grey background with nothing else. I don't see a serial below nor a usb after I connect the phone to the PC. Any idea what is wrong here?

Thanks
[Touch HD Windows Mobile ROM Development] Algus Helm:
Excelent guide mate!!! I made it succefully on my Vista 64.

Now the flashing door are wide open : )
[Touch HD Windows Mobile ROM Development] FuZi0n:
Just a small add, when I tried to update the drivers I ALWAYS got the message "couldn't complete blahblah error...". USPL didn't work either when I got the failed message. However, when I started it and pulled out the usb cable after like a little over 10 seconds, it works. So that's just a tip for the people who experience the same problem.

It's quite a while ago since I started using that 'method', so I don't exactly remember the screen I got but I believe it's the one from nearlygod's screenshots.

Nice guide anyway :)
[Touch HD Windows Mobile ROM Development] lunakirb:
[Question]

i already updated my usb drivers before and flashed many cooked roms already

and just a question pops up my head why flashing last night..

if i uninstall the active sync(old) and install it again(active sync 4.5), do i have to update the USB drivers once again?

thats all

thank you.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Yes you do. :)
[Touch HD Windows Mobile ROM Development] cverstij:
When I go back to the "Show Compatible Hardware" screen where I have to click on the "Have Disk" button and then go choose the .inf file, it comes back with a "This driver is not digitally signed".

What do I do now?
[Touch HD Windows Mobile ROM Development] ClydeB1:
Are you running Vista 64 bit?
[Touch HD Windows Mobile ROM Development] cverstij:
No, 32-bit XP. It will let me go ahead and install the driver, but I get some message that says Microsoft STRONGLY recommends NOT installing the unsigned driver.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Don't worry, install it anyhow
[Touch HD Windows Mobile ROM Development] benezuela:
Works perfect! Thanks.