Support and General Use > Hardware
Serious heat issue with Fuze V2
saratoga:
Would capping it at 20 be enough? Or should it be less?
nexekho:
I'm very sorry for the bump, but this is important.
I managed to get my Fuze replaced not long after my previous posts, and I was wondering if the issue had been diagnosed and fixed so I looked and saw the V2 was considered "stable". I look through this thread and notice nobody knows what's actually causing it or has fixed the issue. If a basic power management problem exists under this firmware and not the stock firmware, then the problem is quite obviously with this firmware. Perhaps some devices are "lucky" or exist in a colder climate so the problem is less apparent. It doesn't matter. And even though several people have had their devices ruined by Rockbox, you've pushed it up to stable. Now I appreciate all the work you put in. Rockbox is fantastic. But it's irresponsible to have a fairly lengthy discussion from which I can draw the conclusion "It'll quite possibly kill your Fuze V2 through normal use" ignored. Most of the posts of which are less than a few months old.
You cannot be serious about marking it stable if this isn't fixed.
yapper:
I've been using a 4GB v2 Fuze for some months with no problems. I have the wheel light timeout set to 2 seconds, backlight set On and brightness set to 14. I've used it for extended periods outdoors in 90 degrees F plus temperatures and haven't observed any unusual heating issues.
There was a change made in May that reduced the maximum brightness setting to 20.
EDIT: OF V02.03.33A allows the brightness to be adjusted over 12 steps. I have no way of knowing if their steps correspond to Rockbox's 1-12 or maybe 5-16 ...
nexekho:
I can't see anything in the change logs? I'd consider "brightness capped to prevent permanent damage" more important than say "Remove track-number generation heuristic from database". And just choosing a seemingly arbitrary number to cap the brightness at doesn't sound like a solution. If I can have my brightness on full on original firmware, but we can't have it on Rockbox without blowing your device's power supply, it smells as if there's another more serious bug lurking and capping the brightness is just a sticking plaster.
[Saint]:
I don't happen to consider having the screen brightness maxed out for extended periods "normal use", also, it was not promoted to stable *after* this was discovered either. It was marked as stable well before then if I remember correctly.
This is also not something that is happening with all of these devices, mine for instance are fine and I see no overheating.
The developers cannot be help responsible for testing every single circumstance that may arise in the usage of the device, as what is "normal" usage to you may not be to them.
To many people these are audio players, not flashlights or ways to play Doom etc. etc. ;)
The developers also can't (nor should they) drop a port from stable to unstable based on problems that only a few devices are seeing. If that was the case then there would be very few ports (if any) that were "stable".
There have been limits set to (hopefully) prevent this overheating issue, but that's not to say that there are not as yet unknown variants of the hardware that will still be damaged by these new "safe" settings.
Also, you must consider that this is *free* software, and under no guarantee whatsoever, it is a conscious decision you are making to install it and if your device is damaged or left in a completely bricked state after installation or usage normal or otherwise then that falls on you and not the Rockbox team.
[St.]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version