PDA

View Full Version : [Android] Eclair 2.0.1 for the Vogue (Nexus One Bootanimation)


Pages : [1] 2 3

zenulator
27th October 2009, 11:31 PM
This is an Eclair 2.0.1 build taken from the 2.0.1 sdk image and parts of the droid/milestone/nexus and the launcher/google apps from manup456's dream build. Settings reads this as 2.1 but it isn't. It's just for compatibility with some nexus apps. The nexus one boot screen is also enabled. I had to remove some apps from system/app so it would fit on nand.They can be installed in your android apps folder on your sdcard or through adb or through an android file manager like astro or pushed to /system/app if running a read/write system image or partiton. This build does not sleep with out the hacked suspend kernel found in the kaiser thread.

Youtube video of the Nexus One bootanimation on the vogue (http://www.youtube.com/watch?v=ECee3bCjfCA)

Downloads:

http://breakaux.com/wp-content/uploads/eclair-221209.zip Bundle with new system image. Do not use the included rootfs.img unless your running from the system.sqsh through haret.

Add on apps
http://breakaux.com/wp-content/uploads/eclair-addon-apps.zip

If you don't have the latest basefiles get them at the Sourceforge Android HTC Download Page (http://sourceforge.net/projects/androidhtc/files/)

Use the newest zImage or nand nbh from dzo @ http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

Kaiser thread containing a Dark themed 2.0.1 build which also works for vogue plus link to hacked suspend kernel. http://forum.xda-developers.com/showthread.php?t=600154

Start with a blank data.img or let a new one be created. Wipe /data if running from nand before installing.


This takes a couple minutes for first boot. After the setup ends and your home screen appears there will be a little lag until android is done scanning your sdcard for pictures/music. Check logcat and you'll know what I mean. After it is done scanning this build is very fast.

You can thank vilord for rebuilding the libs for eclair and srwalter for updating the libgps.so for donut.

What works:
Calls
Data
GPS
Maps
Youtube
Gmail
gtalk
Market
Contacts Sync
Native Exchange Support

Not working:
Camera
Voice Dialer/Voice Search (fixed as soon as libaudio.so is rebuilt with dzo's source)
Bluetooth
Exchange Calender Sync (I don't use exchange so let me know)
Suspend/Sleep (partial fix using suspend hacked kernel)

You can edit your default.txt or build.prop after the first boot and change the lcd density to 110 if your running in qvga and this will display the whole dialer and music app correctly.

Resources.zip with the Nexus One wallpapers/ringtones in Manups thread. http://www.4shared.com/file/173892052/20801a29/Resource.html

bandur
28th October 2009, 12:05 AM
I read you are not looking for bug-reports, and it says vogue only, but I could not resist trying it out on my Kaiser.

It didn't boot, halted shortly after getting to the system image at mdp_dma_to_midi: busy ..

Thanks for your work ...

zenulator
28th October 2009, 12:14 AM
I read you are not looking for bug-reports, and it says vogue only, but I could not resist trying it out on my Kaiser.

It didn't boot, halted shortly after getting to the system image at mdp_dma_to_midi: busy ..

Thanks for your work ...

Really was that necessary.

Stork66
28th October 2009, 12:16 AM
hey Zen....






I <3 U

ruizit0
28th October 2009, 12:25 AM
so zen... and donut ? are you gonna stop donut development to start with eclair ?

zenulator
28th October 2009, 12:32 AM
so zen... and donut ? are you gonna stop donut development to start with eclair ?

I'm staying with donut for a while. The source for eclair isn't even released so theres not much we can do with it right now. The libs for donut aren't working in this build. This was taken from the generic sdk image and it's lacking a lot of functionality.

TheKartus
28th October 2009, 01:07 AM
I'm staying with donut for a while. The source for eclair isn't even released so theres not much we can do with it right now. The libs for donut aren't working in this build. This was taken from the generic sdk image and it's lacking a lot of functionality.

A dump from the Droid should be awesome though, no? Native Verizon CDMA support ftw.

~David
28th October 2009, 03:04 AM
Thanks for the upload Zen :)

And yes, can we please keep this thread to Vogue discussions only? After all, this is the Vogue forum. It's getting a wee bit annoying having Vogue threads hijacked with Kaiser/Polaris discussions.

zenulator
28th October 2009, 12:23 PM
so who likes the new lock screen?

TheKartus
28th October 2009, 04:58 PM
It looks like it may be nice. It slide or anything? or still a press of the menu button to unlock?

zenulator
28th October 2009, 07:42 PM
It looks like it may be nice. It slide or anything? or still a press of the menu button to unlock?

you spin the wheel at the bottom to the right to unlock. spin to the right to turn off sound if we had sound working. looks like there will be other options added because there are several spots open for icons on the wheel. it's pretty cool.

myn
29th October 2009, 12:57 AM
You guys see the new Maps app in 2.0? Unreal..


I can't wait to get eclair working on our phones!

refthemc
29th October 2009, 01:06 AM
Downloading now, i'm pretty hyped about all these new features :thumbsup:

By the way, i'm still using cupcake because donut market problems scare me. lol

zenulator
29th October 2009, 01:38 AM
You guys see the new Maps app in 2.0? Unreal..


I can't wait to get eclair working on our phones!
the eclair maps works in donut its already in the htc donut at vogue hero. as for eclair i made a call with it today but with out audio or data its pretty useless. nice to look at and see new features.

refthemc
29th October 2009, 01:47 AM
the eclair maps works in donut its already in the htc donut at vogue hero. as for eclair i made a call with it today but with out audio or data its pretty useless. nice to look at and see new features.

Isnt that how donut started? dont give up Zen, you guys are pretty awesome with android. Good luck guys

cbaty08
29th October 2009, 01:57 AM
I am currently running Ion, and CANNOT wait for this bada$$ 2.0 to be polished ; )

Thanks for your hard work devs!!!!!!!!!!!!!!!

zenulator
29th October 2009, 03:43 AM
well 2.0 is going to be a major over haul from what i can tell. once google drops the source code or a device similar to the vogue comes out with 2.0 it should be a lot easier to port. if we could figure out how to get data working with a cdma vendor ril like the verizon droid we would be in business. we should have a leak soon. the phone will hit the shelves in a week or so. the old sholes dump had a umts ril which i havent tried and doubt it will do anything. anyway the next couple weeks should be interesting.

jamezelle
29th October 2009, 03:52 AM
yea maybe that ril will unfudge my data:p and undo what the sprint one did... native cdma for verizon will be great


off subject: the desire runs sense UI in either 1.6 or 2.0 from what i gather. so that means it 'should' be compatible with 240x320 , yeah yea i kno we have tattoo but im just saying here is for hoping

tatnai
29th October 2009, 04:34 AM
By the way, i'm still using cupcake because donut market problems scare me. lol

noted a lot more apps in the market today. don't think it is the full deal yet, but plenty more popping up.

zenulator
29th October 2009, 04:50 AM
noted a lot more apps in the market today. don't think it is the full deal yet, but plenty more popping up.
i noticed that too. more featured apps still bt still not as many as cupcake. maybe thats due to the qvga? it seems most of the apps i see in donut are qvga compatible?

myn
29th October 2009, 05:15 AM
Something is definitely going on with the market. When I search for popular apps, like say facebook or google docs I get no search results, with xRom none the less.

myn
29th October 2009, 05:18 AM
the eclair maps works in donut its already in the htc donut at vogue hero. as for eclair i made a call with it today but with out audio or data its pretty useless. nice to look at and see new features.

Really?

I never noticed Google navigation in any of donut roms.

http://www.engadget.com/2009/10/28/google-navigation-video-hands-on-you-want-this/

zenulator
29th October 2009, 05:42 AM
Really?

I never noticed Google navigation in any of donut roms.

http://www.engadget.com/2009/10/28/google-navigation-video-hands-on-you-want-this/

thats motorola's app. it just interfaces with google maps. i have the apk if you want but it's no good without gps working.

jamezelle
29th October 2009, 07:26 AM
thats motorola's app. it just interfaces with google maps. i have the apk if you want but it's no good without gps working.

im sure you have, but i have to ask, have you tried the app in cupcake?:D

mattcoz
29th October 2009, 08:42 AM
thats motorola's app. it just interfaces with google maps. i have the apk if you want but it's no good without gps working.
Nope, it's Google's, available for any Android 2.0 phone.

katmandu421
29th October 2009, 03:27 PM
Nope, it's Google's, available for any Android 2.0 phone.

+1, Here is a video from google, nothing to do with Verizon or Motorola

http://phandroid.com/2009/10/28/google-maps-navigation-announced-video-demos/

myn
29th October 2009, 04:21 PM
Anyone tested the new Google Navigation in cupcake or donut?

Is an APK available?

garringm
29th October 2009, 05:46 PM
Really was that necessary. This is a vogue thread. Respect that.

Thanks for the upload Zen :)

And yes, can we please keep this thread to Vogue discussions only? After all, this is the Vogue forum. It's getting a wee bit annoying having Vogue threads hijacked with Kaiser/Polaris discussions.

I greatly appreciated the work that all developers did even if it wassn't for my phone model, but I feel it must be said, yes this is the vogue thread and I'm sure if there were anyone over on the kaiser threads doing any real developement to the code then most of us wouldnt even be over here chiming in.I haven't seen enate or pmos pipe up for quite some time now. I gave up a 3day old iphone because I seen hope in the android for my ATT phone but its just small snide comments like this that really do kill it for a lot of people. You want people to get more interested in Android thats not the way to do it, this is a community of xda-developers at least thats the website I log into every day not vogue-developers, or
kaiser-developers. I do understand that there are a lot of BS post and most of you may see this as one of them, so be it. After more than a year of being involved with this I do believe I will be calling it quits with the entire android movement. I here those guys over at maemo are doing wonderful things in open source. November's the month it all happens too. C-ya

zenulator
29th October 2009, 07:20 PM
I greatly appreciated the work that all developers did even if it wassn't for my phone model, but I feel it must be said, yes this is the vogue thread and I'm sure if there were anyone over on the kaiser threads doing any real developement to the code then most of us wouldnt even be over here chiming in.I haven't seen enate or pmos pipe up for quite some time now. I gave up a 3day old iphone because I seen hope in the android for my ATT phone but its just small snide comments like this that really do kill it for a lot of people. You want people to get more interested in Android thats not the way to do it, this is a community of xda-developers at least thats the website I log into every day not vogue-developers, or
kaiser-developers. I do understand that there are a lot of BS post and most of you may see this as one of them, so be it. After more than a year of being involved with this I do believe I will be calling it quits with the entire android movement. I here those guys over at maemo are doing wonderful things in open source. November's the month it all happens too. C-ya

All I have to say that this is a vogue thread. I don't mind kaiser users posting but it gets confusing to vogue users when you have page after page about no data in kaiser and people start to think that there is no data in the donut builds on vogue. I think that something like that should be resolved in the kaiser threads. Also there nothing stopping kaiser users from starting their own donut thread in their own forum. I didn't create donut. I just get the system image together to make it work on the vogue which in turn runs on kaiser/polaris/nike. I'm good friends with a couple kaiser users and I'm not trying to make a divide or push them out of development. I personally asked pmos and kb7sqi if they had problems but they have been busy. So it's not like I don't want to see working kaiser builds.

