Android/Linux for CDMA Touch Pro 2

[rushco]

Wirelessly posted (Opera/9.5 (Microsoft Windows; PPC; Opera Mobi/17992; U; en))

Originally Posted by johnpro112

Hey how about answering there question and tell them to look at post 1 because it's a waste of time just saying look at post 1 and not really trying to explain how to fix it to them. I'll be more productive and it'll make everyone look less like a jerk saying "ohh we answer this question read the fourms, learn how to search and etc" what sounds better is " (insert answer) and you can find more answers on faqs on page 3) imo it save time for the poster and maybe future people reading the thread using the "search" button

Thing is we were doing that and we do. We like to think it works. I say for every 10 downloads we get 1 repeat question. So most people get it or search. It is that 1 out of 10 people who won't do anything but download and ask questions. Those people we help and tell to search but there is always the one out of ten that will skip everything and ask questions.

It's like cooking a meal for the first time. You will read up on how to cook it and eat it. If something doesn't taste right you figure out what you did wrong by rereading and seeing if there is anything you missed. The info is there for you. The easy way out is asking mom why it tastes this way or what to do to fix it.

You figure out how to download it and install it. If something doesn't work you figure out what you did wrong by rereading and see if there is anything you missed. The info is all there. The easy way out is asking the members why it doesn't work.

Some people do get stumped. I'll admit that. Something this easy shouldn't stump you though. If it does maybe it is too advanced. Just like cooking something too advanced. But then how do you learn. You ask questions and that's what a forum is. With a forum though most of the time if you have a problem someone else probably did. So you search to find the answer.

Sorry for my long rant. Some people need to think other ways so hopefully this helps people see another point of view on this topic.

[MultiMatt]

Hey guys,
I have been playing with this on my TP2 for over a week now, and following the thread all the way through. I have been taking notes on the differences between Android and WM so I can do a demo of the dual-boot at a monthly meeting we have here in Louisville, KY.

I have added some apps & widgets, and have set up the device quite nicely. Obviously, there are things still not working, but I was set to go for this Tuesday's meeting (23rd).

I routinely play with the Android portion for a while, then boot back over to WM for my regular use. Hasn't been a problem at all.

Suddenly yesterday, I attempted to boot into Android and noticed it was taking an excessively long time. I did a soft-reset and tried again. Seems the boot is getting stuck in an endless loop at the part where the colorful X is animated. It will freeze up for a moment on the X, then will do that "double-vibrate thing again" and begin animating the X again. Never gets beyond that.

Aside from cosmetic tweaks I have been doing for demo purposes, such as adding widgets to the home screen, saving some bookmarks in Opera Mini, etc, I have not done anything different, but I'm stuck in this loop.

Tried some of the latest zImage and modules files, but the result is still the same. I REALLY don't want to start from scratch on my card again - I've done a lot of work to prepare for my Tuesday meeting. Aside from the zImage and Modules files, is there something else I can try overwriting to get past this endless loop at startup?

Thanks, and sorry for being lengthy...

[rushco]

Wirelessly posted (Opera/9.5 (Microsoft Windows; PPC; Opera Mobi/17992; U; en))

Originally Posted by MultiMatt

Hey guys,
I have been playing with this on my TP2 for over a week now, and following the thread all the way through. I have been taking notes on the differences between Android and WM so I can do a demo of the dual-boot at a monthly meeting we have here in Louisville, KY.

I have added some apps & widgets, and have set up the device quite nicely. Obviously, there are things still not working, but I was set to go for this Tuesday's meeting (23rd).

I routinely play with the Android portion for a while, then boot back over to WM for my regular use. Hasn't been a problem at all.

Suddenly yesterday, I attempted to boot into Android and noticed it was taking an excessively long time. I did a soft-reset and tried again. Seems the boot is getting stuck in an endless loop at the part where the colorful X is animated. It will freeze up for a moment on the X, then will do that "double-vibrate thing again" and begin animating the X again. Never gets beyond that.

Aside from cosmetic tweaks I have been doing for demo purposes, such as adding widgets to the home screen, saving some bookmarks in Opera Mini, etc, I have not done anything different, but I'm stuck in this loop.

Tried some of the latest zImage and modules files, but the result is still the same. I REALLY don't want to start from scratch on my card again - I've done a lot of work to prepare for my Tuesday meeting. Aside from the zImage and Modules files, is there something else I can try overwriting to get past this endless loop at startup?

