Hi, @nwlunatic
case download and rebuild will take a long time, so I want to know is this really work on emulator?

@qingyunliu Yes, it does. And actually on emulator we are using (Android emulator version 25.1.6.0), it's working quite fast.
If you would like to check, here is minicap.so https://www.dropbox.com/s/6j8vppbz66tud2u/minicap.so?dl=0
You should put it in stf/vendor/minicap/shared/android-23/x86/
Works only with android emulator sdk version 23, as you can see.

I think we could probably do this by implementing a fallback for emulators, if the ScreenshotClient works there. I can't promise when but I definitely want to take a look into this. Thank you for sharing your findings.

So everything else works, like touch events etc?

Yes, everything works just fine (minitouch, minirev), no provider erros or something, stf treats emulator as a usual device

@nwlunatic Hi, I see it really works just fine for API level 23 and I would like to apply the fix for the other API levels as well. Thus, I would like to ask you how did you build this minicap.so file? Have you followed all the build steps under minicap-shared page(https://github.com/openstf/minicap/tree/master/jni/minicap-shared )? Building minicap-shared following the steps seems hard, that's why I would like to be sure this is the right way.

@adpenev Hi! Yes, I followed minicap-shared build steps and they seem quite simple in comparison to building without docker-container. Still it require quite a lot of disk space (about all of my linux laptop 150 GB (to fetch android repo) ssd to build only android-23). Si I've simplified this Makefile, to build only android-23. I've also faced this issue, but I guess building only x86 is not affected.

@nwlunatic Thanks much for your answer. One more question, what linux OS did you use - Ubuntu, Mint or something? I'm on OS X and having in mind it cannot be used for the build I was thinking to create a Linux virtual machine on Virtual Box for the build.

By the way if you don't care about ever being able to sync the branch
again, you can remove the .repo folder to decrease disk usage. Builds will
still work fine, but repo commands won't.

On Tuesday, 12 July 2016, Igor Pavlov notifications@github.com wrote:

@adpenev https://github.com/adpenev Hi! Yes, I followed minicap-shared
build steps and they seem quite simple in comparison to building without
docker-container. Still it require quite a lot of disk space (about all of
my linux laptop 150 GB (to fetch android repo) ssd to build only
android-23). Si I've simplified this Makefile
https://github.com/openstf/minicap/blob/master/jni/minicap-shared/aosp/Makefile,
to build only android-23. I've also faced this issue
#24, but I guess building only
x86 is not affected.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#27 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAB-_QssOQ7KAzqQ7Hy545RHQnbrgF3yks5qU20qgaJpZM4H6eA3
.

Yep, .repo deleted 100GB, but it was a challenge to fetch all the source before deleting it )

I've used ubuntu. But I'm pretty sure you can use any linux. The only issue with OS X is case-insensitive fs by default. You can also try to make case-sensitive disk tho'

Yes I experienced the same thing. Making a case sensitive disk is OK, but older branches require older versions of Xcode... making it extremely annoying if not borderline impossible to build all the branches.

Oh, well. I was sure all the software to build android tree is inside the docker image. And you only need an mounted fs from host machine to put and get artifacts.
So using docker beta for OS X (docker xhyve) it is only a matter of fs case-sensitivity.

Right, the docker image works fine, it contains what's needed. I thought you were talking about building directly on OS X.

@nwlunatic and @sorccu Thank you for your answers guys. :)

Everything with the build works just fine. Thanks. :)

One question, @sorccu and @nwlunatic I remember you are using Linux what IDE and configuration do you use in order to write code, debug and build the minicap-shared project? Actually, debugging using IDE is what I really would like to setup. I downloaded and built the code on Linux Mint VM and there will be the development environment as well.

Can you guys tell what emulator configuration you used for testing ?
I can help with that, so far I'm still seeing black screen with android-23 x86 emulator

@sorccu Hi, again ) I would like to invest some time to make normal implementation for emulator (i'm targeting x86 23 for now).
I feel myself bad with current changes, because we are using all the stuff (VirtualDisplay, FrameBuffer, CpuConsumer etc.) just to tell if we have a new frame.
Maybe you can say in general words how do you think implementation should look like in your opinion? For example, should we explicitly distinguish between device and emulator?