If kaiser users get 2.0 fully working and start their own thread about it and we go over and invade with bugs specific to our phones thats cool right because its xda-developers not kaiser developers. But if you want to leave android development over the fact that we'd like to keep the threads on the topic of vogue in the vogue sub forum then go for it. Maemo looks pretty sweet.

This is just my view. I spend more time at this than I should.

tallnerd1985
30th October 2009, 03:58 AM
Just Got To Play With The Motorola Droid All Day Long Today!!
I would say the least that I have been very happy with Vogue-Android since the day DZO implemented GPU acceleration because it seemed to me that my phone was a lot more responsive and snappier than the stock G1. I tried the Sprint flavor the HTC Hero when it first launch and wasn't all that impressed, it still had the lag issues that our phones had but not as bad. Today, when I popped into worked, low and behold, a fully activated Motorola Droid was sitting at my desk.

Should I Check The Office To See If Anybody Was Messing With Me?
When I got to my desk, I see what appears to be the Motorola Droid sitting in the multimedia dock. As I am sitting there looking at it in amazement, I think to myself, is my coworkers playing a practical joke on me by setting up a dummy model in the dock so that I get excited for no reason. I cautiously reach for the phone, and as I reach for the phone...............................IT STARTS FLICKERING AND RINGING!!!!!

Holy Cow!!! Its A Live Phone!!
To Be Continued......

jamezelle
30th October 2009, 04:19 AM
Just Got To Play With The Motorola Droid All Day Long Today!!
I would say the least that I have been very happy with Vogue-Android since the day DZO implemented GPU acceleration because it seemed to me that my phone was a lot more responsive and snappier than the stock G1. I tried the Sprint flavor the HTC Hero when it first launch and wasn't all that impressed, it still had the lag issues that our phones had but not as bad. Today, when I popped into worked, low and behold, a fully activated Motorola Droid was sitting at my desk.

Should I Check The Office To See If Anybody Was Messing With Me?
When I got to my desk, I see what appears to be the Motorola Droid sitting in the multimedia dock. As I am sitting there looking at it in amazement, I think to myself, is my coworkers playing a practical joke on me by setting up a dummy model in the dock so that I get excited for no reason. I cautiously reach for the phone, and as I reach for the phone...............................IT STARTS FLICKERING AND RINGING!!!!!

Holy Cow!!! Its A Live Phone!!
To Be Continued......

howzabout a system dump!:D

zenulator
30th October 2009, 04:48 AM
Just Got To Play With The Motorola Droid All Day Long Today!!
I would say the least that I have been very happy with Vogue-Android since the day DZO implemented GPU acceleration because it seemed to me that my phone was a lot more responsive and snappier than the stock G1. I tried the Sprint flavor the HTC Hero when it first launch and wasn't all that impressed, it still had the lag issues that our phones had but not as bad. Today, when I popped into worked, low and behold, a fully activated Motorola Droid was sitting at my desk.

Should I Check The Office To See If Anybody Was Messing With Me?
When I got to my desk, I see what appears to be the Motorola Droid sitting in the multimedia dock. As I am sitting there looking at it in amazement, I think to myself, is my coworkers playing a practical joke on me by setting up a dummy model in the dock so that I get excited for no reason. I cautiously reach for the phone, and as I reach for the phone...............................IT STARTS FLICKERING AND RINGING!!!!!

Holy Cow!!! Its A Live Phone!!
To Be Continued......
I might have to go get a job with you then..

tallnerd1985
30th October 2009, 04:56 AM
I might have to go get a job with you then..

Well, Big Red is always hiring especially in my neck of the woods.

zenulator
30th October 2009, 03:39 PM
So how was the droid?

tallnerd1985
30th October 2009, 08:00 PM
Part 2
So Now The Phone Is Ringing???
So now I am shocked in amazement that their is an actual live droid in my presence on my desk. When I looked down to see the caller ID, it shows my boss's name and picture on the the gorgeous huge screen. I pick up the phone, being slightly heavy and all, and answer the call to find the audio is crystal clear and no distortion out of my boss's voice. I start talking to him asking whats going on with this phone and out of nowhere, he pounces on my back and scares the living shit out of me!!

Why Is There A Droid On My Desk??
After regaining my composure, I ask my boss how in the hell is there a live Droid on my desk?? He looks at me and says that he knows my deep, dark obession with Android and how I used to claim that it was going to knock the pants off the iPhone and Crapberries. So he figured that if anybody gets the right to play with the Droid for a day, that it should be me.

One Stipulation Thou
He says that I can play with it as much as I want but it has to stay in the back office at all times and none of the other employees can touch it since its logged in my name. As disheartened I may be, to hell with it, I am first one in the area that gets to exclusivley play with the Droid all day even thou I cant show it off to anybody besides my coworkers.

This Thing Is Fast As Bill Clintion Denying A BJ From His Secretary The First Time
To Be Continued.....

KERKEDAGAIN
30th October 2009, 08:14 PM
Part 2
So Now The Phone Is Ringing???
So now I am shocked in amazement that their is an actual live droid in my presence on my desk. When I looked down to see the caller ID, it shows my boss's name and picture on the the gorgeous huge screen. I pick up the phone, being slightly heavy and all, and answer the call to find the audio is crystal clear and no distortion out of my boss's voice. I start talking to him asking whats going on with this phone and out of nowhere, he pounces on my back and scares the living shit out of me!!

Why Is There A Droid On My Desk??
After regaining my composure, I ask my boss how in the hell is there a live Droid on my desk?? He looks at me and says that he knows my deep, dark obession with Android and how I used to claim that it was going to knock the pants off the iPhone and Crapberries. So he figured that if anybody gets the right to play with the Droid for a day, that it should be me.

One Stipulation Thou
He says that I can play with it as much as I want but it has to stay in the back office at all times and none of the other employees can touch it since its logged in my name. As disheartened I may be, to hell with it, I am first one in the area that gets to exclusivley play with the Droid all day even thou I cant show it off to anybody besides my coworkers.

This Thing Is Fast As Bill Clintion Denying A BJ From His Secretary The First Time
To Be Continued.....

dump it! dump it!!

tallnerd1985
30th October 2009, 08:31 PM
dump it! dump it!!

There is already a dump on the dream forums

KERKEDAGAIN
30th October 2009, 08:33 PM
There is already a dump on the dream forums

but of course..m'scuzi

zenulator
30th October 2009, 09:46 PM
That dump in the dream thread is old. It's from a umts test build. I'm sure we'll see a new one soon.

tallnerd1985
1st November 2009, 09:41 AM
Part 3 Finale
This Thing Is Fast...
Like I said before, my vogue-android phone compared to an actual G1 stock runs alot faster and smoother but nothing compared to The Droid besides one little thing. Everything from opening an app, zooming in and out of google maps, surfing with the web browser runs super smoothly and opens in one second. The only thing that disturbs me is the homescreen when moving across the desktop kind of lags and stutters a bit but I am guessing thats because of the high resolution screen and the new 2.0 OS.

It Feels Rock Solid In My Hands
The weight and feel of the phone is incredible. I can tell that this phone is top knotch and the build quality is second to none. I like that the slideout keyboard is not spring loaded and that you have to pull the keyboard out because from past experiences with slider phones is that the slider mechanism always breaks. The screen is georgeously clear and brilliant but the auto-dimming sensor can be annoying at times but thats why I turned it off. Lastly, with the compacitive screen, using the onscreen keyboard and rolling thru the menus is exact and precise.

Now For The Only Bad Part
As far as everything goes, the phone is great besides the marketplace with the new 2.0 OS. I downloaded a variety of apps to play around with to see how the phone handles them but soon came to be horified by some of the experiences. It seems to me that Google hasnt fixed the marketplace to filter out incompatible apps because a lot of the apps I downloaded gave me a lot of force closes or didnt function right like the Reality Browser 2.0 and how it interfaced with the camera because it was inverted and distorted. Hopefully they will fix that before the phone launches to ensure a smooth start on America's superior network.

Other than that, I love the phone and cant wait to pickup my personal one when it launches. Happy Halloween and thanks for all the hardwork from the developers and the community here.
http://img145.imageshack.us/img145/4135/downsize.jpg

enatefox
1st November 2009, 12:46 PM
Looking at dzo's Donut audio patch I really can't tell what would be different for Eclair. Nevermind the other files of course. Hopefully someone's got an idea? Time permitting, and the fact that I'm currently the last to post on all the relevant threads (<crickets></crickets>) I'm going to just try dzo's patch against Eclair and try to throw the chicken bones in just the right pattern. Here's to hoping we can make calls..

zenulator
2nd November 2009, 01:13 AM
Looking at dzo's Donut audio patch I really can't tell what would be different for Eclair. Nevermind the other files of course. Hopefully someone's got an idea? Time permitting, and the fact that I'm currently the last to post on all the relevant threads (<crickets></crickets>) I'm going to just try dzo's patch against Eclair and try to throw the chicken bones in just the right pattern. Here's to hoping we can make calls..

the emulator image isn't meant to be run on real hardware. the g1 port isn't much farther along than we are. i've modified it to at least make calls with it on my personal build but with no audio in or out it's useless. you can prob take some libs from the old sholes dump and get it farther along. i think our libaudio and ril from donut will work once the source is released. it's also using a new egl.cfg system thats going to require some reworking of the kernel and a new userspace driver for it. if anyone wants they can port akirah's g1 sdk port so see if anything is different or wait for the g1 port of the motorola sholes is out which should be any day now.

enatefox
3rd November 2009, 03:54 AM
Guess I missed the part about it coming from the emulator. I meant make calls with audio, I know you got pretty far for what you can do with it at this point. Too bad, only 5 pages and there's definately not a lack of desire to make this thing official. Hope we can get a good lead so I can retire my F5 key.

TheKartus
3rd November 2009, 04:21 AM
There is a desire to make this one official. It would be awesome.

cbaty08
4th November 2009, 01:47 AM
I have a GREAT DESIRE GENTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! : )

"If I only had a brain" to help out... :/

I am a QE Tech testing Beta software filing bugs and whatnot, and Would love to help out on any further testing anyone would like worked on.

Good Luck Devs!

-Chris

enatefox
4th November 2009, 01:55 AM
I haven't seen any work on Eclair yet for us. Best I see is we can hopefully borrow from G1/MT3G when they get up to date but still there will be compatibility issues.

So taking a giant step forward with almost no idea what I'm doing, I'll try to figure out the RIL, compiling audio libs without the -fail command and whatever else we need. I know I need help, so anyone who knows what they're doing or can learn keep posting.

sshark
10th November 2009, 03:14 AM
I looked at the droid and I immediately have fallen in love with 2.0, any news on this guys?

It looks really sweet!

zenulator
10th November 2009, 03:21 AM
i ported the sholes build but it's just as unusable as the eclair-sdk build. when it goes open source we'll get to work on it.

TheKartus
10th November 2009, 07:41 AM
Droid dump would be sweet.

