I've updated my Nexus 7 (2013) to Android L preview, and found that one of my apps cannot be launched anymore with the following LogCat Error msg:
E/WindowState(643): getStack: Window{33f867f8 u0
Starting com.xxxxxx.ooooo} couldn't find taskId=151
Callers=com.android.server.wm.WindowState.getDisplayContent:730
com.android.server.wm.WindowStateAnimator.stepAnimationLocked:273
com.android.server.wm.WindowAnimator.updateWindowsLocked:254
com.android.server.wm.WindowAnimator.animateLocked:550
Also note that the app launch animation would be played but then the screen would go back to the previous screen without any user facing error message, so I've only got this error dialog to go on and am hopelessly lost atm. Any help is greatly appreciated.
Edit:
VLC and a few video players that may have used VLC library have the same issue, so I am guessing it's something with VLC's native library given how Android L has tightened up JNI a bit, but I am lost at to where to start modifying given the opaque log message :-/
Related
I am very new to Kotlin and Android studio. I tried running my App through the emulator, I built in AVD manager.
Whenever I run my App it goes to the home screen, I don't know what you'll need to solve this or what causes it:
But based on what I've seen as I researched this issue, here are some info I think you might need;
-I've turned off detect adb location and set the directory to C:\Users\user\AppData\Local\Android\Sdk\platform-tools
-minimumSdk 21
-targetSdk 31
-My Api level is 25
Please whatever info you need to help me rectify this issue just ask me..
I am open to any suggestions, Thank you in advance for your help!
here's a screenshot of build error:
I'm adding a logcat error message screenshot, though they are much of error I just screen the ones that could be taken on a single shot, I hope it enough.
(Please note that previously my logcat was empty even when I was experiencing the same problem, so I created another emulator, and the logcat is no longer empty..)
You can check out the logcat to be able to see what went wrong.
I've a put a WebView in my android app and loaded YouTube in it (Device SDK version 23). Everything worked fine till I went fullscreen with that video. But, when I tried to exit webview's fullscreen that whole application screen went white.
I've picked up two logcat lines with ERROR tag while I've clicked the exit button which may be needed:
08-20 19:34:22.846 28114-28271/test.webview E/chromium: [ERROR:deferred_gpu_command_service.cc(79)] No hardware renderer. Deadlock likely
08-20 19:34:22.846 28114-28271/test.webview E/chromium: [ERROR:deferred_gpu_command_service.cc(79)] No hardware renderer. Deadlock likely
I've uploaded a screenrecord of the event HERE.
As logcat says it's a hardware problem. So, will it be unfixable? What will I do if most of my application's user get in this problem? They will mostly consider it as a bug and will uninstall my app after checking for update for sometimes.
UPDATE:
From HERE I've found someone commented that (on Sep 16 2014) it's have been fixed. But as Google can remember that Android M has been released on September 29, 2015. And, I've bought my device some months ago. I really can't understand what's going.
Greetings StackOverflowers!
I've searched at great length, but finally have to admit I'm out of ideas.
Please find a minimalist Eclipse project at https://github.com/ppinter1/AndroidCamera.git which demonstrates the problem I'm having on a Samsung Galaxy Tab 10.1 and Android 4.1.1
In essence: the dreaded Camera Error 100 (with attendant death of ICamera/media server/Camera server) occurs whenever I call .takePicture after stopping a video recording.
What's tested and working in the code provided:
any number of photos can be captured
any number of videos can be recorded as well
even taking a photo while recording works fine (a nice side effect)
BUT, taking a photo after stopping a recording (that is, either by hitting the 'Stop Recording' button, or because the recording is automatically stopped when the maximum file size of 5MB is reached) causes the generic Camera Error 100.
I would be most appreciative if others would test this code on their Android device.
Is it a bug just with this tablet? If it fails on other devices as well, can anyone tell me
what I'm doing wrong or how to diagnose this further?
If the code works for you, please reply with your device model and Android version.
With many thanks,
Pete
UPDATE:
Couple things:
A Samsung Developer support tech reports no error running my github test code on an S3 device, but sees an Exception with Galaxy Tab and Nexus. He believes the test code uses the Camera API incorrectly, yet I don't think I can make the code any simpler... if anyone spots an API usage error, please correct me!
I've opened an issue at Google's Android tracker with additional log file detail.
As detailed on the tracker link above, it turns out one needs to Add an extra .stopPreview() after .reconnect() and before .startPreview.
Massive thanks go to developer etalv on the Android Open Handset Alliance Project for the tip.
Users comment on google play that app is not opening on nexus 7. I am waiting for my nexus to test that issue. Right now I do not have that device.
My app is OpenGL ES 2.0 game.
Some ppl comment on google play that app is not openning. But I do not get exception error in Crashes and ANRs in Google Play.
What could be a reason for that?
I have a lot of native code. Do native code exceptions are reported somehow?
Could it be a ConfigChooser.chooseConfig bug? Is that recommended ConfigChooser.chooseConfig for Nexus or most apps?
I can confirm that the game crashes the moment you open it on the Nexus 7, however I know why you have nothing in Crashes & ANR... no Force Close dialogue box opens at all, you get a black screen, then the game immediately quits.
I do however have the stacktrace from logcat available, the error is in some C/C++ code you have via the NDK. I have uploaded the entire log from when you open the app onto pastebin for you.
Logcat: http://pastebin.com/dq0kRxnn (the link will expire after 1 month)
I know this is Unity3D question and there are more specific stack/forum sites...
Pls see attached logcat log, is there anything which gives us any clue?
Unity Splash screen appears on device, but after a few seconds it crashes. This app was OK yesterday, I added some C# code textures etc. I carefully examined the debug build logcat log. My code has not even a chance to run, the crash happens before...
Note: No Mono runtime exception in logcat log.
It works fine in Unity editor, or windows standalone build.
Again: It worked fine, with the same settings yesterday. More: The yesterday's backup sill working today, rebuild, deploy to the same device. This today's version (I1ve added textures, code etc) which is not working on the device.
See the log attached.
Don't know where to search toward... :-(
Thx for help
Download logcat log file