When starting Rockbox Utility select the same build type that was used
during the previous run. This broke during refactoring, fix it.
Change-Id: Ibbca3431cbfe65daedd3e5783e0940d83d1594a6
The manual tab didn't show the manual, so it's clearer to have that as
part of the main tab.
Also fixes the wrong manual getting downloaded for releases.
Change-Id: I5d4a287102af037f94f0de8464e025d9ff5f76ed
Avoid having to repeat the same strings for lookup again and again and
use an enum instead, which is also less error prone.
Change-Id: I6ee8393948dbce97cb53850a6d8bdc4de12b4167
Add checkbox for installing the prerendered voice file to the main
install widget. Current limitations:
- only english for now. The available languages are available from the
build server but are not yet taken into account.
- only for releases. This is the same limitations we had before. We do
have voices for daily builds, but that requires adding daily builds
again (those have been removed some time back.)
- Old voice installation dialog still present.
Change-Id: Ia6443b0f15365196df86cc1b64d5e043dff70c4c
Use pattern replacement for lookup instead of expanded values. Will
allow simplifying things later for better handling of different build
types.
Change-Id: Iaad67a6c8654d27c3206cf95a379acab169565bc
Before this was just implemented inline wherever it was needed. Now
it is provided as 2 inline functions in a header called checksum.h.
There should be no differences in actual behavior.
Change-Id: I5d756cc01dc6225f5cc8b6af90911a3fc7b57cd5
* Bump internal mix buffer size by 4x, to 1K frames (matching ALSA period)
* Handle an underrun that occurs when filling the audio buffer
* Log underruns and make them available in the debug info
Change-Id: I28d56dd35d88851fa167ad92368a5882937a758f
It's not large enough on some targets.
(this will be revisited when the USB insertion prompt stuff is moved
out of the USB helper and over to the main thread)
Change-Id: Iefed2cdf2fbb4ce92569fc5cacbdb479b7d24e61
It turns out the code for the firmware size validation was incorrectly
using the total length of the firmware file to check if it was too big
for the flash rom which caused it to incorrectly flag larger bootloaders
as too big even though they would still fit.
As it happens this situation can only really arise after mkboot has been
run on the decoded firmware image. Because mkboot writes the actual binary
size to the ESTFBINR header we will be using that to check if the firmware
image is too large for the flash rom.
Now because this information is embedded in the decrypted / encrypted
region we have to collect it as the region is processed so the validation
is also moved to after the data processing loop.
Change-Id: I8bfead73812fe4e59f08fbbe8956790604dcb4e2
It was short by a fair number of bytes which could be reached when
attempting to insert bootloaders near the maximum size of 64k. This
ensures even the largest acceptable bootloader will not overflow the
buffer.
Change-Id: I8fbc92d4e3452192bf47104d7a32b49248eefc0e
First, the way it was invoking mkboot was no longer correct so it
was not producing files used in the later commands.
Second, support for the H300 1.31k firmware was added sometime ago
but not to this script.
Change-Id: I0e9c74a3b9f83ade8d01df0bebfe06f4d3b92ce4