inline4
12th November 2009, 05:47 AM
I have a droid... if you guys need me to do a memory dump, just tell me how and what s/w to use.

zenulator
12th November 2009, 05:53 AM
I have a droid... if you guys need me to do a memory dump, just tell me how and what s/w to use.

thanks for the offer but someone's already done it.

sshark
12th November 2009, 05:54 AM
I have a droid... if you guys need me to do a memory dump, just tell me how and what s/w to use.

I think people have sholes dump, problem lies in getting ril interface done.

I am sure peeps can do it, month ago when donut came out, we were worried about the same and now we have working donut!

jamezelle
12th November 2009, 06:39 AM
i want the eris dump:D

TheKartus
12th November 2009, 07:10 AM
i want the eris dump:D

Meh, Sense isn't worth it. I want the Droid 2.0 shit.

sshark
12th November 2009, 07:13 AM
Meh, Sense isn't worth it. I want the Droid 2.0 shit.

+1, HTC is shortchanging us on htc ril.

I would vote for 2.0

Shidell
12th November 2009, 07:18 AM
Gah. I'm a pretty smart guy, but I have no background in any of this. Sholes? Rils? What the?

What needs to be ported/changed? Someone please give me a job and point me to documentation and I'll get started. (I'm not kidding. Give me something to read/do/investigate so I can help.)

I do have a background in IT and software development experience, if it helps.

zenulator
12th November 2009, 07:37 AM
http://forum.xda-developers.com/showthread.php?t=581080

verizon droid has already been dumped a couple days ago. So has the gsm version called the milestone.

jamezelle
12th November 2009, 07:38 AM
Gah. I'm a pretty smart guy, but I have no background in any of this. Sholes? Rils? What the?

What needs to be ported/changed? Someone please give me a job and point me to documentation and I'll get started. (I'm not kidding. Give me something to read/do/investigate so I can help.)

I do have a background in IT and software development experience, if it helps.

sholes=motorolas codename for the droid=first phone with android2.0

ril=radio interface layer it needs tweaked to work with 2.0

pm your email and i will get you started;)

Shidell
12th November 2009, 06:28 PM
sholes=motorolas codename for the droid=first phone with android2.0

ril=radio interface layer it needs tweaked to work with 2.0

pm your email and i will get you started;)

Absolutely--PM Sent!

cbaty08
13th November 2009, 01:45 AM
Oh man, you guys are getting me excited!!!!!!!!!!!! : ) Good Luck!

silex
15th November 2009, 04:51 AM
Zenulator, nice to still see you around these parts. Once a dev, always a dev right? Hehe. I just picked up a Droid and let you tell you guys, call me crazy, but I'm returning it to go back to my trusty Vogue. I just miss it too damn much!

zenulator
15th November 2009, 05:46 AM
Zenulator, nice to still see you around these parts. Once a dev, always a dev right? Hehe. I just picked up a Droid and let you tell you guys, call me crazy, but I'm returning it to go back to my trusty Vogue. I just miss it too damn much!

i'm still using my vogue. i'm holding off for a couple months until verizon releases the third android phone then i'll weigh my options. the droid is nice but i'm not digging the looks of it. and the slide out keyboard from what i've seen isn't the best. they shouldn't have put the dpad like the g1 has it.

jamezelle
15th November 2009, 06:29 AM
i'm still using my vogue. i'm holding off for a couple months until verizon releases the third android phone then i'll weigh my options. the droid is nice but i'm not digging the looks of it. and the slide out keyboard from what i've seen isn't the best. they shouldn't have put the dpad like the g1 has it.

yeah im thinking about getting the eris around income tax time, unless they release something better by then.... for now my vogue is doing me just fine

Macmee
15th November 2009, 02:45 PM
yeah im thinking about getting the eris around income tax time, unless they release something better by then.... for now my vogue is doing me just fine

I might buy a G1. I don't need a WVGA resolution:p

According to Bell my vogue is a pda phone not a smartphone, and a smartphone wont work with my data plan..

drewden123
15th November 2009, 03:29 PM
My trusty vogue has lasted me a year next month and first with NFSFAN's roms, then stumbling onto android and all the marvelous work done here, i have to say the devs here are absolutely genius. no other corporation or big company has made (granted, nor did they want) our phones to last so long with so many updates. For example, my friend just dished out the $$ for a droid and brags about android blah blah...then i stroll in with my vogue that's one year old, and has almost all the same functions except not android 2 and no accelerometer for FREE. Thank you zen, your work is greatly appreciated. Do you accept donations?

zenulator
15th November 2009, 04:34 PM
My trusty vogue has lasted me a year next month and first with NFSFAN's roms, then stumbling onto android and all the marvelous work done here, i have to say the devs here are absolutely genius. no other corporation or big company has made (granted, nor did they want) our phones to last so long with so many updates. For example, my friend just dished out the $$ for a droid and brags about android blah blah...then i stroll in with my vogue that's one year old, and has almost all the same functions except not android 2 and no accelerometer for FREE. Thank you zen, your work is greatly appreciated. Do you accept donations?

i don't take donations but if you would like to donate there are donate links at vogue-android to show your appreciation. lot's of people worked hard before i came on the scene and they deserve it.

silex
15th November 2009, 11:20 PM
Same here about the d-pad comment. I have to reach too far in from the right side to type. I've taken a liking to a trackball and it really does need to be on the front face under the LCD.

Giggles 312
16th November 2009, 03:56 AM
yeah im thinking about getting the eris around income tax time, unless they release something better by then.... for now my vogue is doing me just fine

i 200% cant agree with you more :D

enatefox
20th November 2009, 08:58 PM
Just to throw this out there. Having issues with booting Eclair and while I have a Kaiser, thought I'd share the logcat while it crashes at the boot screen in case it helps or someone can help

zenulator
21st November 2009, 12:55 AM
Just to throw this out there. Having issues with booting Eclair and while I have a Kaiser, thought I'd share the logcat while it crashes at the boot screen in case it helps or someone can help

Those errors are because of libaudio.so and libaudioflinger.so not being able to load causing other dependent libraries not to load.

I have a couple working builds of Éclair laying around they just need the rootfs to be updated and libaudio.so and libhtcgeneric-ril.so needs to be recompiled in the Éclair branch. If nobody else does it I'll try to get around to it this weekend.

Right now most images from the dream and sapphire builds will boot if you use the init.donut.rc and rename it sysinit.rc (sysinit.kaiser.rc for you) and modify it to read
export LD_LIBRARY_PATH /system/lib
and put it in /system along with a blank file in /system named custom.build
All the images I've tested so far will boot this way with out modification.

Eventually we will need an eclair folder in rootfs/lib/ to house the new libaudio.so, libaudioflinger.so and libhtcgeneric-ril.so and then we can just rename the init.donut.rc to init.eclair.rc and modify it to point to the new eclair lib folder in the rootfs.img. Eclair is also using bluetoothd so some other changes will be necessary but for the most part basic functionality on par with donut can be achieved this weekend if someone is willing to put forth the effort.

aven_soulgazer
21st November 2009, 02:14 AM
I wish I knew how. I have a feeling that I've got some extra time on my hands this weekend.

Is there anything to note with running 2.0 over 1.6 other than the maps and youtube?

zenulator
21st November 2009, 02:25 AM
I wish I knew how. I have a feeling that I've got some extra time on my hands this weekend.

Is there anything to note with running 2.0 over 1.6 other than the maps and youtube?

Built in exchange support, process explorer, new lock screen, newer browser, cosmetic enhancements and several others.

jamezelle
21st November 2009, 02:37 AM
i didnt know it had a process explorer!!! awesome

Shidell
21st November 2009, 02:52 AM
Eclair is also using bluetoothd so some other changes will be necessary but for the most part basic functionality on par with donut can be achieved this weekend if someone is willing to put forth the effort.

You mean modifying the 1.5/1.6 drivers that devs have already created to work with 2.0?

If that's the case, I'd be willing to lend a hand with the C modifying. I just haven't had time to set up a VM with *nix to install and play with Android specifically.

vogue-droid
21st November 2009, 05:55 AM
i think it will work if you just pull the master branch from the android source code and put the code for the libs from github and sourceforge in the right places and compile it. it's worth a shot from what i hear a semi working 2.0 android thats pretty much running about the same as the current donut builds. but what do i know? then you could get upload rights from vilord to the rootfs repo and edit the init.donut.rc like zen said and also add those new libs to /lib/eclair. i bet zen would release the new 2.0 build he's been holding out on.

enatefox
21st November 2009, 01:36 PM
Well, I did everything like you said but still crashes I guess from libaudio, etc. Seems I still just got hardware stubs despite hand editing (my problem?) Donut audio into Eclair. Guess I'll try again.

sshark
21st November 2009, 04:45 PM
I have a very good feeling about this vogue-droid guy and eclair.:):):D

i think it will work if you just pull the master branch from the android source code and put the code for the libs from github and sourceforge in the right places and compile it. it's worth a shot from what i hear a semi working 2.0 android thats pretty much running about the same as the current donut builds. but what do i know? then you could get upload rights from vilord to the rootfs repo and edit the init.donut.rc like zen said and also add those new libs to /lib/eclair. i bet zen would release the new 2.0 build he's been holding out on.

TheKartus
21st November 2009, 08:14 PM
I have a very good feeling about this vogue-droid guy and eclair.:):):D

Yeah... hopefully.

sshark
22nd November 2009, 07:29 AM
At least a build with voice/data would be good :)

cbaty08
23rd November 2009, 07:40 PM
At least a build with voice/data would be good :)

I can't wait for this :)

My friends will be very jealous!!!

JeckyllHavok
25th November 2009, 08:07 PM
anyone tried to port this rom:
http://forum.xda-developers.com/showthread.php?t=589344

Is it a true Eclair build or just a cupkake/donut build with eclair features? If yes this could work on our devices, too.

KERKEDAGAIN
25th November 2009, 08:55 PM
anyone tried to port this rom:
http://forum.xda-developers.com/showthread.php?t=589344

Is it a true Eclair build or just a cupkake/donut build with eclair features? If yes this could work on our devices, too.

seeems to be true blue Eclair...i'm assuming that's what AOSP means

jamezelle
25th November 2009, 10:42 PM
it is true eclair straight from the master-branch(eclair) from the Android Open Source Project

it isnt really worth porting yet though:rolleyes:

cbaty08
25th November 2009, 11:59 PM
Hey guys, noob again.

Just dropping in to see what the latest was on this...

Curious how far all your hard work has gotten you all regarding data and voice?

Godspeed Gentlemen!

JeckyllHavok
26th November 2009, 12:41 AM
it is true eclair straight from the master-branch(eclair) from the Android Open Source Project

it isnt really worth porting yet though


