Jump to content

zbrin

Members
  • Content count

    50
  • Joined

  • Last visited

Community Reputation

0 Neutral

About zbrin

  • Rank
    Regular

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Previous Fields

  • Your Current Device(s)
    Liquid A1 256mb - CM 1.2
  1. Thank you very much :) Edit: With this kernel i'm getting this logcat and stays there forever (without fully booting): W/SensorClient( 591): SensorService not published, waiting... I/ServiceManager( 591): Waiting for sevice yamaha.hardware.sensors... I/ServiceManager( 591): Waiting for sevice yamaha.hardware.sensors... I/ServiceManager( 591): Waiting for sevice yamaha.hardware.sensors... I/ServiceManager( 591): Waiting for sevice yamaha.hardware.sensors... I/ServiceManager( 591): Waiting for sevice yamaha.hardware.sensors... W/SensorClient( 591): SensorService not published, waiting... I/ServiceManager( 591): Waiting for sevice yamaha.hardware.sensors...
  2. When I try to use that command it says that the system cannot find the path specified. when I search for it in /dev/ there's no file/directory with that name. Thanks for your help ;)
  3. Hey gnufabio, is it possible to disable prox sensor without flashing a new kernel? If not, can you build a kernel without prox sensor? Thanks
  4. I installed through adb, as follows: adb remount adb pull /system/app/Vending.apk "PATH TO BACKUP" (e.g. C:\Vending.apk : adb pull /system/app/Vending.apk "C:\Vending.apk") adb push "PATH TO NEW MARKET" /system/app/Vending.apk And it's done. you can also put this in a zip to flash through recovery, maybe gnufabio can make one for us ;)
  5. I installed this LINK and its working fine ;) (I had to overwrite the previous one)
  6. I'm not sure if you still need this, but here it goes: 0,-80,-112,400,255,255,255,2147483647,2147483647,2147483647,0, Gnufabio CM6.1.1 v2.2
  7. Unfortunately the drain is similar, the powertop for 0% brightness (the minimum) with fixed value, aka no autobrightness, and with last update (2.2) is: Screen on: Top causes for wakeups: 48.0% ( 82.5) <interrupt> : msm_i2c 20.6% ( 35.4) <interrupt> : dg_timer 5.2% ( 9.0) <kernel core> : hrtimer_start (tick_sched_timer) The touchscreen driver is the same as in the other acer ROM's? (sorry if its a dumb question xD) Besides this the ROM is perfect :)
  8. Thanks gnufabio for the quick reply, I will check for this display battery drainin the new update and will report back tomorow :)
  9. Hi gnufabio! Great work with this ROM, I was waiting for a CM 6 with full hw working! Thanks a lot. I'm having a strange behavior though, the display is sucking all my batt, with screen off I'm having like 1%/hour which is great, but with my screen on(lowest brightness) is like 15-20% hour. Running powertop I'm getting this: Screen off: Top causes for wakeups: 28.2% ( 16.1) <interrupt> : dg_timer 11.2% ( 6.4) <kernel core> : hrtimer_start (tick_sched_timer) 11.1% ( 6.3) <interrupt> : msm_otg, msm_hsusb Screen on: Top causes for wakeups: 50.1% ( 81.7) <interrupt> : msm_i2c 18.9% ( 30.8) <interrupt> : dg_timer 4.5% ( 7.3) <kernel core> : hrtimer_start (tick_sched_timer) At the moment on "battery use" with 3h11m unplugged , Display 54% (Time on -> 15m 47s -> Lowest brightness - manual pick) Cell standby 17% Phone idle 15% .. With an acer based ROM with your kernel everything is normal and I'm having a normal Display battery drain. I hope you can solve this, if you need more details just ask. Thanks
  10. Not to gripe at the Developers

    +1
  11. Add: Froyo 2.2 custom cm6-1-roggin-dario93-v2/ And format the topic with bullets, it will make it much more clear. Thanks for the effort, I hope you will keep it updated :D
  12. yes, swap is enabled on kernel.
  13. [NEWS]Gingerbread comes.

    Hmm, I haven't wiped the /cache/dalvik-cache folder, instead I've just deleted the files that were started with "[email protected]" and ones from the system that I didn't needed. At least this way the new system dalvik cache generated is created on cache and not on data but I will test that further. I'm testing this on CM 6 and not on this GB ROM so I'm not 100% sure it behaves the same way.
  14. [NEWS]Gingerbread comes.

    I think that after reboot your ramdisk content gets refreshed so you can't edit it like that. As promised I created a boot.img for this ROM with that line removed. Just flash one, if you get a bootloop right after Acer logo just try the other.I don't have this ROM now so I can't test, just tell me which one works so I can remove the other from the post. A) http://www.multiupload.com/0FGDWWW9E5 (deploy 0) :D http://www.multiupload.com/LXO06E91A6 (deploy 1) You can now execute both commands: adb shell busybox rm /data/dalvik-cache adb shell busybox mkdir /data/dalvik-cache adb reboot (you need to reboot after) You can also delete/create that dir with root explorer or equivalent.
  15. [NEWS]Gingerbread comes.

    I've posted the solution here (which works for CM and MIUI (I'm not sure if the boot.img works with MIUI but the used method - init.rc patched - works)): http://android.modaco.com/index.php?s=&amp...t&p=1546427 Tomorrow I can make a new boot.img to fix it, if no one post it first.
×