-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build / Run Questions #1
Comments
There are some shortcomings in the Git repository! I'm not very proud of
myself. I'm going to fix it and come back to you.
…On Mon, Mar 18, 2019 at 10:37 AM Pierre Carru ***@***.***> wrote:
Hi,
Thanks for making Binder Explorer.
I'd like to run Binder Explorer on an x86_64 userdebug emulator build to
try out but I have a few questions:
Run 'mm' to insert the application on the device
Should there be an Android.mk / Android.bp in the repo then?
You can then run the application from within the ADB shell:
$ OsysBE
I ran the build process but I'm not seeing an OsysBE executable, I guess
it should be a wrapper script in order to run the nodejs app?
Cheers,
Pierre
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAiB8-7x4MKeAy-IqNU7gwG8HUY1c_n7ks5vX6TAgaJpZM4b58ZY>
.
|
We're running into limitations with Android Pie right now.
On what version of Android are you trying to run Binder Explorer?
On Tue, Apr 2, 2019 at 11:10 AM François-Denis Gonthier <
[email protected]> wrote:
… There are some shortcomings in the Git repository! I'm not very proud of
myself. I'm going to fix it and come back to you.
On Mon, Mar 18, 2019 at 10:37 AM Pierre Carru ***@***.***>
wrote:
> Hi,
>
> Thanks for making Binder Explorer.
> I'd like to run Binder Explorer on an x86_64 userdebug emulator build to
> try out but I have a few questions:
>
> Run 'mm' to insert the application on the device
> Should there be an Android.mk / Android.bp in the repo then?
>
> You can then run the application from within the ADB shell:
> $ OsysBE
> I ran the build process but I'm not seeing an OsysBE executable, I guess
> it should be a wrapper script in order to run the nodejs app?
>
> Cheers,
> Pierre
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#1>, or mute the
> thread
> <https://github.com/notifications/unsubscribe-auth/AAiB8-7x4MKeAy-IqNU7gwG8HUY1c_n7ks5vX6TAgaJpZM4b58ZY>
> .
>
|
Thanks |
Ok so there were a few things missing in the repo. The Android.mk file, the OsysBE script and the "images" directory were missing, I've added them. I've also added a line in the Android.mk that will copy .node binary node modules to /system/lib64. This is required to use private APIs within the platform. The repository is now in a state where I can be more useful if you've got problems running BE. |
Thanks! I'm trying that as soon as I get back on this subject |
Hi,
Thanks for making Binder Explorer.
I'd like to run Binder Explorer on an x86_64 userdebug emulator build to try out but I have a few questions:
Should there be an
Android.mk
/Android.bp
in the repo then?I ran the build process but I'm not seeing an OsysBE executable, I guess it should be a wrapper script in order to run the nodejs app?
Cheers,
Pierre
The text was updated successfully, but these errors were encountered: