Saturday, February 13, 2010
Friday, February 12, 2010
Day 7: Clear for takeoff!
Thanks to soupdog from ArchosFans forums init hacking, we've finally got something that's bootable!
There's a few issues to clean up after, but we're finally ready to hack this thing to bits. Stay tuned!
And if you have any ideas or suggestions as to what you'd like to see in a first release, leave a comment and let me know!
There's a few issues to clean up after, but we're finally ready to hack this thing to bits. Stay tuned!
And if you have any ideas or suggestions as to what you'd like to see in a first release, leave a comment and let me know!
Thursday, February 11, 2010
Day 6: Still chugging along...
Hopefully I'll have something to show (for it) soon. I've gotten a few good boots, but nothing 'working' yet.
That said, I'm pretty sure the method I'm working on now will be successful. More to come soon.
If you're interested in helping move this project forward and think you can contribute, whether you're a user, developer, or anything in between - please do come join me in IRC - #opena5it on irc.freenode.net
That said, I'm pretty sure the method I'm working on now will be successful. More to come soon.
If you're interested in helping move this project forward and think you can contribute, whether you're a user, developer, or anything in between - please do come join me in IRC - #opena5it on irc.freenode.net
Sunday, February 7, 2010
Day 2: Research, testing, and more research
Having looked at the initramfs and filesystem differences yesterday and this morning, I decided to try a few shots in the dark - none of them worked. No big deal. I wasn't really expecting them to anyways.
So, what I'm going to settle with for now is modifying the rootfs.img that angstrom loads up from, and modifying the initramfs however it need be to get things booting up into android again. This is easily the safest way to do so, and only requires a few minutes to get it back where it was in the event that it fails.
From there, I'll get everything cleaned up as it should be, but getting android booting up is my first priority.
So, what I'm going to settle with for now is modifying the rootfs.img that angstrom loads up from, and modifying the initramfs however it need be to get things booting up into android again. This is easily the safest way to do so, and only requires a few minutes to get it back where it was in the event that it fails.
From there, I'll get everything cleaned up as it should be, but getting android booting up is my first priority.
Saturday, February 6, 2010
Day 1: Research
The title says it all. Spent most of the day looking into the kernel differences, what is going to have to be done, what can be salvaged from older builds, how angstrom is laid out, etc.
There's quite a bit of work to do, but I have a pretty clear idea of what needs to be done and how to do it. I'll be doing a few tests tonight and tomorrow, and deciding where to go from there.
The real work starts tomorrow.
There's quite a bit of work to do, but I have a pretty clear idea of what needs to be done and how to do it. I'll be doing a few tests tonight and tomorrow, and deciding where to go from there.
The real work starts tomorrow.
Friday, February 5, 2010
Opena5it dev blog!
This will be the home for the opena5it project - An open build of Android for the Archos 5 Internet Tablet. I'll be using this space to talk about all of the work involved, what has been done, design decisions, problems that arose, etc.
Because this is the first post, here's a quick run down of what I'm hoping to achieve:
Because this is the first post, here's a quick run down of what I'm hoping to achieve:
- A complete build of Android 2.0 AOSP ported for the A5IT
- All of the niceties of the 'hacked' ROMs (busybox, root, etc)
Subscribe to:
Posts (Atom)