:( I think mor donuts to eat for now. Can't await some eclairs:D

pelton
26th November 2009, 02:23 PM
I suggest you guys try the new winmo 6.5 with a Samsung Omnia or the HTC phones. Great functionality and you will certainly appreciate the inbuilt social networking features

enatefox
26th November 2009, 05:45 PM
Win Mob 6.5
why would you bother posting

sshark
26th November 2009, 06:38 PM
why would you bother posting

I like it, cool down buddy. May be a lost soul in wrong place :D

ajclai08
26th November 2009, 09:45 PM
I suggest you guys try the new winmo 6.5 with a Samsung Omnia or the HTC phones. Great functionality and you will certainly appreciate the inbuilt social networking features

i think this guy works for M$...

aven_soulgazer
27th November 2009, 10:12 PM
I don't think he understands that we might be tired of WinMo. I hate the 6.5. I wouldn't spend the several hundred dollars it'd take for me to get the Touch Pro 2 which is my only real choice on sprint. I don't have money for upgrading phones very often and I really like Android so I'm biding my time waiting for a good Android phone to come to sprint, though it's probably a lost cause. The two they have are still running 1.5, while I'm running 1.6 on my old vogue and shortly 2.0. Might not have wifi or sensors, but it's still better than winmo to me.

I much appreciate all the development work done to get android running on the vogue

160bpm
28th November 2009, 12:23 AM
I suggest you guys try the new winmo 6.5 with a Samsung Omnia or the HTC phones. Great functionality and you will certainly appreciate the inbuilt social networking features


WinMo is so 2006 :D
Android is so back to the Future :)

thoughtlesskyle
28th November 2009, 05:14 AM
I don't think he understands that we might be tired of WinMo. I hate the 6.5. I wouldn't spend the several hundred dollars it'd take for me to get the Touch Pro 2 which is my only real choice on sprint. I don't have money for upgrading phones very often and I really like Android so I'm biding my time waiting for a good Android phone to come to sprint, though it's probably a lost cause. The two they have are still running 1.5, while I'm running 1.6 on my old vogue and shortly 2.0. Might not have wifi or sensors, but it's still better than winmo to me.

I much appreciate all the development work done to get android running on the vogue

the moment runs donut, and the hero prolly will get a 2.0 update i know its already in the works

jamezelle
28th November 2009, 05:19 AM
the moment runs donut, and the hero prolly will get a 2.0 update i know its already in the works

Correction hero will get a 2.1 update ;)

aven_soulgazer
28th November 2009, 11:47 AM
the moment runs donut, and the hero prolly will get a 2.0 update i know its already in the works

When did the Moment get 1.6? I was in the store two weeks ago and their display was running 1.5 and when I polled for an update it said none available.

zenulator
28th November 2009, 12:13 PM
2.1 is coming. It's already been leaked by someone at htc and a couple devs have it.;)

thoughtlesskyle
28th November 2009, 02:23 PM
When did the Moment get 1.6? I was in the store two weeks ago and their display was running 1.5 and when I polled for an update it said none available.

since i started reading about the moment pretty much everything i saw on it said it was running a 1.6 build, they could have been wrong i dont own one so i cant really say for sure

also store set ups can usually be wrong, i used to work at one and for the longest time it said the centro had build in turn by turn GPS, and some other little stuff

Shidell
28th November 2009, 07:45 PM
2.1 is coming. It's already been leaked by someone at htc and a couple devs have it.;)

What are the changes? Is there a changelog somewhere?

jamezelle
28th November 2009, 07:52 PM
What are the changes? Is there a changelog somewhere?

here (http://www.informationweek.com/blog/main/archives/2009/10/android_20_chan.html;jsessionid=SOO3U23N1GEPJQE1GH RSKH4ATMY32JVN?cid=nl_IW_daily_html) is an unofficial 2.0 changelog

this (http://www.unwiredview.com/2009/11/04/google-hard-at-work-on-android-2-1/) tells a little bit about 2.1 its pretty much bug fixes for 2.0

Shidell
28th November 2009, 07:59 PM
Thanks Jamezelle :)

aven_soulgazer
28th November 2009, 11:51 PM
since i started reading about the moment pretty much everything i saw on it said it was running a 1.6 build, they could have been wrong i dont own one so i cant really say for sure

also store set ups can usually be wrong, i used to work at one and for the longest time it said the centro had build in turn by turn GPS, and some other little stuff

I meant I was playing with the phone itself, went to settings, system. It said it was running 1.5 and there's a menu item to check for newest updates and said there were no new updates. From what I've read since the Moment release it's running 1.5 with no official word if it'll be getting 1.6 or 2.0 or skip to 2.1 or not get jack

forkspoon
29th November 2009, 03:32 PM
Link is broken... no permissions.

zenulator
29th November 2009, 11:23 PM
I don't have a link to the build in the original post. If someone else has it I'll put it up.

160bpm
30th November 2009, 12:34 AM
I was looking on "usenet" and they have most a HTC HERO Eclair Android 2.0 beta build rom...

zenulator
30th November 2009, 12:51 AM
I was looking on "usenet" and they have most a HTC HERO Eclair Android 2.0 beta build rom...

Yes several devs have it on xda it's water marked and not a full rom although it is 2.0. There is also a 2.1 image floating around.

Eclair builds work fine on the vogue we just need libaudio and libhtcgeneric-ril.so rebuilt for it so you can get audio and data working and then update the rootfs.

zenulator
13th December 2009, 07:12 PM
expect a new release later tonight or tomorrow with working calls/data/audio/gps.

deathpod
13th December 2009, 07:15 PM
Looking forward to it for sure! Zen, you're the greatest.

crackeyes
13th December 2009, 07:15 PM
expect a new release later tonight or tomorrow with working calls/data/audio/gps.

Ah sweet been waiting for this. Ill be waiting.......:D

TheKartus
13th December 2009, 08:41 PM
expect a new release later tonight or tomorrow with working calls/data/audio/gps.

Awesome. Can you make sure to post flashable images along with a squashfs file for not being flashed?

sshark
13th December 2009, 08:41 PM
Awesome just awesome!

zenulator
13th December 2009, 09:28 PM
thank vilord he's working on the libs. i just dropped them into my eclair build and looks like it's working pretty good. the same ones work for the eclair hero build so look for that soon too.

kr4zyc1d
13th December 2009, 09:38 PM
Where are the updated 2.0 build files located? I have 1.6 now, but would love to take a look at 2.0 and play around with that. I saw, Zen, that you were going to be updating them today or tonight. I found the updated site on sourceforge (Android on HTC) but those were updated on 12/5/09. Is that 1.6 or 2.0? I have been thinking of doing a refresh and want to try out a new version! Great work so far on this guys! Keep up the great work.

Matt

JeckyllHavok
13th December 2009, 11:33 PM
Oh god, guys you are unbelieveable......

Hunger for eclairs..

sshark
14th December 2009, 02:05 AM
Any idea when this is coming, I am excited and can have phone ready for the week before going to bed :-p

mssmison
14th December 2009, 02:13 AM
Eclair and Hero Eclair should be out soon ;)

sshark
14th December 2009, 02:20 AM
Eclair and Hero Eclair should be out soon ;)

Ok thanks.

TheKartus
14th December 2009, 03:54 AM
Eclair and Hero Eclair should be out soon ;)

My anticipation is killing me.

anotherhawkeye
14th December 2009, 04:14 AM
My anticipation is killing me.

Tell me about it. I have been checking this thread every 30 minutes. Lol.

deathpod
14th December 2009, 04:18 AM
Tell me about it. I have been checking this thread every 30 minutes. Lol.

Do yourself a favor and subscribe to the thread. IF your running android and IF your email address on file with xda-developers is the gmail account tied to your phone and IF you have background data / auto-sync enabled, the thread comes to you! :)

zenulator
14th December 2009, 04:21 AM
ok i'm posting this from eclair running from nand. it's using a modified rootfs.gmail, gtalk, market, maps with gps all work. new slide to unlock. i have two versions. one is generic and one is pretty much looks like the droid. both are eclair 2.0.1. i'll have the generic builld up later tonight.

deathpod
14th December 2009, 04:23 AM
Just pooped my pants!

loserskater
14th December 2009, 04:25 AM
ok i'm posting this from eclair running from nand. it's using a modified rootfs.gmail, gtalk, market, maps with gps all work. new slide to unlock. i have two versions. one is generic and one is pretty much looks like the droid. both are eclair 2.0.1. i'll have the generic builld up later tonight.

Im assuming you are going to be posting the modified rootfs as well?

tatnai
14th December 2009, 04:36 AM
i guess I'll find out by trial and error, but zen do you know off hand if we have to boot with resolution 320x480 first to get all market apps showing like we do in donut? you know what, don't bother answering, i'll know after you post it anyways - would rather get it 2 minutes earlier and try myself anyways :)

salivating. . .

TheKartus
14th December 2009, 04:59 AM
ok i'm posting this from eclair running from nand. it's using a modified rootfs.gmail, gtalk, market, maps with gps all work. new slide to unlock. i have two versions. one is generic and one is pretty much looks like the droid. both are eclair 2.0.1. i'll have the generic builld up later tonight.

Are you also posting a regular squashfs file? Don't leave us that have no flashed behind in the dust...

tatnai
14th December 2009, 05:15 AM
Are you also posting a regular squashfs file? Don't leave us that have no flashed behind in the dust...

system.sqsh should work either way, would be rootfs that would need different versions for nand vs sdcard, if I understand things correctly.

loserskater
14th December 2009, 05:20 AM
system.sqsh should work either way, would be rootfs that would need different versions for nand vs sdcard, if I understand things correctly.

He can either post the .sqsh or a .nbh thats ready for flashing. Im sure he will post the .sqsh so that you can boot through haret or load it into nand yourself.

tatnai
14th December 2009, 05:32 AM
He can either post the .sqsh or a .nbh thats ready for flashing. Im sure he will post the .sqsh so that you can boot through haret or load it into nand yourself.

true, but so far no one has placed the sqsh file in the .nbh file, we've kept them separate like dinner and dessert :D

TheKartus
14th December 2009, 05:33 AM
He can either post the .sqsh or a .nbh thats ready for flashing. Im sure he will post the .sqsh so that you can boot through haret or load it into nand yourself.

That would make both camps satisfied.

polyrhythmic
14th December 2009, 05:37 AM
I. am. stoked.

plemen
14th December 2009, 05:38 AM
ok i'm posting this from eclair running from nand. it's using a modified rootfs.gmail, gtalk, market, maps with gps all work. new slide to unlock. i have two versions. one is generic and one is pretty much looks like the droid. both are eclair 2.0.1. i'll have the generic builld up later tonight.
I would love a how-to when the dust settles. I've been trying to get eclair to boot for the past few days with some movement but no full boot...

plemen
14th December 2009, 06:00 AM
system.sqsh should work either way, would be rootfs that would need different versions for nand vs sdcard, if I understand things correctly.

I had thought they were different too but as it turns out the rootfs is the same for both nand and haret boot... so everything is the same (system.sqsh, rootfs.sqsh, data.img) between the different boots - the big difference is that nand boot requires the squish to be below 90mb decompressed (around 45-50mb compressed).

tatnai
14th December 2009, 06:03 AM
I had thought they were different too but as it turns out the rootfs is the same for both nand and haret boot... so everything is the same (system.sqsh, rootfs.sqsh, data.img) between the different boots - the big difference is that nand boot requires the squish to be below 90mb decompressed (around 45-50mb compressed).

