Rockbox

This patch provides a replacement for buffering.c, where there is only minimal buffering (one 32K buffer for audio data and some static buffers for metadata). It is a proof of concept for how this could work on targets with very little RAM.

I would be interested in feedback on the kind of impact this has on runtime, so if you have a flash target please consider giving it a try and reporting your results :)

Note that you will need to disable album art in your build for this to work. I don't even know what would happen if you don't, but it'd probably be bad. To disable it you need to comment or remove the #define HAVE_ALBUMART line in your target's configuration file (firmware/export/config-[TARGET].h).

Following my patch to control line-out on the Fuze via a setting on the quickscreen (FS#12074), I found I kept forgetting to leave the quickscreen. This meant that when I intended to change track, I was actually changing the shuffle / repeat settings etc and had to fiddle around to get back to where I wanted to - not a good idea when driving at >70mph!

The attached patch adds a configurable timeout to the quickscreen so that it returns to the WPS screen if no button is touched within N seconds. 0 (the default) will disable the timeout preserving the existing behaviour.

The iPod Classic Cirrus CS42L55 DAC+amp chip is specified to output audio up to +12dB versus the reference level (0.775V RMS) and the current Rockbox driver implements this accordingly (note that the OF limits the amplification to a lower level).

However, any amplification above +3dB applied to a 0dB signal results in serious clipping errors, the sound being distorted (oscilloscope measurements attached). This is not a surprise, given that +12dB translates in over 8V peak-to-peak output, way above what the iPod is capable of with its 3.7V battery.

Distortions aside, +12dB can be overkill for most of the earphones (depending on the sensitivity) and not a very pleasant experience. If you put the iPod in your pocket and forget to lock it you may experience this frequently.

In practice not all tracks have peaks reaching the 0dB level (actually nowadays this is quite common given the "loudness war"). To provide some room for additional amplification when needed, I found the +6dB limit to be a good compromise.

Using a bootloader from  FS#9955 , a USB connection is not made if Start Screen is set to WPS, and the user boots Rockbox by inserting a USB cable.

This is possibly also true for other values of Start Screen.

Tested on e280, but I expect it’ll likely be the case on other PP targets with USB

Various users on IRC recently reported cases of filesystem corruption. I have seen them as well, especially when using USB mode (I'm using a Sansa ClipV2, USB-enabled through  FS#11664 ).

One strangeness I've experienced is that when my system has detected filesystem corruption, it is often enough to remove the player from USB and then replug it, without repairing the filesystem and without rebooting Rockbox; on the next USB mount, the filesystem is clean. This might indicate that some buffer is flushed too late for the USB host to see.

[EDIT: Removed previously attached patch, which is now tracked separately as FS#11883.]

Both issues seem to appear with any version of my theme and with any build.
Let's try it with the latest version 1.30 of my theme (in attachment but also here: http://themes.rockbox.org/index.php?themeid=1585 ) and a recent build (I use version: 0c4bd3a-120406)

-Theme loading

When you load the theme for the 1st time, the WPS will never load properly (failsafe). The workaround is to turn off the device and turn it on again and then the WPS will always load properly until you reload the theme for some reasons (trying another theme and revert back to mine etc).
I tried both with the full theme version and this "light" version of WPS: http://pastie.org/3747546

-USB connection (tested on Windows 7, with or without a microSD, and there isn't such an issue with the other themes)

If I plug the USB cable while the player is on or off, it will almost never mount properly.
Usually the USB screen appears on my SBS, the computer recognizes a USB device is connected but either nothing appears in "my computer" or the device appears but is not accessible. When I unplug the USB cable, the Zip gets stuck on the USB screen and only reset can turn it off.
Sometimes it even displays some erros like that when plugging the USB cable: "data abort at 30FSR 0x8 (domain 0, fault address 0x964176 bt pc: 0x3006AC3 bt end" , sometimes it doesn't display the USB on SBS but gets stuck on the main menu.
And rarely in the same conditions it also mounts properly…

Like for WPS, I made a "light" version of SBS without the status bar and that way the Zip seems to mount and unmout properly every time!
http://pastie.org/private/cauhxelaip7hrpqpcwdbxw So maybe a tag in the status bar causes the issue with USB connection?

This may be all players; I have only had experience with the Sansa Clip+ and Clip Zip. On version 3.13 the Automatic Resume feature works inconsistently, especially on the 2nd+ file of a playlist.

In version 3.11.2, the feature worked correctly on my Clip+. If I paused the player and the player turned off due to the timeout, when I turned the player back on and pressed the “Home” button or “Resume Playback”, the entire playlist would be back in place and playback would resume at the spot I paused. If I was 30 seconds into the third file in a playlist, playback would resume at that point. When that file finished, the next file in the playlist would start. Pressing “Previous” or “Next” would play the previous or next file in the playlist.

In version 3.13, this feature does not always work correctly. In fact, it rarely works correctly when playing a file that is not the first file in a playlist. Some times it works fine. Most times when I try to resume playback, it instead plays the beginning of the first track in the playlist. Some times when that happens, if I manually navigate to the track I was in when I paused, it will resume that track from the correct position rather than starting it over from the beginning.

This behavior is seriously agitating. I use my player to listen to multi-hour podcasts broken into separate files for each hour. If I get a phone call and pause my player I expect my player to automatically shut itself off after a few minutes, and it does. When I start the player again, I want to be able to pick up just where I left off. On versions prior to this, I could. In 3.13 it does not work 9 out of 10 times.

This patch adds more touchpad functionality to the game. It is possible to play by selecting the pieces directly instead of using the simulated buttons.
The changes are:
1. Added touchpad_get_mode to the plugin API.
2. Added menu entry for touchpad devices the switch between button mode and direct mode.
3. The user’s default touchpad mode is save during start-up of the plugin and restored after quitting.
4. The direct input mode is set only during the game (not in menu or view).
5. Extended play loop to handle BUTTON_TOUCHPAD event.
6. A piece is selected by clicking twice on it, moving is also done by clicking the target field twice.

The patch has been tested on the COWON D2 and also seems to compile fine for devices w/o touchpad. The patch has been created with

svn diff -x -w apps > touch_chess.diff

in the root directory. It would be nice if someone could test this (also on non-touchpad devices) and give me some feedback (bugs and improvements).

This patch makes the graphic EQ usable in the absolute mode on touchscreen models.
Additionally I made the following changes:

* Add a menu in the touchscreen settings to select the touchscreen mode in the graphic EQ ( because in menus I prefer the grid mode, in the EQ the absolute mode is much better)

* Always try to use the UI_FONT , make the EQ filling the whole screen and add a little margin on the left and right side. In that way it can even used with fingers on a touchscreen (automatic adaption to fill the whole screen should work for all targets with EQ and LCD).

I tested on my Cowon D2 and Iriver H340 to make sure non touchscreen models stil work, both worked perfect.

This patch should save pitch and speed settings to nvram, and restore them after reboot if needed.

If I read the code correctly, there should be enough room in nvram (and anyway, the way this is done doesn't apply to any targets that actually use real nvram)

This code compiles, but apart from that it's completely untested.

Of course, since this patch increments the nvram data version, you'll lose resume info the first time you reboot.

Patch against r28560.

Adds options for displaying pitches according to key (for transposing instruments) and “mixed” accidentals a la Korg (C#, Eb, F#, G#, Bb).

I’d also like to add some kind of support for alternate temperaments (perhaps even just intonation), however this isn’t trivial and I probably won’t undertake the project unless some interest is expressed.

While examining disk performance with  FS#9708 , I found one album where the disk stayed spinning with no activity for 5 s longer when using PIO. This is repeatable with that particular album. With the downloaded r19739-090109 build, this did not happen with the default settings but it started happening as soon as I enabled dircache. Prolonging the disk timeout prolongs the extra sleeping time.

Experimentation with shows that the storage_sleep() part of fill_buffer() (in apps/buffering.c) is executed early in the buffering and it is not executed at the end. With another album where spindown happens properly, ata_sleep() is called twice. Note that ata_sleep() just sets last_disk_activity, and sleep happens over half a second later if there is no disk activity during that period and last_user_activity has timed out.

I think this is a race condition based on how dircache and transfer rates change things. I wonder if it is related to  FS#9541 .

The data mentioned is located at http://spreadsheets.google.com/ccc?key=pkeRcfM0sg949P3a5EYXtew and the delayed spindown is seen in the EP7 PIO test. In that data, also note how sectors written are 5, 10 or 15, with differences between different tests with the same album.

I have a 30GB 5th generation iPod, but I expect this issue affects all SW-codec players.

When listing to a mp3 for some time there starts a massive random noise in the background. It will continue for some time when pausing or stopping playback and will also continue when starting another track.
I’ve noticed this when listening to a random list of mp3s of various sources and using speedup with 225% or 250%.

At the moment I’m using ee758c5 with my clip+.

Using release 3.13 on the clip zip, if I were to put the main crossfeed setting on the right button of the quickscreen, it would cycle through to custom but then stop. If I use the left button of the quickscreen, then after custom there is a data abort crash.

Using build c64b59f-140304, both the left and right quickscreen buttons work to cycle through all 3 settings for crossfeed, but I can still trigger the crash if I use the left button. It seems to be sporadic and timing dependent, because if I click through the options quickly it works fine, but if I slow down and hold the buttons for longer at a time then it will eventually trigger.

Here is a picture of the crash: http://i.imgur.com/wS1CqVr.jpg The text is:
Data abort at 30800E
FSR 0x8
(domain 0, fault 8)
address 0xB00Fb5D
pc:30800BA8 sp:300<snip> the screen is too narrow, here
bt end

Hello,
I’ve recently designed new text editing plugin for Rockbox, which I called (how original…) rockedit. The point is not to compete with current text_editor, but rather to develop a new approach to text editing by, in particular, allowing user to work in insert/replace mode. The major difference is that the keypad has been replaced by a single which the user navigates through using up/down, while left/right are used to change current char. Fire key is used to switch between different chars lists.
I didn’t manage, though, to use keypad as set in r17659. The diff file just reverts it, which is not a good solution at all… Furthermore, I haven’t tested it on any other target but my gigabeat : I cannot boot Windows currently.

I’ve included a patch which includes keymap changes, and another which doesn’t. I’ve also added a screenshot.
Please do comment and help me improve this editor !

This patch implements HAVE_LCD_SHUTDOWN functionality for Photo and Color iPods. It is in response to issue 2 in http://forums.rockbox.org/index.php?topic=20994 : “2. The LCD screen on the iPod is not cleared properly when I shut down rockbox. I see 1-2 horizontal lines remain on the screen (which do fade after a minute or so). Nothing is wrong with my IPod’s LCD screen as I did not experience this with Apple’s Firmware”

It seems the Color iPod can have 4 different LCDs. They’re detected via two GPIO bits in lcd-color_nano.c. Types 0 and 2 are the old LCD with an unknown controller and they use the same init, shutdown and update procedures, and they are reported as 0. Types 1 and 3 are similar to HD66789R. They have different init and shutdown procedures but they share the same update procedure. Both 1 and 3 were reported as 1 earlier.

To see what LCD type you have, from the main menu go to System → Debug (Keep Out) → View HW Info and then see the number after “LCD type:”.

This patch has only been tested with LCD type 3 so far.

I am submitting this as a patch because I feel it is not a significant bug. Theoretically, the DC voltage that’s left can degrade the LCD, but the line fades quickly and no negative after-effects were reported.

I would like to also add LCD initialization code and develop HAVE_LCD_SLEEP functionality.

This patch which is a small change in bidi.c contributes with the diacritics patch (http://www.rockbox.org/tracker/task/10720) to fix the diacritized Arabic text joining problem

Added new menu item under Settings.General.System, to select whether USB cable connection enters charging mode by default, or data transfer mode.

By default, the option is set to "No". Meaning, in order to have RB enter charging mode, a specific button should be pressed by the user.

If the option is set to "Yes", USB connection causes RB to enter charging mode, unless the specified button is pressed, causing RB to switch into data xfer mode.

Initial support for showing input in the fft plugin. Now, on targets supporting recording, instead of quiting when no track is playing, fft starts monitoring the audio input (using the settings under Recording Settings).

The first patch is just the functional changes, the second patch fixes the indentation of the entire file.

I’m not sure if it works at all since I don’t have a device that can record.

The setting works similar to the autoresume dirs: Directories are seperated
by colon, e.g. "/Music:/Podcasts". Default is "/sdcard" on android, "/" on
all other targets.

A maximum of 8 dirs can be selected, the setting cannot be longer than 80 chars.

Note: There's one problem. If you specifiy "/Music:/" (or any folder and one if its parents afterwards), then /Music is scanned twice. It's tricky to fix, and I'm not sure if it's worth it. This does not happen for "/:/Music" as it can be detected more easily in this order (and this is already implemented).

Rockbox WebOS app.

Built on r31467, 32/64-bit Ubuntu 11.10, running on a 32GB Touchpad

Directions (only tested on the above):

* Install WebOS PDK: https://developer.palm.com/content/resources/develop/sdk_pdk_download.html

* Install platform-native libsdl-dev if you haven't already. Only needed to pass configuration check as the PDK doesn't properly install staging sdl-config for some reason.

* Apply patch (patch -p0 < filename.patch)

* cd webos

* ../tools/configure, select WebOS target (206)

* make && make install && sh ./buildpkg.sh

Notes:

* This is one big hack – I fudged just about everything in /firmware (how the target system works is still not altogether clear to me) and piggybacked a lot of this off of the SDL target. Mostly in the interest of getting it to run without adding ifdefs all over the place. Obviously we'll want to be more methodical and thorough about exactly which changes need to go where moving forward.

* The Touchpad's SDL video implementation appears to adjust orientation and scale output to fit within 1024x768 as best as possible. This means that a 800x480 build will appear in landscape mode, letterboxed, while a 320x480 will appear in portrait mode, pillarboxed. The device itself automatically orients to landscape – meaning, if you're in a portrait resolution and then you exit, everything will initially be sideways – but that doesn't affect input. Scaling routines are noticeably slow.

* I tried building this as a hybrid Enyo/PDK (window mgr friendly) app but had some problems with the native part failing to execute at SDL_Init. So for now no backgrounding or notification bar.

* Make scripts use the ARM compilers installed with the PDK. I'm wondering though if this is superfluous given that the Rockbox toolchain also supports ARM7. I did try exposing some of the ARM-specific assembly but the compilation failed with the PDK compiler.

800x480 build: http://www.jasonyu.net/webos/org.rockbox.raap_0.0.1_all.ipk

I'm using the newest build of Rockbox (2007-07-21) with an iAudio X5 20 GB and I have my tuner set to the European region. I encounter two little flaws in the FM-radio. I think they partially have to do with the player's hardware, but maybe Rockbox can improve the quality a bit.

1. The player is really sensitive to movement. The signal strength differs with every meter that you take the player with you. On top of that, most stations sound like they're not correctly tuned, but I can't get them any better. Maybe Rockbox could be more accurate in frequency selection? (Like 101.100, 101.125, 101.150.) I can get these stations quite well on my home radio. I don't expect the same quality from such a small device, but some finetuning would be great. The only problem is that it would take a while to scroll through the frequencies, but once set it'd be fine.
2. (I assume this is very hardware related.) The radio signal may change between stereo and mono. I have it set to stereo, but sometimes it just picks mono. I guess this is because of the hardware, since it is place related. I also didn't find any potential bugs in the source code.

What are your thoughts on this?

Oh, and keep up this good work! I really enjoy Rockbox!

When recording, as file size reaches 25.2MB and again at 52.4MB respectively, disk thrashing noise drowns out the recording for about 2 minutes.
This occurs at about 27.5 minutes if recording as mp3.
And about 5.25 minutes if recording as wav.

I am assuming that Rockbox is filling a cache and then dumping the file to disk all at once.

I would expect it to write quietly. Even if it where to write on the fly, the noise would be reduced to short bursts. 2 minutes of interruption is just not acceptable. I missed out on important information during those 2 minute periods.

How can we eliminate write noise altogether? Or at least in the recording itself.

Select ‘FM Radio’ Choose your station.
Then from the menu select ‘Recording’ Press ‘play’ or ‘Rec’ to begin recording.
Wait for file size to reach about 28MB. Then stop.

I can also provide recordings if necessary.

*note: I also had the USB cord attached to give better FM reception.
tested on e260 & e280
Rockbox Version: r15988-080102

Thanks

This is a recurring problem with this target it seems. With 3.1 installed and resume playback on start up enabled, playback hangs and skips badly while the hard drive is being scanned during start up.

The same behavior occurs when resume on start up is disabled, but playback is resumed by the user during the hard drive scan.

to reproduce:

1. start a big (20mb or more) track. delete it immidiately after starting it.
2. let the song play until it stops. i guess it stops at the end of the buffer. as an alternative you can ff to the end of the track (which shouldn't be buffered)
3. now you're not able to play any track. if you select a new one from the file browser or database, the wps will show up, but nothing is played and the progress bar won't progress. ff and rw also don 't work. only rebooting helps. shutting down needs really long (~15s).

if you delete a fully buffered song, everything works as expected (well, the song continues till the end, and the next song starts. some devs call that "expected" :D ).

tested with r24091 and an e200, although i guess that the bug is target independent and occurs in the last few thousand revisions :)

When using an image in a theme it shows ugly gradients/dithering, as if it was only 16 bit. When the same image however is used as backdrop (%X tag, instead of ‘regular’ %xl and %xd), it looks smooth and 24 bit.

Attached image shows the issue. Top half shows what Rockbox does when the image is loaded via %xl and %xd. Bottom half shows how the image should look like (and how it does indeed look when it’s used as a %X backdrop).

Tested on a Cowon D2 simulator and on an Android device running RaaA.

This Patch changes the way that ratings work. It’s pretty simple, it reads the rating info from an MP3 files ID3 POPM tag, and converts that to a Rockbox rating value (0 to 10).

You can then use patch  FS#6301  - new tags for WPS and tagcache patch 4 (4_rating.patch) to display the rating on the WPS (tag is %rr). Some Themes use this tag already so I’m not sure if it is in SVN already.

The patch is written for MediaMonkey (alpha 3), but it should work with other version of MediaMonkey, and other programs that put ratings in the ID3 tag (not iTunes).

Tested on iPod nano.

One thing I’m not sure of is what value to return for bufferpos - should this return an int ponting to the next id3 tag position, or is it OK to return it as is? it dosen’t seem to make any difference either way.

Comments are welcome.

I created the following fonts from DejaVuSans.ttf using ttf2bdf.

I use them as an alternative for unifont, which is fixed-width.

Attached are a screenshot and a tarball with 8 to 12pt versions of the font.
Perhaps they could be included in the official distribution, if others like them.

This tracker task will be used to house my Summer of Code work. For information about the goals of the project please see http://www.rockbox.org/twiki/bin/view/Main/PluginLocalization . Please read the comments and the descriptions of each patch.

Latest patch:
July 22

This small patch adds a “jump to time” function to wps context menu. After clicking on jump 2 time item user, can specify time in mmmss format E.G:
- 130: jump to 1:30 in currently playing track
- 90: jump to 1:30 in currently playing track (shorter version of previous example)
- 1529: jump to 15:29
- 12345: jump to 123:45 (2 hours, 3 mins, 45 seconds)

I use it to easily transfer “last played position” time from computer to rockbox. Can be useful for audio books listeners.

The database hangs when doing initialization if there is no music file on the player.

How to reproduce:
1. Install Rockbox.
2. Put some music files onto the device.
3. Initialize database.
4. Reboot.
5. Remove all music files from the player.
6. Initialize database.

also category:
Some containers, like Matroska MKA or like Ogg can contain numerous audio tracks, for example the whole AudioCD contained within single Ogg file.

For example VideoLAN.org plays such files ok, while fails to show separate tracks/tags in playlist.

However, RockBox justs freezes and until reboot can no longer play music (each file is detected as having zero duration)

example can be found: [link deleted - it was a full copyrighted album]

Using the latest revision (r20001 - but its been broken since I started using Rockbox) the iAudio M3 does not recharge the battery using either the USB or the Power adapter.

The only way I can get the iAudio M3 to charge is to use Cowon’s firmware.

Build 20399

The database_changelog.txt is corrupted in that the wrong filename is associated with a track, this has happened before (pre v3.0), I had to write ascript to correct it.

Exampe row from log:

artist=”Teach Yourself” album=”Polish Conversation (Disc 3)” genre=”Books & Spoken” title=”Conversation 1: Booking A Hotel In Krakow” filename=”/iPod_Control/Music/Blur/Blur - Blur/14 Essex Dogs.mp3” composer=”<Untagged>” comment=”<Untagged>” albumartist=”Teach Yourself” grouping=”Conversation 1: Booking A Hotel In Krakow” year=”2006” discnumber=”3” tracknumber=”2” bitrate=”71” length=”640824” playcount=”0” rating=”0” playtime=”0” lastplayed=”0” commitid=”12” mtime=”955689818”

When the battery is low, Rockbox is unable to charge iPod. When booting into Rockbox, the charging icon is displayed, but after a while the device shuts down.

Booting the OF and charging under it for few minutes is required.

On the Official Test Build for the Sansa Fuze, when playing Doom, in middle of playing, Rockbox gives a Data Abort Error. If it doesn't happen in middle of playing, it is always reproducible by entering the second Map. The most recent error i got is "Data Abort at 307B32D4". My Version is "r21704-090707".

It happened once just browsing through the Menu, but is only reproduced every time by playing Doom, which is why I filed it under Doom.

I will try to try a later revision and see if it fixes the bug.

The interface of my Sansa Fuze and the file transfer freeze randomly when transferring large amounts of data. If the player runs in Bootloader USB mode everything is fine.

I guess this could break the vfat file system, making this a nasty bug. Disabling Key and Mouseemulation did not help. As long as this isn't fixed, a solution would be to start the player in Bootloader USB mode by default. I don't know if this is possible though, since I don't know the the technical details of rockbox very well.

Beside that everything works just great, keep up the good word!

PS.: I'm using Debian with different kernels. I couldn't see any differences between different kernel versions regarding this issue. Intels Linux USB drivers and the Linux USB stack in general usually work excellent as far as I know, therefore I would blame it on rockbox (no offense :)).

Sansa Clip v1. Stable version 3.10 [Tracker didn’t let me choose it?]
After playing the item for some time [varies] Rockbox crash and give this error:
Data abort
at 3001913E
FSR 0×8 (domain 0, fault 8)
address 0x7261702D

Using DFKT Minimum Clip theme.

In Rockbox for Android it is not possible to highlight an entry in a list without selecting (entering) it.

For example, if I am in the playlist viewer showing the list of just playing songs with my ipod (running rockbox) I was able to scroll through the list which moved the higligting bar through the list and then I could select the desired entry by pressing enter. With the touchscreen I found no way only to highlight a certain entry.

This is important if all entries are very long and have the same starting text. For example "Ludwig von Beethoven, Symphony No. 9 - 1. Adagio" cannot be distinguished from "Ludwig von Beethoven, Symphony No. 9 - 2. Andante" in the playlist viewer since the distinguishing part is cut off. With my ipod I could highlight the entries with the scroll wheel and the highlighted line started horizontally scrolling so I could see the complete text. With the Android port I can only touch the line, but touching the line does not only highlight it but also selects it and so starts playing.

This problem also exists in other list with long entries and happens with all version I compiled until now (latest was a12b2a5).

I have sansa clip+. Lrcplayer opens and plays USLT tag instead of SYLT tag if there are both in mp3 file and no external lyrics(.lrc, .lrc8, .snc, .txt) so lyrics which play are not synchronized. Please make SYLT tag opens and plays defaultly instead of USLT tag.

Rockbox Info: Version: 3.12

Device: iRiver H140, 80GB Toshiba MK8009GAH 8mm 1.8" IDE HDD 8mm

BUG: Repeatable, Consistent.

Additional Information:
1. To verify that I had a good installation of the 3.12 version of the Rockbox firmware working, I have reformatted, and re-flashed rockbox 3.12 two seperate times after initially encountering this, duplicating this behavior. So it doesn't seem to be a bad firmware flash.

Expected Behavior:

1. Player should Power On and boot properly every single time the bootup sequence is initiated correctly (Play Button pressed when Player is in a Powered Off state).

Buggy Behavior:

1. Player Powers Up, then locks up (i.e. "crashes") during bootloader sequence, requiring a hard reset, and upon second boot, finally Powers On and boots properly, bringing up a functional session of the Main User Interface. This is repeatable, and consistent.

Bug Symptoms & How To Repeat:

1. Consistently the Player will lock up during first "boot" sequence. The bootloader will usually reach the text stage, and sometimes crash here. Sometimes the bootloader will get through the text stage and reach the Rockbox Logo and then crash here. The Main User Interface is never reached upon first "boot" sequence.

2. The result of the first "boot" lockup (i.e. "crash") requires that I reset the Player by inserting a paperclip into the Reset hole (on the bottom plate of the Player) and triggering the button hidden in there. This Powers Down the Player, and Resets the Firmware, leaving the Player ready to be Powered On again.

3. Upon the second "boot", the Player will "boot" and the bootloader will make it past the text stage, the Rockbox Logo stage, and then spin up the HDD properly; the bootloader will not lock up the firmware, and behaves 'normally', finally resulting in a completed boot up sequence with the Main User Interface coming up (as a user would expect). The Player is now ready to use.

Playback halts.
No error screen appears – screen seems to stay where it is when freeze occurs, i.e. WPS or back light off.

Tested multiple audio formats.

Does not occur if no head phones are plugged in.

If you play a song for a bit at low volume (tested -14dB) before raising the volume, it is okay.

To reproduce:
Find a loud, bass-heavy part of a song, and halt playback right there.
Set volume to 6dB.
Set bass to 14.
Resume playback.

Usually freezes in less than a second when I do that.

RB version:
33f3af2-130523

Hello

I run rockbox daily (last update 27 Feb 2014) and found an issue that I like to report. I have my sandisk clip zip connected to an external USB hub, which is connected to my notebook. Today I left the sandisk clip zip connected and turned the notebook off. I expected that the player will disconnect from the USB hub → blanks the screen after 20-30 seconds (depending on the setup) and then turns off after a while (depending on the setup). Unfortunately the last step won't happen.

The sandisk clip zip really disconnected from the USB connection (the usb picture disappears from the display) with the notebook going back into the rockbox menu (Play, Radio, Settings, Recording etc.) and after a while also blanks the screen as expected.

Unfortunately it does NOT turn itself off as it would if you leave it entirely unconnected (unwired) with the USB. The sandisk clip zip starts to turn the screen on again after a while, turns off again, turns on again after a while, turns off etc.

I had to plug off the mini USB connection (the wiring between the player and the usb hub) so it turns off and shuts down after a while.

What I believe is, that the USB subroutines might not know the difference between powered on notebook and powered off notebook. It only knows that it's wired and thus tries to turn the player on again after it blanks. It should really be possible to keep the player connected (and wired) when the notebook shuts down and have the player shut down as well (after blanking and then turning itself off).

Could this be reviewed and maybe worked on ?

Thanks so far.

Hi,
I've been using the development version of Rockbox in my ipod classic 6th generation for about two years I think, but from some time, like a month or two, I'm experiencing playback issues as the track I'm listening suddenly skip forward or backward, or even jump for a few seconds on another mp3 file inside the ipod I was just listening before. I don't think is a ipod issue because I can listen the file inside the ipod with my computer player without problems.

There some way I can check older development revisions for the classic? It appears that it doesn't show in the dev build link on the site because is not fully supported. Thanks

I am trying to build Rockbox for Sony NWZ-380 from Git repo, commit ce0b31d87db3c4c1c1bfb535c50770d33e9c4aaf.
arm-elf-eabi-gcc version 5.4.0, ARM binutils 2.30.
Everything goes smooth until just the latest step where this happens:

… LD duke3d.ovl
LD bmp.ovl
LD jpeg.ovl
LD png.ovl
LD ppm.ovl
LD gif.ovl
LD rockbox.elf
/usr/libexec/gcc/arm-elf-eabi/ld: section .ARM.exidx VMA [00000000600a9548,00000000600a954f] overlaps section .bss VMA [00000000600a7f20,00000000600ff773]

I'm using Rockbox on my NWZ-384 for a couple of years now and there were no problems building it in the past. I also was very glad that NWZ-380 port reached stable status in 3.14,
but now something seems to be broken (not terrible it seems, just requires some adjustments to the linker scripts but still).

HI, is there a way that you could add a “Single”
playmode, so it stops after playing one song, instead of
repeating all, or repeating single? That way, it could also
be used as an “auto-off”, where it shuts off after one
song. Also, and maybe this isnt possible, but you could
have an option to play X number of songs and then stop,
where the X is configurable.

It would be nice if the “Generate” menu-option opened a submenu where you could pick which difficulty to generate.

I’ve had a quick glance at the code, and it looks like it’d have to generate until a suitable difficulty is found, but that’s no different from what users have to do now, if they’re after a specific difficulty, except it’d happen automatically.

If I get the time/motivation, I may have another look at it in the next couple of days.

This very small patch simply plays a beep when a charger is removed or plugged in.
I know  FS#7910  voiced this but that was a bit annoying.

The charger stuff will be removed from p7910. I could have added this to it but it isn’t really that related.

When the wake-up alarm starts up the iPod, you wouldn’t want it to boot the OF, but it will do so if hold is on. This patch makes the bootloader check if the alarm is active and start rockbox regardless of the hold state if it is. Also, if the hold switch is on during start up rockbox would normally reset all settings, but this is inactivated if rockbox was started by the alarm.

Applying the patch:
Besides building the firmware, you will need to build and upload the bootloader to your ipod using ipodpatcher.

Limitations:
The bootloader doesn’t check if the alarm started ipod, it only checks if the alarm is active. If you have set the alarm you will have to use the MENU button to start the OF.

I don’t know if this works on any other iPods than the iPod video, but it will probably work on all of them.

This is a variant of an the classic Paratroopers.

It lacks the particles, planes and stacking men. Instead of solders, They're just falling bombs.

For more details about the source of inspiration:
http://en.wikipedia.org/wiki/Paratrooper_(video_game)