yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] DmK75:
106 is minimal and maybe optimal density for QVGA.

On this density apps for HVGA displays fully on QVGA screen.
[Tilt, TyTN II, MDA Vario III Android Development] jt131:
I can confirm 106 dpi works fine on my kaiser. Two things though. The notification bar at the top is no longer visible. I can see the signal and battery icon just fine but the rest of the bar is gone. Second problem is that my favorite game "SkyForce" don't start anymore. Used to work fine before... Oh well...

Any idea on what the maximum could be?
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Some research results.

DPI = Dots Per Inch, and is normally used to describe printer quality/resolution, the correct term for Pixel Density is PPI, or Pixels Per Inch. Since the number and size of pixels cannot physically be altered we should be using the 'Optimum' PPI based on the physical PPI/screen size of our devices.

Theoretically, PPI can be calculated from knowing diagonal size of screen in inches and resolution in pixels (width and height). This can be done in two steps:

1. Calculate diagonal resolution in pixels using the Pythagorean theorem:

2. Calculate PPI:

dp=SQRT(wp^2+hp^2)

PPI=dp/di

where

dp is diagonal resolution in pixels,

wp is width resolution in pixels,

hp is height resolution in pixels and

di is diagonal size in inches. (This is the number advertised as the size of the display.)

For example, for a 20" (50.8 cm) screen with a 1680x1050 resolution, we get a 99.06 PPI.

Note that these calculations are not very precise.

Model	Diagonal	Pixels	PPI

Google Nexus One	3.7"	480×800	252*

HTC Dream	3.2"	320×480	181

HTC Magic	3.2"	320×480	181

HTC Hero	3.2"	320×480	181

HTC Touch Diamond	2.8"	480×640	286*

HTC Touch Pro	2.8"	480×640	286*

HTC Touch HD	3.8"	480×800	246*

HTC Touch Diamond2	3.2"	480×800	292*

HTC Touch Pro2	3.6"	480×800	259*

HTC Tattoo	2.8"	240×320	143*

HTC Touch2	2.8"	240×320	143*

HTC Wizard	2.8"	320×480	143

HTC HD2	4.3"	480×800	217*

HTC Kaiser/TytnII	2.8"	240x320 143*

*Approximate calculation based on given display size.

So the 'Optimal' PPI ( or DPI if you prefer ), would be 143, provided you are using 240x320, for other resolutions you would need to calculate the optimum PPI using the above formula ( note that the diagonal screen size remains the same, only the screen resolution changes).

Note: I use 320x428 res normally, and have set PPI to 144 ( rogue tools does not like me, refuses to settle on 143, lol), and it actually looks pretty good, but remember that although I use a 320x428 resolution, the physical screen resolution is always 240x320
[Tilt, TyTN II, MDA Vario III Android Development] myn:
^-- Awesome post

I am a big 320x428 fan and for awhile I was using 160 as the pixel density. I am gonna have to give 144 a try.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Thanks, it's a collection of information from a few sources, it's not my own work, all I did was put it all together and make it relevant to us kaiser owners.

