[App] TomTom Navigator 7.918.9193 (W)VGA and (W)QVGA - Windows Mobile Apps and Games

for the one's who like it , I made a .cab from the patched files of 7.918.9193 found on ipmart .
just install the cab and you have the Navigator 7.918.9193 (no need to first install an old package).
this version is from a HD2 but runs good on a TP .
DON'T ASK FOR MAP'S AND DON'T ASK HOW TO ACTIVATE MAP'S
Here is the link to ttn7.918.9193_vga_black.cab
Thanks to JaCoL_JcL we also have the ttn7.918.9193_(W)QVGA_black.cab
Here is the link to ttn7.918.9193_(W)QVGA_black.cab
Edit: fixed the link .

You wrote "TomTom Navigator 7.918.9193 (W)VGA" in this tread title, is it really WVGA?

Hassan99 said:
You wrote "TomTom Navigator 7.918.9193 (W)VGA" in this tread title, is it really WVGA?
Click to expand...
Click to collapse
it was a dump from a HD2 so I think so .
on ipmart a lot are using it on a HD2 .

reported as warez link! u must but this application m8! don't share here this kindda files !

JaCoL_JcL said:
reported as warez link! u must but this application m8! don't share here this kindda files !
Click to expand...
Click to collapse
what is wrong with this it is not cracked or someting like that .
and if an admin ask me to remove this link I will do it

JaCoL_JcL said:
reported as warez link! u must but this application m8! don't share here this kindda files !
Click to expand...
Click to collapse
Only the TomTom Maps are considered Warez, the TomTom application isn't.
Dave

DaveShaw said:
Only the TomTom Maps are considered Warez, the TomTom application isn't.
Dave
Click to expand...
Click to collapse
thanks Dave for correcting this .
Gr Cees.

TomTomNavigator 7.918.9193 QVGA/WQVGA
DaveShaw said:
Only the TomTom Maps are considered Warez, the TomTom application isn't.
Dave
Click to expand...
Click to collapse
good to know sry about affair xD
------------------------------------
Here is a (W)QVGA installation cab, color - black:​
Code:
http://www.multiupload.com/LDPXH7IEN3

JaCoL_JcL said:
good to know sry about affair xD
------------------------------------
Here is a (W)QVGA installation cab, color - black:​
Code:
http://www.multiupload.com/LDPXH7IEN3
Click to expand...
Click to collapse
I will post it on the first post

