Develop Bugs

LCD Density Changer

What are your thoughts on this.. Ive never used it on my epic but with all this extra screen space do you think it will work well with it?.. might actually work out well with this screen
Edit.. that was supposed to say lcd density changer
Tapatalkin' it from my Epic 3g

I am definitely planning to use lcd density changer once I get my epic. At 800x480, things will be huge.

This was the first thing I do on my Evo's, change it to 190. I can't wait to do it on this phone and find that sweet spot.

bump. has anyone tried? working / not working?

Yep. 190 or 200 works well. Doesn't break much. Dialer gets wonky, so does the Volume button on the pulldown shortcuts. I think Contacts too. But I use custom launcher, dialer, contacts, etc, so it doesn't affect me.

im running mine at 160 dialer seems to be a bit wonky but it works

ok i finally got around to installing this thing.. man i gotta say i love it so far.. if we could get the stock dialer and some other little quirks worked out this would be perfect

jok3sta said:
ok i finally got around to installing this thing.. man i gotta say i love it so far.. if we could get the stock dialer and some other little quirks worked out this would be perfect
Click to expand...
Click to collapse
I know. At native 240, this display is comically huge. It looks like a clown prop. The sad thing is, as many have already noticed, changing density/DPI is an "unnatural" thing and will always cause some apps to be deformed. A screen of this size with such a low resolution was a huge design flaw.

yah it is a shame. but not a deal breaker. but with lcd changer it just feel right.. maybe we can try to get some of the talented devs on here to work on the issues..

What about if you flash a custom dialer? Will it resize properly?
Sent from my SPH-D700 using xda premium

ive heard custom dialers work.. but i havent tried yet. in my experience, custom dialers dont change the in-call dialer though.. also the dialer isnt the only problem. the calender is messed up as well along with other little things

Tablet version of ICS running on Galaxy Nexus

