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

[hamagc]

i would delete everything and start from scratch and see if that makes a difference. try the latest 2/23 package mak posted a few pages back. he didn't add it to the first post, i don't think it did enough for him to want to add it. maybe it'll give you a different outcome.

[makkonen]

Originally Posted by peterm20

Wouldn't it be the keyboard map files in the XDAndroid system.sqsh that would make the keyboard go funky? I don't think they've changed since December at least that is what is reported when I do a 'ls -a'

I don't know what it would be. The keyboard files did change a bit probably around december/january -- but I can't think why that change, or anything to do with the keyboard mapping in android, would cause the keyboard to work at boot, and then stop working. That sounds like something unrelated to keymaps. Possibly some sort of keyboard handler in Android, though I don't think such a thing exists...

From what everyone's saying, it sounds like it's NOT an issue at the kernel level, since from the command line it hasn't stopped working. (For those testing that: the kernel will throw a hung_task_timeout error and some other data every few minutes, but I don't think that should stop you from being able to keep typing.)

Edit: I don't know what was going on when I read through those posts before, but I take it back. Clearly my reading comprehension was suffering. So, it... does sound like it's at the kernel level? But is weirdly intermittent? I don't really know what to make of it. I really want to say 'hardware failure' and stop thinking about it, but that's probably a dodge. Very strange that a large majority of people haven't reported anything like this.

[makkonen]

Originally Posted by Waus26

I've been playing with this for over a day now and I like it. GPS seems to work, despite what the first post tells us.. (Google Maps locates with a blue spot on the map where I am ATM)

The thing that me annoyed the most was putting the screen of with the hang-up bottun instead of the power on/off button on top of the phone..

It's been an hour of seven since 100% battery and it's now somewhere at 35% btw.

You will probably have a different experience than most people here, since your version is a bit more fully supported than ours. A lot of our bugs don't apply to your model.

GPS doesn't work, but cell tower triangulation does. (Perhaps more robustly on GSM than CDMA.) That's how it's placing you on the map.

And... I find myself hitting End Call to turn the phone off in WinMo now. It sort of makes more sense, even there. We've already got back and home buttons, which do basically the same thing as End. My Android brainwashing is nearly complete, it seems.

Originally Posted by tom6433

ok i am using the 2/8 files from XDA and the 2/18 files that were posted here.

as far as my issue with it resetting, i deleted my data file and went through teh startup process again. once i completed the statup process and tried to open the web brower it reset. any idea what could be causing it? before i didn't use it b/c of the KB issue, but now i can't use it b/c it resets.

Sounds like you could've stumbled on a data connection panic. There's still a few bugs like that out there to be squashed. When I've had crashes like that, the browser opens, but then when it starts trying to download it reboots. Is that what you're seeing? You could try wiping your data.img and starting over, see if it avoids that problem next time. Or you could try turning on Wifi and seeing if that gets around it.

Or it's something else crashing the browser, and I have no idea what to do.

[tom6433]

Originally Posted by makkonen

You will probably have a different experience than most people here, since your version is a bit more fully supported than ours. A lot of our bugs don't apply to your model.

GPS doesn't work, but cell tower triangulation does. (Perhaps more robustly on GSM than CDMA.) That's how it's placing you on the map.

And... I find myself hitting End Call to turn the phone off in WinMo now. It sort of makes more sense, even there. We've already got back and home buttons, which do basically the same thing as End. My Android brainwashing is nearly complete, it seems.



Sounds like you could've stumbled on a data connection panic. There's still a few bugs like that out there to be squashed. When I've had crashes like that, the browser opens, but then when it starts trying to download it reboots. Is that what you're seeing? You could try wiping your data.img and starting over, see if it avoids that problem next time. Or you could try turning on Wifi and seeing if that gets around it.

Or it's something else crashing the browser, and I have no idea what to do.

i will take a closer look at it this weekend. i was bored at work so i thought i would start from scratch, but there is no public wifi there. so it did not have an available connection at first start.

[arrrghhh]

Originally Posted by makkonen

Or it's something else crashing the browser, and I have no idea what to do.

I love your quotes Makk. You must be a teacher of sorts, because you have ridiculous patience.

[makkonen]

Originally Posted by arrrghhh

I love your quotes Makk. You must be a teacher of sorts, because you have ridiculous patience.

Thanks for saying. I try my best.

...though you should hear the awful things I say about you guys on irc.

[chrialex]

Lol, yeah, I get a good laugh out of the logs sometimes...

[vi316435]

i have just installed everything as the first page suggested and had no major issues yet besides the black screen in the boot up. i am running mighty rom ver 6.5 windows and booting from sd card. Thanks for giving me an alternative and making me love my phone more than ever !!

[tom6433]

just saw on XDA that a new rootfs is available and bluetooth is supposed to work now. i don't have anything that uses bluetooth, so someone else will have to report on that.

http://xdandroid.southcape.org/rootfs/

[makkonen]

I believe that only applies to GSM phones, unfortunately. Our bluetooth issues go deeper. (Not 100% sure of that, since... I also don't use anything with bluetooth.)