yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] jim256:
Ok so I've been away for a few months, and just wanted to pop in and try the latest and greatest and see what progress has been made.

2 quick questions:

1. we currently do not have a soft keyboard then besides the original blue kernel one of martins?

2. when are you guys expecting to be using 1.5?

good luck!
[Touch CDMA Android Development] dzo:
I've made a new initrd with different low memory killer parameters, this might help people with slower sd cards. Try initrd-test.gz and see if you can do without changing the max processes.

http://cs-alb-pc3.massey.ac.nz/vogue/files/initrd-test.gz
[Touch CDMA Android Development] mssmison:
There is not a link to a system.ext2. They are bigger and less stable and more apt to corrupt. What are you wanting to copy to your system.img with adb? Maybe I can help? PM me. :)

There are several cupcake builds and even the new ion build available, in the main vogue forum. They all contain the new HTC keyboard, which rivals the windows mobile version. Seperate threads.

http://xdaforums.com/showthread.php?t=523472 (mine)

http://xdaforums.com/showthread.php?t=523692 (vilords, also quite a good build)
[Touch CDMA Android Development] t1mman:
With bell aslo:

SMS send with Outlook in HTML format will get you the chineese coding. Try resending them as text and they will be ok.

I never had to input anything as for login/pass to get a connection on bell's data... :| Got the setup on 1.1 then replaced the files and works fine
[Touch CDMA Android Development] katmandu421:
I look forward to trying this later today.

FYI: The zimage that vilord posted in thedudes cupcake builds (ion thread) seem to perform great but don't have all of the goodies that yours do. Not sure if you can "merge" or take some things from that kernel or not (or if you have already), but wanted to make you aware of the good performance I've had with that kernel.

As always, thanks for all of the effort! It's amazing what you guys can do.
[Touch CDMA Android Development] mssmison:
umm vilords kernel is DZO's kernel. He went back to an earlier version of DZO's kernel and applied a couple of fixes, trying to sort out the no screen wakeup issue that was initially apparent with cupcake builds. DZO has since then sorted it out so we get all of the advantages of his kernel on a working cupcake build. :)
[Touch CDMA Android Development] Whosdaman:
Very good job Martin, I wish we had it as easy as you did on WinCE...
[Touch CDMA Android Development] dru28:
help with my internet didnt know where to post

so i have htc xv6900 from verizon. i have it flashed for cricket and the internet was fine but i love messing with phones lol so i ended up flashing my rom to the wm 6.5(sprint htc touch pro) and had to get a program to get the unlock code to get into my ##778# and the info is right but my data connection is not going through #777 which it was at first so is there a program or app that i can run to connect or sprints code or jus something to get internet back to my phone thank you sorry if i post it in the wrong place
[Touch CDMA Android Development] katmandu421:
The kernel i am using is from before he modified the zimage-gpu from dzo to address the vibrate problem, so I'm not sure what this first one was based on (probably still from dzo's) I think I'll try the new init and the latest kernel from martin tonight and see if performance stays up on the ion (red) build.
[Touch CDMA Android Development] tErbo b00st:
so I tried the latest 1.1 from June 15th two days ago and am loving it once again (took a month break due to issue, see below). However I am having speaker problems with music. My music player will ONLY play music through the earpiece. Not through the speaker, and not through headphones (on previous builds I had music working through headphones and/or speaker). I also have the problem occasionally with ringtones.

I also had the same problem twice over the past couple months. I boot into android and NONE of my contacts/email/sms are saved, and if I try to open any application I immediately get a force close. My sd card remains unharmed, but this means I have to go back and reload everything brand new. Any opinions?

Out of curiousity, who is using 1.5 daily and who is using 1.1?
[Touch CDMA Android Development] mfpreach:
Thanks dzo, I'll give it a shot. In the meantime I ordered a class 6 micro.
[Touch CDMA Android Development] tetrismonkey:
this happens when your data file gets corrupted the best way to fix it is to always have a backup data.img saved somewhere on your sd card

make a folder call it "data backup" and every few days boot into windows and use file explorer to save a copy of data.img and save it to data backup folder

