Database Develop

How to make icons larger on app page?

I would really like the application icons to be larger on the app page. I know I need glasses but they are kinda small. Is there a way to do this?

I would like to increase the size of my icons as well but not via changing screen density which if I reading what it does correctly is lowers screen resolution which make the icon appear to be larger. I want to maintain screen density but have larger icon.

change the lcd density. there's an app on the development forum that lets you change it to 200 or 250. i chose 200, everything looks good.

[Q] DPI in cyanogen 7

I hope someone knows the answer to this...
The DPI of the nook color is rated for 169dpi, yet the build.prop has it set to 161.
Changing it to the hardware correct value even solves some little graphics bugs. Like the "line on notification bar"
So why does it not match HW
Sent from my NookColor using Tapatalk

As explained by dal:
dalingrin said:
Note that lcd_density is an integer value only. Additionally, when using mdpi, 160 is the default lcd density. Any other lcd density with mdpi involves interpolation. If you compare 160 and 169.x you can see that the images used for icons are significantly more blurry at 169.
The reason I chose 161 instead of 160 was to workaround a Market bug that caused the my apps list to fail to load. In my limited testing it seems Market 2.3.4 may have fixed the issue. If so, I plan to switch back to 160 which has the best image quality and best app compatiblity with the exception of Google Maps. However, 160 will need more testing with the latest Market to make sure the "my apps" list is completely fixed.
Click to expand...
Click to collapse
dalingrin said:
The problem with densities greater than 160 is the interpolation that must happen. I just checked for good measure and the icons are definitely not as sharp. Additionally, you will see artifacts from the interpolation such as gradients on the Gingerbread keyboard and the notification drop down.
In my testing I saw no difference in font rendering.
Keep in mind that another motivation for moving to 160 is that afaik, all apps scale properly to full screen. Any deviation from the mdpi standard 160 causes some apps not to scale to full screen. An example is Google Reader. If you click on an article to read, it will give you a libwebcoreview but it does not scale to full screen at >160.
Click to expand...
Click to collapse

fmkaiba said:
I hope someone knows the answer to this...
The DPI of the nook color is rated for 169dpi, yet the build.prop has it set to 161.
Changing it to the hardware correct value even solves some little graphics bugs. Like the "line on notification bar"
So why does it not match HW
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
You can use 169. Despite what people think, 160 is the best value to use for the Nook. Anything other than 160 means extrapolation or interpolation must take place. This is why nearly every HDPI phone uses 240, not 231 or 248, despite their real world DPI. However, there is a bug in the Android Market @ 160 on tablet size screens. For now I have it set to 161 to get around that bug. I don't use 169 because icons and such are more blurry due to the extra extrapolation needed. Until Google fixes the market there isn't a good DPI for us to use. Each has its own problems, 161 has a line in the notification bar but sharp icons, 169 doesn't have a line in the notification bar but has blurry icons....etc

Dalingrin, are you aware of any ill effects from running lower DPIs, such as 140?
That's where I've had mine for months, and I love it. Then again, I'm also running at 1920x1080 on my 15" laptop.

I love this forum!
Thankyou for a clear and logical answer I couldn't get anywhere else!
Sent from my DROIDX using Tapatalk

Sorry for necrothreading, just wanted to point out that Market 2.3.6 (from gapps 0613) still has a problem with My Apps @160dpi. :/
Rodney

[Q] Lowering DPI?

What are you doing exactly when you lower it, and what do you get from it?
I saw a few threads about it but they're all procedures and instructions.

It just makes things on the screen smaller. You can therefore fit more stuff on the screen, if you are using a launcher that allows adjustable row/column settings.
Beware however that TouchWiz looks pretty nasty on non stock settings. Also the dialler and other bits and pieces won't display correctly. You can however adjust it back again.

It is most useful to me where it can display much more in the same screen area. Some apps are not multidpi friendly and do not show correctly, eg the dailer and some games.

nobnut said:
It just makes things on the screen smaller. You can therefore fit more stuff on the screen, if you are using a launcher that allows adjustable row/column settings.
Beware however that TouchWiz looks pretty nasty on non stock settings. Also the dialler and other bits and pieces won't display correctly. You can however adjust it back again.
Click to expand...
Click to collapse
When you say "it just makes things on the screen smaller," is it the icons or other stuff onscreen getting smaller or the screen getting bigger? I'm using GoLauncher EX and I was wondering about that setting on custom rows/columns that goes up to 10. I was wondering how would that fit.
dchsub said:
It is most useful to me where it can display much more in the same screen area. Some apps are not multidpi friendly and do not show correctly, eg the dailer and some games.
Click to expand...
Click to collapse
So also I guess that's why a lot of the "lower DPI"-related threads are about looking for compatible apps. Thanks!
Do many people tweak their DPI? Can you share examples of significant advantages of doing so that's worth the hassle of looking for apps/themes that would work on the adjusted DPI? Thanks again!

