Rockbox Development > New Ports
Rockbox as an Application (Android, WebOS etc.)
kugel.:
--- Quote from: slade on November 08, 2010, 10:56:57 PM ---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
--- End quote ---
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:
--- Quote ---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.
--- End quote ---
I was able to reproduce segmentation fault on my linux pc with the following:
--- Code: ---export SDL_VIDEODRIVER=anythingbutx11
--- End code ---
giving 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: ---Couldn't initialize SDL: No available video device
--- End code ---
I do have /dev/fb0 to /dev/fb2 in one of the upgrade Firmware scripts the following is being done:
--- Code: ---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
--- End code ---
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 :D
kugel.:
--- Quote from: slade on November 22, 2010, 05:22:40 AM ---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.
--- End quote ---
Perhaps a problem with permissions (tried with root access?)? Just a guess though.
rosco_pc:
--- Quote from: JdGordon on November 07, 2010, 10:09:17 PM ---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.
--- End quote ---
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?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version