Database Develop

tomtom poi's to small

With the tomtom 7 on the diamond the poi's are to small.
How can i make the poi's bigger...

J.P. said:
With the tomtom 7 on the diamond the poi's are to small.
How can i make the poi's bigger...
Click to expand...
Click to collapse
Look in the map folder. There are .bmp files for each custom POI. Just replace them with bigger ones.
I am not sure if this can be done with the build in POIs.

I have the same problem with the pocketgps.com speed camera icons, have changed then to 44x44 icons from 24x24 and hasn't seem to change the size at all, they are still way to small. You need a magnifying glass to see them when they flash on the map

got the same problem really is small considering its a point of interest not a bloody tree! Only way i see the Speed camera poi is having the sound warning on which usually pops up the top left corner what is coming up.

MarcLandis said:
Look in the map folder. There are .bmp files for each custom POI. Just replace them with bigger ones.
I am not sure if this can be done with the build in POIs.
Click to expand...
Click to collapse
I think your correct about the size of the images in the map folder and that you can change the size but its a lot of effort?? If anyone gives it the time maybe they could post the lager bmp images in a zip file??
I have the same problem - especially with speed cameras I think that its mainly because the maps were not designed originally for use on our new VGA screens - the maps are scaled automatically but the bmp images are not - maybe when we see dedicated ver 7 maps for VGA PDA's we'll see an improvement?

I have also button menu and font too small on diamond (vga screen)...

Tomtom icons
I have tried to reduce the size to 20X20, 40X40 and 44X44 but the BMP. are far to small.
(with the wrong size the pictures are red in TT)
Is there anybody who have ONE icon in TT with the right size?

Did you try 48*48?

Blob8me said:
I think your correct about the size of the images in the map folder and that you can change the size but its a lot of effort?? If anyone gives it the time maybe they could post the lager bmp images in a zip file??
I have the same problem - especially with speed cameras I think that its mainly because the maps were not designed originally for use on our new VGA screens - the maps are scaled automatically but the bmp images are not - maybe when we see dedicated ver 7 maps for VGA PDA's we'll see an improvement?
Click to expand...
Click to collapse
Same here.
i don't thing we can do anything for this:
1) maps are not scaled in VGA screen. Infact, a greater area of the map is shown, compared to a QVGA screen (tried on both with two different phones). That is why, the POI icons are small, cos they follow always the 32x32 size. In fact, you will see an area 4 times greater than QVGA screens. Therefore, POI icons look 4 times smaller.
2) If you resize the icons to 48x48 or whatever, TomTom will scale them down to 22x22 automatically (auto-fit) if intelligent enough, becasue that is the size TomTom was designed to display. But it will probably simply not understand the bigger size and just display some rubbish with default resolution of 22x22, i.e., all red square.
Sorry. I see no solution. Maybe by using some overlay third party programs to show POIs and disabling TomTom internal ones. What was it called, "POI warner" I think?

Sorry, but also with 48x48 the icon is to small and only red.
What is de original size?

