Related
Can someone please explain the easiest way to get VGA resolution on my XDA Exec? Am I right in assuming that although the screen has a 640x480 resolution, they use pixel doubling to negate it and it actually runs at the same resolution as my Dell Axim X5 (320x240)?
Is there a simple registry hack that disables this, or do I have to botch around installing a hack and then trying to botch all my apps to run in the new resoluition? Does anyone know if TomTom5 works in VGA mode?
I'm sure this has been covered already, but some of the topics are 13+ pages and date back quite a bit, and the site is a tad slow to trawl through lots of postings and searching for VGA brings up hundreds of topics.
Thanks in advance for your helps folks.
This is the best thread - there is a ZIP file on page one that I dobwloaded and it contains all the instructions to get things working
http://forum.xda-developers.com/viewtopic.php?t=32217
this is the post I didn't particularly want to have to trawl through, as it's 13 pages long and really slow to switch pages.
TheFair - as noted above, there is a zip containing instructions. You don't have to read all 13 pages, although it's useful background reading - we didn't write all 13 pages just for fun .
I had to do VGA again yesterday, for the first time in a long time, and it's very simple. Basically:
Unzip, copy files to windows, click ozvga, reset.
V
OK, thanks Vijay. Will I need to install your Bigphone application and replace other system apps once done? Also, any idea if TTN5 works in VGA mode? As my XDA is used primarily as a SatNav, I'll stick with QXGA if it's not going to work properly.
Thanks
thefair1973: VJBigPhone can be used to make the phone app usable again, (I don't use my Uni as a phone, so I don't use it ) Replacing system apps etc is optional, but obviously helpful if you use the apps effected.
No idea about TTN5, but it's basically one click to revert to QVGA, so I'd do a backup and just give it a go if I were you!
V
great, thanks very much for your help Vijay.
I use TTN5 and VGA. TTN appears to drive the screen directly, so you don't get any extra resolution, but it works fine
I use TTN5 and VGA. TTN appears to drive the screen directly, so you don't get any extra resolution, but it works fine
Is VGA in Universal already perfected? Which applications are still not showing right upon application of this hack?
Just finished reading the VGA thread. I have a headache now. One important question though, I am using the latest JASJAR ROM, would OZVGA work on this new ROM?
Yes, I did it yesterday with no probs.
V
vijay555 said:
Yes, I did it yesterday with no probs.
V
Click to expand...
Click to collapse
Thanks Vijay! I just performed a hard reset, so I am ready to try something new. I downloaded the file compliled by Khashim I believe, I'll check if I got his name right. Which one did you use? Is it the file from Carnivor or Khashim? (Yes it is Khashim.)
I think originally I used Carnivor's, but frankly, I had an old set of files that had been sitting on my SD card for some time (I've posted the zip in that thread as well, towards the end).
However, I don't think there's a big difference. Use the one that sounds positive. It's easy to copy over new files if required. But you should only need to fiddle with it if you see problems in some of your apps. I don't use many apps, but I don't see any problems.
V
I tried. It does look wonderful for browsing using PIE. But I do agree that the font are too small. I also tried VJBigPhone and it did made the buttons larger, but the bottom part has a different color. Did I miss something about the skin?
Comm Manager has the same problem about the skin on the bottom part.
I love how ozVGA changes PIE, but weighing the benefits on other applications I use, I decided it is not for me at the moment. I hope someday someone can implement an application to run a specific application on VGA mode selectively and not implement it on the whole device. Thanks for the responses.
cktlcmd said:
I love how ozVGA changes PIE, but weighing the benefits on other applications I use, I decided it is not for me at the moment. I hope someday someone can implement an application to run a specific application on VGA mode selectively and not implement it on the whole device. Thanks for the responses.
Click to expand...
Click to collapse
try tweaks 2k2 vga brute force
cktlcmd: there is a background fix for the phone on my webpage and in the VJBigPhone thread. I haven't looked at the comm manager fix yet.
Waiting for a more selective pixel doubling patch may take a while or be futile. I think it's possible but I've not had time to implement my own hack yet.
V
I've done the VGA hack & overall its a major improvement.
The size of toolbars & the fact that some fonts are too small is a nause, same as the programs that don't display properly. But its SOOO good to see so much text on the screen.
To be honest, if it doesn't really run at 640x480, is it not a case of false advertisment? Just a thought.
xyon: it is running at VGA (640x480), but just making everything sharper and emulating 320x240. I asked an Orange spokesman once and he said they were going for "quality over quantity". I suspect they just didn't know how bloody persistent haxxors could be
I prefer 640x480, but it does make day to day usage inconvenient. Perhaps all apps will eventually have native 640x480 support. But given how many years it took to go back to square screen support, I'm not very hopeful!
V
Just a dream or is it reality?
See the attached pictures. 1 pictures show O2SMS is in VGA mode when my PPC is in QVGA mode, the other shows O2SMS when my PPC is in VGA mode.
Anyone has any idea how this can be done?
How what can be done? Live switch from QVGA to VGA?
V
I do not know how, it is in the O2SmsPlusV1.1.
Maybe you can check it out and enlighten all of us.
Or someone who wrote this software can release the O2SmsPlusV1.1 Source Code.
Attached is the ZIP file of the exe files. just copy into anywhere and run or create a shortcut link and run.
Sorry, think I may misunderstand. Are you saying that on a VGA device the app looks the same, ie hires, when the device is in either QVGA or VGA mode?
This is a choice of the coder, who merely has to code his app to support the true native resolution of the device, ie VGA, rather then "emulating" QVGA on a VGA device using Pixel Doubling, which is the normal path suggested by Microsoft. Any app can be made to support VGA on a VGA device if the programer wants it to, whether you're "apparently" running in QVGA or VGA, by use of the hi res aware resource and appropriate coding. Look up "dpi aware" on msdn.
Pocket Internet Explorer can do it I think. Some other apps to.
V
Ok, now I understand. Thanks.
But the PIE smallest resolution is still not small enough to see the whole width of the explorer.
There was a tool once (can't remember it's name now) that hacked individual apps to work in real VGA. It didn't always sit well with the app, but if you really want to try this same functionality can be achieved with resource hacker.
Just add a binary resource of type "CEUX" called "HI_RES_AWARE" with the following value 01 00 to the exe of the app (note this will mess app the signature if it is a commercial software for WM 5 and may make the file unusable).
CWKJ said:
But the PIE smallest resolution is still not small enough to see the whole width of the explorer.
Click to expand...
Click to collapse
Wait for crossbow. PIE is improved on hi-res devices.
This is what I got from the iGuidance support team. I was excited to hear the solution was so simple.
Hi,
What you are asking is the capability to keep both QVGA & VGA.exe's on your PPC and be able to switch back and forth depending on your applications.
iGuidance will initially install both VGA and QVGA.exe's, but after first launch on your PPC, the program will automatically detect and keep the file according to which mode your PDA has and delete the other one.
For example, immediately after you've installed iGuidance on your PPC and BEFORE you try launching the program, under your program files\iNav\iGuidance directory, initially you will have:
iguidanceVGA.exe
iguidanceQVGA.exe
iguidance.exe
iGuidance.exe isn't QVGA nor VGA. It launches when you launch iGuidance, checks resolution of your PPC, deletes the wrong one, and relaunches the right one.
Thus, the only way to keep both VGA and QVGA exe's are to delete iguidance.exe immediately after installation, then launch iguidanceVGA.exe or iguidanceQVGA.exe manually from the program files\iNav\iGuidance directory based on your need.
Hope this information helps.
Thank you.
Support Team
www.inavcorp.com
In the next few days I hope to whip up a mortscript to see what the current res is and launch the right version for it and also test the VGA version on 128dpi (the default for 128 is QVGA, which is why I asked in the first place - it works, but the icons overlap & some other funky-but-useable stuff.)
Awhile back I posted an even easier solution. Set both of the resolution bound exe´s as “read only”. By doing this you can use the standard launcher in the usual manner.
One caveat, in 128dpi, using this method, the vga app will launch. The menus in the qvga app are better for 128dpi.
Why wouldn't you just create a .lnk to whatever executable
you wish to initiate Iguidance in qvga or vga?
That's what I actually use now. Just wanted to point out that writing a script was not necessary.
The blessing of the developer
RO is, quite frankly, much more ingenious than this solution! Sorry I didn't find it before I spouted off.
I do like the idea of doing things that are supported, and the QVGA does look better, if not perfect, in 128dpi, so I just made shortcuts to each. Also, this way if I have to flash, I can restore my start menu/programs and not worry about blowing one away if I forget to change the properties. It's more clutter, but worth the safety.
Ninja1, the world needs more brains like yours. please keep posting your thoughts!
hi
i have installed tomtom 7 on my diamond and i have one problem.
Probably because of diamond's screen resolution(640x480) during navigation poi icon are too small....there is any way for fix it?can I just resize poi icon?
I have got the same problem, during driving you can't see the small icon properly, but secondly I am using the voices as well, so rather than just the beeping sound my camera database tells me what speed camera is ahead, so this solves the issue even better.
According to your advice I did try to edit and even created a new image of 32x32, 64x64, & 128x128, but none of that work, it just start to show a blank RED icon rather than "30" written on it, so I revert it back.
Regards
Sid
sidd said:
I have got the same problem, during driving you can't see the small icon properly, but secondly I am using the voices as well, so rather than just the beeping sound my camera database tells me what speed camera is ahead, so this solves the issue even better.
According to your advice I did try to edit and even created a new image of 32x32, 64x64, & 128x128, but none of that work, it just start to show a blank RED icon rather than "30" written on it, so I revert it back.
Regards
Sid
Click to expand...
Click to collapse
yes im using voices as well,but with ipod conected to the car's hifi its hard to hear anything else
I guess this problem should appear on every diamond,but around i havnt found any discussion about it.......
So,its a common bug or just for few lucky diamonder??
I have the same problem, the icons is too little
http://forum.xda-developers.com/showthread.php?t=432178
Icons gone !
I have no icons on a Western Europe map V725.1905
But i do have them on an Benelux Map V725.1883.
I don't know whats going on, i use TT7 V7.451 (9033).
Also my WE map loads and is very slow and Benelux is very quick.
Check it out, maybe i'm the only one.
Sorry guys one more clarification, are you using QVGA Tomtom version?
As I was using the QVGA version of "7.40.9028", but now I am using VGA "7.451.9033".
VGA has got normal resolution as in the QVGA everything was TINY.
Basically it is just one EXE file to overwrite the existing QVGA exe in the device, I don't know if the moderator will allow this, otherwise I could upload that.
Regards
Sid
I'm using the VGA Black 7.451.9033 on HTC Diamond, but the radar icons, poi, ecc. are too small and remain too small even by increasing the zoom
Lancillotto69 said:
I'm using the VGA Black 7.451.9033 on HTC Diamond, but the radar icons, poi, ecc. are too small and remain too small even by increasing the zoom
Click to expand...
Click to collapse
Like me!!!
My solution: I edit TomTom.exe to run it at low resolution mode. You'll see all menus fine... and the map and navigation screen at normal size (normal as QVGA equipment).
I spoke with TomTom's service and nobody has solution, while I can use TT7 at car and easily I can see the radar warnings.
From Xda developer tread...i don't remember where......:
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.
Lucausee i have use your solution, in effect solve the problem, tnx.
Excelent fix, well done and thanks.
BC
This project is about rebuilding the touch.dll coude from the original dll assembly.
Latest package:
touch.cab
For adding the "developers certificate" ( read side node on update 21/11/08 ) you can use the following tool:
Microsoft Security Configuration Manager
--------------------------------------------------------------------------------------------------
Update 21/11/08:
Ive finally managed to rebuild the touch.dll from assembly and recompiled it and im able to boot the new touch.dll
Ive cleared some of the calls made to some old features implemented in the original file like the touch cube etc.
Be aware that this isnt for daily use and only for testing purposes. But I really need some input on speed and reliability because i cant test everything on my own ( i flash my device every 4 hours or so so not really long testing times ). If you are not affraid of hard resetting your device and are willing to participate in testing current work please do but dont keep me responsible for freezes etc
I have only tested it on udk R4 because its easy for me to test speed on manilla 2d and it gives me a good impression of daily usability. And because i removed almost all calls to the original cube code it wont be any good for cube lovers as and original HTC roms.
Keep in mind that all ive done now has been done during work in a few hours and although ive tried to be on the safe side i cant tell you all is working as its suppose to and I think i havent done more then remove about 20% of garbage out of it.
I know not all is as fast as its supposed to be but like i said im better safe then sorry and i dont wanna hardreset every 2 mins or so... Some good testing can be done in Manila2d like scrolling through images fast and scrolling through the bottom bar. Also ive noticed that scrolling through the normal "All programs" is still on the slow side ( still need to resolve a lot of scrolling issues... HTC has included a lot of codes for all sorts of winmo controls like listviews etc ) but if you open up the all programs in manila from the programs menu u will see what kind of speed it can work at minimum....
As for the priorities mentioned earlier in this thread im going to set both the priority256 and the priorityhigh256 at 109 ( original microsoft value that can be found at msdn ) in the cab file so we can test the touch interface as it was suppose to be set up... you can easily change these values as you like ( read earlier posts ). Setting it lower then 109 will give it an higher priority which will make the device suffer more from touch input... Setting it higher ( upto 255 ) will give the touch input less priority and will make rendering faster but can also come of the cost of reliability.
Side node:
Make sure your rom has the "Sample Privileged Developer" Certificate installed because i signed both the file as the cab with this certificate ( files need to be signed because of being system file and they dont get any trust at boot without a certificate ).
--------------------------------------------------------------------------------------------------
Start 15/11/08:
Ok so because i didnt had much to do this week i started digging into the touch.dll to see if there can be some solutions to the slow scrolling/stuttering etc when touching the screen.
I already found out that the graphics stuttering mostly happens due to the fact that the touch.dll is set to real-time process priority.
WinMo uses priority values from 255 (low) to 0 (real-time).. Normally touch should be set at 109 ( according to msdn ), but because htc put so much garbage in it ( touchflo related ) and it got slow as #@% they put the priority to 0 as a default and deleted the registry entries
Using IDA i found out that those registry values are still being accessed but since they are not there the default of 0 is used.
Just create the following key
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch
And create the following values in it
Name value (DWORD)
Priority256 255
HighPriority256 255
This will not speed up the actual scrolling but it will also not make the device freeze when pressing the screen... So scrolling seems more natural. ( especially in programs folder and file explorer )
So this is not a fix but a good start for now.
Already found out a few things looking at the code that can be dropped out so im going to try to rebuild the touch.dll from asm without most time expensive calls ( hopefully shrike will help me out on this one ).
Let me be the first to say thank you. I am not sure I did the things right, but my Polaris seems more alive than ever. I will post an exported regkey, please confirm that I've done it correctlly.
I have noticed an improvement in sliding in S2U2 and on everything that involves touching the screen. This indeed is a great step forward for Polaris.
Thanks for trying... As soon as development will progress ill create a cab file which will include the registry keys.
Big difference... great job,
I've noticed though that in icontact, when you scroll contacts, the animation has to finish so that it can accept new gesture, so i set it to 109, scrolling is still good and icontact work propertly..
Great find Rogro! Was irritating me how the graphic stutters whenever I scroll in programs and phonebook..
Just wondering though, if it was such a simple fix, why did they remove the reg key to begin with? as far as i can see, the impact on the processor speed seems really minimal..
I look forward to more of your discoveries..
Nice job! Performance is much better... but in the all programs list the icons all still flashing when scrolling, although its much less.
Thank you
Great job in all programme speed seems little better.
nice
thanx
Hey Rog,
Nice to see you're trying different things.
I looked at my HD but it didn't have the slowdown the Polaris has. But it also doesn't have the registry keys... so i added them and soft reset. Now, my HD's TFLO3D is really unresponsive and stutters... So maybe it's only for non-TF3D devices?
Thank's
It's working well in my M-Amine 2.0 Final Rom.
Here is the little Cab.
EDIT: If you install this cab or change the register by hand (Is the same) , the scrolling work well but maybe you will have problems with Igo, TomTom or destinator.
Please take that in your mind.
Thanks a lot Rogro!! It's wonderful for every application that uses touch scrolling.
Why do HTC engineers leave us alone with those awful bugs? Is it so difficult to add those 2 DWORD values?
Actually it fixes the screen response AND the All Programs scrolling in Manilla 2D
thanks for sharing rogro82.
cheers
Thanks rogro82.
It's working
BTW i've notice something,,maybe wrong.
When you scroll (very fast) in file explorer or program folder, stoping it(the scrolling) with a sigle tap it's not so easy. Or when you tap to stoping it ,then turning to another direction(up or down).
Also the icontact scrolling isn't good enough.
I use the "cbolumar" cab.
BTW i've notice something,,maybe wrong.
When you scroll (very fast) in file explorer or program folder, stoping it(the scrolling) with a sigle tap it's not so easy. Or when you tap to stoping it ,then turning to another direction(up or down).
Click to expand...
Click to collapse
Thats because the scrolling is still way off in terms of speed... the only thing that happens when you change the registry settings is that it will not allow touch.dll to eat all resources and hang all other processes..
Maybe you could try to set it to 109 ( what it should be on a normal driver )..
I never use any gestures or whatever so setting it to 255 works for me for now until i can start cleaning code.
TomTom7 with these settings
Nice find. But in Tomtom7 something strange happens. I have to press the screen much harder then without these reg keys. I Use M-Amine's RTM rom.
Anyone else have this or is it just me having this bug?
ViNZ! said:
Nice find. But in Tomtom7 something strange happens. I have to press the screen much harder then without these reg keys. I Use M-Amine's RTM rom.
Anyone else have this or is it just me having this bug?
Click to expand...
Click to collapse
The same bug for me with Navigon Mobile Navigator 7
kr.,
Frepke
Bug with IGO 8
The same for me , i have a lot of problems with the screen in Igo , the problem disappear after delete the register changes.
To delete this, you must go to the register and delete the new values by hand, not the touch entry but the priority entries.
Only uninstalling the cab is not valid because the driver is in use.
Thanks a lot!
It's like early Christmas!
It´s because of people like you that my Polaris is an increasingly awesome machine. Continuing like this in the near future it will teleport me from one place to the other!
Keep up the good work.
Don't ever leave us Rogro!
TT6 don't work
The screen is no usable.
I have delete all the key and now work well
ROM M-Amine 2.0 Final ITA