Workarounds/known issues 7/22: Updated for FRX07
 

In order to cut down on the amount of repeated posts and questions that clog up the forum, the following is a list of the known issues, along with workarounds if present.

Except where indicated otherwise, these issues should affect all builds as these problems are caused by drivers that just haven't been written yet in the kernel (the kernel and drivers are used universally by all builds).

• Notification LED doesn't notify, but just outputs whether your phone is in sleep (green) or active (orange). If your phone's LED is not turning green while the screen is off, you will get very bad battery life.
• Light sensor and auto-backlight are completely erratic and essentially non-functional.
• Proximity sensor is completely not working.
• Wifi will not connect to WEP, only WPA or unencrypted. Stock Android will not connect to any ad-hoc access points, but a workaround is available. A program called WiFi ACE will let you connect to WEP networks. Furthermore, once turned on, Wifi will never actually turn off again until reboot, so will provide a constant small power drain. It will show as turned off, but power off code is not actually present in kernel.
• Bluetooth is working except for audio, but there are experimental patches that enable audio.
• 3.5mm headset jack on CDMA Touch Pro 2's works for listening but has no support for microphone or call/end button.
• extUSB headset jack works but will often slow the phone down to a crawl, requiring a reboot, on disconnect.
• Location mostly working in FRX, but there are a number of issues. GPS works but phone will not sleep while satellite location is enabled, draining the battery. Satellite information should first be downloaded in Windows Mobile via QuickGPS or else a GPS fix will take forever. Google Navigation has a high chance of rebooting the whole phone after using it for a while. Everything location is not working in GRX.
• Battery level reading is pretty inaccurate, best around 50% and least accurate at the extremes. You can make your battery meter accurate by using jonpry's Super Cool Battery Software.
• Stylus removal/insertion sensor is completely not working.
• TV Out is completely not working.
• Zoom Bar is completely not working.
• Tethering on USB built into Android works in FRX but not GRX, but tethering on wifi built into Android works on both, but is unstable and will crash the system on turning it off. There is a replacement app for wifi tethering called XDAndroid-wifi-tether that works better.
• Speakerphone mute button on back doesn't do anything. You can replace your rootfs with an alternative that enables them. F22's rootfs
• Special keyboard keys like mail don't do anything in the default setup. You can replace your rootfs with an alternative that enables them. F22's rootfs
• Internal memory cannot be usefully accessed except on NAND builds.
• USB Mass Storage only works if you partition your SD card (anyone want to write a guide to this?).
• Shutdown will occasionally mess up the contents of the card when using non-NAND builds. Generally not a problem, but over time file system may build up with errors and need a reformat. Also, files with names like FSCK001 will appear in your SD card's root and need to be deleted.
• Video playback works for low resolutions, but high resolutions such as Youtube HQ have only audio. This can be alleviated with highlandsun's experimental codecs.

You might look at that list and think whoa, but all core features are working, and I've been running it on my Touch Pro 2 as my main OS quite happily.

If I'm missing anything, just let me know and I'll add it to the list.

Re: Unofficial known issues list 8/28
 

You might add that you can't charge at all while in android

Also my voice search worked at one time but i just tried it and it doesn't, so that might be hit or miss.

Re: Unofficial known issues list 8/28
 

Charging is working fine for me on the latest Froyo build. Are you on the new builds?

The issue with voice search seems to be that it's not able to initialize the microphone. If you use it when the microphone is already initialized, like right after a call, it'll work.

Re: Unofficial known issues list 8/28
 

I heard that the Keyboard Backlight actually does work. You just have to have it on when you boot from Windows Mobile to Android, but then the backlight stays on the whole time. Charging in working well in Android, but I believe it will only charge to 85% (in windows mobile percentage).

Re: Unofficial known issues list 8/28
 

I've found that on my phone the LED notification light is on orange most of the time if not always. However, when I lose signal it turns green. Sounds really weird, but when i put it in airplane mode it stayed green. I flipped it back on and back to orange it went.

I have came up with a logical explanation for everything after conducting a lot of research and have come to a conclusion. This android is definitely haunted by the elusive wookisasquatchosaurus. I have tried to catch it in the act and photograph it, but it always slips out of my grasps.

Re: Unofficial known issues list 8/28
 

Thanks, noted!

