yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] squix78:
Hi Vi

Are you using the zImage from the latest linwizard version? And before running Haret I soft-reset and close all other applications, including ActiveSync and the FileExplorer. You have to have as much free RAM as possible... Maybe I'm just lucky or forgetting something...

Good luck! I really hope you can make it run!
[Touch CDMA Android Development] Mr. Vi:
Yes but I renamend zImage to Image, because in the configfile it points to Image and not zImage or am I wrong?

With my previous rom I had after softreset and oxios hibernate about 25mb free memory. Are you running haret from the device or from your sd card?
[Touch CDMA Android Development] suanccd:
Wow, this is amazing! Google maps works very well, however but not the browser. BTW, I am on sprint sero and no need to change anything.
[Touch CDMA Android Development] squix78:
Yes, the kernel in the default.txt and the one on the device need to have the same name. I'm running from the device and it seems you have much more free RAM than I do! How big is your initrd? Mine is about 18.7MB. Is it possible that you own a different version and not an ELF? I get the CLK stuff too and after "HTC init" the tux appears and a lot more boot messages... Could you at least make the initrd from linwizard run?
[Touch CDMA Android Development] Mr. Vi:
I'm having the HTC Touch ELF (64/128, GSM version) I was just trying to run the linwizard initrd which is about 20mb big. I'll give the androidinitrd a try!

And I made a rom for you :)

http://xdaforums.com/showthread.php?p=2129080&posted=1#post2129080
[Touch CDMA Android Development] dzo:
The log is good but I can't see how it's authenticating. Can you try starting pppd by hand (from the terminal in android as root) do:

cat /initmodem1 > /dev/smd0

cat /initmodem2 > /dev/smd0

/bin/pppd /dev/smd1 debug defaultroute local usepeerdns name {YOUR USERNAME} noipdefault unit 0 linkname gprs novj noauth

make sure the username and password is in /etc/ppp/papsecrets

and see what it prints.

make a script for this if it's too much to type.

Martin
[Touch CDMA Android Development] jim256:
What about going to Start -> Settings (then in the System or Connections tab depending on your ROM) -> External GPS. In the Programs tab, try putting the GPS Program Port to (None).

Also try browsing to your Windows folder on your device. Do this with something other than the standard file explorer, and be sure to have all files/extensions etc set to show. Then go the the Startup folder within your Windows foler. What is there?
[Touch CDMA Android Development] xgumbyx:
Is there any more word on the Voicemail number and how we can set it? Its driving me nuts!
[Touch CDMA Android Development] fews:
Does dzo's Vogue/Android development also apply to the GSM version (Elf?). I am from New Zealand and would rather purchase a Vodafone HTC Touch (GSM) as opposed to a Telecom Okta Touch (CDMA).

I have searched the forum and cannot find a solid answer. Anyone who can shed some light on this would be greatly appreciated.

I am a software developer and would love to contribute anything i can to this effort.
[Touch CDMA Android Development] xDarKnighTx:
I believe this particular android development only applies to the CDMA version.

The GSM version have a slightly different hardware configuration, and the CDMA version I believe is also a bit more powerful than the GSM version (but with a tradeoff of no WIFI on the CDMA).
[Touch CDMA Android Development] njakobs:
While we are still using the pre release sdk we wont be able to set it. Easy solution I use is create a contact "voicemail" and a short cut for it on the main screen.

Also found these two apps that seem to work well.

http://vtap.com/wikitap/static/android.html

http://www.phoload.com/software/299-simon-tathams-puzzles/view
[Touch CDMA Android Development] grktaurus83:
Looking at your setupmodem.sh script, you echo "* * $PPPPASS" into both the /etc/ppp/papsecrets and the /etc/ppp/chapsecrets files. However, in your post above, you say to verify that the username and password is in /etc/ppp/papsecrets.

When I check my /etc/ppp/papsecrets, I find:

* * telecom

as it should be based on your setupmodem.sh script. Should I change this to something else? And if so, in what format? (As in, should I just list them as "username[space]password" or in some other way?)

Without changing the /etc/ppp/papsecrets, I ran the commands manually and I got no output form the command. It just moved onto the next line without giving me a response. I also made sure to su before running any of the commands.

