Revision history [back]

Steps to reproduce:

1. Live in Finland - I'm not sure if the stream works abroad. Should apply to others, too...
2. Open Jolla browser and head over to http://www.radiorock.fi
3. Wait until the page loads
4. Click the play/pause symbol on top of the page to start streaming
5. Enjoy the show, and notice device rather quickly warming up

Everything worked as expected, but after some 20 minutes of playing the stream, I took the device off the charger, and noticed it was way too hot! I checked CPU usage using terminal and utility 'top' noticing the browser process using about 45-65% of CPU, pulseaudio was using about 5%, and bluetooth using 1-2%, as I was connected to Logitech bluetooth receiver. I also later checked if not using bluetooth had any difference, but sailfish-browse still used the same amount of CPU power.

This CPU usage seems very high to me. If I stop the stream, CPU usage goes down to idle. I suspect it's in the internal handling of the stream or perhaps missing hardware decoding. The actual stream - this took some digging - is http://83.102.39.40/Radiorock.mp3 and now having created .PLS to play it using the built-in browser, CPU usage is roughly 12-17% for pulseaudio and 3-6% for jolla-mediaplay, the percentages apply to also playing regular MP3 file.

This can be circumvented by digging the actual stream, wrapping it in .PLS and playing that insted, but it's out of usual users' reach - not out of usual Jolla users' reach, though! Does the streaming really hog up that much juice, or could that be optimized somehow?

Oh yeah, I use software version 1.0.7.18 (.16) now, but there doesn't seem to be anything connection-related on this.

Steps to reproduce:

1. Live in Finland - I'm not sure if the stream works abroad. Should apply to others, too...
2. Open Jolla browser and head over to http://www.radiorock.fi
3. Wait until the page loads
4. Click the play/pause symbol on top of the page to start streaming
5. Enjoy the show, and notice device rather quickly warming up

Everything worked as expected, but after some 20 minutes of playing the stream, I took the device off the charger, and noticed it was way too hot! I checked CPU usage using terminal and utility 'top' noticing the browser process using about 45-65% of CPU, pulseaudio was using about 5%, and bluetooth using 1-2%, as I was connected to Logitech bluetooth receiver. I also later checked if not using bluetooth had any difference, but sailfish-browse still used the same amount of CPU power.

This CPU usage seems very high to me. If I stop the stream, CPU usage goes down to idle. I suspect it's in the internal handling of the stream or perhaps missing hardware decoding. The actual stream - this took some digging - is http://83.102.39.40/Radiorock.mp3 and now having created .PLS to play it using the built-in browser, CPU usage is roughly 12-17% for pulseaudio and 3-6% for jolla-mediaplay, the percentages apply to also playing regular MP3 file.

This can be circumvented by digging the actual stream, wrapping it in .PLS and playing that insted, but it's out of usual users' reach - not out of usual Jolla users' reach, though! Does the streaming really hog up that much juice, or could that be optimized somehow?

Oh yeah, I use software version 1.0.7.18 (.16) now, but there doesn't seem to be anything connection-related on this.

Steps to reproduce:

1. Live in Finland - I'm not sure if the stream works abroad. Should apply to others, too...
2. Open Jolla browser and head over to http://www.radiorock.fi
3. Wait until the page loads
4. Click the play/pause symbol on top of the page to start streaming
5. Enjoy the show, and notice device rather quickly warming up

Everything worked as expected, but after some 20 minutes of playing the stream, I took the device off the charger, and noticed it was way too hot! I checked CPU usage using terminal and utility 'top' noticing the browser process using about 45-65% of CPU, pulseaudio was using about 5%, and bluetooth using 1-2%, as I was connected to Logitech bluetooth receiver. I also later checked if not using bluetooth had any difference, but sailfish-browse still used the same amount of CPU power.

This CPU usage seems very high to me. If I stop the stream, CPU usage goes down to idle. I suspect it's in the internal handling of the stream or perhaps missing hardware decoding. The actual stream - this took some digging - is http://83.102.39.40/Radiorock.mp3 and now having created .PLS to play it using the built-in browser, CPU usage is roughly 12-17% for pulseaudio and 3-6% for jolla-mediaplay, the percentages apply to also playing regular MP3 file.

This can be circumvented by digging the actual stream, wrapping it in .PLS and playing that insted, but it's out of usual users' reach - not out of usual Jolla users' reach, though! Does the streaming really hog up that much juice, or could that be optimized somehow?

Oh yeah, I use software version 1.0.7.18 (.16) now, but there doesn't seem to be anything connection-related on this.

Edit: Fixed tags.

Steps to reproduce:

1. Live in Finland - I'm not sure if the stream works abroad. Should apply to others, too...
2. Open Jolla browser and head over to http://www.radiorock.fi
3. Wait until the page loads
4. Click the play/pause symbol on top of the page to start streaming
5. Enjoy the show, and notice device rather quickly warming up

