Shanling Q1

[mambo5king]

I'll send it tonight, it's on my other laptop

That's great.  Thank you very much!

[mambo5king]

After restoring the Shanling Q1 bootloader sent to me by illegalval (thanks again), my Q1 is restored to the original firmware.  I compared the file she sent me with the backup I took and they're the same size but the contents are different.  Mine must have been corrupted or the backup process didn't work.

Anyway, just recording this here in case anyone is searching for a similar solution.

[illegalval]

Happy to help! Don't hesitate to contact me if you need my backup file

@amachronic I have a potential bug report: scrolling by moving the scrollbar up and down does not work on the right side of my screen, only on the right side. I've tried increasing the size a lot, and this still doesn't work. My touchscreen is not defective as far as I understand it, as instead of scrolling, I seem to click on whatever menu item my finger is hovering over.

Also i wondered if you saw my post about the keyboard, if it's possible to change the keyboard layout (and make it bigger) via theming? I've read everything regarding the touchscreen and the keyboard in the manual, and also saw that one of the developers had started working on a keyboard layout change? I don't want to stress you in any way about making changes!! I just wondered  

[amachronic]

@amachronic I have a potential bug report: scrolling by moving the scrollbar up and down does not work on the right side of my screen, only on the right side. I've tried increasing the size a lot, and this still doesn't work. My touchscreen is not defective as far as I understand it, as instead of scrolling, I seem to click on whatever menu item my finger is hovering over.

So which doesn't work? The left side or the right side?    Could it be a theme issue? What theme are you using?

I'm using the scrollbar on the right and sometimes get false menu clicks, but it does work. Bogus clicks are a general rockbox touchscreen problem. I've found the trick with the Q1 is that the touchscreen is still sensitive if you keep your finger all the way to the edge, almost not touching the screen, that way you are "guaranteed" to hit the scrollbar.

Also i wondered if you saw my post about the keyboard, if it's possible to change the keyboard layout (and make it bigger) via theming?

Unfortunately the keyboard cannot be themed but you can load limited custom layouts, see https://www.rockbox.org/wiki/LoadableKeyboardLayouts. When you load a layout that way the keyboard should switch to the menu UI font.

one of the developers had started working on a keyboard layout change? I don't want to stress you in any way about making changes!! I just wondered  

Bilgus was working on the keyboard, somewhat based on this old VKeyboard idea, which I personally think would be an ideal keyboard for Rockbox (both for touch and non-touch) but I don't think it's close to being done.

[illegalval]

@amachronic I have a potential bug report: scrolling by moving the scrollbar up and down does not work on the right side of my screen, only on the right side. I've tried increasing the size a lot, and this still doesn't work. My touchscreen is not defective as far as I understand it, as instead of scrolling, I seem to click on whatever menu item my finger is hovering over.

So which doesn't work? The left side or the right side?    Could it be a theme issue? What theme are you using?

I'm using the scrollbar on the right and sometimes get false menu clicks, but it does work. Bogus clicks are a general rockbox touchscreen problem. I've found the trick with the Q1 is that the touchscreen is still sensitive if you keep your finger all the way to the edge, almost not touching the screen, that way you are "guaranteed" to hit the scrollbar.


It's the right side that doesnt work, the left one is fine! Weirdly enough, it doesn't work on the Oscar themes, the Samsung one and on the Interpod which Christian kindly customized for the Q1. The right scrollbar used to work fine. Yesterday i updated Rockbox to the latest dev build, it had been a few months since I had updated it. Could it be that?

Also - thanks for the clarification on the keyboard! I'm gonna check out your suggestions! Thanks for all your work.

[illegalval]

lol my answer is within the quote!

[illegalval]

Amachronic - things are fine again! I reset the settings in "Manage Settings". Weird that it stopped working, I also played around with a theme, when suddenly it decided to ignore certain settings in it's .sbs file - only reset fixed this, not importing and overwriting the theme again. Weird, but happy to know how to fix issues like this.

[amachronic]

