Database Info

Motorola Q9h, TomTom 6 - GPS and backlight

After installing TomTom 6 on my Motorola Q9h I had two major issues -
1) To start GPS I had to start some external GPS program
2) Backlight did not stay ON.
So, I made a launcher that fixes these things.
Copy MyTTlauncher.exe to the device,
change tt.lnk accordingly and copy to device (\Windows\Start Menu for example).
Default - TomTom and MyTTlauncher.exe are in \Program Files\Navigator\

Can you navigate and select items in the menus in tomtom? My up/down dpad controlls the volume not scrolling..thne when typing on teh keypad only the numbers make numbers so i cant type 10 of the letters so address entry is impossible
i had to edit the config file to make it com5 after using the modaco gps port setter because i couldnt select a gps comport when they listed the available...compared to running on my old 8525 this software feels very cripled on a non touch screen pda....
HOPEFULLY you have some good tips?!

SchmilK said:
Can you navigate and select items in the menus in tomtom? My up/down dpad controlls the volume not scrolling..thne when typing on teh keypad only the numbers make numbers so i cant type 10 of the letters so address entry is impossible
Click to expand...
Click to collapse
Press and hold contact button (on the bottom second from the left) until phone beeps. It will switch keyboard layout between numbers and letters. You can use Fn instead of backspace. Items from the menus can be selected either via d-pad or via numbers. Unfortunately, selection from the list and browsing the map is possible only via fakecursor

Problems...
Hey guy... I have the Moto Q9h as well. i installed tom tom and your files but whenever i open tomtom and hit navigate to it says no gps device? any ideas?

xeo757 said:
Hey guy... I have the Moto Q9h as well. i installed tom tom and your files but whenever i open tomtom and hit navigate to it says no gps device? any ideas?
Click to expand...
Click to collapse
You need to use Microsoft GPSID utility to map GPS to Com3, then configure TomTom to use Com3

SchmilK said:
Can you navigate and select items in the menus in tomtom? My up/down dpad controlls the volume not scrolling
Click to expand...
Click to collapse
TomTom 7 (build 9030) finally works fine with up/down keys!

U-2 said:
After installing TomTom 6 on my Motorola Q9h I had two major issues -
1) To start GPS I had to start some external GPS program
2) Backlight did not stay ON.
So, I made a launcher that fixes these things.
Copy MyTTlauncher.exe to the device,
change tt.lnk accordingly and copy to device (\Windows\Start Menu for example).
Default - TomTom and MyTTlauncher.exe are in \Program Files\Navigator\
Click to expand...
Click to collapse
Thanks, U-2
Would you mind to share the source code? Or explain what your program do (api calls,...)?

aprendiendo said:
Thanks, U-2
Would you mind to share the source code? Or explain what your program do (api calls,...)?
Click to expand...
Click to collapse
int _tmain(int argc, _TCHAR* argv[])
{
PROCESS_INFORMATION pi = {0};
DWORD dwRes = 0;
HANDLE hGPS = 0;
TCHAR tszBacklightName[] = TEXT("BKL1:");
HANDLE s_hBacklightReq = NULL;
HINSTANCE hInst = GetModuleHandle(NULL);
hGPS = GPSOpenDevice(NULL, NULL, NULL,NULL);
if (FALSE == CreateProcess(argv[1], NULL, NULL, NULL, NULL, 0, NULL, NULL, NULL, &pi))
{
//goto Error;
}
s_hBacklightReq = SetPowerRequirement(tszBacklightName, D0,
POWER_NAME, NULL, 0);
Sleep(5000);
do
{
SetSystemPowerState(NULL, POWER_STATE_ON, 0);
dwRes = WaitForSingleObject(pi.hProcess, 5000);
} while (WAIT_TIMEOUT == dwRes);
GPSCloseDevice(hGPS);
if (s_hBacklightReq)
ReleasePowerRequirement(s_hBacklightReq);
return 0;
}
attached .exe does not have the part with SetSystemPowerState. I had to add it because in TT7 my on Q9h GPS stopped after several minutes. I think SetPowerRequirement became redundant, but I left it there

