I'm trying to develop a native application inside Android based on VHAL EVS documentation:
https://source.android.com/docs/devices/automotive/camera-hal
I'm using x86_64 emulator target. Lunch target is sdk_car_x86_64-userdebug, and I'm using the SDK emulator as a target, my Android version is 13.0.0, release 8.
My first and most difficult task is to bring up the evs default service up and running in the emulator. In theory all the codes are present in the Android source code, so I added the required services to the build:
diff --git a/common/car.mk b/common/car.mk
index cbcf55a..5897e90 100644
--- a/common/car.mk
+++ b/common/car.mk
## -18,6 +18,13 ##
PRODUCT_PACKAGES += \
android.hardware.automotive.vehicle#V1-emulator-service \
android.hardware.broadcastradio#2.0-service \
+ android.frameworks.automotive.display#1.0 \
+ android.frameworks.automotive.telemetry-V1-ndk \
+ android.hardware.automotive.evs#1.1 \
+ android.hardware.automotive.evs-V1-ndk \
+ android.hardware.automotive.evs#1.1-service \
+ android.hardware.automotive.evs-aidl-default-service \
+ evs_app \
android.hardware.audio.service-caremu
I build the target (lunch sdk_car_x86_64-userdebug, mm -j8), I prepare the emulator (/device/generic/car/tools/test_pack_avd_img.sh) and finally I execute it, voila, EVS service is not running.
Let's see logcat:
02-13 10:47:31.364 236 236 I servicemanager: Could not find android.hardware.automotive.evs.IEvsEnumerator/default in the VINTF manifest.
02-13 10:47:31.365 933 933 E CarServiceJNI: android.hardware.automotive.evs.IEvsEnumerator/default is not available.
02-13 10:47:31.365 933 933 E CarServiceJNI: Failed to initialize a service context
02-13 10:47:31.365 933 933 E CAR.EVS : Transition failed: error = -1
02-13 10:47:32.366 933 933 D CAR.EVS : Trying to connect to the EVS HAL service.
02-13 10:47:32.366 933 933 I CAR.EVS : Transition requested: UNAVAILABLE -> INACTIVE
What can be the issue? Why servicemanager cannot find the vintf manifest? I checked, the vintf manifest can be found here: /vendor/etc/vintf/manifest/manifest_android.hardware.automotive.evs#1.1-service.xml
Do you have any idea how can I progress?
I tried to use different lunch targets, but it least only sdk_car_x86_64 supports Automative OS emulator out of box.
Related
I am for the first time trying to make a website with blogdown. On running
setwd("..to-my-empty-website-directory..")
library(blogdown)
new_site(theme="yihui/hugo-xmin", dir=".")
I get the error
> new_site(theme="yihui/hugo-xmin", dir=".")
― Creating your new site
| Installing the theme yihui/hugo-xmin from github.com
trying URL 'https://github.com/yihui/hugo-xmin/archive/HEAD.tar.gz'
downloaded 68 KB
Error in dir.exists(x) : invalid filename argument
What is wrong? I have latest versions of hugo v0.103.0 and RStudio 2022.07.1 Build 554. All R packages are up-to-date. Here is Session info
> sessionInfo()
R version 4.2.1 (2022-06-23)
Platform: x86_64-apple-darwin17.0 (64-bit)
Running under: macOS Big Sur 11.7
Matrix products: default
LAPACK: /Library/Frameworks/R.framework/Versions/4.2/Resources/lib/libRlapack.dylib
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] blogdown_1.12.1
loaded via a namespace (and not attached):
[1] compiler_4.2.1 tools_4.2.1 yaml_2.3.5 knitr_1.40 xfun_0.33
This is a bug in blogdown, and I have just fixed it in the dev version. Please try the dev version:
remotes::install_github('rstudio/blogdown')
I'm trying to run my first react native app.
I followed the "getting started" tutorial, and got to the run your app section.
However, when running react-native start, its memory usage when "Loading dependency graph" goes up until it reaches 100% and crashes.
I have 16 GB of ram, which I believe should be plenty enough, and could not find a similar problem googling it.
I use android studio to emulate a device with Pie API (Level 28)
Did I get anything wrong ?
C:\Users\username\AwesomeProject>react-native start
Looking for JS files in C:\Users\username\AwesomeProject
Loading dependency graph... <--- Last few GCs --->
[5552:00000183131C4840] 3440 ms: Scavenge 73.3 (100.8) -> 58.7 (100.8) MB, 1.9 / 0.0 ms (average mu = 0.997, current mu = 0.997) allocation failure
<--- JS stacktrace --->
==== JS stack trace =========================================
0: ExitFrame [pc: 00007FF78F25982D]
1: InternalFrame [pc: 00007FF78F1CDB0B] Security context: 0x02b761800911 <JSObject>
2: next [000002B7618229A9](this=0x03d0580003f9 <JSGenerator>,0x0306a15cc069 <JSArray[18784]>)
3: asyncGeneratorStep(aka asyncGeneratorStep) [0000008A0A6D9311] [C:\Users\username\AwesomeProject\node_modules\jest-haste-map\build\index.js:193] [bytecode=000001EE8E830101 offset=11](this=0x01971d9404d1 <undef...
FATAL ERROR: Zone Allocation failed - process out of memory
This seems to be a node problem, not a module problem.
Downgrading to node v.12.4.0 maybe solve your issue
My application supported on
jdk1.7.0_76
JavaFx2.2.76_b13
Netbeans IDE
It's running successfully till Mac-OSX-HighSierra.
When I tried to run this application on Mojave using Netbeans the application crashes and giving following error.
Launching <fx:deploy> task from /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/../lib/ant-javafx.jar
jfx-deployment-script:
jfx-deployment:
jar:
objc[8382]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/bin/java (0x1018244c0) and /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/jli/./libjli.dylib (0x10b4f3480). One of the two will be used. Which one is undefined.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGILL (0x4) at pc=0x00007fff4200543b, pid=8382, tid=775
#
# JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C [CoreFoundation+0x13f43b] _CFRelease+0x434
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/rahulsharma/NetBeansProjects/CreatFXMLTst/hs_err_pid8382.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Java Result: 134
debug:
jfxsa-debug:
BUILD SUCCESSFUL (total time: 17 seconds)
We're seeing the exact same crash in Firefox (illegal instruction at that address), it's probably an issue in CoreFoundation:
Firefox crashes # CoreFoundation+0x13f43b
I am using gradle wrapper to run my pitest. I have parent build.gradle which has the pitest defined. My subprojects does not have any pitest. If I run the pitest on individual project for example gradlew clean :myproject:pitest. Then the pitest is successful. But if I try to run pitest from parent using gradlew clean pitest. Then it failes with the below error
> Task :pitest
4:57:34 PM PIT >> INFO : Verbose logging is disabled. If you encounter an
problem please enable it before reporting an issue.
4:57:35 PM PIT >> INFO : Sending 0 test classes to minion
4:57:35 PM PIT >> INFO : Sent tests to minion
4:57:35 PM PIT >> SEVERE : Error generating coverage. Please check that your
classpath contains JUnit 4.6 or above.
Exception in thread "main" org.pitest.util.PitError: Coverage generation
minion exited abnormally. Please check the classpath.
Please copy and paste the information and the complete stacktrace below when
reporting an issue
VM : Java HotSpot(TM) 64-Bit Server VM
Vendor : Oracle Corporation
Version : 25.152-b16
Uptime : 2390
Input ->
1 : -Dfile.encoding=windows-1252
2 : -Duser.country=US
3 : -Duser.language=en
4 : -Duser.variant
BootClassPathSupported : true
Please copy and paste the information and the complete stacktrace below when
reporting an issue
VM : Java HotSpot(TM) 64-Bit Server VM
Vendor : Oracle Corporation
Version : 25.152-b16
Uptime : 2391
Input ->
1 : -Dfile.encoding=windows-1252
2 : -Duser.country=US
3 : -Duser.language=en
4 : -Duser.variant
BootClassPathSupported : true
at
org.pitest.util.Unchecked.translateCheckedException(Unchecked.java:20)
at
org.pitest.coverage.execute.DefaultCoverageGenerator.calculateCoverage(DefaultCoverageGenerator.java:103)
at
org.pitest.coverage.execute.DefaultCoverageGenerator.calculateCoverage(DefaultCoverageGenerator.java:49)
at
org.pitest.mutationtest.tooling.MutationCoverage.runReport(MutationCoverage.java:115)
at
org.pitest.mutationtest.tooling.EntryPoint.execute(EntryPoint.java:116)
at
org.pitest.mutationtest.tooling.EntryPoint.execute(EntryPoint.java:49)
at
org.pitest.mutationtest.commandline.MutationCoverageReport.runReport(MutationCoverageReport.java:87)
at
org.pitest.mutationtest.commandline.MutationCoverageReport.main(MutationCoverageReport.java:45)
Caused by: org.pitest.util.PitError: Coverage generation minion exited
abnormally. Please check the classpath.
Please copy and paste the information and the complete stacktrace below when
reporting an issue
VM : Java HotSpot(TM) 64-Bit Server VM
Vendor : Oracle Corporation
Version : 25.152-b16
Uptime : 2390
Input ->
1 : -Dfile.encoding=windows-1252
2 : -Duser.country=US
3 : -Duser.language=en
4 : -Duser.variant
BootClassPathSupported : true
at
org.pitest.coverage.execute.DefaultCoverageGenerator.gatherCoverageData(DefaultCoverageGenerator.java:137)
at
org.pitest.coverage.execute.DefaultCoverageGenerator.calculateCoverage(DefaultCoverageGenerator.java:87)
Can any one direct what may be going wrong as I am using JUNIT 4.12 which is greater than 4.6 which is mentioned in the error.
In my experience, adding explicit dependency to Junit is needed although there are no tests in the submodule.
For me this fixed the problem:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.11</version>
<scope>test</scope>
</dependency>
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ff17a60c678, pid=4219, tid=140673779791616
#
# JRE version: Java(TM) SE Runtime Environment (8.0-b124) (build 1.8.0-ea-b124)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b66 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x665678] jni_invoke_nonstatic(JNIEnv_*, JavaValue*, _jobject*, JNICallType, _jmethodID*, JNI_ArgumentPusher*, Thread*)+0x38
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /media/data/K's World/javaFX/ChatApp/hs_err_pid4219.log
Compiled method (c1) 16675 988 3 java.util.concurrent.atomic.AtomicBoolean::set (14 bytes)
total in heap [0x00007ff16535ef50,0x00007ff16535f2a0] = 848
relocation [0x00007ff16535f070,0x00007ff16535f0a0] = 48
main code [0x00007ff16535f0a0,0x00007ff16535f1c0] = 288
stub code [0x00007ff16535f1c0,0x00007ff16535f250] = 144
metadata [0x00007ff16535f250,0x00007ff16535f258] = 8
scopes data [0x00007ff16535f258,0x00007ff16535f268] = 16
scopes pcs [0x00007ff16535f268,0x00007ff16535f298] = 48
dependencies [0x00007ff16535f298,0x00007ff16535f2a0] = 8
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#
I am writing chat App in javaFx..and I am using eclipse IDE..
My Application is running well but I don't know why suddenly application has been stopped.
It sounds like you're running JavaFX with Java 8 on Linux, and you've run into this bug:
https://bugs.openjdk.java.net/browse/JDK-8141687
App crashes while starting Main.class in JavaFx
ava version "1.8.0_60" Java(TM) SE Runtime Environment (build
1.8.0_60-b27) Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
ADDITIONAL OS VERSION INFORMATION : Mint17.2 Cinnamon 64Bit
SUGGESTION: Try a different version of Java/JavaFX.
Run sudo update-alternatives --config java to see what alternatives are already present on your system. I would downgrade to Java 1.7 if possible.
https://askubuntu.com/questions/272187/setting-jdk-7-as-default
If there are no suitable candidates, use apt-get install openjdk-7-jdk:
https://www.digitalocean.com/community/tutorials/how-to-install-java-on-ubuntu-with-apt-get
I had the same issue (except that it was java-8-oracle build 101) and found out why it was happening:
I have a login screen that appears before my main application and that screen gets closed after the login occurs and, apparently, closing it (or even hiding it) and showing a new window makes it crash.