[12-15-09]Android CDMA TouchPro: TEXT, TALK, data and wifi(RAPH800) Ported!!!

[makkonen]

Originally Posted by travisr528

I have data.img that is 104M on the rood of my sd card. I tried using a 512 lg sd card from my wifes phone, that did not have anything on there too. I will try clearing mine and try.

Something's definitely wrong there. Either it failed to make the data.img correctly, or it got corrupted. I have no idea why that would continue happening, but I'm fairly certain it's where your problems stem from.

Originally Posted by Noghri

The CDMA works the vast majority of the time, but I do suffer from the sleep issue if I touch the screen whilest Rx/Tx data over CDMA (not over wifi). This, combined with the fact that regardless of my battery state and charging status it always shows 5% battery charge and that the screen is almost always dimmed, says to me that the main problems with the intermittent data Tx/Rx and the sleep while doing data Tx/Rx is not only a poor signal, but also a power management issue. Subsequently, I think power management is a very important area to look at. I haven't done any coding or any extensive *nix in probably 5-7 yrs, but I generally pick things up almost instantaneously, so if someone could hook me up with the source code for this, I'd love to collaborate in an effort to get this working properly for everyone. (Can't promise I'll be of much use though, haha)

The dimming backlight issue has to do with automatic backlight dimming being enabled in windows mobile before you boot. It confuses Android.

We'd love to have more people working on it, so come on aboard. (People who can program C and know about low level drivers would be even better; but, hey, we can all learn.) There are instructions in the wave about how to get the source with git, modify it to boot on CDMA, and compile it. That all assumes you have a working linux environment to work with, but that's not too tough (get virtualbox, install ubuntu on a VM, apt-get install git). If you've got questions about building, ask them over there, so we can make that as complete a source for information as possible.

To answer your other questions:

GPS is a fairly long way away, I think. Not working on CDMA or GSM devices.

I'm not sure about the Hero source, but the big issues now are more to do with the specifics of the raphael board than the chipset, so the amount of overlap is probably, disappointingly, less than expected.

And, actually, you can throw everything into an 'android' folder on the sdcard (not sure if capitalization matters), and you don't even have to change anything in your startup.txt. It's setup this way in the init script. I just learned this recently.

[catfishk]

Originally Posted by travisr528

I have data.img that is 104M on the rood of my sd card.

the data.img wasn't fully created. i have had had the process die half way through creating the data store... a lot. just delete it and try again. once it manages to create a 256MB image, it will bypass that initial creation. however, it will not boot or resume creation if a partial file exists- it will just reboot usually

[travisr528]

I want to thank everyone,(catfishk,makkonen,Erythros and Noghri) I am further than I have ever been to getting this to fully boot, but I am now at a different error.
"Failed to find system.img on sd card
/bin/sh: can't access tty; job control turned off
/ #"

[travisr528]

Does anyone know how true this quote is "Other comments that should be made about the Phone Prep -> The SD card needs to be reformatted if it was formatted under WinMO. WinMO will use the FAT32 FS to set up the card and android is expecting the FS as defined by SD Association."

[Noghri]

Originally Posted by makkonen

The dimming backlight issue has to do with automatic backlight dimming being enabled in windows mobile before you boot. It confuses Android.

I tried completely disabling all power saving and backlight control features in WinMo then booting Android and it made no difference at all... I'm curious, how would that even effect it anyway? Doesn't HaRet completely shut down WinMo and boot Android from scratch? I mean how could the entirely seperate OS have anything to do with the settings from the other? Or is HaRet actually just an emulator that runs an Android environment within WinMo? I haven't really read up much on HaRet yet, as I said I just started messing with my phone recently...

Originally Posted by makkonen

GPS is a fairly long way away, I think. Not working on CDMA or GSM devices.

What's the deal with it to make it so far off? I thought it just ran on the same radio as CDMA data, but with a seperate tunnel or port if you will... Is this entirely wrong? Must admit I hadn't even cared to try GPS until I bought a phone with full GPS capabilities...


-an increasingly curious nog

[makkonen]

Originally Posted by travisr528

