[Android] Eclair 2.0.1 for the Vogue (Nexus One Bootanimation)

[sshark]

as well I have a fully working 2.1 base build including some nexus stuff. As I don't believe there's any sense in having 2 of the same build on here I'll let zen post if he likes. As well, there are no sleep issues in 2.1

this is amazing! I saw your name in other/androidspin forum in credits for Eclair on Dream/Magic, I did not know that you were involved in developing other than vogue.

[TheKartus]

as well I have a fully working 2.1 base build including some nexus stuff. As I don't believe there's any sense in having 2 of the same build on here I'll let zen post if he likes. As well, there are no sleep issues in 2.1

Sweet deal. Any 2.1 build sounds awesome. Really makes having an old phone worth it when you get to play with new builds of Android even before the phones they are meant for hit the market.

[zenulator]

I'm not going to post any more android builds so if anyone else wants to continue on be my guest.

[crackeyes]

I'm not going to post any more android builds so if anyone else wants to continue on be my guest.
I will host it if you will want. If you give me a copy of the system img i will host it for every one else.

Sorry to loose your work you do great work.

[TheKartus]

I'm not going to post any more android builds so if anyone else wants to continue on be my guest.

That's a shame. You do good work for the community. It is very appreciated. :)

[polyrhythmic]

:O it's the end of an era! Thanks again zen, I've learned a ton, your work has been invaluable!

[mssmison]

I'm just working out some issues with the framework and it'll be ready to go. I'll start a new post when it's ready. In the spirit of respecting this thread topic let's keep 2.1 comments to the new thread.

Like Zen, this will probably be my last, as mentioned here previously I work with the dream forum as well and have a new dream being shipped to me.
I'll still be around as my wife still has her Android Vogue but I probably won't be too involved in development.

[TheKartus]

I'm just working out some issues with the framework and it'll be ready to go. I'll start a new post when it's ready. In the spirit of respecting this thread topic let's keep 2.1 comments to the new thread.

Like Zen, this will probably be my last, as mentioned here previously I work with the dream forum as well and have a new dream being shipped to me.
I'll still be around as my wife still has her Android Vogue but I probably won't be too involved in development.
Is that the new 2.1 lockscreen? Interesting.

[bri3d]

That's DeskClock.apk, you can get it from the 2.1 dump and run it on 2.0.1 right now if you want. It doesn't work well in 320x240 and the photo slideshow feature requires Gallery, which often times runs out of texture memory and crashes on Vogue depending on how many pictures you've got, but it does work.

[tatnai]

Running Droid 2.1now on the Vogue. With Droid boot animation

as well I have a fully working 2.1 base build including some nexus stuff. As I don't believe there's any sense in having 2 of the same build on here I'll let zen post if he likes. As well, there are no sleep issues in 2.1

we have voice search and camera working yet?

[JM-PDA]

... I made a landing page to download the files at. Located HERE (http://breakaux.com/android-downloads/)

Once Zen gets the 2.1 system image I will upload it there as well.
While your there take a look around the site. (self promoting LOL)

Hi Crackeyes, Thanks for posting/hosting the 4 files on your website. Downloading them as we speak. I am currently running Android 1.5 successfully on my Sprint HTC Touch. Will this Android 2.0.1 version work on a CDMA/Sprint? How stable is it?

Thanks!

[crackeyes]

Hi Crackeyes, Thanks for posting/hosting the 4 files on your website. Downloading them as we speak. I am currently running Android 1.5 successfully on my Sprint HTC Touch. Will this Android 2.0.1 version work on a CDMA/Sprint? How stable is it?

Thanks!

I did not create or originally post this just helping the guys out by hosting it for them.

It works on my CDMA US Cell Touch. I get random lockups sometimes but it is one of my favorites that I have used. It does have a battery drain image with the zimage but I will upload the new zimage that i found that so far is proving not to have the issue.

[jamezelle]

we have voice search and camera working yet?

2.1 has no sound as of yet but it sleeps:D

[Shidell]

2.1 has no sound as of yet but it sleeps:D

Haha. :)

How's 2.1 with everything else? Data? GPS? Bluetooth?

[crackeyes]

2.1 has no sound as of yet but it sleeps:D

