Database Info

Screen problem when playing some games.

Hi there, I'm using VaniljEclair RLS7c, Android 2.1 (downloaded from here: http://forum.xda-developers.com/showthread.php?t=700669)
I've installed a game named ShootU.
But when I play it, the screen shows not properly.
I still installed some other games and faced almost the same problem.
I got a screenshot of ShootU as below, anybody knows how to fix this problem?

I've tried to set the density to 160 in startup.txt and it works.
BUT the icon and text in the desktop and other UI became too large. If I want to use the normal density, I'll have to shutdown and edit the startup.txt and reboot. It's very inconvenient.
Is there any solution?

taurusqh said:
I've tried to set the density to 160 in startup.txt and it works.
BUT the icon and text in the desktop and other UI became too large. If I want to use the normal density, I'll have to shutdown and edit the startup.txt and reboot. It's very inconvenient.
Is there any solution?
Click to expand...
Click to collapse
If you are using NANDroid it is much easier you can use rogue tool to change density
as for haret users we are restricted with following:
- modifying default/startup.txt (currently any lcd mod to default.txt is no longer recognized by kernel---I cannot use this)
- modifying /system/build.prop (copy build.prop change density [ro.sf.lcd_density=xxx], put it on the /system folder and use 7zip to create androidupdate.tar. put it on /andboot folder, run haret, use menu to manually install it just like another update. btw, create two version of this)
So there is not convenient way to change density
PS: I read somewhere that metamorph can be used to prevent certain app to use wrong density, but I still do not know how

wrong place, sorry

Thx mensa07.
I've tried ShootU in a 2.2 build (Incubus26Jc's Super FroYo), the density is default(maybe 120) and it runs fine!!!
But I sometimes got no response in this biuld and had to reboot.
btw, have u tried the overclocking in RogueTools? Did it work?
I've tried, but it seems no change when I use linpack to test the cpu. The scores (around 1.9)are just a little higher than in the 400MHz(around 1.6).
And I've run linpack in a 2.2 build (Incubus26Jc's Super FroYo). Even in 400MHz, the scores are much higher (around 2.4-2.6).
So is that 2.2 has a better performance than 2.1?

taurusqh said:
Thx mensa07.
I've tried ShootU in a 2.2 build (Incubus26Jc's Super FroYo), the density is default(maybe 120) and it runs fine!!!
But I sometimes got no response in this biuld and had to reboot.
btw, have u tried the overclocking in RogueTools? Did it work?
I've tried, but it seems no change when I use linpack to test the cpu. The scores (around 1.9)are just a little higher than in the 400MHz(around 1.6).
And I've run linpack in a 2.2 build (Incubus26Jc's Super FroYo). Even in 400MHz, the scores are much higher (around 2.4-2.6).
So is that 2.2 has a better performance than 2.1?
Click to expand...
Click to collapse
have you tried different resolution for the game? like 320x480 (160) or 320 x 428 (160).
the most comfortable resolution is 320x240 (110) but some apps refuse to open
as for overclocking I have tried but not successful.
I am not sure about linpack score. I think it does not represent real life performance.

Flash on nand...

taurusqh said:
Hi there, I'm using VaniljEclair RLS7c, Android 2.1 (downloaded from here: http://forum.xda-developers.com/showthread.php?t=700669)
I've installed a game named ShootU.
But when I play it, the screen shows not properly.
I still installed some other games and faced almost the same problem.
I got a screenshot of ShootU as below, anybody knows how to fix this problem?
Click to expand...
Click to collapse
This is only Eclair bug, image cannot scale properly.
Decrease lcd.density to 112 if used 240x320, but better use Donut/Froyo.

mensa07 said:
have you tried different resolution for the game? like 320x480 (160) or 320 x 428 (160).
the most comfortable resolution is 320x240 (110) but some apps refuse to open
as for overclocking I have tried but not successful.
I am not sure about linpack score. I think it does not represent real life performance.
Click to expand...
Click to collapse
I've tried 320 x 428 (160) but the game was displayed in a smaller window not full screen and the rest of the screen was black.
I'm using froyo 2.2 now. I feel it's faster than Eclare. And the games run well.

