Do you mean by installing another launcher and resetting the cache from the app info screen? If that's the case, yes, I tried that. I even tried the hard reset way (or "double wipe", as Cayin and Andy call it).
Do you mean by installing another launcher and resetting the cache from the app info screen? If that's the case, yes, I tried that. I even tried the hard reset way (or "double wipe", as Cayin and Andy call it).
There's no difference. The reset inside settings is just a graphical wrapper that issues a command to the recovery firmware, which then proceeds to reset the device. They do the same thing.
There's no difference. The reset inside settings is just a graphical wrapper that issues a command to the recovery firmware, which then proceeds to reset the device. They do the same thing.
In order to catch this nasty bug, we have developed a special beta firmware to keep track of the machine status, the player will operate in developer mode with this beta firmware and generate a log entry whenever the DAP is freezed during playback. We are in the process to recruit beta testers who has experienced frequent freeze or pause during their daily use, we hope the beta firmware will record detail of machine operation status and review the root cause of the bug.
Right now the Beta firmware is only available in Domestic (no Google Play) version. Once we field tested the beta firmware, we'll extend the bug status collection to oversee users. I'll issue a call for beta tester notice here and in the main thread.
We have devoted a lot of resource trying to trace the issue with no luck, let's hope we can identify the root cause of this bug as soon as possible.
As discussed previously, we have developed a beta software to collect information of the player when it pause randomly. The firmware can't generate on all "pause" or freeze" pattern, so we are focused at the "pause and resume to operation automatically after a designated time" situation for the moment. We can expand to other condition if we can't catch the bug afterward.
If your N5ii have experienced the random pause/freeze frequently and is willing to help out , I'd like to invite you to join our user debug program. You'll be given a beta firmware and you need to submit the log of your player through email after you have experienced a system pause or freeze during playback. We'll provide detail instruction and firmware download link when you are selected as a beta user.
Drop me a PM with your email and a brief description to your N5ii random pause problem (frequency of pause, how long does it take to resume operation, ...). While we want to include as many beta tester as possible, but we have to set a limit on the size of beta user group in order to make this manageable, we;ll see what happen as the program kick start.
Looking forward to some good news from this beta user group soon.
1st bug since reset. I'm currently at 3.7 cycles (+- 37 hours). The device lagged for a little while then rebooted on its own. This proves that although the firmware is not flawless yet, 1 bug per 37 hours of constant playback is not too bad.
HOWEVER, no freezing during playback yet O.o, no sight of the bug.
I'll keep doing this till I complete 7 cycles.
(I'm a bit disappointed to be honest having come so far XD, I had hoped it would be flawless, got my hopes too high )
I'm afraid that is the same as doing the recovery reset twice. Two may be better than one, but I don't think this is really going to affect any bugs caused by the firmware as it seems the case here. Bugs happen, that's a truth we have to live with - I just hope Cayin (and possibly HiBy?) will find the root cause(s) soon and solve them swiftly. Once we take a few bugs out of the equation, I love this player and I look forward to using it as my daily driver, it is superb in every respect.
Today I experienced the "pause and resume" bug for the first time. I'm on my 3rd cycle. I moved to the next song and then back, and the bug disappeared. Hasn't reappeared so far.
All else works flawlessly.
Today I experienced the "pause and resume" bug for the first time. I'm on my 3rd cycle. I moved to the next song and then back, and the bug disappeared. Hasn't reappeared so far.
All else works flawlessly.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.