Android/Linux for CDMA Touch Pro 2

[mikezpc]

Originally Posted by Boominsvx

Do you always delete your data.img? In recent attempts, I was finding that I had no service and could not connect to anything if I had android in an "Android" folder. Moving it back out and re-trying a fresh install, I got it back. For this reason, I'm skeptical about advertising it.

No dude i havent deleted data.img since civic's last build i think or the xandroid package maybe, only thing i do is keep updating zimage and modules, and this is my current start up file settings

set RAMSIZE 0x6000000
set RAMADDR 0x10000000

set mtype 2292
set KERNEL zImage
set initrd initrd.gz

#pwf dm.txt 0x8e0000 0x20000

set cmdline "rel_path=Android msmvkeyb_toggle=off gsensor_axis=2,1,3 lcd.density=240 htc_hw.force_cdma=1 physkeyboard=rhod400"

boot

and yeah everything is in the Android folder but of course it creates the a couple of extra folders, like the .thumbnails in the DCIM folder, cache and data i think, one thing i noticed after setting the rel_path=Android is that the data.img is inside the Android folder, without this setting i'm pretty sure it stays on the root, so maybe thats why u were having some issues?

[cflynt]

For those that want to try it, mind you this hasn't been completely signed off on yet, but we are pretty confident it is fine. Here is the latest kernel from today with the tssc fix in it for the double taps on the touchscreen. Thanks go out to bzo for the patch. I have patched todays latest kernel with it and am running it fine myself. So try as you might, hopefully we will get it committed here sometime later tonight.

Just extract, delete your existing zImage and modules files, and then copy these files over.

Edit: Guess I should mention I have been running the patch for a couple of days now without an issue, I just updated to the latest kernel for posting.

[Boominsvx]

Trying it now. I suspect we should probably delete our existing tscalibration file?

[dbrown2]

Let me say Thank You so much for all of your work and others that works on this project too. This fix is great... Thank you again.

Originally Posted by cflynt

For those that want to try it, mind you this hasn't been completely signed off on yet, but we are pretty confident it is fine. Here is the latest kernel from today with the tssc fix in it for the double taps on the touchscreen. Thanks go out to bzo for the patch. I have patched todays latest kernel with it and am running it fine myself. So try as you might, hopefully we will get it committed here sometime later tonight.

[sfxc13]

Originally Posted by cflynt

For those that want to try it, mind you this hasn't been completely signed off on yet, but we are pretty confident it is fine. Here is the latest kernel from today with the tssc fix in it for the double taps on the touchscreen. Thanks go out to bzo for the patch. I have patched todays latest kernel with it and am running it fine myself. So try as you might, hopefully we will get it committed here sometime later tonight.

Just extract, delete your existing zImage and modules files, and then copy these files over.

Edit: Guess I should mention I have been running the patch for a couple of days now without an issue, I just updated to the latest kernel for posting.

Wow scrolling is way way way better with this. Thanks for the prerelease!

[Boominsvx]

Originally Posted by cflynt

For those that want to try it, mind you this hasn't been completely signed off on yet, but we are pretty confident it is fine. Here is the latest kernel from today with the tssc fix in it for the double taps on the touchscreen. Thanks go out to bzo for the patch. I have patched todays latest kernel with it and am running it fine myself. So try as you might, hopefully we will get it committed here sometime later tonight.

Just extract, delete your existing zImage and modules files, and then copy these files over.

Edit: Guess I should mention I have been running the patch for a couple of days now without an issue, I just updated to the latest kernel for posting.

Anyone else having trouble with the market using this? I see the post about processes being stopped. Pretty sure thats android.process.media. Most likely a side effect of recent audio work. I'm going to try it again with a fresh install and see. Just looking for user input (as they asked for).

Edit: My outcome - Market gives an error and forces closed. Fresh install stopped some "process.media" errors, but it seems like a jump backward for us in other areas. I hope this isn't the one they will be releasing. Screen is phenominal, but I believe this is going back a few steps as well. Input anyone?

[deboy69]

Originally Posted by cflynt

For those that want to try it, mind you this hasn't been completely signed off on yet, but we are pretty confident it is fine. Here is the latest kernel from today with the tssc fix in it for the double taps on the touchscreen. Thanks go out to bzo for the patch. I have patched todays latest kernel with it and am running it fine myself. So try as you might, hopefully we will get it committed here sometime later tonight.

Just extract, delete your existing zImage and modules files, and then copy these files over.

Edit: Guess I should mention I have been running the patch for a couple of days now without an issue, I just updated to the latest kernel for posting.

Just copied over your kernal you posted. Makes my phone hang 1 second into boot sequence on dma_addr 23 a600000. curser is still blinking.

*update: only hangs when plugged into usb

[jeep447]

Originally Posted by cflynt

For those that want to try it, mind you this hasn't been completely signed off on yet, but we are pretty confident it is fine. Here is the latest kernel from today with the tssc fix in it for the double taps on the touchscreen. Thanks go out to bzo for the patch. I have patched todays latest kernel with it and am running it fine myself. So try as you might, hopefully we will get it committed here sometime later tonight.

Just extract, delete your existing zImage and modules files, and then copy these files over.

Edit: Guess I should mention I have been running the patch for a couple of days now without an issue, I just updated to the latest kernel for posting.

Ok i might be crazy but I just added the command line switch for speakerphone and with this kernal my speakerphone works!!! I can hear the person on the other line and she could hear me all through the speaker! Anyone else got this or did i miss something? thanks

[Boominsvx]

Originally Posted by mikezpc

No dude i havent deleted data.img since civic's last build i think or the xandroid package maybe, only thing i do is keep updating zimage and modules, and this is my current start up file settings

set RAMSIZE 0x6000000
set RAMADDR 0x10000000

set mtype 2292
set KERNEL zImage
set initrd initrd.gz

#pwf dm.txt 0x8e0000 0x20000

set cmdline "rel_path=Android msmvkeyb_toggle=off gsensor_axis=2,1,3 lcd.density=240 htc_hw.force_cdma=1 physkeyboard=rhod400"

boot

and yeah everything is in the Android folder but of course it creates the a couple of extra folders, like the .thumbnails in the DCIM folder, cache and data i think, one thing i noticed after setting the rel_path=Android is that the data.img is inside the Android folder, without this setting i'm pretty sure it stays on the root, so maybe thats why u were having some issues?

No, all of mine were correct, thus the full boot. It just had no service when I got into it. At best, you should copy a backup of the android os to your desktop, delete data.img off the sd card, and move everything out to the root. If it works then, we know it's a problem having to do with the folder. After, you could move the data.img back and overwrite the new one. That would put you back where you were. I had mine configured correctly as well.

Edit: Screen fix... WOW, She really likes the way I touch her now. Can I get one of these for my future ex wife?

[ndno]

Hey cflynt, thanks for maintaining the FAQ; it's very very helpful. Is there anyway you can bold the questions to make it easy for people to identify the questions? Thanks!!!