Database Users

Boot Image

how can I change the boot image in the XDA????????????

changing bootimage
Using mkrom you can put an image into the "cfg" directory called bootimage.bmp. That image should have the next properties:
- 16 bit
- 240 x 320 pixels
and the next options (only avaliables in Photoshop 7):
-R5-G6-B5
-Flip row order
I remenber the last 2 options appear as an option for saving the image.
As you use Flip row order you should Flip vertial the image in Photoshop in order to have a top to botton image.
Then make the rom with mkrom, and that's it.

2003SE Bootsplash

Hey guys, I've been playing around with 2003SE trying to figure out how to change the bootsplash, and this is what I've found so far.
I executed the following command:
Code:
pmemdump.exe 0x80000000 0x2000000 rom.raw
This should have dumped the entire ROM, as documented here:
http://www.xs4all.nl/~itsme/projects/xda/wince-rom-layout.html
I then opened the file rom.raw using IrfanView with the following options:
Image Width=240, Image height=70000, Header size=0, 16 BPP, NO Vertical flip.
And I was able to see an image that resembled the bootsplash near the top, but it was distorted. However, about a quarter of the way down I see the "Welcome to T-Mobile" logo in 320x240 perfectly.
It looks like the distorted bootsplash image is repeated twice when I open it in this format, so I tried opening the file with a width of 120 pixels, but it was still distorted. I've tried opening the raw file with all of the combinations I can think of, but none show the bootsplash clearly.
Any ideas of how we can determine it's starting byte position and format?

WM2003SE Bootsplash Address and Format Found
The bootsplash for the available WM2003SE rom is stored at 0x800417e0, and is only 76800 bytes long. Extract it from the rom using the following command:
Code:
pmemdump 0x800417e0 76800 bootsplash.raw
Open it as a 320x240 raw file with 8 bits per pixel (grayscale?) no header.
I have attached the bootsplash.raw file below, but had to change extension to .txt for uploading.
I'm unable to write a new bootsplash since pnewbmp doesn't support this offset, and pnewbootloader has other complaints using this offset.
There may be some color information in the 8 bits per pixel.
What we need now:
1.) Someone that knows more about graphic formats to investigate if the bootsplash has color information.
2.) A modified version of the pnewbmp.exe file from http://www.xs4all.nl/~itsme/projects/xda/tools.html that supports the new offset. (Ideally, modify it so it can be used for any offset).
Shawn

Are u sure?
old files had been twice big (153600 Byte)
Have you tried this size?
You shoud be able to run
Code:
pnewbmp -o 0x800417e0 filename
The file you've upladed doesn't look complete.....
Stefan

The T-Mobile ROm you´ve found is added by the kitchen.
Until now it´s not possible to cook a ROM without the splashscreen. So it´s added at the 0x80780000 position.
Has nothing to do with the real splash screen....
Stefan

Fairly Certain
old files had been twice big (153600 Byte)
Click to expand...
Click to collapse
Stefan,
You're absolutely right, it is definitely different than previous bootsplash formats. If I'm right, it's half the size because it uses 8 bits per pixel instead of 16 bits per pixel, as before. I believe that means it must use a standard 256 color table. We just need to know which standardized color table it uses (Windows System?), and find graphics software that will open bitmaps without headers.
Have you tried this size?
Click to expand...
Click to collapse
I've tried dumping the old file size, but it is just garbage after 76800 bytes. Perhaps they switched to this format to save memory.
The T-Mobile ROm you´ve found is added by the kitchen.
Click to expand...
Click to collapse
That's good to know. I thought that was the real bootsplash, and there was some switch in the code for this version of the ROM to point the bootsplash image to a temporary image that we are seeing. Let me illustrate with code:
Code:
Internal_Rom = True;
...
If (Internal_Rom==True)
Bootsplash_start_byte=0x800417e0;
else
Bootsplash_start_byte=0x80780000;
But since that's not the case, we don't need to worry about tracking down that switch.
I've tried using pnewbmp with the offset option, but I'm getting an error reading the bitmap. I've tried appending the original ROM data after my custom bootsplash (when necessary) to create files of sizes 76800, 151672, and 153600, but I still received the error so I don't think it is a problem with the file size, but it may not recognize the format. (pnewbmp appears to be trying to read the size 0x25800=153600, so that file size should have worked if it were a file size issue)
So, here's a theory of how to make a bootsplash for this new ROM format:
1. Create your image in RGB 320x240.
2. Change Image Mode to 8 bits/channel, and Indexed Color using the Palette "System (Windows)" (?).
3. Save your file in RAW format (Uncheck Alpha Channels), 0 Header
Resulting File Size=76800.
Now I just need to test this theory using a program that will allow me to write an arbitrary number of bytes to an arbitrary byte offset in the ROM.
Shawn

