Develop Reference

React-native app stuck on splash screen, works fine on debug mode

My react-native app is running and everything is working fine when I run it in debug mode aka with npx react-native run-android but it gets stuck on splash-screen (doesn't crash) when trying to open the release builds either with npx react-native run-android --variant=release or by exporting apk with assembleRelease command on gradle.
Here's the log I was able to get by using npx react-native log-andoid command: logs.
I can't figure it out what's the issue, is it regarding react-native-gesture-handler? If yes, then why this error/log doesn't come up in debug builds?
Edit: This log appears in android studio:
2022-05-27 08:42:48.087 0-0/? E/init: updatable process 'console' exited 4 times in 4 minutes
2022-05-27 08:42:48.093 0-0/? I/init: processing action (sys.init.updatable_crashing=1) from (/system/etc/init/flags_health_check.rc:10)
2022-05-27 08:42:48.094 0-0/? I/init: starting service 'exec 3578 (/system/bin/flags_health_check UPDATABLE_CRASHING)'...
2022-05-27 08:42:48.097 0-0/? I/init: SVC_EXEC service 'exec 3578 (/system/bin/flags_health_check UPDATABLE_CRASHING)' pid 2148 (uid 1000 gid 1000+0 context default) started; waiting...
2022-05-27 08:42:48.118 2148-2148/? I/flags_health_check: ServerConfigurableFlagsReset reset_mode value: 1
2022-05-27 08:42:48.118 2148-2148/? I/flags_health_check: ServerConfigurableFlagsReset updatable crashing detected, resetting flags.
2022-05-27 08:42:48.102 0-0/? I/init: Service 'exec 3578 (/system/bin/flags_health_check UPDATABLE_CRASHING)' (pid 2148) exited with status 0 waiting took 0.005000 seconds
2022-05-27 08:42:48.105 0-0/? I/init: Sending signal 9 to service 'exec 3578 (/system/bin/flags_health_check UPDATABLE_CRASHING)' (pid 2148) process group...
2022-05-27 08:42:48.107 0-0/? I/libprocessgroup: Successfully killed process cgroup uid 1000 pid 2148 in 0ms
2022-05-27 08:42:48.330 491-491/? E/netmgr: qemu_pipe_open_ns:62: Could not connect to the 'pipe:qemud:network' service: Invalid argument
2022-05-27 08:42:48.330 491-491/? E/netmgr: Failed to open QEMU pipe 'qemud:network': Invalid argument
2022-05-27 08:42:48.640 495-495/? E/wifi_forwarder: qemu_pipe_open_ns:62: Could not connect to the 'pipe:qemud:wififorward' service: Invalid argument
2022-05-27 08:42:48.640 495-495/? E/wifi_forwarder: RemoteConnection failed to initialize: RemoteConnection failed to open pipe
2022-05-27 08:42:51.339 0-0/? E/ICMPv6: RA: ndisc_router_discovery failed to add default route
2022-05-27 08:42:53.074 0-0/? I/init: starting service 'console'...
2022-05-27 08:42:53.087 0-0/? I/init: Service 'console' (pid 2152) exited with status 0
2022-05-27 08:42:53.091 0-0/? I/init: Sending signal 9 to service 'console' (pid 2152) process group...
2022-05-27 08:42:53.094 0-0/? I/libprocessgroup: Successfully killed process cgroup uid 2000 pid 2152 in 0ms
2022-05-27 08:42:53.098 0-0/? E/init: updatable process 'console' exited 4 times in 4 minutes
And in project errors this log

try to run your project with Android Studio, i think you will get some errors here

try adding org.codehaus.groovy:groovy-json:3.0.10 in your dependency list in the app level build.gradle
dependencies {
implementation 'org.codehaus.groovy:groovy-json:3.0.10'
}

Well, after 3 days of suffering I found out what's wrong.
So, a couple of days ago I opened the project on Android Studio and clicked on a popup that said upgrade gradle version which ended up updating my gradle version from 7.0.4 to 7.1.2 causing these problems😢

audio-hal-2-0 not found on booting in android

I'm building android 9 for the Resenas Rcar-H3 board. The building process is successful. But after flash images into the board, The booting process doesn't work correctly. audioserver is restarted by init process and notify several errors like below:
[ 737.947862] init: Service 'audioserver' (pid 2734) exited with status 1
[ 737.954674] init: Sending signal 9 to service 'audioserver' (pid 2734) process group...
[ 737.962915] libprocessgroup: Successfully killed process cgroup uid 1041 pid 2734 in 0ms
[ 737.971171] init: Command 'restart vendor.audio-hal-2-0' action=onrestart (<Service 'audioserver' onrestart>:1) took 0ms and failed: service vendor.audio-hal-2-0 not found
[ 737.986524] init: Command 'restart audio-hal-2-0' action=onrestart (<Service 'audioserver' onrestart>:2) took 0ms and failed: service audio-hal-2-0 not found
[ 742.929725] init: starting service 'audioserver'...
[ 742.964835] init: Service 'audioserver' (pid 2735) exited with status 1
[ 742.971523] init: Sending signal 9 to service 'audioserver' (pid 2735) process group...
[ 742.979681] libprocessgroup: Successfully killed process cgroup uid 1041 pid 2735 in 0ms
[ 742.987951] init: Command 'restart vendor.audio-hal-2-0' action=onrestart (<Service 'audioserver' onrestart>:1) took 0ms and failed: service vendor.audio-hal-2-0 not found
[ 743.003317] init: Command 'restart audio-hal-2-0' action=onrestart (<Service 'audioserver' onrestart>:2) took 0ms and failed: service audio-hal-2-0 not found
[ 747.946500] init: starting service 'audioserver'...
[ 747.981024] init: Service 'audioserver' (pid 2736) exited with status 1
[ 747.987697] init: Sending signal 9 to service 'audioserver' (pid 2736) process group...
[ 747.995844] libprocessgroup: Successfully killed process cgroup uid 1041 pid 2736 in 0ms
[ 748.004108] init: Command 'restart vendor.audio-hal-2-0' action=onrestart (<Service 'audioserver' onrestart>:1) took 0ms and failed: service vendor.audio-hal-2-0 not found
...
Can anyone help me? Thank All!

It looks as if you told init to start vendor.audio-hal-2-0 but did not provide the service definition.
In one of your installed .rc-files there might be a call like this:
start vendor.audio-hal-2-0
You should also have a service definition file that looks somewhat like this:
service vendor.audio-hal-2-0 /vendor/bin/hw/<binary>
<options>
If you don't then you need to create one and if you do it is probably not installed correctly. You can install additional service files in your Android.bp module definition like this:
cc_binary {
[ ... ]
init_rc: [ "vendor.audio-hal-2-0.rc" ],
[...]
}

Android Virtual Device - Black screen and I've tried everything

This is a fresh install of Android Studios on Ubuntu 16.04.
I just get a black screen on the AVD every time. I been reading related threads tried the following:
Changing to software gpu
many different device profiles
many different andoid system image versions
wiping the user data for the device
both x86 and arm images
both the x86 and x64 emulators
various amount of RAM for each device
running with no skins
And more things that I can't recall right now.
The qemu process does start and consume quite a bit of CPU time, but nothing ever happens. No error messages either. Just hangs up.
My i5 processor does have virtualization support as well.
Before I break down and install windows to get this working, is there anything else I can try?
EDIT: The kernel does boot but enters an infinite loop repeating these messages:
[ 117.942709] init: property_set("ro.boottime.wificond", "117942505853") failed: property already set
[ 117.964867] init: starting service 'netd'...
[ 117.965726] init: property_set("ro.boottime.netd", "117965553859") failed: property already set
[ 117.974155] init: Created socket '/dev/socket/netd', mode 660, user 0, group 1000
[ 117.975147] init: Created socket '/dev/socket/dnsproxyd', mode 660, user 0, group 3003
[ 117.976174] init: Created socket '/dev/socket/mdns', mode 660, user 0, group 1000
[ 117.977136] init: Created socket '/dev/socket/fwmarkd', mode 660, user 0, group 3003
[ 117.989764] init: starting service 'zygote'...
[ 118.000458] init: property_set("ro.boottime.zygote", "118000275846")
failed: property already set
[ 118.010134] init: no such service 'wpa_supplicant'
[ 118.011053] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[ 122.394998] init: starting service 'surfaceflinger'...
[ 122.396072] init: property_set("ro.boottime.surfaceflinger", "122395874175") failed: property already set
[ 122.397299] init: Failed to bind socket 'pdx/system/vr/display/client': No such file or directory
[ 122.398293] init: Failed to bind socket 'pdx/system/vr/display/manager': No such file or directory
[ 122.399281] init: Failed to bind socket 'pdx/system/vr/display/vsync': No such file or directory
[ 122.454693] healthd: battery l=100 v=5000 t=25.0 h=2 st=2 chg=a
[ 122.486518] init: Service 'surfaceflinger' (pid 2847) killed by signal 6
[ 122.487278] init: Sending signal 9 to service 'surfaceflinger' (pid 2847) process group...
[ 122.488207] init: Successfully killed process cgroup uid 1000 pid 2847 in 0ms
[ 122.489051] init: Sending signal 9 to service 'zygote' (pid 2815) process group...
[ 122.498945] init: Successfully killed process cgroup uid 0 pid 2815 in 9ms
[ 122.500398] init: Service 'zygote' (pid 2815) killed by signal 9
[ 122.501398] init: Unable to open '/sys/android_power/request_state': No such file or directory
[ 122.502779] init: Unable to write to '/sys/power/state': Invalid argument
[ 122.503869] init: Sending signal 9 to service 'audioserver' (pid 2804) process group...
[ 122.511295] init: Successfully killed process cgroup uid 1041 pid 2804 in 6ms
[ 122.513308] init: Sending signal 9 to service 'cameraserver' (pid 2805) process group...
[ 122.521445] init: Successfully killed process cgroup uid 1047 pid 2805 in 6ms
[ 122.522669] init: Sending signal 9 to service 'media' (pid 2806) process group...
[ 122.530468] init: Successfully killed process cgroup uid 1013 pid 2806 in 6ms
[ 122.531675] init: Sending signal 9 to service 'netd' (pid 2814) process group...
[ 122.539229] init: Successfully killed process cgroup uid 0 pid 2814 in 6ms
[ 122.540805] init: Sending signal 9 to service 'wificond' (pid 2812) process
group...
[ 122.548870] init: Successfully killed process cgroup uid 1010 pid 2812 in 6ms
[ 122.550996] init: Service 'audioserver' (pid 2804) killed by signal 9
[ 122.552127] init: Sending signal 9 to service 'audio-hal-2-0' (pid 2807) process group...
[ 122.559507] init: Successfully killed process cgroup uid 1041 pid 2807 in 6ms
[ 122.561085] init: Service 'cameraserver' (pid 2805) killed by signal 9
[ 122.562292] init: Service 'media' (pid 2806) killed by signal 9
[ 122.563413] init: Service 'audio-hal-2-0' (pid 2807) killed by signal 9
[ 122.564576] init: Service 'wificond' (pid 2812) killed by signal 9
[ 122.565608] init: Service 'netd' (pid 2814) killed by signal 9
[ 122.566673] init: Untracked pid 2858 exited with status 0
[ 122.567567] init: Untracked pid 2817 killed by signal 9
[ 122.568495] init: Untracked pid 2818 killed by signal 9
[ 122.569442] init: processing action (init.svc.zygote=stopping) from
(/system/etc/init/bootstat.rc:62)
[ 122.578092] init: starting service 'audioserver'...
[ 122.579401] init: property_set("ro.boottime.audioserver", "122579133766") failed: property already set
[ 122.580660] init: starting service 'cameraserver'...
[ 122.581377] init: property_set("ro.boottime.cameraserver", "122581249935") failed: property already set
[ 122.582626] init: starting service 'media'...
[ 122.583276] init: property_set("ro.boottime.media", "122583158219") failed: property already set
[ 122.600086] init: couldn't write 2865 to /dev/cpuset/camera-daemon/tasks: No such file or directory
[ 122.870197] init: starting service 'audio-hal-2-0'...
[ 122.871067] init: property_set("ro.boottime.audio-hal-2-0", "122870905135") failed: property already set
[ 122.920102] binder: 2864:2864 transaction failed 29189/-22, size 32-0 line 2936
[ 122.921441] binder: 2864:2864 transaction failed 29189/-22, size 32-0 line 2936
[ 122.942631] init: starting service 'wificond'...
[ 122.943501] init: property_set("ro.boottime.wificond", "122943322473") failed: property already set
[ 122.965669] init: starting service 'netd'...
[ 122.966468] init: property_set("ro.boottime.netd", "122966306126") failed: property already set
[ 122.971540] init: Created socket '/dev/socket/netd', mode 660, user 0, group 1000
[ 122.972491] init: Created socket '/dev/socket/dnsproxyd', mode 660, user 0, group 3003
[ 122.973386] init: Created socket '/dev/socket/mdns', mode 660, user 0, group 1000
[ 122.974265] init: Created socket '/dev/socket/fwmarkd', mode 660, user 0, group 3003
[ 123.002232] init: no such service 'wpa_supplicant'
[ 123.002902] init: starting service 'zygote'...
[ 123.003738] init: property_set("ro.boottime.zygote", "123003531647") failed: property already set
[ 123.009193] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000

Looks like the kernel is not booting.
try to run this command to see some messages.
cd /path/to/your/sdk/emulator-official
./emulator -show-kernel -avd your-avd-name
Please try the following command to use guest gpu:
./emulator -show-kernel -gpu guest -avd your-avd-name

from: \users\yourUsername\AppData\Local\Android\sdk\platform-tools‌​\
execute following command:
emulator -avd yourAvdDeviceName -netdelay none -netspeed full

Android-emulator boot stuck in “QEMU Pipe Device:rw, wait_event error”

I am trying to compile goldfish android kernel and run it with emulator. I did everything as the Google told me.(Android kernel compile and test with Android Emulator, How to compile android goldfish 3.4 kernel and run on emulator)。
yesterday，I follow the tips, and lunch the android-emulator successfully. But today when I launch the emulator again, it does not work. the boot log shows it stuck in "QEMU Pipe Device:rw, wait_event error", who can help me ? thanks in advance sincerely.
environment： VMware10， ubuntu14.04，goldfish3.4，ASOP_arm，Android4.4
the part of boot log:
Freeing init memory: 148K
type=1403 audit(1445259070.600:2): policy loaded auid=4294967295 ses=4294967295
SELinux: Loaded policy from /sepolicy
type=1404 audit(1445259070.620:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: /dev/hw_random not found
init: cannot open '/initlogo.rle'
EXT4-fs (mtdblock0): mounted filesystem with ordered data mode. Opts: barrier=1
EXT4-fs (mtdblock1): VFS: Can't find ext4 filesystem
fs_mgr: Running /system/bin/e2fsck on /dev/block/mtdblock1
e2fsck: executing /system/bin/e2fsck failed: No such file or directory
e2fsck: e2fsck terminated by exit(255)
EXT4-fs (mtdblock1): VFS: Can't find ext4 filesystem
fs_mgr: Cannot mount filesystem on /dev/block/mtdblock1 at /data
init: fs_mgr_mount_all returned an error
init: /dev/hw_random not found
init: Unable to open persistent property directory /data/property errno: 2
type=1400 audit(1445259074.030:4): avc: denied { entrypoint } for pid=36 comm="init" path="/sbin/healthd" dev="rootfs" ino=1232 scontext=u:r:healthd:s0 tcontext=u:object_r:rootfs:s0 tclass=file
healthd: wakealarm_init: timerfd_create failed
healthd: BatteryVoltagePath not found
healthd: BatteryTemperaturePath not found
binder: 36:36 transaction failed 29189, size 0-0
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
type=1405 audit(1445259074.370:5): bool=in_qemu val=1 old_val=0 auid=4294967295 ses=4294967295
avc: received policyload notice (seqno=2)
init: property 'sys.powerctl' doesn't exist while expanding '${sys.powerctl}'
init: powerctl: cannot expand '${sys.powerctl}'
init: property 'sys.sysctl.extra_free_kbytes' doesn't exist while expanding '${sys.sysctl.extra_free_kbytes}'
init: cannot expand '${sys.sysctl.extra_free_kbytes}' while writing to '/proc/sys/vm/extra_free_kbytes'
type=1400 audit(1445259075.370:6): avc: denied { 0x10 } for pid=36 comm="healthd" capability=36 scontext=u:r:healthd:s0 tcontext=u:r:healthd:s0 tclass=capability2
eth0: link up
warning: `rild' uses 32-bit capabilities (legacy support in use)
shell#generic:/ $ QEMU Pipe Device:rw, wait_event error
QEMU Pipe Device:rw, wait_event error
QEMU Pipe Device:rw, wait_event error
QEMU Pipe Device:rw, wait_event error
QEMU Pipe Device:rw, wait_event error

I solved it by myself. the reason of this error is because of the switch parameter of android-emulator. so if you do like this:
root#virtual-machine:/work/android4.4/out/target/product/generic# mv userdata.img userdata.img.bak
and then restart the emulator, emulator can not use that the userdata.img.
all because of the userdata.img. the detail of this I do not know. maybe someone will tell us in future.

Error creating imagefile (Read-only file system)

First of all this is not duplicate question and I have tried solutions from other similar threads but it looks like this case is different.
In my case I can successfully install and run other android project from the same emulator (x86 also tried arm) but this particular app project throws following error when installing also manually "adb install" from inside shell do not work either.
One of the error from log below is found (line number 232)
https://android.googlesource.com/platform/system/vold/+/froyo/Loop.cpp
However I do not know if the error "No content provider..." is related to the same error stack.
If it had the write-permission error (sdcard or file system permission like that) then other apps should also not install!
This problematic app is a NDK project with a custom content provider which I tried omitting but no avail. it seems like content provider error is related to apk installation from os and not really the content provider from within the app.
I am tired of testing with a real device, I am worried this would degrade my phones life because I had to do it very often.
--------- beginning of /dev/log/main
D/AndroidRuntime( 1977):
D/AndroidRuntime( 1977): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
W/linker ( 1977): libdvm.so has text relocations. This is wasting memory and is a security risk. Please fix.
D/AndroidRuntime( 1977): CheckJNI is ON
D/dalvikvm( 1977): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 1977): Added shared lib libjavacore.so 0x0
D/dalvikvm( 1977): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 1977): Added shared lib libnativehelper.so 0x0
D/dalvikvm( 1977): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
D/dalvikvm( 1977): Note: class Landroid/app/ActivityManagerNative; has 179 unimplemented (abstract) methods
E/memtrack( 1977): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug( 1977): failed to load memtrack module: -2
D/AndroidRuntime( 1977): Calling main entry com.android.commands.pm.Pm
E/PackageHelper( 1680): Failed to create secure container smdl2tmp1
--------- beginning of /dev/log/system
W/ActivityManager( 1149): No content provider found for permission revoke: file:///data/local/tmp/myapp.apk
E/Vold ( 932): Error creating imagefile (Read-only file system)
E/Vold ( 932): ASEC image file creation failed (Read-only file system)
W/Vold ( 932): Returning OperationFailed - no handler for errno 30
E/DefContainer( 1680): Failed to create container smdl2tmp1
W/ActivityManager( 1149): No content provider found for permission revoke: file:///data/local/tmp/myapp.apk
D/dalvikvm( 1149): GC_EXPLICIT freed 161K, 22% free 5442K/6948K, paused 1ms+1ms, total 8ms
D/AndroidRuntime( 1977): Shutting down VM

The problem might be either from:
an Android AOSP bug or a bug in the ROM you are using
(misconfiguration)
something has caused the partition where the apps installed on the SD Card (or an emulated internal card) are stored, to be read only
"Apps on SD card are stored in an encrypted container for platform security purposes -- so that other applications can not modify or corrupt them. When mounting the SD card, these containers are mounted so that they can be accessed in the same way as apps stored in internal storage."
On your stacktrace the problem is this:
E/Vold ( 932): Error creating imagefile (Read-only file system)
E/Vold ( 932): ASEC image file creation failed (Read-only file
system)
I've had a similar problem with an application that had defined in its AndroidManifest.xml the android:installLocation="preferExternal" and the following things worked for me (done independently of one another):
I/qtaguid ( 6299): Failed write_ctrl(u 40) res=-1 errno=22
I/qtaguid ( 6299): Untagging socket 40 failed errno=-22
W/NetworkManagementSocketTagger( 6299): untagSocket(40) failed with errno -22
D/Finsky ( 6299): [1] 2.onResponse: Verification id=29 response=0
D/Finsky ( 6299): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 29
E/Vold ( 127): Error creating imagefile (Read-only file system)
E/Vold ( 127): ASEC image file creation failed (Read-only file system)
W/Vold ( 127): Returning OperationFailed - no handler for errno 30
E/PackageHelper( 6280): Failed to create secure container smdl733025106.tmp
W/DefContainer( 6280): Failed to copy package at /storage/emulated/0/myapp.apk
W/DefContainer( 6280): java.io.IOException: Failed to create container smdl733025106.tmp
W/DefContainer( 6280): at com.android.defcontainer.DefaultContainerService.copyPackageToContainerInner(DefaultContainerService.java:327)
W/DefContainer( 6280): at com.android.defcontainer.DefaultContainerService.access$000(DefaultContainerService.java:67)
W/DefContainer( 6280): at com.android.defcontainer.DefaultContainerService$1.copyPackageToContainer(DefaultContainerService.java:108)
W/DefContainer( 6280): at com.android.internal.app.IMediaContainerService$Stub.onTransact(IMediaContainerService.java:60)
W/DefContainer( 6280): at android.os.Binder.execTransact(Binder.java:446)
As per https://developer.android.com/guide/topics/data/install-location.html change to android:installLocation="auto"
As per http://forum.xda-developers.com/showpost.php?p=58409922&postcount=4845 If you want to install it to "internal device storage", regardless of what the manifest says or what the system decides.
Go to Settings > Apps > Open the menu > Preferred install location >
set it to "Internal device storage". I had this set to "Let the system
decide". This caused some of the APKs to fail the install, because
they were marked to prefer the SD card as their installation location
and thus they tried to install onto the SD and it just failed. Now
that everything installs on the device, it works just fine.
If you want to install it to the "external storage"
adb root
adb shell
mount -o rw,remount rootfs /
chmod 777 /mnt/sdcard
pm install /mnt/sdcard/myapp.apk
mount -o ro,remount rootfs /
As per https://code.google.com/p/android/issues/detail?id=9593
&& http://www.androidpolice.com/2011/04/19/fixing-the-couldnt-install-on-usb-storage-or-sd-card-problem-on-android/
Only if you are able to find the smdl2tmp1.asec at the following paths
or you get error
smdl2tmp1 03-24 18:48:38.784: ERROR/Vold(86): ASEC file '/mnt/secure/asec/smdl2tmp1.asec' currently exists - destroy it first! (Address already in use)
adb root
adb shell rm /sdcard/.android_secure/smdl2tmp1.asec
adb shell rm /mnt/secure/asec/smdl2tmp1.asec

In my case I'm using a device with Android version 6, developing for Unity.
I am getting the same error when installing the app directly from the Unity Editor, this will not happen if i do upload the app to the android Game Play Developer console as a Beta version and then download and install it from there, in this case android will do needed encryption and install the app successfully.
My solution to do direct install was to set in the :
android build -> Player Settings > Install location -> to Force Internal

In addtion to #Mnemoinc's answer:
If you want to force the install to the "internal storage"
adb root
adb shell
pm install -f /sdcard/myapp.apk
This could be useful when using Cyanogenmod and having a secure storage.