zustellr New User

Thanks but this is too risky. I already talked to the German techsupport, and they said they would not do it. I hope that the new problem with the "beep on touch" is so annoying to others that they will issue a new upgrade soon.

This problem was fixed. Unfortunately, the update also made an old problem reappear: http://community.acer.com/t5/Smartphones/Acer-Liquid-E700-problem-when-playing-music-in-car/td-p/306498/page/3 So you can either have it work in the car, but then you have to be careful with unplugging the headphones twice every time, or…

Hi, the problem was gone after the latest update, but re-appeared with 1.022. I can confirm that this is dependent on the update version, as I changed nothing except for installing the update. This is really annoying. Is there any way to de-install the update? I'd rather live with the missed headphone unplug events than…

Yes, looks like this fixes it. I now have build 1.022.00 running.

Hi, I was at a local store today, trying to reproduce the headphone problem with one of their phones. No luck. The phone I tested was black and running version 14 of the software, compared to my version 20 red phone. Though I doubt that the color makes a difference, which version are those of you with the problem running?…

IronFly wrote:it's a software issue, this can be fixed with an update, must wait next one from Acer. This is all well, but this implies that Acer is aware of the problem and willing to fix it. As I said, the German support team was entirely unaware. They told me that they never heard of the problem before (despite the fact…

...one more thing: I noticed that the problem is dependent on the time the headphones have been plugged in. If I just plug in and plug out within a few seconds, the unplug detection works. If I plug in, wait for some time (maybe play some music; who wouldn't?) and the unplug, it does not detect this. It's not application…

Hi, just wanted to mention that I have the same problem and have opened a ticket with Acer Support in Germany on September 26th (ID 912 616 4G). At that time, they did not know anything about that error, neither did the (very nice!) person I talked to minutes ago. He advised me to send the phone in for checking, though I…