yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] magicdanw:
I'm trying to figure out how to make those other applications also use the full screen when at a different resolution. I tried the method here

http://xdaforums.com/showthread.php?t=739647

to run a script that rewrites the /system.prop file, and it didn't fix anything, so either that is not where the applications are getting the property from, or we need to rewrite the file earlier in the boot process. :(
[Captivate Android Development] nbs11:
Are you sure those apps are graphically able to scale? Maybe touchwiz does not take scaling into account (at least with native apps) because the screens are all 4 inches.
[Captivate Android Development] magicdanw:
Other applications fail to scale as well. On my Captivate, with the DPI set at 200, both Root Explorer and MailDroid display at a reduced size.

Perhaps, though, they only work at certain expected values? I'll try 160 and report back.

Update: No luck at 160 either. It's strange, because I've read that on other phones changing the build.prop file is sufficient. However, the information I found did tend to focus around Donut - maybe Eclair is doing something different?
[Captivate Android Development] Clienterror:
Yea it's weird. Games scale fine and like 90% of the apps I've tried to ok, it just seems root explorer, linpack, and a hand full of others don't want to scale.
[Captivate Android Development] socket84:
The right one for GALAXY S is 180.
[Captivate Android Development] Clienterror:
That's what I'm running, its a good balance IMO.
[Captivate Android Development] olieebur:
Alright. I basically edited the numbers right on my phone straight on root explorer and rebooted and they settings seemed to have stuck. Ran twlauncher and it worked fine. The app drawer on tw however did not scale right (still showed a 4x4 grid of icons).

Overall I am loving this resolution. 200 is perfect for me. For some reason I am actually more accurate typing on this keyboard lol

Sent from my GT-I9000
[Captivate Android Development] appelflap:
LOL, isn't anyone in this thread using the TouchWizard shell anymore ? :D Because if you use the TWLauncher with this setting you get a FC immediately at startup . Only way to repair this is to flash the firmware again (or make sure you enable the debug mode so you can use adb after restarting the device with the new settings)

Anyway, gonna try this again with an alternative launcher because it really looks very nice. Great find.

BTW I looked at the layout files of rootexplorer and it should work. There's no fixed resolution definition or something like that.
[Captivate Android Development] jamezelle:
this works on any HDPI device
[Captivate Android Development] smeltn:
This looks really nice. I wanna try it on my Captivate
[Captivate Android Development] smeltn:
Whats the FM radio app you have?
[Captivate Android Development] pentace:
Im using an N1 but i went to 200 and it works fine, I also swapped my G1 to 150 and it works fine so no it does not need to be proportional, but they lower the number the more processing power it seems to take for graphics. Also if an app is not made to support multiple screen sizes, they show up tiny.

As far as restoring on boot, that im not sure about as it seems the Samsung phone works differently than my HTC devices in where i need to reboot for the settings to take effect, and on Samsungs they seem to take effect instantly
[Captivate Android Development] bluefisch200:
I have only problems with the phone app at 200 (International SGS), someone knows how to replace the app with another one?
[Captivate Android Development] BenF1:
What effective resolution does this make it? Or will it be the same but smaller? :S
[Captivate Android Development] bluefisch200:
You do not change the resolution, it is like other dpi settings on your PC...
[Captivate Android Development] xan:
Kindof stock.. Came with JM5 AFAIK

Reporting problems with:

- Phone app

- Music Player

- Root explorer

- Robo defence game

I came back to stock setting.
[Captivate Android Development] tongsitat:
Error Dialog blocking screen

Help!.. I adjusted the settings and rebooted, and now I get this error on startup and it won't force close and blocking everything in the background. "The application TwLauncher (process com.sec.android.app.twlauncher) has stopped. Please try again. dumpstate_app_201008220810_com_sec_android_app_twlauncher.log has been saved. Use *#9900# to copy out log."

I cannot click anything on home screen because this dialog keeps pop-up no mater how I click "Force Close".
[Captivate Android Development] smartsreenath:
wow nice job....great work......is this possible another devices like htc legend:):)

Uploaded with ImageShack.us
[Captivate Android Development] appelflap:
Yeah, I warned for this in earlier... Maybe you have the usb debugging enabled? If so try to connect it to the computer and ask a adb wizard how to copy a build.prop to the system dir. (and ask him/her for that build.prop file too :) )

