
28th April 2010, 12:40 PM
|
Elite Recognized Developer - OP
Thanks Meter 3942
Posts: 2,613
Join Date: Nov 2007
DONATE TO ME
|
Quote:
Originally Posted by 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.
|
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
|

28th April 2010, 01:03 PM
|
Senior Member
Thanks Meter 8
Posts: 362
Join Date: Aug 2007
Location: Islamabad
|
Quote:
Originally Posted by 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
|
Awesome, exactly what I needed to know. I'll try this out ASAP.
-----------------------------------------------------------------------------
Google Nexus S
-----------------------------------------------------------------------------
ROM: Android Open Kang Project ICS
Radio: I9023XXKI1
Kernel:SG-NS-ICS Kernel
Setup: 100MHz-1100MHz, Deep Idle, BLN, SmartassV2, cfq
-----------------------------------------------------------------------------
IfAmericansKnew.org
|

29th April 2010, 05:50 PM
|
Senior Member
Thanks Meter 5
Posts: 956
Join Date: Dec 2008
Location: Scotland
DONATE TO ME
|
Quote:
Originally Posted by 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
|
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.
XDA IIi ROM: 1.11.00 WWE Radio: 1.04.0 ExtROM 1.11.171 WWE
HTC Kaiser 1: ROM: Polymod 2.1D Final-Dark : Radio: 1.65.21.18
HTC G1 Dream: GammaFly V1.3 RC2, AmonRa, DangerSPL, Radio 2.22.27.08
Polymod 2.1D Final Version: It's Alive!
Android boot splashes and boot animations (for Kaiser )
|

29th April 2010, 07:34 PM
(Last edited by xPreSiDenT; 29th April 2010 at 07:45 PM.)
|
Senior Member
Thanks Meter 8
Posts: 362
Join Date: Aug 2007
Location: Islamabad
|
Quote:
Originally Posted by 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.
|
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?
-----------------------------------------------------------------------------
Google Nexus S
-----------------------------------------------------------------------------
ROM: Android Open Kang Project ICS
Radio: I9023XXKI1
Kernel:SG-NS-ICS Kernel
Setup: 100MHz-1100MHz, Deep Idle, BLN, SmartassV2, cfq
-----------------------------------------------------------------------------
IfAmericansKnew.org
|

29th April 2010, 10:14 PM
|
Senior Member
Thanks Meter 5
Posts: 956
Join Date: Dec 2008
Location: Scotland
DONATE TO ME
|
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
XDA IIi ROM: 1.11.00 WWE Radio: 1.04.0 ExtROM 1.11.171 WWE
HTC Kaiser 1: ROM: Polymod 2.1D Final-Dark : Radio: 1.65.21.18
HTC G1 Dream: GammaFly V1.3 RC2, AmonRa, DangerSPL, Radio 2.22.27.08
Polymod 2.1D Final Version: It's Alive!
Android boot splashes and boot animations (for Kaiser )
|

30th April 2010, 01:17 PM
|
Senior Member
Thanks Meter 106
Posts: 485
Join Date: Jul 2008
Location: Cracow
|
Quote:
Originally Posted by 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?
|
I tried this, but it's so blury that I had to revert to 240x320x107...
Now using: Xperia Neo V, Nexus 7 16GB
Past: Samsung Omnia 2 (GT-I8000): WM 6.5.3, CM6; HTC Kaiser (HardSPL 3.34, Radio: 1.71.09.01): WM6.5.3, CM6
|

30th April 2010, 03:27 PM
|
Senior Member
Thanks Meter 5
Posts: 956
Join Date: Dec 2008
Location: Scotland
DONATE TO ME
|
Quote:
Originally Posted by voyteckst
I tried this, but it's so blury that I had to revert to 240x320x107...
|
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'.
XDA IIi ROM: 1.11.00 WWE Radio: 1.04.0 ExtROM 1.11.171 WWE
HTC Kaiser 1: ROM: Polymod 2.1D Final-Dark : Radio: 1.65.21.18
HTC G1 Dream: GammaFly V1.3 RC2, AmonRa, DangerSPL, Radio 2.22.27.08
Polymod 2.1D Final Version: It's Alive!
Android boot splashes and boot animations (for Kaiser )
|

30th April 2010, 04:41 PM
|
Senior Member
Thanks Meter 106
Posts: 485
Join Date: Jul 2008
Location: Cracow
|
Quote:
Originally Posted by 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'.
|
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.
Now using: Xperia Neo V, Nexus 7 16GB
Past: Samsung Omnia 2 (GT-I8000): WM 6.5.3, CM6; HTC Kaiser (HardSPL 3.34, Radio: 1.71.09.01): WM6.5.3, CM6
|

30th April 2010, 05:51 PM
(Last edited by zenity; 30th April 2010 at 05:54 PM.)
|
Senior Member
Thanks Meter 5
Posts: 956
Join Date: Dec 2008
Location: Scotland
DONATE TO ME
|
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
XDA IIi ROM: 1.11.00 WWE Radio: 1.04.0 ExtROM 1.11.171 WWE
HTC Kaiser 1: ROM: Polymod 2.1D Final-Dark : Radio: 1.65.21.18
HTC G1 Dream: GammaFly V1.3 RC2, AmonRa, DangerSPL, Radio 2.22.27.08
Polymod 2.1D Final Version: It's Alive!
Android boot splashes and boot animations (for Kaiser )
|

5th May 2010, 06:39 PM
|
Member
Thanks Meter 0
Posts: 35
Join Date: Jul 2009
|
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...
|
|
|