With the zimage that was posted a few post back (zimage3 (http://drop.io/suspendhacking)) it sleeps. As far as i can tell. I have had it unplugged for over 2 hours and my battery has not drained a bit where the one zimage that is in the bundle it usually drains in 20 minutes

[zenulator]

Sound works fine in 2.1. Posting from it right now with music playing fine. Are U using maxismas dump?

[jamezelle]

Sound works fine in 2.1. Posting from it right now with music playing fine. Are U using maxismas dump?

no using drizzy's droid

[zenulator]

no using drizzy's droid

it should work on drizzys too.

[zenulator]

the 2.1 i'm running works just like 2.0.1 plus it sleeps and the google apps are integrated better. the only thing is that it doesn't look as nice in qvga since it's made for wvga. so over all it's a sideways step. not a step up or down. calls/data/sound/gps all work. the droid splash doesn't scale to qvga like the nexus one does.

[TheKartus]

the 2.1 i'm running works just like 2.0.1 plus it sleeps and the google apps are integrated better. the only thing is that it doesn't look as nice in qvga since it's made for wvga. so over all it's a sideways step. not a step up or down. calls/data/sound/gps all work. the droid splash doesn't scale to qvga like the nexus one does.

What about the animated backgrounds and all that?

[Shidell]

Hm, so is there a build of 2.1 available that we can use?

[kr4zyc1d]

hey guys, great work again zen and everyone who put all the effort into this project. is there a link to the most recent downloads for this stuff? Thanks again.

[TheKartus]

Hm, so is there a build of 2.1 available that we can use?

There are two 2.1 roms out. I tried to look at one earlier, but, being a complete amateur I got caught up on a basic step of porting it. We're at the mercy of the pros on this one.;)

[Shidell]

There are two 2.1 roms out. I tried to look at one earlier, but, being a complete amateur I got caught up on a basic step of porting it. We're at the mercy of the pros on this one.;)

Ah. :) Something to look forward to!

[jamezelle]

yeah right.............................

ahhhh|"The Kartus"| There are two 2.1 roms out. I tried to look at one earlier, but. knowing you are free from christmas...We're at the mercy of the pros on this one.

[TheKartus]

yeah right.............................

ahhhh|"The Kartus"| There are two 2.1 roms out. I tried to look at one earlier, but. knowing you are free from christmas...We're at the mercy of the pros on this one.

I'm confused on this one. :( But I have two on my computer from Android Spin, if only I could have gotten my ext2 file to turn into a sqsh, I could have watched my attempt at a port fall dead in the water on my phone, not just on my computer.

[zenulator]

jac is back with a new xrom eclair 2.0.1 aosp.

[crackeyes]

jac is back with a new xrom eclair 2.0.1 aosp.

got a link.

Also when you going to post your 2.1. sorry to a pain but im inpatient

[zenulator]

got a link.

Also when you going to post your 2.1. sorry to a pain but im inpatient

i'm not putting up anymore android builds. i am going to port jac's new build for myself. i'll put up instructions on how to port both so you guys can do it yourself and share it.

[kr4zyc1d]

Thats cool. Do you have a build of 2.1 that can be run from the SD card instead of flashing?

[drewden123]

So, a nand doesn't use a zImage, so are there still sleep issues for nand users I'm guessing? Also, does anybody plan on sharing a 2.1 build? I simply don't have the time to set up linux on my machine, learn to port, etc. Thanks.

[zenulator]

i dont either

[drewden123]

i dont either

I understand. Not even a chance of posting just one last link to 2.1 for vogue? Seeing as you've already ported it. If not, I understand and thank you very much for all the work you've done.

[TheKartus]

So, a nand doesn't use a zImage, so are there still sleep issues for nand users I'm guessing? Also, does anybody plan on sharing a 2.1 build? I simply don't have the time to set up linux on my machine, learn to port, etc. Thanks.

If I can get my attempts to work, I'll be sure to post it. But don't hold your breath.

[drewden123]

If I can get my attempts to work, I'll be sure to post it. But don't hold your breath.

Much appreciated. I look forward to seeing your work. :)

[kr4zyc1d]

Ok, so I understand that you aren't posting your stuff any more, but do you know about the other links that would be most up to date? Such as dzo's basefiles an updated system.sqsh and the zimage3 (or now 5) on the kaiser forum? I wanted to know if there were links for the other stuff, or just general information about those items. Thanks guys.

[TheKartus]

