[to devs] Acer Liquid E Does not Need Compcache

[Guest xaueious]

The Acer Liquid E does not need compcache. It already has double the RAM.

I guess most users are on the Liquid and not the Liquid E, but there are those out there who have double the RAM already, in which case the compcache hacks are not useful.

Just something to note if building ROMs and kernels.

Here's the kernel I'm running on my Liquid E for 998 MHz, no compcache. Based on phhusson's 998MHz with compcache, except I played with the voltages for the slower speeds a little. And it's cfq scheduler.

Bootsplash based on 月喰い谷 by aile, http://www.pixiv.net/member_illust.php?mod...lust_id=6768374

Flash as update.zip.

LCR_1.7_kernel_960MHzUV_nocompcache_audiohack_xau.zip

Edited July 9, 2010 by xaueious

[Guest mmkim]

The Acer Liquid E does not need compcache. It already has double the RAM.

I guess most users are on the Liquid and not the Liquid E, but there are those out there who have double the RAM already, in which case the compcache hacks are not useful.

Just something to note if building ROMs and kernels.

Here's the kernel I'm running on my Liquid E for 998 MHz, no compcache. Based on phhusson's 998MHz with compcache, except I played with the voltages for the slower speeds a little. And it's cfq scheduler.

Bootsplash based on 月喰い谷 by aile, http://www.pixiv.net/member_illust.php?mod...lust_id=6768374

Flash as update.zip.

what version your running liquid E?? and what phhusson version are running??

pls say about that. :)

[Guest xaueious]

what version your running liquid E?? and what phhusson version are running??

pls say about that. :)

I'm running LCR 1.7. I'm just commenting on the custom kernels and the ROMs which come with compcache enabled in the kernel or ROM.

Ideally I prefer compcache to be enabled in the ROM instead of via the kernel. I can't turn it off as easily depending on how the compcache script is setup

Built from phhusson 998MHz ramdisk, modified to remove compcache. Using Acer Liquid E source from phhusson.

Edited July 7, 2010 by xaueious

[Guest mmkim]

I'm running LCR 1.7. I'm just commenting on the custom kernels and the ROMs which come with compcache enabled in the kernel or ROM.

Ideally I prefer compcache to be enabled in the ROM instead of via the kernel. I can't turn it off as easily depending on how the compcache script is setup

Built from phhusson 998MHz ramdisk, modified to remove compcache. Using Acer Liquid E source from phhusson.

ok!! I see. thks!!

P.S.: how much your country of degree & weather??

because in here was very hot.....33 degree. Are you hang your phone?

Edited July 7, 2010 by mmkim

[Guest xaueious]

ok!! I see. thks!!

P.S.: how much your country of degree & weather??

because in here was very hot.....33 degree. Are you hang your phone?

Same here man. I use SetCPU though. It scales up and down up to 998MHz.

[Guest phhusson]

Here's the kernel I'm running on my Liquid E for 998 MHz, no compcache. Based on phhusson's 998MHz with compcache, except I played with the voltages for the slower speeds a little. And it's cfq scheduler.

I hope you're using a SVS enabled kernel, since voltage doesn't change without it.

Also, the governor I use (I can't remember which one it is, but still it's not cfq), is the one that qualcomm says is the best suited for smartphones.

[Guest csics5]

I hope you're using a SVS enabled kernel, since voltage doesn't change without it.

Also, the governor I use (I can't remember which one it is, but still it's not cfq), is the one that qualcomm says is the best suited for smartphones.

Edit: Deleted.

Edited July 8, 2010 by csics5

[Guest HustlinDaily]

I hope you're using a SVS enabled kernel, since voltage doesn't change without it.

Also, the governor I use (I can't remember which one it is, but still it's not cfq), is the one that qualcomm says is the best suited for smartphones.

YES! HES ALIVE!!

WELCOME BACK!!

[Guest xaueious]

I hope you're using a SVS enabled kernel, since voltage doesn't change without it.

Also, the governor I use (I can't remember which one it is, but still it's not cfq), is the one that qualcomm says is the best suited for smartphones.

Ya I am using SVS enabled. I didn't deviate from the .config in your git that much. I just changed to CFQ because that's what Cyanogenmod uses.

The post I made in your thread about voltages was wrong. Anyways I don't really understand how the table works. It does seem like our voltages are not as friendly as those on for Cyanogenmod for 1GHz, as we need 1.3v just to hit 998MHz and they do just fine at 1.275v. But our 768MHz is at a lower voltage.

Your table is a bit weird, especially at 576 MHz at 1.2v (if I remember. I am not looking at it). That's probably why people are reporting loss of battery life.

Anyways back on topic though, having compcache enabled in the kernel is a bit annoying, especially that I couldn't manage to turn it off in with an init.d script. I had to modify the boot.img. Shouldn't the compcache script either be called as a part of init.d so users can change it?

[Guest phhusson]

Ya I am using SVS enabled. I didn't deviate from the .config in your git that much. I just changed to CFQ because that's what Cyanogenmod uses.

The post I made in your thread about voltages was wrong. Anyways I don't really understand how the table works. It does seem like our voltages are not as friendly as those on for Cyanogenmod for 1GHz, as we need 1.3v just to hit 998MHz and they do just fine at 1.275v. But our 768MHz is at a lower voltage.

Your table is a bit weird, especially at 576 MHz at 1.2v (if I remember. I am not looking at it). That's probably why people are reporting loss of battery life.

I didn't change the values at all from what was there before /o\

And I can't see how it can be a battery loss, since AFAIK, before, the voltage was always 1.25V.

Anyways back on topic though, having compcache enabled in the kernel is a bit annoying, especially that I couldn't manage to turn it off in with an init.d script. I had to modify the boot.img. Shouldn't the compcache script either be called as a part of init.d so users can change it?

Of course it should, it's just not as simple for me :)

[Guest dennerjw]

I flashed the zip in recovery and went into SetCPU, it said 960 MHz. I touched the "max" value slider and the max freq. went down to the stock 768... Am I missing something?

On reboot it goes back to 960... but i can't change it with SetCPU without it going back down to stock.

Edited July 12, 2010 by dennerjw

[Guest Quipeace]

...

The post I made in your thread about voltages was wrong. Anyways I don't really understand how the table works. It does seem like our voltages are not as friendly as those on for Cyanogenmod for 1GHz, as we need 1.3v just to hit 998MHz and they do just fine at 1.275v. But our 768MHz is at a lower voltage.

...

998MHz worked fine on 1.25V, it's device specific :).

Edited July 12, 2010 by Quipeace