Database Info

Change LCD densitiy and still download everything in Market?

Hi all.
I have a Samsung Galaxy S2 (I9100) mobile. After using a CM rom and changed the LCD density to around 200 (standard is 240) - I can't imagine me going back to the standard density, it is just way to big.
However many apps and games in Market can't be downloaded and installed because of incompatibility. It is a real pain to default the density, clear cache on Market, reboot, just to install something from Market.
Isn't there a better way? A hacked Market that doesn't check for LCD density?
How about if I changed build.prop model to a mobile model that natively has 200 LCD density? Then Market wouldn't care, right?
Anyone know a model that I could try?
Best regards

slkdk said:
Hi all.
I have a Samsung Galaxy S2 (I9100) mobile. After using a CM rom and changed the LCD density to around 200 (standard is 240) - I can't imagine me going back to the standard density, it is just way to big.
However many apps and games in Market can't be downloaded and installed because of incompatibility. It is a real pain to default the density, clear cache on Market, reboot, just to install something from Market.
Isn't there a better way? A hacked Market that doesn't check for LCD density?
How about if I changed build.prop model to a mobile model that natively has 200 LCD density? Then Market wouldn't care, right?
Anyone know a model that I could try?
Best regards
Click to expand...
Click to collapse
It all depends on how the app developers limitations for screen size. There is no way around it at the moment

[Q] Higher screen resolution?

So is there, or will there, be a way to artificially increase the screen resolution for the Skyrocket (much like this)?
I just moved from the Atrix and the lower screen resolution is killing me with the 4.5" screen. I feel like I'm using an old persons phone with the ginormous buttons and font, plus I hate not being able to fit as much information onto the screen. I'm considering moving to the Atrix 2 just for the resolution issue

Only thing I know of is the app LCD Density Changer from the market. Used it back on my Captivate. Not sure how well it works with the sr, but it was fantastic on my Captivate.
Sent from my SAMSUNG-SGH-I727 using xda premium

First thats hillarious. The atrix/atrix 2 are childs toys compared to the skyrocket. But there is an app called lcd density changer on the market. It requires root. , and if you change the settings apps may show up as unsupported in the market. So you would need to change it back to stock when on the android market.

I know what you mean OP. came from the atrix as well. u can use LCD density changer. along with the market problems (some updates wont even show up until you revert it back)
the touchwiz and its dialer will end up quite wonky as well as they don't adjust to the new resolution well. your option there will be to use a different launcher app/ dialer app.

Well then this solved all my problems! I set it to 200 DPI (instead of the default 240 DPI) and it looks so, so much better.
So far no issues except trying to download apps (I think updating works fine though). Anyone use this regularly and find any specific issues, whether it be with certain applications or whatnot?
Thanks again!

even though i dont use density changer i just go edit the build.prop and change it there.
i have no issues with density less the market stuff, and of course it looks like **** on TW. i have to use another launcher to make it look better. i hate the dead space left on TW when you lower the density.
i leave mine at 210.

Has anyone successfully changed DPI?

I just tried changing DPI, and while it worked, it killed everything in the process.
Apps are missing from the market.
Touchwiz is not at all adjusting (On SKY ICS)
Dialer also didn't feel like adjusting
Everything else is looking good. What was your solution? Finding a different launcher?

http://forum.xda-developers.com/showthread.php?t=1639213
You'll have to get a tweaked version or modify it yourself (LCD Modder), with a non supported display google play will not display certain apps that dont support it.

I use apex launcher and GO contacts. No issues with DPI. You can use LCD Density Modder Pro to fix the play store. I do not recommend actually changing DPI with it as it gave me a boot loop and screwed up my phone forcing me to do a restore. This may be an isolated incident.
Sent from my SGH-I727 using Tapatalk 2

freshjr said:
I just tried changing DPI, and while it worked, it killed everything in the process.
Apps are missing from the market.
Touchwiz is not at all adjusting (On SKY ICS)
Dialer also didn't feel like adjusting
Everything else is looking good. What was your solution? Finding a different launcher?
Click to expand...
Click to collapse
Apps missing from market: This is because you changed DPI. You have two options:
Download LCD Density Modder Pro and use "Fix Market Compatibility Issues"
Use the fix located here: http://forum.xda-developers.com/showthread.php?t=1639213
Touchwiz not adjusting: Touchwiz doesn't do well with a modded DPI. I'd use a different launcher such as Apex, GO Launcher, ADW Ex, etc.
Dialer not adjusting: Stock dialer will not adjust. Try exDialer or Dialer One
I personally run my DPI at 206 and have not had any issues with bootloops. For our device, I wouldn't try running anything lower than 190.
Hit "Thanks" if this helps
Edit: NOTE! Don't use LCD Density Modder Pro to change the DPI, just to fix the Market. It doesn't do well with changing the DPI on the Skyrocket.

