Max I can get is 281, but that is really small. I've tried many apps and the rom settings itself.
I dont no if is optimal solution but for me worked .... so,things i made :
-ro.hwui.text_small_cache_widtch 2048
-ro.hwui.text_small_cache_hight 2048
so.sf.lcd density la 560
persyst_sys.lcd_density 560
ro_slim_lcd_density 560
and restart ! Baaang...all is bigger.
Related
I would really love to see this on our phones:
http://forum.xda-developers.com/showthread.php?t=1543892
is it possible with our AOKP and CM9 builds? can a Dev please make this possible? as i think the size of our screen can really work this one out!
what do you think...
wow no one seems to care about this one....?
Looks like its just changing the DPI to one that is recognized as a tablet. Seems it's 129 for the GNex... he posted something showing a formula for finding the "magic number" for other devices.
From his post:
Code:
int shortSizeDp = shortSize * DisplayMetrics.DENSITY_DEFAULT / DisplayMetrics.DENSITY_DEVICE;
mStatusBarCanHide = shortSizeDp < 600;
full description here: http://baroqueworksdev.blogspot.com/...ice-cream.html
nexus has a width of 720 and a density of 320. shortSizeDp = 720 * 160 / 320 = 360. lower than 600, phone mode.
now put the dpi to magic number 192. shortSizeDp = 720 * 160 / 192 = 600. tadaaa, tablet mode.
Click to expand...
Click to collapse
Edit: It's also using a modded nova launcher. Not sure, however, I don't see why the launcher wouldn't work for us.
In fact, I just spent a little more time looking through this and I think it will work close to 100% with CM9 or AOKP roms. Hmmmm, just gotta find out the right DPI. (I haven't bothered, busy at work.)
Looking at DisplayMetrics:http://developer.android.com/reference/android/util/DisplayMetrics.html
There are a few preset densities which may interest us:
DENSITY_DEFAULT = 160
DENSITY_HIGH = 240
DENSITY_LOW = 120
DENSITY_MEDIUM = 160
Assuming that the above values holds true to the Sensation, then the following would give a 600 output:
DENSITY_DEFAULT = 160 (540 * 160 / 144 = 600)
DENSITY_HIGH = 240 (540 * 240 / 216 = 600)
DENSITY_LOW = 120 (540 * 120 / 108 = 600)
DENSITY_MEDIUM = 160 (540 * 160 / 144 = 600)
Still checking it out!
EDIT: Additional info - DENSITY_DEFAULT is directly linked to DENSITY_MEDIUM (DENSITY_DEFAULT = DENSITY_MEDIUM) so that explains why changes to DENSITY_MEDIUM affect the OS system wide (Not sure if this is the case in all ROMs).
Still checking, but bed time for me!!!.........
Seems we also need a modified services.jar
There is some info here: http://forum.xda-developers.com/showthread.php?t=1467051
Thread here for AOKP B33: http://rootzwiki.com/topic/23418-mod-tabletui-for-240-dpi-legacy-devices-aokp-b32b33/
Instructions state: Set density to 128 MAX & Tablet mode will be automatically activated However, since our Sensations have a screen width of 540, not 480 as most legacy devices, we may still need to find that "Magic Number"
Haven't tried it as i'm not running an AOKP based ROM but we need to know what to change in services.jar and then this should be able to be implimented in all ROMs!
Hope this helps
EDIT: The services.jar above uses the following formula: (480 * 160 / 128 = 600)
We should be able to do it using (540 * 160 / 144 = 600) 144 MAX - However, it wont hurt to try 128 since our device has a default density of 240?!
Also, don't forget to set your Font size to huge (or large) in ROM Control.
I have created a flashable zip for AOKP B33/34 which includes a Patched Launcher, Phone, Market & services.jar.
This should work on all AOKP ROMs!
This should also parse the build.prop and adjust your LCD Density to 128.
Also, don't forget to set your Font size to huge (or large) in ROM Control prior to flashing this.
I haven't tested this - I have created it blind so if you are going to try it then please make a nandroid backup first!!!
Should you try it, then Please leave feedback but don't get upset if it doesn't work for you - If it doesn't work then just restore your nandroid backup!
I hope this is of some use to someone
BTW: Flash using recovery!
I am developing an Android game, in which a ball (bitmap) translates( is in motion). So I have provided motion equations for the ball. I have checked my app on Samsung galaxy S2 whose actual density is roundly 252 dpi, and It works fine on that. So my question is that Does these motions of bitmaps in surfaceView, depends on actual density of phone( i.e 252 dpi for S2) or generalized density(i.e 240 dpi).
I am confused whether if I run this app on 235 dpi smartphone, So will it have the same performance of motion as it is on Galaxy S2( with 252 dpi) or it would be little slow ?
Any help will be appreciated.
This won't work if your Gear 2 is still running Tizen, sorry.
The original DPI on Biktor's Android wear for Gear2 is 280. I found that changing it a little improves everything a lot.
Here is how you do it :
1) Enable USB debugging on your watch and connect it to you PC.
2) Start ADB
3) If for whatever reason, you want to know what your current DPI is, type this : adb shell wm density
4) To change DPI, type this : adb shell wm density 200 (yeah, I suggest 200 for Gear2, but the choice is yours)
The screenshot on the left is with DPI 200, the one on the right with original 280 DPI.
Enjoy
The perfect dip is 240 .
Tried and no blurry icon , max graphics interface
Gabri™ said:
The perfect dip is 240 .
Tried and no blurry icon , max graphics interface
Click to expand...
Click to collapse
Thanks, I will try it
Works great on Ticwatch e as well. Thanks!
guys I'm trying to reach the best DPI setting so i would like to know what you guys are using. thanks
403
360 with Small font size.
380. Best for me.
410
Rajeev said:
380. Best for me.
Click to expand...
Click to collapse
+1 bro,even i use at 380
423 suits me...
432 is best for me
What are the settings Small, Default, Large in "Display Size" equivalent to in actual DPI?
I run in the 'Small' display size setting with default font size.
t-bon3 said:
What are the settings Small, Default, Large in "Display Size" equivalent to in actual DPI?
I run in the 'Small' display size setting with default font size.
Click to expand...
Click to collapse
Me too.
I saw somewhere in seething a dpi seething, but never touched, i only set up "small" in display size.
QUESTION:
use smaller screen size and/or dpi will consume more battery while screen active?
guys I've found my perfect DPI settings 401, try out!
How can I change the dpi ?
pardalos said:
How can I change the dpi ?
Click to expand...
Click to collapse
Settings/system/developer options then find "smalest width"
t-bon3 said:
What are the settings Small, Default, Large in "Display Size" equivalent to in actual DPI?
I run in the 'Small' display size setting with default font size.
Click to expand...
Click to collapse
Answering my own question:
Small: 423 dpi
Default: 360 dpi
Large: 320 dpi
A 5.5" 1080p screen pixels are actually 401 dpi so would the 'correct' settings for the 100% Android stock experience be 401 dpi with default font size?
401, who is the "natural" dpi for a 5.5 inch display full hd, seems much cleaner and defined compared to the 423 default minimum dpi.
I may sound crazy but I use 500 dpi. Initially I had set to smallest which I later turned it up to 500 after finding it could be changed in the developer options. I have a lot of real estate on my phone now. It kinda feels I'm using my computer on my phone and since I do a lot of coding everyday, it feels natural. Give it a shot. It may feel weird, but give it a shot.
I set mine to 420, which translates to 411 when I checked back in the Display settings
wulfe13 said:
I set mine to 420, which translates to 411 when I checked back in the Display settings
Click to expand...
Click to collapse
yes is true, why this difference beetwheen the dpi from develop option "minimum dpi" and the "display setting"?
riccetto80 said:
use smaller screen size and/or dpi will consume more battery while screen active?
Click to expand...
Click to collapse
I set my dpi to 480 and battery life did not changed at all, i still have 8/9 hour sot
Paweuek said:
I set my dpi to 480 and battery life did not changed at all, i still have 8/9 hour sot
Click to expand...
Click to collapse
how to get sot 8/9 hour , i use only ludo king , sometime browsing get 6 h.
I've looked all over the web but I can't seem to find a way to change the screen size of Android TV without magisk, my screen is too stretched and I already tried my normal TV settings, no luck. Is there any other way for me to do so?
dopinder running Lineageos 20
Endex said:
I've looked all over the web but I can't seem to find a way to change the screen size of Android TV without magisk, my screen is too stretched and I already tried my normal TV settings, no luck. Is there any other way for me to do so?
dopinder running Lineageos 20
Click to expand...
Click to collapse
Resolution changing
connect your phone with pc and start adb prompt in CMD
type:
adb shell
then you can do is :
to change the resolution:
=========================
type:
wm size *your preferred resolution from the list
like:
wm size 720x1560
*here put small letter 'x' in between the resolution
to change the dpi:
==================
type:
wm density *your preffred dpi from the list
like:
wm density 269
*REBOOT phone
example:
==========
wm size 1080x2340
wm density 420
*RBOOT phone
list:
=======
Defaultu Resolution: 1080x2340 at 420 dpi
step down 1: 960x2080 (*add your desired dpi)
step down 2: 864x1872 (*add your desired dpi)
step down 3: 768x1664 (*add your desired dpi)
step down 4: 720x1560 at 269 dpi