I've got a few errors in my logcat that keep on repeating every second or so, but I don't understand where they come from ?
1539 1547 E GED : Failed to execute ioctl 3222824709, BridgeID(5), err(-1)
1539 1547 E GasService: Error on query GED info, err=1
1539 1547 E GED : Failed to execute ioctl 3222824709, BridgeID(5), err(-1)
1539 1547 E GasService: Error on query GED info, err=1
1060 1161 E ApplockRunningService.TAG: AppLockService------------->tasks = [android.app.ActivityManager$RunningTaskInfo#40598b4]
1060 1161 E ApplockRunningService.TAG: AppLockService------------->packname = com.android.launcher3
1060 1161 E ApplockRunningService.TAG: getLockFlag------------> c = android.content.ContentResolver$CursorWrapperInner#a210cdd
When listing the android services, there is no such "GasService";
there is also no "Gas" process listed with "ps".
Additional info: the process 1539 is launched by /vendor/bin/ged_srv
which is a binary file that is not visible except by root :-/
So, where do these errors come from ?
Thank you !
GasService see => GpuAppSpectatorService
native:
/system/bin/gas_srv
/system/lib/libgas.so
pkg:
com.mediatek.GpuAppSpectatorService
init:
on property:sys.boot_completed=1
start gas_srv
service gas_srv /system/bin/gas_srv
class core
user system
group system
disabled
se policy:
/system/bin/gas_srv u:object_r:gas_srv_exec:s0
Related
if I run my application on Android I always get this error and the application crashes immediately:
03-25 14:29:44.011 1833 7290 I ActivityManager: START u0 {flg=0x10000000 cmp=cz.jech.muzika/.Muzika} from uid 2000
03-25 14:29:44.093 1833 1998 I ActivityManager: Start proc 17399:cz.jech.muzika/u0a464 for activity cz.jech.muzika/.Muzika
03-25 14:29:44.098 17399 17399 E cz.jech.muzika: Not starting debugger since process cannot load the jdwp agent.
03-25 14:29:44.193 1833 2400 I WindowManager: SURFACE show Surface(name=Splash Screen cz.jech.muzika)/#0xbe60fc9: Splash Screen cz.jech.muzika
03-25 14:29:44.298 14007 17395 D InstalledAppProviderSer: insertAppIntoDb cz.jech.muzika
03-25 14:29:44.302 17399 17414 E AndroidRuntime: Process: cz.jech.muzika, PID: 17399
03-25 14:29:44.302 17399 17414 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: invalid ELF file "/data/app/cz.jech.muzika-iMRmvRSnmwPpVhRlaZJJwg==/lib/arm64/libswscale.so" load segment[4]: p_offset (0x41000) + p_filesz (0x0) ( = 0x41000) past end of file (0x40910)
03-25 14:29:44.306 1833 9531 W ActivityManager: Force finishing activity cz.jech.muzika/.Muzika
03-25 14:29:44.327 1833 4076 I ActivityManager: Process cz.jech.muzika (pid 17399) has died: vis TOP
03-25 14:29:44.336 1140 1237 W SurfaceFlinger: Attempting to destroy on removed layer: AppWindowToken{485887d token=Token{1c63ed4 ActivityRecord{a8f0c27 u0 cz.jech.muzika/.Muzika t4527}}}#0
What could be the root cause of the error? The ffmpeg libraries I use are from here. What does the error "invalid ELF file" mean?
The file /lib/arm64/libswscale.so is corrupt. In particular, it has a PT_LOAD segment with offset that is past the end of the file (file size is 0x40910) and has 0 length.
One way the file may have become corrupt is if you did an FTP transfer and forgot to set binary mode. (Of course there are numerous other ways, such as decompressing the archive and running out of disk space.)
Your best bet is to re-extract the archive, check the length and md5sum of the file, and use scp or something other than ASCII FTP transfer, then verify that the md5sum is still the same on the target device.
I am getting an error in android studio logcat which keeps on repeating itself but I have no idea where it is coming from
1539 1547 E GED : Failed to execute ioctl 3222824709, BridgeID(5), err(-1)
1539 1547 E GasService: Error on query GED info, err=1
1539 1547 E GED : Failed to execute ioctl 3222824709, BridgeID(5), err(-1)
1539 1547 E GasService: Error on query GED info, err=1
1060 1161 E ApplockRunningService.TAG: AppLockService------------->tasks = [android.app.ActivityManager$RunningTaskInfo#40598b4]
1060 1161 E ApplockRunningService.TAG: AppLockService------------->packname = com.android.launcher3
1060 1161 E ApplockRunningService.TAG: getLockFlag------------> c = android.content.ContentResolver$CursorWrapperInner#a210cdd
This is not your fault nor your problem. This is your phone's launcher app message. Look at com.android.launcher3
I followed the instructions from the realm page and did these steps:
npm install realm
react-native link realm --> For iOS everything works out without any further steps at this point.
Opened android studio and updated changes in settings.gradle, app/build.gradle and imported the RealmReactPackage in MainApplication.java
If I build and start the app, everything is working out fine. Then I add new RealmReactPackage() to the list to the other ReactPackages.
If I start the app now, the app crashes immediately. The logcat doesn't say any reason for the crash, but I add the output anyways below.
Things I tried already:
Clear caches
Restart packager
Deinstall app from emulator
Clear node-modules and run npm install again and repeat the steps from above
My setup:
"react": "16.3.1",
"react-native": "0.55.4",
"react-native-navigation": "v2.0.1937"
Node version 9.5.0
Android Studio version: 3.1.3
What I didn't do so far:
There is one instruction at the realm site under Examples:
Note that on Android, you need the NDK installed and must have set the ANDROID_NDK environment variable.
export ANDROID_NDK=/usr/local/Cellar/android-ndk/r10e
My Question is, is this relevant for my config or just for the examples?
LogCat Output:
07-03 17:51:04.909 1664 1676 I ActivityManager: START u0 {flg=0x10100000 cmp=com.cowoperation/.MainActivity} from uid 2000
07-03 17:51:04.938 1664 2392 I ActivityManager: Start proc 32299:com.cowoperation/u0a91 for activity com.cowoperation/.MainActivity
07-03 17:51:05.319 32299 32325 V FA : App package, google app id: com.cowoperation, 1:314188610363:android:2d8c823aa5045bd7
07-03 17:51:05.320 32299 32299 V fb-UnpackingSoSource: locked dso store /data/user/0/com.cowoperation/lib-main
07-03 17:51:05.320 32299 32325 I FA : adb shell setprop debug.firebase.analytics.app com.cowoperation
07-03 17:51:05.320 32299 32299 I fb-UnpackingSoSource: dso store is up-to-date: /data/user/0/com.cowoperation/lib-main
07-03 17:51:05.321 32299 32299 V fb-UnpackingSoSource: releasing dso store lock for /data/user/0/com.cowoperation/lib-main
07-03 17:51:05.654 32299 32345 I zygote : Thread[30,tid=32345,Native,Thread*=0x88b19a00,peer=0x13214b48,"Thread-8"] recursive attempt to load library "/data/app/com.cowoperation-gxY-ptC8QV3xKg796vAtEA==/lib/x86/libfb.so"
07-03 17:51:05.808 1664 1690 I ActivityManager: Displayed com.cowoperation/.MainActivity: +878ms
07-03 17:51:05.880 32299 32325 V FA : Event recorded: Event{appId='com.cowoperation', name='screen_view(_vs)', params=Bundle[{firebase_event_origin(_o)=auto, firebase_screen_class(_sc)=MainActivity, firebase_screen_id(_si)=-6439080053319785913}]}
07-03 17:51:05.979 32299 32345 E AndroidRuntime: Process: com.cowoperation, PID: 32299
07-03 17:51:05.979 32299 32345 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZN5realm8jni_util9hack_initEv" referenced by "/data/app/com.cowoperation-gxY-ptC8QV3xKg796vAtEA==/lib/x86/librealmreact.so"...
07-03 17:51:05.980 32299 32345 E UncaughtException: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZN5realm8jni_util9hack_initEv" referenced by "/data/app/com.cowoperation-gxY-ptC8QV3xKg796vAtEA==/lib/x86/librealmreact.so"...
07-03 17:51:06.074 32299 32325 V FA : Event recorded: Event{appId='com.cowoperation', name='app_exception(_ae)', params=Bundle[{firebase_event_origin(_o)=crash, firebase_screen_class(_sc)=MainActivity, firebase_screen_id(_si)=-6439080053319785913, timestamp=1530633065983, fatal=1}]}
07-03 17:51:06.153 32299 32325 V FA : Event recorded: Event{appId='com.cowoperation', name='user_engagement(_e)', params=Bundle[{firebase_event_origin(_o)=auto, engagement_time_msec(_et)=596, firebase_screen_class(_sc)=MainActivity, firebase_screen_id(_si)=-6439080053319785913}]}
07-03 17:51:06.359 1664 2392 W ActivityManager: Force finishing activity com.cowoperation/.MainActivity
07-03 17:51:06.373 1664 1684 I ActivityManager: Showing crash dialog for package com.cowoperation u0
07-03 17:51:06.569 32299 32325 V FA : Event recorded: Event{appId='com.cowoperation', name='user_engagement(_e)', params=Bundle[{firebase_event_origin(_o)=auto, engagement_time_msec(_et)=266, firebase_screen_class(_sc)=MainActivity, firebase_screen_id(_si)=-6439080053319785913}]}
I am seeing following sepolicy errors in Android-N.
W Binder:3929_E: type=1400 audit(0.0:29): avc: denied { write } for path="/dev/ttyGS0" dev="tmpfs" ino=73461 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:serial_ic:s0 tclass=chr_file permissive=0
I have created directory "vendor/qcom/sepolicy/acm/" and made its entry in BoardConfig.mk as shown below.
# ACM features belong in vendor/qcom/sepolicy
BOARD_SEPOLICY_DIRS := vendor/qcom/sepolicy/acm
Also I have commented in "device/qcom/sepolicy/common/file_contexts"
-/dev/ttyGS0 u:object_r:gadget_serial_device:s0
+#/dev/ttyGS0 u:object_r:gadget_serial_device:s0
I have changed sepolicy in following directories:
[1] vendor/qcom/sepolicy/acm/file_contexts
# These are the ports used to talk.
# We have to relabel these because domain.te has never allow rules that prevent
# any other domain (other than init or ueventd) from accessing these files
/dev/ttyGS0 u:object_r:serial_ic:s0
[2] vendor/qcom/sepolicy/acm/file.te
type serial_ic, dev_type, fs_type;
[3] vendor/qcom/sepolicy/acm/platform_app.te
allow platform_app serial_ic:chr_file { ioctl open read write };
[4] vendor/qcom/sepolicy/acm/system_server.te
#allow for acm node
allow system_server serial_ic:chr_file rw_file_perms;
[5] vendor/qcom/sepolicy/acm/untrusted_app.te
# for serial chat app
allow untrusted_app serial_ic:chr_file ioctl;
allow untrusted_app serial_ic:chr_file { read write };
[6] vendor/qcom/sepolicy/acm/system_app.te
#allow acm node
allow system_app serial_ic:chr_file { ioctl open read write};
Still I am not able to resolve "write" sepolicy error.Whenever from my serial chat application it tries to access node "/dev/ttyGS0" application crashes.
Posting logs for reference
--------- beginning of crash
01-01 07:11:46.954 15292 15292 E AndroidRuntime: FATAL EXCEPTION: main
01-01 07:11:46.954 15292 15292 E AndroidRuntime: Process: com.android.serialchat, PID: 15292
01-01 07:11:46.954 15292 15292 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
01-01 07:11:46.960 3929 8483 W ActivityManager: Force finishing activity com.android.serialchat/.SerialChat
01-01 07:11:46.965 3929 8483 D ActivityTrigger: ActivityTrigger activityPauseTrigger
01-01 07:11:46.949 8597 8597 W Binder:3929_E: type=1400 audit(0.0:29): avc: denied { write } for path="/dev/ttyGS0" dev="tmpfs" ino=73461 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:serial_ic:s0 tclass=chr_file permissive=0
I have problem with Android O HIDL. The failure log shows it can't find out the service.
However I can see it by adb shell ps -A | grep fingerprint
system 18758 1 17408 3276 pipe_wait 7c79e93e08 R android.hardware.biometrics.fingerprint#2.1-service`
Could anyone give me a hint how to solve the problem? I checked https://source.android.com/devices/architecture/hidl/ but could not get the solution.
Error log:
08-21 06:00:35.864 1890 2264 V FingerprintService: mDeamon was null, reconnect to fingerprint
08-21 06:00:35.864 1890 2264 I system_server: Looking for service android.hardware.biometrics.fingerprint#2.1::IBiometricsFingerprint/default
08-21 06:00:35.864 2240 2240 D wpa_supplicant: nl80211: Set mode ifindex 24 iftype 2 (STATION)
08-21 06:00:35.866 566 566 W /system/bin/hwservicemanager: getTransportFromManifest: Cannot find entry android.hardware.biometrics.fingerprint#2.1::IBiometricsFingerprint in either framework or device manifest, using default transport.
08-21 06:00:35.866 1890 2264 E system_server: service android.hardware.biometrics.fingerprint#2.1::IBiometricsFingerprint declares transport method EMPTY but framework expects hwbinder.
08-21 06:00:35.867 1890 2264 E FingerprintService: Failed to get biometric interface
08-21 06:00:35.867 1890 2264 E FingerprintService: android.os.RemoteException: HwBinder Error: (-2147483648)
08-21 06:00:35.867 1890 2264 E FingerprintService: at android.os.HwBinder.getService(Native Method)
08-21 06:00:35.867 1890 2264 E FingerprintService: at android.hardware.biometrics.fingerprint.V2_1.IBiometricsFingerprint.getService(IBiometricsFingerprint.java:44)
08-21 06:00:35.867 1890 2264 E FingerprintService: at com.android.server.fingerprint.FingerprintService.getFingerprintDaemon(FingerprintService.java:239)
08-21 06:00:35.867 1890 2264 E FingerprintService: at com.android.server.fingerprint.FingerprintService$FingerprintServiceWrapper.isHardwareDetected(FingerprintService.java:1198)
08-21 06:00:35.867 1890 2264 E FingerprintService: at android.hardware.fingerprint.IFingerprintService$Stub.onTransact(IFingerprintService.java:156)
08-21 06:00:35.867 1890 2264 E FingerprintService: at android.os.Binder.execTransact(Binder.java:674)
08-21 06:00:35.867 1890 2264 W FingerprintService: fingerprint HIDL not available
I've succeeded in running my fingerprint HAL on Android 8.1 executing on HiKey
96 board after modified files as below.
Firstly, it's necessary that adding HIDL configures to declare a device as a vendor or you would get VTS failed.
About HIDL configures
device/linaro/hikey/manifest.xml
+<hal format="hidl">
<name>android.hardware.biometrics.fingerprint</name>
<transport>hwbinder</transport>
<version>2.1</version>
<interface>
<name>IBiometricsFingerprint</name>
<instance>default</instance>
</interface>
</hal>
Secondly, finger service will be started after you define it in the file below.
device/linaro/hikey/device-common.mk
+#init finger service and copy
android.hardware.biometrics.fingerprint#2.1-service.rc to
system/vendor/etc/init
+PRODUCT_PACKAGES += \
+android.hardware.biometrics.fingerprint#2.1-service
+# copy permission file of finger service
+PRODUCT_COPY_FILES += \
+frameworks/native/data/etc/android.hardware.fingerprint.xml:system/etc
/permissions/android.hardware.fingerprint.xml
Finally, check finger service has been started and running in Android system by using terminal commands such as "adb shell" and "ps | grep finger".
Any suggestion is welcome.
I found out that I need to add the code to the manifest.xml
(Ref. https://source.android.com/devices/architecture/vintf/objects )
<hal format="hidl">
<name>android.hardware.biometrics.fingerprint</name>
<transport>hwbinder</transport>
<impl level="generic"></impl>
<version>2.1</version>
<interface>
<name>IBiometricsFingerprint</name>
<instance>default</instance>
</interface>
</hal>