deezhemi said:
Apps missing from market: This is because you changed DPI. You have two options:
Download LCD Density Modder Pro and use "Fix Market Compatibility Issues"
Use the fix located here: http://forum.xda-developers.com/showthread.php?t=1639213
Touchwiz not adjusting: Touchwiz doesn't do well with a modded DPI. I'd use a different launcher such as Apex, GO Launcher, ADW Ex, etc.
Dialer not adjusting: Stock dialer will not adjust. Try exDialer or Dialer One
I personally run my DPI at 206 and have not had any issues with bootloops. For our device, I wouldn't try running anything lower than 190.
Hit "Thanks" if this helps
Edit: NOTE! Don't use LCD Density Modder Pro to change the DPI, just to fix the Market. It doesn't do well with changing the DPI on the Skyrocket.
Click to expand...
Click to collapse
Any reason 206 vs 200? Prolly not much of a difference but still curious. Also guess that confirms lcd Modder Pro issue I had is not isolated.
Sent from my SGH-I727 using Tapatalk 2

lnfound said:
Any reason 206 vs 200? Prolly not much of a difference but still curious. Also guess that confirms lcd Modder Pro issue I had is not isolated.
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
206 is the native density according to the specs (so I've heard, can't remember where I read it).
That said, I have mine at 206 as well and don't have any issues. I switched to exDialer for the phone.
Only issue I have is with Mort Player... it installed on stock, and is still installed, but the market no longer sees it on the phone (still says it's compatible from the web, though), so I can't upgrade it... Bah!

On the fly screen DPI switching!

Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)

omniphil said:
Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)
Click to expand...
Click to collapse
Yeah, it's great if you decide to stay stock as you don't have to do much to change the DPI. You can change the DPI also without rooting by opening a command prompt in adb and running a command.

omniphil said:
Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)
Click to expand...
Click to collapse
Is this on the new updated roms? Because if can not find this setting on my stock 702 rom version?

Benjiro said:
Is this on the new updated roms? Because if can not find this setting on my stock 702 rom version?
Click to expand...
Click to collapse
I'm on a 703 running B108.
Settings -> Apps -> App Layout
That's what I have...

omniphil said:
I'm on a 703 running B108.
Settings -> Apps -> App Layout
That's what I have...
Click to expand...
Click to collapse
That explains that ... My 702 is still on B103 ... No official updates have come yet for the internal updater.

the only problem though is that the Microsoft Office apps such as Word does not go to tablet mode despite it being set to reducing mode but whenever I tweak the dpi to 320 via adb, it does show in tablet mode but some app icons and task manager are a bit messed up. Other apps such as Facebook or Youtube does seem to display on tablet orientation when in reducing mode.

mcdhol_24 said:
the only problem though is that the Microsoft Office apps such as Word does not go to tablet mode despite it being set to reducing mode but whenever I tweak the dpi to 320 via adb, it does show in tablet mode but some app icons and task manager are a bit messed up. Other apps such as Facebook or Youtube does seem to display on tablet orientation when in reducing mode.
Click to expand...
Click to collapse
I think that has to do with teh odd 1920x1200 rez. If it were 1920x1080 then it probably would detect phone mode/tablet mode correctly

Flash rom KangVIP, you can adjust DPI switching to 400, 380,360,340,320 dpi
http://cn.club.vmall.com/thread-6033530-1-1.html

eennap said:
Flash rom KangVIP, you can adjust DPI switching to 400, 380,360,340,320 dpi
http://cn.club.vmall.com/thread-6033530-1-1.html
Click to expand...
Click to collapse
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.

mcdhol_24 said:
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.
Click to expand...
Click to collapse
UI will be normal same as original B109 rom but font in app will be smaller.

mcdhol_24 said:
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.
Click to expand...
Click to collapse
If you use Nova Launcher, that fixes the icon problem.

For the unlucky ones with 702L. I found a possible fix (still testing) to set the dpi to 320 without issues in SwiftKey being huge for example. Need to be ROOTED. So this is what I did.
1. Edit the build prop and add/change both " qemu.sf.lcd_density=320 " and " ro.sf.lcd_density=320 "
2. Use terminal emulator with
Su
Wm density 320
Reboot.
Now Wm density should show one value not 2 and SwiftKey should work as well.
Cheers.

