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.
Related
Hi, I'm running into the issue that the screen is being rendered larger than the physical size of the screen so status boxes sometimes partially off screen and app icons get half hidden in the corners.
I plaid around with build.prop, but it didn't really help any. Is there a way to modify the home screen without changing the resolution? Also, if anyone knows of a way to change icon sizes short of installing a different launcher, that would be a huge plus.
TIA!
I've read that there are limitations in place for the preview image that kind of create this problem. If I understand the problem correctly it may be a case of changing pixel density but the preview image doesn't let you go beyond a certain density so even then the problem still exists. It's probably just something we have to deal with until Honeycomb becomes publically available for development.
This makes sense. The only reason I care about this is that when I use Aldiko, I can't see the top line of text because it pushes the words above the actual screen.
Does anyone have a recommendation for an E-Reader that they use successfully on HC???
xdadidida said:
Hi, I'm running into the issue that the screen is being rendered larger than the physical size of the screen so status boxes sometimes partially off screen and app icons get half hidden in the corners.
I plaid around with build.prop, but it didn't really help any. Is there a way to modify the home screen without changing the resolution? Also, if anyone knows of a way to change icon sizes short of installing a different launcher, that would be a huge plus.
TIA!
Click to expand...
Click to collapse
You changed the LCD density in build.prop and the screen didn't change???
What is your lcd _density set at?
Sent from my NookColor using XDA App
I haven't really looked into this but I do know there are ports of honeycomb for various phones such a the evo, maybe try pulling the build.prop from one of those and see howe they altered screen density.
Sent from my PC36100 using XDA App
i've tried changing the number but havent had much success through the buid.prop. Any ideas on a good number and which number to change? Looks like there are 3 density numbers
For Honeycomb, I found that 120 is the best lcd density, it shows all the options when you expand the settings from the clock, it also displays the correct number of running apps in the quick change button (or whatever you call it) Also, Lcddensity is a good app for trying out diffrent settings. For Aldiko, I recommend increasing the margin size to see the top line of text, not a perfect solution, but it works.
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
Hey everyone,
due to the high resolution and comparably large screen estate I would like to use a lower screen density of around 410dpi, instead of the stock 480. :fingers-crossed:
One example:
On my Galaxy Nexus I was used to having a 24dpi high navigation bar at the bottom of the screen.
It was small but still I was able to hit the buttons accurately.
Same goes for the small keys of my keyboard of choice, Swiftkey.
Since I am on the HTC One and I flashed a Custom ROM, which I am running on 410dpi and wanted that stock android navigation bar at the bottom even at 48dpi (which is like 1.7x the height of the one I was using on my Galaxy Nexus) I have trouble hitting the buttons.
This is very disappointing.
It feels like the Touch layer of the HTC One is not that accurate
Is it just me or is this a known problem?
(Couldn't find anything via search, though)
Any ideas what to do about it?
All the best and thanks in advance :good:
I don't see this at 360dpi which is what I have mine at, but I do see it at 240, but everything then is silly in size.
Have you enabled the show touches in dev options and checked where its actually pressing?
Always keep forgetting about that! Thanks!
That is pretty weird...the touch inputs seem to be quite accurate, though. (Debugging Tool)
But it doesn't recognize them in something like "the upper half of the navigation bar" :/
I quickly shot a Video (sorry not the best focus point )
One can clearly see that I am hitting the home button several times, but the input doesn't get recognized.
That is really really weird and unsatisfactory :/
I gave it a shot for you... It seems to work fine on 36dp and above. 30 and 24 exhibit the same behavior as your video.
FYI: I'm running SlimROM at 361dpi. That was the default for me when I went from ARHD 10.2 to Slim b6 and it has stuck with me since then. I tried to get the same look in RootBox but it didn't work the same, so I went back to SlimROM b6.8, and am now on SlimROM b7.
Thanks :good:
I am starting to believe that this is might be caused by the Logo-Button-Hack.
If you peek closely from the side under the tip of your finger touching the button and starting from the very bottom of the glass area there is just no response at all on the logo. It's like the first pixel of the screen are allocated to the logo-button and not the area below the screen.
Maybe an area of lets say 10-15 pixels height is used for that and therefore not any longer available for the nav bar.
Which doesn't really matter if you are hitting the comparably huge app-icons in the drawer otherwise
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.
After recently rooting my J7, I've decided to use one of the resolution changing apps to give my phone a 1080x1920 pixel faked resolution, with a dpi of 280. For the most part, it works. Some built-in apps such as the camera or even the touchwiz launcher (seems some UI elements used hard-coded numbers to define regions, or in case of the camera, the view is almost a quarter of the screen with black around the edge, and the touch input is offset to a different corner.
All else seemed good, until I realized another major flaw - the call screen - it works, however when trying to pull up the keypad when in a call, it only displays a single, gigantic 1 button. no other buttons are available. Button-based menus are of course now impossible to navigate... unless every button to press is 1, 1 and 1. And then 1.
Can't take pictures of it now as the resolution change causes an issue for screenshots - I'll need to get a screenshot app for this, but ultimately, are there apps that replace the call screen? I thought a dialer app would fix this but the one I have only replaces the text/call/contacts apps, not actually calling. I'd prefer there to be an app that can replace it, as it seems most third party apps are almost never hard-coded to a specific resolution, meaning I'd imagine it should work on my modded phone.
If more explanations are needed I can try to provide some screenshots as needed when i'm done. I'm really hoping I don't have to reset the screen. I love how everything works otherwise...
anthonyloprimo said:
After recently rooting my J7, I've decided to use one of the resolution changing apps to give my phone a 1080x1920 pixel faked resolution, with a dpi of 280. For the most part, it works. Some built-in apps such as the camera or even the touchwiz launcher (seems some UI elements used hard-coded numbers to define regions, or in case of the camera, the view is almost a quarter of the screen with black around the edge, and the touch input is offset to a different corner.
All else seemed good, until I realized another major flaw - the call screen - it works, however when trying to pull up the keypad when in a call, it only displays a single, gigantic 1 button. no other buttons are available. Button-based menus are of course now impossible to navigate... unless every button to press is 1, 1 and 1. And then 1.
Can't take pictures of it now as the resolution change causes an issue for screenshots - I'll need to get a screenshot app for this, but ultimately, are there apps that replace the call screen? I thought a dialer app would fix this but the one I have only replaces the text/call/contacts apps, not actually calling. I'd prefer there to be an app that can replace it, as it seems most third party apps are almost never hard-coded to a specific resolution, meaning I'd imagine it should work on my modded phone.
If more explanations are needed I can try to provide some screenshots as needed when i'm done. I'm really hoping I don't have to reset the screen. I love how everything works otherwise...
Click to expand...
Click to collapse
Install Google Phone apk and set it as the default dialer app.
It also replaces the incall screen
Ruturaj Kadam said:
Install Google Phone apk and set it as the default dialer app.
It also replaces the incall screen
Click to expand...
Click to collapse
Awesome. It worked like a charm. Thank you so much!