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

[socialsavant]

I just successfully installed the latest AIO (may 11th). I did as mj said: installed from scratch the old march AIO, ran it, shutdown, OVERWROTE with the new AIO (did NOT touch data.img), ran it, waited a good long time during the Nexus One boot screen, and success.

I had trouble with the endless looping boot screen before when trying to do a fresh install of the new AIO as well. This workaround is great. I do still see the missing depmod line in the boot up as well as the "bad mode" line and noticed that when booting the old march AIO there is a SHORT pause after the screen calibration where it reads something about not finding setupmodem.sh or something like that, but when the new AIO runs there is a LONG pause in the same place. It would seem though, that if you have patience and wait, the boot old and overwrite method works.

Thank you all, I have been dreaming of putting Android on my TP for a long time and am soooo happy with the results so far. I WILL BE DONATING as soon as I get paid.

Great Work Everyone!

--socialSavant

[makkonen]

Originally Posted by mj41374

Something between 2010-03-31 and 2010-05-07 AIO broke.

Clearly. Thanks for all the debug work, mj41374, arrrghhh, and hamagc (and anyone else I've forgotten). There's a pretty big change between 3-31 and 5-7. The build process for the Android system (system.sqsh) has completely changed from a sort of patchwork to a build off the AOSP sources. I saw one person's logcat from a phone that was looping, and it seemed to have to do with the ConnectivityService and getPersistedNetworkPreference. What this means, I have no clue (except that it sounds like it's got to do with having uninitialized network preferences on first boot... maybe).

I just noticed in the RHOD package by ReeferMattness that there's a file that has to be in the /sdcard/cache folder. I'm not sure what, if anything, that has any bearing on, but is another thing to look into.

What's weird is that for some people, the 5-07 and 5-11 seem to work out of the box. (Is this true?) There's at least one, and possibly many, pieces of the puzzle yet to be put in place. Wish I could be more help in debugging.

[arrrghhh]

Originally Posted by makkonen

What's weird is that for some people, the 5-07 and 5-11 seem to work out of the box. (Is this true?) There's at least one, and possibly many, pieces of the puzzle yet to be put in place. Wish I could be more help in debugging.

I'm not sure I've tried this. I will and report back...

[makkonen]

Originally Posted by tx_jaycee

How do you shutdown when in Android?

Originally Posted by hamagc

soft-reset, let windows boot, then shutdown. andorid shutdown is a known problem that is being looked at.


do people actually shut their phones down?

Or just pull the battery. That's my method. That's if you mean actually shutdown. If you just mean how do you get out of Android, hold the End key until the menu comes up, and select shutdown. (Which won't actually shutdown, it'll reboot into WinMo.)

Originally Posted by ChaosTheory

Quick question, I just updated both my zImage, module, and rootfs, and now my headphones/headphone jack doesn't work. Any idea which one is the most likely culprit, so I don't have to roll back all of them if I don't have to?

I didn't realize the headphone jack was ever working... it was working? Anyone?

[hamagc]

makk to my knowledge it doesn't work out of the box. there was a problem with the 5/7 and the zimage (unless you fixed that and reposted it).

as for the 5.11 the files look correct. haven't tried that one.

[arrrghhh]

Originally Posted by arrrghhh

I'm not sure I've tried this. I will and report back...

Works, just downloaded the AIO from the first post.

[tx_jaycee]

Makk and hamgc thanks for the help. Sorry for the n00b question on shutdown wasn't sure if there was a formal way of shutting down within Android. I got the AIO 5/11 to work using hamgc's workaround and 2.1 is working great.

[Noah Vail]

Originally Posted by makkonen

If you just mean how do you get out of Android, hold the End key until the menu comes up, and select shutdown. (Which won't actually shutdown, it'll reboot into WinMo.)

This is where I've been stuck for a while. Holding down the End Key doesn't bring up a shutdown menu.

Pressing the End Key seems to be a Right-Arrow command. Holding it down sometimes repeats the Right-Arrow Command - sometimes does nothing.

I need to exit back to WinMo because Lumos was monitoring my launched apps. I'm trying to get Lumos to exempt itself from grabbing control of the backlight; when Android is launched.

Thanks for an amazing product.

NV

[Noah Vail]

Originally Posted by hamagc

soft-reset, let windows boot, then shutdown. andorid shutdown is a known problem that is being looked at.

Ah. Looks like I just need to be patient, then.

I'll find another way to get Lumos to let go of backlight control.

Thanks.
NV

[makkonen]

I never had a problem with Lumos and the backlight. It was the internal WinMo backlight control that would cause problems.