Database Develop

Gem Miner not working after density change

Hey,
I really like the Gem Miner: Dig Deeper game but after changing the lcd density it's not working anymore.
My default density was 240 and i wanted to try a smaller one so i picked 220. But i noticed the game wasn't working anymore. I get a white screen with 1 brown block. So i changed it back to 240 but the game is still fckd.
Can someone please help me, i really like this game
I tried reinstalling the game and remove all app data stuff.

Nobody?

Damnit, i really want to play this game xD
I'll try to reinstall my ROM then and hope this will fix it.

hey, I had the exact same problem with gem miner, figured out it was the density issue, but you don't have to wipe or reinstall, you just need to enable compatibility mode in the density changer app. If the one you're using doesn't have this in options then get 'LCD Density Changer', has a little red screen icon, go into settings and check the compatibility mode check box and reboot, game should work perfectly now ;->
note: you can still have a custom density and the game will work with compatibility mode.

LCD DENSITY screen size

Well..i need to learn something from the devs..!
i like to have my lcd density at 180-190 instead of original 240!
so the question is that if can someone make some fixes about this beacuse when you change the lcd density some games are not fitted well on screen also the dialpad too..and the keyboard become so small...!
its a little request if that can be fixed..or teach me how to make it work!
HD2 at lcd density 167 had original size keyboard,right oriented dialpad on screen..and all games was fitted well on screen!
thank you all guys!
P.S if the thread is not in the right place please moderators remove this elsewhere!!
(Example...try playing FAST AND FURIOUS 5 with 180 lcd density and see the screen size)

Hi, what you do mean by density? Do you mean resolution? Or the threshold when you press the screen???
Sent from my LG-P990 using XDA Premium App

xxdoggyxx said:
Hi, what you do mean by density? Do you mean resolution? Or the threshold when you press the screen???
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
hi there..i mean resolution!
you can change it on system/build.prop and change the line where it says lcd density:240 and set on 240 whatever you want and reboot device..!mine is 190!if you dont like it just change again the line to 240 which is the stock resolution...its simple!

Oh, haha.
Anyway, off-topic: where to download fast five for android?

Mine is on 161, the reason of 161 instead of 160 is the notification bar, with setting of 160 it will not go fullscreen, but 161 would.
About small keyboard button issue, I compile my own keyboard from 2.3 gingerbread source a 2.3 stock keyboard, with a larger define on the keys, works well now on my 2X.
About some games are not "resize" to take the different LCD density issue, try install Spare Parts from market, Un-tick "Run in compatibility mode", reboot it "should" help, this is needed on many older/not multiple resolution ready apps.

when changing the density to 161 or 180 the notification bar gets all corrupted, am i the only one having this? i'm on CM7 19
[EDIT] typo, was on 170, but is this normal?

svceon said:
when changing the density to 161 or 180 the notification bar gets all corrupted, am i the only one having this? i'm on CM7 19
[EDIT] typo, was on 170, but is this normal?
Click to expand...
Click to collapse
I am stock ROM 10a, no such problem (corrupted).
I am sure 160, 161, 180, 200, 220, 240 works, the catch on non 161 and 240(default) is the notification do not extent to full width, which is actually common and known issue of mdpi/sdpi/hdpi issues.
can u plz post an image to show how it corrupted?

CM7.1 with ADWLauncherEX Bug

I have this bug whereupon startup of ADWLauncherEX in CM7.1, the icons and text are much smaller then specified in the settings. However, this seems to remedy itself once i restart ADWLauncherEX. Anyone have a more permanent solution for this?

I'm using ADWex too, and haven't noticed this issue. Although my LCD density is set to 165, but never noticed it before at 160.

Help adjusting dpi

I cannot find the DPI line in build.prop. It seems like it's not even in there. I've tried using apps and they don't work. I have appsettings but I don't think I can use that for the overall DPI of the phone. Can anyone please help?
Edit: I was able to fix the issue. I had no DPI coding in build.prop so I put it in myself. I have no idea why it's not there because the phone is new and the first thing I tried was DPI edit after immediately rooting. Now I can adjust everything and app settings works.
GS5 Towel Rooted

Black overlay on chrome in landscape