hmm, we're now OT but I was confused because dzo posted the new rootfs when he posted the nand stuff. assuming he dumped something new in there, but it still has all the stuff to run it off haret. probably old rootfs works only with haret, new one works with both.

TheKartus
14th December 2009, 06:05 AM
hmm, we're now OT but I was confused because dzo posted the new rootfs when he posted the nand stuff. assuming he dumped something new in there, but it still has all the stuff to run it off haret. probably old rootfs works only with haret, new one works with both.

OT is fine to keep occupied until the big moment

deathpod
14th December 2009, 06:06 AM
I thought his most recent nbh's (as in uploaded today) were to include the updated zImage, but I may be completely wrong.

** Zen, we're friggin' pumped!

tatnai
14th December 2009, 06:10 AM
I thought his most recent nbh's (as in uploaded today) were to include the updated zImage, but I may be completely wrong.

** Zen, we're friggin' pumped!

yeah, new rootfs as in the original one posted with the first .nbh files that were released.

exodus409
14th December 2009, 06:24 AM
It feels like it's christmas eve!

tatnai
14th December 2009, 06:31 AM
this is killing me, I can't get any work done in between checking back here every 30 seconds.

vilord
14th December 2009, 07:54 AM
gah, I'm annoyed at u Zen!
I sent all those updated libraries to get audio and Radio working, and now I see you put my libraries to good use... but, you didn't post! :( :( :(

jamezelle
14th December 2009, 07:57 AM
gah, I'm annoyed at u Zen!
I sent all those updated libraries to get audio and Radio working, and now I see you put my libraries to good use... but, you didn't post! :( :( :(

you ready for eclair hero. "give me the go ahead" and i will post it credits to you and mssmison. :)

tatnai
14th December 2009, 07:58 AM
getting hot in here :o

TheKartus
14th December 2009, 07:59 AM
you ready for eclair hero. "give me the go ahead" and i will post it credits to you and mssmison. :)

Hows the speed comparable to sensehero?

vilord
14th December 2009, 08:30 AM
hey sorry dude, I can't give you permission to post mssmison's eclair hero... only he can do that :)
It is *really* slow on my device, but I never ran sensehero, so, I have nothing to compare to. I also didn't put in in flash, running from sqsh, so that may be most of the slowness...

I'd rather straight up eclair from Zen...

jamezelle
14th December 2009, 08:31 AM
Hows the speed comparable to sensehero?

well its pretty snappy, I havent tested it to hard though but rosie is pretty smooth.

TheKartus
14th December 2009, 08:32 AM
hey sorry dude, I can't give you permission to post mssmison's eclair hero... only he can do that :)
It is *really* slow on my device, but I never ran sensehero, so, I have nothing to compare to. I also didn't put in in flash, running from sqsh, so that may be most of the slowness...

I'd rather straight up eclair from Zen...

If you liked Hero, you should try the sensehero build. It runs at a very reasonable speed even for everyday use. Its nice.

moekind
14th December 2009, 08:36 AM
Vilord I know your the Radio expert. I was wondering if the call waiting issue is going to be fixed anytime soon. Switching in between calls, still doesn't work.

vilord
14th December 2009, 08:41 AM
yeah i don't like hero... i guess i'd say that eclair hero is about the same speed as regular hero/sensehero or whatever... not for me, but some folks really like it :D

We'll see when official eclair hero comes out maybe it'd work for me then, but I'm thinking i'll likely stick with the straight up clean builds, I like me a speedy phone :D

vilord
14th December 2009, 08:43 AM
Vilord I know your the Radio expert. I was wondering if the call waiting issue is going to be fixed anytime soon. Switching in between calls, still doesn't work.
oh right, switching between calls... I'll have to do some more investigation, maybe try to get that to function with the CDMA radio and get a radio log... I'll put it back on my list

zenulator
14th December 2009, 11:27 AM
well i ran into some force closes and other odd bugs in the generic build. i'll post it after i get those worked out..

zenulator
14th December 2009, 01:16 PM
dupe............

zenulator
14th December 2009, 01:21 PM
looks like the libaudio.so causes the phone to reboot after trying to make a call. other than that everything is running good. since the libs have to be in /system/lib i'm not going to post anything until it gets fixed or else i'd have to upload a totally new build for the fix. i'm on a 3G connection so i need to keep uploads to a minimum.

djp3k05
14th December 2009, 01:40 PM
take your time, no rush!

zenulator
14th December 2009, 04:01 PM
ok i'm uploading the build and rootfs.img for it. the rootfs.img should work for both the eclair-hero and my generic eclair.

anotherhawkeye
14th December 2009, 04:08 PM
ok i'm uploading the build and rootfs.img for it. the rootfs.img should work for both the eclair-hero and my generic eclair.

After all the wait overnight, its finally happening...:) I haven't been this excited on a Monday in a long time.

kr4zyc1d
14th December 2009, 04:26 PM
I might be stupid, but I cannot find the link to where they are posted. The one on sourceforge has a basefiles zip that is dated a month or so ago. Anyone have the new link?! Thanks man, great work!

Matt

zenulator
14th December 2009, 04:28 PM
I might be stupid, but I cannot find the link to where they are posted. The one on sourceforge has a basefiles zip that is dated a month or so ago. Anyone have the new link?! Thanks man, great work!

Matt

http://forum.xda-developers.com/showpost.php?p=4828030&postcount=1

kr4zyc1d
14th December 2009, 04:31 PM
http://forum.xda-developers.com/showpost.php?p=4828030&postcount=1

Thanks Zen

hellovx7600
14th December 2009, 04:51 PM
Is there a specific eclair.user.conf that we should be using?

zenulator
14th December 2009, 04:53 PM
Is there a specific eclair.user.conf that we should be using?

right now it's using the hero one. although i'm not running with any swap/compcache or renice and it's running fine.

Shidell
14th December 2009, 04:57 PM
Is there a specific data.img file I should be using for this build?

hellovx7600
14th December 2009, 05:00 PM
Thanks Zen! I <3 you!

CyCLoBoT
14th December 2009, 05:06 PM
Do I still use the same basefile package that were posted on the Vogue Android site?

zenulator
14th December 2009, 05:17 PM
Do I still use the same basefile package that were posted on the Vogue Android site?

It should work.

anotherhawkeye
14th December 2009, 05:18 PM
Using it now. Its a little slow (sensehero slow) and getting lot of force closes. But everything I tried has worked so far.

CyCLoBoT
14th December 2009, 05:20 PM
Using it now. Its a little slow (sensehero slow) and getting lot of force closes. But everything I tried has worked so far.

Did you try bluetooth as well? I didn't see it on the list whether its working or not.

kr4zyc1d
14th December 2009, 05:27 PM
This is great stuff, it is pretty quick as well. I did notice a few things. The only force close I came across was trying to change the ringer volume in the sound and display settings page. Also, the speaker is acting up when it makes notification rings, such as volume up/down, receiving a text and some other things. I listened to a google voice mail that I had and noticed the same issues. I made a phone call however, and it sounded fine however, but could not put the phone into speakerphone mode. Anyway, really great work, I'm sure more is to come! Good job!

Matt

JeckyllHavok
14th December 2009, 05:33 PM
Hey Zen, can you tell me how to edit files in rootfs.img?

TheKartus
14th December 2009, 05:40 PM
Gonna pull out my SD card adapter in my history class to load this up.

The choice of paying attention to the review for the final or loading Eclair on my phone is not difficult.

plemen
14th December 2009, 05:49 PM
Hey Zen, can you tell me how to edit files in rootfs.img?

mount it to a dir, modify what you like, unmount

1) mkdir rootfs_mount
2) mount -o loop rootfs.img rootfs_mount

polyrhythmic
14th December 2009, 06:05 PM
My device stops here during boot:

A N D R O I D
init: unable to open persistent property directory /data/property errno: 2

I'll try swapping some files around to see if anything works.

hellovx7600
14th December 2009, 06:07 PM
I'm having issues getting my account added. When I go to add a new account, it only has corporate and facebook.

JeckyllHavok
14th December 2009, 06:09 PM
mount it to a dir, modify what you like, unmount

1) mkdir rootfs_mount
2) mount -o loop rootfs.img rootfs_mount

Thanks, i forgot that i mounted it from root terminal and then tried to modify with normal user...it's late...and i go home now:D

JeckyllHavok
14th December 2009, 06:12 PM
I'll try swapping some files around to see if anything works.