Change Your Screen Resolution on HTC Evo 4g

In this post I'd like to share a small bit of Android information with you. I've discovered it while looking around at the build.prop file and did some research on it, and it turns out to be a pretty cool and powerful feature. Of course, seeing as this requires root you can probably already guess that it involves some more-than-consumer level risk, so anything you do here is your responsibility. This is not a tweak for a fairly novice user. You will need some basic knowledge on command line terminal and how to copy/edit files. I will be assuming you know how to setup and run ADB, and how to execute it and work with it in command prompt.
What's this mod do? Basically it changes your resolution (not really, but for simplicity sake we'll say it does) to a higher pixel density. What this means is everything on your screen will look smaller as if you changed your resolution on your PC to a higher setting. Now obviously we don't want to increase this too much or it will make our screen look bad and be impossible to read things, so I recommend you stick with the settings I have and only tweak it if you're daring.
Now for setup:
1: You require root access for this to work, so make sure you have it prior to doing anything else.
2: Next you will need to get your build.prop file from the /system directory. An easy (and free) way to do this is to use Astro file manager. Open up Astro, navigate to /system/ and copy the build.prop file to the sdcard.
3: Hook the phone up to your PC and enter USB Mass Storage mode. Open the drive on your computer and copy the build.prop file to the desktop.
4: IMPORTANT: make a second copy of this file, and rename it to: build.prop.BAK - accept the change to filetype and leave it alone for now.
5: Open up build.prop using notepad. Once its open you'll see a whole ton of text assuming you have Word Wrap enabled. Press Control + F and type in "density" then press enter.
6: Close out the search menu and find the number "240" to the right of "density"
7: Change the number from 240 to 200. Save the file and close notepad. (Note - higher numbers means bigger text/objects, smaller numbers means smaller text/objects allowing you to fit more on the screen)
8: Put your phone back into PC Mode, and then enable USB Debugging in Settings->Applications->Development
9: At this point I assume you have ADB setup on your PC. Copy and paste the modified build.prop file into the folder with ADB, and then open up a command prompt, change directory to wherever you have ADB installed (ex: cd C:\adb\ ), and type in "adb devices" without the quotes to start ADB and make sure your device is configured properly
10: Now you must push the modified build.prop file to your sdcard. To do so type this in:
adb push build.prop /sdcard/build.prop
11: You should see the text indicating it successfully transferred the file. Now type in "adb shell" without quotes. You should see a $: appear. Once it does, type in "su" and it should change to a #: sign.
12: Now that you're in root access, you must mount /system as read/write to copy over the new build.prop file. To do so type this in exactly as it is, making sure to not skip any spaces or use wrong letters/characters:
mount -o remount,rw /dev/block/system /system
You should see the line repeated and that means it went ok. If you get anything else like an error, somethings not right with the text you entered. Go back and double check it.
13: Now we'll copy the file from the sdcard to the system directory to overwrite the old build.prop file:
cp /sdcard/build.prop /system/build.prop
Again, you should see the line repeat below to confirm it copied it successfully. You can now reboot the phone to make the changes happen (note: for a speedy reboot, simply type in "reboot" from the #: prompt, this will drop you out of root shell and do an automatic reboot of your phone pretty neat)
Once your phone is booted back up you should notice some pretty significant changes in appearance. Everything will look smaller much akin to the changes you see on your desktop PC when you increase the resolution from say 800x600 to 1600x1200. In case you want to change it back to the old look, simply re-trace your steps using the original build.prop file, with the pixel density set to 240 instead of 200.
Screenshots for comparison. Note how lines of text are fully exposed in the new screenshots compared to the old ones, where it has to scroll/cut off text in App names etc:
http://forum.androidcentral.com/motorola-x-roms-hacks/32035-how-resolution-tweak-req-root.html

Or you can save a whole lot of time and effort and use this app. http://www.xda-developers.com/android/lcd-density-changer-application-v3-0-released/

I think that is pretty sweet bro!! Great finding
Sent from my PC36100 using Tapatalk

njfoses said:
Or you can save a whole lot of time and effort and use this app. http://www.xda-developers.com/android/lcd-density-changer-application-v3-0-released/
Click to expand...
Click to collapse
Been using this for a few days now. It works great. They should have released the Evo with the higher resolution from the start.

Looks great in my opinion. I lowered just slightly to 220 and i used RootExplorer to just change the Build.prop file.

Shouldn't this be in general? This is like dpi in windows lol... not resolution

rawdikrik said:
Looks great in my opinion. I lowered just slightly to 220 and i used RootExplorer to just change the Build.prop file.
Click to expand...
Click to collapse
yeah, root explorer is fantastic. it even creates a backup for you after you edit the file.

The interesting part about this is, I made a thread about the density change back when the EVO first launched and nobody cared lol

Just changed to 200 with the aforementioned app, the only problem I have is the main status bar and most of the popup menus and stuff look like crap. Hoping we can find some higher resolution (or whatever) pieces to use. Might be because I'm using Manup's theme.

bdoople said:
Just changed to 200 with the aforementioned app, the only problem I have is the main status bar and most of the popup menus and stuff look like crap. Hoping we can find some higher resolution (or whatever) pieces to use. Might be because I'm using Manup's theme.
Click to expand...
Click to collapse
i noticed that too....so i just went to like 215. 200 was looking good though

ro.sf.LCD_Density=240
Is that the proper value to change in root explorer?
Right below it, there is another value of 160, that's why I ask. I'm on an Evo
Poor resolution has always bugged me. On such a big screen, that number of pixels really isn't enough. This will be a great mod, just don't wanna mess it up.
Thanks.

see there's an easier way to do everything, by that i mean there is an app for that, lol.

scottspa74 said:
ro.sf.LCD_Density=240
Is that the proper value to change in root explorer?
Right below it, there is another value of 160, that's why I ask. I'm on an Evo
Poor resolution has always bugged me. On such a big screen, that number of pixels really isn't enough. This will be a great mod, just don't wanna mess it up.
Thanks.
Click to expand...
Click to collapse
The line below it (With the value of 160) has a # in front of it as that is the default value if none specified. Change the 240 to 200 or 220 or 210 or 190 etc depending on your preferences. Again, appelflap has an awesome application to easily do this for you and it provides a boot monitor as well that will check to make sure you can see the screen, and if you can't it will revert back to default setting in case you mess something up. It costs approximately $1 and is well worth it.

On my evo I am using the app and I set mine to 180. Everything looks fine so far. I don't recommend using it with the sense launcher at this level though.
Sent from my PC36100 using XDA App

Appreciate all the feedback. When it comes to system tweaks like this, I've always preferred to do them manually. Makes it easier to keep track of changes, and, if you know what's goin on 'behind the scenes'. Even with winmo, I always would opt for tweaking via registry editor, rather than some blind, hands-off tweak app.
Thanks all, though.
Edit: ok, foot in mouth. So I opened root explorer, found build.prop, opened it clicked the mount R/O toggle, but can't seem to edit it no matter what. NVM, found editor
Also, I checked out the app on the market, looked at comments and saw lots of people say that density broke certain apps, and can't get back to normal, broken phones, blah blah blah
Anyone speak to this?

Exposes lame apps
Worked great on rooted EVO running CM6.2.
Need to increase the power of my bifocals now!
Also exposes lame apps that display set screen resolutions, such as WeatherChannel. Poopnoodles!

Very cool find, not one I will be keeping though. The taskbar icons get a bit blurry, and the widget/icon spacing looks ugly.

njfoses said:
Or you can save a whole lot of time and effort and use this app. http://www.xda-developers.com/android/lcd-density-changer-application-v3-0-released/
Click to expand...
Click to collapse
Just tried that. Was able to make a few changes with no problems. As soon as I tried to go back to the stock settings my phone would no longer boot past the white EVO screen. Doing a restore now
And of course the restore isn't working properly for some reason. Argh.

yeah
Yeah, I read the thread by Appleflap, about his app, and it really sounds like there are a lot of issues from doing this (at this point), some of which cannot be recovered from. And at the very least, there are apps and icons that won't scale properly, and there's no fix for that but to find new ones (from the horses mouth).
Things to be worked out by some real sharp devs.

I'm not totally convinced that this makes things anything beyond just smaller. I've been testing this a various resolutions and am not sure it really adds any new pixels...aren't "pixels" more hardware related? If it were just a software thing wouldn't everyone do it?

[Q] Raise the dpi

halo
i don't see so well and the Resolution in the one s is to high to me
i raise the DPI Through rom toolbox to 260
but i get some error of the system ui "Unfortunately system UI has stopped"
for example when i enter to "recent up" i got this erorr and i can't enter there....
there is a way to fix it ??
thanks

If I'm not totally wrong raising the resolution will result in smaller letters. You should lower it instead. So please try it.
And you can change letter size within settings -> display & gestures -> font size. By default it is medium, so you can change to large or extra large.
At least under accessibility there is an option named TalkBack, which will activate a spoken feedback to what you touch, choose or activate. I hope your ability to see is not that bad!

rootrider said:
At least under accessibility there is an option named TalkBack, which will activate a spoken feedback to what you touch, choose or activate. I hope your ability to see is not that bad!
Click to expand...
Click to collapse
I just checked that out.
What's with the notification about it "collecting" info? Collecting it where? And what? I didn't go any futher.....

Tomney,
I am not sure if this will actually work but if you have root you can edit your build.prop file. In that file there is a line that refers to ro.sf.lcd_density. By adjusting that number up or down you can change the dpi of the screen. Now that does not necessarily mean that all of your apps or even the Sense UI will work correctly, but it might be worth a try.
If you want to easily do this I would download the BuildProp Editor app from the market.

Haven't tried it on this phone, but at least on every sense Rom I've used for the hero changing LCD density has always messed up everything. One of the reasons I allways used aosp
Sent from my HTC One S using XDA

usrbrv8 said:
Tomney,
I am not sure if this will actually work but if you have root you can edit your build.prop file. In that file there is a line that refers to ro.sf.lcd_density. By adjusting that number up or down you can change the dpi of the screen. Now that does not necessarily mean that all of your apps or even the Sense UI will work correctly, but it might be worth a try.
If you want to easily do this I would download the BuildProp Editor app from the market.
Click to expand...
Click to collapse
as i said i did it with romtoolbox. it is the same , i raise the dpi to 260....
it makes some problems with system ui and i got some errors
i now replace the rom to miui and the dpi change doesn't Affects the system ui
dpi change can be on a rom without htc sense ui and i think even regular ice !
but..... now there is some problem with the market because Resolution Compatibility i think... there is some app i can't download .....
for now i need to come back to 240 dpi for download some apps and its Annoying
maybe if could change the Resolution to Exactly 800\480 i wouldn't get the market-app-Compatibility issue but i dont know how... maybe someone know how to do it?
my vision isn't so bad and i know the regular options aka font enlarger Etc ...
dpi change is the best choice for me .

[Q] Rooted OnePlus w/CM11s LCD Density Value

Are you able to change the value and have it applied after reboot?
Explanation:
I have an Nexus 7 (2013), Galaxy S3, & Galaxy S4, all running CM11 (I have only successfully executed this method with Cyanogen CM10 & CM11, haven't tried others).
With a rooted phone and a file explorer app; you are able to go under the root folder and changed the density value of your screen, increasing the resolution per se (think of Paranoid ROM when changing display settings "Phone", "Phablet", "Tablet").
/system/build.prop
open as text and search for variable "ro.sf.lcd_density=320"
320 was the default value on my s3, i personally prefer to change it 280. Save changes and reboot.
I AM NOT SUGGESTING OR RECOMMENDING TO DO THIS ON ANY OF YOUR DEVICES IF YOU'RE NOT FAMILIAR WITH WHAT YOU'RE CHANGING. IF YOU CHOOSE TO DO SO, IT'S AT YOUR OWN RISK! I WILL NOT BE HELD RESPONSIBLE!
So I repeat, any one been able to successfully pull this off for CM11s?

ElihuRodriguez said:
Are you able to change the value and have it applied after reboot?
Explanation:
I have an Nexus 7 (2013), Galaxy S3, & Galaxy S4, all running CM11 (I have only successfully executed this method with Cyanogen CM10 & CM11, haven't tried others).
With a rooted phone and a file explorer app; you are able to go under the root folder and changed the density value of your screen, increasing the resolution per se (think of Paranoid ROM when changing display settings "Phone", "Phablet", "Tablet").
/system/build.prop
open as text and search for variable "ro.sf.lcd_density=320"
320 was the default value on my s3, i personally prefer to change it 280. Save changes and reboot.
I AM NOT SUGGESTING OR RECOMMENDING TO DO THIS ON ANY OF YOUR DEVICES IF YOU'RE NOT FAMILIAR WITH WHAT YOU'RE CHANGING. IF YOU CHOOSE TO DO SO, IT'S AT YOUR OWN RISK! I WILL NOT BE HELD RESPONSIBLE!
So I repeat, any one been able to successfully pull this off for CM11s?
Click to expand...
Click to collapse
Yep, running stock on my OPO I was able to change it to 320 and it held through reboot.

Yep. Same succes here. I feel confortable with density set to 400 instead of stock 480 dpi.

Yes it works, I switch dpi using texdroid.https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi

[TUTORIAL] How to increase Screen Density/DPI value of any Android Device

The phones keep becoming inferior with every superior model getting launched. Some users might not want to buy a new phone just yet. You might want to get the most out of your device while it lasts. To compensate for the continously increasing screen sizes and resolutions in the newer phones, we can change the Screen Density of our devices in order to utilize our screens more efficiently.
Most manufacturers stick to the standard DPI of 240 on the large screened phones like Samsung Galaxy S II or HTC Desire HD, so it might be too big to really make efficient use of the Android device.
Still, there is hope. Just make sure that you are rooted and equipped with Root Explorer or a free app like ES File Explorer in order to access the Root owned partition of the device.
Method:
1. Open Root Explorer
2. Go to /system
3. Click on Mount RW (It shall appear aa Mount RO)
4. Look for build.prop. Long press on the file and press Open file in Editor
5. Scroll down to ro.sf.lcd_density=240
6. Change the value to anywhere between 180 and 240. The lower the value, the higher density your screen will have.
7. Click on the Menu button , and Save and Exit.
8. Reboot.
You should now have a phone with the same screen size but alot more density, slightly smaller text and more space to use applications on.
This guide can be used on all Android phone, even the smaller MDPI and LDPI phones to make your screen to appear bigger and more useful . However, you will have to tinker with the value unless you find one that suits you best.
If some applications cannot span properly to the new screen size, download Spare Parts from the market, uncheck Compatibility Mode in the options, and reboot.
Some launchers may act wierd , however most do look good with a higher density look!
Do press the Thanks button if this guide has helped!

Reserved.

I am using 160. With this value you don't have problems with play store.

Bighardy said:
I am using 160. With this value you don't have problems with play store.
Click to expand...
Click to collapse
What issues did you experience with play store before?

When I used different values between 160 and 240, i. e. 180 or 200, I had compatibility problems with play store. New program version weren't shown as update, and if I searched for apps the message Not compatible with this device appeared. With 160 no problems with unhacked play store.