Valid HTML 4.01 Transitional

Samsung Galaxy S III
Bug Reports

Jim Carter, 2012-10-23

AOSP Bug Report Page. To file a bug you need to authenticate with your Google ID; searching can be done anonymously.

CyanogenMod Bug Report Page. This is the wiki page for how to file a bug report.

Active Issues

No TLS after X.509 client cert is demanded

Issue 39526 filed on 2012-11-11 with AOSP.

Steps to reproduce the problem:

A tree of web pages is configured to require authentication by a X.509 client certificate. In Apache, SSLVerifyClient require, and 'SSLRequire %{SSL_CLIENT_I_DN_CN} eq CFT Root Certificate' in a Location block.

A non-expired certificate issued by the required CA is installed on the device.

I navigate to the covered web page.

What happened:

The Android browser proposes to send the correct certificate and I confirm this. But the browser pops a modal dialog saying Couldn't establish a secure connection and the Webpage not available local error document is shown.

The same thing was tried with a variety of other browsers including Dolphin, Opera Mobile, Maxthon, UC Browser, Skyfire, and Google's Chrome. All failed similarly, although the native Android browser was the only one that asked for confirmation to send over the certificate. It is possible that some of them may be incapable of dealing with client certs at all, which could not be distinguished from buggy handling of the browser's part of setting up the connection.

What you think the correct behavior should be:

On a variety of desktop machines, the certificate is sent over, TLS is set up, and the page is delivered. The same pages are available at a different URL for which a client cert is not demanded (it falls back to password auth), and the Android browser is able to do TLS and show the page. On a phone running Android-4.0.x Ice Cream Sandwich the certificate could be presented and TLS could be established and the content displayed. Also Android-2.3 Gingerbread.


Additional attempts to fix:

Fixed Issues

Phone Tester by Miguel Torres

All pages behave normally except the sensors page. It displays results very fast (same as on previous versions), but gets slower and slower, and eventually freezes solid and is given a ANR notice.

DeaDBeeF by Aleksey Yakovenko

After non-obvious contingencies, DeaDBeeF would go catatonic, blank screen no matter how it was started, until a ANR notice appeared.

Dialpad On Call Not Heard by Partner

Steps to reproduce the problem:

Dial a voice number that has a DTMF menu, such as Verizon's voicemail (*86) or customer service (*611). You can dial with any dialer app; the result is the same and you end up using the stock dialpad while on call (not the app's dialpad). Press dialpad keys. You can also connect a Bluetooth keyboard and press number keys; the result is the same.

What happened:

The partner does not respond to the key presses, even though local DTMF tones are heard and written numbers are echoed on the dialpad (even with the Bluetooth keyboard). The partner responds Please enter your password, Are you still there, Idiot, press a number key, Sorry you're unable to make your phone work, goodbye.

Change in behavior: Sometimes when you press 1 the dialpad goes black for 1-2 seconds, then comes back having done no visible or audible action.

What you think the correct behavior should be:

The partner should receive and recognize the DTMF tones, and cough up the voicemail or give customer service.


Workaround for Voicemail:

This is all for Verizon. Details will be different for other carriers but the basic strategy will probably work.

To listen to your voicemail, start the Phone app, Menu - Settings - Voicemail - Setup - Voicemail Number. Edit the number. In the GUI press the #* key and you will get a sub-menu of symbols, one of which is pause, represented in the dial string by a comma. Set your number to *86,,12345,,,,1

*86 is Verizon's voicemail number. It needs two pauses to get ready for the password (fake password shown). It needs 4 pauses to be ready for the first command (two are not enough). The 1 requests to play messages. After the first message you can't do anything more, so hang up. The next time you call, you will get the next message.

To delete the messages you need to call your mobile number from a landline. On the handy don't answer, or refuse the call. Back on the landline, press # before the voicemail greeting finishes. Give your password when asked, followed by DTMF commands.

The Fix

Do what it says on the CyanogenMod issue tracker instructions page. Most bugs are resolved during this process.