Rockbox

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bugs
  • Category User Interface
  • Assigned To No-one
  • Operating System Sansa AMSv2
  • Severity Low
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by idak - 2011-09-25
Last edited by freddyb - 2011-09-27

FS#12292 - Sansa Clip+: Cannot boot since r30589 with real target

Sansa Clip+: Cannot boot since r30589 with real target.

Bootloader is displayed, but rockbox main menu is not displayed (black out) since r30589 with real target.
Simulator is all ok.

Closed by  freddyb
2011-09-27 22:14
Reason for closing:  Fixed
Additional comments about closing:  

Fixed in r30613 by delaying settings_reset() until after font_init() for hardware targets.

reset your settings. if the menu is blacked out it did boot… most likely oyur theme didnt load and it set bad default colours

idak commented on 2011-09-25 08:13

I reset my settings (delete .rockbox and reinstall new one). But rockbox main menu is not displayed.

exact same issue here. i have to do a long power off to reset so i know it’s not a simply case of the display not being visible. it must have panicked/froze.

The same thing happens on my Sansa Fuze v2. Whiteout, player hangs.

My Clip+ boots fine with r30602, but my FuzeV1 dies at a white screen immediately after the bootloader version flashes on the screen. Clearing the settings and checking the disk for errors did not help.

my e200v2 behaves the same as saratoga’s FuzeV1 - works fine with r30588 - fails with r30589

Looks like this might be the same bug as reported for Onda Vx747 on  FS#12290 ? Maybe we need those buflib unit tests….

Yes, and I’m sure it’s due to font cache changing and has the same reason as  FS#12290 . I think we should revert the change first and re-merge it until it’s stable.\
I can help test VX747, and there’s need for more testers.

I don’t think we should revert unless it’s not resolved and we need a release. The bug needs fixing, not ignoring.

I only have sims/Android to play with, so not sure I can help directly (but just setting up an Onda sim).

Does anything connect the Onda and Clip+ - lower memory, alignment fussiness?

this hits the clipv1 also, it doesnt appear to be a memory size issue. annoying that it doesnt crash the sim though :/

Indeed Onda sim runs fine… Some kind of hardware initialisation sequence??

We’re not trying to ignore it but we need a stable build for most users to use. We should create a branch and commit on it first. We’ll merge in back into the master when it’s stable.

Steve, the task you linked to is not the same issue, that was a fuckup on my part to not reinit fonts after usb which I’m hoping to fix on my flight tonight.
I have no idea what this issue is :/ (other than it being a data abort or something equally severe)

Jd - Ah, ok.

PurlingNayuki - Isn’t 3.9.1 the stable branch for most users? trunk is unstable and for devs only.

@Steve Bavin: Well that’s a solution :P
I can test for OndaVX747 build. The simulator isn’t always working like the real target, especially problem with booting, memory management, etc..

Well, I’m a developer and trunk has become completely unusable for me too.
If a player won’t boot properly, I can’t develop for it, it’s that simple.

I rate this issue as a pretty critical.

Hopefully r30613 fixes this.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing