Support and General Use > Hardware
[Clip+, Clip Zip, ClipV2, FuzeV2] Improve battery life, part 2
Mihail Zenkov:
--- Quote from: asymsucon on January 02, 2017, 10:53:07 AM ---Still, it seems that the best way to measure this consumption would be on a used opened unit with a PSU instead of 3.7V li-ion battery.
This battery benchmark will produce different results based on 'wear level' of each user's battery and is thus a poor indicator of how much energy was saved compared to dev build.
--- End quote ---
I do that for myself tests and measuring current. But we have short spike of big power consumption when read from flash or sd so I cant measure it right.
--- Quote from: asymsucon on January 02, 2017, 10:53:07 AM ---From your 30-hour figure, that'd be around 38mW during playback (3.7V@290mAh). That's insanely low!
--- End quote ---
I have ~9.5 mA consumption on mp3 playing and in future we can get even less power consumption.
--- Quote from: asymsucon on January 02, 2017, 10:53:07 AM ---Just for comparison, Fiio X5II consumes about 25 times more, Fiio X7 over 40 times more! :)
--- End quote ---
:) But it have external DAC and AMP so it should consume more. Probably it also can be optimized.
For example - original sansa firmware have poorly optimized flac decoder and consume ~40 mA. At same conditions my latest build consume ~8 mA.
--- Quote from: asymsucon on January 02, 2017, 10:53:07 AM ---I'm curious. How much more approximately? Having an undistorted 1V RMS into 600Ohm load would be worth sacrificing a bit of battery runtime, but depends on how much.
--- End quote ---
I will try measure it later. In any case - better have high volume with higher power consumption than unusable high volume with clipping and lower consumption.
Mihail Zenkov:
--- Quote from: asymsucon on January 03, 2017, 12:31:21 AM ---The battery lasted 9 hours and 14 minutes. Not an improvement from regular version.
During the test the UI was somewhat unresponsive.
--- End quote ---
If you have some big lag in UI - you have problems with reading/writing on sd card or internal flash: driver try reread again and again and drain battery too fast. So don't have sense do battery bench if you have this problem.
Probably I found solution to prevent instability - I update links in first my post.
At first better try test and do battery bench without sd card at all (eject it).
johnb:
BTW, when I copied the build over to the Fuze, properly ejected in Win10 and the unplugged I got (with the first build and the latest) a white screen with
data abort
and I have do a longpress Power ...
instead of being asked if I want to reload firmware.
johnb:
Now using the -2 version on clip+ var1:
* no issues with internal memory
* drop out on +3 -> +4dB remains
* still the same navigation issues with my Samsung EVO 64GB -> empty dirs
* different Samsung 64GB:
Startup and scanning disk takes long. I can play songs from SD. Resume playback after boot (on a flac file) -> starts to play, pauses, plays, pauses ...
The buffer runs empty (checked in debug). When skipping to the next song, this does no longer happen. Seeking in the song it happens again after playing has resumed.
johnb:
On buffering from internal vs. external flash, I picked an extreme test case, i.e. a hires file from http://www.2l.no/hires/index.html :
http://www.lindberg.no/hires/test/2L-125_stereo-88k-24b_04.flac
File size : 26 MB (27 275 400 bytes)
Bitrate : 2177 kbps
It plays without stuttering from internal memory, but not from any of my Samsung SDs nor the 128GB Sandisk.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version