Rockbox as an Application (Android, WebOS etc.)

[AlexP]

Guys, this is a thread for development, not support or general comments.  When the port is further advanced, support questions will belong in the main forums, but not yet.  Please stick to development only.  I'll go through and prune this topic soon.

[Spoonman]

hey guys, just found out that you are porting rockbox to android and have instantly seen that there are some major problems...

this is why i strongly suggest the devs of this port to join xda developers, post about the port and what rockbox is in

Android Software Development Section http://forum.xda-developers.com/forumdisplay.php?f=524

and get helped by the most vibrant and qualified dev comunity that exists for android devices.

Nice Greets Spoonman

[Llorean]

Rockbox isn't really an evangelical project. We don't go out to various places and say "you guys should really help us" or anything. We generally depend on interested developers finding us and choosing to contribute (or not) as they see fit.

That being said, if there's a question that needs the resources at XDA I'm sure the appropriate developers will go there and search or ask, but it's not the habit of this project to encourage development discussion off-site, as it makes it much harder for new developers to see what's going on if discussion is split.

Were there any specific Android problems you felt the XDA developers were likely to be able to help with, or were you just generally advertising the site?

[JdGordon]

http://jdgordon.info/rockbox/rockbox.apk needs testing... it's just about svn and a patch to make rockbox figure out the lcd size on load instead of having to need one apk for each phone.

so test it out and let me know any issues which weren't happening before.

That apk requires a sdcard because it extracts a bunch of files there, you probably want to clear the data in the android app settings for rockbox so you can reclaim about 15MB

[slade]

Hey Everybody I cross compiled LibSDL for my YP-R0 and it upgraded fine I also cross compiled rockbox as Application with lcd size 240*320. works fine under my linux but I didn't figure out 2 things:
1. how can I make fullinstall besides my regular linux path but instead in my rootfs of the player? where can I set the option where fullinstall goes too.
2.

Code: [Select]

/mnt/media0/ypr0/rockbox: line 1: cannot create
 @@0ú!@8 @$@@@@@ø
ø
88@8@

@@Έ: Read-only file system
/mnt/media0/ypr0/rockbox: line 1: ELF

: not found
/mnt/media0/ypr0/rockbox: line 2: Έ: not found
/mnt/media0/ypr0/rockbox: line 3:
èï: not found
/mnt/media0/ypr0/rockbox: line 4: èïjèïjt˜: not found
/mnt/media0/ypr0/rockbox: line 5: syntax error: word unexpected (expecting ")")this error I get on the player, my rootfs are almost completly read only using cramfs only /tmp folder has very limited space for rw. Is there a way I can redirect all the calls to NAND 8GB flash only?
I couldn't figure out where it is set.
Update
Ok I got around read/write erros now having the follwing error left:

Code: [Select]

/mnt/media0/yp-r0/rockbox: line 1: syntax error: word unexpected (expecting ")")
What could be the reason?

[JdGordon]

have a look at firmware/common/rbpaths.c get_user_file_path() (or whatever its called) which translates "/.rockbox/" to a useable path.

There is a patch on flyspray to get rid of this and do it transparently in the calls to open() but it isnt finished

[slade]

I have a short question. I think everything is compiled right (no errors on either rockbox nor libsdl)
so when I start the application on my x86 build on my linux its fine and runs ok but on my arm-eabi build on the player the only error it gives me is "Killed". I don't know exactly what happens. may be you guys can give me a hint when this message comes. I can't imagine it being killed ?!

I now get a seqmentation fault
Is there some way to be able to get a dump ? Its only telling me segmentation fault
Thanks you

[Bkd11]

http://jdgordon.info/rockbox/rockbox.apk needs testing... it's just about svn and a patch to make rockbox figure out the lcd size on load instead of having to need one apk for each phone.

so test it out and let me know any issues which weren't happening before.

Working fine on Moto Droid 1. Screen size for the menus is perfect. Just had to manually select cabbiev2.480x800x16 from settings/wps for the wps to display properly.

[burkejavier]

The UI is much improved on my Viewsonic GTab, but Vorbis files are just static.

[saratoga]

The UI is much improved on my Viewsonic GTab, but Vorbis files are just static.

Do any other formats not play?

Theres test files here if you need them:

http://download.rockbox.org/test_files/

[kugel.]

I have a short question. I think everything is compiled right (no errors on either rockbox nor libsdl)
so when I start the application on my x86 build on my linux its fine and runs ok but on my arm-eabi build on the player the only error it gives me is "Killed". I don't know exactly what happens. may be you guys can give me a hint when this message comes. I can't imagine it being killed ?!