If you don't like all the hassle. Just reflash the firmware.
[Captivate Android Development] olieebur:
Twlauncher wasn't force closing on me but I wouldn't use it anyway. The whole homescreen isn't scaled right except the dock.

Sent from my GT-I9000
[Captivate Android Development] wuffa:
SGS:

-Default lock screen not scaling all the way to the bottom

-Dialer, Calc, Music, Calendar, various apps not scaling correctly

-Launcher pro dock overlapping icon names above

Changed took "user:write" permission off build.prop and it seems to persist after a reboot. Sticking with 180 as the benefits by far outweigh the above :)
[Captivate Android Development] AJerman:
Absolutely, it works on all Android devices. I've been using this for a while on the Captivate, but I don't go too low because some things do get messed up. If you just do a small amount, 200 or even 220, it makes things pleasantly better without throwing anything off too far.
[Captivate Android Development] priorit:
Happened to me, and it's actually possible to get back to the original without flashing: I connected to my Galaxy S using adb shell and then requested superuser rights (su).

If you are lucky you checked the "remember" box earlier and you have a shell right away. If not, one has to click on the allow-button. Since there is the "FC" dialog in front this is not easy. However, after clicking on "Force Close" there seems to be a small window where the SuperUser application can be clicked. In my case I was able to do this right after a reboot. You might need to play a little bit, but it is possible.

From then on I simply used vi to change the file (but you can also adb push a new version to the sdcard and then simply copy it from there to the /system folder).
[Captivate Android Development] xan:
I guess we should tinker with these:

http://developer.android.com/guide/practices/screens_support.html#attrs

However, Ir no dev and dont know it can be changed in .apk or .jar
[Captivate Android Development] daktah:
did it on my evo and it works and looks great aside from the rendering in 240 mode glitch which looks weird but i can deal with it. cant wait for a fix for it.
[Captivate Android Development] appelflap:
I posted a little app to play with the Density Setting here

