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?
Related
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 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
I'm currently working on an app in Android Studio where I need to capture an image using the camera on the phone. The image must be very specific and not contain any background noise.
The way I want to solve this problem is by adding a box to the camera preview indicating the region of interest (ROI). After that the image can be cropped in a way that only the content of the ROI is present.
How do I add this box to define ROI?
In my mind it would be perfect if it was a thin white line.
Can I do it if I use the Image Capture Intent or do I have to create my own camera app?
Check this out - is that what you're after?
http://code.tutsplus.com/tutorials/capture-and-crop-an-image-with-the-device-camera--mobile-11458
I have encountered a problem while adjusting UI for various devices on android.
I created res/values-hdpi folder and similar other folders to put the dimensions of the layout there and adjust app's UI. I tested it on two devices
1) HTC ONE S
2) Samsung GT i8262
Both the devices comes under normal hdpi category according to android developers site. But the layout is completely misaligned in samsung device. Is there a solution to this sort of problem. I have also checked by changing the dimensions in the values-hdpi folder to confirm that both devices pick from same resource and it does!!! Both pick the dimensions from values-hdpi folder but misaligned in one of them.
Note: Both devices have only hardware buttons no navigation bar. So need not worry about that.
My guess is that HTC ONE S is 256 ppi, samsung gt i8262 is 207 ppi, but both have 4.3" screens, is this the problem?? How do I solve this if this is the case?
I finally created two values folders values-sw360dp-hdpi for HTC 1S and values-sw320dp-hdpi for Samsung GT i8262 and it worked.
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