Rockbox as an Application (Android, WebOS etc.)

[[Saint]]

You were using a truly ancient build from kugel with a patch that isn't in svn, and almost certainly never will be, to increase the list item height.

So its no surprise it didn't look as you expected when you installed an svn head version.

I've had multiple testers for this theme port, and I can honestly say that with the 48pt font I have never had a complaint about touchscreen usability in the lists.

I /could/ of course increase the font size, but I think (and testing so far has shown) that 48pt is a good balance between list height, total items displayed in the list (you don't want the menus to be needlessly sparse when scrolling long lists), and usability.

I continue to update these theme ports as I develop and work on new ideas...and nothing is set in stone.

I can tell you, though, that the only way (for now) you'll get the lists the way you wanted them is to revert to the build you were using if it still is hosted anywhere. That patch isn't going to get into svn, I'm ~99% sure of that.
There are sane ways to alter the list item height with the skin engine on a per screen basis (committed recently) that I would find to be an acceptable solution as opposed to forcing gigantic lists in all cases where a list is drawn.

This would allow for an (optional(depending on how creative I'm feeling)) way to expand only lists that need it (menus for instance), and not the lists you don't want to have vast amounts of blank space (long scrolling lists).



[Saint]

[a_b_c_d]

I've had multiple testers for this theme port, and I can honestly say that with the 48pt font I have never had a complaint about touchscreen usability in the lists.

I /could/ of course increase the font size, but I think (and testing so far has shown) that 48pt is a good balance between list height, total items displayed in the list (you don't want the menus to be needlessly sparse when scrolling long lists), and usability.

I agree it's a good compromise between touchscreen usability and handling long lists.
But for those without sensitive fingers: Would it be time-consuming to add an option that provides bigger fonts (at the moment I can switch between 36-cabbiev2-[bold], 36-cabbiev2-[regular] and 48-cabbiev2-[regular])?

I can tell you, though, that the only way (for now) you'll get the lists the way you wanted them is to revert to the build you were using if it still is hosted anywhere.

I've got the ".apk"-file still on my phone, but I think I will use the newest version with 48-cabbiev2-[regular] anyway, although I'd prefer menu items that are a bit higher.

There are sane ways to alter the list item height with the skin engine on a per screen basis (committed recently) that I would find to be an acceptable solution as opposed to forcing gigantic lists in all cases where a list is drawn.

This would allow for an (optional(depending on how creative I'm feeling)) way to expand only lists that need it (menus for instance), and not the lists you don't want to have vast amounts of blank space (long scrolling lists).

*sign*


And thanks for the fast support.

[Falco98]

Could anyone point me to a build they think would be optimal for use on the Thunderbolt?  I was running a decent one ago on my old Eris, a while ago, but honestly I forget whether I found the build here or on another forum.  A brief browse of the last few pages has left me generally unsure which one I should try to use :-P

[[Saint]]

Could anyone point me to a build they think would be optimal for use on the Thunderbolt?  I was running a decent one ago on my old Eris, a while ago, but honestly I forget whether I found the build here or on another forum.  A brief browse of the last few pages has left me generally unsure which one I should try to use :-P

RaaA doesn't care about anything except the screen dimensions and the Android version.
So, "optimal" in this instance just means:

"an Android OS greater than 1.6 and a RaaA .apk built for a resolution the same as my device or smaller"

That's all.

The build doesn't need to be the exact screen dimensions, but it cannot be larger than the screen dimensions in either width or height. Builds for resolutions smaller than the devices LCD resolution will be aligned to the top left corner and the rest of the screen will remain unused.

As for availability, the *only* RaaA .apk I recommend installing is:
rasher's unmodified daily builds
As these builds contain no third party patches that may or may not be applied/built correctly, and they reflect the current svn state of RaaA.

Just remember that these builds are *unsupported!*, so don't lodge bugs against them, and they are not officially sanctioned by the Rockbox project. They are provided by rasher so that people may test the current state of RaaA.
Remember, RaaA is still officially "Unusable" as stated on the main page.


[Saint]

[Falco98]

As for availability, the *only* RaaA .apk I recommend installing is:
rasher's unmodified daily builds
As these builds contain no third party patches that may or may not be applied/built correctly, and they reflect the current svn state of RaaA.

Thanks, this is basically what I was looking for   As I said, I'd used it on my eris (sloooooow) and it worked okay there, except for the inability to move an app to the SD card and the eris' built-in memory became an extreme limiter with only a handful of apps installed.  By this point I didn't even remember where I got the build I had on there, but this was probably it (but presumably updated some, by now).

[TexasRockbox]

Don't know if this link will help with RaaA

CRC Canada has an FM/RDS application that works (both FM and RDS) on the newly released Samsung Galaxy Player 5.0 (USA Version) and other Samsung devices.

http://mmbtools.crc.ca/content/view/52/77/

CRC does provide downloadable libraries.

[R_E_K]

Hello,

absolutely great, thank you for this port!

I had different iRivers, Sansas and since two years iPhones (3GS and 4). I've allways missed rockbox. Now I've bought a SGS II for using it with rockbox - this is my killer application for Android ;-)

Is there any plan to support iPhone-headsets (Denon AHC 560 R in my case)?

Best regards,
Ralf

[paulheu]

Hi guys.. me's back.. After some thought on my new phone it is..... A Nokia N9

Honestly it's an awsome phone.. but could do with some RockBox TLC..

Now before I get my head snapped off by the autoresponder I am not expecting anyone to jump on it, just if there is anyone doing any work on a meego version..

tx, Paul

[froce]

Sorry for my poor English.
There is a bug in Android port.
When bluetooth headphone connect,rockbox can't playback any song until the phone reboot.
My phone is SE Xperia Neo.

Anyone know about the bug?...thanks.

[Liamness]

noob says hi. Just installed rasher's latest build on my phone (cheapy San Fran II) and I'm very impressed! I'm familiar with rockbox, having used it on sandisk devices, but I was under the impression that the rockbox version wasn't very far along. It is listed as 'unusable' on the main page after all! However it seems stable enough to use as my main music player, and all the features that made me love rockbox in the first place seem to have made it through. Few questions though;

How can I restrict the database so it builds from just one folder? All my music is in one place on the sd card, but rockbox scans the whole phone. Things like podcasts and ringtones are mixed in with everything else. Not a big deal though obviously.

I noticed there is a patch for a widget. Thusly I would like to try and build the apk from source myself, as my understanding is that this is the only way to add such a patch. I don't really know what I'm doing though, I can't even work out where to find the source. I looked at svn.rockbox.org and just got confused. The phone is rooted and I have used adb with it, so at least there's that.

[paulheu]

http://www.rockbox.org/wiki/DocsIndex#For_Developers

[kinnexsus]

Rockbox as a launcher

What if we designed a rockbox based GUI launched for android, avaliable on the android market,
To cut out hassle and hacks of it all, bringing in the phone functions like call and text, email, internet browsing...
Making a launcher is relativaly easy-
or just a theme for go launcher ADW.launcher





What do you Think?

[[Saint]]

Rockbox as a launcher

What if we designed a rockbox based GUI launched for android, avaliable on the android market,
To cut out hassle and hacks of it all, bringing in the phone functions like call and text, email, internet browsing...
Making a launcher is relativaly easy-
or just a theme for go launcher ADW.launcher





What do you Think?

I'm curious, as I'm sure others are as well, what "hassle and hacks" it is that you're talking about...
I'm perhaps more curious about how Rockbox as a Launcher would negate any of said hassles and/or hacks.

Perhaps I'm not thinking laterally enough?

I'll leave my comments about the idea itself until I'm clear on the issues that its intended to negate.


[Saint]

[meaninglessvanity]

I'm using Rockbox for Android (LG Optimus V) and it works mostly.  I'm having occasional cut outs but it generally starts playing again after a few seconds.  I can deal with that.

The thing that's bothering me is I always used bookmark on stop on my previous Sansas, so that when I turned off the device it would save a bookmark in my book so I could start again from the right spot.  What I've noticed is that the Android app doesn't do that when I pull the headphone cable out.  Do I have something set up wrong, or is that just not in the code?

Thanks!

[kugel.]

Pulling the headphone only pauses, it does not stop (unrelated to RaaA), therefore no bookmark is created. You need to stop manually (long press on the play/pause icon in the wps).