Has anyone else had a problem with Chaos Rings where it runs fine but the game does not run full screen and the text boxes for speech text are not aligned with the text and the characters and interactive items on the screen are out of place from the background when played on a Honeycomb tablet with a 7" screen with an LCD density of 120? If I change the density to 160 it displays fine, but that changes Honeycomb to look like Gingerbread and screws up the menus and everything else and I don't want to have to reboot the tablet every time I want to play the game. I know the game uses pre-rendered backgrounds and that's probably what's causing it, but I've scoured the Web for days and found no one else with this problem or a way to fix it. My Thunderbolt with Gingerbread runs it fine as well. Someone please help!
Sent from my Streak 7 using witchcraft
zenisnotchosen said:
Has anyone else had a problem with Chaos Rings where it runs fine but the game does not run full screen and the text boxes for speech text are not aligned with the text and the characters and interactive items on the screen are out of place from the background when played on a Honeycomb tablet with a 7" screen with an LCD density of 120? If I change the density to 160 it displays fine, but that changes Honeycomb to look like Gingerbread and screws up the menus and everything else and I don't want to have to reboot the tablet every time I want to play the game. I know the game uses pre-rendered backgrounds and that's probably what's causing it, but I've scoured the Web for days and found no one else with this problem or a way to fix it. My Thunderbolt with Gingerbread runs it fine as well. Someone please help!
Sent from my Streak 7 using witchcraft
Click to expand...
Click to collapse
How did you fix the alignment issue?
I didn't. I gave up after a while and I was only able to play it on my Thunderbolt.
The only way to fix it is to change the DPI of your tablet to 160dpi. It doesn't run on 120dpi tablet/smartphone.
btw: If you are going to change the dpi of your device, make sure that you change the resolution as well to match up the icon, 1020x600 is best for 160 dpi on wide screen devices.
Related
Has anyone had success with the LDC Density app? My friend used it on his galaxy s it was pretty cool
I tried it and my phone just froze. Had to do a battery pull to fix it.
Yes, im rooted.
this has been answered multiple times in a few thread.
maybe if you tried searching you'd have an answer.
Froze on my rooted TB with Adrynalyne's Rom. Curious to see if anyone has this working.
Didn't work for me either. Just manually edited /system/build.prop to change it around. Messes with the look of the Sense Clock Widget, and certain skins for the SenseUI.
Chris Hansen said:
Didn't work for me either. Just manually edited /system/build.prop to change it around. Messes with the look of the Sense Clock Widget, and certain skins for the SenseUI.
Click to expand...
Click to collapse
where in the build.prop do you edit the file?
nm found the line. it was obvious enough
FWIW 190 has been a good number for me. I was at 200 for awhile, set it at 190 today and it runs pretty well.
So I take it you aren't running Sense then? Because anything lower than 240 messed up the flip clock and some of the themes bar at the bottom.
I am sure I am not alone when I say this but does anybody know why the fonts on the screen are so massive? Was this phone originally intended for people with failing vision?
Why, with such a lot of real estate, doesn't htc squeeze in more info into the screen so that we lessen scrolling? Beats the hell out of me.... Its irritating to say the least. The net effect is that I have a bigger phone than the inc but I have exactly the same amount of info on the screen. I really do not see the point...
Rant over - now how do we lower font size and line spacing without messing everything up. Any easy fixes? In the uber z rom for the inc, gmichaelow made a zip that changed font sizes and line spacing to much lower levels without messing anything up. So its possible. LCD density is definitely not the answer.
khanam said:
I am sure I am not alone when I say this but does anybody know why the fonts on the screen are so massive? Was this phone originally intended for people with failing vision?
Why, with such a lot of real estate, doesn't htc squeeze in more info into the screen so that we lessen scrolling? Beats the hell out of me.... Its irritating to say the least. The net effect is that I have a bigger phone than the inc but I have exactly the same amount of info on the screen. I really do not see the point...
Rant over - now how do we lower font size and line spacing without messing everything up. Any easy fixes? In the uber z rom for the inc, gmichaelow made a zip that changed font sizes and line spacing to much lower levels without messing anything up. So its possible. LCD density is definitely not the answer.
Click to expand...
Click to collapse
I thought the exact same thing, my Droid has a higher resolution than the Thunderbolt (480x854 for OG Droid vs. 480x800 for Thunderbolt). Everything was blown up like crazy. I don't understand why they wouldn't have gone higher for a crisper look to rival the sleek look of the iPhone. There should be font packs out there, but I'm not sure where yet. Lowering my density to 190 definitely looks a lot better for everything but the notification bar icons. I'm going to look into smaller fonts as well, but for now, I'm happy with the lowered density, as it also makes things on screen look more crisp.
I've heard people talk about this in the past, but never fully understood what it did? Any explanation of what this actually does is appreciated. Thanks in advance
Just look at my picture compared to the stock setup. Mine is much crisper and smaller. It's like upping the resolution basically.
Chris Hansen said:
I thought the exact same thing, my Droid has a higher resolution than the Thunderbolt (480x854 for OG Droid vs. 480x800 for Thunderbolt). Everything was blown up like crazy. I don't understand why they wouldn't have gone higher for a crisper look to rival the sleek look of the iPhone. There should be font packs out there, but I'm not sure where yet. Lowering my density to 190 definitely looks a lot better for everything but the notification bar icons. I'm going to look into smaller fonts as well, but for now, I'm happy with the lowered density, as it also makes things on screen look more crisp.
Click to expand...
Click to collapse
Thanks. Will try this. Hopefully it does not mess any widgets.
Sent from my thunderbolt
Lcd density just hangs on my phone. I'm running storm. Anybody else manage to get it working on that rom?
Sent from my thunderbolt
Does anyone have themes out for specific lowered densities? I have found that when I lower the density, the bottom dock (Where the phone, app tray and personalize button are) looks disconnected and not very nice. Only thing holding me back.
Is there a way to keep with the stock launcher and theme it so it fits or would I be forced to switch to another launcher to alleviate that problem?
going to give this a try and see how it goees
i tried 225, 220, 210 and would rather just leave it at stock 240 than have blurry status bar icons...that drives me nuts and makes the phone look like ****..the rest of the screen looked perfect at 225 for me tho..
I run at 190. I used to run at 140 on my dinc. I hate big resolutions. I don't use the sense launcher so I don't have aproblem with it getting messed up
Sent from my ADR6400L using XDA Premium App
Even manually editing the build prop (CHMOD 777) I'm unable to get the changes to take effect. Any advice?
Gimpeh said:
Even manually editing the build prop (CHMOD 777) I'm unable to get the changes to take effect. Any advice?
Click to expand...
Click to collapse
Use root explorer, find build.prop, open it in a text editor, change the line that says LCD density. Save and exit, reboot. Done.
FatTony666 said:
Use root explorer, find build.prop, open it in a text editor, change the line that says LCD density. Save and exit, reboot. Done.
Click to expand...
Click to collapse
Yeah thats what I meant by manually changing the build prop.
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
I just flashed CM7 on my Nook Color last night. While it looks and works great on the 7" screen I did notice some things were a bit too small and hard to read. You can always increase font sizes in specific applications but that's not a consistent solution to the problem. After experimenting with different DPIs, I found 187 to be okay but still a bit too small in some areas, 240 to be too large, and 204 to be just about perfect, allowing me to keep font sizes set to normal in applications and the handle on the notification tray remains in the center. Blurriness hasn't bothered me too much yet. I'm curious what values other people are using.
As an aside, why does increasing the DPI make elements larger and not the reverse? Thinking of it as "dots per inch," I would think more dots within an inch means a rendered element would fit into a smaller space...
Honestly, I've found the default 161 quite usable so I haven't played with it for quite some time.
Sent from my Apple IIe
hololight said:
Honestly, I've found the default 161 quite usable so I haven't played with it for quite some time.
Sent from my Apple IIe
Click to expand...
Click to collapse
Ditto. 240 (and such) just create icons wayyyy to big for me. I have a high res screen, i want to use it as such.
I personally like 140, however you lose "My Apps" ability in the market at this DPI.
The default 161 with a different font applied works for me. (The font is mentone, in case you were wondering.)
I tried 180 for awhile but that screwed up the formatting on a lot of apps.
Default for me. Tried many others and they either made the icons look big and stupid or really screwed up formatting in some apps.
I've been using 187 for about a month now. I think it looks nice, and really helps with the close-to-edge unresponsiveness by having slightly bigger objects to poke. I enjoy spending unreasonable amounts of time crafting custom UI's, and certain setups really pop with higher LCD density settings. I ran 210 for a while combined with a really sleek super simple interface. Ended up scraping it because it required an insane amount of widgets and 500 megs of RAM just wasn't enough.
Play around with the popular settings. Personal preference trumps what ever you'll read here.
Sent from my NookColor using Tapatalk
I just stick with 161.
Still rocking the Incredible with the XDA Premium App.
I need to use 160 for some apps to go fullscreen (Google Reader & FieldRunners). But this kills My Apps in the market. Does anyone know a DPI that will scale these apps correctly and keep the market working 100%?
JonMayer said:
I need to use 160 for some apps to go fullscreen (Google Reader & FieldRunners). But this kills My Apps in the market. Does anyone know a DPI that will scale these apps correctly and keep the market working 100%?
Click to expand...
Click to collapse
Fieldrunners works at any DPI if you turn off compatibility mode. The only fix for GoogleReader is to use a different program
Market works fine at 161+
Thanks for the info on the game. I'm going to reboot and try that out now. I used to love that game on my iPod Touch.
I figured the Reader app just hasn't been updated in forever is why. I'll stick with my 161 then. I like the size of everything on the screen and it's still comfortable for me to read.
I use the default setting..
If you have the new Market, I would recommend using 160.
160 will be the new default as soon as more folks get the update Market.
dalingrin said:
If you have the new Market, I would recommend using 160.
160 will be the new default as soon as more folks get the update Market.
Click to expand...
Click to collapse
My first thought when the new Market appeared was, "OMG I hope it works at 160 so I can have both my Market and Google Reader working at the same time!"
And.... so far so good! Woooooooooooooot!
dalingrin said:
If you have the new Market, I would recommend using 160.
160 will be the new default as soon as more folks get the update Market.
Click to expand...
Click to collapse
SiMi clock doesn't display correctly at 160.
It doesn't display correctly at 161, either, but it's worse at 160.
161 leaves a column of pixels unused on the right side in portrait, where the wallpaper shows through the clock's background.
160 makes the clock's background very thick, and overlaps my power button widget in landscape mode.
I've been using 169. This creates the least bit of widget overlap between the clock and power bar, and also makes the clock cover the entire row in portrait. It makes desktop icons a tad blurry, though. Everything else displays fine.
gadzooks64 said:
My first thought when the new Market appeared was, "OMG I hope it works at 160 so I can have both my Market and Google Reader working at the same time!"
And.... so far so good! Woooooooooooooot!
Click to expand...
Click to collapse
Sorry to burst your balloon. After a couple of reboots, My apps disappears (just like before).
So I'm running DJ-Steve's latest Honeycomb on my DS7 and I have an app for fiddling with the density. At the resolution I really prefer (don't recall which one). Whenever I download and install apps they appear JUST off the edge of the screen with no way to retreive or move them short of changing the density, moving them, changing back, etc..... PITA. is there some way I can make these stupid things not do that? OR does android have some sort of "auto arrange desktop" option or something like that?
Thanks
fliberdygibits said:
So I'm running DJ-Steve's latest Honeycomb on my DS7 and I have an app for fiddling with the density. At the resolution I really prefer (don't recall which one). Whenever I download and install apps they appear JUST off the edge of the screen with no way to retreive or move them short of changing the density, moving them, changing back, etc..... PITA. is there some way I can make these stupid things not do that? OR does android have some sort of "auto arrange desktop" option or something like that?
Thanks
Click to expand...
Click to collapse
This is because this was based on Honeycomb for a 10inch - the grid is larger than our screen.
Untill someone rips a build from one of the 7 inch Honeycomb tablets, or the source is released, this will be a problem.
If you don't need 3.2, you can DL 3.1 RC3, and use the 160 image. DJ_Steve was somehow able to edit the launcher from one of the 10 inch builds to fit our screen perfectly in that build. It's by far my favorite Honeycomb build. I check all the Honeycomb updates to try them out, but always find myself back on Froyo or 3.1 RC3.
I sorta figured thank you. Just seems like if the system could keep the little google voice search widget and the apps tray framed properly it should be able to keep everything else in check.
Thanks
Has anyone figured out how to get the Opera Mobile tablet friendly UI in CM9? The UI is great in CM7 but on CM9 it defaults to the phone UI.
Sent from my NookColor using xda premium
I'm having the same issue, it seems that the reason behind it is that the ICS builds have LCD density and DPI setting which result in Android believing that the screen is 4 inches instead of 7 inches. There are several screen test utilities on the market and all show a screen diagonal of about 4 inches.
I posted this issue on my.opera and predictably (seems that their devs don't read the forums...) received no answer to date.
Does anyone know of a utility to change the DPI settings in ICS, or how to manually chnage them in the build.prop (or does ICS store this somewhere else?)? I've played aound a bit but without success.....
Thanks,
Changing screen density to 120 gets the Tablet UI, makes things very small though in launcher etc....
I haven't tried Opera mobile but I played with Opera mini some.
It worked okay after I reduced the font size.