144 seems indeed to be the optimum PPI for kaiser, I used to use 120 on myself, but found it a little too small, after changing to 144 everything looks 'right', I may try a variety of resolutions and PPI settings, but I think 144 is the magic number, (143 is the 'actual' optimum number, but 144 or 142 is the closest I can get with rogue tools, no idea why it won't set 143).
[Tilt, TyTN II, MDA Vario III Android Development] fldash:
With this, are some apps cut off or does everything display correctly?
[Tilt, TyTN II, MDA Vario III Android Development] jt131:
I can set 143 just fine on my Kaiser but since there are other values I can't stick to, maybe in the next version we can also have a box where we can actually type the number instead of using the slider.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
So far I have had no problems with any of the apps I use, however, depending on the apps you use, your own experience may be different.
[Tilt, TyTN II, MDA Vario III Android Development] celticchrys:
Seems to work on my Vogue

Thanks for the new tool, Myn!

It seems to work so far for me, although I would definitely vote for a box where a value could be entered. I also have a great deal of trouble settling directly on many values with the slider.

Can anyone suggest the best benchmark or test to use?
[Tilt, TyTN II, MDA Vario III Android Development] myn:
FYI updated Rogue Tools to ver 1.1

Changelog:

04/27/2010

Added device support for Nike

04/24/2010

Version 1
[Tilt, TyTN II, MDA Vario III Android Development] myn:
PS. I am now in love with 320x428 @ 144 dpi.

Thanks for bringing this to everyone's attention.
[Tilt, TyTN II, MDA Vario III Android Development] xPreSiDenT:
For more precise value input, I dont think we need a text box, especially for our devices which have directional buttons. Just tap on the slider, and use the directional buttons for fine selection of values.

Btw all this praise for 320 x 428 makes me want to try it... any way I can change the resolution or will I have to flash a new nbh? And is the screen blurry? I tried a higher resolution once but because of the blurriness I've been using 240 x 320 ever since.
[Tilt, TyTN II, MDA Vario III Android Development] myn:
Yeah you'll need a new NBH (320x428).

My impression in contrast to 320x428@144

320x480@160 = More blurry

240x320@120 = Most clear but apps like the phone don't render correctly

240x320@110 = More blurry
[Tilt, TyTN II, MDA Vario III Android Development] xPreSiDenT:
Awesome, exactly what I needed to know. I'll try this out ASAP.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Note that the further away you are from 143PPI the less clear it becomes, which was the reason I decided to go looking for a way to calculate the correct density value in the first place.
[Tilt, TyTN II, MDA Vario III Android Development] xPreSiDenT:
Just set the density to 143 @ 428x320 and I must say this is awesome. Thanks for the research.

edit -Just tried 144 and it seems to me 144 is sharper than 143. Anyone else tried both?
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Not tried 143 actually, since 144 was as close as I could get, there should be very little difference between the two, however the figure of 143 is a calculated one, and 144 may give better performance due to it's 'even-ness', not sure really, lol
[Tilt, TyTN II, MDA Vario III Android Development] voyteckst:
I tried this, but it's so blury that I had to revert to 240x320x107...
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Have you tried 320x428@144 or 240x320@144? Not that it should make any difference, however the clarity at 428x320@144 is pin sharp and just feels 'right'.
[Tilt, TyTN II, MDA Vario III Android Development] voyteckst:
I just tried 240x320x144 and as I thought everything was so big ;-)

Later I will try 320x428x144. Last I set dpi to 143 and there probably was my mistake.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
well 240x320@143 is pretty much the same as 144, however it will look larger than the 320x428@144, which so far is my favourite settings on donut and eclair.

The larger the ppi value, the smaller everything looks, since it tries to fit the 160 pixels onto a screen, which is physically only 143 pixels per inch, 240x320 @107 should look larger than at 144, since it only needs to display 107 pixels per inch.

If you imagine a square of pixels 100x100 then at a ppi of 107 it will take up almost all the screen, however if you have the same 100x100 square at 144 ppi there will be 44 pixels not covered. Since the physical screen area is 240x320 pixels this makes the square on the 144 ppi screen seem smaller.

Confused? I was too until I actually worked it all out, but trust me, thats the way it is , larger ppi=more screen area.

Just a thought, but if we use ppi numbers that are 'square' then we may get cleaner looking screens, since pixels are square, incidentally, 144 is 12^2, so using a squared value may mean less distortion at the pixel level, as I said, just a thought :)
[Tilt, TyTN II, MDA Vario III Android Development] dukeofdream:
i was trying to overclock my tytn under windows for a while but everybody said that you can't overclock this processor...so now the developer of this tool proved them wrong :) any chance of getting it for windows?i tried android but it's too unstable to use it every day...sometimes i'm not able to receive calls...someone calls me the line it's good but the phone isn't ringing...it freezes all the time etc...
[Tilt, TyTN II, MDA Vario III Android Development] dukeofdream:
i tried the program 4 times in a row...everytime i pressed the set clock button the device freeze...i guess i'm not lucky :(...
[Tilt, TyTN II, MDA Vario III Android Development] mantorp:
I set my Kaiser to 143 and while things are crystal clear the icons overlap a little and part of the dialer is off the screen to the right. Great App though and thanks for the explanation of the dpi settings.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Ok some more research:

Following my previous result I decided that since TFT LCD panel pixels are square, and 144 seems to be the optimum PPI for 240x320 panels, that perhaps the best PPI settings should be squared numbers.

64 -	8

81 -	9

100 - 10

121 -	11

144 -	12

169 -	13

196 -	14

225 -	15

256 -	16

As you can see the following PPI numbers, each whole number has a corresponding potential PPI setting.

The reason these should display properly is that, since each pixel is square, then it follows that any number outside of the above table, will mean that each pixel block will attempt to display some of it's neighbours image, as well as it's own, reason being that we are trying to force a square pixel block, to display a rectangular image that is larger, ( or smaller ), than the block is.