Also, I'm not quite sure how to unpack the initrd and repack the initrd to include my own scripts, so I just typed them out manually. I looked into unpacking and repacking the initrd and used

cpio -id < initrd

to successfully unpack it all. I tried to repack it all and gzip it for the phone using

find . -print | cpio -ov > ../initrd

gzip ../initrd

but the phone would not boot with my new initrd.gz and would lock up the phone in haret.

Seems like I'm close but messing something small up. Anyone have any pointers?
[Touch CDMA Android Development] fews:
Thanks DarkKnight :) Here is a comparison matrix http://connectwirelessweb.com/HTC-Touch-Specifications-GSM-and-CDMA.htm

Can anyone else confirm this? dzo?
[Touch CDMA Android Development] njakobs:
Read the first page! This will only work on the vogue. (Telecoms - Okta Touch in NZ)
[Touch CDMA Android Development] dzo:
Well, telecom shouldn't be in the papsecrets file, it should be your password. The two stars mean to use that password for all usernames and connections.

pppd probably logs to the system log. Type logcat after the command to see it.

Try -H newc in your cpio command.

We're on 200 pages!!!! Perhaps there should be some more threads.
[Touch CDMA Android Development] d3mon187:
Well, NOW we are on 200 pages :D

Great work Dzo, I'm continuing to test everything from day to day and it all seems to be working well besides the already known problems. I was thinking that the problem with sending a text message longer than 160 characters might be an easy fix, and would be a lot of help to me since I regularly type out long texts. I think it's so stupid that there is a limit on text messages, when even those with regular keypads frequently send me text messages well over the 160 limit.
[Touch CDMA Android Development] etiger13:
Mine's at 40 pages because I changed the default posts per thread. But I am working on the forums at my site and should be done soon. Any topics you would like in particular?
[Touch CDMA Android Development] exabrial:
sudo find . | sudo cpio -o -H newc | gzip -c - > ../initrd-new

Someone just posted that for me a few messages back. Try that.
[Touch CDMA Android Development] pchasco:
There's a very good reason for the 160 character limit. SMS messages on the GSM network are limited to 256 bytes. Some of those bytes are needed for control information. What's left is the room you have to send a message. SMS is not native to our CDMA networks. CDMA networks emulate the SMS function and by doing so we have the same restrictions that GSM carriers have. When you send a text message that is longer than 160 characters it will be sent in two or more SMS messages. I think the way that these messages are coalesced is carrier specific, though I'm not certain about that.
[Touch CDMA Android Development] d3mon187:
Thank you for that lesson in sms (and I'm really not being sarcastic). So why can't they raise the limit of 256 bytes?

As for the current handling in Android, when I send a text it disconnects from the network and says it cant send the text until it has service, then it sends the first part, then it says it lost service again, then reconnects and then sends the second part. When I get the text message back it is complete garbage and is in Chinese and square characters. Also, when I send the text message Android says it is only 2 texts, but I will get back 3. This is when sending messages to myself, as I haven't tested a long text from another phone, but I would assume it would receive them fine.
[Touch CDMA Android Development] etiger13:
Do text messages shorter than 160 characters come in ok?
[Touch CDMA Android Development] pchasco:
It would be very difficult for them to raise the limit. The GSM network and all GSM phones have been designed to support this 256 byte packet size. The investment in time and money would be incredible. I imagine that the multiple message implementation we have today for long texts was the only cost effective solution -- plus it enables carriers to charge us more.
[Touch CDMA Android Development] jim256:
Ya I think that just splitting them up is a more than ok solution.

But I wanted to say that I have also had this problem, whenever I send a msg to someone over 160 characters all they get is garbage. Anything coming in our going out at 160 or under is just fine.
[Touch CDMA Android Development] d3mon187:
exactly, I think it's just messages going out at over 160 is the problem.

I agree that the threaded messaging is a lot more helpful, but instead of changing the entire system they could just add a flag to the end of each package that states that the text is continued to the next package, and that way the phone could just organize it into one long message instead of a couple separate texts. Just a thought, but you have to figure that sooner or later they are going to HAVE to do something about the limit.
[Touch CDMA Android Development] grktaurus83:
Ah, there it is! I looked skimmed back about 10 pages because I thought someone had mentioned it, but I must have missed it. I hate it when that happens. *sigh* Thanks exabrial and dzo for that pointer.

I know that telecom shouldn't be in there. I kept it in there to see if I can get the output to say there was an authentication error. That means that we're at least getting through. Then I'd fudge around with username and password arrangements (whether it's username, username@sprintpcs, username@sprintpcs.com, etc.).

