diff options
-rw-r--r-- | docs/FILES | 1 | ||||
-rw-r--r-- | docs/KNOWN_ISSUES | 22 |
2 files changed, 23 insertions, 0 deletions
diff --git a/docs/FILES b/docs/FILES index 21f2faf0a8..6eab98d824 100644 --- a/docs/FILES +++ b/docs/FILES | |||
@@ -13,3 +13,4 @@ NODO | |||
13 | README | 13 | README |
14 | TECH | 14 | TECH |
15 | UISIMULATOR | 15 | UISIMULATOR |
16 | KNOWN_ISSUES | ||
diff --git a/docs/KNOWN_ISSUES b/docs/KNOWN_ISSUES new file mode 100644 index 0000000000..db36ae5835 --- /dev/null +++ b/docs/KNOWN_ISSUES | |||
@@ -0,0 +1,22 @@ | |||
1 | This is a list of known "issues" in the current Rockbox. | ||
2 | |||
3 | These are flaws/bugs we know of that are not likely to be fixed within a | ||
4 | reasonable time so we list them here and close the bug tracker entries for | ||
5 | them. | ||
6 | |||
7 | FS#894 - When the complete playlist fits in the mpeg buffer, and the playlist | ||
8 | is played multiple times, the tracks are reloaded from disk multiple times | ||
9 | instead of loaded only once. | ||
10 | |||
11 | FS#2147 - It's a bug in the MAS. It starts bitshifting data on occasion. High | ||
12 | load on the MAS makes this behaviour more likely (high recording level, high | ||
13 | quality setting, high sample rate). It's impossible to avoid, but there are | ||
14 | plans to implement a recording 'framewalker' that checks recorded data and | ||
15 | restarts recording when the MAS starts delivering bitshifted data. | ||
16 | |||
17 | FS#4937 - A constant rhythmic ticking noise occurs in the right | ||
18 | channel. Believed to be related to our slow I2C implementation, and occurs | ||
19 | when the battery status and/or realtime clock are updated (the battery is | ||
20 | read at up-to 2.5hz and the clock at up-to 1hz). Nothing is going to change | ||
21 | with it until someone spends a lot of time analyzing the portalplayer's I2C | ||
22 | control registers, or finds a datasheet for the damned thing. | ||