(OMG I wish they hadn't pull all the Galaxy S variant forums apart... oh well)
[Captivate Android Development] lpsi2000:
I just tried this app and when I rebooted my device I can't see the screen. Can some one post their Captivate Original Build.prop file.

Thanks
[Captivate Android Development] amwbt:
I used this app and now my screen stays black right from boot. I didn't backup my file, like a moron. Can someone post the steps to fix this from adb shell through USB please? I don't want to have to flash again.
[Captivate Android Development] jdsemler:
A good build.prop is attached. Here's how I would approach your situation.

C:\android-sdk-windows\tools> adb push build.prop /sdcard

C:\android-sdk-windows\tools> adb shell

$ su

# rm /system/build.prop

# mv /sdcard/build.prop /system/build.prop

# exit

$ exit

C:\android-sdk-windows\tools> adb reboot
[Captivate Android Development] F_L_Abs:
Used the app and had the same result... Black Screen

I don't think I had USB Debugging on =S

Is it at all possible to have the original file through an update.zip for recovery mode?

-Edit-

I just thought about it and I don't think I can put the file into my phone anyway! Lol

Crap I guess I'll have to reflash
[Captivate Android Development] jdsemler:
@amwbt: If the apk does not work out for you, look for Notepad++. It does a great job at editing the file cleanly and keeping everything formatted properly.
[Captivate Android Development] lpsi2000:
This won't work for me because su is given segmentation fault. That sucks, it looks like I am going have to re-flash
[Captivate Android Development] lpsi2000:
Recovered from the App issue

I recovered from the problem caused using the app by doing the following:

http://xdaforums.com/showpost.php?p=7796276&postcount=29
[Captivate Android Development] Bhonka:
Not sure if this is related but my auto brightness feature is missing.
[Captivate Android Development] :
True who ever decided to put all the SGS device on separate forums, simply dint do its research, all 2 GSM SGS are the exact same device except for few kernel differences, and the same apply's to its CDMA brothers, why did the user experience admin decided to put five different SGS devices forums is beyond me...i already pm xda's admin, he said he was going to have a look at it with hes co-admins.
[Captivate Android Development] Brantyr:
Just did this on my Galaxy S (again, rage at the unnecessary forum splitting), the general effect is very nice but there's more than a little weirdness with a lot of UI elements. I think it's going to take a significant amount of work with various graphics and XML files but would be well worth it to most power users.

If the Dell Streak ever gets a proper update the APKs from that would probably go a long way to making things look better but only at 160 which may be a little high (some fonts are getting eye-hurtingly small in some places but 200 should hopefully be the sweet spot).
[Captivate Android Development] AJerman:
200 seems like the sweet spot to me. I wish there was some kind of underlying code to force apps to stretch when they aren't coded properly to allow them to. Most apps are fine, but a few get thrown off. Most of the time you can still use them just fine too, but I have noticed a few that it messes up the touch locations with too.
[Captivate Android Development] appelflap:
Partial solution for the scaling prob.

Ahhh, someone found a fix for the scaling problem. Download an app called "spare parts" from the market and turn off compatibility mode. It works on almost any app. Almost, there are still some apps that doesn't scale right, like for example the dialer.

BTW Sorry for spoiling the party going on here, by posting my app. :D Anyway, if someone is willing to participate in a test please PM me or leave a message here. I think its very worthwhile to develop the app further. Eventually I can add a feature to turn of the compatibility mode, and if I can solve the dialer issue, I can add that too.
[Captivate Android Development] sunriu:
It might be a stupid but isnt it better to increase pixel density than reducing it?
[Captivate Android Development] lpsi2000:
I was on the users who had the issue with your app and I don't think you spoiled anything. Sh*T happens and it is good idea to have an application that would make the changes for you. Keep your head up and keep the application moving forward.

I am not mad at you, just a little dissappointed:p lol
[Captivate Android Development] solidkundi:
working amazing on my Vibrant!

EDIT: @180 Density .... heres my review

everything is working as it should...one good thing is that u can see more of ur live wallpaper but ur still

but..I'm still only able to fit 4 icons across on my Launcher Pro.. and same goes to the widget....

also widgets are looking messed up for the most part... Pure Calendar's "days of the week" go beyond the widget.. .. Fancy Widget seems to work okay..

dialer..apps..games so far so good..

maybe the "spare parts" might work... i'll give that a try and post back
[Captivate Android Development] jdsemler:
It depends on what is meant by pixel density.

The way Google describes it is relative to the size of the device. A 800x480 5" device has a lower pixel density than a 800x480 4" device. In this case, think of this as dots per square inch. The dots are the same quantity wise, but the dots are either more compacted or more spread apart.

This is why raising the pixel density makes things bigger, because a more dense display means a smaller display.
[Captivate Android Development] Clienterror:
To get more icons across you need to use adw launcher and tell it to make more rows/columns. The system dosent know it can fit more on the screen it's just reading the stock settings which says 4 across.
[Captivate Android Development] jdsemler:
Spare Parts really did the trick for me. I'm at 160 and things look much better. Root Explorer, Robo Defense, and most everything else is full screen again. The status bar is a lot better, but it still uglies itself up. I have found that if you rotate from landscape back to portrait (or vice versa), it forces it to redraw and looks good again.
[Captivate Android Development] solidkundi:
oh okay...thanks for the info but i went back to 240 cuz i had touch problems with some of the apps like "Aldiko" and i need that to read my books... so yeah

and also .. rite after i changed back to 240.. my phone nearly froze every other minute... but its okay now.. that scared me!
[Captivate Android Development] appelflap:
In case someone is interested, I updated the app I wrote earlier. I now did choose the "eris market fix" approach. If that app works for you, then my app will work without any problems.
[Captivate Android Development] appelflap:
:D then here is a fix for ya.
[Captivate Android Development] Brantyr:
Just set mine to 200, none of the weirdness that 160 caused and everything is about the right size, also works better with my 5 row ADW desktop (before some widgets would get cropped if you left them at their default size, now they don't).

Also, the setting presisted after a reboot on it's own (at least 160 did I haven't rebooted since putting on 200), wtf?
[Captivate Android Development] Bjd223:
You can't change the physical pixel density of the display obviously. All this does it tells the OS how large or small text and other elements like buttons, etc. should be rendered. The only other way to increase the size of elements is to reduce resolution, but this will cause the image to be degraded (if it is scaled to 100% of the screen).

If you raise the density too high or low, than what the display was designed for, then elements will be rendered larger or smaller than the designer had in mind. This does not change the physical amount of pixels displayed or the quality of the image, thats what resolution changes.

So for example if the pixel density is 96dpi (stock) and you change it to 120dpi the resolution is not changed but all the elements are scaled to be about 20% larger than normal. The quality is the same they are just larger.
[Captivate Android Development] iphonekillers:
Nice brah all looks godd feel good thnks to that app settings at 215 gonna make ite 200

Thnks
[Captivate Android Development] sportedwood:
Just did this at 200. Perfect! Thanks for posting.
[Captivate Android Development] xan:
Why everybody is so overly excited?

Am I missing sth?

Most of apps dont even scale properly!

Unless they do, its useless. For me.
[Captivate Android Development] jdsemler:
The apps I have that were not scaling were fixed by installing Spare Parts from the android market then disabling compatibility mode.
[Captivate Android Development] dc41:
All apps I've tested are working fine for me. It's the widgets that can't seen to adapt to the new density. Weather Bug elite is a perfect example. The semi transparent background it uses to separate days starts to overlap and looks awful. In fact most widgets that are bigger than 1x1 seem to have problems.
[Captivate Android Development] sportedwood:
using spare parts to disable compatibility mode everythings great for me, plus using 5 icon on launcher pro makes widgets fit right.
[Captivate Android Development] ranova:
http://www.appbrain.com/app/com.beansoft.lcd_density_changer

this app works great, try it out!

Has built in boot monitor mode to make sure what you set is safe after reboot, ability to disable compatibility mode, etc

edit: saw that it was posted for free on the XDA forums on the OP - make sure to donate to him!
[Captivate Android Development] FMXP:
Does this do anything useful on Droid X?
[Captivate Android Development] Clienterror:
I'll take a shot in the dark here....it does the same thing as the captivate?
[Captivate Android Development] glio1337:
I've got to say I'm impressed. I would have never even thought of doing this to my phone.
[Captivate Android Development] gotfolk:
Not sure if this was posted but u can use root explorer to edit the file right where it sits. Just click the mount button at the top and then go into edit and edit away and save it and when u do root will make a backup.

Def loving this great find!!
[Captivate Android Development] ranova:
changing density to 200 causes the weather effects of beautiful widgets to stop working. anyone know how to fix this?
[Captivate Android Development] Shuggins:
SetCPU force closes on my phone now. Can anyone confirm this problem. Not sure if its something else causing it. I have spare parts and compatibility disabled.
[Captivate Android Development] dalingrin:
Oddly, I found 209 to be the best lcd density for my Captivate. 210 lead to ugly display errors in ADW launcher and other applications but 209 seems to fix it.
[Captivate Android Development] norpan111:
How can i find root/system build.prop?`i edited build.prop from inside android with Astro, but now i cant find that folder again :( its so sad
[Captivate Android Development] nammyczc:
use program called lcd density changer
[Captivate Android Development] bassahaulic:
I've been running 200 and it seemed to cause a lag of some sort.

180 seems to fix that lag. :)
[Captivate Android Development] slider2828:
I am currently using 200 and it looks the best.... I think 210 might fill the gaps better, but now I have waaayyyy more room on my screen. This is awesome!
[Captivate Android Development] lpsi2000:
I was running Froyo on my HD2 and was using the 180 and it was pretty nice. So I thought 4.3 vs 4.0 should not be too much of a big deal. But 180 on the captivate was a little too small. I have recently tried 185 and it seems to be comparable to to HD2. 200 is definitely the sweet spot, but 185 seems to be doing it for me.
[Captivate Android Development] poulosjr:
will this work for the Fascinate or are there different codes in the Fascinate?
[Captivate Android Development] jdsemler:
It works on pretty much all phones. It is a standard setting.
[Captivate Android Development] poulosjr:
has anyone noticed when you go down to 160 the touch on the keyboard freezes??
[Captivate Android Development] smeltn:
Same problem here. Also it looks horrible because it centers itself to the left side of the screen and you can not adjust it to center in the middle of the screen which sucks..

Guess I need to find a new weather widget.. BLEH
[Captivate Android Development] landwomble:
I'm using this on the Desire. It's great at 200. On my last ROM (AuraxSense 7.6.1) I've noticed that despite build.prop being correctly set at 200, it doesn't persist after a reboot. I can use LCD Density app plus a hot restart to get it set to 200, but basically the ROM doesn't seem to be reading the setting out of build.prop.

Anyone seen this or suggest a fix as it's a bit annoying having to reset after each reboot...
[Captivate Android Development] killer23d:
I am using an application called Brightness by Curvefish. I have the brightness on 0.
[Captivate Android Development] slider2828:
Just a word to everyone, Skype for Android crashes if you change the LCD Density. Its basically usless and FC's if you change the density. Sucks!!! I love LCD Density changes.

Also doesn't seem to stick on Froyo...
[Captivate Android Development] chewybang:
LCD Density at 160 on Droid X

NEVERMIND! I'm in the wrong forum. I'll post it in the correct one... unless anyone here knows the issue :P

I have a rooted Droid X, OTA 2.2, no themes, using ADW Launcher.

I changed the LCD density to 160 on the build.prop file and I love it; however, it's causing this glitch on my notifications bar:

(http)i22.photobucket.com/albums/b328/chewybang/snap20101021_131858.png

(can't embed the picture because I'm a new member. Boo!)

The notification bar is transparent (I don't mind that glitch as much but would like to know why) and the notifications are actually still displaying as if they were at 240 density. I have Spare Parts installed and it fixes most of my programs when I have compatibility mode set to "off" but it doesn't fix this. If I got to 180 density it works properly but I rather find the reason why this is not stretching correctly.

Anyone have any ideas? I can't be the only one with this issue, right?
[Captivate Android Development] zeus_chingon:
I'm using a Nexus One. I find that 200 makes the street name on the Maps too small for reading, 201 solved the problem. I just wish there were a modded dialer that will scale the dialpad back to normal.
[Captivate Android Development] eclypse3demons:
But aren't they upping the screen res in 3.0 to 1280x720 for 4" and larger screens anyway?
[Captivate Android Development] psychoace:
All minimum requirements that have been posted so far are bogus
[Captivate Android Development] usmcdvldg:
I've got my HD2leo at 180 and loving it. Skype works fine also :)
[Captivate Android Development] PCDEC:
Fixed the problem. Thanks
[Captivate Android Development] zerojay:
Skype works fine with a different LCD density. I'm using 200 and Skype runs just fine. And I'm running Froyo.
[Captivate Android Development] barnesk9:
I've noticed a lot of errors and force closes when you use anything less than 180 for the density
[Captivate Android Development] GeoMandell:
Anyone have any leads on a manual fix for certain apps? My phone APK window draws with correct proportions, but not the buttons. It's only a slight OCD-ish annoyance, but it'd be nice to figure out how to get them back to full screen.

Uploaded with ImageShack.us

Would editing the manifest settings for "anydensity" work if the app wasn't programmed for it in the first place?
[Captivate Android Development] velizet:
Hi,

I cannot find the build.prop for editing after I pull it using your syntax. It may not be pulling of course, but there is also no error message.

Where does adb sdk puts the pulled file?
[Captivate Android Development] gemuse:
adb pull puts the file in the directory adb is inside... so if adb is inside of your android sdk folder, than there will the files go, also. Happy .prop'ing!
[Captivate Android Development] KAASHP:
The lcd dencity 167 works better on HD2 i tested it on many roms it works well with many builds but not working on miui

---------- Post added at 07:16 PM ---------- Previous post was at 07:06 PM ----------

Just edit it with notepad++ or other text editor and change the dpi and save as it is do not change file type hope it works well
[Captivate Android Development] melbourne408:
183 is perfect for my cappy

Sent From My Swaggin 1.6 Son Of A Glitch
[Captivate Android Development] bmunday:
what's the difference between what you are attempting to accomplish and the use of lcd density changer? does density changer not stick an Gingerbread?
[EVO 4G Q&A, Help & Troubleshooting] beastmods:
i need the stock ruu for 1.47 and it is downloading way to slow from htc

anyone have a mirror?

thanks
[About XDA developers] mingkee:
HTC Vanguard (aka T-Mobile US G2) will be released later next month. Will xda-developers open up forums for this phone?
[About XDA developers] svetius:
Yes, coming soon!