Related
Hello,
I recently purchase a T-Mobile MDA. I love the phone but, it seems that the processor is just plain slow. It takes seconds between application launches. I have hear that I may be able to send my phone to some one who can speed it up memorywise?
My question is is this a good idea and how much does it cost?
As well as is there a way I can get a program to remove what is taking up space in my phones memory, storage and memory?
I am also confused about what a ROM is? Is this something I should consider?
I would appreciate any help, thanks.
You can send the phone and pay for someone else to do the same thing you can do, there is no hardware upgrade only software/registary tweaks.
There are several things you can do to speed things up, they have been discussed here extensively I would suggest doing a search.
Thanks man. Appreciate it.
I think the best way is to overclock...
I tried overclocking but to tell you the truth the best performance gains came from removing software (Anti-Virus) and reg tweaking.
Upgrade to a stable latest ROM could be a big step-up in speed as well, among some other improvements
first, upgrade to the newest ROM version.
second, run Omapclock to overclock your Wizard to a maximum of 260MHz. (240MHz is preferred)
Are there any drawbacks to this omapclock and over clocking mechanism?
eg. loss of memory space/storage space?
reduced battery life + possibly instability depending on how far you go.
I think some big differences need to be explained about speed and responsivness.
Speed is how fast the thing actually runs, responsivness is more what it sounds like this guy wants.
In our case, speed will help us squeeze another 2-3 fps out of our video players, where responsivness will make a program load in 1 or less seconds. Your standard reg tweaks and hacks will help with responsivness. If you have a video file that is kinda skipping or laggy, then overclokcing will help.
You will get little to NO performance difference with a few mhz overclock on your main OS.... I would be suprised if it did anything and not surprised if it slowed down.
In the end, look about the forums, there are MANY hacks and tweaks here posted and on other websites off of google which will help with your responsivness problems.
Some search items to look for:
GDI, animated menus, fat or fat32, cache
Thats off the top of my head, those should make you run pretty fast.
Let's do better
Here goes :
Speedup Display :
[HKEY_LOCAL_MACHINE\System\GDI\GLYPHCACHE]
Limit=8192
Disable menuanimations :
[HKEY_LOCAL_MACHINE \SYSTEM\GWE\Menu]
AniType=0
Speedup filesystem:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\]
CacheSize=4096
EnableCache=1
I don't understand this post. How do I use these links?
Sevenpelicans said:
I don't understand this post. How do I use these links?
Click to expand...
Click to collapse
they aren't links, they're registry changes
you'll need to find a registry editor to do them
Okay, I have a registry editor, as in memmaid, and resco explorer. Can someone explain how I perform these registry changes?
The are probably better and more detailed explanations but basically:
1) Launch the registry editor
2) Navigate the tree structure to the appropriate part (like using explorer for files)
Then either,
3) Edit the appropriate value (i.e. 'Anitype' is already a variable in \System\GWE\Menu) - select the variable (tap) then enter the corrected value (i.e. from above DWORD value is '6' change to '0')
or
4) Insert a new variable with the precisely correct spelling, then enter the appropriate value(s).
NOTE: You have to enter the correct type of variable, but generally you are adding:
Key (like a new folder)
String Value (has a name and then a 'string' value)
DWORD Value (has a name and 'DWORD' value, usually in dec not hex)
Hope that helps... like i said, there are better explanations out there...
PS you should often have to re-start your device for the changes to take place!
Sevenpelicans said:
Okay, I have a registry editor, as in memmaid, and resco explorer. Can someone explain how I perform these registry changes?
Click to expand...
Click to collapse
Open the Resco Registry Editor, search the key which is between the [] and adjust the values as suggested above.
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.
Just found out something which was not in the forums and thought to share it with all (found only one reference, but for different device - it had different location for the counter).
In case you want to change the counter of the file numbers that the camera will record with (i.e. IMAGE001.JPG, but you want IMAGE045.jpg), you need to edit your registry with a registry editor:
Go to HKCU\Software\HTC\Camera\5.04\Preferences edit the key "Values" as per the attached screenshot - the next number for the picture (in HEX format - use windows calc in advanced mode to convert the number to HEX) should be typed at position 68 HEX.
Next time you take a picture it will use the number you placed there.
Nice one, I've been looking out for a solution to this issue! I'd like to add that if you want to set the counter beyond 255, you also have to edit position 69 HEX. This way, "FF 00" on positions 68 and 69 translates to "255", whereas "00 01" translates to "256", "01 01" translates to "257", etc.
To change the video counter, you have to change position 70 HEX. Keep in mind that this is not the position right after 69; after 69 comes 6A, 6B, etc., before you arrive at position 70. This probably is obvious to most of you, but it is a mistake easily made.
OK, this is exactly what I've been looking for also, but as a person who understands little or nothing about hex I would appreciate some guidance as to what to input, and precisely
where.
I would like to reset my camera's counter to 300, so that the files go 300.jpg. 301.jpg etc etc. If one of you could help me out, I'd appreciate it.
I just would rather not screw it up
Thanks.
As mvc mentioned, you can use the Windows calculator to convert the desired (decimal) value to the corresponding hexidecimal value. In your case, "300" would translate to "12C" (which equals to "01 2C"), meaning you have to change position 68 HEX to "2C" and position 69 HEX to "01".
If you need a program capable of editing the registry, I recommend the freeware utility Task Manager (the program which is used in the above screenshot):
http://www.freewarepocketpc.net/ppc-download-task-manager.html
Good luck!
Hi,
this game is quality...
I've finished the 32 levels of this game and i want MORE
Is it possible to add new levels to this game??
Are there any better sensor games out there?
Raf
No there are currently no gyro-driven games, but wait a few months-:
Steering a car, flying a plane all with Gsen support , like a mini-WII
Why not taking the advantage , now that you created a thread anyway, to post some scores , just for fun
Rule: Post your score after finishing your FIRST TIME finalized 32 levels.
I got a 21 min 35 sec with +18 attempts in total from which 7 were on a same level
unfortunately i didnt make a note of my score after completion and upgraded to a new ROM....
rafter_01 said:
Hi,
this game is quality...
I've finished the 32 levels of this game and i want MORE
Is it possible to add new levels to this game??
Are there any better sensor games out there?
Raf
Click to expand...
Click to collapse
I don't know if you can add levels, but you can edit (and than distibute) them.
The levels are described in files 1.txt - 32.txt in de windows folder.
You can edit these (e.g. with Total Commander) to edit the levels.
The syntax is straight forward:
"B" with two params determines begin position.
"E" with two params determines end position.
"W" with four params determines walls.
"H" with two params determines holes.
See attached file for a new level (replacing the old 1st level)
Just replace the file in the windows folder (after making a backup of the original of coarse)
coolio
thanks for that
more games
i am not sure about this:
while cooking my ROM i discovered these files belonging the teeter:
\windows\1.txt, 2.txt, 3.txt, etc.
i think these are the chellenges. simple txt files
i think we could examine them and make new challenges.
Patrickw_mdav said:
I don't know if you can add levels, but you can edit (and than distibute) them.
The levels are described in files 1.txt - 32.txt in de windows folder.
You can edit these (e.g. with Total Commander) to edit the levels.
The syntax is straight forward:
"B" with two params determines begin position.
"E" with two params determines end position.
"W" with four params determines walls.
"H" with two params determines holes.
See attached file for a new level (replacing the old 1st level)
Just replace the file in the windows folder (after making a backup of the original of coarse)
Click to expand...
Click to collapse
faster than flash
ykat said:
faster than flash
Click to expand...
Click to collapse
Looser makes a new level
I'm waiting
Like the idea, but how do you replce the .txt file, as they're protected, and you can't edit the propeties.
How about adding a 33.txt, anybody know if that adds another level?
bobajob14 said:
Like the idea, but how do you replce the .txt file, as they're protected, and you can't edit the propeties.
Click to expand...
Click to collapse
Did you try edit the properties in Total Commander ?
I'm not sure wether I changed them or not. But I was able to replace the file, and play this new level.
Yes - but whenever I change the attributes, it doesn't save and just reverts back to "read only".
bobajob14 said:
Yes - but whenever I change the attributes, it doesn't save and just reverts back to "read only".
Click to expand...
Click to collapse
mmh.. stange behaviour. In Total Command, you can File->Edit these files and save changes.
Maybe afterwards, you can make changes, at least I can.
Great - I was opening, editing, then saving, which doesn't work.
Going File, edit, save works a treat.
Nice level by the way!
glacieruk said:
How about adding a 33.txt, anybody know if that adds another level?
Click to expand...
Click to collapse
I can confirm that just adding a 33.txt file to the windows directory does NOT add a 33rd level.
Can't see any point in adding more levels when you can alter the levels anyway.
It reminds me of changing the levels on jet Set Willy!!!!
So what are the setting for the later levels? With the uneven floors?
Can we perhaps have 2 instances of teeter
put it in its own folder, /teeter2/ or whatever, copy all the files across from the orginal version.
Then, edit the original files, so we have an all new version of the teeter game.
If someone can group all the needed files, graphics, txt files etc, il work on editing all 32 levels and producing a new version.
dzign-it said:
So what are the setting for the later levels? With the uneven floors?
Click to expand...
Click to collapse
Including a line with :
Code:
D 0
Does the trick..
Has anyone got any further with this?
In the mean time I have found a way to have another 32 levels with editing anything.
Lye on your back and hold your diamond above you, screen towards you (of course).
Then try the 32 levels again. It is very difficult.
Pete
best thing would be to make a level-editor for the game
just drag the holes and walls and press export
Helllo! I am Russian, my English is not very good, but I have not success with my idea in my country (nobody cares about health).
I want to talk about absolutely another way for health caring, if you compare this with traditional design and usability.
Now we have a LOT of people with glasses. People take their first glasses in childhood, and most of them using tablet or PC very often, and this is really bad. Also, we can see something like this (it's not me , and it's very bad to.
Why his back is a curve? It's not only "bad habbit" of one man, it's a problem of many people . I think that the reason of bad back and glasses is very simple and stupid - he (we) physically can not see text well, and glasses or curve back it's a trying for compensation!
So, if we want to have health people, developers should rebuild old methods of text displaying, because they are not compatible with our health!
Most of Russian spend a lot of time for sitting in our social network. VK.COM . If we talk about PC (not mobile phone or tablet), it uses 11px font by default! It's not only very small font, it's very low detailed font, especially, if we remember, that "program" DPI is 96 (in paper this is 300). Really display DPI in windows does not matter - font drawing in 3 times less.
I want to say we should use 16px/12pt font size by default, and stop use small font size. It's something like this (if we say about detalization)
Why 16 px? Firstly, it is compatible with 12 pt (12pt*96dpi/72=16px). So, we can use 16px not only in web, but also in Window interface. Secondly, I want to say that "bigger is better", but 18px (for example) in most of font look absolutely different (bolder) with 12-17px, it is unusual for some people.
Also, I want to say about features of human text perception. Long line length (more 100 symbols) is not good for us, and text understanding becomes worse. If we read books, line length physically can not be very long, but in the Internet a lot of text (for example, Wikipedia) do not consider this. Bigger font size can reduce line length, but developers should to consider it.
I mean, that most of children hate reading, because this associated with big eyes's strain (small font-size), curve back and inability to get text well (loong line-length).
Also, some rules are existed - if we use bigger font and shorter line-length, we should reduce line-height. Default line-height is 150%, I think we need to reduce it to 136%.
So, these principles can be simple realized in CSS:
*{font-size:16px;
line-height:136%}
I called it ESI - eyes saving interface, and it have realization in plugin, which load custom CSS for sites. There is not only font-size and line-height, it includes rebuild site rebuilding. I does not make it good, but something like this:
It's usual VK
It's ESIed VK
It can looks unusual and bad, if compare it with traditional representation of design, but I believe it's better for health.
ESI is better, than scaling, because we don't lost information, and ideally we can control base FONT-size.
It's YouTube
It's ESI YouTube.
Ideally, user need to have an opportunity for manual tuning of base text parameters.
It's wikipedia's control (prototype). You can choose font-size, line-height, max-width, and you can change font-family (for big texts it's preferred use serif, but apply it for every element it's too global)
Also, ESI realized to Windows in themes, you can download it and try. You can apply it correct to the Windows 7 (maybe Vista) only, because Windows 8 has independent font setting.
But Windows have some "bug" - you can set 12pt for icon's text, but horizontal spaces are not in theme. It means, that icon's names will look like
«Wind...» int 12 pt, not «Windows» in 8(9?)pt. In Windows 7 you canenlarge horizontal spaces to 85 (I prefer numbers that are divisible by 17) or something, but in Windows 8 you can not control it, maybe in registry.
So... I think that ESI idea should have some support. Suppose I can rebuild every program and site for comfortable of my eyes, but it's quite hard and eats my time. I'll still see people with poor eyesight and curve back, who hate reading, and I believe, that some developers can affect on it.
Now, you can test ESI with my plugin (it's Stylish with little mod) and give your opinion. You can install it using google chrome bit.ly/esi_c or bit.ly/esi_o for opera. Then you can find esi styles for some sites, Facebook (I did not work on it), Wikipedia, YouTube...
I can not post external link for images...
It's good someone's passionate about this and I think it would be a good idea. I hope one day you vision is achieved (no pun intended)
you can do it!! :silly: