Related
Does anyone know of a way for the camera to record video and use the Bluetooth via headset for audio? Or any other cheap wireless mic solution that will work with on an android phone and doesn't require recording audio and video separately? Thanks
TheEnternal said:
Does anyone know of a way for the camera to record video and use the Bluetooth via headset for audio? Or any other cheap wireless mic solution that will work with on an android phone and doesn't require recording audio and video separately? Thanks
Click to expand...
Click to collapse
Bump
TheEnternal said:
Bump
Click to expand...
Click to collapse
If you connect your BT headset it still records from it's normal mic?
laurensschu said:
If you connect your BT headset it still records from it's normal mic?
Click to expand...
Click to collapse
It does, I just ended up using a wired mic with another camera
laurensschu said:
If you connect your BT headset it still records from it's normal mic?
Click to expand...
Click to collapse
Yes. The camera app only records from the internal mic. I really need a wireless solution that allows me to have the microphone several meters away to record the sound. I could only find wired solutions and they were not even for android.
I think I've got it!
so, I've been trying to do this exact same thing for about a week now, and I think I've got it. with the help of some random people on the internet.
it seems this is actually a two part problem.
1) get the device to recognize the bluetooth microphone (from a headset or other bluetooth wireless device).
2) get the audio into a video recording.
it seems that android and an OS is not readily prepared to do either of these, and the built in video recorder cannot use audio from a source other than the devices built-in microphone.....so....we have to improvise a little.
First, we will need to get android to play nice with the bluetooth device. start by installing a free little app called "bt mono" you can find it on the google play store.
once installed you will need to run this any time you want to use your bluetooth device in a way other than as a phone.
on a side note, this works great for listening to music via a bluetooth headset.
second you will need a video recorder that can take the audio input that bt mono gives you. so, run back over to the google play store and get "lgCamera"
the only thing you have to do now is tell lgCamera that you want to use the "microphone" as the audio source.
thats it. you now have a video recorder on your phone/tablet that will use "almost" any bluetooth device as the audio input.
I have this exact set up on my Verizon Samsung Galaxy Nexus with CM 10.1.0 rooted, and it works perfectly. I am not sure if this works with unrooted devices, though I don't see why it wouldn't. hope this helps anyone who's been dredging the depths of the interwebs!
very special thanks to david hadaller and to Warren Barton for the breakdown and links!
joeypent69 said:
so, I've been trying to do this exact same thing for about a week now, and I think I've got it. with the help of some random people on the internet.
it seems this is actually a two part problem.
1) get the device to recognize the bluetooth microphone (from a headset or other bluetooth wireless device).
2) get the audio into a video recording.
it seems that android and an OS is not readily prepared to do either of these, and the built in video recorder cannot use audio from a source other than the devices built-in microphone.....so....we have to improvise a little.
First, we will need to get android to play nice with the bluetooth device. start by installing a free little app called "bt mono" you can find it on the google play store.
once installed you will need to run this any time you want to use your bluetooth device in a way other than as a phone.
on a side note, this works great for listening to music via a bluetooth headset.
second you will need a video recorder that can take the audio input that bt mono gives you. so, run back over to the google play store and get "lgCamera"
the only thing you have to do now is tell lgCamera that you want to use the "microphone" as the audio source.
thats it. you now have a video recorder on your phone/tablet that will use "almost" any bluetooth device as the audio input.
I have this exact set up on my Verizon Samsung Galaxy Nexus with CM 10.1.0 rooted, and it works perfectly. I am not sure if this works with unrooted devices, though I don't see why it wouldn't. hope this helps anyone who's been dredging the depths of the interwebs!
very special thanks to david hadaller and to Warren Barton for the breakdown and links!
Click to expand...
Click to collapse
You are right! Tks!
Hi bud...
did you find any solution-for phone camera to record video and use the Bluetooth via headset for audio?
i looking for same too Sam.Note4 but no luck so far
Yes. lgCamera and BT Mono works on android. It properly records the video from the phone and the audio captured from my Nokia HS-3W Bluetooth Headset.
Tested with Sony Ericsson LT18i.
Cinema FV-5 has a setting for audio source, and BT works
The only problem - 'cinema fv-5' doesn't seem to utilize the front camera, only the main one.
(can't post the link, search on play store for 'cinema fv-5')
Hello. I kinda worked for 3 secs then it automatically switch back to internal mic.
I have level u headphone and note 5. Is is there anyway to make it stay?
is there any solution that we could hack the OS to make external Bluetooth Mic recognised by the native video camera app in the android phone? its so silly that if you try for example "Open Camera" app from play store the external mic works fine. But i am interested to use the native Camera app for video recordings
any thoughts or feedback will be much appreciated!!
Cinema FV-5 Front Camera
To utilize the front camera on Cinema FV-5 swipe from Left to Right.
If you swipe the left menu bar to the right it will switch to the front camera.
This is documented NO WHERE in the user manual. I found it when I purchased the Camera FV-5 app. On a pop-up instructional screen it said to swipe the left menu bar from left to right to engage the front camera. The photo camera version also has an icon on the right menu bar that switches the photo camera to the front camera but there is no icon nor instructions for the video camera.
It works. Cinema FV-5 works excellently with any bluetooth headset to record audio on video from the BT headset. Just make sure to have the BT headset connected before you open Cinema FV-5 or there may be connection issues to the app.
These are some of the videos that use audio from the BT headset around my neck.
The videos are on YouTube, just paste the ending part below at the end of YouTube.com i.e. /endingpart
u4MWMJaahQw
Kax1yrnQkws
K1SdKe-TAbo
oSD6wklTpQM
An in-ear headset is actually clearer and I've just switched to that type of BT headset but I don't have any of those uploaded at the time of this posting..
UPDATE: Although the swipe left to right will switch to the front camera, the BT audio does not work with the front camera, only the rear camera. Perhaps Cinema FV-5 will fix this with a future update.
Hi guys, we could manage this function through the btmono app, up to version 8. Today, we are at 11 and the situation has not changed .. They say for safety but I cannot give up this solution and I remain at 8.
Do you guys who got this to work with BT Mono and lgCamera have a link to the playstore lgCamera app? I searched it but could not find it. Thanks!
jhqt said:
Do you guys who got this to work with BT Mono and lgCamera have a link to the playstore lgCamera app? I searched it but could not find it. Thanks!
Click to expand...
Click to collapse
I also do not find it on playstore. Probably it is outdated. I can only see it on apkpure https://m.apkpure.com/lgcamera/rubberbigpepper.lgCamera
When I got this device I had installed PA, and so far I had been using that with no issues. Since I heard about 38R's default extra audio stuff I decided to install it. Now, USB audio no longer works. Google music player says "cannot play audio" (flac file) and poweramp (the other player I use) starts then immediately stops if i use default kernel. *IF* I root and install Franco then poweramp can play the music via USB but it still comes out in 44.1Khz/16bit. Can someone tell me what the hell is going on with Cm11S and USB DAC support?
TjPhysicist said:
When I got this device I had installed PA, and so far I had been using that with no issues. Since I heard about 38R's default extra audio stuff I decided to install it. Now, USB audio no longer works. Google music player says "cannot play audio" (flac file) and poweramp (the other player I use) starts then immediately stops if i use default kernel. *IF* I root and install Franco then poweramp can play the music via USB but it still comes out in 44.1Khz/16bit. Can someone tell me what the hell is going on with Cm11S and USB DAC support?
Click to expand...
Click to collapse
for me it works as it should...
i have 7.1 usb sound card. and OFC i have only on 2 channels. but not skipping flac tracks.
edit: 96khz 24bit listening now via usb and sounds really great.
maybe you have corrupted flac files... or try to flash everything again
gerciolisz said:
for me it works as it should...
i have 7.1 usb sound card. and OFC i have only on 2 channels. but not skipping flac tracks.
edit: 96khz 24bit listening now via usb and sounds really great.
maybe you have corrupted flac files... or try to flash everything again
Click to expand...
Click to collapse
You're getting 96/24 on USB really? dang.
Ok I fluked into the solution. I told my music player *not* to use it's own volume settings and so on (PowerAmp has an option for this called 'Direct Volme control') and to completely bypass MusicFX (or any equivalent equaliser). PowerAmp has an option for both ('enable AudioFX' in poweramp to be unchecked). THEN it works with USB audio, it's still a bit wierd the first time you plug it in (i think).
This also means 'Google Music' will not work (which it doesn't) since it has no option to *not* send things via MusicFX. Well, I never had a ROM with built in equaliser, maybe the fact that there is one in CM is causing issues for USB DACs?
TjPhysicist said:
Ok I fluked into the solution. I told my music player *not* to use it's own volume settings and so on (PowerAmp has an option for this called 'Direct Volme control') and to completely bypass MusicFX (or any equivalent equaliser). PowerAmp has an option for both ('enable AudioFX' in poweramp to be unchecked). THEN it works with USB audio, it's still a bit wierd the first time you plug it in (i think).
This also means 'Google Music' will not work (which it doesn't) since it has no option to *not* send things via MusicFX. Well, I never had a ROM with built in equaliser, maybe the fact that there is one in CM is causing issues for USB DACs?
Click to expand...
Click to collapse
you know what?? my poweramp doesnt want to play some flac's with higher qualities even when "direct" is unchecked, but play music does and audiofx built in equaliser works good with play music.
btw how do you checking real bit and freq which is playing by device?
gerciolisz said:
you know what?? my poweramp doesnt want to play some flac's with higher qualities even when "direct" is unchecked, but play music does and audiofx built in equaliser works good with play music.
btw how do you checking real bit and freq which is playing by device?
Click to expand...
Click to collapse
my DAC displays the input it receives and the method (e.g/ usb. 48Khz 16 bit). it doesn't do all (44.1 is missing but gets converted to 48 I guess ?). Real idk, but the device reports it as " this is the digital signal I'm getting". As an example...on my computer I use foobar and have it set to bitperfect mode (no conversions just send signal directly to DAC whatever the bitrate etc)...when I play a cdrip my dac says "48" and "16". if I then switch to my 96khz/24 bit download of dire straits it immediately switches to saying "96" and "24bit" in the little screen on my DAC.
TjPhysicist said:
my DAC displays the input it receives and the method (e.g/ usb. 48Khz 16 bit). it doesn't do all (44.1 is missing but gets converted to 48 I guess ?). Real idk, but the device reports it as " this is the digital signal I'm getting". As an example...on my computer I use foobar and have it set to bitperfect mode (no conversions just send signal directly to DAC whatever the bitrate etc)...when I play a cdrip my dac says "48" and "16". if I then switch to my 96khz/24 bit download of dire straits it immediately switches to saying "96" and "24bit" in the little screen on my DAC.
Click to expand...
Click to collapse
i wonder there are apps to show in notification bar my current media quality... couldnt find any..
After I updated my Shield Tablet to Stock Lollipop (happens on both 5.0.1 and 5.1),
I noticed that with certain files that use the SW decoder, the audio in MXPlayer crackles a lot, and eventually the audio on the whole tablet cuts out for around 10 seconds (at least judging by the Logcat). This only occurs with MXPlayer. VLC has no audio issues, but I'd rather using MXPlayer for better seeking support. Also, when the audio cuts out, the video keeps playing, but when the audio starts working again, the video pauses until it aligns with the audio.
This appears to be a relevant line of the logcat:
Code:
W/AudioFlinger(17468): write blocked for 10016 msecs, 1 delayed writes, thread 0xaedd7000
One thing that the problematic video files have in common are 48000Hz audio channels, which I believe is the native sample rate of my device. Is there some resampling that isn't getting applied to 48KHz audio that might fix the issue? Is the AudioTrack not getting flushed properly?
The full log is attached. And these lines I believe are not relevant, because they happen nearly all the time when I have headphones plugged in:
Code:
W/NvAudioPolicyManager(17468): getDeviceForStrategy() unknown strategy:
xperia64 said:
After I updated my Shield Tablet to Stock Lollipop (happens on both 5.0.1 and 5.1),
I noticed that with certain files that use the SW decoder, the audio in MXPlayer crackles a lot, and eventually the audio on the whole tablet cuts out for around 10 seconds (at least judging by the Logcat). This only occurs with MXPlayer. VLC has no audio issues, but I'd rather using MXPlayer for better seeking support. Also, when the audio cuts out, the video keeps playing, but when the audio starts working again, the video pauses until it aligns with the audio.
This appears to be a relevant line of the logcat:
Code:
W/AudioFlinger(17468): write blocked for 10016 msecs, 1 delayed writes, thread 0xaedd7000
One thing that the problematic video files have in common are 48000Hz audio channels, which I believe is the native sample rate of my device. Is there some resampling that isn't getting applied to 48KHz audio that might fix the issue? Is the AudioTrack not getting flushed properly?
The full log is attached. And these lines I believe are not relevant, because they happen nearly all the time when I have headphones plugged in:
Code:
W/NvAudioPolicyManager(17468): getDeviceForStrategy() unknown strategy:
Click to expand...
Click to collapse
@xperia64Did I don't think this is a resampling issue. Have you tried HW+ decoder? SW decoder on high resolution video might cause this issue. And I will be test more if you send a sample video clip.
bleu8888 said:
@xperia64Did I don't think this is a resampling issue. Have you tried HW+ decoder? SW decoder on high resolution video might cause this issue. And I will be test more if you send a sample video clip.
Click to expand...
Click to collapse
The issue occurs on nearly all if not all videos with 48KHz audio tracks, from 320x240 all the way up to full HD. It is impossible to play some of these videos with HW+ due to them being WMV or Microsoft MP4's. I've encountered the issue even in Big Buck Bunny. I've tried the 1280x720 and 854x480 MP4's and the 854x480 MSMP4, which exhibit the issue https://peach.blender.org/download/
The lower resolution ones especially should not be that intensive.
If I play the regular BBB MP4's with the HW/+ decoder and SW audio (because AC3), I didn't notice any crackling. If I play them with the SW decoder, they eventually start crackling and audio on the whole tablet cuts out. If I play the MSMP4 version with the SW decoder and software or hardware audio, it will crackle.
I've been using MXPlayer for quite a while, and I remember that when playing larger files on an older device like the Motorola Droid 1, the audio track would sometimes get ahead of the video, and the audio would pause for a while, but this is different because there is no apparent lag and audio on the whole tablet dies.
It would appear that Nvidia's stock kernel is part of the problem here. I flashed a different kernel and I cannot reproduce the crackling/cutout. Although it's somewhat strange that only MXPlayer had this issue.
Well at least you have audio. I updated to 5.1 and did it through the ota with twrp and I have NO audio. Makes no sense. I went back to 5.0.1 and I have audio again. I tried a bunch of different things and still no way for me to get any audio on 5.1. I am thinking of trying a kernel and see if that helps. Or maybe go back, again, and wait for a fix!
JohnK71 said:
Well at least you have audio. I updated to 5.1 and did it through the ota with twrp and I have NO audio. Makes no sense. I went back to 5.0.1 and I have audio again. I tried a bunch of different things and still no way for me to get any audio on 5.1. I am thinking of trying a kernel and see if that helps. Or maybe go back, again, and wait for a fix!
Click to expand...
Click to collapse
@JohnK71 @xperia64
Would you try latest test version from following link?
https://sites.google.com/site/mxvpen/translation/test-build
Feedback will be appreciated.
bleu8888 said:
@JohnK71 @xperia64
Would you try latest test version from following link?
https://sites.google.com/site/mxvpen/translation/test-build
Feedback will be appreciated.
Click to expand...
Click to collapse
Sorry, but I am saying "NO" audio even playing music or checking and changing sounds. No sound at all and also no mic. It all works good back on 5.0.1 so not sure what's the deal with 5.1 for me. I guess I will hope for better results with next version of lollipop. Thanks anyway for the suggestion.
The test build did nothing different. However, version KS-034 of this kernel appears to have fixed my remaining audio issues. On KS-033, the audio was fine for 48KHz audio files, but would still cut out with 24KHz audio files and somewhat break any future AudioTracks in any app until reboot. Version 034 said it increased the HD audio buffer so I guess that did something.
http://forum.xda-developers.com/shi.../tweaked-kernel-nvidia-shield-tablet-t3069776
xperia64 said:
The test build did nothing different. However, version KS-034 of this kernel appears to have fixed my remaining audio issues. On KS-033, the audio was fine for 48KHz audio files, but would still cut out with 24KHz audio files and somewhat break any future AudioTracks in any app until reboot. Version 034 said it increased the HD audio buffer so I guess that did something.
http://forum.xda-developers.com/shi.../tweaked-kernel-nvidia-shield-tablet-t3069776
Click to expand...
Click to collapse
Shield Tablet OTA 3.0 looks like suspended due to audio issue.
See this link: https://forums.geforce.com/default/...3-0-update-feedback-thread-released-5-22-15-/
That is because of a different audio issue where the speakers would literally explode. I had the crackling on 5.0.1/2.2.1. as well.
And I actually went back to KS-033 because KS-034 made audio too latent and it reintroduced crackling on all files, granted it was diminished.
After updating to the latest BitO Kernel (KSX-043) and MXPlayer test version, crackling behavior has changed again, but I have a theory on the crackling this time.
I noticed that after a reboot, the crackling would stop for a while before it returned. The CPU in this device tries as hard as it can to keep its clockspeed at the minimum 51MHz while in sleep mode, regardless of wakelocks/background apps. I had been using Droidsound-e and my own AudioTrack-based music player in sleep mode and I noticed that those apps would skip/crackle a bit as they tried to process the music files but couldn't. That appears to somehow throw off audio output until reboot. The issues are still most noticeable in MXPlayer, but also appeared in other apps as well. I increased the minimum clockspeed to 204MHz and it seemed to help.
I don't know if this is the cause, or if it works on the stock kernel, but on my current setup it seems to work fine.
v1.10.17 - custom codec installed
Firestick 4K
Fire TV 2
I have several fire devices, including a FTV2 and the new 4K stick.
While testing the new 4K stick, I found several issues, first is only on the new stick, 2nd is on both devices.
Hopefully you guys can help me out, I have spent 2 evenings already and still not resolved.
1) Random switching from HW to HW+ to SW
During playback of many video's, including tv episodes, the video starts playing in HW mode, runs smooth. Then at random times it switched to HW+, usually with black reloading screen in between, then later it switches to SW stating HW+ not supported - and stays in SW modus. In SW it seems OK-ish, but sometimes see skipping, lag etc. that is not present in HW(+) decoding.
a) If it starts playing OK, then why does it need to switch to other modes? If it works then i dont understand why that happens
b) The older FTV2 does not have this issue, I have never seen this before. It starts with HW or HW+ and stays that way, never any issues in this regard. The new stick hardware codec support is even better than the older FTV2.
2) No audio on many streams
I found that many streams starts in HW modus, with no audio at all. It stays that way if I let it run.
If I switch it to HW+, it does have audio, but out-of-sync.
Also, after a while it switches back to HW or sometimes SW.
a) why does it choose HW, not HW+?
b) why out of sync in HW+?
c) Why does it switch back to HW or SW, if it working (out-of-sync)
d) Installed custom-codec all-in-one, did not solve it
-------------------------------
I have also tried several other players, to some success. But they have their own issues, like buffering, laggy playback, stutter when FWD etc.
So I need to get this working, there are no real alternatives
I have done some extra testing. I now got it all working on my FTV2, with an older version 1.9.11 (+compatible codec pack).
I also set HW+ as default for network streams. I have tested several video's, x264/x265, dts/ac3 they seem to all work and keep working OK. Usually they stay in HW+ modus until the end and all smooth.
I couldnt find the older version, so I tried the latest MX 1.10.25, with latest codec pack. At first, it was working...but later when watchin an episode it gave me all sorts of trouble:
- blocking issues
- streams stops
- stream does not start again after trying new
- switch from HW+ to SW
- cant switch manually to HW+, gives error HW+ not supported
So weird, especially since it is working fine on the older FTV2.
Anyway, will try to get the older version and see if that helps.
timtoolman2k11 said:
I have done some extra testing. I now got it all working on my FTV2, with an older version 1.9.11 (+compatible codec pack).
I also set HW+ as default for network streams. I have tested several video's, x264/x265, dts/ac3 they seem to all work and keep working OK. Usually they stay in HW+ modus until the end and all smooth.
I couldnt find the older version, so I tried the latest MX 1.10.25, with latest codec pack. At first, it was working...but later when watchin an episode it gave me all sorts of trouble:
- blocking issues
- streams stops
- stream does not start again after trying new
- switch from HW+ to SW
- cant switch manually to HW+, gives error HW+ not supported
So weird, especially since it is working fine on the older FTV2.
Anyway, will try to get the older version and see if that helps.
Click to expand...
Click to collapse
In general, It will automatically try the next decoder when the playback has failed before completion of the file. It is an intended behaviour since 1.8.x. Kindly collect the bug report from the latest version immediately after the issues. It will help us to understand better.
Thanks for your reply. I will try to get the report next time.
In meantime I have tested with exact same (old) version, 1.9.11 + codec pack on fire stick 4K.
I had set HW+ as default for network, same as on the FTV2.
So basically, exactly same set-up, same streams, but on newer hardware.
At first it seemed ok, however:
- setting HW+ as default, at some streams, I cannot FWD, it just jumps back to beginning
- on tv episodes, it starts with HW+, then jumps to HW for some reason (no change in audio or video) - does not happen on FTV2
- on certain movies, it starts with audio on HW+, then jumps to HW modus without audio, makes no sense - does not happen on FTV2
- on movies with multiple audio tracks, in HW modus it plays just one track , cannot switch to other track, stuck in commentary track. same stream in HW+ modus has the main track selected and playing.
All in all very weird, never had so many issues. I just installed it and it would work. What troubles me is that I now have a working FTV2 setup, ubt exact setup does not work on the Fire stick 4K. Very frustrating.
I also found that HDR playback is very dull, very dim, not bright at all. So staying on old version is ok up until 1080P. 4K+HDR is not working ok, but will be probably be fixed in newer version.
I will keep the FTV2 at the now working setup.
I wil re-install latest mx and codec pack on 4K stick and test again.
If I encounter errors, I will try to post bug report. Hopefully that will help the devs to fix this. It seems it is not really liking the new Fire stick hardware for some reason.
Ok. Did some testing again. Here my results + logs.
- Fire 4K Stick
- MX 1.10.25 (default settings)
- codec pack: https://forum.xda-developers.com/attachment.php?attachmentid=4656301&d=1543696913
(from a post saying that it worked perfectly on ac3, while another didnt)
- 6 different network streams
---------------------------------
1. 720P X264 - single channel audio (stereo i think)
- starts in HW+
- stays in HW+
- FFWD OK
- keeps playing OK
2. 1080P X264 - multichannel 5.1 audio
- starts in HW
- commentary track on - cannot switch to other tracks
- FFWD not working OK
After a short while:
- restarts video in HW+
- audio main channel on
Very short after:
- switched to SW
- no audio
- choppy playback
Log: report_2018-12-03_194334.zip
-------------------------------------
3. 4K X265 stream
- MX crashes directly after start
- Starting 2nd time, MX starts playing in HW+
- Audio/video OK
- FFWD OK
- Keeps playing ok
Log: report_2018-12-03_194948.zip
-------------------------------------------
4. 1080P X264 stream
- starts in HW
- No audio
- FFWD not working OK
After short while:
- restart in HW+
- audio not starting right away, after about 10s it starts (but sync)
- FFWD OK
- keeps playing OK
5. HD 5.1 audio
- starts in HW
- no audio
- FFWD not working
After short while:
- restart in HW+
- audio working
- FFWD working
- keeps playing OK
Log: report_2018-12-03_200011.zip
--------------------------------------
6. 720P X264 - stereo
- starts in HW
- No audio
Shortly after playing:
- switch to HW+
- audio working
Very short after:
- Switch to SW
- Choppy playback
Log: report_2018-12-03_200412.zip
---------------------------------------------
My conclusions so far:
- Stream 1 starts in HW+, keeps playing OK, no issues
- Stream 4 & 5 should be fixed by setting HW+ default for network streams.
(except for the small delay in start of audio of 4, but that is ok)
- Stream 2 & 6, can partially be fixed by HW+ default, but not the switch to SW
- Stream 3: crash is not OK, but after 2nd try it works OK
- I dont understand why some streams start in HW+, while other start in HW then later switch to HW+
This is now keeping me from using my stick. While on my old FTV2, with old MX it seems to all work just fine.
Seems like it is not liking the new 4K stick hardware / does not seem to see the hardware decoding abilities - which are matching and surpassing the old FTV2.
Hopefully my testing and logs can help you guys to fix these issues. - if fixed it will be an instant Pro buy for me thats for sure!
I have tried other players, but they all have their own issues - and not the level of support of MX devs.
So I will now sit back and wait for the fixes to come on.
Ofcourse I am happy to test again to verify correct workings after updates.
timtoolman2k11 said:
My conclusions so far:
- Stream 1 starts in HW+, keeps playing OK, no issues
- Stream 4 & 5 should be fixed by setting HW+ default for network streams.
(except for the small delay in start of audio of 4, but that is ok)
- Stream 2 & 6, can partially be fixed by HW+ default, but not the switch to SW
- Stream 3: crash is not OK, but after 2nd try it works OK
- I dont understand why some streams start in HW+, while other start in HW then later switch to HW+
This is now keeping me from using my stick. While on my old FTV2, with old MX it seems to all work just fine.
Seems like it is not liking the new 4K stick hardware / does not seem to see the hardware decoding abilities - which are matching and surpassing the old FTV2.
Hopefully my testing and logs can help you guys to fix these issues. - if fixed it will be an instant Pro buy for me thats for sure!
I have tried other players, but they all have their own issues - and not the level of support of MX devs.
So I will now sit back and wait for the fixes to come on.
Ofcourse I am happy to test again to verify correct workings after updates.
Click to expand...
Click to collapse
The HW decoder directly uses the android mediaplayer framework implemented on the device. So, most of the issues on HW decoder might be caused by the firmware itself. It looks like Amazon has heavily modified the android mediaplayer and media codec frameworks or its implementation has issues. According to the logs, the media server process ( a system process) which plays a vital role in hardware accelerated playbacks (HW & HW+) has died in the midway. So, the player has encountered the issues and switched to the next decoder. So, MX Player doesn't have much scopes for the improvement on this issue.
Wow really? That would mean everyone with this new device should have these issues. That has not been reported anywhere. All praise for this stick. Or am i the only one to have a faulty one? Very odd.
I installed MX fresh out of the box. I can try to do a reset and re-install. If that doesnt work, then I guess I have to return it.
Is there really nothing you can do to fix this? You are on amazon store as well, right? Then I guess it should work, but it currently doesnt.
Ok, did a reset of the stick, only installed bare minimum for testing.
Now, it seems to work ok !
I guess something was messed up causing the media server issues. Don't know what, maybe some other apps I installed.
Yes, still some streams start in HW, with no audio or wrong audio.
However, I have set HW+ as default - so that is fixed.
I have watched several streams last night, they started in HW+ and kept playing in HW+, all working fine. No fallbacks to SW.
The only issue I have now is the crash on some 4K streams on first play still happens. After 2nd try it works fine. Not a biggie, still would be good if this is fixed.
timtoolman2k11 said:
Ok, did a reset of the stick, only installed bare minimum for testing.
The only issue I have now is the crash on some 4K streams on first play still happens. After 2nd try it works fine. Not a biggie, still would be good if this is fixed.
Click to expand...
Click to collapse
Can you please collect the bug report immediately after the crash?
In your previous bug report, the logs were so limited. Looks amazon has set the log buffer size to the minimum. If it possible, enable the developer option and increase the log buffer side.
Slight issue.
Using VLC and the new OnePlus Z headphones, I am getting about 250ms mismatch between the audio and video when playing a movie. VLC can correct this, but I've never seen this before on other devices.
Anyone got any ideas why? I haven't checked with other apps yet to see whether it's VLC or the phone or headset.
Alan
OK - just tested a couple of other apps and it may be VLC which is the issue. Either that or it's sorted itself out
Alan