Does anyone know how true this quote is "Other comments that should be made about the Phone Prep -> The SD card needs to be reformatted if it was formatted under WinMO. WinMO will use the FAT32 FS to set up the card and android is expecting the FS as defined by SD Association."

I'm not aware of that being the case. Though I do think the last time I formatted my microsd card, it was as FAT, not FAT32. A quick search shows people recommending FAT32, so I don't think that's it.

Originally Posted by Noghri

I tried completely disabling all power saving and backlight control features in WinMo then booting Android and it made no difference at all... I'm curious, how would that even effect it anyway? Doesn't HaRet completely shut down WinMo and boot Android from scratch? I mean how could the entirely seperate OS have anything to do with the settings from the other? Or is HaRet actually just an emulator that runs an Android environment within WinMo? I haven't really read up much on HaRet yet, as I said I just started messing with my phone recently...

It's neither. Well, it's the first, but with complications. Yes, HaRET is loading a linux kernel and completely replacing Windows Mobile in memory. However, it does this without cycling power or reinitializing the device. So the linux boot just steps into this bootstrapped environment and takes the handoff. It's a weird sort of hybrid... frankenstein's monster situation. As for your backlight issues, I'm surprised. I never had them, and people who have generally have had them solved by turning off WinMo's auto-brightness.

What's the deal with it to make it so far off? I thought it just ran on the same radio as CDMA data, but with a seperate tunnel or port if you will... Is this entirely wrong? Must admit I hadn't even cared to try GPS until I bought a phone with full GPS capabilities...

Yes, it is a part of the same radio. A non-functioning part, in the current smd driver.

The HTC Vogue (another MSM 7500-series device) now has mostly working GPS. I was just saying it seemed a long way off because the vogue has had a build with working GPS for 3 days, and is a comparatively mature, stable port. The vogue port over a year ago was where the CDMA raphael port is today.

However, there is overlap, and one may hope that since it's working on the vogue, that knowledge can just be lifted up and transferred over to our project. I am not particularly hopeful, because I see no one with the expertise, interest, and a CDMA RAPH/DIAM in his/her hand.

[vestaviajag]

I finally tried to get this to work on my Touch Pro... I've been reading for weeks, and think I know how to get it to the point where everyone else has it; but I keep getting stuck on the boot screen. It is prolly something easy, but I can't see where anyone else has had this problem.

I downloaded the newest package from CUBT, and the newest z-info, but I when I boot, it sticks... it gets to

[ 10.255981] mmc1: host does not support reading read-only stich, assuming write-enable
[ 10.291198] mmc1: new SD card at address cd5d
[ 10.310424] mmcbik0: mmc1:cd5d SU025 1985024KiB
[ 10.329101] mmcblk0: p1 < p5 >

I don't know what to do, what am I royal-y messing up? thanks

EDIT: with all the versions and startups, I hate to ask this, but can someone give me detailed instructions on excatly what to run, how to copy it, and which versions, because I'm confused, and I typically know what/how to mess with my TP, I'm not an idiot, just feel like one cause I'm lost.

[makkonen]

I'm not sure (errors seem to be able to pop up from all sorts of weird places), but it sounds like you're trying to boot off the non-customized zImage. That's usually what causes a hang at mmcblk0: p1. (the little <p5> after makes me think it might be something different, though.)

First get the 11-22 package from Connect-UTB. Dump the files to the root of the sd card. Delete startup.txt, any zImages, and rootfs.img. Move raph800.txt from 'startup-configs' to the root of the sd card, and rename it to startup.txt.

Get the customized files from this post. Put the zImage-2009-12-08-cdma-data on your sd card and rename it to just zImage. Put the other two files from the zip on your sd card as well. If it doesn't get past mmcblk0: p1 then... well, it's something else.

[catfishk]

Originally Posted by travisr528

"Failed to find system.img on sd card
/bin/sh: can't access tty; job control turned off
/ #"

just try to do it all over again, with fresh files. it's a PITA i know, but this is a very picky boot process. eventually it WILL work with the instructions on Connect-UTB and makkonen's post. sometimes i just have to blow it all out and try fresh, then boot over and over to get it to finally come up. however, once it has fully initialized it seems to be stable from then on, that is until i replace my kernel again :/

[orangekid]

so does this not work for diamond at all?