I wonder if this happened to anyone else so far. I am developing an app that is sending Bluetooth strings to Arduino while playing VR video. I am using Note 4 for testing and Android Studio for development.
The video and bluetooth works just fine until i put in the 4k video. It starts playing it and if not in "cardboard mode" it works. But as soon as we go to "cardboard mode", the video freezes. The voice continues to play in the background and if i go out of "cardboard mode" it continues the playback.
Any ideas to why this is happening? I have implemented VR video View just as Google suggests (from their test code). Monitor shows no errors, nothing. When i check the GPU monitor i just some really bad spikes when entering "cardboard mode", but then it just stops.
Related
I have an application that allows users to stream video and audio from their phones using webrtc to the server. The streaming should not be interrupted if the device locks down or the app goes to background. Everything works perfectly in the first case. In the second case, however, when I press the home button, audio still works perfectly but the video freezes. Any help would be much appreciated here.
P.S. I'm using ionic with capacitor.
I'm working on a video recording app designed to keep recording despite interruptions (phone calls, etc.). My use case would be a user in the app pushing a button on screen to start a recording, and then at some later time manually locking the phone. I'm trying to keep the app recording video even while the phone is locked.
On devices running earlier versions of Android (tested on Android 4.1, DROID 4), the video recording keeps going when the phone has been locked. Testing on various devices, I have been unable to get the video to continue recording on any Android version past 4.1. On devices past 4.1, the video stops recording, but the audio still continues recording, while the last video frame stays on screen.
Is there any way to keep the app recording when the user locks the phone?
Basically, lock screen does not affect the working of services in an application. So if you use a service, then your recording will proceed. check out this link for more information:
Android app video recording when screen off
I have a server Icecast working with Liquidsoap to stream internet radio and I noticed there is a problem with receiving the music on some Android devices (Samsung Galaxy tab, for example) - after a few seconds of buffering of the music the playing of the music starts for about a second, then it abruptly stops, then there is a silence for a few more seconds, and only after that it starts playing normally. On some other Android devices, like HTC desire - no such thing occurs - music starts playing normally after the bufferization.
Here is the example of the stream in question: http://rdsradio.ru:8000/4th.mp3
That happens when I open the link in the browser (Google Chrome) on the Android device. With the same result I connected to the Icecast stream from the Android app, which I currently develop, using the android.media.MediaPlayer class: mediaPlayer.setDataSource("http://rdsradio.ru:8000/4th.mp3");
Also, even on those problem devices I could normally connect and listen the streams of other Icecast radio sources, like http://dancewave.hopto.org:9990/dance.mp3
- that is why I think there could be something wrong in my settings of Icecast + Liquidsoap - what makes that music stops playing in the beginning.
<burst-on-connect>1</burst-on-connect>
<burst-size>64000</burst-size>
I tried to change those parameters in /etc/icecast2/icecast.xml, like increasing the burst-size to 10-20 times or setting burst-on-connect to 0, but did not notice any difference at all (I run /etc/init.d/icecast2 reload after changing the parameters to reload the configuration).
Any idea - how to fix that behavior?
UPDATED: I tried to open the stream in VLC player on Android and it worked with no problem, so it seems the problem in using the android.media.MediaPlayer (probably the built-in HTML5 audio player in Google Chrome uses the same library). I will try to use a different Media Player in the app.
Actually, the solution was simple. The burst-size setting to 500000 in icecast.xml fixed the problem. Earlier I used /etc/init.d/icecast2 reload after changing the icecast.xml and for some reason I thought that the burst-size would also change in Icecast in the similar way, but it didn't happen. Only restart of icecast actually changed that setting.
Hi everyone I recently made an application that is actually a media player of a football club ultras music. I tested it on my phone (Motorola X running Android 4.4.4) when i go back to the dashboard the music keeps playing and everything is OK. But I had a review that on Samsung Trend Plus running Android 4.2.2 the music stops playing when going back to dashboard. I didn't know what may cause this issue? any ideas? Thanx
Most likely your problem is with audio focus. On certain system, when user go to the dashboard, the launcher might take audio focus (and pause your audio play) to play its launch sound (the clicking noise or w/e). Right after that, it should hand back audio focus to you and you will need to resume your playing.
http://developer.android.com/training/managing-audio/audio-focus.html
I have an AIR Android application which has multiple pages, each page has their own music and sound effects. Music is executed via code and the effects are part timeline and part code executed.
This all works fine on the AIR Simulator but as soon as I run it on a Tablet with Android 4.4.2 it is ok for the first page, but once the first page music and effects sound channels have been faded out (via a volume tween) you wont hear a sound from the application again. Android 4.2.2 however is fine.
I've traced the volumes and the values are fine, I've even tweened the SoundMixer volume itself and still not a sound.
The code is just basic soundmixer and soundtransform code, virtually identical to what is on adobe live docs. I've even skipped the first page and gone directly to the second to see if the sounds are working correctly and they are fine.
Anyone got any suggestions?
Issue was: omni-4.4.2-20140128
Flashed version: omni-4.4.2-20140318
and all is fine in the world once again!