So I was playing around with the build.prop, and decided to play with the LCD density. I discovered that if you bring it down, (I just cut it in half from 320 to 160, I don't know what the smallest/biggest it can be is) after rebooting Ice Cream Sandwich will look like how it does on a tablet!
I don't know if everyone already knew this or anything, but I thought it was cool and I bet that someone would be interested in making it work!
The problem is, immediately upon booting, system.ui force closes, meaning that you don't have navigation buttons anymore... I'm no developer, so I don't know why it dies, or how to fix it, but hopefully someone does, because this would be a fun ROM to try!
http://youtu.be/nx0bC-6vxMY

same thing happens if you set it to 240 dpi
try it...things won't b so tiny
Sent from my Galaxy Nexus using xda premium

mrfuzzie23 said:
same thing happens if you set it to 240 dpi
try it...things won't b so tiny
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for testing that, now my question is what's the best way to revert back to how it was? I just reflashed my ROM, but I'm sure there's gotta be a better way...

patrick848 said:
Thanks for testing that, now my question is what's the best way to revert back to how it was? I just reflashed my ROM, but I'm sure there's gotta be a better way...
Click to expand...
Click to collapse
There is an app called LCD Density Changer that I used to use on my Nook Color. It required root and idk if it works on ICS or not.

the way I did it was I ran gscript to remount /system.. which happily force closes after its done so u can leave to another app, then used total commander to fix the build.prop.. I had a copy of build.prop renamed to build.prop.old sitting in /system... on hindsight u could use a script to do this for u..
Sent from my Galaxy Nexus using XDA App

You can change it in Rom Toolbox by JRummy16

240 will run things in tablet mode. If you have errors running some apps like YouTube put in landscape mode first. Also dpi 241 works well but not many tablet apps work
Sent from my Galaxy Nexus using XDA App

IT WOULD BE GREAT TO USE IT IN TABLET MODE W/ SOFT KEYS WORKING. I HAVE BUTTON REMAPPER AND USE VOL -/+ as back/menu. BUT IM PRETTY SURE TELEPHONY AKA PHONE CALLS DONT WORK AT 160 DSI BUT! 120 DSI SHOULD HAVE WORKING CALLS IN ANDROID 4.0.2 AND 4.0.3.

Phone calls work fine at 160.
Easiest way to revert it to have two build.props:
Build.prop and build.prop160
Use root explorer to rename the file you want
I also use the softkeys for root app to get onscreen buttons
If you get a fc loop for any other dpi just use adb push build.prop /system/ to fix
Making sure you have a backed up build.prop in your adb folder.

This looks good lol hope somebody picks up on this asap!
Sent from this GN on 4GLTE!

That's pretty cool, but this thread probably doesn't belong in development as nothing has been developed.

Please don't post in the wrong topic. It pisses me off.

shenye said:
Please don't post in the wrong topic. It pisses me off.
Click to expand...
Click to collapse
Sorry, thanks for moving it.

[REQ] Modified CM9 phone.apk for custom DPI

Hi there, I'm kind of new. I've recently been modifying the dpi on our device and I can't tell you how amazing it makes the screen look. However, on cm9, any dpi lower than 190 causes the phone to crash so calls cannot be made or received.
Other phones have mods for this, however, flashing these causes all sorts of issues with service all together. Is anyone up for making one? I'm on my phone right now, but if you need a link I can post when I get home. Hope this is in the right section, thanks.
Sent from my SPH-D700 using Tapatalk 2 Beta-2

shockvaluejj said:
Hi there, I'm kind of new. I've recently been modifying the dpi on our device and I can't tell you how amazing it makes the screen look. However, on cm9, any dpi lower than 190 causes the phone to crash so calls cannot be made or received.
Other phones have mods for this, however, flashing these causes all sorts of issues with service all together. Is anyone up for making one? I'm on my phone right now, but if you need a link I can post when I get home. Hope this is in the right section, thanks.
Sent from my SPH-D700 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
cm9 seems to have problems with alot more than just the phone with anything under 182. So if you're planning on going lower than that you might be in for a headache. I agree with stuff looking better at lower densities tho. I have my cleangb rom set at 160. Aokp seems to go to lower densities without as much difficulty, and has a lot more options than cm9, is very stable, and better on battery. In fact, LCD density is an option in rom control in system settings on aokp, so there's no need for a 3rd party app to change it. Maybe you should try flashing that and playing with it for a while, see what you think. Its basically cm9, just, better. IMHO at least. There's a thread for it in the dev section if you're interested. Peace nd happy flashing.

Thank you, I'll definitely give that a try as soon as possible. Do you know if aokp can spoof the dpi so the market is still usable?
Sent from my SPH-D700 using Tapatalk 2 Beta-2

Not sure what you mean exactly, but I've never had a problem using the market on aokp, and my LCD density is set to 175. What program are you using to change the density? Sometimes the actual app can cause the problem. If your rom doesn't have the option to change density then the best two apps you can use, in my experience, are rom toolbox and blade buddy. Both have free versions that allow you to change a lot of settings. And, just to make sure we're on the same page, when you say dpi, you are reffering to LCD density, correct? Meaning the lower the number the bigger your screen appears (icons and text look smaller). Whereas the default value is 240. Just making sure we're talking about the same thing.
Sent from my SPH-D700 using xda premium

186 is my sweet spot
Sent from my MIUI V4 Epic 4G via Tapatalk 2 beta 4

Are you having any issues with the phone or market apps? Which rom are you using? I think different densities look better with different roms. For instance, IMO, miui doesn't look good with anything under 220, but on the other hand, I have cleangb set to 160 and it looks great. Although I had to use spare parts + to make the text bigger, and the stock phone app won't change density, so when you open it, the dialer only takes up a small portion of the screen. I'm looking for a decent custom dialer to fix that. Any suggestions?
Sent from my SPH-D700 using xda premium

ICS Pixel Density

Do any of the pixel density apps work once you upgrade to ICS? I read somewhere on the forum that this guy wasn't able to change his pixel density & had to stick with the stock one which is soooo big.

garyx24 said:
Do any of the pixel density apps work once you upgrade to ICS? I read somewhere on the forum that this guy wasn't able to change his pixel density & had to stick with the stock one which is soooo big.
Click to expand...
Click to collapse
Are you talking about like using ROM toolbox to change your dpi from stock 240 and make it lower like 200???
ROM toolbox will change your dpi if your rooted and tons of other stuff like app backup and font changer ect.

sinfulgray said:
Are you talking about like using ROM toolbox to change your dpi from stock 240 and make it lower like 200???
ROM toolbox will change your dpi if your rooted and tons of other stuff like app backup and font changer ect.
Click to expand...
Click to collapse
yea something like that, I use lcd resolution to change the density on my rooted gingerbread 2.3.5 but I heard someone said pixel density apps don't work with ICS when it's rooted even. Idk if it's true or not.

garyx24 said:
yea something like that, I use lcd resolution to change the density on my rooted gingerbread 2.3.5 but I heard someone said pixel density apps don't work with ICS when it's rooted even. Idk if it's true or not.
Click to expand...
Click to collapse
ROM toolbox works i have mine at 200 now and stock is 240 but ive never tried any other app cause ROM toolbox is like a 10 in 1 app

Yeah, i also use rom toolbox just make sure to follow the steps in order to get a working play store if not you won't be able to download 90% of the apps.
Sent from my SAMSUNG-SGH-T989 using xda premium

garyx24 said:
yea something like that, I use lcd resolution to change the density on my rooted gingerbread 2.3.5 but I heard someone said pixel density apps don't work with ICS when it's rooted even. Idk if it's true or not.
Click to expand...
Click to collapse
Yea lcd resolution and lcd density modder apps werent working for me on ics, they either gave me a black screen or just wouldn't boot. Rom toolbox is good to go or just by changing the dpi in the build prop too which I think is the best and cleanest way to go.

0Tolerance said:
Yea lcd resolution and lcd density modder apps werent working for me on ics, they either gave me a black screen or just wouldn't boot. Rom toolbox is good to go or just by changing the dpi in the build prop too which I think is the best and cleanest way to go.
Click to expand...
Click to collapse
k thanks

[Q] [REQ] Method of UNIVERSAL Tablet UI Mod for ICS/JB

SORRY TITILE SHOULD BE: [Q] [REQ] Method of UNIVERSAL Tablet UI Mod for ICS/JB, the forum won't let me mod that...
I don't really want to ask similar questions again... I've been looking SOOOOO hard on the internet for this, but all I got are all kinds of ParanoidAndroid ports for other devices, device- and ROM-specific mods not universally applicable and (finally) this thread Link showing a likely but very vaguely descripted method to enable tablet UI for ICS.
I know E4G has already got satisfactory ROMs for this purpose, but I have an HTC Incredible S (no separate Q&A forum for it), which hasn't got AOKP-JB (it has tablet UI included in settings) yet. It's now on CM10.
So I'm asking: how to enable tablet ui for any ICS/JB ROM? (It's OK even if it requires modding framework/services.jar/etc.)
Hope mates here can help for a bit. Thanks