Ok, so I understand that you aren't posting your stuff any more, but do you know about the other links that would be most up to date? Such as dzo's basefiles an updated system.sqsh and the zimage3 (or now 5) on the kaiser forum? I wanted to know if there were links for the other stuff, or just general information about those items. Thanks guys.

We need one organized community site like we had with vogue-android. Whether its on Sourceforge or Google Code again, it needs to exist to keep everything labeled, up to date, and organized.

[myn]

x2.

This is getting out of control.

The updated lib for the fixed GPS isn't incorporated into dzo's repository nor sourceforge. The only place to find it is here on xda. There are mixed versions of rootfs floating around too.

Ideas?

[kr4zyc1d]

x2.

This is getting out of control.

The updated lib for the fixed GPS isn't incorporated into dzo's repository nor sourceforge. The only place to find it is here on xda. There are mixed versions of rootfs floating around too.

Ideas?

Yea, it is a bit confusing. I agree with TheKartus, some sort of localized community download area such as google code. Could we not clean out and start fresh with the original google code area?

[gigermunit]

Yea, it is a bit confusing. I agree with TheKartus, some sort of localized community download area such as google code. Could we not clean out and start fresh with the original google code area?

If it comes to it i might try and put up a site if necessary :/

[mssmison]

My 2.1 build is not finished yet. I'm just working out some framework issues in the services.jar file.
Because droid is so much higher res it's causing some issues. I could drop a 2.0.1 dump, but I really want to see 2.1 sdk 7 running, (which is what nexus is based on) and what I'm using.
Patience. Everyone emailing me is not going to make it any faster.
I'm also working on porting two other builds at the same time.

[AndroidNoob]

I am totally new to Android on the Vogue but so far I've been able to use the .tar file to flash to Android but that's it. I just placed the .tar file in my card and flashed using the nbh in the android install file. I really would like to try this build but don't get how I'm supposed to go about it. Here are my questions.

Do I need to use the .tar file again?
Do I use the NBH from the AndroidInstall.zip or the one from DZO's site and what resolution?
Do I need anything from the eclair-221209 file if I'm flashing?
Does it matter if I use a blank data file or not?
Do I need to use the datatonand, systemfstonand, rootfstonand file to flash to this build?

I tried searching but there are no guides that cover all of this. Some builds use .sqsh files others don't and some. Hope someone here can find the time to answer my questions. I'm really impressed with the work the devs have done and want to use this build

Thanks in advance:)

[stiltzkin]

I'm just working out some issues with the framework and it'll be ready to go. I'll start a new post when it's ready. In the spirit of respecting this thread topic let's keep 2.1 comments to the new thread.

Can someone point me to this thread? I can't seem to find anything. Thanks.

[TheKartus]

Can someone point me to this thread? I can't seem to find anything. Thanks.

There is no build out, so it doesn't exist yet. Patience is the key at this point.

[drewden123]

My 2.1 build is not finished yet. I'm just working out some framework issues in the services.jar file.
Because droid is so much higher res it's causing some issues. I could drop a 2.0.1 dump, but I really want to see 2.1 sdk 7 running, (which is what nexus is based on) and what I'm using.
Patience. Everyone emailing me is not going to make it any faster.
I'm also working on porting two other builds at the same time.

Soundd great. Thank you

[stiltzkin]

There is no build out, so it doesn't exist yet. Patience is the key at this point.

Oh, alright...thanks. I only asked because it sounded like a new thread already existed. I'll be patient :)

[vilord]

x2.

This is getting out of control.

The updated lib for the fixed GPS isn't incorporated into dzo's repository nor sourceforge. The only place to find it is here on xda. There are mixed versions of rootfs floating around too.

Ideas?
The updated lib for gps has been in the rootfs posted on sourceforge since the *day* it was released.

Why is everyone getting so grabby? Did you not get enough presents at x-mas/Hanukkah/new years?
The site is sourceforge.com/projects/androidhtc
I took down the one on google code because it was too much of a pain to manage and I don't like mercurial for source control (and i didn't want to have things spread all over the net)

[stiltzkin]

Why is everyone getting so grabby? Did you not get enough presents at x-mas/Hanukkah/new years?)

Hahaha, well obviously we didn't all get new phones :D

I think it's just because mssmission and zen have mentioned here that 2.1 porting is nearing completion (or is at least in a semi-usable state) and that it fixes some of the current problems with 2.0.1.