nobnut said:
It just makes things on the screen smaller. You can therefore fit more stuff on the screen, if you are using a launcher that allows adjustable row/column settings.
Beware however that TouchWiz looks pretty nasty on non stock settings. Also the dialler and other bits and pieces won't display correctly. You can however adjust it back again.
Click to expand...
Click to collapse
You're everywhere, nobnut! (Sorry for the off-topic)
Anyway, I hope soon everything will be smooth when changing dpi (maybe CM port or ICS). It's really useful for us with good sighting, I've been using my HD2 at 160 dpi instead of 240 and it's not only neater on the homescreen but very useful in some apps (and a less toyish aspect )

I suddenly want to switch to 240 DPI but the effort scares me.
Found this: http://forum.xda-developers.com/showthread.php?t=1369162&page=2
I don't like how it doesn't work for some apps as of now, though I never heard of Samsung ever accommodating DPI changes? That's why I didn't learn of this from somewhere else before the forums. :O

rerp said:
I suddenly want to switch to 240 DPI but the effort scares me.
Found this: http://forum.xda-developers.com/showthread.php?t=1369162&page=2
I don't like how it doesn't work for some apps as of now, though I never heard of Samsung ever accommodating DPI changes? That's why I didn't learn of this from somewhere else before the forums. :O
Click to expand...
Click to collapse
Just try this app: https://market.android.com/details?...wxLDIxMiwiY29tLmlubm9kcm9pZC5kcGljaGFuZ2VyIl0.
It's easy as hell, you can try and then undo effortlessly. But I'm sticking to 320 until... until I try again 240

rerp said:
When you say "it just makes things on the screen smaller," is it the icons or other stuff onscreen getting smaller or the screen getting bigger? I'm using GoLauncher EX and I was wondering about that setting on custom rows/columns that goes up to 10. I was wondering how would that fit.
Click to expand...
Click to collapse
Everything is smaller. Everything.
Yes, Go Launcher looks good at a lower dpi once you have set the rows and columns. Shortcuts, texts, widgets etc will all display as smaller.
For example O at 320 might look like o at 240.
To edit, there are apps to use (if you are noob ). The best way is to open the build.prop file in the 'system' folder, find the line ro.sf.lcd_density=320 and change the 320 to your value... then reboot.
Just remember the default value is 320 if you want to return again.

AzureD said:
Just try this app: https://market.android.com/details?...wxLDIxMiwiY29tLmlubm9kcm9pZC5kcGljaGFuZ2VyIl0.
It's easy as hell, you can try and then undo effortlessly. But I'm sticking to 320 until... until I try again 240
Click to expand...
Click to collapse
nobnut said:
Everything is smaller. Everything.
Yes, Go Launcher looks good at a lower dpi once you have set the rows and columns. Shortcuts, texts, widgets etc will all display as smaller.
For example O at 320 might look like o at 240.
To edit, there are apps to use (if you are noob ). The best way is to open the build.prop file in the 'system' folder, find the line ro.sf.lcd_density=320 and change the 320 to your value... then reboot.
Just remember the default value is 320 if you want to return again.
Click to expand...
Click to collapse
Thanks for the link but I don't think that changing the DPI itself is any difficult. It's cleaning up the possible mess after, with changing the incompatible apps. I've heard some of them won't work right on different DPIs. Is there a thread for that around here?
Also, I read one about S-Memo not working nicely, and I use that app a LOT, so I guess I'll be monitoring what they do in that thread too.
I do like how it looks like though. Makes me feel the phone is even bigger.