Fixed for ya
XDA Moderator

kennyglass123 said:
Fixed for ya
XDA Moderator
Click to expand...
Click to collapse
Thanks sir.
Sent from HTC Incredible S @ CM10

Lower the DPI in the build.prop.
ro.lcd_density=XXX or something like that.
Sent from my SPH-L710 using Tapatalk 2

That's what I mostly saw in Google which simply doesn't work no matter how low I've changed that. Neither will other build.prop hacks work
Sent from HTC Incredible S @ CM10

AndyYan said:
That's what I mostly saw in Google which simply doesn't work no matter how low I've changed that. Neither will other build.prop hacks work
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
Hrmm....check around in the /data folder to see if there is a local.prop. That would be the only thing i could think of that would override the build.prop, but usually that has to be manually created anyways. What is the default density of CM set to on the Inc S?

zanderman112 said:
Hrmm....check around in the /data folder to see if there is a local.prop. That would be the only thing i could think of that would override the build.prop, but usually that has to be manually created anyways. What is the default density of CM set to on the Inc S?
Click to expand...
Click to collapse
1. build.prop density changes work but DOES NOT bring device into tablet, only shrinks display...
2. IncS has a default density of 240 as most WVGA phones.
3. /data/local.prop not found.
Thank you sir for replying and giving possible solutions But does the answer really goes in .prop files? I mean, in the ParanoidAndroid thread link I provided, 2nd post says for ICS some changes can be done to some .jar framework to lock the preference, but the guide doesn't tell which and exactly how... Could anyone shed light on that?
Sent from HTC Incredible S @ CM10

