Notices

Originally Posted by Nozu

I've been using 300secs buffer size as I recall you mentioned using and I've almost always used 3g. I do use the power kernel and swappolube and they may cause the problem. I decided to remove the swappolube config file and so resetting the swaps to device default and setting the buffer to default 30secs and gave Qspot a try. This time I didn't notice any device slowdown that would bother, I still received a memory error but it was after I had played over 3 standard albums of music. Here's a screenshot of top taken right after the memory error. Have to test more when I have time.

Originally Posted by aenbacka

Thanks a lot for the feedback, and top output. So it seems that swappolube (possible in combination with power-kernel) could cause some problems (myself I am using swappolube with suggested settings on stock PR1.3 without any problems, also using 300secs buffersize). Total memory left is quite low according to the top output, and this is probably the reason for the out of memory message. Could you resume playback after the memory error message?

Originally Posted by Nozu

I can resume playback after the memory error message, but my N900 still gives me the same error if I or the device tries to do anything else. I can't open any new apps no matter how small or simple they would be. Quitting Qspot resolves this problem.

Originally Posted by aenbacka

Ok, did you also use the high bitrate 320k option?

Originally Posted by Nozu

So I'd recall.

I found some thread where people are having the same memory error message. Some using MicroB, some using Modest and no-one seems to have a clue what is causing this. I've now noticed that the top may show low memory even if I'm not running any programs at all. I think Qspot isn't responsible for this behaviour it just happens to "cross the line" for the error message in my case. If only I could know what is causing this...