There was no init,eclair.kaiser.rc in rootfs. I've added it and now i'll test. (just rename init.eclair.rc to init.eclair.kaiser.rc. When i come home i'll upload it

But therefore i'll open a new thread in kaiser forum, cause even if here are the geniuses we are in the wrong forum

polyrhythmic
14th December 2009, 06:27 PM
Good call, I had suspected that also but the errors scroll by really fast! I modified my rootfs and am happy to be the first to report Eclair booting on Kaiser!!

However, I got a black screen where the Android boot logo usually is, but I watched it boot through adb.

EDIT: Data works on first boot, I get some FC's on some settings, but overall it looks awesome -- especially the lockscreen :D. Thanks again guys!!!!!!!!!!!!!

moekind
14th December 2009, 06:29 PM
Can someone post an empty data.img file, I cant log into my google account.

TheKartus
14th December 2009, 07:01 PM
Good call, I had suspected that also but the errors scroll by really fast! I modified my rootfs and am happy to be the first to report Eclair booting on Kaiser!!

However, I got a black screen where the Android boot logo usually is, but I watched it boot through adb.

EDIT: Data works on first boot, I get some FC's on some settings, but overall it looks awesome -- especially the lockscreen :D. Thanks again guys!!!!!!!!!!!!!

I think I'm getting a black screen too after the linux scroll. I'm gonna give my phone a few more minutes before I try to boot again, or I hook it up to adb and see whats up.

plemen
14th December 2009, 07:02 PM
Can someone post an empty data.img file, I cant log into my google account.

Here you go:

http://www.mediafire.com/file/yzzwdmyntmy/blank_data.zip

polyrhythmic
14th December 2009, 07:14 PM
I think I'm getting a black screen too after the linux scroll. I'm gonna give my phone a few more minutes before I try to boot again, or I hook it up to adb and see whats up.

I freaked out for a second but as soon as I started watching the adb logs I saw it was going through the normal boot process. It looks like the screen is ON, just black.

Well for all us Kaiser users I started an Eclair thread (http://forum.xda-developers.com/showthread.php?p=5144644) in the Kaiser forum so we can sort things out appropriately. I've posted the modified rootfs.img for Kaiser there as well.

moekind
14th December 2009, 07:27 PM
Thanks Plemen, I can login now!

zenulator
14th December 2009, 07:27 PM
The android bootscreen doesn't show it's just black so you have to wait for it. Anyone have problems with calls or audio?

I've been having trouble with outgoing calls on both builds I have. The phone reboots after attempting to make a call. I didn't happen at first and thats why I released this build.

TheKartus
14th December 2009, 07:28 PM
Yeah, it eventually boots up. Slightly slow in the beginning, but seems to work fine. Sound is a little weird through the speaker, there is like a constant buzz out of it when sound starts to when it stops.

The lockscreen makes it all worth it though.

kr4zyc1d
14th December 2009, 07:40 PM
The android bootscreen doesn't show it's just black so you have to wait for it. Anyone have problems with calls or audio?

I've been having trouble with outgoing calls on both builds I have. The phone reboots after attempting to make a call. I didn't happen at first and thats why I released this build.

Making calls is good. I haven't had any problems there, but any audio other than calls coming out of the speaker are all nasty and staticky. I'm not sure if there is a fix for it but just letting you know of the updates.

Matt

plemen
14th December 2009, 07:44 PM
The android bootscreen doesn't show it's just black so you have to wait for it. Anyone have problems with calls or audio?

I've been having trouble with outgoing calls on both builds I have. The phone reboots after attempting to make a call. I didn't happen at first and thats why I released this build.

Works perfectly so far. I can receive and make calls, contacts/gmail synced, gps and market work - no force closes yet.

kr4zyc1d
14th December 2009, 07:45 PM
Works perfectly so far. I can receive and make calls, contacts/gmail synced, gps and market work - no force closes yet.

That is the one thing I can't figure out. How does the GPS work on the vogue? Do I need to have flashed something in order to get the hardware working? Because my location is never found. Any help?

polyrhythmic
14th December 2009, 07:47 PM
I can make calls just fine, and my audio is as clear as day, through the speaker or through the USB headphones adapter.

I am using the newest kernel zImage-11-12-09 (http://it029000.massey.ac.nz/vogue/files/zImage-11-12-09), are y'all?

My problem is that I get Force Close on Brightness and Ringer Volume in the Settings. I can set ringer volume just fine from the home screen. I have a Brightness widget but it's weird that the settings don't work.

KERKEDAGAIN
14th December 2009, 07:49 PM
The android bootscreen doesn't show it's just black so you have to wait for it. Anyone have problems with calls or audio?

I've been having trouble with outgoing calls on both builds I have. The phone reboots after attempting to make a call. I didn't happen at first and thats why I released this build.

i'm not running it from nand yet, but as of right now i'm having no issue making or receiving calls..

TheKartus
14th December 2009, 07:53 PM
Anyone try any other resolutions besides QVGA?
EDIT: Also, anyone have facebook contacts working? I can't get it to show the pictures. In edit contacts, the phone says that "Facebook contact information is not available on this device"

kr4zyc1d
14th December 2009, 08:04 PM
I can make calls just fine, and my audio is as clear as day, through the speaker or through the USB headphones adapter.

I am using the newest kernel zImage-11-12-09 (http://it029000.massey.ac.nz/vogue/files/zImage-11-12-09), are y'all?

My problem is that I get Force Close on Brightness and Ringer Volume in the Settings. I can set ringer volume just fine from the home screen. I have a Brightness widget but it's weird that the settings don't work.


Hey, I downloaded the new zImage from the link, but that doesnt seem to fix the other audio issues. Making calls sounds perfect, but ringtones, and alarms sound bad. Just FYI! Thanks again for the suggestions.

Matt

Edit: I rebuilt my data file using the new zimage and it seems to be working better, no static.

zenulator
14th December 2009, 08:12 PM
Ok i'm taking it down and i'll work on it some more.

KERKEDAGAIN
14th December 2009, 08:18 PM
Anyone try any other resolutions besides QVGA?
EDIT: Also, anyone have facebook contacts working? I can't get it to show the pictures. In edit contacts, the phone says that "Facebook contact information is not available on this device"

running on 320x480..too lazy to change default.txt, heh

Ok i'm taking it down and i'll work on it some more.

I dont think its much of a problem..its very snappy n just has that same crackle we should be accustomed to by now, haaa

TheKartus
14th December 2009, 08:28 PM
running on 320x480..too lazy to change default.txt, heh



I dont think its much of a problem..its very snappy n just has that same crackle we should be accustomed to by now, haaa

Yeah, Im running it at 320x480 too now. The only issue I have run into, isn't a problem with the build, just seems to be an issue with 2.0 where text autocorrection is just pulling in names from my phonebook... turning a world like hi into Julie via autocorrection.

anotherhawkeye
14th December 2009, 08:32 PM
Did you try bluetooth as well? I didn't see it on the list whether its working or not.

For me:

What works:

Calls
Data
Maps/Gps
Exchange /w Direct push (yay)
Gmail
Ringer volume using vol up/down buttons

What doesn't:
Speakerphone
Voice search/recognition
Bluetooth
Navigation (Searching for GPS..., same result as Donut. I think srwalter needs to make a change in the GPS driver to add velocity/accuracy info)
Brightness setting through settings (force closes)

The build was slow when I used ext2. Without ext2, its blazing fast.

TheKartus
14th December 2009, 08:35 PM
For me:

What works:

Calls
Data
Maps/Gps
Exchange /w Direct push (yay)
Gmail

What doesn't:
Speakerphone
Voice search/recognition
Bluetooth
Navigation (Searching for GPS..., same result as Donut. I think srwalter needs to make a change in the GPS driver to add velocity/accuracy info)

The build was slow when I used ext2. Without ext2, its blazing fast.
You gotta give ext2 a while to warm up. Once it gets settled on the build its really very fast with no issues.

Fancy_Lad
14th December 2009, 09:03 PM
Thank you everyone for your hard work - this is amazing!

Using the system image posted earlier, and I'm not having too many problems. Only thing I'm not clear about is Exchange Calendar sync. Reading about it on the Droid, there is a separate application to do this called "Corporate Calendar" that does the Exchange calendar... I'm not clear on if this is something that is included in Eclair or if it is a Motorola addin. Anyone able to shed some light on this?

Full Exchange support is the one thing holding me back from using Android full time :)

sportsterBK8
14th December 2009, 10:41 PM
Is there a way I can hide or delete an app that came built in with this build?
twidroid will never be used on my phone, and if I click on it, it gets stuck in a loop of trying to get me to enter a login name, and since I don't have one, I can't exit.

I have tried app managers, and none of them say that twidroid is installed, so I can't uninstall it.

I know in some older android builds, there was a way to hide apps, so they aren't viewable in the drawer, but I can't find that setting in this 2.0.1 build.


Any Ideas? or can you post a link of this build without the extra apps, so I don't have twidroid on there?

Thanks.

jamezelle
14th December 2009, 10:49 PM
Is there a way I can hide or delete an app that came built in with this build?
twidroid will never be used on my phone, and if I click on it, it gets stuck in a loop of trying to get me to enter a login name, and since I don't have one, I can't exit.

I have tried app managers, and none of them say that twidroid is installed, so I can't uninstall it.

I know in some older android builds, there was a way to hide apps, so they aren't viewable in the drawer, but I can't find that setting in this 2.0.1 build.


Any Ideas? or can you post a link of this build without the extra apps, so I don't have twidroid on there?

Thanks.

you could delete it from /system/app via adb

zenulator
14th December 2009, 11:02 PM
ok so far i've seen just about everyone say that calls work fine. and a few have problems with audio. one person says that they switched to a newer zimage and it cleared audio up. one said that they redid there data.img and had clear audio.

so my question is how many have clear audio? the build is still up i just took the link down so nobody else gets a bad image with crappy audio. voice search/dialer is a problem in the libaudio.so it was the same way with donut until we got the lib fixed.

frad
14th December 2009, 11:19 PM
i guess I'll find out by trial and error, but zen do you know off hand if we have to boot with resolution 320x480 first to get all market apps showing like we do in donut? you know what, don't bother answering, i'll know after you post it anyways - would rather get it 2 minutes earlier and try myself anyways :)

salivating. . .

Hi Tatnai.... any word on whether the market apps show up by default with the res set to QVGA? Thanks

polyrhythmic
14th December 2009, 11:22 PM
I have always had clear audio, but I also am running a Kaiser.

plemen
14th December 2009, 11:36 PM
ok so far i've seen just about everyone say that calls work fine. and a few have problems with audio. one person says that they switched to a newer zimage and it cleared audio up. one said that they redid there data.img and had clear audio.

so my question is how many have clear audio? the build is still up i just took the link down so nobody else gets a bad image with crappy audio. voice search/dialer is a problem in the libaudio.so it was the same way with donut until we got the lib fixed.

Had clear audio from the beginning...

zenulator
15th December 2009, 12:27 AM
I put the link back up. I'm running it now from the squashfs image with a new data.img and have clean audio and calls seem fine. The only other thing I would suggest is to turn down compcache in the hero.user.conf to no more than 24MB. You can turn compcache off and it still runs fine.

kr4zyc1d
15th December 2009, 12:43 AM
ok so far i've seen just about everyone say that calls work fine. and a few have problems with audio. one person says that they switched to a newer zimage and it cleared audio up. one said that they redid there data.img and had clear audio.

so my question is how many have clear audio? the build is still up i just took the link down so nobody else gets a bad image with crappy audio. voice search/dialer is a problem in the libaudio.so it was the same way with donut until we got the lib fixed.

Hey Zen, I have clear audio, but I had to use the new zImage posted earlier, and I had to rebuild the data file. (I had updated the zImage without making a new data file and it didn't work, so I created a new data file and it did). Everything is working well, I still have a problem with my GPS, but not sure what to do there. Great work again.

Matt

kr4zyc1d
15th December 2009, 01:09 AM
the only other thing I noticed, and I'm not sure if this is because I haven't given it a full charge yet, but it is eating my battery away very quickly. Anyone else having this problem?

Giggles 312
15th December 2009, 01:12 AM
Hey Zen ...




I <3 You TOO!

p.s. awesome. thank you so much! i'm proud to say my vogue is now offically running android, and android alone!

one tiny comment the lock screen is a nice slide over, not like the droid's turn thing. but as i type this i realised that maybe its a certain thing for the droid. i dunno, but i love this build. THANKS!

bri3d
15th December 2009, 01:24 AM
the only other thing I noticed, and I'm not sure if this is because I haven't given it a full charge yet, but it is eating my battery away very quickly. Anyone else having this problem?

Are you using Facebook? Both the Facebook app and Facebook sync services seem to kill the CPU, head into swap, and garbage collect all the time (thus killing the battery) for me.

Facebook contact merge also breaks all my contacts - I hear it's somewhat flaky on real 2.0/2.0.1 devices too.

With data disabled when not in use and Facebook disabled entirely my battery seems roughly similar to Donut with the same practices, although I haven't done any hard testing or had much time on it yet.

tatnai
15th December 2009, 01:39 AM
Hi Tatnai.... any word on whether the market apps show up by default with the res set to QVGA? Thanks
haven't had a chance to load it, been working too hard :mad:
Hey Zen, I have clear audio, but I had to use the new zImage posted earlier, and I had to rebuild the data file. (I had updated the zImage without making a new data file and it didn't work, so I created a new data file and it did). Everything is working well, I still have a problem with my GPS, but not sure what to do there. Great work again.

Matt

If GPS is getting your location, then GPS is working - we've never had velocity or accuracy information, this is how it has been in cupcake all along. So yeah, Google navigation only really adds that the screen stays awake while navigating, not much more right now. We'll have to wait until someone gets an itch to do more . . . considering starting a BOUNTY thread against my personal values . . .

TheKartus
15th December 2009, 01:45 AM
Hey Zen ...




I <3 You TOO!

p.s. awesome. thank you so much! i'm proud to say my vogue is now offically running android, and android alone!

one tiny comment the lock screen is a nice slide over, not like the droid's turn thing. but as i type this i realised that maybe its a certain thing for the droid. i dunno, but i love this build. THANKS!

The turn lock screen thing you are talking about no longer exists on the Droid. The lockscreen we have is the same the droid has with the 2.0.1 update.

zenulator
15th December 2009, 01:50 AM
Turn off sync to avoid the power drain. I left it on last night and forgot to plug it in fell asleep and woke up a couple hours later to a dead phone. Also make sure GPS is turned off when not in use that causes drain too.

Giggles 312
15th December 2009, 01:54 AM
The turn lock screen thing you are talking about no longer exists on the Droid. The lockscreen we have is the same the droid has with the 2.0.1 update.

ahh well then i have no more complaints. :D awesome build Zen.

kr4zyc1d
15th December 2009, 01:55 AM
haven't had a chance to load it, been working too hard :mad:


If GPS is getting your location, then GPS is working - we've never had velocity or accuracy information, this is how it has been in cupcake all along. So yeah, Google navigation only really adds that the screen stays awake while navigating, not much more right now. We'll have to wait until someone gets an itch to do more . . . considering starting a BOUNTY thread against my personal values . . .

No, GPS is not getting my location. I can enable GPS in the settings, but Google Maps cannot get my location. It hasn't worked for any of the versions I have had. Is there some flashing I need to do? Or something other than just clicking it on?

Also, I stopped the Facebook sync, and left my gmail sync on (as it had been in my other versions) and I will give this a try over the next 24 hours. Thanks for the updates and help.

dclay89
15th December 2009, 02:17 AM
No, GPS is not getting my location. I can enable GPS in the settings, but Google Maps cannot get my location. It hasn't worked for any of the versions I have had. Is there some flashing I need to do? Or something other than just clicking it on?

Also, I stopped the Facebook sync, and left my gmail sync on (as it had been in my other versions) and I will give this a try over the next 24 hours. Thanks for the updates and help.

I have the same problem with GPS not getting my location.

enatefox
15th December 2009, 02:24 AM
Thanks for getting this going further. I needed the mods for Kaiser which I had never figured out on my own but it's working now. I only did outbound calling and the audio is perfect (edit: and media audio is perfect too), the call connected instantly.. this is very stable from my minimal testing so far.

Guess I'll see what I can do with it now to help out.

sshark
15th December 2009, 02:49 AM
Good and quality job Zen!

Using DZO 14-12-2009 .nbh kernel and rootfs/eclair system provided by Zen, using old data file from Donut (dalvik-cache cleared) I have following:

1- Calls (normal audio quality, # frequency of hang-ups compared to Donut is reduced)
2- Data (normal - works)
3- Audio (normal - music using Pandora, speakerphone, ringer)
4- GPS (normal as Donut, gets location but navigation is not active)
5- Gmail (normal - works)
6- Contacts (normal - works)
7- Facebook (normal - works)
8- Exchange (email only works)

5- Camera (no app found, not working)
6- Google calendar (not found, not working)
7- Exchange calendar (not found, not working)


My question is, can we get calendar app somewhere and get it syncing/working, I need calendar badly!

bri3d
15th December 2009, 03:01 AM
Depending on if srwalter gets back to me or is already working on it I'll see what I can whip up for GPS speed/direction this weekend when I've got some time - thing is, I don't have time to debug the winmo driver and find the right data off the chipset (if it's there) so I'd just use great circle formulas / Haversine to interpolate between last 2 updates, and it might not be super fast.

sportsterBK8
15th December 2009, 03:07 AM
you could delete it from /system/app via adb

is there a trick to this?

once connected to adb with this build I have gone into system/app/com.twidroid.apk

and deleted that file, it says it has been deleted and refreshes, only to show that file still there...


So I still can't get twidroid off my phone while keeping this build.


anything I'm missing?

kr4zyc1d
15th December 2009, 03:08 AM
Depending on if srwalter gets back to me or is already working on it I'll see what I can whip up for GPS speed/direction this weekend when I've got some time - thing is, I don't have time to debug the winmo driver and find the right data off the chipset (if it's there) so I'd just use great circle formulas / Haversine to interpolate between last 2 updates, and it might not be super fast.

So you are saying that it is just a coding thing to get GPS to work on the vogue with android?:confused:

bri3d
15th December 2009, 03:39 AM
So you are saying that it is just a coding thing to get GPS to work on the vogue with android?
Well yeah, GPS already works thanks to srwalter's work, on my Vogue at least. The reason(s) Maps Navigation doesn't work is that it needs direction / speed data in order to figure out which way you're going, because it isn't smart enough otherwise.

So think about it: we know where you are located every x amount of time, meaning we can figure out how fast and in what direction you're going - just a matter of doing the math if the hardware doesn't let us know already.

The issue is that the math is sort of involved because (to simplify) it involves mapping a sphere into a plane, so if the hardware were to tell us instead that would be optimal.

I don't have the time to go prodding around the Windows Mobile drivers (like srwalter did to make things in the first place) to figure out if it does, so my approach is sub-optimal, but it will probably work to some degree or another.

So I guess it's "just a coding thing" (everything is "just a coding thing" in the end).

kr4zyc1d
15th December 2009, 03:42 AM
Well yeah, GPS already works thanks to srwalter's work, on my Vogue at least. The reason(s) Maps Navigation doesn't work is that it needs direction / speed data in order to figure out which way you're going, because it isn't smart enough otherwise.

So think about it: we know where you are located every x amount of time, meaning we can figure out how fast and in what direction you're going - just a matter of doing the math if the hardware doesn't let us know already.

The issue is that the math is sort of involved because (to simplify) it involves mapping a sphere into a plane, so if the hardware were to tell us instead that would be optimal.

I don't have the time to go prodding around the Windows Mobile drivers (like srwalter did to make things in the first place) to figure out if it does, so my approach is sub-optimal, but it will probably work to some degree or another.

So I guess it's "just a coding thing" (everything is "just a coding thing" in the end).

Yeah, I get the math behind it, I was just curious as to how to figure out how to make my GPS work on the vogue. Is there a link to srwalter's work or some files and tutorial that srwalter used in order to make it work? Any info is great. Thanks for the updates.

enatefox
15th December 2009, 03:44 AM
Just another thanks to everyone (zen) for getting this going. Already have Home++ on it, some bugfixes I will post when I get it all looked over with a sober eye. The dialer is almost instant. Can't believe it.

bri3d, either post or pm me or something. I can't help you specifically with GPS drivers but I know math and can probably help optimize the functions. Let me know. I haven't ever had GPS working but I think I need to fix my radio. Either way, I like a challenge so I'm down for the cause.

sportsterBK8, sounds like you're using either the sqsh image or you haven't remounted /system as read-write:
mount -o remount,rw /system
and when you're done:
mount -o remount,ro /system
that will fix it. Yea, it's weird it will "let you" delete some things but it won't really-- there's not enough error reporting in there.

bri3d
15th December 2009, 03:53 AM
Yeah, I get the math behind it, I was just curious as to how to figure out how to make my GPS work on the vogue. Is there a link to srwalter's work or some files and tutorial that srwalter used in order to make it work? Any info is great. Thanks for the updates.

Got it, misunderstood - sorry.

I have no idea why yours isn't working - srwalter's libgps code is right at
http://github.com/srwalter/libgps-vogue and the kernel code is in the usual vogue kernel ( http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue ) but it's incredibly straightforward (that's not to say lots of work didn't go into it) - and it's always worked on my Vogue (I'm using a coKe unlocked GPS bootloader+radio, if that helps).

kr4zyc1d
15th December 2009, 04:07 AM
Got it, misunderstood - sorry.

I have no idea why yours isn't working - srwalter's libgps code is right at
http://github.com/srwalter/libgps-vogue and the kernel code is in the usual vogue kernel ( http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue ) but it's incredibly straightforward (that's not to say lots of work didn't go into it) - and it's always worked on my Vogue (I'm using a coKe unlocked GPS bootloader+radio, if that helps).

No worries. I will take a look at that and see if I have any issues. I tried flashing my vogue a few months back using coke, but I only got half way through. The multi colored screen shows coke but the next part of the flash didn't work, and I have a feeling that's what I need to do to make it work.

Any hints? Thanks!

margosmark
15th December 2009, 04:12 AM
Good and quality job Zen!

Using DZO 14-12-2009 .nbh kernel and rootfs/eclair system provided by Zen, using old data file from Donut (dalvik-cache cleared) I have following:

1- Calls (normal audio quality, # frequency of hang-ups compared to Donut is reduced)
2- Data (normal - works)
3- Audio (normal - music using Pandora, speakerphone, ringer)
4- GPS (normal as Donut, gets location but navigation is not active)
5- Gmail (normal - works)
6- Contacts (normal - works)
7- Facebook (normal - works)
8- Exchange (email only works)

5- Camera (no app found, not working)
6- Google calendar (not found, not working)
7- Exchange calendar (not found, not working)


My question is, can we get calendar app somewhere and get it syncing/working, I need calendar badly!

Google calendar works for me, its installed and in the programs list as calendar.

jamezelle
15th December 2009, 04:14 AM
Google calendar works for me, its installed and in the programs list as calendar.

for me too.

sportsterBK8
15th December 2009, 04:14 AM
No worries. I will take a look at that and see if I have any issues. I tried flashing my vogue a few months back using coke, but I only got half way through. The multi colored screen shows coke but the next part of the flash didn't work, and I have a feeling that's what I need to do to make it work.

Any hints? Thanks!


Do you run on Verizon??
because if you do, then you definitely need to do this
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
in order to get gps working on the xv6900 vogue on any android build.

I upgraded to mr1 windows mobile 6.1 with the valhalla gps fix and got nothing for gps in android, even though I had gps in Windows mobile.
followed those simple steps, 1-4, and have gps working in android 2.0.1 as of yesterday.


If you're not on verizon, then I can't help much, but probably something similar needs to be done.


Best of luck. :]

sportsterBK8
15th December 2009, 04:19 AM
sportsterBK8, sounds like you're using either the sqsh image or you haven't remounted /system as read-write:
mount -o remount,rw /system
and when you're done:
mount -o remount,ro /system
that will fix it. Yea, it's weird it will "let you" delete some things but it won't really-- there's not enough error reporting in there.

Okay, so I didn't read correctly, I am indeed using the sqsh image, is this a read only system in which I cannot delete any values?
And if so, is there any way at all for me to remove twidroid from this build?


Thanks again.

TheKartus
15th December 2009, 04:27 AM
Is the system image on the first page, the original image? or is that the one you did more work on?

kr4zyc1d
15th December 2009, 04:59 AM
Do you run on Verizon??
because if you do, then you definitely need to do this
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
in order to get gps working on the xv6900 vogue on any android build.

I upgraded to mr1 windows mobile 6.1 with the valhalla gps fix and got nothing for gps in android, even though I had gps in Windows mobile.
followed those simple steps, 1-4, and have gps working in android 2.0.1 as of yesterday.


If you're not on verizon, then I can't help much, but probably something similar needs to be done.


Best of luck. :]

Yes, I saw that and only got through part 1 successfully. I will have to run that again and see if I can get it to work once again. But you say that if I run steps 1-4 and then boot android 2.0.1 from the SD card, the GPS should work? Awesome. Thanks a bunch for the help. I'll post back if need be.

sportsterBK8
15th December 2009, 05:04 AM
Yes, I saw that and only got through part 1 successfully. I will have to run that again and see if I can get it to work once again. But you say that if I run steps 1-4 and then boot android 2.0.1 from the SD card, the GPS should work? Awesome. Thanks a bunch for the help. I'll post back if need be.


Yes, 1-4 are all the steps that are necissary on verizon.

You will get GPS, but not assisted GPS, but assisted GPS isn't supported in android builds yet any ways. So the only reason to do step 6 is if you want a faster GPS fix when you're booted into windows, however, I don't know if this may hinder android use of the gps, all I can say for sure is that the first 4 steps will get GPS on the xv6900 on this build with verizon working. :]

look forward to hearing that your gps is up and running.

bri3d
15th December 2009, 05:07 AM
Enabling AGPS in WinMo shouldn't have a negative effect on Android, at least not that I've noticed.

kr4zyc1d
15th December 2009, 05:07 AM
Yes, 1-4 are all the steps that are necissary on verizon.

You will get GPS, but not assisted GPS, but assisted GPS isn't supported in android builds yet any ways. So the only reason to do step 6 is if you want a faster GPS fix when you're booted into windows, however, I don't know if this may hinder android use of the gps, all I can say for sure is that the first 4 steps will get GPS on the xv6900 on this build with verizon working. :]

look forward to hearing that your gps is up and running.


Thanks, I really appreciate all the help. I should know in a day or so.

kr4zyc1d
15th December 2009, 05:10 AM
Is there a better tutorial for doing the steps 1-4?

I had found this one: http://www.atwistedweb.com/xv6900/index.html

and it seems to be similar, however there are some ambiguous steps involved, and forgot what the link was that was directly related to the wiki for it. Thanks again.

sshark
15th December 2009, 05:37 AM
for me too.

thanks both of you for reply, I dont have calendar app in drawer..hmm. May be I will flash again!

kr4zyc1d
15th December 2009, 05:49 AM
I am quite fond of the date widget. It is very nice!

sshark
15th December 2009, 06:12 AM
Does anyone know how to build application drawer? I can see under /system/app calendar app but don't have shortcut for that in the drawer.

I have already cleared dalvik-cache couple of times but to no avail!

sportsterBK8
15th December 2009, 07:24 AM
Does anyone want the
Car Home, and Dock Home
apps for the droid that will run on this build?
I know others can probably do the exact same thing as I did, but if a moderator would tell me if it is within forum rules, I would gladly post the apk's necissary to launch the two docks in this build.


Pretty much makes the droid feel of the build complete, let me know if anyone wants links

thanks.

grktaurus83
15th December 2009, 12:04 PM
...let me know if anyone wants links

There's no way there won't be takers on an offer like that...

I'd say upload it somewhere and link it here. If someone has an issue with it, promptly remove it.

grktaurus83
15th December 2009, 01:47 PM
So just loaded the build up right now... Not bad. Not bad at all.

Noticed that this build doesn't have the "have to press the power button multipled times to wake up the phone" issue that some other builds have. That was never really a big deal, just nice to see it respond immediately. This is probably the fastest I've been able to wake up the phone in any of the builds. Very nice.

Call quality is very clear. Might be the best I've heard in Android so far... Might also be me imagining things since this was an issue being specifically pointed out a few pages back.


Seems like this is out of alpha stage, so I'll drop some bug reports. If you still don't want any bug reports, let me know.


1) I'm getting haptic feedback on the dialer and lock screen even though haptic feedback is turned off in the settings.

2) Getting the forced close issue on ringer volume and brightness (as someone else reported).

3) Auto-correct is using contact names and not the dictionary (also reported before).

