![]() |
2009-10-29
, 20:25
|
|
Posts: 2,669 |
Thanked: 2,555 times |
Joined on Apr 2007
|
#2
|
I've been using the N900 that I received in the summit for a few weeks now as my primary and only phone (so let's not forget that I am talking about a preproduction device here). Everything mostly works well, but sometimes the thing just gets really really slow while using certain apps like E-mail or Maps, or updating the software catalog. Browsing the web may do this, perhaps when opening a complicated page or a page with a lot of flash. In this situation the music player starts making short frequent pauses and the user interface gets slow. I also get unrecognized taps or one tap recognized multiple times (or perhaps there are problems playing the tap sound effect - that's how I recognize it).
Does anybody else experience this or do I have something wrong with this particular device?
This is just a hunch/guess but perhaps there is something wrong with the flash memory (or memory handing)? The device acts really slow whenever there's more than a little I/O going on. An extreme example was when trying to copy a gigabyte of music from the microSD card (using cp in shell) to the internal memory and simply jammed the whole thing. It never finished and I had to reboot. It just totally stopped after a few hundred megabytes.
To see what I mean, run:
dd if=/dev/zero of=/home/user/MyDocs/foo bs=1M
and wait for a while. Try opening other apps or generally doing anything while dd is running. My device is nearly unusable. This is of course a really extreme example, but in my opinion high I/O load should not halt the device to such a crawl. And no UI slowness at all when there is less than full use of I/O.
Is there a setting somewhere to tweak I/O behaviour for testing purposes? Could it be helped by altering some process priorities?
![]() |
2009-10-29
, 20:30
|
Posts: 21 |
Thanked: 26 times |
Joined on Sep 2009
@ Madrid, Spain
|
#3
|
![]() |
2009-10-29
, 20:35
|
Posts: 1,038 |
Thanked: 737 times |
Joined on Nov 2005
@ Helsinki
|
#4
|
![]() |
2009-10-29
, 20:41
|
Posts: 31 |
Thanked: 32 times |
Joined on Jan 2008
@ Helsinki
|
#5
|
![]() |
2009-10-29
, 21:15
|
|
Posts: 70 |
Thanked: 11 times |
Joined on Oct 2009
|
#6
|
![]() |
2009-10-29
, 21:59
|
Posts: 46 |
Thanked: 8 times |
Joined on Aug 2009
|
#7
|
![]() |
2009-10-30
, 00:16
|
|
Posts: 569 |
Thanked: 159 times |
Joined on Sep 2009
@ District of Columbia
|
#8
|
dude why would it get slower? lol!
If you have too many apps, or downloaded too much crap on it, ofc, it might get slower, but not if you treat it nicely.
![]() |
2009-10-30
, 00:17
|
|
Posts: 569 |
Thanked: 159 times |
Joined on Sep 2009
@ District of Columbia
|
#9
|
This is my greatest concern - I am almost sure this device will get very slow after a month of using it...hope not.
Does anybody else experience this or do I have something wrong with this particular device?
This is just a hunch/guess but perhaps there is something wrong with the flash memory (or memory handing)? The device acts really slow whenever there's more than a little I/O going on. An extreme example was when trying to copy a gigabyte of music from the microSD card (using cp in shell) to the internal memory and simply jammed the whole thing. It never finished and I had to reboot. It just totally stopped after a few hundred megabytes.
To see what I mean, run:
dd if=/dev/zero of=/home/user/MyDocs/foo bs=1M
and wait for a while. Try opening other apps or generally doing anything while dd is running. My device is nearly unusable. This is of course a really extreme example, but in my opinion high I/O load should not halt the device to such a crawl. And no UI slowness at all when there is less than full use of I/O.
Is there a setting somewhere to tweak I/O behaviour for testing purposes? Could it be helped by altering some process priorities?