Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 1 hr ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 21 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 6 hrs ago - more...
punto |
2010-12-14
, 20:18
|
|
Posts: 182 |
Thanked: 40 times |
Joined on Apr 2010
|
#371
|
Originally Posted by aenbacka
Yes - that's what it seems to be.
| The Following User Says Thank You to punto For This Useful Post: | ||
|
|
2010-12-15
, 08:23
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#372
|
Originally Posted by punto
This will need to be investigated further; I tried some scenarios myself yesterday but was not able to get the device into such a state that it would take as long as you described to open the screen lock. However it seems that the wakeup from sleep state requires a lot of power from the cpu, which could cause QSpot to become unresponsive (I have noticed that it could take some time for QSpot to "recover" from sleep state, but once wake up has completed it works just fine). I almost daily listen to QSpot while sitting in the bus for close to an hour (over 3g, low / normal bitrate; with a buffer length of 300secs), and I have not noticed that the device has been unresponsive once I try to open the screen lock.
Yes - that's what it seems to be.
Have you used some custom buffer length (other than the default value of 30secs)?
|
|
2010-12-15
, 09:31
|
|
Posts: 75 |
Thanked: 27 times |
Joined on Dec 2009
|
#373
|
Punto seems to have the same problem as I do. I mentioned this problem earlier. After I get my phone out of the sleep mode (if I get it out), my N900 might have an system error message on the screen: "Action temporarily prevented. Not enough memory." (My translation from Finnish.)
It still keeps playing music though. But the device getting so quickly sluggish makes the Qspot nearly unusable for me.
It still keeps playing music though. But the device getting so quickly sluggish makes the Qspot nearly unusable for me.
|
|
2010-12-15
, 09:52
|
|
Posts: 182 |
Thanked: 40 times |
Joined on Apr 2010
|
#374
|
I don't get any messages FYI.
And I use the default buffer length.
This morning it woke up fine. However, I manually paused playback yesterday night after only a few minutes of comedy show listening (Dane Cook really does come across as a ****).
Last edited by punto; 2010-12-15 at 09:56.
And I use the default buffer length.
This morning it woke up fine. However, I manually paused playback yesterday night after only a few minutes of comedy show listening (Dane Cook really does come across as a ****).
Last edited by punto; 2010-12-15 at 09:56.
|
|
2010-12-15
, 10:29
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#375
|
I am not sure that Punto's problem is exactly the same, but they could be related. In case memory would be full, QSpot would probably stop playback completely. It seems that something happens when the device is in sleep state, and QSpot is running (or when the device is trying to get out of sleep state and resume normal operation). Have you by the way used swapolube to optimize kernels parameters such as swappiness?
Originally Posted by Nozu
Punto seems to have the same problem as I do. I mentioned this problem earlier. After I get my phone out of the sleep mode (if I get it out), my N900 might have an system error message on the screen: "Action temporarily prevented. Not enough memory." (My translation from Finnish.)
It still keeps playing music though. But the device getting so quickly sluggish makes the Qspot nearly unusable for me.
|
|
2010-12-15
, 18:41
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#377
|
Originally Posted by punto
I have tried to investigate this issue further, but not being able to reproduce it. QSpot does not consume any extra cpu while in idle state (i.e, playback paused / stopped). Pulseaudio do seem to consume slight cpu also in idle state (~4% max); this could of course slowly cause battery drain under a longer period. Anyway, more investigation is still needed.
I don't get any messages FYI.
And I use the default buffer length.
This morning it woke up fine. However, I manually paused playback yesterday night after only a few minutes of comedy show listening (Dane Cook really does come across as a ****).
|
|
2010-12-15
, 20:50
|
|
Posts: 182 |
Thanked: 40 times |
Joined on Apr 2010
|
#378
|
so same today as well - once again I manually stopped playback and left it, no problems. whatever issues are there it appears to be a byproduct of the times that I leave it playing and it either stops playback randomly as remarked before, or perhaps when the playlist ends...?
|
|
2010-12-19
, 14:34
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#379
|
Related to the problem that has been reported abot N900 becoming sluggish when QSpot has been running for a longer time with the display off, I have been planning to introduce a new sleep timer function in the next version. Using the sleep timer, it possibe to enable automatic stop of playback (as well as automatic close of the QSpot app) after a specified time..
|
|
2010-12-20
, 00:23
|
|
Posts: 48 |
Thanked: 21 times |
Joined on May 2010
|
#380
|
Originally Posted by aenbacka
Well, that doesn't really seem to be a solution but more like a hack.
Related to the problem that has been reported abot N900 becoming sluggish when QSpot has been running for a longer time with the display off, I have been planning to introduce a new sleep timer function in the next version. Using the sleep timer, it possibe to enable automatic stop of playback (as well as automatic close of the QSpot app) after a specified time..
I've got the same problem (clean PR1.3-205).
When the screen is locked (off) and QSpot is playing music, after a while (10-20mins), and I try to unlock it, the device is very unresponsive.
| The Following User Says Thank You to florian For This Useful Post: | ||
 |
| Tags |
| premium account, spotify |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 02:36.