Workarounds/known issues 7/22: Updated for FRX07

[coolsilver]

Originally Posted by arrrghhh

I experience this as well... just random radio flakiness. Talking with some devs, CDMA is definitely in the minority... so our radios don't work quite so well. I'm hoping it'll get some more polish when other things are completed, but the remaining issues seem slow going.

I notice more and more, almost 2 out of 3 times I bring my phone out of sleep I check and my APN settings are missing. No defaults. I have to reset them for data to work again.

[arrrghhh]

Originally Posted by coolsilver

I notice more and more, almost 2 out of 3 times I bring my phone out of sleep I check and my APN settings are missing. No defaults. I have to reset them for data to work again.

Huh, I've never had that happen... I've NEVER had to muck with APN settings more than the first time... And lately I haven't had to touch them at all.

Very strange.

[pirapan]

Originally Posted by arrrghhh

Yes, I believe 210 will fix it. However, other apps may look like they're too small and you'll have black bars on the side of 'em.

Basically fitmet isn't perfect yet - it's gotten a lot better, but since there is no Android device designed with the same resolution as our screens, I doubt it'll ever be "perfect" - the devs can make it look good at a system level, but they can't really control how the apps look. I guess I should've asked, are you talking about check boxes within apps or like on a system settings page...? I've only had sizing issues with apps...

I just tried 210, and still doesn't fix. Maybe it depends on apps.
Thanks anyway

[Gilliland]

Like perhaps hundreds of others, I'm trying Android on the TP2 for the first time now that sound is working. I'm sure I'll have lots of issues to figure out, but there are a couple of things that I've run into right from the start.

1) The hardware shift keys on the keyboard don't work correctly. The "FN" key seems to act as the shift key (it gives me CAPITAL letters), while the shift key gives me an unexpected set of other characters (sometimes numeric, sometimes various special characters, definitely NOT the characters associated with the key). This makes it pretty awkward to use.

2) Everyone here says that the front LED should be Orange in normal operation and Green when the phone is asleep. Mine is always Orange. Is there a setting somewhere to let the phone go to sleep? I haven't been able to find one.

I'm entirely new to Android, so I'm just feeling my way along. If anyone has any specific tips for me on these or other topics, feel free to pass them along. I've found several FAQs concerning the TP2 and Android, but many of them seem to be out of date. So I'm not sure what's real and what's not.

In any event, though, I like what I see. This is some very impressive work.

Thanks in advance.

[manekineko]

Originally Posted by Gilliland

1) The hardware shift keys on the keyboard don't work correctly. The "FN" key seems to act as the shift key (it gives me CAPITAL letters), while the shift key gives me an unexpected set of other characters (sometimes numeric, sometimes various special characters, definitely NOT the characters associated with the key). This makes it pretty awkward to use.

You need to set your keyboard settings in startup.txt.

Take a look at the FAQ:
http://forum.ppcgeeks.com/tp2-androi...pt-2010-a.html

You can find the keyboard setting you need by searching for physkeyboard.

[Gilliland]

Originally Posted by manekineko

You need to set your keyboard settings in startup.txt.

I'm booting with the WM Startup utility that lets me select the keyboard and CDMA on the way in. It appears to be automatically selecting the right layout (Rhod400) for my Sprint TP2.

When I changed it in the startup.txt file, it broke the LaunchPro app. I'm about to reinstall and try again.

(Bear with me if I'm twisting any of the names of these tools - this is all new to me.)

[arrrghhh]

Originally Posted by Gilliland

I'm booting with the WM Startup utility that lets me select the keyboard and CDMA on the way in. It appears to be automatically selecting the right layout (Rhod400) for my Sprint TP2.

When I changed it in the startup.txt file, it broke the LaunchPro app. I'm about to reinstall and try again.

(Bear with me if I'm twisting any of the names of these tools - this is all new to me.)

Do NOT use MGJDroidUtil. It's known that it's faulty, and honestly should be removed from builds until it's fixed... C'est la vie I guess. Just don't use it

[drynaps]

Originally Posted by [ACL]

I have a few comments.

• USB is always active and cannot connect to computer to send data. <--we started looking into this issue. This is more important for the nand version since without it, debugging is very difficult.

OK, maybe I'm not understanding this, because I can get my USB debugging working, to the point that I can use DroidExplorer and ADB from my computer when connected through USB.

All I have to do is have the latest android SDK installed as well as DroidExplorer (the latest SDK has the latest drivers)

I plug in my phone while in Windows Mobile and let the OS detect the phone. When the phone is detected then I start Haret.exe and when I get to Android I have my debugging enabled. Windows recognizes the ADB device and it shows it in "My Computer" right along the "Mobile Device" under "Other" with an id of "0000000000000000" Then all I have to do is double click the device and DroidExplorer pops up and connects to my device and away I go.

I hope this helps.

I have a TP2 RHOD400 on US Cellular.

[manekineko]

Originally Posted by drynaps

OK, maybe I'm not understanding this, because I can get my USB debugging working, to the point that I can use DroidExplorer and ADB from my computer when connected through USB.

All I have to do is have the latest android SDK installed as well as DroidExplorer (the latest SDK has the latest drivers)

I plug in my phone while in Windows Mobile and let the OS detect the phone. When the phone is detected then I start Haret.exe and when I get to Android I have my debugging enabled. Windows recognizes the ADB device and it shows it in "My Computer" right along the "Mobile Device" under "Other" with an id of "0000000000000000" Then all I have to do is double click the device and DroidExplorer pops up and connects to my device and away I go.

I hope this helps.

I have a TP2 RHOD400 on US Cellular.

I seem to remember seeing the devs talking about getting USB working in some form. Anyone know if USB debugging has been fixed lately?

At any rate, I will update the list.

[[ACL]]

Originally Posted by manekineko

I seem to remember seeing the devs talking about getting USB working in some form. Anyone know if USB debugging has been fixed lately?

At any rate, I will update the list.

USB is working on the nand version now. We back-ported .32 usb drivers to get everything to work.

My understand is that you should be able to connect via ADB already on the haret version. Is this not the case? I'm sure its possible or else there would be way complaints.