Ok anyone who is still following that, may like to try using some of these values and see what results you get, I still prefer 144, but squared values should give a nice crisp image.

Oh, and don't try values below 100, not sure what the upper limit is tho ;)
[Tilt, TyTN II, MDA Vario III Android Development] leona:
Thanks for developing this, found it really useful in adjusting the DPI.

As for future features, do you think its possible to add the ability to adjust the system's font size / style? I find the default font small and hard to read, a hack to increase this would be great.
[Tilt, TyTN II, MDA Vario III Android Development] leona:
Zenity, with regard to the screen PPI (DPI), I found that going any higher than 106 broke the dialer, then I installed a dialer fix that allowed me to go to 120, but if I go to 144 surely this will break the dialer again, (when I say break, I mean half the buttons are missing), I run my res at 240x320, so how do you keep your dialer intact when using these settings?
[Tilt, TyTN II, MDA Vario III Android Development] mnjm9b:
first of all,

Great tool.

I am sure it will be a 'must have' for many future roms to come.

just a thought on more "Rogue" type settings,

1. screen resolutions

2. battery settings

3. wifi power settings

4. led settings

5. keymapping

6. ppp.nostart= 0/1

7. mem limits

8. compcache/swap settings

9. system rw/ro

10. fonts

I think ten is enough for now...I have more...LOL
[Tilt, TyTN II, MDA Vario III Android Development] xPreSiDenT:
144 is not at all meant for 240x320, it works best for 320x428.
[Tilt, TyTN II, MDA Vario III Android Development] citrit:
To get exact settings in the Density slider first select the Density Tab, then move the slider a bit. Then press the down key on the front panel, the slider will be highlighted. Then use the left and right and you will be able to adjust by one.

This also works for the over clocking but it moves by 30 each time.
[Tilt, TyTN II, MDA Vario III Android Development] DmK75:
I set resolution to 360x480 in defaul.txt and leave 160 density.

Is make good effect: all 320x480 apps fits to screen but not have distortions like oval instead round.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Ok a few notes on this weeks research, for those of you using 240x320 res, lower density is better, 100 or 121, for 320x480, 144 is good, for 320x480 169 seems to be the best candidate, purely from a mathematical standpoint, however it also seems to be build dependant to an extent.

Also note that 240x320 and 320x428 have the same aspect ratio, where 320x480 is slightly stretched vertically in comparison.
[Tilt, TyTN II, MDA Vario III Android Development] :
Overclocked to 600mhz. So awesome. Will post results :P

EDIT: 600mhz leads to a fuzzy screen such as the one of a bad channel on an old tv. Clocking down to 500 again. Went to 512 as I figure the process er will appreciate it more.
[Tilt, TyTN II, MDA Vario III Android Development] DmK75:
I have stable working with overclocking up to 550, if i set more device freeze.
[Tilt, TyTN II, MDA Vario III Android Development] myn:
Excellent list! This should keep me busy until Gingerbread comes out :).

I am thinking of expanding Rogue Tools some more. This list is a great starting point.

Very interesting research.

I am going to give 121 a try with 240x320.
[Tilt, TyTN II, MDA Vario III Android Development] mnjm9b:
Just a couple more items to add to your list.

1. manage startup apps/services

2. manage apps/services that run while phone is sleeping.

let me know if I can help with anything on the list.
[Tilt, TyTN II, MDA Vario III Android Development] mr_pablo:
RogueTools is working really well for me atm, apart from one feature - "Set on Boot" for overclocking.

I set my speed to 450-500mhz, click set on boot, close roguetools, sleep phone, wake it up, mess about for a bit, reboot phone (power off, wait, turn on) and the cpu is back to 400mhz :(

when i change the value it says roguetools has superuser access, which is fine.

anyone else encountered this issue?

btw, using CyanogenMod 6 on HTC TyTn 2
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Whole screen

Hey there, first I wanted to thank you for such a great app for our Kaisers (and other models). I've been following and testing all suggested settings for dpi.

I am running 320x428 at 144 but I have noticed in several apps, better terminal for example, the left and right sides do not cover the whole screen, that is a thiner screen than what we have. this also causes my lockscreen apps to show part of the background image and i've been messing around and found that 146 dpi makes them reach the sides, however i do not know if the top or bottom are showed completely or are cut.

Just thought i'd share my experience with you all and if anyone has any idea on how to verify if i am cropping the top or bottom, i am all ears.
[Tilt, TyTN II, MDA Vario III Android Development] kaluaabyss:
Same issue, HTC 8925 using dzo's FroYo w/ haret.
[Tilt, TyTN II, MDA Vario III Android Development] tuzi215:
Is it work on wm or android? and what's the url of the market talked above thx :)
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
This app is for Android :) as I imagine you are running winmo I am gonna tell you Market is an application on Android that lets you browse, search, and install applications both free and paid.
[Tilt, TyTN II, MDA Vario III Android Development] miazza:
Om Polaris , above 120 some apps are crashing...