AndyYan said:
1. build.prop density changes work but DOES NOT bring device into tablet, only shrinks display...
2. IncS has a default density of 240 as most WVGA phones.
3. /data/local.prop not found.
Thank you sir for replying and giving possible solutions But does the answer really goes in .prop files? I mean, in the ParanoidAndroid thread link I provided, 2nd post says for ICS some changes can be done to some .jar framework to lock the preference, but the guide doesn't tell which and exactly how... Could anyone shed light on that?
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
How low have you tried setting it? Eventually, it will enter tablet mode. Try intervals of 20(make a nandroid before hand just in case) I can't remember if WVGA screens need 120, 160, or 180.. one of those should do it though. Tell ya what, I'll try on my Epic which is on CM 10.1.
At 240 is normal
At 180 its almost got a GS3 feel to it. Very spacious.
I skipped 160 and 140.
At 120 it has entered Hybrid UI.
Everything below that point( down to at least 20, which isn't usable lol) is still the Hybrid UI.
I guess that's why on JB, you have to mod the framework. Google is moving away from the traditional tablet ui.
On ICS though, the DPI change will work. I know that for sure. Lol
Sent from my SPH-L710 using Tapatalk 2

zanderman112 said:
How low have you tried setting it? Eventually, it will enter tablet mode. Try intervals of 20(make a nandroid before hand just in case) I can't remember if WVGA screens need 120, 160, or 180.. one of those should do it though. Tell ya what, I'll try on my Epic which is on CM 10.1.
At 240 is normal
At 180 its almost got a GS3 feel to it. Very spacious.
I skipped 160 and 140.
At 120 it has entered Hybrid UI.
Everything below that point( down to at least 20, which isn't usable lol) is still the Hybrid UI.
I guess that's why on JB, you have to mod the framework. Google is moving away from the traditional tablet ui.
On ICS though, the DPI change will work. I know that for sure. Lol
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Is that so? Once on my Epic at CM9 I tried a dpi as low as 120 and the SystemUI just FCs again and again. This time on IncS I had the density also changed to 120 but it enters a Nexus-7-ish phablet mode, and things have become way too small to operate on.
And BTW, the calculated tablet threshold DPI for WVGA is 128.
Damn that Google, I don't so care about Nexus 7 using the phablet UI (it should, really) but why the hell is Nexus 10 doing the same, you wanna make it a giant phone?! AND you removed tablet mode support just because of this?! How utterly childish
Sent from HTC Incredible S @ CM10

AndyYan said:
Is that so? Once on my Epic at CM9 I tried a dpi as low as 120 and the SystemUI just FCs again and again. This time on IncS I had the density also changed to 120 but it enters a Nexus-7-ish phablet mode, and things have become way too small to operate on.
And BTW, the calculated tablet threshold DPI for WVGA is 128.
Damn that Google, I don't so care about Nexus 7 using the phablet UI (it should, really) but why the hell is Nexus 10 doing the same, you wanna make it a giant phone?! AND you removed tablet mode support just because of this?! How utterly childish
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
Here is how I did it on Ainol Tablets. Smali code editing in android.policy.jar and services.jar.
I have no idea though if it is "universal" or not but it worked on multiple tablets.

fuser-invent said:
Here is how I did it on Ainol Tablets. Smali code editing in android.policy.jar and services.jar.
I have no idea though if it is "universal" or not but it worked on multiple tablets.
Click to expand...
Click to collapse
Thank you for finally supplying a legit-looking tutorial. Now, however, I'm concerned with the problem of how to transform a tablet with tablet UI to the Nexus-7-ish phablet UI. Now via build.prop hacks I'm only able to achieve phone UI and I want to know if the same method works and what modification in the parameters this needs to be altered... Thank you all again
Sent from HTC Incredible S @ CM10.1

AndyYan said:
Thank you for finally supplying a legit-looking tutorial. Now, however, I'm concerned with the problem of how to transform a tablet with tablet UI to the Nexus-7-ish phablet UI. Now via build.prop hacks I'm only able to achieve phone UI and I want to know if the same method works and what modification in the parameters this needs to be altered... Thank you all again
Sent from HTC Incredible S @ CM10.1
Click to expand...
Click to collapse
The reverse method should work. Just look for the PhabletUI code and make sure that the relevant sections in the guide I linked to in my thread point the device towards PhabletUI instead. You could also do the same for PhoneUI if you wanted.
If at any point you want to convert the new JB 4.2 UI back to Tablet UI, I used the Tabletizer Alpha app here. When it was done, I did have to move the update.zip to my computer and repackage/resign it for my tablet as well as edit the update-script but the jar files worked.

fuser-invent said:
The reverse method should work. Just look for the PhabletUI code and make sure that the relevant sections in the guide I linked to in my thread point the device towards PhabletUI instead. You could also do the same for PhoneUI if you wanted.
If at any point you want to convert the new JB 4.2 UI back to Tablet UI, I used the Tabletizer Alpha app here. When it was done, I did have to move the update.zip to my computer and repackage/resign it for my tablet as well as edit the update-script but the jar files worked.
Click to expand...
Click to collapse
Great thanks for the tip!
Sent from HTC Incredible S @ PACman v20