I was also very disappointed this week. I use the audio and FM transmitter regularly in the car. I finally got around to try and use mappero. Boy is that app CPU hungry. The whole device kept on freezing and unfreezing and the audio wouldn't stop stuttering.
Ended up having to powerbutton+end current task.
Actually it is possible to do GPS navigation, music, and browsing the web at the same time with no stuttering audio. Though opening the camera usually causes the problem.
So, you're actively doing GPS, while browsing the internet, AND taking pictures, and are surprised that it's laggy and stuttering? Most laptops (or desktop PCs) would have problems doing all that at once! That's expecting an awful lot out of a pocket-sized device, no?
If you're just playing audio, it does well. If you want to browse the web, while GPS navigating, and listening to MP3s, and taking a picture, then go get a... wait.. nothing else can do all that at once either. Go buy a GPS, a digital camera and a cheep mp3 player, then use the N900 to browse. It'll all be much happier that way.
Well OK, that IS a lot to ask, but still I think OS should not get to state where it is unresponsive to any user input for several minutes. Once I waited over 20 minutes to get control back to my device, but nothing worked and battery had to be taken out to make N900 reboot. Other times I just waited few minutes because I was sure it will never recover as in this first time.
The common thing in these lock ups were Mappero. It maybe is just too resource hungry program for N900, but it is the same time necessary because Nokia Maps is so bad in offline use.
With N95 I used to be able to use Nokia Maps with navigation, web browser and camera all at the same time without needing to reboot. And I thought Symbian should be worse than Linux in multitasking.
OS should not get unresponsive due to some userspace application; Mappero in this case.
Ok, Mappero should be fixed also so it wouldn't take OS down.
Mappero is rather aggressive with downloading maps. I guess the only solution to avoid non-response is to be more aggressive about asking to close apps. That or if you really want it, find a way to implement Android task killing.
It's an awesome phone dushkin.
Seriously I have never seen the hardware so exposed to the OS previously.
Just wish the baseband code were open source. Rapuyama... nice name :P
This one is talked about as fixed in PR1.1 in the comments with reports of it actually working, are non-whitelisted processes still stopped while doing other things?