i use android 1.1 and i don't i need the data back up that often but when i do at least i only lose a day or so of info
[Touch CDMA Android Development] srwalter:
I modified initrd to mount the /data partition with -o sync. I've not had data.img get corrupted since then, nor have I noticed a negative impact on performance. Does anyone know why initrd doesn't do this by default?
[Touch CDMA Android Development] vilord:
Srwalter: I use sync option in my initrd as well...

Katmandu, the kernel I posted is from pre-gpu with vibrate fixed.

Martin, do you know why total RAM shows 98 megs when the phone has 128?
[Touch CDMA Android Development] katmandu421:
Found out that the new init and kernel from dzo dont play nicely with the ion system img, for those who were curious. I may try it with vilords kernel later, but as of now it's switched bck to the dudes. I'll keep you posted...
[Touch CDMA Android Development] dzo:
The phone actually has 160M but 23M is used by AMSS (the radio software), 1M for the fb and ram console, 15M for the GPU (it will work using only 7M but some apps go quite slowly), 1M for USB buffers, 8M for the adsp (needed for youtube to work), 8M for the 2D graphics cache (mdp) and 3M for the camera. This leaves 101M which is exactly the same as the G1 (it has an extra 16M but it's version of AMSS uses more memory) and the kernel uses about 3M leaving 98M.

I've just changed my initrd to include the sync option and also added a few apps to data.gz.
[Touch CDMA Android Development] refthemc:
Hey dzo, are you gonna release a 1.5 version anytime soon because i would rather just get a complete package from you? rather than mix and match files with vilords and msmissions files but no offense to their great ion work ofcourse : )
[Touch CDMA Android Development] njakobs:
Hi I have been using the test-initrd from last night without setting max apps and it has been working perfectly! Does this new initrd contain those changes aswell?

What apps did you add? Just wondering if it is worth rebuilding data.img

Cheers
[Touch CDMA Android Development] dzo:
Thanks, I'm actually using one of your ROMs to boot android, nice work. I don't know if we have had it easy running linux really, it's meant writing lots of drivers from scratch! Why not join us and use your skills in the open source world, we have a lot more control of the hardware than wince gives you.
[Touch CDMA Android Development] dzo:
Yes, the new initrd has the lowmem settings and sync. There's no point rebuilding data, the apps are neocore, buka-demo and nswplayer. These should be available elsewhere, I just put them there so that when people first try android they have something to play with. Now that adb works, it' easy to add apps to the phone too.
[Touch CDMA Android Development] vilord:
Check my ion thread for low- and hi-res initrd's that *should* work with both 1.1 and 1.5. Brought over all of Martin's memory updates as well.

-Jesse
[Touch CDMA Android Development] dzo:
I haven't had a lot of time to look at 1.5 and I was waiting to see if somebody could get google login working without needing 1.1 first, I also need to fix the camera. I'll probably get something working next week but I don't suppose it will be any better than the currently available images. Thanks to vilord, mssmison and srwalter we have a good selection of 1.5 images. Perhaps my time is better spent on the kernel anyway, there's still lots of work to be done.
[Touch CDMA Android Development] Ideal2545:
im really enjoying all the new changes to 1.1, its absolutely usable for me now, as long as i have chompsms and all of dzo's changes, im happy. hopefuly someday we'll get an android phone with the same gps hardware too so that we can port it over to our android phones!

great work dzo
[Touch CDMA Android Development] jaredakelly:
mssmison's Hero ION theme build is actually extremely fast and stable. i suggest you try it out. download the clean dude build and then download the hero ion build system.img, use the system.img from the hero ion build and your good to go
[Touch CDMA Android Development] Ideal2545:
dzo, do we still need to have the clock-7x00 stuff in our txt files now?
[Touch CDMA Android Development] sequen:
Latest Build(6-18-) is SOOOOO GOOOD!.. definately noticing a speed increase in scrolling, screen refresh rate and as well as how long the phone takes to show the caller ID on a incomming calls especially while running another app such as Buka while receiving a call. This is really good stuff.
[Touch CDMA Android Development] vilord:
Martin, your memory updates to the initrd are GREAT! Using my initrd with your updates, cupcake/1.5 flies now on my phone!
[Touch CDMA Android Development] Ideal2545:
vilord, is that with intrd-test or with the new package?
[Touch CDMA Android Development] vilord:
That is with using my initrd. Head over to http://xdaforums.com/showthread.php?t=523692 for that.

