[GH-ISSUE #67] Doesn't work on Android Phone - Google Chrome browser #49

Closed
opened 2026-02-26 02:31:55 +03:00 by kerem · 28 comments
Owner

Originally created by @riteshpuj2013 on GitHub (Dec 16, 2015).
Original GitHub issue: https://github.com/koel/koel/issues/67

Hi Phanan,

I finally got it working. It works on and desktop as well phone. But on phone, it works only on firefox but not on chrome.

P.S: Phone is One plus one using Android L 5.1.1

Let me know if you need more details.

Thanks
Ritesh

Originally created by @riteshpuj2013 on GitHub (Dec 16, 2015). Original GitHub issue: https://github.com/koel/koel/issues/67 Hi Phanan, I finally got it working. It works on and desktop as well phone. But on phone, it works only on firefox but not on chrome. P.S: Phone is One plus one using Android L 5.1.1 Let me know if you need more details. Thanks Ritesh
kerem closed this issue 2026-02-26 02:31:55 +03:00
Author
Owner

@Thom-x commented on GitHub (Dec 16, 2015):

Music is also not loading on Android M 6.0.1 (no error in console).

<!-- gh-comment-id:165027190 --> @Thom-x commented on GitHub (Dec 16, 2015): Music is also not loading on Android M 6.0.1 (no error in console).
Author
Owner

@itinerant-fox commented on GitHub (Dec 16, 2015):

Tried on Note 4 - Android version 5.0.1 Stock - Chrome browser .
Page loaded fine. Music streaming didn't work in Mobile Chrome Browser.
Everything working fine in Mobile firefox.

<!-- gh-comment-id:165070715 --> @itinerant-fox commented on GitHub (Dec 16, 2015): Tried on Note 4 - Android version 5.0.1 Stock - Chrome browser . Page loaded fine. Music streaming didn't work in Mobile Chrome Browser. Everything working fine in Mobile firefox.
Author
Owner

@MarceauKa commented on GitHub (Dec 16, 2015):

Galaxy Alpha - Android 5.0.2 - Chrome and Native browser.
All is fine on my local network.

<!-- gh-comment-id:165072175 --> @MarceauKa commented on GitHub (Dec 16, 2015): Galaxy Alpha - Android 5.0.2 - Chrome and Native browser. All is fine on my local network.
Author
Owner

@riteshpuj2013 commented on GitHub (Dec 16, 2015):

My google chrome version is 47.0.2526.83

I hope it helps to debug the issue further.

<!-- gh-comment-id:165086081 --> @riteshpuj2013 commented on GitHub (Dec 16, 2015): My google chrome version is 47.0.2526.83 I hope it helps to debug the issue further.
Author
Owner

@etopian commented on GitHub (Dec 16, 2015):

we should not be using the ♫ character for the path. that seems to break chrome's paths. it's cute, but unnecessary.

<!-- gh-comment-id:165292116 --> @etopian commented on GitHub (Dec 16, 2015): we should not be using the ♫ character for the path. that seems to break chrome's paths. it's cute, but unnecessary.
Author
Owner

@phanan commented on GitHub (Dec 17, 2015):

we should not be using the ♫ character for the path. that seems to break chrome's paths. it's cute, but unnecessary.

That character doesn't have anything to do with song playback. Every browser I know supports utf-8 URLs anyway.

<!-- gh-comment-id:165316591 --> @phanan commented on GitHub (Dec 17, 2015): > we should not be using the ♫ character for the path. that seems to break chrome's paths. it's cute, but unnecessary. That character doesn't have anything to do with song playback. Every browser I know supports utf-8 URLs anyway.
Author
Owner

@etopian commented on GitHub (Dec 17, 2015):

Perhaps I have a problem with the nginx configuration. for me the page did not load on chrome on android.

<!-- gh-comment-id:165316925 --> @etopian commented on GitHub (Dec 17, 2015): Perhaps I have a problem with the nginx configuration. for me the page did not load on chrome on android.
Author
Owner

@etopian commented on GitHub (Dec 17, 2015):

The URL gets escaped in Chrome on Android, this is on purpose by Chrome, this is Chrome 44. And that results in NotFoundHttpException. Changing that route to the URL 'm' works for me.

<!-- gh-comment-id:165317982 --> @etopian commented on GitHub (Dec 17, 2015): The URL gets escaped in Chrome on Android, this is on purpose by Chrome, this is Chrome 44. And that results in NotFoundHttpException. Changing that route to the URL 'm' works for me.
Author
Owner

@phanan commented on GitHub (Dec 17, 2015):

I'd suggest checking your nginx conf then.

<!-- gh-comment-id:165327758 --> @phanan commented on GitHub (Dec 17, 2015): I'd suggest checking your nginx conf then.
Author
Owner

@kevincaradant commented on GitHub (Dec 17, 2015):

@etopian , what is your configuration to work on your mobile phone or even a device other that the server itself ? localhost:8080 on server OK that work. but on my computer or smartphone , i can't have KOEL even by IP on the URL :( .

I tried apache but i failed and i wish to try with nginx but everytime that said me "error 404" or "forbidden 403" but i don't think it's a problem of rights... if you can explain me step by step , it should be very nice from you.

I just put all files of koel in /var/www/koel/html. And try to follow this tuto unsuccessfully :/ : https://www.digitalocean.com/community/tutorials/how-to-set-up-nginx-server-blocks-virtual-hosts-on-ubuntu-14-04-lts.

So this is my state :

capturenginx
capturenginx2

Thank you in advance :)