Re: Unofficial known issues list 8/28
 

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.
• SD Card cannot be dismounted, and on an occasional basis will mess up the contents of the card. <-- course you cant dismount.. android running off it.
• Software shutdown does not work. <--- You need to look into this.. It is working for us. Now it may be because i'm running code for the Nand, but has no one been able to successfully shut down ?
• Microphone is not properly activated for voice search and some other applications. Does work fine for phone calls and some apps. <-- Jonpry is already attacking this area.
• 3D acceleration is completely not working. <-- yes, not working .. :-(
• Android UI Process Crashes are frequent on the latest version without the crackling speakers, but this isn't actually that big a deal, as Android just reopens the UI right away. <-- weird.. need logcat dumps to troubleshoot this. or dmesg dumps would help too.
• MMS not working. <-- too low priority to attack right now.
  

Re: Unofficial known issues list 8/28
 

Software shutdown is working for me after an update to the latest module and zImage to silence the speaker.

Re: Unofficial known issues list 8/28
 

Shutdown works for me
Charging, idk lol i left on the charger at night, booted into android and it was dead at 4 AM :/ while the charger was on
Facebook accounts is a bug on mult devices running FroYo
Face keys also don't work, same deal with the keyboard backlight lol (same "fix" also)
Since hardware3D and camera are on there, why not add BT? :P
Does screen refer to Auto Backlight? Or Brightness in general (Which also works funny)
And no crashing for me :)

Re: Unofficial known issues list 8/28
 

With me it is that it keep restart just after it completely finish starting up. For the life of me nothing seem to work even reinstall and updating.

Re: Unofficial known issues list 8/28
 

Updated again with everyone's input. Thanks all!

Re: Unofficial known issues list 8/28
 

One more thing to add Can not access the SD card at lest i can not well a program's can not see the sd card

Re: Unofficial known issues list 8/28
 

I believe the proximity sensor should be on the list (turn off screen when you hold it to your face in calls). I have my touch activated right now and am only playing with the TP2 over WiFi, so I can't confirm. But I believe that was the case when I tried it a week or so ago.

Light sensor doesn't work either, right?

Re: Unofficial known issues list 8/28
 

Really? I can see the SD card okay when using Astro. In fact, I think that's all I can access, and I can't access internal memory.

Re: Unofficial known issues list 8/29
 

The Shift and FN notification LEDs on the keyboard do not work.

Re: Unofficial known issues list 8/29
 

I installed the 8/26 release of 2.2 and I have this constant low level sound "static" from the speakers when not in use. Is this a known problem and does anyone have a solution? ](*,)

Re: Unofficial known issues list 8/29
 

I have installed the 2.2 Blazn release on my sprint tp2. First run is awesome, but as soon as I boot back to winmo (energy 21914 Aug 25) whenever I launch haret (rhod400 option, force cdma checked) I get "Launch a script file. Defailt path is the same where the executable lives."


Have installed twice, then reformatted, installed again.


EDIT: Sorry, I didn't read into it enough. Seems I've found the best answer here:

http://forum.ppcgeeks.com/showthread.php?t=132159

Re: Unofficial known issues list 8/29
 

I assume you installed the .cab version, The crackleing is a known issue that has already been addressed, you just need to update to the latest kernal, the easiest way to do this is to go in to the app in windows mobile, click on menu and click update zImage .

If I helped you please click thanks.

Re: Unofficial known issues list 8/29
 

i can see the sd card on a file manger but i can not see it on android(as a os) or any programs that save stuff to the sd card

Re: Unofficial known issues list 8/29
 

Can you give an example? I have lots of apps that are saving data to the SD card, and they all seem to be working fine.

Re: Unofficial known issues list 8/29
 

Id also like to add that sometimes text messages dont come through, dunno if im the only one having this issue

Re: Unofficial known issues list 8/29
 

The Scripture app from the lds church

Re: Unofficial known issues list 8/29
 

Even though this is not directly related to the android OS and more with HaRet...when WinMo is overclocked, HaRet will not boot. Rather, a black box will cover the screen partially. What's interesting is if you keep trying to start HaRet after every reboot, the black box moves more down and down. Bottom note (many of you know already): clock back to stock speed or use safe mode before you boot into Android

Re: Unofficial known issues list 8/29
 

Sounds like even the unofficial issues cannot be agreed upon...I was thinking about making the leap but I will wait until it gets a little more stable before I give it a try, or use my spare device for a test run

Re: Unofficial known issues list 8/29
 

