Database Develop

Honeycomb: Problem with default screen resolution

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.

[Q] Stock Screen Density

Hi, I am fairly new to Android development. I have a question regarding the Galaxy S. What is the stock screen density of this phone in 2.1? I am trying to create the Galaxy S environment on an emulator so that I can test my application (I do not own one of these phones). Does the density change in later versions?
I have read hxxp://developer.android.com/guide/practices/screens_support.html
I know that the phone screen resolution is 480x800.
I am not sure what type of screen it is (Normal or Large), hence I cannot determine the density.
Is there an easy way of determining the density and screen type of a phone?
Thanks!

I do not know how to find out a density of other phones thought its a standard
But Samsung Galaxy S I9000 should have 240 (as seen in build.prop ro.sf.lcd_density=240 ) as the standard one and no it doesn't change in the versions.
(I use 200 though looks nicer )

Hmm, strange. The application seems to work fine with that configuration, yet one of the users is reporting an issue. I wonder if he changed the density..
Thanks for your help!

What kind of issue?
Well tell that guy to download spare parts and unticks "compatibility mode" if he is using changed density it may help him.

Grr. It was a simple user error. He thought the background picture was not appearing in the center, when it was. Just the way the picture is.
I started fiddling with making the application accessible to other densities. The AVD comes with a large screen, medium density skin (480x800/480x854 at 160dpi). Are there actually any devices that use that kind of setup? I ran my application at those settings, and for some reason it is loading the mdpi resource, which is designed for a normal screen (640x480).
Thanks for your help Pagot!

[Q] Max events in build prop

Just wondering if anyone knows if there is a "maximum" value that can be used, before we start see diminishing reutrns possibly? I know the value is currently set to 180 in the Tho3ry ROM. Just wondering how high I can crank it up to? The blur launcher/app drawer still has that annoying slight stutter when you switch between the first screen. The stutter only occurs once, then after that it's pretty damn smooth. Any information would be great! Thanks!

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.

AMOLED tone changes when switching apps.

Hi.
I seem to have a funny hue over the screen when switching apps sometimes. It's like the colour tone of the Amoled changes.
Does anyone else have this?

Disable "Natural Tone" under Display settings

It still does it when I turn that option off.

I confirm this happens to me also, even if I disable natural tone and auto brightness. It also happens when the lighting changes fast. It is a bug in the software for sure, I asked about this some time ago but I have not received any answer regarding this, not even from Huawei.

Find out why here:https://forum.xda-developers.com/huawei-p20-pro/help/blue-shade-recent-apps-t3915308/page2

Cheers.
I've noticed performance in pretty bad across the board with nova launcher plus the numerous bugs.
Can anyone recommend another launcher that has a pixel launcher option.

Warren_Orange said:
Cheers.
I've noticed performance in pretty bad across the board with nova launcher plus the numerous bugs.
Can anyone recommend another launcher that has a pixel launcher option.
Click to expand...
Click to collapse
I removed the default launcher and now Nova works amazing! Although the recents is card flip.