Rockbox open source high quality audio player as a Music Player Daemon
mpris
rockbox
mpd
libadwaita
audio
rust
zig
deno
Futher corrections
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@1841 a1c6a512-1295-4272-9138-f99709370657
+75
-73
+75
-73
www/docs/FAQ
+75
-73
www/docs/FAQ
···
12
12
-------------------------------------------------------------------
13
13
14
14
15
-
Rockbox FAQ
16
-
-----------
17
-
18
15
Q1. What is a FAQ?
19
16
A1. A rare small animal of the species 'Textius Electronicus'. It is known for
20
17
its helpful attitude and vicious misspellings.
21
18
22
-
Q2. What is Rockbox? What is it's purpose?
23
-
A2. The purpose of this project is to write an Open Source replacement
19
+
Q2. Okay, fine, what is _this_ FAQ?
20
+
A2. This FAQ is for questions (that we have answers too) that have been asked
21
+
repeatedly either in emails or on IRC.
22
+
23
+
Q3. What is Rockbox? What is it's purpose?
24
+
A3. The purpose of this project is to write an Open Source replacement
24
25
firmware for the Archos Jukebox 6000, Studio 20 and Recorder MP3 players.
25
26
26
-
Q3. I want to write code for my Archos, how do I proceed?
27
-
A3. First make sure to read the file CONTRIBUTING in the firmware directory
27
+
Q4. I want to write code for my Archos, how do I proceed?
28
+
A4. First make sure to read the file CONTRIBUTING in the firmware directory
28
29
on Sourceforge. See http://rockbox.haxx.se/firmware/CONTRIBUTING
29
30
if you do not want to have to wade through the CVS directories.
30
31
31
-
Q4: Whats CVS?
32
-
A4: Concurrent Versions System (http://www.cvshome.org). We have a small
32
+
Q5: Whats CVS?
33
+
A5: Concurrent Versions System (http://www.cvshome.org). We have a small
33
34
help page about how to use this to get, update and commit files on the web
34
35
at http://rockbox.haxx.se/cvs.html
35
36
36
-
Q5. What exactly is the CONTRIBUTING file?
37
-
A5. Just like the name implies, it lists conventions that the project follows,
37
+
Q6. What exactly is the CONTRIBUTING file?
38
+
A6. Just like the name implies, it lists conventions that the project follows,
38
39
and in turn asks you to follow, for the formating of source code in
39
40
general.
40
41
41
-
Q6. Okay, so I read CONTRIBUTING and although I don't agree with all your
42
+
Q7. Okay, so I read CONTRIBUTING and although I don't agree with all your
42
43
conventions, I am going to be sensible and follow them anyway. Now what?
43
-
A6. Start by reading up on the information about the jukeboxes on our web page.
44
+
A7. Start by reading up on the information about the jukeboxes on our web page.
44
45
Then go into CVS and look at the code we've written. Then take what you
45
46
need and start writing.
46
47
47
-
Q7. Okay, so how do I submit a patch?
48
-
A7. Run: "diff -u oldfile newfile > patchfile" against the file(s) you have
48
+
Q8. Okay, so how do I submit a patch?
49
+
A8. Run: "diff -u oldfile newfile > patchfile" against the file(s) you have
49
50
changed. Then mail the output to any member of the development team and
50
51
we will take it under consideration. (Please remember that all
51
52
submissions are not automatically accepted, this is nothing personal.)
···
53
54
Of if you would like to run the diff against the current cvs code:
54
55
cvs diff -ub [file(s)]
55
56
56
-
Q8. I want to join the development team, but don't have a SourceForge account,
57
+
Q9. I want to join the development team, but don't have a SourceForge account,
57
58
what should I do?
58
-
A8. Head on over to http://sourceforge.net/account/register.php and create an
59
+
A9. Head on over to http://sourceforge.net/account/register.php and create an
59
60
account for yourself.
60
61
61
-
Q9. Do you have a mailing list?
62
-
A9. Sure do! As a matter of fact, we have several of them for specific
62
+
Q10. Do you have a mailing list?
63
+
A10. Sure do! As a matter of fact, we have several of them for specific
63
64
things. Please check out: http://rockbox.haxx.se/mail/
64
65
65
-
Q10. Great you have a mailing list! Is there anyway for me to catch up on
66
+
Q11. Great you have a mailing list! Is there anyway for me to catch up on
66
67
past posts?
67
-
A10. Check out the archives at: http://rockbox.haxx.se/mail.cgi
68
+
A11. Check out the archives at: http://rockbox.haxx.se/mail.cgi
68
69
69
-
Q11. How can I meet the developers working on the project?
70
-
A11. One way is by visiting us on IRC. Head on over to the server
70
+
Q12. How can I meet the developers working on the project?
71
+
A12. One way is by visiting us on IRC. Head on over to the server
71
72
irc.openprojects.net, and then join "#rockbox". There is usually at
72
73
least one person there. If you don't see any activity, feel free to post
73
74
questions anyway, serveral of us log the channel and will get you answers
74
75
when we unidle.
75
76
76
-
Q12: Wow, you guys talk on IRC alot? I wish I had been around for those
77
+
Q13: Wow, you guys talk on IRC alot? I wish I had been around for those
77
78
conversations to see what happened.
78
-
A12: We are glad you mentioned that! http://rockbox.haxx.se/irc happens
79
+
A13: We are glad you mentioned that! http://rockbox.haxx.se/irc happens
79
80
to have a list of various logs we have recorded of events in the channel.
80
81
Feel free to read up, and ask questions on what you find.
81
82
82
-
Q13. What is this "SourceForge" you keep mentioning?
83
-
A13. http://www.sourceforge.net
83
+
Q14. What is this "SourceForge" you keep mentioning?
84
+
A14. http://www.sourceforge.net
84
85
85
-
Q14. Can the changes or the software that Rockbox suggests or offers
86
+
Q15. Can the changes or the software that Rockbox suggests or offers
86
87
possibly damage my Archos Player?
87
-
A14. All firmware mods that are presented are still highly experimental.
88
+
A15. All firmware mods that are presented are still highly experimental.
88
89
Try them at your own risk. We offer no guarantee that this software, or
89
90
the hardware modifications we show, will not damage your player or void
90
91
your warranty. That said, we have not been able to damage any of our
91
92
units by modifying only the firmware. You can accidentally password
92
93
protect your harddisk, but there are ways around that. (See below.)
93
94
94
-
Q15. I want to see what the inside of my player looks like, but I would really
95
+
Q16. I want to see what the inside of my player looks like, but I would really
95
96
like to avoid voiding my warranty. Is there anything you can suggest?
96
-
A15. We have a collection of photos of both the player and recorder. Look at
97
+
A16. We have a collection of photos of both the player and recorder. Look at
97
98
http://rockbox.haxx.se/internals/
98
99
99
-
Q16. What exactly are you trying to achieve with this line of development?
100
+
Q17. What exactly are you trying to achieve with this line of development?
100
101
(A.K.A. whats your purpose for being here?)
101
-
A16. Firstly, we wouldn't start something like this if we didn't simply enjoy
102
+
A17. Firstly, we wouldn't start something like this if we didn't simply enjoy
102
103
it profusely. This is great fun!
103
104
Secondly, we feel the firmware is lacking some features and contain a
104
105
number of annoying bugs that we want to fix.
···
126
127
being on the list does not mean it isn't a neat idea. Bring it to
127
128
the list.
128
129
129
-
Q17. I don't see you mentioning other file types on your list of ideas. What
130
+
Q18. I don't see you mentioning other file types on your list of ideas. What
130
131
about supporting those?
131
-
A17. Pessimist's Answer: At the current time we belive this is not very likely
132
+
A18. Pessimist's Answer: At the current time we belive this is not very likely
132
133
The Micronas chip (MAS3507) decoder in the archos does not natively
133
134
support decoding and there is very little program space in the player to
134
135
implement it ourselves. The alternative would be to write a software
···
145
146
help, please get in touch!
146
147
147
148
148
-
Q18. What about supporting playing of WMA files?
149
-
A18. Dear Mr. Gates, you have two options. Re-read question #17, or go buy
149
+
Q19. What about supporting playing of WMA files?
150
+
A19. Dear Mr. Gates, you have two options. Re-read question #17, or go buy
150
151
your own project.
151
152
152
-
Q19. When do you think there will be a version available for my Archos?
153
-
A19. We recently released version 1.2, so head on over to
153
+
Q20. When do you think there will be a version available for my Archos?
154
+
A20. We recently released version 1.2, so head on over to
154
155
http://rockbox.haxx.se/download.html and pull it down.
155
156
Make sure to read the release notes.
156
157
(http://rockbox.haxx.se/download/rockbox-1.2-notes.txt).
157
158
158
-
Q20. What do you plan to add to coming versions?
159
-
A20. We have a rough idea of which features we plan/expect/hope to be included
159
+
Q21. What do you plan to add to coming versions?
160
+
A21. We have a rough idea of which features we plan/expect/hope to be included
160
161
in which versions. Once again, remember that none of this is written in
161
162
stone (noticing a pattern yet?)
162
163
···
166
167
Version 1.4
167
168
Recording?
168
169
169
-
Q21. I tried one of your firmware files and now I can't access my harddisk!
170
+
Q22. I tried one of your firmware files and now I can't access my harddisk!
170
171
When I turn on my jukebox, it says:
171
172
Part. Error
172
173
Pls Chck HD
173
-
A21. Your harddisk has been password protected. We're not 100% sure why it
174
+
A22. Your harddisk has been password protected. We're not 100% sure why it
174
175
happens, but you can unlock it yourself. Look at:
175
176
http://rockbox.haxx.se/lock.html
176
177
177
-
Q22: This FAQ doesn't answer the question I have. What should I do?
178
-
A22: You have a couple options here. You could forget the question, find an
178
+
Q23: This FAQ doesn't answer the question I have. What should I do?
179
+
A23: You have a couple options here. You could forget the question, find an
179
180
easier question, or accept '42' as the answer no matter what. We don't
180
181
really recommend any of these (though I do opt for '42' often myself).
181
182
What we do recommend is stopping by IRC, reading
···
184
185
mailing list (rockbox@cool.haxx.se) or the FAQ maintainer listed on the
185
186
project homepage.
186
187
187
-
Q23: Are there other ways to contact the developers?
188
-
A23: Yes.
188
+
Q24: Are there other ways to contact the developers?
189
+
A24: Yes.
189
190
190
-
Q24: Are you going to tell us what they are?
191
-
A24: No. Post to the mailing list and we will get back to you.
191
+
Q25: Are you going to tell us what they are?
192
+
A25: No. Post to the mailing list and we will get back to you.
192
193
193
-
Q25: But I _really_ want to talk with you in person.
194
-
A25: I'm sorry. My girlfriend/boyfriend/pet says I'm not allowed to, and the
194
+
Q26: But I _really_ want to talk with you in person.
195
+
A26: I'm sorry. My girlfriend/boyfriend/pet says I'm not allowed to, and the
195
196
doctors here won't let me have pens or pencils. They say its some rule
196
197
about us not having sharp objects. I'm sorry. Now please stop calling me
197
198
here.
198
199
199
-
Q26: Will you ever port Quake II to the Archos?
200
-
A26: If you ask that again, I'm sending your address and phone number to the
200
+
Q27: Will you ever port Quake II to the Archos?
201
+
A27: If you ask that again, I'm sending your address and phone number to the
201
202
guy that mailed us with question #23.
202
203
203
-
Q27: Umm, was that sarcasm?
204
-
A27: That's it, I'm mailing him now.
204
+
Q28: Umm, was that sarcasm?
205
+
A28: That's it, I'm mailing him now.
205
206
206
-
Q28: Is this legal? I mean, I'd just hate to see something like that
207
+
Q29: Is this legal? I mean, I'd just hate to see something like that
207
208
challenged under the DMCA in all its ridiculousness. Any thoughts or
208
209
ideas?
209
-
A28: We believe we are in the green on this. We are not violating anyone's
210
+
A29: We believe we are in the green on this. We are not violating anyone's
210
211
copyright and we are not circumventing any copy protection scheme.
211
212
This has been a big point for the project since its inception. Some
212
213
people wanted us to distribute patched versions of the original firmware,
213
214
but seeing as that _would_ have violated Archos' copyright, we didn't
214
215
follow that course of action.
215
216
216
-
Q29: On the website [and various information postings] you state
217
+
Q30: On the website [and various information postings] you state
217
218
"Every tiny bit was reverse engineered, disassembled and then
218
219
re-written from scratch".
219
220
If it was rewritten from scratch then why was it first reverse-engineered
220
221
and disassembled? Instead this sounds more like someone disassembled it
221
222
then used the understanding that they gained to create a new version,
222
223
which is not quite the same as "from scratch".
223
-
A29: Don't confuse the terms. Reverse engineering means examining a product
224
+
A30: Don't confuse the terms. Reverse engineering means examining a product
224
225
to find out how it works. Disassembling the firmware is merely one tool
225
226
used in that examination. Oscilloscopes and logic analyzers are other
226
227
tools we have used. We have written every single byte of the Rockbox
···
230
231
software without first researching the surrounding interfaces, then no
231
232
software has ever been written from scratch.
232
233
233
-
Q30: Wait a minute here. When you released version 1.0 you did not have a single
234
-
one of the ideas you have mentioned on your website actually implimented!
235
-
Calling this version 1.0 is really misleading. Whats the story?!
236
-
A30: In simple terms, the first release was called 1.0 because it had a basic
234
+
Q31: Wait a minute here. When you released version 1.0 you did not have a
235
+
single one of the ideas you have mentioned on your website actually
236
+
implimented! Calling this version 1.0 is really misleading. Whats the
237
+
story?!
238
+
A31: In simple terms, the first release was called 1.0 because it had a basic
237
239
working feature set that worked and had no known bugs. That is what 1.0
238
240
meant. It is true that Rockbox 1.0 lacked most of the feature set that
239
241
every sane user wanted. However, we never said it was more
···
245
247
releases we have completed many of our desired goals, and several new ones
246
248
that were implimented to fullfill user requests.
247
249
248
-
Q31: I've heard talk of a 'Rolo'. What is that? (Or 'All you ever wanted
250
+
Q32: I've heard talk of a 'Rolo'. What is that? (Or 'All you ever wanted
249
251
to know about Rockbox boot loaders')
250
-
A31: The developers have discussed the possibility of a boot loader. (Mainly
252
+
A32: The developers have discussed the possibility of a boot loader. (Mainly
251
253
because having one sounds cool, and isn't Rolo just a great name?)
252
254
The idea would be that a user could use the load to choose between
253
255
different verions of Rockbox or the Archo firmware itself. We have a
···
258
260
the main release. Please check the mailing list logs and irc logs for more
259
261
information.
260
262
261
-
Q32: I was thinking about making the USB a bit more usable. What are the
263
+
Q33: I was thinking about making the USB a bit more usable. What are the
262
264
chances of using the USB port to [play games / share files / list
263
265
the device as something other then a hard drive / sell my soul to you
264
266
for a nickel]. What do you think?
265
-
A32: You really don't want to know what I think, it involves road flares,
267
+
A33: You really don't want to know what I think, it involves road flares,
266
268
microwave ovens and shaved cats. Enough said. But regarding the USB
267
269
portion of your question, this is not feasible. First, any ideas
268
270
regarding special communications over the USB port will not work because
···
274
276
master involved there can be no communication. Sorry. Now about your
275
277
soul. Would you settle for 3 cents and a small wad of belly button lint?
276
278
277
-
Q33: When I use RockBox my jukebox's red "error" light turns on a lot, but this
279
+
Q34: When I use RockBox my jukebox's red "error" light turns on a lot, but this
278
280
doesn't happen on the factory firmware. Why?
279
-
A33: Rockbox uses the red LED as harddisk activity light, not as an error
281
+
A34: Rockbox uses the red LED as harddisk activity light, not as an error
280
282
light. Relax and enjoy the music.
281
283
282
-
Q34: How do I use the loadable fonts?
283
-
A34: Loadable fonts are a work in progress. We do not have full documentation
284
+
Q35: How do I use the loadable fonts?
285
+
A35: Loadable fonts are a work in progress. We do not have full documentation
284
286
for it. The best we can do now is tell you that you need a valid .bdf
285
287
font, and to use the tool "bdf2ajf" from CVS to conver to the .ajf format.
286
288
The final .ajf font must be stored in the archos root as 'system.ajf'
287
289
We do expect more documentation on this process shortly.
288
290
289
-
Q35: I have a question about the batteries...
290
-
A35: STOP! We have put togeather a completely different FAQ for battery
291
+
Q36: I have a question about the batteries...
292
+
A36: STOP! We have put togeather a completely different FAQ for battery
291
293
related questions. Check out: http://rockbox.haxx.se/docs/battery.html
292
294