I understand that a tremendous amount of effort goes into this process though, and I'm really appreciative of those with the time and talent to make new builds happen. I mean come on - N1 is barely a twinkle in the general public's eye at this point and 2.1 is well on its way for a phone from 2007. That in itself is impressive.

So, in a word, sit tight guys. And don't forget to give credit where credit is due.

[vilord]

Okay. So I just noticed that I actually did *not* put the latest libgps for donut onto sourceforge...
I'll have that remedied in a few minutes :)

[myn]

Excellent thanks :)

[ParMaster]

Hey Great! Thanks a bunch.

[zenulator]

for those of you wanting to see 2.1 wait until the libs and frameworks are fixed. stop pm'ing me and other devs.... i'm prob not going to release a 2.1 build but one will be released by another dev in another thread when the time is right. i'd rather see a 99% build than a 80% build with power issues and no voice dial/search. as always thanks for testing.

[jamezelle]

for those of you wanting to see 2.1 wait until the libs and frameworks are fixed. stop pm'ing me and other devs.... i'm prob not going to release a 2.1 build but one will be released by another dev in another thread when the time is right. i'd rather see a 99% build than a 80% build with power issues and no voice dial/search. as always thanks for testing.

i need to work on a few framework files, and im waiting on the libs to be rewritten before any release. so yea... please be patient guys

[mssmison]

just the typical. :) Everyone wants everything new right away before it's even done. lol
I love that there's still the excitement about his phone guys :)

[Shidell]

just the typical. :) Everyone wants everything new right away before it's even done. lol
I love that there's still the excitement about his phone guys :)

Same here. :) Sometimes I feel like I'm so far behind some of you guys, but the desire to keep this phone alive and learn is enormous. :D

[TheKartus]

just the typical. :) Everyone wants everything new right away before it's even done. lol
I love that there's still the excitement about his phone guys :)

It seems as though, at least in my experience, that the Vogue never really caught a big crowd on Verizon. Most people that see my phone ask me what it is and then see the software on it and think its just as up there as a Droid. I know someone who just got a Droid Eris and was shocked to see my old phone running SenseUI also.

Its lots of fun to play with. I can't really imagine actually using this phone with Windows Mobile anymore...

[polyrhythmic]

