Fuze and Griffin Dock line out

[j8048188]

Ggul: If you post the working patch in Flyspray, it may be accepted.
I don't see any patches with any work done, so you should create a new one.
Best of luck!

[saratoga]

Post the patch to FS (cleaned up and working since I have no way to test it) with your real name and I'll commit it then add you to the credits.

Edit:  Also would you be willing to test if DBOP_DIN pin method works for enabling line out with your dock?  Read pin 9 and use that to enable or disable power to the line out amplifier.  That way we won't waste power on the line out when its not being used.

[bertrik]

It would be nice indeed if LINE OUT could be enabled only on with a dock attached.

Maybe we can use a mechanism similar to the headphones insertion detection to enable/disable LINE OUT?

[saratoga]

The DBOP and GPIO pins change when a dock is inserted, so checking them should be enough. Although first I'd be happy with a working patch that just leaves it on all the time.

[sanmigel]

Hi! Does any progress in line out on Fuze rockbox?

[saratoga]

Hi! Does any progress in line out on Fuze rockbox?

I'm sure if theres progress, someone will mention it.

[orbidia]

I could definately use line out from the fuze for a portable setup with an external amp and a diy line out cable.

It sounds like gglul figured it out and it works on the fuze v1 at least. I guess gglul's "patch 2" is the one to use.

Is this difficult to post to flyspray and get this in one of the builds? Sounds like the code is done and just waiting to be added...

[OldOne]

There is a patch on flyspray to enable for E200v2 as well as Fuze v1. Work is being done  on the Fuze v2.  #11367

Link Below
http://www.rockbox.org/tracker/task/11367?project=1&type=4&order=dateopened&sort=desc

[mc2739]

Line out for the e200v2 is enabled as of r27162.  This should also work for the Fuzev1, but has not been tested.

Be sure to connect the dock after booting Rockbox. Connecting the dock with power off will boot into the OF.

For the c200v2 and Fuzev2 we still need to determine how to detect when the dock is connected.

[Avalon]

I have tested on a Fuze V1 and it works! 

Many thanks to the developers.  This is a very useful feature.

I have found one problem which may be a setting I am not aware of.  My Fuze powers down while docked after about 10 minutes.  I have changed the idle timeout to off with no change.  Does anyone know why this is happening?  

A couple of observations:

1. As indicated, the Fuze must be in RockBox mode before connecting.

2. When the Fuze is connected it displays the "USB Keyboard Mode: Multimedia" message, pauses the current track and reverts to the main menu.  You must select "Resume Playback" to continue with the current track.
 
3. When connected to the dock, the Fuze appears to provide the true line out since there is no volume control at the Fuze.  I checked this by disconnecting the playing Fuze from the dock and connecting it to the dock output cable.  To get the same volume level, the Fuze volume had to be set to the 6dB maximum level. 

4. I could not check to see if the headphone output is enabled when connected to the dock because I have to remove the headphones to connect to the dock.  However, this is not a consideration for me since the dock keeps the Fuze fully charged. 

Thks again!!

[mc2739]

I have found one problem which may be a setting I am not aware of.  My Fuze powers down while docked after about 10 minutes.  I have changed the idle timeout to off with no change.  Does anyone know why this is happening?

I am not sure what is going on here.  This does not happen with my e200v2.  I have had it playing music through the dock connection and just sitting idle while connected for more than an hour each without shutting off.

One thing you might try is to reset your settings to default.  This can be done through the Settings -> Manage Settings menu.  You may want to save a copy of your .rockbox/config.cfg file so that you can restore your settings if the reset does not help.

[Avalon]

I don't know what was going on either.

I reset the settings to default, selected the theme I use and put back my normal settings.....everything is working perfectly!

I ran the Fuze V1 in the dock for 3 hours and counting with no problems.

Thanks for the suggestion!

[Avalon]

I recently installed the new boot firmware and r27578-100726 to check out the USB function.  It works great for connecting to my PC (XP)...thanks to the developers.  This greatly improves access to the Fuze.

Since the USB interface is now supported, is the docking modification discussed in this thread affected?

I am asking this because, it appears that my Fuze V1 does not work properly when powered down and inserted into the dock.  The following outlines what I have seen.

__________________________

If I connect to the dock (Griffin) with RockBox running, it works fine. 

If I connect while the Fuze is powered down, it boots up in RockBox mode as it should, but it will not resume playback.  If I try to select another album, the database initialization menu is displayed.  If I then disconnect from the dock the Fuze will resume playback, but the current playlist is corrupted (E**) and tracks are skipped.

It seems that by connecting to the dock, the fuze database access is corrupted in some way.

I found that this occurs when directory cache is enabled.  When I turn off directory cache, everything seems to work fine.  This is an inconvenience for me because the database initialization is much faster with directory cache enabled.

Has anyone else seen this....any comments?

[mc2739]

I am asking this because, it appears that my Fuze V1 does not work properly when powered down and inserted into the dock.

You need to download the latest version of mkamsboot (v1.4) and the latest bootloader (v2.0 for the Fuze v1).  The links to the files and the installation instructions can be found on the SansaAMS wiki page in the Manual installation section.

[Avalon]

Perhaps I was not clear.  As I indicated, I have installed the new boot firmware as of July 31, 2010.  I don't know what version of mkamsboot or the bootloader, but both were downloaded from the SansaAMS wiki page on July 31, 2010.  I used these to generate the new boot firmware.

I went back over some older posts and found the suggestion to clear the config file to reset it.  I did that and the problem is fixed.

Thanks for the feedback.