Jump to content
youpi666

[CM7.2] Cyanogenmod 7.2 for LiquidA1/LiquidE

Recommended Posts

I've installed cpuSpy and it semms that Deep Sleep Mode is never used, so the answer is, "no, fast dormancy is not enabled in this rom"

Any way to do that, i've noticed an heavy battery drain compared to LN 1.9.2

Share this post


Link to post
Share on other sites

I've installed cpuSpy and it semms that Deep Sleep Mode is never used, so the answer is, "no, fast dormancy is not enabled in this rom"

Any way to do that, i've noticed an heavy battery drain compared to LN 1.9.2

deep sleep works for me, but i notice the heavy battery drain

Share this post


Link to post
Share on other sites

deep sleep works for me, but i notice the heavy battery drain

Ok, after a counter reset now i see deep sleep on. But i've heavy battery drain too.

Share this post


Link to post
Share on other sites

I've installed cpuSpy and it semms that Deep Sleep Mode is never used, so the answer is, "no, fast dormancy is not enabled in this rom"

No. Because fast dormancy and deep sleep are two very different things :)

What are good settings for custom SVS? Should I take the values from this thread? http://www.modaco.co...incredicontrol/

These values are already use in liquidparts as the suggested values.

But be sure you could have to adapt to your phone, every liquid react differently.

Share this post


Link to post
Share on other sites

i'm pretty sur that's have the auto brightness on eat more battery than off :)

or don't let your brightness to the max when auto is off.

You measure that ?

Share this post


Link to post
Share on other sites

i'm pretty sur that's have the auto brightness on eat more battery than off :)

or don't let your brightness to the max when auto is off.

You measure that ?

autobrightness on: 14 hours battery life

autobrightness off: 5 hours battery life (backlight set to 30%)

Share this post


Link to post
Share on other sites

The first think you must do is to cut 3G and wifi when you don't use it i have little more than 48h battery life (with autobrightness off) (or you're a power user :) )

I'll see if i could redo the phenomenon

(but for the moment always think that the the autobrighness is not the origin of your difference ;) )

Share this post


Link to post
Share on other sites

I'm sorry to say, I went back to the stock rom :blush:

The battery life is fine with 2G and low screen brightness.

These things still bother me before I will use this as default ROM:

