Is there a way to build/run AOSP 11 in a headless mode? Couldn't find any Android documentation detailing how to run an AOSP without a display. for example, the documentation here details how to run Android with more than 2 displays, https://source.android.com/devices/tech/display/multi_display/displays
I am building on ASOP 11, specifically Omni ROM. Tried running the RPi4 without a display and didn't boot completely.
Any idea where to modify the codebase or settings to run it headless other than using a dummy display adapter?
Related
I installed code-server on a Pixelbook Go (x86 Intel i3 with 8GB RAM, 64 GB SSD). I installed it as a user, not a root, not sure if that's a problem or not. The code-server service is enabled and starts when I start the Developer Linux VM (penguin). As far as I know I'm upgraded to the latest Crostini (104.0.5112.83) and the VM is a Bullseye Debian, I installed it not so long ago.
Outside of the VM I started the Chrome browser and I can view the GUI portion of the code-server by visiting http://localhost:8080 (as per .config/code-server/config.yaml). I installed the Flutter and the Dart extensions in the GUI. I also opened the root folder of my Flutter project (which is a regular project (https://github.com/TrackMyIndoorWorkout/TrackMyIndoorWorkout): no embedded or multi-module things in it).
I connected my phone (OnePlus Nord, Android 12), it displayed the bottom sheet related to the connection and I allowed Transfer. The Crostini detected this connection and popped up a notification about it. I could use that notification bubble to shuttle to the connected USB devices settings and enabled the Nord device.
Here is where things started to differ from starting the "regular" VS Code (installed into the penguin VM from a package) itself: VS Code shows a device selection in the footer section, which lists target devices such as the Pixelbook Go and also the Nord (AC2003) - see screenshot later. However the GUI of the code-server doesn't have selector for the devices. When I start to initiate a debug session it displays an error message:
Unable to launch Flutter project in a Dart-only workspace. Please open a folder close to your Flutter project root or increase the value of the "dart.projectSearchDepth" setting.
Here is how it should look like in the "regular" VS Code:
I opened the root folder of the Flutter project just as I did when I use the "regular" VS Code, so this project search depth doesn't make any sense to me, the dart files are there including the main.dart in the lib folder. And the VS Code kinda works, except that the build hangs due to possibly low resources, hence I'm trying to get code-server working so I can migrate at least the VS Code GUI portion out of the anemic VM. I suspect that the main problem might not be the Flutter / Dart settings, but first I have to figure out whey the GUI doesn't show a device selector. Then I can lament on this error message if still persists.
How to proceed?
I run "ionic cordova run android" using visual studio code.. but the apps shows white screen in the emulator.. it display properly if using USB debugging.. the device also display properly if install using the apk.. the reason why I want to use emulator because I want to debug "http://10.0.2.2".. this is my emulator setting..
Emulator setting
Things that I have done is as per below
Choose ANGLE (D3D11) for OpenGL ES Renderer at the emulator advance setting
Choose Software - GLES 2.0 graphic for the Emulated Performance during create emulator
Try both R and Q for the system image during create the virtual device
Update the SDK based on the system image set at the emulator
System image selection
Issue
I compile the source code at different laptop (Laptop A) and it manage to display error at the web console using google inspect
it display "newtrustedfunctionforjit fn.bind is not a function"..
Founding
the issue is related to the chrome version 83 and the browser need an upgrade to solve the issue
The emulator is not using a browser (it using web view) hence I cannot update the google version
Solution
download new skin for newer android model into laptop A
download same skin on the laptop B (the laptop that I initially come with this post)
Below is the explanation from GitHub for angular
Explanation about the chrome issue
Below is my new System Image
Release Name S
API Level 31
ABI x86_64
Target Android 12 (Google APIs)
New System Image
When building Android,
lunch
possible images are:
...
5. aosp_x86-eng
6. aosp_x86_64-eng
...
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
...
What is exactly mini_emulator? What is the difference between mini_emulator and aosp_x86?
You can find the configurations here:
build/make/target/product/aosp_x86.mk
build/make/target/product/aosp_x86_64.mk
device/generic/mini-emulator-x86/mini_emulator_x86.mk
device/generic/mini-emulator-x86/mini_emulator_x86_64.mk
The names of these configurations mean:
aosp means a full-featured Android. Sometimes also refered to as Generic System Images.
mini means a reduced Android.
emulator means that this Android is meant to be run in the qemu-emulator.
x86 and x86_64 describe the architecture.
eng means
Development configuration with additional debugging tools
userdebug means
Like user but with root access and debug capability; preferred for debugging
I'm trying to create a Samsung Smart TV application. I have the SDK installed on my windows VM (via VMWare) and it all looks fine until you go to run the application in the emulator. It does nothing.. I even tried starting the emulators manually and here are the respect errors:
[2011]Samsung TV Emulator(2.5.1)
C:\Program Files (x86)\Samsung\Samsung TV SDK 4\Emulator\Emulator2011_v2.5\bin\Emulator2.exe
The application has failed to start because its side-by-side configuration is incorrect. Please set the application event log or use the command-line sxstrace.exe tool for more detail.
[2012]Samsung TV Emulator(3.5.2)
The application was unable to start correctly (0xc0150002). Click OK to close the application.
[2013]Samsung TV Emulator4
The application was unable to start correctly (0xc0150002). Click OK to close the application.
Extra Details
I'm running Windows 7 Pro on Mac OS using VMWare Fusion 5
So I'm not sure what to do at this point. Does anyone know of a work around? Thanks.
I had the same trouble.
Install vcredist_x86.EXE http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=26347
Exactly vcredist_x86.EXE 2.6 MB
Emulator will work on Windows 7 x64. Checked.
I'm using Eclipse Juno (build 20120920-0800) on openSUSE 12.2 to code Android applications.
I have installed the SDK by uncompressing it into my home directory (if I install the SDK via YaST package I can't download stuff unless I'm root). I installed ADT from Eclipse Marketplace, configured the path of the SDK and configured a couple of emulator configurations.
I can run and debug fine on my phone, and I guess the same applies to my tablet even if I haven't tried yet.
The real problem is that I can't run the emulator. Clicking on the bacarozzo debug icon prompts me to run the application on the device but doesn't show me available emulators.
If I open the device manager I'm shown with the virtual devices I created but I can't just start any. The progress bar reaches the end, I see no emulator screen and if I try to delete the emulator I'm warned that the instance is running... (OK in the screenshot there is only one, I already managed to delete the other)
I urge to test some GUI features in an outdated version of Android. I have done all the field tests of the business logic code in my program on a JB device and I know for sure that code works on any device.
Now I only need to be backward-compatible with preferences and layouts.
How can I start the emulator in Linux?
Just by luck I managed to run the emulator from console
djechelon#RAYNOR:~/android-sdk-linux/tools> ./emulator-arm -avd Emulator_cell
It came to life and Eclipse debug is detecting it as active device