<!-- gh-comment-id:165445191 --> @kevincaradant commented on GitHub (Dec 17, 2015): @etopian , what is your configuration to work on your mobile phone or even a device other that the server itself ? localhost:8080 on server OK that work. but on my computer or smartphone , i can't have KOEL even by IP on the URL :( . I tried apache but i failed and i wish to try with nginx but everytime that said me "error 404" or "forbidden 403" but i don't think it's a problem of rights... if you can explain me step by step , it should be very nice from you. I just put all files of koel in /var/www/koel/html. And try to follow this tuto unsuccessfully :/ : https://www.digitalocean.com/community/tutorials/how-to-set-up-nginx-server-blocks-virtual-hosts-on-ubuntu-14-04-lts. So this is my state : ![capturenginx](https://cloud.githubusercontent.com/assets/6093175/11870104/fc78def6-a4c4-11e5-892a-fb9eb255b5f6.PNG) ![capturenginx2](https://cloud.githubusercontent.com/assets/6093175/11870103/fc77714c-a4c4-11e5-8ebd-088899423c80.PNG) Thank you in advance :)
Author
Owner

@etopian commented on GitHub (Dec 17, 2015):

@kevincaradant i use my docker image.. https://github.com/etopian/docker-koel

<!-- gh-comment-id:165447066 --> @etopian commented on GitHub (Dec 17, 2015): @kevincaradant i use my docker image.. https://github.com/etopian/docker-koel
Author
Owner

@kevincaradant commented on GitHub (Dec 17, 2015):

Ah oki nice , i'm going to try ! :).

<!-- gh-comment-id:165451568 --> @kevincaradant commented on GitHub (Dec 17, 2015): Ah oki nice , i'm going to try ! :).
Author
Owner

@MyIgel commented on GitHub (Dec 19, 2015):

I have debugged it on my android phone (5.1.1, cm12.1) with the latest Chrome Beta:

Uncaught TypeError: Failed to construct 'Notification': Illegal constructor. Use ServiceWorkerRegistration.showNotification() instead.
t.default.play @ main-56b549c9de.js:14
(anonymous function) @ main-56b549c9de.js:14
e @ main-56b549c9de.js:7

the related Code is

[...] n=new Notification("♫ "+e.title,{icon:e.album.cover,body:e.album.name+" – "+e.album.artist.name}); [...]

in resources/assets/js/services/playback.js:97

the Notification() has been removed from Chrome on Android, see here