initrd-test still doesn't quite work right with 1.5.
[Touch CDMA Android Development] cccpms6:
I have a question about getting the internet connection working on the andriod. I am a brand new member and this forum does not have any good searching tools. I do not have internet in my plan at verizon but I need it to be able to hook up to the internet so I would be able to get the media mail such as pictures and videos. If anyone could help me or direct me to what page i might find this information i would appreciate it. thanks

By the way great job with Android, much more interesting than the windows system.

Thanks.
[Touch CDMA Android Development] vilord:
You mention media mail... if you are talking about MMS, then we can't help you yet because MMS doesn't work at all for non-tmobile users.

Beyond that, you'd have to set up a reverse proxy using ADB, and right now that just isn't implemented...
[Touch CDMA Android Development] cccpms6:
Thanks for that information. Hopefully you get to solve the MMS issue. Good luck with that.

I've got a few more questions. Sorry I am new to this so please bear with me.

So I went and got some apps for the Android, I downloaded them via computer and placed them on the storage card, but when I boot the android system those apps do not show up anywhere. I cannot seem to find any place where there might be a file explorer or some sort of thing like that. Any help would be nice, thanks.

Oh and the apps I got was the Anycut, and I believe the SMS pop up.
[Touch CDMA Android Development] njakobs:
Create a folder called "AndroidApps" in the root of your SD card. Place your apk files in it and reboot android.
[Touch CDMA Android Development] aven_soulgazer:
I believe the capital A's are important and are case sensitive
[Touch CDMA Android Development] dzo:
Or install adb and the driver and do "adb install filename.apk"
[Touch CDMA Android Development] cccpms6:
Thanks for all the help. But I have one more question, I think.

The phone for some reason kicks me out of whatever I am doing and goes to the booting screen and it keeps listing the battery status. It lists the percentage left, or if charging it lists the percentage charged. Does anyone know what the problem might be? I would like to be able to exit the screen but non of the buttons are able to get me out of it.

Sorry if this questions has been addressed already.
[Touch CDMA Android Development] katmandu421:
I think you are referring to the menu screen that shows "Android" and states" press menu to unlock". Menu is volume down. All of the button functions are listed in the first post.
[Touch CDMA Android Development] cccpms6:
No no, the screen i get is the booting screen that comes on before the Android menu screen. Its the screen that comes up when you just began to boot the program. It lists the operations it is doing.

I got that screen twice already and each time I was writing a sms and that screen would pop up and just list the functions it is doing.

For example it would just list the battery status and whatever other operation that was going on.

I think its the script page. I do not know alot about all this but its sort of like the GWbasic MSDOS screen that gives you a place to input commands and everything. I know this program is not based on GWbasic but it looks like that.
[Touch CDMA Android Development] mssmison:
Sounds like your seeing the logcat data. I'm not sure why that would pop up. Did you happen to enable any development settings for debug app?
[Touch CDMA Android Development] dzo:
you probably pressed sym+0 by mistake, press sym+6 to get back to the ui.
[Touch CDMA Android Development] cccpms6:
Thank you for the above information and for all the work put into this program.

However, I have just one more question. Well I hope its the last one. But does this program use the internet on its own? I do not have a data package so I checked the usage on the data and I think the android is connecting to the internet and using up kilobytes. Does the android do that on its own? And is there anyway I could block it from connecting to the internet in anyway?

Thank you.
[Touch CDMA Android Development] vilord:
if you're using all the 1.1 stuff from dzo, run togga and hit disconnect, and don't connect.

if you're using 1.5 stuff, run modem and hit disconnect and don't connect.
[Touch CDMA Android Development] oxsolid:
Fabuous Work! Spread the word!!!

dzo, vilord, mssmison, srwalter, everyone I missed... this work is super!

I'm a highly tech savvy person, and for the past 9 months I've been scouring the net for any news of a "Sprint" or "CDMA" Android phone. I've set my Google news up to display this info and I’ve been checking it daily for the past 2 months.

