Hi at all,
the well-known problem, when we play an hw-accelerated video file (just like a 720p mkv ) is that the subtitles aren't ouputted to TV throght hdmi-mhl. That's because when the hw decoding is used, only the video layer is ouputted.
This is the answer form the diceplayer google group :
"Hi,
The overlay including subtitle when HW accelerated should be supported by manufacturer. The Android framework does not have any interface for HDMI (MHL), so the HDMI output depends on manufacturer's implementation.
But the most devices do not support the HDMI output with the overlay, so it is to hard to support it.
Thanks."
Click to expand...
Click to collapse
So, I think that this is the only missing thing to make out GNEX a perfect media player, better than an atom + ion platform.
I saw that here in XDA, there is a project for the galaxy S2:
http://forum.xda-developers.com/showthread.php?t=1335549&page=3
A video player that can output subtitles over mhl... (unfortunatly not ICS compatible)
So, If galaxy S2 can, why the GNEX not? we have an "open" platform where to develop software...
I ask to everyone that can help with this project, if someone knows where to start debugging the problem: software or hw related? what libs are involved in this?
If someone give me a starting point i'll try to spend my free time to figure out a possibile solution. I'm not used to gnex development, so I need a starting point from expert developers...
Btw, any kind of info that anyone can provide I think it will be useful.
Thanks,
WZ
I don't know if anyone else has had issues with streaming any kind of audio through Bluetooth but I found a fix for it without screwing up anything else audio-wise with the phone.
I just got a Mazda with Bluetooth audio built into the stereo and was completely underwhelmed with the quality of the Bluetooth audio compared to an aux plug. It sounded so poor as if the phone converted the high quality 320kbps files I uploaded to Google Play to a lower 64kbps.
I researched and found its in the coding of the audio_policy.conf in system/etc.
The file should contain the following...
# Global configuration section: lists input and output devices always present on the device
# as well as the output device selected by default.
# Devices are designated by a string that corresponds to the enum in audio.h
global_configuration {
attached_output_devices AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_SPEAKER
default_output_device AUDIO_DEVICE_OUT_SPEAKER
attached_input_devices AUDIO_DEVICE_IN_BUILTIN_MIC|AUDIO_DEVICE_IN_BACK_MIC
}
# audio hardware module section: contains descriptors for all audio hw modules present on the
# device. Each hw module node is named after the corresponding hw module library base name.
# For instance, "primary" corresponds to audio.primary..so.
# The "primary" module is mandatory and must include at least one output with
# AUDIO_OUTPUT_FLAG_PRIMARY flag.
# Each module descriptor contains one or more output profile descriptors and zero or more
# input profile descriptors. Each profile lists all the parameters supported by a given output
# or input stream category.
# The "channel_masks", "formats", "devices" and "flags" are specified using strings corresponding
# to enums in audio.h and audio_policy.h. They are concatenated by use of "|" without space or "\n".
audio_hw_modules {
primary {
outputs {
primary {
sampling_rates 44100
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_AUX_DIGITAL|AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET
flags AUDIO_OUTPUT_FLAG_PRIMARY
}
}
inputs {
primary {
sampling_rates 8000|11025|16000|22050|24000|32000|44100|48000
channel_masks AUDIO_CHANNEL_IN_MONO|AUDIO_CHANNEL_IN_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_IN_BUILTIN_MIC|AUDIO_DEVICE_IN_BLUETOOTH_SCO_HEADSET|AUDIO_DEVICE_IN_WIRED_HEADSET|AUDIO_DEVICE_IN_BACK_MIC
}
}
}
a2dp {
outputs {
a2dp {
sampling_rates 44100
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_ALL_A2DP
}
}
}
usb {
outputs {
usb_accessory {
sampling_rates 44100
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_USB_ACCESSORY
}
usb_device {
sampling_rates 44100
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_USB_DEVICE
}
}
}
}
Click to expand...
Click to collapse
Let me know if anyone else had this problem and if it worked for you.
I just put the previous code in the file with nothing else and rebooted.
I have only tested this on MMuzzy 4.2.1
Didn't seem to be the source of the problem for me. I'm on stock (rooted) and the a2dp values are already what you posted. The a2dp quality has gone to crap since the 4.2 update. There is compression type distortion on all the music I stream from my phone to my car. Is there any 4.2 ROM that has fixed this issue yet? This was perfect up until 4.1.2.
ra990 said:
Didn't seem to be the source of the problem for me. I'm on stock (rooted) and the a2dp values are already what you posted. The a2dp quality has gone to crap since the 4.2 update. There is compression type distortion on all the music I stream from my phone to my car. Is there any 4.2 ROM that has fixed this issue yet? This was perfect up until 4.1.2.
Click to expand...
Click to collapse
Oh wow, didn't know it was a 4.2 problem at all. Makes sense though. I'm not sure of any Roms that work around this at the moment. Keep me posted if you do.
I'm also running stock (rooted) and my audio_policy.conf had the same values you posted. The terrible sound quality is driving me insane! Are you using Google Music on your device? I think there might have been a change in Google Music that caused the problem when they introduced gapless playback. On my Motorola Xoom, running stock (rooted) 4.1, it sounded great before I updated to the new Google Music. Ever since the update, it sounds like crap. Rolling back to the old version does nothing. Maybe since Google Music is a system file on Google Experience devices, the update modified something else on the system level.
Aw man you guys are lucky you can at least steam your music to your car I can never get it to work using my gnex streaming to a Fiat Punto which uses blue and me. I can connect for calls to be made and received but never can get music to work.
Do you have to use bluetooth tether or something?
What I tried was connecting to Bluetooth on the car and press play on Google play music and nothing happens on the cars speakers just music plays of the phone.
I also tried a 3.5mm - USB and plugged that into the car and same results as above. I think the car doesn't support the file system of gnex.
Can you explain to me how you guys are streaming as I'd love to use this feature
Sent from my Galaxy Nexus
Are you sure that ad2p is working with your radio? Check manual!
Used it with a lot of cars and adapters.
Never get problems with connections or quality.
FrankNS said:
Are you sure that ad2p is working with your radio? Check manual!
Used it with a lot of cars and adapters.
Never get problems with connections or quality.
Click to expand...
Click to collapse
Personally I really don't know, to sound extremely noobish could you explain exactly how you go about streaming to a car?
Sent from my Galaxy Nexus
MetalMessiah78 said:
I'm also running stock (rooted) and my audio_policy.conf had the same values you posted. The terrible sound quality is driving me insane! Are you using Google Music on your device? I think there might have been a change in Google Music that caused the problem when they introduced gapless playback. On my Motorola Xoom, running stock (rooted) 4.1, it sounded great before I updated to the new Google Music. Ever since the update, it sounds like crap. Rolling back to the old version does nothing. Maybe since Google Music is a system file on Google Experience devices, the update modified something else on the system level.
Click to expand...
Click to collapse
Sorry for replying so late...
I'm experiencing the same issue as you but I can't say it was better on 4.1 because I only got my car at the beginning of December. I initially found Google Music to have this problem but since I have learned that Pandora is the same result.
My code fix did not fix it after I upgraded my ROM even after changing the code again in the new ROM. Not sure where the problem lies.
Any luck from anyone else?
I'm on 4.2.1 (CM10.1 M1), and I haven't had too many problems with bt streaming. I do think the quality use to be better on CM10, and a few times its paused itself randomly, but not so bad I want to connect a cable. I'm using PowerAmp as my music player, and the XtremeMac InCharge Auto BT.
It has been fixed in the latest nightly
Sent from my Nexus 4 using Tapatalk 2
Well I don't think it will fix audio streaming because I have tested it with CyanogenMod's audio_policy.conf!
At least I got it better a little bit and that file is included in my ROM, but that won't fix the audio streaming quality completely,I have also added CM's Bluetooth files ("/system/etc/bluetooth/") but still pretty same result..
Then I sent message to Cm dev team and I got reply that the Bluetooth files are incompatible with stock android ROM so it's not possible to fix A2DP streaming with CM's files!
But yeah, I know that audio_policy.conf is one of the files that affects to A2DP streaming quality..
manumanfred said:
Well I don't think it will fix audio streaming because I have tested it with CyanogenMod's audio_policy.conf!
At least I got it better a little bit and that file is included in my ROM, but that won't fix the audio streaming quality completely,I have also added CM's Bluetooth files ("/system/etc/bluetooth/") but still pretty same result..
Then I sent message to Cm dev team and I got reply that the Bluetooth files are incompatible with stock android ROM so it's not possible to fix A2DP streaming with CM's files!
But yeah, I know that audio_policy.conf is one of the files that affects to A2DP streaming quality..
Click to expand...
Click to collapse
Yes I was assuming everyone would understand you need to flash CM to get this fix....
Sent from my Nexus 4 using Tapatalk 2
FYI, i tested the BT Audio quality in my car tonight and it is MUCH MUCH better =) Cymbals are crisp!
Vanhoud said:
FYI, i tested the BT Audio quality in my car tonight and it is MUCH MUCH better =) Cymbals are crisp!
Click to expand...
Click to collapse
Are you using a new ROM? After flashing Aroma's, I have no issues with Bluetooth at all. He raised the streaming quality so its perfect now. Give it a try!
gfro9191 said:
Are you using a new ROM? After flashing Aroma's, I have no issues with Bluetooth at all. He raised the streaming quality so its perfect now. Give it a try!
Click to expand...
Click to collapse
yes im using the latest CM 10.1 nightly
can i play mpag dash video without encryption from Android apps without a third party SDK
its written in documentation that its supported in anderoid 4.4
Has anyone written such apps? Can you give an example?
¨Android 4.4 brings formal support for adaptive playback into the Android media framework. Adaptive playback is an optional feature of video decoders for MPEG-DASH and other formats that enables seamless change in resolution during playback. The client can start to feed the decoder input video frames of a new resolution and the resolution of the output buffers change automatically, and without a significant gap.¨
thanks
At $84, I'm tempted to buy one, but only if 1080p playback works flawlessly. Have the bugs finally been worked out?
Sizzlechest said:
At $84, I'm tempted to buy one, but only if 1080p playback works flawlessly. Have the bugs finally been worked out?
Click to expand...
Click to collapse
It depends on the codec within it. With XBMC or SPMC, I've found my Blu-Ray rips all technically play of course, but those whose video are encoded in VC-1 don't have hardware decoding and thus don't play smoothly. Those using MPEG-2 or H.264 play perfectly. To get around that, I transcoded such BR's to H.264 at a rather high quality (and kept the originals around for if / when VC-1 hardware decoding ever gets going).
On the audio side, I have pass-through enabled along with Dolby Digital encoding enabled for XBMC's audio transcode (that second part is necessary so something like 5.1 PCM, FLAC, Dolby True HD, or DTS Master audio can reach my receiver in 5.1, since Android devices currently can't pass full-bandwidth surround audio). Hope this helps you in making your decision.
The official listing has no details about the audio codecs supported, so I was wondering whether LDAC, AptX HD, and the likes are supported with this phone.
Thanks
Hope it is what you mean by supported codecs.