| Selection | Checkout | Install | Apps | Hacking | Top |
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.
Issue 39526 filed on 2012-11-11 with AOSP.
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.
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.
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
.
Following the successful fix for the dialpad bug, I tried these steps (unsuccessfully):
all): force stop, clear cache, clear data.
Couldn't establish a secure connection.
disabled by administrator, encryption policy, or credential storage.
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.
Interact with the developer (migueltorcha@gmail.com) and get this fixed. Sent mail on 2012-11-04.
Temporarily I'm using the old Tricorder app, which still works.
Developer identified the bug and sent back v1.71, which is fixed. This issue is now finished.
The problem was that sensor data was coming back very fast, and the program has no delay in its loop, so screen updates were piling up on the way out. Adding a delay helped. I suggested 1 second, but Miguel made it much shorter (but nonzero).
After non-obvious contingencies, DeaDBeeF would go catatonic, blank screen no matter how it was started, until a ANR notice appeared.
I sent mail to the developer, wakeroid@gmail.com (Aleksey Yakovenko) on 2012-11-04. Reply: look in /sdcard/.deadbeef/config. If the player is killed while paused, it may have saved corrupt resume parameters here. Try editing them out.
I had other mysterious messes including an instance in /external_sd/.deadbeef; I had to delete that one entirely before it would work again. But once again it's working.
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.
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.
The partner should receive and recognize the DTMF tones, and cough up the voicemail or give customer service.
PhoneApp Version: 4.1.2-eng.20121023.225511
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.
Do what it says on the
CyanogenMod issue tracker instructions page. Most
bugs are resolved
during this process.
Reboot. Corruption from one app can cause bugs in an unrelated one. On phones with limited memory and a lot of running apps, an app may handle a memory allocation failure ungracefully, which is a bug, but the issue will be revealed if the app starts working immediately after a reboot. (In my case, multiple reboots didn't help.)
Upgrade to the lastest CyanogenMod version. As of 2012-11-13 we're off nightlies and the current version has been classified as stable. (The installation includes reboots, so you don't have to do that separately.)
I think it unlikely that I actually got a new bugfix; CyanogenMod's issue tracker shows no related bug reports. Even so, updating to the latest declared stable version is a good idea.
In general, before declaring that something is a bug, reinstall freshly and wipe the data partition, since leftover back-version data and corrupted whatevers are often the cause of bugs.
I cheated: to save myself the work of selectively restoring app data, I just used Settings - Apps - All on the Phone app. First I killed the process, to avoid zombie data sitting in memory, and then I cleared the application data.
That fixed it. Formerly, when you turn on the dialpad while on call, it would have the voicemail icon on the 1 key, and I'll bet when that was pressed (short press, not long), it would flip into speed dial mode and either send the number or do something else useless. Now the voicemail icon is gone, and all keys including 1 yield DTMF that the partner can hear and respond to. I am now able to do both customer service and voicemail.
| Selection | Checkout | Install | Apps | Hacking | Top |