So, I've tried a lot of app which allow me to decrease my DPI but no luck, always bootloop so today I've simplest way to resize your dpi without bootloop
HOWTO
Download Root Explorer or that thingy which can mount system to R/W
Open app and mount /system as R/w
go to system/build.prop and edit it
find the line which says "ro.sf.lcd_density=240
edit the 240 to anything youwant (smaller in number,the smaller you get)
BOOM THAT's IT!
P.S. Not Smaller Than 200!! Or your phone will get in trouble (such as too small text or that thingy )
Don't forget to press thank if i helped you
Did it actually work?
I'm not sure if it actually worked for me. I did for a trial and set it to 200. Rebooted the phone. Did not feel any difference.
How can you justify if it's correct method to do so?
And what if I reduce it to 100?
And I'm not sure if there is any process as such which can change the PPI of the screen. And yes, do change the Header as PPI and not DPI, as its always PPI for Electronic screens.
mysteryno46 said:
I'm not sure if it actually worked for me. I did for a trial and set it to 200. Rebooted the phone. Did not feel any difference.
How can you justify if it's correct method to do so?
And what if I reduce it to 100?
And I'm not sure if there is any process as such which can change the PPI of the screen. And yes, do change the Header as PPI and not DPI, as its always PPI for Electronic screens.
Click to expand...
Click to collapse
Mine worked Have you tried mount the system R/W ? and save it? and yes, It's DPI, If i use PPI, people may get confused
The difference you can see is the statusbar will get smaller
Use textdroider app from play store...never reduce the DPI less than 180 and it will become unreadable.
Sent from my GT-I9082 using Tapatalk now Free
drganbds said:
Use textdroider app from play store...never reduce the DPI less than 180 and it will become unreadable.
Sent from my GT-I9082 using Tapatalk now Free
Click to expand...
Click to collapse
+1 with the Textdroider app `
Related
I know our device is considered a mid range device and that one of the main reasons we can't port other roms is due to the lack of an hd screen. What if we were to take the screen density changer from the android apps forum and incorperate that with say the evo or galaxy rom? It would allow us to use these roms without having to resize every image. I'm just thinking out loud. I pm'd CR about it hoping he could work on it, but haven't had a response back yet. Let me know.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I'm not entirely sure its impossible. Can we figure out what rez the pixel density changer can get us to? If it can get us to an hdpi rez ill give it a shot.
Sent from my T-Mobile myTouch 3G Slide using XDA App
ignore my last post. Not thinking this is possible. The pixel density doesn't affect the device resolution from what I can tell. See attached screenshot. Things look smaller (appears to have higher res) however, screenshot is still the same stock res. I'll change some more build prop settings to see if i can get some different or better results. Fyi this is pixel density set @ 130.
EDIT: It does make angry birds lite fit better on the screen, gonna play with some other settings in the build prop and some hdpi apps and see if I can make something happen for you guys.
Good stuff. I know it won't change anything about the resolution, but it allows the device to mock a higher resolution on the screen. Just seems like we should be able to view bigger images on the screen. I'm gonna take an image with the mts's resolution and the same image but with the galaxy's resolution and see if they display full screen in their respective settings in the density changer. Should be a good test.
Edit: Just remembered, the netbooks running android only display icons 4 wide from the factory. Your screenshot reminded me of that. If those screens which are higher res than ours look the same as ours (the icons are bigger only because the screen is bigger) then in theory this should work.
Edit 2: Just for ****s and giggles I read through the comments on the market for lcd density changer. On the hdpi devices people are complaining about certain widgets not scaling well, but the mdpi devices are only having issues when scaling to funky non-standard resolutions... just wanted to post another reason why with a little hackage, this should work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I'm working on finalizing my DPI changer app. It should be possible because the Android specs states that pixels = density * ( dpi / 160 ) or something like that (I don't have the page pulled up right now). My program is 90% complete... the logistics are done, but it just has an error wsaving, but it's due to programmer error most likely.
So, for example to scale an image from HDPI to MDPI you take the X resolution and multiply it times 0.75 and let the image program lock the aspect ratio (e.g. don't specify the Y resolution). MDPI to HDPI is (obviously) multiplied by 1.25.
Hope that helps.
Sent from my T-Mobile myTouch 3G Slide using XDA App
nbetcher said:
I'm working on finalizing my DPI changer app. It should be possible because the Android specs states that pixels = density * ( dpi / 160 ) or something like that (I don't have the page pulled up right now). My program is 90% complete... the logistics are done, but it just has an error wsaving, but it's due to programmer error most likely.
So, for example to scale an image from HDPI to MDPI you take the X resolution and multiply it times 0.75 and let the image program lock the aspect ratio (e.g. don't specify the Y resolution). MDPI to HDPI is (obviously) multiplied by 1.25.
Hope that helps.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
THanks for the info
Anyone know where/how an apk determines its going to render in mdpi v hdpi? My guess is the build.prop, but It doesn't appear to gather that info from the pixel density. (rom manager won't cover the entire screen when lcd density is set to 130 so i'm thinking its sensing mdpi some other way) Any help would be appreciated
mobile_mogul said:
I know our device is considered a mid range device and that one of the main reasons we can't port other roms is due to the lack of an hd screen. What if we were to take the screen density changer from the android apps forum and incorperate that with say the evo or galaxy rom? It would allow us to use these roms without having to resize every image. I'm just thinking out loud. I pm'd CR about it hoping he could work on it, but haven't had a response back yet. Let me know.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You may want to change the thread name to something like "THINKTANK: MDPI To HDPI Port via Pixel Desnity"
That way people will have a better idea what the thread is about
Changed. Also, I wasnt able to test anything last night as it got pretty late, but I have tonight and all day off tomorrow to tinker around with things.
The problem is that HDPI devices don't have MDPI drawables, so every image in every app (and then some) have to be scaled down.
I have a program on my computer called image resizer, that let's me right click on the pic in file explorer and click resize photo, the select 320x480 and it rezises it for you.
Sent from my HTC Espresso, that is apperantly a failing device using the XDA App
Whoareyou said:
I have a program on my computer called image resizer, that let's me right click on the pic in file explorer and click resize photo, the select 320x480 and it rezises it for you.
Sent from my HTC Espresso, that is apperantly a failing device using the XDA App
Click to expand...
Click to collapse
What version you using? 2.1?
It keeps aspect ratio so sometimes it doesn't resize perfectly. ie when I try to resize boot screens it converts to 296x480 instead.
That would be the purpose of the density changer. No need to resize any images. Just load the changer and it visualizes a higher resolution on the screen....
mobile_mogul said:
That would be the purpose of the density changer. No need to resize any images. Just load the changer and it visualizes a higher resolution on the screen....
Click to expand...
Click to collapse
Wouldn't that cost alot of CPU power to dynamically resize the images?
I've never used the density changer so I wouldn't know.
Ok, after chattin with IB, he provided a little insight on how the density changer works.
I just got the touchwiz ui to load no problem on the slide by changing the density to an HDPI equivalent. It's still a little "off". But im gonna keep tweaking it.
Ok, so I've been able to get pretty much anything made for the n1 to run properly on the slide. Only thing i've had issues with are when loading the touchwiz ui, it is all pushed to the left side of the screen. If I can force tw to use 5 columns it would fill the screen and we'd have an almost full port of the tw launcher.
r0man said:
Wouldn't that cost alot of CPU power to dynamically resize the images?
I've never used the density changer so I wouldn't know.
Click to expand...
Click to collapse
Sorry to triple post, but it wouldnt use any extra cpu cycles... All the res changer does is change the value in the build.prop.
mobile_mogul said:
Sorry to triple post, but it wouldnt use any extra cpu cycles... All the res changer does is change the value in the build.prop.
Click to expand...
Click to collapse
But its still displaying an HDPI image, just scaled down?
Well I installed Density Changer from the market, but it won't do any thing, it says it works nut when I reboot my phone nothing is any different, and its still at the default res, any idea on why this is????
Sent from my HTC Espresso, that is apperantly a failing device using the XDA App
http://forum.xda-developers.com/showthread.php?t=785864
HI!!
I am new to this forum. I rooted my mini pro then installed a droid overclock. but i am unable to overclock. it has extra options in which changing lcd density is one. i changed it to stock value. after that it asked for reboot. after reboot the resolution is decreased ...i only see large icons most parts are invisible.
i tried using lcd density app and lcd density changer app...both didn work
i tried for factory reset ...but that too had no response... i also restored backup ...but no change ....please any one help..
its X10 mini pro
Android version 2.1
Thankyou!!!
Look into the /system/build.prop file.. you should find a line referring to screen LCD density
ro.sf.lcd_density=
Change the number at the end to 110
E.g. ro.sf.lcd_density=90 --> ro.sf.lcd_density=110
Save and exit, then reboot .. should fix your issue
Alternately you could search xda for ADB mask controller.. I think that has an options to edit the LCD density
Sent from my X10 mini using XDA App
Gothic-4-Schiffer said:
Look into the /system/build.prop file.. you should find a line referring to screen LCD density
ro.sf.lcd_density=
Change the number at the end to 110
E.g. ro.sf.lcd_density=90 --> ro.sf.lcd_density=110
Save and exit, then reboot .. should fix your issue
Alternately you could search xda for ADB mask controller.. I think that has an options to edit the LCD density
Sent from my X10 mini using XDA App
Click to expand...
Click to collapse
Mini and mini pro default lcd density value are 120
Sent from my X10 mini pro using XDA App
I need to post on small threads sorry. Btw just change the build.prop
Sent from my U20i using XDA App
i am new to this site and just rooted my galaxy mini.i have changed my screen density to 220 have messed up my screen.since i can't access superuser due to limited icons being displayed im stuck up with a ****ty screen as help would be much appreciated.
P.S i haven't/cant install busybox since i cant access the superuser functionality
ha17sun said:
i am new to this site and just rooted my galaxy mini.i have changed my screen density to 220 have messed up my screen.since i can't access superuser due to limited icons being displayed im stuck up with a ****ty screen as help would be much appreciated.
P.S i haven't/cant install busybox since i cant access the superuser functionality
Click to expand...
Click to collapse
You might be able to use adb to edit the build.prop but this is a totally different phone so you will have to follow your phones guides for restoring things like stock ROM
Sent from my U20i using xda premium
solution.
Hello,
a moment ago had the same problem,you do not need to reset or anything.
just follow. I know that all apps become hard to operate and in the app "build.prop" it wont even show the size. here's a solution that might help. you need to have an app which has a bigger UI . like I used -"Root explorer" since it gives more space to edit the build.prop file.
now go to app , find build.prop , edit, search for ro.sf.lcd_density , after an "=" you'll see the value associated with it. since your keyboard will be like before only, type default value and save.
note- if you are not able to open play store from device , try opening it from a pc, then install directly to phone.
hope that helps.
Sunny
Is there a way to reduce the size of fonts? I want to be able to see more on the screen especially the contacts menu. The contacts is so big and you see about 6 on the screen. Currently i am searching for small fonts to help reduce the size. But is there a way through root that allows me to reduce size?
thanks
porkchop8 said:
Is there a way to reduce the size of fonts? I want to be able to see more on the screen especially the contacts menu. The contacts is so big and you see about 6 on the screen. Currently i am searching for small fonts to help reduce the size. But is there a way through root that allows me to reduce size?
thanks
Click to expand...
Click to collapse
edit your Build.prop or get an app from the market
i had a look in the build.prop. what am i looking for? i cant find anything obvious like font size. many thanks
ro.sf.lcd_density=240
Change 240 to whatever you like. 200 is a figures i havr heard is fine.
I take 0 responsibilty if u screw ur phone up
Sent from my GT-I9100 using XDA Premium App
So I'm on eclipse .6 but I also had this problem on .5. Whenever I change my density to 220, as apposed to the stock 240, my mobile data connection cuts off and wont connect. Why is that? lol
I don't even know what you're talking about. What is this "density" you're speaking of?
Pixel density. There's an app called lcd density that changes it.
I dont use lcd density anymore because of the way it reboots the phone to set the build property it is editing and because if you reboot, you have to do it all over again. I use JRummy's android overclock to edit the build properties. It isnt free, but it is a little easier than editing ur build.prop in my opinion....
https://market.android.com/details?id=com.jrummy.droidx.overclock
DAG425 said:
I dont use lcd density anymore because of the way it reboots the phone to set the build property it is editing and because if you reboot, you have to do it all over again. I use JRummy's android overclock to edit the build properties. It isnt free, but it is a little easier than editing ur build.prop in my opinion....
https://market.android.com/details?id=com.jrummy.droidx.overclock
Click to expand...
Click to collapse
Root tools, also by jrummy, is a better solution, I think.
Sent from my DROID X2 using Tapatalk
You can also edit the line in build.prop to make any LCD density change permanent.
ro.sf.lcd_density = (input your pleasure) I have mine set at 180.
I used the text editor in root explorer ...
Keep in mind though that modded density levels may create problems with the Market, as some have reported that certain apps may appear incompatible with your phone after the change. This is definitely an issue with the new market (3.1.3), so I restored an older version (2.4.5) and froze market updater to resolve this.
Hope this helps ...
Pj
Messing with the LCD Density always causes some kind of conflict regardless of how you do it, I just end up keeping it at default.
Before we could and still can change DPI for the phone but now that xposed is not working, we can't change specific apps that need original stock DPI. I hope I can live with the original DPI settings lol
Brava27 said:
Before we could and still can change DPI for the phone but now that xposed is not working, we can't change specific apps that need original stock DPI. I hope I can live with the original DPI settings lol
Click to expand...
Click to collapse
Have you tried changing the DPI? I tried with textdroider and despite trying a few different values it didn't change. Textdroider reported the proper value but there was no change in anything.
you know you have to be rooted to change dpi, right?
if you are, do it in the build prop
wase4711 said:
you know you have to be rooted to change dpi, right?
if you are, do it in the build prop
Click to expand...
Click to collapse
Yes I know that and changing it in the build.prop is what textdroider does. I've done it with app and manually and it doesn't change anything.
so, when you save the new build.prop, and you open it again, it shows that your density settings are saved?
And, then after rebooting, the old density is back in the build prop?
I wont get my phone until later today, so I cant try it now, but that's strange..
wase4711 said:
so, when you save the new build.prop, and you open it again, it shows that your density settings are saved?
And, then after rebooting, the old density is back in the build prop?
I wont get my phone until later today, so I cant try it now, but that's strange..
Click to expand...
Click to collapse
Yes the new value shows after manual (and after textdroider) edit and save/reboot but the screen DPI doesn't actually change. The value is shown, but the screen is the same.
There are actually a few different values, the one that is 400 is the one I'd been changing. I wasn't sure what the two 640 values were and haven't changed them. Never seen a build.prop with multiple values. Didn't know if maybe those two values corresponded to the left and right edge screens since there are settings for them.
Have you found out any more info about this setting?
Has anyone tried running this via adb shell:
wm density 380 (or whatever density you want)
This worked fine without root on my Xperia phone. Just curious as I am thinking about getting this phone, but not setting density is a potential dealbreaker.
Alright so an update, it's the first 640 value that changes the DPI. The one under #system.prop for universal7420. I changed it to 580 and the attached pic is the result. I loaded google now launcher to test the scaling and it appropriately scales itself to use the whole screen whereas TW moved itself to the top left of the display. I guess the next challenge is to make TW properly scale.
I noticed that last night. I wonder what the other 2 dpi settings control?
adb works
I have successfully changed the DPI using adb on normal S6, though Play Store now believe it to be a tablet. Also, most of touchwiz hates it, not a big deal for most things, camera may be the biggest annoyance when its only taking up the upper right 60% of the screen.
Has anyone sucessfully changed the per app DPI, like you can with Paranoidandroid?
Look for "buil prop editor" on play store!! But the kamera and keybord looks like a#$
Dears, you can easily swap de dpi with a simple app : Resolution changer.
Kind regards,
wikidavid said:
Dears, you can easily swap de dpi with a simple app : Resolution changer.
Kind regards,
Click to expand...
Click to collapse
What are you doing? trying to pad your post count? Exact same reply in three different threads about DPI, as well as your other post in the same threads asking "dears to please not use the double post..." WTF?
schollianmj said:
What are you doing? trying to pad your post count? Exact same reply in three different threads about DPI, as well as your other post in the same threads asking "dears to please not use the double post..." WTF?
Click to expand...
Click to collapse
I'm just trying these things :
1) delete double post/overflow on the forum
2) give a solution anyway.
Don't be upset, there's no reason to... Have a nice day !
boosting1bar said:
Have you tried changing the DPI? I tried with textdroider and despite trying a few different values it didn't change. Textdroider reported the proper value but there was no change in anything.
Click to expand...
Click to collapse
I also tried the same thing with no results
Hi,
I changed my DPI successfully by changing the first occurrence of ro.sf.lcd_density from 640 to 540 in /system/build.prop using the built-in texteditor in root explorer (and rebooting afterwards ofcourse).
Then I noticed the camera didn't work properly anymore, so I created a fix for that (see this post).
Hope you'll get it to work, it seems the same to me as on earlier devices with as exception that the ro.sf.lcd_density occurs multiple times in the build.prop file.
Cheers,
Bane.
For testing different resolutions:
- have a functional adb
- enable USB debugging on device (developer options)
- connect device to your PC via USB cable. Then start a cmd in folder containing adb.exe. Type "adb devices" (without quotes) in the command prompt to check if adb recognizes the phone
- If is OK, type "adb shell wm density ZZZ" (no quotes) where "ZZZ" is the pixel density value you want to try (default is 640)
- no reboot needed, the change is on-the-fly
- check the programs (Samsung ones - dialler, calendar, camera, launcher, etc...)
- the change will disappear when you reboot your device.
per-app DPI...not; only with Xposed, when will be available.
Once you find the desired resolution it can be inserted in build.prop