Jump to content

[ROM] CM7 Liquid (kang) 1.2.18 -CM7RC1-

Guest koudelka

By Guest koudelka
in Acer Liquid

 Share

Recommended Posts

Guest albi86

Guest albi86

Posted
Posted

I tried to install the build Koudelka "old sensor" and the app "Proximity Screen Off", however, the proximity sensor is still not working, that is, once set up the program, the sensor works divinely, but as soon as you restart the phone, sensor operates at the beginning and then the screen stays black and locked and I pull the battery to restart the phone. Too bad because this rom is very very good :) , perhaps even more than miui! (excuse my English as always) :)

Link to comment
Share on other sites
  • Replies 1.8k
  • Created
  • Last Reply

Popular Days

Popular Days

Posted Images

Guest sundawg

Guest sundawg

Posted
Posted
Downloaded, flashed, restarted and i have a boot loop! same with leo rom don't know why.. any ideas?

did u do a manual wipe before flashing the rom?

Link to comment
Share on other sites
Guest fear_factory84

Guest fear_factory84

Posted
Posted
I did this and after testing it for a day, it's been 24h and I have 35% left

Could you test if sygic aura works with that flavour of rom (acer's gl driver on acer roms don't work)? You can easily use the demo on the market.

Thanks

Link to comment
Share on other sites
Guest sundawg

Guest sundawg

Posted
Posted
yes, I did

did u follow the complete wipe procedure? wipe all, wipe dalvik,wipe ext2 if u have ext 2 enabled, wipe rotate, wipe battery stats and finally cache, dont try wipe all including sd which is at the end.do this procedure twice and flash the rom with no sign check,and reboot,while reooting make sure u remove usb cable .and after first boot.reboot ur device again..i believe it will be up and running.give it a try.. :)

Link to comment
Share on other sites
Guest Delnar_Ersike

Guest Delnar_Ersike

Posted
Posted
btw apps to sd gui doesnt work

how to make it work XD

Seconded, it keeps Force Closing on me, so I can't set the ROM to use my 256MB swap partition. Here's a logcat if it helps:

I/ActivityManager(  131): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0

x10200000 cmp=com.elgubbo.a2sdGUI/.DashBoard } from pid 1551

I/ActivityManager(  131): Start proc com.elgubbo.a2sdGUI for activity com.elgubbo.a2sdGUI/.DashBoard: pid=8306 uid=10022

 gids={}

D/su	  ( 8315): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/su	  ( 8316): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/su	  ( 8318): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/su	  ( 8320): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/A2SDGUI ( 8306): Hey! readA2sdFlags is started!

D/A2SDGUI ( 8306): the index of 2.7.5.3 is -1

I/ActivityManager(  131): Displayed com.elgubbo.a2sdGUI/.DashBoard: +733ms (total +4s476ms)

D/su	  ( 8323): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/dalvikvm( 8306): GC_CONCURRENT freed 253K, 52% free 2721K/5639K, external 0K/0K, paused 2ms+9ms

D/su	  ( 8325): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/AndroidRuntime( 8306): Shutting down VM

W/dalvikvm( 8306): threadid=1: thread exiting with uncaught exception (group=0x40015560)

E/AndroidRuntime( 8306): FATAL EXCEPTION: main

E/AndroidRuntime( 8306): java.lang.NullPointerException

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdgui.refresh(A2sdgui.java:149)

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdgui.init(A2sdgui.java:59)

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdChecker.onPostExecute(A2sdChecker.java:83)

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdChecker.onPostExecute(A2sdChecker.java:1)

E/AndroidRuntime( 8306):		at android.os.AsyncTask.finish(AsyncTask.java:417)

E/AndroidRuntime( 8306):		at android.os.AsyncTask.access$300(AsyncTask.java:127)

E/AndroidRuntime( 8306):		at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:429)

E/AndroidRuntime( 8306):		at android.os.Handler.dispatchMessage(Handler.java:99)

E/AndroidRuntime( 8306):		at android.os.Looper.loop(Looper.java:123)

E/AndroidRuntime( 8306):		at android.app.ActivityThread.main(ActivityThread.java:3839)

E/AndroidRuntime( 8306):		at java.lang.reflect.Method.invokeNative(Native Method)

E/AndroidRuntime( 8306):		at java.lang.reflect.Method.invoke(Method.java:507)

E/AndroidRuntime( 8306):		at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)

E/AndroidRuntime( 8306):		at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)

E/AndroidRuntime( 8306):		at dalvik.system.NativeStart.main(Native Method)

W/ActivityManager(  131):   Force finishing activity com.elgubbo.a2sdGUI/.DashBoard

On a side note, for some reason, my Liquid's contrast became higher than normal. I don't know what caused it, it doesn't really annoy me, it isn't the Brightness setting, it isn't a render effect, it isn't a CM profile AFAIK, the contrast was reset after a reboot, but I'd still like to know what caused it and/or if I could turn it on again somehow. :)