Nice. Been looking for the SwiftKey fix. So, for this fix to be working do you need to get it rooted? Cheers
On 2nd thought, this SwiftKey problem doesn't exist on other keyboard apps like fleksy, googles own and go keyboard.

Yes you have to be rooted for that. But being rooted has of course a lot of other advantages and is easy to do once the bootloader is unlocked (I used the paid option from the root guide and I was rooted within half an hour).
I tried the other keyboards as well, seems SwiftKey uses other parts of build.prop to get dpi.
Hope I could help.

Swipe screen in app fails

I don't know how to explained this but I hink it has something to do with screen red, DPI and poor programming. I can't send you link to app as you need logon to membership. The app works on other phones. It has a swipe to turn page function. But instead of turning the page it appears as though a second layer is formed and I can move the layer around on top of the back layer. But it will not swipe to next page because of it. Are there any thought which could cause this anomoly I tried messing with DPI and screen size using app settings closed module but have had no luck.

for more information on this as i have been mesisng with it more and more. I am using RR marshmallow and have set my display to 480dpi because i like small and compact. this is deffinately what is causing the issue. if i go back to the default setting of RR which is 560dpi, the app works as expected. but when i go to 480dpi, the app fails and gives this anamoly. so i tried to adjust the dpi for the app using app settings xposed module to 560. however this does not work. i am curious is there also a screen resolution i should set for the 560 dpi?

1) on another custom ROM, some people had trouble with Google Maps by trying to go too small DPI. Some apps just don't like it.
2) Stock (factory) DPI for the Quark is actually 640 DPI.
@baybutcher27 chooses to make it smaller 560 DPI in Resurrection Remix. It's his choice, since he's the dev.
And you are going even smaller? 480 DPI. You must have good eyes.
Screen resolution is 1440p.

ChazzMatt said:
1) on another custom ROM, some people had trouble with Google Maps by trying to go too small DPI. Some apps just don't like it.
2) Stock (factory) DPI for the Quark is actually 640 DPI.
@baybutcher27 chooses to make it smaller 560 DPI in Resurrection Remix. It's his choice, since he's the dev.
And you are going even smaller? 480 DPI. You must have good eyes.
Screen resolution is 1440p.
Click to expand...
Click to collapse
both hose statements are known conditions. conditions i am ok with. my question is really why doesn't app settings work to correct the change in dpi. or is there a known solution to correct the dpi issue since the app itself does not like 480dpi, nor does it like app settings trying to correct it to 560 dpi.

johnbravado said:
since the app itself does not like 480dpi, nor does it like app settings trying to correct it to 560 dpi.
Click to expand...
Click to collapse
OK. Let's try something. In Resurrection Remix, @baybutcher27 does some coding stuff to make 560 DPI be the "default" accepted by apps when REALLY it's supposed to be 640 DPI.
Maybe this one app is immune and is still looking for 640 DPI? So, just for fun, change the DPI for your phone to 640 DPI -- the factory stock value -- and see if the app works then.
I'm not saying to keep that DPI, I'm just curious if we can make the app work correctly under any circumstances.
If it works with 640 DPI, then we know the issue is somehow the app is still seeing what the REAL default DPI is supposed to be. You can then work with @baybutcher27 to fix the problem.
If it doesn't even work even with 640 DPI, then I have no idea.

ChazzMatt said:
OK. Let's try something. In Resurrection Remix, @baybutcher27 does some coding stuff to make 560 DPI be the "default" accepted by apps when REALLY it's supposed to be 640 DPI.
Maybe this one app is immune and is still looking for 640 DPI? So, just for fun, change the DPI for your phone to 640 DPI -- the factory stock value -- and see if the app works then.
I'm not saying to keep that DPI, I'm just curious if we can make the app work correctly under any circumstances.
If it works with 640 DPI, then we know the issue is somehow the app is still seeing what the REAL default DPI is supposed to be. You can then work with @baybutcher27 to fix the problem.
If it doesn't even work even with 640 DPI, then I have no idea.
Click to expand...
Click to collapse
Thanks for the assistance i turned the appsettings xposed module off and reran it at 640dpi, stock moto dpi setting and the result was, success. i ran the system at the stock RR default dpi at 560dpi and the result was, success. At 480dpi failure. this is all without using the app settings xposed module to adjust the dpi on a per app basis. strictly letting the phone do what the phone does at that dpi setting. there is something about the 480 dpi.

Yeah, similar to that Google Maps incident. It wouldn't work at a specific DPI but go up a few and it worked OK.
Experiment and see the minimum acceptable DPI for that app to not complain?
First, try increments of 10 -- 490, 500, 510, 520... Then, back down to find the exact minimum DPI. Might be some strange number like 508.