Related
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?
Been playing with the Bionic for a day now, (came from LG G2X) and it's pretty amazing. Have it all rooted and such.
Used "Root Explorer" and decided to changed the density from 240 to 190. Looks very nice on that big screen. Everything seems to be working normally, except the lock screen is a little funky. But I didn't mind.
I've never done or heard of changing the pixel density before. What does it do and how did you do it please?
art0605 said:
Been playing with the Bionic for a day now, (came from LG G2X) and it's pretty amazing. Have it all rooted and such.
Used "Root Explorer" and decided to changed the density from 240 to 190. Looks very nice on that big screen. Everything seems to be working normally, except the lock screen is a little funky. But I didn't mind.
Click to expand...
Click to collapse
Ohhhhh. If you have used ROMS for other phones, for me it was the X, then you would know about that. Like "Liberty toolbox" and not other "Tool-boxes" let you turn screen settings up or down. To the thread starter, any way to get a pic of "Before" and "After"?
mikecheat04 said:
I've never done or heard of changing the pixel density before. What does it do and how did you do it please?
Click to expand...
Click to collapse
It's an effect you put on the framebuffer to give the illusion of having a higher resolution on your phone. If you lower the pixel density value, it will make everything more spaced out and smaller in general, giving the illusion of the phone having a higher resolution. It adds nothing besides a placebo affect and breaks certain things, such as the lockscreen and the background image for the pull-down bar. If you don't care about those things, you can try it out and test it for yourself. I recommend a value of 200.
Check out lcd density in the market, it is free and there are some screen shots. I have mine set at 200. Make sure to get spare parts from the market and turn off compatibility mode to make some of the troublesome apps fill the screen.
200/220 seems to be the nicest with the pentile display and century gothic as the new stock font, anything lower and you really really see the pixels...bleh
Is it just me or just everything seem really big on this phone even with the font set to small? I feel like my S5 can fit a ton more content on the screen and they are supposed to be the same resolution. I.e. my keyboard takes up almost half the screen on the X. It feels like still 720p...
km8j said:
Is it just me or just everything seem really big on this phone even with the font set to small? I feel like my S5 can fit a ton more content on the screen and they are supposed to be the same resolution. I.e. my keyboard takes up almost half the screen on the X. It feels like still 720p...
Click to expand...
Click to collapse
This is amoled technology, it looks like pixelated as u said but it have many advantage, amoled can produce much high ratio of color saturation than other screen, there are only one screen technology that can truly turn off pixel where black picture is, I mean at black colour, pixels are off, means true black you cant find any faint or visible black that is cool feeling when you see at black especially at night... This feature is my favorite.
Sent from my XT1033 using XDA Free mobile app
Mandeep148 said:
This is amoled technology, it looks like pixelated as u said but it have many advantage, amoled can produce much high ratio of color saturation than other screen, there are only one screen technology that can truly turn off pixel where black picture is, I mean at black colour, pixels are off, means true black you cant find any faint or visible black that is cool feeling when you see at black especially at night... This feature is my favorite.
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
I dont think you understood my original question.
Yeah, the DPI is set pretty crazy on the phone. First thing I did was root and change the density to 380 instead of 480. That fixed the problem for me.
l2and said:
Yeah, the DPI is set pretty crazy on the phone. First thing I did was root and change the density to 380 instead of 480. That fixed the problem for me.
Click to expand...
Click to collapse
Which app did you use?
If you are rooted just use a File explorer to edit the build.prop.
Be aware that the Camera app will no longer function if you change the DPI
knitler said:
If you are rooted just use a File explorer to edit the build.prop.
Be aware that the Camera app will no longer function if you change the DPI
Click to expand...
Click to collapse
lol that is ridiculous - need a camera
km8j said:
lol that is ridiculous - need a camera
Click to expand...
Click to collapse
If you want to change the build.prop, you'll need to mount /system as well.
After doing that, install Xposed and used the "App Settings" module. After the restart, go to app settings and change the DPI back on the camera and moto display if you're using the active notifications to 480 (com.motorola.camera and com.motorola.motodisplay). After that, you should be good to go with everything else. If you come across another app that looks funny or doesn't load, go back to app settings and change it.
l2and said:
If you want to change the build.prop, you'll need to mount /system as well.
After doing that, install Xposed and used the "App Settings" module. After the restart, go to app settings and change the DPI back on the camera and moto display if you're using the active notifications to 480 (com.motorola.camera and com.motorola.motodisplay). After that, you should be good to go with everything else. If you come across another app that looks funny or doesn't load, go back to app settings and change it.
Click to expand...
Click to collapse
But this cans the camera?
I tried the moto X in at&t store and also noticed the icons and text being a lot bigger. I tried using nova launcher and this displayed everything normally. I think the stock google now launcher is the problem
viking2.0 said:
I tried the moto X in at&t store and also noticed the icons and text being a lot bigger. I tried using nova launcher and this displayed everything normally. I think the stock google now launcher is the problem
Click to expand...
Click to collapse
Yes, Google launcher has bigger icons that stock Android launcher.
Yes but everything is that way. Even individual apps are simply huge
Yeah they definitely should have tweaked the DPI for this phone. Most of it is fine (for me) but the icons are ridiculously large. Not going to give up the camera app to change it though.
km8j said:
But this cans the camera?
Click to expand...
Click to collapse
It will force the camera to stop working until you go into app settings using xposed and set the DPI to the camera back to 480. Once you do that, the camera will work just fine.
......
Hmmm anyone else notice that the active display time and lock icon is all screwed up after changing dpi
Changing the DPI on active display app works
The annoying part is that Moto Display is only compatible with the stock DPI. I went from 480 to 400 today and everything is fine besides that and stock camera app crashes on opening. However, I use Google Camera so meh.
Yup, if you need your active display back. Change com.motorola.display back to 480.
There are a couple apps in the play store that will change the DPI for you.. DPI changer, texdroider DPI. Both work great. As mentioned, use the Xposed module "app settings" to change any app that is acting up, back to stock DPI. I've got the VZW variant, I may have to make an exchange to the pure edition. I myself prefer a much smaller DPI, as well as hiding my nav keys and enabling pie via LMT. Not to mention the Xposed module "Tinted Status Bar" which improves the look of the interface dramatically.
I always used 290 on my nexus 4 and it was great.
I really don't like how big the icons are stock. Any suggestions?
Sent from my XT1095 using Tapatalk 2
I use Nova, Google Launcher icons are stupidly big
320 maybe
I wouldn't go 320... the stock value is 480.
I use 440, it's perfect for me. It could be smaller (but 320 is WAY too small), but with the large screen and bumbling one-hand use 440 is perfect. Plus if you don't use XGELS to modify the launcher settings, it adds a 5th column in the app drawer.
I will also add: if you change the DPI at all, Moto Display will be weird. It's just graphical, off center and funky icons. Xposed module App Settings allowed me to change the DPI of just Moto Display back to 480 and problem solved.
how do you change the dpi? the large icons are bugging me too
_bottle_ said:
how do you change the dpi? the large icons are bugging me too
Click to expand...
Click to collapse
The large icons aren't a dpi issue, it's just the style of the Google launcher
_bottle_ said:
how do you change the dpi? the large icons are bugging me too
Click to expand...
Click to collapse
Edit the build.prop.
I just use the app "textdroider dpi" to adjust mine
Just rooted 5.0. On 4.4.4, I had my DPI at 400 with the Xposed Module App Settings to correct Moto Display. Obviously, that's not an option on Lollipop. So, my questions is, does anyone know a way to correct this while maintaining a similar DPI to 400 and do it without Xposed?
Crooke356 said:
Just rooted 5.0. On 4.4.4, I had my DPI at 400 with the Xposed Module App Settings to correct Moto Display. Obviously, that's not an option on Lollipop. So, my questions is, does anyone know a way to correct this while maintaining a similar DPI to 400 and do it without Xposed?
Click to expand...
Click to collapse
Yeah I just switched to 400 and I'm having the same issue, anyone have a fix for this?
ggmask said:
Yeah I just switched to 400 and I'm having the same issue, anyone have a fix for this?
Click to expand...
Click to collapse
Don't think there really is a fix.. With xposed you could do per app DPI.. I've learned to deal with it being a little off center using 420 dpi
CWick4141 said:
Don't think there really is a fix.. With xposed you could do per app DPI.. I've learned to deal with it being a little off center using 420 dpi
Click to expand...
Click to collapse
That was my plan but then I noticed that after some time it seemed to re-center, but the actual active portion of the screen doesn't. So I have to slide to the left of the actual unlock icon to unlock it (???). Weird.
I'm interested too, those icons and applications are too big for me. I feel like we don't benefit of the entire 5.2" screen 1920x1080 and 441 ppi... it shows exactly the same amount of content as a 4.2" screen with 150 ppi. I would be happy to find a little fix too, I have not enough skills to build it.
Maybe the key is to come back to Nexus' line, but the Moto X 2014 seem so perfect except that point.
Just install nova launcher
Sent from my XT1095 using Tapatalk
Tried it. Indeed the desktop is better, but each time I launch an application like Youtube, Whatsapp or Settings for example, it feels I'm a old person who needs very big font size. I would like to see more on my screen, with smaller font size then.
Setting ourself the DPI would have been great.
I edit with pro build dpi with root explorer , perfect.
regards
Anybody else noticed that the phone icon hasn't updated to the flatter one after update?... Looks out of place
Well, I decided to keep my XT1092 and try it out with some tweaks. I'm on Lollipop 5.0 (22.21.19 reteuall).
I firstly unlocked the bootloader, secondly I rooted it with Multitool 4.1, and finally I used "adb shell wm density XXX" to change the DPI to 360.
PERFECT : I have no glitches at all, even Active Display is OK. So I recommend this very easy method to be happy with a good screen DPI.
Edit : my bad, after the 1st reboot, I have same problem with Active Display, but it's worth it.
There will be Xposed soon I hope, then I'll take it back.
StiiLe said:
Well, I decided to keep my XT1092 and try it out with some tweaks. I'm on Lollipop 5.0 (22.21.19 reteuall).
I firstly unlocked the bootloader, secondly I rooted it with Multitool 4.1, and finally I used "adb shell wm density XXX" to change the DPI to 360.
PERFECT : I have no glitches at all, even Active Display is OK. So I recommend this very easy method to be happy with a good screen DPI.
Edit : my bad, after the 1st reboot, I have same problem with Active Display, but it's worth it.
There will be Xposed soon I hope, then I'll take it back.
Click to expand...
Click to collapse
I found this too, but ended up going back to stock DPI for another reason as well: the back button does not get properly sized when you adb the DPI, it looks too big. Same goes for some of the status bar icons (for example the battery is larger than other buttons). Then there's the glitches like your profile icon in hangouts being way too big, the top developer icon in play store being way out of position, and the triple dots under the middle word suggestion on google keyboard being too large. Changing DPI is just a hassle and makes the phone uglier, which is a real bummer because this phone desperately needs a better DPI setting.
ggmask said:
I found this too, but ended up going back to stock DPI for another reason as well: the back button does not get properly sized when you adb the DPI, it looks too big. Same goes for some of the status bar icons (for example the battery is larger than other buttons). Then there's the glitches like your profile icon in hangouts being way too big, the top developer icon in play store being way out of position, and the triple dots under the middle word suggestion on google keyboard being too large. Changing DPI is just a hassle and makes the phone uglier, which is a real bummer because this phone desperately needs a better DPI setting.
Click to expand...
Click to collapse
I don't have your problems...
Maybe it depends on which number DPI you are, mine seems OK with all of this. Also, I set "Small" font size in the settings. I got one "big" problem for me anyway, I can't use Swiftkey with this, there is a strange bug with this keyboard, I will post an screenshot later.
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.