Anyway, I’ve never connected the player to PC in RB mode cause I did it once and the device driver installation or something failed and I never tried it again.
However, yesterday, I accidentally connected my player to PC forgetting it is on RB mode, this time the driver installed successfully, and 2 additional folders appeared in the player’s root folder. “##MUSIC#” and “##PORT#”.
Been working flawlessly ever since, been turning the player off and on about 10 times now, both to test and to listen to music, working perfectly.
Funny that I’ve been looking for help all over the place and it gets fixed by a fluke… Thanks for all the help, fingers crossed that it keeps working
Okay, after a couple of days of working flawlessly, giving me the exact same **bleep** again.
Never touch any settings or files, never mess with anything at all.
Getting real frustrated >.>
Your issues are an absolute mystery to me. The RB devs are somewhat conservative in their classification of builds as “stable” or unstable, and the Clip+ port certainly lives up to “stable”…once it hit official stable status, I ran it on two of them for many months without a single issue, only selling them when I got the newer model, the Clip Zip.
There has to be more to the story here. Emospence has had more trouble in a short time on a player with a stable port (the Clip+), than I have had in seven months on my Clip Zip with its still “unstable” port. Whether it is something with their filesystem, or their computer, or their actions, I don’t know.
I still would be willing to bet that the majority of those who have used Rockbox have had good results with it. I even have it on my Samsung Android device, and out of the several music apps I have on there, I use Rockbox about 70% of the time…and that app is probably farther away from “stable” status than the Zip is.