DPI Change Flashable ZIPS - Samsung Galaxy Star
DPI is density per pixels
so by editing it u can change the layout, text etc.
by lowering the value u can put more content in same scrn
scrnshots will help u understand if u dont get it
If u have used the aclex rom
u may hv noticed the resolution change
since some users requested it here it iis
Instruction:- Flash thru CWM
Dpi- 110 - will make things look normal smaller on screen
Dpi- 120 - the default configuration (Stock) - (can also be called recovery.zip)
If u want any other dpis request it here and ill upload it as quickly as i can
Downloads:
View attachment 2724775
View attachment 2724776
NOTICE:
The build prop used here is from my rom - T3ROM
and since i hv used a different ringtone in my rom
u will have silent ringtone after flashing this :crying:
pls change the ringtone after flashing
also the rom version will be shown as 4.1.2 as in the stock (If u have rom name it will be gone)
any1 using this will also have some tweaks tht improve responsiveness and performance :highfive:
also if u can upload stock build.prop file from stock rom
it is present in /system/
Scrnshot will be posted in a minute
Working!!
It works in my SGS thanks.
T3snake said:
DPI is density per pixels
so by editing it u can change the layout, text etc.
by lowering the value u can put more content in same scrn
scrnshots will help u understand if u dont get it
If u have used the aclex rom
u may hv noticed the resolution change
since some users requested it here it iis
Instruction:- Flash thru CWM
Dpi- 110 - will make things look normal smaller on screen
Dpi- 120 - the default configuration (Stock) - (can also be called recovery.zip)
If u want any other dpis request it here and ill upload it as quickly as i can
Downloads:
View attachment 2724775
View attachment 2724776
Click to expand...
Click to collapse
uhmm.. actually o.o
DPI is dots per inch.. used in some printers to define print quality.. techinally for screens you'd say ppi or pixels per inch.. but eh.. everyone calls it dpi so let's just say dpi..
dpi is constant for mobile devices screen... there maybe some mobile devices which allow changing dpi but i don't know about that..
dpi is the number of physical pixels on a unit inch of a screen.. calculated by the below formula..
dpi=sqrt((x^2)+(y^2))/d (x an y are no. of pixels and d is the size of screen diagonally in inch )
no. of horizontal pixels(x) of star = 240
no. of vertical pixels of star = 320
stars screen size diagonally (d) = 3.0 inches
dpi=sqrt((x^2)+(y^2))/d
dpi=sqrt((240^2)+(320^2))/3
dpi = 133.333
dpi of star is approximately 133.. and that won't change unless you change the ro.board.lcd.. just joking.. :cyclops:
for dpi.. the higher the better.. higher dpi means more pixels per inch.. which gives more sharper and clearer picture..
how awfully awesome it would be it we could change dpi to 734 for our star.. that's full HD on a 3 inch display lol
what we indirectly, change with ro.sf.lcd_density is the scaling factor, by which the ui is scaled .. ( read on about android's density independent pixels and scaling )
this may give a impression like the resolution is changed.. but unlike in monitors where actual physical resolution is changed.. this is just a hack to scale the ui
psych.half said:
uhmm.. actually o.o
DPI is dots per inch.. used in some printers to define print quality.. techinally for screens you'd say ppi or pixels per inch.. but eh.. everyone calls it dpi so let's just say dpi..
dpi is constant for mobile devices screen... there maybe some mobile devices which allow changing dpi but i don't know about that..
dpi is the number of physical pixels on a unit inch of a screen.. calculated by the below formula..
dpi=sqrt((x^2)+(y^2))/d (x an y are no. of pixels and d is the size of screen diagonally in inch )
no. of horizontal pixels(x) of star = 240
no. of vertical pixels of star = 320
stars screen size diagonally (d) = 3.0 inches
dpi=sqrt((x^2)+(y^2))/d
dpi=sqrt((240^2)+(320^2))/3
dpi = 133.333
dpi of star is approximately 133.. and that won't change unless you change the ro.board.lcd.. just joking.. :cyclops:
for dpi.. the higher the better.. higher dpi means more pixels per inch.. which gives more sharper and clearer picture..
how awfully awesome it would be it we could change dpi to 734 for our star.. that's full HD on a 3 inch display lol
what we indirectly, change with ro.sf.lcd_density is the scaling factor, by which the ui is scaled .. ( read on about android's density independent pixels and scaling )
this may give a impression like the resolution is changed.. but unlike in monitors where actual physical resolution is changed.. this is just a hack to scale the ui
Click to expand...
Click to collapse
yes of course we cant change the dpi of the screen we cant change hardware...
everyone calls it dpi i call it dpi
emulation is enough
i made it for some users that didnt wanna edit build.prop
yes 768 dpi u were talking about
the density which we can change shud be 240 which is the one used in some tabs and the most higher res devicrs like s3
it was pathetic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
statusbar looked gud
Sent from my GT-S5282 using Tapatalk
T3snake said:
yes of course we cant change the dpi of the screen we cant change hardware...
everyone calls it dpi i call it dpi
emulation is enough
i made it for some users that didnt wanna edit build.prop
yes 768 dpi u were talking about
the density which we can change shud be 240 which is the one used in some tabs and the most higher res devicrs like s3
it was pathetic
statusbar looked gud
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
you said "DPI is density per pixels" in OP and that's wrong... that's all it was about..
by changing the ro.sf.lcd_density to 240 everthing will be bigger.. cause it changes the scaling to 2x.. which will make everything (the ui) look twice as big..
psych.half said:
you said "DPI is density per pixels" in OP and that's wrong... that's all it was about..
by changing the ro.sf.lcd_density to 240 everthing will be bigger.. cause it changes the scaling to 2x.. which will make everything (the ui) look twice as big..
Click to expand...
Click to collapse
i dunno i really knew it was dots per inch as i told some users that asked me
i dunno why i wrote density
maybe because it was density
well changing density in some apps helps a lot
Sent from my GT-S5282 using Tapatalk
T3snake said:
DPI is density per pixels
so by editing it u can change the layout, text etc.
by lowering the value u can put more content in same scrn
scrnshots will help u understand if u dont get it
If u have used the aclex rom
u may hv noticed the resolution change
since some users requested it here it iis
Instruction:- Flash thru CWM
Dpi- 110 - will make things look normal smaller on screen
Dpi- 120 - the default configuration (Stock) - (can also be called recovery.zip)
If u want any other dpis request it here and ill upload it as quickly as i can
Downloads:
View attachment 2724775
View attachment 2724776
Click to expand...
Click to collapse
Wrks well except for dialer... anyways thank u...
Vortex99 said:
Wrks well except for dialer... anyways thank u...
Click to expand...
Click to collapse
Well this was mainly for u since u requested it
use exdialer it is quite fast and doesnt give problem
also u can use app settings to set dpi per app
T3snake said:
Well this was mainly for u since u requested it
use exdialer it is quite fast and doesnt give problem
also u can use app settings to set dpi per app
Click to expand...
Click to collapse
App settings works for dialer...??
Vortex99 said:
App settings works for dialer...??
Click to expand...
Click to collapse
Yes everything
Related
[rom][8/1] paranoidandroid 3.91 | 4.3
kernel source FEATURES for 3.0+, Hybrid engine, Per app Layout, this will let you choose the UI of any app, that means you can switch apps into their tablet layouts Per app Size, scale apps individually, this is especially important if you use tablet apps, go as small or big as you like Per app Color, this lets you select statusbar and navbar colors for apps individually, colors will shift when you jump from one app to another Hybrid engine makes it possible to use any tablet ready app available on your phone, start with your regular Google apps and see what treasures lie hidden in them and just how well they work on your device. You can use hybrid engine to use all available general interface UI's aswell: Phone, Phablet, Tablet. This is safe as milk, we don't change DPI, we don't trash your market, we don't shrink all your apps or force them into layouts, you don't need to edit system files for that. Transparent bars and color pickers, new SystemUI drawables thanks to giannisgx89 Theming Engine Statusbar Settings, Lockscreen Settings Multiuser support Quicksettings -> Quicktoggles 4.2 Walls and sounds, Google stock apps As we merge back our old CMPA feature catalogue this list will grow considerably over the coming weeks New holo-styled theme chooser T9 dialer New papreferences app DONATIONS, to molesarecoming to D4rKn3sSyS to jaybob413 to aaronpoweruser
{ "lightbox_close": "Close", "lightbox_next": "Next", "lightbox_previous": "Previous", "lightbox_error": "The requested content cannot be loaded. Please try again later.", "lightbox_start_slideshow": "Start slideshow", "lightbox_stop_slideshow": "Stop slideshow", "lightbox_full_screen": "Full screen", "lightbox_thumbnails": "Thumbnails", "lightbox_download": "Download", "lightbox_share": "Share", "lightbox_zoom": "Zoom", "lightbox_new_window": "New window", "lightbox_toggle_sidebar": "Toggle sidebar" } BE WARNED, 4.2.0 is not the most bugless android, the issues are known. INSTRUCTIONS, 1. UPDATE RECOVERY 2. FACTORY RESET 3. INSTALL ROM, GAPPS, FIX-IF ANY 4. WIPE CACHE & DALVIK CACHE 5. REBOOT PA 2.99+ UPDATES DO NOT NEED A FACTORY RESET, BUT YOU NEED TO INSTALL GAPPS ASWELL. Changelogs are on the paranoid andorid google+ page Know bugs: graphical glitch when using pie CREDITS, AOSP/Google, Cyanogenmod, Goo, XDA, Krebsmilk, giannisgx89, AOKP, our users, supporters and donators, everyone who's helped us in the past, heartfelt thanks to all of you! LINKS, Github: www.github.com/paranoidandroid Gerrit: review.paranoid-rom.com BANNERS,
PARANOIDANDROID 2.16 | Only Rom on Android capable of Hybrid mode | Click and see Just in case...
Just in case...
Can't wait. Loved paranoid on my skyrocket Sent from my Nexus 7 using XDA Premium HD app
I already have a booting PA port for the nexus 7. If you want it I can upload it for you. Sent from my Nexus 7 using XDA Premium HD app
That's at DPI 213 at work right now so can't really play with it atm Screen size 1280x800 Sent from my Nexus 7 using XDA Premium HD app
Ro.sf.lcd_density=213 Can't wait, thanks! Sent from my Nexus 7 using Tapatalk 2
ahhhhhhhhhhhhhh, Can't wait!
Sweet! Love the paranoid Sent from my Nexus 7 using XDA Premium HD app
the density is 213 edit: got ninja'd big time.....slow internet ftw? haha
molesarecoming said: what i need to make a running build is: 1. the value of ro.sf.density in system/build.prop 2. full screensize in pixels for width and length 3. the three treshold dpis to kick off phoneUI, phabletUI and tabletUI - PA is completely independent of this, its just for reference. you can calculate it by the formula i have given in the porting topic or just drop lower/higher dpis to find them yourself. if you calculate it, the three magic shortest-width-devicepixels are: 360 (phone), 600 (phablet) and 720 (phablet). 4. i need the full data that this http://forum.xda-developers.com/showpost.php?p=27583329&postcount=12 app spits out in all three modes. especially the screenheight and the screenlayout, that long number. if its too complicated i'll ask around and find these values on my own but it would speed up the process considerably if any of you could do it. thx alot! Click to expand... Click to collapse 1. 213 2. How can I get this info? 3. shortSizeDP < 600 = PhoneUI 601<shortSizeDP < 719 = PhabletUI shortSizeDP > 720 Source 4. with 213 DPI I get: Height: 880 Width: 600 Layout: 268435475 Tablemode DPI Treshold: 213 < 321 With 601 DPI I get: Height: 259 Width: 212 Layout: 17 Tablemode DPI Treshold: 213 < 285 I will keep updating as I get the info. There must be something wrong because the screen size was almost useless. If anythign I think it shoudl be decreased from 213 to obtain table mode or something like that.
molesarecoming said: this goes out to all of you who would like help, i can not imagine anything more proper than androids one and only true hybrid rom running on this device, especially since google somehow saw the need to declare it one big phone. as always, build.prop hacks suck and degrade the device so i'd really like to have it here. problem is, i live in germany and it'll take some while until i can get my paws on it. but i thought --- i have made ports for nexus toro & toroplus and its an official aosp device, so why not just going ahead and making a build. but there's still something i need your help for and would be very obliged if you could lend me a hand, PA needs a couple of magic values to work and these must be extracted or calculated. if you would like to help out we could get a running build pretty quickly and this topic would evolve into the official PA/nexus7 build. first, this is what the rom will bring to the table: http://forum.xda-developers.com/showthread.php?t=1717079 i guess you can easily see the benefits here, this is different than dropping your entire device into a fixed dpi and its different than hacking android.policy into displaying the dropup-notification box. it brings total freedom, scale any app/widget or systemcomponent you like, display any app/widget/syscomponent in whatever UI mode you prefer (phone, phable, tablet). this works individually on per-app basis. second, for reference, heres a topic i made up for our porting friends: http://forum.xda-developers.com/showthread.php?t=1619582 what i need to make a running build is: 1. the value of ro.sf.density in system/build.prop 2. full screensize in pixels for width and length 3. the three treshold dpis to kick off phoneUI, phabletUI and tabletUI - PA is completely independent of this, its just for reference. you can calculate it by the formula i have given in the porting topic or just drop lower/higher dpis to find them yourself. if you calculate it, the three magic shortest-width-devicepixels are: 360 (phone), 600 (phablet) and 720 (phablet). 4. i need the full data that this http://forum.xda-developers.com/showpost.php?p=27583329&postcount=12 app spits out in all three modes. especially the screenheight and the screenlayout, that long number. if its too complicated i'll ask around and find these values on my own but it would speed up the process considerably if any of you could do it. thx alot! Click to expand... Click to collapse As soon as my wife gets back with mines I'll get those values if anyone hasn't. On a side note.. I need to get the wife one so she can stop using mines lol
Someone send him a N7!!! Can't wait for this rom, rocking it right now on my SGS2
SGT7, and My Rom, have this information already in the settings, you can use that. If switches between tablet and phablet mode with a switch in the settings, if you want the treshhold it is mentioned in the android development section in a thread using a jar file in the framework.
#2 Diagonal cm (in) - 18 (7) Resolution - 1280×800 ppcm (PPI) - 85 (216) Aspect ratio - 8:5 (4.8:3) Source
Hyperrunner said: SGT7, and My Rom, have this information already in the settings, you can use that. If switches between tablet and phablet mode with a switch in the settings, if you want the treshhold it is mentioned in the android development section in a thread using a jar file in the framework. Click to expand... Click to collapse thx for the offer! i guess the infos coming in here will do though. to explain myself, pa is independent of dpi, the system will always run in the one that google chose. the treshold dpis are only good for the gui panel, we have sliders there which you use to scale apps. if you switch an app to tabUI or phoneUI, it is separate from the dpi you chose, you can get tabUI/phone/phabUI with dpi 1 or dpi 1000000. that also applys to the phone itself, tabUI means nothing else than dropping systemUI into that UI mode and still you can scale it. in essence, with PA theres no tablet mode anymore, its hybrid. each and every app runs in whatever scale and UI mode you individually give.
thx alot guys, this gives me something to work out.
Albinoman said: I already have a booting PA port for the nexus 7. If you want it I can upload it for you. Sent from my Nexus 7 using XDA Premium HD app Click to expand... Click to collapse you can paste it here if you want, no probs. in the future though i plan this to be PA/nex7 official as i'd like to get the device for myself and build for it.
SimPup said: View attachment 1225923 That's at DPI 213 at work right now so can't really play with it atm Screen size 1280x800 Sent from my Nexus 7 using XDA Premium HD app Click to expand... Click to collapse one down, two to go, thx man! Rafase282 said: 1. 213 2. How can I get this info? 3. shortSizeDP < 600 = PhoneUI 601<shortSizeDP < 719 = PhabletUI shortSizeDP > 720 Source 4. with 213 DPI I get: Height: 880 Width: 600 Layout: 268435475 Tablemode DPI Treshold: 213 < 321 With 601 DPI I get: Height: 259 Width: 212 Layout: 17 Tablemode DPI Treshold: 213 < 285 I will keep updating as I get the info. There must be something wrong because the screen size was almost useless. If anythign I think it shoudl be decreased from 213 to obtain table mode or something like that. Click to expand... Click to collapse suppose this thing has 1280x800, then 800 is the shortest side, then according to this formula: treshold_dpi = shortest-side-dp * 160 / 600 your dpi must be 213. turns out it is, so we got phablet down, so your treshold dpi for tabUI should be: 177-178 (800 * 160 / 720) and for phone: 355-356 (800 * 160 / 360) what i need you to do is boot into these dpis and comfirm your settings is either tab or phone, then start the app i linked (in portrait-view) an post the full values. all im really looking for is the screensizes and the layout number, because as i wrote, changing dpi to get into any mode is out of style. :fingers-crossed:
[Q] Android DPI
Can someone please explain how the android DPI system works? If i reduce my dpi on my Gnex, from 320 to 250, everything gets smaller; it gets denser (as there is more in a smaller space), however the name (dots per inch) would suggest that a higher figure would result in a more dense screen.
maxib123 said: Can someone please explain how the android DPI system works? If i reduce my dpi on my Gnex, from 320 to 250, everything gets smaller; it gets denser (as there is more in a smaller space), however the name (dots per inch) would suggest that a higher figure would result in a more dense screen. Click to expand... Click to collapse http://developer.android.com/guide/practices/screens_support.html There is plenty to read... but you might just take a look at figure 4. which explains sizes of xhdpi, hdpi, mdpi and ldpi drawables. It's basicly hidger dpi = higher res drawable = takes more space on your screen.
Change Dpi
Hello Can i change dpi stock 240. Someone have tested?
kvadde said: Hello Can i change dpi stock 240. Someone have tested? Click to expand... Click to collapse A solid-state screen's DPI is a physical attribute, you cannot change it.
I believe OP is referring to the soft DPI settings in build.prop. You must root, then edit the ro.sf.lcd_density setting in build.prop. It's already 240 on CM, not sure about stock though.
Cat McGowan said: A solid-state screen's DPI is a physical attribute, you cannot change it. Click to expand... Click to collapse You are talking about PPI, not DPI
Stock DPI is also 240. But why would you want to change that?? If some app is not displaying to your satisfaction, it's better not to modify build.prop, because it could lead to unexpected weird behaviors. Better is to use the "Xposed Framework" with the module "App Settings"; there you can specify individual DPI settings for each app. The safer and more flexible solution! I use it without problems on all my devices.
Felimenta97 said: You are talking about PPI, not DPI Click to expand... Click to collapse You have it backwards.
kvadde said: Hello Can i change dpi stock 240. Someone have tested? Click to expand... Click to collapse As you didn't specify whether you want this on stock firmware or an AOSP ROM, I'd suggest to try the PACman port to the XTZ, as it includes per-app DPI modifier. It's currently in nightlies and no fully stable release as of yet, but it's worth to try if you really need that feature.
DPI = Dots Per Inch PPI = Pixels Per Inch The reason we've started to use PPI instead of DPI is because of PenTile, since that technology yields more pixels than dots per inch (dots are shared between adjacent pixels). Both are properties of the hardware but by telling Android you have a different DPI you can scale the UI. This procedure will make graphical elements that makes use of their physical size on the display (rulers, printing tools, etc.) show up at incorrect sizes. For example, if you have a virtual measurement tape, you'll need to multiply all values with the original DPI divided by the new DPI. So if you choose to change your tablets DPI to 120, making every UI element scale to half of the original size, you'd need to multiply every value by 240/120=2 for it to match up with the real world. I hope this clears things up.
Shanliang- said: As you didn't specify whether you want this on stock firmware or an AOSP ROM, I'd suggest to try the PACman port to the XTZ, as it includes per-app DPI modifier. It's currently in nightlies and no fully stable release as of yet, but it's worth to try if you really need that feature. Click to expand... Click to collapse As I already said: No need to change firmware. Just install Xposed framework with App Settings module on rooted device, and you can freely modify DPI per app.
[Q] How To Resize Framework Of 320 x 480 Rom To 240 x 320 ?
Hey I Have Ported A Rom to My Device Having Rosolution of 240 x 320 But Now ported rom's app drawer not fitting to screen and lock screen not at center . i there is any way to fix it ?
try increasing or decreasing the DPI just add ro.sf.lcd_density= (watever dpi you want) check you stock ppi just third party apps like cpuz or anythings reliable in your case your case you wanna reduce the size of the app drawer try decreasing the DPI value from stock so lets say if you have a dpi of 200 at stock get it down to 180 dpi or still big then 160 dpi reduce it till you think the app drawer fits your screen perfect you will have problems with the dialer just ask for help about it even i could not figure out how to resize the dialer
Turn your one plus 2's full hd screen to 2k hd display
STEP 1 : install resolution changer pro on any h2os rom from play store (kinmaricans i preffer). STEP 2 : First do not enable it just put height = 1440 and width = 2560 and then density to 538. STEP 3 : ENABLE IT. ENJOY
Can't it be in oxygen or any other cm based custom rom
You can't change your phone's screen resolution ahahaha that depends on the hardware. That app is just changing your DPI to change the size of UI elements. If you could change your phone screen resolution with a simple app, why would any OEM make phones with 4k screens? The OP2 was, is, and will always remain 1920x1080. You can always change the DPI to get smaller icons or whatever (I prefer 380, stock is 480). More the DPI, bigger your UI elements.
jash2909 said: STEP 1 : install resolution changer pro on any h2os rom from play store (kinmaricans i preffer). STEP 2 : First do not enable it just put height = 1440 and width = 2560 and then density to 538. STEP 3 : ENABLE IT. ENJOY Click to expand... Click to collapse That is just absolute nonsense, sorry to say that. You just make the device believe to have a 2k display, which means the GPU will have to push even more "virtual" pixels, while everything is just "downscaled". You won't get any benefits from that, in contrary you will just introduce more cluster****, by letting it run on a virtual resolution instead of it's native. There's a reason why people with 2K phones set the virtual resolution down to 1080p, so that the GPU doesn't have to work as hard.
How this differ from changing dpi, it comes to my mind that oos doesn't like changing dp Sent from my ONE A2005 using Tapatalk
OP, you may want to alter your thread title in the advanced edit menu to something more accurate. You will see what I mean if you read the comments here. And members, it's fine to try to educate someone or correct them, but do it respectfully. Or don't post otherwise. Thanks, Darth Forum Moderator