Thank you very much, U-2
I tried something similar (with "CeRunAppAtTime"), using only "SetSystemPowerState", but it doesn't worked out.
Finally I installed Tomtom 6 + Tomtom 6.03 and now it's working perfectly with my IPaq 214. After the installation the BT couldn't turn on, but a reset fixed it

Call forwarding with VJDialer

Hi all!
I have tried the search, but with no satisfying result.
I searching for a solution to control call forwarding in profiles. I know there is phonealarm etc. but I already have bought phoneweaver and would like to keep it.
I tried to set up VJDealer with **21*0123456789# to register call forwarding. Unfortunately it is not dialing the whole string (only **21 apears while dialing) and it fails.
Ist it possible to use VJDialer for this? How to do it right?
Using WM 6.1 on a Charmer and this shotcut for VJDialer:
"\program files\Vijay555\VJDialer.exe" **21*0123456789#
Thanks a lot

mortscript solution
so, I have found mortscript and made a basic script to to so.
for anybody who is interested in:
activate:
SendSpecial( "F3" ) # start phone with green dial button
WaitForActive( "Phone",3 )
MouseClick( "Phone",40,245 ) # *
Sleep( 1500 ) # avoid receiving p instead of double *
MouseClick( "Phone",40,245 ) # *
MouseClick( "Phone",120,135 ) # 2
MouseClick( "Phone",40,135 ) # 1
MouseClick( "Phone",40,245 ) # *
MouseClick( "Phone",120,245 ) # 0
MouseClick( "Phone",40,135 ) # 1
MouseClick( "Phone",200,175 ) # 6
MouseClick( "Phone",120,245 ) # 0
...
MouseClick( "Phone",200,245 ) # #
SendSpecial( "F3" ) # register call forwarding with green dial button
Sleep( 10000 ) # wait 10 seconds for confirmation
SendSpecial( "F3" ) # get rid of phone status message "succeded" with green dial button
SendSpecial( "F4" ) # use red end of dial button to return to today screen
and deactivate:
SendSpecial( "F3" ) # start phone with green dial button
WaitForActive( "Phone",3 )
MouseClick( "Phone",200,245 ) # #
MouseClick( "Phone",200,245 ) # #
MouseClick( "Phone",120,135 ) # 2
MouseClick( "Phone",40,135 ) # 1
MouseClick( "Phone",200,245 ) # #
SendSpecial( "F3" ) # register end of call forwarding with green dial button
Sleep( 10000 ) # wait 10 seconds for confirmation
SendSpecial( "F3" ) # get rid of phone status message "succeded" with green dial button
SendSpecial( "F4" ) # use red end of dial button to return to today screen
I know its not perfect, but it seems to work for WM6.1.
well if anybody has some hint to improve the code - would be great.
Especially in handling this phone message box which says succeeded. I did not manage to find or handle it in mortscript as it has the same window title "phone".
regards

[Q] Android automation

Is anyone aware of a program that would allow me to automate a series of "touch" events on Android to test an app I have written. Something controlled by ADB I would assume.
For example;
Touch @ X axis = 500 Y axis = 200;
Wait 0.5 seconds;
Release touch;
Wait 1.9 seconds;
Touch @ X axis = 300 Y axis = 400;
Wait 0.5 seconds;
Release touch;
etc.

[GUIDE] Proper Shutdown - Emulating long press power button

