yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] Smobbo:
There are basically two types of WM6.5 which are in use at the moment.

The 21xxx branch refers to WM6.5 as the version that is/will be used by HTC when they update their newer devices.

The 23xxx branch refers to WM6.5 as the version which will eventually become WM7. It has the bigger buttons (and start is also on the bottom). This version is also referred to as WM6.5.1.

The 21xxx branch is the more stable atm, since not all programs can adapt well to the new buttons in the 23xxx branch.

Hope this clarifies it a bit ;)!
[Touch HD Windows Mobile ROM Development] Insinr8:
Thanks for that, cleared it up for me too :D
[Touch HD Windows Mobile ROM Development] doudaix:
I didn't know that until yet...
[Touch HD Windows Mobile ROM Development] bouwew:
What is the difference between the 230xx and the 235xx series?

MaryOne X0.03☻Build 23502 COM5

XannyTechROM GRID LEO 1.9 Latest Leo (21870/23081)
[Touch HD Windows Mobile ROM Development] THUDUK:
I would like to know this, as there doesn't seem any difference at all ?
[Touch HD Windows Mobile ROM Development] hmmhmm1222:
no i havent found one single difference so far.....
[Touch HD Windows Mobile ROM Development] Sander101077:
Leo

Hi guys,

can you maybe also explain (just out of interest, I am not an expert) what Leo means and what this brings on WM? Also I wonder what the Manilla versions do and their differences.

Maybe an Idea to start a threat about all parts/differences.

I am just curious and read a lot so just would like to know a little bit more.

Best regards,

Sander
[Touch HD Windows Mobile ROM Development] Smobbo:
Leo is the name for the new phone from htc (the HTC HD 2).

It is also the first with the new manila version (2.5), which is why it is often referred to as the 'leo manila version'.

It doesn't really bring anything new to WM, WM is developed separately from Manila (WM by Microsoft and manila by HTC). Of course HTC adepts her Manila to WM, or atleast it should ;).

This is afaik how things are related :)
[Touch HD Windows Mobile ROM Development] jefafa:
Thank you for explaining. It becomes much clearer now.
[Touch HD Windows Mobile ROM Development] AleksZ86:
thanks for the answers :) but now i have found the searched thread, here is the link:

http://xdaforums.com/showthread.php?t=569715

have fun :)
[Touch CDMA General] zenulator:
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

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

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://xdaforums.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
[Touch CDMA General] bandur:
Great to see work on this!

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 ...
[Touch CDMA General] zenulator:
Really was that necessary.
[Touch CDMA General] Stork66:
hey Zen....

I <3 U
[Touch CDMA General] ruizit0:
so zen... and donut ? are you gonna stop donut development to start with eclair ?
[Touch CDMA General] zenulator:
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.
[Touch CDMA General] TheKartus:
A dump from the Droid should be awesome though, no? Native Verizon CDMA support ftw.
[Touch CDMA General] ~David:
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.
[Touch CDMA General] zenulator:
so who likes the new lock screen?
[Touch CDMA General] TheKartus:
It looks like it may be nice. It slide or anything? or still a press of the menu button to unlock?
[Touch CDMA General] zenulator:
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.
[Touch CDMA General] myn:
You guys see the new Maps app in 2.0? Unreal..

I can't wait to get eclair working on our phones!
[Touch CDMA General] refthemc:
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
[Touch CDMA General] zenulator:
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.
[Touch CDMA General] refthemc:
Isnt that how donut started? dont give up Zen, you guys are pretty awesome with android. Good luck guys
[Touch CDMA General] cbaty08:
I am currently running Ion, and CANNOT wait for this bada$$ 2.0 to be polished ; )

Thanks for your hard work devs!!!!!!!!!!!!!!!
[Touch CDMA General] zenulator:
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.
[Touch CDMA General] jamezelle:
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
[Touch CDMA General] tatnai:
noted a lot more apps in the market today. don't think it is the full deal yet, but plenty more popping up.
[Touch CDMA General] zenulator:
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?
[Touch CDMA General] plemen:
Works perfectly so far. I can receive and make calls, contacts/gmail synced, gps and market work - no force closes yet.
[Touch CDMA General] kr4zyc1d:
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?
[Touch CDMA General] polyrhythmic:
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, 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.
[Touch CDMA General] KERKEDAGAIN:
i'm not running it from nand yet, but as of right now i'm having no issue making or receiving calls..
[Touch CDMA General] TheKartus:
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"
[Touch CDMA General] kr4zyc1d:
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.
[Touch CDMA General] zenulator:
Ok i'm taking it down and i'll work on it some more.
[Touch CDMA General] KERKEDAGAIN:
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
[Touch CDMA General] TheKartus:
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.
[Touch CDMA General] anotherhawkeye:
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.
[Touch CDMA General] TheKartus:
You gotta give ext2 a while to warm up. Once it gets settled on the build its really very fast with no issues.
[Touch CDMA General] Fancy_Lad:
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 :)
[Touch CDMA General] sportsterBK8:
Hide or delete an app

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.
[Touch CDMA General] jamezelle:
you could delete it from /system/app via adb
[Touch CDMA General] zenulator:
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.
[Touch CDMA General] frad:
Hi Tatnai.... any word on whether the market apps show up by default with the res set to QVGA? Thanks
[Touch CDMA General] polyrhythmic:
I have always had clear audio, but I also am running a Kaiser.
[Touch CDMA General] plemen:
Had clear audio from the beginning...
[Touch CDMA General] zenulator:
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.
[Touch CDMA General] kr4zyc1d:
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
[Touch CDMA General] kr4zyc1d:
Battery

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?
[Touch CDMA General] Giggles 312:
<3

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!
[Touch CDMA General] bri3d:
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.
[Touch CDMA General] tatnai:
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 . . .
[Touch CDMA General] TheKartus:
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.
[Touch CDMA General] zenulator:
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.
[Touch CDMA General] Giggles 312:
ahh well then i have no more complaints. :D awesome build Zen.
[Touch CDMA General] kr4zyc1d:
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.
[Touch CDMA General] dclay89:
I have the same problem with GPS not getting my location.
[Touch CDMA General] enatefox:
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.
[Touch CDMA General] sshark:
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!
[Touch CDMA General] bri3d:
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.
[Touch CDMA General] sportsterBK8:
help removing twidroid from this build

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?
[Touch CDMA General] kr4zyc1d:
So you are saying that it is just a coding thing to get GPS to work on the vogue with android?:confused:
[Touch CDMA General] bri3d:
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).
[Touch CDMA General] kr4zyc1d:
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.
[Touch CDMA General] enatefox:
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.
[Touch CDMA General] bri3d:
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).
[Touch CDMA General] kr4zyc1d:
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!
[Touch CDMA General] margosmark:
Google calendar works for me, its installed and in the programs list as calendar.
[Touch CDMA General] jamezelle:
for me too.
[Touch CDMA General] sportsterBK8:
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. :]
[Touch CDMA General] sportsterBK8:
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.
[Touch CDMA General] TheKartus:
Is the system image on the first page, the original image? or is that the one you did more work on?
[Touch CDMA General] kr4zyc1d:
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.
[Touch CDMA General] sportsterBK8:
yes

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.
[Touch CDMA General] bri3d:
Enabling AGPS in WinMo shouldn't have a negative effect on Android, at least not that I've noticed.
[Touch CDMA General] kr4zyc1d:
Thanks, I really appreciate all the help. I should know in a day or so.