Thanks, and sorry for being lengthy...

Maybe try a new startup.txt or post it here so we can look at it. Not sure if that could be the reason.

[gmfeny]

Originally Posted by MultiMatt

Hey guys,
I have been playing with this on my TP2 for over a week now, and following the thread all the way through. I have been taking notes on the differences between Android and WM so I can do a demo of the dual-boot at a monthly meeting we have here in Louisville, KY.

I have added some apps & widgets, and have set up the device quite nicely. Obviously, there are things still not working, but I was set to go for this Tuesday's meeting (23rd).

I routinely play with the Android portion for a while, then boot back over to WM for my regular use. Hasn't been a problem at all.

Suddenly yesterday, I attempted to boot into Android and noticed it was taking an excessively long time. I did a soft-reset and tried again. Seems the boot is getting stuck in an endless loop at the part where the colorful X is animated. It will freeze up for a moment on the X, then will do that "double-vibrate thing again" and begin animating the X again. Never gets beyond that.

Aside from cosmetic tweaks I have been doing for demo purposes, such as adding widgets to the home screen, saving some bookmarks in Opera Mini, etc, I have not done anything different, but I'm stuck in this loop.

Tried some of the latest zImage and modules files, but the result is still the same. I REALLY don't want to start from scratch on my card again - I've done a lot of work to prepare for my Tuesday meeting. Aside from the zImage and Modules files, is there something else I can try overwriting to get past this endless loop at startup?

Thanks, and sorry for being lengthy...

If worse comes to worse try deleting everything except your system.sqsh file... That file should save all your setting. But i don't know about installed programs those might need to be installed again.

[kawaiius]

i cant believe we dont have sound yet..i was sure we would have it by now lol.

[citats]

Originally Posted by MultiMatt

I REALLY don't want to start from scratch on my card again - I've done a lot of work to prepare for my Tuesday meeting. Aside from the zImage and Modules files, is there something else I can try overwriting to get past this endless loop at startup?

Have u tried deleting all the .rec files off your card?

[MultiMatt]

Originally Posted by citats

Have u tried deleting all the .rec files off your card?

Interesting you say that! I was just looking at all the contents on my SD card, and I had 36 FSCK.rec files! The first file was 0kb, 34 files were 32kb, and one file (FSCK0024.REC) was 608k - odd...

I removed them all, and rebooted. Still the same endless loop at the X animation. Damn...

@rushco: I compared my startup text file to some originals, and it is the exact same...

@gmfeny: aside from saving my system.sqsh file, what about the data file? It's 256MB, so I have to think it contains something important? Or not?

If I don't get it resolved shortly, I'm just going to wipe it all out and start fresh - my only concern is having this happen right when I'm about to demo at the meeting, with dozens of people watching!

[cornelious2]

yes data.img holds many settings as well. if you have access to an ubuntu install on someones computer you can mount that and pull off specifics but its alot of work for just UI tweaks and the possible game save.

[yuyjust]

Originally Posted by MultiMatt

Interesting you say that! I was just looking at all the contents on my SD card, and I had 36 FSCK.rec files! The first file was 0kb, 34 files were 32kb, and one file (FSCK0024.REC) was 608k - odd...

I removed them all, and rebooted. Still the same endless loop at the X animation. Damn...

@rushco: I compared my startup text file to some originals, and it is the exact same...

@gmfeny: aside from saving my system.sqsh file, what about the data file? It's 256MB, so I have to think it contains something important? Or not?

If I don't get it resolved shortly, I'm just going to wipe it all out and start fresh - my only concern is having this happen right when I'm about to demo at the meeting, with dozens of people watching!

I have that exact same thing happen to me about 6 days ago. Wont go past black scrolling text and sometime if I get lucky I'd get as far as the animation. Tried to fix it for couple of days, then I gave up I ended up reformat the whole card (just to be sure) and copied the fresh copies of all the files onto it. Now everything work fine so I cross my fingers that it will not happen again (it happen for no good reason at all, one minute it work the next it went poof). I think it may have something to do with your card (something along the line of cannot get read/write access to the card for some reason)

[cornelious2]

I actually remember getting that problem once restarting before the boot finished. now even if I hit haret accidentally I let it boot all the way to android then and only then do i I shut it down.