4) Buttons in Modem app are slightly distorted (looks like left and right edges are shifted down a pixel, but most likely it's the center that's shifted up).


Haven't really noticed much beyond that in the 30 minutes I've been tinkering with it. Very snappy build. Nicely done, Zen.

kr4zyc1d
15th December 2009, 02:53 PM
So just loaded the build up right now... Not bad. Not bad at all.

Noticed that this build doesn't have the "have to press the power button multipled times to wake up the phone" issue that some other builds have. That was never really a big deal, just nice to see it respond immediately. This is probably the fastest I've been able to wake up the phone in any of the builds. Very nice.

Call quality is very clear. Might be the best I've heard in Android so far... Might also be me imagining things since this was an issue being specifically pointed out a few pages back.


Seems like this is out of alpha stage, so I'll drop some bug reports. If you still don't want any bug reports, let me know.


1) I'm getting haptic feedback on the dialer and lock screen even though haptic feedback is turned off in the settings.

2) Getting the forced close issue on ringer volume and brightness (as someone else reported).

3) Auto-correct is using contact names and not the dictionary (also reported before).

4) Buttons in Modem app are slightly distorted (looks like left and right edges are shifted down a pixel, but most likely it's the center that's shifted up).


Haven't really noticed much beyond that in the 30 minutes I've been tinkering with it. Very snappy build. Nicely done, Zen.



