twrock, on 14 September 2011 - 12:06 AM, said:
I have thought as much as well. However, I can do a "stock" install of CM6.1, install no apps, set everything I can find to optimize battery life, and still have my battery drop over 10-15% overnight (8 hours or less). That is with no use at all. That can't be right.
Today sat for 10 minutes with a cpu monitor app and watched the frequency only drop to 245mhz momentarily before immediately jumping back up to 614 (default) and sitting there for more than 90% of the time. But the monitor was showing me that I had less than 20% cpu usage. That can't be right. It makes no sense to me.
I know I don't know much, but if the cpu settings in the rom are any indication, the frequency in this boot.img is supposed to drop when the load is below 60% and not go back up until the load reaches 76%. That is not what I am seeing.
BTW, you'll probably know what this means and can hopefully tell me if it matters at all. What I noticed is that in stock Huawei roms, the cpu sampling_rate is set at 200000 (in init.qcom.sh). But in the CM6.1 boot.img's it is set at 20000, 10 times less (in init.qcom.rc). Purposefully, or did Tom just make a typo? I have no idea, but that is what I was trying to test.
And with all the other complaining about CM6 roms, I think there is more to it than just my phone. Please give any other feedback you have. Thanks.
Edit: Regarding "stock install", please let me clarify. I have been installing DT Apps2SD in addition to the base rom and gapps. Do you run DT a2sd or use the built-in? Can you elaborate on your setup?
Hey, sorry for late reply. Unfortunately I don't know much about about the sampling_rate etc, but from what I understand it is the frequency that the cpu load is checked to adjust the clock speed as appropriate (ondemand_governor), so if the clock speed jumps up it should be because something is loading the cpu. As the Pulse has old hardware I guess it makes sense that basic tasks would load the cpu?
Not sure what cpu monitoring app you're using but I personally use the latest setCPU for monitoring/checking that kind of stuff. Also as you had the app open that would prob explain why the cpu clock kept jumping up as it was loading the cpu doing it's monitoring. I guess increasing the sampling_rate might reduce how often the clock speed jumps up, but that may also mean a reduction in performance?
With regard to my set up, I've never used DT. I use a couple of firerat's scripts (not sure if they will do every thing you would want though?) for apps2sd. And I have a swap partition that is controlled by a script in init.d. Haven't played with the pulse for ages but I basically have a modded rom of what Tom released. Think I deleted some of the default apps so maybe that had an effect? If you can connect your phone via adb maybe do a ls of your /system/app/ directory & paste it up so I can see what I've deleted?
I guess there's also the possibility you have a dodgy battery
The above is also all speculation by the way, I don't have any specific knowledge on the matter at all lol!
EgyptoBoy, on 14 September 2011 - 11:29 AM, said:
please can you upload a kernel like your 710mhz but with 748mhz oc (because i loved your 710 kernel and i want higher freq because my device can run it without errors)
Sorry, I don't even have access to the pc that has all the source files etc anymore. I'm pretty sure someone posted one somewhere though, as I remember helping him calculate the numbers?