This is something I haven't seen before. I just got a Nexus 6, and on the first day I had it, I poked around on the phone with the OOB configuration, and chrome did work in landscape. Videos would be full screen, etc. Since then, I have:
Upgraded to 5.0.1
Rooted the phone
Removed the encryption
Changed the dpi to 493 with textdroider
Replaced the google launcher with Nova
Set the desktop grid to 8x7
Now, if I switch the chrome into landscape mode, the page takes up the whole screen for about a second, but then half of the screen becomes black, like there is an overlay over it. It cuts off the bottom half of the page. This happens when playing full screen videos in chrome too. Everything else on the phone, including the desktop.
I put the dpi back to its original value, but that didn't matter, so I changed it back. I've also set the desktop grid in Nova back to its original settings, which also didn't matter. I tried using chrome beta, but it has the same issue. Has anyone experienced this before? I haven't found any other examples of this. I tried to take a screenshot to post here, but the screenshot came out looking normal.

Fixed it.
Setting the DPI back to 560 fixed the issue. It must just not like the 493. I tried 520, but that didn't work either. I'm going to try 480 now, since 493 looked pretty nice.
cptInsane0 said:
This is something I haven't seen before. I just got a Nexus 6, and on the first day I had it, I poked around on the phone with the OOB configuration, and chrome did work in landscape. Videos would be full screen, etc. Since then, I have:
Upgraded to 5.0.1
Rooted the phone
Removed the encryption
Changed the dpi to 493 with textdroider
Replaced the google launcher with Nova
Set the desktop grid to 8x7
Now, if I switch the chrome into landscape mode, the page takes up the whole screen for about a second, but then half of the screen becomes black, like there is an overlay over it. It cuts off the bottom half of the page. This happens when playing full screen videos in chrome too. Everything else on the phone, including the desktop.
I put the dpi back to its original value, but that didn't matter, so I changed it back. I've also set the desktop grid in Nova back to its original settings, which also didn't matter. I tried using chrome beta, but it has the same issue. Has anyone experienced this before? I haven't found any other examples of this. I tried to take a screenshot to post here, but the screenshot came out looking normal.
Click to expand...
Click to collapse

Change lcd density to 560 in /system/build.prop, save changes, exit, and then reboot. 520 was the closest I've found that was free of issues but chrome would still have that issue in landscape with side buttons down. In landscape with side buttons up, however, chrome works fine in landscape in 520. I'm sure other values will provide the same but it seems other apps get affected.

480 was a no-go
Nope, issue persists on 480 too. Guess I'm going to be stuck at 560 until this is figured out.
cptInsane0 said:
Setting the DPI back to 560 fixed the issue. It must just not like the 493. I tried 520, but that didn't work either. I'm going to try 480 now, since 493 looked pretty nice.
Click to expand...
Click to collapse

460 DPI seems to work for me. I had issues with 480 and other DPI I tried as well. Seems hit or miss at certain settings.

460 works fine. I started at 480 and had half black screen as well.

I have been fiddling with different settings and 498 was the lowest/smallest I have been able to get with out any issues what so ever. With other numbers that I have seen seem to work but then I always end up with letters in the keyboard being cut off from the pop-up when I tap them. I don't know much about how the screen works and how scaling works to figure it out which DPI's will work with out any issues.

493 dpi over here.
I experience half black screen bug in landscape when i rotate my phone in such way that my power/volume buttons are on the buttom of the phone and if the keyboard is not present.
if I rotate the phone in proper direction, meaning, when the phone is in a landscape position and my power/volume buttons are located at the top of the phone, bug isn't present.
if keyboard is present and the phone is in landscape mode( power/volume buttons on the bottom) position results in keyboard flashing/constantly trying to redraw itself every time I press on keyboard.
Black overlay bug is system wide for me, not just in chrome(also present in other browsers, message app, file manager, etc), so I think the bug lies in Google Keyboard not liking 493dpi in landscape.
{ I'm as well, removed the encryption, root'ed, 5.0.2(AOSP, LRX22G, Pure Shamu) with Nova(12x7 grid) as default launcher. }

I just wanted to let you know that this issue seems to be resolved on Android 6 / Marshmallow.
I'm now able to set the density to 384dpi without getting the infamous half black screen in landscape mode (when the phone is rotated clockwise).
FYI: 384dpi is the highest value possible to keep the UI in tablet mode (including 4-way screen rotation, etc). From 385dpi up the UI switches to phone mode.