I hope I'm using the correct terminology concerning Bluetooth. Here's my situation:
When connecting to my car's built-in bluetooth audio with stock ROM the music artist, song title, album, etc work great. I can skip and pause songs. This also works on other TouchWiz roms like i747z. This is using Google Music.
However, every time I try to use any CM builds I lose those features on my car radio. I can still skip songs and pause but I don't get any of the music info. So I'm wondering if it's something in the ROM or something in the kernel that is causing that loss of features.
Has anyone seen something similar and figure out a way around it. I love CM but I really miss that feature when I don't have it. Thanks
Jooced said:
I hope I'm using the correct terminology concerning Bluetooth. Here's my situation:
When connecting to my car's built-in bluetooth audio with stock ROM the music artist, song title, album, etc work great. I can skip and pause songs. This also works on other TouchWiz roms like i747z. This is using Google Music.
However, every time I try to use any CM builds I lose those features on my car radio. I can still skip songs and pause but I don't get any of the music info. So I'm wondering if it's something in the ROM or something in the kernel that is causing that loss of features.
Has anyone seen something similar and figure out a way around it. I love CM but I really miss that feature when I don't have it. Thanks
Click to expand...
Click to collapse
That's actually a problem with AOSP 4.2 and I don't think much can be done until we see official 4.2.
P.S.: It's called AVRCP.
I am getting a loud pop whenever I am changing tracks in any music player. Its a short pop but it is very loud and hurts my ears when I have headphones on. The problem occurs with the external speaker too. It does not appear to happen with every single song, only a select few. I double checked the song files on my computer and they play fine without a loud pop. I have also resynced my music to rule out corrupt mp3 files.
I am experiencing this problem on Slimbean 4.3 RC1/RC2 and Slimhalo RC2. I do not recall this issue when I was using CM10.1. Also, this issue manifests itself even after a fresh clean rom install leading me to think that the problem is inherent in Slimbean itself but my friend is also on Slimhalo RC2 but he claims that he doesnt have an issue.
Any ideas?
On cyanogenmod (cm-12.1-20150822-NIGHTLY-m8), but this problem has been occurring since 12.0. Any time I start new audio either using the default 'Music' or Google 'Play Music' audio players, there is a very loud audio pop before the music starts. When this occurs with headphones, its far too loud and could easily lead to audio loss. Seems to only occur on the first playback attempt.
Video below demonstrating the default CM12.1 audio player -- but can also be reproed with Google Play Music, thus a OS problem: https://www.youtube.com/watch?v=CTXcKklggeY
2 days ago, I update my one m8 from cm 12.1 to cm 13, and i found since then I could not play music or video normally.
For audio file, it skips and finishes a 3-minute song within a few seconds, but seems ok with short audio files like whatsapp recordings.
For video, it cannot play .mp4 but still can play .flv.
At first I thought it maybe the problem of my new sdcard, but I put one song in internal storage, nothing changes.
I tried turning back to cm 12.1 and it did not help. Everytime I do clean install.
I really don't know how to fix this.:crying:
Hi there,
I noticed problems with some of my podcasts. They would restart from the beginning when I tried to skip within the track or the player would crash and skip to the next track. I discovered that this only happens with MP3s that are encoded with either VBR (variable bitrate) or ABR (average bitrate) settings, and it is happening with every player (play music, music, pocketcasts) I tried. I converted some of those podcasts using constant bitrate (CBR) and everything worked fine then. I found an old thread (https://code.google.com/p/android/issues/detail?id=8154) describing pretty much exactly my problem.
I tried the same MP3 on my old S4, and that seems to be able to deal with the variable bitrate just fine.
Can anyone try to verify this? There is an ABR MP3 here which gives me those problems. If you skip towards the end it will start playing from the beginning ("Hey everybody this is Sam")
Cheers.
I just played your mp3 straight from the default Files app on my (stock) OP3 and tested two players: the default Music player and Google Play Music. Both were able to skip around just fine. Are you playing the file from a music player or from a podcast app? (Edit: I see where you said which players you tested. Hmm.)
The problem seems to happen after skipping to somewhere past the halfway mark of the file. I just tested it on a colleague's OP3 (3.2.4, all stock) and it happens there as well.
Funnily enough, I just listened to a podcast today when the host mentioned that one of the listeners wrote in with this exact same problem. A quick look into their backcatalog revealed them switching from CBR to VBR a couple of episodes ago.
I don't know what I was doing the first time when I tested, but yeah, now that I'm looking for it, I definitely see the issue. The very first time I played it this time, it auto skipped to the end and would have played the next track in the queue if one existed. From that point on, skipping around did a variety of things. Sometimes it worked; sometimes it played the audio from the very beginning ("Hey everybody, this is Sam") but the slider indicated I was still like 66% of the way through - not at the beginning. Very strange. I'm on the latest 3.2.6, btw.
When you're encoding to VBR, are you using any switches / arguments (e.g. --alt-preset standard)? If so, maybe try something else?
I haven't done any encoding myself (but for back converting some VBR tracks to CBR), I only noticed it in a couple of podcasts I was following, and the thing they had in common was NOT using CBR. I don't know if a certain switch in the VBR/ABR encoding settings might be the problem, but what I find more worrying is that my former sony xperia z5c running marshmallow as well as my s4 active running lollipop do not have this problem. It would be interesting if someone with CM or another ROM but stock could try this to see if it is a ROM specific problem.
A podcast I listen to (The Bayesian Conspiracy) has some episodes as CBR and some as VBR. All of the VBR episodes have issues trying to seek past half-way. This happens on ALL methods of playback that I've tried (streaming, Pocket Cast, Google built-in player, Podcast Addict) on my OnePlus 3.
Found an article ("The First and last word on CBR vs VBR questions" - sorry can't create links yet) talks about why VBR is bad, in general and why podcasts shouldn't use it anymore, but it sure does suck that OxygenOS doesn't handle this properly (because not every podcast is encoded with CBR).
I have contacted the podcasts which I discovered used VBR and ABR and so far I was lucky in that they switched back to CBR, but that can't be the solution.
I have this problem with my config: DailyTechNewsShow with either BeyondPod or PodcastAddict, same problem when reaching 2/3 of the time.
Using OnePlus3 stock with rom 3.2.8.
2 years later, i have the same issue on a Xiaomi Mi A2 Lite. i guess it won't be fixed any time soon...
does anyone know a place where we could report this bug to Xiaomi?
AFAIU, the bug is in their playback code, not in Android. i listen to podcasts a lot, some of them use VBR, and it's annoying me to no end...