Jump to content

piernov

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

3 Neutral

About piernov

  • Rank
    Newbie
  • Birthday 09/05/1996

Contact Methods

Profile Information

  • Your Current Device(s)
    Acer Liquid E
  1. It's in french but it might help you : http://forum.frandroid.com/topic/177035-tuto-remplacer-la-vitre-tactile-de-son-acer-liquid-e2/
  2. From http://www.modaco.com/topic/363086-cm10-rom-super-hornet-acer-liquid-os-412-jelly-bean/ : "Problems: wifi, usb tether: try to use third party app" If it doesn't work with third party app, post a logcat when you're trying to enable it, I might take a look at it.
  3. Hey, some (not so interesting news) : still trying to get 2.6.38 kernel to boot, about the first problem described in the first post, it seems solved by using yaffs2 filesystem driver from 2.6.35, though sysinit can't be started. For now I'm working on recovery (TWRP), and the main problem is that nothing appear on the display. Here are the logs : http://pastebin.com/CnHEFHDH → don't show anything wrong with display…
  4. It's actually what I'm using, branch android-msm-2.6.35-acer_a1 comes from this repo. Cherry-picked essential/useful commits like c975299c , a405e429 , 7c30b7f5 , 6ee9c17e , 4539a4a8 , bf6b4aa8 , 1b575dcd , f810e59b and adapted a few things for 2.6.38.
  5. Hi there, hacking around acer liquid e these days. Trying to get newer kernel to boot. 2.6.38.6 : Kernel itself boots, but when the /system partition gets mounted, all of its content is erased Start backport of 3.0's kgsl driver (in order to compile correctly KitKat) Boot logo isn't shown so there might be a problem with the display. Would be easier to debug if android booted. Log : http://pastebin.com/LYyRtYKY Using msm-2.6.38 branch from caf, ported some commits of android-msm-2.6.35-acer_a1 from errmsg 3.0.21 : Kernel starts but crash early because of GPIO initialization failure : gpio_request fails with error -22 (Invalid argument) Log : http://pastebin.com/6HLfVyxY Using msm-3.0 branch from caf, ported some commits of android-msm-2.6.35-acer_a1 from errmsg It would be wonderful if someone is able to help me with these issues, or even work together to get a newer working kernel. If someone is interested and wants the source code, it's not yet on github because it's really dirty and WIP, but I can zip it and upload it. For now we are far from getting KitKat on this device, but at least having a clean and up-to-date kernel would help a lot I think : the goal is to get 3.4 if it's possible, because KK is based on it. (another problem is that the size of /system is now 336Mo, 64Mo left for /data, xdata would be mandatory) PS: The logs are from UART debugging : opened up my acer liquid, opened the miniUSB to see the other face, soldered the 2nd pin from the left to TX, the 3rd to RX. http://servers.piernov.org/~piernov/IMG_20140609_221433.jpg http://servers.piernov.org/~piernov/IMG_20140609_221446.jpg Another thanks to errmsg for the UART tip : http://rtg.in.ua/blog/serial-debug-on-acer-a1/
  6. EDIT: Sorry, it seems I was wrong.
  7. But we only have a 2.6.29.6 kernel working. We also have a 2.6.32, but it's far from working with Android 4.x. And the 2.6.35 doesn't even fully work with a stock ROM. (didn't look at it, but some problems might come from the fact that using 2.6.35 kernel should require Android 2.3) Currently with the 2.6.29.6, we have KGSL 3.8. I think we would need to update it to 3.14 along with the binary blobs to be able to boot a newer Android. I already took a look at that, but I'm not a kernel dev at all, nor even a good C programmer… So when I tried to backport a newer version of the graphics driver, it was just failing. (by the way, the newer graphic driver also uses newer functionnality from 2.6.35 kernel and maybe above for exemple so they need to be rewritten to work on 2.6.29.6) Graphic driver may not be the only thing needing update. To conclude, yes it's portable of course, but it needs good knowledges of kernel development, lot of time and a huge amount of work. And better than trying to backport all the time stuff for 2.6.29.6 kernel, we should rather try to get a fully working 2.6.35, then 2.6.38, then 3.0 kernel. Then starting from here we would normally have all the needed stuff to run Android 4.4 on our device. (but, after that we should also try to update to 3.4 since 3.0 is now deprecated, if we want to be able to update Android in the future)
  8. These phone surely don't have the same chipset (QSD8250) as the acer liquid. AFAIK it's the only device with that chipset which has gone so far (getting CM10). But now, the main problem is the kernel. For exemple, to get CM10.1 (Android 4.2) on the acer liquid, we have to update the graphics driver, which need an huge amount of changes to backport it to the 2.6.29.6 kernel. (which the liquid use). In fact, in order to get Android 4.2, and more especially 4.3 and now 4.4, we need to get at least a 3.0 (3.0.100 for exemple) kernel to work on it. Currently, the most up to date kernel we have is the 2.6.35, and doesn't work perfectly and only with the original Android 2.2 ROM. So it needs really a lot of work but the acer liquid community isn't active as the CM9 ages (which also needed a lot of work).
  9. If it just doesn't charge anymore (and the battery drain was faster than expected before), it's probably a dead battery. Had the same problem some months ago, so I bought a 1500mAh battery on eBay and now it works perfectly. (and my power button was broken so the phone was just stuck in a sort of "bootloop" displaying the empty battery icon, because the battery was empty and it kept trying to boot due to the power button being pressed) And if the battery is empty or absent, the phone will not boot. However, you may try to boot in fastboot mode, it might work, (then maybe booting on OS will work too) but I don't think so.
  10. You have to partition your SD card in the recovery (remember to save all data before doing this) and select the desired size for the FAT32 and EXT4 partition. You can also add a swap parition if you have only 256MB of RAM. Then, boot Android, open Terminal Emulator, type "su -", accept, type "a2sd formatext". It'll format your SD card's second partition to EXT4. Reboot. Returns to Terminal Emulator, type "su -". Now you have to choose between having only the apps on SD-EXT, or the whole /data partition (use that only if you have at least a class-6 SD (works with a class-4 here though) card with more than 512MB for the EXT partition, otherwise it's useless and will slow down your device). The first is set by "a2sd install", the second by "a2sd xdata". Reboot, and try to install some apps, if you don't reach the internal data storage limit, then it's working. There's already an a2sd script in CyanogenMod, the only point of this script is to allow the user to not move /data/data, so not very useful as we can use the integrated script which works well.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.