Rockbox Technical Forums

Rockbox Development => New Ports => Topic started by: metaphys on November 17, 2010, 12:40:37 PM

Title: Sansa Fuze+
Post by: metaphys on November 17, 2010, 12:40:37 PM
I 'm starting on a port for Sansa Fuze+

http://www.rockbox.org/wiki/SansaFuzePlus

For the moment there is only PCB scans and a few info about components

Futher info to come... to be continued

Title: Re: Sansa Fuze+
Post by: pamaury on November 29, 2010, 10:50:55 AM
I have been able to decrypt the Fuze+ firmware. The sbinfo program in the SVN is nearly complete now and allows to retrieve the code in an decrypted form, even though it would be better to rebuild an elf file out of it to work on it.
I would be quite interested in helping the port if possible.
Title: Re: Sansa Fuze+
Post by: metaphys on November 29, 2010, 05:00:18 PM
Please do!  :D
Actually i'm learning C by now and will not be able to contribuate to the port before i'm done with it (I'm starting this port from scratch with no other knowledge than my will to learn.... I don't know how long it'll need before I'll could write anything valuable. I just though I would do whatever I could (scanning pcb, open a new wiki, for exemple...) and then start to learn before to continue on contribuing.

I'm really impressed on the rapidity people did start to find and give information about it  :o. If you need more info, or someone to test your program in the case you don't own a fuze+, I still can help.  ;D

Correct me if i'm wrong but with the firmware being decrypted, I suppose the next level should be to make a fake very close from the original and try to update the device with it... isn't it?

ps: I updated my profil's page so that you can email me if you need to.
Title: Re: Sansa Fuze+
Post by: bertrik on December 01, 2010, 05:32:29 AM
A few of the things I wonder about the fuze+:
1) how does the whole booting of this thing work? (important to know at what point during the boot process we can make it start running rockbox code)
2) does it have some kind of recovery mode? (very important once we start trying to run our own possibly buggy code)

Could you (for example) try to figure out if there is some kind of special boot or recovery mode?
Very often a special boot mode is started when holding a specific button during power-up (or perhaps a combination of buttons).
Sometimes these boot modes don't show anything on the screen but you can recognise them because they act as a USB device, possibly with a different USB vendor/product id than it shows normally.

Does it have a reset button (reachable only by a paperclip possibly)?
Title: Re: Sansa Fuze+
Post by: metaphys on December 01, 2010, 11:30:26 AM
concerning 1) i'm really not competent - or is there any test I could perform that might helps you to figure it out?
as far as I understand it: there are 3 different boot mode:
- normal:
          - boot
          - then screen change to some sandisk turning logo asking to wait (probably rescaning of tag info or updating already saved library)
- USB mode MTP
- USB mode MSC

note that there is an optionnal menu in the original firmware to choose between the two USB mode, note also the following hints to force MSC mode...

2)
a) There is a reset fonction mentionned in the manual by hold on/off button for 20 sec.
see: http://forums.sandisk.com/t5/User-guides-Firmware-Software/User-Manuals-for-all-Sansa-Products/td-p/185344 on p. 10 (I suppose some kind of hard reboot)

b) on: http://forums.sandisk.com/t5/Fuze/Sansa-Fuze-Firmware-01-29-03/td-p/207292
 the former firmware update mentionned the implementation of a new fonction:
"Force device into MSC mode using key combination (Device OFF press & hold Volume down Button and connect device to PC)"

But as it comes as a firmware update I suppose we can count that out to recover after changing the firmware.

c) As I mentionned on the port page (see remarks's section), after being disconnected from battery for a long time (2 or 3 days) the player wouldn't start anymore. After connecting it to the computer it start again and after being unplugged it showed the message: "firmware succefully updated" allthrough I didn't put any firmware files on its root.
It seems like a saved-firmware-automatically-recovered-mode to me... but again I'm just starting about all those stuff, what do you think about it?
Title: Re: Sansa Fuze+
Post by: pamaury on December 02, 2010, 05:41:26 AM
Hello,

Indeed the manual mentions this reset (we should have had a look at it before !) but what you describe is a bit strange. So perhaps there is a firmware in ROM or an hidden part of the nand of whathever.

I'm trying to disassemble what looks like the boot code so perhaps I'll find something.
Title: Re: Sansa Fuze+
Post by: metaphys on December 02, 2010, 07:27:08 AM
Hello,

If its helps You can find different version of the firmware on sansa forum (go http://forums.sandisk.com/t5/Fuze/bd-p/Fuzeplus and look older pages), so that you could actually compare them to each other? Or perhaps you already did? or pehraps it's useless?
(I nearly don't understand what your are doing and the page you made about the firmware is like foreign language to me - by the way is there anything I could read to learn about it and being able to understand it?)
Title: Re: Sansa Fuze+
Post by: casainho on December 02, 2010, 07:55:46 PM
We at Lyre project are using a Open Source board/hardware using i.MX233 just like Sansa Fuze+ AND we are starting the port of Rockbox.

We have already working code for blink and LED on our board and initialise and test the 32MBytes SDRAM -- on our SVN. i.MX233 is booting from uSDCard.

We are using JTAG to debug the firmware. Read more here: http://lyre.sourceforge.net/?q=blog
Title: Re: Sansa Fuze+
Post by: metaphys on December 04, 2010, 06:44:57 AM
oh I didn't get that i.MX233 and STMP37XX where the same. So I've just add its datasheet to the port page
Title: Re: Sansa Fuze+
Post by: casainho on December 04, 2010, 07:30:34 AM
oh I didn't get that i.MX233 and STMP37XX where the same. So I've just add its datasheet to the port page

Yeah. Luckily, knowing this, everyone can develop the Rockbox port code for Sansa Fuse+, using Lyre project i.MX233 board, or Chumby hacker board. On both boards, there are available JTAG for debug/run program from SDRAM, which boost of 1000X for development.

There are examples codes for i.Mx233, there are Linux and Android port for it :-)
Title: Re: Sansa Fuze+
Post by: pamaury on December 26, 2010, 05:16:13 AM
Hi,
I'm still working on the Fuze+ firmware. Since I had a little disk problem I had to restart everything from scratch so I lost quite a bit of time. I will thus stick with my current firmware revision because it shouldn't change anything for the hardware and I would have to restart from scratch again.
Title: Re: Sansa Fuze+
Post by: pamaury on January 19, 2011, 12:34:19 PM
For those who are interested, I'm still working on the disassembly of the OF. There is still lot of work to be done but I now have a good knowledge of the threading/interrupt code. And I hope to be able to get gather some hardware information soon.
I already found pretty much everything which is LCD related but the OF has a number of init paths for it and I don't really know which one is selected for now.
As a side note, I also have found some code for the debug uart, so it's well possible that there are some uart pins somewhere on the board.
Title: Re: Sansa Fuze+
Post by: lugu on February 09, 2011, 09:46:07 AM
Hi,

Does anyone have information regarding JTAG and sansa fuze+?

Many thanks!
Title: Re: Sansa Fuze+
Post by: pamaury on February 11, 2011, 11:36:03 AM
Hi,
I personally don't have any information about it. But I'm in the process of (finally !) buying a Fuze+. I hope I'll be able to start a new port based on the disassembly I've done (and not finished). However, the OF seems to have support for ETM (by configuring some ports for it when something goes bad) so perhaps there are some debugging pins somewhere on the PCB.
Title: Re: Sansa Fuze+
Post by: metaphys on February 15, 2011, 01:10:11 PM
Is there a quick way I could test this ?
Title: Re: Sansa Fuze+
Post by: pamaury on March 06, 2011, 05:39:43 AM
Hello,
I finally have a fuze+ \o/ I've tried various things but I can't find a recovery mode for know.
I'm still disassembling the firmware because I need to understand how the booting process works as this is not exactly clear.

I could try to replace what I believe is the user part of the firmware and keep what I believe to be the usb/msc one but I don't want to take any useless risks for now.
Title: Re: Sansa Fuze+
Post by: yelped on March 06, 2011, 06:14:20 PM
Thanks for all the hard work you're putting in to the port.
Title: Re: Sansa Fuze+
Post by: metaphys on March 08, 2011, 10:42:31 AM
Following what I've said about this funny behaviour of the fuze+ recovering automatically, I've tried to open it again. There is no possibility to disconnect the battery from it (unless cutting). So I supposed I must have accidentaly putted in contact some part of it leading to this automatic recovery. It might be something like that :
http://www.rockbox.org/wiki/SansaAMSUnbrick

It would be good to have someone that could lead us in how those were found  ::) assuming there is any method for it  ::)
Of course it would not be an ideal solution but it will at least assure us that we can go pretty bad keeping the possibility to recover

thanks for your work anyway...

Post Merge: March 09, 2011, 09:20:31 AM
So I've manage to reproduce the auto update behavior but only once and every other try failed... There is definitively a way to do so but no idea how! Anyway I never managed to access the flash memory directly through USB.
Furthermore after the end of this upgrade process the firmware version is the last installed one, any setting are reseted to default ones. So I suppose some save is systematically made on every upgrade. :-\ not sure about how to go further...
Title: Re: Sansa Fuze+
Post by: haim on March 13, 2011, 05:50:09 AM
I want to buy the FUZE+, what do you say? How long will it take to get an unstable version of Rockbox for this player? (Estimated)
Title: Re: Sansa Fuze+
Post by: [Saint] on March 13, 2011, 08:10:27 AM
I want to buy the FUZE+, what do you say? How long will it take to get an unstable version of Rockbox for this player? (Estimated)


Estimated: "Anywhere from some time in the future, to never"

Estimates simply aren't given, as the future cannot be predicted.
Developers work on what they want to, when they want to, in an entirely volunteer fashion.
There is also no telling what road-blocks may be hit along the way.

For now, only a very basic disassembly has been started to my knowledge.



[St.]
Title: Re: Sansa Fuze+
Post by: haim on March 13, 2011, 08:15:55 AM
Thanks, I just wanted to know if by progress today it looks it will happen this year, of course no one would have to do anything, and I thank you for all the work you are doing
Title: Re: Sansa Fuze+
Post by: pamaury on March 13, 2011, 08:59:25 AM
Hello,
I'm giving regular updates so here is one. I'm still working on disassembly because I still don't know how exactly the fuze+ is booting but I now have a theory. Apparently, the firmware file is split into 3 parts: the first part is the actual boot part which is probably written to the flash using the format describe in the datasheet. The two other parts are probably written somewhere else and manually loaded by the boot code.
The boot code seems to have three modes: normal mode (boots "play"), usb mode (boot "host") and update mode where it reads the firmware.sb file written at the root and update the flash content with it.

I still need to confirm this but if it were the case, it means we could simple replace the "play" part and have a failsafe mechanism since the host is able to expose the filesystem through usb. I'm also unsure about the checks done to authenticate the firmware updates. I know for sure that 1.32 only accept upgrades and not downgrades.

Sorry for all this taking a long time but the code is really complicated, it is obviously not a simple OS written for the fuze+ but more a full blown RTOS. I really have no estimate for now.
Title: Re: Sansa Fuze+
Post by: pamaury on April 04, 2011, 04:51:29 AM
Hello,
I have made some big progress in the analysis of the booting process. I'm now sure sure that the last booting stage is doing something of the firmware.sb file. I've found some cryptographic primitives which suggest that it's somehow checking that the file is valid and probably writing some part of it to the flash. I'm still not done but I'm getting closer.
As suggested in the Wiki, the access to the flash is done through a SD interface which is a good point since there is no FTL and it acts as a block device. It's still unclear to me how the screen works although I've reverse engineered most of code, it's a insane mixture of code, sometimes using GPIOs directly, sometimes using the PIX IP block, without the documentation it might be quite hard to make it work.

I still have no documentation for the touchpad. The photos show it's Synaptics chip but I can't find any datasheet, any help is welcome :)
Title: Re: Sansa Fuze+
Post by: casainho on April 04, 2011, 05:01:43 AM
I am looking forward for your work/advances, since I can't for now have a working code for C startup file for interrupts -- I need a working interrupt code for have Rockbox kernel tick working.

Good luck!
Title: Re: Sansa Fuze+
Post by: pamaury on April 04, 2011, 05:47:00 AM
Setting up interrupts for a tick timer shouldn't be too difficult, basically you need to:
You just need to be careful because on this chip to enable a interrupt there are zillions of things to enable (typically you need to enable the irq AND enable to irq to interrupt path). And you perhaps need to setup a clock path somewhere (the timrot uses the crystal osc I think but I don't have the doc right now).
Title: Re: Sansa Fuze+
Post by: casainho on April 04, 2011, 06:02:07 AM
Setting up interrupts for a tick timer shouldn't be too difficult, basically you need to:
  • Enable icoll block
  • Setup interrupt vector base
  • Enable timer interrupt
  • Enable timrot block
  • Setup a timer
  • Enable timer irq
You just need to be careful because on this chip to enable a interrupt there are zillions of things to enable (typically you need to enable the irq AND enable to irq to interrupt path). And you perhaps need to setup a clock path somewhere (the timrot uses the crystal osc I think but I don't have the doc right now).

I also need the assembly C startup code, for setup correct interrupt stacks, etc...
Title: Re: Sansa Fuze+
Post by: yelped on April 05, 2011, 05:52:34 PM
Pamaury, can any of these documents help you on the touchpad?
http://www.synaptics.com/developers/archive
Title: Re: Sansa Fuze+
Post by: pamaury on April 06, 2011, 04:06:50 AM
Hello,
I've not yet reverse engineered any code on the touchpad but these document can prove useful, thanks. I'll tell you when'll I'll come to it but this is not my priority.
Title: Re: Sansa Fuze+
Post by: pamaury on April 08, 2011, 04:17:19 PM
Hi all,
although I haven't done much progress I have some great news: I found the USB Recovery mode ! It's all explained on the wiki page SansaFuzePlus but it would be nice if some could confirm:
The device will appear as a HID device from Sigmatel

The VID/PID is coherent with the datasheet unfortunately, it seems to use some HID reports with commands, and the commands are not listed in the datasheet ("A list of USB bootloader commands is available upon request.").
I contacted Freescale to get some information, we'll see if I get an answer. Unfortunately, I couldn't find anything useful about it on Google so ideas are welcome :)
Title: Re: Sansa Fuze+
Post by: pamaury on April 09, 2011, 01:13:37 PM
I figured out that there was a Windows program call MfgTools provided by freescale to download a file to the RAM using this recovery mode. I had a look at the protocol and it seems quite easy to reproduce it, TheLemonMan is on the case. This way I managed to download some code as a proof of concept since one simply need to download a normal sb file.
Title: Re: Sansa Fuze+
Post by: metaphys on April 10, 2011, 05:02:19 AM
Hi all,
although I haven't done much progress I have some great news: I found the USB Recovery mode ! It's all explained on the wiki page SansaFuzePlus but it would be nice if some could confirm:
  • Turn off the device
  • Hold down volume up and while doing so, plug in usb
The device will appear as a HID device from Sigmatel

The VID/PID is coherent with the datasheet unfortunately, it seems to use some HID reports with commands, and the commands are not listed in the datasheet ("A list of USB bootloader commands is available upon request.").
I contacted Freescale to get some information, we'll see if I get an answer. Unfortunately, I couldn't find anything useful about it on Google so ideas are welcome :)

I can confirm it even with last firmware:
Quote
[16553.669075] usb 1-1: new high speed USB device using ehci_hcd and address 4
[16553.783791] usb 1-1: New USB device found, idVendor=066f, idProduct=3780
[16553.783799] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[16553.783806] usb 1-1: Product: ROM Recovery
[16553.783810] usb 1-1: Manufacturer: Sigmatel, Inc.
[16554.210234] generic-usb: probe of 0003:066F:3780.0001 failed with error -22
[16554.210261] usbcore: registered new interface driver usbhid
[16554.210264] usbhid: USB HID core driver

Anyway did you saw that :
http://mympxplayer.org/sigmatel-recovery-guide-updated-vt8150.html ?
Title: Re: Sansa Fuze+
Post by: pamaury on April 12, 2011, 05:10:20 AM
The link you provide apply to older versions of the stmp chips (35xx and 36xx iirc) which used a different recovery mechanism (basically a DFU mode and a much simpler sb file format).

Anyway, I got an answer from Freescale and it was the same as TheLemonMan got: the bootloader commands are under a NDA. Anyway, both of us managed to reverse engineer the part of the protocol we needed, here is a link to the short program to download some code on the device:
https://github.com/pamaury/pa-tools/tree/master/fuze+/recovery_hid (https://github.com/pamaury/pa-tools/tree/master/fuze+/recovery_hid)
There might be a conflict with usbhid so one perhaps to unload it (a problem TheLemonMan encountered).
Here is the link to his code (and there quick description of the protocol):
https://github.com/LemonBoy/OpenBLTC (https://github.com/LemonBoy/OpenBLTC)
There might a subtle difference here because he uses a reset to end the transfer and I wait for the interrupt transfer on my side. Since we do not have the same device and the same chip (3700 vs 3780), there might a difference here too.
Title: Re: Sansa Fuze+
Post by: pamaury on April 18, 2011, 05:44:03 AM
I didn't have much time last week but this week-end I fixed some bugs in sbinfo (now called sbtoelf) and wrote an open-source version of elftosb. All this can be found in the SVN.
Title: Re: Sansa Fuze+
Post by: pamaury on April 19, 2011, 09:38:46 AM
Since I've begun writing some code for the recovery mode of the fuze+, I thought it would be good to publish it somewhere before it's ready. Everything can be found here: https://github.com/pamaury/pa-tools/tree/master/fuze+
The recovery_hid is the tool to download the sb file to the device. To build the sb file, one need elftosb, the current Makefile uses the syntax of the one found in Rockbox trunk but with minor tweaks it can be made to use Freescale's one.
Title: Re: Sansa Fuze+
Post by: pamaury on April 23, 2011, 03:30:38 PM
Hello,
I've got some good news: I've managed to make USB work (wasn't too hard) so using another tool in my repo (usb_debug) I can output debug strings ! I've started to write some code for the LCD and it appears that there might be two models available out there. Unfortunately, my current code currently doesn't work, the LCD is not responding :( I hope to have LCD working soon.
Title: Re: Sansa Fuze+
Post by: pamaury on April 24, 2011, 07:45:21 AM
Good,
I've finally reverse engineered the whole lcd init/enable/disable sequence for one model and I know how to tweak backlight more or less. Now I'm wondering if there are actually are two kinds of LCD in the nature. Producing the binary for the recovery mode is not exactly trivial so I can provide the binary. Do people out there are able to build the recovery_hid tool in my repository (https://github.com/pamaury/pa-tools/tree/master/fuze+/recovery_hid, linux only) and are willing to test some binary to see if the LCD is of the same kind as me ?
Title: Re: Sansa Fuze+
Post by: metaphys on April 24, 2011, 08:11:27 AM
Yes i'm on a debian 64 bits and I could try this if you explain how...  ;)

I've tried a basic 'make' & 'make install' but it doesn't seems to be that simple...  ;D

edit : ok  I have to execute Makefile... and I need a few dev lib... Is it suppose to be cross-compiling already? Do I already need a whole cross compiling environment?
Title: Re: Sansa Fuze+
Post by: pamaury on April 24, 2011, 08:23:23 AM
It's rather simple: you "make" into the recovery_hid (there is not "make install" target) and it should produce a recovery_hid tool (you will need libusb-dev version 1.0), then download this file: http://amaury.pouly.free.fr/recovery.sb (http://amaury.pouly.free.fr/recovery.sb) and put it in the same directory. Then plug the fuze+ in recovery mode (holding volume up) and run as root:
recovery_hid 1024 recovery.sb

EDIT: you don't need a cross compiler, the recovery_hid is a pure host tool. You only need a cross compiler if you want to build recovery.sb yourself
EDIT2: to check that the code is actually working (in case the lcd doesn't light), you can use the usb_debug tool in my repository ("make" and then run it as root), it will output the debug message logged by the device
Title: Re: Sansa Fuze+
Post by: metaphys on April 24, 2011, 08:34:05 AM
WAAAOOOHH!  ;D

As I type de command the screen of the fuze+ turn white, then it disconected itself and go back to mass storage device mode

Is it what was expected?

Edit ok i will try debug now
Edit2 : wait it did light up, do you still need debug?
Title: Re: Sansa Fuze+
Post by: pamaury on April 24, 2011, 08:36:40 AM
Yes, the screen turns on and off two types (when off with backlight on, that's garbage) and after 10 sec it turns off (and reboot if still plugged). Ok so it means you have the same lcd controller as mine :) Thanks for testing ! I still to work a bit to know how to display pixels but this is nearly it.
Title: Re: Sansa Fuze+
Post by: pamaury on April 24, 2011, 01:39:15 PM
I finally got the LCD working, that's wasn't too easy finally but it works.
I took a picture http://amaury.pouly.free.fr/SSL22450.JPG (http://amaury.pouly.free.fr/SSL22450.JPG)but it looks much more nicer on the device :)
There are still a few things I nice to understand, I think the LCD supports partial blits but I'll investigate later.
Title: Re: Sansa Fuze+
Post by: metaphys on April 25, 2011, 04:11:57 AM
nice indeed  ;D
Let me know if you need some more test...
Title: Re: Sansa Fuze+
Post by: metaphys on May 06, 2011, 06:15:20 AM
I'm thinking about leaving a message asking for tester on the sansa forum dedicated to the Fuze+ (especially about this lcd other kind issue. Obviously we are both french and althrough I'm living in austria, it's not so suprising that we got the same kind... it's still EU)
But I wonder if this would please the sansa team ...  ??? Any history about that? Is there any policy principle when dealing with official company and Rockbox?
Title: Re: Sansa Fuze+
Post by: pamaury on May 06, 2011, 06:35:56 AM
No idea, I think I saw some comments asking whether Rockbox would be supported in the Sansa forums :) But moderators could well delete that message.
When I'll have time I'll reverse engineer the second sequence and implement it. By carefully checking, it should be ok and if it's not, people will hopefully post to the bug tracker.
By the way you're right that the second type of screen might have to do with the location.
Title: Re: Sansa Fuze+
Post by: metaphys on May 06, 2011, 07:25:25 AM
ok so I guess there is no urge for tester about this other lcd kind just right now...
Title: Re: Sansa Fuze+
Post by: Molot on May 09, 2011, 05:30:19 AM
I want to buy Fuze+. But I will do that only if one of the following is meet:
1) Rockbox will be available quite soon, at least in an unstable version.
2) There will be any way for me to contribute to making rockbox available.
Sadly, I hardly know anything about microcontrollers. I can debug, can write in C, can test. Can learn coding. Can try to buy particular subversion of the device.
So should I buy it?
Title: Re: Sansa Fuze+
Post by: [Saint] on May 09, 2011, 05:38:21 AM
At this stage I probably still wouldn't buy a Fuze+ in the hope that Rockbox might one day be available for it.
No one can, or ever will, give a projected release time as there are just too many variables.
It could look promising today, and tomorrow a roadblock could be found that completely stalls development.

Also, what is your definition of "quite soon"?

Quite soon, relative to some other ports starting to unstable, could easily be a year or more.


[St.]
Title: Re: Sansa Fuze+
Post by: Molot on May 09, 2011, 05:58:56 AM
I was not expecting any promises. Sometimes a project needs just few minor tricks to get basic functionality - I only wanted to know if it's the case. But I really do not expect it is (sorry if I sounded like I was - language barrier, it seems), so there was point 2 - is this work at a point I might be in any way useful? Or get useful in a month or two?
Title: Re: Sansa Fuze+
Post by: pamaury on May 09, 2011, 06:08:54 AM
From now on it's hard to tell. LCD is working which is good point, USB can easily made to work, the physical keys work. The storage code is standard SD and the on-disk layout is documented so normally it shouldn't be difficult to get it work. The unknowns are still:
The sad point is that I will not have too much free time starting from mid-may until the beginning of June (except for DevCon), after that I'll have much more time I hope.
Title: Re: Sansa Fuze+
Post by: pamaury on May 09, 2011, 03:44:55 PM
I have some news regarding the touchpad code. I think it uses the RMI protocol from Synpatics. On there website one can find two specification: http://www.synaptics.com/developers/manuals
But on the internet there is another difference PDF ! I still can't tell what is the difference (probably more device types). I'll try to write some code to read the interesting registers.

EDIT:
I made some tests and it's indeed a RMI device. It reports itself as "1533", RMI version 0.1 but rmi specification 3 matches.
It has one function: 2-D TouchPad sensor (0x10) with 3 sensors. It's quite late so I did not dumped all the registers yet to see its capabilities.

A funny fact: the fuze+ OF has both a software and hardware implementation of i2c but it uses the software one with the hardware pins! I don't exactly know why but I myself used the generic rockbox i2c software implementation since it's not worth using the hardware in this case.
Title: Re: Sansa Fuze+
Post by: pamaury on May 10, 2011, 12:12:13 PM
When reverse engineering the LCD code for the second kind of lcd, it became clear to me that the two share a pretty close register set. Looking on the internet, I found that Sitronix produces a ST7783 lcd controller, a datasheet for the ST7781 is available and matches. So I guess the two LCD kinds are:
Title: Re: Sansa Fuze+
Post by: Molot on May 11, 2011, 05:26:23 AM
Fast questions:
1) Do you own both types of device?
2) If not, would you get any benefit if I'd buy the other kind and test stuff for you?
3) If so, how can I tell in the shop what kind is it?

Last AND least - which one is better? Both seems to have the same resolution and up to 18bit color, if I found right datasheets.

(Yep, I am willing to help however I can with my very limited abilities)
Title: Re: Sansa Fuze+
Post by: pamaury on May 11, 2011, 05:32:20 AM
I only own one Fuze+ and as suggested by metaphys previously in the thread, this might be a regional choice. Currently we don't even know if there exists Fuze+ shipped with the 9325 kind LCDs, only the OF analysis suggests it :) Furthermore you probably can't tell the difference except by tearing down the device (and even then it could not be obvious). I think both are equivalent.
Title: Re: Sansa Fuze+
Post by: Molot on May 11, 2011, 05:39:59 AM
Most regional choices I've encountered in electronics was like:
1) USA & Canada
2) European Union
3) Rest of the world
With just minor tricks around.
I'm in the European Union. Maybe it's worth checking... I'll try to investigate. I kinda doubt I'll find out, but no harm in trying.

Addendum:
I have mailed Sandisk technical support and got answer. They assured that there are no regional differences between currently manufactured players, parts used are the same all around the world, especially there are no technical differences between America and European Union products, despite different warranty terms & periods. Spare parts are told to be the same all over the world.
However they did not say a thing about changes in time and I don't know how to ask this to get answer ;) I couldn't just go to them saying "hey, help me to crack your device!", you know.

As I see it now, the only way to test the "time" option is to obtain old and current original firmware and see if there are two drivers in both. If so, then Sandisk is not perfectly honest with us and there was always some kind of variants. If not, then one is just later. In the second case we'll need to see if you have the older version. In that case I might buy new one and hope to have the screen you don't, and test stuff for you.
Title: Re: Sansa Fuze+
Post by: pamaury on May 11, 2011, 05:47:32 PM
I think the safest option is wait and see. The code is there so if it doesn't work people will show up and say "hey it doesn't work!" :D
On the good side, I've played a bit with the touchpad and it should be matter of a few hours to have something basically working. I let the most motivated read the datasheet but basically the touchpad handle "gestures" itself: tap, double tap, tap and slide, ... So one can let the device do the work and we can just translate those event and map them to virtual keys like left, right, up, down, enter, return and play/pause. Later on, there will be some work to handle slide as a button repeat but the most important is to have the device usable.
The code is in the SVN so if you have a fuze+, feel free to play with! I'll try to implement a nicer debug screen soon. They I'll move on to the storage part.
Title: Re: Sansa Fuze+
Post by: metaphys on May 12, 2011, 10:09:05 AM
Is it the files on the same location as for the LCD's test or is it somewhere else...
Yeah I feel quite stupid on this one...  ::)
Title: Re: Sansa Fuze+
Post by: pamaury on May 12, 2011, 10:17:57 AM
No, I committed the code to the SVN so if it's not the case you need to get the rockbox code using SVN, build the fuze+ bootloader and then use some tools to download the code to the device:
http://www.rockbox.org/wiki/HowToCompile
http://www.rockbox.org/wiki/SansaFuzePlusPort
I'll try to provide a binary if it's too much work but I can't do it on a regular fashion.
Title: Re: Sansa Fuze+
Post by: metaphys on May 12, 2011, 10:20:02 AM
Ok, wait I will try to find my way through those link - if I can't, I will tell...  ;)
Title: Re: Sansa Fuze+
Post by: kerobaros on May 13, 2011, 03:25:55 AM
Currently compiling the toolchain to test this out. Question: does installing your bootloader to the Fuze+ overwrite the Sandisk bootloader? Is there a way to boot the original firmware again afterwards?
Title: Re: Sansa Fuze+
Post by: pamaury on May 13, 2011, 04:59:28 AM
When booting in recovery mode, nothing is written to disk, your device will boot normally afterwards. The recovery mode is not an "installation", it's really just a way to run some binary without installing anything.
Title: Re: Sansa Fuze+
Post by: kerobaros on May 13, 2011, 05:21:17 AM
Okay, I have compiled a bootloader.elf, and am trying to pack it into the .sb file following the instructions on the wiki. However, elf2sb segfaults every time I run it.

From my dmesg:
Quote
[ 3185.897354] elftosb[13167]: segfault at 30303044 ip 0804cb60 sp bf8db8b8 error 4 in elftosb[8048000+7000]
[ 3206.972947] elftosb[13229]: segfault at 30303044 ip 0804cb60 sp bfffbf48 error 4 in elftosb[8048000+7000]
[ 3227.578542] elftosb[13292]: segfault at 30303044 ip 0804cb60 sp bfe53768 error 4 in elftosb[8048000+7000]
[ 3279.296148] elftosb[13445]: segfault at 30303044 ip 0804cb60 sp bf90be38 error 4 in elftosb[8048000+7000]

Running Arch Linux x86, compiled the toolchain using the automatic method from the wiki. Help? :D
Title: Re: Sansa Fuze+
Post by: pamaury on May 13, 2011, 05:24:45 AM
Strange,
normally elftosb is compiled in debug mode by default, can you use gdb or valgrind to see where it segfaults ?
If you don't know how to do this or just can't, could you send me both the bootloader.elf file and the elftosb binary ?
Title: Re: Sansa Fuze+
Post by: kerobaros on May 13, 2011, 05:28:13 AM
Quote
(gdb) run bootloader.db fuze+_key_file.txt bootloader.sb
Starting program: /home/kerobaros/fuze/elftosb bootloader.db fuze+_key_file.txt bootloader.sb

Program received signal SIGSEGV, Segmentation fault.
0x0804cb60 in elf_get_nr_sections (params=0x8050018) at elf.c:467
467           sec = sec->next;

Does that help at all? (Also: I didn't know how to use gdb, but apparently it's time to learn!)
Title: Re: Sansa Fuze+
Post by: pamaury on May 13, 2011, 05:47:12 AM
That's really strange, I don't how it could segfault at this point.
The simplest solution is that you send me all the related files (the elf files which come from sbtoelf and bootloader.elf) since it will take you lots of time to debug it if you don't know how the program works.
Title: Re: Sansa Fuze+
Post by: kerobaros on May 13, 2011, 05:50:13 AM
Alright. I sent you a message on IRC; could we discuss this there?
Title: Re: Sansa Fuze+
Post by: pamaury on May 13, 2011, 07:14:23 AM
I fixed the bug, there was an uninitialized structure in the code. I think you can retry now :)
Title: Re: Sansa Fuze+
Post by: metaphys on May 13, 2011, 02:00:42 PM
Ok it's working. Should we test anything specific? For what I can see REL and Abs values are correct and there is also a value changing when pushing volume key
Title: Re: Sansa Fuze+
Post by: pamaury on May 13, 2011, 02:02:43 PM
I have committed somes changse, now there is a graphical feedback! For now that's just for fun / testing that the code works on all devices. I will now move on to the storage code.
Title: Re: Sansa Fuze+
Post by: kerobaros on May 13, 2011, 02:34:53 PM
Just played with your test code for a few minutes. So nice to see something on that screen that isn't the Sandisk firmware! Works perfectly, pamaury, keep up the good work.
Title: Re: Sansa Fuze+
Post by: metaphys on May 14, 2011, 09:46:44 AM
Very nice indeed  ;D . On my device the upper part of the red square is unreachable (like 0,5 cm) And on the bottom part the cursor go out of the screen... Don't know if this it important, so I prefer to mention it...

Great job anyway!  :D
Title: Re: Sansa Fuze+
Post by: pamaury on May 14, 2011, 11:39:14 AM
So the red rectangle fits in the screen but the cursor goes out of the rectangle ?
Normally that's impossible :-/ Can you copy the values displayed on the screen (and in particular x_max and y_max) ?
Title: Re: Sansa Fuze+
Post by: metaphys on May 14, 2011, 01:05:14 PM
RMI: id=1533 p=B7 s=E
xmax=3009 ymax=1974 res=82

I retested it precisly:
I unable to exced about 1700 (record 1696) on the vertical axe (by wich value I'm already at the end of the touchpad).
between 50-70 the point disapear from screen (througt not reaching the red line) but I see it's still tracked down because of the vertical value that are still droping to nearly zero
By the way by the time I wrote I've tested again and now this does not happen anymore (for the bottom part) but unstead, I reached the end of touchpad (no more tracking of value) between value 80-100.
I'm the one who take his device appart, so pehraps I just broked it partly? I does feel any problem when using it anyway...

EDIT:
Altogether I would say the cursor covert pretty well the whole surface except for the upper part of the red rectangle
Title: Re: Sansa Fuze+
Post by: pamaury on May 14, 2011, 01:11:56 PM
I don't reach the extreme values either but normally the cursor CAN'T escape the rectangle by design (the value reported are always below the maximum) so I found it a bit strange :)
Title: Re: Sansa Fuze+
Post by: metaphys on May 14, 2011, 01:16:02 PM
no no it does not! But being all the way down and disapearing leave the impression it's gone out of the screen... Plus the fact value are still tracked down (but I can't reproduce this right now...)
Title: Re: Sansa Fuze+
Post by: pamaury on June 01, 2011, 04:27:34 AM
Hello,
just a quick post to say that I'm still alive but as I said previously, I don't have much time right now. I've tried to make the storage work (it's SD based) but without success for now...Perhaps I'll make some progress at the devcon next week-end :)
Title: Re: Sansa Fuze+
Post by: Frank9321 on June 08, 2011, 09:44:13 AM
Hi,
I just bought a Fuze+ in order to replace my old e200 (running rockbox) that broke some weeks ago. I received the sansa today and I tested it. The firmware isn't that good so it would be very interesting to be able to port rockbox to the sansa+. Actually, I'm preparing for an exam (the french BAC) but after that, after the 22th of June,  I will be free. I know a bit C and I do program microcontrolers (ATMELs AVR) so I hope that I will be able to contribute a bit. I don't know anything about ASM and all that but I do know how µC I/O works, etc...

Meanwhile, I hope that you will be able to learn more about the fuze+.

Cheers,
Title: Re: Sansa Fuze+
Post by: pamaury on June 10, 2011, 09:54:37 AM
Hi,
we already have an ongoing port, the code is in the SVN and there is info on the wiki on how to compile/build everything. Everyone is welcome to help of course :) If you are interested, you might have a try at making the sound work, although I'm unsure if it needs info from the OF or not. But for now, everything is a bit difficult since we don't have the storage working !

I'm still unable to make the internal (or external) SD/MMC work but I have make some progress anyway. Since the bootloader of the fuze+ is in an i2c eeprom on the board, I wrote some hacky code to read it and it seems to work. I'll try to dump it all and study it, this way I could understand what I'm doing wrong with the SSP/SD/MMC code.
Title: Re: Sansa Fuze+
Post by: pamaury on June 10, 2011, 06:51:00 PM
Ok, I've managed to dump the rom. It uses the sb format too with a zero key just like the firmware. It consists in two parts:
I don't know yet what the code does.

I old fiddle a bit with the USB and it works in the bootloader even though it requires a few hack right now because I haven't written the code to correctly detect insertion.
Title: Re: Sansa Fuze+
Post by: pamaury on June 17, 2011, 05:23:54 PM
I've got some good news. After a bit of tweaking I finally managed to make the internal eMMC flash to work. I can reset it, do the power up sequence and read the CID so now it should be really easy to read/write from it. I will commit the commit as soon as possible.

EDIT:
I can now read the internal flash but I'm a bit puzzled by the content it. It has a MBR but it looks strange:
- all partition (except one) are of FAT12 type (even though one has size of 7.9G approx)
- one partition has type 'S' to be booted by the ROM but the starting sector doesn't match the actual data (there is an offset of 0x800 bytes of so...)
That's all very weird :-/
Title: Re: Sansa Fuze+
Post by: pamaury on June 30, 2011, 04:39:31 PM
Hello,
I finally got the storage working, so SSP, DMA and MMC is working, and the code does the necessary stuff to try to find the good partition so hopefully the bootloader will now try to find a rockbox firmware in the internal flash.
As the OF uses some weird layout, I would appreciate some testing on fuze+ with different internal flash size. Mine has 8G so testing it with 4G and 16G would be really nice.

WARNING: I change the bootloader.db file to include a third stage of the original OF, please see the change on the SansaFuzePusPort wiki page; the code will NOT work without it, it's related to voltage and frequency setting.

I need to think about where exactly I will put the bootloader: replacing the OF seems a bit aggressive and even though I could aggregate both in one file, any OF update would destroy the bootloader. There is a i2c chip on the device but it's only 64kb large and I don't know if it's write protected. Having support for dual-boot would be really nice but non-trivial it seems. Any idea is welcome :)
Note that somehow the OF manages to do it but I don't understand how and since I don't really have a proper documentation of the sb format, I'm stuck.
Title: Re: Sansa Fuze+
Post by: danger355 on July 01, 2011, 06:59:27 AM
I would appreciate some testing on fuze+ with different internal flash size. Mine has 8G so testing it with 4G and 16G would be really nice.

Hi,

I've been following this post for a while now and noticed all the progress being made (thank you!). I wanted to be ready for when if this port became usable so I actually ordered a 16G and it's scheduled to be delivered mid next week, so I'm willing to test it out.

This will be my first time testing something so early in development, but I do have plenty of other experience in using non-stock firmwares on other small electronics - my last two phones and my nook color all run custom Android ROM's and I had an iRiver HP-120 that had rockbox on it. So don't worry, I know the risks and am willing to ignore them :)

Once I get it in, I'll run through the wiki and I guess I'll just post if I run into any snags?

Thanks, and cheers!
Title: Re: Sansa Fuze+
Post by: metaphys on July 02, 2011, 02:30:01 AM
Hello Pamaury,

My device is 16GB and I will test it as soon as possible. For the moment I'm travelling around so I'll will not be able to do so before a few days.
Title: Re: Sansa Fuze+
Post by: pamaury on July 04, 2011, 07:17:53 AM
Hi,
one more note about dual-booting. I finally found how the OF booted by disassembling the boot ROM. I now see a way of dual-booting provided that the i2c epprom is not write protected.

The simplest way would be to put the bootloader in the i2c chip (so 64kb at most) which would have three sections:
The only annoying point here is that the bootloader would be limited to 64kb which will require to rewrite to the OF init code for EMI (memory), voltages and frequencies but it shouldn't be a major problem.
Title: Re: Sansa Fuze+
Post by: pamaury on July 09, 2011, 01:31:10 PM
Hum, in fact I made an error while reading: the i2c eeprom chip is only 8kb large :(
This means that dual-booting will be a little bit more tricky than expected.

On the positive side, I found out the pins used by the FM radio chip which is a si7403 as expected. It seems that it is RDS capable but rockbox doesn't handle this yet. I'm now focusing on the audio part: recording and playing.
Title: Re: Sansa Fuze+
Post by: danger355 on July 10, 2011, 03:37:41 PM
hi,

i'm in the process of building the bootloader, and keep running into an issue with the sbtoelf tool.

it seems no matter how i try and run it, i always get a 'command not found' error.

i'm running the code shown here in the SansaFuzePlusPort page after building a regular bootloader using the cross compiler:

Code: [Select]
sbtoelf firmware.sb fuze+_key_file.txt OUT.
from the wiki after the code:

Quote
where the sbtoelf tool can be found in the trunk in utils/sbtools/ along with fuze+_key_file.txt; this should produce lots of output and several files:

does this mean that all three files (the sbtoelf.c tool, the firmware, and the fuze+_key_file) need to be in the same file folder? I've tried that and i get the error above.

any help would be appreciated. thanks.
Title: Re: Sansa Fuze+
Post by: saratoga on July 10, 2011, 04:19:30 PM
it seems no matter how i try and run it, i always get a 'command not found' error.

Sounds like you didn't build sbtoelf.  Theres a makefile in utils/sbtools.  That will build the tool for your system, then you can run it like any other executable.

does this mean that all three files (the sbtoelf.c tool, the firmware, and the fuze+_key_file) need to be in the same file folder? I've tried that and i get the error above.

Are you familiar with command line programs?  Generally nothing ever has to be in any particular folder provided you have the right paths.  Once you build the executable, you can run it with no arguments to see what inputs it takes:

Code: [Select]
mike@biosgroup-desktop:~/rockbox/codeclib/utils/sbtools$ ./sbtoelf
Usage: ./sbtoelf <firmware> <key file> [<out prefix>]

So the actual folder locations shouldn't matter so long as you give correct paths for each file. 

Title: Re: Sansa Fuze+
Post by: danger355 on July 10, 2011, 05:42:04 PM
Sounds like you didn't build sbtoelf.  Theres a makefile in utils/sbtools.  That will build the tool for your system, then you can run it like any other executable.
there is already an 'sbtoelf.c' in the folder. is there another sbtoelf file i need? by 'build', do you mean use the make command? i tried that too and i get the error "*** No rule to make target `sbtoelf.c', needed by `sbtoelf'.  Stop."

Are you familiar with command line programs?  Generally nothing ever has to be in any particular folder provided you have the right paths.  Once you build the executable, you can run it with no arguments to see what inputs it takes:
not intimately familiar, but i can usually get by. i've run into a few minor roadblocks so far, but this is the only one i haven't been able to google my way out of. i realize it should work, i just can't see/figure out what i'm doing wrong.
Title: Re: Sansa Fuze+
Post by: saratoga on July 10, 2011, 06:54:25 PM
Sounds like you didn't build sbtoelf.  Theres a makefile in utils/sbtools.  That will build the tool for your system, then you can run it like any other executable.
there is already an 'sbtoelf.c' in the folder. is there another sbtoelf file i need? by 'build', do you mean use the make command? i tried that too and i get the error "*** No rule to make target `sbtoelf.c', needed by `sbtoelf'.  Stop."

The command is "make" with no arguments.  Are you sure you typed that and not "make sbtoelf.c"?  make is a tool for handling dependencies, but it doesn't understand c files so it'll fail if you point it at code. 
Title: Re: Sansa Fuze+
Post by: danger355 on July 10, 2011, 07:48:14 PM
The command is "make" with no arguments.  Are you sure you typed that and not "make sbtoelf.c"?  make is a tool for handling dependencies, but it doesn't understand c files so it'll fail if you point it at code. 

yes i'm sure. i also tried others earlier, glad to know i at least got that right.

Code: [Select]
ubuntu@ubuntu:~$ cd rockbox/utils/sbtools
ubuntu@ubuntu:~/rockbox/utils/sbtools$ make
make: *** No rule to make target `sbtoelf.c', needed by `sbtoelf'.  Stop.
ubuntu@ubuntu:~/rockbox/utils/sbtools$

just to make sure, i've gone as far as creating the bootloader.elf file. there was nothing in the wiki about putting this file in the /rockbox/utils/sbtools directory, so i placed it in a newly created /build-dir (as suggested in the make prompt while creating the bootloader)

is there anything that i missed that i still need to do?
Title: Re: Sansa Fuze+
Post by: pamaury on July 11, 2011, 05:00:40 AM
Hello,
the normal steps to build sbtoelf is to have an up to date svn checkout and to type make in utils/sbtools. You error definitely indicate something wrong; are you sure you have the sbtoelf.c ?
Then you should follow the steps in the wiki SansaFuzePlusPort page, everything is written. The directory in which is happen is not important, a fresh one will do.
Title: Re: Sansa Fuze+
Post by: danger355 on July 11, 2011, 06:03:56 PM
Hello,
the normal steps to build sbtoelf is to have an up to date svn checkout and to type make in utils/sbtools. You error definitely indicate something wrong; are you sure you have the sbtoelf.c ?
Then you should follow the steps in the wiki SansaFuzePlusPort page, everything is written. The directory in which is happen is not important, a fresh one will do.

Hi pamaury,

yes, i definitely have sbtoelf.c in the /sbtools folder. i followed the steps in the wiki, but it's still very possible i did something incorrect, so i'll try starting from scratch soon and see if that changes anything
Title: Re: Sansa Fuze+
Post by: metaphys on July 15, 2011, 05:04:56 AM
@danger355
Starting from scratch can you give the exact sequence of command you type?

@Pamaury
ok I suppose I've build the stuff correctly and transfert it to the device:
Code: [Select]
root@debian:/home/jean-louis/Informatique/Rockboxfuse+/rockbox/build# ../utils/imx_hid_recovery/imx_hid_recovery 1024 bootloader.sb
Transfer size: 1024
ret 0
root@debian:/home/jean-louis/Informatique/Rockboxfuse+/rockbox/build#

But nothing hapen... Screen stay black nothing responding. Same after uplugging it. It stayed not responding for awhile and finally after several attempt repluging it bring the OF control back
for info here the dmesg sequence:
Code: [Select]
[  885.657178] usb 1-2: new high speed USB device using ehci_hcd and address 11
[  885.772049] usb 1-2: New USB device found, idVendor=066f, idProduct=3780
[  885.772058] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  885.772065] usb 1-2: Product: ROM Recovery
[  885.772069] usb 1-2: Manufacturer: Sigmatel, Inc.
[  885.773332] generic-usb: probe of 0003:066F:3780.0004 failed with error -22
[ 1151.536349] usb 1-2: USB disconnect, address 11
[ 1184.911095] usb 1-2: new high speed USB device using ehci_hcd and address 12
[ 1190.021141] usb 1-2: device descriptor read/64, error -71
[ 1195.232065] usb 1-2: device descriptor read/64, error -71
[ 1195.435091] usb 1-2: new high speed USB device using ehci_hcd and address 13
[ 1200.545136] usb 1-2: device descriptor read/64, error -71
[ 1205.756061] usb 1-2: device descriptor read/64, error -71
[ 1205.959102] usb 1-2: new high speed USB device using ehci_hcd and address 14
[ 1209.184143] usb 1-2: device not accepting address 14, error -71
[ 1209.235413] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1215.166156] usb 1-2: new high speed USB device using ehci_hcd and address 16
[ 1220.276168] usb 1-2: device descriptor read/64, error -71
[ 1225.487141] usb 1-2: device descriptor read/64, error -71
[ 1225.690165] usb 1-2: new high speed USB device using ehci_hcd and address 17
[ 1230.800052] usb 1-2: device descriptor read/64, error -71
[ 1233.338240] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1239.412152] usb 1-2: new high speed USB device using ehci_hcd and address 18
[ 1244.522150] usb 1-2: device descriptor read/64, error -71
[ 1249.733077] usb 1-2: device descriptor read/64, error -71
[ 1249.936105] usb 1-2: new high speed USB device using ehci_hcd and address 19
[ 1250.744340] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1261.633078] usb 1-2: new high speed USB device using ehci_hcd and address 20
[ 1266.743069] usb 1-2: device descriptor read/64, error -71
[ 1271.954073] usb 1-2: device descriptor read/64, error -71
[ 1272.157078] usb 1-2: new high speed USB device using ehci_hcd and address 21
[ 1277.267168] usb 1-2: device descriptor read/64, error -71
[ 1282.478151] usb 1-2: device descriptor read/64, error -71
[ 1282.681140] usb 1-2: new high speed USB device using ehci_hcd and address 22
[ 1286.033143] usb 1-2: device not accepting address 22, error -71
[ 1286.084330] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1290.087183] usb 1-2: new high speed USB device using ehci_hcd and address 24
[ 1295.197139] usb 1-2: device descriptor read/64, error -71
[ 1300.408075] usb 1-2: device descriptor read/64, error -71
[ 1300.611121] usb 1-2: new high speed USB device using ehci_hcd and address 25
[ 1305.721057] usb 1-2: device descriptor read/64, error -71
[ 1310.932142] usb 1-2: device descriptor read/64, error -71
[ 1311.135048] usb 1-2: new high speed USB device using ehci_hcd and address 26
[ 1316.541049] usb 1-2: device not accepting address 26, error -71
[ 1316.643103] usb 1-2: new high speed USB device using ehci_hcd and address 27
[ 1322.049060] usb 1-2: device not accepting address 27, error -71
[ 1322.049097] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1323.576058] usb 1-5: new high speed USB device using ehci_hcd and address 28
[ 1328.686082] usb 1-5: device descriptor read/64, error -71
[ 1333.897118] usb 1-5: device descriptor read/64, error -71
[ 1334.100098] usb 1-5: new high speed USB device using ehci_hcd and address 29
[ 1339.210124] usb 1-5: device descriptor read/64, error -71
[ 1343.022333] hub 1-0:1.0: unable to enumerate USB device on port 5
[ 1345.970065] usb 1-5: new high speed USB device using ehci_hcd and address 30
[ 1351.080122] usb 1-5: device descriptor read/64, error -71
[ 1356.291129] usb 1-5: device descriptor read/64, error -71
[ 1356.494118] usb 1-5: new high speed USB device using ehci_hcd and address 31
[ 1361.604119] usb 1-5: device descriptor read/64, error -71
[ 1366.815142] usb 1-5: device descriptor read/64, error -71
[ 1367.018124] usb 1-5: new high speed USB device using ehci_hcd and address 32
[ 1372.424057] usb 1-5: device not accepting address 32, error -71
[ 1372.526073] usb 1-5: new high speed USB device using ehci_hcd and address 33
[ 1377.932139] usb 1-5: device not accepting address 33, error -71
[ 1377.932177] hub 1-0:1.0: unable to enumerate USB device on port 5
[ 1378.174179] usb 4-1: new full speed USB device using uhci_hcd and address 2
[ 1383.286094] usb 4-1: device descriptor read/64, error -71
[ 1388.498142] usb 4-1: device descriptor read/64, error -71
[ 1388.701175] usb 4-1: new full speed USB device using uhci_hcd and address 3
[ 1393.812150] usb 4-1: device descriptor read/64, error -71
[ 1399.023136] usb 4-1: device descriptor read/64, error -71
[ 1399.226156] usb 4-1: new full speed USB device using uhci_hcd and address 4
[ 1404.632075] usb 4-1: device not accepting address 4, error -71
[ 1404.734138] usb 4-1: new full speed USB device using uhci_hcd and address 5
[ 1410.140052] usb 4-1: device not accepting address 5, error -71
[ 1410.140095] hub 4-0:1.0: unable to enumerate USB device on port 1
[ 1482.158176] usb 1-5: new high speed USB device using ehci_hcd and address 34
[ 1482.273176] usb 1-5: New USB device found, idVendor=0781, idProduct=74e0
[ 1482.273184] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 1482.273191] usb 1-5: Product: Sansa Fuze+
[ 1482.273196] usb 1-5: Manufacturer: SanDisk
[ 1482.273200] usb 1-5: SerialNumber: 0000000100001C150002DCDF27F55C15
[ 1482.274204] scsi8 : usb-storage 1-5:1.0
[ 1483.274939] scsi 8:0:0:0: Direct-Access     SanDisk  Sansa Fuze+      0100 PQ: 0 ANSI: 4
[ 1483.275556] scsi 8:0:0:1: Direct-Access     SanDisk  Sansa Fuze+      0100 PQ: 0 ANSI: 4
[ 1483.279931] sd 8:0:0:0: [sdb] 7748864 2048-byte logical blocks: (15.8 GB/14.7 GiB)
[ 1483.280521] sd 8:0:0:0: [sdb] Write Protect is off
[ 1483.280529] sd 8:0:0:0: [sdb] Mode Sense: 3e 00 00 00
[ 1483.285855] sd 8:0:0:0: [sdb] Incomplete mode parameter data
[ 1483.285861] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[ 1483.288148] sd 8:0:0:1: [sdc] Attached SCSI removable disk
[ 1483.292763] sd 8:0:0:0: [sdb] 7748864 2048-byte logical blocks: (15.8 GB/14.7 GiB)
[ 1483.294408] sd 8:0:0:0: [sdb] Incomplete mode parameter data
[ 1483.294413] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[ 1483.295711]  sdb: sdb1
[ 1483.298043] sd 8:0:0:0: [sdb] 7748864 2048-byte logical blocks: (15.8 GB/14.7 GiB)
[ 1483.299414] sd 8:0:0:0: [sdb] Incomplete mode parameter data
[ 1483.299418] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[ 1483.299422] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 1483.727360] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 1561.041434] WARNING! power/level is deprecated; use power/control instead
[ 1561.100383] usb 1-5: USB disconnect, address 34
Title: Re: Sansa Fuze+
Post by: pamaury on July 15, 2011, 05:08:48 AM
@metaphys
It used to work on your device, didn't it ? I haven't change much in the lcd code recently :-/
Did you account for the change in the bootloader.db file ? I'm now using the first 3 stages. Without the first one, usb is likely to not work properly. But that doesn't explain why the screen stays black.
Title: Re: Sansa Fuze+
Post by: metaphys on July 15, 2011, 05:28:01 AM
Yes it used to work  :-\

I did this new build from scratch and followed the instruction on the port's page so I guess i did have the new db file... Confusing indeed. Let me know if I should test something else  :D
Title: Re: Sansa Fuze+
Post by: pamaury on July 15, 2011, 05:32:28 AM
If you are motivated, you could try to bisect to see which revision of the svn caused that. You can also try to change this in lcd-fuzeplus.c:
replace
Code: [Select]
default:
            lcd_kind = LCD_KIND_9325;
by
Code: [Select]
default:
            lcd_kind = LCD_KIND_7783;

Title: Re: Sansa Fuze+
Post by: metaphys on July 15, 2011, 05:56:33 AM
If you are motivated, you could try to bisect to see which revision of the svn caused that. You can also try to change this in lcd-fuzeplus.c:
replace
Code: [Select]
default:
            lcd_kind = LCD_KIND_9325;
by
Code: [Select]
default:
            lcd_kind = LCD_KIND_7783;

I just tried this, same problem (actually as it used to work it would have been surprising)

How can I bisect ? I'm not very familiar with svn, where can I read doc about it ? is it just
Code: [Select]
man svn ?
Title: Re: Sansa Fuze+
Post by: pamaury on July 15, 2011, 06:00:55 AM
There is the svn-bisect tool. If you are using git, there git-bisect.
Title: Re: Sansa Fuze+
Post by: pamaury on July 18, 2011, 11:41:07 AM
Any news about this screen problem ?
Title: Re: Sansa Fuze+
Post by: metaphys on July 19, 2011, 03:56:22 AM
Sorry but i'm again travelling around... I will tell you as soon as possible. But do you mean it works on your device? Isn't it strange?  :-\
Title: Re: Sansa Fuze+
Post by: pamaury on July 19, 2011, 04:02:06 AM
I *think* I would have noticed if the screen didn't work on my device :)
the only thing I changed (except if I did a mistake) is that if the type of screen is not detected, it falls back the type 9xxx instead of 7xxx (don't remember the number). So it's a bit strange :-/
Title: Re: Sansa Fuze+
Post by: pamaury on July 19, 2011, 07:03:49 AM
Hum, my mistake, the wiki is not up to date. Thinking about it, I made two important changes:
- one about memory layout
- one about elftosb
Be sure to have the latest elftosb complied from the SVN.

I've updated the wiki. sorry for the mess :)
Title: Re: Sansa Fuze+
Post by: pamaury on July 27, 2011, 05:02:16 AM
Hi all,
As you may have seen for the SVN log, I've made some progress toward actually compiling the main firmware. I've also investigated dual-boot. The good point is that it is possible to build a firmware.sb file such that the OF will upgrade itself :D That means that installing the bootloader will be easy. However, I did it on mine and dual-boot doesn't work for some rason. I do not quite understand how the OF is booting, this is weird.
Anyway, I'm still working on that.
Title: Re: Sansa Fuze+
Post by: pamaury on August 21, 2011, 02:56:40 AM
Hi all,
I've been in holydays for the last 3 weeks and I probably won't be able to work on the Fuze+ next week but then I'll be back. Please don't send private messages to ask for some news.
Title: Re: Sansa Fuze+
Post by: pamaury on September 12, 2011, 02:43:11 AM
Hi,
again some news from the port ! I'm recently reworked mainy things about memory and the bootloader. I've implemented some ADC related stuff and I'm working on battery charging (not so easy with this chip). I've also fixed the USB tricky details so the bootloader now has USB support and works perfectly. I've tweaked it so one can access either only the main partition or the whole disk (to update the bootloader). Once charging is implemented, I'll move on to the audio drivers and to the touchpad one.
As a side note, for those who are interested, Freescale released the source code of eltosb2 as well as the documentation of the sb file format on their website (download section of the IMX233, perhaps need to register).
Please note that the wiki page is *not* up to date, and I still have some non-committed stuff.
Title: Re: Sansa Fuze+
Post by: pamaury on September 12, 2011, 09:14:33 AM
Hum,
I tried to flash the bootloader myself to what i thought was the bootloader partition and apparently it doesn't work. So I only have recovery mode working on my device now \o/ This is weird because either the ROM doesn't follow the documentation I have either I misunderstood it.

To recover from this situation, I would need a clean flash image. Could someone run recovery mode on some file I provide and do a partial dump of the disk ? This is completely safe and only requires linux + dd.
Thansk in advances.
Title: Re: Sansa Fuze+
Post by: pamaury on September 13, 2011, 02:29:38 AM
Ok,
here is the procedure for anyone who wants to help me:
1) download this file: http://www.mediafire.com/file/71cfi4b7a55g25n/recovery.sb This a the svn bootloader with some modifications I haven't yet committed
2) build the imx_hid_recovery tool in the svn (utils/imx_hid_recovery/, http://svn.rockbox.org/viewvc.cgi/trunk/utils/imx_hid_recovery/) if you haven't done it (no need for a cross-compiler !)
3) Boot the fuze+ in recovery mode (see the SansaFuzePlus wiki page, basically hold volume up while plugging usb)
4) Send the recovery.sb file to the device(probably need root access):
imx_hid_recovery 1024 recovery.sb
5) the screen will show some message, wait a few seconds and it should go into usb mode and appear as a mass storage device
6) make a partial raw dump of the device(I would like the first 64Mb if possible, and at least the first 4Mb) using dd:
dd bs=512 count=131072 if=/dev/sdb of=fuzep.bin
Don't forget to replace /dev/sdb by the actual device name (see dmesg messages) and changes count if you want to dump less (64Mb => 64 * 1024 * 1024 / 512 = 131072, 2Mb => 4 * 1024 * 1024 / 512 = 8192)
7) upload the fuzep.bin file :)

Thanks in advance :)
Title: Re: Sansa Fuze+
Post by: kerobaros on September 14, 2011, 12:15:53 AM
pamaury: here you go. http://dl.dropbox.com/u/126382/fuzep.bin
Title: Re: Sansa Fuze+
Post by: pamaury on September 14, 2011, 11:30:20 AM
Thanks to metaphys and kerobaros I've found out what the problem was. I've managed to build a dual-boot bootloader so I can now select either rockbox or the OF. However doing so currently requres to use freescale's elftosb because the OF expects some alignement that my tool doesn't provide for now.
Title: Re: Sansa Fuze+
Post by: metaphys on September 16, 2011, 06:55:11 AM
great news!
I was just thinking: shouldn't the fuze+ appear on the unusable port's list of rockbox's homepage?
Title: Re: Sansa Fuze+
Post by: pamaury on September 16, 2011, 12:26:40 PM
Yes you're right, it should probably appear. I should also update some parts of the wiki too.
Title: Re: Sansa Fuze+
Post by: pamaury on October 02, 2011, 03:34:08 PM
Hi all,
It has been a long time since the last update but I have some great news! I've made lots of internal changes recently and now the port entirely usable except for the audio part. I wrote a basic touchpad driver so I can navigate it the menus and launch plugins. I changed lots of things regarding the bootloader and the wiki is not up to date but I plan to make Rockbox Utility capable of producing a fuze+ firmware and bootloader as soon as possible.
Title: Re: Sansa Fuze+
Post by: RipCurl on October 03, 2011, 06:01:42 AM
I always wonder, what part of the fuze+ is responsible for the laggy touchpad.... (touchpad itself, cpu, ram or bad firmware ???)

so i just want to know if the navigation in the rockbox menu is smooth and intuitive. Is it still some kind of laggy because its a problem with the hardware?
Title: Re: Sansa Fuze+
Post by: pamaury on October 03, 2011, 06:51:10 AM
The touchpad itself is quite responsive, it can give the finger position 30 times per second or more. However the touchpad itself includes some gesture recognition software so instead of only giving the position of the finger and can also tells you things like "tap at x,y" "slick at at xy,y in direction dx,dy". The OF relies on this gesture recognition which is not really good and laggy. That explains why the OF seems to "miss" some gesture too. In the basic touchpad driver I wrote, I don't use the gesture recognition so it's really responsive but because the current driver is simplistic, it's not as good as I would like, yet.
Title: Re: Sansa Fuze+
Post by: RipCurl on October 03, 2011, 07:01:52 AM
that sounds REALLY GREAT!!!

btw: is there a way to navigate by "sliding" without using the gesture recognition from the touchpad? (= a selfmade/better gesture recognition implemented in rockbox)
Title: Re: Sansa Fuze+
Post by: pamaury on October 03, 2011, 07:05:02 AM
Yes but I need to implement gesture recognition myself. I plan to do it but this is not a priority, the priority is to have audio work of course :)
Title: Re: Sansa Fuze+
Post by: kumy on October 05, 2011, 08:53:27 AM
I have some great news! I've made lots of internal changes recently and now the port entirely usable except for the audio part

youhou !

Great work. good luck for the next part

the wiki is not up to date

is the wiki updated ? Could you point me to the right page please ?
Title: Re: Sansa Fuze+
Post by: pamaury on October 18, 2011, 05:14:50 PM
Hi all,
for those of you who don't follow the mailing list, I now have working sound !
It's still not quite easy to test it on real target because building the bootloader is rather tricky but I'll try to make rbutil do this as soon as possible.
Title: Re: Sansa Fuze+
Post by: metaphys on October 19, 2011, 11:26:31 AM
you rock endlessly  ;D
Title: Re: Sansa Fuze+
Post by: sandro on October 23, 2011, 08:56:49 AM
you do :D

Post Merge: October 23, 2011, 09:00:41 AM
Will it be released only when all the features are working 100%? For example I see that fm radio is not implemented
Title: Re: Sansa Fuze+
Post by: metaphys on October 23, 2011, 09:30:11 AM
I guess not but it seems that there is  still some work to have an installation process for human beings
Title: Re: Sansa Fuze+
Post by: pamaury on October 23, 2011, 09:47:25 AM
Yes there is still some work to do to have an installation process feasible by anyone. Basically I need to write a tool that combines several other ones and integrate it into rbutil.
Title: Re: Sansa Fuze+
Post by: Rarog on October 24, 2011, 09:52:13 AM
Is there already an easy way to build alternative firmware and is the bootloader being able to boot rockbox as well as original firmware so I can always fall back? If yes, I'm willing to try the daily builds as I am waiting for the rockbox port for several months now and it seems to be usable for my needs.
Title: Re: Sansa Fuze+
Post by: metaphys on October 24, 2011, 11:35:12 AM
Yeah everybody is very impatient now to test this port! But I think, that if pamaury says so it means we have to wait. There used to be a way and it was on the port's page. Then pamaury stopped to update it. I guess there are good reason for it: it becames way to complicated. And from what I red on the IRC, dual booting is precisly the tricky part about it... Leave him one or two more weeks and I guess it will be there...  ;D
Title: Re: Sansa Fuze+
Post by: Rarog on October 24, 2011, 04:40:46 PM
Of course I'll be patient. It's just that I discovered the daily builds on FTP, so I wanted to know the status. I was lurking in this thread since months. :D
Title: Re: Sansa Fuze+
Post by: Adam. on November 01, 2011, 02:22:34 AM
Long time lurker, first time poster.

I actually bought a Fuze+ half a year ago because I knew you were working on it. Even though my Clip just died and I am music-less, I can wait :)

Everybody appreciates the hard work you do!
Title: Re: Sansa Fuze+
Post by: pamaury on November 06, 2011, 04:00:07 PM
Hi all,
I finally wrote the tool to build the bootloader image. The tool is called mkimxboot and instructions are written on the SansaFuzePlusPort page on the wiki. There is no support yet in Rockbox Utility so unfortunately this means you need to get the source and compile it. I hope to add Rockbox Utility support for it soon.

Please note that this is all very preliminary so do it at your own risks. If you follow the procedure from the wiki, please tell me if anything is wrong or unclear or doesn't work as expected. The IRC channel is best for discussing issues instead of polluting this thread. Thanks in advance.

Finally note that the wiki does not include the instructions on how to remove the bootloader yet.
Title: Re: Sansa Fuze+
Post by: metaphys on November 06, 2011, 04:58:58 PM
It works I've been able to start! Well I guess next step for me is to learn how to actually use it!  ;D Thanks very much for this! 

Post Merge: November 06, 2011, 05:44:14 PM
what is exactly the mapping of touchpad for now ? I try to set the timer select is the middle of the cross on the touchpad, and revert is the upper left button ? But how to change the item ? I tryed the different direction, it just change the selected item without any possibility to change the item itself ?? I must be missing a key ...
Title: Re: Sansa Fuze+
Post by: Rarog on November 06, 2011, 06:52:24 PM
I fail to build at this step:

Code: [Select]
./mkimxboot -i sandisk-firmware.sb -b bootloader-fuzeplus.sansa -o firmware.sb -t dualboot
It tells me following:

Code: [Select]
[INFO] mkimxboot models:
[INFO]   Fuze+: idx=0 rb_model=fuz+ rb_num=72
[INFO] mkimxboot mapping:
[INFO]   md5sum=c3e27620a877dc6b200b97dcb3e0ecc7 -> idx=0
[INFO] MD5 sum of the file: E8 24 AB 3B AE E9 9D F6 57 6E 52 E6 F5 B6 EF 7D
[ERR] MD5 sum doesn't match any known file
Result: -4

I'm using the firmware.sb with version 02.36.03.

EDIT:
I'm an idiot, I don't know why I took not the latest firmware download. :D Everything works now.
Title: Re: Sansa Fuze+
Post by: pamaury on November 06, 2011, 07:05:17 PM
Just in response of this post, you need to download the latest sandisk firmware (2.38.6). Other versions might (and will probably) work but we only add support for them if there has been some confirmation that it works. I can't see any reason not to use the latest version of the OF so I only added support for the latest one, BUT if you have a good reason to stay with an older one, I can test it and add it to the tool.
Title: Re: Sansa Fuze+
Post by: Rarog on November 06, 2011, 07:20:28 PM
No, the reason was just, that I opened the older url from firefox cache. Then I decided to look into the code and noticed, that md5 is for newer version then the one I downloaded. (facepalm.jpg) Of course I have the newer version 2.38.6 installed.

Post Merge: November 06, 2011, 07:22:59 PM
Ok, another question, i flashed the firmware, now I just have gray screen. It seems, that i did boot into the non-existent rockbox, I connected the fuze and copied the folder .rockbox to my Fuze+, but I don't know how to restart it, so it would boot. It doesn't seem to react to 15 seconds holding down the power button. Do I have to wait, until the Fuze shuts itself down?

Post Merge: November 06, 2011, 07:25:58 PM
Hm... Strange. Seems it was off, as I can boot the original firmware now, but I don't see, why it didn't load the rockbox firmware previously. I will wait, till the original firmware hast read the SD card and will try to reboot and see what happens.

Post Merge: November 06, 2011, 07:28:19 PM
Hm... Still grey screen when I try to boot in rockbox mode.
Title: Re: Sansa Fuze+
Post by: metaphys on November 06, 2011, 08:01:23 PM
SD is not supported and not recommended during firmware update... could it be the reason ?
Title: Re: Sansa Fuze+
Post by: Rarog on November 06, 2011, 08:12:21 PM
During the update SD wasn't inside. I inserted it only after booting original firmware. Before I got the grey screen directly after the firmware update.
Also I tried to boot rockbox with and without the SD card. It doesn't make any difference. Independent of SD card inside I can boot the original firmware as described in the FAQ.

Post Merge: November 06, 2011, 08:37:07 PM
Also booting original firmware and afterwards connecting to usb leads to grey screen again.
Title: Re: Sansa Fuze+
Post by: ddscentral on November 06, 2011, 08:58:43 PM
Been following this thread for a while and decided to post my observations.

Built rockbox and the bootloader fine without much trouble on Debian 6.
Some observations:
- Boots VERY quickly (in 1-2 sec, original FW may take up to a minute)
- Music playback is louder than in original FW (I like that).
- The touchpad is very responsive (unlike in original FW)

Problems:
- The screen fade-in fade-out is funky (IIRC, this is already known)
- The keys (touchpad) sometimes act funky. For example Back key doesn't seem to work in the player screen. Cursor keys don't work at all in text editor screen.
- Some plugins are broken (again, mostly key related problems)
- SD card doesn't work (IIRC, SD card is listed in wiki as non-working, so can't complain here)
- Battery readout looks strange to me. The original FW shows about 50%, while rockbox shows 98%.

The only thing I miss right now is the SD card support (and possibly charging without the original FW).
Title: Re: Sansa Fuze+
Post by: pamaury on November 07, 2011, 03:07:14 AM
Hello,
a grey screen probably means you have the second type of LCD which I haven't tested (because I don't have it). Perhaps there is a problem with it, I will have a look. Thanks for the feedback. Note that plugging usb in the OF makes it reboot so if you want to reboot to the OF, hold volume down on usb plug.
Title: Re: Sansa Fuze+
Post by: Rarog on November 07, 2011, 03:16:28 AM
Ah, the thought with 2nd display came into my mind. Well, I wanted to  boot the OF to charge,a s it doesn't work with Rockbox yet, but I found out, that plugging the MicroUSB t directly into the wall instead of Computer does the trick.
Can I help you implementing it by using some special debug build or by providing you with some logging output perhaps?

Post Merge: November 07, 2011, 03:19:40 AM
But by the way we'll need a manual reflash function or instruction, as currently it seems to ignore firmware.sb during the boot.
Title: Re: Sansa Fuze+
Post by: pamaury on November 07, 2011, 03:23:42 AM
For the screen, I will post a few files and instructions that would greatly help me. Just give me a few moments.
If you want to reflash, you need to boot into OF usb mode: hold Volume Down and plug usb, then release Volume Down. Then put the firmware.sb file and unplug. Then reboot into Of using Volume Down again.
Title: Re: Sansa Fuze+
Post by: pamaury on November 07, 2011, 03:40:48 AM
Here is the file:
http://www.mediafire.com/file/6lpj5xlq89b2jsj/lcd_dumper.zip
If you want to recompile, run make clean and make but the zip already contains the recovery.sb file. In the otp_read/ subfolder, recompile it then run the following commands:

sbloader 1024 recovery.sb
otp_reader/read_util 066f:3780

where sbloader can be found the the SVN in utils/imxtools/. You might need to ran both program with sudo. The read_util will produce some output, please copy it here if you have a non-working screen (one copy should be sufficient).

EDIT:
I have committed a new change to the SVN to fix a typo in the lcd initialization, you can try to rebuild the bootloader and reinstall it (you will need to do a svn up) to see if it works.
Title: Re: Sansa Fuze+
Post by: Rarog on November 07, 2011, 04:40:59 AM
Sadly I didn't take my MicroUSB cable to work so I'll be able to test everything only this evening, but I'm really looking forward to it. Rockbox for Fuze+ seems to be in a very hot phase and should get usable very fast and I'd be glad to help bringing it forward! ;D

Post Merge: November 07, 2011, 04:46:04 AM
And btw, will I have to build the bootloader or just the normal rockbox? And if bootloader, then I'll have to use the original USB mode to reflash it, am I right?
Title: Re: Sansa Fuze+
Post by: pamaury on November 07, 2011, 04:48:11 AM
Good question, rebuilding normal rockbox will be sufficient but I advise you to rebuild the bootloader as well because it displays some messages which might be useful for debugging or just to know what the code is doing. To reflash the bootloader you will have to use the original USB mode.
Title: Re: Sansa Fuze+
Post by: metaphys on November 07, 2011, 07:31:51 AM
So I ve made a few test to stress audio reading:
a few mp3 160kbps - ok
ogg 256kbps - ok
flac 858 kbps - ok
flac 24bit  - 96khz - stereo (2685 kbps) (1 song = 84 MB) wich a lot of software still not handle! for example xcfa can't convert this! - ok, wow mama!
flac 24bit  - 96khz surround 5.1 (6437 kbps) (1 song = 209 MB, album = 3,2 GB  :D) - the file is opened show kpps info but then close immedialy (perhaps because of the chanal exceding 2) gotcha at the end  ;D

Post Merge: November 07, 2011, 08:21:23 AM
anyway i suppose the device won't really play it at 24 bit isn't it?

Post Merge: November 07, 2011, 08:45:07 AM
I've got a pretty good question: As there is no battery support what happen if battery reach end while running rockbox? Isn't there a risk of dying device?
Title: Re: Sansa Fuze+
Post by: pamaury on November 07, 2011, 09:17:09 AM
If the battery run out, plug USB hold Volume Down to boot to the OF and recharge.
Title: Re: Sansa Fuze+
Post by: Rarog on November 07, 2011, 09:31:01 AM
Also while in the OF when using a normal MicroUSB charger (e.g. from your phone) doesn't reboot the device into Rockbox and charges without any issues.
Title: Re: Sansa Fuze+
Post by: pamaury on November 07, 2011, 09:34:19 AM
Yes, the OF only reboots if there is an host on the other side, in which case you need hold Volume Down when rebooting.
Title: Re: Sansa Fuze+
Post by: saratoga on November 07, 2011, 11:41:53 AM
flac 24bit  - 96khz surround 5.1 (6437 kbps) (1 song = 209 MB, album = 3,2 GB  :D) - the file is opened show kpps info but then close immedialy (perhaps because of the chanal exceding 2) gotcha at the end  ;D

You should probably file a bug report with a link to a sample flac file that doesn't decode.  Sounds like a bug in our decoder. 
Title: Re: Sansa Fuze+
Post by: metaphys on November 07, 2011, 12:24:53 PM
Quote
You should probably file a bug report with a link to a sample flac file that doesn't decode.  Sounds like a bug in our decoder. 

Ok i will but honestly who want to listen 5 channel 24 bit flac on a portable player ?


Regarding the port: all toshiba gigabeat themes seem to be compatible!

Post Merge: November 08, 2011, 07:08:07 AM
Hello!  :D
 I've got a bug. It happens often so I guess it can be related to the port... When browsing file in player mode (with next or prev  song button) it sometime happen (while not systematicaly, several time a day) that I suddenly get a white screen with:
Undefined instruction
at 0000AC44
The adress is some time another but I already have this one 3 three time. Then I have to reboot rb
Anything I could do to debug this?
Title: Re: Sansa Fuze+
Post by: Rarog on November 08, 2011, 11:55:27 AM
Ok, here is the patch with documentation of the instructions for the 9325 display.

http://pastebin.com/RdpDeegE
Title: Re: Sansa Fuze+
Post by: metaphys on November 10, 2011, 03:41:43 AM
Wow! I just tested the gameboy plugin and it runs really good.  :D  :o
One can even play small game like tetris while listening to music (not big ones -> not enough memory  ::)).

i'm looking forward to do those codec's test: http://www.rockbox.org/wiki/CodecPerformanceComparison

But would it works without time and power implementation?

Edit : Ok I guess I'm asking kind of a stupid question! How could it record decoding time without time implemented?  ;D
Title: Re: Sansa Fuze+
Post by: pamaury on November 10, 2011, 07:02:43 AM
I don't think time is needed for the codec tests because we already use a tick timer internally for time measure, RTC has nothing to do with it and only has precision up to a second. As for power, you can test the codec performance without charging implemented, I don't see the problem.
Title: Re: Sansa Fuze+
Post by: metaphys on November 10, 2011, 07:45:14 AM
I thougt the codec might be using battery level to evaluate consomption. Anyway the problem is I have to stop this noob attitude always to ask before trying...  ;)
Test runnnig I will post result asap
Title: Re: Sansa Fuze+
Post by: pamaury on November 10, 2011, 12:28:30 PM
I've committed a few changes so if someone with a non-working screen can try it would be nice. It shouldn't change anything but we never know.
Title: Re: Sansa Fuze+
Post by: pamaury on November 10, 2011, 01:09:25 PM
@ those who have a grey screen: could you try to see if rockbox is actually running or if it's just stuck ? There a many possibilities, one would be to press power a few seconds to see if the player shutdown, or wait a bit to see if backlight fades out and then in when you press a key.
Title: Re: Sansa Fuze+
Post by: metaphys on November 13, 2011, 02:25:22 PM
Ok pamaury I've just talk with alienkid on the IRC and there is no grey screen anymore - it works !!! \o/
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 13, 2011, 02:50:05 PM
Hi finally signed up. Let me clarify a bit:
screen works fine I do get a grey screen for a bit on bootup but then fine except for lines being on screen. Like on an olde TV set or something they are a RB specific "feature." (not in OF)
Also Touchpad needs work but you knew that already.
THANK YOU for all your hard work! And thank you both for compiling it for me to test on. Give me a yell and the compiled stuff and I'll continue you test when you need me too. For now I'm gonna play with it then reflash OF back on.
Title: Re: Sansa Fuze+
Post by: metaphys on November 13, 2011, 03:00:15 PM
you don't really need to reflash the of: If you keep the volume down key pressed while power on it should boot  into OF (dualboot)
Title: Re: Sansa Fuze+
Post by: pamaury on November 13, 2011, 03:39:46 PM
I'm glad to see that it works, however I have even less explaination for the lines your are seeing, can you take a photo ?
Also can you tell which commit fixed it: r30926 or r30958 ?
Title: Re: Sansa Fuze+
Post by: metaphys on November 13, 2011, 03:46:23 PM
I've gave him a bootloader compiled yesteday evening
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 13, 2011, 07:29:30 PM
r30975 says the system>rockbox info menu. Lines I don't think would show in a pict
Title: Re: Sansa Fuze+
Post by: metaphys on November 14, 2011, 05:35:17 AM
I think I know what are those "lines" does it occurs all the time? On my device sometime I have something like the display frequency was going down (probably related with heavy charge on the CPU)
Title: Re: Sansa Fuze+
Post by: pamaury on November 14, 2011, 05:40:53 AM
The display frequency is derived from the crystal so it shouldn't change with the cpu load (it could be the case with hbus clock with auto-slow only iirc). But perhaps the crystal is not precise enough, I'll try to change the clock setting to see if it works better.
Title: Re: Sansa Fuze+
Post by: metaphys on November 14, 2011, 05:56:00 AM
well on my device it is not very often (and cpu load relation is just a suposition and wasn't prooven for now...)
I've made some new test about the memory but and I get a new bug. I think that there must actually be several different problem. Because I can reproduce "undefined instruction" on some file systematicly and some other undefinined instruction error are like random (for example the ones in the test-codec plugin can occurs from early beginning till middle of the whole files tested)
I've made a lot test yesteday so I think we can count out disk problem (I reformated the device, double checked the partition, installed the test file with firmware usb)
II don't have all detail here cause i'm still at work but I'm done with it now so I'll be aroud in one hour or so...
Title: Re: Sansa Fuze+
Post by: Rarog on November 14, 2011, 06:49:16 AM
Finally I have internet again and could get the last changes and I can confirm like alienkid, that the 2nd display finally works. It's good to see Rockbox on my MP3 player again.
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 14, 2011, 08:51:35 AM
Rarog: do you get lines across like me? That you can pick out from a normal use distance? (about 10-12in from face)

Pamaury: is there a bold version of the default font available at it's default pt size? Personally I would find it easier to read.

EDIT: Also the power % read out varies greatly from the OF. 97% when OF says ~85%
Title: Re: Sansa Fuze+
Post by: pamaury on November 14, 2011, 09:09:39 AM
The battery has not been calibrated so the battery percentage is wrong.
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 14, 2011, 09:32:21 AM
OK. I'm working on getting a compile environment setup in a VM right now. How can I get the build of rockbox that is auto-built? (everyday?) Someone linked me it in IRC yesterday but I don't know how to find it.
Title: Re: Sansa Fuze+
Post by: saratoga on November 14, 2011, 11:41:42 AM
How can I get the build of rockbox that is auto-built? (everyday?) Someone linked me it in IRC yesterday but I don't know how to find it.

That link is updated everytime SVN changes, and is still in the SVN logs.
Title: Re: Sansa Fuze+
Post by: metaphys on November 14, 2011, 12:05:53 PM
Ok to clarify this I've updated the wiki with a link to a zipped bootloader and instruction for non compiling user  ;)
Title: Re: Sansa Fuze+
Post by: RipCurl on November 14, 2011, 04:17:53 PM
Hey
i've followed this thread since the early days and today was the day of the days   :D
Here is my feedback:
Screen: I have the same prob as alienkid10. Between every vertical "pixel line", there are thin black lines. Also the lines are flickering like a very old CRT-TV with a low refresh frequency. It seems like the contrast is pretty low, too.


Navigation: Is the "back-button" disabled while being in wps-mode???
Sometimes the up and down buttons are acting strange: Often I have to touch/press them a few times. Then the touchpad starts to realise that its should be responsive and the    responsiveness starts accelerating ( = at first it reacts pretty slow then it accelerates and after 1-3 seconds I can tap as fast as i want).
I also have the feeling, that the left and right buttons are not that affected by this weird acceleration.
I would recommend a implementation of the play/pause-button while being in browsing mode.
In general the back button is not that responsive. But a few times while testing it reacted as fast as the accelerated up/down buttons.

Sound: Wow! rockboxed fuze+  + my akg k518's.... the sound is much more "crispy" than before. 24bit flac == Eargasm  ;D ;D ;D

Keep up the good work!!!

RipCurl
Title: Re: Sansa Fuze+
Post by: buckminster on November 15, 2011, 09:10:37 AM
Great work! Forgot how quick an mp3 player can start up with decent firmware  ;D Can't wait until FM Radio and SD card support!

I noticed that it won't voice the menus. I tried creating a voice file using RockboxUtility, but it doesn't seem to work. I used the same settings to create dirname files and that works fine.

I see the horizontal line (interlaced) issue as well, but it looks like it's just the bitmaps used because if I turn off the backdrop, I don't see the issue any more.
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 15, 2011, 02:04:53 PM
I don't think it's the bitmaps. Try using the "rockboxed" theme from the gigabit I believe it just sets BG color and you can see the lines on it.
Pamaury: anyway I can help to debug the LCD looks like CRT thing?
Title: Re: Sansa Fuze+
Post by: buckminster on November 15, 2011, 03:08:37 PM
Ah, you're right - it just looked fine because the background (and the lines) were black.  :D
Title: Re: Sansa Fuze+
Post by: gama on November 16, 2011, 01:16:02 PM
Hi, i installed rockbox in my fuze+ last week, and it works quite well already.   But it seems the battery drains really fast when using rockbox.  Does anyone else have this problem?.
Title: Re: Sansa Fuze+
Post by: pamaury on November 16, 2011, 01:17:39 PM
The fuze+ is in an early stage, there are a couple unimplemented features that currently a imply a faster battery drain.
Title: Re: Sansa Fuze+
Post by: Adam. on November 17, 2011, 03:32:18 AM
Thanks metaphys for uploading a bootloader for mortals like me :)

Just a quickie - is the touchpad near impossible to use (very unsensitive/unresponsive) for anybody or is it just me?
Title: Re: Sansa Fuze+
Post by: metaphys on November 17, 2011, 05:05:43 AM
the touchpad only has basic fonction implemented. It is very simple and there are even still some key missing (select key in many menu for example) as written by pamaury, this is very early stage.
It only give basic usage far from what is possible with it. There are still a lot of part that don't even have a fonctionnal basic driver for now (usb charging sd radio recording, not to mention power optimization...) so touchpad just cannot be a priority by now... the statut of the port is still "unusable" even if it become day after day more usable.
Title: Re: Sansa Fuze+
Post by: Adam. on November 17, 2011, 05:20:27 AM
Absolutely understood. Cheers :)
Title: Re: Sansa Fuze+
Post by: pamaury on November 17, 2011, 01:45:18 PM
I think I found out the sensibility problem: the OF handles two different revisions of the touchpad and uses two different sensibility parameters, so I'll do the same for the now. Perhaps a setting will be appropriate later on.

EDIT:
I have committed what I think the OF does, please retry it. What would be nice would be that some of you go into the system > debug > view HW info, press enter twice to reach the touchpad debug string and report the product ID if it's different from the following ones (I'll update the list according to feedback):
- 1533

PS: the escape the button debug view, press power once
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 17, 2011, 08:23:05 PM
in r31026 I have same ID as you. 1533
Title: Re: Sansa Fuze+
Post by: buckminster on November 18, 2011, 12:02:14 AM
Another 1533
Title: Re: Sansa Fuze+
Post by: Adam. on November 18, 2011, 01:56:03 AM
And another 1533. Much better now (though still unable to register left/right in the menus).
Title: Re: Sansa Fuze+
Post by: metaphys on November 18, 2011, 07:30:10 AM
1533 here also. Am I the only one struggling with the back button in the menus? ;D if not perhaps the detection zone could be enlarge?
Title: Re: Sansa Fuze+
Post by: pamaury on November 18, 2011, 07:34:41 AM
Thanks for the feedback butplease don't post it if you already have a number which has been reported, otherwise it's basically spamming. The detection zones for the buttons are not very good; depending on how you put your finger on the touchpad, it might be detected or not.
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 18, 2011, 09:09:19 AM
Sorry about starting that flood pamaury.  :D
Meta: I too have trouble getting back to work sometimes. Also down doesn't work consistently for me.
Title: Re: Sansa Fuze+
Post by: gama on November 21, 2011, 02:56:41 PM
Hi, i updated to latest revision on friday and i'm having some weird problem, sometimes when i select a song from the file browser, all songs are skiped like if there some problem at loading time.  Could this be a problem from the fuzeplus port?  I will try the another revision to make sure.
Title: Re: Sansa Fuze+
Post by: halonachos117 on November 22, 2011, 06:40:27 PM
I've been having that same problen, as well. Perhaps it can't read the files, since the wiki lists the SD driver as only being 40%, with only a few commands implemented. If that's the case, I'm sure this will get fixed eventually, although Pamaury does still have a long to-do list, so be patient. 8)
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 22, 2011, 09:14:18 PM
so far songs play fine for me. Internal storage. 8GB MP3 128kbps.
Title: Re: Sansa Fuze+
Post by: gama on November 23, 2011, 09:51:20 PM
@alienkid10: could you please tell me which svn revision are you using?  Also the problem i reported doesn't happen in simulator build.
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 24, 2011, 10:18:29 AM
R31045. I tryed to play a video today and only get "cannot create buffering thread" any help?
Title: Re: Sansa Fuze+
Post by: pamaury on November 24, 2011, 05:08:40 PM
Hi,
I might know why the thread won't create, I'm missing an extra thread define because of the touchpad thread. I've worked on a radio and I must admit I hit a wall :) The radio chip i2c works but it won't seek/tune for some reason (which why the device freeze). It might be due to some incorrect oscillator setting and our generic code for that chip doesn't do the init quite correctly. I hope will fix this problem soon but I don't have much time during the week.
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 24, 2011, 06:16:09 PM
no prob. Get radio working first. Video isn't that important.
Title: Re: Sansa Fuze+
Post by: metaphys on November 24, 2011, 07:39:15 PM
Hi all  :D

I've started to have a look at the touchpad code. Although, i still don't trust me enough to start implementing gesture, I might have find some interessting test to perform on the touchpad in order to adjust one of the only setting that would stay whatever we implement: sensitivity.
You might have noticed that if you go to the touchpad debug screen that pamaury told about a few days ago (system > debug > view hw info and then pressing in the middle of the cross 2 times) you can actually set the touchpad sensitivity using volume button. Be carefull, above some value you will not be able to control anything because the touchpad will go mad even if you don't touch it, under some value you will not be able to use it anymore (in any case the value get reseted on reboot). You can use this to set the value that you prefer for example for it remains as long as you don't turn the device of.
But before going any further as implementing some setting menu or even calibration, I would need further test. The biggest problem is that we don't know if the values we need are mainly the same/totaly a matter of taste/only different on different hardware. Depending on the answer I could know how to go further.
So I've found some "objective event that could be used to make comparaision:
In the debug screen you will see 3 values that are always moving if you touch the touchpad "attn" and the two "rel" values. I noticed that if the value is too high, those value are still moving and never get stable again even if you don't touch anything (but after having touched it once) on my device the limit is sensi: 24 above this values it does not calm down... Then I also noticed that if you do the tap and hold gesture (double click but you hold the hand on the touchpad on the second contact) if the values is two high the tap and hold always remain... (on my device it occurs for any values above 21) so let's says this will be the HIGH values.
On this other and if the values is to low the contact cursor is starting to flicker. It means that if you hold tap and hold pressed while setting sensitivity down at some point it the tap and hold message will disapears. And it starts from the corner (which is actually the reason why we have difficulty with side upper button) and also with the vertical line of the cross (strange, but this is the reason why we sometime have problem with down) So if we do a tap and hold on the back button and hold it while setting sensitivity down it we could decide it will be our LOW values. (on my device -9)
Finally we could have a PREFered values. (for me 21)

It would be nice if you could test this and send me your values so that we know how consistent they are. In order to avoid flooding this thread, you could PM me.
For the moment this is difficult to test because the sensitivity setting of the sensitivity is itself to sensitive :D  !!!
But I've made a little patch. it is in the flyspray: http://www.rockbox.org/tracker/task/12405. I don't know all long it will take to have it in the build so for the moment this will only be for compiling user - others one could try the alternative test build on the port's page. Anyway the mixing between power and volume button is still anoying...
EDIT: Well it is a very simple hack on a debug fonction, i've tested it, but I guess that you should wait for answers or comment to come either here or on the flyspray before testing it  ::)

Pamaury: Regardind Rockbox utility it turns out that it is not possible/not worthing to implement before we have the bootloader on the server. As I don't trust me enough to write something without being able to make test step by step, I will have to wait on that. Anyway I will probably have to update things because Bluebrother is also updating the way installing methods are implemented in rbutil (http://www.rockbox.org/tracker/task/12402)
Title: Re: Sansa Fuze+
Post by: qiaozi on November 25, 2011, 08:45:36 AM
@metaphys,

I have been looking at the touchpad code as well and thought the main difficulty with setting the "sensi" value was because the while() loop is ticking over too quickly. I will try putting a delay in the while loop and also try your mod of the sensitivity counter to see what works best. At the moment my favourite "sensi" value is about 10, below 0 is not sensitive enough and above 16 is too sensitive.
Title: Re: Sansa Fuze+
Post by: metaphys on November 25, 2011, 01:56:39 PM
@qiaozi and all:

Actually:
1) the code is more easy as I thought
2) Pamaury did nearly all the early work to implement further fonctions

so I've started basic mapping on the device to have at least all RB fonction available (even poorly) you can follows/comment/help that here:
http://www.rockbox.org/tracker/task/12405
compiling people can tweak their own mapping in the file: apps/keymaps/keymap-fuzeplus.c (look at other files it is not that complicate
Ideas about how should what works are also welcome (which touch for what) but not here, there. Actually for the moment this is very basical because as I'm planning to add new implementation the mapping are probably going to change partly. (the device is really good! we should be able to have fonctions like double click, double click with 2 finger, scrolling with one finger, scroll with 2, button with two finger) ... yes but I have to write them first... If anyone want to help, please do!
First I think that I will start to find a way to have a proper setting menu for sensibility and save over boot...
Finally after gesture are implemented I guess the best way would be to have a menu to configure the key and gesture as we want them

I'm actually not sure about were to implement new gesture... there are no touchpad target in the tree... Perahaps should I write a generic driver for touchpad? On the other hand if they are not a lot of touchpad around or if they don't work that way it would be useless... Any ideas about that pamaury?

Jimmyboy : radio doesn't work for the moment.
alienkid10 : yeah I also have this issue
Title: Re: Sansa Fuze+
Post by: metaphys on November 26, 2011, 07:12:38 PM
So here are some new...

I've made a big patch that improve touchpad driver and key mapping. All info and a link to a build for non compiling user can be found here: http://www.rockbox.org/tracker/task/12405
1) Change the key limits on the touchpad: they are now 9 virtuals keys on 3 x 3 grid and a tenth key has been added: simultaneous touching the touchpad with 2 fingers (see patch 3 and 4 in the file.
A consequence I noticed is an very impressive increase of the touchpad reactivity because button zone are now wider.
2) Add A LOT LOT LOT of mapped key (see first patched file):
major change are:
a) in WPS:
-bottomright and bottomleft keys are direct link to file browser and playlist. another click and you are back in the WPS! (COMMENT: IS THERE A WAY TO GO TO THE DATABASE UNSTEAD?
-long press with two fingers activate LOCK when the finger are released from touchpad (this is the only way I found to avoid to much sensibility leadind to multiple lock unlock sequence)
b) keyboard:
We now have a fully fonctionnal virtual keyboard
-directions to select a letter
-play to insert a letter
-buttomright and bottomleft to move cursor
-back as backspace
-doublefinger key to finish
-power to abord
c) menu and list:
-left and right to go to previous/new page
-doublefinger key bring you back to the main menu

d) mapping for future : basic to handle recording, time and radio

3) reset standart sensitivity value to 13 on all touchpad

TODO:
- a setting menu to have sensitivity and future scrolling sensitivity (I don't know how to do that, HELPS)
- Implement different kind of scrolling and test them
- having a menu to map button to everyone suits...
Title: Re: Sansa Fuze+
Post by: qiaozi on November 27, 2011, 10:13:35 AM
@Metaphys,

I applied your v9 patch, it works very well, touchpad much easier to use now. I still find that sensitivity level of 13 is a bit too sensitive on my device and have to set it to 10. The keyboard is good, the only problem I had is when playing a music file and using the text editor, there is a beeping sound when scrolling around the keyboard. I will do some debugging and try to find the cause of the beeping.

Anyway, my Fuze+ is finally usable, many thanks to you and pamaury.  :D
Title: Re: Sansa Fuze+
Post by: metaphys on November 27, 2011, 05:37:35 PM
thanks for the comment... I really need direction about what to do how because we have now a bunch of key to use... For example the WPS will get some improvement further! And if nobody tell me what is the action to go from wps to database... then I'll create it!

It seems that rockbox already has support for touchpad sensibility I found nice #define HAVE_TOUCHPAD instruction in the code  ;D
But the compilation fail with it, I guess we need to implement the fonction to set sensitivity...

well a lot of work still to do
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 27, 2011, 07:03:36 PM
meta: can I have list of the mappings now?
Title: Re: Sansa Fuze+
Post by: metaphys on November 28, 2011, 02:53:21 AM
if you can read my post I guess so  ;D

Edit: I think I will change simple double finger click to quickmenu unstead of going back to main menu... what do you say?
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 28, 2011, 08:17:59 AM
What's the quickmenu?
Sorry was tired when I asked didn't realize you did tell them.  ::)
Also how can I test sensi as non-compiling user? Right now when in that screen when I press up sometimes the screen goes back to debug menu (I assume it's because it's wired to the same thing as power?)
Also still no way I can help debug the second screen?
Also can we make volume buttons usable when locked? (in meta's touchpad build)
Title: Re: Sansa Fuze+
Post by: metaphys on November 28, 2011, 08:55:15 AM
Quote
Also how can I test sensi as non-compiling user?

debug menu and sensi is the value changing when you press volume keys

Quote
when I press up sometimes the screen goes back to debug menu
jep no idea how to avoid that usely i try to press again powwer and volume keys before coming back the menu
Quote
Also can we make volume buttons usable when locked?
Ouch! didn't notice  that. I don't know ik it is possible I'll will have to investigate....
Anyway everybody: DON'T GET USE TO THE NEW BUILD KEYMAPS IT'S ALL GONNA CHANGE!!!
I just found the keymaps specialist I was looking for and he raised a good one: keymaps has to be consistent with other port.
So I'm plannign my third keymaps whole remake in 3 days while considering a bouhdist conversion...
Title: Re: Sansa Fuze+
Post by: santatution on November 28, 2011, 07:32:51 PM
Hi I'm not sure if this the right board for this but how do you do a restore so I can go back to the main firmware? I already tried using the recovery mode but it doesn't show up on my computer. Thanks.
Title: Re: Sansa Fuze+
Post by: metaphys on November 29, 2011, 04:21:53 AM
You can acces original firmware by pushing volume down and holding it while pressing power. After 5 - 10 second the OF should show up. If you really want to take rockbox totally out of your device: Just do a usual firmware update with an official Firmware release from Sansa forum
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 29, 2011, 03:56:32 PM
not sure if this should be posted here:
I noticed some themes are up for the Fuze+ but they appear to be landscape themes. Which orientation should themes be made for and should this be made know to theme creators?
Title: Re: Sansa Fuze+
Post by: RipCurl on November 29, 2011, 05:24:35 PM
the themes for the gigabeat s work fine with the fuze+ because the resolution is the same
http://themes.rockbox.org/index.php?target=gigabeats
Title: Re: Sansa Fuze+
Post by: metaphys on November 29, 2011, 05:37:54 PM
so: new mega update on the touchpad mapping: http://www.rockbox.org/tracker/task/12405

Please do help me debugging finding idea how to map stuff... We are not completly free but we still can change some stuff...

@Alienkid The question of volume change while key are locked seems o have quite an history here...
The people presenting the patch might have it done in an improper way (changing default behaviour for example)
I'll will have to go for some advice about it...
Title: Re: Sansa Fuze+
Post by: alienkid10 on November 29, 2011, 07:13:41 PM
@ripcurl I know thye do but a Sansa Fuze+ section as appeared under themes and they (seemingly) are landscape. I tried getting the one based off cabbie to work but it doesn't.

@meta: any chance of a zip for non-compilers to help you test?
Title: Re: Sansa Fuze+
Post by: saratoga on November 29, 2011, 07:19:19 PM
@ripcurl I know thye do but a Sansa Fuze+ section as appeared under themes and they (seemingly) are landscape. I tried getting the one based off cabbie to work but it doesn't.

Its been reported.  The theme site database appears to be stuck at the moment, so someone with access to the machine might need to look at it. 

@meta: any chance of a zip for non-compilers to help you test?

If you're going to be posting useful bug reports in this thread, you should really invest the 10 or 15 minutes involved in figuring out how to compile (not counting download time anyway if you have a slow connection).
Title: Re: Sansa Fuze+
Post by: jimmyjboy on November 29, 2011, 09:15:10 PM
i noticed to get out of the "now playing screen" you have to press in the center of the touch-pad insted of the top left "back button". don't know if this was on porpus but i personally think center press should be now playing settings like the OF
Title: Re: Sansa Fuze+
Post by: qiaozi on November 30, 2011, 07:20:06 AM
@Metaphys,

I tried to apply the v16 patch, but most of the chunks were rejected. Not sure why, but looks like I will have to enter all the mods manually, unless you can drop your .c and .h files onto dropbox. ;)
Title: Re: Sansa Fuze+
Post by: metaphys on November 30, 2011, 08:44:24 AM
well the patch include all my work on this from the beginning so you have to download fresh sources before applying it...

EDIT : Anyway I made a slight change and added a link to zip ... Pamaury said it will be in the sources this evening...

Post Merge: November 30, 2011, 11:14:39 AM

EDIT 2 : @jimmyboy.
i noticed to get out of the "now playing screen" you have to press in the center of the touch-pad insted of the top left "back button".
No. Center is database or file browser (it depends on the last one you used to get to WPS) on short press
context on long ones.
i personally think center press should be now playing settings like the OF
Rockbox don't follow OF way to work. As it works on many device it has to follow some standards, at least on default configuration. We could implement some configuration of the keys but this has to be done very cleanly (to be supported on all device) and will be a lot of work!
To get out of the WPS (while playing screen) you have to press back key short... this is pretty intuitive, isn't it?
to go to wps from menu or browser or database you have to press play... this is also intuitive, isn't it?

@Everyone: I'm moving forward learning latex in order to have a manual compiled anyone familliar with latex want to help?

EDIT 3: We now have ours own dedicated themes page working, thanks!!
Title: Re: Sansa Fuze+
Post by: qiaozi on November 30, 2011, 12:13:52 PM
@Metaphys,

Applied v16 patch, no problems if I do a svn checkout instead of update. ;D

I have been testing the apps and could not exit from some of them, such as the metronome app. I had to power off the device to exit. In Fuzev2 the exit key for the metronome app is defined as "long HOME". Since there is no HOME button on Fuze+ some other key/combo will have to be used, maybe another two finger combo like the WPS lock.
Title: Re: Sansa Fuze+
Post by: metaphys on November 30, 2011, 01:34:17 PM
too late!!! we are already on patch 17!!  ;D (but only a minor fix this should'nt change anything to your problem... which one anyway doesn't appears on my device... long press on back keys take me easely out of metronome...)  ::)
Title: Re: Sansa Fuze+
Post by: qiaozi on November 30, 2011, 02:19:35 PM
Yes, long press on back key works for me now, just have to press longer. This is a bit confusing, many of the apps and demos use different keys/buttons for exiting such as power button, play key and back key. It would be nice if they were all consistent, but probably too much work to modify them all now.
Title: Re: Sansa Fuze+
Post by: metaphys on November 30, 2011, 02:42:52 PM
oh no that not a lot of work at all - it's just impossible !   ;D
There is no app mapping, they seems to use they're own map... for what I know at least... If not then it could be rather easy... I would give you the generic file, you write it as you want and then i add it too sources... But as far as I know plugin are just independant application
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 01, 2011, 09:11:36 AM
Meta: I tried to do the sensi test and here are my results using r31065M:
upper limit: can't reach since it frustratingly quits the HW info touchpad thing most times I press up vol. I got it to about 20 which allowed me to not touch it at all and just hover over it and have it see me.
preferred setting: 10-13  with 12 being what I mostly use.
lower setting: anything below 0 is basically unusable
no detection below: -10/-11
Title: Re: Sansa Fuze+
Post by: metaphys on December 01, 2011, 11:11:14 AM
thanks this is nearly what I get on mine. It would be nice to have other report because if it's only a matter between 10-13, I guess there no use to have some setting menu for that...
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 01, 2011, 08:27:12 PM
just me or is anyone on r31106 have left (in menus only?) act like back and right act like center? (select?)
Also how do I set the time? It doesn't keep when I push center.
Title: Re: Sansa Fuze+
Post by: jimmyjboy on December 02, 2011, 02:23:04 AM
just me or is anyone on r31106 have left (in menus only?) act like back and right act like center? (select?)
Also how do I set the time? It doesn't keep when I push center.
time dosin't work for me ether but date dose.
my menu is like that to but i think it's supost'a be right  ???
Title: Re: Sansa Fuze+
Post by: pamaury on December 02, 2011, 05:35:30 AM
If you read the thread, you'll see that RTC is not implemented yet. There is indeed a problem with the keymap, I did a battery bench and was unable to escape the WPS screen ! For information: the battery bench lasted ~10h which is not so bad since no power optimization is done (I'm working on it). I'll try to implement micro-sd support asap as well as RTC. As for the radio, there is still a great deal of mystery, I don't really know which it doesn't work.
Title: Re: Sansa Fuze+
Post by: metaphys on December 02, 2011, 06:44:14 AM
seems I still have some work to do on keymaps then.  :)
The left right thing is to be consistent with rockbox standarts. The cancel action used to be: back, left, power. Since I change power to alternative lock, there is no alternative cancel for some menu...
Pamaury: What kind of file did you used for the test? I didn't find this power test menu how to get there?

Post Merge: December 02, 2011, 06:47:21 AM
the manual compiles but I still need to map the key for it!  >:( I think I will write something to have it made automaticaly from the firmware keymap
Title: Re: Sansa Fuze+
Post by: pamaury on December 02, 2011, 06:48:47 AM
The problem is not only consistency: I just can't escape the WPS screen for example, that's not consistent ;) But yes, left is back for cosnistency in some places, that's pretty natural. To do the battery bench, we have a standard procedure: set repeat to all, start playing an album which doesn't fit the audio buffer (>100Mb should do here, I hope it was the case :)) at full battery and run the battery_bench plugin. It monitors the battery and logs everything to a file.

EDIT: I forgot to update so in fact the keymap was probably correct. Sorry.
Title: Re: Sansa Fuze+
Post by: metaphys on December 02, 2011, 06:52:15 AM
ok to escape WPS you can use cancel on back button (short press and release because else it's the recorder !) or long press on play (but this is stopping music)
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 02, 2011, 08:14:59 AM
Long press on back is the recorder? Neat once it's implemented. Thanks for confirming that the keymap is supposed to work that way it seemed odd coming from the OF and other players.
Thanks for all the work you two have done!
Title: Re: Sansa Fuze+
Post by: milonga on December 02, 2011, 01:10:55 PM
It seems that seeking (fast forward / rewind) is broken in version r31110.

While holding the right or left button I see the correct double arrows in the lower right of the display.
Playback stops, but the time indicators don't change.
When I release the button, the icon returns to the single arrow and playback continues at the exact same position.


Title: Re: Sansa Fuze+
Post by: claudiocpr on December 02, 2011, 01:45:37 PM
hello,

at the moment is it possible to create voice file for sansa fuze+? can you create it for download?

Title: Re: Sansa Fuze+
Post by: metaphys on December 02, 2011, 01:55:34 PM
It seems that seeking (fast forward / rewind) is broken in version r31110.

Yeah I've got that too... It must be related to rockbox core...

at the moment is it possible to create voice file for sansa fuze+? can you create it for download?

I don't know because I'm new to rockbox but I don't think that voice file are player specific, are they?
Title: Re: Sansa Fuze+
Post by: bluebrother on December 02, 2011, 04:09:02 PM
at the moment is it possible to create voice file for sansa fuze+? can you create it for download?

I don't know because I'm new to rockbox but I don't think that voice file are player specific, are they?

Voice files are player specific, and you can create voice files for the Fuze+ with the latest Rockbox Utility. Since support for the Fuze+ in Rockbox Utility is not considered complete (you can't install the bootloader) you need to enable disabled devices in the configuration dialog to use it. Apart from that it works.
Title: Re: Sansa Fuze+
Post by: buckminster on December 02, 2011, 07:12:39 PM
I have yet to make voice menus work with my Fuze+. I've used a number of daily builds and have been using the latest RockboxUtility on Ubuntu 11.10 (32-bit) to create the voice file. I can make .talk files for directories for the Fuze+ that work fine. Yes, Voice Menus is turned on and yes, there is an english.voice file in the langs directory. I've successfully created voice files before for my Sansa e260R following the same steps.

Anyone else get Voice Menus to work with the Fuze+? If so, could you make your english.voice file available for others to try?
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 03, 2011, 02:48:06 PM
Meta: change in my sensi values. (just my preference and something interesting)
pref: 8-11 9/10 being used more because:
detection when finger is above pad (but not touching): anything above or = to 9 or 10. Makes using it one handed hard for me. 10 seems to be my sweet spot, but I'll experiment as time goes on.
Title: Re: Sansa Fuze+
Post by: metaphys on December 03, 2011, 04:21:28 PM
they're been a problem with patch I made: i don't know why it isn't in the three as it should be (there is a light modification on some value, wich is the reason why we have the problem of fw/rw. I'll talk with pamaury. Thank for having reported it!
Title: Re: Sansa Fuze+
Post by: jimmyjboy on December 04, 2011, 05:18:00 PM
when i try to sync rockbox utility with my fuze plus it says "The following errors occurred:
No mountpoint given
You need to fix the above errors before you can continue."

( i have checked the "show disabled targets" box)
Title: Re: Sansa Fuze+
Post by: saratoga on December 04, 2011, 05:25:16 PM
when i try to sync rockbox utility with my fuze plus it says "The following errors occurred:
No mountpoint given
You need to fix the above errors before you can continue."

( i have checked the "show disabled targets" box)

That means you didn't point rockbox utility at the drive letter (windows) or mount point (unix) corresponding to your player.  In the future, please remember that this is a development thread, so questions about rockbox and its tools do not belong here, but rather in the support forums.
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 04, 2011, 06:05:14 PM
is there a key to hold/way to make the player not go into USB keypad mode? So I can listen too it while it's charging off my Wii?
Title: Re: Sansa Fuze+
Post by: saratoga on December 04, 2011, 06:10:23 PM
is there a key to hold/way to make the player not go into USB keypad mode? So I can listen too it while it's charging off my Wii?

Unless somethings broken, holding any key on USB insert should do that.
Title: Re: Sansa Fuze+
Post by: halonachos117 on December 04, 2011, 07:29:01 PM
Why does my player seem to skip a bunch of files when I try to play them? I can make it stop temporarily by pressing the pause button, and then unpause and everything will play fine, including the ones skipped. Any chance of this getting fixed? I know you guys have a lot on your table, such as it is, but I hope this gets cured soon.
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 04, 2011, 08:57:01 PM
thanks Saratoga wasn't sure if it was keymap specific or not.
Title: Re: Sansa Fuze+
Post by: metaphys on December 05, 2011, 01:46:32 PM
@halonachos117
What format are you using? I have seen this problem with mpc and flac: http://www.rockbox.org/tracker/task/12429
Title: Re: Sansa Fuze+
Post by: halonachos117 on December 05, 2011, 02:29:06 PM
I'm using r31113-111202. I don't use mpc or FLAC, though. I've mostly been using m4a (aac hev2, encoded by Nero AAC, two-pass mode), and ogg/vorbis (encoded by the version of aoTuv included in the latest FreAc). MP3's seem to be unaffected, although I've only tested one MP3. The same goes for WMA.
Title: Re: Sansa Fuze+
Post by: metaphys on December 05, 2011, 02:40:30 PM
yes MP3 are ok here to. Further questions:
- how big are those file you use and how big the dynamic list generated when you read them ?
- No panic till now (white screen of the death   ;D ) ?
- what if you disable directory cache (settings > system > disk) ?
Title: Re: Sansa Fuze+
Post by: halonachos117 on December 05, 2011, 02:54:41 PM
I do not get the White Screen of death, but my files "play" so fast, the thing skips through an entire playlist within seconds. I usually decide out-of-the blue to play one particular album or another, so I make a playlist out of just that album. I will try disabling the cache, though and see if that helps.

I suddenly wonder if it's a problem with this particular port of with rockbox's own codecs.
Title: Re: Sansa Fuze+
Post by: metaphys on December 05, 2011, 05:32:46 PM
Yeah it's very similar to what I call non-playing phase in my bug report
for now we think its fuze+ specific for pamaury doesn't have the problem on his clip+

In order to avoid to flood the thread, further discussion about this should go on the bug's page I guess  ::)
Title: Re: Sansa Fuze+
Post by: halonachos117 on December 05, 2011, 07:37:00 PM
Wow... I just realized that this is the same bug report that "gama" reported on page 13! I even replied to that! :o

Sorry for reporting the same bug again. :-[
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 05, 2011, 08:39:23 PM
Now that that's sorted out: it is normal to gray/white screen when I first push power for about .3 a second then go to the rockbox logo then proceed as normal? It happens since I install RB but not when booting OF.
Title: Re: Sansa Fuze+
Post by: qiaozi on December 05, 2011, 09:17:57 PM
The gray screen happens on mine as well, I have been looking at the LCD driver code to see what is causing it, I think it is an initialization value when first configuring the screen.

Also is anyone able to charge their battery? I can't get any charging even if I boot the OF.
Title: Re: Sansa Fuze+
Post by: halonachos117 on December 05, 2011, 09:48:09 PM
I can charge the battery in the OF just fine. Perhaps your cord is damaged? Or perhaps you managed to break the part of your Fuze+ the cord plugs into? Try another cord and see if it works. If you are using a computer to charge, try another computer. The same goes for if you are using a USB charger.

Also, what OS are you running? More importantly do you have the Windows Media Player 10 or higher (assuming you have Windows)? If you have a older version of Windows Media Player, don't have Windows Media Player at all, or are not running Windows, you may need to change the default USB mode in the OF to MSC (Mass storage Class). A Windows OS with WMP 10 or higher will be necessary to use the other mode (MTP).
Title: Re: Sansa Fuze+
Post by: jimmyjboy on December 05, 2011, 11:44:19 PM
I had the "no charging" problem to for a wile to but then i realized you have to not only boot the OF you also have to hold the volume down button when you plug in the cable.  ;D
Title: Re: Sansa Fuze+
Post by: buckminster on December 06, 2011, 12:20:51 AM
Now that that's sorted out: it is normal to gray/white screen when I first push power for about .3 a second then go to the rockbox logo then proceed as normal? It happens since I install RB but not when booting OF.

I'd be more concerned about other functionality (FM radio, SD card support, etc.) than this, but yes, I have it, too.
Title: Re: Sansa Fuze+
Post by: halonachos117 on December 06, 2011, 01:37:04 AM
I had the "no charging" problem to for a wile to but then i realized you have to not only boot the OF you also have to hold the volume down button when you plug in the cable.  ;D

Unless, of course you use a USB wall adapter, in which case just boot into the OF.
Title: Re: Sansa Fuze+
Post by: pamaury on December 06, 2011, 04:45:13 AM
Hello,
I know lots of you have been waiting long for this port but please do not spam this thread, it's about the Fuze+ development only. If you have bugs, please add them on the tracker (flyspray). Here are the known problems that do NOT need to be brought to my attention again, I'm well aware of them:
Thanks for your patience
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 06, 2011, 09:04:39 AM
Sorry Pamaury! I'll check on the CRT-like effects later today.
Pamaury if I ran a debug build would that help with getting the 2nd screen sorted? Let me know and I'll try and figure out how to compile one now that my compile set up is working.
CRT screen is GONE as of r31158 I don't know what changed but it's gone! EDIT: was gone after plugging USB then updated but power cycle brings it back.
BTW Thank you Pamaury and meta for doing this! I've been using meta's patch build then trunk right after it got implemented exclusively (except for charging) for over a week now with basically no problem except for me forgetting the radio isn't implemented. :P So THANK YOU both!
Meta: don't trust my sensi values right now I'm gonna keep using it and find my good ones.
Title: Re: Sansa Fuze+
Post by: metaphys on December 07, 2011, 12:10:55 PM
So just to be clear again:
Anything related to touchpad go there: http://www.rockbox.org/tracker/task/12405
Anything related to playback issues (undefined instruction, data abort, file skipping) go there:  http://www.rockbox.org/tracker/task/12429
Any other bug has to be reported  here: http://www.rockbox.org/tracker/
Any other question regarding rockbox in general goes on the forum (but not in this thread  ;D )
Any info about the port's development (things you want to do, things you founded how to do, etc) come in this thread
Title: Re: Sansa Fuze+
Post by: Rarog on December 07, 2011, 06:14:34 PM
CRT screen is GONE as of r31158 I don't know what changed but it's gone! EDIT: was gone after plugging USB then updated but power cycle brings it back.
Hm... I can't seem to be able to reproduce the non-flickering mode, not by plugging in or out, not by updating to newer build. How exactly did you do it and are you able to reproduce it by yourself?
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 07, 2011, 08:44:41 PM
I haven't tried yet but I KNOW I saw it. If someone has the build 4 revisions after when meta's pacth hit trunk can you send me the .zip? (or is there a way to findout what revision you had on before the current one so I know exact r?) Plugin in/out doesn't work. Here is EXACTY what I did:
1 hour of listening to music in rockbox at 55 brightness.
Pluged in loaded new revision and a podcast
pluged out then hit select to yes update
it (soft?) rebooted and I had no lines. I let backlight fade out then made it come in and still nothing
I was using a custom background so thought it might have been tricking me so switched to the cabbie background still no lines switched to my background again then
went to now playing and then powered off and back on and was saddened to see lines. :(
Also I noticed it was (seemingly) darker without lines.
Title: Re: Sansa Fuze+
Post by: Rarog on December 08, 2011, 03:41:15 AM
So you need revision r31133 and r31137/r31138? I could provide you these.

My idea was to check the debug screen for voltage setting and compare it to the situation when the CRT lines are there.

EDIT:
And in any case it would be good if we hat a way to reproduce this case to see, what's causing and what's removing it.

EDIT2:
r31133 http://www.megaupload.com/?d=NE8GSA20
r31138 http://www.megaupload.com/?d=R36VD23T
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 08, 2011, 02:43:25 PM
did it again!
this time going to r31141

here are values without lines:
r31141
first screen:
480000
24000
24000
96000
480000
261818
130909
130909
24000
battery mv: 3872 jumping to something else for a millisecond but don't know what.
screen after battery:
VDDD: 1550
VDDA: 1750
VDDIO: 3300
VDDMEM: 2300
freg: 0
EDIT: All values appear the same on my player with lines

Here's how to do it:
plug in WHILE RB is booted up
drop new revision on
select YES to update or w/e it says (important part!!!)
lines are gone as long as power isn't offed
Title: Re: Sansa Fuze+
Post by: Rarog on December 08, 2011, 06:01:01 PM
Very strange... I think it should be diged into the code to see, what's done in a different way when doing a soft reboot.
Title: Re: Sansa Fuze+
Post by: pamaury on December 10, 2011, 05:55:03 AM
Soft reboot (aka RoLo) is inherently an unsafe feature, the code tries to not assume too many things on the hardware state but you can't tell for sure if the initialization will be correct or not after RoLo.
Title: Re: Sansa Fuze+
Post by: Rarog on December 10, 2011, 12:52:11 PM
But it seems, that some commands are called, which cause the hardware voltage changes/settings, which apparently fix the behavior of the 2nd LCD.
Title: Re: Sansa Fuze+
Post by: metaphys on December 11, 2011, 01:25:01 PM
test, confirm, other infos, would be appreciated about those 3 bugs. They seem to be Fuze+ related:
http://www.rockbox.org/tracker/task/12446
http://www.rockbox.org/tracker/task/12447
http://www.rockbox.org/tracker/task/12442

(of course comment on those are going on those pages)
Title: Re: Sansa Fuze+
Post by: ddscentral on December 15, 2011, 09:04:20 PM
The SD card seems to work with the latest build (no USB support yet though, still need OFW to access SD from Windows).

Also, the player does not seem to detect USB disconnects and stays in USB mode if you plug and unplug USB cable when in Rockbox (everything is OK from the bootloader).
Title: Re: Sansa Fuze+
Post by: pamaury on December 16, 2011, 04:45:41 AM
Hello,
all comments on the CRT effect or lcd problem go here: http://www.rockbox.org/tracker/task/12457 (http://www.rockbox.org/tracker/task/12457) and all comments on SD problem with USB go here: http://www.rockbox.org/tracker/task/12458 (http://www.rockbox.org/tracker/task/12458).
Please do not spam this post anymore, and post bug reports in general rather than responding to this thread.

Note that the SD card is suppose to work with USB, so it if does NOT work, please post on FS#12458 and not here.
Title: Re: Sansa Fuze+
Post by: metaphys on December 16, 2011, 10:22:57 AM
ok so it's raining bootloader  ;D
I've updated the wiki with a link to the third version...
Title: Re: Sansa Fuze+
Post by: metaphys on December 19, 2011, 05:37:52 PM
bootloader v4 on the wiki page...

Post Merge: December 19, 2011, 05:56:35 PM
I've made a little hack on the touchpad mapping. I find it more usuable... Pehraps this should go in the tree if there is a consensus... let  me know... comment and patch and description there -> http://www.rockbox.org/tracker/task/12405#comment41870
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 20, 2011, 09:13:59 AM
do I need to update BL? What's changed?
Title: Re: Sansa Fuze+
Post by: metaphys on December 20, 2011, 09:22:33 AM
V2: fix 2nd screen problem
V3 : sd support
V4 : better sd support
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 20, 2011, 02:33:40 PM
V2 what did it add?
I don't use SD so no need for me yet.
Title: Re: Sansa Fuze+
Post by: metaphys on December 22, 2011, 10:50:41 AM
new bootloader-V5 on wiki: correct a few error on sd (related to a typo in the signal handling sd)
however there is still a bug that rarog is activily working on. So I guess we can expect new bootloader update soon. So except if you want to help debbuging it is probably not worthing to install this.
Title: Re: Sansa Fuze+
Post by: pamaury on December 25, 2011, 06:29:29 AM
I have implemented power management so with the latest SVN it should correctly charge over USB. I'm currently experimenting with the implementation of core_sleep to increase the battery life, I'm doing a battery bench and although it is not finished yet, it will probably last for 16h. I'm wondering if someone has tried to benchmark the OF battery life ? (I'm not interested in the OF claim since these are rarely accurate)

EDIT: the battery bench is finished, it lasted 16h40 but without the rtc it's not too precise. However it causes the screen to flicker, I'll try to see if using the pwm to control backlight gives better result.
Title: Re: Sansa Fuze+
Post by: metaphys on December 25, 2011, 07:54:09 AM
no and I don't really know how to make some test because basicly there are no logging of power value... I guess we could ask the user on sansa forum.

Post Merge: December 25, 2011, 08:50:17 AM
according to this site they tested 20h58 with mp3
http://www.expertreviews.co.uk/mp3-players/1280728/sandisk-sansa-fuze/specifications
Title: Re: Sansa Fuze+
Post by: saratoga on December 25, 2011, 12:35:22 PM
To test the OF, set it to repeat and record the audio with a PC. Open the output when it dies and see how long it lasted.
Title: Re: Sansa Fuze+
Post by: kumy on December 25, 2011, 03:22:35 PM
I've just opened 2 bugs (don't know if they are Fuze+ specific):

FS#12483 - [Fuze+] Terribly unpleasant sound on startup
http://www.rockbox.org/tracker/task/12483

FS#12484 - [Fuze+] Shuffle doesn't works when playing tracks from "Files"
http://www.rockbox.org/tracker/task/12484
Title: Re: Sansa Fuze+
Post by: metaphys on December 26, 2011, 01:10:48 PM
Bootloader V6 availlaibe: core sleep implemented = up to 6 hour battery life improvement

Post Merge: December 26, 2011, 01:28:36 PM
A little update have been made on the touchpad:
- no more 2 finger touch
- no more direct link to recorder from WPS
- no more hotkeys in list

this to improve usability when pressing back key
Title: Re: Sansa Fuze+
Post by: JaySeeJC on December 26, 2011, 11:16:37 PM
I know this is a little off topic but i'm not too sure where else to put it.

I have recently put rockbox on my fuze+ and am wondering how to access the files on my SD card. I have read that support for the SD slot just recently got implemented so I'd like to be able to use mine as i really hate the original fw on the device and the only reasons i use it anymore are for the radio and SD access

Sandisk MicroSDHC 8GB

what else is there to say? it doesn't show up in System -> Debug -> View disk info or System -> Debug -> View partitions

help?
Title: Re: Sansa Fuze+
Post by: ddscentral on December 27, 2011, 12:15:18 AM
I know this is a little off topic but i'm not too sure where else to put it.

I have recently put rockbox on my fuze+ and am wondering how to access the files on my SD card. I have read that support for the SD slot just recently got implemented so I'd like to be able to use mine as i really hate the original fw on the device and the only reasons i use it anymore are for the radio and SD access

Sandisk MicroSDHC 8GB

what else is there to say? it doesn't show up in System -> Debug -> View disk info or System -> Debug -> View partitions

help?

It shows up in System -> Rockbox Info.
Use Files -> <MMC1> to access the SD contents.
Title: Re: Sansa Fuze+
Post by: JaySeeJC on December 27, 2011, 09:44:15 AM
I know this is a little off topic but i'm not too sure where else to put it.

I have recently put rockbox on my fuze+ and am wondering how to access the files on my SD card. I have read that support for the SD slot just recently got implemented so I'd like to be able to use mine as i really hate the original fw on the device and the only reasons i use it anymore are for the radio and SD access

Sandisk MicroSDHC 8GB

what else is there to say? it doesn't show up in System -> Debug -> View disk info or System -> Debug -> View partitions

help?

It shows up in System -> Rockbox Info.
Use Files -> <MMC1> to access the SD contents.


It's not showing up there.
Title: Re: Sansa Fuze+
Post by: ddscentral on December 27, 2011, 10:58:10 AM
I know this is a little off topic but i'm not too sure where else to put it.

I have recently put rockbox on my fuze+ and am wondering how to access the files on my SD card. I have read that support for the SD slot just recently got implemented so I'd like to be able to use mine as i really hate the original fw on the device and the only reasons i use it anymore are for the radio and SD access

Sandisk MicroSDHC 8GB

what else is there to say? it doesn't show up in System -> Debug -> View disk info or System -> Debug -> View partitions

help?

It shows up in System -> Rockbox Info.
Use Files -> <MMC1> to access the SD contents.


It's not showing up there.

Strange. My 32GB Kingston works fine with revision r31450.
What revision are you using ? Have you tried building the latest source from SVN ?
Title: Re: Sansa Fuze+
Post by: JaySeeJC on December 27, 2011, 11:13:24 AM
I'm using the latest source. just compiled last night.The only thing i didn't compile locally was the bootloader. I downloaded the v6 this morning after seeing it was upgraded. would that make any difference?
The only other thing i can think of is that the hardware is a little beaten up. but the card works perfectly with the original firmware...
Title: Re: Sansa Fuze+
Post by: buckminster on December 27, 2011, 08:56:26 PM
Are you sure that the bootloader installed? Is there still a firmware.sb at the root of the fuze+? Did you see the Sansa "Updating Fuze+" screen?
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 27, 2011, 09:24:35 PM
Is there still a WPS hotkey? (SVN update list makes it look like no.) If not why still have a menu item? If yes what is it?
Title: Re: Sansa Fuze+
Post by: metaphys on December 28, 2011, 07:30:14 PM
the wps hotkey is still availlaible (long press on bottom right)
the tree hotkey has been removed
what do you call menu item?
Title: Re: Sansa Fuze+
Post by: alienkid10 on December 29, 2011, 09:56:12 AM
settings menu item for the file browser hotkey is still setable even though it's gone.
Title: Re: Sansa Fuze+
Post by: metaphys on December 29, 2011, 05:11:25 PM
ah yeah I don't think I can get it out

Post Merge: December 29, 2011, 09:24:49 PM
those interrested on having volume while keys are locked should have a look at the patch I made:
http://www.rockbox.org/tracker/task/12495

It's pretty out of the rockbox's standarts, so it probably never be in the tree, you will have to compile to use it

Post Merge: December 29, 2011, 09:27:39 PM
minor update on the bootloader - V7: print its version on boot
Title: Re: Sansa Fuze+
Post by: JaySeeJC on December 31, 2011, 07:14:57 PM
Are you sure that the bootloader installed? Is there still a firmware.sb at the root of the fuze+? Did you see the Sansa "Updating Fuze+" screen?

I am 100% certain the bootloader installed. the firmware.sb was deleted from the root and i saw the "Updating Fuze+" screen. I'll try installing the v7 firmware when I get home on sunday.
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 01, 2012, 08:40:40 AM
Will the BL be updated if Sandisk ever releases a new firmware version for Fuze+ so it has the latest OF? (I know not a concern to many.)
Title: Re: Sansa Fuze+
Post by: metaphys on January 01, 2012, 10:50:20 AM
I don't think that I will release bootloader anymore. Rockbox Utility is ready to patch whatever Original Firmware they will release with the RockBox bootloader.
All we need is to have RockBox bootloader on the server. That could take a week because the people managing the server seems to be in holidays. Manual is almost ready
Title: Re: Sansa Fuze+
Post by: bluebrother on January 02, 2012, 06:07:42 AM
All we need is to have RockBox bootloader on the server. That could take a week because the people managing the server seems to be in holidays. Manual is almost ready

Just to avoid confusion: this is not entirely correct. While it's a prerequisite to have the bootloader on the download server for Rockbox Utility to install it we also need to get the installation support into Rockbox Utility in -- currently it's a patch on the tracker. I'll try to get around doing this soon, but as of now neither the latest released Rockbox Utility nor an svn version could do the installation.
Title: Re: Sansa Fuze+
Post by: evemir on January 02, 2012, 06:27:07 AM
Is it be possible to disable click sound when keys are locked? This is pain in the *** because the touchpad is so sensible that it activates even inside a pocket...
Title: Re: Sansa Fuze+
Post by: metaphys on January 02, 2012, 08:52:05 AM
oups right I'm going a bit too quick on this one!  ;D

Post Merge: January 02, 2012, 08:53:14 AM
@evemir:
click sound should'nt be activated by default
Title: Re: Sansa Fuze+
Post by: Eridyne on January 02, 2012, 07:04:21 PM
On a (vaguely) similar note to evemir's post, I find that, due to the high sensitivity of the touchpad on the fuze+, it does indeed register touch inside one's pocket fairly consistently, and that does not do delightful things to its battery life, thanks to the activation of the backlight repeatedly, often on intervals shorter than the timeout.

My current imperfect workaround is just to have a very short timeout and a low brightness setting, but this can be inconvenient in its own right when I'm interested in doing something in brighter environments and/or taking my time perusing music.

Is there any other workaround? Though I don't recall any such function, is there a way to set a separate time-out and/or brightness when the keys are locked? Or perhaps the unit should simply not respond to anything but the lock function, even in terms of the backlight?

I'm not opposed to poking at the source, but as I'm utterly unfamiliar with it and am not much of a coder, I have doubts as to my ability to accomplish anything....so I figured I might as well ask first.
Title: Re: Sansa Fuze+
Post by: metaphys on January 02, 2012, 07:13:36 PM
hum!!  :-\ Very good point! I have no Idea but that definitively worth a try! I too busy with the manual/plugin keymaps right now but I find the idea really interressant
Title: Re: Sansa Fuze+
Post by: Eridyne on January 02, 2012, 07:17:11 PM
Tis just a thought - I know it's more of a general feature, but out of all the players I've used rockbox on, this one alone has issues with burning up way too much battery life with constantly detecting touches and turning the screen on.

I rather think it's quite low priority, though. Would be convenient, but isn't a serious issue.
Title: Re: Sansa Fuze+
Post by: pamaury on January 03, 2012, 04:23:33 AM
I am a bit surprized by what you say since the fuze+ has a capacitive touchpad so it's not sensitive to pressure. The only way I could think about false activation in a pocket would be that it detect your skin.
Unfortunately I can't think of a perfect solution. Making the device inactive while locked is not an option, reducing the touchpad sensitivity while locked seem feasible although I'm unaware of such a mechanism in rockbox so it would specific to this target.

The battery life is something complicated, it's not only related to backlight and touchpad. Furthermore, we are not that bad with approximately 16h of playback. It's just that there is still some work to do to reduce power consumption when possible but that requires time.
Title: Re: Sansa Fuze+
Post by: Eridyne on January 04, 2012, 03:15:17 AM
I was a bit surprised as well that it activated, as I'm aware it's not sensitive to pressure. It does seem, however, to be sensitive enough to detect skin through any thin material - including your average jeans pocket or thin knit gloves. It wouldn't be a problem if I had other pockets, or put the fuze in a jacket pocket, I suppose, but it seems to always get dropped in my jeans pocket, out of habit, and I don't always have a jacket on.
Reducing the sensitivity when locked would be a good idea, I think, better than any of my suggestions, but I imagine it would be quite a pain to implement.

Battery life is always complicated, I agree. I was merely pointing out, in my earlier post, that having the backlight on much of the time doesn't help the battery life, not trying to imply that it was the primary deciding factor.

EDIT: Out of sheer curiosity, just tried using the touchpad with a bit of my t-shirt wrapped around my finger. Works...surprisingly well.
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 04, 2012, 08:25:17 AM
Meta: I can now say I definitely do not like 13 as the sensi value it fells way to sensitive, mostly I've been using 10 sometimes 11 so I for one would like a permanent setting for sensi somehow (if that's possible).
Title: Re: Sansa Fuze+
Post by: metaphys on January 04, 2012, 08:58:29 AM
possible certainly but for the moment I have to much to do with other stuff (keymaps, manuals...) those are pretty easy stuff to  do but take a lot of time, and as no one is helping well... this is going to take a lot of time...
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 04, 2012, 10:02:06 AM
No problem simply reporting in like you wanted. Thank you both for doing this! Unfortunately I don't have time to learn to help with the manual since I'm wrapped up in my school and Boy Scout stuff.
Thanks to you both again!
Title: Re: Sansa Fuze+
Post by: megal0maniac on January 04, 2012, 04:46:54 PM
Hey all
I'd like to contribute, but I'm not sure about how much detail I need to provide.
I got hold of a Fuze+ 8gb and rockboxed it, but it's extremely buggy.
(I'm not moaning, I want to help if I can)

Among the issues found are:
Will update when I have more specific details on other problems.

Question: How difficult would it be to change the mouse HID mode to use the touchpad as an actual touchpad? Support for gestures is already implemented in the firmware.
All that needs to be done is for the relative cursor position to change depending on position on touchpad as opposed to button presses, or at least my limited knowledge leads me to think...

RE touchpad sensitivity, the touchpad works even with the cover which comes with the device. I can even make it work with my finger 1 or 2mm away.

Is the Fuze+ destined to be amongst the stable builds, or was buying one instead of the Clip Zip a stupid decision?
Title: Re: Sansa Fuze+
Post by: metaphys on January 04, 2012, 05:06:24 PM
Hello,

Quote
Recording doesn't work
FM Radio doesn't work
Those are not bug - just not fully implemented yet.

Please do read the port's page on the avancement

Quote
MicroSD card doesn't show up in Windows
If you want to help on this go there this has been reported: http://www.rockbox.org/tracker/task/12458

Quote
MPEG Player says "Cannot create buffering thread" upon attempt to playback video, including known supported files
This has already been reported in this thread but it would be good to have a bug report as a reminder - feel free to open one there: http://www.rockbox.org/tracker/index.php (don't forget the field player)

Quote
Garbage on music playback (sometimes) Restart usually fixes it, haven't been able to pinpoint steps to reproduce. Music plays up to 50% faster when this happens, so it sounds like samples are being missed. Looks as though buffer is full when this happens, but don't have confirmation. Will create recording upon request.
this has been reported by rarog, I do also experience it but this is very rare on my device (pehraps because I use special codec) Feel free to add a new bug report on Flyspray, I don't think that there is already one.

Quote
Question: How difficult would it be to change the mouse HID mode to use the touchpad as an actual touchpad? Support for gestures is already implemented in the firmware.
All that needs to be done is for the relative cursor position to change depending on position on touchpad as opposed to button presses, or at least my limited knowledge leads me to think...
For what I know (not much  :-X) it is a little more complicated but some work has started in this direction in order to have a proper way to test/debug gesture

Quote
Is the Fuze+ destined to be amongst the stable builds

All player are destined to be stable. I t just depend on the work you want to do on it...
Title: Re: Sansa Fuze+
Post by: megal0maniac on January 04, 2012, 06:02:11 PM
FM RADIO
I have read the port status page, but I assumed that the FM radio simply wouldn't tune, not that it would freeze the player.

MOUNTING IN WINDOWS
The MicroSD card issue I think is different to the one in 12458. It is Windows specific and occurs both from the bootloader as well as from within Rockbox. Accessing the SD card is only possible if you hide the internal drive, it won't see both otherwise.
Both the internal memory as well as the card show up using my Clip+ on the same computer.

VIDEO PLAYBACK
Task opened here (http://www.rockbox.org/tracker/task/12510)

GARBAGE AUDIO
Will look into this and open a task if necessary. Any suggestions on technical debug info to look for while experiencing this behaviour?

HID
On the HWInfo screen, one of the pages shows you exactly where your finger is on the touchpad and recognises gestures. So the information is already there, it's just a case of interpreting it correctly and sending it to a computer.
Code: [Select]
while (finger down)
cursorPos = value relative to measured coords upon finger down
That's how it works in my head, reality might differ...

This can't be stable soon enough :)
Title: Re: Sansa Fuze+
Post by: metaphys on January 05, 2012, 07:42:09 AM
Quote
HID
On the HWInfo screen, one of the pages shows you exactly where your finger is on the touchpad and recognises gestures. So the information is already there, it's just a case of interpreting it correctly and sending it to a computer.
Yes but actually hid implementation works with button. So the way it work's now is: touchpad driver convert absolut value into virtual button, button are passed to hid. hid control mouse. For what you are talking about to work, hid need to be rewrited... and this is clearly something not that urgent because the main point of hid is for device with remote control: you plug your device and use remote to control the computer. So except to piss off your friends saying: "hey look what my rockboxed device can do!"  (mandatory! ;D) I can't see no high priority in this.
Quote
MOUNTING IN WINDOWS
If you think this is something different then please open a new bug report

Quote
VIDEO PLAYBACK
thanks

Quote
Will look into this and open a task if necessary. Any suggestions on technical debug info to look for while experiencing this behaviour?
no idea, pamaury is doing the core implementation on the fuze+ you might find people on the IRC that could help

Title: Re: Sansa Fuze+
Post by: metaphys on January 07, 2012, 02:28:08 PM
new change today:
- pamaury add a thread that should solves the mpeg-plugin (videos)
- he also commited 2 patchs I made:  1) consistent and usuable keymaps on all plugin game
                                                           2) correct a little bug that was leading volume up key to be interpreted as power key
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 07, 2012, 03:09:30 PM
Mpeg buffering issue fixed but:
trying to play ele-dream 320x240 4:3 from mpegplayer page:
undefuned instruction at 5EE96BF0
that happened first time but now it gets to video area seems to play audio fine but video is fronzen AND only a tiny bit displays as a right triangle from bottom (left edge when held normally) of play btn to the top left screen edge. (top right when held normally)
Audio plays fine.
Title: Re: Sansa Fuze+
Post by: megal0maniac on January 07, 2012, 03:43:09 PM
Experiencing the same behavior wrt video playback.
Have commented with the details here. (http://www.rockbox.org/tracker/task/12510)
Didn't get the undefined instruction error though. Could be the bug reported when playing a different file format than the previous file. You shouldn't get this error after a fresh boot.
If you do, though, please let us know  :)
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 07, 2012, 03:49:22 PM
It was because I was listening to music before trying video, most likely. Will try to recreate later.
Title: Re: Sansa Fuze+
Post by: Raiden175 on January 10, 2012, 12:01:41 AM
Hello everyone. I come here with an issue that has recently occurred to my Sansa FuzePlus player. I was updating the rockbox files and boot loader. I do believe i also  deleted and re-added my music and ever since then when I attempt to add new files or such it does nothing. Also another think I noticed was when I boot into my OF it says "Database Error! Please format this device." Then a few seconds later it says "Your Sansa will shit down" which it does. I have tried reformatting it but it on windows but it says it is unable. Any Ideas what may have happened?

Sorry if I put this in the wrong place. Will make a new post if I am required to do so.
Title: Re: Sansa Fuze+
Post by: metaphys on January 10, 2012, 10:16:07 AM
it looks like an internal memory error. You could try to do a scan of the disk for error...
Title: Re: Sansa Fuze+
Post by: Raiden175 on January 10, 2012, 06:57:45 PM
I tried last night but still nothing. I ran Chkdsk and other programs on it.
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 12, 2012, 02:14:47 PM
sleeptimer doesn't off device. I had my "soft/slow" stuff on repeat with a sleeptimer for 2hrs and woke up to a dead battery instead of a player that slept like it was supposed to. Does SLT need BL>1?
Title: Re: Sansa Fuze+
Post by: pamaury on January 13, 2012, 04:49:04 AM
I don't know how the sleep timer works, I'll have a look.
I encountered a problem with audio yesterday: the Fuze+ would randomly in some files play garbage and then skip to the next file. I happened one every two of three files. I'm going to open a bug report if I can reproduce it. If you have seen this bug, please wait for the bug report and don't write it here
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 13, 2012, 09:53:48 AM
sleeptimer wouldn't have been a problem if I didn't have it set to repeat forever, but I do it that way since the list is shorter then 2hrs. Haven't seen that bug yet. Thanks for the hardwork!
Title: Re: Sansa Fuze+
Post by: RipCurl on January 13, 2012, 05:14:43 PM
is there still someone working on the mpeg player issue???
http://www.rockbox.org/tracker/task/12510 (http://www.rockbox.org/tracker/task/12510)

since megal0maniac described occurring playback bugs (which I can confirm), there hasn't been any further feedback about the current status.
Title: Re: Sansa Fuze+
Post by: saratoga on January 13, 2012, 05:16:55 PM
is there still someone working on the mpeg player issue???
http://www.rockbox.org/tracker/task/12510 (http://www.rockbox.org/tracker/task/12510)

Unless you are working on it, theres no need to ask about it here. 
Title: Re: Sansa Fuze+
Post by: pamaury on January 15, 2012, 08:07:44 AM
Hi all,
I'm sorry that the porting has been stalling a bit recently because I have a lot of work. Fortunately Jean-Louis Biasini is doing lots of stuff. We are also currently transitioning from svn to git so I will not commit killer features until the buildserver is back ;) However,
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 15, 2012, 08:34:27 AM
No need to be sorry you do this voluntarily! Sleep timer is still an issue  as of the last SVN revision. Again I give you guys both a big THANK YOU!

Meta: If it isn't too much work for you right now can you fix the text_editor keymap so we can add newlines? (AKA so we can get to the Line Options menu)

Thanks again guys!

PS: why is this still marked "unusable"? It's been rather useable for quite awhile now.
Title: Re: Sansa Fuze+
Post by: bluebrother on January 15, 2012, 11:21:30 AM
Rockbox Utility has support for the fuze+ thanks to Jean-Louis but we still don't have a bootloader file online

This is wrong -- there is a bootloader on the download server, and Rockbox Utility will happily install it. You need a recent build of Rockbox Utility though (the latest release 1.2.11 doesn't have bootloader support for the fuze+ at all). You can try a svn build if you want to (see my signature for a link or the sticky in the Rockbox Utility forum).

PS: why is this still marked "unusable"? It's been rather useable for quite awhile now.

Is that really important? Nobody did it, and as pamaury said we're in the transition to git, so some things will need to get sorted first.
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 15, 2012, 12:33:18 PM
PS: why is this still marked "unusable"? It's been rather useable for quite awhile now.

Is that really important? Nobody did it, and as pamaury said we're in the transition to git, so some things will need to get sorted first.
It's not but it doesn't get a place on the builds page as unsusable. I was just asking.
Title: Re: Sansa Fuze+
Post by: bluebrother on January 15, 2012, 04:37:58 PM
It's not but it doesn't get a place on the builds page as unsusable. I was just asking.

A player taking part in the builds page (i.e. the automated builds) is not related to the state of the port or what's displayed on the front page.
Title: Re: Sansa Fuze+
Post by: gama on January 16, 2012, 08:12:08 PM
Hi, just found another issue, there is something wrong with VGM (Sega Genesis) music, it doesn't play realtime, and i have to turn the player off cuz it gets unresponsive. I remember even on the fuzev2 they played fine.  Can anyone confirm this?
Title: Re: Sansa Fuze+
Post by: santatution on January 17, 2012, 11:31:21 AM
I'm also having an issue. Whenever I play Doom the game runs super fast. Does anyone know how to fix the game? Thanks.
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 17, 2012, 08:35:26 PM
Pamaury:  with the last build the SVN provides (r31646) sleep timer works. Maybe it didn't work before because I was in a plugin?
Title: Re: Sansa Fuze+
Post by: megal0maniac on January 22, 2012, 05:17:15 AM
@pamaury: When you get a chance, would it be possible to post more detail about the mpeg player issue on the tracker?
http://www.rockbox.org/tracker/task/12510
Title: Re: Sansa Fuze+
Post by: pamaury on January 27, 2012, 02:17:08 PM
I have some news: I finally moved the target to unstable. I fixed the yuv blitting and screen updating so mpegplayer should now work (I hope).
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 27, 2012, 05:41:25 PM
Cool. Will test later. Wish we could figure out what's making the CRT effect on screen 2. I'm still open to helping if you can tell me what to do.
Title: Re: Sansa Fuze+
Post by: milonga on January 29, 2012, 02:51:45 PM
I have some news: I finally moved the target to unstable. I fixed the yuv blitting and screen updating so mpegplayer should now work (I hope).

Hello pamaury,
I don't know if it has something to do with your screenupdating and blitting fix, but in version c5f772c-120129 I get a strange display behaviour.

A small horizontal part of the very bottom of the screen (that with the play button) appears there where usually the title of the actual and the next song are displayed. So the horizontal bar appears at 3 parts of the screen.
http://imageshack.us/photo/my-images/252/rockboxscreen.jpg/
If that happens, the music still plays, but the buttons aren't working anymore and the display gets no longer updated.
To get rid of the behaviour I have to press the power button a very long time till the player is forced to shut down. After switching on again the player still behaves "mysterious". Another "normal" restart gets back to normal behaviour.

I can't provide a method to reproduce the error, but it happens often. I've got the impression that it may be related to the length of the title text.


Thanks a lot for your time!
Title: Re: Sansa Fuze+
Post by: pamaury on January 30, 2012, 03:35:19 AM
Hum, that's unexpected to say the least. Can you do a build to check if this bug has to do with my blitting fix ? I have a theory about this bug but I need to test it to be sure.
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 30, 2012, 08:09:48 AM
I can confirm that bug in 94177e6. In addition (at least) bockblox keymap has been reverted to before meta's fix? Pamaury how far back should I build to?
Title: Re: Sansa Fuze+
Post by: pamaury on January 30, 2012, 08:23:42 AM
I did not revert any keymap and not even changed one recently. Which commit are you referring to by 94177e6 ? Is it this one: http://git.rockbox.org/?p=rockbox.git;a=commit;h=d32891fa5940bb4eda47e513c2c7d0be27f38ecb (http://git.rockbox.org/?p=rockbox.git;a=commit;h=d32891fa5940bb4eda47e513c2c7d0be27f38ecb) ?
Title: Re: Sansa Fuze+
Post by: alienkid10 on January 30, 2012, 10:02:33 AM
That's my current revision the 94177e6. Odd well the keymap is definitely reverted
now:
back=restart up=rotate play=drop to bottom
left=left center=rotate right=right
bot left=nothing down=faster drop bot right=nothing
which is the old keymap in rockblox.
Title: Re: Sansa Fuze+
Post by: megal0maniac on January 30, 2012, 04:36:18 PM
Running 54044fd, have not been able to reproduce the issue in the WPS (but I'm almost certain that this has happened to me before the mpeg player issue was resolved - while we were still on SVN)

Just a note, the issue with flickering display after booting with USB power still exists. Goes away after a power cycle.
Title: Re: Sansa Fuze+
Post by: pamaury on February 01, 2012, 09:00:14 AM
I have committed a potential fix for this screen issue, although I'm not sure that's the actual problem. I know the screen sometimes flickers, even on mine but I have absolutely no idea why. The only way to find the difference would be to implement an emulator which is a big task.
I have also find something useful related to sd handling. It seems the OF set a pin to 1 when the sd card was changed and the DB refreshed. Perhaps that's a way to avoid an OF DB refresh but I'm not sure how to use this.
Title: Re: Sansa Fuze+
Post by: alienkid10 on February 01, 2012, 12:58:11 PM
OF db wasn't refreshing for me before your patch so setting the pin doesn't seem to do anything unless it's something else I'm not understanding.  (in reference to ac4d648) Screen issue as in the patch of the WPS materializing where the (long) title is or the "CRT effect"? I'm gonna wait to apply ac4d648 until someone posts back saying it works, I don't really want to brick (might be being overly cautious but better that then bricked player).
Title: Re: Sansa Fuze+
Post by: pamaury on February 01, 2012, 01:06:28 PM
The pin clearly affects several things. I affects the OF when changing the SD card for example. But it also shutdowns some hardware, I'm pretty sure of it. In any case there is absolutely no risk.
The fix prevents blitting outside the screen but as I said I still have no idea for the crt effect (please read my post).
I also managed to make the radio work but it requires some changes in our radio code (I don't want to commit what would otherwise be a hack).
I did not manage the WPS screen spotted by megal0maniac so I can only hope it was something else (file system corruption ?).
Title: Re: Sansa Fuze+
Post by: alienkid10 on February 01, 2012, 01:34:14 PM
OK. I did read your post but didn't quite understand it. I'll chkdsk my MP3 player since I had the WPS issue too.
Title: Re: Sansa Fuze+
Post by: gama on February 01, 2012, 01:38:55 PM
Hi, i'm using daily build ac4d648-121201, and i get the same screen issue milonga reported.  I assume it's related to the text scrolling.  Because everytime i play a song with a *long* info string, for example a long title, the text starts scrolling and after a couple of seconds i can see the same screen issue as milonga. Controls don't respond anymore but the music keeps playing.
Title: Re: Sansa Fuze+
Post by: megal0maniac on February 01, 2012, 04:53:00 PM
WPS issue can be reproduced without fail with track names long enough to cause scrolling. Didn't try any particularly long filenames last time.

Post Merge: February 01, 2012, 04:59:31 PM
Also, I still have the problem with tracks playing too fast and getting garbage audio. It seems like a random issue and I haven't been able to faithfully reproduce the issue, but a power cycle does not fix it.
Will fiddle more tomorrow and record a sample clip.
Does anyone else experience this at times?
Title: Re: Sansa Fuze+
Post by: RipCurl on February 01, 2012, 05:23:54 PM
WPS issue can be reproduced without fail with track names long enough to cause scrolling. Didn't try any particularly long filenames last time.

Post Merge: February 01, 2012, 04:59:31 PM
Also, I still have the problem with tracks playing too fast and getting garbage audio. It seems like a random issue and I haven't been able to faithfully reproduce the issue, but a power cycle does not fix it.
Will fiddle more tomorrow and record a sample clip.
Does anyone else experience this at times?

I'm using 0f02da2-120201 and I can't confirm this sound bug.

nevertheless I have this strange display behaviour too

EDIT: most of my files are 320cbr and 16bit flac + a few 24bit flac
Title: Re: Sansa Fuze+
Post by: pamaury on February 01, 2012, 05:41:50 PM
Indeed, I can reproduce it with long names, thanks for noticing. That should help me hunt the bug !
Title: Re: Sansa Fuze+
Post by: megal0maniac on February 02, 2012, 04:08:36 AM
The WPS issue also presents itself when the track coming up has a long name.

Garbage audio
This is what I have. (http://www.mediafire.com/?z5qwk4oi6bloz7o)
For reference sake, the song is called Austere by The Joy Formidable.
There is no pitch change from the original.

To reproduce this issue, I play any of the songs from this album. The files themselves are fine and play everywhere else. (including Rockbox on my Clip+) The tracks are MP3 VBR, ranging from 170 - 200 kbps.

The strange thing, is that after you play one of these files, the phenomenon occurs with every other mp3 file you play afterwards.
The only way to fix it is to restart a couple of times (shut down properly, then turn back on) or I've found that it stops when playing a FLAC file.

I have gotten these "problem files" to play correctly on my Fuze+, but I'm not sure how.
This has been an issue since a build which was current in Early Jan.

Also, sometimes when playing FLAC, the player suddenly freezes.

Unfun :(

EDIT: Also, that spike on the left channel as the track starts is non existent in the file.
Title: Re: Sansa Fuze+
Post by: pamaury on February 02, 2012, 05:17:29 AM
I think I have fixed the WPS issue. Please test and report back. I will try to reproduce the sound issue but I haven't run into it so far.
Is it consistently reproducable ? Can you provide a file for us to test ?
Title: Re: Sansa Fuze+
Post by: megal0maniac on February 02, 2012, 06:39:10 AM
It seems to be, just by playing the file. Or any of the files from the album.
I just haven't been able to find out exactly how to make it go away.

I'm busy uploading a file, it lives at http://atinyhedgehog.za.net/03-the_joy_formidable-austere.mp3 :)
Left the filename intact just to be safe. Haven't had much time to play around.

Post Merge: February 02, 2012, 03:43:41 PM
WPS issue seems to be sorted. A little glitchy when the title first appears, but hardly anything that needs to be fixed.
What was wrong?
Title: Re: Sansa Fuze+
Post by: pamaury on February 03, 2012, 01:08:19 PM
The bug is briefly explained in the commit message: I used the data co-processor to copy some pixels but my implementation yields during the copy instead of busy waiting. And during that yield, another screen update might occur resulting in some registers of the lcd being changed before sending the data to the lcd. One solution could be to use a mutex but I preferred to simply replace the use of the co-processor by a call to memcpy.
Title: Re: Sansa Fuze+
Post by: qiaozi on February 03, 2012, 11:16:58 PM
I got an error compiling the bootloader:

~/project/rockbox/firmware/target/arm/imx233/sansa-fuzeplus/lcd-fuzeplus.c: In function 'lcd_init_device':
~/project/rockbox/firmware/target/arm/imx233/sansa-fuzeplus/lcd-fuzeplus.c:388: error: 'lcd_on' undeclared (first use in this function)


Had a look in the code, 'lcd_on' is defined as:

#ifdef HAVE_LCD_ENABLE
bool lcd_on; /* framebuffer-imx233.c */
#endif


But I cannot find anywhere in the code that defines HAVE_LCD_ENABLE. Is this set by the configure script?

EDIT:

Ignore the above post, I updated my source tree and the problem is gone now.
Title: Re: Sansa Fuze+
Post by: pamaury on February 05, 2012, 07:25:22 AM
The bootloader built has been fixed. But you normally don't need to build the bootloader, there is already a released version on our server.
Title: Re: Sansa Fuze+
Post by: qiaozi on February 05, 2012, 08:14:05 AM
Thanks pamaury,

Everything working OK now. ;D
Title: Re: Sansa Fuze+
Post by: pamaury on February 05, 2012, 10:15:47 AM
By chance today I managed to get the weird audio bug that megal0maniac described (with the exact same file). But it was by chance: I forgot to shutdown my player and after some time I realized it was still playing the audio output was exactly like yours. I'll try to add some audio debug screen in case it happen again.
Title: Re: Sansa Fuze+
Post by: megal0maniac on February 05, 2012, 04:59:47 PM
Is there anything I can do in the way of capturing debug info when this behaviour occurs?
Something I could compare between regular and broken playback?
Have you perhaps found anything unusual about the file? (It does this with the whole album, though)
Title: Re: Sansa Fuze+
Post by: kumy on February 06, 2012, 12:38:12 PM
Hi,

(I post my message here, as it could be a good source for anyone else having the same trouble)

during my last firmware upgrade, I ran out of battery (shame on me, yet I was warned)...

Now, fuze+ won't boot anymore.

I've been able to boot it in HID_Recovery, and successfully load recovery.sb with imxtools/sbloader (so it's not totally dead).

Now, my question is how can I flash it again ? (with the patched firmware, or original)

could I just "dd" something like seen in posts #105/#106 ? (http://forums.rockbox.org/index.php/topic,26284.msg184559.html#msg184559)

Should It try to load [original]firmware.sb so the flash process will restart ?

What are your advices ? :)
Thanks

Edit:
Thanks to pamaury, my fuze+ is now recovered !

FTR, this is what we've done.

[sandisk-firmware.sb, is the OF]

$ wget http://download.rockbox.org/bootloader/sandisk-sansa/fuzeplus/bootloader-fuzeplus.sansa
$ ./mkimxboot -i sandisk-firmware.sb -b bootloader-fuzeplus.sansa -o recovery.sb -t recovery

press vol up (keep it down) then plug on USB

$ sudo ./sbloader 1024 recovery.sb
$ ./mkimxboot -i sandisk-firmware.sb -b bootloader-fuzeplus.sansa -o recovery.sb -t recovery

$ fdisk -l
then find which device is has ID 53

My result are:
Disk /dev/sdb: 15.9 GB, 15925772288 bytes
1 heads, 1 sectors/track, 31105024 cylinders, total 31105024 sectors
Units = cylinders of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *      109569    31105024    15497728    1  FAT12
/dev/sdb2            1025      101376       50176   53  OnTrack DM6 Aux3
/dev/sdb3          101377      105472        2048    1  FAT12
/dev/sdb4          105473      109568        2048    1  FAT12


So it's /dev/sdb2

$ sudo dd if=firmware.sb bs=512 seek=4 of=/dev/sdb2

Then unplug USB.
Boot one time onthe OF to end the flash process...
Title: Re: Sansa Fuze+
Post by: pamaury on February 06, 2012, 12:48:17 PM
Yes it is possible. If possible, it would be better to come on IRC. Otherwise I'll write down the procedure.
Title: Re: Sansa Fuze+
Post by: megal0maniac on February 06, 2012, 04:44:45 PM
I'm sorry, but it would probably be best if you wrote it down. I can check if you're on IRC every now and then, but I have no way of staying logged on throughout the day.
Title: Re: Sansa Fuze+
Post by: alienkid10 on February 08, 2012, 10:21:58 AM
Pamaury: The CRT effect is GONE for me. I've been using BL V1 since I don't use an SD card and thus saw no need to update bootloader, but just now on a whim I thought I'd give it a shot, after the firmware update I booted to RB some stuff flashed on the top 6-7 lines of the screen then it went white for a fraction of a second then to the normal RB splash screen. I'm running with 7d54ff0 and BL V7 screen 2 with no CRT effect. No idea what in the boot loader would do it but it works!
Title: Re: Sansa Fuze+
Post by: Mystos on February 13, 2012, 02:58:53 PM
I am sorry for my bad English. I use the translator.

I have put today Rockbox on the Fuze +. Has found out the similar problem described in 12458. Internal memory and SD card  are not mounted in Windows simultaneously. If parametre USB Hide Internal Drive = YES - mounted internal memory. If USB Hide Internal Drive = NO - mounted SD card.
Title: Re: Sansa Fuze+
Post by: gevaerts on February 13, 2012, 04:16:30 PM
If parametre USB Hide Internal Drive = YES - mounted internal memory. If USB Hide Internal Drive = NO - mounted SD card.

Are you sure about this? "USB Hide Internal Drive = YES" should show only the SD card, not the internal memory...
Title: Re: Sansa Fuze+
Post by: Mystos on February 13, 2012, 04:23:06 PM
If parametre USB Hide Internal Drive = YES - mounted internal memory. If USB Hide Internal Drive = NO - mounted SD card.

Are you sure about this? "USB Hide Internal Drive = YES" should show only the SD card, not the internal memory...
Excuse me, I was mistaken.
You are right:
If parametre USB Hide Internal Drive = NO - mounted internal memory. If USB Hide Internal Drive = YES - mounted SD card.
Somebody works over the decision of this problem?
Title: Re: Sansa Fuze+
Post by: megal0maniac on February 14, 2012, 04:55:00 AM
If parametre USB Hide Internal Drive = NO - mounted internal memory. If USB Hide Internal Drive = YES - mounted SD card.

I can confirm this issue. Both drives show up fine in Linux, however.
Using Windows 7 SP1 x64
Title: Re: Sansa Fuze+
Post by: Mystos on February 14, 2012, 05:38:36 AM
I am sorry for my bad English. I use the translator.

I do not know where to say of suggestion on development of functional. I will write while here.

Whether it is possible to add such function: when pleer is blocked the buttons of adjusting of volume were executed by the functions of "Play" and "Pause". This possibility must be in options (on/off). It would enable to put pleer on a pause not taking out him. It is not very enough now.
Title: Re: Sansa Fuze+
Post by: buckminster on February 15, 2012, 09:47:34 AM
I noticed that the FFWD and Rewind buttons don't function properly during playback when the backlight is off and "First button press turns on backlight" is set to No. I'll hear a click for the key press and the backlight turns on, but I'll have to press the button again for it to FFWD or Rewind. Other button functions work as expected.

Don't know if this has been posted before and/or if this is a RB issue or specifically Fuze+. I tried to search here and under the bug tracker.
Title: Re: Sansa Fuze+
Post by: mysiak on February 16, 2012, 07:46:37 AM
I noticed that the FFWD and Rewind buttons don't function properly during playback when the backlight is off and "First button press turns on backlight" is set to No. I'll hear a click for the key press and the backlight turns on, but I'll have to press the button again for it to FFWD or Rewind.
Just tried FFWD/REWIND buttons with backlight off and it works fine for me - just one key press needed (version 9acd702M-120214).

However I am observing another issue with charging - if I connect rockbox in MSC/HID mode to the PC, battery is slowly discharging. I have to use USB connection via original firmware or plug in rockbox with some button pressed to charge the battery. Is anyone else observing this?

I would have one more question/request - is it possible to decrease the sensitivity of "ON/OFF" button (the one on top of the player)? It is very easy to accidentally press the button and player turns ON in a pocket. Maybe increasing the required button press time from few miliseconds to 3 seconds for example would help (similar way as with shutdown - we need to keep key pressed for few seconds to power off the player).
Title: Re: Sansa Fuze+
Post by: pamaury on February 16, 2012, 07:51:42 AM
Hello,
no it's not possible to change the sensitivty of the power button unfortunately. I agree it's far to sensitive to me but there no workaround.
I'll have a look at the battery issue in MSC/HID mode, it should not discharge.
Title: Re: Sansa Fuze+
Post by: mysiak on February 16, 2012, 08:13:13 AM
Maybe some dirty workaround could be feasible - first press turns ON the player, but bootloader would wait for another key press, either power button again or some other button to load rockbox FW, otherwise it would power off..?

Regarding the charge/discharge - it seems that with MSC/HID connection it charges the battery to 100%, but does not keep it charged at 100% and it slowly decreases (I noticed that battery was around 80% after connected for 5 hours).

Edit: btw. thanks for a very quick reply :)
Title: Re: Sansa Fuze+
Post by: pamaury on February 16, 2012, 08:20:03 AM
I prefer to avoid such dirty tricks if possible. But yeah, by changing the bootloader, one could perhaps require that power be pressed for 1 or 2 seconds.
Interesting, so the problem might be that when the charge is finished, I incorrectly configure the power control to use the usb source.
Title: Re: Sansa Fuze+
Post by: mysiak on February 16, 2012, 09:50:09 AM
If it's possible, could you please consider change of bootloader startup behavior for longer button press? It would really help as we don't have hardware lock button. Or maybe you could offer two types of bootloader and user will choose what he prefers? :)

Small update about battery:
Discharging seems to be also in "player" mode. I had ~90% of battery when I connected player to PC (button pressed) and watched the battery in debug menu. It went to 100% with status "charging", then status changed to "discharging" and it started to slowly decrease (approximately -0.002 V per minute).. After re-connection, player charged to full capacity again.
Title: Re: Sansa Fuze+
Post by: buckminster on February 16, 2012, 02:48:30 PM
Regarding my touchpad problem, while the backlight is on, all touchpad functionality appears to function normally. I just downloaded and installed bootloader V7(was on V6) and installed a current build (d2f97da-120216). I reset my settings to default as well.

With "First press turns backlight on" set to no and the backlight currently off (keyclick set to "weak" and no repeat):

Menus -
WPS -
With "First press turns backlight on" set to yes and the backlight currently off (keyclick set to weak and no repeat):

Menus -
WPS -
Am I the only one experiencing this? Should I file a bug?
Title: Re: Sansa Fuze+
Post by: alienkid10 on February 16, 2012, 06:21:47 PM
I have this too.
Pamaury on the PWRBTN issue: I find it odd how sensitive it is, since with OF Bootloader it's not this sensitive.
Title: Re: Sansa Fuze+
Post by: mysiak on February 17, 2012, 05:15:38 AM
Buckminster, I have tried your tests and sometimes it worked exactly as you described, but in other cases I couldn't repeat the behavior - key presses were detected and interpreted correctly. Maybe pamaury can bring some light on this.
Title: Re: Sansa Fuze+
Post by: pamaury on February 17, 2012, 05:18:37 AM
I have checked what the OF does and indeed, it doesn't boot if the power button is not hold for a certain amount of time. Unfortunately, this check happen after the rockbox bootloader decides whether to boot to OF or rockbox. As a consequence, the boot delay only exists when one boot the OF.
I'll modify the bootloader to mimic this behaviour. But it also means that to boot the OF, the two delays will be cumulated.

I have no answer for the key presses which are ignored. I think this is not related to the fuze+.
Title: Re: Sansa Fuze+
Post by: alienkid10 on February 17, 2012, 09:17:28 AM
pamaury: How long will the delay be for both boot to RB and OF?
Title: Re: Sansa Fuze+
Post by: highwar on February 18, 2012, 05:36:24 AM
hello

I am new to rockbox there are a few stuff I dont understand

I tried to install the file of sansa fuze plus ( the rockbox-sansafuzeplus file ' I unzipped it)
and copied it to the player ( it was at msc usb mode)
but it doesnt work what do I need to do ? is there a simple way ?


edit I put the .rockbox folder and the firware.sb at the player at msc mode but the original os still pops up
Title: Re: Sansa Fuze+
Post by: buckminster on February 18, 2012, 10:36:40 AM
If the firmware.sb is in the root folder of the fuze+, it should have caused the fuze+ to go into it's firmware update mode once you unplugged it from your computer. If it didn't, then you didn't put the file in the correct directory. Both the .rockbox folder and the firmware.sb should be in the root (main) folder of the fuze+ (there should be other folders there like Music, Playlists, Recordings, etc.).

Someone else will need to confirm, but I think the RockboxUtility might work for a more automated install of the bootloader and firmware now.
Title: Re: Sansa Fuze+
Post by: ddscentral on February 18, 2012, 11:12:51 AM
hello

I am new to rockbox there are a few stuff I dont understand

I tried to install the file of sansa fuze plus ( the rockbox-sansafuzeplus file ' I unzipped it)
and copied it to the player ( it was at msc usb mode)
but it doesnt work what do I need to do ? is there a simple way ?


edit I put the .rockbox folder and the firware.sb at the player at msc mode but the original os still pops up

To install Rockbox, copy firmware.sb (you need to patch it with Rockbox bootloader first) and .rockbox directory to player root.
After reboot, player should go into firmware upgrade mode. After the upgrade is finished, Rockbox should boot by default. To boot the OF, hold volume down key when powering on.
Title: Re: Sansa Fuze+
Post by: highwar on February 18, 2012, 11:16:14 AM
I did it just as you siad and it did do updating sansa fuze screen but after that it went to the original system.. is there a way like pushing a combination of keys to start rockbox os ?

how do I patch firware.sb ?
and where can i download the bootloader is it the rockbox Utility ?


edit I used the rockbox utility program and I started to patch the file and  the program disapeared meaning shutted down by it self ????
Title: Re: Sansa Fuze+
Post by: mysiak on February 18, 2012, 11:22:00 AM
Use "alternative method" mentioned here: http://www.rockbox.org/wiki/SansaFuzePlusPort
Title: Re: Sansa Fuze+
Post by: highwar on February 18, 2012, 11:31:40 AM
I did as you said with the bootloader v7
+the folder

what it did :
started updating fuze plus after that it wrote you have successfully updated your device and then it went to the original os ? what the ? lol ???


can you guys help me or even upload your fireware file and rockbox file amby it will help although I dont think so.

since i want to try rockbox
Title: Re: Sansa Fuze+
Post by: mysiak on February 18, 2012, 12:00:23 PM
That's really strange, I downloaded bootloader v7 and latest build of rockbox for fuze+, extracted both files to the root of internal storage and rebooted the player. OF booted, detected new FW, updated FW and restarted to rockbox. Everything worked at first try.. Maybe you could try to remove microSD card if you're using one, it's recommended to do FW updates with no card inserted.
Title: Re: Sansa Fuze+
Post by: halonachos117 on February 18, 2012, 12:06:21 PM
I think you need to reboot the player after you install the bootloader. Once the OF installs it, it will reboot into itself, I think. But when you reboot the player, Rockbox should load.
Title: Re: Sansa Fuze+
Post by: highwar on February 18, 2012, 12:09:49 PM
I did it without sd card... maby its beccause I have the latest fireware of  sansa fuze ..they made a very new update 3 days ago I think


you downlaoded the rockbox-sansafuzeplus extracted it on your pc
then extracted the v7 bootloader


then copied the v7 and rockbox. to the player and it worked//well I did the same and it didnt work
Title: Re: Sansa Fuze+
Post by: ddscentral on February 18, 2012, 12:25:53 PM
Try using an earlier version if the latest version doesn't work.
Title: Re: Sansa Fuze+
Post by: highwar on February 18, 2012, 12:48:24 PM
you were right thanks man ...

the touchpad is still very sensitive but its time to check rockbox out :)
Title: Re: Sansa Fuze+
Post by: bluebrother on February 18, 2012, 03:59:44 PM
edit I used the rockbox utility program and I started to patch the file and  the program disapeared meaning shutted down by it self ????

While not intended this to be expected when running it on Windows -- there is a bug in the latest release of Rockbox Utility in the bootloader installation for the Fuze+. Please read the changelog on the RockboxUtility (http://www.rockbox.org/wiki/RockboxUtility) wiki page, it does mention this. You can use a development build in the meantime (see my signature for a link).

Furthermore, this is a development thread. If you have problems with Rockbox Utility please post in the Rockbox Utility forum. If you have problems with manual installation please post in the appropriate forum for manual installation.
Title: Re: Sansa Fuze+
Post by: pamaury on February 19, 2012, 12:43:58 PM
@alienkid10: I have no idea for the OF delay. The OF code does something like "loop 550000 times and boot only if power was hold at least 400000 out of 550000 times". I'll try to add some delay and post the code on gerrit so people can test it.
Title: Re: Sansa Fuze+
Post by: al3rd on February 21, 2012, 04:36:02 AM
Good day i installed the rockbox on fuze+ but when i charged it the battery level stays the same.
Title: Re: Sansa Fuze+
Post by: mysiak on February 21, 2012, 06:47:51 AM
the battery level stays the same.
Could you please check battery levels in debug menu? I have attached screendump for my battery charge/discharge graph and rate. Battery charged to 100% and then started to discharge slowly with USB plugged in.
Title: Re: Sansa Fuze+
Post by: al3rd on February 21, 2012, 11:14:36 PM
good day how do you get that screenshot? i turn on the screendump i dont see any effects yet.
Title: Re: Sansa Fuze+
Post by: mysiak on February 21, 2012, 11:55:06 PM
I followed these instructions Screendump (http://www.rockbox.org/wiki/ScreenDump)
Title: Re: Sansa Fuze+
Post by: highwar on February 23, 2012, 12:59:08 PM
how can I delete the rockbox ? since I deleted it with the utility but the startup is  boot version...
arg=...
I want to flush the program how do I do that ?
Title: Re: Sansa Fuze+
Post by: mysiak on February 23, 2012, 01:07:41 PM
Unpack original firmware file to the root and reboot to OF. Player should detect new FW and update itself. This way you'll return original bootloader back.
Title: Re: Sansa Fuze+
Post by: metaphys on February 24, 2012, 07:25:45 PM
@pamaury:
the only way to boot into OF being to have volume down pressed as we push power button, you could implement a delay that only occurs if this button isn't down. This way you would avoid the cumulated wait time effect.
Title: Re: Sansa Fuze+
Post by: pamaury on February 27, 2012, 09:57:19 AM
@metaphys: very good point ! I'll implement that asap. I just returned from holydays.

I committed the patch which enables the fuze+ radio. It would be nice if some of you could test it and report problems (if any). You will need to use git HEAD of course. After that, I still need to investigate the battery issue and implement recording.

EDIT: I implemented the power up delay the same way as the OF. The change requires to update the bootloader but since the change is in mkimxboot, it doesn't require a new bootloader release for now (but we will do one nevertheless soon). So basically, one need to recompile mkimxboot, rerun it and resend the firmware.
Title: Re: Sansa Fuze+
Post by: mysiak on February 27, 2012, 02:17:30 PM
I just tried radio - it tuned fine, however froze quite often (I am not very familiar with Rockbox radio interface, so just pressed some random buttons - quick menu, left, right, play etc. which led to complete freeze). I will try to write down exact steps how to simulate this behavior.

Thank you for all your effort, I'm sure that people will appreciate if you will be so kind and have a look also into SD mount issue in Windows :)
Title: Re: Sansa Fuze+
Post by: halonachos117 on February 27, 2012, 11:30:02 PM
I get freezes, too. It seems to happen when you leave the device unattended long enough for the screen to shut down (at least that's the case for me, as I have the screen set to shut down after 30 seconds). I think you can avoid this by returning to the Main Menu before this happens.

Plus, I can't seem to easily get the radio to change from "Preset" mode to "Seek" easily. As soon as I open the radio, it changes back to "Preset" mode. The only way I can do this is to return to the Main Menu and select FM Radio. Then, I hold the center button to open the FM Radio options, and select Auto-Scan Presets. I can then cancel the process, return to the FM Radio options, and change to "Seek" mode.

Is this a bug, or am I just missing something. One thing's for sure... It sure is hard to add my favorite stations as presets.

PS: Pamaury, you rock for everything you do!
Title: Re: Sansa Fuze+
Post by: alienkid10 on February 28, 2012, 09:06:54 AM
I don't get freezes exactly but after back light goes out and I turn it on again (15 seconds for me) then  sign sth reads 0 and no input works but radio keeps playing fine.

So far only bug I've found.

Keep up the awesome work Pamaury and Meta! One day I'll never need the OF hopefullly.
Title: Re: Sansa Fuze+
Post by: buckminster on February 28, 2012, 11:45:19 AM
Same here with the lack of button/touchpad functionality after the backlight turns off (except for turning the backlight back on).

Sequences that recreate the problem:

Title: Re: Sansa Fuze+
Post by: metaphys on February 29, 2012, 08:22:14 AM
@pamaury:
Actually that radio button freeze might not be related to the radio code:
I noticed that the solitaire plugin that used to work give me the very same behaviour (no touchpad respond) quite interessing is that it only occurs on this plugins. So there might be something special with it that occurs also with radio.
Title: Re: Sansa Fuze+
Post by: Trailblazer7818 on February 29, 2012, 11:00:40 AM
Sorry if this is completely redundant, but I can't get the Rockbox utility to recognize my Fuze plus, either through autodetect, or manually. I see it in explorer, and can load files to the device. Does anyone have any ideas?
Title: Re: Sansa Fuze+
Post by: alienkid10 on February 29, 2012, 11:13:03 AM
Trailblazer: This should bein thr RB util forum but, is it in MSC mode? (hold voldwn while plugging in to make sure.) It should have a drive letter if it is in MSC mode.
Title: Re: Sansa Fuze+
Post by: Trailblazer7818 on February 29, 2012, 11:51:55 AM
I just tried that, And it sees the device, and autodetect sees it.  but it won't take the update. When I run the bootloader, and point it to the firmware file, it says patching file, and then the Utility just closes, and the device doesn't update. I tried redownloading the file, and I get the same result.
Title: Re: Sansa Fuze+
Post by: pamaury on February 29, 2012, 11:57:36 AM
There is an issue with the current rbutil closing if something wrong arises. It's fixed in git but we haven't released it yet. Are you sure you are using the right files for patching ?

EDIT: Ah right, on windows there is random error, you need to get the dev version.
Title: Re: Sansa Fuze+
Post by: bluebrother on February 29, 2012, 12:41:06 PM
There is an issue with the current rbutil closing if something wrong arises.

No, the issue is when trying to patch the firmware file on Windows. It is not caused by an error (well, technically it's an error, but it's not a user error and nothing a user can do anything about -- except using a different version or OS).

You need to use a version later than 1.2.12. Get a development binary at the link in my signature.
Title: Re: Sansa Fuze+
Post by: Trailblazer7818 on February 29, 2012, 01:27:52 PM
Thanks! Worked great.. Any known issues I should watch out for with this version?

Post Merge: February 29, 2012, 10:03:49 PM
Have another issue.. I don't know if it's related to the firmware, but after it's been playing for a while, the cursor goes to the bottom most position unless I shut it down and restart, then it works for awhile, and does the same thing again. I scroll up, and as soon as I let go, it goes to the bottom most position.. Any ideas?
Title: Re: Sansa Fuze+
Post by: buckminster on March 01, 2012, 07:33:16 PM
For those not keeping an eagle eye on the Port Status page, it looks like V8 of the bootloader was made available today. The only difference of which I'm aware is a longer button hold to turn on the RB firmware.
Title: Re: Sansa Fuze+
Post by: alienkid10 on March 02, 2012, 12:02:14 PM
yay meta fixed the keymaps again! Thanks meta! I haven't upgraded my BL yet and won't until after the weekend since I'm without internet except for basic browsing right now.
Title: Re: Sansa Fuze+
Post by: metaphys on March 02, 2012, 01:59:01 PM
I noticed that I cannot upgrade my bootloader if the firmware.sb file is installed from rockbox usb. I had to copy it with original firmware usb mode to have my file picked up to upgrade

@alienkid10:
we actually don't know exactly how they did get out of the tree
@buckminster:
that's the only modification.

I'm still waiting for the next official Rockbox Utility release before I can remove this wiki alternative method. It seems some problem has to be solved before its release

I should release a touchpad sensitivity setting very soon. Actually the patch is ready but I have to wait for approvement from the developer community to be sure it's clean enough.
git people may have a look here http://gerrit.rockbox.org/r/#/c/123/
Title: Re: Sansa Fuze+
Post by: nabule on March 04, 2012, 05:47:05 AM
I noticed that I cannot upgrade my bootloader if the firmware.sb file is installed from rockbox usb. I had to copy it with original firmware usb mode to have my file picked up to upgrade

@alienkid10:
we actually don't know exactly how they did get out of the tree
@buckminster:
that's the only modification.

I'm still waiting for the next official Rockbox Utility release before I can remove this wiki alternative method. It seems some problem has to be solved before its release

I should release a touchpad sensitivity setting very soon. Actually the patch is ready but I have to wait for approvement from the developer community to be sure it's clean enough.
git people may have a look here http://gerrit.rockbox.org/r/#/c/123/
I also had this problem.I can't update my bootloader to V8 and even original firmware.But sometimes before was OK.
To solve this, I boot my fuze+ in original firmware, and  reset setting. Then I can update bootloader normally.

Sorry for my poor engling :-[
Title: Re: Sansa Fuze+
Post by: megal0maniac on March 05, 2012, 04:58:26 AM
I noticed that I cannot upgrade my bootloader if the firmware.sb file is installed from rockbox usb. I had to copy it with original firmware usb mode to have my file picked up to upgrade

Confirmed.
Problem is, if you connect USB while running OF, you get the rockbox bootloader USB mode screen.
I've changed between MSC and MTP modes in the OF and can't seem to get it to connect in the OF.
Which means that I can't get it to detect the firmware file which makes it impossible to upgrade.
-sigh-

I'm currently running bootloader V7 (r31459-111229)
Suggestions?

Post Merge: March 05, 2012, 05:13:39 AM
Apologies, but nabule had already answered my question.
I just didn't fully understand :)

First copy the file to the internal memory.
To kick off the upgrade, boot into OF, go to settings and select "Restore"
Restart the player and it will begin the upgrade.
Title: Re: Sansa Fuze+
Post by: alienkid10 on March 05, 2012, 08:42:35 AM
I have an easier way to upgrade:
make sure player is off
hold vol-down
connect USB cable
release vol-down after 3-10 seconds
you are now in OF-USB mode.
Title: Re: Sansa Fuze+
Post by: SYNERGiST on March 05, 2012, 04:57:22 PM
Hi.

I just bought my Sansa Fuze+ And installed latest rockbox. But I am quite new to this so where do I see bootloader version I am using?.
Title: Re: Sansa Fuze+
Post by: ddscentral on March 05, 2012, 06:21:32 PM
I don't remember having to use OF USB mode when updating to bootloader V8.
I've just uploaded the firmware file in RB bootloader USB mode and then rebooted to OF (OF automatically triggered the update).
Title: Re: Sansa Fuze+
Post by: Trailblazer7818 on March 06, 2012, 09:49:11 AM
I've been using the new developer firmware for the past few days, but now the unit is locked up, and Is now unusable no matter what I do. Is there any way to delete the RB firmware, so that I can reinstall? Please advise..

Thanks!
Title: Re: Sansa Fuze+
Post by: pamaury on March 07, 2012, 09:13:15 AM
It has been explained several times in this thread: reboot to the OF using volume down and reinstall the OF.
Title: Re: Sansa Fuze+
Post by: Trailblazer7818 on March 07, 2012, 09:43:08 AM
I guess I didn't explain myself all that well... When I connect the device to the computer, it won't boot. It shows the bootloader id, and that's it. When I unplug the device from the computer, it turns off. Thinking the battery might be low, I left it plugged in for a couple of hours, and got the same result. When I remove the device from the computer, it shuts off, and will not restart, so there is no way to boot into either firmware. When connected to the computer, I can see the files through explorer even though the unit remains dark, other than the boot loader id. The Rockbox utility also sees and auto detects the unit. I tried reloading the FW, and it appeared to load correctly according to the utility, but once again, when I removed the device from the computer, it shuts off and cannot be turned back on. I was wondering if you could tell me if there's a way to manually remove the Rockbox FW, by telling me in detail which files to delete, and hopefully then I can reinstall either the original FW, or preferably the Rockbox FW. As I mentioned, I can see all the files on the device in Explorer. Any help regarding this would be greatly appreciated.

Thanks!
Title: Re: Sansa Fuze+
Post by: pamaury on March 07, 2012, 09:49:03 AM
You do not read what I wrote: the bootloader will normally boot the OF if you hold volume down and press longer a few seconds. If you see the bootloader, it means you already missed the step where you could boot the OF. If the device has low battery, just hold volume down and plug the usb cable while holding it.

As for the boot problem: could you at least tell us the bootloader error printed ? That will help us fix the problems if there is one.
Title: Re: Sansa Fuze+
Post by: halonachos117 on March 07, 2012, 02:41:48 PM
I do wonder if this is a Rockbox issue. There have been a number of people complaining about this problem on the SanDisk forums, most of whom don't even have Rockbox. It seems to be some weird Fuze+ issue, possibly caused by poor manufacturing or something. It has been suggested numerous times that users test there Fuze+'s in the parking lot to make sure the unit works.

Post Merge: March 07, 2012, 07:46:54 PM
Also, there's been a random freeze problem that's been killing me for some time. Has anyone else had this? FS# 12609.

PS: I'm sorry if this has been reported before, I couldn't find anything.
Title: Re: Sansa Fuze+
Post by: Trailblazer7818 on March 08, 2012, 10:01:41 AM
I was able to manually delete everything, and successfully reload the RB firmware, and now all is well. Thanks for all your help.

Cheers!
Title: Re: Sansa Fuze+
Post by: buckminster on March 08, 2012, 12:57:04 PM
Also, there's been a random freeze problem that's been killing me for some time. Has anyone else had this? FS# 12609.


I do get random lock ups (music stops, touchpad unresponsive, screen is black) while listening to music sometimes (less than 5 times in the last few dozen times I've played used it), but I haven't analyzed it since it doesn't happen often enough to determine a pattern.
Title: Re: Sansa Fuze+
Post by: pamaury on March 12, 2012, 01:09:04 PM
After some investigation, it seems that the radio freeze is caused by the chip failing to tune and thus the driver looping over and over trying to tune. I can avoid the freeze by exiting after a few failures but then the chip won't tune until it is stopped and restarted. I'm still looking for a solution... Interestingly, it seems related to the backlight. I suspect that when the backlight shut downs or starts up, there is some intereference which causes the chip to fail.

I have no clue for the playback lock up since it is looks so random.
Title: Re: Sansa Fuze+
Post by: megal0maniac on March 13, 2012, 03:23:34 AM
Interestingly, it seems related to the backlight. I suspect that when the backlight shut downs or starts up, there is some intereference which causes the chip to fail.

Perhaps someone could try and turn off the "fade in" or "fade out" setting on the backlight?
Dimming creates far more electrical interference than straight switching.
I'd try it myself, but strangely, my player isn't freezing at all...
It was freezing last time I used the radio(?)
Running d18a5ca-120304
Title: Re: Sansa Fuze+
Post by: buckminster on March 13, 2012, 04:21:50 AM
Perhaps someone could try and turn off the "fade in" or "fade out" setting on the backlight?
Dimming creates far more electrical interference than straight switching.

Doesn't make a difference for me. Glad that you found something out, pamaury. [wild speculation]If the backlight is causing interference for the radio chip, it might very well be causing the touchpad issue as well.[/wild speculation]
Title: Re: Sansa Fuze+
Post by: megal0maniac on March 13, 2012, 04:12:39 PM
I tried the fade thing, didn't make a difference for me either.

What I did find strange, is that the only time it would freeze was when I let it auto-scan the whole way through without pressing a button (the backlight time-out is slightly shorter than the time it takes to complete a scan)
If I press a button during the scan to keep it awake, then it doesn't freeze no matter what I try.

Does anyone have a reliable way to reproduce the freezing issue?
Title: Re: Sansa Fuze+
Post by: alienkid10 on March 13, 2012, 04:35:37 PM
have it in the mode where you can just tune. (not preset mode)
pick a station
leave player alone until backlight goes off
wake player
be stuck.
Title: Re: Sansa Fuze+
Post by: megal0maniac on March 14, 2012, 02:46:52 AM
Okay, that works.
But if you go back to the main menu, then it's fine.
Or if you go back to the main menu and then to the tuner then it doesn't freeze after a BL cycle (sometimes)
Or it does freeze as soon as you go back to tuner (without a BL cycle)
Or it freezes while going through region selections in the tuner settings (as this changes the allowed ranges and shifts the tuned frequency)
The last two scenarios don't require a BL cycle and don't happen every time.

Hate these bugs...
Title: Re: Sansa Fuze+
Post by: alienkid10 on March 14, 2012, 08:03:40 AM
Let's stop flooding the thread and make a flyspray (which I always read "flys pray") bug.
Meantime I haven't found any other bugs.
Title: Re: Sansa Fuze+
Post by: metaphys on March 15, 2012, 12:36:26 PM
pamaury just released a new bootloader and I updated the wiki page.
V9 add support for charging the battery in booloader mode (i.e if you plug the device while rockbox isn't running
Title: Re: Sansa Fuze+
Post by: Rarog on March 16, 2012, 02:23:37 AM
I'm not sure if this is a one-time glitch or something which can happen occasionally. For some resons rockbox played after every song on an album some seconds of other music (with time counter of the song of the album with negative count) before beginning playing the next song. I checked the filesystem and tried the music files on my PC and everything is ok. So Fuze read some other sectors/clusters which didn't belong to the song files.
Title: Re: Sansa Fuze+
Post by: alienkid10 on March 16, 2012, 08:16:42 AM
Interesting. I haven't been getting that.
Title: Re: Sansa Fuze+
Post by: buckminster on March 16, 2012, 04:58:54 PM
Does it happen on just the Fuze's drive or on a microSD card as well? Could be the File allocation Table is corrupt? Reformatting it may help.
Title: Re: Sansa Fuze+
Post by: Rarog on March 17, 2012, 01:31:13 AM
It was on SD card and I already checked it under Linux and Windows, it's correct.
Title: Re: Sansa Fuze+
Post by: beezeer38 on March 18, 2012, 11:59:41 AM
I can no longer delete files nor write files to the onboard memory.  It appears to work but when switched off & on again there is no change.  Deleted files are still there & written files are not.
I can navigate the file menu ok but the database no longer functions.
Tried to resort to the Sansa OS but although the root directory appears to accept the original sb file it's not actually being written to disk.
Title: Re: Sansa Fuze+
Post by: megal0maniac on March 18, 2012, 04:08:52 PM
@beezeer38:
Have you tried formatting the internal memory from within the OF?
Or going into the OF USB mode instead of Rockbox?
With the player off, hold vol-down while plugging in the USB cable.

@dev
May I suggest that the keymap for mpegplayer be modified?
Left and right nav keys control fast-forward and re-wind.
Usually this would be logical, however videos are played in landscape orientation so left/right becomes down/up.
I'd do this myself, but I don't know how. Plus I believe it's worth committing.
Title: Re: Sansa Fuze+
Post by: beezeer38 on March 19, 2012, 03:05:27 AM
I've tried formatting the internal memory via the sansa menu & windows but both fail.
Quick format via windows fails immediately whilst full format appears to be working but fails as it appears to complete.
Title: Re: Sansa Fuze+
Post by: metaphys on March 19, 2012, 03:25:26 AM
@beezeer38:

I had the same issue with my Fuze+ and didn't find any solution to it. Pamaury helped to perform some test on the device but we didn' find any solution.  :-\

- Where you using the database a lot?
- how old is your device?
Title: Re: Sansa Fuze+
Post by: beezeer38 on March 19, 2012, 01:11:42 PM
13 months old.
Started using Rockbox about 3 weeks ago.
Tended to navigate via the database rather than the file menu.
I have approx. 4000 audio files on internal memory & 3000 on a 16Gb external card.
Although I can no longer make changes to the internal memory I can change files on the external memory.

Title: Re: Sansa Fuze+
Post by: Rarog on March 20, 2012, 02:11:12 AM
Hm... Is it possible to try to repartition the device?
Title: Re: Sansa Fuze+
Post by: metaphys on March 20, 2012, 05:11:30 AM
@breezer:
Yeah that was about my experience too. Except I had used rockbox since 3 month as the problem occurs... It could be a hardware defect as we are only two with the problem. Or might be related to the database? I used to use the database a lot to build a random playlist of every files (16gb + 32 sdcard)
@Rarog:
It wouldn't help. The mmc interface report success on every operation althrough it DOES NOT perform them :/
Title: Re: Sansa Fuze+
Post by: beezeer38 on March 20, 2012, 05:41:30 AM
Tried reformatting, partition wipe & partition delete.
All appear to do what they say but at the end of the process there is absolutely no change to the contents of the internal memory.
Looks like I'm stuck with just using file access & making any changes to external memory.
Title: Re: Sansa Fuze+
Post by: megal0maniac on March 22, 2012, 02:15:17 AM
Fuze appears to be making quite a bit of noise when changing volume.
Especially when reaching 0dB and +2dB
(There is constant noise from +2dB and above. Spikes on on every other change.)

I've noted the dB value which was reached as the spike occurred.
I've tested this with headphones, earphones, studio monitors as well as my laptop's onboard soundcard.

When decreasing the volume, the larger spike occurs when you reach -1dB as opposed to 0dB.

(http://i.imgur.com/sBqmBl.jpg) (http://i.imgur.com/sBqmB.jpg)

Has anyone else experienced this?
Title: Re: Sansa Fuze+
Post by: RipCurl on March 22, 2012, 04:36:23 PM
Yep, I also have this noise.

Additionaly I can hear a beepy sound whenever I scroll through my music/menus and the music is turned off. Then, when I choose a file to play there's a noise (for about a half second) which is probably because of the buffering/loading... Maybe the audio output is in some kind of direct relation to the navaigation/ buffering...

EDIT: I use the Superlux HD661
Title: Re: Sansa Fuze+
Post by: megal0maniac on March 23, 2012, 02:35:36 AM
Strange, because it didn't behave like this before. Unless I was really being that ignorant...?
Title: Re: Sansa Fuze+
Post by: pamaury on March 24, 2012, 08:01:05 AM
There is an important change in the way the volume is managed before 0dB and after. Before, only the DAC volume is used and volume changes are handled by hardware by waiting zero cross to minimize noise. After 0dB, I begin to use the headphone amplifier which also has a zero cross mechanism. At the switch, it is possible that something weird happen, I will investigate this.
I think I also heard the noise when loading but it's not really "beepy".
Title: Re: Sansa Fuze+
Post by: metaphys on March 24, 2012, 10:02:36 AM
@Pamaury did you see the post from beezeer38 on the previous page? This is quite a problem, though it's still only two user so far, there seems to be a problem with internal memory.
It might be interresting to investigate further on this/to have a bootloader that can boot from sdcard
Title: Re: Sansa Fuze+
Post by: pamaury on March 24, 2012, 10:38:09 AM
This must be a hardware problem. The mmc flash reports success on every operation, I can't possibly do anything. Jean Louis told me that the problem also arised with the OF, several users reported it on the Sansa forums.
Title: Re: Sansa Fuze+
Post by: alienkid10 on March 24, 2012, 08:10:06 PM
no beeping that I've noticed, yet I'll keep and ear out for it. No flash problems either. Radio is freezing the whole player when I try to go into it. (like when it wasn't implemented right.)
Title: Re: Sansa Fuze+
Post by: megal0maniac on April 06, 2012, 04:57:01 AM
A few issues which I found while bug-hunting yesterday.

Noise while scrolling through menus, immediately after power-on. Goes away when you start playing audio.

CRT-effect when playing music. Only occurs when you start a song from the database or file manager, not when you skip to the next track.
Screen flickers for about 5 seconds when a track begins, seems to be related to disk access.

Radio seems to be working alright, but I always go back to the menu after starting it, and I don't autoscan.
Title: Re: Sansa Fuze+
Post by: halonachos117 on April 11, 2012, 06:03:59 PM
Has anyone noticed that Rockbox's clock is always one hour behind the OF clock, or is it just me?
Title: Re: Sansa Fuze+
Post by: alienkid10 on April 11, 2012, 08:13:10 PM
Haven't noticed but will check tonight.

confirmed OF is +1hour compared to RB.
Title: Re: Sansa Fuze+
Post by: halonachos117 on April 12, 2012, 07:29:22 PM
Perhaps it has something to do with Daylight Savings Time? Perhaps the OF sets the clock/chip back one hour, then adds an hour while in operation? If Rockbox doesn't do that, Perhaps the mistery is solved.
Title: Re: Sansa Fuze+
Post by: alienkid10 on April 13, 2012, 03:12:20 PM
I don't think so. It needed to be reset manually for me. I don't know a good way to test this though.
Title: Re: Sansa Fuze+
Post by: megal0maniac on April 16, 2012, 02:50:18 AM
The daylight saving theory would make sense, if it were possible to turn DST (daylight saving) on or off.
There isn't even a timezone setting. Closest thing to it is regional settings, to which mine is set to "rest of world"
In South Africa, we don't have DST. In fact many countries don't.

Most likely just a quirk of the OF. Shouldn't be too difficult to advance the the Rockbox clock by an hour as well...

Meanwhile, my Fuze is doing other stupid things.
When it boots, sometimes it takes a while before booting, (stays on "power up source" for about 4 seconds,) sometimes it boots fine and sometimes it says "File not found"

I've re-installed Rockbox to the device to rule out a sketchy rockbox.sansa file and I've run chkdisk on the internal memory and it came out fine.

Is the bootloader on a different partition on the main memory, or on a seperate eeprom?
Has anyone else had this issue?
Title: Re: Sansa Fuze+
Post by: pamaury on April 16, 2012, 04:28:27 AM
Hi,
having reverse engineered the OF on this point, I'm sure that the calculation are right. This one hour offset must come from daylight saving or different time zone.
The bootloader is stored on the internal storage (in a hidden partition) and it should be fast to boot. I don't think I've heared of someone getting random errors at boot time. Sometimes the device goes crazy if you didn't power it off properly. In doubt you can boot and immediately power off so that it properly turns off. Or perhaps there is a problem with the internal flash, you wouldn't be the first then but reports are always about write failures, not read.
Title: Re: Sansa Fuze+
Post by: Raiden175 on April 17, 2012, 10:13:55 PM
Sorry if I am a little late to the party. I had the same problem as you Breezer I could not Add/Delete Files either. I couldn't even access the OF. It inevitably sucked. I ended up getting an RMA for it. And I reinstalled Rockbox and it did not happen again, but in the time I did have it I could not find a solution to fix it. So I feel your pain.
Title: Re: Sansa Fuze+
Post by: halonachos117 on April 18, 2012, 05:46:43 PM
I've always noticed a three or four second delay when booting into Rockbox. This extra delay only occurs when the player was previously booted in the OF. If the last time you used the player, you booted into rockbox, there is no delay. If the last time you used the player, you booted into the OF, there is a delay.

Very strange. I assume there's some good reason behind this. I wouldn't worry about it.

As for the false "File not found" error, I've had that once. A simple reboot fixed it.
Title: Re: Sansa Fuze+
Post by: megal0maniac on April 19, 2012, 03:38:53 PM
So I decided to boot into the OF and go back to Rockbox to see whether I had the same delay.
I did.
Then I restarted it, and now all it does is say "File not found."
Consistently. Every time I start it up.

arg=CAFEBABE addr=40000000
Are these parameters correct?
Not that I could change them, but it might point to what's causing this issue.

Running ee6e88f-120315.
Can't remember which bootloader, but it was the first one to introduce the power button delay.

Will update shortly when I get it working.

UPDATE: Booting into OF and back into Rockbox fixed it the first time. But then I restarted and same issue. Went back into OF, restarted, and "File not found"
Any suggestions on checking the integrity of the internal memory?

UPDATE AGAIN: Installed (updated?) bootloader and Rockbox through the utility. Delay after booting OF is minimal now and the other issue is gone.
Title: Re: Sansa Fuze+
Post by: luetzel on April 22, 2012, 03:45:01 AM
@Pamaury did you see the post from beezeer38 on the previous page? This is quite a problem, though it's still only two user so far, there seems to be a problem with internal memory.
It might be interresting to investigate further on this/to have a bootloader that can boot from sdcard

Well, one more to count - I've got the same problem as well, and no solution. Tried re-formatting the device and the recovery procedure - nothing helps. When looking at the partition table, fdisk or cfdisk do not recognize/complain about an unsupported table. Any options to restore it somehow?
Title: Re: Sansa Fuze+
Post by: pamaury on April 22, 2012, 04:52:55 AM
Jean-Louis Biasini sent me his first Fuze+ which suffers from the same problem (internal memory is not writable anymore). I'm looking at the problem but I have no solution for now. I will add support for booting from the sdcard if the internal storage fails. That will not fix the broken ones but hopefully prevent total failures for the others. Has anyone of you tried to send it back to sandisk ?
Title: Re: Sansa Fuze+
Post by: luetzel on April 22, 2012, 05:25:15 AM
No, I haven't sent it to sandisk. Meanwhile, I managed to see all partitions.
Looks actually exactly as in other posts that I've seen:

Disk /dev/sde: 15.9 GB, 15925772288 bytes
1 heads, 1 sectors/track, 31105024 cylinders, total 31105024 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot      Start         End      Blocks   Id  System
/dev/sde1   *      109568    31105023    15497728    1  FAT12
/dev/sde2            1024      101375       50176   53  OnTrack DM6 Aux3
/dev/sde3          101376      105471        2048    1  FAT12
/dev/sde4          105472      109567        2048    1  FAT12


 fdisk can remove/create them and write to the table, however, when trying to format it with "mkfs.vfat, /dev/sde1" it fails with an error.

Post Merge: April 22, 2012, 05:27:34 AM
Ah, I forgot to add that the OF starts, but shuts down because of a database error, requesting a reformat to fix it. The rockbox build installed is from 120417.
Title: Re: Sansa Fuze+
Post by: megal0maniac on May 07, 2012, 02:54:43 AM
I'm sad to say that my Fuze+ is dead.
Plugged it into my computer (while off), had the bootloader "USB mode" screen.
When I unplugged it, the screen was very bright (more than the usual CRT effect)

Could only see half of the icons, if I went into a menu and back to the main menu, all the icons were gone until I went into another menu.
I went into settings, got a "Divide by zero" error and turned it off.
Now it won't turn on, regardless of what I try.

Have even opened it and de-soldered and reconnected the battery, but it won't do anything.
Battery was low at the time, but still had about 2 hours of play time.

RIP Fuze+...
Title: Re: Sansa Fuze+
Post by: pamaury on May 07, 2012, 03:58:13 AM
Have you tried the recovery mode ?
Title: Re: Sansa Fuze+
Post by: megal0maniac on May 07, 2012, 09:26:21 AM
Absolutely nothing is working.
Not recovery mode, no charging, nothing.
It's totally dead.

Post Merge: May 07, 2012, 09:36:07 AM
!!!!
Got it into recovery mode... But now what?
Does this mean there's hope?
Can I dump a firmware image like this?

Post Merge: May 08, 2012, 04:25:50 AM
Chatted to pamaury on IRC.
It seems as though the player can no longer locate the internal memory whatsoever.
A slightly more severe failure than most, but internal memory related once again.

I've been told that the only foreseeable method of recovery would be to modify the i2c eeprom to boot of a micro SD card, which wouldn't exactly be recovery as the internal memory would still be inaccessible, but would make the player usable once again by circumventing it completely.

The eeprom is write-protected, but this should theoretically be possible to change by pulling the write protect pin to GND.
Then it's a matter of knowing what to write and where to write it, I'd imagine.

Any credit for useful information goes to pamaury.
Just thought I'd post this for informative purposes.

Bottom line: My Fuze+ is essentially dead, without chance of recovery at this stage.
(It isn't possible to determine whether this is Rockbox related or not, but as it says on the wiki, you install Rockbox at your own risk.)
Title: Re: Sansa Fuze+
Post by: Enclavejedi13 on May 08, 2012, 09:17:55 AM
I have the same problem as megal0maniac, except my internal memory is still intact. But I am unable to charge my Sansa Fuze+ at all. When I plug it in, it still shows the bootloader usb mode, but I can't even turn it on. What should I do?
Title: Re: Sansa Fuze+
Post by: pamaury on May 08, 2012, 10:14:58 AM
You should boot into the OF using volume down.
I manage to write the epprom on the Fuze+ Jean-Louis sent me but currently it requires to short pins. I'm still trying to find a software only way.

By the way I think I found the reason of the tuner bug. I committed a fix but did not test it yet so if someone can confirm/invalidate, it would be nice.
Title: Re: Sansa Fuze+
Post by: megal0maniac on May 08, 2012, 11:25:43 AM
I have submitted an RMA request to Sandisk.
Problem is I can't find proof of purchase and there's a scratch inside the cover from when I opened it, on the transparent plastic over the screen.  ::)
So we'll see whether or not they replace it.

If they don't, I'm all for shorting pins out. It isn't like I could really make it worse...
In a silly way, I'm almost hoping that Sandisk don't replace it so I can try and fix it myself. ;D
Title: Re: Sansa Fuze+
Post by: halonachos117 on May 09, 2012, 12:00:53 AM
I have not noticed any bug that have been *fixed*  :'( Maybe next time it will actually work.
Now, after the screen goes black, I can return to the radio screen, but the signal strength turns to 0dBuV, even though the signal sound great. If one tries to change the station, it freezes just like before. However, now you can return to the main menu, and power down. You can also power down from directly inside the radio screen.

And just like before, once I set my radio to some preset, I can't set the radio screen to seek to non-preset stations. As soon as I enter/return to the radio screen, it switches from "scan" mode to "preset" mode. I can set it back to "scan" mode, but that would be useless, since it will go back to "preset" mode as I describe above.

PS: I'm using version d26a35d-120509, if that make a difference.

PS2: Once again, thanks for being awesome, Pamaury!

Post Merge: May 09, 2012, 06:26:34 PM
Update: Okay, so I've decided to try my luck, and updated just a few minuets ago. Now it seems to work much better, although I've only tested it for a few minuets. Perhaps your updateed radio code hadn't made it into the automated builds yet?

Anyway, so far so good. I will continue to test and see if I can find any bugs.
Title: Re: Sansa Fuze+
Post by: pamaury on May 10, 2012, 07:56:54 AM
Yes in fact I changed something after that along with some other things (pin use tracking and I fixed some could which would disable the gpio output on the fm i2c pins!). I have tested it today and the radio works reliably now. I also implemented RDS support but my fuze+ doesn't seem to have a good enough reception to meet our RDS parser requirement. I have implement a better RDS parser (see patch http://gerrit.rockbox.org/r/#/c/237/ (http://gerrit.rockbox.org/r/#/c/237/)) but it needs discussion. I am interested in any feedback regarding RDS, am I the only one to have poor RDS reception ?
Title: Re: Sansa Fuze+
Post by: alienkid10 on May 11, 2012, 12:29:54 PM
Can't test RDS since seemingly no stations around me use it, but radio works better now.
Title: Re: Sansa Fuze+
Post by: buckminster on May 11, 2012, 04:58:17 PM
I'm not getting anything for RDS (it just says "No RDS") when it works fine in OF.

I also noticed that the volume hardware buttons aren't functioning while on the Radio WPS. The presses are registered (wakes up the screen), but they don't adjust the volume. Touchpad volume control works fine. If I exit the Radio WPS, volume buttons work as expected.

EDIT:
On the plus side, I think your modifications fixed some problems I was having with playback from my SD card. Occasionally, I would get some garbling of the music and haven't been able to reproduce it since downloading the latest build. I don't remember the version of the previous build I had, but it was from the last few weeks (prior to your latest changes).
Title: Re: Sansa Fuze+
Post by: pamaury on May 12, 2012, 06:28:41 AM
sorry, I forgot that I did not commit the RDS stuff, it was only a patch. I finally committed the RDS support so now you can test it :) If it doesn't work and you can compile, I encourage you to apply http://gerrit.rockbox.org/r/#/c/237/ (http://gerrit.rockbox.org/r/#/c/237/) to see if it makes a difference.
Title: Re: Sansa Fuze+
Post by: buckminster on May 12, 2012, 12:09:19 PM
Running 1d21e54-120512 and no RDS being displayed (just "No RDS"). I just rebuilt my system and I don't have the time to download and compile right now. Is there any debug info I can provide you to help?
Title: Re: Sansa Fuze+
Post by: pamaury on May 15, 2012, 09:16:02 AM
Hi,
I would like to get some feedback on the audio volume of the radio. As you probably noticed, even at low volume the radio is still too loud. This is because the SoC cannot attenuate the tuner audio too much. Hopefully there is a way to attenuate the signal directly in the tuner but due to some limitation, the attenuation will have to be constant. So the question is: how much should I attenuate the radio output ? Of course, doing so will allow lower volumes but disallow higher ones. Alternatively, would a setting for this be useful ? (note that having a good default value is still important).
Title: Re: Sansa Fuze+
Post by: gama on May 15, 2012, 12:31:26 PM
Hi, Pamaury

have you managed to get the cpu frequency scaling working?.  I remeber you told me that currently rockbox doesn't change the frequency in the fuze+ and the bootloader doesn't set the maximun frequency either.  I hope that gets fixed soon ;).
Title: Re: Sansa Fuze+
Post by: ddscentral on May 15, 2012, 02:31:48 PM
Running ab91905-120513 (with RDS patch), RDS seems to work fine for me (tried with a local radio station).
Title: Re: Sansa Fuze+
Post by: alienkid10 on May 15, 2012, 08:24:29 PM
I noticed the loud radio in the OF before too, but it seems like it's only on some stations, I'll try some stations tonight in RB. I'm always for a setting for anything. If you could add a (persistent) setting for the touchpad sensi that would be nice to.
On another note I still have nothing interms of RDS, I know one station uses it since I got it in the OF.
Small thing: can you add a hotkey or something in the radio wps to change between preset and scan modes? I don't have everything as preset.
Title: Re: Sansa Fuze+
Post by: germandan on May 16, 2012, 05:36:07 AM
Hi everyone,

first off great work on this port, it really gives my fuze+ a real edge and is way more usable than the OF. Thank you very much for your efforts!

I am having a few issues so far though that I couldn't find in the bug tracker (at least not the exact problem I am having).
When skipping a track, Rockbox panics with the following error:

Data abort at 60070210
FSR 0x1
(Domain0, fault 1)
address 0x00000013
bt pc: 0x60070210, sp: 0x00004A80


It is usually this error, though I have also seen this one when skipping tracks very fast:

prefetch abort at FFFFFB44
FSR 0x1
(Domain0, fault 1)
bt pc: 0xFFFFFB44, sp: 0x00004B50
bt end:


The error only occurs when skipping from a mp3 file to a flac file, but it panics very reliably if I do that. Flac -> Mp3 seems to work fine, I haven't tested OGG or WMA though. Again, it only happens when skipping. If the track changes from mp3 to flac by itself when a song ends, no problems occur.

I am using the build dd59e1d-120511, everything was tested using the internal storage of my 8GB Fuze+.

Any ideas?

--Daniel
Title: Re: Sansa Fuze+
Post by: RipCurl on May 17, 2012, 10:02:46 AM
same here...
Title: Re: Sansa Fuze+
Post by: halonachos117 on May 17, 2012, 11:38:42 PM
I have learned to live with it for now, but...
Whenever I used to experience either this bug or FS# 12609, I used to have to manually skip from whatever song I had played the last time I willingly shut down, to what every I was player before the thing crashed/freezed. Now, it remembers where I was, regardless of whether I shut it down willingly or not.
@Pamaury: did you commit some kind of mod to force this?
Title: Re: Sansa Fuze+
Post by: germandan on May 29, 2012, 10:26:34 AM
Now, it remembers where I was, regardless of whether I shut it down willingly or not.

Yes, there must have been some sort of change, because it used to also forget all changes in the EQ settings for example when crashing. It doesn't do that anymore.
For now I'm just very conscious about what formats I have in the playlist and try to not skip tracks when the next song is a flac, which works pretty fine.
Title: Re: Sansa Fuze+
Post by: pamaury on May 31, 2012, 06:57:23 AM
Hi all,
I have not yet found the bug causing playback crashes but thanks to rarog, we have identified that the SD not showing up on windows might be linked to the lack of device serial number. I have implemented this now so that the device reports a really unique serial and Windows should be happy with that. If some of you (not everyone) can confirm that it works or not, that would be nice.
Title: Re: Sansa Fuze+
Post by: ddscentral on May 31, 2012, 08:56:11 AM
Seems to work for me. I can see both the internal eMMC and SD card under Windows 7. It also works in bootloader mode (after updating the bootloader).




Title: Re: Sansa Fuze+
Post by: Rarog on June 06, 2012, 06:40:57 AM
I've uploaded a precompiled Bootlader v10 with the fixes for Windows at the wiki page.
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on June 06, 2012, 10:57:11 AM
I've uploaded a precompiled Bootlader v10 with the fixes for Windows at the wiki page.
so any reason to update if you use linux?
Title: Re: Sansa Fuze+
Post by: pamaury on June 06, 2012, 11:02:03 AM
You shouldn't update the bootloader if you don't really have a problem. I'll try to do an official release including this fix and a boot menu if it's stable enough.
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on June 06, 2012, 11:03:08 AM
cool thanks.       
Title: Re: Sansa Fuze+
Post by: alienkid10 on June 08, 2012, 09:11:55 AM
boot menu?
Title: Re: Sansa Fuze+
Post by: pamaury on June 08, 2012, 09:14:12 AM
Something new to allow to boot from either internal storage or sd. Since the internal storage seems to weak and failing for some people, this allows the device be usable even with dead internal sotrage.
Title: Re: Sansa Fuze+
Post by: covvie99 on June 08, 2012, 11:00:44 AM
Just Registered so i could say a big thankyou to the Rockbox team and especially to those working on the sansa fuze+ port, which i'm currently using  ;)
Looking forward to the next revision, again Thankyou and keep up the good work. oops should read forum rules b4 posting , my bad .
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on June 09, 2012, 10:45:05 AM
Does anyone have the problem where the player just locks up when connecting to your pc while on but when connected when off bootloader usb mode works perfectly?    Running latest build with latest bootloader and am connecting to debian wheezy netbook
Title: Re: Sansa Fuze+
Post by: RipCurl on June 11, 2012, 07:13:11 PM
yes, same problem here... but I recently found a trick to connect the booted fuze+ to my pc without crashing: as soon as the connection screen (usb picture) appears you should change the connection type with the lock/power button quickly (e.g. Presentation -> browser -> mouse ...) if you're fast enough the player won't crash =)

EDIT: Windows 7 64-Bit, newest build, newest bootloader...
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on June 11, 2012, 10:21:22 PM
now i just get a data abort message when plugging it in while on.   when i do it while off it will connect but when i unplug it i get bad checksum error.
Title: Re: Sansa Fuze+
Post by: pamaury on June 12, 2012, 03:55:29 AM
Ok, I'll have a look at this issue. It seems other usb related problems have been reported recently.
Title: Re: Sansa Fuze+
Post by: halonachos117 on June 17, 2012, 11:45:43 AM
Pamaury: I don't know if this is you doing (I'm guessing it's not), but the undefined instructions/data aborts/prefetch aborts seem to have disappeared last night on my player. I'm running revision 47ea5b5-120612, if that helps.

Edit: It still seems to have an undefined instruction when switching from an m4a, to mp3, and back to the same m4a, although this doesn't seem 100% reproducable. Doing the same with a later part of the playlist, this time with an ogg file, does not give any errors. I'll look into reproducing this later, and post the exact error, with all its magic numbers and everything.
Title: Re: Sansa Fuze+
Post by: fsclavo on June 18, 2012, 06:05:23 PM
Hi! First of all, thanks for Rockbox! I love it, this firmware makes my fuze+ a decent player.
I'm not a developer, but I wanna help with this project.
Please let me know how I can help.

Thanks and best regards.

Fernando
Title: Re: Sansa Fuze+
Post by: germandan on June 22, 2012, 02:18:01 AM
Pamaury: I don't know if this is you doing (I'm guessing it's not), but the undefined instructions/data aborts/prefetch aborts seem to have disappeared last night on my player. I'm running revision 47ea5b5-120612, if that helps.


I can confirm this. After downloading the latest release to my fuze+ the data aborts etc. on changing codecs have disappeared. It's fantastic! Whoever made that fix, thank you very much!!
Title: Re: Sansa Fuze+
Post by: pamaury on June 22, 2012, 03:10:43 AM
Hello,
I'm sorry to inform you that this not me and I have absolutely no idea why. The crashes seem to be related to the cache so the real issue is problably still there but since cache issues are subtle, a little change can make it work (or fail).
Title: Re: Sansa Fuze+
Post by: halonachos117 on June 22, 2012, 06:05:55 PM
I'll look into reproducing this later, and post the exact error, with all its magic numbers and everything.

As promised, the exact error I receive when switching from m4a to mp3, and back to m4a is:

Undefined instruction at 63E68CE0
bt pc: 63E68CE0, sp: 000048E8
   A: 63E5FEE0
   A: 63E610F4
bt end.

I still can't quite reproduce this error, although ogg/mp3 switches still seem to be immune to this problem.
Title: Re: Sansa Fuze+
Post by: afruff23 on June 26, 2012, 02:36:00 AM
Is there any way to charge and listen at the same time?
Title: Re: Sansa Fuze+
Post by: mysiak on June 26, 2012, 02:51:29 AM
Just hold the "center" button while plugging the USB cable, release after few seconds and you can charge&listen.
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on June 27, 2012, 10:56:56 AM
Hey guys has anyone had a problem where the player screen just goes black with no sound?  But if you hold down the power button for 10 seconds or so it turns back on no problem?  It happens very rarerly but it does happen.   Kind of worried because i kept the receipt in my wallet and it's so faded that i wouldn't be able to use it as proof of purchase for warranty if needed.  i did use my cc so i might be able to use that
Title: Re: Sansa Fuze+
Post by: halonachos117 on June 27, 2012, 01:00:27 PM
Sportscrazed2:
A few things you should know: Sandisk offers a one-year warranty in America, two-year in Europe, so if there's a problem with the unit, you can exchange it from Sandisk for a replacement, and I don't think you need a reciept (I could be wrong).

Also, I should mention that this is a known issue with Rockbox, which probably only affects the Fuze+. I wouldn't worry too much about it, unless this is happening with the OF on your device.
Title: Re: Sansa Fuze+
Post by: RipCurl on July 14, 2012, 04:42:23 AM
Any further progress yet?
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on July 16, 2012, 10:13:32 PM
crashing happening way more frequently in todays build.   
Title: Re: Sansa Fuze+
Post by: leejey on July 18, 2012, 04:55:47 AM
Hi metaphys,
I use Sansa Fuze+ player. I upgraded its firmware to verion 02.38.06 (old version is: 02.37.01). Then I want to install Rockbox on it but I got Rockbox Utility crash error when I installing bootloader. And I can't downgrade my firmware to old version. Hence could you help me with this issue? Thanks.
Title: Re: Sansa Fuze+
Post by: bluebrother on July 18, 2012, 06:44:52 AM
Use a development version of Rockbox Utility. This is a known and fixed issue (and has been discussed / mentioned in the forums a couple of times)
Title: Re: Sansa Fuze+
Post by: leejey on July 18, 2012, 08:22:07 AM
Thanks, bluebrother.
I will try the latest Utility.
Title: Re: Sansa Fuze+
Post by: pamaury on July 23, 2012, 11:25:32 AM
Hi all,
sorry for the delay, I've not had time to work on the fuze+ recently but I have work in progress which I hope to commit soon. Many I have fixed some dma issue which probably cause the random crashes here and there, I just more time to test it and make sure there are no performance regression. Apart from this I think the fuze+ itself is quite stable, the major missing feature is recording but without proper dma it would just cause more crashes. Other missing features include the headphone insert/eject detection, cpu frequency scaling and battery calibration. There is still the annoying issue with the usb bootloader mode crashing the binary on disconnection but I don't know how to solve it currently.
Title: Re: Sansa Fuze+
Post by: alienkid10 on July 24, 2012, 08:31:47 PM
what would the "headphone insert/eject detection" do?
Title: Re: Sansa Fuze+
Post by: Chronon on July 24, 2012, 09:46:35 PM
It would allow automatic pausing and resuming of playback when an event is detected.
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on July 25, 2012, 09:20:36 AM
awesome do other players have that?  where is it in settings?  i sometimes drop my player and the headphone comes unpulgged.   i have a fuze v2 as well
Title: Re: Sansa Fuze+
Post by: Chronon on July 30, 2012, 12:02:41 AM
It depends on the hardware.  My e280 doesn't.  My F40 does.
Title: Re: Sansa Fuze+
Post by: megal0maniac on August 04, 2012, 06:20:11 AM
Sportscrazed2:
A few things you should know: Sandisk offers a one-year warranty in America, two-year in Europe, so if there's a problem with the unit, you can exchange it from Sandisk for a replacement, and I don't think you need a reciept (I could be wrong).

I live in South Africa and bought my Fuze+ in the US while on holiday.
Internal storage died and the device was bricked (not confirmed to be rockbox-related)
Contacted Sandisk, and after some admin sent the player to the Czech Republic.
Didn't have proof of purchase, just the name of the store and an estimated date of purchase.
Less than a week later, a brand new boxed unit was in my hands. They even used a customs brokerage service so it didn't cost me a cent. Only had to pay to send the unit to them.
+1 for Sandisk :)

Point of the story (relevant) is that if is broken, it is worth going through Sandisk first. And the warranty is a worldwide one.
Title: Re: Sansa Fuze+
Post by: pamaury on August 19, 2012, 06:34:51 AM
@megal0maniac: very nice to hear that. I wonder if they change it that easily because they know the hardware is fragile :)

Some news:

EDIT: I have made other changes to the data storages to simplify the driver. You can help by testing latest HEAD.
Title: Re: Sansa Fuze+
Post by: alienkid10 on August 19, 2012, 06:21:47 PM
Haven't updated my build in awhile, but after things calm down here I'll update it and report bugs.

That's too bad about no jack detect. :(
Title: Re: Sansa Fuze+
Post by: halonachos117 on August 21, 2012, 01:08:00 AM
IDK about the touchpad, but now my internal storage is REALLY hard to use. No, this isn't the "it says it worked, but it didn't" error (thank goodness). Everytime RB tries to modify something, the FS becomes corrupt. Even something as simple as updating my DB seems to fail. If one uses the OF to update RB, everything should work for a while, but if you try to launch RB to update RB, the player crashes. Then it become difficult to manually browse the Internal Memory, even in the OF. However, I can still run a checkdisk, which allows be to delete the .rockbox directory and start from scratch. So far it doesn't look like the External storage is effected, although I haven't exactly been willing to brave it. This happened with two builds of RB (IDK which the first build was, but the second was 39396cc-120819). I have just reverted to 47ea5b6-120612, which seems to work so far.
Title: Re: Sansa Fuze+
Post by: pamaury on August 21, 2012, 05:41:26 AM
Thanks for the report. You should try with more revisions to find the culprit ? I would expect it between 246c212 and 4908b8e if it's related to my changes.
Title: Re: Sansa Fuze+
Post by: fsclavo on August 21, 2012, 08:51:18 AM
Pamaury, I'm running 39396cc without problems (at least, not new ones!).
I used to listen flac music and the players hangs with black screen in past over and over again, after the upgrade (and still now) the problem has disappeared!
I'll keep testing, thanks for your work!
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on August 21, 2012, 10:07:47 AM
Haven't had any crashes with the current built.  Everything seems to be working great.  Thanks for turning my unusable mp3 player with OF to something awesome with rockbox
Title: Re: Sansa Fuze+
Post by: halonachos117 on August 22, 2012, 03:02:41 AM
85a6715 seems to work, as does 06aa7e8, although I haven't tested them thoroughly, yet. I do seem to still be having one issue where my PC seems very slow to detect the device for browsing, but that might be a problem with my own computer. I'll experiment more tomorrow.
Title: Re: Sansa Fuze+
Post by: ddscentral on August 23, 2012, 12:11:52 AM
I've noticed that USB transfers became very slow with the current build (latest sources from git repo).
~120-150KB/s write, ~1.5MB/s read, both internal and microSD (32GB class 10 card).
In OF, speeds are fine.
Title: Re: Sansa Fuze+
Post by: pamaury on August 23, 2012, 08:09:48 AM
Thanks for reporting, I just fixed that in the last commit. I got an improvement from ~1MB/s to 12MB/s on read which is much closer to what you can expect.
I hope to be able to implement recording before the feature freeze which is a few days ahead now. Any other really wanted feature to suggest before freeze ?
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on August 23, 2012, 12:23:31 PM
Does this mean the fuze+ will be upgraded to stable with the newest release?   I had a crash the other day so have moved back to my original fuze for the time being.  can't be having crashed during a 2 hour podcast.   
Title: Re: Sansa Fuze+
Post by: halonachos117 on August 23, 2012, 11:19:25 PM
Hmm... all the device doesn't seem to take so long to become "browseable" on the other machine I just tested it on (same RB build). I guess it really is a problem with my own computer. Just though you should know.

PS:

Any other really wanted feature to suggest before freeze?

I have one. I would love to be able to lock the player, regardless of which screen I'm on. At the very least, I would love to lock the main screen, and I'm sure others would love to lock the radio screen. Of course, whatever you do, you're definitely my hero for all you've done.
Title: Re: Sansa Fuze+
Post by: gontofe on August 24, 2012, 08:37:23 AM
This is great, I have finally moved from using Rockbox on my old iPod Video to my new Fuze+.

What's the best way to report bugs? There are a couple of things I've noticed, but overall it works really well, thank you!
Title: Re: Sansa Fuze+
Post by: pamaury on August 24, 2012, 08:42:07 AM
Report bug on flyspray (see bugs link on the left menu of the website). I'm not sure a global lock is feasible without much work with our current code. The WPS lock key is really special to the WPS but I'll see what I can do. I agree the radio screen needs a lock key too.
Title: Re: Sansa Fuze+
Post by: gontofe on August 24, 2012, 09:36:27 AM
That's great, thanks for that.

Is there a way to make the backlight turn off as soon as the screen is locked?
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on August 24, 2012, 04:44:07 PM
Updated to latest build about 5 minutes ago and it immediately told me to charge it.  so i set it up to charge and it rebooted itself about 3 times and now seems to have settled down.   also when i unplugged it from the power source the screen went all grey and it locked up forcing a power down.  has anyone experienced something like this?
Title: Re: Sansa Fuze+
Post by: gama on August 24, 2012, 05:18:16 PM
Hi pamaury, can you work on fixing cpu scaling?  I like videogame music and VGM playback was very laggy last time i tried and spc playback needs a bit more cpu power too.
Title: Re: Sansa Fuze+
Post by: buckminster on August 26, 2012, 11:05:41 AM
Still having this issue as far as I can tell. Not sure what else I can do to ask for help on this. Any debug information I could submit? Not the end of the world, but really annoying.

http://www.rockbox.org/tracker/task/12594
Title: Re: Sansa Fuze+
Post by: fsclavo on August 27, 2012, 12:21:11 PM
Excellent news!
Maybe cpu scaling is my most desired feature; if this can reduce battery consumption.
Thanks.
Title: Re: Sansa Fuze+
Post by: metaphys on August 27, 2012, 01:48:13 PM
hi all. I've been away for a while and 'm just passing through... I've closed:
http://www.rockbox.org/tracker/task/12447
http://www.rockbox.org/tracker/task/12446
http://www.rockbox.org/tracker/task/12442

For I cannot reproduce then anymore. Let us know if you are still experiencing them (especially the first one that always has randomly occurred.)
Title: Re: Sansa Fuze+
Post by: gontofe on August 28, 2012, 01:37:37 PM
Agree with buckminster about http://www.rockbox.org/tracker/task/12594.

Pamaury, do you have your own git repository?
Title: Re: Sansa Fuze+
Post by: pamaury on August 30, 2012, 05:58:34 PM
I have implemented basic frequency management in HEAD, it can switch between 261MHZ and 454MHz. I have also enabled the auto-slow feature which divides the clocks when unused. This should allow for high performance when needed and better power savings when idle. I also fixed the battery calibration so it should display more realistic values. If you notice anything special, tell me so I can revert before the branch on sunday.

I have no clue about the touchpad unexpected behaviour. I'll try to reproduce it but I never noticed something similar.

EDIT: has anyone noticed random freeze ? If yes, does it seen to be related to usb connection or database settings (load to ram, auto update, gather runtime data) ?
Title: Re: Sansa Fuze+
Post by: RufusA on September 03, 2012, 11:00:12 AM
I agree the radio screen needs a lock key too.

Firstly @pamaury great work on this port / bug fixes. A radio screen lock is the one feature I really miss. Also if anyone does dabble with some of the radio key mappings, it would be great if the physical volume buttons could control the radio volume!
Title: Re: Sansa Fuze+
Post by: fsclavo on September 03, 2012, 01:33:34 PM
I'm not having luck with latest version, the fuze+ hangs (for example with 1e8eb47).
Reverted to 4999913 and haven't problems, the player is very stable.
Regards
Title: Re: Sansa Fuze+
Post by: pamaury on September 03, 2012, 05:35:37 PM
Unfortunately it seems that is related to frequency scaling. I have disabled it in the last commit. Can you confirm that it fixes the problem ?
Title: Sansa fuze plus is proper dead
Post by: kfrans1k on September 04, 2012, 03:26:56 AM
my fuze plus is cactus..

I think its a battery charging issue - but cant tell if its firmware based as cannot load sansa firmware (battery completely dead)

upon connecting to usb the screen shows:

"Boot version: 1.0
arg=CAFEBABE, addr=40000000
USB: connecting
Bootloader Usb Mode"

Thats all i can get out of it.

Prior to being completely dead the usb would actually connect and show the drive and all files. Now nothin..

Anyone had this?

Title: Re: Sansa Fuze+
Post by: pamaury on September 04, 2012, 03:52:08 AM
You should always be able to boot in the OF by powering off, holding volume down and plugging usb. If you don't, come on IRC so we can discuss how to recover.
Title: Re: Sansa Fuze+
Post by: knob on September 04, 2012, 05:11:34 AM
Also if anyone does dabble with some of the radio key mappings, it would be great if the physical volume buttons could control the radio volume!

For my personal use build I already disable the touchpad volume for the music player, it's not hard if you download the build environment, and have a play.

Generally I find the touchpad easier to manage if volume is operated only by the physical buttons.

IMO it's a bad idea to have the volume controlled from the touch pad at all. if you touch the pad by accident the volume can go loud very quick!

What do others think about the idea of operating the volume only from the physical buttons?

Title: Re: Sansa Fuze+
Post by: fsclavo on September 04, 2012, 12:03:46 PM
Unfortunately it seems that is related to frequency scaling. I have disabled it in the last commit. Can you confirm that it fixes the problem ?

Confirmed! I updated to 072bade and the problem is gone.
Title: Re: Sansa Fuze+
Post by: metaphys on September 05, 2012, 02:26:21 AM
I get data abord on usb deconnection with the cpu-scaling on. Untill now I could'nt reproduce it with the new update (scaling off)
Title: Re: Sansa Fuze+
Post by: buckminster on September 06, 2012, 03:00:58 PM
Not sure how long this has been a problem, but I noticed that using the FM Radio will break voice menus/directories/etc. The only way I've been able to work around this is to either play some music (mp3/whatever) or turn off and turn back on the player. Voice functionality returns to normal after that.

If anyone can confirm this as well, I'll submit a bug.
Title: Re: Sansa Fuze+
Post by: music_lover001 on September 08, 2012, 02:11:31 PM
Hi all - -

First, I want to thank all those responsible for Rockbox.  I think it is terrific, and it is obvious that a lot of thought went into the project.

This started when I recently purchased a set of Beyerdynamic T50P headphones.  On my Fuze + I noticed that when I resumed playback after turning on the player, or started playback from a different directory, there was a buzzing noice that lasts 6-7 seconds (if from the onboard flash), or 10-12 seconds (if from the microSD card).  In addition, the buzz - when from the microSD card - is louder.  For giggles, I changed the theme to the Rockbox default.  After I did this, the buzz changed:  it was much quieter until the screen blanked out, then it resumed at the louder volume for a couple of seconds before stopping (my settings are such that the screen blanks out after 20 seconds).

Also I could hear some white noise when no music is playing.  Changing the volume has no effect on the buzzing or white noise.  (I also noticed a popping noise when changing the volume on the main menu screen, but I think this has been discussed elsewhere before.)

I cannot hear any of these sounds when using the original firmware, nor when I am using any of my other headphones (PX100, PX200-II, Bose IE2).

Does anyone have any suggestions or work arounds (other than using the headphones that I cannot hear it with)?

Thank you in advance.

EDIT:  I have noticed the noise mentioned in paragraph 2 with the following builds:  1e7f606-120731, 1e8eb47-120902, and 4f99dd4-120905.
Title: Re: Sansa Fuze+
Post by: fsclavo on September 09, 2012, 10:49:11 AM
Hi all - -

First, I want to thank all those responsible for Rockbox.  I think it is terrific, and it is obvious that a lot of thought went into the project.

This started when I recently purchased a set of Beyerdynamic T50P headphones.  On my Fuze + I noticed that when I resumed playback after turning on the player, or started playback from a different directory, there was a buzzing noice that lasts 6-7 seconds (if from the onboard flash), or 10-12 seconds (if from the microSD card).  In addition, the buzz - when from the microSD card - is louder.  For giggles, I changed the theme to the Rockbox default.  After I did this, the buzz changed:  it was much quieter until the screen blanked out, then it resumed at the louder volume for a couple of seconds before stopping (my settings are such that the screen blanks out after 20 seconds).

Also I could hear some white noise when no music is playing.  Changing the volume has no effect on the buzzing or white noise.  (I also noticed a popping noise when changing the volume on the main menu screen, but I think this has been discussed elsewhere before.)

I cannot hear any of these sounds when using the original firmware, nor when I am using any of my other headphones (PX100, PX200-II, Bose IE2).

Does anyone have any suggestions or work arounds (other than using the headphones that I cannot hear it with)?

Thank you in advance.

EDIT:  I have noticed the noise mentioned in paragraph 2 with the following builds:  1e7f606-120731, 1e8eb47-120902, and 4f99dd4-120905.

Same issue here. I hear noise and it's louder while the player is accesing storage (internal or sd).
Title: Re: Sansa Fuze+
Post by: metaphys on September 13, 2012, 07:18:37 AM
I'm experiencing some random freeze while playing audio file usely it comes at the end of some song in a playlist. But not alway with the same song or the same playlist. Does this occurs to other too?

Post Merge: September 13, 2012, 07:20:06 AM
oh and I forget pamaury: it also occurs often while trying to access/browse database during playback
Title: Re: Sansa Fuze+
Post by: metaphys on September 14, 2012, 05:42:58 PM
Pamaury : reverting to 417da66 makes the randoms freeze disappear. Do you already know where they are coming from or should I try other build between 417da66 and present build to find out starting from which commit it occurs ?
Title: Re: Sansa Fuze+
Post by: bodymind on September 17, 2012, 03:38:53 PM
first of all... thanks a lot to all the community and main developers for your work, you amazing your skillzz :)

my fuze+ just run out of battery the other day, should the bootloader, check the battery before it loads?
is the bootloader when on usb mode charging?

anyway with the last build, when my battery dried too much, the rockbox was not able to recover it.. i had to go to the OF and do it from there, its no problem but scary when I thought my player just bricked!
Title: Re: Sansa Fuze+
Post by: halonachos117 on September 17, 2012, 08:12:49 PM
Anyway with the last build, when my battery dried too much, the rockbox was not able to recover it.. i had to go to the OF and do it from there, its no problem but scary when I thought my player just bricked!
If you wish to avoid this again, try updating your boot loader with the newest one (you can find it on the Fuze+ wiki). The newer bootloaders can charge your battery. Just make sure you have enough battery to perform the update, though or it WILL be bricked!
Title: Re: Sansa Fuze+
Post by: bodymind on September 18, 2012, 03:03:25 AM
aw right! :)
well... i am trying to update the bootloader with the new rbutil 3.0... and it creates a new file firmware.sb in the root of the player, but when i boot the player doesn't load it, booting from the OF or rockbox.
Title: Re: Sansa Fuze+
Post by: bluebrother on September 18, 2012, 04:07:45 PM
well... i am trying to update the bootloader with the new rbutil 3.0... and it creates a new file firmware.sb in the root of the player, but when i boot the player doesn't load it, booting from the OF or rockbox.

There is no Rockbox Utility 3.0. Plus, you might need to boot into the original firmware before installing the firmware file to the player.
Title: Re: Sansa Fuze+
Post by: music_lover001 on September 18, 2012, 04:32:27 PM
Hi all - -

First, I want to thank all those responsible for Rockbox.  I think it is terrific, and it is obvious that a lot of thought went into the project.

This started when I recently purchased a set of Beyerdynamic T50P headphones.  On my Fuze + I noticed that when I resumed playback after turning on the player, or started playback from a different directory, there was a buzzing noice that lasts 6-7 seconds (if from the onboard flash), or 10-12 seconds (if from the microSD card).  In addition, the buzz - when from the microSD card - is louder.  For giggles, I changed the theme to the Rockbox default.  After I did this, the buzz changed:  it was much quieter until the screen blanked out, then it resumed at the louder volume for a couple of seconds before stopping (my settings are such that the screen blanks out after 20 seconds).

Also I could hear some white noise when no music is playing.  Changing the volume has no effect on the buzzing or white noise.  (I also noticed a popping noise when changing the volume on the main menu screen, but I think this has been discussed elsewhere before.)

I cannot hear any of these sounds when using the original firmware, nor when I am using any of my other headphones (PX100, PX200-II, Bose IE2).

Does anyone have any suggestions or work arounds (other than using the headphones that I cannot hear it with)?

Thank you in advance.

EDIT:  I have noticed the noise mentioned in paragraph 2 with the following builds:  1e7f606-120731, 1e8eb47-120902, and 4f99dd4-120905.

Same issue here. I hear noise and it's louder while the player is accesing storage (internal or sd).

Hi all - -

This is a little clarification.

The "white noise" is present when the player is first turned on.

Also, the noise changes when using the Rockbox Failsafe theme with white letters and a black background.

In addition, I turned the directory cache off to see if it would make any difference.  It did not.
Title: Re: Sansa Fuze+
Post by: halonachos117 on September 19, 2012, 01:32:16 AM
How's this for clarification: the noise stops after something, eg. music or the radio is played (might also work with MPEG player plugin).
Title: Re: Sansa Fuze+
Post by: music_lover001 on September 19, 2012, 12:02:53 PM
How's this for clarification: the noise stops after something, eg. music or the radio is played (might also work with MPEG player plugin).

This is incorrect.  I can still hear the mentioned noised,
but not the "white noise," when playing music for several
seconds - especially when using the cabbie2 theme.

However, you are correct in that this noise is not present
while listening to the radio.

In addition, I  noticed that I can hear this noise with the PX200-II headohones has well.
Title: Re: Sansa Fuze+
Post by: RipCurl on September 19, 2012, 05:49:36 PM
How's this for clarification: the noise stops after something, eg. music or the radio is played (might also work with MPEG player plugin).

This is incorrect.  I can still hear the mentioned noised,
but not the "white noise," when playing music for several
seconds - especially when using the cabbie2 theme.

However, you are correct in that this noise is not present
while listening to the radio.

In addition, I  noticed that I can hear this noise with the PX200-II headohones has well.

I can confirm this for my superlux hd661
Title: Re: Sansa Fuze+
Post by: halonachos117 on September 19, 2012, 06:56:36 PM
Hmm... I just tried that, but radio doesn't kill white noise, either. Actually, I haven't even noticed the white noise before (just the "squeakies"). I wonder if this is something new.

Edit: I just noticed this in the OF, too. Could this be a hardware issue? Perhaps a cheesey DAC?
Title: Re: Sansa Fuze+
Post by: Disturbed on September 27, 2012, 08:34:59 AM
Hello, I have Sansa Fuze+ and because I don't really like the firmware, I want to try Rockbox instead. But I'm worried about the whole "unstable" thing. When do you believe the port will be stable enough to use?. I care mostly for the keys, music playback and the battery. Thank You.
Title: Re: Sansa Fuze+
Post by: wodz on September 27, 2012, 10:44:55 AM
In this terms it is stable. Unstable means basically that there are features not implemented yet and there may be some parts supported suboptimal.
Title: Re: Sansa Fuze+
Post by: Disturbed on September 27, 2012, 12:13:17 PM
In this terms it is stable. Unstable means basically that there are features not implemented yet and there may be some parts supported suboptimal.

Thank you. By the way, is the Port Status chart on this page updated to the current release?:
http://www.rockbox.org/wiki/SansaFuzePlusPort (http://www.rockbox.org/wiki/SansaFuzePlusPort)
Title: Re: Sansa Fuze+
Post by: xpmule on October 01, 2012, 04:45:52 PM
Can someone tell me what are the charging options ?
I noticed my player was low on power and plugged it in and left it
and came back a couple hours later to a corrupt screen and i have had that happen
a bunch of times as well as crashing / lock ups and worst of all
i don't see any indication of it charging lol

Basiclly i have tried plugging it into windows 7 x64 while it was off or on
and also tried booting into the normal firmware and as soon as i did that
it triggered the Rockbox bootloader screen.

My player is almost dead and i need power !
And i'm using the newest bootloader released a week or 2 ago
and the firmware is version 121001 (updated from 120927 today)

This may seem dumb but i don't know what to expect..
Like does the HDD mode in the settings have anything to do with charging ?
What is the best way to get it charging ? make its off and plug it on or.. ?

EDIT:
ok i went and found the manual..
it says to make sure its on and hold any button and plug it in to your pc.
i did that and the battery level increased so i think that is working :)

I like reading manuals as much as I like reading TOS agreements lol
This charging info can be seen in the manual at (Quick Start / USB Charging)
Title: Re: Sansa Fuze+
Post by: ildarion on October 06, 2012, 11:45:30 AM
I have install rockbox on my sansa fuze + and i realy love it !  Thanx for your work, it's realy better than the OF !
Title: Re: Sansa Fuze+
Post by: tonqua3000 on October 09, 2012, 07:44:51 PM
Hey, I installed Rockbox on the Sansa Fuze + and it works great! Rockbox is the best.
I'd like to report a problem though. Not sure if it's the right place but I've been reading around and haven't found a solution.
When the keys are locked and the player turns off the screen, after 30 seconds the player freezes and shuts off. I then have to wait 30 seconds to start it again. It seems really random as it shuts off 2 or 3 times and then works fine. This is really annoying and makes listening to music and podcast difficult.
Has anyone experienced something similar and is there a workaround?
Thank you.
ah, the back of the player says:
BL1009cbwk-16gb
and rockbox version:
213f69d-120915
Title: Re: Sansa Fuze+
Post by: halonachos117 on October 10, 2012, 07:02:48 PM
You should probably make a bug report in Flyspray (on the left side of the page). That's where bug reports should go.

Also, the info on the back of the player is just a serial number (and storage size). It is of little interest, and will only be of importance if you ever need to contact Sandisk support.
Title: Re: Sansa Fuze+
Post by: 11sword11 on October 17, 2012, 09:48:27 AM
When loading large amounts of data via a cable to a memory card, after a while there is an error, copying stops and the computer no longer sees the card.
After reboot and reconnect rockbox device to a PC, it works, but if you download large amounts of data to a memory card, after a while the error is repeated.

I have this problem is present on all the latest builds, is forced to download music to use a card reader.
Title: Re: Sansa Fuze+
Post by: halonachos117 on October 17, 2012, 06:41:11 PM
I get this, too, both in pre-bootloader mode, and in "regular" mode. FYI, the OF doesn't give any such problems.
Title: Re: Sansa Fuze+
Post by: xpmule on October 17, 2012, 10:16:19 PM
Transfer on windows ?
Should be something logged in the event viewer i'd imagine (related to transfer errors)
I'd be pretty surprised if there was no info if an error occurred.

How much data are you guys talking about ?
I have a 1gb card i uses sometimes and never had a problem with it.
(so obviously i couldn't transfer more than 1gb in 1 transfer session)

If the device vanishes like you said there should be a log of that too
The error report is vague guys and if your using at least windows 7
there is a LOT of hardware logging that happens at all times ;)
never mind advanced methods of debugging a device or software.
Title: Re: Sansa Fuze+
Post by: 11sword11 on October 18, 2012, 04:54:55 PM
Transmission error appears in the windows and linux, it is not a PC problem in the player and it is in the software.
I've got it there in the transmission of significant amounts of data in a single session is usually a 2-3GB
When an error occurs the PC shows a message that the device is no longer available, in Device Manager card is displayed as part FAT32, but the PC can not copy data to it, or even to determine the capacity of the disk. Several times after that card did not work, even in card reader is not scanned until windows file system and correct the issue.
Title: Re: Sansa Fuze+
Post by: xpmule on October 19, 2012, 04:38:31 AM
Unless one of the devs can re create the problem i doubt it will get fixed any time soon.

I'd like to help but i have not had any transfer errors.
If I do, i will try and round up some info for the Rockbox team.
Title: Re: Sansa Fuze+
Post by: halonachos117 on October 20, 2012, 02:14:55 PM
I sometimes get this error when only transferring an album. I use ~96 kbps vorbis, so the albums are usually only a few megabytes. However, sometimes I can transfer videos of maybe 20 megs or more without issue.

Workaround: use a copier that supports pausing and resuming, such as Super Copier, or Tera Copy (both programs are for Windows). When the error happens, you can probably unplug the device, reboot, reconnect, and resume copying.
Title: Re: Sansa Fuze+
Post by: xpmule on October 21, 2012, 10:34:54 PM
any of you notice strange charging behaviour ?
what i mean is i plug in charge mode starts.. i leave it for a while
and when i come back after a while it stopped and says connected.
and when i pull out the cord and check the battery level its only partly charged.
so if i plug it in and try and charge more it does.. and then stops again after a while..
to get my device fully charge the other day i did this like 3 or 4 times LOL
and THEN it showed full or close to it.. other wise it just doesn't get close to Full charge.

my previous player was a Creative ZEN and it took a loooong time for the battery to show its age
Lithium Ion batteries obviously have a finite lifespan like almost any electronic device
and with wear and tear they decay and hold less and less of a charge to the point
where it won't stay charged for more than 5 minutes etc
My2nd oldest ZEN got so bad it would stay charged for about 4 minutes if that lol
that taught me a big lesson. Battery life is precious commodity and you should conserve it as much as possible.
And this long winded rant has a point ;)
my Fuze+ started to show major battery life decay after a month or so which was surprising !
since then its been going down hill gradually. i don't know about anyone else but i think the battery
in these Fuze+'s suck or how they are used. for example i heard in the Sansa forums before
that someone thought the battery was being used when the device was turned off and THAT
may explain the premature battery life problem i think. and of course its a usage issue.
This is one of the other reasons i chose not to use a memory card too
it will use more battery power to use the cards i'm pretty sure. it may not be much
but i feel like my device is dying early and i want preserve it before i'm forced to buy
some other player at some point. anyways, i've said it a lot at the sansa forums and i wanna say it here too
TURN OFF your device when your not using it and make every effort to conserve battery power
and NEVER charge it or plug it in unless you need to transfer or your battery level is too low.
i have seen the results of this on phones, pmp's laptops etc
some people don't care at all and 1 guy said so what i'll just buy a new one etc
but i think that's dumb ..take care of your rechargeable battery products !

anyways one else notice a premature life expectancy on the Fuze+
or strange charging behavior like i mentioned earlier ?
Title: Re: Sansa Fuze+
Post by: halonachos117 on October 22, 2012, 06:56:38 PM
any of you notice strange charging behaviour ?
what i mean is i plug in charge mode starts.. i leave it for a while
and when i come back after a while it stopped and says connected.
and when i pull out the cord and check the battery level its only partly charged.

I've noticed this, too. My player never charges past 96% or so. This behavior started appearing after Pamaury did some battery calibration (then I had problems with internal storage). The OF show 100%, so perhaps the battery need a little more calibration. I can't say about your player, though.

Also, you should try getting a portable battery charger. I have one from Duracell, and I tend to bring it whenever I think I will be away from my computer and will be listening to a lot of music. It's a bit more of a pain, but its cheaper than buying a new player. You should be able to get one form Amazon.
Title: Re: Sansa Fuze+
Post by: xpmule on October 24, 2012, 09:29:03 AM
cheaper than a new player ?
well i said that because of the battery decay
so i don't understand what you meant by that.
as long as you use the battery in the device it slowly dies
like any rechargeable battery right. for example,
i recently bought a pack of 50 AA's for my wireless mouse/keyboard
because the pile of rechargeable  AA's i bought a couple years ago don't
hold their charge very long anymore and it wouldn't matter what charger
i use with them they would still die quickly because the materials inside
are almost exhausted. see what i mean ?
So unless i can replace the internal battery i'm screwed and SOON :(
i can see the decay rate on my Fuze+ is picking up speed and it won't be
long until the battery life is too short to be viable for use anymore
and buying a new battery would be dumb i think for many obvious reasons.

To put this into perspective i bought ZEN and did a bad job taking care of it
one of the things i did was leave it plugged in to my PC ALL the time.
it wasn't long until the battery was almost dead and would only stay charged for 5 minutes.
So i bought the next generation ZEN with no hard drive and flash storage instead.
and that never started to show its age like my current Fuze+ until like a year roughly
Fuze+ within 1 month i was getting a depressed sinking feeling and could tell this thing was gradually
dying off and i remember with my ZEN month after month being impressed at how
the battery just seemed brand new month after month. And i know this is not scientific lol
but the difference between the 2 is extreme and as i implied i treated them both the same way.
I know most electronics have an estimated life span but i wonder if their was some truth
to the rumor i heard about he Fuze+ using the battery when its off..
because if this is true the implications would be bad lol
if you figure the thing is rated to last 2 years at idle (off) and it sat on the shelf for 6 months before you bought it.. then..

I dunno maybe i just got a crappy battery lol
Title: Re: Sansa Fuze+
Post by: ddscentral on October 24, 2012, 07:02:22 PM
I think he meant you should get a portable USB charger.
Portable USB charger is basically a rechargeable battery with USB ports which can be used to charge USB devices, e.g. Fuze+.

So even if the internal battery dies, you can still use the player by connecting it to a portable charger.
Title: Re: Sansa Fuze+
Post by: xpmule on October 28, 2012, 01:14:42 PM
well i don't see what difference that would make.
if the battery in the fuze+ doesn't work anymore i find it doubtful it would work.
i recently did some experiments with my expensive rechargeable shaver
that is showing its age and won't hold a charge and whether i plug it into the wall
or not makes no difference unless i cut the power wires on the internal rechargeable batteries.
I ended up soldering in brand new replacement rechargeable batteries using the same spec's.
I think the fuze+ would work the same way ? On the original firmware you would never be able to
use the device either (can't charge + use it at the same time)

I've never seen a portable usb charger before and i doubt i'd ever buy one
when i have a matching wall cable for my device. and if you need to use a cable or "portable charger"
i think you ALREADY screwed and missing the point ;)
(time to pull the wallet out and buy a replacement Lithium Ion battery or move on with life..)
Title: Re: Sansa Fuze+
Post by: monoid on October 28, 2012, 02:17:59 PM
It cannot be generalised, device might run with worn-out battery or not (when plugged in a charger). On contrary to your experience, my shaver does run and very old notebook also.

I've read somewhere that design life of li-ion/li-pol battery is not more than aprox. 5 years (even if not used) - on average. I have 8-7 year's old iRivers H120 and H140 and battery seems to be still quite OK. I used it 12 hour a day for several years....
Title: Re: Sansa Fuze+
Post by: ddscentral on October 28, 2012, 04:05:41 PM
From my experience, I think many (if not most) devices charged from USB should work without batteries. Some, however, might require a battery to be present (even if it's dead) to work, but should run from a charger if it supplies enough current.

I guess it all depends on how device works. Some devices can run directly from charger, some need a battery to work (but can work with a dead battery), some won't work at all.
Title: Re: Sansa Fuze+
Post by: halonachos117 on October 28, 2012, 06:00:03 PM
I hate to be the wet blanket here, but this thread really isn't the place to talk about dead batteries. I would go the Forums on Sandisk.com or AnyThingButIpod.com. I know I haven't exactly been following that rule by making my suggestion (and really, all it was meant to be was a suggestion, not a reinvented wheel). However, if you wish to buy a permanent battery replacement (ie, desolder your old battery, and solder a replacement), there is a separate section in this forum for that.

In this section, we are supposed to talk about developing Rockbox for the Fuze+. It's not really meant to talk about batteries or any other hardware, except in the case of figuring out how to make Rockbox work on said hardware.
Title: Re: Sansa Fuze+
Post by: monoid on October 31, 2012, 10:31:07 AM
I would like to ask about the recording ability. It is the only thing I miss in this RockBox port. I had the feeling it was finished and close to being issued 2 months ago, but nothing has happened since then.

What are the plans to implement it, if any?

Anyway, thanks to all developers for all the work. RockBox port for Fuze+ just rocks!
Title: Re: Sansa Fuze+
Post by: [Saint] on October 31, 2012, 06:02:09 PM
<snip>...I had the feeling it was finished and close to being issued 2 months ago, but nothing has happened since then...<snip>

Fact of the matter is, as I'm sure you are at least partially aware, the developers work on what they want to work on when they want to work on it. The nature of this project allows you to contribute yourself if you feel that development is going slower than you would like it to.

Please don't read this as: "If you don't like it, go and do it yourself", but please do read it as "The maintainers of new ports are more often than not working largely alone, doing a job that has the potential to consume many hundreds of man hours, and those that would like to see a particular feature implemented or a particular bug squashed should seriously consider taking a crash course in C, setting up a development environment, checking out the source, and contributing to those areas themselves."


[Saint]
Title: Re: Sansa Fuze+
Post by: monoid on November 01, 2012, 02:31:24 PM
I am sorry if it seemed that I am complaining.  :-[

I am very happy that someone took the tedious task to make Fuze+ usable when SanDisk didn't do the job. It is just perfect, as it is now. :)

I was just curious what happened, as it seemed to me, that it was prepared for release. I can live without recording ability, if it is not implemented at all...
Title: Re: Sansa Fuze+
Post by: xpmule on November 03, 2012, 09:30:17 AM
any of you notice strange charging behaviour ?
what i mean is i plug in charge mode starts.. i leave it for a while
and when i come back after a while it stopped and says connected.
and when i pull out the cord and check the battery level its only partly charged.

I've noticed this, too. My player never charges past 96% or so. This behavior started appearing after Pamaury did some battery calibration (then I had problems with internal storage). The OF show 100%, so perhaps the battery need a little more calibration. I can't say about your player, though.

Also, you should try getting a portable battery charger. I have one from Duracell, and I tend to bring it whenever I think I will be away from my computer and will be listening to a lot of music. It's a bit more of a pain, but its cheaper than buying a new player. You should be able to get one form Amazon.

notice the first sentence you quoted ?
and buddy we have been talking back and forth over at Sansa long before i came over here
so you already know my name lol
I brought this up because like everyone else is saying normal behaviour is normal
and what i'm seeing is *obviously NOT.
a) The charging behaviour is weird. (It doesn't get fully charged)
b) The charge doesn't last.. (even when device is off / as reported many times at Sansa forums)

so YES it's related.. think about it
or should i explain ?
Title: Re: Sansa Fuze+
Post by: halonachos117 on November 04, 2012, 08:10:46 PM
so YES it's related.. think about it
or should i explain ?

Not to seem rude, but please don't. At least not here. 8)

Once again, this is a SOFTWARE DEVOLOPEMENT THREAD. There's a hardware section of this forum you can use if you wish. If  you wish to permanently upgrade your battery, there's also a "Repairing and Upgrading Rockbox capable Players" thread with people who could help you with that. Otherwise, I guess you're out of luck. :'(
Title: Re: Sansa Fuze+
Post by: pamaury on November 13, 2012, 05:47:42 PM
Hi all,
to reply to the few complains about battery life, I would like to state again that 1) the battery life will naturally decrease over time, this is not related to rockbox 2) rockbox on the fuze+ still lacks some power optimisations with explains the lesser lasting battery but we do our best to improve this.

On the good side, I would like to point out that I (hopefully) solved the audio pop on startup in the current HEAD so I would greatly appreciate feedback on this. I also made a RMAA test to compare the fuze+ OF with rockbox and the results can be seen here: http://amaury.pouly.free.fr/Images/Comparison.htm (http://amaury.pouly.free.fr/Images/Comparison.htm). The results are encouraging but there is a lot of distortion compared to the OF so I still need to improve this.
Title: Re: Sansa Fuze+
Post by: RipCurl on November 13, 2012, 06:50:57 PM
hmm, THD and  intermodulation distortion seem to be A LOT worse than OF and Intel Onboard Soundcard(?).... looks like the rockboxed fuze+ sounds (at current state of development) not as good as the OF fuze+...

E: maybe some eq involved?

E: now the audio pop is lot more gentle/almost unhearable. the white noise before playing the first track after booting is gone also....
Title: Re: Sansa Fuze+
Post by: monoid on November 14, 2012, 04:55:37 AM
Hi Pamaury,
thanks a lot for your work on Sansa Fuze+. OF was almost unusable with more music loaded in....

Thanks for audio quality comparison. Are the high values of low frequency "noise" related to a problem that I started discuss in this thread?
http://forums.rockbox.org/index.php/topic,41608.0.html (http://forums.rockbox.org/index.php/topic,41608.0.html)

I noticed it first in Fuze+ (but it seems to me that it was not always like that....) and after RockBoxing iRiver H120 also in iRiver, which was quite surprise for me. In iRiver, there is no "noise", if optical digital output is used. So I guess, it must be related to D/A conversion in both devices.

I hope, it helps.
Title: Re: Sansa Fuze+
Post by: metaphys on November 14, 2012, 06:52:23 AM
noise beep on startup much better here too

EDIT:
What about RDS I'am on the impression that it is working much better now. Wiki port's page still mention problem should I correct it?
Title: Re: Sansa Fuze+
Post by: fsclavo on November 14, 2012, 07:48:11 AM
Thanks again for your work pamaury!
The startup pop sound is almost unhearable.

Title: Re: Sansa Fuze+
Post by: pamaury on November 14, 2012, 08:16:04 AM
Yes the RDS is working much better because we relaxed and improved the parsing a few months ago.
@metaphys: go ahead and fix the wiki :)
Title: Re: Sansa Fuze+
Post by: metaphys on November 15, 2012, 05:17:43 PM
ok wiki corrected.

what about my touchpad sensitivity patch?
http://gerrit.rockbox.org/r/#/c/123/
Title: Re: Sansa Fuze+
Post by: metaphys on November 18, 2012, 01:30:37 AM
I don't know if you guy are still having issue with clock, but you might want to have a lock here:
http://forums.rockbox.org/index.php/topic,41766.0.html
Title: Re: Sansa Fuze+
Post by: pamaury on November 30, 2012, 10:54:02 AM
I recall to everyone that this thread is *not* meant to fix problems, it's about development only. If you have problems with your device, please first have a look first on the wiki  http://www.rockbox.org/wiki/SansaFuzePlusPort (http://www.rockbox.org/wiki/SansaFuzePlusPort) and then  ask on IRC http://www.rockbox.org/irc/ (http://www.rockbox.org/irc/). There is known problem about the clock/date which might stop, please see here http://forums.rockbox.org/index.php/topic,41766.0.html (http://forums.rockbox.org/index.php/topic,41766.0.html) and there is some noise while playing sound which is still to be fixed. It is also known that keypress while backlight is off behave strangely.
Title: Re: Sansa Fuze+
Post by: pamaury on December 02, 2012, 05:53:35 AM
I changed some audio code to try to improve the audio quality, here is the result: http://amaury.pouly.free.fr/Images/Comparison3.htm (http://amaury.pouly.free.fr/Images/Comparison3.htm). As one can see, with a correct bias this is much better but the frequency response suffered a bit.
Title: Re: Sansa Fuze+
Post by: xpmule on December 16, 2012, 03:16:55 PM
Not sure i can wrap my head around what you said pamaury lol
did you commit your new changes ?

I looked in this topic because i have been having strange key press behavior for a while
and i have been randomly dropping by and updating to newer builds.. so i dunno
Hard to explain but the navigation is just going to hell and any problem i can think of has been happening
some times stuck key presses sometimes skipping drastically through menus etc
So i cam here to see if anyone was seeing the same.. doesn't look like it

I think i'll try and reformat and reset all settings etc and see if that helps ad maybe clean it too
although its already pretty clean (touchpad area) it does get finger prints on it though cause well you press it lol

Thanks for your continued efforts :)
Reading the recent activity occasionally i see your coding skills dwarfs mine so much i doubt there would
be much point in trying to contribute anything with you guys lol
You got some serious skills and the technical understanding of some advanced stuff for sure !

Last minute question..
Is there a future goal to get Rockbox to charge the device or should we just get used to booting orig firmware for that ?

Thanks also to the other contributors too for example J.Gordon
He's been working endlessly over time to improve a lot such as GUI related stuff i noticed. (experiments / fixs etc)

Not a lot i can do to support the project but its of such high quality that i have a perm interest..
Even if i don't post comments i'm happy to see the recent activity page HAS recent activity. lol
Rockbox is a project in its own league and deserves my butt kissing lol
Title: Re: Sansa Fuze+
Post by: halonachos117 on December 17, 2012, 05:47:13 PM
Rockbox recharging was implemented a long time ago. If you have a recent build, which you said you do, you can recharge easily. Also, if you have a new bootloader, you charge it right from the moment you plug it in.

IF you're device is not charging, yo might want to report this as a bug.
Title: Re: Sansa Fuze+
Post by: xpmule on December 22, 2012, 02:06:34 AM
i mentioned this on page 37..
i also quoted that it says in the manual that your suppose to plug in and use orig firmware.

from the manual..

Quote
3.3  USB Charging

To charge your player over USB, hold any button while plugging it in. This will prevent it from connecting to your computer and let you continue to use it normally. Your player must already be in Rockbox for this to function.

So if you hold the button and plug it in what happens ? lol
Am i insane or does that sound misleading ?
Also its funny no one said anything after my comment on page 37.

Anyway i tried it and it did seem to charge now.. what i did was turn on rockbox before i plugged in normally
Before the bat was at 50% and i just checked and its at 83%.
I must not have clued in on the changes when they happened (i havn't tried doing that in a long time)

So thanks for setting me straight ;)
it works :)
Title: Re: Sansa Fuze+
Post by: saratoga on December 22, 2012, 03:05:33 AM
Also its funny no one said anything after my comment on page 37.

You said that you figured it out and that it was charging.  So probably people assumed that you figured it out.

Anyway, this is a development thread.  It seems like you're not doing development, so you probably shouldn't be posting in this thread. 
Title: Re: Sansa Fuze+
Post by: xpmule on December 24, 2012, 06:30:40 AM
thats a bit rude

and did you say that to every other person that is making comments not related to development ?
why are you singling me out of all of us ?

and no don't worry i won't make any more comments..

a reminder to us ALL that this topic os for development would have sufficed
and the need to single me out was not needed.

Screw it.. I'm not gonna waste my time around here anymore

edit:
to make this clear.. i only started talking in this forum thread AFTER reading a TON of other people (talking about whatever they want related to the player)
And the way i see it is if there is an issue ? How about a suggestion to fix it ?
Last time i checked this was the ONLY topic where people are discussing this.
So a suggestion to create a new topic may have been a bit more friendly then "hey xpmule be quiet"

I don't deal with jerks and i've noticed some attitude already so i've had enough and won't be around anymore.
Feel free to run your community anyway you want..
Title: Re: Sansa Fuze+
Post by: [Saint] on December 24, 2012, 09:26:23 AM
"It's OK, because everyone else did it too" doesn't hold up, I'm afraid.

You were not "singled out" as you put it, in a post on December 1st, pamaury reminded us all that this is a development thread:
I recall to everyone that this thread is *not* meant to fix problems, it's about development only. If you have problems with your device, please first have a look first on the wiki  http://www.rockbox.org/wiki/SansaFuzePlusPort (http://www.rockbox.org/wiki/SansaFuzePlusPort) and then  ask on IRC http://www.rockbox.org/irc/ (http://www.rockbox.org/irc/)...

Then, on the 17th of December (it seems like a big gap, but it is all on the same page, and there is only one post in between), you do exactly what you were asked not to do.

You state that:
a reminder to us ALL that this topic os for development would have sufficed
And, in my opinion, this was done. Additionally, if you go through the ~600 or so other posts in this thread, you can find many more reminders of this type.

You were not singled out, you were asked not to do something which you did anyway, and you got called on it, at which point you threw your toys and decided to go and play somewhere else. As a side note, if you felt that you were being singled out, this wasn't the way to handle it.


[Saint]
Title: Re: Sansa Fuze+
Post by: pamaury on December 25, 2012, 07:33:25 PM
Hi all,
development continues ! I'm back with a new attempt at making frequency scaling actually working and it required quite a few changes. The current code is not perfect (EMI clock is not changed) but it seems stable on my fuze+ at least. I fixed at least two problems: voltage regulators need time to settle and clock settings need to be carefully done ! Anyway, if you want to check, you can find the code here:
http://gerrit.rockbox.org/r/#/c/374/ (http://gerrit.rockbox.org/r/#/c/374/)
I encourage you to test it if you can compile the code (it's a one liner change to enable it) and report success/failure on gerrit and not in this thread if possible.
If you have even more time, it would be very interesting to see the effect on battery life by running a battery bench.

On the more technical side, there are few settings which we can tweak here:

I also implement lcd flip and invert since someone asked for this feature. I tested it on my fuze+ which has lcd kind "st8873". You can see your lcd kind in debug>HW Info> (press next many times). But it should work on all kinds.

NOTE: if you build rockbox from the source, you will need probably to do a "make clean" because the lcd flip/invert pulls in new strings. Otherwise the UI will display wrong strings !
Title: Re: Sansa Fuze+
Post by: pamaury on January 09, 2013, 08:06:20 PM
Hi all,
I've committed some work on EMI frequency scaling. This means that rockbox can now use the lowest and highest performance settings. I expect this to improve the maximum performance (for example doom) while improving battery life while unboosting. This is disabled by default but people who can compile can test this feature by uncommented this line in firmware/export/config/sansfuzeplus.h:
Code: [Select]
//#define HAVE_ADJUSTABLE_CPU_FREQIf you have some time, I would be very interesting by battery benchmarks with and without this feature enabled.
Title: Re: Sansa Fuze+
Post by: Roboturner913 on January 15, 2013, 03:16:50 AM
whatever you did, it worked.  i just got 29 hours 11 minutes on a charge, and even better the whole thing is much more stable. screen doesnt even flicker anymore.

so much respect to you for making the fuze+ usable....actually forget usable, its damn close to being a powerhouse with all the recent improvements.
Title: Re: Sansa Fuze+
Post by: metaphys on January 16, 2013, 01:56:11 AM
Test on two different device have proven an incredible 39h of continuous playback (mp3 128) for one charge!  ;D (that is to say with standardize rockbox battery bench method: no backlight, device being left alone playing a very big playlist)

Frequency scaling should be soon activated by default...
Title: Re: Sansa Fuze+
Post by: buckminster on January 20, 2013, 11:32:44 AM
I take it frequency scaling is enabled now?  8)

http://git.rockbox.org/?p=rockbox.git;a=blob;f=firmware/export/config/sansafuzeplus.h
Title: Re: Sansa Fuze+
Post by: halonachos117 on January 20, 2013, 07:46:50 PM
Indeed, it is! HERE (http://git.rockbox.org/?p=rockbox.git;a=commit;h=e9f8846ce2b7967f9fa14f565b6970b900b1618e) is the proof.
Title: Re: Sansa Fuze+
Post by: fsclavo on January 23, 2013, 01:44:54 PM
WOWWWW!!
I didn't a battery benchmarl, but simply using my fuze+ with new frequency scaling enabled, I noticed a huge improvement on battery life. Many thanks!!
Title: Re: Sansa Fuze+
Post by: Roboturner913 on January 24, 2013, 03:30:51 AM
Another battery bench leaves me around the 29 hour mark, but I just realized my standard listening settings probably have a lot with that - EQ on, bass at +20, treble at +9, MP3 files at 360 kpbs.
Title: Re: Sansa Fuze+
Post by: sstavross on January 24, 2013, 06:43:59 PM
Hi!

My first post here, as I bought fuse+ a few day ago!
First I want to thank you all the devs for this wonderfull firmware! It is almost perfect! My player is a different player with rockbox!
I have installed the lattest release (02130124) and before that I had tested the 20130121. The only little problem for me is that I see some screen flickering when I start playing a song in the now playing screen. It starts flickering and after 7-10 seconds it stops. I have also constant flickering when I use the picture flow mode. Is this ok or have I done something wrong?
Title: Re: Sansa Fuze+
Post by: Roboturner913 on January 24, 2013, 07:34:04 PM
The flicker happens when your player is accessing the memory. Once it accesses enough memory to build a buffer, the flickering stops, as you noted it takes maybe 10 seconds or so.

It's normal, although it was less frequent/noticeable before the frequency scaling changes were made (not that I'm complaining). But I bet it'll get ironed out soon.
Title: Re: Sansa Fuze+
Post by: oh_fuck_im_a_ghost on January 25, 2013, 09:24:42 PM
What are the start up times like on a rockboxed Fuze+ compared to the original firmware?  I went with a Clip Zip ONLY because I read about long boot up times with the OF.
Title: Re: Sansa Fuze+
Post by: pamaury on January 26, 2013, 07:54:28 AM
The Fuze+ OF starts in about 9/10 seconds whereas rockbox boots in about 4/5 seconds. It is hard to beat the Sansa AMSv2 (clipv2, clip+, clip zip) with respect to start up time.
Title: Re: Sansa Fuze+
Post by: monoid on January 26, 2013, 01:25:08 PM
I haven't used OF for a year or so, so I do not remember exactly. But it seems to me that OF with full 16 GB memory and 32 GB uSD card have booted many tens of seconds. Maybe a minute. Ill driver of touchpad and extremely long boot time were the main reason I switched to RB.

EDIT:
Just to avoid confusion...
The startup with RB is fast, but of course not instant. Few seconds.
Title: Re: Sansa Fuze+
Post by: buckminster on January 27, 2013, 10:15:33 AM
Yes, without a microSD card inserted, the OF is reasonable in start time; with one, however, it's an insanely long. My guess is it rebuilds the database on the microSD card every time. That alone would convert anyone that knows of Rockbox. I also found that removing album thumbnails that Windows creates improves start time for the OF (since it's building a DB for it's photo viewer).
Title: Re: Sansa Fuze+
Post by: Roboturner913 on February 03, 2013, 04:20:22 AM
Getting some hangups with the past few updates. Extreme slowdowns while playing files - happens completely at random. Any button press would take a 5-6 second delay before executing the action, buffer would take up to 30 seconds to build up, screen fade-in/fade-out was noticeably slow.

Went back to an earlier build of Jan. 15 which solved the problem. Doesn't bother me at all, just making it a known issue.
Title: Re: Sansa Fuze+
Post by: pamaury on February 03, 2013, 12:26:40 PM
Can you bisect the problem to find which commit caused this ? Or at least get a smaller window of when such a breakage could have happened.
Title: Re: Sansa Fuze+
Post by: Roboturner913 on February 03, 2013, 01:23:56 PM
Honestly, I don't know. somewhere between Jan. 15 and the first build with the 10-band EQ. I went a couple weeks without updating. I'll experiment with it a little and see what happens. I was inclined to call it a hardware failure until rolling back erased the problem.
Title: Re: Sansa Fuze+
Post by: pamaury on February 03, 2013, 01:36:53 PM
I cannot reproduce the problem with the latest version, can you try to remove the .rockbox dir, do a clean install with the HEAD version and if it still fails, post a bug report describing exactly what you do.
Title: Re: Sansa Fuze+
Post by: Roboturner913 on February 04, 2013, 10:17:59 AM
I'm not sure what you mean by HEAD version. But when I first noticed the bug I did format the player and installed RB from scratch with the daily build from Jan.31 and it still happened. Same with the Feb. 2 build.

As to what triggers it, not sure. Seems to be completely random. Sometimes happens when I'm playing a file and then go into the database and pick another album. Sometimes happens when a file is already playing with the backlight off and I press the button to go into the menu (the slow "fade in" I mentioned earlier). Seems to be no rhyme or reason to it at all.

It reminds me of an old laptop I have that just decides to take a dump every once in a while. That I know is a hardware problem, which is why I assumed the same for the player. But rolling back to earlier builds with no issues pretty much rules that out, I guess.

EDIT: Now that I go back and look at it, its either f2dfc84-130126 from Jan. 27 or 1789b71-130122 from Jan. 23. One of those was the first time I noticed the problem. Not sure which, but I'll try them both when I can.

Title: Re: Sansa Fuze+
Post by: [Saint] on February 05, 2013, 03:29:35 AM
I'm not sure what you mean by HEAD version

This link will always point to a Fuze+  binary compiled from git HEAD (http://build.rockbox.org/data/rockbox-sansafuzeplus.zip). Backup your .rockbox directory (if desired) and remove it from the device, then extract the linked binary to the root of the device and see if you can still replicate the issue.
If you can replicate the issue, please report it on Flyspray, our Bug Tracker (http://www.rockbox.org/tracker/index.php?type=2), making a note of the specific firmware version listed in:

Quote
System -> Rockbox Info -> Version: xxxxxxx-13****
(xxxxxx is a unique 7 digit alphanumeric version string, 13**** is the build date formatted as YYMMDD)


[Saint]
Title: Re: Sansa Fuze+
Post by: fsclavo on February 05, 2013, 12:10:43 PM
Getting some hangups with the past few updates. Extreme slowdowns while playing files - happens completely at random. Any button press would take a 5-6 second delay before executing the action, buffer would take up to 30 seconds to build up, screen fade-in/fade-out was noticeably slow.

Went back to an earlier build of Jan. 15 which solved the problem. Doesn't bother me at all, just making it a known issue.

Same here. The player keeps playing (with some minor audio gaps) but the response times are so slow that becomes unusable. It's like the processor doesn't scale up frequency when load is increased. I'm using 42a725f.
Title: Re: Sansa Fuze+
Post by: pamaury on February 06, 2013, 11:55:49 AM
Please post bug reports for those issues, remember that this thread is about development only and we try to keep it reasonably readable.
Title: Re: Sansa Fuze+
Post by: fsclavo on February 07, 2013, 03:49:33 PM
Opened task http://www.rockbox.org/tracker/task/12821
Regards
Title: Re: Sansa Fuze+
Post by: sdf5 on March 11, 2013, 12:15:19 AM
Hi,

My Fuze+ with Rockbox was working fine for a while but now it's behaving strangely and I'm not sure if it's related to Rockbox firmware or something else.

The problem now is that when my Fuze+ is disconnected from PC it stays dead and doesn't respond to on/off button at all. When I connect it to PC it connects to PC in USB mode and I can access the player and transfer files between the Fuze+ and PC. The following messages are shown on Fuze+'s screen when it's connected to PC:
  Boot version: 1.0
  org=CAFEBABE addr=4000000
  USB: Connecting
  Boot Loader USB mode

When I press and hold the on/off button while Fuze+ is connected to PC, Fuze+ seems to reboot itself going blank and then showing the above message again.

I tried to reinstall Rockbox using the installation utility and it seems to work fine (with exception that the player went dead instead of rebooting itself) but but it did not resolve the problem.

Any ideas? Thanks
Title: Re: Sansa Fuze+
Post by: pamaury on March 11, 2013, 03:15:05 AM
The battery might simply be flat and our bootloader doesn't charge currently. Try booting to the OF in usb (hold volume down when plugging the device).
Title: Re: Sansa Fuze+
Post by: sdf5 on March 11, 2013, 07:56:50 AM
The battery might simply be flat and our bootloader doesn't charge currently. Try booting to the OF in usb (hold volume down when plugging the device).

That was it, thank you for your help.
Title: Re: Sansa Fuze+
Post by: Vkins on March 18, 2013, 02:17:47 AM
Playing music seems to be broken right now. There hasn't been changed anything in the Fuze+ code recently if I recall correctly, but no matter what I put on there (mp3/ogg/wav tested)...it doesn't play anything and just returns to the main menu.

Can someone reproduce & confirm this? I don't know when that happened, but it didn't work with yesterdays build.
Title: Re: Sansa Fuze+
Post by: pamaury on March 18, 2013, 05:26:23 AM
I just checked and it works fine on mine. Could you check with another build, perhaps there was a buidl problem ?! You might have unmatched codec/core, that's the usualy explaination of why it returns to the main menu immediately. If it still doesn't work, post a bug report after trying to erase the.rockbox direction and doing a clean install.
Title: Re: Sansa Fuze+
Post by: Vkins on March 18, 2013, 01:09:55 PM
Yup, indeed a problem on my end.
Removed and reinstalled Rockbox, now it works. Sorry.  :-\
Title: Re: Sansa Fuze+
Post by: halonachos117 on March 18, 2013, 07:55:58 PM
I've had the same issue with build 2febee5-130227. It seems to happen if I plug in from the debug battery screen, and persists until I unplug, at which point my player then works like normal.
Title: Re: Sansa Fuze+
Post by: gontofe on May 27, 2013, 04:37:03 AM
Apologies if this has already been covered - my Fuze+ hangs on the splash screen in 2 circumstances:

If it is connected by usb to my computer (shows USB bootloader on screen) when the Fuze+ power is off, once I have finished transferring files etc and unmount, the splash screen comes up (very bright), and it hangs.

If I connect it to the power supply (with Fuze+ power off), again the splash screen appears and it hangs.

Am I doing something wrong?

I am using bootloader 1.0 and RB version 30fe6eb-130526.
Title: Re: Sansa Fuze+
Post by: pamaury on May 27, 2013, 10:14:46 AM
Hello,
this is a known issue with the current bootloader. It should get better with the next bootloader and the partial rewrite to be committed soon. Admitted this is annoying.
Title: Re: Sansa Fuze+
Post by: gontofe on May 28, 2013, 06:55:28 AM
Ah, ok, not just me then!

Thanks for that.


Probably not the right time/place for a feature request, but I am always caught out by the lock behaviour. I would generally expect it to work more like the iPod lock switch, i.e. be available from all screens not just WPS, and to disable other key input while locked (currently screen activates with keys locked message). This would mean you could use the one master lock button.

Is this a terrible idea/heinously complicated to implement?

**edit**


Just seen this http://www.rockbox.org/mail/archive/rockbox-dev-archive-2013-03/0005.shtml - where you ask about this exact thing (global lockscreen, disable touchpad, screen off).

I wish I could be of more assistance as my C++ knowledge is nil at the moment, and I can't access git via cygwin at work (proxy authentication), otherwise I'd have more of a play myself!

So for the moment, just a +1 for this.
Title: Re: Sansa Fuze+
Post by: saratoga on May 28, 2013, 12:15:01 PM
I wish I could be of more assistance as my C++ knowledge is nil at the moment, and I can't access git via cygwin at work (proxy authentication), otherwise I'd have more of a play myself!

Good news, we don't use c++ and do not recommend using cygwin ;)
Title: Re: Sansa Fuze+
Post by: gontofe on May 28, 2013, 04:32:58 PM
Touché.

Not sure about installing the VM at work either ;)
Title: Re: Sansa Fuze+
Post by: gontofe on June 03, 2013, 03:03:24 AM
OK, checked out the code and successfully built at home.

Found this: http://gerrit.rockbox.org/r/#/c/421/ applied and rebuilt. Looks like it works perfectly to me.

For the Fuze+, is it right to use origin/master or should I be switching to another branch?

Not sure I understand about hooking up the keylock to the backlight to stop the screen turning on when the touchpad is pressed when keys are locked.

In action.c, could this section:

 300         else
 301 #if (BUTTON_REMOTE != 0)
 302             if ((button & BUTTON_REMOTE) == 0)
 303 #endif
 304         {
 305             if ((button & BUTTON_REL))
 306                 splash(HZ/2, str(LANG_KEYLOCK_ON));
 307             return ACTION_REDRAW;
 308         }

be linked to a setting ("display keylock on message" or similar)?
Title: Re: Sansa Fuze+
Post by: Vkins on June 06, 2013, 01:49:05 AM
Something else:
Does anyone else experience weird backlight flickering on the Fuze+?
With flickering I don't mean on/off but alternating between higher/lower brightness.
When using the OF it works fine so I assume it's not a hardware failure.
Title: Re: Sansa Fuze+
Post by: gontofe on June 06, 2013, 07:38:48 AM
see http://www.rockbox.org/wiki/SansaFuzePlus#Backlight_flickering
Title: Re: Sansa Fuze+
Post by: halonachos117 on June 17, 2013, 11:51:47 PM
Hi all, I have good news and bad news. The good news is, it seems the annoying freeze experienced when booting by plugging in a USB power source has been fixed. The bad news is that once again my screen looks like a cathode ray tube. I have a ST7783 LCD.

Update: Player seems to freeze with latest batch of updates
Title: Re: Sansa Fuze+
Post by: pamaury on June 18, 2013, 06:12:52 AM
Indeed, a bug made it into the trunk. We bisected the problem and it is now fixed in trunk. Sorry for the inconvenience.
Title: Re: Sansa Fuze+
Post by: RufusA on June 20, 2013, 08:30:25 AM
I notice that the keylock function has now been added to the FM Radio screen in the latest dev release. I guess as a result of this:

http://gerrit.rockbox.org/r/#/c/421/

A much needed and useful addition - thanks to all who made it happen!

Rufus,.
Title: Re: Sansa Fuze+
Post by: metaphys on June 25, 2013, 07:49:09 AM
Hey pamaury! Here's another point for deactivating touchpad while being locked:
http://www.rockbox.org/tracker/task/12874

 ;)
Title: Re: Sansa Fuze+
Post by: pamaury on June 27, 2013, 04:29:31 AM
Some users reported having problem with the micro-sd slot not being detected until plugged to a computer with USB.
I have investigated the issue thanks to Jean-Louis Biasini and produce a tentative fix, the patch can be found here:
https://gist.github.com/pamaury/5879015 (https://gist.github.com/pamaury/5879015)
If some of you want to test it, please report results on IRC. I'll commit this with some cleanup soon.
Title: Re: Sansa Fuze+
Post by: ildarion on June 29, 2013, 03:40:00 AM
I woult like to use wake up function (like I do before, month ago), but now, I think it's dosen't work. My clock it corretly fine, i choos the time for the wake up, i select "play". Sansa tell me it's ok, in XXhours it will wake. So now à shutdown him and after nothing...

I do not think the problem comes from the onscreen user (me) since I had used before with success.
Title: Re: Sansa Fuze+
Post by: pamaury on June 29, 2013, 05:37:24 AM
Indeed, the alarm is not implemented, mostly because no one complained before :) I will have a look at this, the chip has support for alarm wake up so it shouldn't be a big deal.

Edit: I removed some posts, this forum thread is supposed to be development only, bug reports go on Flyspray.
The freezing (with very bright screen) when booting after USB has been plugged is a known issue, it should get fixed by the next bootloader when the issue is completely unerstood.
By the way, the alarm function will also require a bootloader change.
Title: Re: Sansa Fuze+
Post by: psycoxl on July 01, 2013, 05:41:38 PM
Some users reported having problem with the micro-sd slot not being detected until plugged to a computer with USB.
I have investigated the issue thanks to Jean-Louis Biasini and produce a tentative fix, the patch can be found here:
https://gist.github.com/pamaury/5879015 (https://gist.github.com/pamaury/5879015)
If some of you want to test it, please report results on IRC. I'll commit this with some cleanup soon.

I have the same problem,  but can you maybe provide an old firmware? Cause i can't find it anywhere and i don't know how to use the patch.
Title: Re: Sansa Fuze+
Post by: pamaury on July 01, 2013, 05:46:49 PM
I just committed the SD init card fix, this should fix the issue of the sd card not showing up in USB. I also committed the alarm wake up work but it is currently unsuable because the bootloader is not fixed.
Title: Re: Sansa Fuze+
Post by: psycoxl on July 02, 2013, 04:16:46 PM
Perfect it works again (like a charm) Thank you for the fast update :)
Title: Re: Sansa Fuze+
Post by: pamaury on July 07, 2013, 10:38:17 AM
Hi all,
I have committed some power management fixes which should hopefully fix the freezing issue after USB bootloader mode. Any feedback on this issue would be appreciated. I will also upload a release candidate for the new bootloader today or tomorrow which should bring charging to USB bootloader mode and also fix the alarm wake up.
Title: Re: Sansa Fuze+
Post by: pamaury on July 12, 2013, 06:43:39 AM
Hi all,
I have some good news: here is a release candidate for the new bootloader !
Link: https://www.dropbox.com/s/86f4v7hmjw2hjmi/firmware.sb (https://www.dropbox.com/s/86f4v7hmjw2hjmi/firmware.sb)
To install it, download the file, put it at the root of your device (be sure to name it firmware.sb), power off and reboot into the OF (by holding volume down). It will trigger an upgrade and then you're done. I recall you that is it a beta software, it may or may not work, use it at your own risks. That being said, I would appreciate that some people here try it and give some feedback. The new features of this bootloader are:

About recording, there has been some progress: the player no longer crashes and actually records but for some odd reasons, it records silence. I'll will have a look at this annoying issue.

PS: sorry for deleting the posts but the policy of development threads is to remove posts which ask about progress
Title: Re: Sansa Fuze+
Post by: rba on July 12, 2013, 11:00:44 AM
Yes !! the wake up alarm and the charging in the usb are working.

Can I use this bootloader in a sansa fuze that has many bugs ?

Thank's a lot
Title: Re: Sansa Fuze+
Post by: pamaury on July 12, 2013, 07:43:27 PM
I have committed some recording fixes. Apparently the recording volume setting were broken by a recent general rework, which explain the near silence: volume had to be set close to maximum to hear something...
Title: Re: Sansa Fuze+
Post by: pamaury on July 14, 2013, 03:36:20 AM
Thanks for the feedback of some people, apparently is it confirmed that battery charging works with the new bootloader. On the other hand, alarm seems random. I opened a bug report, please add any information here: http://www.rockbox.org/tracker/task/12879 (http://www.rockbox.org/tracker/task/12879).
I also realised that there is a problem with the volume keys, I know the issue but opened a bug report here: http://www.rockbox.org/tracker/task/12880 (http://www.rockbox.org/tracker/task/12880).
Any other issues should also go on flyspray please: http://www.rockbox.org/tracker/ (http://www.rockbox.org/tracker/), try to put "[fuze+]" or correctly set the player to Sansa Fuze+ in it.
It has been reported that recording works too, but if you encounter any corner case, please report it on flyspray too.
Thanks
Title: Re: Sansa Fuze+
Post by: elvi2008 on July 14, 2013, 09:56:57 AM
I have a problem with Sansa Fuze +. I've used Rockbox for a year, yesterday it stopped to turn on with the power button, but turns off with the same button.
It turns on only when connected via USB to any device(tuner, TV, PC), the computer says USB device is not recognized and there is nothing to see or to do.
I have managed to access native Sansa about 5 times, the picture jumped on the setup menu, but after several clicks I've entered setup menu to check msc usb settings and the picture was stable. The same result with the computer. Now i can't access native firmware. If I just connect with the computer via USb the player turns on and I can use it. While pressed volume- button and USB connected it doesn't connect or turn on. If I release volume- button Rockbox turns on and the player works fine even if disconnected from the computer. Then I turn it off and can't turn it on again and I have to connect it to the computer again. After all this a new problem appeared: volume+ button started to block the display. I can change volume only via volume settings. The player hasn't been covered with water or fallen.
Title: Re: Sansa Fuze+
Post by: pamaury on July 14, 2013, 10:39:39 AM
@elvi2008: be warned that reposting while your post has been removed is considered very rude ! I will not remove it again but I will ask to not *NOT* post again on the same problem. For these kinds of problems it's better to use flyspray (http://www.rockbox.org/tracker (http://www.rockbox.org/tracker)) or even IRC (http://www.rockbox.org/irc/ (http://www.rockbox.org/irc/)). That being said, my only advise is: come on IRC, it looks like a hardware problem.
Title: Re: Sansa Fuze+
Post by: metaphys on July 16, 2013, 08:22:38 AM
so as some of you already notice, we have now a touchpad sentivity settings that pamaury and I implemented. (general setting > system)
I also improved the keymaps on FM.
Also some correction about on some keymaps hint that were wrong
Title: Re: Sansa Fuze+
Post by: fsclavo on July 16, 2013, 10:53:27 AM
Thanks devs for this great work!
Pamaury: I downloaded firmware.sb and tried to upgrade bootloader on my fuze+, but OF is "ignoring" the upgrade. I tried several times, booting to OF, resetting the device, but OF always boot in normal mode, just like if firmware.sb doens't exists in root folder.
Do you have any ideas?
Title: Re: Sansa Fuze+
Post by: pamaury on July 16, 2013, 11:06:20 AM
Try to download the file again, make sure it is named correctly with no space, cleanly umount the disk before unplugging.
Title: Re: Sansa Fuze+
Post by: monoid on July 18, 2013, 09:40:38 AM
Many thanks to developers. New bootloader seems to work well, no problems so far. Charging started to work.
Also thanks for adding recording recently. And also it seems to me that touchpad reacts now in more predictable way. Even before it was by great deal better than original by Sansa, but now it seems to be fully satisfactory.

Thanks a lot!!!  :)
Title: Re: Sansa Fuze+
Post by: megal0maniac on July 18, 2013, 04:49:52 PM
Thanks devs for this great work!
Pamaury: I downloaded firmware.sb and tried to upgrade bootloader on my fuze+, but OF is "ignoring" the upgrade. I tried several times, booting to OF, resetting the device, but OF always boot in normal mode, just like if firmware.sb doens't exists in root folder.
Do you have any ideas?
I've also had this issue. I needed to copy the firmware.sb file onto the device while in the OF USB mode. Rockbox USB or bootloader USB would result in it being ignored.
Delete the file, then with the device off, hold volume down and plug in the USB cable then copy the file.
Title: Re: Sansa Fuze+
Post by: pamaury on July 19, 2013, 02:43:51 AM
Once again I have to clarify things for a few people who don't dare to read the last posts:
Title: Re: Sansa Fuze+
Post by: Roboturner913 on July 27, 2013, 05:18:34 AM
Anybody else still have the freezing/slowdown issue during playback? It appears to happen completely at random.

I may have stumbled into a solution, or at least a workaround. Turning off the EQ seems to eliminate it. I turned it off because it was more convenient than messing with the tone controls on my car stereo. Ran it nearly 6 hours without one incident, whereas before it would happen roughly once an hour for 2-3 minutes at a time.

Title: Re: Sansa Fuze+
Post by: ildarion on July 28, 2013, 03:07:21 AM
Yeah, I still have the freezing/slowdown during playback and yes it's seem to be random. Sometimes it appears several times in a row, sometimes it is about to mean a whole ~30mins.
Title: Re: Sansa Fuze+
Post by: pamaury on July 28, 2013, 04:31:06 AM
Please, please, please, please, bug reports go on flyspray.
If you suffer from random freeze/slowdown, report it here: http://www.rockbox.org/tracker/task/12886 (http://www.rockbox.org/tracker/task/12886). Please do a complete a description and whenever you report a bug, make sure to reset all your settings before doing so. Thank you.

Announcement: some patches to disable touchpad on lock are on rail, Jean-Louis has made some tests and low power modes of the touchpad seem to gave us an extra 10% battery life. Wait and see :)
Title: Re: Sansa Fuze+
Post by: gontofe on August 07, 2013, 02:46:11 AM
Quote
some patches to disable touchpad on lock are on rail, Jean-Louis has made some tests and low power modes of the touchpad seem to gave us an extra 10% battery life.

Is this on flyspray or similar? Would be good to have a look and maybe recompile and test this?
Title: Re: Sansa Fuze+
Post by: [Saint] on August 07, 2013, 05:24:28 AM
No need. Just grab a current build.


[Saint]

EDIT by pamaury: it is not in the trunk, there are some patches like http://gerrit.rockbox.org/r/#/c/525/ (http://gerrit.rockbox.org/r/#/c/525/) but Jean-Louis is still working on them. Be patient
Title: Re: Sansa Fuze+
Post by: pamaury on August 21, 2013, 01:21:21 PM
Hi all,
there have been very few user noticable changes recently but it will change soon. For now, some SD handling changes have been merged. This will effectively drive the microSD card at 50MHz instead of 25MHz. This should noticeably increase the read/write speed to sd cards in rockbox and via usb too. Note that will probably not read reach the full sd read/write speed with USB yet because of other latencies which I am trying to track down.
If you encounter any new problem with sd (like panic init failed or card not recognised), please make sure that older revision did work and if so report the problem.
Title: Re: Sansa Fuze+
Post by: taxor on August 22, 2013, 12:19:20 PM
After updating to firmware a122b52 my fuze+ is not playing flacs from SD Card anymore. MP3 from SD it is playing and flacs from internal memory too. If starting from SD card it always freezes instantly.

Older build from a week ago worked fine, especially all these random freezes the fuze+ sometime had were gone with that build. I hate me for done the update today  :-\
Title: Re: Sansa Fuze+
Post by: max242 on August 22, 2013, 03:44:02 PM
I did experience a couple of "delayed write failed" issues in the last couple of days while i was trying to put pictures in the mp3 using mp3tag.  Thinking maybe the uSD filesystem got corrupted i did run a checkdisk (in Windows 7), but apparently no FAT issues were found on the uSD-card.

So i hope the new code you want to release makes those things go away.  Anyhow, I'm willing to test.

And thanks for the great work of all you rockbox developers!

Marc
Title: Re: Sansa Fuze+
Post by: pamaury on August 22, 2013, 04:45:37 PM
I have reverted the high speed card switch become it appears to be unstable for some people. There are some new changes related to clock management, it shouldn't change anything on the Fuze+ but if you see new issues, let me know.
Title: Re: Sansa Fuze+
Post by: taxor on August 23, 2013, 07:36:10 AM
After updating to firmware a122b52 my fuze+ is not playing flacs from SD Card anymore. MP3 from SD it is playing and flacs from internal memory too. If starting from SD card it always freezes instantly.

Older build from a week ago worked fine, especially all these random freezes the fuze+ sometime had were gone with that build. I hate me for done the update today  :-\

With build fbc4ef7-130822 flacs from SD Card are working again. I use a Transcend microSDHC 32GB class 10 card, if that helps.
Title: Re: Sansa Fuze+
Post by: Njones on August 28, 2013, 07:36:04 PM
Tried updating to to today's build. won't boot into rockbox. Bad checksum message? 74761b7
Title: Re: Sansa Fuze+
Post by: pamaury on August 29, 2013, 02:41:55 AM
Try redownloading the build and installing again. Your file got corrupted.
Title: Re: Sansa Fuze+
Post by: Njones on August 29, 2013, 06:49:04 AM
I uninstalled RB and started with a fresh install and all is good. Thanks.
Title: Re: Sansa Fuze+
Post by: metaphys on September 05, 2013, 01:17:49 PM
Hi all,

1) after a while we finally got that touchpad disable on keylock.

BE AWARE THAT if you lock your device it will looks like idle until you unlock it back (no more lcd display unless you use volume or power key.
Next I will go on writing some code to have a setting for whether we want only the touchpad to get disable  on lock.

2) ALSO AN IMPORTANT KEYMAPS MODIFICATION that might be annoying to some people is that we had to map the back key to the "back to main menu" action. Normal cancel is still available on the left key as it always was... This was made for consistency reason as main menu is suppose to be a core action. Also the point was to save the two navigation big step in list keys (botton right and left)
Title: Re: Sansa Fuze+
Post by: Xanikseo on September 08, 2013, 06:42:46 AM
with the latest updates, the lag when playing music has disappeared!

scratch that. I must have just been lucky. I charged the thing up and now the problem is as it was before
Title: Re: Sansa Fuze+
Post by: metaphys on September 20, 2013, 05:53:08 AM
following the last keymap update with the implementation of the menu key (on the back arrow key) there has been a few screen made unusable (bookmark, recording, EQ). Those have been corrected. Please report any remaining issue.
Title: Re: Sansa Fuze+
Post by: pamaury on September 27, 2013, 06:52:38 AM
Hi all,
This is a new release candidate for the bootloader: it will become V2 if nobody reports any new issues. The changes are minimal: slightly faster boot and it should fix some hanging boot issues that happen from time to time. Please feel free to test it and report success/failures.

https://www.dropbox.com/s/w9cnnr4w5m3edpd/fuzep_rb_firmware_v2.sb (https://www.dropbox.com/s/w9cnnr4w5m3edpd/fuzep_rb_firmware_v2.sb)
Title: Re: Sansa Fuze+
Post by: Julian67 on September 27, 2013, 11:35:32 AM
Hi all,
This is a new release candidate for the bootloader....Please feel free to test it and report success/failures.

Success!

I had some problems at first as the Sansa firmware did not "see" the new firmware.sb file after I copied it to device root.  In the end I switched off the player, held down volume button and attached the USB cable so the device was in Sansa's USB mode, not Rockbox's.  Then I copied the firmware again.  The next time I booted into Sansa firmware in playback mode it did update the firmware with the V2 bootloader.

It does boot noticeably faster.
Title: Re: Sansa Fuze+
Post by: Xanikseo on September 28, 2013, 12:43:04 PM
Disabling crossfade seems to prevent the playback lagging on sd card, without needing to boost cpu

Also, flashed the new bootloader successfully. No problems so far!
Title: Re: Sansa Fuze+
Post by: fsclavo on September 30, 2013, 10:37:47 AM
Updated bootloader and Rockbox: all perfectly functional!
I had a issue sometimes when fuze+ responded very slow, but disappeared now!
Didn't noticed some boot time improvement.
Title: Re: Sansa Fuze+
Post by: ddscentral on September 30, 2013, 08:22:11 PM
Back key does not seem to work in some places for me (eg. System->Rockbox info). I can use the left key to return, but shouldn't the Back key always return to the main menu ?
Title: Re: Sansa Fuze+
Post by: metaphys on October 01, 2013, 01:00:31 PM
yes this is becaus this menu action immplementation is not very clean... I would see If I can improve that
Title: Re: Sansa Fuze+
Post by: Njones on October 02, 2013, 09:24:52 AM
Do I put the new bootloader file into the rockbox file on the Fuze + or just add to the list of files?
Title: Re: Sansa Fuze+
Post by: fsclavo on October 03, 2013, 02:58:18 PM
Do I put the new bootloader file into the rockbox file on the Fuze + or just add to the list of files?

You must boot OF on your fuze+, rename bootloader file to "firmware.sb", copy it to the root folder of your device and reboot it with OF again.

Title: Re: Sansa Fuze+
Post by: Njones on October 03, 2013, 06:23:27 PM
Thanks,
I was doing everything except renaming to firmware.sb. Now it shows up as v2
Title: Re: Sansa Fuze+
Post by: silvertree on October 06, 2013, 11:49:52 AM
I installed v2 last week and I have noticed the speedy boot up.  Very nice.  I really don't understand much more about the bootloader to comment that it works well but I have made 2 observations.

1.  More of a question and of the lowest priority since OF doesn't appeal to me but is it a desired function to have the OF drop to the bootloader upon USB connection?

2.  I've observed that after properly shutting down the OF the next boot, bootloader takes a considerable longer time to execute Rockbox.


Last question:  I'm new here but have been using Rockbox for 6 years on several irivers and a couple Sansas.  Would it be acceptable to post a rather long list of observations I've made over the last few months using Rockbox on my  Fuze+?

I love the project and entirely appreciate the work everyone has put into this port.  It's not that I love making more work by pointing out issues... I do it because I care.

Thanks, gang.
Title: Re: Sansa Fuze+
Post by: pamaury on October 11, 2013, 08:13:57 AM
Hi, as soon as I have a proper internet connection, i'll answer with more details (typing on phone is boring). Quickly: the OF reboots on usb connection, that cannot be changed. And yes i've noticed this but i have no clue, anyway i don't expect people to use the OF very often.
Title: Re: Sansa Fuze+
Post by: pamaury on October 22, 2013, 08:53:50 AM
Hi All,
if by chance you tried to update to the latest nightly build, you maybe have ran into a panic message. This should now be fixed, please upgrade again to fix this improper behaviour.
Title: Re: Sansa Fuze+
Post by: BenBrown on October 24, 2013, 08:03:40 AM
Oh, very nice work on the V2 bootloader.  I really like all the new status updates.  No troubles with it so far for me.
Title: Re: Sansa Fuze+
Post by: ildarion on October 27, 2013, 06:06:49 PM
Hey !

Alarm clock work for you and it's me or it's normal ?
Title: Re: Sansa Fuze+
Post by: bthomson on November 05, 2013, 01:05:02 PM
Hey guys, just bought a Fuze+ but having a little trouble getting Rockbox loaded. I can't use the rockbox utility so I am trying to follow the directions under "Alternative Method" at [1].

I downloaded [2] and extracted it to the device root (so there is now a .rockbox folder there). I downloaded [3] and added it to the root. Then I did safe eject in windows and removed the cord from the device. A screen popped up that said "Fuze+ Updating...", and then the device rebooted back into the original firmware.

I tried this again a couple times and then tried following the same procedure with [4] (making sure to rename it to firmware.sb), but the same thing happened. No rockbox, just the original firmware.

Did I miss anything? Maybe I should check the hash of the firmware.sb on the USB device before ejecting to make sure it hasn't gotten corrupted.

[1] http://www.rockbox.org/wiki/SansaFuzePlusPort
[2] http://build.rockbox.org/data/rockbox-sansafuzeplus.zip
[3] https://www.dropbox.com/s/86f4v7hmjw2hjmi/firmware.sb
[4] https://www.dropbox.com/s/w9cnnr4w5m3edpd/fuzep_rb_firmware_v2.sb
Title: Re: Sansa Fuze+
Post by: pamaury on November 05, 2013, 01:43:32 PM
Hi,
I can think of two possibilities: the firmware you downloaded is corrupted and you should download it again, or you have a device with a new version of the firmware and since it prevents downgrading, it refuses to upgrade. You can check the second theory easily: go into the device parameters and find the OF version. The latest known one is current 2.36.08
Title: Re: Sansa Fuze+
Post by: bthomson on November 07, 2013, 04:14:57 AM
Thanks very much pamaury. After a redownload today, I had success!

I would also like to express my gratitude for your work on this rockbox port. So far the Fuze+ is much nicer to use with rockbox than my tiny Clip Zip. I really enjoy being able to read filenames and menus without having to scroll, and the touchscreen seems less susceptible to accidental button presses when I put the device in my pocket. Overall it is a big improvement for me.
Title: Re: Sansa Fuze+
Post by: blackshard on November 07, 2013, 03:57:41 PM
Hello guys, just a side question... I'm using from long time Rockbox on my fuze+ and I greatly appreciate the work done! I'd would ask if it is a known glitch/issue or it is just my unit that sometimes, during audio playback, some buffers get lost and you hear a sudden jump in the stream.
Title: Re: Sansa Fuze+
Post by: pamaury on November 12, 2013, 11:39:43 AM
@blackshard: don't suffer from this issue at all, which format are you playing and what is the bitrate ? Can you upload a file on which it happen ?

Hi all,
I have tagged the V2 bootloader version and uploaded it so that Rockbox Utility can install it. I will thus removed the firmware my dropbox for obvious legal reasons. Please use the Rockbox Utility to update the bootloader as of now.
Title: Re: Sansa Fuze+
Post by: azhag on November 15, 2013, 07:34:17 AM
Hi,

I tried to update the bootloader using the RU 1.3.1:

- checked the "Bootloader" to be installed,
- downloaded needed OF,
- RU did all the magic with patching and stuff,
- I rebooted to OF.

And I still have v1 of the bootloader.

Do I need to perform some additional steps to update it? Or do I have to wait some time until RU knows about v2?
Title: Re: Sansa Fuze+
Post by: pamaury on November 15, 2013, 07:54:44 AM
Did the OF display the "upgrading" message ? Sometimes the OF doesn't trigger the update from mysterious reasons and you have to manually remove the firmware.sb file at the root of the device and start over again.
Title: Re: Sansa Fuze+
Post by: azhag on November 15, 2013, 08:36:16 AM
Did the OF display the "upgrading" message ?
No.

OK, I'll try again.
Edit: still no luck.
Edit 2: scratch that. After like third boot to OF (with the same firmware.sb!) it started to update itself. No idea why it didn't work at first.
Title: Re: Sansa Fuze+
Post by: Julian67 on November 15, 2013, 09:58:51 AM
The Rockbox Utility bootloader update worked first time for me.  After unexpected bootloader install failure with previous version I found it works reliably if you connect the Fuze to PC in OF USB mode: with player powered off,  hold down the hardware volume down button and connect USB cable.  Fuze+ then connects in Sansa's USB mode and it recognises any new firmware.sb file and upgrades as expected on safe remove/umount and disconnection.
Title: Re: Sansa Fuze+
Post by: pamaury on December 01, 2013, 05:36:53 PM
For those interested, we are discussing the inclusion of a deadzone parameter for the touchpad. See http://forums.rockbox.org/index.php/topic,43672.0.html (http://forums.rockbox.org/index.php/topic,43672.0.html) for more information.
Title: Re: Sansa Fuze+
Post by: pamaury on December 02, 2013, 05:16:37 AM
For your information, commit http://git.rockbox.org/?p=rockbox.git;a=commit;h=2ce484c (http://git.rockbox.org/?p=rockbox.git;a=commit;h=2ce484c) solves a power regression which happened in July and resulted in a 10h loss of battery life. The Fuze+ should now again last 40h+ in playback with recent batteries.
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on December 02, 2013, 02:25:58 PM
Dropbox link for new bootloader is dead it appears any alternatives?   Also the player freezes up with sd card installed right now but sd card works fine in my og fuze.    Is this a firmware or hardware problem?
Title: Re: Sansa Fuze+
Post by: pamaury on December 02, 2013, 02:28:15 PM
You should now use Rockbox Utility, this is the preferred way to install the bootloader.
If it freezes it's a software problem but I need more information: retry with the newest version of rockbox and bootloader first. If you still face this issue, post again with detailled version information and possibly a simple procedure to reproduce the bug. Also try to reset all your settings to see if it changes anything.
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on December 02, 2013, 07:53:05 PM
You should now use Rockbox Utility, this is the preferred way to install the bootloader.
If it freezes it's a software problem but I need more information: retry with the newest version of rockbox and bootloader first. If you still face this issue, post again with detailled version information and possibly a simple procedure to reproduce the bug. Also try to reset all your settings to see if it changes anything.
That is how I originally installed the bootloader a few weeks back when I bought the player.  I was just thinking of upgrading to the latest one to make sure I had the latest version to see if problem went away.   The problem exists with one sd card but not my main one.   My main one i used so much that the sticker on the back peeled off maybe that could cause the problem?   I am using the latest build posted on the site.  Also I just cleaned off a little bit of sticker gunk on back of card and now I get a data abort immediately after boot now.   
Title: Re: Sansa Fuze+
Post by: pamaury on December 02, 2013, 07:54:42 PM
Is your card properly formatted ? It is possible that a faulty file system crashes Rockbox.
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on December 02, 2013, 08:13:08 PM
Is your card properly formatted ? It is possible that a faulty file system crashes Rockbox.
Yep it's fat 32.   I have it in my fuze v2 with rockbox right now works fine.  Also works fine in my clip zip with rockbox.  edit I should note that i had rockbox setup to start at the bookmark screen.   I just switch out the card between players so i wonder if it has anything to do with bmkarks created on other devices?    Anyway I'm doing a fresh install now and will let you know.   Resetting everything to stock first.  Yep 100% fresh install and data abort isn't immediate now but as soon as i select a track .  Number is 000000320 if that helps anything sp:60BBA68 if that means anything to you
Title: Re: Sansa Fuze+
Post by: pamaury on December 09, 2013, 11:48:14 AM
@sportscrazed2: Can you clarify and explain what is the minimum setup required to trigger the bug: if you use another card, does it crash ? if you reformat the card does it crash ? If you play a file from internal storage (with and without card inserted) ?

To all, it seems there are two different versions of the touchpad and I need your help to check this. If you are using the latest build (from today), can you report those two information together:

NOTE: to escape the touchpad debug menu, press power. You will probably suffer from a crash, this is a known problem so don't report it (that's why it's in the debug menu !)
Title: Re: Sansa Fuze+
Post by: bthomson on December 17, 2013, 06:55:14 PM
Hey sportscrazed2, did reinstalling or reformatting fix that issue for you? I ask because mine's been randomly freezing up a lot too. It seems to be a problem with file access because the disk icon always appears when it locks up. It's random and not reproducible with any particular set of actions.

I've also gotten messages about failures writing the bookmarks, and occasionally the "recent bookmarks" menu gets emptied out (but they're still accessible in the filesystem). chkdisk said my sd card filesystem is OK but I guess I should try reformatting it next.
Title: Re: Sansa Fuze+
Post by: sportscrazed2 on December 19, 2013, 01:43:24 PM
Sorry just got back to playing with it again.   I updated everything to most recent version today and it still crashes when selecting a file on micro sd card but only sometimes.  I have no idea what can be causing it.
Title: Re: Sansa Fuze+
Post by: bthomson on December 20, 2013, 02:04:14 PM
Thanks, sportscrazed. I'll give a try reformatting the SD card using Windows this time, and then recopy the data. I think I used FreeBSD to format it originally, which could potentially be causing an issue.

But its possible this is a problem with the Fuze+ port, because I used the same SD card on a Rockbox Clip Zip for a long time without any issues.
Title: Re: Sansa Fuze+
Post by: halonachos117 on December 21, 2013, 01:25:50 AM
Generally, the best ways to format anything to be used on a Sansa devices are to format with the OF from the computer in MTP mode, or from the Settings menu.

Of course, running a filesystem checker might help.
Title: Re: Sansa Fuze+
Post by: pamaury on December 21, 2013, 05:21:32 AM
@bthomsonl:
can you try with this build https://www.dropbox.com/s/ewwvyezg1730e7h/rockbox_fuzep.zip (https://www.dropbox.com/s/ewwvyezg1730e7h/rockbox_fuzep.zip) and report here exactly what is written on the crash screen please ?
Title: Re: Sansa Fuze+
Post by: silvertree on December 21, 2013, 09:37:22 AM
With the Fuze+ RB bootloader v2 (and likely earlier)
When one connects a USB to Windows while in the OF, the machine reduces back down to the RB bootloader.  Therefore there is no formatting benefit from formatting with Windows within OF. 

However, if OF has an option to format the card, perhaps try that although since the OF has a filesize limit of around 30 gigs this method becomes useless with larger cards.
Title: Re: Sansa Fuze+
Post by: sdf5 on December 24, 2013, 01:23:25 PM
What I would like to see in the Fuze+ port is the ability to operate the player (that is, to go to the next/previous item, increase/decrease volume, start/stop playback) without the use of touchpad, only using the player's buttons. This would allow to put the player in the playback mode, lock the screen and then only use the player's buttons to operate it -- a useful functionality to have if you carry the player in your pocket.

Since the player has only three (3) buttons (Volume Up, Volume Down and On/Off) some creativity would be needed to implement the above. Perhaps it could be done the following way:

   Volume Down pressed for less than 1 sec = go to the previous playback item
   Volume Down pressed for more than 1 sec = decrease volume
   Volume Up pressed less than 1 sec = go to the next playback item
   Volume Up pressed more than 1 sec = increase volume
   On/Off pressed for less than 1 sec while in playback mode = start/stop the playback
   On/Off pressed for more than 1 sec while in playback mode = unlock the screen
   On/Off pressed for less than 1 sec while NOT in playback mode = lock the screen

Something like that. Thanks
Title: Re: Sansa Fuze+
Post by: bthomson on December 25, 2013, 12:02:00 AM
@bthomsonl:
can you try with this build https://www.dropbox.com/s/ewwvyezg1730e7h/rockbox_fuzep.zip (https://www.dropbox.com/s/ewwvyezg1730e7h/rockbox_fuzep.zip) and report here exactly what is written on the crash screen please ?

Thanks for your help! I really appreciate it. I tried that build today but I think I borked the install because the bootloader now says "Bad Checksum". This weekend I will try to download again and give it another shot.

However, if OF has an option to format the card, perhaps try that although since the OF has a filesize limit of around 30 gigs this method becomes useless with larger cards.

Hey, that's a great idea! I'll check for this option and use that to reformat (if it's available). The card is 32GB so it wouldn't be a major loss.
Title: Re: Sansa Fuze+
Post by: FCB38 on December 25, 2013, 10:13:41 AM
Hello,

I bought a Fuze+ for my daughter. I put rockbox on it using Windows 7.
When I try to connect the player on a computer with Windows XP I can't see the internal memory. How can I do to put new files (music or videos) on it?

Thank you for your help!!!!
Title: Re: Sansa Fuze+
Post by: fsclavo on December 26, 2013, 10:16:58 AM
I just updated my fuze+ to 8566cd7 and the player is unusable now. There is a loud hiss sound constantly, and music is almost unhearable.
Title: Re: Sansa Fuze+
Post by: oceanguru on December 26, 2013, 04:10:20 PM
I recently bought a Fuze+, and I am using Rockbox version 8566cd7. When playing back Opus files I have blocks of audio dropped accompanied by lag in touchpad response. I have tested using MP3 files, and they have not resulted in this problem on microSD cards or internal storage. I have also tried the same version on my Clip Zip without issue. The only things I have altered from the defaults are the theme and font used.
Title: Re: Sansa Fuze+
Post by: silvertree on December 26, 2013, 04:42:43 PM
I recently bought a Fuze+, and I am using Rockbox version 8566cd7. When playing back Opus files I have blocks of audio dropped accompanied by lag in touchpad response. I have tested using MP3 files, and they have not resulted in this problem on microSD cards or internal storage. I have also tried the same version on my Clip Zip without issue. The only things I have altered from the defaults are the theme and font used.



The lag is a commonly reported problem.  As far as I know there is no immediate solution.

I have observed that not changing fonts and theme helps reduce the occurrence of the fits.

Reset Rockbox back to defaults and only change necessary settings.
Title: Re: Sansa Fuze+
Post by: silvertree on December 26, 2013, 04:44:24 PM
Hello,

I bought a Fuze+ for my daughter. I put rockbox on it using Windows 7.
When I try to connect the player on a computer with Windows XP I can't see the internal memory. How can I do to put new files (music or videos) on it?

Thank you for your help!!!!

Check the manual.  If the player is recognized in the pc but the internal memory is not visible it is likely that the option to hide the internal memory has been enabled.
Title: Re: Sansa Fuze+
Post by: FCB38 on December 27, 2013, 02:39:08 AM
Check the manual.  If the player is recognized in the pc but the internal memory is not visible it is likely that the option to hide the internal memory has been enabled.

Hello,
Thank you Sylvertree.
I tried this option but it's not OK. Some times I can see the 8 gb of the player but it's impossible to create a new folder or copy a new file. At this moment the Windows explorer is very slow until I remove the player.
I think there's a driver problem but I don't know withc driver I have to give to Windows to make Fuze+ works on XP.

Regards.

-----------------------------------------------------------------------------------------------------------------
Last minute:

I finally change USB port. It's OK now. I used the USB port of the mother board; now I use a USB port of a additional card.

Regards
Title: Re: Sansa Fuze+
Post by: halonachos117 on December 28, 2013, 03:16:29 PM
With the Fuze+ RB bootloader v2 (and likely earlier)
When one connects a USB to Windows while in the OF, the machine reduces back down to the RB bootloader.  Therefore there is no formatting benefit from formatting with Windows within OF.

FYI, you can boot into MTP with the OF, it just requires knowing how. On that note, I've decided to post instructions on how to do this on the Wiki, in hope that they will be useful to others. See HERE (http://www.rockbox.org/wiki/Main/SansaFuzePlusPort#Booting_the_OF_in_MTP_USB_mode.).
Title: Re: Sansa Fuze+
Post by: silvertree on December 28, 2013, 05:02:16 PM
FYI, you can boot into MTP with the OF, it just requires knowing how. On that note, I've decided to post instructions on how to do this on the Wiki, in hope that they will be useful to others. See HERE (http://www.rockbox.org/wiki/Main/SansaFuzePlusPort#Booting_the_OF_in_MTP_USB_mode.).

Thank you, I was unaware.
Title: Re: Sansa Fuze+
Post by: metaphys on December 29, 2013, 08:29:38 AM
Pamaury,

I can't reach you on the IRC but I just meet a very serious issue:
As you know I've been running rockbox on a modified fuze+ that boot directly from the sdcard, as its intern memory is dead. Recently something very fuck up happens: The sdcard I've been using is now dead the very same way the intern memory was:
- read only
- formating and so on doesn't work even with low level tools

That's a 64 gb sdcard gone  :'(

So I'll modify the wiki to mention that the dead memory turnaround is a dead end...
Title: Re: Sansa Fuze+
Post by: pamaury on December 29, 2013, 10:58:18 AM
Is that a sandisk card ? I know some people have suffered fron firmware bugs and Sandisk exchanged the card. The internal storage of the Fuze+ is also from Sandisk so maybe it's all related to a bug in their firmware. At least ir's worth a try.
Title: Re: Sansa Fuze+
Post by: metaphys on December 29, 2013, 08:18:40 PM
no it was a transcend
Title: Re: Sansa Fuze+
Post by: toehser on December 29, 2013, 09:13:07 PM
What low level utilities did you try that couldn't write to it?  Are you sure that the operating system hadn't decided to put it into read-only mode, leaving the utilities stuck?
Title: Re: Sansa Fuze+
Post by: metaphys on January 01, 2014, 05:43:11 PM
yes because I used both windows and linux to try to format it. And writing doesn't work also from rockbox or my android phone

If been using dd to zeroing the partition, no effect
Title: Re: Sansa Fuze+
Post by: pamaury on January 02, 2014, 06:16:05 AM
I still don't understand how this is possible, especially with both SD and eMMC. And if you suffered from it, potentially anyone could, your custom build does nothing special about SD and MMC. And I don't see how Rockbox could possibly brick a SD card which is an issue. Metaphys, could you send me (again) the SD card so I can have a look at it ?
Title: Re: Sansa Fuze+
Post by: sdf5 on January 05, 2014, 02:16:36 AM
What I would like to see in the Fuze+ port is the ability to operate the player (that is, to go to the next/previous item, increase/decrease volume, start/stop playback) without the use of touchpad, only using the player's buttons. This would allow to put the player in the playback mode, lock the screen and then only use the player's buttons to operate it -- a useful functionality to have if you carry the player in your pocket.

Since the player has only three (3) buttons (Volume Up, Volume Down and On/Off) some creativity would be needed to implement the above. Perhaps it could be done the following way:

   Volume Down pressed for less than 1 sec = go to the previous playback item
   Volume Down pressed for more than 1 sec = decrease volume
   Volume Up pressed less than 1 sec = go to the next playback item
   Volume Up pressed more than 1 sec = increase volume
   On/Off pressed for less than 1 sec while in playback mode = start/stop the playback
   On/Off pressed for more than 1 sec while in playback mode = unlock the screen
   On/Off pressed for less than 1 sec while NOT in playback mode = lock the screen

Nobody thinks it's a good idea? The touchpad works pretty poor for me, it'd be nice to be able to avoid using it in the playback mode.
Title: Re: Sansa Fuze+
Post by: pamaury on January 05, 2014, 06:10:10 AM
I'm sorry but I don't see the point of it. If you don't like the touchpad, why did you bought the Fuze+ in the first place ? With custom keymaps, I think it is possible to achieve something close to what you want but it will never make it to our codebase I'm afraid, at best you would need to write it yourself (maybe with some help) and compile your own version of Rockbox.
Title: Re: Sansa Fuze+
Post by: sdf5 on January 05, 2014, 09:42:38 AM
If you don't like the touchpad, why did you bought the Fuze+ in the first place ?

I didn't know that  the touchpad would be that inconvenient to use before I bought the player. Besides, this feature would allow to operate the player without having to look at it, a nice feature to have if you carry the player in your pocket and don't want to take it out every time you want to start/stop/skip ahead/go back. I thought it'd be  simple to implement something like that and It could be an optional feature too, that is, the user would change a config setting to enable it.
Title: Re: Sansa Fuze+
Post by: saratoga on January 05, 2014, 12:47:39 PM
You're welcome to implement it yourself, but those kind of options are generally not welcome in the official code.
Title: Re: Sansa Fuze+
Post by: bthomson on January 09, 2014, 12:57:42 AM
@bthomsonl:
can you try with this build https://www.dropbox.com/s/ewwvyezg1730e7h/rockbox_fuzep.zip (https://www.dropbox.com/s/ewwvyezg1730e7h/rockbox_fuzep.zip) and report here exactly what is written on the crash screen please ?

Thanks for your help! I really appreciate it. I tried that build today but I think I borked the install because the bootloader now says "Bad Checksum". This weekend I will try to download again and give it another shot.

Hello, I am sorry I have not replied for a couple weeks. About a week ago I got this build working and today the player has locked up again. Here is what happened:

1) Audio playback stopped. Player was still on the "while playing screen", but the counter was no longer advancing.

2) Buttons were still working at this stage. I was able to hit back to go from the "while playing screen" to the menu and then back to the "while playing screen" again.

3) Now buttons have stopped working, sorta. All the buttons including volume up, down, power, and the touchpad will light up the backlight, but the player doesn't respond otherwise. It's stuck on the while playing screen. The backlight turns off after the configured delay period (10s).

4) Player has been in this state for more than the 5 minute idle shutdown so that is not activating. I force shut down the player by holding power button.

When I installed the build pamaury provided last week my settings were reset to default (I think that's because settings are stored in the .rockbox directory. I moved my old rockbox directory to .rockbox-old before unzipping). I decided to stick with the default settings for a while and did not experience any lockups while in default settings. However, yesterday I started changing the settings back to my preferences and today it has locked up. This could be a coincidence or it could be one of the settings I chose is the problem. So unless anyone has anything they would like me to try, my next step will be to reinstall pamaury's build and use the player with the default settings for a few weeks to see if I can reproduce the lock up that way.

I used this same SD card in a Rockbox Clip Zip for a while before installing pamaury's build on the Fuze+ and didn't experience any problems during that time. Well, except that Clip Zip sucks compared to Fuze+  ;D
Title: Re: Sansa Fuze+
Post by: halonachos117 on January 09, 2014, 07:39:38 PM
Perhaps you should create a bug report in Flyspray, as this forum isn't really meant to be used to discuss bugs. I would recommend uploading your config.cfg file, which is usually located in .rockbox (or in your case, .rockbox-old). From there, perhaps the individual settings could be tested one-by-one. I would also try posting a hyperlink right here to said bug report, so as to allow the rest of us to know this report exists.
Title: Re: Sansa Fuze+
Post by: gevaerts on January 10, 2014, 04:23:44 AM
Perhaps you should create a bug report in Flyspray, as this forum isn't really meant to be used to discuss bugs.

While a bug report would certainly be useful, this is a development thread, and as such I'd say bug reports can be relevant here
Title: Re: Sansa Fuze+
Post by: ildarion on January 12, 2014, 05:20:36 AM
Hey, it's been a while since I just annoy you with a function that does not work (just for me?) and probably rarely used by users: alarm clock.

Am I the only one? Do you will fix this? (if it's not too much work)

Title: Re: Sansa Fuze+
Post by: pamaury on January 12, 2014, 06:14:00 AM
@bthomson: I'm sorry but without more details, I simply cannot find the bug. If you think it might be related to a setting, you should reset them all and change them one by one until you trigger the bug. Otherwise I'm blind, I cannot know what is crashing.

@ildarion: I was not aware that there was a problem with the alarm clock, I will have a look.
Title: Re: Sansa Fuze+
Post by: halonachos117 on January 13, 2014, 11:08:17 PM
Ildarion, what exactly is happening (or not happening) with the alarm? Have you updated you bootloader to the newest version?
Title: Re: Sansa Fuze+
Post by: ildarion on January 14, 2014, 11:50:10 AM
My bootloader have ~2 months old (I can"t upgrade for now)

So basicly, the alarm don't trigger. I choos the time, press the right touch for confirm, rockbox say alarm will be trigger in XXmins but never do.
Title: Re: Sansa Fuze+
Post by: pamaury on January 14, 2014, 12:00:14 PM
@ildarion: can you be more specific ? If you read the documenation http://download.rockbox.org/daily/manual/rockbox-sansafuzeplus/rockbox-buildch11.html#x14-17100011 (http://download.rockbox.org/daily/manual/rockbox-sansafuzeplus/rockbox-buildch11.html#x14-17100011), you will see that powering down and up the player after having specified an alarm will cancel it. I am also unsure of the behaviour of the alarm in case you specify it and don't power off. Anyway, alarm works on mine if I just setup the alarm and power off. I'm running bootloader V2 and latest version of Rockbox.
Title: Re: Sansa Fuze+
Post by: ildarion on January 14, 2014, 12:47:45 PM
Quote
I just setup the alarm and power off.

I do the same (no power ON, just setup and power OFF) and don't work. I try regularly this since 1 year. But actually I don't have the last update (few months old) so if they work for you, it's just me.
Title: Re: Sansa Fuze+
Post by: metaphys on January 15, 2014, 05:12:28 AM
I still don't understand how this is possible, especially with both SD and eMMC. And if you suffered from it, potentially anyone could, your custom build does nothing special about SD and MMC. And I don't see how Rockbox could possibly brick a SD card which is an issue. Metaphys, could you send me (again) the SD card so I can have a look at it ?
Given the rate at which it's happening a lot of people should be suffering of it, if it was a common problem. The Sd card burned in only a few months! (just as the intern if I remember correctly). I'm starting to think it may be related to some storage controller on the device (is there any common micro-controller for eMMC and SD on the F+?)
Before I send it to you (it might take a while, i'm living in Romania now...) Are there some stuff you would like me to test first?
Title: Re: Sansa Fuze+
Post by: pamaury on January 15, 2014, 05:17:05 AM
No, the eMMC/SD controller is the SoC itself and it has dedicated hardware, plus all transfers are CRC protected so it's unlikely that the host be able to send strange commands that would somehow brick the card. Did you try to contact the company that produced the card ? They might be interested or even know about issues. Appart from this, no I don't have any other suggestion because if it doesn't work when plugged to your computer, something must be seriously wrong with it.
Title: Re: Sansa Fuze+
Post by: sdf5 on January 15, 2014, 05:27:23 PM
yes because I used both windows and linux to try to format it. And writing doesn't work also from rockbox or my android phone

If been using dd to zeroing the partition, no effect

When you are on Linux, what does "fdisk -l /dev/xxx" say, where xxx is the device associated with your SD card? If the card is still recognized, that is, fdisk shows you valid info about the card, you may want to try zeroing the whole card  with dd, instead of a single partition, overwriting the partition table and then repartitioning it again manually with fdisk.

Other than that, the suggestion to contact the card manufacturer is a good one I think, they may know something or may suggest other things to try.

HTH
Title: Re: Sansa Fuze+
Post by: ildarion on January 17, 2014, 06:37:14 AM
After a fresh install of rockbox (utility 1.4.0), I was trying the alarm clock again and still doesn't trigger.

Up and Down to adjust the minutes setting, Down and Up to adjust the hours. Select confirms the alarm, It say it will be start in XXtimes. I wait fews secs and i turn OFF sansa with the power button.

I try to set the alarm on radio FM or back play, same.

In the rockbox utility, it say I have the bootloader 2013-11-12T15:00:31
Title: Re: Sansa Fuze+
Post by: rna023 on January 17, 2014, 12:41:02 PM
rbinstall$ ./mkamsboot firmware.sb bootloader-fuzeplus.sansa patched.sb
mkamsboot Version 1.6
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[ERR]  Model name "fuz+" unknown. Is this really a rockbox bootloader?
[ERR]  Could not load bootloader-fuzeplus.sansa
Title: Re: Sansa Fuze+
Post by: pamaury on January 17, 2014, 12:43:18 PM
@rna023: a little hello wouldn't kill you, the lack of it might however, please be careful. The Fuze+ uses mkimxboot but you should probably use RbUtil directly.
Title: Re: Sansa Fuze+
Post by: bthomson on January 18, 2014, 09:26:17 AM
today the player has locked up again... I decided to stick with the default settings for a while and did not experience any lockups while in default settings. However, yesterday I started changing the settings back to my preferences and today it has locked up. This could be a coincidence or it could be one of the settings I chose is the problem.

@bthomson: I'm sorry but without more details, I simply cannot find the bug. If you think it might be related to a setting, you should reset them all and change them one by one until you trigger the bug. Otherwise I'm blind, I cannot know what is crashing.

Thank you pamaury, I am sorry I do not have more useful information to provide. I will keep trying to isolate this issue.

I have experienced another lockup today. Same behavior as I described last time. I believe the only settings that were changed from default were:

Settings->General->Bookmarking->Bookmark On Stop->Yes
Settings->General->Bookmarking->Load Last Bookmark->Ask
Settings->General->Bookmarking->Maintain a List of Recent Bookmarks->Unique Only

I have used this same SD card in a Clip Zip for a lot of playback time this week and it has never locked up. So I am pretty convinced now that this a problem specific to either the Fuze+ rockbox port or perhaps even my specific Fuze+ unit (hardware problem is always a possibility).

I have been reading back through this thread for 2013 and did find this bug in flyspray (http://www.rockbox.org/tracker/task/12886) which is related to freezing. So I have copied all of this information into a comment in that issue.

Do you guys think this might be related to the SD card code? I am thinking about copying some audio files to the player's internal memory, removing the sd card, and just sitting it somewhere in play mode for 24 hours to see if it freezes up that way. That is not a perfect test but might give us some clue. Someone also reported in the flyspray that switching from a 32GB down to a 4GB SD card solved the problem for him, but we haven't heard back from him since last year.
Title: Re: Sansa Fuze+
Post by: xpmule on January 24, 2014, 05:09:15 AM
over time these builds have been getting worse and worse for me.. plenty of buggy sketchy behavior
but worst of all is lock ups started happening and have been happening more frequently the newer the update.
right now i can turn it on and navigate to certain database album lists or specific settings options and it locks.. every time :(
very repeatable yet seemingly at random places / albums etc.
When i highlight one menu option it freezes on me an di have to hold the power button down to shut it off and reboot
BUT
i checked changing from my custom theme i made and uploaded way back that has always worked fine
to the newest cabby v2 theme that comes with the firmware update and to my surprise i was not getting the freezing.
I started flipping back and forth and every time my theme froze the player and the official one did not.
and i just said it had always worked fine but i had noticed changes in the theme code implemented in the build logs i think couple weeks ago roughly.
My theme had nothing special or fancy going on with it either and i also noticed unusual lag a lot and way more sketchy navigation behavior using my theme too.

As it stands now Rockbox is simply unusable. I go out for a ride around town with it playing but have it turned off in my pocket by the time i go home.
Because it just keeps freezing (all over the place) and navigation is getting seriously hellish.

Over time i honestly think this Rockbox beta for the Fuze + has gotten incrementaly worse and worse.
Thank god i save my old builds lol

I'm preparing now to just use my Samsung Galaxy S3 as my main music player now (just need to find a good media player)
I appreciate the effort all the contributors have done and i wish the devs luck and i hope my feedback here was helpful (to others struggling)
But i think i'm done.. having only a beta version to use with no official build and random devs free to randomly break things like existing themes etc
is a crappy situation to be in. It's been a looooooong time since this was in beta stages and it's only gotten worse with getting out of beta no where in sight.
think of the users please.

PS: USB charging with Rockbox still don't work for me either (remember bitching at me about that ? lol)
I have to boot to the orig firmware just to charge it and lately that has has been failing too :(
This port has gone to hell !
Title: Re: Sansa Fuze+
Post by: thegreatyashu on January 24, 2014, 09:43:43 AM
How do you change the bottom left and right "hold" hotkeys in the WPS? By default on the fuze+, if you hold the bottom left in the WPS, you get the speed/pitch menu. This is REALLY REALLY annoying because of the touch pad. This menu comes up ALL THE TIME. I am always accidentally changing the pitch or the speed. There is no option to change this menu or turn it off. It seems hard coded. It is not controlled by the hotkey selection in the settings, nor is the bottom right "hold" menu either (it brings up the file/song tag info).

How do you change button mapping?

Otherwise, it's working really well. This is the only issue I have had. The most recent build that includes a volume limit is astounding. I'm glad this feature made it in.
Title: Re: Sansa Fuze+
Post by: bthomson on January 24, 2014, 03:37:57 PM
over time these builds have been getting worse and worse for me.. plenty of buggy sketchy behavior
but worst of all is lock ups started happening and have been happening more frequently the newer the update.

xpmule, can you provide any more info? Specifically, which builds you have that lock up and which builds do not? I am also experiencing problems with lock-ups and would be very interested in trying the older code if it's more stable.

I am sure many of the other Fuze+ users would also appreciate your help in tracking down these more stable revisions.
Title: Re: Sansa Fuze+
Post by: pamaury on January 24, 2014, 03:47:33 PM
but worst of all is lock ups started happening and have been happening more frequently the newer the update.
right now i can turn it on and navigate to certain database album lists or specific settings options and it locks.. every time :(
very repeatable yet seemingly at random places / albums etc.
When i highlight one menu option it freezes on me an di have to hold the power button down to shut it off and reboot
Can you provide more information on this ? Are you using default parameters ? default theme ? Do you have a repeatable procedure to trigger the problem ?

i checked changing from my custom theme i made and uploaded way back that has always worked fine
to the newest cabby v2 theme that comes with the firmware update and to my surprise i was not getting the freezing.
I started flipping back and forth and every time my theme froze the player and the official one did not.
and i just said it had always worked fine but i had noticed changes in the theme code implemented in the build logs i think couple weeks ago roughly.
My theme had nothing special or fancy going on with it either and i also noticed unusual lag a lot and way more sketchy navigation behavior using my theme too.
The theme engine has had many regressions recently which are not specific to the Fuze+ and can trigger strange behaviours. If the bugs only happen with your theme, it would be nice to open a bug report and attach it so that we have more example to try to track down bugs.

But i think i'm done.. having only a beta version to use with no official build and random devs free to randomly break things like existing themes etc
is a crappy situation to be in. It's been a looooooong time since this was in beta stages and it's only gotten worse with getting out of beta no where in sight.
think of the users please.
Think of developers please, I'm doing this on my free time, just like other devs. Also if you don't report bugs, I cannot know about them.

PS: USB charging with Rockbox still don't work for me either (remember bitching at me about that ? lol)
Are you using the latest bootloader ? Because charging is working in Rockbox and in latest Rockbox bootloader and I don't know of anyone for which it fails so I suggest you upgrade the bootloader using Rockbox Utility.
Title: Re: Sansa Fuze+
Post by: sdf5 on January 25, 2014, 12:30:30 PM
How do you change the bottom left and right "hold" hotkeys in the WPS? By default on the fuze+, if you hold the bottom left in the WPS, you get the speed/pitch menu. This is REALLY REALLY annoying because of the touch pad. This menu comes up ALL THE TIME. I am always accidentally changing the pitch or the speed. There is no option to change this menu or turn it off. It seems hard coded. It is not controlled by the hotkey selection in the settings, nor is the bottom right "hold" menu either (it brings up the file/song tag info).

I'm having a similar issue, would be nice if it was possible to fix it.
Title: Re: Sansa Fuze+
Post by: pamaury on January 25, 2014, 12:56:24 PM
How do you change the bottom left and right "hold" hotkeys in the WPS? By default on the fuze+, if you hold the bottom left in the WPS, you get the speed/pitch menu. This is REALLY REALLY annoying because of the touch pad. This menu comes up ALL THE TIME. I am always accidentally changing the pitch or the speed. There is no option to change this menu or turn it off. It seems hard coded. It is not controlled by the hotkey selection in the settings, nor is the bottom right "hold" menu either (it brings up the file/song tag info).

I'm having a similar issue, would be nice if it was possible to fix it.

It is hardcoded, however I'm curious about how you manage to trigger it all the time, how it different from other buttons that you don't trigger by accident ?
Anyway, if people are generally in favour of dropping this behaviour and map bottom left or right to hotkey we can surely change this.
Title: Re: Sansa Fuze+
Post by: sdf5 on January 25, 2014, 01:13:13 PM
I'm curious about how you manage to trigger it all the time, how it different from other buttons that you don't trigger by accident ? Anyway, if people are generally in favour of dropping this behaviour and map bottom left or right to hotkey we can surely change this.

I don't do anything special to trigger them, whenever I do Next or Previous I often get those two screens instead. To me they are of little use. Perhaps some config option could be added to disable them.
Title: Re: Sansa Fuze+
Post by: ildarion on January 26, 2014, 01:51:58 PM
I Was able to update my bootloader to V2 (OF trigger,...) but now, the device is unknow in windows 7 (sometimes work under XP)

I get Black sansa screen if the player is OFF
If Rockbox ON and plug, the player seem to freeze / sometime this error : http://titanpad.com/3D0XHuPWhn
On OF + plug => Black screen
Device OFF + Volum down + plug = Nothing/black screen

Everytime i need to reset with holding power.

Now I was trying to format the device with the OF and..... I don't think it was a good idea  :D

I was using a recent build (few days old), and off course I was reset all settings (rockbox and OF) I had also try yo restore settings with my back up. Same issue and after start on OF, my rockbox setting was reset. And I can observe the settings many time reset. Maybe after starting on OF ?

So now on OF in MSC usb mode, the device is still unknow on windows
Title: Re: Sansa Fuze+
Post by: halonachos117 on January 26, 2014, 09:57:57 PM
Does the device even show up in the device manaer? Hw about the disk manager (winlogokey + r, type diskgmt.msc and press enter)?


Now I was trying to format the device with the OF and..... I don't think it was a good idea  :D

So, does that mean you decided not to? Or, does that mean doing so somehow made things worse?
Title: Re: Sansa Fuze+
Post by: thegreatyashu on January 27, 2014, 05:16:44 PM
Quote
Anyway, if people are generally in favour of dropping this behaviour and map bottom left or right to hotkey we can surely change this.

Please do this. I'm not doing anything abnormal, but going forward or back it is easy to accidentally trigger them, or worse, since they are on the bottom edges, just holding the device wrong will do it. The bottom right isn't as bad as the bottom left. The pitch menu is something that would be rarely, if ever used. Most people don't want to mess up the pitch when listening.

Also, I cannot seem to copy songs onto my microSD over USB without it locking up in the middle of a copy and then dismounting the drive. I have to take the microSD out and copy stuff to it elsewhere. Computer will say "cyclic data error" or something similar when trying to copy. I have to reboot the fuze+ to get it to read the card again. Is this a known bug? Is it my device? Is it my microSD card (which works fine in my sansa fuze V2)?
Title: Re: Sansa Fuze+
Post by: pamaury on January 27, 2014, 05:21:36 PM
Several people have reported failures on the microSD port over USB but I was not able to reproduce the issue so far. Is it deterministic on your device ? If so, I am very interested, maybe we could experiment a few things to try to determine the cause of this issue. Maybe you can PM me so we can discuss the detail without polutting the thread.
Title: Re: Sansa Fuze+
Post by: silvertree on January 27, 2014, 06:49:51 PM
Quote
Anyway, if people are generally in favour of dropping this behaviour and map bottom left or right to hotkey we can surely change this.

Please do this. I'm not doing anything abnormal, but going forward or back it is easy to accidentally trigger them, or worse, since they are on the bottom edges, just holding the device wrong will do it. The bottom right isn't as bad as the bottom left. The pitch menu is something that would be rarely, if ever used. Most people don't want to mess up the pitch when listening.


I for one, use 3 of the 4 features supported by these buttons.  I do not use the Track info [long press of bottom right.]

I have no issue with making these features togglable but I balk at the proposal to remove these features outright. 


If I may speculate, a bulk of these touch interface issues could be addressed with gesturing being introduced.  Though I understand the difficulty in implementing such a feature.

As always, I appreciate your work.

Title: Re: Sansa Fuze+
Post by: rapthead on January 28, 2014, 12:44:35 PM
Hi, i have some bug in theme engine. In WPS screen if keyboard is locked and playlist is ended you go back to the library and when i add some new songs to playlist wps lock icon show 'unlocked' state but touchscreen and screen actualy locked. When i press any key lock icon show right state - 'locked'. I think %?mh<|> directive work sometimes incorrect. Can anybody help me? Maybe somebody can tell me in which file in source tree i must search this problem?

P.S. Sorry for my bad English
Title: Re: Sansa Fuze+
Post by: halonachos117 on January 30, 2014, 12:20:42 AM
I'll have to cast a vote for not changing the keymap. IMHO, the keymap is perfect as it is. Of course, I'll still be greatful no matter what happens. 8)

TheGreatYashu, did you know you can lock the screen while in either the radio screen or the WPS by quickly tapping power button? That way, you can force the Fuze+ to ignore the touchpad altogether.
Title: Re: Sansa Fuze+
Post by: thegreatyashu on February 01, 2014, 01:01:16 PM
Quote
TheGreatYashu, did you know you can lock the screen while in either the radio screen or the WPS by quickly tapping power button? That way, you can force the Fuze+ to ignore the touchpad altogether.

Yes, but what happens is when I hold it to change tracks or seek and such, the touchpad detects the edges of my hand, or other parts of my fingers and go to the pitch menu. The touchpad is super sensitive. I would like the ability to change the keymap for those shortcuts. Maybe to something else, maybe disable. An option for this. I understand if it is not possible or high priority.

I'm glad to have rockbox on it regardless.
Title: Re: Sansa Fuze+
Post by: pamaury on February 01, 2014, 01:03:17 PM
Don't forget that you can change the touchpad sensitivity using the setting menu.
Title: Re: Sansa Fuze+
Post by: pamaury on February 10, 2014, 05:46:53 PM
Hi all,
I have committed a number of changes recently: they should be mostly invisible but they might hopefully remove the audio glitches. If you previously suffered from these glitches, please tell me if it helps. If you get unusual crashes please report too of course.
Title: Re: Sansa Fuze+
Post by: pamaury on February 19, 2014, 01:14:33 PM
Hi again
since someone popped up for the 1000th time about volume keys when WPS is locked, here is a patch for those who want to try and/or contribute and/or improve and/or use it for their private builds. It mixes ideas from metaphys and from action contexts and I feel it's clean enough to share and maybe commit (although debate is necessary).
http://gerrit.rockbox.org/r/#/c/760/ (http://gerrit.rockbox.org/r/#/c/760/)
Title: Re: Sansa Fuze+
Post by: dirwiz on February 21, 2014, 12:47:07 PM
Just picked up a Sansa Fuze+ (Refurb) and after loading up the latest dev build: 8927df4-140217 firmware: 02.38.06 the unit is crashing a lot.

One specific example is just paging through the files on the internal drive.
Prefetch abort at FFFFFB5C
FSR 0x88
(domain 8, fault 9)
pc: FFFFB5C sp:600008BC
bt end

It seemingly comes up randomly.  Any ideas?
Thanks much!
Title: Re: Sansa Fuze+
Post by: pamaury on February 21, 2014, 03:22:47 PM
Can you retry with the default theme and by resetting the settings ? That would help narrowing down the errors otherwise it's just impossible to get a clue about what happen. The address suggests memory corruption which is extremely hard to debug.
Title: Re: Sansa Fuze+
Post by: dirwiz on February 21, 2014, 03:46:05 PM
No such luck.  I wiped the entire memory clean including .rockbox.  Used the installer and only put in the bootloader and rockbox itself, no extras.. The menu is unusuable.. darned thing keeps crashing a few seconds after I start using it..

I even went farther and used gparted and created a new partition table AND a win32 partition.. Same results.
Title: Re: Sansa Fuze+
Post by: dirwiz on February 25, 2014, 07:39:55 PM
pamaury,
You are welcome to send me test builds to help debug this.  I can also be on IRC if that helps.  My timezone is EST.
Title: Re: Sansa Fuze+
Post by: Julian67 on February 26, 2014, 08:06:50 PM
Hi again
since someone popped up for the 1000th time about volume keys when WPS is locked, here is a patch for those who want to try and/or contribute and/or improve and/or use it for their private builds. It mixes ideas from metaphys and from action contexts and I feel it's clean enough to share and maybe commit (although debate is necessary).
http://gerrit.rockbox.org/r/#/c/760/ (http://gerrit.rockbox.org/r/#/c/760/)

I've been using a build with this commit for a few days and the feature is very useful with no apparent drawbacks.  The volume buttons require very positive pressure and it's hard to see how they could be pressed unless done deliberately.    It's good to be able to change the volume unsighted (i.e. player with locked WPS in pocket or in the dark) and will also be better for anyone wearing gloves, people using the player in flip cases and so on.
Title: Re: Sansa Fuze+
Post by: TAC109 on February 27, 2014, 03:44:29 AM
Just got myself a Fuse+ and am enjoying it with Rockbox. However I can't find the "Quick menu" key combination. It's not in the manual either. Has this been implemented yet?  Thanks
Title: Re: Sansa Fuze+
Post by: monoid on February 27, 2014, 03:31:22 PM
@Julian67

+1

Even thought, this semi-locked approach might be against general RB rules, I would also prefer to have possibility to lock only touchpad and leave volume keys unlocked even when Fuze+ is locked.

One has to lock Fuze any time it is not placed on table. Being able to adjust volume without need to remove it from pocket, unlock it, do volume change, lock it and put it to pocket would be handy.

But one can live with how it works now.
Title: Re: Sansa Fuze+
Post by: pamaury on February 27, 2014, 05:05:01 PM
Just got myself a Fuse+ and am enjoying it with Rockbox. However I can't find the "Quick menu" key combination. It's not in the manual either. Has this been implemented yet?  Thanks

I just had a look at the keymaps and apparently the quick menu combination is not mapped in the standard context. If you have a reasonable suggestion for a mapping maybe it can be added to the keymap.
Title: Re: Sansa Fuze+
Post by: silvertree on February 27, 2014, 06:20:29 PM
During WPS the quick menu is bottom left short press.

Am I missing something or not understanding the question?
Title: Re: Sansa Fuze+
Post by: pamaury on February 28, 2014, 04:27:19 AM
@silvertree: the quick menu is only mapped in the WPS at the moment and not in any other screen
Title: Re: Sansa Fuze+
Post by: metaphys on March 06, 2014, 04:11:09 AM
Jep when I did the keymaps I assumed it was better to have the more browsing keys available and let the playing settings available in WPS. The idea is that the WPS is only one keys away from any screen. This allows to save extra keys for next/previous page on tree context. If you have big library like the f+ can handle (16GB + 32GB for instance) those keys are really usefull
In tree list the only keys that would be available are those bottom left and bottom right key - All the rest is lock up by rockbox policy. For instance Left and Right are redundant with back and select but we need to keep them for consistency.
I don't really see this change idea as usefull but I guess it depends a lot on the way you use your device...

Pamaury:
I'm just reinstalling your sd mod on my fuze+ with a new card... If it breaks I'll send it to warranty and at least we will know for sure that this is broken... I can't stand the android version anyway... it's still way too buggy and I don't have time to debug it for now...
Title: Re: Sansa Fuze+
Post by: silvertree on March 06, 2014, 02:03:07 PM
I for one, am content with the button layout.  I love the page up/down during file browser.

I would suggest that during file browser the power button could be the HotKey.  I really miss having a browser hotkey.

Also long press left/right on file browser to scroll the text of long file names.

I've never needed access to quick screen in browser.
Title: Re: Sansa Fuze+
Post by: metaphys on March 08, 2014, 07:13:38 AM
you are right, I forgot the power keys... But I doubt that could go through RB policies to let us map anything that power or lock on this keys.... If that get accepted I'm all for it :)
Title: Re: Sansa Fuze+
Post by: halonachos117 on March 18, 2014, 03:41:48 PM
Perhaps a long press of the middle row, left colum would do.

Also, I have one unrelated keymap recommendation: have the top left button go back one menu on short press (like it used to). A long press could be used to return to the main menu.
Title: Re: Sansa Fuze+
Post by: metaphys on March 24, 2014, 10:48:25 AM
In my experience the long/short press is to sensitive on such function to work well. It would worth another try. I will see I i can make a test build soon
Title: Re: Sansa Fuze+
Post by: metaphys on March 24, 2014, 01:33:27 PM
 @Pamaury: I just notice that my fuze+ won't charge above 85% is there something new?
Title: Re: Sansa Fuze+
Post by: pamaury on March 24, 2014, 01:47:28 PM
No, I don't think the charging code or the battery calibration has been changed recently. I'll try with my fuze+ but it may indicate a bad battery perhaps.
Title: Re: Sansa Fuze+
Post by: halonachos117 on March 26, 2014, 12:37:27 AM
Metaphys: I've been having the similar issue, with my device not being able to charge past 90%. However, in my case, I'm quite sure it's simply due to my battery getting old, perhaps the same is happening to you. Try recharging from within the OF. Then, disconnect the player, go to Settings > Info, and scroll to the battery percentage indicator. If the OF only shows ~85%, perhaps your battery is no longer capable of charging to 100%.

If there is a charging bug, perhaps you can avoid it by charging from either the Rockbox bootloader or the OF.

Please note: the OF can be a bit slow in recalulating battery levels, so you might need to wait a few seconds to get an accurate readout. If you don't wait, the OF may show a better charge than you actually have (eg, saying you are 99% charged when you are only 80%).
Title: Re: Sansa Fuze+
Post by: silvertree on March 29, 2014, 10:52:39 AM
I, too, have observed something over the past 2 months regarding charging levels.  I figured it was an aging battery.  Sometime after a full night of charging it was still only 60 percent.

Until last night.  I was awakened early for unrelated reasons and I used my player to distract my restlessness.  At that time the charge level was near 95% and as the morning progressed, while still plugged into the USB charger, the battery level continually dropped.

I speculate that for some reason once optimal charge is completed all charging ceases although the device stays powered on because it is connect to external power.  This could be why my device is at 60% by morning.

It's just an idea, but since I have owned the device, this is a somewhat new experience.
Title: Re: Sansa Fuze+
Post by: monoid on March 29, 2014, 11:15:36 AM
Interesting observation.

Usually, I do charging in a way I plug Fuze+ in USB power adapter. Fuze goes on and starts play. I stop playback to reduce comsuption and let it be. Usually for not too long, few hours.

I recolect that it did happen several times, that after long overnight charging it was only 50-60% full. I thought, I did something wrong or that there was bad connection in USB connector or the power adapter is not fully OK. Something like that.

But what if the problém is, that Fuze+ charges to make battery as full as possible and than stops charging and goes on battery. If it is overnight charging, maybe 5-6 hours. And battery becomes partly discharged.
Title: Re: Sansa Fuze+
Post by: pamaury on March 29, 2014, 11:20:09 AM
I see, it looks like a charging problem. I will investigate the problem, no need to report it again. Thanks/
Title: Re: Sansa Fuze+
Post by: metaphys on March 29, 2014, 02:07:49 PM
Well after one complete cycle my battery charge again fully, so it might have been weakened by staying at 0 for long but I don't have a charging problem anymore
Title: Re: Sansa Fuze+
Post by: timtoo on April 02, 2014, 10:07:53 AM
My beloved e260 screen finally got smashed, so I'm trying the Fuze+. I had to compile it myself as the firmeware link in the install instructions appears to be broken (and also RockboxUtility fails to download it).

It works pretty well so far, though I have had a couple of lock ups...

Several times i've triggered a kernel panic/crash when inserting the SD card. This doesn't happen all the time, but always does eventually. Especially if removing/replacing the card quickly. The message displayed is:

Code: [Select]
*PANIC*
microSD init failed : -100
pc:60061360 sp:600F9968
bt end

The other freeze-up I had seemed random and has not repeated, so I can't narrow in on what may have caused it.

Is there an explanation of how the touchpad/buttons work on Fuze+ anywhere? I figured out the obvious up/down/left/right & select presses, but didn't even realise you could press the lower/right & lower/left quadrant area, for example, until reading this thread. (And finally figuring out that lower/right quadrant press changes mode on the pitch screen -- something that had been baffling me. My old e260 used the record button for this, which of course does not exist on Fuze+.)

I'm looking at keymap-fuzeplus.c source code and slowly starting to understand the constants there... but it's a pretty rough way to learn.  ;)

(Okay, fourth attempt at solving the captcha to post now... what the hell?!)
Title: Re: Sansa Fuze+
Post by: pamaury on April 02, 2014, 10:13:43 AM
Hi,
I'm not sure what you mean by broken because the usual link (http://build.rockbox.org/data/rockbox-sansafuzeplus.zip (http://build.rockbox.org/data/rockbox-sansafuzeplus.zip)) works for me.
Also you must be aware that we have a manual which documents all the keymap, it took a lot of work to write it down.
For the sd panic, yes it's a known thing, could be solved but in practice it never happen if you don't insert the sd half-way and remove it.
It would be interesting if you could have a reproducible sequence of the lock-up.
Title: Re: Sansa Fuze+
Post by: MadkaT on April 02, 2014, 10:31:29 AM
I think he's saying that the Dropbox link for the bootloader are dead, I was trying them too.

Well, I have a Sansa Fuze plus too, and I have a pair of questions, I've installed rockbox like a year ago, but when the battery reaches 0 percent of charge and I try to charge the sansa with the pc, It wont boot in the Original Firmware, it boot in Rockbox USB Mode, and if I try to restart I get a white screen showing a stack overflow message (stkoflw or something like that i can't remember) my question is: If I update the bootloader file it fixes this boot problem when the battery is fully discharged and won't boot in original firmnware? I have installed rockbox from the Rockbox utility from windows. I think those files don't have applied this fixes if they're accesible.

Thanks for reading.
Title: Re: Sansa Fuze+
Post by: pamaury on April 03, 2014, 05:17:36 PM
Hi,
I will remove the dropbox links, they are not supposed to be used anymore anyway. The current bootloader version is "V2" so if you bootloader displays "V1", you should update it.

EDIT: there are no dropbox links on the wiki so I don't know which links are supposedly dead.
Title: Re: Sansa Fuze+
Post by: MadkaT on April 03, 2014, 06:39:23 PM
Yes, when I turn it on it says Bootloader 1.0 but where can We get the Ver 2 of the bootloader?
Title: Re: Sansa Fuze+
Post by: pamaury on April 04, 2014, 03:12:56 AM
As always, install it with RockboxUtility...
Title: Re: Sansa Fuze+
Post by: Frenchie23 on May 30, 2014, 04:49:35 PM
"Keys:Physical keys are handled (see (1)). Touch pad RMI driver has been implemented, some basic gesture analysis has been written but needs to be enhanced. "
100% it is when ?
Title: Re: Sansa Fuze+
Post by: [Saint] on May 30, 2014, 07:22:03 PM
100% it is when ?

Some time between now, and never.

Such is the nature of the project.

People work on what they want to work on, when they want to work on it, if they want to work on it.
You could perhaps help to speed up completion by contributing to the project yourself.


[Saint]
Title: Re: Sansa Fuze+
Post by: pamaury on September 08, 2014, 06:08:32 AM
Hi All,
The Fuze+ has gained a new feature: the touchpad has a configurable deadzone between buttons, to prevent mispress. You can find it next to the sensitivity setting.
Title: Re: Sansa Fuze+
Post by: Njones on September 08, 2014, 05:21:44 PM
Is this in the latest development build?
Title: Re: Sansa Fuze+
Post by: __builtin on September 08, 2014, 06:01:12 PM
Is this in the latest development build?

Yes, it was commited very recently.
Title: Re: Sansa Fuze+
Post by: Njones on September 08, 2014, 06:53:10 PM
What is a reasonable # to set it on.
?
Title: Re: Sansa Fuze+
Post by: [Saint] on September 08, 2014, 07:14:39 PM
What is a reasonable # to set it on.
?

Whatever feels reasonable to you.

Experiment.


[Saint]
Title: Re: Sansa Fuze+
Post by: fennectech on December 09, 2014, 03:13:17 AM
hey pamaury   your code runs on my device    you do great work   thank you for creating this port :D
Title: Re: Sansa Fuze+
Post by: pamaury on May 03, 2016, 11:09:40 AM
Hi All,
some update on the target. I haven't touched the fuze+ for a long time, I'm sorry. I have been doing some maintenance, and posted some patches on gerrit to review and test. Here is a short overview of what is coming:
Title: Re: Sansa Fuze+
Post by: Julian67 on April 17, 2017, 02:28:36 PM
Hi All,
some update on the target. I haven't touched the fuze+ for a long time, I'm sorry. I have been doing some maintenance, and posted some patches on gerrit to review and test. Here is a short overview of what is coming:......

Hi pamaury, I didn't log-in here or check for progress for a long time as my Fuze+ has become redundant in these days of cellphones with high quality audio playback.  But I still have it and it simply refuses to die so anyway this evening I charged up my Fuze+ and built the newest Rockbox from git.  Very nice!  OK I am almost a year late but thank you pamaury for the device specific improvements.  The auto lock stuff is great, as I like to have volume hardware keys active when touchpad is locked; this is so much easier and better than the old patches i.e. http://gerrit.rockbox.org/r/#/c/760/  and it's very nice that different people can make their own choices.  The general touchpad and menu UI improvements are very welcome too.

I have to say this thing still sounds very nice with my Shure SE215 and SE425.  I'm still impressed by it.

I am now thinking I might be interested in a 512GB micro SDXC if such a thing ever becomes a reality.  Probably you should pay half ;-)
Title: Re: Sansa Fuze+
Post by: Julian67 on May 03, 2017, 06:10:17 PM
Naturally two days after I posted this my Fuze+ died on me (faulty USB hardware making kernel panic).  Oh well, back to the iRiver H140 which will is now 14 years old but has been revived with SSD and big capacity battery.  In that time it has seen the the arrival and death of several phones and three Sansa players.
Title: Re: Sansa Fuze+
Post by: greatjack on September 20, 2017, 01:39:54 PM
Im looking into getting a new device, I just wanted to know what the state of the fuze+ touch pad driver is, last time i tried it with rockbox it was limited to tapping the arrows. Has any progress on gesture analysis been made? If yes what is the status of it? is it comfortable to use?
Title: Re: Sansa Fuze+
Post by: pamaury on September 20, 2017, 01:40:56 PM
No the state is the same, we do not support gestures.
Title: Re: Sansa Fuze+
Post by: InGearX on October 20, 2017, 06:02:34 AM
any idea what is max capacity that Sansa Fuze+ will support?

128GB FAT32? maybe even 200GB and 256GB?

official page is useless - as it says 32 GB for Sansa Clip+  and Sansa Clip Zip  but I have formatted my 128GB microSDHC and works fine
says the same for Sansa Fuze+ but it is older - so who knows
https://kb.sandisk.com/app/answers/detail/a_id/200/~/highest-capacity-memory-card-supported-by-a-sansa-player


https://www.rockbox.org/wiki/SansaFuzePlus

PLEASE - IF YOU REPLY - send me also a PM - as I will also get an email ... (as this thread is rarely updated / checked )

thank you so much
Title: Re: Sansa Fuze+
Post by: pamaury on October 20, 2017, 06:08:19 AM
I have no idea if the original firmware has a limit on size of the microSD card. Rockbox has no limitation and 128GB cards should work without problem. One thing for sure is that this is no electrical limit, it's entirely a software thing.
Title: Re: Sansa Fuze+
Post by: InGearX on October 20, 2017, 11:39:57 PM
I have no idea if the original firmware has a limit on size of the microSD card. Rockbox has no limitation and 128GB cards should work without problem. One thing for sure is that this is no electrical limit, it's entirely a software thing.
thank you would love a confirmation from anyone who got it working with 128GB

before I order some ...

thank you ...
Title: Re: Sansa Fuze+
Post by: electropirate on October 21, 2017, 04:23:57 AM
64 GB no issues ;D
Title: Re: Sansa Fuze+
Post by: InGearX on October 22, 2017, 06:06:23 AM
64 GB no issues ;D
NICE!! thank you so much!!

128 GB should be good to go as well then
and 200 and 256

will see