Rockbox Technical Forums
Rockbox Development => New Ports => Topic started by: amachronic on May 23, 2021, 07:52:49 PM
-
Well, I know I said I wasn't gonna do this, but some users here on the forum were asking about a Shanling Q1 port which got me to investigate the "trick" to run scripts on its OF... in the end I found out a bit more information than I originally intended!
I've made some headway disassembling the Q1's Linux kernel, and probably identified most of the important hardware components. I haven't done much on the "hosted" side of things 'cause it's not easy to get an interactive shell on the player. For anybody interested I posted my current findings on the wiki, https://www.rockbox.org/wiki/ShanlingQ1Port (https://www.rockbox.org/wiki/ShanlingQ1Port).
Long story short, it looks like a native port would be pretty easy. All the hard/tedious parts were implemented with the FiiO M3K port. The main downside with a native port is that wifi/bluetooth will probably never work in Rockbox. With a hosted port we at least have a chance of wrapping the OF kernel's functionality with menus, and if Shanling's kernel is well done then tbh there may not be much benefit to a native port. In the short term I'll probably just keep checking out the hardware/software and find out if the OF kernel has any serious shortcomings.
I emailed Shanling and asked them nicely if they'd release their Linux kernel sources for the greater good of Rockbox. I'm not expecting much on that front, but who knows? They might just help us out, it's at least worth asking.
There is one other annoyance -- the Q1's screen resolution is 360x400, which isn't used by any other Rockbox player. So there's no ready-made themes for it, even Cabbie will need to be ported.
I'd like to hear opinions about wireless support... making a wild guess, given Rockbox's "target audience" maybe I'm not the only user who doesn't care much for it.
-
Well, I know I said I wasn't gonna do this, but some users here on the forum were asking about a Shanling Q1 port which got me to investigate the "trick" to run scripts on its OF... in the end I found out a bit more information than I originally intended!
I've made some headway disassembling the Q1's Linux kernel, and probably identified most of the important hardware components. I haven't done much on the "hosted" side of things 'cause it's not easy to get an interactive shell on the player. For anybody interested I posted my current findings on the wiki, https://www.rockbox.org/wiki/ShanlingQ1Port (https://www.rockbox.org/wiki/ShanlingQ1Port).
Long story short, it looks like a native port would be pretty easy. All the hard/tedious parts were implemented with the FiiO M3K port. The main downside with a native port is that wifi/bluetooth will probably never work in Rockbox. With a hosted port we at least have a chance of wrapping the OF kernel's functionality with menus, and if Shanling's kernel is well done then tbh there may not be much benefit to a native port. In the short term I'll probably just keep checking out the hardware/software and find out if the OF kernel has any serious shortcomings.
I emailed Shanling and asked them nicely if they'd release their Linux kernel sources for the greater good of Rockbox. I'm not expecting much on that front, but who knows? They might just help us out, it's at least worth asking.
There is one other annoyance -- the Q1's screen resolution is 360x400, which isn't used by any other Rockbox player. So there's no ready-made themes for it, even Cabbie will need to be ported.
I'd like to hear opinions about wireless support... making a wild guess, given Rockbox's "target audience" maybe I'm not the only user who doesn't care much for it.
A different port, but I'm interested in bluetooth support, is anybody still working on that feature, would like to use it on agptek rocker.
-
More devices is always a good thing!
But what about that touch screen; is that supported?
-
Very nice, looking forward to your progress.
The Shanling app is not bad but compared to RockBox it feels incredibly limited. A hosted version would not be bad at all though native works great on the FiiO M3K.
The wireless functionality is not needed for me, I have always only ever used it with wired buds. The wifi functionality that was added in the latest official firmware feels more like a 'because we can' feature than actually useful.
@Telehubis: Seems the touchscreen is using the same controller as the touchstrip on the M3K so it will probably work similar too.
-
I'd like to hear opinions about wireless support... making a wild guess, given Rockbox's "target audience" maybe I'm not the only user who doesn't care much for it.
WiFi probably isn't going to ever happen. The Q1 uses an SDIO-attached broadcom b43xx. It's not clear if it's a softmac or fullmac part, but either way writing a native driver for that chip is a major undertaking in its own right. Not to mention potentially writing an 802.11 stack plus coming up with network-enabled applications and usecases.
Bluetooth is a lot simpler at the "driver" level, but we're faced with having to write a stack from scratch or port the likes of bluez/bluedroid, another substantial undertaking. At least that stack would be usable for our other BT-supporting targets...
-
Just posting to let everyone know I have got Rockbox running on the Q1, but no audio or bootloader yet; I'm stuck trying to get the DAC to work. There's a patch in gerrit in case anyone is interested. The simulator works, at least (lol).
I will probably put this aside and come back later, hopefully some 'enlightenment' will strike and I'll figure out how to get the DAC working.
-
Thanks for the update and your efforts.
I read the comment in Gerrit about the state of your attempts. I also read you have great Google-fu so I am sure you found the LG V30 code for this DAC. Would have hoped that helped.
How did you run it without a bootloader? Read the code, answer is USB boot :)
Hopefully inspiration will strike at some point. The M3K port is great but the Q1 feels so much nicer and does not have the crazy touchpad.
-
Problem is, I just don't know how the board is physically wired... I've got datasheets but it's no help if the DAC won't turn on.
-
Saw in the IRC logs that you managed to get audio. Very exciting.
Great that enlightenment struck so quickly!
-
Just one note on the WiFi - perhaps a dual boot would solve it?
-
Yeah, I actually got dual boot working today for the Q1 and FiiO M3K (that was a real pain due to OF kernel bugs...)
Since I'm here, I may as well say the Q1 port pretty much "works" hardware-wise, aside from some odds and ends, but you can really feel how neglected touchscreens are in Rockbox... It's something I hope to improve over time though. I was able to jury-rig the M3K's bootloader to work on the Q1, but I don't want to release something so half-baked, with the potential for things to go terribly wrong -- my own Q1 was "bricked" for a while due to one such mistake.
-
I have been playing around a bit with the Q1 patch from Gerrit (https://gerrit.rockbox.org/r/c/rockbox/+/3460) and it works quite well.
You have to start it with usbboot as there is no bootloader yet and it takes some serious getting used to the 3x3 touchscreen grid input.
Having said that, it plays music quite nicely and just looks cool.
Hopefully one day it will be mature enough to use like any other Rockbox player. Unlike most, you can still actually buy the Q1!
Attached is a screendump taken from the actual Q1 running Rockbox and playing a tune.
-
Saw that Q1 port is available. That is such a great news!
I would like to check it out so can you please share how to install that via usbboot?
Also how to achieve dual boot / revert to OF?
Great work!
-
You'd have to compile the bootloader yourself. All needed files spl.q1, bootloader.bin/.q1 will be in the bootloader build directory. Hold the play (middle) button at boot to enter USB boot mode. Once connected, run usbboot in utils/ingenic_tools:
./usbboot -c x1000 -1 <spl.q1> --wait 1 -2 <bootloader.bin>
You'll get a recovery menu; to install the bootloader you need to place bootloader.q1 onto your SD card. You should take a bootloader backup before installation; it creates a backup file named shanlingq1-boot.bin on your SD card. In case you want to revert to the 'pure' OF, simply put that file back on your SD and choose restore in the recovery menu.
Boot options:
- hold NEXT (bottom button) to enter rockbox bootloader's recovery menu
- hold PREV (top button) to enter OF
- hold NEXT+PREV to run the OF recovery (this provides an alternate restore method if you lose your backup or want to upgrade or downgrade the OF)
Proper docs, bootloader binary, jztool support, etc, should be ready over the next little while. Theme site and daily builds will be available once the patch is merged.
Enjoy!
-
Alright, at last there's bootloader binaries available for the Q1. Installation instructions and download links are in the manual (https://download.rockbox.org/daily/manual/rockbox-shanlingq1/rockbox-buildch2.html). If there's anything unclear or confusing about the manual let me know and I'll fix it; the install process is basically the same as for the FiiO M3K so its installation forum thread (https://forums.rockbox.org/index.php/topic,53858.0.html) might clarify things.
-
The manual understandably is very generic so some pointers:
- Rockbox Utility support or a release build do not exist yet, you need a 'dev build' from the link on the top left of the Rockbox site.
- Make sure your sd card is fat32. exfat will not work.
- Windows users need to install 'Zadig' for direct usb access support.
- Put the bootloader.q1 file on your sd card before running jztool, you need to install it from the bootloader menu launched by jztool.
- You can get additional fonts here: https://www.rockbox.org/download/byhand.cgi (it does not matter the q1 is not listed, the fonts are the same for all players so pick any).
After succesfully installing, I really recommend turning on the 'Absolute Point' touchscreen mode so you can select items directly in the menus and file lists instead of using 3x3 mode.
'Touchscreen mode' is burried in General Settings -> Display -> Touchscreen Settings.
-
Hi.
I'm writing to this thread because I'm a lucky new owner of this beautiful little player (I have an iPod Video with rockbox since 2006, but it has broken :( ).
I'm installed rockbox manually on the Q1 without any problems and it is working very well.
I've uploaded a Theme for this player based on the one I've used in iPod for many years.
About this port, the few things I noticed are:
- There are no battery estimated time.
- There are no disk activity (in this case the SD card).
- For me, the height of the menu items it's to big.
- It would be nice if the keys were locked via the power button, the screen will never turn on, like the hold button in iPod. This will permit to disable the turn on of the screen on track change in case of the buttons locked.
- It would be nice too if there is an option to activate the "line-out" like in the original firmware, in rockbox the volume has to be adjusted to the maximum level manually (or via a cfg file in shortcuts.txt)
All the previous points are not essential, but would be nice to have it :)
Finally, thanks for this port!
-
Hi.
I'm writing to this thread because I'm a lucky new owner of this beautiful little player (I have an iPod Video with rockbox since 2006, but it has broken :( ).
I'm installed rockbox manually on the Q1 without any problems and it is working very well.
I've uploaded a Theme for this player based on the one I've used in iPod for many years.
Glad you found it a smooth ride! And thank you for your theme contribution. I think now we're officially up to 4 users :D
- There are no battery estimated time.
Known issue, will be fixed eventually. The power management IC used in the X1000 targets is able to report the real-time current consumption and I was hoping to use that to report battery runtime more accurately, based on the actual usage. The Q1's also got a separate, dedicated battery monitor chip which can provide percentage charge & estimated runtime directly, but it's bugged (in multiple ways) and maybe more trouble than its worth if it ends up being no more accurate than Rockbox's estimates.
- There are no disk activity (in this case the SD card).
Sounds like a bug. I'll try to get it fixed soon.
- For me, the height of the menu items it's to big.
Agreed. The height can be changed in General Settings > Display > Touchscreen Settings > Line Padding in Lists. Personally, I use 24px but the default works out to something crazy, like 66 px (it's derived from DPI, poorly). Guess I should fix the broken default.
- It would be nice if the keys were locked via the power button, the screen will never turn on, like the hold button in iPod. This will permit to disable the turn on of the screen on track change in case of the buttons locked.
Keylock is mapped to the power button but you need to configure it in General Settings > System > Advanced Key Lock. For the backlight, you need to go to Display > LCD settings > Backlight exemptions. Also, the keylock only works in the WPS in order to map the power button to 'back' in the menus.
- It would be nice too if there is an option to activate the "line-out" like in the original firmware, in rockbox the volume has to be adjusted to the maximum level manually (or via a cfg file in shortcuts.txt)
Well, it seems the Q1's DAC always outputs via an integrated headphone amp so it doesn't really have a line out in a strict sense. I did determine conclusively that the original firmware merely sets the volume to 100% when you choose line out mode. That's why Rockbox doesn't have a line out mode -- it wouldn't make much sense as you can accomplish the same thing by volume control. But I get why having an easy setting is nice.
-
Thanks for your quick answer!
I'll check your suggestions and wait for possible bug fixes :)
-
- It would be nice if the keys were locked via the power button, the screen will never turn on, like the hold button in iPod. This will permit to disable the turn on of the screen on track change in case of the buttons locked.
Keylock is mapped to the power button but you need to configure it in General Settings > System > Advanced Key Lock. For the backlight, you need to go to Display > LCD settings > Backlight exemptions. Also, the keylock only works in the WPS in order to map the power button to 'back' in the menus.
I do not think that is an answer to the question.
I have the same request, when Key Lock is on, I would like the screen not to be turned on at all when touched.
Additionally, but this is different, I would like the LCD to be turned off immediately when I turn on Key Lock.
-
Disk LED fix is now merged, it was a minor oversight in the driver. For some reason I thought it was handled elsewhere but apparently not.
7o9, are you still experiencing the backlight turning on from touches on recent builds? It should've been fixed by commit 62260aa705 (https://github.com/Rockbox/rockbox/commit/62260aa7057f322f7f99062a6a3bd7534ea0047d). Just double checked it on my end so if you're still getting the problem with the latest build please share steps to reproduce!
-
You are right, amachronic, that commit seems to help. I was on a build from one or two days before that change.
To get close to what I want, I needed to enable the 'Disable Touch' option under 'Advanced Key Lock'.
Right now I have disabled 'Backlight Exemptions', enabled 'Advanced Key Lock' and have checked the 'Exempt Volume', 'Exempt Play' and 'Exempt Skip' options (for the physical buttons), combined with 'Disable Touch'.
I still do not particularly like the screen turning on when I use those exempted physical buttons but I have not found a way around that.
Thanks!
-
I've tested the disk activity indicator and works well :)
-
I really like this player with Rockbox on it. :)
When it comes to patching; how do I do that? Do I just copy & paste Rockbox newer version folders to the player?
-
I really like this player with Rockbox on it. :)
When it comes to patching; how do I do that? Do I just copy & paste Rockbox newer version folders to the player?
Yes, extract the latest dev build to your sd card overwriting the .rockbox folder. Make sure to answer 'Yes' when prompted to overwrite existing files.
-
Hey guys! I rockboxed my Q1 yesterday and I must say that I was blown away by how great the result sounds. I find the sound improvement of RB over vanilla FW pretty substantial. Is there an explanation why that might be? Back when I was angry with iBasso players' sound signature changing with every FW release, I had a theory that those Chinese manufacturers are applying some kind of DSP to make everything sound more "audiophile" and only messing things up with it. What is correct explanation however? Or am I just plain wrong in my perception?
Also, I'm sending a small donation, this is really some great work.
-
Sorry abut OT, but why this thread was moved to this forum? Topics for other players remain in the "new ports" and this goes to "general"...
-
Any idea if playing opus files would consume more battery than other formats like ogg or mp3?
-
Hi !
Oh ! What a surprise ! I used to use Rockbox something like... 15 years back ? More ? Not sure. I used to check every now & then and thought it was dead.
I have no idea why I checked today and... It's incredible, I do have a Q1 and a port has just arrived :-)
I will definitely give it a try if that's safe enough ;-)
The official firmware is really a pain to navigate (IMHO).
Cheers ! And thanks for keeping it alive ;)
-
I will definitely give it a try if that's safe enough ;-)
No guarantees in life, but Q1 has a built-in recovery USB-mode that you cannot break by installing Rockbox. It should be very safe to install.
I have been using it since it became available and have not seen any problems.
-
Thanks for the recent touchscreen-related fixes, amachronic. Especially the keyboard that is now actual somewhat usable.
Another thing I noticed that does not seem to work on my Q1 (the only touchscreen Rockbox player I have) is the 'List Wraparound' setting.
Is that something that could be easily fixed? Especially on long lists it is quite useful to not have to scroll through the entire list to get to the other end.
-
It could be done with some effort. But you can already drag the scrollbar to quickly jump around the list, which gives you almost the same functionality.
-
The scrollbar does work indeed.
I have had some issues when dragging up first but dragging down works quite reliably. Same with down and then up.
Is the width of the scrollbar detection area related to how wide it is drawn? Perhaps I need to make it wider.
-
Yeah, the touch area is the same size as the graphical scrollbar. Looks like the touch area needs some extra 'slop space' to make it possible to use narrow bars.
-
Hi, I'm new here but considering getting the Q1! Is this port being further developed?
I am in no way experienced with programming but might look into making/modifying some themes if it isn't too hard. If I get the player, I would gladly write detailed bug reports (etc).
/Val
-
It really works good in its current state.
Rockbox is developed continuously, the Q1 port benefits from that.
I am not aware of any major problems or pending developments specifically for this device.
-
Just wanna say I got the player and ported Rockbox on it without any issues! Thanks so much Amachronic, it really makes the player much better. ;D
I have one question/bug report (?): I put some Japanese pop on it and it seems to not show Japanese characters, is this something specific for this Rockbox port or something that can happen in general?
-
Also, there seems to not happen anything when i choose the higher (2vrms) dac output mode, is this fixable?
-
Just wanna say I got the player and ported Rockbox on it without any issues! Thanks so much Amachronic, it really makes the player much better. ;D
I have one question/bug report (?): I put some Japanese pop on it and it seems to not show Japanese characters, is this something specific for this Rockbox port or something that can happen in general?
That is probably more a generic Rockbox/font issue than Q1-specific. You probably need a different font but I am not sure which one (or any) have Japanese characters.
Some fonts can be gotten under 'extras' in the top left corner of the site.
-
Ah, yeah that makes total sense that it is a font-issue, thanks. Gonna see what I can do.
-
I have one question/bug report (?): I put some Japanese pop on it and it seems to not show Japanese characters, is this something specific for this Rockbox port or something that can happen in general?
https://forums.rockbox.org/index.php?topic=15996.0
https://www.rockbox.org/wiki/UnicodeFonts
https://www.rockbox.org/wiki/UnicodeGuide
-
Thx so much! That will solve the issue :) Anyone knows about the high-gain output not working?
-
Niiiiiiice. You guys are getting a donation. My amazon review of the Q1 was absolutely stinging, and 99% of it was about the dreadful MTouch OS. Thank you for rescuing this thing from the charity shop. I was just about to toss it into a bag of other giveaways when I decided to do "one final search" to see if anyone had an alternative ROM. Imagine my sheer delight when I find that Rockbox is available for it! (I've been a long time user of Rockbox on every Sansa Clip I ever owned - sadly the last one broke a few years ago) :)
-
Just wanna say I got the player and ported Rockbox on it without any issues! Thanks so much Amachronic, it really makes the player much better. ;D
I have one question/bug report (?): I put some Japanese pop on it and it seems to not show Japanese characters, is this something specific for this Rockbox port or something that can happen in general?
You may find these font creation tools useful if you don't mind using the command line.
https://forums.rockbox.org/index.php/topic,54079.msg249705.html#msg249705
Also, there seems to not happen anything when i choose the higher (2vrms) dac output mode, is this fixable?
I committed a fix for this just now, it was a regression caused by a previous bugfix that prevented the DAC from resetting and switching to the new mode. Thanks for reporting!
-
I committed a fix for this just now, it was a regression caused by a previous bugfix that prevented the DAC from resetting and switching to the new mode. Thanks for reporting!
[/quote]
Thanks Amachronic, it works perfectly now! (It really helps my DT 880's :) )
-
Two interesting things:
1. I just got an out-of-memory panic:
*PANIC*
audio_reset_buffer(): OOM!
Right before this happened, I had plugged it into USB, rsynced tracks and playlists to it, ejected it and finally asked Rockbox to initialize the database. (After the panic, I restarted it, and it displayed the message "Committing database [1/10]" and then continued to start up.
2. My playlists are only showing the track title, no artist. The playlists I copied have EXTINF data, so Rockbox seems to be ignoring that. Is this normal? All I can find on the subject is this: https://www.rockbox.org/tracker/task/7652
-
Probably related to the panic, but the database never rebuilt itself. It seems to be stuck at "Building database... 7934 found (OFF to return)". I'll go debug that. Probably nothing to do with the Shanling port.
-
Is parametric equalizer working fine?
I am interested in purchasing this device :)
-
The EQ works well. It's a core feature available on all devices supported by Rockbox.
-
I have bought one of the last Shanling Q1's from Shenzenaudio. I have used Rockbox version 1.4 years ago on a Archos Studio. At the beginning of this year I have bought my first iPod (mini gen 2), replaced the battery and converted it to 256 GB flash storage. I am very happy with this iPod running Rockbox. So I used the opportunity to buy a new player which can run Rockbox, specially one with a touch screen.
Having said that, themes working well with touch are rare. So I have converted my (not yet published) theme Oscar from my iPod mini to the Shanling Q1. I have implemented a wps which can be used in "absolute point" mode. With this theme I am quite happy to run Rockbox on a touch device. Therefore I have uploaded this theme to themes.rockbox.org as "Oscar Q1".
Remember to turn on "absolute point" mode yourself, as it is not allowed to be set in the themes config file.
-
I have made the second update to the theme "Oscar Q1". It now hides the touch area symbols, while the device is locked.
While working on the theme, I have struggled a lot with memory. Sometimes the wps would not load at all. Other times it displayed screen artefacts in the graphics, mostly the cover art, Sometimes some random objects (images/viewports?) would not display at all. Also when using the theme "lebellium Samsung-like", the cover art would not be shown on my device. One reason could be, that my cover images have typically a size of 700x700 pixels. Another reason could be the touch areas. Is my assumption about memory constrains correct? Could the theme memory (objects, images etc.) be increased for the Q1 build? I guess bigger screens call for more memory.
BTW Finally I have released my iPod mini themes "Oscar" and "Oscar cover".
-
Memory usage shouldn't be a problem. The theme engine will allocate as much as it needs, and the Q1 has 64 MB of RAM which is a lot by rockbox standards. If you're hitting a bug or a theme engine limitation you'll need to provide more info, preferably a test case that shows the problem (as minimal as you can make it), and explain what you expect it should do, otherwise nobody will be able to help.
Also, thanks for the theme! I'll try it out on my Q1.
-
Thanks for the answer. At the moment I am happy with the result. But when I will stumble about a problem in the future expanding the theme, I will try to make a test case.
-
I have made the second update to the theme "Oscar Q1". It now hides the touch area symbols, while the device is locked.
While working on the theme, I have struggled a lot with memory. Sometimes the wps would not load at all. Other times it displayed screen artefacts in the graphics, mostly the cover art, Sometimes some random objects (images/viewports?) would not display at all. Also when using the theme "lebellium Samsung-like", the cover art would not be shown on my device. One reason could be, that my cover images have typically a size of 700x700 pixels. Another reason could be the touch areas. Is my assumption about memory constrains correct? Could the theme memory (objects, images etc.) be increased for the Q1 build? I guess bigger screens call for more memory.
BTW Finally I have released my iPod mini themes "Oscar" and "Oscar cover".
I relly luv your theme, is there any chance to make a dark version? White is too agressive for night use :(
-
I relly luv your theme, is there any chance to make a dark version? White is too agressive for night use :(
Yes, have a look at https://themes.rockbox.org/index.php?target=shanlingq1 (https://themes.rockbox.org/index.php?target=shanlingq1). ;-)
-
Thanks a lot!
-
Thanks Oscar for this nice theme, it really makes it easier to use the player.
Amachronic, I have a potential bug report. I could be using the functionality completely wrong, but the (Meier) crossfeed doesn't seem to be doing anything? I understand that the effect is subtle, but even when I tinker with the settings, nothing seems to happen. I've used Meier crossfeed on other devices and programs, and I kind of know what to look for in terms of sound. Anyone else who could try it and hear if they have a problem with this?
-
Also, a lot of artwork doesn't want to show up. I often do extensive tagging of my files, either via MusicBrainz Picard or MP3-tag, and I always both embed and add a cover.jpg or folder.jpg in the album folder. Despite this, it often doesn't show up. Could this have to do with differences in jpg-compression codecs or certain resolutions? Maybe this is just a general rockbox problem.
Anyhow, no stress in looking this all up, just wanted to report.
-
Could this have to do with differences in jpg-compression codecs or certain resolutions?
Most of the time, when a cover art doesn't show up in my collection, it is embeded as progressive Jpeg, which is not supported by Rockbox. In that case I extract the image from the MP3-file with Mp3tag (a great ID3 tagger for Windows), load the image into irfanView (a image viewer for windows), save it (non progressive), and re-embed it into the MP3 with Mp3tag.
Most of my cover art is 700x700 pixels which is on the large side for Rockbox, but most of the time they do display with no problem.
-
That makes sense, Oscar. Thanks for the info! I might just use a program as RIOT, and convert the existing file. There is also this nice little tool called Album Art Downloader which scrubs relevant websites for album artwork, and then I can just convert it.
-
I tried out Rockbox (for the second time) on my Q1 last night. When I try to restore the OF, I get the Shanling splash screen and then a message "Update Failed". I also tried restoring the backed up shanling bootloader but that leaves it completely inoperative (I can't even do the PREV/NEXT Power button reset). I have to reinstall the rockbox bootloader just to get it to attempt the reset.
As I said, this is the second time I've tried out rockbox and my reset the first time worked flawlessly so I'm not sure what's different.
If anyone has any ideas on what I could try to restore the original firmware, I would appreciate it.
Thanks,
Kevin
-
There should not be more than to extract the Shanling firmware to the sd card and reboot to let it update.
Or shut down the player. Hold the 'previous' button while turning it on again to boot the Shanling firmware and select 'System update' from the 'System' menu.
-
I tried out Rockbox (for the second time) on my Q1 last night. When I try to restore the OF, I get the Shanling splash screen and then a message "Update Failed". I also tried restoring the backed up shanling bootloader but that leaves it completely inoperative (I can't even do the PREV/NEXT Power button reset). I have to reinstall the rockbox bootloader just to get it to attempt the reset.
As I said, this is the second time I've tried out rockbox and my reset the first time worked flawlessly so I'm not sure what's different.
If anyone has any ideas on what I could try to restore the original firmware, I would appreciate it.
Thanks,
Kevin
It might have something to do with installing different Shanling firmware versions in between flashing the RB bootloader. I'm guessing when you originally installed rockbox and took a bootloader backup you had one firmware version, and now you're trying to install a different version? Maybe you could try installing the version you had when you first installed RB and see if that works.
The bootloader backup on the Q1 isn't a complete backup of the Q1's original bootloader. What might be happening is you're restoring an old version of the bootloader, but you have a newer flashed version, and the result is an unusable mess. In other words your bootloader backup is only usable with the firmware version that you had when you made the backup.
That's an annoying problem I overlooked. Ah well. I'll have to make a note of it on the wiki, as it's not something I can fix quickly.
-
It might have something to do with installing different Shanling firmware versions in between flashing the RB bootloader. I'm guessing when you originally installed rockbox and took a bootloader backup you had one firmware version, and now you're trying to install a different version? Maybe you could try installing the version you had when you first installed RB and see if that works.
The bootloader backup on the Q1 isn't a complete backup of the Q1's original bootloader. What might be happening is you're restoring an old version of the bootloader, but you have a newer flashed version, and the result is an unusable mess. In other words your bootloader backup is only usable with the firmware version that you had when you made the backup.
That's an annoying problem I overlooked. Ah well. I'll have to make a note of it on the wiki, as it's not something I can fix quickly.
I believe I've always been on 2.2. I tried other versions of the firmware 1.2 and 1.4 also. Maybe, in the end, it's a blessing. After being forced to live with rockbox I'm starting to appreciate it more. In fact, the only thing that made me give up on rockbox was the invisible 3x3 touchscreen grid. I can never seem to remember where to touch. The more I use it, the more I'll get used to it I guess.
Thanks for taking the time to respond :)
-
One other nugget of information. If I do the PREV+NEXT+POWER reset without the sd card inserted, I get exactly the same result. Splash screen followed by Update Failed.
-
In fact, the only thing that made me give up on rockbox was the invisible 3x3 touchscreen grid. I can never seem to remember where to touch. The more I use it, the more I'll get used to it I guess.
Turn on 'absolute point' mode in the settings so you can use it like a normal touchscreen.
-
One other nugget of information. If I do the PREV+NEXT+POWER reset without the sd card inserted, I get exactly the same result. Splash screen followed by Update Failed.
So that does not mean anything? You can only update with a firmware file on the sd card.
Makes me suspect you might have done something wrong putting the firmware on the sd card.
Anyway, Rockbox is 'multiboot', you can still boot the Shanling firmware by holding PREV while turning on the device. So you can have it both ways.
-
So that does not mean anything? You can only update with a firmware file on the sd card.
Makes me suspect you might have done something wrong putting the firmware on the sd card.
Anyway, Rockbox is 'multiboot', you can still boot the Shanling firmware by holding PREV while turning on the device. So you can have it both ways.
I mentioned it because it acts the same way whether a card is inserted or not. Which leads me to believe the problem is occurring before it even attempts to read the card.
Multiboot doesn't work either. I get the Shanling splash screen and then it boots into rockbox.
Are the various BUTTON+POWER combinations a rockbox thing or are they built into the Q1?
FYI here's the splash screen: https://photos.app.goo.gl/6xjck1yjtAwJNVAi9 (https://photos.app.goo.gl/6xjck1yjtAwJNVAi9)
and here's the update failed: https://photos.app.goo.gl/DbSEm6LDuVMa1yhS6 (https://photos.app.goo.gl/DbSEm6LDuVMa1yhS6)
-
They are part of the Rockbox bootloader.
Weird that booting into the Shanling firmware does not work.
I wonder if a backup from another 2.2 device would help you.
-
First of all, thanks for investing time and effort for the Q1 Port to all involved! I got the player as a bluetooth/sd card alternative to my stash of several Sandisk Sansa Clip Zip's. I'm eager to try it, but the main reason I'd switch to using the Q1 would be being able to use it with BT earbuds. Taking into consideration what Amachronic said in the first post (quoted below), did I understand correctly that currently BT connectivity to headphones isn't supported and is this still the case?
Thanks!
...The main downside with a native port is that wifi/bluetooth will probably never work in Rockbox...
-
.. did I understand correctly that currently BT connectivity to headphones isn't supported and is this still the case?
Yes, no BT at all.
-
A question regarding themes: when i want to save an eq preset, for example, the page where i can name the preset is just small black text on a white background, and uses the 3x3 touch-mode. Is it possible to make this page more usable with a theme, or is it just a limitation of the touch interface?
-
They are part of the Rockbox bootloader.
Weird that booting into the Shanling firmware does not work.
I wonder if a backup from another 2.2 device would help you.
Does anyone have a backup from a 2.2 device that they could send me?
-
Does anyone have a backup from a 2.2 device that they could send me?
I've got one, i'll send you a wetransfer link!
-
I'll send it tonight, it's on my other laptop :)
-
I'll send it tonight, it's on my other laptop :)
That's great. Thank you very much!
-
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.
-
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 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 (https://www.rockbox.org/wiki/VKeyboardDesignProposal) 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.
-
@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.
-
lol my answer is within the quote!
-
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 - 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.
-
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.
-
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
-
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!
-
[...] 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.
-
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.
-
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?
-
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.
-
[...] 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.
Yeah, not sure what happened. The sequence of events was as follows:
1. Used Q1 for 6 months with stock firmware
2. Tried rockbox for a month
3. Decided to go back to stock firmware, restored backed up bootloader
4. Used Q1 for 2 months
5. Decided to try rockbox again, backed up bootloader
6. Decided to switch back, restore failed.
-
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.
I understand and read all the warnings when initially installing but it would still be good if there was an independent way to return to stock.
But given that the Shanling firmware apparently does not touch/contain the bootloader, there is no such thing as a '2.2' bootloader? Anyone with an original Q1 and the latest tools could donate a bootloader for the greater good.
Having said that, I am very happy with Rockbox on my Q1 and with the option to hold a button to boot the OF, I have best of both worlds.
-
I've uploaded my Q1 and M3K bootloader backups to the wiki. They're found on the JztoolInstall page in the "Removing Rockbox" section.
-
Here's a new bootloader release for the Q1, version b4e7c60c6d-221029. Download it here (https://download.rockbox.org/bootloader/shanling/q1/20221029-b4e7c60c6d/bootloader.q1) or from the wiki.
This version fixes a few bugs:
The old Rockbox bootloader interrupted the original firmware's update process, preventing OF updates from being installed. This is fixed in the new version, and you can now update the Q1's firmware from the Shanling player app. There are a couple things to be aware of: Shanling's updates don't include the bootloader, so the Rockbox bootloader will remain installed after an OF update. If you want to remove Rockbox you need to restore from a bootloader backup. Second, after the update finishes you will be rebooted into Rockbox. The update has succeeded at this point, but some leftover files will remain on the SD card; you can either remove them yourself or reboot to the Shanling app, which should clean up the files automatically.
The bootloader backup and restore functionality will now display an error message if it looks like the backup is corrupted. The level of protection is minimal but it's better than the old bootloader, which had no such safety checks.
The Linux loader had a bug which added garbage to the end of the kernel command line. This has been fixed.
-
Hi,
I have lost bootloader backup for my device. Will the one in wiki work?
I have FW Version V2.1
-
Hi,
I have lost bootloader backup for my device. Will the one in wiki work?
I have FW Version V2.1
Yes, it should be fine. If it doesn't work let me know.
-
All fine. Updated OF and RB.
Thanks!
-
Hi
I don't know if this is the right place to report this but Advanced Key Lock is not working since a couple of months, it use to work before but now any hardware button isn't working after lock even with properly exemption configured.
-
Hi
I don't know if this is the right place to report this but Advanced Key Lock is not working since a couple of months, it use to work before but now any hardware button isn't working after lock even with properly exemption configured.
There was a change submitted some time ago which broke quite a few settings for a while before it got caught, this might be related to that. Assuming you're on the latest development/daily build, If you haven't tried it already, you might want to try starting from a fresh config file (try moving .rockbox/config.cfg to .rockbox/backup.cfg), configure it through the menu again. See if it works after that.
-
Hi
I don't know if this is the right place to report this but Advanced Key Lock is not working since a couple of months, it use to work before but now any hardware button isn't working after lock even with properly exemption configured.
After getting annoyed for the n'th time I finally got around to bisecting the bug. It's fixed now in the latest build.
-
Hi everyone! Thanks for this phenomenal port that I've been using happily for about six month until yesterday ... something broke. Without any further changes (not attached to a new computer, no charging, no manipulations to sdcard etc.), the Shanling Q1 refuses to start. It does show the bootloader and boots into OF. When asked to boot Rockbox, it shows the logo, very briefly shows the text scanning... or similar and shows the logo again. It stays in this state for about 15 seconds or so, dims the screen, later turns the screen off, finally shuts down after a few minutes. I tried:
- Check if the sdcard has bad blocks. Yes, it does (unsurprisingly), so I formatted it with mkfs.vfat -c in order to skip over bad blocks. No effect.
- Tried another sdcard. No effect.
- Tried another sdcard. No effect.
- Tried to reflash the bootloader. No effect.
- Tried to flash the original bootloader. Software refused, claiming it's not a tar archive (which is true).
- Update: Took the wrong file :-( it lets me flash the original bootloader (which works as expected) and flash Rockbox' bootloader (which boots OF properly and leaves Rockbox stuck).
Do you have any hints what else to try? Do you need any more information?
-
Hi, I'm wondering if anyone has an og bootloader backup? One I got was corrupt, weirdly enough.
-
Hi, I'm wondering if anyone has an og bootloader backup? One I got was corrupt, weirdly enough.
Do you mean the original bootloader? I attach the bootloader I have as a backup of my Q1 which runs the firmware V2.2 (see the known issues here: https://www.rockbox.org/wiki/ShanlingQ1Port.html)