- Status Closed
- Percent Complete
- Task Type Bugs
- Category
- Assigned To No-one
- Operating System
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Opened by Anonymous Submitter - 2003-11-24
Last edited by linusnielsen - 2004-04-09
FS#1816 - odd backlight behavior
This would be an Archos FM Recorder, 20gb version (JBR FM
20GB). Firmware would be the FM Recorder firmware, daily build
for November 23rd (CVS=031123).
Hardware info:
ROM: 1.23
Mask: 0×0504 USB: positive
ATA: 0×200, master
PR: positive
Flash: M=BF D=D6
ROM CRC: 0x222F V1
I have the backlight set to turn itself off 1 second after pressing any
button, but this only happens about half the time. The other half of
the time the backlight stays on for a second then becomes really
bright, then slowly (over the course of about 10 seconds) fades in
intensity to nothing. Whether it does this or turns off correctly seems
to happen at random.
- atmcsld@sbcglobal.net
2004-04-09 23:56
Reason for closing: Rejected
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
Logged In: YES
user_id=259137
This happens with the original firmware
as well. It's a
hardware
issue.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
Yea my Recorder 10 also does that. Sometimes the backlight
goes off instantly, other times it becomes bright, then takes
time to fade out.
As far as I know, this is a hardware problem. Can you verify
that this also occurs with the original firmware?
This happens with the original firmware as well. It’s a
hardware issue.