- Auto brightness not smooth ( I don't like switching brightness every time )

- Battery life with 3G is bad, 2G is just too slow for me

Since I travel in the train for 3hrs every day, battery life is important to me.

I look forward to future updates!

Share this post


Link to post
Share on other sites

75% brightness is sufficient for most uses. Anything beyond this value burns through the battery really quickly. That's probably the cause of your battery drain.

I wouldn't be against it if you modified the ROM to lower maximum backlight brightness to increase battery life for most users.

Auto-brightness on makes backlight brightness lower right now.

Edited by xaueious

Share this post


Link to post
Share on other sites
I wouldn't be against it if you modified the ROM to lower maximum backlight brightness to increase battery life for most users.

That will make phone totally unusable under sunlight. Never do that!

Share this post


Link to post
Share on other sites

Well after many tests, the light sensor works great, it's the CM transition method who's not perfect (but really usable, personally i don't understand the trouble cause by a little jump on a brightness value :) )

AND

All the auto brightness param are tweakable by the CM menu so :

For the next update, all param will be default param, users who want use auto brightness could tweak it as they will.

Don't ask for the date of update, need to finish some kernel things first :)

Edited by youpi666

Share this post


Link to post
Share on other sites

Youpi, can you check what's wrong with swap enabled? The phone become unusable with that option and on A1 very necessary a swap area.

If you want i can take some logs.

Share this post


Link to post
Share on other sites

nothing wrong with swap enable, i use it since first day, and have no problem :)

Sure about your microSD quality ?

Maybe some log could help to see what happen on your device.

Share this post


Link to post
Share on other sites

I'm trying a different value of HeapSize of the VM, was 48, now is 24 and it seems to be good, with swap enabled.

I've a 16GB class10 samsung microsd, with 256MB swap, 1GB ext4 and the other is FAT32.

My adb logcat with swap enabled ( 20 swappiness) and VM heapsize 48 is here (only some interesting rows):

I/dalvikvm( 4430): threadid=4: reacting to signal 3

D/dalvikvm( 286): GC_EXPLICIT freed 12K, 51% free 2659K/5379K, external 0K/0K, paused 89ms

I/dalvikvm( 4430): Wrote stack traces to '/data/anr/traces.txt'

I/Process ( 2071): Sending signal. PID: 2071 SIG: 3

I/dalvikvm( 2071): threadid=4: reacting to signal 3

D/dalvikvm( 286): GC_EXPLICIT freed <1K, 51% free 2659K/5379K, external 0K/0K, paused 40ms

D/dalvikvm( 286): GC_EXPLICIT freed <1K, 51% free 2659K/5379K, external 0K/0K, paused 26ms

I/dalvikvm( 2071): Wrote stack traces to '/data/anr/traces.txt'

I/Process ( 2071): Sending signal. PID: 7884 SIG: 3

I/dalvikvm( 7884): threadid=4: reacting to signal 3

I/dalvikvm( 7884): Wrote stack traces to '/data/anr/traces.txt'

I/Process ( 2071): Sending signal. PID: 7389 SIG: 3

I/dalvikvm( 7389): threadid=4: reacting to signal 3

I/dalvikvm( 7389): Wrote stack traces to '/data/anr/traces.txt'

W/SharedBufferStack( 7389): waitForCondition(LockCondition) timed out (identity=1436, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 7389): waitForCondition(LockCondition) timed out (identity=1436, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 7389): waitForCondition(LockCondition) timed out (identity=1436, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 7389): waitForCondition(LockCondition) timed out (identity=1436, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 7389): waitForCondition(LockCondition) timed out (identity=1436, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 7389): waitForCondition(LockCondition) timed out (identity=1436, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 7389): waitForCondition(LockCondition) timed out (identity=1436, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 7389): waitForCondition(LockCondition) timed out (identity=1436, status=0). CPU may be pegged. trying again.

and i have many of this rows

W/AudioTrack( 4467): obtainBuffer() track 0x1a78e0 disabled, restarting

W/AudioTrack( 4467): obtainBuffer() track 0x1a78e0 disabled, restarting

W/AudioTrack( 4467): obtainBuffer() track 0x1a78e0 disabled, restarting

W/AudioTrack( 4467): obtainBuffer() track 0x1a78e0 disabled, restarting

W/AudioTrack( 4467): obtainBuffer() track 0x1a78e0 disabled, restarting

W/AudioTrack( 4467): obtainBuffer() track 0x1a78e0 disabled, restarting

W/AudioTrack( 4467): obtainBuffer() track 0x1a78e0 disabled, restarting

W/AudioTrack( 4467): obtainBuffer() track 0x1a78e0 disabled, restarting

W/AudioTrack( 4467): obtainBuffer() track 0x1a78e0 disabled, restarting

W/AudioTrack( 4467): obtainBuffer() track 0x1a78e0 disabled, restarting

I/AudioHardwareQSD( 289): AudioHardware pcm playback is going to standby.

Share this post


Link to post
Share on other sites

yet another tiny bug but probably cm side.

if you press power off button to block your device but accidentally touch any of the bottom sensor keys while it's animating then the device will turn on back

(thought the screen will be blocked so it doesn't hurt much as it will turn off later in your pocket)

Share this post


Link to post
Share on other sites

Hello everyone. Put the firmware, works fine, the battery gets 1% of the time lying on the table. (Wi-fi, mobile internet switched off, is the mode 2g). Backlight automatically removed, is 60%.

Is it possible to increase fps on the camcorder? 10 fps does not satisfy...

Share this post


Link to post
Share on other sites

@bellanano : Your oc ? a2sd ?

GvM: don't have the problem, check in CM menu if a option like this is not enable.

Shurigreek : don't know if i could do something on this, must check.

Share this post


Link to post
Share on other sites

Hi youpi666, thanks for your great work.

Could you improve 3d performance of this cm7.2 like in liquidnext?

Thanks

Share this post


Link to post
Share on other sites

I've OC at 1152MHz +smartassV2 (I've tried ondemand too), no compcache, no dithering, 16 bit transparency on, heap VM 24m (with this value the phone is quite usable).

I'm using svs suggested value and a2sd ON

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

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