I've build aosp_x86_64-eng target on Linux and now I can start it using emulator command. However, I'm looking for a way to "deploy" the .img files and whatever is necessary to Windows, so I could run the same emulator on Windows.
My main problem is that in out directory (out/target/product/generic_x86_64) there are a lot of things and I'm not sure which to choose and how to glue them with .ini and .prop files. I also didn't find any working tutorial or example on that topic. On the other hand I'm sure it's possible, since Google provides working emulators for Windows and they had to be build on Linux or Mac OS.
Related
I'm using VSCode as my IDE. Is there a "Device File Explorer" in VSCode just like in Android Studio?
There is none. The tools available at your disposal currently are the devtools which run in a browser and embedded in VScode for the latest version 1.20
Android Studio/IntelliJ are dedicated IDEs to develop Android applications and hence have low level functionality to interact with the file system of Android Virtual device.
I can't find an easy solution even in 2021.
At the end I do the following
adb shell
su
cd <where ever I wish>
At least I can check the files that I have created
to download
adb pull <source> <destination>
I have just started looking at Capacitor as a possible solution to package my hybrid apps in an electron shell. This is the first time I have used Electron, so really know very little about it's details.
I ran through the following steps..
1. Create new Ionic app
2. install capacitor as per doco
3. run npx add electron
4. cd electron
5. npm i electron-packager -g
6. electron-packager . --platform=win32
I ended up with a subfolder electron\capacitor-app-win32-x64that contained an executable, which ran fine on both my dev machine (Windows 10 x64), and another Windows (Windows Server 2008 R2 Standard x64).
My ultimate target device is a specialised small ruggedised tablet, that runs Windows 7 Embedded 32 bit.
It does not run on this, I get The version of this file is not compatible with the version of Windows you're running. I am not even sure if the build app is managed or unmanaged (assuming unmanaged?)
So, I would like to know what is not compatible about the Windows machine. Initial questions are
How do I Know what "bitness" the Electron app is (ie 32 bit, 64 bit, or is it .net to is like "any cpu"). I can't see where to find out this information (dotpeek won't open the exe, and opening the exe in Visual Studio, I don't see much information)
Could it be it is not build for the correct CPU?
Is there some other dependency that perhaps the embedded Windows 7 has not got
Any help is how to figure this out would be great!
[UPDATE1]
Following some advice as given here, it appears it is a 64 bit application, which is strange as the command electron-packager . --platform=win32 appear to indicate we want a 32 bit. So that may be my problem.
Does anyone know how to make it build to 32bit?
Found the problem. Just need to add a --arch=ia32 to get 32 bit.
So my complete build command was
electron-packager . --platform=win32 --arch=ia32
and it is now 32 bit and runs on the 32 bit machine.
I have installed sdk with ide for webOS TV. I have installed emulator and run it before running webOS TV IDE. However doesn't matter how I try I can't connect to emulator devices. I have the following error:
First, you must run the .vbox file (LG_webOS_TV_Emulator) from Emulator installed directory folder.
If you are using windows OS for example, directory
C:webOS_TV_SDK\Emulator\v3.00\ (.vbox) file
then you can connect to emulator
I run into the same problem, cannot connect the emulator into the IDE. So I've tried to skip this step.
First I've exported my project into .ipk file and then using the "menu" button on the emulated remote control, installed it directly via "App Manager". App was working fine this way.
Funnily enough, after this "workaround" the connection error was somehow fixed within the IDE.
I use eclipse IDE for developing my GWT and android apps. I would like to transition to a chromebook for my main development computer, but I can't figure out how I would get eclipse "installed". There is no chrome app version of eclipse, at least not that I can find. I do see that there are other IDEs in the chrome store, but I don't think they would have all the nifty helper plugins that eclipse has for google developers. Anybody know if a chrome version of eclipse is coming? Do others share my desire to develop on a chrome book?
Eclipse is not coming for Chrome OS. You need a JVM to run it and one of the compatible desktops for the UI widgets. So you would have to escape from Chrome OS desktop into base Linux and somehow launch a regular Linux desktop (like GTK) to have any hope of running Eclipse. Also, a typical chromebook is far too underpowered to run a full IDE.
Here are some options to consider:
Project Orion - A web based IDE from many of the same people who develop Eclipse. One of the goals is to enable Eclipse-like capabilities for platforms like iOS, Android, Chrome OS, etc. It has quite a few base IDE capabilities already, but not a lot of plugins just yet. Probably not going to see something as sophisticated as ADT for a while if ever. Google would have to implement Android emulators in JavaScript. Not an easy task.
Run Eclipse on another machine and use a remote desktop from your chromebook.
Run Eclipse Che on another machine or cloud server and use Chrome
The most straightforward and transparent way I was able to do so was to do a combination of things (some of which was mentioned in previous answers):
install crouton (alongside an ubuntu chroot) - this is not dual booting but running Ubuntu side by side with Chrome OS just alternating between both windowing systems.
install crouton chrome extension & xiwi - this enables running the X11 windows in the ubuntu chroot as native Chrome OS windows that can be easily alternated into.
install a JDK inside the ubuntu chroot.
download, mount and execute eclipse-installer.
once the eclipse distribution of choice is installed, for ease I symlinked the main eclipse executable to /usr/local/bin/eclipse and am able to run it from Chrome OS via crouton/xiwi: sudo startxiwi eclipse
Here's a screenshot of what it looks like when done:
Eclipse requires a JVM (maybe even a full-blown JDK), so there's no way to make it into a Chrome app. You could enable developer mode and try to install a Linux JDK since Chrome seems to be running Linux under the hood.
Do others share my desire to develop on a chrome book?
The solution is to load a normal linux distribution and run IDE from there. I'm using a netbook with intel n260, 1G ram, 1.6G Hz. NetBeans runs quite well. A chromebook runs more than twice faster, I'm sure it will be good enough.
As to how to load a linux, there is the Ubuntu on Cr-48 page that explains how to do it in depth. And also this very user friendly blog on arstechnica, or this blog on liliputting. They both point you eventually to the ChrUbuntu, that is a hand-re-packaged ubuntu with some scripts to ease your work.
You can install ubuntu via crouton (for more info: https://www.youtube.com/watch?v=d_MuVwJq_XQ&list=FLFel7rdB1nWQSjsJCaepEOg&index=1) and then you can install eclipse I'm not sure if you can install the ADT from the android sdk website but you can install the plugins from the eclipse website, third party developers, or if you really want to download it from the android sdk website you can probably get it to work with a little efort.
:) Enjoy
Yes! I share your desire to program on a Chromebook! While I am still a high-schooler, I am an amateur Java and Python programmer. My school provides with a class set of about 30 Chromebooks per classroom, and I didn't know how to run my code on them. I had Eclipse on my Windows desktop at home.
When I looked around online, I found something called codenvy.io. It is basically an Eclipse Che IDE that runs online. It uses Docker images to start up a workspace, runs all in the cloud, and a free account has 3 GB of RAM.
It suited my needs, and I loved it! You should check it out.
I tried to run the directx samples from ..\Windows Mobile 6 SDK\Samples\PocketPC\CPP\win32\directx\d3dm\tutorials on a Samsung Omnia and on the emulator and it doesn't work because of a deployment error.
I am using Microsoft Visual Studio 2008 and have installed Windows Mobile SDK Standard and Professional refresh.
The device is correctly plugged in and set up for active sync (I know this because other samples work, also a creating Win32 smart device application and running it works).
When I try to run a directx sample application it compiles without errors but the message:
" There were deployment errors, Continue? Yes/No" appears
If I manually copy the application from the debug folder to the device and run it from there, it works.
The same deployment error message appears if I try it on an emulator. Other applications are deploying successfully.
Is there any way to make the deployment work? Maybe there is an obscure option I need to set...
What I do is:
Connect the Mobile device to the PC,
Open Visual Studio 2008,
Open a directx sample project,
Click Run (in Debug or Release mode).
The problem with the deployment is that the file msvcr80.dll could not be found.
It was specified at the deployment options as an additional file "Project->Properties->Configuration Properties->Deployment" then "General->Additional files"
with the paths msvcr80.dll|$(BINDIR)\$(INSTRUCTIONSET)\|%CSIDL_WINDOWS%|0;
Removing it makes the deployment successful. I have only tested this on a Windows Mobile 6.1 device and with the D3DM reference driver on an WM6.1/WM6 emulator.
What I haven't figured out is where does $(BINDIR)\$(INSTRUCTIONSET) point to.
Also I don't know why msvcr80.dll is in the addition files if it is not actually needed.
Is there actually a msvcr80.dll compiled for Windows Mobile platform on an ARM cpu?
I was able to resolve this issue after doing some low-level Sysinternals Debugging. It was trying to deploy NETCFv35.Messages.EN.cab to the device and in my case it was deleted for some reason. Re-installing .NET CF fixed the issue for me. Wish VS 2008 said what file was missing instead of a generic message. Hope this helps you too.