Support and General Use > Hardware
[Clip+, Clip Zip, ClipV2, FuzeV2] Improve battery life, part 2
johnb:
clip+ var1 with -4:
seems to work fine with regular files on both Samsung cards. I had one shrieking glitch (no stuttering) with one of the hires files.
FuzeV2 var0 with -2:
Similar to what I reported for the respective clip version: long startup, huge delay in starting songs on one of the 64G Samsungs, for the 64 EVO I cannot even browse the SD.
Mihail Zenkov:
--- Quote from: asymsucon on January 03, 2017, 02:45:32 PM ---Variant4
No apparent problems on Samsung 128GB filled to 98%.
--- End quote ---
Good.
--- Quote from: asymsucon on January 03, 2017, 02:45:32 PM ---100ms square wave distortion when going downwards from +6dB to 0dB that happens on +3dB and 0dB step - Non-issue.
Audible pops when approaching +6dB from 0dB on sensitive earbuds with no music playing.
--- End quote ---
I will try eliminate it later.
Mihail Zenkov:
--- Quote from: johnb on January 03, 2017, 03:28:43 PM ---clip+ var1 with -4:
seems to work fine with regular files on both Samsung cards. I had one shrieking glitch (no stuttering) with one of the hires files.
--- End quote ---
Good.
--- Quote from: johnb on January 03, 2017, 03:28:43 PM ---FuzeV2 var0 with -2:
Similar to what I reported for the respective clip version: long startup, huge delay in starting songs on one of the 64G Samsungs, for the 64 EVO I cannot even browse the SD.
--- End quote ---
I update links in my first post - so you can try new build for FuzeV2.
asymsucon:
59% battery left after 10 hours!
I'll update this post once it reaches 0%.
BTW, I do have this little issue with charging. For me, charging stops at 80%, once I reboot it starts back again and then concludes at 100%.
Final update: OK, I got a little carried away, it wasn't 20 hours, but really close. 19 hours, 21 minutes.
55mW average consumption, 64Ohm headphones, level set to -25dB, playback through folders, Opus - 140kbit at 48kHz
Very impressive! I think M3 just got pwned. ;D
Further savings could be delivered from dimming the OLED a bit more - I have it on 0 and it's still unnecessarily bright. Though the PWM dimmer could have been a bit faster, say 500Hz instead of sub-200Hz.
johnb:
FuzeV2 var0 with -4:
tested with various cards, looks good. Responsive UI, startup sometimes delayed depending on card. In one session with the 64GB EVO card I had the effect, that mpc, flac, mp3 files started immediately, but songs from an album with opus 140kbit files had a 5s delay in starting.
Swapping different cards in and out I cannot reproduce it anymore.
What are further things we should look out for, like stressing the device?: High file I/O and or CPU load?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version