Rockbox as an Application (Android, WebOS etc.)

[lefko]

Hi, thanks for the response.  The version I am using is r29590M-110316.  Not 100% sure how to tell if that is old or not.

While I have taken the SDcard out to add files/playlists what I am seeing appears not to be related to that, so I guess it must be the locking issue?

The lock I am referring to is the phone screen lock as addressed in the previous comment  I think it would be helpful to have it automatically lock. What I mean by the feature "lock the playback settings" means that the playback settings on the playback screen will be unaffected by the touch screen, and you would have to go through the menu system to change them.  Right now with the Cabbie(?) screen I can change them in the playback settings menu, but also on the touchscreen itself while it's playing.  Maybe what I am saying is just give me the option to turn the touch screen portion off for the playback screen

[saratoga]

Hi, thanks for the response.  The version I am using is r29590M-110316.  Not 100% sure how to tell if that is old or not.

11-03-16, so your build is about 4 months old.

[lefko]

THeres really no way to tell from this page http://www.rockbox.org/wiki/AndroidPort but it appears to be the latest built version.  Is there someplace else I should be looking, or did the ambiguous statement above mean it was the latest?

[JdGordon]

THeres really no way to tell from this page http://www.rockbox.org/wiki/AndroidPort but it appears to be the latest built version.  Is there someplace else I should be looking, or did the ambiguous statement above mean it was the latest?

Those links are old, rasher is doing daily builds so I've fixed the wiki to point to them.

[[Saint]]

I could achieve this effect in the theme I am working on now for the Android port.

It wouldn't be a setting, but rather a "soft lock" in the form of a screen icon that toggled all other touch areas conditionally leaving the screen active and the theme displayed (unlike the devices hardware key lock or idle time-out key lock) but still have the screen "locked" (to an extent). Just tap (or I think I would make this a "long hold" action if possible to limit accidentally un-/locking the screen) the icon to un-/lock the screen.

The thing is...its a lot of work, and this theme has had a massive case of feature creep since its humble beginnings, three complete re-writes and approximately 800 iterations, and I'm still working on it...
For me to consider another (almost complete) re-write at this point to accommodate yet another feature I would need to know that more than one person will find it worthwhile, or that others don't think its a bad idea because it would be annoying if pressed accidentally...and so on.

So, basically...is this something we'd want for the RaaA theme?



[St.]

[JdGordon]

Adding a softlock region would be dead simple and I'm happy to add that code, making it be able to auto-lock isnt though.

[[Saint]]

Adding a softlock region would be dead simple and I'm happy to add that code, making it be able to auto-lock isnt though.

I don't think it should...to be honest. I think soft-locking the screen should be a conscious decision, we don't need another setting for this (presumably if it applied automatically you would want to configure the timeout) cluttering up the menus (although I presume it would go in the touchscreen settings menu which isn't very crowded at all...but anyway).



[St.]

[JdGordon]

we agree... i was saying im not going to implement auto-locking

[lefko]

I have been using the daily build for a few days now and it seems really good to me.  I have not had a problem with playback yet anyway.  Also have the fades working on the device, so I am happy.  I'm going to play around with loading fonts and themes today

[notlistening]

Did you manage to have any joy with the themes and fonts. I have loaded on the fullzip version and have found that I can not access the fonts menu item. I also can not access the while playing screen in the theme menu. This was build from a fresh update from SVN tonight.

[[Saint]]

Try loading one of Rasher's unmodified daily builds to verify you didn't do something weird.

I seem to recall that "make fullzip" doesn't actually work with the Android port, but I'm not in a position to check this for some hours now, I'll update this post if I get a chance to test this before you reply.

If you do find that Rasher's builds work for you (note that you'll need to uninstall your build as the signing keys won't match so it won't be treated as an update) then try doing just "make zip" as opposed to "make fullzip".

If that doesn't work, cd to the root of your source checkout and do "svn stat" to see what's messed up in your checkout.



[St.]

[notlistening]

No luck, I have done all the above barr using one of rashers builds as they are going to be the wrong size for my phone and at the moment small font or not I am using it everyday.

T

[lefko]

No luck with the themes for me either

[[Saint]]

No luck, I have done all the above barr using one of rashers builds as they are going to be the wrong size for my phone and at the moment small font or not I am using it everyday.

T

Did you actually look?

If I remember correctly from the recent conversation between yourself and I on IRC you have a 800x480 landscape device?
If so here is the link to a binary for your device from Rasher's page

No luck with the themes for me either

When you say this...what exactly do you mean?
What have you tried?
What haven't you tried?

Are you aware that RaaA only builds with one theme *if* and *only* if your device is one of these resolutions:

240x320 - Portrait
340x480 - Portrait
480x800 - Portrait
800x480 - Landscape

If you do not have one of these resolutions you will only have the choice of the fallback theme (its not even a choice really ) which you will recognise by the tiny, tiny font, incredibly basic .wps, and complete lack of images.

You may use a theme that is physically smaller than your targets resolution, but not larger. If a smaller theme is used it will be aligned to the top left of the screen and the remaining screen space will be ignored and display as a black border.

If you do have a target with a resolution listed above, then it will ship with one theme and one theme only which is the current default theme "cabbiev2".
If you have found or created a theme for your device, then it needs to be placed on the uSD card under a directory named "rockbox" and must retain the original directory structure.
Fonts are to be placed in:

/mnt/sdcard/rockbox/fonts/

Themes are to be placed in:

/mnt/sdcard/rockbox/themes/

.WPS and .SBS files in:

/mnt/sdcard/rockbox/wps/

Icons in:

mnt/sdcard/rockbox/icons/

And so on and so forth...


The Rockbox Themesite can offer themes which you can use with your device (literally any of them will work on your handset as long as the syntax is valid and the dimensions are either smaller than or the same size as your devices resolution), but if they are not touch-screen enabled you will not be able to use them properly unless your handset/device has a physical D-Pad at the very least (even then you may find yourself able to get into situations you are not able to get out of).

I will be happy to help you debug this issue, please inform me what you have/have not tried and we'll go from there.



[St.]

[lefko]

OK, I was putting it in ./rockbox/.rockbox instead of the top directory, so fonts and themes are working now.  However most of the themes I chose seem to have the now playing screen stop at 160 or 240 width instead of full width.   Also the default font for a lot of the themes were very very small such that I could not see the menu.  Luckily I have the laptop dock which helped me get back.  I believe I looked for the 480x800 themes, but I will check again.  Thanks for the help on that. 

Went back to the cabbiev2 theme, but with a bigger font
Post Merge: August 02, 2011, 10:36:13 AMI had the settings issue come up again yesterday.  The shuffle stopped working.  The playback screen indicated that the shuffle was set.  The next song was the next song in the folder. 

I've run it about 5-6  hours real time over the ~4 days since I installed the new firmware.  I'm not sure how many times I have started and stopped it, but I have changed playlists a couple of times.  I have several playlists in multiple directories on the external SD.  IEach directory has a 6-9 folders each folder has a live recording.  The immediate directory above has the .m3u playlist.  I used foobar2000 to create the .m3u. 

Since the last time it was working I have done nothing with the phone except lock the input.  In fact I had run it about 2 hours before in shuffle and the rockbox screen was still up and on top.  Since I installed the firmware I had taken the external SD card out but that was probably within the first 1/2 hour of the 5-6 hours of playtime.  I had reset the phone within 24 hours before this happened.

I fixed it by cycling the shuffle indicator on the playback screen.