Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!

[callmesaul8889]

Originally Posted by foxmotoracer23

Did you remove the .txt on the new configuration file? I know I forgot to do that and the calibration was all messed up but once I removed the .txt and it became a .conf file it was all good.

yeah i removed the .txt and it became a .conf file. still nothing.. does the .conf~ file need replaced too?

[stellar19]

So the latest developments on this port have been awesome. However, I still can't get CDMA data to work with US Cellular. I've tried to set up the APN with the username / password for USCC data but still nothing. Is there another config file that I need to be looking at?

[mbg19]

I guess the next thing is better power management, but great work done your getting really good progress

[wehweh]

Yeah, this is really good. It seems to me that charging is working and it's reporting the battery level accurately now, but still always says its charging. Wi-fi works w/o having to declare a mac in the startup, very nice. And my god, the "u" key. Having 1/5 of your vowels missing is quite crippling, I must say. Really good stuff though, really snappy. I had a hard time waking it up from sleep on the first 2 boots, but it ironed itself out I guess, works like a charm now.

[makkonen]

Originally Posted by callmesaul8889

yeah i removed the .txt and it became a .conf file. still nothing.. does the .conf~ file need replaced too?

conf~ file does not need to be replaced. If you have the calibration command installed correctly, as you boot up, about half a page before the 'A N D R O I D' thing shows up, you should see a bunch of lines (7, I think) with touch_calibration in them. If those aren't showing up, it's not reading the calibration command.

Originally Posted by stellar19

So the latest developments on this port have been awesome. However, I still can't get CDMA data to work with US Cellular. I've tried to set up the APN with the username / password for USCC data but still nothing. Is there another config file that I need to be looking at?

Damn. You're sure you have the username and password correct? (Not sure how you'd test that... I guess some sort of dial up networking connection through windows mobile?) I don't know of anywhere else you'd have to change settings. But, then again, I haven't looked too closely at it. I'm sort of out of ideas on that one. except searching for vogue android users who have experience with cdma data connections that require a password.

Originally Posted by wehweh

Yeah, this is really good. It seems to me that charging is working and it's reporting the battery level accurately now, but still always says its charging. Wi-fi works w/o having to declare a mac in the startup, very nice. And my god, the "u" key. Having 1/5 of your vowels missing is quite crippling, I must say. Really good stuff though, really snappy. I had a hard time waking it up from sleep on the first 2 boots, but it ironed itself out I guess, works like a charm now.

Charging works. Reporting of whether it's charging does not. Battery reporting "works". What it does is look at the supposed voltage (though that reads a bit low), look at the charging/discharging rate, look it up in a table, and take an educated guess as to what that means the battery level is. This is not the official method for determining the battery level. In my experience, it reads consistently low (89-93% = 100% in WinMo. 5% = anything up to 25% in WinMo), and is jumpy as hell. I might tweak the coefficients again to make it line up a bit better with reality, but it's sort of a waste of time until we can actually figure out a more reliable method.

Agreed on the u key. You don't miss it until it's gone.

Originally Posted by mbg19

I guess the next thing is better power management, but great work done your getting really good progress

Yeah. I think today was my first day running Android instead of windows mobile while I was out and about -- good milestone. At this point, top priorities seem to be power management (4 hours battery life is not enough), hardware graphics acceleration (UI should be more responsive), and the memory limitations (unresponsive UI is not helped by having to reload apps every time you open them). And the crashes. Crashed once while I was using it today, then 3 more times when I tried to get it up and running again. Seems like if it makes it 5 minutes, it'll go 3 hours.

On a positive note, the hardware keyboard is faster in android than it has ever been in winmo. And the SMS app is not a bloated, unresponsive piece of garbage. So that was pleasant.

[wehweh]

Speaking of UI responsiveness, what's the progress on the OpenGL ES? I never read what the problem with that was.

[makkonen]

the MSM hardware 3d acceleration driver is currently not being built, I think. I don't know why, exactly... I know it's not working now, but I'm not sure if it was working in the past. I think at some point if you started a 3d app in WinMo to initialize the hardware (yep, that old story), it would work in Android. Not so much at the moment.

I haven't looked into it at all.

[makkonen]

Originally Posted by smarcin

The bad: the Market mostly causes my phone to crash. Sometimes it's just browsing the Market, but almost always when I try to download apps, my phone spontaneously reboots. Then, because Android remembers your downloads, when I get it booted back into Android, it often crashes before I can cancel the download.

The ugly. I DO use the hack of starting a call in WM before hitting haret. The first call I make usually works. I can hear and sometimes the person I'm calling can hear me. Sometimes they hear only static, though. After that first call, I don't even hear anything, and they get static when they answer. If someone calls me, I have no ringer, though the volume is turned up. I believe this is a known bug, though? I see the call on my screen. When I go to answer, I get nothing. The person calling me gets static.
...
I'm also getting a lot of fsck files generated, presumably at boot up. These, as I understand, are file system checks, supposedly because there's some problem with file corruption?

I have no real reason to prove this, but I'm thinking the Market problems are caused by memory issues, as in running out of memory. This could also account for other lockups and random reboots. Perhaps leaning out the number of apps that come with this build might help. We can, theoretically, download what we need from the Market. Something else that might help is something that is working on the Touch. On the Touch you can partition your SD card. You make the first partition fat32, and the other 2 partitions ext2. It seems to run faster that way, and I'd bet it also helps with memory issues. Of course you need access to LINUX to do this. Either a LINUX install (I dual boot my laptop) or running from a live LINUX CD/DVD. I think this is handled in the .conf file as well as the rootfs, though, so both would need to be set up to take advantage of this. A swap partition might help, too, though it might shorten the life of your SD card. (I just by the ones with a "lifetime" warranty.)

Sorry, I missed responding to this earlier. Thanks for the feedback.

I don't think the market crashes are due to memory, because it seems that the market is less likely to cause a crash if it's downloading over Wifi than if it's using cdma data. This is only my experience with a sample size of 1, so it's really nothing more than a hunch. I can confirm those crashes, though, and they are very vexing.

I haven't noticed the problems with call quality degrading -- but I've never run for long enough to get more than 2 or 3 calls, so I wouldn't have, anyway.

Re: Apps sucking up memory, I'm sure you've noticed that the newest XDANDROID build has removed basically every extraneous app, which seems to help a bit.

The FSCK files that show up on the sd card are nothing to worry about. If you have a keen eye at boot time, you can see that there's a DOSFSCK that runs before anything is done with the sdcard. It invariable creates one of those files, even if there is no damage. Then the regular fsck runs on the mounted data.img (which does tend to throw errors, because it's never cleanly unmounted; but hey, that's what fsck is for).

As far as running from a partition on the sd card, I've read about it in the Vogue forum on XDA, and in glancing at the init script on the XDANDROID rootfs, it has some checks in place to mount from a partition (I assume since the eclair build was ported from Zenulator's Vogue version). I haven't heard of anyone bothering to do it on RAPH/DIAM/etc, and would guess that there's a few more pieces that have to be put in place for it to work correctly, though..

[Vincentchan]

How to get cdma data work.I am using china telecom's cdma network.Seems not working with his package.

[tgun65]

Just a note, I'm on USCC and data is working fine on the 1-16 build. I've been able to download apps from the marketplace, check email, etc. The UI definitely seems snappier, but I have had a few spontaneous reboots.

Just keeps getting better!