One can only hope. Of course if I had wanted to run android exclusively - I would have bought another android phone, or simply used the Nexus Google sent me.
i agree man, i hade the same situation, i was going between the google n1 or the n900 but i chose this, and i have no regrets, i'm not a developer or a hacker or anything, i'm just a 16 years old that had no idea what x-terminal is, now i can do a lots of tweaks with my device, proof : mine is overclocked at 1 ghz, with over 100 apps, and a lots of tweaks in the maemo ui.
bottom line is having nitdroid has one headline : the n900 is the best device in the market.
i agree man, i hade the same situation, i was going between the google n1 or the n900 but i chose this, and i have no regrets, i'm not a developer or a hacker or anything, i'm just a 16 years old that had no idea what x-terminal is, now i can do a lots of tweaks with my device, proof : mine is overclocked at 1 ghz, with over 100 apps, and a lots of tweaks in the maemo ui.
bottom line is having nitdroid has one headline : the n900 is the best device in the market.
you then need to check that the kernel is in /boot/multiboot if so it should work fine, if not check /boot and see if it is there and move to /multiboot if so.
When I check, I see the OMAP1 in multiboot but the boot menu does not show it as one of the options. What should I do next?
Also, is the Maemo 2.6.28.10-omap1 the one that I need since it is patched?
yes, i followed instruction,got it boot up, slowww as hell then open the apps,freeze then i have to force lose it, i tried all apps and about 95% of it stuck and kill it.
* Requires ideally 2.6.28.NIT.05 kernel (see below)
"Ideally"? Does that mean it can boot without it? And btw, are kernel patches avail?
I see that multiboot reflashes the kernel everytime you choose a diferent entry. This means you can swap between the original kernel and Nitdroid's around 100,000 times "only"
I swapped the power and back keys by swapping the two functions in all the files in /system/usr/keylayouts. The only caveat is that when the phone is locked, you need to use the real power key (not the slider) to unlock it. Otherwise I think it's much more usable when portrait browsing.
I also found so source code available from the android-x86 project to implement touch gestures for those functions in android 1.6 (I believe). I have no idea if it will work in 2.2, but if anyone wants to take a peak at the source in question it's here: http://git.android-x86.org/?p=platfo...d85b69fdb2133d
Javispedro: it also works with the .04 kernel for the most part. So you don't HAVE to use the new one if you don't want too. It's a good idea to use the latest though.
Then I rebooted the N900 with the slider open and didn't see the stock kernel as a selection BUT I pressed zero (0) and it began to load the OMAP1 kernel. After the usual double boot with 0, I am now able to use the default Kernel and I tested Fcam, HDR and Lowlight and they all work!!!
Better yet, I still have the Power Kernel and NITDroid as boot options. So it goes as
0: Hidden OMAP1 stock Kernel
1: Titan's Kernel
2: NITDroid
Fcam only works on the stock kernel as it is incompatible with Titan's kernel at the moment. If you load Titan's kernel, your N900 camera app will not work. You can either boot into stock or delete Fcam and the Fcam drivers to gain usage of your N900 camera using Titan's kernel.
As always, do this at your own risk but it did enable triple boot for me.
Trying to follow the partitioning section to try this and getting stuck already, could someone assist please?
I deleated all off the SD card and reformatted it in windows to make sure empty. This is what I did from the first time and the card has worked perfectly since.
umount /dev/mmcblk1p1
I get the following: cannot umount ........: No such file or directory
sfdisk -uM /dev/mmcblk1 << EOF
,<fat32>,C
,,L
,,
,,
EOF
I get the following: BLKRRPART: Device or resource busy
The disk is currently in use - repartitioning is probably a bad idea. Umount all file systems, and swapoff all swap partitions on this disk.
Use the --no reread flag to suppress this check.
Use the --force flag to overrule all checks.
way over my head and no idea how to get around this so any assistance would be most appreciated.
Another question, is is possible to split the SD card into 3 partitions and load NIT Droid across 2 and say Easy Debian on the 3rd partition and would it work with the boot menu?