Amachronic - things are fine again! I reset the settings in "Manage Settings". Weird that it stopped working, I also played around with a theme, when suddenly it decided to ignore certain settings in it's .sbs file - only reset fixed this, not importing and overwriting the theme again. Weird, but happy to know how to fix issues like this.

If you switched themes, one of them maybe enabled a setting that the other didn't reset. So yeah, resetting your settings would help in that case.

Anyway after doing some testing, the scrollbar works fine on cabbiev2, either left or right side, but on Interpod it's iffy. I think the problem is that the UI viewport doesn't extend all the way to the edge of the screen with that theme. There are a few pixels of dead space on the left and right. Touchscreen presses outside the UI viewport get ignored so touches are likely going into the empty spaces on the borders.

I'm not sure how best to fix this -- but a workaround would be to go into the .sbs, and change the %Vi viewport to occupy the full width of the screen.

[amachronic]

After restoring the Shanling Q1 bootloader sent to me by illegalval (thanks again), my Q1 is restored to the original firmware.  I compared the file she sent me with the backup I took and they're the same size but the contents are different.  Mine must have been corrupted or the backup process didn't work.

Anyway, just recording this here in case anyone is searching for a similar solution.

Would you happen to have your original "bad" backup still?

illegalval, would you also mind sharing your good backup?

I'd like to compare them. There's been another complaint of "can't remove rockbox" on head-fi, so I guess this isn't a one off problem.

[mambo5king]

After restoring the Shanling Q1 bootloader sent to me by illegalval (thanks again), my Q1 is restored to the original firmware.  I compared the file she sent me with the backup I took and they're the same size but the contents are different.  Mine must have been corrupted or the backup process didn't work.

Anyway, just recording this here in case anyone is searching for a similar solution.

Would you happen to have your original "bad" backup still?

illegalval, would you also mind sharing your good backup?

I'd like to compare them. There's been another complaint of "can't remove rockbox" on head-fi, so I guess this isn't a one off problem.

I sent you a link to the bad bootloader in a PM

[illegalval]

After restoring the Shanling Q1 bootloader sent to me by illegalval (thanks again), my Q1 is restored to the original firmware.  I compared the file she sent me with the backup I took and they're the same size but the contents are different.  Mine must have been corrupted or the backup process didn't work.

Anyway, just recording this here in case anyone is searching for a similar solution.

Would you happen to have your original "bad" backup still?

illegalval, would you also mind sharing your good backup?

I'd like to compare them. There's been another complaint of "can't remove rockbox" on head-fi, so I guess this isn't a one off problem.

I sent you a message with a link to it now!

[amachronic]

[...] Mine must have been corrupted or the backup process didn't work.

Your backup contains rockbox-info.txt... what appears to be random junk... and apparently a copy of bootloader.q1! Whatever the case, that backup can't have come from a bootable device.

I'll add some basic sanity checks to the restore process to prevent it flashing total garbage, but honestly, I have no idea how all that junk got into your backup in the first place. Especially rockbox-info.txt, since it doesn't exist anywhere except inside the .rockbox folder, and the bootloader doesn't open it.

[7o9]

Is restoring a backup of the stock bootloader that you are suppose to make when installing Rockbox the way to revert to the stock firmware?

I always thought reinstalling a Shanling firmware would do it, but that must not touch the bootloader then.

I know I made the backup initially, but lost it at some point.

[amachronic]

Well, illegalval's backup is identical to my own. Modulo the expected differences from Ingenic's bugs, at least.

It seems Shanling's firmware updates don't package the bootloader, unlike the Fiio M3K. And it doesn't have a full copy of U-Boot, it uses the same single stage X-Loader SPL that the M3K does. (There's still a big empty partition allocated for U-boot though; that's probably why I was thinking the Q1 used U-boot...)

So... I'll give the updates a shot on my player and see if Shanling's updater damages anything. I definitely tested booting the recovery kernel; maybe I never used it to see if it worked?

[amachronic]

Is restoring a backup of the stock bootloader that you are suppose to make when installing Rockbox the way to revert to the stock firmware?

Yeah, that's supposed to be the tried & true method.