The point is that I'm SURE that there is a large community of people like myself with programming experience, who are just simply bound to a contract but would love to get involved with a project to get Android running on their network.

___

Quick timeline:

After I had gotten fed up with Sprints complete refusal to mention anything about Android until the buzz around Palm Pre wears down, I decided to start "You Tube" searching for current port progress... I had done this before, but this time I was on a mission...

well after many hours I was most impressed with the HTC Touch, but let me tell you, once I narrowed in on the touch and started looking for videos on progress, I think the newest video out there shows dzo's 12-8-2008 build, with the wacky screen resolution... it was a little hokey, but I had decided that I could deal with it...

that was 4 days ago, 3 days ago I bought a touch off craigslist on the cheap, I spent all night reading the forums to get it to work (I’m too impatient to post questions)... I missed most everything the next day because I slept through it... and I just loaded up vilords 6-20-2009 changes with dzo's 6/18/2009 root system (after setting up my data)......

.....

........ and as you already know, this blows the socks off the 12-8-2008 YouTube videos... and it's all around awesome

Had I seen a video of the current progress, there would have been no hesitation at all.

______________________________

So basically, I think that if somehow we could get a Google news article (and webapage that appears on a standard search) that had the keywords "sprint"/"Verizon"/"android"/"Google"/"HTC Touch Vogue = MP6900 and vx6900", letting them know that they can have an almost fully functional version of android now, and explained the progress with a link to a video, and these forums... you all would have a lot more potential helpers... and the price of HTC Touch phones on eBay would skyrocket

A side effect would be a lot of newbie questions/posts on the forums

Below is a list I bet you all have, but took me a long time to compile:

Updates:

dzo(forum)

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

dzo(home page):

http://it029000.massey.ac.nz/vogue/

dzo(files):

http://it029000.massey.ac.nz/vogue/files/?C=M;O=A

mssmission(forum):

http://xdaforums.com/showthread.php?t=523472&page=1

vilord(forum):

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

Instructions(this is mainly good for letting people know what the buttons do, but some of the install instructions are outdated):

http://xdaforums.com/showpost.php?p=3709708&postcount=105

Install(this has good information, and i think that most people can find this easily, but it needs to be updated):

http://www.androidonhtc.com/vogue/install
[Touch CDMA Android Development] vilord:
updated initrd on my thread here: http://xdaforums.com/showthread.php?t=523692

Now supports automatic time and timezone updates, also supports call waiting ID on cupcake, and VM indication on verizon (and maybe others).

Thanks to srwalter for the call waiting ID and VMI fixes.
[Touch CDMA Android Development] zapat0s:
This project already showed up on engadget a few months back and caused a huge swarm of people to visit these forums. However very few of them offered any real help and honestly development slowed down a lot because DZO and everyone else had to answer questions from all of the new users who kept asking questions about things that were answered thousands of times already. Now since progress seems to have really picked up again i would prefer (and im sure im not the only one) to not see it slow back down again because running android on the vogue became popular again.

So in short just wait. Its nowhere near ready for any substantial amount of users yet lets wait until a lot more of the functionality is finished (improved camera, MMS maybe bluetooth and GPS as well) before telling too many people they can run android on their vogue.
[Touch CDMA Android Development] f00bar:
I might get a bit of time this weekend to do some work. I plan to update "Modem" to include tethering support. You can tether now using tetherbot, but that just uses a proxy and is pretty limited/not the best way to do things. The right way is to use iptables/NAT in the kernel.

