Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’d like to buy an Acer Liquid E as an Android test phone (normal size, high density screen, android v2.1 up to 2.2).
Before actually doing that, it’ll be great to know if anyone had any bad experience with it. My dev environment is Eclipse + ADT on Windows 7 64 bits. I’m thinking about things like USB drivers, logcat displayed correctly, breakpoints hit, and so on.
I read about this issue, but it’s from 2009 and in the end it was solved anyway.
Thanks.
This is not exactly the answer to this question, but I’ll post it in case it might be useful for some other developer in need.
In the end I did not go into buying this exact phone model. Instead I bought an Acer Liquid MT S120 (or Metal) phone. In order to be able to debug apps on it, I just had to look for official Acer Windows drivers.
Those where relatively easy to find (here version 1.0): the only quirk was that I had to select the former Android version (2.2 instead of actual 2.3) in order to see the drivers under the Application tab, otherwise they would not show.
Apart from that, debugging experience was very straightforward: plug USB in, and Eclipse/adb where able to see the device. APK upload times are really fast (I guess this holds for any USB-connected device too). The same holds for integration/functional tests.