I've succeeded to screen mirror the RPI running android things. What I did is:
installed TeamViewer_Host.apk via adb
Ran it on the RPI and login to my account(needed a display connected by HDMI)
connected to it by my laptop TeamViewer application
then got a very nice 1080p resolution mirrored screen
But the problem appeared when I tried to do the same thing but without the HDMI display connected and then suddenly got a poor 32x32 tiny screen on the laptop!
I tried it with Vysor app too but got the same result
My guess is that Android Things somehow detects automatically the resolution of the display and fits itself with it but when there's no display connected, it gives us a 32x32 one!
You guys have any ideas for this one?
Okay. I finally got the right way to do this.
The only thing you need to do is to adjust the resolution(while your Pi is connected to an HDMI display). After that you dont need the physical display any more and can connect to the Pi via TeamViewer.
For adjusting the resolution use this command in ADB:adb shell wm size 1080x1920 or any other resolution.
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.
Since I upgraded my monitor to 4k, I have a problem with the Android emulator. On my system (KDE neon 5.15) the AVD does not scale the display of the device, but only the device itself, as it can be seen here: Display of Android device not scaled. So it's almost impossible for me to click on the right area on the display, as the input field of the touch gestures is also scaled correctly, but only the display itself is not. I already checked similiar problems on stack overflow like 4k display & Android emulator: fail, but non of them seem to have the same problem. Does any one else have experienced a similiar problem on Linux and 4k monitors?
I experienced the same problem with my Windows 10 computer. Here is a solution that works for me:
Switch your screen resolution to 1920 x 1080
Start the android emulator
While the emulator is running, switch your resolution back to 3840 x 2160 and it should be scaled properly
You will have to do this every time you start the emulator.
Once you have it running properly in 4k DO NOT close the emulator because you will have to repeat the above steps.
This worked for me on my Windows 10 machine. I am not sure how it would respond on Linux.
today I noticed something wired. I have got an Emulator Device running a resolution of 1440x2560. I was developing most of the time on this Emu Device and today I plugged in my cousins Galaxy S7 Edge, which has the same resolution, but I noticed that there was less screen space LOL I know it sounds stupid, but I know for sure because my Admob Ads weren't showing up anymore, and I saw that they didnt have enough space (width,height) to show up. After changing some width & heights settings inside my code the Ads did show up again, but this had me seriously confused. How could this even be possible? The Emu Device has the exact same screen resolution, the same Android Version (Marshmallow). Why would I have more space inside the emulator and less on a real device? Anyone noticed something familiar?
I'm trying to run the emulator in Android Studio. When I run the avd for Nexus 5 API 8, the phone image appears, but the screen is blank. Some research uncovered that the nexus screen may be too dense to display on my 1368x768 laptop screen, so I tried creating smaller density avds such as 4" wvga nexus s and 3.4" wvga. When I run these, I get the error "failed to create drawable" and no phone image pops up. When I connect my LG phone via usb in developer mode, the app works fine on the phone. Why can't I get the emulator to display the app output?
I had a similar problem and the solution was to disable hardware rendering.
Steps:
Open Tools\Android\AVD Manager
Edit the Virtual Device (Click on the pencil)
Change Emulated Performance - Graphics to 'Software-GLES 2.0'
See also this answer for other options.
I just started using genymotion and I really like it.
One thing that is frustrating me is that emulators take a lot of screen space and are contained within scrolling window.. which makes it less convenient to use
I tried to change screen resolution or look for some kind of option myself but with no luck
is there "scale to real device size" option like in sdk emulator?
UPDATE
when I start genymotion binary, get the following in the console
~/coding/genymotion$ sudo ./genymotion
Genymotion log file: /home/u238/.Genymobile/genymotion.log
Player log file: /home/u238/.Genymobile/genymotion-player.log
OpenGL connected to 192.168.56.101:25000
Port 22468 will be used for OpenGL data connections
The emulator shows up for about 5 sec.. black screen with white ui buttons on the right.. and then it disapears from screen
UPDATE
[facepalm] to solve the vanishing emulator just install graphic drivers supporting opengl 2
GenyMotion Virtual Device opens and disappears immediately
Ok I get it.
You're not running the Genymotion player but Virtual Box. Try to run the genymotion binary (the one where you downloaded the templates) and to launch your VMs from it directly. It brings a lot of improvements.