Support and General Use > Hardware

RB 3.8 Sansa clip+ doesn't terminate generating database

(1/5) > >>

lwizard:
I have a Sansa clip+ with a 32GB uSD.
All was right with 3.7 version, also database worked very well.

Now I have updated to 3.8.
When I click on database it ask me to initialize.
I find about 6000 items then it stuck there.
After a lot of minutes it power off.
When I turn on again the database is still to be initialized.
I have tried keeping it alive by pressing buttons, but database doesn't terminate to compile.

Once I have also played music while compiling but RB hanged and I had to force power off.

Any idea?
Anyway.. great great job! I am a very fan of RB! Sadly I haven't time to code but I support RB with donation!

saratoga:
Under the debug menu there is an option to enable database logging.  This will generate a list of all the files parsed when you build the database.  Could you enable that, find the file it crashes on decoding, and upload it here?

lwizard:
I'll do as soon as possible!
Post Merge: March 01, 2011, 11:57:13 AMIt does stop at a certain file in the internal memory, but if I delete it, it stops at another file and so on.
Analyzing the internal memory in windows, it was corrupted.
So I reformatted the Sansa from the original firmware.
I reinstalled rockbox 3.8 with no mp3 on the internal memory.
I insrted the 32GB uSD card and initialized the database: all went right!
So I had few al lot of mp3 on internal memory, updated database: allright.
I added some mp3 again in internal memory: again database hang on refreshing or reinitializing and the internal memory is corrupted in windows.

I always do safe removal.

I think something corrupt internal memory.. maybe the new version of rock box?
II'll try for the last time, than turn back to 3.7.1 that was stable.


NEW:turned back to 3.7.1, the problem disappear.
It seems a 3.8 new bug!

lebellium:
I confirm this issue with Rockbox 3.8 on my 8GB Clip+

vroetman:
I also had problems with 3.8. It would hang on database generation. Furthermore, something got corrupted and I could not even access the filesystem with USB using the OF. The Sansa OF also took an unusually long time to boot. Other than those three problems, things seemed to work fine (with no database). I finally had to reformat from the OF (and will revert to 3.7.1).

Navigation

[0] Message Index

[#] Next page