Just read this over and only have one solution: for the haptic feedback, check in spare parts and see if it is checked in there.

I am also getting the force close issue, But I don't use the predictive text, and auto correction isn't enabled. Lastly, the modem app on my phone appears to be alright. Sorry I couldn't have been more help on the other stuff, but hopefully that will work.

kr4zyc1d
15th December 2009, 02:53 PM
Does anyone want the
Car Home, and Dock Home
apps for the droid that will run on this build?
I know others can probably do the exact same thing as I did, but if a moderator would tell me if it is within forum rules, I would gladly post the apk's necissary to launch the two docks in this build.


Pretty much makes the droid feel of the build complete, let me know if anyone wants links

thanks.

I sent a PM last night. Not sure if that is working for me however, it's not keeping any records of it and I don't think people are getting them...

kr4zyc1d
15th December 2009, 02:58 PM
Ok, so as stated earlier I had some battery issues. I turned off Facebook sync, but left my gmail sync on. I let it charge for a full 3.5 - 4 hours before going to bed last night, and woke up to a 30% life phone. I started poking around to see what my battery usage was like and it came up with 72% in Cell standby and 23% in Phone idle. Those were my largest. (this is in settings-phone info- battery use). Then I checked in spare parts - battery history and saw that since the last unplugging, it has been running for 100%. (The top most bar simply said "running"). Either way, I think I will turn off gmail sync today and do a full charge and see if that has any effect on the battery. If not, does anyone have any solutions? Thanks everyone, have a good day.

grktaurus83
15th December 2009, 03:02 PM
Just read this over and only have one solution: for the haptic feedback, check in spare parts and see if it is checked in there.

I am also getting the force close issue, But I don't use the predictive text, and auto correction isn't enabled. Lastly, the modem app on my phone appears to be alright. Sorry I couldn't have been more help on the other stuff, but hopefully that will work.

It was disabled in spare parts when I checked just now and it still did the same. Thanks for the tip though, forgot that the option was also in spare parts.

Yea, the predictive text shows only names. Not sure if it actually auto-corrects using those names since it didn't do that during my first few tests.

vilord
15th December 2009, 03:15 PM
updated rootfs on sourceforge now supports this... modified the memfree values as well, there were conflicting entries, and i picked a middle ground between them.

kr4zyc1d
15th December 2009, 03:25 PM
updated rootfs on sourceforge now supports this... modified the memfree values as well, there were conflicting entries, and i picked a middle ground between them.

Just curious as to what the update was or the "this" is; happy to test!

grktaurus83
15th December 2009, 03:45 PM
Oh, another thing that didn't work was the Calendar widget. It says "Problem loading widget" whenever you add it.

vilord
15th December 2009, 04:48 PM
Just curious as to what the update was or the "this" is; happy to test!
"this" is eclair 2.0.1 from this thread. The update was adding the modified init.**.rc files and updating init.

Sorry I haven't read the whole thread yet, was it reported that the calendarsyncprovider isn't working (or isn't there)? I don't see an option to sync to my work calendar...

lauyanyameric
15th December 2009, 04:59 PM
Hi zen,

is Wifi not working too?

bri3d
15th December 2009, 05:25 PM
It looks like the full sleep state is broken (wakelock issues?) - the LED never goes into amber blink and the Spare Parts power meter sticks with 100% Running for everyone.

polyrhythmic
15th December 2009, 05:26 PM
Wifi does not work on Kaiser, although I assumed this is a seperate issue from Vogue so we have some Kaiser devs working on it.

TheKartus
15th December 2009, 05:42 PM
It was disabled in spare parts when I checked just now and it still did the same. Thanks for the tip though, forgot that the option was also in spare parts.

Yea, the predictive text shows only names. Not sure if it actually auto-corrects using those names since it didn't do that during my first few tests.

It was only auto correcting to the names when I had autocorrection on.

zenulator
15th December 2009, 06:02 PM
updated rootfs on sourceforge now supports this... modified the memfree values as well, there were conflicting entries, and i picked a middle ground between them.

# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.SECONDARY_SERVER_ADJ 2
setprop ro.BACKUP_APP_ADJ 2
setprop ro.HOME_APP_ADJ 4
setprop ro.HIDDEN_APP_MIN_ADJ 7
setprop ro.CONTENT_PROVIDER_ADJ 14
setprop ro.EMPTY_APP_ADJ 15

# Define the memory thresholds at which the above process classes will
# be killed. These numbers are in pages (4k).
setprop ro.FOREGROUND_APP_MEM 1536
setprop ro.VISIBLE_APP_MEM 2048
setprop ro.SECONDARY_SERVER_MEM 4096
setprop ro.BACKUP_APP_MEM 4096
setprop ro.HOME_APP_MEM 4096
setprop ro.HIDDEN_APP_MEM 5120
setprop ro.CONTENT_PROVIDER_MEM 5632
setprop ro.EMPTY_APP_MEM 6144

# Write value must be consistent with the above properties.
# Note that the driver only supports 6 slots, so we have HOME_APP at the
# same memory level as services.
write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15

write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144

# Set init its forked children's oom_adj.
write /proc/1/oom_adj -16

# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5


Those should be the values.

vilord
15th December 2009, 06:14 PM
those are the right values for a device with more ram than ours.... is that what you'd like to use? it will kill off more background apps with the settings i picked, but it'll also run quicker...

bzo
15th December 2009, 06:31 PM
It looks like the full sleep state is broken (wakelock issues?) - the LED never goes into amber blink and the Spare Parts power meter sticks with 100% Running for everyone.

I'm seeing this too. I suppose this is the cause of the battery running down so quickly.