Link to comment
Share on other sites
Guest koudelka

Guest koudelka

Posted
Posted
Seconded, it keeps Force Closing on me, so I can't set the ROM to use my 256MB swap partition. Here's a logcat if it helps:

I/ActivityManager(  131): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0

x10200000 cmp=com.elgubbo.a2sdGUI/.DashBoard } from pid 1551

I/ActivityManager(  131): Start proc com.elgubbo.a2sdGUI for activity com.elgubbo.a2sdGUI/.DashBoard: pid=8306 uid=10022

 gids={}

D/su	  ( 8315): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/su	  ( 8316): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/su	  ( 8318): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/su	  ( 8320): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/A2SDGUI ( 8306): Hey! readA2sdFlags is started!

D/A2SDGUI ( 8306): the index of 2.7.5.3 is -1

I/ActivityManager(  131): Displayed com.elgubbo.a2sdGUI/.DashBoard: +733ms (total +4s476ms)

D/su	  ( 8323): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/dalvikvm( 8306): GC_CONCURRENT freed 253K, 52% free 2721K/5639K, external 0K/0K, paused 2ms+9ms

D/su	  ( 8325): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/AndroidRuntime( 8306): Shutting down VM

W/dalvikvm( 8306): threadid=1: thread exiting with uncaught exception (group=0x40015560)

E/AndroidRuntime( 8306): FATAL EXCEPTION: main

E/AndroidRuntime( 8306): java.lang.NullPointerException

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdgui.refresh(A2sdgui.java:149)

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdgui.init(A2sdgui.java:59)

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdChecker.onPostExecute(A2sdChecker.java:83)

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdChecker.onPostExecute(A2sdChecker.java:1)

E/AndroidRuntime( 8306):		at android.os.AsyncTask.finish(AsyncTask.java:417)

E/AndroidRuntime( 8306):		at android.os.AsyncTask.access$300(AsyncTask.java:127)

E/AndroidRuntime( 8306):		at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:429)

E/AndroidRuntime( 8306):		at android.os.Handler.dispatchMessage(Handler.java:99)

E/AndroidRuntime( 8306):		at android.os.Looper.loop(Looper.java:123)

E/AndroidRuntime( 8306):		at android.app.ActivityThread.main(ActivityThread.java:3839)

E/AndroidRuntime( 8306):		at java.lang.reflect.Method.invokeNative(Native Method)

E/AndroidRuntime( 8306):		at java.lang.reflect.Method.invoke(Method.java:507)

E/AndroidRuntime( 8306):		at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)

E/AndroidRuntime( 8306):		at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)

E/AndroidRuntime( 8306):		at dalvik.system.NativeStart.main(Native Method)

W/ActivityManager(  131):   Force finishing activity com.elgubbo.a2sdGUI/.DashBoard

you should probably report this to elgubbo instead, I don't think it has anything to do with the rom (if it does, I think he should know how to fix it :), since he has the code :))

Link to comment
Share on other sites
Guest fischschneehase

Guest fischschneehase

Posted
Posted
Seconded, it keeps Force Closing on me, so I can't set the ROM to use my 256MB swap partition. Here's a logcat if it helps:

I/ActivityManager(  131): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0

x10200000 cmp=com.elgubbo.a2sdGUI/.DashBoard } from pid 1551

I/ActivityManager(  131): Start proc com.elgubbo.a2sdGUI for activity com.elgubbo.a2sdGUI/.DashBoard: pid=8306 uid=10022

 gids={}

D/su	  ( 8315): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/su	  ( 8316): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/su	  ( 8318): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/su	  ( 8320): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/A2SDGUI ( 8306): Hey! readA2sdFlags is started!

D/A2SDGUI ( 8306): the index of 2.7.5.3 is -1

I/ActivityManager(  131): Displayed com.elgubbo.a2sdGUI/.DashBoard: +733ms (total +4s476ms)

D/su	  ( 8323): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/dalvikvm( 8306): GC_CONCURRENT freed 253K, 52% free 2721K/5639K, external 0K/0K, paused 2ms+9ms

D/su	  ( 8325): 10022 com.elgubbo.a2sdGUI executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/AndroidRuntime( 8306): Shutting down VM

W/dalvikvm( 8306): threadid=1: thread exiting with uncaught exception (group=0x40015560)

E/AndroidRuntime( 8306): FATAL EXCEPTION: main

E/AndroidRuntime( 8306): java.lang.NullPointerException

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdgui.refresh(A2sdgui.java:149)

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdgui.init(A2sdgui.java:59)

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdChecker.onPostExecute(A2sdChecker.java:83)

E/AndroidRuntime( 8306):		at com.elgubbo.a2sdGUI.A2sdChecker.onPostExecute(A2sdChecker.java:1)

E/AndroidRuntime( 8306):		at android.os.AsyncTask.finish(AsyncTask.java:417)

