Chrome for Android update\ mp3 stream

[Elad Naimi]

Chrome for Android updated 2 days ago and since then jplayer doesn't work anymore with mp3 stream

I'm using jplayer 2.7

Thanks

[tta]

I've just been notified of the same issue from a user. (Android 4.4.2 with Chrome) 

[Elad Naimi]

Hi

Is there a chance for a fix in the coming days?

Please let me know... I have to find a solution for this soon

[Cyril Agard]

Hi, 

Today we noticed the same behavior on our site, but it was working fine in Google Chrome v.36.0.1985.122, but stopped working in latest one v.37.0.2062.117.

I spent whole day today, trying to find a workaround.

I found a solution, but it's kinda weird one.

In the source there is a special checks called 'androidFix', so if you disable a part of it, player starts working.

If you download latest jPlayer version 2.7.0, you can comment out line 1827, and it will work. Not sure, if it breaks old versions of android browsers, or Google Chrome (Checked on 4 devices, with different version of browsers, still works.)

// Setup the Android Fix - Only for HTML audio.
if($.jPlayer.platform.android) {
   //self.androidFix.setMedia = true;
}

I hope it will help somebody to have quick fix, while official one is coming.

[Ahmed Etman]

thank youuuuuu , you have saved me time and effort :)

[Richard Kaiser]

Yes, that does the job :) Thank you very much!

[Elad Naimi]

It's working  :)

Thanks!!!

On Wednesday, September 10, 2014 12:23:57 AM UTC+3, Cyril Agard wrote:

[croelec...@gmail.com]

I'm kind of lost here. i looked at jquery.jplayer.min.js file and I cannot figure out where to do change. Am I doing something wrong?

[tta]

Worked for me as well. Users report success (once they cleared their caches!). Thanks for this fix! 

[Elad Naimi]

instead of working with jquery.jplayer.min.js

delete that file

and replace it with jquery.jplayer.js

you can find it here http://jplayer.org/download/

latest release -> jplayer 2.7.0 --> [line 2] source

now follow the instructions like you did before

--
You received this message because you are subscribed to a topic in the Google Groups "jPlayer: HTML5 Audio & Video for jQuery" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jplayer/BoVUNok0yl4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jplayer+u...@googlegroups.com.
To post to this group, send email to jpl...@googlegroups.com.
Visit this group at http://groups.google.com/group/jplayer.
For more options, visit https://groups.google.com/d/optout.

--

 נינג'ה רקורדס. טכנאי ומעצב קול.

ninjarecords.co.il   |   052-5787652

[croelec...@gmail.com]

I was able to figure it out by myself. Thank you anyway. And I learned how to minimize Java code too in the process. I guess I had some extra time on my hands :-)

[AdamGuy]

The fix helped, but now I have users of older androids that can't use the player.

Hope a permanent fix is in the works :)

[Mark Panaghiston]

It is about time I commented on this thread...

First of all, thanks to Cyril, Elad and others that have helped in this thread.

The problem here is that Google keep moving the goal posts.

First of all they took about 4 years to fix a basic bug with the audio element... Simply change the SRC and tell it to play and OMFG that was too complicated. So we had to allow it time for a cup of warm milk and a biscuit in between changing the media URL and asking it to play. To do this, we used the progress event to ensure that the media element was ready and setup with the new URL and ready to play it without throwing the pacifier. We used the progress event as an alternative to the "wait 3 seconds and it should work" solution... After all, we are making every android user wait, so I wanted it to be the absolute minimum and robust time, hence the progress event.

Pretty much as we released the android fix, the mainstream - non google - devices, like Samsung, started working without the fix in the default browser.

In the current Android, the progress event does not fire in the same way as before. Before, changing the SRC would cause the progress event to fire, which we used to apply the fix. Now that never happens, so the fix is breaking all of android.

I am currently looking into other events that we could use for the purpose, otherwise we cannot fix both the old bugs while supporting the current release... And the current release will win if it comes to an ultimatum. ie., Just remove the fix.

It should be noted, that this android fix that I talk of only affected cases where you changed the media, such as a playlist.

Anywayz, I will be looking into this in detail and plan to release a solution next week.

[Mark Panaghiston]

My initial investigation into an alternative event shows the loadeddata event as a strong contender for the androidFix. My initial tests on a Nexus 7 and a really old 2.3 phone show it working well on both. (The current nexus 7 does not work with the current jPlayer 2.7.0 - And YES, it did when I published 2.7.0 a few weeks ago.)

[Mark Panaghiston]

The fix is on github, jPlayer 2.7.1. See post for more info:

https://groups.google.com/d/msg/jplayer/-i-Hb9gs8aM/07rI5BJg-bUJ

[Elad Naimi]

It's working

thanks!

[Jonathan2]

Looks like this HAS now been fixed with v2.7.1 on Github - you can download the file here:

https://raw.githubusercontent.com/happyworm/jPlayer/master/jquery.jplayer/jquery.jplayer.js

Given that this affects so many users, it's unfortunate that this isn't on the main download site.

The good news is that it's available all nice and compressed on cdnjs - just link to this instead of your local copy or having to mess around downloading the version on Github :)

//cdnjs.cloudflare.com/ajax/libs/jplayer/2.7.1/jquery.jplayer/jquery.jplayer.min.js