Is there an option to scale the display, so everything will look bigger (for people who have difficulties reading the small fonts that is everywhere).
I'm not looking for a local solution as changing the browser font size, but something like the same effect as when you lower the screen resolution on your PC.
Thanks.
There are a few tools that let you change the DPI, for example: https://market.android.com/details?id=com.innodroid.dpichanger
You need root to use it.
thanks,
the app you mentioned crushed, but this one does work. if I increase the DPI too much then it switches to another launcher and the soft buttons are tiny or gone.
original DPI=160
max DPI working well with the original launcher=177
min DPI = 120 (also works well)
so I only succeded to increase the DPI by 10% and still keep the system work well, not very effective.
https://market.android.com/details?...wsMSwyLDEsImNvbS5iaXJkYXBpLmFuZHJvaWQuZHBpIl0.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I use 120 dpi with Go Launcher to fix the view of the home screen. Works very well in expanding the usage of most apps. Though some sharpness is loss in the text...even though it was never that sharp to begin with in 160 dpi.
Related
Modifying the LCD density of your screen will provide HUGE REACTIVITY GAIN to the tablet
We can also tweak Dalvik heapsize for large application
Both are editable using software but they're also properties on the build.prop :
- dalvik.vm.heapsize
- ro.sf.lcd_density
Does editing this properties is enough for the Folio follow or do we have to make much complex operations ?
I there, is this fix already implemented or has to be done manually?!?
I've implemented them using FolioWidget rewriting build.prop.
Not sure the folio take care of it.
But it seems that's is not required by users so i'll wipe them
Sol Ido said:
I've implemented them using FolioWidget rewriting build.prop.
Not sure the folio take care of it.
But it seems that's is not required by users so i'll wipe them
Click to expand...
Click to collapse
I dont understand what u mean.
ps: have u read my pm?
Sol Ido said:
I've implemented them using FolioWidget rewriting build.prop.
Click to expand...
Click to collapse
density of 120 works quite fine here now.. with old market app, there was a problem with 120 but that seems resolved now with new market app..
and yes, somehow screen and browsing seems to work better? or is it just the bigger picture giving a nicer resolution of browsing?
All resolution are good. If you have a lot of items on the screen lower density is best.
But by using something like 180 you get a lot of visibility. Since i've developped a lot of complex widgets, it's my favorite one.
Using a density >120 will get you less data to manage on the screen and you can feel the gain ! i'm using multipicture and a lot of complexes widgets and there's not fillrate lag at all.
I was quite surprised with this benefits.
My purpose is that those options can really feet somes users needs. VM heap tricks like the one you found on cyanogen helps on huge application like PDF readers.
But even after editing those properties on the build.prop they are not taken into account. Maybe because of the previous installation i've done. So i'm looking to better understand how to override android properties.
I'm not sure how android handles non-default values for this property.
You should try with one of these:
120 (low-density)
160 (medium-density, Folio default)
240 (high density)
Depending on how this is handled, setting a density different than that may result in broken applications (depending on how the layouts are coded)
Using the LCD DEnsity application i confirm that all resolution are compatible with the folio
Maybe some application will have a bad behavior ! so we've to be able to change the density
metuskale said:
I there, is this fix already implemented or has to be done manually?!?
Click to expand...
Click to collapse
This is no fix, as there are no real issues with these things. Its only a matter of tweaking the folio to your best personal use. They have to be implemented manually.
Shouldn't the dalvik heapsize fix the sound problem with some avi files?
I'm using the foliomod 1.3d, foliowidget works, but some avi files arn't giving me sound
Hello, could someone tell me how the default value for the heapzize is, please? There is only 16, 24 and 32 to choose, but I read something about 64!? How can I choose this value or get back to default?
Thx
Tom
Edit: solved!
Hello All,
I am Charan Kumar, a beginner in android. I have created an UI design XML file. The design I have created shows all the components on a 3.7 inch display screen phone(default Nexus Phone in eclipse emulator). But, When I try on 3.2 inch and 3.4 inch screen phone, the components which are at lower part of UI are not getting displayed. The components are not getting fitted to the screen.
I am using "dp" to mention height, and "fill_parent" for width.
Please help me how to design an UI that displays all components on all phones, the design must be compatible for all mobile screens.
U cannot use dp or any other hard coded methods if u want the UI to work for all screen sizes.
I would suggest 2 options.
1. Use fill_parent n wrap_content only as view sizes and use weight attribute and margin and padding values to set the positions and sizes.
2. Else if u want to set the sizes preciously, set the sizes dynamically after reading the screen size from windowManager.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Hello Tablet Z community,
This is my first post in this devices forums since getting mine last week. It's a great device, love it, etc.
I've never owned an Android device with a screen resolution this high so I've yet to encounter this problem - some of my games (specifically the emulator PPSSPP) have relatively low framerates (compared to my less powerful Samsung P6810 @ 800x1280). I know with computers in particular it's trivially easy to change resolutions in games/the OS, especially to increase FPS but I've never seen a method to do this on Android and Google searches turn up people mentioning device resolution without changing them.
Does anyone know if it's possible to, ideally, force a different resolution for a particular application? A less than ideal solution would be a system wide change but I would be willing to endure temporarily to increase FPS.
Any advice and suggestions would be greatly appreciated
I would be interested to know about this, iv just loaded ppsspp however havent been able to play any of the playable games listed, I did see a few videos of the xperia z playing well, however that has the same resolution and specs.
juzza87 said:
Does anyone know if it's possible to, ideally, force a different resolution for a particular application? A less than ideal solution would be a system wide change
Any advice and suggestions would be greatly appreciated
Click to expand...
Click to collapse
That was recently discussed in this thread: LCD Density Changes and Results (With Pics)
Cat McGowan said:
That was recently discussed in this thread: LCD Density Changes and Results (With Pics)
Click to expand...
Click to collapse
This is very different, setting the DPI to a non-stock value just resizes the userspace, the resolution is fixed and unchangeable as the OP is thinking. Compared to a Windows PC where you can change the resolution, in Android you only have the ability to change the dpi, which states how large the pixel-to-screen size is. A smaller number indicates a smaller pixel-to-screen size, meaning the information shown on screen is sized for a laeger screen (making it smaller, since the screen is a fixed size). And a larger number has the reverse effect. Android UI guidelines set the optimal dpi for resolution vs. screen size, to mainain a similar experience across devices (similarly sized icons and fonts, etc). Again, this has nothing to do with adjusting the physical resolution of the device, which (to my knowledge) is not possible in Android.
daveid said:
This is very different, setting the DPI to a non-stock value just resizes the userspace, the resolution is fixed and unchangeable as the OP is thinking. Compared to a Windows PC where you can change the resolution, in Android you only have the ability to change the dpi, which states how large the pixel-to-screen size is. A smaller number indicates a smaller pixel-to-screen size, meaning the information shown on screen is sized for a laeger screen (making it smaller, since the screen is a fixed size). And a larger number has the reverse effect. Android UI guidelines set the optimal dpi for resolution vs. screen size, to mainain a similar experience across devices (similarly sized icons and fonts, etc). Again, this has nothing to do with adjusting the physical resolution of the device, which (to my knowledge) is not possible in Android.
Click to expand...
Click to collapse
Heh. Thanks for the schooling, but it was unnecessary, I didn't just fall off a turnip truck.
Thanks for the replies guys, at least now I know for sure..
[[MODS-Please move to Right Section if needed, Sorry if posted in wrong section]]
I have been trying to get used to the DPI adjustments on the GPe ROM. It appears that the default DPI is set at 400 on install but using ROMToolBox (You can use your favourite app to change DPI), I was able to tweak it to the most optimum number and concluded that DPI 289 is the most comfortable to the eye and compatible with Apps. I went all the way down to early 210s and tracked it all the way up but could not find any DPI better than 289 that accommodated the application options menus, the operation of the camera on the default GPe Lock Screen and the much nicer arrangement of the icons on the App Drawer.
You can off course try to experiment with different setups and share your findings but I think I am on to something. Enjoy the Post!
AWFRONT said:
I have been trying to get used to the DPI adjustments on the GPe ROM. It appears that the default DPI is set at 400 on install but using ROMToolBox (You can use your favourite app to change DPI), I was able to tweak it to the most optimum number and concluded that DPI 289 is the most comfortable to the eye and compatible with Apps. I went all the way down to early 210s and tracked it all the way up but could not find any DPI better than 289 that accommodated the application options menus, the operation of the camera on the default GPe Lock Screen and the much nicer arrangement of the icons on the App Drawer.
You can off course try to experiment with different setups and share your findings but I think I am on to something. Enjoy the Post!
Click to expand...
Click to collapse
wrong section bro,btw try set to 290.
Agree. I've set mine to 290 as well
Sent from my C6806_GPe using xda app-developers app
not GPe, but I have SlimKat set to 280, might just tyr 290 to see what the fuss is about
EDIT:
No real difference at 290 compared to 280, except that chrome popped out of tablet mode at 290
I've used all my android phones till now (galaxy nexus, xperia z and now z ultra) at tablet LCD density (half the default setting) - 160 for ZU, rotation locked on landscape, with large font size and at times custom font types too.
Try DPI 260 its perfect
jutley said:
Try DPI 260 its perfect
Click to expand...
Click to collapse
Thanks for the share but as I stated in my original post, if we want to enjoy using our XZU at its best as a GPe ZU, then the lowest DPI we should go for is 289 for the following reasons; Lock screen is intact with camera shortcut visible, Applications Drawer is more unified and certain applications are better handled with their options/menus visible. At DPI 260 The UI is broken, lockscreen is not complete and applications with menus have their menus missing i.e try RealCalc to see what I mean.
I would really like to hear from anyone who can go much lower than the DPI of 289 and share their findings as to whether the above issues could be experienced. If not I really want to push it as low as possible to get the best out of the XZU screen real estate without compromising stability and completeness of the UI features.
AWFRONT said:
Thanks for the share but as I stated in my original post, if we want to enjoy using our XZU at its best as a GPe ZU, then the lowest DPI we should go for is 289 for the following reasons; Lock screen is intact with camera shortcut visible, Applications Drawer is more unified and certain applications are better handled with their options/menus visible. At DPI 260 The UI is broken, lockscreen is not complete and applications with menus have their menus missing i.e try RealCalc to see what I mean.
I would really like to hear from anyone who can go much lower than the DPI of 289 and share their findings as to whether the above issues could be experienced. If not I really want to push it as low as possible to get the best out of the XZU screen real estate without compromising stability and completeness of the UI features.
Click to expand...
Click to collapse
220 dpi definitely starts to break the UI on slimkat where 280 or 290 (camera on locksceen fails at 280 but works at 290) is good for most apps that I use, I then use app settings and bump a few apps down to 220-240 (gmail etc)
How on earth are you capable of doing anything with a DPI under 200? I can't imagine getting anything done with that kind of DPI when I'm walking, or even standing up. 320 (stock) is in my opinion the best since all UI elements are properly sized and they can be tapped on without having to aim for anything.
Sent from my C6833 using Tapatalk
For those who don't know you can change DPI in the dev menu under "Minimum Width" (not taking any responsibility if you mess something up lol there is a reason it is hidden in the dev menu). The default is 411.
So far I have tried 10 different settings but due to the aspect ratio of the screen I cannot find the perfect DPI for games but also for everyday use. Not a fan of changing DPI just to play a game when I have a few minutes to kill. Any one have better luck?
Mine is currently at 441 (which means it must have adjusted itself from the 440 I set it to), and I think it's pretty good for daily use.
Can't really speak for games though.
Yep I'm using 480 at the moment and games seem to fit great but some apps don't like it
I've had mine set to 530 (it defaults to 533 after exiting settings for some reason) for a while. I found that setting it to anything above 550 results in a misaligned finger register where taking one place registers about 4mm above it. As much as I'd love to set it to 570, doing so results in this misalignment.
I haven't noticed any issues with 530. Only thing that messes up is Samsung's keyboard, but I use the AOSP Android L keyboard with the symbols.
Could you please post images of these gaming issues you are referring to?