I'm trying to set up ADB on a 1080 x 1920 pixel (a ZTE Blade X Max aka Z983) my display at runtime is cropping right & bottom. Looking for more info on how to define device correctly.
Currently have "Generic Phones and Tablets" definition set up for it.
Where are the definition files and how can I edit (and add) ADB profiles?
ADB not the problem, device runtime display size adjustment needed in code??? Found Settings-Display-Display Size in my Android... "Small" is all the pixels. I had "Default" which reduced the visible area, there was also "Large" with even less viewable.
End result --- ADB is max displayable, or "Small". Using alternate "Device for Preview" in editor for "Default" Android setting of fewer pixels
Related
I have two Pixel 4s connected for testing/debugging. They both show up as Google Pixel 4 [uniqueID]. Is there a way to change the displayed name, to make it easier to tell them apart without me having to remember each uniqueID?
I'm working with flutter in Android Studio in windows.
I set the screen size 768*1024(ipad mini size) when I create my virtual devices in android studio, but I find the height is smaller than expected. Actually when I call function window.physicalSize it shows that the size is 768*796.
I have gotten the fact that the function only shows the size of the screen that flutter can render.(So the hidden part is about what? bottom navigation bar,including three buttons, back, home, and the other one, or something else, I'm not sure.)
So, the question is how can I get exact size screen I want(768*1024)?
I'm working on firmware for a BLE device and need to define an appearance value. For now, I have chosen a 'Generic Computer'. However, the full list of appearance values https://www.bluetooth.com/specifications/gatt/viewer?attributeXmlFile=org.bluetooth.characteristic.gap.appearance.xml
has some values that might be more appropriate. In Windows 10 the 'Generic Computer' shows up with an icon of a desktop PC. Is there a resource available that will allow me to view the icons for any/all of the supported appearance values? I'd like to avoid multiple compile, load and browse cycles just to observe the icons.
The best answer to this question I can find is that:
The specification only assigns a general description to different values (e.g. "generic phone" or "generic thermometer". The official mapping can be found at bluetooth.com.
The actual icons (and perhaps any extensions) are vendor-specific. I have yet to find a search result that shows all icons for a particular implementation.
I have created an Android 4.2 AVD. For the need of my current project, the main screen orientation is landscape. The software keys option is selected.
The mode is set to xhdpi, like a Galaxy Nexus phone.
As I start the emulator, I see a black stripe on the right where the buttons should appear, but it remains black. Thus, there is no way to trigger a Back action since the emulated physical keys are disabled.
The problem can be fixed by configuring the emulator in portrait mode then rotate it once started; the buttons appear as expected. This causes problems since the window is automatically scaled down to fit on my monitor; I did not find any shortcut to restore 1:1 scaling at runtime, after the rotation is done. This is important since I would like to see pixel-perfect results.
I am using SDK version 21 and platform-tools version 16.0.2, as updated yesterday.
Found the solution myself... this is a workaround that allows getting 1:1 scale and the software buttons working.
Leave the AVD (Galaxy Nexus or cloned from it) on portrait mode.
Run the emulator from the command line, using the -scale 1 option; this is the magic that forces 1:1 pixel perfect ratio even if the window does not fit in screen at startup. By default, automatic downsizing happens to fit the monitor.
Rotate the display using Ctrl+F11 or Ctrl+F12 to get landscape mode.
I'm having trouble running my app on the Galaxy tab original 7". It appears to make everything 1.5 times bigger, i.e. if I specify 40dip for a textSize in my layout, it will display as 60 dip when I run it on the tablet.
I tried messing around with the display metrics and changing the density and densityDpi to 1. (When I run a toString of the display metrics in the Galaxy tab 2, they are both 1, whereas the Galaxy tab 1 has values of 1.5)
The app runs very well on every phone I've tested it on, and on the Galaxy tab 2, so I can't figure out what the problem is. I even tried creating a dummy app with just a textView with a size of 40dip, and it still converted it to 60.
Any ideas?
Does the answer to this question help you? Seems that he is having the same (or similar) problem.
Android layout on emulator vs device
Android, concerning the User Interface design