I now get a seqmentation fault
Is there some way to be able to get a dump ? Its only telling me segmentation fault
Thanks you

I suspect you're out of memory. The first "Killed" came from the Linux OOM killer. It kills before even starting if the static allocation of the problems are too much.
That you're now getting a segfault can mean that there's a malloc() call failing.

[slade]

I suspect you're out of memory. The first "Killed" came from the Linux OOM killer. It kills before even starting if the static allocation of the problems are too much.
That you're now getting a segfault can mean that there's a malloc() call failing.

I was able to reproduce segmentation fault on my linux pc with the following:

Code: [Select]

export SDL_VIDEODRIVER=anythingbutx11giving my rockbox app on linux the same segmentation fault. I think my main problem is as I tried the numerous sdl test programs I always get the following error:

Code: [Select]

Couldn't initialize SDL: No available video deviceI do have /dev/fb0 to /dev/fb2 in one of the upgrade Firmware scripts the following is being done:

Code: [Select]

echo U:240x400p-60 > /sys/class/graphics/fb0/mode
echo U:240x400p-60 > /sys/class/graphics/fb2/mode
echo 0 > /sys/class/graphics/fb0/blank
echo 0 > /sys/class/graphics/fb2/blank

if [ -e $IMAGE_FILE ]
then
    cat $IMAGE_FILE > /dev/fb0
    cat $IMAGE_FILE > /dev/fb2
fi
if I try the same it wont work. Also I tried export fbdev, fbcon and directfb but I always get the no video device error. I hope somebody could give me a hint on what to look for. libsdl should be compiled right but I honestly don't get why I can't use the framebuffer device for SDL.

[scott_goff]

Hi all!

1st: I've been using rockbox for years, first on an old Archos Recorder, then on a 5th Gen iPod. So, I was jazzed to find that there was a port in active development for Android, as I own an HTC Aria. I have been trying to get myself comfortable with my phone as my primary media player, so I can cut down on the number of devices I carry with me everyday.

Anyhow, I've tested the newest auto-display sensing build posted on the Android port page, and it works great, generally. Gives me consistent ability to play WMA files (which I haven't had any luck with at all in the stock Android Music Player, or any 3rd party apps) and mp3s, though I haven't tested any other file types.

The only trouble I have had with it was when manually killing the app during testing; upon reopening Rockbox, my screensize wasn't detected properly (super small text) and my touchscreen settings (grid) weren't recognized; it defaulted to absolute.

Finally, while I know I'm not a developer, I do have some suggestions for future development on this platform. It would be nice to be able to specify different touchscreen modes for the WPS and the file browser, etc. screens, i.e. absolute during WPS, and grid for everything else.

Also, it would be awesome if there were built in support for playback control via headsets with remotes. I know the implementation of remotes on headsets is a bit hit and miss on Android, even with the stock player (quite a few forum post around the net on the topic). Personally, I've tried three different headsets so far, and all results with the stock music player have been different. With Skullcandy Ink'd Mic'd, the remote worked for play/pause/next/prev and answering/denying calls while playing music. With a Sony EX38iP headset (three button remote) the middle button only worked for the previous mentioned functions, and the mic wouldn't work at all (not part of the scope of Rockbox, probably, but thought I'd mention). And, with a VModa Faze headset (one button), mic works fine, but the remote button doesn't work out of the box at all with the stock player. It does, however, work with the addition of a 3rd party app called Droid Shuffle (but with or without Droid Shuffle running, Rockbox doesn't recognize remote input; only tested this with the vmoda headset, though I expect results would be similar with other headset remotes). So, I guess long story short, it would be good if similar functionality to the Droid Shuffle app could be built into Rockbox.

Thanks to the primary dev(s) for their work on this port! I look forward to testing future versions 

[kugel.]

if I try the same it wont work. Also I tried export fbdev, fbcon and directfb but I always get the no video device error. I hope somebody could give me a hint on what to look for. libsdl should be compiled right but I honestly don't get why I can't use the framebuffer device for SDL.

Perhaps a problem with permissions (tried with root access?)? Just a guess though.

[rosco_pc]

http://jdgordon.info/rockbox/rockbox.apk needs testing... it's just about svn and a patch to make rockbox figure out the lcd size on load instead of having to need one apk for each phone.

I recently got an Malata zPad (same as a Viewsonic gPad) and tried this out. It starts and uses a properly sized font (although the display seem to be upside down, at least when compared to other application. This is not a big issue though).

I can select music, but:

• Even though cabbie is selected, It uses the "old" default wps theme.
• It does not play any music selected

Any idea what I can do to trace these problems?