I was primarily wondering about the *'s and whether the username should be in that file as you had said in that post. The mention of username being in the papsecrets in that file was what confused me since that wasn't in your original script.

And I'm a retard, I should have checked logcat. *sigh* Well that's what I get for doing this at 4am.

It seems like I've finally got my feet on the ground now. I'll see if I can get you guys some results later today.
[Touch CDMA Android Development] knownboyofno:
thank you I wish that my computer was working right cuz I would love to help out.
[Touch CDMA Android Development] d3mon187:
Nevermind, I take that back. I just got a long message from a friend, and the first part was fine, but the second text came in all garbled. Asked him to resend the second part, and that came in garbled too.
[Touch CDMA Android Development] bugzy:
so .. what am i missing?

is internet on demand working for you?

I'm on sprint also
[Touch CDMA Android Development] bugzy:
wonder if anyone else porting Android to HTC phones is having issue on Sprint, or just Vogue's
[Touch CDMA Android Development] grktaurus83:
So I sent Martin my logcat output to look over whenever he gets some time. For everyone else interested, the output that stands out to me is the following:

W/pppd ( 514): LCP: timeout sending Config-Requests
I/pppd ( 514): Connection terminated.
W/pppd ( 514): Receive serial link is not 8-bit clean:
W/pppd ( 514): Problem: all had bit 7 set to 0
D/pppd ( 514): using channel 2
I/pppd ( 514): Using interface ppp0
I/pppd ( 514): Connect: ppp0 <--> /dev/smd1
W/pppd ( 514): Warning - secret file /etc/ppp/pap-secrets has world and/or group access
D/pppd ( 514): sent P
W/pppd ( 514): tcflush failed: m

Anyone else think they can shed some light on this?
[Touch CDMA Android Development] grktaurus83:
You're not missing anything, internet-on-demand is not working yet. I'm doing some footwork for Martin since he isn't on Sprint. I'm also tweaking the script to see if I can figure a few things out to try and alleviate Martin's load (since this is a big portion of the questions being directed at him).
[Touch CDMA Android Development] jim256:
Just patience ;)

This is greatly appreciated. Certainly one of the major factors for not using Anroid for me and I'm sure many others on sprint and other like carriers.

(and after that hopefully its on to kb support (somehow) and moving on to the real android open source code!)
[Touch CDMA Android Development] grktaurus83:
So, I've been making small changes and checking logcat. Some notes:

1) Whenever pppd tries an using an odd channel, it sends many packets and eventually terminates the connection because of "LCP: timeout." Whenever an even channel is used, I see "tcflush failed: m" and it moves onto the next channel. Oddly coincidental? (ha, unintended pun there...)

Hey Martin, do you see this sort of thing on your device? Do you connect on an odd, even, or either channel?

2) setupmodem.sh echos the password from the command line to the files "papsecrets" and "chapsecrets" but the files that exist there already are "pap-secrets" and "chap-secrets." I tried echoing to all 4 locations with no change in results.

3) Whenever I run the commands manually, I get no output when I run "ifconfig" after my script, but I do see a loopback connection after running setupmodem.sh. This is probably because of the telnet command at the end of the setupmodem.sh script. I haven't checked that though.

4) I'm thinking of trying the "noauth" option for ppp to see if that helps. Any reason not to?