<!-- gh-comment-id:166022360 --> @MyIgel commented on GitHub (Dec 19, 2015): I have debugged it on my android phone (5.1.1, cm12.1) with the latest Chrome Beta: ``` Uncaught TypeError: Failed to construct 'Notification': Illegal constructor. Use ServiceWorkerRegistration.showNotification() instead. t.default.play @ main-56b549c9de.js:14 (anonymous function) @ main-56b549c9de.js:14 e @ main-56b549c9de.js:7 ``` the related Code is ``` javascript [...] n=new Notification("♫ "+e.title,{icon:e.album.cover,body:e.album.name+" – "+e.album.artist.name}); [...] ``` in resources/assets/js/services/playback.js:97 the Notification() has been removed from Chrome on Android, see [here](http://stackoverflow.com/a/31787926)
Author
Owner

@phanan commented on GitHub (Dec 20, 2015):

Damn! More work for us, thanks Chrome team!

<!-- gh-comment-id:166053391 --> @phanan commented on GitHub (Dec 20, 2015): Damn! More work for us, thanks Chrome team!
Author
Owner

@lazyhummingbird commented on GitHub (Dec 20, 2015):

I saw this bugfix (wow you're fast!), but how do I implement it now that I've replaced the file? Do I have to reinstall koel entirely or is there a way I can just update it?

<!-- gh-comment-id:166079206 --> @lazyhummingbird commented on GitHub (Dec 20, 2015): I saw this bugfix (wow you're fast!), but how do I implement it now that I've replaced the file? Do I have to reinstall koel entirely or is there a way I can just update it?
Author
Owner

@phanan commented on GitHub (Dec 20, 2015):

Just git pull and then gulp --production ;)

On Sun, Dec 20, 2015 at 3:36 PM, lazyhummingbird notifications@github.com
wrote:

I saw this bugfix (wow you're fast!), but how do I implement it now that
I've replaced the file? Do I have to reinstall koel entirely or is there a
way I can just update it?


Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/issues/67#issuecomment-166079206.

<!-- gh-comment-id:166089188 --> @phanan commented on GitHub (Dec 20, 2015): Just `git pull` and then `gulp --production` ;) On Sun, Dec 20, 2015 at 3:36 PM, lazyhummingbird notifications@github.com wrote: > I saw this bugfix (wow you're fast!), but how do I implement it now that > I've replaced the file? Do I have to reinstall koel entirely or is there a > way I can just update it? > > — > Reply to this email directly or view it on GitHub > https://github.com/phanan/koel/issues/67#issuecomment-166079206.
Author
Owner

@lazyhummingbird commented on GitHub (Dec 20, 2015):

I double checked that playback.js was up to date and did 'gulp --production' but I'm still having the same error :/

Sorry to resurrect this bug. This whole project is great work and I can't wait until it works on my mobile device.

<!-- gh-comment-id:166151122 --> @lazyhummingbird commented on GitHub (Dec 20, 2015): I double checked that playback.js was up to date and did 'gulp --production' but I'm still having the same error :/ Sorry to resurrect this bug. This whole project is great work and I can't wait until it works on my mobile device.
Author
Owner

@pelletiermaxime commented on GitHub (Dec 20, 2015):

Just tried on Android and had no sound in Chrome/Opera. Works fine in Firefox.

<!-- gh-comment-id:166157183 --> @pelletiermaxime commented on GitHub (Dec 20, 2015): Just tried on Android and had no sound in Chrome/Opera. Works fine in Firefox.
Author
Owner

@phanan commented on GitHub (Dec 21, 2015):

Now to think about it, that audio isn't being played shouldn't have anything to do with notifications. The play() method is executed before notification happens.

<!-- gh-comment-id:166176826 --> @phanan commented on GitHub (Dec 21, 2015): Now to think about it, that audio isn't being played shouldn't have anything to do with notifications. The `play()` method is executed before notification happens.
Author
Owner

@phanan commented on GitHub (Dec 21, 2015):

Sadly I don't have an Android to test.

<!-- gh-comment-id:166176852 --> @phanan commented on GitHub (Dec 21, 2015): Sadly I don't have an Android to test.
Author
Owner

@Dogfalo commented on GitHub (Dec 21, 2015):

@phanan, I was also having problems on my Android Chrome. Maybe if I have time tomorrow I will take a look

<!-- gh-comment-id:166199509 --> @Dogfalo commented on GitHub (Dec 21, 2015): @phanan, I was also having problems on my Android Chrome. Maybe if I have time tomorrow I will take a look
Author
Owner

@Dogfalo commented on GitHub (Dec 28, 2015):

@phanan,
I took a very brief look last week, there were no console errors. I think the problem may be related to this:

http://stackoverflow.com/questions/31843020/using-htaccess-authentication-breaks-html-audio-elements-in-chrome-android
Chromium bug tracker: https://code.google.com/p/chromium/issues/detail?id=331876

<!-- gh-comment-id:167678789 --> @Dogfalo commented on GitHub (Dec 28, 2015): @phanan, I took a very brief look last week, there were no console errors. I think the problem may be related to this: http://stackoverflow.com/questions/31843020/using-htaccess-authentication-breaks-html-audio-elements-in-chrome-android Chromium bug tracker: https://code.google.com/p/chromium/issues/detail?id=331876
Author
Owner

@phanan commented on GitHub (Dec 29, 2015):

Well, except Koel doesn't use htaccess basic auth...

On Tue, Dec 29, 2015 at 7:28 AM, Alvin Wang notifications@github.com
wrote:

@phanan https://github.com/phanan,
I took a very brief look last week, there were no console errors. I think
the problem may be related to this:

http://stackoverflow.com/questions/31843020/using-htaccess-authentication-breaks-html-audio-elements-in-chrome-android


Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/issues/67#issuecomment-167678789.

<!-- gh-comment-id:167690463 --> @phanan commented on GitHub (Dec 29, 2015): Well, except Koel doesn't use htaccess basic auth... On Tue, Dec 29, 2015 at 7:28 AM, Alvin Wang notifications@github.com wrote: > @phanan https://github.com/phanan, > I took a very brief look last week, there were no console errors. I think > the problem may be related to this: > > http://stackoverflow.com/questions/31843020/using-htaccess-authentication-breaks-html-audio-elements-in-chrome-android > > — > Reply to this email directly or view it on GitHub > https://github.com/phanan/koel/issues/67#issuecomment-167678789.
Author
Owner

@Dogfalo commented on GitHub (Dec 29, 2015):

ok I did more digging. It is a bug related to chrome and Partial Content (206). I tried commenting that out and it worked in chrome on android. But it essentially removes the "streaming" aspect as it needs to download the song first before playing.. Not really sure how this can be fixed if it is a problem with chrome

<!-- gh-comment-id:167739105 --> @Dogfalo commented on GitHub (Dec 29, 2015): ok I did more digging. It is a bug related to chrome and Partial Content (206). I tried commenting that out and it worked in chrome on android. But it essentially removes the "streaming" aspect as it needs to download the song first before playing.. Not really sure how this can be fixed if it is a problem with chrome
Author
Owner

@phanan commented on GitHub (Dec 29, 2015):

Thanks. If it's Chrome then I guess it will be fixed in no time. I have
high trust in the team.

On Tue, Dec 29, 2015 at 3:28 PM, Alvin Wang notifications@github.com
wrote:

ok I did more digging. It is a bug related to chrome and Partial Content
(206). I tried commenting that out and it worked in chrome on android. But
it essentially removes the "streaming" aspect as it needs to download the
song first before playing.. Not really sure how this can be fixed if it is
a problem with chrome


Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/issues/67#issuecomment-167739105.

<!-- gh-comment-id:167739761 --> @phanan commented on GitHub (Dec 29, 2015): Thanks. If it's Chrome then I guess it will be fixed in no time. I have high trust in the team. On Tue, Dec 29, 2015 at 3:28 PM, Alvin Wang notifications@github.com wrote: > ok I did more digging. It is a bug related to chrome and Partial Content > (206). I tried commenting that out and it worked in chrome on android. But > it essentially removes the "streaming" aspect as it needs to download the > song first before playing.. Not really sure how this can be fixed if it is > a problem with chrome > > — > Reply to this email directly or view it on GitHub > https://github.com/phanan/koel/issues/67#issuecomment-167739105.
Author
Owner

@Isaiahjm commented on GitHub (Feb 29, 2016):

@Dogfalo May I ask how you went about commenting out the cause of the issue? This bug in Chrome has prevented me from using koel since the first release. It just sits idle on my server. Would be great if we could add the temporary work around in the wiki as well for those thinking about using koel.

<!-- gh-comment-id:190177319 --> @Isaiahjm commented on GitHub (Feb 29, 2016): @Dogfalo May I ask how you went about commenting out the cause of the issue? This bug in Chrome has prevented me from using koel since the first release. It just sits idle on my server. Would be great if we could add the temporary work around in the wiki as well for those thinking about using koel.
Author
Owner

@lazyhummingbird commented on GitHub (Apr 18, 2016):

@Dogfalo @phanan any chance that either of you can detail the fix?

<!-- gh-comment-id:211535538 --> @lazyhummingbird commented on GitHub (Apr 18, 2016): @Dogfalo @phanan any chance that either of you can detail the fix?
Author
Owner

@ZJUGuoShuai commented on GitHub (Oct 4, 2018):

Still cannot play on Chrome for Android 69...

<!-- gh-comment-id:427072239 --> @ZJUGuoShuai commented on GitHub (Oct 4, 2018): Still cannot play on Chrome for Android 69...
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#49
No description provided.