Hi
So you want to emulate the native android shutdown sequence. Broken power button? Car or fixed Nexus 7 installation? TV Stick? Here is the solution! (I advise you not to use one of the many shutdown apps because they shutdown without unmounting filesystem etc. and thus can damage your filesystem in the long run).
This should work on ANY Android device!
You can do it directly on your device, no adb needed. BUT: You have to be rooted!
How to:
1. Install Bash X from playstore (I'm not affiliated with them)
2. Start it and choose #root shell
3. Type: getevent -c 3
4. Push power button and release it (short, without the boot dialog)
5. Now you see something like this:
# getevent -c 3
add device 1: /dev/input/event0
name: "pmic8xxx_pwrkey"
add device 2: /dev/input/event1
name: "gk-keypad-8064"
add device 3: /dev/input/event4
name: "hs_detect"
add device 4: /dev/input/event3
name: "suspend_autotest_pwrkey"
could not get driver version for /dev/input/mice, Not a typewriter
add device 5: /dev/input/event2
name: "touch_mxt1188S"
/dev/input/event0: 0001 0074 00000001
/dev/input/event0: 0000 0000 00000000
/dev/input/event0: 0001 0074 00000000
#
add device output shows you the event numbers off your input devices. On my LG Pad the power key is assigned to /dev/input/event0. On your device it will be a other eventX number. On my Nexus 7 it is event2 (gpio).
Now we convert the hex strings of the events in dec (google a online converter). The last 3 lines then look like this:
/dev/input/event0: 1 116 1
/dev/input/event0: 0 0 0
/dev/input/event0: 1 116 0
1 116 1 means power key down
1 116 0 means power key release
6. Install Tasker. Set up a new profile with the profile you want to be the trigger for your action (shutdown). Under tasks choose script, start shell and paste our new script:
/dev/input/event0: 1 116 1;
/dev/input/event0: 0 0 0;
sleep 1;
/dev/input/event0: 1 116 0;
Now we need only some dpad keys for going down and right in the menu:
input keyevent 20;
input keyevent 66;
input keyevent 22;
input keyevent 66;
(Where 20 is down, 22 is right and 66 is enter. This works on stock and CM10)
The Tasker action finally looks like this:
/dev/input/event0: 1 116 1;
/dev/input/event0: 0 0 0;
/dev/input/event0: 1 116 0;
input keyevent 20;
input keyevent 66;
input keyevent 22;
input keyevent 66;
exit;
Don't forget to check "use root" in your action. Test it out!
Cool it is
I also thank the many people working on this question on other places.
edit: if you experience no proper shutdown (have to press 15sec power button for boot), its because tasker hangs on shutdown. Export a app from tasker and start it with automateit. Weird but it works
Olivier

[Q] How to calibrate an external touchscreen properly (using IDC)

I'm struggling with calibration of a touchscreen on Android plataform.
It is an USB Single-Touch Touchscreen from vendor 0dfc and product 0001 as checked with dmesg:
Code:
<6>[ 4118.091541] input: USB Touchscreen 0dfc:0001 as /devices/platform/usb20_host/usb2/2-1/2-1.3/2-1.3:1.0/input/input23
I'm pushing the Vendor_0dfc_Product_0001.idc file /data/system/devices/idc/ (following the documentation from android source - IDC)
I got the touch device with all requirements for single touch events:
Code:
[email protected]:/ # getevent -il /dev/input/event3
add device 1: /dev/input/event3
bus: 0003
vendor 0dfc
product 0001
version 0202
name: "USB Touchscreen 0dfc:0001"
location: "usb-usb20_host-1.3/input0"
id: ""
version: 1.0.1
events:
KEY (0001): BTN_TOUCH
ABS (0003): ABS_X : value 540, min 0, max 32767, fuzz 0, flat 0, resolution 0
ABS_Y : value 289, min 0, max 32767, fuzz 0, flat 0, resolution 0
input props:
<none>
I also enabled the Pointer Location option from Developer options (Android settings) in order to debug this stage of calibration.
Setup 1
Code:
touch.deviceType = touchScreen
With this setup (1) all the gestures on the touchscreen take place at the up-left corner - just a few pixels left/right/up/down no matter the gesture (swipe). All the touchscreen get events. All the gestures are reversed - when swipe left the pointer goes right; when swipe up, the pointer goes down.
Setup 2
Code:
touch.deviceType = pointer
touch.gestureMode = pointer
With this setup (2), as expected, it shows a pointer, placed at the position from the last pointer device left (mouse). All the gestures on the touchscreen (no matter the swipe size) keep beaving like setup 1 - move only a few pixels with each swipe event, and with reversed axis.
Setup 3
Code:
touch.deviceType = pointer
touch.gestureMode = spots
With this setup (3) the result is the same as setup 2. I just did that to prove that the IDC file is being interpreted correctly.
At this stage, as you can check by now, I have a working IDC file (setup 1) requiring calibration for this touch device.
I tried a lot of combinations from other IDC files (internet samples) and from android source - IDC - ANY OTHER PROPERTY TOOK EFFECT (NOT A SINGLE ONE) - raw.*, output.*, touch.size.*
Does anyone knows how to calibrate properly a touch screen in Android that could guide me in this process?
Thank you