At 240 (default DPI for 800x480) "all" (can't tell for sure) apps will work. Everything also looks good since, again, it's the default Android DPI and some UI elements will look like crap if you set it to 260 or so. Try out the app and see if you like it. If not just reboot the phone and it'll be back to normal.
Sent from my iPad GT-N7000 using xda premium

Wait... Need some clarification about this... I've gotten some games in the market before and I uninstalled them because they didn't go full screen. They left like a fourth of the screen unoccupied and simply black. If I switched to 240, you think they would take the full screen?
Sent from my GT-N7000 using XDA App

no. for example, live holdem pro looks the same crap on 320 and 240 too
Sent from my GT-N7000 using XDA App

That's not nice. Are there any workarounds for such apps? I thought DPI would be a solution.

[Q] Ice Cream Sandwich, Swype and Screen Resolution

I'm running Ice Cream Sandwich on my Galaxy Tab, and I'm having issues installing Swype because of the screen resolution.
According to Wikipedia, my resolution should be 1024x600 (which is supported by Swype).
Screeninfo told me that my resolution was actually 600x976. I used this app to change my LCD density (from 160 to 140), now Screeninfo reports my resolution as being 600x982 in Portrait mode, and 1024x558 in Landscape.
There seems to be a 42px offset in my resolution (it should be 1024x600). I'm guessing this is because of ICS' new "notification" bar. Could this be why I can't get Swype installed?
Is there a may to get apps to detect my resolution without subtracting 42px for the "notification" bar?

you have to set your tab at 240 DPI in build.prop and than you are able to install swype beta keybord

chickygamon said:
you have to set your tab at 240 DPI in build.prop and than you are able to install swype beta keybord
Click to expand...
Click to collapse
If 160 DPI was 600x976 and 140 DPI was 600x1024 what resolution would 240 DPI be? That would be really small (making everything on the screen huge!). Swype said it should work at 1024x600.

I set 240, installed swype and than come back to 160

chickygamon said:
I set 240, installed swype and than come back to 160
Click to expand...
Click to collapse
Would that work? Before Swype announced the ICS version, I tried using Titanium Backup to restore the keyboard, and it kept giving me resolution errors when I opened the keyboard.

I have done it yesterday with slimdizzy CM9 kang and it works

chickygamon said:
I have done it yesterday with slimdizzy CM9 kang and it works
Click to expand...
Click to collapse
Hey, it worked. Also, at 240 DPI, it added the notification bar back to the top, weird. Also it seems to be at 1024x600 also. Neat. Thanks.
EDIT: It seems the resolution is always the same at all the DPI settings. Why didn't Swype like 160?

[Q] Increase DPI of Galaxy Note

I know most of you with think why would i want to increase the DPI of Galaxy note.. Lets just say a special person needs to use it and requires REALLY REALY LARGE fonts.. The largest possible hopefully.. is it possible to increase the DPI higher than 320? if so how?.. Most apps i found only limit to 320 DPI.. what is a safe DPI can i use higher than 320?.. Thanks alot..

if you need large font, just go to settings, accessibility, and change the font size from 'normal' to 'huge'. that should help with some apps. but i think what you want is lower dpi. fonts occupy a set number of pixels on screen. higher dpi makes the pixels smaller and hence font smaller, lower dpi makes the pixels larger, hence font larger.

Souai said:
if you need large font, just go to settings, accessibility, and change the font size from 'normal' to 'huge'. that should help with some apps. but i think what you want is lower dpi. fonts occupy a set number of pixels on screen. higher dpi makes the pixels smaller and hence font smaller, lower dpi makes the pixels larger, hence font larger.
Click to expand...
Click to collapse
Its already in Huge but, the its still to small for him to read.. If i decrease the DPI, The resolution of the phone increases and the fonts become smaller.. I tried it.. So far, i got the screen to go up to 400 DPI and the fonts get larger, however if i go beyond the default 320 DPI, the settings application FC.. Anyone have an advice?

xyzsor said:
Its already in Huge but, the its still to small for him to read.. If i decrease the DPI, The resolution of the phone increases and the fonts become smaller.. I tried it.. So far, i got the screen to go up to 400 DPI and the fonts get larger, however if i go beyond the default 320 DPI, the settings application FC.. Anyone have an advice?
Click to expand...
Click to collapse
Not sure if and how it'll work for you, but there's a "Font changer" app on the market, which can resplace default Droids Sans font on rooted device with any .ttf font of your choosing.
What you could try - if DPI attempts fail - is finding some readable font which will be bigger on the screen. What I mean is that when I tried replacing default device font with e.g. Segoe UI or Tahoma or Calibri (copied from my Windows), some of those fonts were visibly smaller or bigger than Droid Sans - maybe there is sth that's much much bigger than the rest - Arial Black or Impact perhaps?
also - CyanogenMod builds for other devices had small app called Spare Parts, which enabled changing the deafualt font size for all apps. There is similar Spare Parts app on the market, did not try it, but maybe it also has the same ability

xyzsor said:
Its already in Huge but, the its still to small for him to read.. If i decrease the DPI, The resolution of the phone increases and the fonts become smaller.. I tried it.. So far, i got the screen to go up to 400 DPI and the fonts get larger, however if i go beyond the default 320 DPI, the settings application FC.. Anyone have an advice?
Click to expand...
Click to collapse
The higher the DPI the smaller the fonts will get. Best try to get some large fonts installed. If you are able to change DPI then it means you are rooted so try Absolute System Root Tools or Jrummy Root Toolbox and both have a lot of fonts ranging from small to large and they change the fonts of every text on the phone !!!

I also thought higher DPI, smaller font size. But indeed, higher DPI, bigger font size (like in PC Display)

on ICS, Changing DPI causes bootloop
Has anyone noticed that making these changes on ICS causes the phone to fail to boot? Quite annoying, as I'd like to make better use of the screen estate.

Actually if you use romtoolbox it wont fail at boot. At least with fpi bigger then 219
Sent from my GT-N7000 using Tapatalk 2