110 would be the best but ...

miazza
[HD2 General] JonFolse:
Title is self explanatory. Im just trying to see if I should downgrade to the 2.07 or upgrade to the new 2.10, depending on the rom of course. Im currently on 2.08 how has battery life been on the other radios???
[Touch Cruise Android Development] myn:
[APP] RogueTools v1.1 - [Overclock & Change Screen Density] - [Updated: 04/27/2010]

I now present you with RogueTools v1.1.

Summary:

This application is designed for the Vogue, Kaiser, Polaris and Nike devices. It allows you to dynamically overclock your device as well as change the screen density.

Requirements:

This application requires write access to your /system so this will only work on EXT2 and NAND installations.

Overclocking Notes:

Overclocking results will vary. Based upon the beta test results everyone was able to Overclock to 500mhz and have very stable results. Above this results really were mixed. Give it a try, I'd love to hear your results.

To download, search in the market for "RogueTools"

Screenshots:

Before (400mhz) and After (500mhz) CaffeineMark Benchmark

HUGE thanks to all of the beta testers. You guys did an outstanding job!:

citrit, cp0020, damianiw, DmK75, dzo, GriloVirante, Incubus26jc, inertone, jnadke, mblaster, Millence, mssmison, paipo, pyrator, scouzer, vrflyer

Disclaimer:

As always, I’m not responsible for anything that happens to your phone while using these files.

Future Versions:

I'm looking for some creative ideas on other additions you'd like to see added to this application. So if you have some thoughts, please let me know.

Changelog:

04/27/2010

Added device support for Nike

04/24/2010

Version 1
[Touch Cruise Android Development] imfloflo:
Great work !
[Touch Cruise Android Development] DmK75:
This is undoubtedly an excellent tool, thanks to Myn!
[Touch Cruise Android Development] iseeka:
thanks a lot! great and needed app!

trying at 500mhz
[Touch Cruise Android Development] retsam88:
I though that overclock was impossible on Qualcomm MSM7200 processors.

If it works on android why it wouldn't on WM6?

Also *if* it works it could be very harmful to your device.
[Touch Cruise Android Development] iseeka:
tried to benchmark with neocore but doesnt seem an appropiate app

wich one should we use? or there is any performance data?
[Touch Cruise Android Development] DmK75:
I get maximum 37.2FPS instead normal 28.9

But i overclocked device to real 528Mhz, it possible with "Open Overclocker" app.

It app allow apply RogueTools frequency w/o wakeup, and show real result e.g "400"=384 and "550"=528Mhz.

"Linpack" app i use for testing MFlops.
[Touch Cruise Android Development] myn:
CaffeineMark is a nice app to benchmark your overclocking. Available in the market.
[Touch Cruise Android Development] retsam88:
Can anyone explain me how does it work?

And again, whats so special about android so it's possible to o/c QUALCOMM 7200 processor?
[Touch Cruise Android Development] iseeka:
I do not know but there are some facts about android...

-it is possible to enable video acceleration in most devices (that in wm not)

-and now this!!

It is great

now if DZO manage to enable wifi with all the latest updates included that would be almost perfect (BT)

thanks a lot devs!
[Touch Cruise Android Development] Backwardsblade:
is there a download link for any of use without access to the market (no data connection?) An apk would be great!!

Thanks!
[Touch Cruise Android Development] lexie2797:
hey i use you're android version but from sd is there a possibility to make such thing for sd boot maybe in a config file or something like that?
[Touch Cruise Android Development] myn:
FYI updated Rogue Tools to ver 1.1

Changelog:

04/27/2010

Added device support for Nike

04/24/2010

Version 1
[Touch Cruise Android Development] retsam88:
Can you explain how EXACTLY this program works? I mean the main differences and why it cannot be done in Windows Mobile enviroment.
[Touch Cruise Android Development] criosray:
How does it affect battery life?
[Touch Cruise Android Development] Lord Meshadieme:
Im not very keen on mobile device hardware and their capability but something like Undervolting would be cool, as a new feature to dynamically control voltage reduce battery consumtion etc.
[Touch Cruise Android Development] retsam88:
is this project dead?
[Touch Cruise Android Development] DmK75:
Why? Is available on Market, stable release.

