Author
Topic: [Solved] Shortcut to set volume (Read 865 times)

I own a nice player I was stupid enough to immerse in water. Stupid me.

I disassembled it, dried it, reassembled it, revived it. Except for the volume up button which I happen to destroy in the reassembling process. Supid stupid me.

But, lucky me, my device is RockBoxed. Through the menu, I can go to [Settings // Sound settings // Volume] and pick the volume I want. The RockBox firmware is terrific, and it's definitely a device-saver !!! I can't thank you enough, guys !!!!

Now, in order to optimize my use of my device from the pocket, I have set useful shortcuts. I would like to have a shortcut setting the volume to a given level. Hence, in my [shortcuts.txt] file, I added the following lines :

I have tried various things, with very mixed result, none being what I expect.

I can - make a very convenient cfg file, perfect ;- test it buy loading it, perfect ;- create the shortcut by summoning the context menu while browsing the .cfg files, perfect.

Then when I summon the shortcut, my device freezes.

Same result with your items, copied and pasted.

If I make something lighter, by writing the code lines in the .cfg file, and the shortcuts.txt file with Notepad++ for example, sometimes the shortcut doesn't finds the .cfg file, sometimes the shortcut doesn't shows in the shortcuts list.

The best I can do is having a shortcut pointing to the volume settings, avoiding me to venture in the menus :[shortcut]type: settingdata: volume -6name: Volume

Your advice, johnb, and your files, proved me the problem is not in RockBox, nor in my works. Elsewhere, then.

I may now confess I happen to be a kind of RockBox dissident. I mean : my device is a XDuoo X3, and the RockBox Firmware I use is an unofficial port made out of the RB Legacy. I easily understand the firmware I use may have some bugs. Actually, there are some that many XDuoo X3 users constantly mess with. My problem may come for the very RockBox/device combination I use.

Anyhow, a defective RockBox is still a wonderful improvment over most official firmwares. And, as my last Clip Zip lost his jack, I had to find a modern device playing RockBox. Despite all the bugs, I'm mostly satisfied with the XDuoo.

I am looking forward for the official port to this device that was announced. Meaningwhile, my shortcut will be enough.

I owned an Xduoo X3 for two months and the same approach worked (with the latest rockbox build from xvortex).The copy I pasted above was from a clip+ though. You might have to tweak the path in the shortcut.txt file due to the 2 sdcards.

I won't give up. Although the shortcut to the volume setting does the trick, I still would be happy to have a shortcut to a specific volume level.

The path to the .cfg file in the shortcuts.txt may be an issue :- if I code it by hand, I never manage to reach the .cfg file by using the shortcut. - if I let rockbox modify the shortcuts.txt, it makes a shortcut to the very .cfg file I point to, and I can use the shortcut. However, two possibilities.- - I can use the .cfg file sample you provided. Or I can use my main configuration file, with the volume setting modified accordingly to my wishes. Then using the shortcut freezes the XDuoo. And the modification of the shortcuts.txt empties the values of the other working shortcuts (activate sleep mode for 30 mins, or deactivate sleep mode) I have. - - I can use a .cfg file with only the volume setting, by writing it, by using your .cfg file sample and removing the unneeded lines. The result is the same, it give me access to the sound settings (all the sounds settings, not the volume settings).

Once upon a time, I had another trouble with the shortcuts.txt, for RockBox seemed to prefer linux type textfile (lines ending with <LF>) to Windows type textfiles (lines ending with <CR><LF>). But the problem is solved in RockBox code since 2012, and changing the type of the line ending seems to have no effect on my issue.

I don't give up. For the pleasure of fine tuning, I'm looking for a complete solution. And I would be glad you would provide a working one. But for the use of my device, I consider myself having a working solution.