As for autostart, see:
Code:
if [ -f /ezx_user/etc_files/startup ]; then
chmod +x /ezx_user/etc_files/startup
/ezx_user/etc_files/startup
end
- that way, we can have autorun, without the need for memory card. And we can easily write to that file.
All java apps are gone, same for ringtones and wallpapers (just one ring and one wallpaper left). Instead I put busybox binary there, and removed standard ash/bash/sh, now it uses busybox' ash. And I added terminfo entries, so programs in ncurses will work. And tab-complete, up arrow history, etc.
There is also modified /etc/profile (no need to . /home/native/.profile). I don't really understand /etc/fstab in ezx, it's totally inaccurate to things really mounted :/
I would like to have everything (all fw's files, except for memory card) mounted on jffs2-type (included in kernel) rw partition, but for now that's beyond my skill... no info about motorola's internals, heh.
I also integrated ext3/ext2/loop drivers. I'd love to integrate bluez module, but my toolchain isn't able to compile any kernel module...
Autoswap - yeah. It'll just look for swap file in your desired directory (at least the /ezx_user/etc_files will be useful - that's where config files live, because it's safer than memory card, and won't take up much space).
USBnet never worked for me, so I'll just leave it as a program you can install from pkg. I'd like to put "motnet" in usb modes, but so far I have no idea how, still have to work on it.
@drhstoor: Nothing will be integrated, sorry
You can always install them in any way you prefer, which takes just seconds. I don't know about camera quality - is it software dependant? And about newer software from a1600 - I've read they don't add anything useful, but are more bugged on our e6. So there is no point in doing that.
Release? In a month or so :P For now I'm working with files extracted from firmware (hell, is there a safe way to test things? Like virtual machine working like E6?) packaging and testing will be later.