The D3 bug/quirks listing

[Setsunakute]

I know there is only a few D3 running around there at this time.
But this thread is for anyone who is experiencing crashes or software bugs.
Please give feedback if you ran into the same issues, or think it is device- or user-related.


My list:

-Multiple reboots during media scanning : The player hangs itself during ~30 seconds, then reboots. The file shown by the notification list is not always the same. (I am suspecting inconsistencies in some files, have to sort them out, but they are not causing problems on other DAPs. Maybe it is the file system, but I always disconnect it properly. The worst case would be a faulty NAND). I have to put a .nomedia file in my microSD to prevent media scanning from it, because it always crashes otherwise.
-While operating, it turns back into lock screen : this one is pretty annoying, and it happens sometimes.
-Clock resets after running out of battery : Date is reset to November 23, 2010 when charging the battery back.

(to be completed...)

Firmware version is 1.25

[CrowdAds]

[Setsunakute]

Another one:
-If the playlist db is too large (maybe with several caracters encoding in tags), the music app crashes : Tested with 5000+ files in internal + micro SD memory.
There is 2000 files in 32G microSD and 3000 files in main.
If the main memory or the µSD is scanned alone (by using a .nomedia file to prevent scanning in one of the two storage devices), the Music app can be opened
If the µSD+internal is scanned, the Music app won't open, with those messages in logcat

E/DatabaseUtils( 1089): Writing exception to parcel
E/DatabaseUtils( 1089): android.database.sqlite.SQLiteDiskIOException: disk I/O
error
E/DatabaseUtils( 1089):         at android.database.sqlite.SQLiteQuery.native_fi
ll_window(Native Method)
E/DatabaseUtils( 1089):         at android.database.sqlite.SQLiteQuery.fillWindo
w(SQLiteQuery.java:75)
E/DatabaseUtils( 1089):         at android.database.sqlite.SQLiteCursor.fillWind
ow(SQLiteCursor.java:288)
E/DatabaseUtils( 1089):         at android.database.sqlite.SQLiteCursor.getCount
(SQLiteCursor.java:269)
E/DatabaseUtils( 1089):         at android.database.CursorToBulkCursorAdaptor.co
unt(CursorToBulkCursorAdaptor.java:132)
E/DatabaseUtils( 1089):         at android.database.BulkCursorNative.onTransact(
BulkCursorNative.java:79)
E/DatabaseUtils( 1089):         at android.os.Binder.execTransact(Binder.java:28
7)
E/DatabaseUtils( 1089):         at dalvik.system.NativeStart.run(Native Method)
D/AndroidRuntime( 2851): Shutting down VM
W/dalvikvm( 2851): threadid=3: thread exiting with uncaught exception (group=0x4
001b178)
E/AndroidRuntime( 2851): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime( 2851): java.lang.RuntimeException: Unable to create service co
m.cowon.musicplayer.CWMusicPlayerPlaybackService: java.lang.NullPointerException

E/AndroidRuntime( 2851):        at android.app.ActivityThread.handleCreateServic
e(ActivityThread.java:2790)
E/AndroidRuntime( 2851):        at android.app.ActivityThread.access$3200(Activi
tyThread.java:119)
E/AndroidRuntime( 2851):        at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1917)
E/AndroidRuntime( 2851):        at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 2851):        at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 2851):        at android.app.ActivityThread.main(ActivityThrea
d.java:4363)
E/AndroidRuntime( 2851):        at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 2851):        at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 2851):        at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 2851):        at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:618)
E/AndroidRuntime( 2851):        at dalvik.system.NativeStart.main(Native Method)

E/AndroidRuntime( 2851): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 2851):        at com.cowon.musicplayer.FolderCursor.sort(Folde
rCursor.java:125)
E/AndroidRuntime( 2851):        at com.cowon.musicplayer.FolderCursor.refresh(Fo
lderCursor.java:58)
E/AndroidRuntime( 2851):        at com.cowon.musicplayer.FolderCursor.<init>(Fol
derCursor.java:49)
E/AndroidRuntime( 2851):        at com.cowon.musicplayer.PlayingListManager.setC
ategoryInternal(PlayingListManager.java:244)
E/AndroidRuntime( 2851):        at com.cowon.musicplayer.PlayingListManager.setC
ategory(PlayingListManager.java:167)
E/AndroidRuntime( 2851):        at com.cowon.musicplayer.CWMusicPlayerPlaybackSe
rvice.setCategory(CWMusicPlayerPlaybackService.java:919)
E/AndroidRuntime( 2851):        at com.cowon.musicplayer.CWMusicPlayerPlaybackSe
rvice.setCategoryForLastPlayingFile(CWMusicPlayerPlaybackService.java:454)
E/AndroidRuntime( 2851):        at com.cowon.musicplayer.CWMusicPlayerPlaybackSe
rvice.loadPref(CWMusicPlayerPlaybackService.java:445)
E/AndroidRuntime( 2851):        at com.cowon.musicplayer.CWMusicPlayerPlaybackSe
rvice.onCreate(CWMusicPlayerPlaybackService.java:250)
E/AndroidRuntime( 2851):        at android.app.ActivityThread.handleCreateServic
e(ActivityThread.java:2780)
E/AndroidRuntime( 2851):        ... 10 more

I believe this issue looks like this : http://www.mail-archive.com/android-.../msg79398.html

[Olley]

The music database will grow with every song added. One thing to watch for is that there is some free space left on the device after adding content and apps. I also expect the dat file can't exceed 2gb as the files system doesn't support files over 2gb either.

[Setsunakute]

The available space is not an issue there; there is 614MB remaining on the Android partition, and over 6GB in both main and micro SD's. It is probably due to a size limit of the database that can not be handled by the less-than optimized Music App, and/or a problem with the sqlite journal.

[Olley]

Just curious, Setsunakue. Where do you you live (country-wise)? I've been told the D3 doesn't charge from the USB cable. Is that true? Meaning it'll need a dedicated AC adapter, and I'm not sure it comes with a universal one that would work in the U.S..