It works!
I'm getting ready to sell my Wallaby (replaced with PPC-6700), so I gave my (old) theory a try, and it worked!
I executed the following commands:
Code:
pmemdump.exe 0x80000000 0x417e0 one.raw
pmemdump.exe 0x800543E0 0x1FABC20 three.raw
I opened one.raw, three.raw, my new bootsplash raw image (described above), and an example NK.nbf file in a hex editor (PSPad). I appended the first two lines from NK.nbf to one.raw. They look like this:
PW10B1-ENG-3.16-000-aa9a--------
Click to expand...
Click to collapse
I then appended my new bootsplash image to the end of one.raw, then appended three.raw to the end of one.raw. I then saved this file as NK.nbf and replaced the default NK.nbf for the installer built at LumpiStefan's site.
When I ran the installer, it complained that aa9a wasn't the correct checksum, but it went through anyway, and works fine. The only problem is I can't control colors, since I don't know what color pallet it uses. The closest match is Mac OS. Until that gets figured out, it's best to just use a black & white image.

The ultimate Pocket PC hacking + Asus MYPAL A620BT thread

The ultimate ( Asus MYPAL A620BT ) Pocket PC thread
World Wide English Windows Mobile 2003 / PocketPC 2003
{
"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"
}
German Windows Mobile 2003 / PocketPC 2003
(Screenshoots, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
1. Introduction
2. Attemps getting a A620BT ROM image
3. Hacking/modifying the ROM image
4. A620BT Combo Buttons
5. Screenshots - how did I built them?
6. Problems/questions
1.) Introduction
Hi.
Short time ago I bought the Asus MYPAL A620BT Pocket PC / PDA.
It is a great PDA bundled with the superb "Destinator" navigation software.
Well, I like it to modify embedded software & firmware (especially BIOS files),
as you can see here:
The BNOBTC homepage
So I started to do some reverse-enginering with the A620BT.
2.) Attemps getting a A620BT ROM image
So, logically, I looked for a method how to dump / get the ROM file,
before I could start modifying the Asus MYPAL A620BT ROM itself.
I could not find anything, even the Asus support homepage did not help any further.
But with the help of google.com I could find other interesting stuff:
3.) Hacking/modifying the ROM image
Asus' FTP Server for "special" PDA related files:
"ftp4.asus.com.tw"
UN: PDAUser
PW: pda9983!
( Tip: When I was writing this article the UN:ftp01tk* and PW:vtf2g6z* seemed to be outdated and did/do not work anymore.)
*= can also be found by google.com
Here:
ftp4.asus.com.tw/PDA/AD620BT/ROMImage/PPC2003
I was able to find English, German, etc..., ROM update files.
Inside the zip archives (e.g.: "SW-A4H01WA-007_09931WWE.ZIP") you can find following files:
+ AD620N.nb0
+ BOOT620N.nb0
+ IPL620N.nb0
+ .doc / .txt / readme file
3.1.) AD620N.nb0
It contains the Pocket PC operating system (Windows Mobile 2003 [a.k.a PocketPC 2003])
and the PocketPC Diagnostic Program
(Screenshoots, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
The eight symbolic characters, which are shown on the upper-left and upper-right corner inside the
PocketPC Diagnostic Program can also be found in the "AD620N.nb0" file.
Here is the list with offsets, data and images of/from the symbolic chars:
symbolic character 1 @ 0x0000A400:
00001010FFFE101000007FFC01001110FFFE111001007FFC01003FF801000100
symbolic character 2 @ 0x0000A420:
00007DFE1010102021FE21024102FDFE4502450245FE4502450245FE7C480084
symbolic character 3 @ 0x0000A440:
00003FF80100FFFE8102BD7A8102BD7A00003FF821083FF821083FF8010201FE
symbolic character 4 @ 0x0000A460:
00007C924492452446487D244492449244407DFE4586454A4532454A45868DFE
symbolic character 5 @ 0x0000A480:
000020202020202023FCF82020202BFC310420886050A02020502088A1046202
symbolic character 6 @ 0x0000A4A0:
000003FE00480048FC48084811FE20484048BC482448244824483C8801080208
symbolic character 7 @ 0x0000A4C0:
000001000100010001007FFC41044104410441047FFC01000100010001000100
symbolic character 8 @ 0x0000A4E0:
00000000020001801100510851045006D00290021008100810080FF000000000
There is also another method to get the symbolic characters:
The ROM update file contains a kind of a file system which can be viewed with the really great utility:
=+ DUMPROM += by Willem Jan Hengeveld ( The XDA Developers homepage ).
With DUMPROM I could extract all files and "nk.exe" is the actual/proper/real file
which contains the PocketPC Diagnostic Program / AD620 Test Program.
Because of the "nk.exe" does not begin at offset 0x00 inside the "AD620N.nb0" file,
the real adresses are following:
symbolic character 1 @ 0x00009800.
symbolic character 2 @ 0x00009820.
symbolic character 3 @ 0x00009840.
symbolic character 4 @ 0x00009860.
symbolic character 5 @ 0x00009880.
symbolic character 6 @ 0x000098A0.
symbolic character 7 @ 0x000098C0.
symbolic character 8 @ 0x000098E0.
To view / see the symbolic characters, you just need to convert the hex data into binary (0,1) strings.
For example let us convert the data of the first symbolic character into a viewable symbolic character:
0000 1010 FFFE 1010 0000 7FFC 0100 1110 FFFE 1110 0100 7FFC 0100 3FF8 0100 0100
==>
Code:
HEX |Binary
------+--------
00 00 |00000000 00000000
10 10 |00010000 00010000
FF FE |11111111 11111110
10 10 |00010000 00010000
00 00 |00000000 00000000
7F FC |01111111 11111100
01 00 |00000001 00000000
11 00 |00010001 00010000
FF FE |11111111 11111110
11 10 |00010001 00010000
01 00 |00000001 00000000
7F FC |01111111 11111100
01 00 |00000001 00000000
3F F8 |00111111 11111000
01 00 |00000001 00000000
01 00 |00000001 00000000
Now, let us convert all "0" to "." and "1" to "X" to get a better view:
Code:
................
...X.......X....
XXXXXXXXXXXXXXX.
...X.......X....
................
.XXXXXXXXXXXXX..
.......X........
...X...X...X....
XXXXXXXXXXXXXXX.
...X...X...X....
.......X........
.XXXXXXXXXXXXX..
.......X........
..XXXXXXXXXXX...
.......X........
.......X........
Then, with a drawing program / utility,
each "X" will be drawn as a colored pixel and each "." will not be painted.
Finally, you reached to convert a binary character into a bitmap and you can see the first symbolic character:
(Screenshoot, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
(Now you are able to modify the upper-left and upper-right corner of the diagnostic screen inside the "nk.exe" )
(The background color green was just used for easier image processing.)
The PocketPC Diagnostic Program ( AD620N Test Program ) also contains a nice
Key/Button Test
title scren --> testing the buttons
-->
(Screenshots / animations, PNG / gif conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
3.2.) BOOT620N.nb0
This file contains the bootloader and a built-in flash utiliy which can be accessed by/with special Combo Buttons in section "4"
Furthermore it contains the splash logo which is shown after a reset / after "booting" the Asus MYPAL A620BT PDA.
Here is a photo, which I made:
(Photo by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net)
However, I am not able to rip and display the logo in a decent way.
If you open the BOOT620N.nb0 file in a HEX editor and if you jump to offset:
0x00001E45 (or: 0x00001E47, if the 0D0A string does not belong to the image data),
then you can see the beginning of the image data.
It seems to be any kind of a palette area.
The real / plain image data seems to begin @ offset: 0x00001F98 and seems to end @ offset: 0x00027798.
That means 25800 Bytes [Hex] = 153600 Bytes.
After extracting the area ( after extracting the mentioned 153600 Bytes ) and pasting the data to a new (.RAW) file,
you can open the file in programs which are able to import/open raw files, such as:
"Irfanview".
( http://www.irfanview.com )
In Irfanview choose "RAW - RAW Image Data" as file type when you open the new built .RAW file.
After selecting and opening the file, a new window appears, where you can enter the dimensions and select the bits per pixel.
Take: 240 * 320 * 16bit.
This was my first attempt.
(The RAW image file began with one byte too much. )
(I did not copy and paste the area: 0x00001F98 - 0x00027798. I copied 0x00001F97 - 0x00027798. )
(Screenshoot, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
This was my final attempt:
(This time, the area: 0x00001F98 - 0x00027798 inside the BOOT620N.nb0 was copied and pasted to a new raw file exactly.)
(Screenshoot, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
The logo seems to be have a color depth of 16 bit (2bytes per pixel) + a kind of a palette??????!????
Well, as you can see, I am currently not able to display the image correctly.
So, there are questions.
Please goto section 6.
3.3.) IPL620N.nb0
? ? ?
So, logically, there are questions.
Please goto section 6.
3.4.) .doc / .txt / readme file
The file contains helpfull information and detailed instruction for a ROM Image Update.
It also describes the special Combo Buttons.
4.) Special Combo Buttons
1. Power button + Reset Button --> Cold Boot
2. Record button + Reset Button --> ROM Image Update (Immediately Update AD620N.nb0)
3. AP1 button + Reset button --> Eboot Mode
4. AP2 button + Reset button --> ROM Image Update (Need User Input File Name)
5. AP3 button + Reset button --> Diagnostic Program
6. Power button + AP4 button --> Calibration for Touch Screen
There are further questions.
Please goto section 6.
5.) Screenshots - how did I built them?
Here are some programs which are able to control Pocket PC systems via PC (Netmeeting-like)
and which can be used to build screenshots as long as the Pocket PC is not in FlashROM mode or inside the Diagnostic Program.
+ ActiveSync Remote Display ( part of Windows Mobile Developer Power Toys)
( free download: http://www.microsoft.com/downloads/...d6-1dcc-47aa-ab28-6a2b006edfe9&displaylang=en )
( http://download.microsoft.com/downl...-83a0-81d7d9ac9ce1/WindowsMobilePowerToys.msi )
+ dotPocket (commercial software)
( http://www.dotpocket.com/pocket-pc-software.html )
+ Pocket Controller (commercial software)
( http://www.soti.net/ )
Because there are no(**) lossless methods to grab the screen while the PDA is in Diagnostic - or in FlashROM mode,
and because there are no screen dumping utilities which would work in the mentioned states/modes,
I looked for alternatives and I found some.
With the help of my Plustek USB scanner I could take some really huge and detailed scans from my Asus MYPAL A620BT.
The images were scanned with 1200 DPI, so I was able to:
+ see each dot/pixel/transistor on the touchscreen/TFT
+ re-draw each character and symbol and store each of them in a single graphics file.
With the help of HTML I could rebuild the different screens in a pixel accurate way.
So, I did a huge amount of reverse engineering to get decent screenshots instead stupid and bad photos.
( **= Theoretical, I could open the PDA and grab the digital video / display data from the
TFT / touchscreen pins. )
There are further questions.
Please goto section 6.
6.) Problems, troubles & questions.
Reffering to: 3.) Hacking/modifying the ROM image & 3.3.) IPL620N.nb0:
What are the files: "BOOT620N.nb0" "IPL620N.nb0" detailed for?
How to dump the bootloader area from a Pocket PC to a file?
Reffering to: 3.2) BOOT620N.nb0,
I would like to know:
"How to rip and modify the splash logo in a accurate way?"
"Did I forget something to do?"
Reffering to: 3.4.) .doc / .txt / readme file,
are there further Combo Buttons?
Reffering to: 5.) Screenshots - how did I built them?:
I already tried find the binary data for the displayed font /characters,
when the Asus MYPAL A620BT is in Diagnostic - or in FlashROM mode.
So, I tried to find the binary data for many re-painted chars in the three .nb0 files and extracted files.
For example, I also looked for the binary data of the character: A [ 3078CCCCFCCCCC ]
Code:
HEX|Binary
---+--------
30 |00110000 ..XX....
78 |01111000 .XXXX...
CC |11001100 XX..XX..
CC |11001100 ==> XX..XX..
FC |11111100 ==> XXXXXX..
CC |11001100 XX..XX..
CC |11001100 XX..XX..
However, no files seems to contain the "console font".
In the PC area, the VGABIOS contains the (8*8, 8*16,...) charsets/fonts,
which are "encoded" in the same binary way.
Is there any kind of "VGABIOS" inside the Pocket PC?
(WinRAR and TotalCommander are able to search HEX strings inside files.)
Where is the standard/console font stored (in)?
Is it also stored in one of the .nb0 files?
Reffering to 2.) Attemps getting a A620BT ROM image:
After a second search with http://www.google.com,
I could find two methods to dumping the rom, but both methods do not really work.
a)
The OSImage Tool ( http://www.xs4all.nl/~itsme/projects/xda/OsImageTool.html ) seems to work,
but after ~ 1.5 - 1.7MB nothing happens anymore.
No crash, ...etc., the dumping process just stops and nothing happens anymore.
I tried the OSImage Tool many time and I also removed/closed all applications from the memory.
(Pocket PC->settings->memory)
But everytime I try to dump,
the OSImage Tool stops after ~ 1.5 - 1.7MB.
The dumped part seems to be ok. (There are no weird chars inside the 1.5MB dumped part.)
However, it is just a part - not the whole dump.
In this forum I could find another person, who described the same problem in another thread:
http://forum.xda-developers.com/viewtopic.php?p=34550#34550
I did not try the "bootblaster" yet.
But, I think it is important that the current OSImage Tool will also be improoved.
b)
grab_it ( http://forum.xda-developers.com/viewtopic.php?t=22861 ) brings a stupid error message:
(Screenshoots, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
The autostart feature worked and I also tried to start the grab_it manually, but everytime I get the error message:
Cannot create file

I think this will work
grab_it by default trys to write dump.bin file to "/Storage Card" folder since you have "/Speicherkarte" instead it ends with error message try attached file with modiffyed grab_it to work with your asus.

How to restore ROM
Is it possible to restore the original ROM as my PDA doesn't boot (I believe it lost the ROM image).

latest rom for A620BT GER
hi everybody,
i know it's an old post and i'm very unhappy to get it outside the recycle bin but i really need ur help.
IS THERE SOMEBODY WHO HAD THE LATEST ROM v0.99.31 or so in german language for Asus MyPal A620BT? I really need it.
Thanks to the one who can share it with me.
gReeTs
cYBERdEL

rom asus a620bt
hello guys.I desperately need a ROM in English for a620bt.ma someone can help please. [email protected]
Finally i found ROM for A620bt v0.99.31 WWE,and German language,and for A620 the last ROM.I am verry hapy.yeah

A620BT ROM image?
Finally i found ROM for A620bt v0.99.31 WWE,and German language,and for A620 the last ROM.I am verry hapy.yeah
I'd also be a happy guy like you - could you please send the ROM for A620bt v0.99.31 WWE?
thanks in advance
Luke
[email protected]

Disabling TF3D Clock as Shortcut & A Few More Ideas

Greygabe.. Sorry for hijacking this thread but here's a chance to continue with learning about mode9 editing and stuff Your question is in post 2 which actually made me get into the classes
Finally got the mode9 edited to remove the selection on clock and the date line below it Thanks to headsup from above and mode9 quick tutorials from xboxmod
Attached are my LUA scripts for removing the clicks "just for reference" not to be used directly to device

[Q] Disabling TF3D Clock as Shortcut
So you know how when you press the clock in TF3D it brings you to the clock settings thing (the Time/Alarms settings)?
Does anyone know how to stop that?
It is a giant hit box for the touch screen and when it is in my pocket - it is the most common thing accidentally hit...
Plus it's not a settings menu I often need...

You have to edit the 1c684cd8_manila file, aka home tab mode9 file. It has a selection box defined which can be modified to remove the selection area for clock. I would post file, but not everyone has the same file, depending on with or without flipclocks for starters, but there could also be other differences too. The file can be edited using m9editor.

Has anyone ever figured this out? I constantly touch my clock screen inadvertently, sending it to alarms and setting.

greygabe said:
So you know how when you press the clock in TF3D it brings you to the clock settings thing (the Time/Alarms settings)?
Does anyone know how to stop that?
It is a giant hit box for the touch screen and when it is in my pocket - it is the most common thing accidentally hit...
Plus it's not a settings menu I often need...
Click to expand...
Click to collapse
You could change script on offset 798.lua in 1c684cd8_manila.
There are two of 'NavigateToClock()', one is for thouching, other is for clicking. You could get rid of what you want.

showaco said:
You have to edit the 1c684cd8_manila file, aka home tab mode9 file. It has a selection box defined which can be modified to remove the selection area for clock. I would post file, but not everyone has the same file, depending on with or without flipclocks for starters, but there could also be other differences too. The file can be edited using m9editor.
Click to expand...
Click to collapse
Hi showaco. I edited the file you mentioned in m9editor. Copied to windows and using it without any problems actually. But when i click on the date line below clock, it opens the clock applet. also when i click the clock after flipping it, it still opens the clock applet. how to get rid of that?
i edited the name size value to 0,0 last line in the screen below. am i doing something wrong?
{
"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"
}

Hi guys. I wanted to remove this code from the attached script of 1c684cd8_manila file
Code:
OnAlarmPressed = function(l_3_0, l_3_1)
_application.Navigation:Navigate(URL("Manila://WorldClock/alarmview.page"))
l_3_1.value = true
end
Even if I simply decompile the script in m9editor (3.3.0.1) and try to re-compile without editing anything, it gives me the below error
Am still learning this whole LUA script thingy so I cant know what is to be done. Please help somebody. Also I want to edit the date line & alarm line to place above the clock. Any ideas what is to be edited in the 1c684cd8_manila file?
EDIT: Found the problem. There was an extra "end" mentioned below. Compared the script with an earlier manila file. Removed that "end" and got the script to work
Code:
else
AlarmClockOn._visible = false
AlarmClockOff._visible = true
AlarmTime.String = "[[IDS_ALARMOFF]]"
if alarmSelected == true then
AlarmTime.Color = GetAlarmSelectedColor()
AlarmTime.Opacity:Interpolate(100, 0, 0, Interpolate_Linear)
else
AlarmTime.Color = GetAlarmOffColor()
AlarmTime.Opacity:Interpolate(50, 0, 0, Interpolate_Linear)
end
[B][COLOR=red] end
[/COLOR][/B]end

Hi guys. I am attaching my 1c684cd8_manila file for some help needed This file is not to be used directly since it is customised to my home layout
I need to move the text "Airtel" (carrier name) to the extreme left, keeping the operator logo (Ameet) as is. I have edited the mode9 file in such a way that I only need to replace a .png image called op.png (150x50) in windows dir to change the operator logo Works good for me
Can you guys tell me what is to be edited for moving the carrier name to the left. I tried changing the pos x of carrier name in the mode9 file but it just wont budge

Didnt do much good in the earlier section. Got no responses there. Hoping someone might be able to help out in here

Hi Ameet
to move operator text position
you need to edit attached lua.
in new manila 90% of item are placed in lua
lots of mode9 value are ignored.
if you need more info ask me.
bye

xboxmod said:
Hi Ameet
to move operator text position
you need to edit attached lua.
in new manila 90% of item are placed in lua
lots of mode9 value are ignored.
if you need more info ask me.
bye
Click to expand...
Click to collapse
Hi brother. The file you posted is actually for landscape? (home_landscape.luac)
The script from my file is different (attached my file for comparing )
Code:
TitleBar._visible = true
if OperatorLogo._visible == true then
CarrierNetwork.Position.value = Vector3(208, -15, 0)
CarrierNetwork.HorizontalAlignment = Alignment_Right
end
this is from portrait screen. I dont want to move the operator logo, it is perfect where it is right now. I just want to move the carrier name "Airtel" in screen above post to the left. Which code to be edited for that?

Hey xboxmod, I replaced the home.mode9 file from your package brother and edited my 25d04412_manila.lua script as the below to move the clock tab below and the date / alarm tab above it Changed only the lua script to avoid editing the main mode9 file directly
Code:
clock_tabs.CameraPosition.value = Vector3(0, [COLOR=blue]30[/COLOR], 320)
clock_tabs.LookAtPosition.value = Vector3(0, [COLOR=blue]30[/COLOR], 0)
TabsLeft.CameraPosition.value = Vector3(0, [COLOR=blue]30[/COLOR], 320)
TabsLeft.LookAtPosition.value = Vector3(0, [COLOR=#0000ff]30[/COLOR], 0)
TabsRight.CameraPosition.value = Vector3(0, [COLOR=#0000ff]30[/COLOR], 320)
TabsRight.LookAtPosition.value = Vector3(0, [COLOR=#0000ff]30[/COLOR], 0)
alarmCamera.Position.value = Vector3(0, [COLOR=red]220[/COLOR], 0)
I also played around with the values to get the below scene Its not perfect yet but I'm sure someone witll surely find a new theme pack for it
Code:
clock_tabs.CameraPosition.value = Vector3([COLOR=red]50[/COLOR], 30, 320)
clock_tabs.LookAtPosition.value = Vector3(0, 30, 0)
TabsLeft.CameraPosition.value = Vector3([COLOR=red]50[/COLOR], 30, 320)
TabsLeft.LookAtPosition.value = Vector3(0, 30, 0)
TabsRight.CameraPosition.value = Vector3([COLOR=red]50[/COLOR], 30, 320)
TabsRight.LookAtPosition.value = Vector3(0, 30, 0)
I changed all this only in the portrait right now (if l_2_0._application.Orientation == ScreenOrientation_Portrait then)

Ameet, care to look into Music tab... playlist problem?
When ever i add new playlist, once i do a soft reset, the playlist will be deleted.
thank in advance. =)

StyL3-Ivan said:
Ameet, care to look into Music tab... playlist problem?
When ever i add new playlist, once i do a soft reset, the playlist will be deleted.
thank in advance. =)
Click to expand...
Click to collapse
StyL3-Ivan, I've not hijacked this thread for providing support in editing lua scripts and stuff but for sharing information and learning things
We'll surely work on the solutions and new stuff all together, but right now its learning time

This is just a thought process right now to work on moving the QTC image files to storage card (Internal Storage in case of Diamond) This is not a confirmation yet, still in testing. Will keep updating this post as and when more info is found on this
Path Value for the 012.qtc to be used from in home.mode9 file is seen as “.\Assets\Images\Home\VGA\012.qtc” which is actually “\Windows\HTC\Assets\Images\Home\VGA\012.qtc"
Hence hash name of this 012.qtc file is “1C813F6C_manila”
If we change this path to “\Internal Storage\012.qtc” then the hash name of this same file becomes “5D1AA6D8_manila”
Change the path in mode9 file to “\Internal Storage\012.qtc”
And copy the “5D1AA6D8_manila” file (renamed 012.qtc) to root of Internal Storage
EDIT: 22-Apr-09
This didnt work as suspected. Changed all instances of the qtc path to above, found about 9-10 instances Creating a folder called Internal Storage in windows and putting the new hash file didnt work either Attaching my home.mode9 and the 012.qtc file (with above hash name) for someone to check. The time below is actually 22:53
EDIT: 23-Apr-09
It might have worked well actually. "Internal Storage" folder in windows was not created correctly. Will try later again on saturday night. I think we need a way to hex the manila.exe in recognising root path of the device. The mode9 files refer to path ".\Assets\Images.." etc etc which means it calls for the HTC folder as "\Windows\."

Can all the lines in all LUA scripts starting from "trace" be safely deleted?
Since these are debug codes, thought it will speed up the Manila a bit
for e.g.
Code:
trace("HandleLetterSelected=" .. string.char(l_16_0 + 65))
trace("HandleLetterSelected indexJump=" ..
or I can only remove such lines?
Code:
trace("+++++++[Programs_ScreenRotation] : ResetListViewContent")

Ameet said:
Can all the lines in all LUA scripts starting from "trace" be safely deleted?
Since these are debug codes, thought it will speed up the Manila a bit
for e.g.
Code:
trace("HandleLetterSelected=" .. string.char(l_16_0 + 65))
trace("HandleLetterSelected indexJump=" ..
or I can only remove such lines?
Code:
trace("+++++++[Programs_ScreenRotation] : ResetListViewContent")
Click to expand...
Click to collapse
Yes they can, they are for testing purposes only, 12

12aon said:
Yes they can, they are for testing purposes only, 12
Click to expand...
Click to collapse
But all the lines starting with trace can be removed? Would that really help speed up the manila?
xboxmod is kinda busy these days, but hoping he tries and helps me in understanding the hex editing part on manila.exe to make it search for qtc files from root

Ameet said:
EDIT: 23-Apr-09
It might have worked well actually. "Internal Storage" folder in windows was not created correctly. Will try later again on saturday night. I think we need a way to hex the manila.exe in recognising root path of the device. The mode9 files refer to path ".\Assets\Images.." etc etc which means it calls for the HTC folder as "\Windows\."
Click to expand...
Click to collapse
This may sound totally stupid but it's worth a try. Since ".\" refers to "\Windows\", "..\" should refer to "\". Windows CE has no concept of relative paths and ".\" must be included as a pointer to "\Windows\" by HTC. Somehow I doubt they created a "..\" pointer but it isworth a shot.
Sorry but I myself haven't tried this yet as I'm slightly new (as in total noob ) to MODE9 editing and HTC's implementation of Lua.

Ameet said:
But all the lines starting with trace can be removed? Would that really help speed up the manila?
xboxmod is kinda busy these days, but hoping he tries and helps me in understanding the hex editing part on manila.exe to make it search for qtc files from root
Click to expand...
Click to collapse
Should be but Zstupy said it would not matter much though, though I will be removing all trace in my next edits, 12

Create custom watch faces for Qualcomm Toq

Hello
I've recently buy a Toq Qualcomm SamrtWatch and, because the sdk does not permit a lot of things, I've started a little hacking
In this thread I would like to explain how i've beenableto create a custom watch face. This is a first try, I'll hope I will come later to explain more things.
And sorry for my english, I'm french. Ok let's start :
- First get the Toq Manager Android application because it contain some watch, if you own a Toq you must have install it via google play store. :
you can follow the tuto here http://forum.xda-developers.com/showthread.php?t=1755436 but it must be :
Code:
adb pull /data/app/com.qualcomm.toq-1.apk
- 2 extract the apk to find where the watch face are :
for this I will android-apktools, https://code.google.com/p/android-apktool.
SO basically in my folder I have :
Code:
apktool
apktool.jar
com.qualcomm.toq-1.apk
I extract the apk in a new directory, named "toq" with:
Code:
./apktool d com.qualcomm.toq-1.apk toq
- 3 find the watch face :
in the toq/Assets directory there is a file named "allclocks.json" wich contains the watch faces definitions :
Code:
{
"Clocks": [
[...]
{
"bundle": "degreesclock.zip",
"type": "dynamic"
},
{
"displayName": "Agenda",
"icon": "clock_agenda",
"type": "builtin"
}
]
}
so you can add a custom watch face by modifying this json and adding this lines for example
Code:
{
"bundle": "myclock.zip",
"type": "dynamic"
},
you can see that a "dynamic" watch face is defined by a zip file, wich is the assets folder too. you must add this zip file to create the watch
4: Create the watch face :
There is two zip file to create to add a custom watch face. the first will describe the watch face. It will be named xxxxx_app.zip, xxx is your watch face name, mycolock for example.
This zip file will contains two lua file :
- manifest.lua will describe the watch :
Code:
clock {
name = "MyClock",
entrypoints = "ClockEntries"
}
the second will be executed by the Toq to draw the watch face and will be named init.lua.
We can add image file that will be used by the init.lua script.
I started a project on github to convert png to qualcomm img format : https://github.com/marciallus/toq_imgTools
I attach the myclock_app.zip in this thread.
The second zip file will be name xxxxx.zip, myclock.zip for example. and will contain 3 files:
- The zip files create before will be add to in this zip, I dont see why.
- clock.json will describe the watch too
Code:
{
"Clock": [
{
"displayName": "My Clock",
"packageName": "com.qualcomm.qce.myclock",
"asset": "myclock_app.zip",
"icon": "my_clock.png",
"jsonName":"com.qualcomm.qce.myclock/MyClock"
}
]
}
- my_clock.png will be displayed in the Taq Manager Android Application to choose the custom watch
I've attached the myclock.zip in this thread too
5 : Repackaging
Now we have created the two needed files in assets folder we will recreate the apk to resintall this modified version on the phone :
-first use apktool to repackaging in com.qualcom.toq-modified.apk
Code:
./apktool b toq com.qualcom.toq-modified.apk
-we need to sign the apk :
Code:
jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore [your keystore] com.qualcom.toq-modified.apk [your key]
you can see how to create a keystore here : http://developer.android.com/tools/publishing/app-signing.html
- we can zip align the file, it's better :
Code:
zipalign -fv 4 com.qualcom.toq-modified.apk com.qualcom.toq-modified-aligned.apk
6 : Installing
We just have now to reinstall the modified apk :
Code:
adb install -r com.qualcom.toq-modified-aligned.apk
And if you go on your phone on Toq Manager -> Preferences -> Clock Style !! TADA !! your clock is here, you can select it to push it to your watch !!
that's all
feel free to comment, it's my first thread creation so I'm open for remarks
--
MarCo

I recently bought an Toq on eBay, I will try it as soon as it arrives. Do you know a way to transform from IMG to PNG?
Thanks for the hack!

alaintxu said:
I recently bought an Toq on eBay, I will try it as soon as it arrives. Do you know a way to transform from IMG to PNG?
Thanks for the hack!
Click to expand...
Click to collapse
The github i've started here : https://github.com/marciallus/toq_imgTools doas png to IMG but I will add the options to make inverse
--
MarCo

marciallus said:
The github i've started here : https://github.com/marciallus/toq_imgTools doas png to IMG but I will add the options to make inverse
--
MarCo
Click to expand...
Click to collapse
Thanks! No love here so far, but I've been looking for this for some time. Been waiting to get a new PC (old one died) before I explored this. Might still be a little while before I make an attempt though.

Flipclock
I've found that there is a clock that is not enabled called "flipclock".
Just editing allclocks.json and adding:
{
"bundle": "flipclock.zip",
"type": "dynamic"
},
You have a new clock! Now I'm trying to add 24h formats to some existing clocks (bold and facets). Do you have any clues to do that?
P.S.: Did you enable the possibility tor transform from img to png yet? I didn't see any changes in your github project.

24 Hours digital watchface
I created a simple watchface, showing 24h digital clock and the date, something like:
Jan, 07
13:00
Wednesday​

Great
I've deposed one here two
https://github.com/marciallus/mytoqmanager/blob/master/toq/Data/assets/newclock_app.zip
alaintxu said:
I created a simple watchface, showing 24h digital clock and the date, something like:
Jan, 07
13:00
Wednesday​
Click to expand...
Click to collapse

marciallus said:
Great
I've deposed one here two
Click to expand...
Click to collapse
I checked your code and i think you can much more easily get 24-hour clock by just changing timestyring format:
Code:
timeModel:getTimeString("%I")
change to:
Code:
timeModel:getTimeString("%H")
Since it's all lua script they should be using lua time format strings.

Pyblo said:
I checked your code and i think you can much more easily get 24-hour clock by just changing timestyring format:
Code:
timeModel:getTimeString("%I")
change to:
Code:
timeModel:getTimeString("%H")
Since it's all lua script they should be using lua time format strings.
Click to expand...
Click to collapse
Ah Yes thx a lot
I just discovered lua
I Will try that
bye
--
MarCo

About your image conversion...
I'm wondering how did you figured out how to open or modify those .img files? Honestly I have no idea what was going on or what was your reasoning in order to create your little program. Did you found something provided by Qualcomm or Mirasol?
marciallus said:
I started a project on github to convert png to qualcomm img format: github.com/marciallus/toq_imgTools
Click to expand...
Click to collapse
I have found a java class to convert .img to .png files:
gist.github.com/moneytoo/8446716
I would like rewrite your code to run it in java. I hope you can help me to understand how it works.
By the way, It is possible to create a watchface with a custom image background, like this example:
github.com/KhaosT/ToqImageGenerator
Thank you!