Everything worked as expected, but after some 20 minutes of playing the stream, I took the device off the charger, and noticed it was way too hot! I checked CPU usage using terminal and utility 'top' noticing the browser process using about 45-65% of CPU, pulseaudio was using about 5%, and bluetooth using 1-2%, as I was connected to Logitech bluetooth receiver. I also later checked if not using bluetooth had any difference, but sailfish-browse still used the same amount of CPU power.

This CPU usage seems very high to me. If I stop the stream, CPU usage goes down to idle. I suspect it's in the internal handling of the stream or perhaps missing hardware decoding. The actual stream - this took some digging - is http://83.102.39.40/Radiorock.mp3 and now having created .PLS to play it using the built-in browser, CPU usage is roughly 12-17% for pulseaudio and 3-6% for jolla-mediaplay, the percentages apply to also playing regular MP3 file.

This can be circumvented by digging the actual stream, wrapping it in .PLS and playing that insted, but it's out of usual users' reach - not out of usual Jolla users' reach, though! Does the streaming really hog up that much juice, or could that be optimized somehow?

Oh yeah, I use software version 1.0.7.18 (.16) now, but there doesn't seem to be anything connection-related on this.

Edit: Fixed tags.

Steps to reproduce:

1. Live in Finland - I'm not sure if the stream works abroad. Should apply to others, too...
2. Open Jolla browser and head over to http://www.radiorock.fi
3. Wait until the page loads
4. Click the play/pause symbol on top of the page to start streaming
5. Enjoy the show, and notice device rather quickly warming up

Everything worked as expected, but after some 20 minutes of playing the stream, I took the device off the charger, and noticed it was way too hot! I checked CPU usage using terminal and utility 'top' noticing the browser process using about 45-65% of CPU, pulseaudio was using about 5%, and bluetooth using 1-2%, as I was connected to Logitech bluetooth receiver. I also later checked if not using bluetooth had any difference, but sailfish-browse still used the same amount of CPU power.

This CPU usage seems very high to me. If I stop the stream, CPU usage goes down to idle. I suspect it's in the internal handling of the stream or perhaps missing hardware decoding. The actual stream - this took some digging - is http://83.102.39.40/Radiorock.mp3 and now having created .PLS to play it using the built-in browser, CPU usage is roughly 12-17% for pulseaudio and 3-6% for jolla-mediaplay, the percentages apply to also playing regular MP3 file.

This can be circumvented by digging the actual stream, wrapping it in .PLS and playing that insted, but it's out of usual users' reach - not out of usual Jolla users' reach, though! Does the streaming really hog up that much juice, or could that be optimized somehow?

Oh yeah, I use software version 1.0.7.18 (.16) now, but there doesn't seem to be anything connection-related on this.

Edit: Fixed tags.

Steps to reproduce:

1. Live in Finland - I'm not sure if the stream works abroad. Should apply to others, too...
2. Open Jolla browser and head over to http://www.radiorock.fi
3. Wait until the page loads
4. Click the play/pause symbol on top of the page to start streaming
5. Enjoy the show, and notice device rather quickly warming up

Everything worked as expected, but after some 20 minutes of playing the stream, I took the device off the charger, and noticed it was way too hot! I checked CPU usage using terminal and utility 'top' noticing the browser process using about 45-65% of CPU, pulseaudio was using about 5%, and bluetooth using 1-2%, as I was connected to Logitech bluetooth receiver. I also later checked if not using bluetooth had any difference, but sailfish-browse still used the same amount of CPU power.

This CPU usage seems very high to me. If I stop the stream, CPU usage goes down to idle. I suspect it's in the internal handling of the stream or perhaps missing hardware decoding. The actual stream - this took some digging - is http://83.102.39.40/Radiorock.mp3 and now having created .PLS to play it using the built-in browser, CPU usage is roughly 12-17% for pulseaudio and 3-6% for jolla-mediaplay, the percentages apply to also playing regular MP3 file.

This can be circumvented by digging the actual stream, wrapping it in .PLS and playing that insted, but it's out of usual users' reach - not out of usual Jolla users' reach, though! Does the streaming really hog up that much juice, or could that be optimized somehow?

Oh yeah, I use software version 1.0.7.18 (.16) now, but there doesn't seem to be anything connection-related on this.

Edit: Fixed tags.

Steps to reproduce:

1. Live in Finland - I'm not sure if the stream works abroad. Should apply to others, too...
2. Open Jolla browser and head over to http://www.radiorock.fi
3. Wait until the page loads
4. Click the play/pause symbol on top of the page to start streaming
5. Enjoy the show, and notice device rather quickly warming up

Everything worked as expected, but after some 20 minutes of playing the stream, I took the device off the charger, and noticed it was way too hot! I checked CPU usage using terminal and utility 'top' noticing the browser process using about 45-65% of CPU, pulseaudio was using about 5%, and bluetooth using 1-2%, as I was connected to Logitech bluetooth receiver. I also later checked if not using bluetooth had any difference, but sailfish-browse still used the same amount of CPU power.