Where can someone go to check the status of things not working mainly the hw3d?

Re: Unofficial known issues list 8/29
 

chat logs :-)

Re: Unofficial known issues list 8/29
 

Maybe I'm just having it on a worse scale, but I actually consider this one a major deal breaker as pretty much every app I've tried (at least ones that weren't natively built into the build) crash immediately. Sure Android itself doesn't crash, but it pretty much makes the platform unusable when you can't launch most of your apps.

I haven't had a chance to try the build that came out yesterday yet, but I'll have to give it more than 24/48hrs once I do so as the first sound-fix build worked just fine for the first day or so before the apps suddenly started crashing. From what someone mentioned in the thread specific to this issue yesterday this problem seems to be specific to Sprint devices.

Re: Unofficial known issues list 8/29
 

Really? Are you overclocked?

I'm on a Sprint TP2, and my problem is exactly the opposite. All apps are rock solid, have literally not had a single one crash. However, Android's home screens crash for me all the time. It's gotten worse for me on the latest build, probably 75% of the time I want to move a widget, it won't do it properly, and then will crash in about a minute.

Re: Unofficial known issues list 8/31
 

i have noticed that the speed of 3G connection seems to be slower in android as compared to WM

i am not having crash issues (apart from a couple launcher crashes) and i have had my phone on android full time since yesterday morning.

The only major issue i have right now is battery life.

Re: Unofficial known issues list 8/31
 

:grin:I tried this and it actually made the mic work for everything,... i'm talking about voice search google... dial... and the micdroid program and talking tom who could never hear me because mic didn't work until... the stepis like wayyyyyyy before... MAKE A PHONE CALL TO VOICE MAIL PUT ON SPEAKER AND BOOT INTO ANDROID GAURANTEED TO WORK.:wink:

Re: Unofficial known issues list 8/31
 

This worked for me as well on the latest build

Re: Unofficial known issues list 8/31
 

Worked for me as well, I noticed I initially had the static back when I did it, but once I adjusted the volume the static was gone and the mic still worked.

Mic continued to work after making calls, etc.

Tested with TiKL and Google Search voice input.

Re: Unofficial known issues list 8/31
 

I am having trouble downloading applications from the android market place. How do you do this?

Re: Unofficial known issues list 8/31
 

The nice thing is you dont have to do nothing static will go by itself,

Re: Unofficial known issues list 8/31
 

can someone give me the exact text to add to the startup text and exactly where to put it in the startup text? I need to fix the call volume thing because right now that is the ONLY thing keeping me from using Android full time. Please and thanks.

Re: Unofficial known issues list 8/31
 

you could try this http://sites.google.com/site/android...llvolumeupdate .

Re: Unofficial known issues list 8/28
 

Same here, phone died twice while still on the charger (and smoking hot). I have a feeling it's related to the faulty battery meter. Phone thinks its "full" so it stops charging? Mine shows full like 2 minutes after plugged in.

Re: Unofficial known issues list 8/31
 

you shoudn't leave it plugged in over nite, i think your gonna fry the battery. charging by computer i noticed doesn't get the phone hot, and the phone thinks its full fast. at nite you should charge winmo and morning go android, here's a tip charge with phone off. and check this out http://www.ehow.com/how_5736621_exte...tery-life.html

Re: Unofficial known issues list 8/31
 

Maybe this has been around for awhile and I just haven't noticed because I haven't stayed in Android very long until we got sound. But I'll notice in the mornings that the time Android's reporting is a good 10 minutes or so behind. It won't be that noticeably off in the evening, but it seems to creep off during the overnight hours. Boot back into WM and the correct time shows up.

I'm running the OC'd Blazin version FWIW

Re: Unofficial known issues list 8/31
 

I've only been playing around for a total of a few hours so far but things I've noticed that haven't already been mentioned:
1) Power button and end button are working bass ackwards
2) Sprint 3G speeds aren't as good in Droid as WinMo
3) My WiFi is way stronger in Droid than WinMo
4) I've only done this a couple of times but when I have roaming set to Sprint Only in Droid, then reboot to WinMo if I have WinMo set to Roam only when I reboot to Droid it boots in Airplane mode and which I can't turn off without a reboot
5) If you set the on-screen keyboard to vibrate on key presses it severely slows the device down while typing to the point it's unusable

Hopefully I can give some more feedback the more I play with it. I'm running 2.2 Blazn cab