E/AndroidRuntime( 8306):		at android.os.AsyncTask.access$300(AsyncTask.java:127)

E/AndroidRuntime( 8306):		at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:429)

E/AndroidRuntime( 8306):		at android.os.Handler.dispatchMessage(Handler.java:99)

E/AndroidRuntime( 8306):		at android.os.Looper.loop(Looper.java:123)

E/AndroidRuntime( 8306):		at android.app.ActivityThread.main(ActivityThread.java:3839)

E/AndroidRuntime( 8306):		at java.lang.reflect.Method.invokeNative(Native Method)

E/AndroidRuntime( 8306):		at java.lang.reflect.Method.invoke(Method.java:507)

E/AndroidRuntime( 8306):		at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)

E/AndroidRuntime( 8306):		at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)

E/AndroidRuntime( 8306):		at dalvik.system.NativeStart.main(Native Method)

W/ActivityManager(  131):   Force finishing activity com.elgubbo.a2sdGUI/.DashBoard

On a side note, for some reason, my Liquid's contrast became higher than normal. I don't know what caused it, it doesn't really annoy me, it isn't the Brightness setting, it isn't a render effect, it isn't a CM profile AFAIK, the contrast was reset after a reboot, but I'd still like to know what caused it and/or if I could turn it on again somehow. :)

use swapper 2 instead;)

Link to comment
Share on other sites
Guest KeruDoitsu

Guest KeruDoitsu

Posted
Posted

I just noticed that Add Gesture in lockscreen in CMparts just makes it force close xD

Does anyone experience a fast battery drain sometimes?

I don't know, sometimes battery life is insanely great, sometimes it drains faster O_O

Or maybe it's just me becoming paranoic for the perfect rom xD

Link to comment
Share on other sites
Guest chiksum

Guest chiksum

Posted
Posted
I just noticed that Add Gesture in lockscreen in CMparts just makes it force close xD

Does anyone experience a fast battery drain sometimes?

I don't know, sometimes battery life is insanely great, sometimes it drains faster O_O

Or maybe it's just me becoming paranoic for the perfect rom xD

I think this is the answer :)

Nice =)

Anyway, with every cm7 build I tried I have the same "strange" problem.

Battery drain is faster after a full battery charge with phone turned on (sleep mode).

Then, if I perform a hot or normal reboot..everything turns back fine and I have a normal battery drain.

Does anyone else have this.. behaviour? =O

Thanks :)

Link to comment
Share on other sites
Guest fear_factory84

Guest fear_factory84

Posted
Posted

cm7_1.4.18 + gralloc qsd + no_prox boot img, rebooted after charge, airplane mode, 35% battery drain during the night... :)

Link to comment
Share on other sites
Guest sundawg

Guest sundawg

Posted
Posted

well for me its other way ..i'm getting good battery ..almost like 1%/hour ...with proxy sensor on 3g on..what i did was let the battery drain after first flash,by using it randomly.on the second charge with phone off first took off battery for about 30-40 seconds and plugged back in.and chraged it to full in phone off mode.maybe it took around 7 hours to complete charge..did a normal boot and once it comes to home screen rebooted the phone in recovery & did a wipe battery stats.and reboot..thats it..everything s working perfect with 1% / hour ..its now 25 hours my battery still has 72% left..hope this helps :)

Link to comment
Share on other sites
Guest sundawg

Guest sundawg

Posted
Posted (edited)
btw apps to sd gui doesnt work

how to make it work XD

app to sd gui works for me though..with ext 2 =1024mb swipe =0 :)

Edited by sundawg
Link to comment
Share on other sites
Guest Robin Woodo

Guest Robin Woodo

Posted
Posted

I'm sorry for that question, but there are so many new versions out, so I don't know which version is the best at the moment. So what is the version with the best battery drain at the moment?

Link to comment
Share on other sites
Guest Dr. Robert Chase

Guest Dr. Robert Chase

Posted
Posted
I'm sorry for that question, but there are so many new versions out, so I don't know which version is the best at the moment. So what is the version with the best battery drain at the moment?

tle last one.

Link to comment
Share on other sites
Guest sundawg

Guest sundawg

Posted
Posted
I will probably release new one tonight for the people who like testing :(

Sounds good koud ..all of ur roms are very snappy ..plus the last build on post #1160 really works amazing for me.. :) :huh: ....i posted earlier ..my results of usage ..but will def test the next coming up by you..thanks & great work.. :)

Link to comment
Share on other sites
Guest koudelka

Guest koudelka

Posted
Posted
Sounds good koud ..all of ur roms are very snappy ..plus the last build on post #1160 really works amazing for me.. :) :) ....i posted earlier ..my results of usage ..but will def test the next coming up by you..thanks & great work.. :)

hopefully you will have same battery life with this new build :( and it might even be a bit faster since I now include kernel built from thepastos source, and he has added some nice patches to lowmem killer and ondemand governor :huh: uploading now, will be up in about 15min

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

Important Information

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

  I accept