Sansa Fuze+

[halonachos117]

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.

[xpmule]

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..

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

[saratoga]

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. 

[xpmule]

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..

[[Saint]]

"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 and then  ask on 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]

[pamaury]

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/
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:

• auto slow: this allows the hardware to automatically clock down when idle, we can choose the frequency divider (currently set to 8 ). Higher divider means more savings but also less responsiveness and potentially more changes so not so efficient if too high !
• frequencies: currently we boost at 454MHz (max) and unboost at 261MHz. Boosting at max seems reasonable but we could unboost even lower at 64MHz. Perhaps this could improve battery life.
• emi: we curently don't touch the sdram frequency because it's rather tricky. It's not a real problem because it's running at 130MHz but in theory we could push it up to 150MHz for even more performance when boosting.

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 !

[pamaury]

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.

[Roboturner913]

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.

[metaphys]

Test on two different device have proven an incredible 39h of continuous playback (mp3 128) for one charge!  (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...

[buckminster]

I take it frequency scaling is enabled now? 

http://git.rockbox.org/?p=rockbox.git;a=blob;f=firmware/export/config/sansafuzeplus.h

[halonachos117]

Indeed, it is! HERE is the proof.

[fsclavo]

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!!

[Roboturner913]

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.

[sstavross]

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?

[Roboturner913]

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.