In coming from the Evo to the Photon, the biggest change for some on the down side is the font is smaller. And I can't find a perfect way to change it. I have 2 options and they are both a little flawed.
Font Size (for root users) - It works great but I am noticing that fonts are sometimes not big enough for the space they are in (menu items, widgets, and android market text are good examples) so the font is kind of cut off on the top and/or bottom. But the font does get larger.
Spare Parts + Pro - This changes the font perfectly. I can even select the largest size with no worries of fonts being cut off. The problem is, the setting is not saved. All you have to do is shut your phone off or worse, merely rotate your screen and the setting is gone.
Does anybody know a better suggestion? Any help would be greatly appreciated. Cause I have to say, It is straight up ridiculous that this question needs to be asked. And I don't mean ridiculous of the community, I mean it is ridiculous that the people that develop the operating system do not include such a setting in every phone.
I"m greatful for the 2 apps I mentioned above and I registered both. But I really hope somebody knows a better suggestion, one that lets you increase the font size as reliably as Spare Parts + Pro and saves that setting like Font Size (for root users). I would really appreciate it.
bump...wanting same solution. Spare parts won't hold setting for me, either.
What do you think the chances are that someone will develop a ROM that incorporates larger font sizes?
I haven't found anything that works like you're looking for. Unfortunately most apps were designed with a lower resolution in mind. Now that phones are arriving with higher resolutions developers are gonna need to update their apps.
The Evo was what 800x480? Photon (and other QHD's) run 960x540. BIG difference for text on you screen.
If you're rooted you can use something like LCD Density changer to mimic the density of the EVO 4g (LCD density of Evo 4g was 240)
https://market.android.com/details?id=lv.n3o.lcddensity&feature=search_result
stevieraveon said:
If you're rooted you can use something like LCD Density changer to mimic the density of the EVO 4g (LCD density of Evo 4g was 240)
https://market.android.com/details?id=lv.n3o.lcddensity&feature=search_result
Click to expand...
Click to collapse
Good call...forgot about suggesting that!
LCD Density changer - Yipee...that was it!!!! Thank you sooooo much
I think I love my Photon now. I was considering going back to the Evo 4g because of the larger font. Been looking at everything except a "density changer".
i changed my lcd density in the rom toolbox and now so many apps will not let me download them... any idea what the lcd density should b on the photon so i can go back to that.
uncfan44 said:
i changed my lcd density in the rom toolbox and now so many apps will not let me download them... any idea what the lcd density should b on the photon so i can go back to that.
Click to expand...
Click to collapse
I have not found any phone different than 240. I have the photon and it was 240.
I have the same issue with apps like you. I have to reset my density to 240, reboot and then update my apps now and then.
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
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.
This was a duh moment for me, so learn from my fail.
If your having issues with apps not allowing you to update/install and the online market says your device is not compatible and you've modified your lcd density, comment out that line in your build.prop and reboot. Open the market after and poof, market works again. Likely the reason folks smarter than me (djsteve, etc.) comment this line out or exclude it by default in roms now...
Sent from my Dell Streak
Ic... understand now...
strvmarv said:
This was a duh moment for me, so learn from my fail.
If your having issues with apps not allowing you to update/install and the online market says your device is not compatible and you've modified your lcd density, comment out that line in your build.prop and reboot. Open the market after and poof, market works again. Likely the reason folks smarter than me (djsteve, etc.) comment this line out or exclude it by default in roms now...
Sent from my Dell Streak
Click to expand...
Click to collapse
Thanks for the information...
I was confused because this happened today after re-flashing the rom and adjusted the LCD density... (DS5 to 200, Galaxy 5 to 130) but should give up to adjust LCD density to suitable for me because of this market problem ?? Not easy to decide....
Is there any other solution ???
Thanks, anyway... help me to save my time a lot to find out the problem...
there are no known solutions to this problem except a couple cheap tricks (only one in fact: freeze the market updater, uninstall all market updates and manually install market v2.x, but you still wont be able to install from the website).
also it is nothing that rom chefs/devs can solve: it's a "feature" google implemented in the latest market versions. of course it's device independent, too.
the only good lcd densities are 160 (streak default) and 240 (big UI small estate, like all normal 4'' screen phones).
I run my streak @ 240 dpi and have occasional issues with the market, I use lcd density changer app to change the dpi, it's easy enough to reset to 160, install the app, then reset the lcd density....not a hassle, really (I wish it wasnt necessary but oh well, I guess if I want to tweak the device around, having to do that is part of the tweaks needed)
GT247 said:
I run my streak @ 240 dpi and have occasional issues with the market, I use lcd density changer app to change the dpi, it's easy enough to reset to 160, install the app, then reset the lcd density....not a hassle, really (I wish it wasnt necessary but oh well, I guess if I want to tweak the device around, having to do that is part of the tweaks needed)
Click to expand...
Click to collapse
weird, 240 dpi shouldnt be an issue (as a matter of fact, on mine it isnt) because it's a standard setting. most phones (like sgs2, sgs, sensation etc) use this value.
240 may be standard with most devices, but not the s5.
240 breaks the dialer, ui wise on 2.2, completely on 2.3
The default dpi is 160, why stuff doesnt show up on market might have to do with the way the app author published it, or it could be a bug
TheManii said:
240 may be standard with most devices, but not the s5.
240 breaks the dialer, ui wise on 2.2, completely on 2.3
The default dpi is 160, why stuff doesnt show up on market might have to do with the way the app author published it, or it could be a bug
Click to expand...
Click to collapse
yes, but it's a standard setting. hdpi has 240 mdpi has 160. Therefore publishing an app that isnt compatible with 240 would be overkill for a developer. Regarding this there is a bug report on google, link:
http://code.google.com/p/android/issues/detail?id=19744
the problem, it seems, is related mainly to a change of policies from google: now developers MUST explicitly declare compatibility with non-standard lcd densities whereas in the past it was simply ignored.
I recommend everyone to star the issue at the above link (but don't comment as every comment generates notif email)
Just wanted to congratulate you guys on a great app.
I have a Galaxy Mega 6.3 i9205 which has a resolution of 1280x720 but unfortunately a default 240 dpi.
Most parts of various themes working correctly, its just a few items are not correctly aligned.
From experience, the 240 dpi causes problems with other launchers and changing to 320 dpi fixes those launchers but makes the rest of the interface far too big and breaks some of the menus.
I was wondering if there was a way to adjust some of the themes manually or anything else I could do?
Much appreciated.
neodoughnut said:
Just wanted to congratulate you guys on a great app.
I have a Galaxy Mega 6.3 i9205 which has a resolution of 1280x720 but unfortunately a default 240 dpi.
Most parts of various themes working correctly, its just a few items are not correctly aligned.
From experience, the 240 dpi causes problems with other launchers and changing to 320 dpi fixes those launchers but makes the rest of the interface far too big and breaks some of the menus.
I was wondering if there was a way to adjust some of the themes manually or anything else I could do?
Much appreciated.
Click to expand...
Click to collapse
Hi, it's hard to say as Themer is designed to look what phone it's on, in this case the Mega isn't fully supported. The advice we could give would to to maybe try changing the resolution as well, but we can't guarantee this will work and that you should try it at your own risk.
neodoughnut said:
Just wanted to congratulate you guys on a great app. Most parts of various themes working correctly, its just a few items are not correctly aligned. From experience, the 240 dpi causes problems with other launchers and changing to 320 dpi fixes those launchers but makes the rest of the interface far too big and breaks some of the menus.
Click to expand...
Click to collapse
ThemerSupport said:
Hi, it's hard to say as Themer is designed to look what phone it's on, in this case the Mega isn't fully supported. The advice we could give would to to maybe try changing the resolution as well, but we can't guarantee this will work and that you should try it at your own risk.
Click to expand...
Click to collapse
This is why I created a similar thread a few days ago. Themer does not play well with non-stock DPI. If widgets and other graphics could be placed relative to the display margins/center (instead of absolute pixels), they should render correctly regardless of DPI.
sublimaze said:
This is why I created a similar thread a few days ago. Themer does not play well with non-stock DPI. If widgets and other graphics could be placed relative to the display margins/center (instead of absolute pixels), they should render correctly regardless of DPI.
Click to expand...
Click to collapse
Zooper already does render things like this. Try out something like Simple Sea or Pro UI. I rebuild these themes so that the anchor points for objects are relative to the side of the screen they are on. IE Top Center, Top Left, Top Right, Center, Center Left, Center Right, Bottom Center, Bottom Left, Bottom Right.
The only things that you will likely have issue with are when Zooper adds spacing, so layers such as Regular Text thats curved, Series based layers, and Progress bars that have spacing splits. Also Regular and Rich Text, that is set to an anchor of left or right, but also has a text alignment of Center, will be off by a bit. These are all as you are saying based on absolute pixel. Everything else in Zooper is based off of DIP (device independent pixels, http://developer.android.com/guide/practices/screens_support.html#density-independence)
There is NO WAY to fix these issues without breaking every Zooper widget, be it stand alone or in Themer, that was produced before your suggested change.
We do not support non-stock DPI. So if you want to use non-stock then you are going to have to do a little leg work on your own to fix the themes on your device.
ritalin said:
Zooper already does render things like this. Try out something like Simple Sea or Pro UI. I rebuild these themes so that the anchor points for objects are relative to the side of the screen they are on. IE Top Center, Top Left, Top Right, Center, Center Left, Center Right, Bottom Center, Bottom Left, Bottom Right.
The only things that you will likely have issue with are when Zooper adds spacing, so layers such as Regular Text thats curved, Series based layers, and Progress bars that have spacing splits. Also Regular and Rich Text, that is set to an anchor of left or right, but also has a text alignment of Center, will be off by a bit. These are all as you are saying based on absolute pixel. Everything else in Zooper is based off of DIP (device independent pixels, http://developer.android.com/guide/practices/screens_support.html#density-independence)
There is NO WAY to fix these issues without breaking every Zooper widget, be it stand alone or in Themer, that was produced before your suggested change.
We do not support non-stock DPI. So if you want to use non-stock then you are going to have to do a little leg work on your own to fix the themes on your device.
Click to expand...
Click to collapse
In my original thread, I mentioned the fact that graphic elements were still irregular when DPI was changed to stock. This persisted after multiple uninstalls/reinstalls, cache & dalvik wipes. But thanks for the feedback.
Sent from my SCH-I605 using Tapatalk
Was Was thinking about getting that phone but it doesn't have a Stylus and I thought it wasn't a quad core too.
From time.... CM users await DPI support....
Hispanico
Themer for Xperia U
I have an Xperia U ST25i and i have trying to install themer on it....while i can install it. I cannot access the themes.
I know that you currently do not support Xperia U for this app.. but i just wanted to know if there is a work around to this by changing the Dpi of my screen and if so, could you point me in a direction where i can get further information. Thanks
This would be a great addition for those roms who change the default dpi. In my installation of slimkat most themes are simply unusable,
karanvir90 said:
I have an Xperia U ST25i and i have trying to install themer on it....while i can install it. I cannot access the themes.
I know that you currently do not support Xperia U for this app.. but i just wanted to know if there is a work around to this by changing the Dpi of my screen and if so, could you point me in a direction where i can get further information. Thanks
Click to expand...
Click to collapse
Full Xperia U support is on its way. You can try modifying the DPI and resolution, but we'd recommend just waiting a few more weeks, it will be worth the wait
ThemerSupport said:
Full Xperia U support is on its way. You can try modifying the DPI and resolution, but we'd recommend just waiting a few more weeks, it will be worth the wait
Click to expand...
Click to collapse
I am not the kind who nags but i really can't wait anymore to get themer on my phone..... any news ??? is there light at the end of this tunnel?
Thnx man.... That Worked
karanvir90 said:
I am not the kind who nags but i really can't wait anymore to get themer on my phone..... any news ??? is there light at the end of this tunnel?
Click to expand...
Click to collapse
There is light, it's just going to take a while :fingers-crossed: Delays in this current version pushed everything else a few weeks behind schedule.
Hello. This is probably a first, but i want to ask if anyone knows how i could resize everything on my phone, so that its a bit smaller? Lets say the statusbar is a bit thinner, then the icons on the bottom of the screen are smaller. I've seen my friend do it once, it creates the illusion of a bigger display screen, i don't know how he did it though. So far i'm using [THIS] rom.
Is this possible on the xperia go?
Basically if it were a windows computer, to do this you'd change the resolution to a bigger one, as on lets say 800x600 the icons would be big, everything would be big, and if you change it to 1280x720 it would all shrink a bit.
Add this line to /system/build.prop (a few ROMs already have it, likely set to 240, in which case obviously just change the number):
ro.sf.lcd_density=200
200/210 is the setting I'm most comfortable with (sufficiently small but keyboard still usable).
Keep in mind that a few apps like Sony's launcher don't work well with DPI changes...
Ryccardo said:
Add this line to /system/build.prop (a few ROMs already have it, likely set to 240, in which case obviously just change the number):
ro.sf.lcd_density=200
200/210 is the setting I'm most comfortable with (sufficiently small but keyboard still usable).
Keep in mind that a few apps like Sony's launcher don't work well with DPI changes...
Click to expand...
Click to collapse
thank you, that worked. The rom i'm using is using a kitkat launcher which works splendid, only thing i noticed that is buggy is the number dialer, which i'll probably just replace with a different one now. cheers