Can this simply be installed over an existing TomTom installation, or will maps have to be re-authenticated (re-registered, whatever it's called)?

pistou said:
Can this simply be installed over an existing TomTom installation ?
Click to expand...
Click to collapse
yes it can .

If you have Tom Tom already installed just extract te cab file in this post.....rename the 001-file to "Tom Tom navigator.exe" and the 002-file rename to "data.chk". Copy these 2 files to the navigator map in your phone directory replacing the existing files and you are done. All your settings will remain.
Have this version running since a few days.......no problems!

Frank Caarls said:
If you have Tom Tom already installed just extract te cab file in this post.....rename the 001-file to "Tom Tom navigator.exe" and the 002-file rename to "data.chk". Copy these 2 files to the navigator map in your phone directory replacing the existing files and you are done. All your settings will remain.
Have this version running since a few days.......no problems!
Click to expand...
Click to collapse
Hi all
one question !
in the past ,for change the VGA to QVGA version ,the hack are for the TTN7 build 7451.9033 : run in qvga black or blue, or VGA black.
For this , use an hexadecimal editor like Hexedit or Ultraedit, open TomTom Navigator.exe and modify displacement 2A8578h :
. 10h VGA Black
. ODh QVGA Blue
. 12h QVGA Black
but in the new 7.918 there is no "2A8578" in the file tomtom.exe ,how change this, in this version ? in the first post,this is only a VGA version ,not QVGA for me ???
thanks in advance for your reply

Frank Caarls said:
If you have Tom Tom already installed just extract te cab file in this post.....rename the 001-file to "Tom Tom navigator.exe" and the 002-file rename to "data.chk". Copy these 2 files to the navigator map in your phone directory replacing the existing files and you are done. All your settings will remain.
Have this version running since a few days.......no problems!
Click to expand...
Click to collapse
Unzipping via 7zip actually gave me different filenames... renamed according to nearest filesize, gonna try and see. Anyway, thanks for the idea!

Frank Caarls said:
If you have Tom Tom already installed just extract te cab file in this post.....rename the 001-file to "Tom Tom navigator.exe" and the 002-file rename to "data.chk". Copy these 2 files to the navigator map in your phone directory replacing the existing files and you are done. All your settings will remain.
Have this version running since a few days.......no problems!
Click to expand...
Click to collapse
Nice post, but wrong for me. (For the file I downloaded from the OP).
The two files you need will be the two largest ones, with data.chk being the larger of the two. You know you have found the correct tomtom exe because the icon will change to a tomtom logo.
I hope this one solves my keyboard problems, for some reason my keyboard always stopped working properly after a while, though I suspect tomtom home maybe screwing with my phone install or something.

I have tomtom 7 with us and canada maps.
What exactly is this and what does it do?

what does this offer that is not already in 7.916.9189 ??
is it simply that it's WVGA ?
does it actually look any better for being WVGA ? (am I missing the plot ?)

according to GPS undergound, this version will only work on :* ERA MDA Vario IV
* HTC HD 2
* HTC P3470
* HTC Touch 2
* HTC Touch Cruise
* HTC Touch Cruise II
* HTC Touch Diamond 2
* HTC Touch HD
* HTC Touch Pro
* HTC Touch Pro 2
* HTC TyTN II
* O2 XDA Diamond Pro
* O2 XDA Guide
* O2 XDA Orbit 2
* Orange HTC Touch Pro
* Orange P4550
* Samsung i900 Omnia
* SFR HTC Touch HD
* SFR HTC Touch Pro
* Sony Ericsson XPERIA X1
* Swisscom HTC Touch Pro
* Swisscom HTC Touch Pro 2
* Swisscom XPA1615
* T-Mobile MDA Vario III
* T-Mobile MDA Vario IV
* Vodafone HTC Touch Pro
* Vodafone XPA1615
because it's not been cracked for any pda yet ? - is this a cracked version ?
http://www.gpsunderground.com/forums/showthread.php?p=162055#post162055

if you open the .cab with winrar you will find the file setup.xml
if you open the setup.xml you can read what the file name is.
Code:
- <wap-provisioningdoc>
- <characteristic type="Install">
<parm name="InstallPhase" value="install" />
<parm name="SetupDLL" value="1" />
<parm name="ProcessorType" value="2577" />
<parm name="OSVersionMin" value="3.0" />
<parm name="OSVersionMax" value="100.0" />
<parm name="BuildNumberMin" value="0" />
<parm name="BuildNumberMax" value="-536870912" />
<parm name="AppName" value="TomTom Navigator" />
<parm name="InstallDir" value="%CE1%\Navigator" translation="install" />
<parm name="NumDirs" value="4" />
<parm name="NumFiles" value="7" />
<parm name="NumRegKeys" value="0" />
<parm name="NumRegVals" value="0" />
<parm name="NumShortcuts" value="1" />
</characteristic>
- <characteristic type="FileOperation">
- <characteristic type="%CE2%" translation="install">
<characteristic type="MakeDir" />
- <characteristic type="ttn6bt2003.dll" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="TTN6BT~1.001" />
<parm name="OverwriteIfExists" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
- <characteristic type="BtCoreIf.dll" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="BTCOREIF.002" />
<parm name="OverwriteIfExists" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
- <characteristic type="BtSdkCE30.dll" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="BTSDKC~1.003" />
<parm name="OverwriteIfExists" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
- <characteristic type="phone.dll" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="000PHONE.005" />
<parm name="NoOverwrite" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
</characteristic>
- <characteristic type="\TomTom" translation="install">
<characteristic type="MakeDir" />
- <characteristic type="TTToday.dll" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="0TTTODAY.004" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
</characteristic>
- <characteristic type="%InstallDir%" translation="install">
<characteristic type="MakeDir" />
- <characteristic type="[COLOR="Red"][B]TomTom Navigator.exe[/B][/COLOR]" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="[COLOR="Red"][B]0CABB32B.006[/B][/COLOR]" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
- <characteristic type="[COLOR="Blue"][B]data.chk[/B][/COLOR]" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="[COLOR="Blue"][B]0CABE6BA.007[/B][/COLOR]" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
</characteristic>
- <characteristic type="%CE11%" translation="install">
<characteristic type="MakeDir" />
- <characteristic type="TomTom Navigator.lnk" translation="install">
- <characteristic type="Shortcut">
<parm name="Source" value="%InstallDir%\TomTom Navigator.exe" translation="install" />
</characteristic>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="Registry" />
</wap-provisioningdoc>
that mean that 0CABB32B.006=TomTom Navigator.exe and 0CABE6BA.007=data.chk

evilc said:
Nice post, but wrong for me. (For the file I downloaded from the OP).
The two files you need will be the two largest ones, with data.chk being the larger of the two. You know you have found the correct tomtom exe because the icon will change to a tomtom logo.
I hope this one solves my keyboard problems, for some reason my keyboard always stopped working properly after a while, though I suspect tomtom home maybe screwing with my phone install or something.
Click to expand...
Click to collapse
Indeed you are right.....have downloaded this TomTom Navigator from a "different" place......
Sofar had no problems to make map updates with TomTom Home....but for how long.....?

Related

Bypass Welcome Screen with DCD 2.3.1 Kitchen?

I changed from DogGuy to this new DCD kitchen and do really like it, but I have come across a couple of strange things. I was wondering if anyone else is having the same issues, and has figured them out. I can no longer skip the welcome screen and calibration with this new kitchen. I even tried to recreate the script with the newest oemizer, and still no luck. I am using a real high GUID (ffffffff-f493-424e-b7f1-cab5da57bd61) so it should be one of the last updates to the registry. But it still does not work. It did work with the DogGuy kitchen and the 6.1 rom from No2Chem. Has anyone made this work? Here is the code form my oem:
;<<<<<----- First Boot Settings ----->>>>>
;Skip Welcome Screen
;================================================= ============
[HKEY_LOCAL_MACHINE\Software\Microsoft\Welcome]
"Disable"=dword:FFFFFFFF
;Stylus Calibration
;================================================= ============
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"CalibrationData"="2018,1980 3383,3022 3387,972 649,950 667,3021"
[HKEY_LOCAL_MACHINE\ControlPanel\Stylus]
"Group"=dword:00000001
;--------------------------------------------
Also, I have not been able to successfully change the today screen through an oem either.
;Today Theme
;================================================= ============
[HKEY_CURRENT_USER\Software\Microsoft\Today]
"Skin"="\\Windows\\Lamborghini_Gallardo.tsk"
"UpdateFlag"=dword:00000001
"Restriction"=dword:00000002
Thanks,
Poltergeek.
you need to edit initflashfiles.dat and remove the line that places welcome in startup.
Poltergeek said:
I changed from DogGuy to this new DCD kitchen and do really like it, but I have come across a couple of strange things. I was wondering if anyone else is having the same issues, and has figured them out. I can no longer skip the welcome screen and calibration with this new kitchen. I even tried to recreate the script with the newest oemizer, and still no luck. I am using a real high GUID (ffffffff-f493-424e-b7f1-cab5da57bd61) so it should be one of the last updates to the registry. But it still does not work. It did work with the DogGuy kitchen and the 6.1 rom from No2Chem. Has anyone made this work? Here is the code form my oem:
;<<<<<----- First Boot Settings ----->>>>>
;Skip Welcome Screen
;================================================= ============
[HKEY_LOCAL_MACHINE\Software\Microsoft\Welcome]
"Disable"=dword:FFFFFFFF
;Stylus Calibration
;================================================= ============
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"CalibrationData"="2018,1980 3383,3022 3387,972 649,950 667,3021"
[HKEY_LOCAL_MACHINE\ControlPanel\Stylus]
"Group"=dword:00000001
;--------------------------------------------
Also, I have not been able to successfully change the today screen through an oem either.
;Today Theme
;================================================= ============
[HKEY_CURRENT_USER\Software\Microsoft\Today]
"Skin"="\\Windows\\Lamborghini_Gallardo.tsk"
"UpdateFlag"=dword:00000001
"Restriction"=dword:00000002
Thanks,
Poltergeek.
Click to expand...
Click to collapse
place a file named " welcome.not " without quotation marks on the sd card and when you hard rest it will skip the welcome screen including calibration
Thanks DCD that did it. You are the man! I learn something new everyday.
-Poltergeek
dcd1182 said:
you need to edit initflashfiles.dat and remove the line that places welcome in startup.
Click to expand...
Click to collapse
which initflashfiles.dat would this be?
\OEM\OEM_Lang_0409\initflashfiles.dat
Poltergeek
Hey poltergeek - what about the today screen.... have you been able to figure out how to set it to the theme you want in ROM???
Nope, Still working on that. Something in the Kitchen is still overriding my settings in my hacks oem folder. I had trouble with it in the DogGuy kitchen as well. It uploads the Lamborgini tsk file, but I cannot get it to set properly. I just have to manually set it after every flash.... which is often. If I figure it out, I will post the fix.
Poltergeek
same here, poltergeek. i used oemizer to make the oem, and whatever the setting is, its overriding anything i do to change the theme...dcd help!
another problem im having is i edited the initflashfiles.dat to have nobottombar.exe in the startup folder. well, its in the startup folder and it doesnt activate until i go into the windows/startup folder and open it ugh. heres the line i made, its the last one listed:
; Startup Folder
Directory("\Windows\StartUp"):-File("coldinit.lnk","\Windows\coldinit.lnk")
Directory("\Windows\StartUp"):-File("bugtrap.lnk","\Windows\bugtrap.lnk");
Directory("\Windows\StartUp"):-File("poutlook.lnk","\Windows\poutlook.lnk")
Directory("\Windows\StartUp"):-File("CheckAutoRun.lnk","\windows\CheckAutoRun.lnk")
Directory("\Windows\StartUp"):-File("TrayAp.lnk","\windows\TrayAp.lnk")
Directory("\Windows\StartUp"):-File("nobottombar.exe","\Windows\nobottombar.exe")
Poltergeek said:
Nope, Still working on that. Something in the Kitchen is still overriding my settings in my hacks oem folder. I had trouble with it in the DogGuy kitchen as well. It uploads the Lamborgini tsk file, but I cannot get it to set properly. I just have to manually set it after every flash.... which is often. If I figure it out, I will post the fix.
Poltergeek
Click to expand...
Click to collapse
that something is wm6.1. it sets the default wm6.1 theme over anything you set in an oem.
i think you can still use cusTSK.exe and config.txt to set a different theme with autorun.
dcd, what would happen if we delete the windows mobile 6.1 theme?
Skipping the welcome screen. A while back I used OEmizer from Dogguys kitchen to make a simple OEM called preferences. in it I checked off skip welcome screen, Owners name, my IMAP settings for email etc. All of which are automatically implimented when I build the rom. I simply took that OEM and inserted it in the OEM folder of DCD's kitchen and it worked perfect.
On a side note, it allows you to choose your skin, but I never figured out how to make the new skin upload or auto impliment.... any idea?
You cant depend on an OEM for everything. You guys need to check the shell folder and edit this file mxipcold_wpc_2.provxml
Enjoy!
Poltergeek said:
\OEM\OEM_Lang_0409\initflashfiles.dat
Poltergeek
Click to expand...
Click to collapse
thanks.....
UGH! this is so aggrivating! i edited mxipcold_wpc_2.provxml and changed the .tsk to the one i want. i edited the today picture to what i want. now i cant get the right color for the bars! does anyone know a basehue color for black? mine is <parm name="BaseHue" value="16400A4" datatype="integer"/> its supposed to show up black but its showing up blue?!?!? heres my mxipcold_wpc_2.provxml:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKCU\Software\Microsoft\Today">
<parm name="Skin" value="\Windows\vista.tsk" datatype="string"/>
<parm name="UseStartImage" value="1" datatype="integer"/>
</characteristic>
<characteristic type="HKCU\Software\Microsoft\Today\vista.tsk">
<parm name="COLOR_TITLEFLATCENTER" value="1657344" datatype="integer"/>
</characteristic>
<characteristic type="HKLM\Software\Microsoft\Color">
<parm name="SHColor" value="/wAAAAAAAADd3d0A///MAP///wAVvB0AFbwdAMnpywAUpxsA////ABSnGwAUpxsAFKcbABW8HQA0fzgA////AMnpywA30z8AN9M/AP///wAVvB0AFKcbAP///wAVvB0AhITDABW8HQAUpxsA////AP///wAAAAAA////AAAAAAD///8AFbwdAAhKAADe/2MA////AMnpywAUpxsA////ABSnGwA=" datatype="binary"/>
<parm name="BaseHue" value="16400A4" datatype="integer"/>
</characteristic>
<characteristic type="HKLM\System\GWE">
<parm name="SysColor" value="yenLAAAAAAA30z8AjdWRAP///wD///8AAAAAAAx/EgAAAAAA////AAAAmQDAwMAA////ADfTPwD///8AyenLAICAgAC/v78AAAAAAP///wD///8AAAAAAP///wAAAAAA///MAP///wAAAAAAT5r2AMDAwAA=" datatype="binary"/>
</characteristic>
</characteristic>
<characteristic type="FileOperation">
<characteristic type="%CE2%" translation="install">
<characteristic type="stwater.jpg" translation="install">
<characteristic type="Copy">
<parm name="Source" value="%CE2%\stwater_240_320.jpg" translation="install" />
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Just delete the file. You will loose the flat bars on 6.1 tsk.
Enjoy
ok if i delete the file, and make an oem to set whatever.tsk as the theme, will it make it the theme?
edit:: ok i deleted the file. made an oem to make a certain .tsk default, and still isnt working. just makes the today screen have a blue background and blue bars.
so... no luck changing the default theme as it boots up?

[HardSPL] Fast App Unlock Method

Here's a fast method to app unlock your device so that HardSPL will run smoothly and without errors. It uses RapiConfig to edit the registry for you. All modifications made are from here
[HOW TO]​
Download AppUnlock Pack
Run 01 - App Unlock.bat
Reboot WM using Power button
Flash HardSPL
Run 02 - App Relock.bat
[FAQ]​What does this do?
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Security\Policies\Policies" recursive="true">
<parm datatype="integer" value="1" name="0000101b"/>
</characteristic>
</characteristic>
<characteristic type="Registry">
<characteristic type="HKLM\Drivers\BuiltIn\EXT_FLASHDRV" recursive="true">
<parm datatype="string" value="OEM_FLASHDRVXXX.dll" name="Dll"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
App Unlock
Sets HKLM/Security/Policies/Policies/0000101B to dword:1
Sets HKLM/Drivers/BuiltIn/EXT_FLASHDRV/Dll to "OEM_FLASHDRVXXX.dll"
App Relock
Sets back HKLM/Drivers/BuiltIn/EXT_FLASHDRV/Dll to "OEM_FLASHDRV.dll"
Cheers
-
hi, i am having a problem, my filie looks like 0000102B after using appunlock, and when i try to edit that to 0000101B it says Cannot create a file when that file already exists. what to do? please help...
You cannot edit the xml file directly...
Can you paste your RapiConfigOut.xml file contents after using AppUnlock here?
or alternately your RapiConfigOut.xml file contents after using Check Unlock

Developing XPERIA S / T for X10 Mini pro with HW Support!

Hi Im developing a xPeria S Keyboard with hw Support but i have Problems to convert it what i have found are follow ´things
uploaded one developer kit for all that want to help me.
the Rom that the xperia S Keyboard works and we have to fix the layouts only i have uploaded here Achotjan_Semc_Debrand_Engine_v30_Beta_04_U20i.zip
this includes the Keyboard of Achotjan_Semc_Debrand_Engine_v30_Beta_04_U20i -> download here -> http://rapidshare.com/files/1307696133/keyboards.zip
-> it has the properties : - If you install it on minicm 10 it crashes ( xperia process has been finish Or so)-
- you can Setup the xperia s Keyboard if you set another Keyboard as Default...
- you notice it if it will be Switches to be in Hardware mode -> it don't work in minicm10 at the Moment if somone have time you can test it on minicm7 and write nme if it is working there
they are the orgiginal files in it without changes
Semc_Debrand_Engine_6.0.B.0.743_U20i -> http://rapidshare.com/files/1821291341/developer_patchsemc_6.0b.zip​
xperia S Keyboard and Hardware use . im understanding how it works basicalyy but im not a expert in it later i will send you some Information what i find
but what i find is follow:
the xperia mini pro (sk17i) has a similiar structur with the x10mini pro in the things, Keyboard layout, chars and so on. on my xperia s Keyboard there isn't the structure avable so the Keyboard can't use it. i belive the key for sucseess is in the
Folders
/System/Usr/Keyboard-config ------------------------>
/System/USR/Keychars - ------------------------->
/System/USR/Keylayout ------------------------> similiar to minicm7 xperia Keyboard
System/USR/srec
/System/USr/textinput
/System/USR/XT9
Note the files : qwerty.kcm.bin; mimmi_keypad.kcm.bin; or z8d files we can open with hexeditor
so If we can adapt to our x10mini pro we should have an xperia S- Keyboard that the Hardware Keyboard should work with it and we have a update to our minicm7 Keyboard .. I don't know how but if you find a way it is a Milestone in our x10mini pro . hope everyone can help me
Developer_Package_with_xperia_sabithwsupport Note to edit some file you should use Notepad++ and a hexeditor --> i don't have any knowledge about hex files
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i have tryied follow things
http://forum.xda-developers.com/showthread.php?t=2102979
http://forum.xda-developers.com/showthread.php?t=1547404
http://forum.xda-developers.com/showthread.php?p=18569390
http://forum.xda-developers.com/showthread.php?t=1670352
http://forum.xda-developers.com/showthread.php?t=2155803
this are my files with Keyboard of both and fixes
http://forum.xda-developers.com/showthread.php?t=2094572
so what i have found is follow on xperia S i have found a way to be activate the blue key for it. But without ÄÜÖ the rest are avable.
if i have something Change in keychars and keylayout the minicm7 use the left blue key for both.
In one configuration the xperia s try to load the Hardware Driver with sim key and so on but it goes back to the original state. In the Framework Folder i found in one xperia s interessting things suqushashinput.jar ----> (ist a file of our minicm7 too) and uxprexe it is the file of the xperia s Keyboard. i don't know but im belive this are the user Interface of Hardware using of the Keyboard.....
In the Folder Keyboard-config you find 11 files that are similar to minicm7 Keyboard. only the language files are a bit otherwise of the Name in our phone. I believe if we use the rigth files of booth and create it that the xperia s Keyboards loads the minicm7 Interface it should be working or if the xperia s inteface is loading with modified files to our phonen i hope anyone can help me
- apk Manager: apl managere
hi bro
yesterday i tested latest nAa's nightly with latest nAa(jb)04 kernel...hwkey works fine with my keychars but there's one problem
L key seems like works as RETURN key
When I press L key phone comes back to homescreen.
Do you now why? Thanks
yes
Chuck95 said:
hi bro
yesterday i tested latest nAa's nightly with latest nAa(jb)04 kernel...hwkey works fine with my keychars but there's one problem
L key seems like works as RETURN key
When I press L key phone comes back to homescreen.
Do you now why? Thanks
Click to expand...
Click to collapse
It is always a kernel bug you can test it . go to cwm -> advance -> Key test
now you ssee on some keys are two keys
the Problem isn't fixed correctly
R: Developing XPERIA S / T for X10 Mini pro with HW Support!
Thank you very much
Sent from my U20i using xda app-developers app
---------- Post added at 10:29 PM ---------- Previous post was at 10:16 PM ----------
Hiii...I noticed one thing
Before replace keychars when I typed with hw keyboard there were these problems:
-when I type i it shows ''ijj'' and same problem with other buttons but now that i replace keychars there isn't no more this problem so i think that problem with L key is in ROM not in KERNEL because if i fixed it i can fix L key too...I will let you know
Sent from my U20i using xda app-developers app
---------- Post added at 10:32 PM ---------- Previous post was at 10:29 PM ----------
If i fix it you can add my usr folder in your new project
Sent from my U20i using xda app-developers app
Nice work, released that
Hi i tested rom changing usr folder...I replaced it with older but problem is still there so we have to wait a new kernel
It would be nice if this would work :good:
Achotjan gave up to try and make it work in Semc Debrand Engine.
There is a lot of discussion about the XPERIA S HW-keyboard-problem in that thread, also alot of good sugestions and info. It's a long thread, but worth looking throug for some inspiration :silly:
Also the sk17i-HW-keyboard got more keys (extra row to the right) than U20i-HW-keyboard. This gave alot of headache for us all, LOL
Emperor.dk said:
It would be nice if this would work :good:
Achotjan gave up to try and make it work in Semc Debrand Engine.
There is a lot of discussion about the XPERIA S HW-keyboard-problem in that thread, also alot of good sugestions and info. It's a long thread, but worth looking throug for some inspiration :silly:
Also the sk17i-HW-keyboard got more keys (extra row to the right) than U20i-HW-keyboard. This gave alot of headache for us all, LOL
Click to expand...
Click to collapse
im knowing up that in one configuration i have a similar Hardware layout configuration of minicm7 Keyboard if im using Default Input and in xperia s i have the qwertz ofthe config of minicm7 nbut without sym key and later i have a configuration with working blue keys without symkey and qwerz but with no function it on the minicm7 arg
allesand said:
im knowing up that in one configuration i have a similar Hardware layout configuration of minicm7 Keyboard if im using Default Input and in xperia s i have the qwertz ofthe config of minicm7 nbut without sym key and later i have a configuration with working blue keys without symkey and qwerz but with no function it on the minicm7 arg
Click to expand...
Click to collapse
this is my configuraton, working fine for me, hard keys and blue keys (Achotjan rom)
HTML:
<?xml version="1.0" encoding="utf-8"?>
<Keyboard xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../scancode_mapping.xsd">
<!-- First row -->
<Row>
<MappingKey scancode="16" id="C1.1" />
<MappingKey scancode="17" id="C1.2" />
<MappingKey scancode="18" id="C1.3" />
<MappingKey scancode="19" id="C1.4" />
<MappingKey scancode="20" id="C1.5" />
<MappingKey scancode="21" id="C1.6" />
<MappingKey scancode="22" id="C1.7" />
<MappingKey scancode="23" id="C1.8" />
<MappingKey scancode="24" id="C1.9" />
<MappingKey scancode="25" id="C1.10" />
<MappingMetaKey scancode="14" id="META_DELETE" />
</Row>
<!-- Second row -->
<Row>
<MappingKey scancode="30" id="C2.1" />
<MappingKey scancode="31" id="C2.2" />
<MappingKey scancode="32" id="C2.3" />
<MappingKey scancode="33" id="C2.4" />
<MappingKey scancode="34" id="C2.5" />
<MappingKey scancode="35" id="C2.6" />
<MappingKey scancode="36" id="C2.7" />
<MappingKey scancode="37" id="C2.8" />
<MappingKey scancode="38" id="C2.9" />
<MappingKey scancode="40" id="C2.10" />
<MappingMetaKey scancode="28" id="META_ENTER" />
</Row>
<!-- Third row -->
<Row>
<MappingMetaKey scancode="42" id="META_SHIFT_LEFT" />
<MappingKey scancode="44" id="C3.1" />
<MappingKey scancode="45" id="C3.2" />
<MappingKey scancode="46" id="C3.3" />
<MappingKey scancode="47" id="C3.4" />
<MappingKey scancode="48" id="C3.5" />
<MappingKey scancode="49" id="C3.6" />
<MappingKey scancode="50" id="C3.7" />
<MappingKey scancode="214" id="C3.8" />
<MappingMetaKey scancode="103" id="META_DPAD_UP" />
<MappingMetaKey scancode="368" id="META_LANGUAGE" />
</Row>
<!-- Fourth row -->
<Row>
<MappingMetaKey scancode="56" id="META_ALT_LEFT" />
<MappingMetaKey scancode="216" id="META_SYMBOL" />
<MappingKey scancode="26" id="C4.1" />
<MappingKey scancode="51" id="C4.2" />
<MappingMetaKey scancode="57" id="META_SPACE" />
<MappingKey scancode="52" id="C4.4" />
<MappingMetaKey scancode="105" id="META_DPAD_LEFT" />
<MappingMetaKey scancode="108" id="META_DPAD_DOWN" />
<MappingMetaKey scancode="106" id="META_DPAD_RIGHT" />
</Row>
<!-- Back key -->
<Row>
<MappingMetaKey scancode="158" id="META_BACK" />
</Row>
</Keyboard>
chilakil said:
this is my configuraton, working fine for me, hard keys and blue keys (Achotjan rom)
HTML:
<?xml version="1.0" encoding="utf-8"?>
<Keyboard xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../scancode_mapping.xsd">
<!-- First row -->
<Row>
<MappingKey scancode="16" id="C1.1" />
<MappingKey scancode="17" id="C1.2" />
<MappingKey scancode="18" id="C1.3" />
<MappingKey scancode="19" id="C1.4" />
<MappingKey scancode="20" id="C1.5" />
<MappingKey scancode="21" id="C1.6" />
<MappingKey scancode="22" id="C1.7" />
<MappingKey scancode="23" id="C1.8" />
<MappingKey scancode="24" id="C1.9" />
<MappingKey scancode="25" id="C1.10" />
<MappingMetaKey scancode="14" id="META_DELETE" />
</Row>
<!-- Second row -->
<Row>
<MappingKey scancode="30" id="C2.1" />
<MappingKey scancode="31" id="C2.2" />
<MappingKey scancode="32" id="C2.3" />
<MappingKey scancode="33" id="C2.4" />
<MappingKey scancode="34" id="C2.5" />
<MappingKey scancode="35" id="C2.6" />
<MappingKey scancode="36" id="C2.7" />
<MappingKey scancode="37" id="C2.8" />
<MappingKey scancode="38" id="C2.9" />
<MappingKey scancode="40" id="C2.10" />
<MappingMetaKey scancode="28" id="META_ENTER" />
</Row>
<!-- Third row -->
<Row>
<MappingMetaKey scancode="42" id="META_SHIFT_LEFT" />
<MappingKey scancode="44" id="C3.1" />
<MappingKey scancode="45" id="C3.2" />
<MappingKey scancode="46" id="C3.3" />
<MappingKey scancode="47" id="C3.4" />
<MappingKey scancode="48" id="C3.5" />
<MappingKey scancode="49" id="C3.6" />
<MappingKey scancode="50" id="C3.7" />
<MappingKey scancode="214" id="C3.8" />
<MappingMetaKey scancode="103" id="META_DPAD_UP" />
<MappingMetaKey scancode="368" id="META_LANGUAGE" />
</Row>
<!-- Fourth row -->
<Row>
<MappingMetaKey scancode="56" id="META_ALT_LEFT" />
<MappingMetaKey scancode="216" id="META_SYMBOL" />
<MappingKey scancode="26" id="C4.1" />
<MappingKey scancode="51" id="C4.2" />
<MappingMetaKey scancode="57" id="META_SPACE" />
<MappingKey scancode="52" id="C4.4" />
<MappingMetaKey scancode="105" id="META_DPAD_LEFT" />
<MappingMetaKey scancode="108" id="META_DPAD_DOWN" />
<MappingMetaKey scancode="106" id="META_DPAD_RIGHT" />
</Row>
<!-- Back key -->
<Row>
<MappingMetaKey scancode="158" id="META_BACK" />
</Row>
</Keyboard>
Click to expand...
Click to collapse
nice in whitch of the files i can find it?
chilakil said:
this is my configuraton, working fine for me, hard keys and blue keys (Achotjan rom)
HTML:
...
<MappingMetaKey scancode="57" id="META_SPACE" />
...
Click to expand...
Click to collapse
I see you have only one MetaKey for space. Do you get a "space" pressing both edges of the key?
Doing a key-test in CWM returns two scancodes for right and left edge.
See post # 405 (at the buttom of the post i list all the scankeys) on this page: http://forum.xda-developers.com/showthread.php?t=1504637&page=41
allesand said:
nice in whitch of the files i can find it?
Click to expand...
Click to collapse
system/usr/keyboard-config/scancode_mapping,xml
---------- Post added at 10:37 AM ---------- Previous post was at 09:51 AM ----------
Emperor.dk said:
I see you have only one MetaKey for space. Do you get a "space" pressing both edges of the key?
Doing a key-test in CWM returns two scancodes for right and left edge.
See post # 405 (at the buttom of the post i list all the scankeys) on this page: http://forum.xda-developers.com/showthread.php?t=1504637&page=41
Click to expand...
Click to collapse
Extra key is not necessary because the navigation keys are functional (right to left), but you not will get extra space by pressing the navigation key to the right if that's what you mean.
Emperor.dk said:
I see you have only one MetaKey for space. Do you get a "space" pressing both edges of the key?
Doing a key-test in CWM returns two scancodes for right and left edge.
See post # 405 (at the buttom of the post i list all the scankeys) on this page: http://forum.xda-developers.com/showthread.php?t=1504637&page=41
Click to expand...
Click to collapse
ok so what do you mean it wit one MetaKey for space?
i don't understand it
allesand said:
ok so what do you mean it wit one MetaKey for space?
i don't understand it
Click to expand...
Click to collapse
the space-bar got two buttons. One under B and one under M.
they could actually be maped into two different functions like space for the one under B and TAB for the one under M. I always wondered why we didn't had a TAB key. i will try to make it for the learning experience.
but read in the thread i linked to get some idears to make XPERIA S keyboard work on our mimmi
Emperor.dk said:
the space-bar got two buttons. One under B and one under M.
they could actually be maped into two different functions like space for the one under B and TAB for the one under M. I always wondered why we didn't had a TAB key. i will try to make it for the learning experience.
but read in the thread i linked to get some idears to make XPERIA S keyboard work on our mimmi
Click to expand...
Click to collapse
http://forum.xda-developers.com/show...504637&page=41 you mean this thread
allesand said:
http://forum.xda-developers.com/show...504637&page=41 you mean this thread
Click to expand...
Click to collapse
Yes
http://forum.xda-developers.com/showthread.php?t=1504637&page=41
i tried follow
Emperor.dk said:
Yes
http://forum.xda-developers.com/showthread.php?t=1504637&page=41
Click to expand...
Click to collapse
im downloading the Rom of azopikolo or what his Name is copy the Keyboard files Change the configure files and make a new developer kit . so im testing it if im think this is great i will update the files to newer one . so i m hope this is the rigth way to make a keyfix for our phone so we should have an xperia s Keyboard with working keys or isn't it so ..?
so there are many Versions of it. Which Rom was the best Rom to can make the fix ? there are many Versions of Semc Debrand Engine | 3.0_Final | FreeXperia Project | 6.0.B.0.743 | RELEASED !
should work
have tested old Rom quickly i see that this has to work on our phone
im testing the old Rom of achioat or so
i have founding an bug that has some Versions of the android Systems of nAas on 3.05 and 4.0 that nAa has been fixed with the symkey
so im think we Need this files of the old Rom and has it to update it and then we Need a System like it is existing for xperia s or the System works to don't know but im thinnking this are good news
the existing Keyboard layout zip files or integratet in my fix should be work soon with xperia S HW
tested with minicm7rom of a_
allesand said:
the existing Keyboard layout zip files or integratet in my fix should be work soon with xperia S HW
tested with minicm7rom of a_
Click to expand...
Click to collapse
I told you I've been using for several months without problems :good:

[Q] iGo Primo & Loquendo TTS for Android

Hello,
There are way too many versions of iGo all over the internet and I have tried several ones. It looks like iGo folder structure is shared across many platforms and the .apk for Android is the one that manages its interactions with the OS.
I managed to get iGo and LoquendoTTS (v7, I guess) installed on my phone and they both seems to work fine, except for one problem. Whatever language/voice I select inside iGo has no effect to the TextToSpeach engine. In other words, it will ALWAYS get the system default language/voice. Why is that?
Let me be more specific: I want my phone language to be set to English, but I need iGo use the TTS engine in Brazilian Portuguese. If I set phone language to English, then I enter iGo and choose a Portuguese voice, the TTS sound will be spoken in Portuguese words, but with English pronounciation and voice. On the other hand, if I choose Portuguese in Android's settings then Portuguese in iGo, everything is spoken in Portuguese.
It seems to be an iGo problem, not Android's. Every other app I have that uses TTS will allow me to select the language/voice to be used, except for iGo.
I found out a few things:
1) Loquendo installs its language/voice settings to its default folder (usually /sdcard/LoquendoTTS/) and here is an example:
Portuguese.ttsconf
(Loquendo TTS Language - Brazilian Portuguese)
<?xml version="1.0" encoding="UTF-8"?>
<config>
<languages>
<language name="PortugueseBr" basename="Portuguese" defaultvariant="no">
<library name="LTTS7${basename}" entrypoint="${name}" />
<info description="${basename}" />
<resources path="modules/${basename}">
<resource class="base" type="lexicalinfo" name="${name}" />
<resource class="base" type="lexicon" name="${name}" />
</resources>
<languagealiases>
<alias type="internal" name="${name}" />
<alias type="IETF" name="pt-BR" />
<alias type="WinLangid" name="1046" />
<alias type="generic" name="BR" />
<alias type="generic" name="Brazilian" />
<alias type="generic" name="pt" />
</languagealiases>
<modes>
<mode name="default">
<parameters />
<resources>
<remove class="" type="" name="" />
<add class="base" type="" name="" />
</resources>
</mode>
</modes>
</language>
</languages>
</config>
Click to expand...
Click to collapse
Gabriela.ttsconf
(Loquendo TTS VOICE configuration: Gabriela - Brazilian Portuguese)
<?xml version="1.0" encoding="UTF-8"?>
<config>
<voices>
<voice name="Gabriela" mothertongue="PortugueseBr">
<library name="LTTS7${name}" entrypoint="${name}" />
<info description="Brazilian female voice" age="35" gender="female" demosentence="Meu nome é Gabriela: sou uma voz feminina de Loquendo, e a minha língua nativa é o português do Brasil." basepitch="180" basespeed="128" />
<resources path="modules/${name}">
<resource class="base" type="vocaldb" name="${name}">
<flavour codec="LTTS7CodecMsx" frequency="16000" bitrate="32800" rank="10" name="${parent.name}.${this.frequency}.${this.codec}.${this.bitrate}.${this.rank}.bin" />
</resource>
<resource class="gilded" type="vocaldb" name="${name}GildedPhrases">
<flavour codec="LTTS7CodecMsx" frequency="16000" bitrate="32800" rank="10" name="${parent.name}.${this.frequency}.${this.codec}.${this.bitrate}.${this.rank}.bin" />
</resource>
<resource class="gilded" type="vocaldb" name="${name}GildedParalinguistics">
<flavour codec="LTTS7CodecMsx" frequency="16000" bitrate="32800" rank="10" name="${parent.name}.${this.frequency}.${this.codec}.${this.bitrate}.${this.rank}.bin" />
</resource>
</resources>
<modes>
<mode name="default">
<parameters />
<resources>
<remove class="" type="" name="" />
<add class="base" type="" name="" />
<add class="gilded" type="" name="" />
</resources>
</mode>
</modes>
<languagealiases>
<alias type="internal" name="${mothertongue}" />
<alias type="IETF" name="pt-BR" />
<alias type="WinLangid" name="1046" />
<alias type="generic" name="BR" />
<alias type="generic" name="Brazilian" />
<alias type="generic" name="pt" />
</languagealiases>
</voice>
</voices>
</config>
Click to expand...
Click to collapse
2) iGo Voice files is specific for each language and is a .zip file containing some dictionaries, icons and also an info file like this:
info.ini
(iGo Brazilian Portuguese Voice)
[INFO]
;TTS Loquendo Lua Pro
LCID=0x0416
ask_recalulate="Fora da rota. Recalcular?"
asr_language="pt-br"
brand="Standard"
cmlangkey="Voice_Portuguese-br"
;dynamiccompressor=1
entering_tunnel="Você está entrando num túnel!"
flag="flag_bra.bmp"
flag_icon="countryflag_bra"
gps_disconnect="O GPS foi desconectado"
gps_signal_lost="Perda do sinal de Satélite"
languagekey="Portuguese"
languagename="Portuguese"
lang_extention_flag=""
luavoice=1
name="Gabriela (TTS) v2.9"
offroute="Fora da rota"
overspeed="Você está acima do limite de velocidade"
phoneme_lang="POR"
recalulate="Novo cálculo da rota"
;roadnameparsing=0
sex="female"
testsound="Olá, meu nome é Gabriela, tenha uma boa viagem, e dirija com cuidado!"
timestamp="1262873210"
timestamp_readable="2010_01_07__15_06_50"
tmcsup=1
tts_destnames=1
tts_engine="loquendo"
tts_eta="Você chegará ao destino aas \number=time %H e %M"
tts_langname="PortugueseBr"
;tts_langname_loq7="PortugueseBr"
tts_mode_mixed=0
tts_rate=50
tts_srate="11025"
tts_voicename="Gabriela"
;tts_voicename_loq7="Gabriela"
ttsvoice=1
traffic_jam="Há um congestionamento logo adiante!"
unitssup_kmm=1
unitssup_mlf=1
unitssup_mly=1
version=1
voicekey="Gabriela"
Click to expand...
Click to collapse
As you can see, iGo voice file has redundant settings to tell the system which language/voice to use.
The thing is: I tried a lot of combinations to these settings, but none got to work. I wonder why.
My only guess was to assume that these settings are specific iGo For WinCE, not for Android. As for I've heard WinCE comes with a loq_tts subfolder with some .dll and .exe files to make the LoquendoTTS engine to work.
Is anyone capable of giving me some directions on this? I am totally lost.
Thanks in advance.

