please close thread

---

Development has been integrated with the new rootfs.
Please see the thread here:
http://forum.xda-developers.com/showthread.php?t=584707

New version coming soon:
Version 2.3 info:
-Newer simplified setup, whether you use a partition or not you will use the same files;
- fixed copying issues that were stopping some Donut builds from working. All builds should now work file.
-there are no additional files unlike previous builds.
- support for a data partition as well.
- supports all phones that the rootfs is supporting, kaiser vogue diamond etc.


Version 2.2 info;
updated for better data file backup naming.
updated to support donut
updated to support wifi (thanks enate for this)


Version 2 info;
On boot it will prompt you to boot the new recovery image, if you press a key it will load the recovery image, (the first boot you must do this to install the system) if not it will boot as normal.
If you have a system.sqsh on your sd card it will prompt you to install to your ext2 partition
- after installing the system it will move it to /sdcard/installedsystem/installedsystem.sqsh
- it will move your data file to /sdcard/datafilebackup/data$date
and create a new one. After the inital boot you can reboot and copy back your data file again.

There is one caveat that was pointed out to me today. Do not change systems twice in one day unless you don't care about your data. Because it creates the data file based on date it will overwright the old one.
Why not data to? Well our current data.img solution is awesome for backing it up.


What's coming;
Native support for update.zip's from the dream themes forum.
Menu support with several different usefull options for setting up android (this is proving to be tough but I'm working on it)

here it is!

http://code.google.com/p/vogue-andro...q=#makechanges

Originally Posted by mssmison

Hey guys, I've got something new coming for vogue android, I need 2 people with VOGUES's only to test something for me.

Requirements; linux install, vogue only, be able to provide bug reports, be serious!

pm me; I'm hoping to have testing ready by the end of the day.

sure

have linux and vogue pmed you. dang, guess i didnt pm you in time...

I don't know what this is, but you've sure got me curious as hell.

If you need another tester, let me know.

Well looks like I'm not in the closed beta, but I'm looking forward to this with great excitement. With the loss of Zen, it's good to have you back and active on this stuff again. This wouldn't happen to be Android running natively on our little wonder-units would it?

Originally Posted by stickus

Well looks like I'm not in the closed beta, but I'm looking forward to this with great excitement. With the loss of Zen, it's good to have you back and active on this stuff again. This wouldn't happen to be Android running natively on our little wonder-units would it?

Technically, Android doesnt run "native" on any device. You don't have to port a device to android..just the linux kernel to get api's to work. I know your refering to booting android on our faster but much smaller enternal flash but the speed difference would be minimal and we would be confinded to smaller builds. I think it has to do with a memory limitation in android from the dalvik vm it uses. I'm not 100% sure on what im talking about but this is the impression ive had for android for a while. Please enlighten me if I have missed something..

posting in epic thread

Originally Posted by stickus

Well looks like I'm not in the closed beta, but I'm looking forward to this with great excitement. With the loss of Zen, it's good to have you back and active on this stuff again. This wouldn't happen to be Android running natively on our little wonder-units would it?

It's been stated before and I'll state it again, the speed of the nand (internal memory) on the vogue is very slow. Making android boot from the nand would be a step backwards... What I'm hoping I've got it a step forwards

Originally Posted by mssmison

It's been stated before and I'll state it again, the speed of the nand (internal memory) on the vogue is very slow. Making android boot from the nand would be a step backwards... What I'm hoping I've got it a step forwards

Interesting.

I really don't understand why the internal NAND is so slow. Windows Mobile runs just fine from NAND, so why would running Android from it be any different?

Alternatively, it seems that a flashable Android would be much more convenient, and permanent.

I'm very curious to know what you're working on, mssmison.

Originally Posted by Shidell

Interesting.

I really don't understand why the internal NAND is so slow. Windows Mobile runs just fine from NAND, so why would running Android from it be any different?

Alternatively, it seems that a flashable Android would be much more convenient, and permanent.

I'm very curious to know what you're working on, mssmison.

Duel booting would a better option in my opinion..wm is just a better mini PC OS(Windows) and Android is a better phone/internet OS . This makes our devices even more versitle then phones just running android. I dont get how just having android would makes things better..since we just manually boot android instead of it booting once the phones is turned on...how about a linux bootloader that launches before wm does..and a graphical UI to choose from the two OS's

Originally Posted by ajclai08

Duel booting would a better option in my opinion..wm is just a better mini PC OS(Windows) and Android is a better phone/internet OS . This makes our devices even more versitle then phones just running android. I dont get how just having android would makes things better..since we just manually boot android instead of it booting once the phones is turned on...how about a linux bootloader that launches before wm does..and a graphical UI to choose from the two OS's

My understanding is that there isn't enough room to dual-boot both WinMo and Android from the NAND on the Vogue.

You could possibly put the bootloader in NAND and run WinMo and Android from storage, but that sorta defeats the purpose.