I got the MediaPlayer error code as (1,-110) on BeagleBoard Hardware running ICS.The code runs fine on android tablets with ICS but I get a dialog box as "Sorry,this video cannot be played" error on BeagleBoard only.Any suggestions.
This is a time out error from the MediaPlayer:
http://developer.android.com/reference/android/media/MediaPlayer.html#MEDIA_ERROR_TIMED_OUT
Also, it may happen with an issue with Samsung firmware on Android 4.1.2, I've seen it in Galaxy S2 mini and Galaxy S3. Take a look here:
https://stackoverflow.com/a/18378273/3032209
You could solve it if you play the file it with another library, which will have the adequate codecs, like aacdecoder-android
I know my answer is too late to your question and I think you were able to fix this problem by now, but if not and for those people who are struggling with the Media Player Error (1, -110) (like I did the whole day today, Android HTC Desire X Jelly Bean 4.1.1), maybe this is the solution for you:
Just reboot your android (or close all the apps, which are using the Media Player).
In my case it was not a programming error, I just had to many apps open using the Media Player Instance, which led to that time out and I could not use it anymore.
Related
I'm writing an android audio player and on my nexus 5 running android 5.0 the MedaPlayer stops playing audio tracks around 2 to 5 seconds early. It's not predictable. It can change on the same track. Is there anyone else experiencing this, that found a workaround. I know this is not just my app that's having this issue on this device, because I tested it in Vanilla Music Player and it did the same thing. I've seen a few other people post on things sort of similar, but in most cases I see it has to do with steaming.
According to this answser:
https://stackoverflow.com/a/27827402/1415199
This is a bug in Android.
Ok it looks like the issue is Android 5.0.1's experimental MediaPlayer
called NuPlayer. NuPlayer is being enabled by default on all Android
5.0.1 devices and is only disabled through Developer Options. I've filed a bug against Android here:
https://code.google.com/p/android/issues/detail?id=94069&thanks=94069&ts=1420659450
The link above contains a suggested workaround
I have a very strange issue with android's VideoView class.
My app streams a video file from my server. Sometimes the app tries to fetch the video file before it is actually there (still processing), and I get error ( 1 , -1004) from the videoView's mediaPlayer. Than I try to stream the same url after the video is already in that path, but the videoView will keep sending the same error again and again for a few minutes.
Other clients (android/ios/vlc) will succeed playing that same video file, while the app that tried to play it while it wasn't in there will continue to fail for a few minutes.
The VideoView will succeed playing all video's 99% of time - the ony issue I have with it is this one.
I tried creating a new videoView instance to play that url, but it gives the same error -1004 (MEDIA_ERROR_IO).
I tried quitting the app / restarting the device - but that same url will continue to fail for a few minutes.
I tried copying the url from the failing device, to the VLC app in that device, and will succeed playing it.
The issue is not device/version specific - It happens to all the devices I tested on, and all android versions I tried:
Samsung galaxy s3 Jelly bean.
LG nexus 4 - kitkat.
Samsung galaxy nexus ICS.
Samsung Galaxy s2 gingerbread.
Samsung nexus s - ICS.
It's as if MediaPlayer is remembering that bad link, and will continue to send the same error for a while without checking it again.
Does the videoView cache links in any way?
What could be the issue??
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.
i'm having trouble trying to find a video player to play a stream for my app on a galaxy nexus.
it works on every other phone apart from nexus.
if i dont give the app the tag to tell it that it's a video in the url it gives me an options screen to choose what to complete the action with, in this list it doesn't show a video player. (if i state that it is a video i get a class not found exception)
anyone know what the issue is? as i said it's working on other phones apart from nexus, even works on galaxy s3
thanks
our new game seems to be smooth on other phones but on samsung gaxalxy s2 it always freezes and crashes. the application uses gdx lib. the issue seems to be connected with the music.
while the music is turned off from the code the gameplay is smooth, but after turning it on the whole series of crashes and freezes start.
Any solutions or advice on this ?
You can check the game here Fish vs Pirates
Thanks in advance.
The Samsung Galaxy S2 has a known audio bug: http://code.google.com/p/android/issues/detail?id=17623
Supposedly using the MediaPlayer API instead of the SoundPool API is supposed to work-around the issue. There are also reports that this is fixed in the ICS update. (If you're not using the SoundPool API, then you're probably not seeing this particular issue.)