Axdroid 2010-09-16

Reading time ~2 minutes

Get it here :)

Little in terms of major user visible changes again I’m afraid. The biggest are probably that the lock screen is disabled once more (and in a much better way than I did before - I need to think of how I’ll distribute this code though, I have to choose between a custom frameworks/base repo or a patch file…), and any key should wake up the device rather than just menu. I’ve spent a while changing things in the build system, and mostly want to make sure I didn’t break anything (that wasn’t broken before :p). Axdroid now uses it’s own toolchain rather than the prebuilt codesourcery ARM toolchain. The axdroid one is newer (GCC 4.5.1 & binutils 2.20) and targets the xscale specifically, and seems to have built a smaller kernel binary than the codesourcery toolchain did. CompCache is updated to it’s latest code. I have ported the Axim code over to Linux 2.6.35, but it seems to have some bug involving a spinlock, so until I get chance to look into that Axdroid is still on 2.6.32. The init scripts saw some changes, and some stuff was moved around from the initrd to the root filesystem. Anyway, moan if I broke something.

Also, I just registered the IRC channel #axdroid on freenode. Let’s see if anyone uses it :)

Finally, for anyone who builds Axdroid themselves, sorry about all the changes to the build system! You might want to just grab a fresh copy and start from a clean slate. At the very least, you’ll want to ./ -c and mv src/kernel src/kernel-2.6.32. If you happened to build a toolchain whilst I’ve been messing with it over the past few days it’s probably worth doing rm -r toolchain too. I don’t have any more major changes to the build system planned, and switching to Linux 2.6.35 should happen seamlessly with a ./ -u when I get it working (if you move src/linux to src/linux-2.6.32 as I said). Also, whilst we’re stuck on 2.6.32 you’ll need to apply this patch to compcache to get it to build. Once 2.6.35 works it won’t be necessary anymore (but won’t hurt either).

comments powered by Disqus