Hey guys,
I've been having this issue since I installed the chroma Rom on my nexus 6. Basically whenever I play a video of any sort in chrome and full screen it, the url bar shrinks but is still visible on the screen, which add you can guess is a little annoying, an example is shown in the screenshot below, note this occurs in portrait as well as in landscape.
I've tried looking in a few places add well as here, and in settings for a solution but can't find any. So I was hoping you guys could help. The only thing that I think it could be and haven't tested yet is that I adjusted the pixel density to 420.
Help is much appreciated
Related
Hello Everyone!
I am new to Android, my Galaxy Note is my first Android phone. So maybe my questions will seem stupid :
- Is there a way to quickly change between Silence/vibrate/ringtones ? Like a widget ? It is easy to switch between vibrate to ringtones, but I have to go to settings when I have to get the vibration off.
- Is there a way to be reminded of memos or tasks, like an alarm, but with memos ? An app for that maybe ?
- My screen has sometimes problems with black pixels on dark photos or youtube videos. There are huge packs of black pixel, not showing great hardware problem ? I hope not...
Thank you!
[Sorry I'm French...]
Kimundi said:
Hello Everyone!
I am new to Android, my Galaxy Note is my first Android phone. So maybe my questions will seem stupid :
- Is there a way to quickly change between Silence/vibrate/ringtones ? Like a widget ? It is easy to switch between vibrate to ringtones, but I have to go to settings when I have to get the vibration off.
- Is there a way to be reminded of memos or tasks, like an alarm, but with memos ? An app for that maybe ?
- My screen has sometimes problems with black pixels on dark photos or youtube videos. There are huge packs of black pixel, not showing great hardware problem ? I hope not...
Thank you!
[Sorry I'm French...]
Click to expand...
Click to collapse
If you slide down the drop down menu you can turn on sounds or no sounds. You can also get widgets on the market that can enable or disable vibrations I believe as well.
Gtasks is an app I use to sync google tasks, there are options to put reminders (alarms). I don't believe memos in theory need reminders or alarms. I believe that to be a task if it's time constricted.
You could upload a picture here, and we can see if we can replicate the issue. I don't have my note yet, it's on its way. But I'm sure someone else wouldn't mind taking a look at it.
Cheers
Kimundi said:
Hello Everyone!
- My screen has sometimes problems with black pixels on dark photos or youtube videos. There are huge packs of black pixel, not showing great hardware problem ? I hope not...
Thank you!
[Sorry I'm French...]
Click to expand...
Click to collapse
If it is "sometimes" then usually it is not a dead pixel because they are "everytime"... It could be just contrast issues on the picture.
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
Ok so I originally posted this question here:
http://forum.xda-developers.com/showthread.php?t=2556217
but I was told it was probably the wrong place and I should ask it in this section.
When I play some games, for example Paper Monsters, or Cordy 2, the game orients itself to landscape but upside down, and when I flip it the other way, the game keeps changing to upside down. I have no idea what the heck is going on!? The orientation and rotation settings work great for pretty much every other app, which means so far I haven't found any other apps doing this. Could it be a problem with the ROM I'm on? This is the ROM I'm using:
http://forum.xda-developers.com/showthread.php?t=2482192
There are some apps I can download from the PLAY store to help compensate for this issue somewhat, one I'm using called "Set Orientation" and it works ok but it sets the global rotation for everything, even some apps that shouldn't rotate. It's a decent bandaid I just have to set it to disabled when I'm using the apps that I don't want to rotate, for example, gravity / physics apps where you rotate and move your device all around to get maybe balls or particles moving in different directions. I would like a permanent fix however. Any help is greatly appreciated!!! :good::good::good::laugh::laugh:
I want to be fixed this problem.
Kindle 8.9 display is should rotate left-to-top, right-to-bottom. Official case is designed like that.
This seems in CM11.0 and CM12.0. Is there no plans to fix it?
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.
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!