Only one thing unfinished - wrong clock slider, real cpu clock is 96% from this.

E.g 400*0.96=384, 500 is 480 etc.
[Touch Cruise Android Development] retsam88:
i wonder if they could port this to windows mobile, as i can't use android..
[Touch Cruise Android Development] DmK75:
Need to ask NetRipper.

Perhaps he try to add support our devices into Msm7kCpuSpeed.

With this tool i have stable overclock on Diamond2, up to 768Mhz.
[Desire General] halfsjj:
I believe that the HTC Desire is branded on the HW and the SW, but my question is does anyone know how to remove the software branding and make it like a standard unlocked version?

Is it possible to flash the Euro ROM and not screw anything up? If so, can someone please point me to that info.

Any help would be appreciated.

Thanks,
[Hero CDMA Themes and Apps] jonesdana:
I loaded the following dialer "DarchVader_Dialer_DamagedTrev.zip" and it has a goofy picture of Homer as the default pic. Does someone else have another "black dialer" or stock dialer or way to simply change the default picutre?

Thanks!
[Hero CDMA Themes and Apps] alexthearmo:
Click on the theme in my signature and scroll down to the bottom of the first post. There are a couple of black dialers to.choose from. Always nandroid first. Let me know if that works for you.
[Hero CDMA Themes and Apps] alexthearmo:
Actually, darchvader might be based on a legend Rom...(im not sure)....if it is than my zips wouldn't work. Either way, nandroid.
[Hero CDMA Themes and Apps] gomorrah:
Actually it is. I made it for Legend, and Treve ported the dialer for sprint based Roms without changing the picture. :D If you want to get rid of Homer I posted a phone.apk, but that got erased with the rest of the theme thread. Or you can replace him yourself. The picture is in Phone.apk and its called phone_default_icon_png. You can change it to whatever you want as long as its in reasonable standards(meaning sizes).
[Hero CDMA Themes and Apps] jonesdana:
Thanks for the assistance. Actually when it came to replacing it... I struggled to think of what I really wanted. I threw this together as a temp replacement. Piece of cake to do after your help.

Thanks!
[HD2 General] Tref:
I did a search but didn't find much. Any word on the street about when AT&T might be putting the HD2 in their stable?
[HD2 General] zarathustrax:
They won't. The HD2 is already over 6 months old. Plus they wouldn't have anything that might compete with their iphone sales.
[HD2 General] sancmat:
HD2 is a T-Mobile Exclusive. if you want it for AT&T I think the Telstra version is at&t 3g compatible.
[HD2 General] Tref:
Is TMOUS advertising it as an exclusive?

I'm not familiar with Telstra. Is it WWE out of the box? And it will work on 3G, not just Edge?

Thanks
[HD2 General] Tref:
The TP2 was more than 6 months old when it was added by AT&T...

And it doesn't compete with the iPhone any more than the HD2 would. Besides iPhone 4.0 is coming out soon so I don't think potential iPhone sales will be hurt by "just another" WinMo device.
[HD2 General] zarathustrax:
Yeah, the australian Telstra HD2 will work on the 850 band, which AT&T uses for most of there 3g. You'll have to check and make sure at&t's 3g is on the 850 band in your area. They use another band for 3g in some areas. The Telstra HD2 will cost you around $800 to get it imported, but it's unlocked already, so you can put your at&t sim card right in and use.
[HD2 General] zarathustrax:
Well, either way, it is advertised as T-Mobile exclusive in the US, so it won't be going to AT&T.
[HD2 General] Tref:
Good info guys, thanks. Guess I'll have to exhale now since holding my breath til AT&T brings it in isn't going to work. Anyone know of any reputable vendors with Telstras?
[G1 Q&A, Help & Troubleshooting] hoshmosh:
Im having troubles with the new 2.22.23.02 my 3g sucks now -.- really hard.

Can i downgrade back to 2.22.19.26I? Sorry if this has been asked, i searched but kept finding threads how to update...
[G1 Q&A, Help & Troubleshooting] hoshmosh:
i see why no one post things inside of the Q&A sections...
[G1 Q&A, Help & Troubleshooting] borodin1:
You can downgrade to 2.22.19.26I with no problem.
[G1 Q&A, Help & Troubleshooting] jshealton:
I am using JesterBlur 1.2.5 which is a cupcake ROM. How do I update the market to the one that comes with Donut? I tried to push vending.apk and marketupdater.apk to my phone but that did not work. It is still the old black market. Any help would be appreciated.