[Clip+, Clip Zip, ClipV2, FuzeV2] Improve battery life, part 2

[Mihail Zenkov]

The bootloader patch should be applied according to this guide? https://www.rockbox.org/wiki/WorkingWithPatches#Applying_A_Patch

Yes, but better wait until someone provide tested binary build.

sometimes loading a song can take several seconds.

My patch have delay (1 ms) before start each read. So if we read many small blocks we can have longer loading. I see this delay when have track with album art. I'll fix it later - when all other will be fixed - as it help a lot in debug.

As for performance, v12 takes at least 15 seconds to load Opus files of any bitrate.

Try this: http://download.rockbox.org/test_files/opus_192k.opus

[johnb]

V12, Fuze var0: has been running now for 6h @99 without any re-init, etc.
With 98 they still happened.

[Mihail Zenkov]

With 98 they still happened.

Is internal flash work after reinit (you can play next file)?

[johnb]

I am checking now again with 98, but after 4hs stats are still at 0,0,0,0 ...

[Mihail Zenkov]

johnb
Can you set 95-90 and check is it freeze on reinit or not? Also what you have on others players after reinit on internal flash? Is it freeze or not?

[asymsucon]

Try this: http://download.rockbox.org/test_files/opus_192k.opus

No change.
I take those 15 seconds back, I tested it on the faulty one. On all other ones, it's 3 seconds.

I did finish testing on all 5 Clip+ var. 1. 88-89 should be best compromise with extra room for error.

[Mihail Zenkov]

No change.
I take those 15 seconds back, I tested it on the faulty one. On all other ones, it's 3 seconds.

Without reinit in debug menu?

[asymsucon]

Exactly, no reinits (0,0,0,0).
Shutdown also takes a while longer.

[Mihail Zenkov]

asymsucon
It looks like opus codec specific problem: it read by small chunks or/and read big part of file before start. In any case it will be fixed later.

[asymsucon]

Tried Opus with different lengths (up to 60 mins) with no change in load time. (pending further confirmation on all units)
Perhaps they'll fix the FFT length requirements in libopus 1.2.x which would help its optimization.

[johnb]

johnb
Can you set 95-90 and check is it freeze on reinit or not? Also what you have on others players after reinit on internal flash? Is it freeze or not?

I had the fuze var0 running now @92 for 2h: 2,9,0,0 but still responsive, can use the file browser and launch other songs.


On my clip+ on reinits it was mostly stuck or incrementing the counters or it even crashed with dc_write_callback etc.

[Mihail Zenkov]

I had the fuze var0 running now @92 for 2h: 2,9,0,0 but still responsive, can use the file browser and launch other songs.

What about fuze var1?

On my clip+ on reinits it was mostly stuck or incrementing the counters or it even crashed with dc_write_callback etc.

You mean clip+ v1? On clip+ v0 it just crash/panic at low voltage?

[johnb]

Mihail, I am afraid I did not note that down properly and need to re-run ...

[johnb]

Fuze var1: crashed in less than 30min with "data abort" @81, prefetch data abort to be precise.

clip+ var0: I ran without any re-inits for more than 5hs at even 74, flickering got even worse. It got stuck when I navigated through the shortcuts, still playing the song. I could stop the song, but stayed in shortcuts and then idle powered off.

[asymsucon]

For internal flash 86-88 on CVDD2 seems to be the most stable overall. Unfortunately all my units are only var. 1.
Except for the Clip+ with faulty internal flash, all other 5 run very well on 88.
If we could move on to the SD card testing, I'm getting 2 extra 64GB microSD cards, Transcend and Samsung.
I'd imagine no issues on v12 for those, but this 128G Sandisk is still giving me tons of reinits and causes Clip+ to be very slow (even browsing through dir structure).
Loading and seeking through Opus takes anywhere from 3 to 15 seconds.
DOOM takes forever to load (after 10 mins I performed reset) 
IT/XM modules vary between 1-3 minutes.

After 3 hours of continuous playing I was at 0,0,134,0

But despite this slowdown, I'm fairly certain we're close to 30 hrs target runtime. After those 3 hrs, the battery percentage dropped just by 8%.