Android/Linux for CDMA Touch Pro 2

[jackreisinger1511]

Originally Posted by cflynt

Is it possible your Calibration for the screen is messed up? As sensitive as the screen is, it is real easy to miss a box when calibrating, you should have a total of 5 boxes you tapped on during setup. If that is a possibility, then I would delete your ts-calibration file from the root and next time you boot Android it should prompt you to re-calibrate, just be careful, some say using your finger to touch each box works better, haven't tested that theory yet myself, but regardless make sure it sees each box, Top left, Top Right, Middle, Bottom Left and Bottom Right. In that order, if you didn't have to touch a box then it took one of your taps as it on a previous tap. So delete and repeat.

Good Luck.

Thank you for the help so far. I attempted what you suggested but I do not see a calibration after deleting the ts-calibration file. The only screen I can navigate to after the animated "X" splash screen are the "Welcome to XDANDROID" and "Learn how to use your XDANDROID" screens. The weird thing is I got a force close notificaition which responded to the touchscreen and was accurate. However when I attempt to tap "Skip" or "Begin" they do not respond to touch.

Is there a way I can dump a log file or something I can post from the SD card that would help troubleshoot?

[cflynt]

Originally Posted by jackreisinger1511

Thank you for the help so far. I attempted what you suggested but I do not see a calibration after deleting the ts-calibration file. The only screen I can navigate to after the animated "X" splash screen are the "Welcome to XDANDROID" and "Learn how to use your XDANDROID" screens. The weird thing is I got a force close notificaition which responded to the touchscreen and was accurate. However when I attempt to tap "Skip" or "Begin" they do not respond to touch.

Is there a way I can dump a log file or something I can post from the SD card that would help troubleshoot?

I am no expert, but that makes no sense whatsoever. Do you have some more info on your setup? Like what ROM are you using? Is it Calkulins Android ROM? If so and running off his setup instead of the SDCard, maybe he has a ts-calibration file in there. Or are you trying to run Android via a directory on your SDCard, if so maybe for some reason you have that ts-calibration file somewhere in the directory. But I was pretty sure it only accesses it via the root.

If you really want to work on getting this going, I would go ahead and wipe all the Android stuff off the storage card and try and copy the files again. Either use one of the ts-calibration files others have posted in this thread, sorry, don't have one avail to upload for you right at moment, but if still in need I will do it when I can here later on. But sounds like something is hosed in your data.img or something. So I would basically start over and see if that helps you at all.

Using the Civic rootfs that MrPippy helped with will work, but you will be missing out on the IMEI stuff and updated RIL fixes that make it run more stable and you won't have Market then and that will be a huge loss. So I would focus on working on getting the current rootfs working and see if what might be going on.

Sorry bout all your woes, hopefully starting over helps. But going back to the ts-calibration. I have done numerous tests on where it sees files and such and if that file doesn't exist it won't even finish booting till the screen gets calibrated, either right or wrong heh. You will see a little white box in the top left corner if it is working and if you can read it, it is asking you to calibrate by tapping the box. And then of course it moves onto the next box etc.

[Jackrm9]

[QUOTE=cflynt;1619388]I am no expert, but that makes no sense whatsoever. Do you have some more info on your setup? Like what ROM are you using? Is it Calkulins Android ROM? If so and running off his setup instead of the SDCard, maybe he has a ts-calibration file in there. Or are you trying to run Android via a directory on your SDCard, if so maybe for some reason you have that ts-calibration file somewhere in the directory. But I was pretty sure it only accesses it via the root.

I had this same problem touch screen not accurate

[cflynt]

Originally Posted by Jackrm9

I had this same problem touch screen not accurate

You had the problem with Calkulin's ROM or just in general with a bad ts-calibration file?

[Jackrm9]

i was using his 29mb rom with droid all in one build

sorry the problem was the calibration....

[cflynt]

Originally Posted by Jackrm9

i was using his 29mb rom with droid all in one build

sorry the problem was the calibration....

Ok, kinda what I was thinking. So ya, that's why no matter what the other guy is doing with the ts-calibration file it is still causing him fits. I am running that ROM but I am booting to the SD card with my own copy of Android. So is the ts-calibration already on the device or does it create it on the device on first boot? If so, then hopefully it still can be deleted and then try again. Otherwise, I just recommend you copying the proper files to the SDCard and running it from there instead, Calkulin makes a shortcut to run Haret.exe on SD. Just run it instead once your files are on the SDCard.

Edit: Just wanted to point out, his 29MB ROM had a bug with Sound and wouldn't let in-call volume and mic work. You want to upgrade to his 28MB ROM if you haven't already.

[matthewb57]

Wow... that took a long time to go through!

Amazing progress as usual though. Good job guys!

In an attempt to cut down on all the similar questions and answers cluttering the thread, it would be good if people headed over to the http://www.androidonhtc.com wiki and edited the Rhodium FAQ page I just created. I have dumped the old wiki FAQ and also the FAQ that has been compiled at the beginning of this thread. Anyone can create an account and edit the page to update it.

If you just take a couple minutes and post questions and answers that you come across in the wiki, everyone can benefit.

http://www.androidonhtc.com/wiki/Rhodium_FAQ is the direct link.

MrPippy or cflynt, can you include this link in the first post(s)?

Thanks.

[jackreisinger1511]

Originally Posted by cflynt

I am no expert, but that makes no sense whatsoever. Do you have some more info on your setup? Like what ROM are you using? Is it Calkulins Android ROM? If so and running off his setup instead of the SDCard, maybe he has a ts-calibration file in there. Or are you trying to run Android via a directory on your SDCard, if so maybe for some reason you have that ts-calibration file somewhere in the directory. But I was pretty sure it only accesses it via the root.

If you really want to work on getting this going, I would go ahead and wipe all the Android stuff off the storage card and try and copy the files again. Either use one of the ts-calibration files others have posted in this thread, sorry, don't have one avail to upload for you right at moment, but if still in need I will do it when I can here later on. But sounds like something is hosed in your data.img or something. So I would basically start over and see if that helps you at all.

Using the Civic rootfs that MrPippy helped with will work, but you will be missing out on the IMEI stuff and updated RIL fixes that make it run more stable and you won't have Market then and that will be a huge loss. So I would focus on working on getting the current rootfs working and see if what might be going on.

Sorry bout all your woes, hopefully starting over helps. But going back to the ts-calibration. I have done numerous tests on where it sees files and such and if that file doesn't exist it won't even finish booting till the screen gets calibrated, either right or wrong heh. You will see a little white box in the top left corner if it is working and if you can read it, it is asking you to calibrate by tapping the box. And then of course it moves onto the next box etc.

I'm currently using the standard Verizon/Windows Mobile 6.5 ROM. My device only has 184mb of RAM and 254mb of Storage which is different than what's posted on the Verizon site. Would that be why I can not get the new build of Android to load? Do I need to change some parameters?