My android device behaves in a strange manner when I connect a 1366 X 768 lvds display. The UI is different from what I was getting with HDMI connected. I'm getting a different home screen with some other wallpaper and more than that the navigation keys at the bottom are missing.
It looks like based on the hardware display configuration the UI is configured.
Is there a way to override this behaviour? Please suggest some ways to tackle this..
Android Version : Lollipop 5.0.1
issue was due to a hard coded display density parameter. It was hard coded to 240. Issue is resolved when the density value is changed to 160.
$adb shell "echo qemu.sf.lcd_density=160 >> /system/build.prop"
Thanks,
Arjun.
Related
I am trying to connect a fire stick 4k max to a 5.5 inch 4k lcd (where the hdmi interface is provided by a MI-PI board). However, here's what i get :
While booting :
and a few seconds later :
The lcd is working on windows. Also, after struggling with display configuration, I managed to make the lcd work on a RPI 4, at the desired resolution (i.e. 3840x2160#30). I am pretty sure that it should also work with a fire tv 4k max, regarding to the first image which is in 4k (I think), but with rotation and wrong pixel positionning issues; I had something very similar on RPI4 before changing some parameters in /boot/config.txt file.
I am a total noob at android. I tried however to set the resolution and the density via adb shell,
but it didn't work...
I also tried to force the rotation using
adb shell settings put system user_rotation 1
but still havig the same problems... Any Ideas or suggestions? I can send some logs if needed. Thank you in advance.
I've several comments in my android wear applications which says that my app doesn't look good on two devices:
ZenWatch and Sony SmartWatch3.
I've gathered DPI and resolution of both:
ZenWatch - 320x320 round 278dpi 1.63 inches
SmartWatch3 - 320x320 square 283dpi 1.6 inches.
Now, I'm trying to run the APP further than the basic emulator. However, there are just two configurations I can use:
I've tried editing it's config files, with no luck.
in config files I couldn't manage to find screen size. Just DPI and looks like any configuration changed, is ignored.
The following is all the configuration I've found interesting:
hw.lcd.density=240
No screen size, no resolution. Just lcd density, which for me looks like DPI, but now I'm not sure. So I cannot mimic any of the two above mentioned devices.
Any tips about this?
Edit 6 June 2015:
I cannot run the device I configurated:
As you can see, a yellow warning is shown, which says the following
So I'm not able to run any device I created.
Click Button of AVD Manager, then click Create Virtual Device..., then click New Hardware Profile, then you can in the new window customize settings of a hardware, like Device Name, Device Type, Screen(ScreenSize, Resolution), Memory, Input, Supported Device states, Camera and Sensors.
After finishing these, you can select this Hardware Profile to create your AVD.
If I understood you correctly, you need to click on the "New Hardware Profile" button on the buttom left corner and then you can change the size of the screen, it's resolution and more.
Just for the sake of answering some other users... What I've been actually facing, was that there's a different DPI used in an AsusZenwatch on 4.4W and 5.1.1... Weird but true. Be sure to test on both APIs
I have an Android tablet (Teclast X98) with an extremely annoying feature that it constantly keeps adjusting the brightness of the display all by itself.
Initially I thought maybe the tablet has a faulty display unit - the pumping of the brightness is that annoying. After a lot of investigation I finally noticed this in dmesg:
QL: i915_dpst_compute_brightness dpst factor = 7022.
QL: i915_dpst_compute_brightness dpst factor = 6987.
QL: i915_dpst_compute_brightness dpst factor = 6882.
Put DPST into Google and I find the Intel engineers came up with this:
http://en.wikipedia.org/wiki/Intel_Display_Power_Saving_Technology
So it's not just the brightness that is adjusted, but also the chroma of the display, which leads to washed out colors in addition to the reduced backlight intensity.
Next I try and find the driver where this is implemented. Giving the function name a shot on GitHub I found it in the i915 GPU driver.
Now I see in that the driver has a dpst.enabled setting.
Presumably there should be some way to set dpst.enabled to false.
Anyone have any clue how I could turn it off?
sysctl, /proc/...? There has to be some way to turn it off?
Well. That was surprisingly easy.
Not sure if this is the correct way to do it, but here's how I got rid of it:
echo 0 > /sys/class/drm/card0/power/i915_dpst
# Something keeps writing 1 into this file, so I just prevent it like this
busybox chmod gou-w /sys/class/drm/card0/power/i915_dpst
If someone knows a better way to disable it please add an answer.
A while ago, I was able to resize the screens on Android. For example, I had a Xoom, and was able to run a command from ADB which shrunk it down to a 7" screen (leaving a black border around it). Granted, it was a little buggy because the home/back/app-switch buttons disappeared, but I know it's possible. It's a 1 line command where I input the new screen resolution in X and Y pixels for the Xoom.
I was wondering if anyone was familiar with this, and knows how to do it.
(and if anyone says it's not possible, I can assure you it is)
(and I want to do this so I can test apps in various screen sizes on my Nexus 10, and I'd prefer not using an emulator)
An update to this answer for Jelly Bean 4.3 from Android dev Adam Powell on Google+ (link found via this SO answer):
In Android 4.3 these options moved from the "am" command (ActivityManager) to the "wm" command (WindowManager). Type "adb shell wm" for details.
So you can now run on 4.3 devices:
adb shell wm size 1280x800 or whatever size or reset
and
adb shell wm density 480 or whatever density or reset
Just make sure the screen is not currently displaying at the moment you run the command.
I believe it is:
adb shell am display-size
but i am away from a computer to try it. An example use would be:
adb shell am display-size 640x480
you can also change the resolution via android terminal, just type "wm size 720x1280" for example.
How can I build a standard ADV to test my Hello World app. I've just built my Hello World app on Android - using eclipse, and am having real problems getting the AVD to work properly. My setup Android 3.1 level 12, and I set the skin to 800 x 600 as the default WXGA, seem to make a massive screen. When it loads, I get just the Android screen but no side keyboard.
In addition, why do I get completely different looking skins when I play around with the skin size. Sometimes, I get a nice sea scape sometimes, but its portrait not landscape - how do I turn it? One time I get a lock?
Any help would be really appreciated. (I using Java 1.6 64 bit).
Thank you very much.
Ed Ryan
My setup Android 3.1 level 12, and I set the skin to 800 x 600 as the default WXGA, seem to make a massive screen.
Use the scale option when launching the emulator to resize it to something manageable. There are no 800x600 Honeycomb devices, so you are far better served using WXGA.
When it loads, I get just the Android screen but no side keyboard.
Correct. You won't get the side keyboard for WXGA, either. You do not need it, as everything on that side keyboard is available to you from your own physical keyboard on your development machine.
The skins are only available for the out-of-the-box skins or the ones you create manually (see here). However, you can access all of the keys using other keyboard shortcuts, which I personally found way more convenient. Plus, you save space.