Android: rasher's unmodified daily builds.

[ZincAlloy]

You simply put files into the "rockbox" folder instead of ".rockbox". 

[steak]

I will be hosting, until a time when official daily builds become available, builds of Rockbox for Android, updated daily. I'll not be updating this thread unless something dramatically changes.

The builds will be unmodified from SVN, as with my simulator builds.

Find them on http://rasher.dk/rockbox/android/

I'll add resolutions if requested (but keep in mind the lack of default themes).

I've been given a Motorola Defy MB525 with 480x854 resolution. I had it previously and mistakenly remembered that it ran rockbox. Could this resolution be added to the list so I can try a build ?

Cheers.

[steak]

Hello rockbox folks,

i used rockbox on my gigabeat an now i own an motorola defy. i tried the rasher build and everthing seems fine. but where can i find the widget. if i try to add a widget nothing no rockbox stuff is in the lists.
thx for help

best regards the pi

Judging by this, if it relates to the first Motorola Defy, maybe I remembered well... But then what resolution should be used ? I think it failed with 480x800. I "think" because actually I would like to confirm but I cannot put my hand on the damn thing. (Don't tell me to call its number, it has none as I planned to use only as a music player)

[steak]

Once upon a time, not so long ago, Rockbox on Android had the ability to load a binary with a target resolution smaller than that of the intended host.

Does that mean that installing a build dating back to that time would make Rockbox usable on a target which has no recent build matching its exact resolution ? As I mentioned just above I kind of remember having used a Motorola Defy (480x854) with rasher's build (480x800 ?) but with my second Defy and the latest builds it does not work.

On a dev's point of view it is probably best to keep up with the latest builds, on my user's point of view I would stick to a release but since there is none, I'd be happy with any specific build that works for good. My best android target so far has been a Galaxy S1 which worked just as good as my Sansa Clips. The much larger screen allowed me to change the WPS and display all tags suited to my needs. As I'm getting older this large screen becomes essential for me to be able to use any player.

I have a Galaxy S2 that handles rockbox for a while but freezes after random time : the music goes on if the playlist has not reach its end but it's impossible to call the app back on screen. At this point I have to force stop it through Settings/application manager/. I have no time or money to spend testing targets until I find one that works like my previous target. I have no time or skills the skills to fix whatever is going wrong. I have looked at the steps, they are just too far for me.

[[Saint]]

If one wants to run Rockbox on their device that badly, they should likely investigate building from source.

It really isn't difficult.

I don't say that meaning "its not difficult, for me, because I have the necessary skills in order to be able to do so", I say it in a completely literal sense. Compiling Rockbox for Android really isn't difficult at all.

If this is a thing you'd actually be interested in, I could write up a full walk through for compiling Android on a modern distribution using the latest Android SDK and NDK iterations, but I won't do so until I am convinced that there is a need for such a thing because its a reasonable undertaking on my behalf and I'm understandably unwilling to do so if there isn't any obvious demand for such a thing.


[Saint]

[steak]

If one wants to run Rockbox on their device that badly, they should likely investigate building from source.

It really isn't difficult.

I don't say that meaning "its not difficult, for me, because I have the necessary skills in order to be able to do so", I say it in a completely literal sense. Compiling Rockbox for Android really isn't difficult at all.

If this is a thing you'd actually be interested in, I could write up a full walk through for compiling Android on a modern distribution using the latest Android SDK and NDK iterations, but I won't do so until I am convinced that there is a need for such a thing because its a reasonable undertaking on my behalf and I'm understandably unwilling to do so if there isn't any obvious demand for such a thing.
[Saint]

Considering what I wrote elsewhere I repeat, I'd be an idiot to say no. So YES I am actually interested to learn to build from source. At this point I havve to forget everything I tried to understand about compiling and rely on your words. So ok it's easy in a literal sense, and that means I can do it.

Yes means YES literally.

Let me get rid of the "buts" : I am not sure of anything below but these things are part of what prevented me from trying to find out how to compile

> I believe I will need to have Linux installed on my computer. I have always been willing to install it but never did. I actually did to attempts where friends who had the skills tried and failed. I mean they did install it but I could not use it properly. With one version the buttons to click in different softwares were impossible to get on screen, with the other I cannot remember. My friends were not able to fix it. I also remember one trying to explain how he would leave allow double boot on my computer. (I do need Windows for softwares I use in common wiith friends, family, etc..)

> I understand what you mean by
>> Rockbox is compatible with any Android hardware that has a screen .../...
> I understand
>> .../... and a minimum API level of 8 (= Android 2.2 & above)

> I have a doubt : how useful will that be ? Let me explain... Rockbox was 100% usable on my Samsung Galaxy S1. It did not freeze, it did not crash, it worked as good as on my Sansa Clip+, Clip zip or Cowon D2.
Now I have a Galaxy S2. The secreen resolution is the same so I am able to use the same build on it but it freezes after random time. (the app is still running but cannot be called back on screen and controlled, stopped)
In my mind having Rockbox on a "mp3 player port" can't compare with an Android device : the mp3 player is a single target, the Android device is a generic target with 100s versions : different brands, different models, differents android versions...!!
I don't think compiling a build will stop the Galaxy S2 freezing. I guess the problem can come from the Rockbox app or the hardware or the Android version or a combination of all ?

If my compilation version for a device  is a 100% usable, fine, if not, I'll be left looking for another device again ?

NEVER MIND THOUGH, MY COMPILED BUILDS WILL HELP OTHERS, I WILL ALSO BE ABLE TO USE THEM FOR TESTING PURPOSES.

> Is it just the build I will need or also the Theme. I have been able to write my own themes but only based on pre-existing ones.
EDIT : in fact...

Compiling the build isn't going to fix your issue, at least not solely
The reason you don't have a theme is that no such theme exists for your target resolution.
You will have to create one, hope someone else does, or hope that I find that time and motivation to finish my long winded efforts on making a resolution agnostic theme for Rockbox.

> Does that mean one Theme needs to be created for each target resolution ?
> What does "resolution agnostic theme" mean ? A theme that would work on all target resolution ?

FINALLY YES I'm interested and if I find it literally as simple as you, it won't take long to achieve, if not well, I'll do my best but will have to consider how much time I can devote to going further !! You must not think that the time it will take (if any) for me to follow your instructions means you will have made a reasonnable undertaking for someone who does not do his best to use it.

[steak]

Combining this

Internet Archive to the rescue.  You can grab the 2-26 builds (though there is still some bugginess) here:
https://web.archive.org/web/20140227030816/http://rasher.dk/rockbox/android/

and that

Once upon a time, not so long ago, Rockbox on Android had the ability to load a binary with a target resolution smaller than that of the intended host.

I managed to download an old build that works on Motorola Defy MB525 android target. In a few days of usage, I'll be able to confirm what I think I remember i.e. it should be pretty usable (not freeze, etc...)
EDIT:  Damn it !! Rockbox just froze after less than 5mn playing time !! Then it came back for a few seconds, then froze, etc.. really weird and not like anything I encountered before. Looks like I am going to have to investigate, try more builds and so on. Hopefully it will work. I'll update this.

IF it works eventually, That means could mean...:

If one wants to run Rockbox on their device that badly, they should likely investigate building from source.
It really isn't difficult.
I don't say that meaning "its not difficult, for me, because I have the necessary skills in order to be able to do so", I say it in a completely literal sense. Compiling Rockbox for Android really isn't difficult at all.

I'm still willing to be convinced AND I'd be compiling not just for me but for friends willing to try Rockbox on a target with no build available... if the Theme is not a problem though !!

If this is a thing you'd actually be interested in, I could write up a full walk through for compiling Android on a modern distribution using the latest Android SDK and NDK iterations, but I won't do so until I am convinced that there is a need for such a thing because its a reasonable undertaking on my behalf and I'm understandably unwilling to do so if there isn't any obvious demand for such a thing.

Given your/my work/private commitments, and the fact that the problem is probably sorted for now, it's up to you  to see if and when you would write this full walk through. (If you do it, once again & a last time, remember I will try it)

Whatever you decide, thanks a lot for suggesting it !

[steak]

Good news :
1- Rockbox build d475dd3-130622 (2013-0622) on Motorola Defy MB525 + Android 2.2.2 is VERY USABLE at last : I've been using it for a couple of days while travelling with no crash, black screen or any problem.

My only problem is to access internal memory of the phone so I can change the WPS. Not a big problem, just a bit of hassle.

2- Rockbox build bb5341c-141107 on Samsung Galaxy S2 GT-I9100 + Android 4.1.2 is USABLE too : I've been using it randomly without the black screen bug. I still need to use it on a regular basis for a few days before I'm sure but it sounds good. There again I still have to adapt the WPS to my taste. Good news is it's much access to the WPS file with that phone so I'll be editing/testing my version on it and then it should work on the other phone (they share the same screen resolution build)

[TexasRockbox]

Hello. Does anyone have Rockbox for Android (any build) working on any Android 5.0 "Lollipop" build (official or unofficial)?  I see the Rockbox logo for a moment as it loads then it just crashes.  I am using a Galaxy Note 3 with a build of CM12.  Kitkat (4.4.x) changed the permissions for how writing is done to the internal/external memory.

[[Saint]]

Not presently.

I have it booting in 4.4.4 w/ ART, but 4.4.4 ART and 5.0.x ART are quite different beasts. I haven't been terribly motivated to look into what's tripping it up yet.


[Saint]

[erolk7]

Trying to run the latest on Samsung S5 (1080x1920) and I'm having no luck.  I believe I cleaned up everything from previous installations and I still get the small fonts.  Does anybody know of a theme that will work for this resolution.  I love rockbox and miss it on my new S5.   Any help is appreciated.

[ForteD]

Hi, I was try to install rockbox on my google nexus 7 2013, but can't open it when installed, it's freeze all the time. I was try 1920x1080, 1080x1920, 480x800, still can't run rockbox . I try to install it on my phone, it run perfecly

[LambdaCalculus]

What version of Android is your Nexus 7 running? Please note that Android 5.0 and any derivatives of it won't run Rockbox currently; Rockbox doesn't support the ART runtime in these newer versions of Android.

[JLHack7]

On my UMX MaxPatriot Tracfone there's android 4.1.2, and there's a weird clicking in the background when I play audio that is identical to the clicking in the rockbox iPod Classic 6G builds.

The specs for the phone are here: http://tracfonereviewer.blogspot.com/2015/01/unimax-maxpatriot-tracfone-review.html

I've been using PowerAMP because I prefer the equalizer's smoothing algorithm, which makes 5 dollar Koss earbuds with 16 Ohms of resistance and 10 mm drivers sound like 32 Ohms with 11 mm drivers on my Sanza Clip+.

I'd like to be able to get that smoothing in Rockbox if possible as well.

Edit: Wow, I'm such a noob at this.

PowerAmp's equalizer sounds good because of the high Q value done with a power of 2 increase in the equalizer bands, which sounds really good. Derp.

Managed to get an excellent sound by setting the Q values of the bands at 2.0-2.5.

[X86]

Hi, rockbox runs on android with ART, at least for me. I'm running kitkat 4.4.2, no problems at all, installs and then runs flawlessly. My phone if you want to know is an Alcatel Pixi 3(4), 4 inches 840 by 480 screen.

The problem with ART is that it precompiles the files and opposed to Dalvik, there is one vm for all the apps, not like Dalvik, individual vm's for each app, thats the conflict here. Also some apps won't like to be precompiled.