Anyone else have some ppp experience in linux?
[Touch CDMA Android Development] SyubSnunb:
I know a fair amount about the GSM standard (due to my job; also ironic that i have a CDMA phone). You can find a lot of info about the GSM standard on the www.3gpp.org website. For info on the initial technical realization of SMS look at the 23.040 and the protocol is in 24.011. The short version of the spec is that there is a 134 byte (don't ask me why they picked 134 that's just what the spec says; but my guess is they did some analysis to figure out how long they estimated the average message would be along with the amount of time it takes to send an SMS over the secondary channel when you have traffic up supporting a call) TP-UD that contains the actual text of your message (it's packaged in a RP and CP layers). This text is typically encoded in a 7 bit schema so 134*8/7 = 153 characters is the limit of a single text message. However they did add functionality to allow for concatenated SMSs. Basically the protocol supports a set of transactions to be given sequence numbers. But it's up to the application handling the SMS to take a message greater than 153 characters, break it up giving each message the correct sequence number and then send each as an individual SMS. Then the application on the phone receiving the SMSs is responsible for collecting the SMSs and putting them back together based on the sequence numbers. Many of the original GSM phones had applications didn't use the concatenated SMS they would simply limit you to 153 characters per SMS and when the received concatenated SMSs they would simply display them as separate SMSs. Now I'm not really sure how the CDMA standard emulates SMS but my guess is that it simply encapsulates the GSM standard. Hope this helps you understand where the limit is coming from.
[Touch CDMA Android Development] njakobs:
Ok so we have a working kernel due to all the magical work by martin.

Would a quicker path forward to be to take an android image from an existing G1 and putting that on our vogues to run on Matin's linux kernel?

This would give us all the apps people want. Market, gmail, calendar etc

I am sure I am missing a whole heap of technical aspects here but it seems possible to me if my understanding of the relationship between linux to kernel to Android is right.
[Touch CDMA Android Development] grktaurus83:
I got android to lock up on my through my tinkering.

1) I established a network connection in windows mobile and went over to android. Even though the internet connection works, ifconfig outputs nothing. Annoying.

2) I went to a website to find my IP, ran telnetd, and connected to to my vogue remotely. I ran "ls" from telnet and noticed that my vogue's screen woke up showing the "press menu to unlock" screen. I watched it to see if anything else would happen and eventually it turned back off. I ran "ls" through telnet again and I got no telnet response. It was then that I noticed that the LED was now flashing orange instead of red.

Maybe a bug in the collapse framework?

And I need to check previous posts to find out what the orange LED means again.

Besides that, nothing new to report (other than I have been neglecting my work and need to stop working on this tonight).
[Touch CDMA Android Development] dzo:
I had the same thing happen to me today and I think I found the problem. I put a new release on the site that should fix it (only zImage has changed).

I'm still trying to get the camera working, it's quite close, perhaps a few more days.

Try /bin/ifconfig, it seems the android one doesn't work but the busybox one does.
[Touch CDMA Android Development] dzo:
This would explain why it only works in NZ, I was writing the password into the wrong file. The latest initrd should be better.
[Touch CDMA Android Development] qwho:
So now the password is in the correct location, does this mean if we have the correct login info in default.txt that there is a chance this will work for sprint users now?
[Touch CDMA Android Development] grktaurus83:
Like I said in a previous post, I tried echoing the password info into all of the locations (correct and incorrect) before the changes were made and I did not see a difference in the results.

I tested it again a little while ago, and still no luck. There are still a few tests left for me to do before I can make a more definite statement.

