I have a Nexus 4 with Android 6.0 and i have connected it in Developer Mode to my Android Studio to see what the Log-File output looks like. The LogCat sends many errors:
1. 02-25 09:15:46.787 548-623/? E/WifiStateMachine: WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0,00 rxSuccessRate=0,00 targetRoamBSSID=any RSSI=-53
2. 02-25 09:15:46.787 548-623/? E/WifiStateMachine: WifiStateMachine L2Connected CMD_START_SCAN source -2 226, 227 -> obsolete
3. 02-25 09:15:36.955 3609-3609/? E/JavaBinder: !!! FAILED BINDER TRANSACTION !!!
4. 02-25 09:15:28.154 195-218/? E/ANDR-PERF-LOCK: Failed to apply optimization for resource: 4 level: 0
5. 02-25 09:15:27.479 548-623/? E/WifiStateMachine: cancelDelayedScan -> 227
6. 02-25 09:15:27.483 548-623/? E/native: do suspend true
7. 02-25 09:14:42.632 188-31249/? E/ACDB-LOADER: Error: ACDB AudProc vol returned = -8
8. 02-25 09:16:36.436 1596-1596/? E/ctxmgr: [PowerConnectionProducer]Could not write powerInfo=Plug state: 2 BatteryLevel: 0.85, status=Status{statusCode=unknown status code: 7503, resolution=null}
What are all these errors? They are appearing over and over again in different orders and are appearing independent from each other.
The Error:
02-25 09:18:36.981 3609-3609/? E/JavaBinder: !!! FAILED BINDER TRANSACTION !!!
Appears each 10 seconds even when there is no app active and all background proceses of all apps are killed.
Many apps running the background log the actions being done. Some of them also raises errors. WifiStateMachine gives data about your Wifi connection, PowerConnectionProducer gives data about your battery and so on. You will get errors similar to these on all devices.
This is no reason to worry, unless you have an error associated with your own app.
These are system logs,which you see after connecting your device.
This Binder transaction buffer has a limited fixed size, currently 1Mb, which is shared by all transactions in progress for the process. Consequently this exception can be thrown when there are many transactions in progress.
Please refer to TransactionTooLarge
Related
After some troubleshooting with updating the video solution to Android API 30, I have finally ended up with the following Logcat error after having upgraded Exoplayer to 2.12.0 and imported guava:30.0-jre:
[OMX.android.goldfish.h264.decoder] setPortMode on output to DynamicANWBuffer failed w/ err -1010
E/FMQ: grantorIdx must be less than 3
E/FMQ: grantorIdx must be less than 3
E/ion: ioctl c0044901 failed with code -1: Inappropriate ioctl for device
E/FMQ: grantorIdx must be less than 3
I have also replaced SimpleExoPlayerView with PlayerView as it caused Inflating class error as described in my previous thread here: Inflating class error with Exoplayer 2.12.0 on Android
Was just wondering if anyone here had a clue for this one. Thanks in advance.
EDIT: I also receive Emulator: Process finished with exit code -1073741571 (0xC00000FD) every time I try to access the video solution. A colleague tried to replicate the error using Linux and it looked like it worked for him.
EDIT2: It looks like it is mainly due to qemu_system-x86-64.exe stops working, which is mainly a Windows-file, so I conclude with this being a bug in Windows rather than Android.
I am getting this error -
A/libc: Fatal signal 31 (SIGSYS), code 1 in tid 4168 (m.messagingdapp)
When I upgrade my app from API 24 to 26 (have to do to get java.nio.file features). It is the only error that I can see in my logcat. It works fine when running with API 24. It gets the error when accessing an API I'm using called go-ethereum on this line -
String f = this.getFilesDir() + "/.ethereum";
Long n = Geth.LightScryptN;
Long p = Geth.LightScryptP;
AccountManager am = Geth.newAccountManager(f, n, p); //HERE
There seem to be lots of other errors on different parts of the logcat in the drop down menu i.e system_process. However, I am new to android and don't really know what I am looking for (I have googled all of them separately but have gotten no fix). Thanks.
Full lolcat -
07-25 22:17:14.774 9625-9625/? I/zygote: Not late-enabling -Xcheck:jni
(already on)
07-25 22:17:14.825 9625-9625/? W/zygote: Unexpected CPU variant for X86
using defaults: x86
07-25 22:17:15.181 9625-9625/benkrarup.ethereum.messagingdapp W/zygote:
Class android.support.v4.util.SimpleArrayMap failed lock verification
and will run slower.
07-25 22:17:15.181 9625-9625/benkrarup.ethereum.messagingdapp W/zygote:
Common causes for lock verification issues are non-optimized dex code
07-25 22:17:15.181 9625-9625/benkrarup.ethereum.messagingdapp W/zygote:
and incorrect proguard optimizations.
07-25 22:17:15.184 9625-9625/benkrarup.ethereum.messagingdapp W/zygote:
Class cz.msebera.android.httpclient.conn.util.PublicSuffixMatcherLoader
failed lock verification and will run slower.
07-25 22:17:15.191 9625-9625/benkrarup.ethereum.messagingdapp
D/NetworkSecurityConfig: No Network Security Config specified, using
platform default
07-25 22:17:15.216 9625-9625/benkrarup.ethereum.messagingdapp
W/Java7Support: Unable to load JDK7 types (annotations,
java.nio.file.Path): no Java7 support added
07-25 22:17:15.596 9625-9657/benkrarup.ethereum.messagingdapp A/libc:
Fatal signal 31 (SIGSYS), code 1 in tid 9657 (m.messagingdapp)
Android 8 O (SDK 26) limits which system calls are allowed for security reasons by enabling a feature called secure computing in the Linux kernel.
This means only whitelisted calls can be executed and that any other call will result in signal 31 (SIGSYS), code 1 (SYS_SECCOMP), like you are experiencing. You will need to examine the stack trace of this signal to find out which system call was not allowed (which was not listed completely in your question).
You can find a list of allowed calls here. Any other call is not allowed.
You can find what Google wrote about this here.
My Android cordova-based app crashes on an Motorola Droid Turbo 2, Android Version 6.0. The app runs fine on many other devices/platforms - including my android phone. I can crash the app by making a selection in a completely barebones dropdown.
ADDITIONAL DETAILS (new 5/27/16): 1.) The app does not always crash the first time. Sometimes he can tap on 2 or 3 dropdowns. 2.) The user has another app on his phone, which I built with the same architecture, and it runs fine.
UPDATE: I finally followed USKMobility's tip and handled the whitelist error I had been getting, and got different message right before the app crashes. I have updated them in the block below.
Here are the crucial logcat lines. They start with when I tap the dropdown.
04-30 11:28:26.619: W/Adreno-GSL(9728): <gsl_ldd_control:475>: ioctl fd 38 code 0x40180917 (IOCTL_KGSL_CMDSTREAM_FREEMEMONTIMESTAMP_CTXTID) failed: errno 22 Invalid argument
04-30 11:28:26.620: W/Adreno-GSL(9728): <gsl_ldd_control:475>: ioctl fd 38 code 0x40180917 (IOCTL_KGSL_CMDSTREAM_FREEMEMONTIMESTAMP_CTXTID) failed: errno 16 Device or resource busy
04-30 11:28:26.635: I/Adreno(9728): DequeueBuffer: dequeueBuffer failed
04-30 11:28:26.692: W/google-breakpad(9728): Microdump crash handler failed.
04-30 11:28:26.707: A/libc(9728): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x7f576c0000 in tid 9780 (Chrome_InProcGp)
Another update is that I the app no longer crashes consistently on the first time I use a dropdown. Sometimes I can use 3-5 dropdowns before it crashes. Ideas?
On Nexus 4, with Android 5.1.1 I have the following problem that drives me mad:
When trying to record the screen (on Kubuntu 15.04) with:
adb shell screenrecord --verbose /sdcard/Download/intro9.mp4
just few seconds (1-4) are recorded and then recording stops by itself.
In the logcat there is relevant output:
09-16 14:12:46.943 5733-5742/? I/OMXClient﹕ Using client-side OMX mux.
09-16 14:12:46.946 188-4537/? E/OMX-VENC-720p﹕ Is component secure 0
09-16 14:12:46.969 188-188/? E/OMX-VENC-720p﹕ set_parameter: metamode is valid for input port only
09-16 14:12:46.969 188-188/? E/OMXNodeInstance﹕ setParameter(50:qcom.encoder.avc, OMX.google.android.index.storeMetaDataInBuffers(0x7f00001c): Output:1 en=0 GB=0) ERROR: UnsupportedSetting(0x80001019)
09-16 14:12:46.969 5733-5742/? E/ACodec﹕ [OMX.qcom.video.encoder.avc] storeMetaDataInBuffers (output) failed w/ err -1010
09-16 14:12:46.971 188-4537/? E/OMX-VENC-720p﹕ WARNING: Unsupported Color format [2130708361]
09-16 14:12:46.972 188-4537/? E/OMX-VENC-720p﹕ C2D init is successful
09-16 14:12:46.972 188-188/? E/OMX-VENC-720p﹕ WARNING: Unsupported Color format [2130708361]
09-16 14:12:46.973 188-5092/? E/OMX-VENC-720p﹕ venc_set_intra_period: nPFrames = 600 nBFrames = 0
09-16 14:12:46.982 188-5743/? E/OMX-VENC-720p﹕ Allocated virt:0xb3e4b000, FD: 41 of size 1474560 at index: 0
09-16 14:12:46.982 188-5743/? E/OMX-VENC-720p﹕ Allocated virt:0xb3ce3000, FD: 43 of size 1474560 at index: 1
09-16 14:12:47.011 188-5743/? E/OMX-VENC-720p﹕ open Color conv for RGBA888
After Ctrl-C:
09-16 14:13:21.482 188-716/? E/OMX-VENC-720p﹕ ion recon buffer free failed
09-16 14:13:21.482 188-716/? E/OMX-VENC-720p﹕ ion recon buffer free failed
09-16 14:13:21.521 188-5744/? E/OMX-VENC-720p﹕ ioctl VEN_IOCTL_CMD_READ_NEXT_MSG failed
09-16 14:13:21.521 188-5092/? E/OMX-VENC-720p﹕ Destroy C2D instance
The console outpus is:
Main display is 768x1280 #60.00fps (orientation=0)
Configuring recorder for 768x1280 video/avc at 4.00Mbps
Content area is 768x1280 at offset x=0 y=0
I've tried different solutions like lowering the bitrate, restarting the phone, using telecine, using different PC, turning off MTP but with no luck. In the past when faced the same problem even downgraded the Android to 4.4 but again no luck.
Did someone had this problem and how did you solved it?
P.S. The weird thing is that everything was working as expected initially: I was able to record about 2 minutes of screen recording with Telecine (few times). And then for no apparent reason it started to behave like this...
It turns out the reason is pretty simple: when Android Studio or Eclipse is running it obviously sends some adb messages periodically that interrupt the recording. The solution is stop the AS or eclipse and then to record.
Every once in a while, typically when I do a new install of my App, I will attempt to authenticate with our HTTPS Auth endpoint, the request takes a very long time (around 20-40 seconds) and then fails with an unknown error. I turned on Verbose Volley tracing and I see this nonsense about safebrowsing.google.com. What the heck is happening and how do I make it stop? I am using a Nexus 5 with 4.4 KitKat over wifi.
2662 qtaguid I Failed write_ctrl(u 71) res=-1 errno=22
2662 qtaguid I Untagging socket 71 failed errno=-22
2662 NetworkManagementS.. W untagSocket(71) failed with errno -22
2662 Finsky D [1] 3.onErrorResponse: Verification id=7 error response com.android.volley.NoConnectionError: java.net.UnknownHostException: Unable to resolve host "safebrowsing.google.com"
: No address associated with hostname
2662 Volley D [1] Request.finish: 40045 ms: [ ] https://safebrowsing.google.com/safebrowsing/clientreport/download 0xc9395b26 NORMAL 11
I search inside Volley's code and can't find the URL "safebrowsing.google.com"
I think that maybe your Auth endpoint doesn't accept your request params and redirects you to this domain.
It is Google feature to detect potentially harmful app:
https://support.google.com/accounts/answer/2812853?hl=en
Android calc hash of your app and send to Google for check on this address:
https://safebrowsing.google.com/safebrowsing/clientreport/download
If apk unknown it can upload it to Google for check.