Source code for reboot.png

[GoogleCodeExporter]

Hi, I'm working on building this app for F-Droid repository 
(http://f-droid.org). We can build Busybox with the NDK for at least ARM , but 
there is no source code for reboot.png, ls.png and toolbox.png. Do you know how 
to allow these to be built with NDK , (cross compiler or chroot if not), or 
could you provide a patch or branch that would allow the apps to function 
without these programs? The same issue applies to Permissions Denied.

Original issue reported on code.google.com by david8bl...@gmail.com on 23 Jun 2013 at 3:06

[GoogleCodeExporter]

These are just binaries I pulled from a device. I don't have the source for 
them or steps on how to cross compile them with the NDK

Original comment by Stericso...@gmail.com on 9 Jul 2013 at 2:42

• Changed state: Done

[GoogleCodeExporter]

Hi, the Busybox Pro app from revision 32 has been published on F-Droid but all 
the assets was removed before building. Was this a bad move? Sorry for the n00b 
question but it was mentioned in the forums the these binaries were no longer 
necessary and revision 32 was the most recent revision I could find that was 
working. If it was a bad idea, just say so and it can be pulled . Thanks.

Original comment by david8bl...@gmail.com on 21 Jan 2014 at 11:30

[GoogleCodeExporter]

yea, removing the assets is not recommended.

Why would the binaries no longer be necessary?

Original comment by Stericso...@gmail.com on 21 Jan 2014 at 6:34

[GoogleCodeExporter]

The Busybox binaries have been built from source by the NDK. Toolbox could 
feasibly stay, because prebuilt programs that come with the system are allowed 
in free software, but it's better to avoid. The fonts went too, because it was 
easier to delete the lot.

Original comment by david8bl...@gmail.com on 21 Jan 2014 at 6:44

[GoogleCodeExporter]

yea, I'm sure that doing all of that is going to cause crashes unless you 
modified the code to not use them.

Also, there are a number of updates coming down the road here soon but the 
changes to the pro version won't be  made open source at this time. So the free 
version is what I would recommend to provide as it will stay up to date.

You're going to run into the issue where the free version is going to be 
further along than the pro version. The updates coming down the road will be 
the support for other architectures such as mips and i86 all compiled against 
the NDK. 

Original comment by Stericso...@gmail.com on 21 Jan 2014 at 6:49

[GoogleCodeExporter]

I couldn't build the free version; it's missing some code (support). I couldn't 
build x86 or mips either. I'd be glad to get that published instead; as long as 
it's safe to use and installs BB and doesn't have toolbox, that's OK.

Original comment by david8bl...@gmail.com on 21 Jan 2014 at 7:02

[GoogleCodeExporter]

Hmm, I had no idea the free version was not compilable. I'll look into that and 
work to resolve it.

I'll re-open this issue to serve as a reminder for me.

Original comment by Stericso...@gmail.com on 21 Jan 2014 at 7:05

• Changed state: Accepted

[GoogleCodeExporter]

I've pushed the latest version to github, I'm probably going to start reducing 
the use of code.google in the future so I pushed it here to kick things off.

https://github.com/Stericson/busybox-free

Let me know if you have any problems building it.

Original comment by Stericso...@gmail.com on 24 Jan 2014 at 1:28

• Changed state: Done

[GoogleCodeExporter]

It builds OK. Before publishing this instead of the Pro version, are you happy 
that the app is functional and safe without reboot.png and toolbox.png? What 
about changing /data/local/toolbox to system/bin/toolbox? Also bear in mind the 
Busybox included will be that built with this config: 
https://raw2.github.com/linusyang/android-busybox-ndk/master/android_ndk_sterics
on-like. Sorry I don't understand much about code so I hope you can make it 
good on your end.

Original comment by david8bl...@gmail.com on 24 Jan 2014 at 3:15

[GoogleCodeExporter]

not having reboot.png is fine, but not having toolbox can cause issues on some 
devices, that's why it's there.

You can provide that binary, but it's outdated. 1.22.1 is the newest and 
building it against the ndk is broken at the moment.

Original comment by Stericso...@gmail.com on 24 Jan 2014 at 3:20

[GoogleCodeExporter]

OK. I'll include toolbox as it can be included under system library exception, 
except I'll use a binary pulled off my own phone; of course, you're trusted, 
but it's a policy of f-droid to minimize use of prebuilts via the developer.

To help in keeping the app updated please use tags or mark release commits 
clearly. Donation methods are welcomed.

Original comment by david8bl...@gmail.com on 24 Jan 2014 at 3:53

[GoogleCodeExporter]

I noticed this free version doesn't have info about some of the applets that 
will be included such as ar, whereas the pro version did.

Original comment by david8bl...@gmail.com on 24 Jan 2014 at 3:57

[GoogleCodeExporter]

That could be an issue I need to address as well. I'll have to look into that, 
the free and the pro should both give information about all applets.

What do you mean about Donation Methods?

Also, F-Droid is pretty new to me, only found out about it recently but it 
looks pretty cool.

I'll be doing a bit of work soon with Busybox so I think you'll see updates 
coming soon. I'm going to revert back to the uclibc build that I have been 
using because I've once again found that it's usually less problematic than the 
ndk compiled version. I have seen many issue arise in the past when I've tried 
offering the ndk binary and this time around I'm also seeing issues again. I 
might try to find a way for someone to choose the ndk build over the uclibc 
build but the problem with that is that I either have to increase the 
application size because I need to provide the binaries within the application 
or I have to add internet access to my application so it can download said 
binaries and both are frowned upon.

Not sure what my solution will be here. I compiled an x86 version of Busybox 
against the uclibc and I just ordered the razr i (an x86 arch cpu) to test it 
on. I hope to offer x86 users this binary as well. This may mean that I will be 
removing the ability to select a version of busybox to install and just provide 
one version so that I can keep the size of the application to a min.

Original comment by Stericso...@gmail.com on 24 Jan 2014 at 4:07

[GoogleCodeExporter]

Donations are preferably a web page, explaining why you need the money, but it 
can also be an XDA button, flattr id, bitcoin/litecoin/dogecoin address or even 
a paypal url with email address encoded. As long as you inform f-droid when 
things change and money doesn't go into thin air.

You are welcome to contribute changes via git at gitorious.org/f-droid. 
Although it would be great to support other toolchains, only the latest NDK is 
currently supported.

Original comment by david8bl...@gmail.com on 24 Jan 2014 at 4:28

[GoogleCodeExporter]

Ah, ok. I'm not too worried about that.

How did it come about that the NDK is the only supported toolchain?

Original comment by Stericso...@gmail.com on 24 Jan 2014 at 4:33

[GoogleCodeExporter]

I suppose most apps can be built with the current NDK.  It's all automated; you 
can create your own build environment to build the apps by running a couple of 
commands, so plenty of thought has to be given to what should be supported.

Original comment by david8bl...@gmail.com on 24 Jan 2014 at 4:58