05/01/2015, 02:41 AM
Some more tests:
I know this phone has a Qualcomm chipset, but I don't know if that includes the modem or if that is made by another manufacturer. Qualcomms website didn't seem to be useful - maybe I need to be a developer.
Out of interest, I tried the voice dialler - something I never really use. It failed to respond to anything.
Instead of the quick test, I ran the interactive ones - specifically the audio section.
Tests that recorded and played back using the main microphone AND the headset (palm standard) failed.
This suggests a fault upstream from both microphones...
Interestingly, the first test, which played a sound, was audible, but very faint.
Next recording from the main mic - Total Fail.
Speakerphone (playback only) - Pass
Headphone - insertion and removal detection - both passed.
Headphone playback - Pass
Headphone record / playback - Fail
I tried the quick tests again - modem error 20. The only lists of GSM error codes I can find state that 20 is 'Out of memory' , but there was no code 1000, so these codes might be specific to HP/Palm & mean something else.
After the quick tests, there was no improvement, so I rebooted. This fixed the problem and all tests were passed. Of note is that the first test - designed I think to be listened to with the phone to the ear, seemed louder and clearer, but still a bit crackly.
So... one plus is that if you need to make an important call, you can get through these tests quickly and be confident your mic is live or reboot and test if there's a problem. You can also use Skype's echo service for this. There's no embarrassment of making silent calls to people, then having to take a few mins to reboot before redialling with your explanations. Receiving calls when you can't be heard is slightly less embarrassing...
It's not clear to me that the quick tests are a fix - obviously it has to fail before I can test fixes.
My experience with my old PalmOS phone was the old tricky headphone socket issue which made calls silent on both ends (deaf & mute). The temp fix was using the headset and it was largely fixed with a thorough cleaning. The mic problem on the Pre3 could be a socket issue, but that both mics fail and are fixed with a reboot again points to a software or intermittent hardware failure.
So with a functioning mic, I ran the quick tests again and watched carefully. There are 4 tests, 1. Memory seemed to take a good two minutes. 2. was WiFi - pretty quick, 3. was the modem - this was when I got the big yellow triangle and again the error code, 20 so I don't know what test 4 is. Maybe 20 IS out of memory. Maybe something is filling the memory of the modem and blocking transmission, but not reception?
However, I ran the interactive tests again and all was still working! As is Skype echo
I doubt anyone who actually knows will be passing these forums... so I guess it's time to start fiddling to see what might prevent the issue, but it's fumbling in the dark a bit!