This CPU usage seems very high to me. If I stop the stream, CPU usage goes down to idle. I suspect it's in the internal handling of the stream or perhaps missing hardware decoding. The actual stream - this took some digging - is http://83.102.39.40/Radiorock.mp3 and now having created .PLS to play it using the built-in browser, CPU usage is roughly 12-17% for pulseaudio and 3-6% for jolla-mediaplay, the percentages apply to also playing regular MP3 file.

This can be circumvented by digging the actual stream, wrapping it in .PLS and playing that insted, but it's out of usual users' reach - not out of usual Jolla users' reach, though! Does the streaming really hog up that much juice, or could that be optimized somehow?

Oh yeah, I use software version 1.0.7.18 (.16) now, but there doesn't seem to be anything connection-related on this.

Edit: Fixed tags.

Edit 2015-09-12: Now running 1.1.9.28, 1.1.9.28 and it seems I can't stream anything using the browser! browser! Also, that IP address no longer seems to work. YouTube still works, so I think it may be only MP3 streaming issue... Could anyone confirm that?that? Disregard that, reboot helped.

Steps to reproduce:

1. Live in Finland - I'm not sure if the stream works abroad. Should apply to others, too...
2. Open Jolla browser and head over to http://www.radiorock.fi
3. Wait until the page loads
4. Click the play/pause symbol on top of the page to start streaming
5. Enjoy the show, and notice device rather quickly warming up

Everything worked as expected, but after some 20 minutes of playing the stream, I took the device off the charger, and noticed it was way too hot! I checked CPU usage using terminal and utility 'top' noticing the browser process using about 45-65% of CPU, pulseaudio was using about 5%, and bluetooth using 1-2%, as I was connected to Logitech bluetooth receiver. I also later checked if not using bluetooth had any difference, but sailfish-browse still used the same amount of CPU power.

This CPU usage seems very high to me. If I stop the stream, CPU usage goes down to idle. I suspect it's in the internal handling of the stream or perhaps missing hardware decoding. The actual stream - this took some digging - is http://83.102.39.40/Radiorock.mp3 and now having created .PLS to play it using the built-in browser, CPU usage is roughly 12-17% for pulseaudio and 3-6% for jolla-mediaplay, the percentages apply to also playing regular MP3 file.

This can be circumvented by digging the actual stream, wrapping it in .PLS and playing that insted, but it's out of usual users' reach - not out of usual Jolla users' reach, though! Does the streaming really hog up that much juice, or could that be optimized somehow?

Oh yeah, I use software version 1.0.7.18 (.16) now, but there doesn't seem to be anything connection-related on this.

Edit: Fixed tags.

Edit 2015-09-12: Now running 1.1.9.28 and it seems I can't stream anything using the browser! Also, that IP address no longer seems to work. YouTube still works, so I think it may be only MP3 streaming issue... Could anyone confirm that? that? Disregard that, reboot helped.

Steps to reproduce:

1. Live in Finland - I'm not sure if the stream works abroad. Should apply to others, too...
2. Open Jolla browser and head over to http://www.radiorock.fi
3. Wait until the page loads
4. Click the play/pause symbol on top of the page to start streaming
5. Enjoy the show, and notice device rather quickly warming up

Everything worked as expected, but after some 20 minutes of playing the stream, I took the device off the charger, and noticed it was way too hot! I checked CPU usage using terminal and utility 'top' noticing the browser process using about 45-65% of CPU, pulseaudio was using about 5%, and bluetooth using 1-2%, as I was connected to Logitech bluetooth receiver. I also later checked if not using bluetooth had any difference, but sailfish-browse still used the same amount of CPU power.

This CPU usage seems very high to me. If I stop the stream, CPU usage goes down to idle. I suspect it's in the internal handling of the stream or perhaps missing hardware decoding. The actual stream - this took some digging - is http://83.102.39.40/Radiorock.mp3 and now having created .PLS to play it using the built-in browser, CPU usage is roughly 12-17% for pulseaudio and 3-6% for jolla-mediaplay, the percentages apply to also playing regular MP3 file.

This can be circumvented by digging the actual stream, wrapping it in .PLS and playing that insted, but it's out of usual users' reach - not out of usual Jolla users' reach, though! Does the streaming really hog up that much juice, or could that be optimized somehow?

Oh yeah, I use software version 1.0.7.18 (.16) now, but there doesn't seem to be anything connection-related on this.

Edit: Fixed tags.

Edit 2015-09-12: Now running 1.1.9.28 and it seems I can't stream anything using the browser! Also, that IP address no longer seems to work. YouTube EDIT 29.10.2016: Running 2.0.4 now, with updated browser and stuff, the situation is still works, so I think it may be only MP3 streaming issue... Could anyone confirm that? Disregard that, reboot helped.the same. I have been using Nettiradio for a long time, works like a charm! Doesn't really fix the problem, though.