Related
It seems that wifi scanners detectors like WiFiFoFum don't work with WM6 roms. It seems to load up fine but it cannot seems to find any access points. I tried every device in the list and still it cannot find anything. If I run it on any none WM6 OS [3.X roms using > WM6 ], it works correctly. Any ideas?
raiden said:
It seems that wifi scanners detectors like WiFiFoFum don't work with WM6 roms. It seems to load up fine but it cannot seems to find any access points. I tried every device in the list and still it cannot find anything. If I run it on any none WM6 OS [3.X roms using > WM6 ], it works correctly. Any ideas?
Click to expand...
Click to collapse
No problems with Xplore 1.1 - tested wififofum just three day ago. Find alot of ap and could connect. SO no problem.
Yes also NetBox 2.0 working fine
WiFiFoFum on WM6
Might want to make sure you get version 2.2.7 or above.
Second, try turning on the WIFI before you launch WiFiFoFum. I had a similar problem and never understood the "Power Device" menu selection, thats the same thing as turning the wifi radio on and off.
Not sure if anyone else has noticed this, but I flashed my TILT to the HTC ROM (excellent work everyone btw), and after using the device for about a week, I've noticed this strange bug.
Start at the Today screen with the keyboard out
Start dialing by name (example, type V E L M A)
The first letter will work correctly, but when you press L on the dailpad screen, you get an X. The output will be VEXMA instead of VELMA.
Start over (go back to Today screen), and try pressing V V which should bring up "VV", but instead brings up "VT".
Apparently there are some key mapping problems in the dail pad screen at least on a TILT flashed with the Kaiser ROM. I have applied the key mapping fix from the sticky post, and I'd like to see if someone else has this problem too!
In addition, there are MANY letters that do not work correctly, some do not work at all in the dial pad!
Verified here too. It's a bug in the smartdialer when running on the tilt. Will be interesting to see if:
it works ok on a tytn II
everything is ok with the AT&T rom
yes to both = interaction bug (I guessing this will be the case)
Unbranded HTC Tytn II, running HTC stock rom... no problem.
VELMA and VV work correctly.
just tried this on my tilt flashed with an HTC (MFG) ROM and this is definitely a confirmed issue for Tilt handsets flashed with the HTC ROM. Hopefully someone can figure out where the keymapping problems are coming from.
btw, i have TaurusBulba's Tilt keyboard fix installed, have yet to try without his keyboard fix
Nm, fixed my problem.
that is strange I wonder if its in the registry since you are using the same smartdail.dll since you are running the HTC ship ROM. I also confirmed I have no issue on a HTC TyTN II
Hey guys. Fixed the problem. I've updated the Tilt keyboard fix here.
**** taurusbulba i wish i could say the new fix worked but now i get "TEXMA" when i type in VELMA from the today screen
hmmm.... I installed your cab tb & now keys aren't mapping into the smart dialer at all. Pressing from today brings up phone app but not the smart dialer. Is there another reg entry under HKLM\HTC\SmartDialing perhaps?
edit: @Taurusbulba: if you have a tilt running AT&T ROM, can you dump hklm\Software\HTC\SmartDialing & all subkeys plz?
Sure wish I had tools that could dump this ROM...
Try removing the fix via Remove Programs, soft reset, then install the updated cab and soft reset again.
I did this and it worked fine.
Doug2873 said:
**** taurusbulba i wish i could say the new fix worked but now i get "TEXMA" when i type in VELMA from the today screen
Click to expand...
Click to collapse
Have you done what vasquja mentioned? Uninstall the old, soft reset, install the new, soft reset? It's working perfect for me.
At the moment I'm using a Tilt with the stock HTC ROM. Out of curiosity, what ROM are you using?
Here ya go Sleuth....
youre correct it works now, thanks.
I'm on SPRINT'S HTC TOUCH PRO RAPHAEL
Ive been looking for the classic WMODEM.exe for a long time now.
I tried the Titan version, doesnt work
I tried a bunch of different versions from someone in the XDA Developer's Raphael Software Forum (above this one)
- didnt work.
I dont like ICS because its not that compatible with say, OpenBSD, FreeBSD, requires hacking to get working with Linux, and is basically microsoft proprietary bulls**t. I want the real deal PPP Wmodem. If nobody can provide a working one, and its deemed 'impossible' by the experts here, is there a way to hex edit or hack it so it works? Perhaps there is a registry key that prevents it from loading properly?
Please help me finally get WMODEM.EXE to load on the HTC Touch Pro! ICS sucks!!!
whats the problem you're experiencing when you're trying to load wmodem, exactly?
you double tap or excute the file right? and it does nothing.. you can sit there tapping over and over or pressing the enter button or anything and it just wont run
It's like compiling this into a C program:
main() {
exit(0);
}
--
on a hunch im going to try turning off touchflo3d, and executing the four different versions of wmodem i have, maybe one of them will load.. but i doubt it. I tried doing it this way with the Titan wmodem.exe and it still wouldn't load
ok i tried it, it does not work.
can anyone explain why WMODEM does not work for the TOUCH PRO?
has anyone gotten it to work?
maybe theres something embedded in wmodem.exe that causes it to exit() when executed in this operating environment?
can any developers or someone with debugging tools isolate what the cause is ? I have a feeling you could probably hex edit
or hack the wmodem.exe into working properly. Where would i post to request this?
it's actually running on my device, but when i tap the start connection button, the radio crashes, and the program says it could not open the com port.
i think it might be using obsolete api's or something, and that's why it doesn't load properly.
i tried to use it with a reg logger, to see if it searches for any special settings we could tweak, but i didn't spot anything special.
sry dude.
Where are the real hackers of the phone community? Just wondering? Should I try getting ahold of Lennysh on this issue? i hear hes pretty skilled.
the thing is, ICS drains the hell out of your battery. if you dont have over80% battery life on your touch pro, and you attempt to tether using ICS it will drain like crazy and your computer wont charge it.
as well as it not being a true ppp dialup connection, that too also sucks. meaning you have to use special hacks or tweaks for it to work under linux. thats bs
I will bring this back as I am also looking for a working WModem for the Raph.
afaik, wmodem provides support for gsm, you want dmrouter for cdma (which should come on all cdma roms)
the 5.08 AT&T test rom contains wmodem.exe.. as does the official AT&T ROM.. and it functions fine under both
When i try to run Voice Commander I get an out of memory error. I am running version 1.6.19209 Anyone else tried this or gotten it to work?
I'm using 1.6.21040.
Gave an error during installation, but seems to be working as far as announcing calls and reading texts.
I have tried to installed version 1.6.21725 and it seems to work fine, but I tried to link to the key virtually using AE Buttons, everything collapsed. The lnk file just got deleted: any suggestion.
How did you guys use to assign to a key?
Was asking the same question. Install worked with one error message. The program works when I start it manually, but I cannot find a way to assign execution to a specific button press. Looking for ideas here.
Toby
i didnt link the button once i got the latest version installed and working. i jsut made a link and put it on the start menu instead and it works great that way
I've switched to 21725 and used aebutton plus to assign it to long press windows key, all works perfectly now.
I dont want to use aebutton plus, so I tried to use the old Long_Send.lnk and had no luck, am I doing something wrong?
or is it a diffrent name in 6.5
MSVC
I got that error too but it has stopped for some reason and now works well.
Version is v1.6.21040
I tried to upload a cab for you but it wouldn't upload.
I use MSVC for text to speech, to announce calls, read emails to me and announce calendar reminders.
This version won't read text msgs.
I don't use it for voice commands, Cyberon Voice Speed Dialer is much better for that.
mallman said:
When i try to run Voice Commander I get an out of memory error. I am running version 1.6.19209 Anyone else tried this or gotten it to work?
Click to expand...
Click to collapse
mallman said:
i didnt link the button once i got the latest version installed and working. i jsut made a link and put it on the start menu instead and it works great that way
Click to expand...
Click to collapse
WHICH LINK DID YOU USE, THE SHORT OR LONG ONE??
Thanks!
I got this error on the stock TP2 ROM as well. For me, it only occurred when I checked the box for announcing WMP selections.
Oh, regarding the MS Voice Command CAB, while it is not the reason the upload failed, XDA does not allow MSVC to be posted in CAB form since it can then be installed on devices that it is not licensed for.
MSVC cab
Oops!
Got it.
NotATreoFan said:
I got this error on the stock TP2 ROM as well. For me, it only occurred when I checked the box for announcing WMP selections.
Oh, regarding the MS Voice Command CAB, while it is not the reason the upload failed, XDA does not allow MSVC to be posted in CAB form since it can then be installed on devices that it is not licensed for.
Click to expand...
Click to collapse
So was anyone able to get MSVC running with a bluetooth headset??
I mean initiating MSVC commands via the headset button and also get the commands itself in the headset?
I cannot get it run like this.
bill340 said:
So was anyone able to get MSVC running with a bluetooth headset??
I mean initiating MSVC commands via the headset button and also get the commands itself in the headset?
I cannot get it run like this.
Click to expand...
Click to collapse
When I start MSVC, the command is repeated through the headset first time then it comes through phone speaker after that. Phone calls are directed through the headset ok. Strange.
I Think I've Found An Answer
If you go into the registry and go to:
\\HKLM\Software\OEM\VoiceCommand
and edit the value for VoiceCmdEnable to 1 (it was set to 0 on my HD2), then soft reset.
Now you should be able to get Voice Command working through BT, at least it's working for me at the moment.
It does not help fo rme at all...
No change!
Which version of MSVC do you use?
I'm not entirely sure, but in the Voice Command settings it shows v1.60.4622.0
weepatc said:
When I start MSVC, the command is repeated through the headset first time then it comes through phone speaker after that. Phone calls are directed through the headset ok. Strange.
Click to expand...
Click to collapse
In my case it is very similar, but when i activate voice command with the assigned button on my HD2 and not via the headset, everthing works as it should. Maby thats a indication how to get it worki`n the right way.
VoiceCommander Working
Hi,
Initially I couldnt get the BT to connect to VC (just got a BT disconnect beep in my ear).
Tried installing 2nd time (over the top), and seemed to 1/2 work but sometimes I would have to say name I wanting to dial through handset - then it would put call through BT - strange.
Finally, I noticed that if the BT headset was on when the phone was switched on (fluke that happened), it worked fine.
If the BT headset is switched on after the phone, it still plays up. Not tried turning BT on handset off and on whilst BT headset turned on yet - something to try tonight I guess.
Note : this only started working a day or so ago so not tested throughly yet.
My VC version is 1.6.4622.0.
I also noticed that on handango - a new VC version is available (updated 20/11/2009) which says works with Touch HD2 - but only USA voice at the mo so I'm waiting for the UK (hopefully released soon).
Hope the above helps.
Looks like I have an old version of Voice Command MSVC1.6.19214. How do I get a later version? Don't see why I should have to pay for it again when it is still 1.6.
Sorry, my bad - not working anymore. Worked for one day, then I get the same as everyone else
Just installed this little driver http://sotolog.net/bluekeyboard/ and my old iGo Stowaway keyboard now works. I know various people have hacks to get this to work previously - but with this simple install, your just configure the keyboard and are away. No terminal command lines, no rooted phones - it just works.
Great! - Just thought you should all know.(bluekeyboard is available in the Android Market)
help! the link is down, and i would love to get the kb to work with my t-mobile g2. can you send me the file? hope that is not a hopeless newbie question, but i can get it paired, get bluekeyboard installed, configured, and seeing the keyboard to select it in setup, but it will not connect!!!
thanks.
Mark
Application is available in the Android Market - I just re-downloaded it to confirm.
It sounds like you have everything you need. You just need to pair it with your device. How you trigger pairing on your keyboard depends on the keyboard. The stowaway use the 2 Fn keys held down for a few secs and the LED then pulses.
I misunderstood. I thought you were referring to something you had to add to bluekeyboard. I have paired the kb. It will simply not connect. I thought I saw a customer comment that it does not work on 2.2, which my G2 runs. Everything seems configured, unless I need to press something on the kb to get it to connect. Argh
Hi
Can someone send me the apk or upload it somewhere? For some reason after I upgraded the ROM, bluekeyboard can't be found in market + if i use market website it says it is not compatible with my device (a htc desire).
weird...