Looks like I'll be getting no sleep tonight.
[Touch CDMA Android Development] pchasco:
Another SD card bites the dust :(
[Touch CDMA Android Development] brunes:
dzo, when you get the camera working, you will have to PM me your address so i can mail you a beer, or a 6 pack :P
[Touch CDMA Android Development] d3mon187:
Nooooooo, I have been running android without problem for 2.5 days now and I just looked over and its flashing orange and non responsive. No idea what caused it, and it doesn't respond to calls or anything even though the calls DO NOT go straight to voicemail like they would if it was off.
[Touch CDMA Android Development] bugzy:
with the latest build, when i open Browser, it opens to default Google page, but when i open another page using bookmark, it opens the page, but closes Browser immediately.

i tried inputing a URL also
[Touch CDMA Android Development] qwho:
Maybe reboot and try again, that's happened to me about once on every build on the first couple bootups...
[Touch CDMA Android Development] bugzy:
tried a reboot, still browser closes
[Touch CDMA Android Development] summerblink:
i don't get any thumbnails when going to the "pictures" app, or browsing for a wallpaper . . . is anybody else having that problem?
[Touch CDMA Android Development] bugzy:
Pictures works normal for me

also, i fixed the Browser issue, i deleted all the Android files and put the newest build fresh

and then imported my contacts using the CSV importer app
[Touch CDMA Android Development] summerblink:
where do you have your picture files stored? and your music, for that matter - i can't see that either! the CSV importer RULES though :D

i guess this is really going to take a trip up to Fry's for a new microSD card . . .
[Touch CDMA Android Development] dzo:
Does anybody have a copy of compare anywhere or shopsavvy (or any other app that uses the camera). I've got the camera almost working and would like to check that it works with real apps.
[Touch CDMA Android Development] jim256:
Had it not wake up on me today while on a long call.

Couldn't ever get it to wake up, even after the call ended trying to use the red end key. It even kept vibrating so I think I got a bunch of msgs...guess I'll never know :( :S

dzo,

this uses the camera...good enough?

http://www.slideme.org/content/voice-android

A soft KB???

http://www.slideme.org/content/my-ime

one of those that I'm not sure how to dl tho :S
[Touch CDMA Android Development] etiger13:
Is it on SAM2?
[Touch CDMA Android Development] ntiernan:
dzo, here is shopsavvy.apk... btw, thank you for all your efforts on this port.
[Touch CDMA Android Development] unsungboxer:
download slideme. its a pkg manager like synaptic. then u can try these apps
[Touch CDMA Android Development] jim256:
have been meaning to try, but keep getting distracted (i don't have data in android unless I reboot, establish connection, then boot into android again...= pain :S lol)

anyone else tried yet?

EDIT: just tried it. Too large resolution for our devices. I think its just another copy-paste thing anyway :(
[Touch CDMA Android Development] Macropoutsis:
I got shopsavvy to work. Not with the camera, but by entering the code. Can't wait to get that camera working. Would also be nice to get GPS going. It helps with the local search for products. Great job so far.
[Touch CDMA Android Development] smopoim86:
I've been reading about all the dieing sd cards. For some reason (I could be imagining things) I seem to recall seeing problems with people having corrupted cards in winmo as well, not just android users. I'm wondering if the hardware write leveling doesn't work well on the touch and it's just that the card is getting used much more than normal.

I wish I could find where I saw the posts from people that had dieing cards that haven't tried android. I really don't think it's an exclusive problem.
[Touch CDMA Android Development] etx:
Yeah, I had a sd card go bad two weeks after I got my Touch last January. Now I'm on my third one this year. Definitely not an android issue, but the increased throughput could make it happen more often.
[Touch CDMA Android Development] derekwilkinson:
Great work so far!

Is there anyway we can get the portrait keyboard back for easier input? (without having to flip the device).

I hope GPS and the Camera function can come soon :) I am worried about using it without GPS...
[Touch CDMA Android Development] jim256:
I have also heard of this a lot with people on touch's long before android.
[Touch CDMA Android Development] pchasco:
I think wear leveling is performed by the SD card itself.

I wonder if there would be any benefit from moving /var/log off of the SD card and mounting it on a ram filesystem? A few megabytes would probably be enough. What do you guys think?
[Touch CDMA Android Development] etiger13:
Could someone possibly send me their dead SD card? I am curious as to how they are dead.
[Touch CDMA Android Development] pchasco:
It's dead in a very strange way...

When Android attempts to boot I get:

Init SD

Init SD Retry

Init SD Retry

Init SD Retry

Init SD Retry

Init SD Retry

Init SD Retry

Init SD Retry

...Ad Infinitum

Windows Mobile could still read it.

My computer could still read it when placed in a card reader. I ran CardTest on it and it quits after about 27% due to having exceeded the 50 error limit I've set. One of the reported sectors with error is sector 0.

When attempting to format the card with Windows it completes to 100% but then notifies me that the format failed.

Even after all of this, none of the data that was on the card seems to have been erased. Yes, that's right -- it's all still there. Even after a format. Even after running a write test with CardTest.