[Q] Open local KML file in Google Maps in offline mode

Hello all,
i just registered here to find out if opening a KML file on my SD card with Google maps in offline mode can work.
I am looking for an solution quite a time, but only found this thread on stackover...
To load kml into Google Maps on Android without writing an app, you can create a little html file somewhere with a geo-uri link to the kml file and then click on that link in any Android web browser.
For example: suppose your kml file is located in /sdcard/overlay.kml then you write a geo-uri link like this:
<html>
<head><title>Example KML link page using a geo-uri</title></head>
<body>
overlay.kml
</body>
</html>
Click to expand...
Click to collapse
Clicking on the link will launch Maps and then Maps will attempt to load and your kml.
Be warned however that the Android version of Maps does not appear to handle the same version/range of kml elements as the desktop version (or desktop Google Earth).
Click to expand...
Click to collapse
a other thread is about editing the manifest file to get maps to open local KML files
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="h**p://schemas.android.com/apk/res/android"
package="com.example.lyold"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="15"
android:targetSdkVersion="16" />
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.VIBRATE"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.CAMERA" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="com.example.lyold.LoginActivity"
android:screenOrientation="landscape"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity
android:screenOrientation="landscape"
android:name=".Home" />
<activity android:name="com.google.earth.EarthActivity" android:screenOrientation="landscape"/>
</application>
</manifest>
Click to expand...
Click to collapse
Don't know if this is already outdated solution or not, i just cant get it to work.
Does anybody know a way to open local KML files with google maps in offline mode ?
ThX in advance !
PS: i want to open kml ONLY in google maps, i know there are several apps out there that support kml files....
hello again,
before i start trying to finf out how to edit the manifest file.
I wanted to ask if adding the line
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
Click to expand...
Click to collapse
could help me out here ?
ThX,
SA
Please Help !
Hello world !
Does someone know if editing the manifest file could solve the problem that google maps won't open KML file which are on the phones SD-card.
If not, i can give up to find an option..
ThX,
SA

Categories

Resources