I must say when I first got my Diamond it was TomTom that I was looking forward to putting on there for the real VGA 'experience' and at first glance I was very impressed... but then I started using it for navigation and, not least given I use it in 2D mode, soon found that everything was a tad too small! I wasn't so fussed about the POIs but it was the map scale overall - at arms length I could hardly see the map detail and really didn't need to see for 10 miles around - it wouldn't be so bad if it didn't zoom out so much.
So, here's how I sort of fixed it.... a kind of workaround which disables TomTom's awareness of it being VGA. The upshot of this is that everything becomes a reasonable scale however the drawback is that it's a waste of VGA and at first glance you might think 'oh my God that's awful - so blocky!' but I soon found that when actually using it in my car I really don't now notice. The blockiness is down to running at a non-native resolution - like all fixed-pixel screens you end up with unclean lines.
Grab yourself a copy of the freeware resource PC tool Resource Hacker, make a copy of the TomTom Navigator.exe file on the PPC, and open it up with the tool.
Now find the resource CEUX\HI_RES_AWARE\2057, right-click it and delete it. It will likely take the whole branch with it if it is the only entry in there. Now save the resulting file (I got an error at this point - dunno if it's Vista or what but it still seemed to work) and copy the file back to the PPC (note it makes a backup so make sure you get the right one!) - you might want to call it something different so you can then have a choice of VGA or non-VGA TomTom's to run.
And that's it... I'm sure when you first see it in action you'll think it's horrible... but in use I think it is fine and indeed for me makes it at least usable once more.
Mathew

Wow nice trick man
POI's are now bigger but OMG this is very ugly lol !
Need anti-aliasing
Its nice but there are some bug for the text display

I actually find it okay when at arms length!
What were the text bugs you mentioned? (I must confess I've only used it a few times since doing this so could well have missed some major showstopper!)
Mathew

MJNewton said:
I must say when I first got my Diamond it was TomTom that I was looking forward to putting on there for the real VGA 'experience' and at first glance I was very impressed... but then I started using it for navigation and, not least given I use it in 2D mode, soon found that everything was a tad too small! I wasn't so fussed about the POIs but it was the map scale overall - at arms length I could hardly see the map detail and really didn't need to see for 10 miles around - it wouldn't be so bad if it didn't zoom out so much.
So, here's how I sort of fixed it.... a kind of workaround which disables TomTom's awareness of it being VGA. The upshot of this is that everything becomes a reasonable scale however the drawback is that it's a waste of VGA and at first glance you might think 'oh my God that's awful - so blocky!' but I soon found that when actually using it in my car I really don't now notice. The blockiness is down to running at a non-native resolution - like all fixed-pixel screens you end up with unclean lines.
Grab yourself a copy of the freeware resource PC tool Resource Hacker, make a copy of the TomTom Navigator.exe file on the PPC, and open it up with the tool.
Now find the resource CEUX\HI_RES_AWARE\2057, right-click it and delete it. It will likely take the whole branch with it if it is the only entry in there. Now save the resulting file (I got an error at this point - dunno if it's Vista or what but it still seemed to work) and copy the file back to the PPC (note it makes a backup so make sure you get the right one!) - you might want to call it something different so you can then have a choice of VGA or non-VGA TomTom's to run.
And that's it... I'm sure when you first see it in action you'll think it's horrible... but in use I think it is fine and indeed for me makes it at least usable once more.
Mathew
Click to expand...
Click to collapse
Anything similar for iGO 8?

I didn't think iGO8 had any issues re size/legibility on the VGA screens?

It works fine, the black popup right above in the screen with the text (for example "no GPS") is to large. But thats not a big problem because it's not mention when you navigate.

MJNewton said:
I actually find it okay when at arms length!
What were the text bugs you mentioned? (I must confess I've only used it a few times since doing this so could well have missed some major showstopper!)
Mathew
Click to expand...
Click to collapse
Well, when you check how much satellites your GPS found, the numbers are displayed bigger.
And on the main screen, the speed indicator number is smaller than "km/h" .
But still nice

Great solution! Thanks.

It seems that TomTom 7 isn't really VGA-ready. Any news on an update?
Think it's very bad for business to offer such a bad solution for VGA screens, which are coming more and more.

Memory Map - file sizes

Hi all,
I have Memory Map with all the UK at a scale of 50k. Problem is that they're devided into 12 regions, each file being between 200-400MB. My Touch Pro won't open any of them, MM gives an error saying 'unable to load' type error. After some research it seems that the files are too big for it to open, even though MM say try to keep the file sizes below 400MB (which they are, give or take). I can send visible screen capture maps from my PC which do work kinda confirming that it is a size issue.
Does anybody have any suggestions in solving this. As I really want all regions on the phone as a resource without having to consider where i'm going before hand and uploading just that portion or route.
Thanks.

No solution I'm afraid, just confirming that it looke like a file size issue... I tried copying via both Activesync and direct to disk in case it was that. 120Mb seems to open OK, which covers all of north Wales... I used MM on my Wizard too but never tried copying a whole tile over due to lack of storage, so I don't know if it's a hardware limit or an application problem...

Ok. thanks for confirming that.
It's a shame MM dosn't allow you to zoom out further as it would be possible get extracts at the limit of the file size possible to load and then build your own tiles of the UK. As it is, this would be far too time consuming at the current zoom extent.

Organic99 said:
Ok. thanks for confirming that.
It's a shame MM dosn't allow you to zoom out further as it would be possible get extracts at the limit of the file size possible to load and then build your own tiles of the UK. As it is, this would be far too time consuming at the current zoom extent.
Click to expand...
Click to collapse
If you can get hold of the 1:600000 road map you can use that to zoom out further. The higher resolution maps you have will appear as green outlines. You can then subdivide your 50k maps and save them as smaller, slightly overlapping sections by drawing a closed route on the low-res version of the map. Then increase the resolution, right-click on a line of the route, go Operations->send enclosed map to mobile device then choose a place to save the map (does not have to be on your PPC so you can transfer quickly later). Of course because of the overlap the total amount of storage for the whole of the UK is greater... it's a bodge but it's better than no maps at all
Cheers,
Tim

I can confirm that the Touch HD has the same problem, maps over about 120MB dont open. Maps 100-120MB sometimes work sometimes dont Interestingly The maps and sizes are exactly the same as I have previously used on both an original Touch and and MWG Atom Life without any problem. They didn't give a problem untill the file size got considerably bigger. Wonder whats different on these newer phones?

[INFO] Solved Internet Globe w/o XML Editing

Procedure To Edit The Internet Globe Button Manila Files
(No more solid white blank buttons)
7d3f1247_manila - Globe Unselected
3f00cd2f_manila - Globe Selected
What:
With this procedure you will be able to select any graphics or highlight color you want to use for both the selected and non selected states of the Internet globe button.
How:
There are no special tools required other than Manila Editor 0.2 and a graphics program that can work with png files. You will need to know how to use both of these programs though.
Advantages:
The biggest advantage over editing either 27c65cbd_manila or InternetPortal-en-US.xml would have to be speed. When I tried that way on my Fuze it would take well over 5 seconds to load every time I scrolled to the Internet tab. Sometimes almost double that on a fresh boot. Second advantage would be that this *should* work on any device that uses those 2 files, where the xml edits are different files for different devices. Which leads to the third advantage of not needing special install instructions for theme makers. Edit the manilas and drop them in with the rest.
Other Info:
(Just skip this part if you don't care about the why and scroll down to the instructions.)
I have literally scoured these forums and the Internet for days trying to find information on editing not only the Internet globe manila files, but the other 7+ files that just don't work right with Manila Editor. Most theme makers know of these files. Mostly what I found was a lack of information and more questions than answers. The only other procedure I could find at all for converting manila files gives better results than using Manila Editor but it's very complex for the average user requiring command line tools. Even so the author, (Chainfire) has written a damn near fool proof tutorial so if anyone is interested you can find the thread HERE. Unfortunately even that procedure would not handle the problem manila files properly and quits with the following message.
Reading file: 5c01b59c_manila
Error: file is not QTC format
For reference, this is the list of files that I know of at the moment with this problem, and all return the same error except for 7d3f1247_manila. (More on this file to come.)
7d3f1247_manila - Globe_Unselected (512x256) 28.5k
3f00cd2f_manila - Globe_Selected_D (512x256) 64.5k
40ec2415_manila - Small Avatar_D (64x64) 2.5k
2f411611_manila - Exclamation Point_D (256x256) 32.5k
4d97cac6_manila - Add Contact_D (256x256) 32.5k
54e0759d_manila - Contact Avatar_D (256x256) 32.5k
400b663e_manila - You Tube_D (64x64) 2.5k
55cc771a_manila - Selection Highlight Bar (512x256)64.5k
5c01b59c_manila - Contact Avatar2_D (256x256) 32.5k
The first oddity I noticed when using Manila Editor on the Globe file (3f00cd2f_manila) is no mater what size my graphic was before running it through, it always came out to be approximately 125k. Since the stock file was roughly half that size I knew something was really wrong. The other glaring anomly with most of the files is they show up as duplicated (side by side) images when viewed with M.E. so I figured that somehow all of this must be connected.
I am not a programmer by any stretch but I know just enough to get me into trouble most of the time. Anyway I loaded both files into Notepad++ and turned on hex view to see what was so different. The header of both files were similar but not exactly the same so I copied chunks of the problem file from below its header and pasted it into the good manila at the same address location. What it produced was a repeating pattern on the top left corner of the stock green button but every other row was white. I don't know why but the fact that the image repeats in M.E. as well and the file being double the size made me think to cut the image in half and try to see if M.E. would accept it. It did and I was elated to finally see an image on my phone other than than the big white rectangle.
I had an image that was really distorted but it wasn't difficult at this point to see what was going on by the way it was distorted. I was able to get a perfect button on my next try by creating my image on a 256x128 canvas and then scaling it to 512x128. It looks really bad and stretched out at this point but after processing with M.E., the phone will compress back to it's original aspect and it looks just perfect. I use The Gimp as my image editor and just save as a png file with the default settings.
Now that I Finally had a working selected globe image I wanted to change the static globe as well. (7d3f1247_manila) This was a whole new battle but at least I had something to work from this time. There are some significant differences in this file compared to the selected globe. First, it looks perfect when you extract it using M.E. which led me to believe that this would be easy. I couldn't find much info on this particular manila and I think I know the reason why. Either people are replacing both images via the xml workaround, or they are just concerned with getting the highlight the right color on the selected image. Either way, when I tried to do a 1:1 replace in M.E I got to see the wonderful white rectangle again. At this point I had finally gotten all the tools working from the post I mentioned before and decided to try this file using that procedure as it should return better results if it did work. It worked perfectly but I still wanted to get it to work using M.E as most people are not going bother with a long drawn out procedure.
After playing around some I found that if I scaled the 512x256 image to 256x256 it worked perfectly. The up side is the file size is half of the stock image. The down side is the resolution is obviously cut in half. It's really not a show stopper but using the other method does produce perfect results. Not completely satisfied yet I tried some more images at different resolutions to see what happened. The 480x240 image I had from one of the globe mods that are floating around produced a white rectangle. I then decided to try another unscaled image that was almost completely transparent and it worked without a hitch. Now that I was completely confused I went back and tried the original 512x256 that produced the white and it did so again. It wasn't until I switched to another tab and back again that it finally showed up correctly.
So what does it all mean? Hell if I know but at least the scaled 256x256 method seems to work every time without any problems and its fast to boot. The long procedure would be the best method of them all but probably not worth the effort for most. As far as the other problem files go I guess I'll try and work them out too unless someone else more capable picks up the ball and runs with it. The selected globe was the particular image that stuck in my craw and got me started on this.
Instructions for 3f00cd2f_manila - Globe Selected:
1. Create your image at a size of 256 x 128 exactly how you want it to look on your device.
2. Scale it to a size of 512 x 128 and save it. You will have to "unlock" the aspect ratio lock in most graphics programs. This will distort your image badly but do not fret. Yet.
3. Fire up Manila Editor as usual and use your new image. Now you can fret as you wait to see if this works or not.
4. <-- I hope
Instructions for 7d3f1247_manila - Globe Unselected:
1. Create your image at a size of 512 x 256 exactly how you want it to look on your device.
2. Scale it to a size of 256 x 256 and save it. You will have to "unlock" the aspect ratio lock in most graphics programs.
3. Fire up Manila Editor as usual and use your new image.
General Notes:
If you don't want to mess with any of this and like what's in the screen-shots attached, you can install the cab or just unpack the zip into your windows directory on your device. As always, please back up your files before adding new software.
Notes concerning 7d3f1247_manila:
This procedure *should* work if done as stated. If you use the alternate method I linked to in the info section above you don't have to scale the image and will get a higher resolution image. I have successfully used a non scaled image before with Manila Editor but it goes white on first load after a reboot then somehow clears up. With the scaling method I've yet to see the dreaded white rectangle. Read the info section for more information.
More Information:
Manila Editor 0.2.0
Editing Manila
Manila 3D Porting
Pixel Perfect TF3D ***
Manila Fine Details
Cheers,
Eidolen
*Disclaimer*:
Obviously I can't test this on every device but I can't think of any reason why this wouldn't work on any TF3D enabled device. If this doesn't work for you, feel free to post here or contact your congressman. (Where applicable) If this helps anyone please be sure to drop in and say hi.

There is some real development going on about this subject over on the pixel perfect thread. If you are just looking for a quick fix then what I posted above is still relevant but you might want to keep an eye out for a *real* fix as I doubt it will take them long once they sink their teeth into it.
I believe they already figured out that you can patch the header on the problem files to correct the payload size which should work also. If you are not so technically inclined then the method posted here still works flawlessly for me and should for you as well.
I've added a picture that might help if the directions above were confusing at all, so it might help clear it up. You can find the link to the Pixel Perfect thread right above this post.
Cheers,
Eidolen

png optimizing

Hey guys, I may be way off on this... but just tell me if my thinking is sound.
One of the things I see people doing in themes and roms is optimizing all of the png's for a smaller file size. At first glance, that seems like the thing to do -- Less in memory, less size = better.
But I know that on applications that need to load images very fast it is always better to make them as uncompressed as possible. That way, in order for the system to show the image, the cpu has less to uncompress before displaying it.
An example would be on my HTPC. There are all kinds of fan art and huge wallpapers that change with each click to the next menu. So when I switch from Music to TV Shows. My wallpaper switches from a picture of AC/DC to a picture of the cast from "House". The first thing everyone will tell you to do is convert them to bitmaps. Bigger file size but way less for the cpu to do in order to show it. This helps with not having a delay or one of the pictures not showing up for a split second.
Now I know we can't use bitmaps because we need the transparency. But with such little cpu power on these phones, wouldn't we want the pngs to be as uncompressed as possible?
As I said, let me know if there is something I am not thinking of. The answer could be as simple as the cpu required to uncompress the pngs has less impact that a few more megabytes of memory being used. Not sure if anyone has done any testing on this.

You can try re-saving with minimal compression using IrfanView or a similar tool (even Photoshop I'm sure).

Oh, the I am a web developer. I work with image compression everyday. Thats not the problem, I just wanted to know if anyone had considered this or if there is another reason I'm not thinking of.

[Q] 8 bit? Themers Please help

Hi all, i am trying to work on a theme for the Droid X. Can anyone tell me why some of the images open in photoshop incorrectly and more to the point how to fix them?
I cant post a link apparently to the image or a http link since i'm new but
You can view the image here. http:/ / dl.dropbox.com/u/6769503/8bit.jpg
Is there a setting or something I can change in PS to open these correctly?
Thanks for your time.
KraYzeE

krayzee said:
Hi all, i am trying to work on a theme for the Droid X. Can anyone tell me why some of the images open in photoshop incorrectly and more to the point how to fix them?
I cant post a link apparently to the image or a http link since i'm new but
You can view the image here. http:/ / dl.dropbox.com/u/6769503/8bit.jpg
Is there a setting or something I can change in PS to open these correctly?
Thanks for your time.
KraYzeE
Click to expand...
Click to collapse
What is the original file extension? .png?
I had this same problem with some .png files wich had transparency in windows image viewer, but not in photoshop.
My solution was to open it in Paint.net and save it, rewriting the original image. Please be sure to set the transparency correct whilst saving in paint.net.
Download Paint.net

Thanks for the reply, yes it was a PNG, ill try paint.net but i would really like to use Photoshop. I cant understand how it can mess up the transparency and anti alias like that.

Update: Paint.net does indeed open the file correctly... so while i do now have a solution. I would still like to find out why Photoshop (both CS4 & CS5) open it incorrectly ?

Well technically 8 bit pngs are indexed images with a varying amount of colored pixels and then varying amount of transparent and semi transparent pixels so some programs might not like this. I would recommend gimp over ps as its similar but doesn't have this issue.
Sent from my HERO200 using XDA App

that image actually seems correct, can you post an image of the alpha channel? then we will know if photoshop is not reading the file correctly

As one poster said, it's because the images is indexed. If you do Image > Mode > RGB, it will un-index it. I must warn you though, PS is HORRIBLE with indexed images. Use GIMP/Paint.NET to un-index it to save yourself a headache

JAguirre1231 said:
As one poster said, it's because the images is indexed. If you do Image > Mode > RGB, it will un-index it. I must warn you though, PS is HORRIBLE with indexed images. Use GIMP/Paint.NET to un-index it to save yourself a headache
Click to expand...
Click to collapse
Ahh but then you lose the 8 bit optimization, even running optpng will not put it back to index png cause it will ossy optimize it. So just use gimp.

Thanks for the replys guys.
Here is an example image.
http:/ / dl.dropbox.com/u/6769503/btn_circle_pressed.png
If you open it in PS, you will see what i mean, changing it to RGB does not change the image. I can open it correctly it Fireworks, then save it without making any changes, and then i am able to open it in Photoshop correctly.
This will do for now in case anyone else runs into this issue. The file size isn't too much bigger this way, so it will work for now.
Thanks again to all that helped.

http://dl.dropbox.com/u/1631008/btn_circle_pressed_fixed.png
Here's the image fixed, it was indexed... all I did was open it up with osx Preview and save it again. Or you can try this gimp they all talk about but I think it's overkill to switch to another program just because 1 or 2 images are weird, especially after you paid for your copy of Photoshop.

DBBGBA said:
http://dl.dropbox.com/u/1631008/btn_circle_pressed_fixed.png
Here's the image fixed, it was indexed... all I did was open it up with osx Preview and save it again. Or you can try this gimp they all talk about but I think it's overkill to switch to another program just because 1 or 2 images are weird, especially after you paid for your copy of Photoshop.
Click to expand...
Click to collapse
Thanks for your help. I don't have OSX and i absolutely cannot get used to Gimp. but opening it in adobe fireworks and saving it again right away does the trick, so although it's a pain, its simple to do.
If anyone ever figures out a way to directly open these types of files in Photoshop i'd be glad to know.
Cheers
KraYzeE

krayzee said:
Thanks for your help. I don't have OSX and i absolutely cannot get used to Gimp. but opening it in adobe fireworks and saving it again right away does the trick, so although it's a pain, its simple to do.
If anyone ever figures out a way to directly open these types of files in Photoshop i'd be glad to know.
Cheers
KraYzeE
Click to expand...
Click to collapse
Yes that works but your removing the indexing. Android uses indexed pngs wherever possible because this saves space and resources, if you changed every file in the android system to rgba your phone would be noticeably slower.
If you change it to rgba and then run optipng on it you'll see it will not index cause it can only lossy optimize, but if you set the mode to index and then optimize it you'll notice then file will be considerably smaller with little or no image quality loss. So in short your removing a vary important optimization feature of the android system.
If your looking for a quick image conversion tool try image magick, this will allow you to write scripts to convert them png24/32 to png8 and back whole folders at a time.

well as we do with video it's always better to work with uncompressed, high res images. Then when everything is done and set in stone we compress and optimize without loosing too much image quality.
If i had to start a theming project I'll probably do the same, convert everything to high res, work on it then compress to a more optimized format.

DBBGBA said:
well as we do with video it's always better to work with uncompressed, high res images. Then when everything is done and set in stone we compress and optimize without loosing too much image quality.
If i had to start a theming project I'll probably do the same, convert everything to high res, work on it then compress to a more optimized format.
Click to expand...
Click to collapse
Yeah for video thats fine, but in theming and specifically for this file gimp will allow you to work on the indexed file and you literally can not tell the difference with the indexed file being atleast 50% smaller. Maybe this would make sense with an image that has alot of quality or is high res but in this instance it a loss of time and added steps when the same could be accomplished with industry standard tools.