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

[peterm20]

I tried to get on the google wave but I am waiting for my invite.

[paschott]

Karafa,
Just tried your suggestion on my ATT Fuze. I get down to some message that's half off the bottom of the screen and it seems to be locked up. Got the latest XDA files and the latest files from the Wave thread. Last message I can almost read is:

"mmcl: Command timeout"
"kernel BUG at kernel/workqueue ?:188!" (not sure what character is before that 188, but reasonably sure about that).

Looks like it's locked up again. I can't tell if it's trying to build a file or if I'm just stopped. Anyone know what I might try from here? Am I using the wrong files for an AT&T Fuze?

[getwilde]

I am able to boot and get to the android screen, but can't get past it due to incorrect calibration (I've downloaded the *.conf.txt file, renamed it and put it in /conf dir, as explained. I also tried the instructions on post 181.)
On reboot, I'm seeing an exception a few lines above the "A N D R O I D" line, which says:

Can't create  /sys/class/input/input3/calibration_points: nonexistent directory

Any thoughts on what might be causing this?

EDIT: Hold up. I didn't notice that part in the original instructions to delete all files named zImage*, modules*, and startup.txt. I think I might have had an extra modules* file on my SD card. I'll try this again and report back.

EDIT #2: Yes, that was my problem. I just needed to CAREFULLY read ALL instructions on the first post.

[karafa]

Originally Posted by paschott

Karafa,
Just tried your suggestion on my ATT Fuze. I get down to some message that's half off the bottom of the screen and it seems to be locked up. Got the latest XDA files and the latest files from the Wave thread. Last message I can almost read is:

"mmcl: Command timeout"
"kernel BUG at kernel/workqueue ?:188!" (not sure what character is before that 188, but reasonably sure about that).

Looks like it's locked up again. I can't tell if it's trying to build a file or if I'm just stopped. Anyone know what I might try from here? Am I using the wrong files for an AT&T Fuze?

Just follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=601751

This thread is for CDMA touch pro, not the GSM. You've got the GSM.

[paschott]

Should have figured it was something like that. As noted - I get confused on which version I have.

Thanks, Karafa. That should save me quite a bit of time/trouble. :P

[borderal]

when i try to run it says Cannot open script file\storagecard\xdandroid.24.01.10\default.txt

[peterm20]

Originally Posted by borderal

when i try to run it says Cannot open script file\storagecard\xdandroid.24.01.10\default.txt

its gotta be on /storeage_card/ can't run from a sub directory

should be like

/sdcard/zimage
/sdcard/modules-xxxx
/sdcard/haret.exe
/sdcard/AndroidApps
/sdcard/startup.txt
/sdcard/rootfs.img ...etc

[karafa]

Hey, the discussion wave says it's full. Perhaps it needs a pruning? Posting this here..

The functionality of this is pretty good. Texting, calls, data, wifi, backlight, keyboard, buttons... it's very very functional. I wouldn't call it alpha anymore, to be honest. I haven't had a crash, I think we're at a good point in terms of stability. Actually, trying to load a video from the weather channel app caused what looked like a 'soft reboot' in android, but I don't think we should expect that to be working right now.. the basic promised functionality works without much hassle.

I'm curious as to what's on the developer's agenda? Regarding the touchscreen, where do the drivers for it come from? I'm wondering if since this is designed for a capacitive touch screen, if perhaps we would be able to write a new driver with a resistive touch screen in mind..? it seems that dragging motions on this screen like are not consistent. For instance, unlocking the screen with the pattern lock is fairly difficult, it doesn't really keep a consistent line without pressing hard and doing it slow. Same with placing icons on the home screen.. hard to do continuous drags.

I've also read that the graphics are running in software mode.. and that at one point, starting something '3d' would allow haRET to access the 3d hardware just like the mic situation.. any more info on this? Would this kind of acceleration speed up menus and everyday use? Or only in games..? I'm a little confused as to what exactly uses the graphics hardware at this point.

The other thing I've been wondering is kind of vague, but I'm wondering what kind of optimizations (besides crucial drivers that are missing at this point) can be made to speed up the interface and extend battery life. Are there big chunks of code that are inefficient on the CDMA touch pro? Maybe it's too early to tell at this point, I'm not sure. What advantages, if any, are there to going from using haRET to a flashable rom?

Again, I'm in no way trying to rush anyone here, I'm just trying to see if it's possible to lay out the tasks ahead of us before we can do something like make this a flashable rom, because then maybe people can work at bits and pieces of it and help out.

[Batman]

i cant get data to work...

[marco-polo]

Originally Posted by spb37

MP,
My mistake was letting the voice call finish before the phone got midway into the android boot. Now I call my sprint voice mail midway into the android boot the call gets cut off.

Ohhhh .. so you have to call, then boot android, while you're on the phone. Not just do a call, close the call, boot android. Damn, I'm stupid.