I've had quite a bit of problems with kernels after mid-april or so, in that things have seemed extremely sluggish. In another thread people mentioned things have gotten better. Have these problems gone away in the most recent kernel? (In which case, I'll post an iptables/NAT build with that one), or are they still there? (In which case, I'll start from an older one).

Dzo, what do you think of just including iptables/NAT in your kernel builds in the future? It seems to me like a reasonable thing to include by default.

Edit: I just saw in commit 4b8dc02af072238e7aa2e45840aec67e97d3e6b8 you turned off ether and replaced it with the ADB device. Is there an easy way to support both? Ether seems like the right way to do tethering..
[Touch CDMA Android Development] dzo:
I added a fix to the usb code last week that made the adb driver work really well now but I haven't tried ether recently.

The problem with enabling both adb and ether is that the necessary device ids are different so on the host something would need to change. It may not be difficult to do, a udev rule on linux and a minor change to the adb driver on windows. I'll take a look at it tomorrow if i have time.
[Touch CDMA Android Development] vilord:
gadget-ether is the right way to do tethering, but right now we aren't using usb-gadget, we're using adb directly.

before we were using cdc_subset ethernet which doesn't support windows, so a lot of people are happier with adb.
[Touch CDMA Android Development] oxsolid:
DL is cool

Zap-

I can definitely see that as a negative, most newbie’s dread looking up answers for themselves...

the main positive i can think of is that there is a large population of plp that would love to know about this, but causal/typical searching makes this info hard to find...

I'm fine with keeping it on the DL for a bit, but it might be wise to spread the word before Sprint/Verizon actually come up with a new android phone

more plp w/ touch = more potential plp to help port features over from a new Verizon/sprint phone... maybe someone from qualcomm will pick up a touch... that would be lucky :)

-Ox
[Touch CDMA Android Development] mfpreach:
Android on the vogue, at this point is too buggy for mainstream use. I think it works fantastically but I think there is still a ways to go.
[Touch CDMA Android Development] vilord:
Updated the above link again, Google Sign-on works in cupcake/1.5 now!!! No need to load 1.1 at all unless you need the camera, hopefully someone has time to work on the camera now that sign-on works? :D

Use a blank data file and you won't get strange error messages about partner setup crashing. Just grab supptools.zip and there's a blank data file in there.
[Touch CDMA Android Development] f00bar:
Just wondering, how did you fix it? I believe the reason was that the setup.apk was getting NetworkDisconnected messages from the framework and not even trying to login. Did you fix the RIL so the networkstatemonitor in the famework works correctly?
[Touch CDMA Android Development] vilord:
Another update to initrd on my thread... http://xdaforums.com/showthread.php?t=523692

Mute and Unmute now function, 3g indicator now functions, data active indicator now functions. Just use modem to turn on and off the connection.

f00bar I fixed it by turning back on the checkin config option, apparently 1.5's google signon services require checkin.
[Touch CDMA Android Development] oxsolid:
keyboard screen calibration

HTC touch vouge sprint

For anyone new who has been really frustrated with the keyboard, (like me)... I found that the keyboard / screen calibration was the culprit, and the instructions on how to do this are scattered, but this is what i have found works:

Originally Posted by dzo :

"Screen calibration should work again, press the cam button to display the onscreen kbd, then while pressing the end call button tap opposite corners of the screen. "

I only tap the opposite corners once each (with the stylus) , but i immediately check it with

"dev tools"->"pointer location" afterwards to see if it works

it took me a few times to get it right, but i found it works best when i tap on the furthest edge(or corner) of the touch screen even (almost not even showing up anymore[if you were on pointer location])

now the touch screen is sooo much more enjoyable...

hope this helps someone
[Touch CDMA Android Development] prairiefire:
I have never been able to get this to work. I wonder if i'm doing something wrong. (i am using dzo's latest 1.1 image). i turn the onscreen keyboard on and when pressing end call, I just get the pop up asking if i want to shut down the phone or go into silent mode. when i try opening up "dev tools" -> "pointer location" it gives me an error and tells me to "force close" it.
[Touch CDMA Android Development] mssmison:
hold down the end key when you press the top right and bottom left..
[Touch CDMA Android Development] oxsolid:
try a fresh install

sounds like something is messed up (it shouldn't force close on pointer location),

try deleting your SD card, and reloading everything, i use dzo's kernel, and vilords everything else (the 1.5 build is awesome)

[ vilords build - http://xdaforums.com/showthread.php?t=523692 ]

******************

Also does anyone know if it should hold the calibration after reboot, i'm fine recalibrating it now that i know how, but it'd be cool to know if there was a way to hold the calibration settings through reboot (i just rebooted and needed to recalibrate)