Not here to threadjack, but since zenulator is no longer releasing builds I have continued in his spirit and released a build based on this ROM with several fixes. Vogue users are welcome to visit my Dark-Themed Eclair thread (http://forum.xda-developers.com/showthread.php?p=5144644#post5144644) in the Kaiser forums and give it a try. I haven't tested it on Vogue yet, but I don't see any reason it shouldn't work. Y'all and the Polaris users can comment in my Kaiser thread and I'll do my best to fix any bugs. Someone is also welcome to port my build to NAND and repost it over here, if they like. The suspend issue isn't fully fixed, but if you really want Eclair we've done the best we can.

Thanks again to zenulator and all the devs for their hard work, and for helping us Kaiser users get in on the fun. I couldn't have done any of this without their work to build from.

[mario_castaneda]

ok so im new to this and i already have android on my vogue but how do i go about getting this on my phone? is it just replacing the things on my phone with the downloads provided on the first page?

[smarcin]

Not here to threadjack, but since zenulator is no longer releasing builds I have continued in his spirit and released a build based on this ROM with several fixes. Vogue users are welcome to visit my Dark-Themed Eclair thread (http://forum.xda-developers.com/showthread.php?p=5144644#post5144644) in the Kaiser forums and give it a try. I haven't tested it on Vogue yet, but I don't see any reason it shouldn't work.

Thanks for the invitation. Do we Vogue users use the same rootfs and zImage as you Kaiser users or do we use the Vogue ones? If we use Kaiser rootfs and zImage, are they made to use with ext2? Thanks.

Sally

[wdbanks]

Thanks for the invitation. Do we Vogue users use the same rootfs and zImage as you Kaiser users or do we use the Vogue ones? If we use Kaiser rootfs and zImage, are they made to use with ext2? Thanks.

Sally

Use everything in the zip file except zimage3...it works flawlessly!

[zenulator]

woo hoo almost made the front page of xda-developers.com via a diamond/raphael port of this build from babijoee. :D

[Shidell]

woo hoo almost made the front page of xda-developers.com via a diamond/raphael port of this build from babijoee. :D

:( I'm going to miss you if the Vogue community loses your help.

I need to get up to speed on Android development and learn as much from you as I can ASAP. Gah.

[stopthebus]

Use everything in the zip file except zimage3...it works flawlessly!

Could you define flawlessly?
Sleep?
Voice Dial/Search?
What resolution are you using?

Thanks

[smarcin]

Use everything in the zip file except zimage3...it works flawlessly!

I have been using zImage3 from the Kaiser forum on my Vogue. The reason I am using this zImage is so that my Vogue will sleep. It does sleep, so I hate to change zImages. I am running with ext2 partitions (2). The rootfs is the separate one in post #1 in this thread. Here's what I'm experiencing. Data works, GPS works, calls are fine. (I still have yet to find a headset that I can use for calls, though.) I am getting a lot of force close/waiting popups, though. I was also not able to load all the apps that are in the add on folder. I REALLY want to install Terminal. I have not been able to install it, either by adding it to my AndroidApps folder or by running it from Astro. I haven't been able to install it from the Market either. I am running 240 x 320 @ 120.

Does anyone know if the sleep problem is solved on any of the Vogue zImages for Eclair?

Could the force close/waiting popups be due to the Kaiser zImage3 or is it something to do with my ext2 partitions and the way memory is used?

Finally, can anyone suggest how to get Terminal onto my Vogue? I did originally boot it at 320 x 480 @ 160. Maybe if I back up my data.img and boot into 320 x 480 I will be able to install terminal?

Thanks.

Sally

[wdbanks]

Could you define flawlessly?
Sleep?
Voice Dial/Search?
What resolution are you using?

Thanks

Im using the resolutions recommended 240 x 320 x 120
it sleeps fine
voice dial doesnt work on the kiaser version either

[wdbanks]

I have been using zImage3 from the Kaiser forum on my Vogue. The reason I am using this zImage is so that my Vogue will sleep. It does sleep, so I hate to change zImages. I am running with ext2 partitions (2). The rootfs is the separate one in post #1 in this thread. Here's what I'm experiencing. Data works, GPS works, calls are fine. (I still have yet to find a headset that I can use for calls, though.) I am getting a lot of force close/waiting popups, though. I was also not able to load all the apps that are in the add on folder. I REALLY want to install Terminal. I have not been able to install it, either by adding it to my AndroidApps folder or by running it from Astro. I haven't been able to install it from the Market either. I am running 240 x 320 @ 120.

Does anyone know if the sleep problem is solved on any of the Vogue zImages for Eclair?

Could the force close/waiting popups be due to the Kaiser zImage3 or is it something to do with my ext2 partitions and the way memory is used?

Finally, can anyone suggest how to get Terminal onto my Vogue? I did originally boot it at 320 x 480 @ 160. Maybe if I back up my data.img and boot into 320 x 480 I will be able to install terminal?

Thanks.

Sally

I switched to an older zimage that allows my headset to work (zimage-audio in the archives) I dont have my sd card partitioned and I dont have any issues with it sleeping and waking up properly.

[polyrhythmic]

Interesting, we should merge that audio patch into the newer kernel.

[zenulator]

Interesting, we should merge that audio patch into the newer kernel.

that zimage-audio just disabled bluetooth. wait until the audio libs are recompiled. that should fix sleep with out messing with the kernel.

[TheKartus]

I switched to an older zimage that allows my headset to work (zimage-audio in the archives) I dont have my sd card partitioned and I dont have any issues with it sleeping and waking up properly.

You mind posting the zImage your using?

[preardon]

ok, figured out how to fix this. This method will work if you have an ext2 install, otherwise the system.sqsh will have to be modified and rebuilt. In an adb shell, or terminal emulator:


umount /system/build.prop
mount -o rw,remount /system

edit system/build.prop and modify these lines:

ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi

to

ro.product.cpu.abi=armeabi
ro.product.cpu.abi2=armeabi-v7a

sync



after rebooting, you should be able to install LatinIME.apk. I think manup's latest build has this change, so when zen updates the build again, it will be fixed for everyone.

This build is working nicely for me now with a working keyboard, and sleep problem seemingly fixed with the kaiser newbie16 kernel.

I'm using nand, and this works until I reset, how can I make it stick and then delete the chinese keyboard?

[sshark]

I'm using nand, and this works until I reset, how can I make it stick and then delete the chinese keyboard?

include them in your build.prop file.