Update to my 'good news.'
After getting the tablet back, the same problem happened in about 2 days.
It's back in for repair.
Typical Acer..
It's not the charging/USB port is it? i just got mine back for that problem.
with things like that WHERE I WORK, you have to fix and in some cases modify a device to over come the what ever design flaw the device has so it doesn't happen again.
EDIT: also why no custom roms for the A110? Can you overclock with the stock rom?
No over clock available because there isn't a kernel that supports OC for this device.
How come no one has made a custom rom yet? I was alpyign GTA 3 the other day and it was little bit laggy at times. i would be nice to ahve a newer/faster os with OC capabilities.
There really isn't enough support for this device. No developers want to develop for it. I tried porting a ROM from the nexus 7. It worked but had many bugs.
I gave up on the tablet and gave it to my dad.
I will continue to support people and their questions here though.
Also, if it lags, change the power saving mode to high performance.
And, if you're rooted, use setcpu to set CPU to 1.3(max). I noticed that by default, the tablet plays games at 1.0-1.2.
Sent from my Nexus 5 using XDA Premium 4 mobile app
that's not overclocking but, forcing the cpu to it's max speed?
*I, nor any of the people involved in the rooting process of this
tablet are responsible for any damage you may cause to your device.
*If you brick your device, we are not to blame.
*Your warranty may be void after doing this.
*By using this guide, you acknowledge that you are fully responsible
for any damage you cause to your device and the device accessories.
Settings > Developer Option
adt-bundle-windows-x86_x64\sdk\platform-tools
adb devices
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
fastboot devices
fastboot boot a110-412-CWM-recovery.img
Exactly the same results as the previous guys, every step appears successful, including sideload, but no SU after reboot. My Firmware has WW in name.
Only messages seen during sideload which imply errors are E: can't mount /cache/recovery/log etc etc.
Anyone any idea what may be wrong?