yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] julianwp:
[MENTION=5604178]zwliew[/MENTION] is there any custom cpufreq from 100MHz in the new release?
[Galaxy Ace II Android Development] doctormord:
200...
[Galaxy Ace II Android Development] tofikos:
No deep sleep Rox 02/06 zwliew 02/06 :(
[Galaxy Ace II Android Development] julianwp:
will it be 200,300,400,500,600,700,800,900,1000 , ..... 1250 ?
[Galaxy Ace II Android Development] doctormord:
Just the standard ones, 2/4/6/8/1000 + 1050..1250, as of the older kernel-versions. (i.e. 0519 which works best here)
[Galaxy Ace II Android Development] zwliew:
currently in the midst of rebasing the kernel from scratch, may take a while. but for now, here is what i've done so far :]

this will take a while, but at least all known problems are solved.
[Galaxy Ace II Android Development] ace2nutzer:
I've make the following test and i find it very weird:

CPU 200 Mhz both Cores online, idle, airplane mode, display on and for 1 % Battery: 9 minutes.

The same Test, but with only 1 Core online: 9 minutes too !

So, that should us mean that the Hotplugging makes no effekt for battery life..

When Core 1 is offline, this comsumes power anyway...

therefore:

it makes no sense with the hotplugging ... thereby one has rather a higher battery consumption because then Core 0 has a higher utilization.

The battery consumption is classified as: (a lot of by little)

- 100% CPU load

- Frequency (the higher, the more consumption)

- CPU voltage

Earlier, it was different ... in the computer field, the higher the Vcore higher or the consumption (in idle mode) Temperature!

When Ace 2 is different! The Cortex A9 CPU is very efficient and economical!

Who all does not believe can test yourself ..

once with 200Mhz idle and once with 1000Mhz idle and you can see the temperature is at 1100 Mhz around 6 ° C less than 200 Mhz! (because by 1100 Mhz the CPU has less load) but it consumes anyway a little more power than 200 Mhz, because on 1,1 Ghz we have more Vcore.. That's all!

Test it with CPU Temp Plus of google play:

https://play.google.com/store/apps/details?id=com.yanyan.cputemp&hl=en

From this:

There is no need to even go to 100 MHz in idle .. the consumption depends most on the load! (and voltage) .. so it is enough to make UV for step0 .. my CPU runs at 200 Mhz with 0,825 V (default: 1 V ) ( -175mV )
[Galaxy Ace II Android Development] zwliew:
cpu load doesn't affect battery consumption, cpu load affects the cpu clock which affects the voltages at the same time. it is the cpu clock and voltages that affect battery consumption
[Galaxy Ace II Android Development] ace2nutzer:
yes .. not quite what I meant when you set the freq. manually .. try it out from.

If you are 100% load @ 200Mhz, did you have more consumption than at 1000 MHz and 10% load!

I believed until now the hotplugging a good idea is .. but in reality it makes our unit slowly.

EDIT:

Yes.. this is right, but WITH load ! without load the consumption is very low !!
[Galaxy Ace II Android Development] zwliew:
1000 mhz at 10% load should have more battery consumption than 100% load @ 200 mhz. anyway, why are you talking about hotplugging when the kernel doesn't have any?
[Galaxy Ace II Android Development] ace2nutzer:
Yes, I speak not of your kernel, I'm talking about hotplugging general!

I currently have the stock kernel from CM 11 .. but with changed Abyssplug governor I could test the thing with hotplugging.

By default, switches abyssplug Core 1 only if it is absoulut in idle!

I modified the Abyssplug Governor Value: hotplug_in_sampling_periods of 5 @ 200, then goes Core 1 online only if core 0 has a very high utilization!

And when you switch to ondemand remains core 1 completely offline until the next reboot!

So I could test!

What do you think? Try it! it is really weird !! :D:D:D
[Galaxy Ace II Android Development] asdroid:
With stock tc cm11 kernel and 200/1000, pegasusq/sioplus performance and battery life are very good.. 2 h of screen and 47% of battery remain :)

I think pegasusq put off one core only when screen is off, and it makes our phone much smooth than abyssplug governor imho.
[Galaxy Ace II Android Development] ace2nutzer:
nope :angel:

When screen is OFF u have deep sleep ! it's all the same witch governor u use

pegasusq is smoother than abyssplug because that scaling much more faster a freq. up, and from 200 - 400 this governor scaling very fast... aka up_threshold_at_min_freq ... look all the Files and Settings in the various Governors.. and u will see what i mean.. and u can changed this settings via Terminal or make it via init.d on boot ;)

pegasusq hotplug core 1 very rare... but abyssplug a little more.. and is slower.. therefore abyssplug saves power.. but is laggy !
[Galaxy Ace II Android Development] zwliew:
pegasusq does only hotplug cpu1 on suspend. abyssplug hotplugs based on load and stuff. offlined core saves more battery than online, deep sleep core
[Galaxy Ace II Android Development] julianwp:
is there any app to see the activity and elapsed time for each frequency but for each core?

we know CPU Spy, but as far as i know it only shows single core activity
[Galaxy Ace II Android Development] borkins:
Try Android Tuner app from play store.
[Galaxy Ace II Android Development] ace2nutzer:
Ok zwliew thank u ! i will make another (preciser) test as soon i can...

But i think the difference in idle with 1 core or 2 cores online is very low.

For now i use my phone with self made power profiles.. see in my signature.. i made an How-to incl. scripts !

It's very good.. No more lags so... but unfortunately you have to manually switch the profiles..

But you can expand it with TASKER and automate ! (thanks [MENTION=4962787]fluffi444[/MENTION] for the tip !)

For example: Screen OFF: LOW POWER profil; Screen ON: ECO Profil; and if required -----> NORMAL or TURBO !

After screen off and on, the Profile is ECO again .. that's perhaps a good thing !!!!!!

Another thing.. just for curiosity:

can u plz post which lines u have changed in Source to fix the min. cpu freq. ??:good::good::good:

Thank u very much !!
[Galaxy Ace II Android Development] matthias1976:
Llama from playstore iss a cheap alternative.

Ill love it !!
[Galaxy Ace II Android Development] ace2nutzer:
Deleted
[Galaxy Ace II Android Development] fifo171:
Please, delete the link. Warez isn't allowed at XDA.
[Galaxy Ace II Android Development] Oceandar:
Deleted
[Galaxy Ace II Android Development] ace2nutzer:
[MENTION=5604178]zwliew[/MENTION]

I'm Back :D

I make a Power consumption test with this app:

https://play.google.com/store/apps/details?id=com.manor.currentwidget&hl=de

and so as I thought: With 1 core online or two, it makes no differences.. but perhaps it is only on an Stock Kernel ??!!

Has your Kernel better hotplugging driver ? - Can u plz test it with tihs App ?? This Work very well !!

The Second Thing:

Undervolting less than: 0,85 V makes no sense.. and it consumes more power.

The Third good Thing:

My CPU runs with 200Mhz and 400Mhz at the same Voltage.... an i tested whether it makes a difference with 200 Mhz or 400Mhz ... ---> no difference !!!! So we can all set the minimum cpu freq. [MENTION=1989751]400[/MENTION] MHz (but with good UV) without more power consumption and make at the same time the Phone faster and smoother !! Therefore setting a min. cpu freq. @ 100Mhz saves no power and it make only the device very slow and choppy. (only from 600Mhz consumes more power!)

The Same Thing with the GPU: !

I tested with GPU Governor (AutoBoost GPU) in NT App one time with min: 192Mhz @ 1 Vape and maximum: 540 Mhz @ 1,225 Vape ...

and one time i test it with disabled AutoBoost and i set the Freq. @ 540MHz .. same Vape and again: no difference !!!!

In all tests I also have the deep sleep current checked!

He was in all cases at 30 - 35mA!

The tests I have done all in offline mode and always with the same brightness display!
[Galaxy Ace II Android Development] doctormord:
I wont trust this app. Current/power measuring must/should be made in hardware. This app is slow and even not calibrated.
[Galaxy Ace II Android Development] borkins:
The performance go down at steps 6,7,8,9, when change varms to 0x36, 0x37, 0x38, 0x39.

I make many tests with every step and with these values the CPU work better at 1.0 - 1.05 GHz, than the last 1.1, 1.15, 1.2 and 1.25 GHz.

Also I have reboots over 1.05 GHz ( i didn't try uV-oV ).

Edit: Maybe with different voltages for the last 4 steps the CPU will work better. But now there is now change

in the voltage for steps 6,7,8,9 and is not equal to the change between steps 0-5.

So, if 1362 mV is the max possible Voltage, what else can be done for stabilisation of the CPU at last 4 steps?
[Galaxy Ace II Android Development] S.AMU:
Why should undervolting damage the hardware? Or do you mean overvolting?
[Galaxy Ace II Android Development] Asus-Tek:
Omg my mobile always booting last kernel + CM11 TC build 20/5 :(

Wipe dalvik cache wipe cache partition and factory reset do not work :crying: mobile always booting what?
[Galaxy Ace II Android Development] zwliew:
you installed the f2fs build didn't you? -_- install an old kernel that isn't marked with f2fs. if you don't have, you have no other choice but to odin stock rom. please don't install builds that you don't know whether they work or what they are for next time.

anyways,

new release 20140608!

i've rebased everything from scratch and i've been testing it for quite a while now. no problems so far. reboots and stuff should have been fixed. sorry for the wait but it's finally here! :D

hope you enjoy :]
[Galaxy Ace II Android Development] AtEExll:
I did try this new release, I go to recovery, make wipe cache and dalvik, instal kernel and reboot, all OK but is not installed... In settings / information phone / kernel version is not you kernel...

But in the install put ( installation complete) without error...

Is this kernel incompatible with android 4.4.3?

Thanks by advance.

Best regards.

AtEExll

Sent from my GT-I8160 powered by CyanogenMod 11
[Galaxy Ace II Android Development] ace2nutzer:
oops posted in an wrong thread... but the answer is coming in a pair of minutes !
[Galaxy Ace II Android Development] Eselter:
reboots, reboots, reboots ;/

back to kernel from 5-19
[Galaxy Ace II Android Development] zwliew:
i did not change the kernel version to my 'zwliew'. but as long as you see 'g63568d6' in the kernel version then it installed correctly.

what were you doing on your phone when you encountered reboots? i've not encountered a single reboot in a week. :/
[Galaxy Ace II Android Development] dragos281993:
Well this latest build looks very good. I'll have to admit that I didn't test it in a"hardcore" way, but I like the fact that the smoothness increased significantly due to "project butter" you implemented, I suppose. I'm on C-ROM 6.4 and I'm using the default settings which are interactive, row, but with min 400MHz --> max 1000MHz clock speed, and everything seems to be fine till now. When I wake up I'll play some games to see if the phone can take the heat.
[Galaxy Ace II Android Development] Master-ZizO:
First boot after installing kernel... Reboot at lockscreen and then reboot at boot logo.. Back to TC Stock kernel
[Galaxy Ace II Android Development] zwliew:
i don't get why you guys have reboots yet it's working perfectly like a charm here :/
[Galaxy Ace II Android Development] Eselter:
Nothing, I have reboot after 1 min of flashing kernel (on homescreen, 2 times).

Now I install new version of RR rom and I will try again latest kernel.

Sorry for my english :/
[Galaxy Ace II Android Development] zwliew:
can you guys send me the last_kmsg after you experienced a random reboot? it is in /proc/last_kmsg
[Galaxy Ace II Android Development] exodius48:
[MENTION=5604178]zwliew[/MENTION] is latest version from 20140607 support f2fs?
[Galaxy Ace II Android Development] zwliew:
don't use 20140607 unless you know what you're doing and are following the f2fs thread here
[Galaxy Ace II Android Development] Eselter:
http://www26.zippyshare.com/v/15118332/file.html

Now I have reboot in browser.
[Galaxy Ace II Android Development] exodius48:
So only build 20140607 that support f2fs?
[Galaxy Ace II Android Development] zwliew:
can you guys, and everyone else who has reboots try this test build? (applies to those who have reboots)

View attachment zwliew-kernel-20140609-test.zip

yes
[Galaxy Ace II Android Development] AtEExll:
Oh yeah! I can see g63568d6 in settings / phone information, it's all OK, no reboots and No FC, here works fine build 20140608.

Thanks for you efforts.

Best regards.

AtEExll

Sent from my GT-I8160 powered by CyanogenMod 11
[Galaxy Ace II Android Development] INFERNO777:
My reboots and fc
[Galaxy Ace II Android Development] Eselter:
I'm curious. What you see in last_kmsg :P?
[Galaxy Ace II Android Development] Oceandar:
Is it compatible with Dark CM 4.1 ? Would like to try but now I'm not near my laptop (Odin) if something's wrong happen...
[Galaxy Ace II Android Development] zwliew:
It should be.
[Galaxy Ace II Android Development] zwliew:
is the latest 20140609-test working okay without reboots?
[Galaxy Ace II Android Development] Eselter:
For now I don't have reboots, but bln not working :P.
[Galaxy Ace II Android Development] zwliew:
bln is not changed at all, it is working well
[Galaxy Ace II Android Development] Eselter:
I need script?Beacause with NT settings 1.5 not working :/
[Galaxy Ace II Android Development] zwliew:
you don't lol. are you sure your phone just doesn't have wakelocks while bln is going on? bln only blinks when your phone is awake/there is a wakelock holding your phone awake.
[Galaxy Ace II Android Development] ace2nutzer:
Or just activate swipe2wake, then the phone stay awake too.

Zwliew i have 2 questions:

1. it is possible to change the charging voltage ?? I see in Kernel it is setted @ 4350mV .. i would it to change @ 4300mV to increase some lifetime of the battery ! It's possible over script ?

2. It is possible to fix the min. cpu freq. bug over script ?! I'm on 13/05 Build.. i wanna fix it.. only for safety.. if 07/06 Build doesn't work good for me.. i know that is fixed in latest build...but I want to learn it.

Thank u very much !!

EDIT: I have posted my CPU / GPU UV / OV / OC Values / script here:

http://xdaforums.com/showpost.php?p=53244532&postcount=659

Nope... too much OV / UV can damage the hardware.. not only CPU / GPU !

if the voltage is too low, then turn certain transistors no longer correct and the current takes a different path. That is the reason why too much UV consumes more power .. because then lands set of undesirable current. To understand this, you can in the NT-App in "audio" "LPA Mode" enable the value in single steps down making: from 22 @ 21 .. then OK then display off .. music must of course run .. and if you scrape a loud hear from the speakers, you know ....if not, set the value @ 20 etc. The modest sound card no longer gets enough volts and the circuit makes errors and lets the stream through the speakers .. on the dot of what voltage it is .. or what component for one, can there are thus destroyed!
[Galaxy Ace II Android Development] S.AMU:
but I think you dont set it lower than, in my case, 20, because you still want to listen to music not scary sounds :DD also UV does not consumes more power. For example for the sound chip or for a brushless motor controller it would be bad, but a cpu would simply "shut down".
[Galaxy Ace II Android Development] INFERNO777:
[MENTION=5604178]zwliew[/MENTION] no reboots with 09test
[Galaxy Ace II Android Development] ace2nutzer:
I have little "tich" Sounds after display off with 23 ! ..24 works good.. no scary Sounds :D and i set it @ 25 now !!

All my CPU / GPU UV Values.. i have added +12.5mV on a stable Voltage.. Just for safety it runs really 100% stable !!

U must know that Transistors switches or not... with setted Voltage.. and depends on temp too !

Ok, u have probably right, with the CPU it can happen u have miscalculating or corrupted Data.. while he make errors by to low voltage.. u don't see the problem shortly.

But by GPU to low voltage can damage the Screen ! Like Sound Chip ----> Speaker ! GPU -------> Display....
[Galaxy Ace II Android Development] borkins:
I have reboots over 1050 MHz. Also the performance over 1050 MHz drops down a little. I make test with nenamark2 with different varm settings.

With 1.0, 1.05 GHz - 43.6 fps; 1.1, 1.2 GHz - 42.8 fps. With uV/oV the results are equal, also reboots are rarely.

What are the real voltages for last 4 steps, because it's difficult with values like 0x36, 0x3c and etc, especially when we can't see the voltage change

over 0x35 ( 1362.5 mV ).

I think will be better to change the voltage for last steps independent. I think now can't be stable with uV/oV for all steps.

Edit: I'm talk about something like this, or a way to see the real voltage somehow, not that must be. :\
[Galaxy Ace II Android Development] Eselter:
BLN now working fine (strange because I changed nothing).

But after pressing "home", buttons stays disabled.

I must turn off screen and again turn on.

This is a bug?
[Galaxy Ace II Android Development] danny19901:
Does this work on 4.4.3 I'm assuming it should but I need to sure as I will be using 26th of may build if this works
[Galaxy Ace II Android Development] ace2nutzer:
This happened when the CPU make miscalculating.. then everything is choppy like less performance...

U need to spend some more time to make it really stable over 1050 Mhz...

I can help u a bit..

from low to high.. iMHO:

34, 35, 36, 37, 38, 39, 3f

3a - 3e works very badly ! .. something is 100% wrong with the algorithm !

Try this scripts on init.d .. if u don't know the way... post it.. we help u !

don' use Voltage apps.. and don't use the Voltage regulator in NT- APP for now.. until everything working good.

1. Script:

#!/system/bin/sh
sleep 90
echo varm=0x33 > /sys/kernel/liveopp/arm_step5
echo varm=0x36 > /sys/kernel/liveopp/arm_step6
echo varm=0x36 > /sys/kernel/liveopp/arm_step7
echo varm=0x37 > /sys/kernel/liveopp/arm_step8
echo varm=0x38 > /sys/kernel/liveopp/arm_step9
#

if this doesn't work.. try next:

2.

#!/system/bin/sh
sleep 90
echo varm=0x30 > /sys/kernel/liveopp/arm_step4
echo varm=0x35 > /sys/kernel/liveopp/arm_step5
echo varm=0x38 > /sys/kernel/liveopp/arm_step6
echo varm=0x39 > /sys/kernel/liveopp/arm_step7
echo varm=0x3f > /sys/kernel/liveopp/arm_step8
echo varm=0x3f > /sys/kernel/liveopp/arm_step9
#

3.

#!/system/bin/sh
sleep 90
echo varm=0x31 > /sys/kernel/liveopp/arm_step4
echo varm=0x37 > /sys/kernel/liveopp/arm_step5
echo varm=0x39 > /sys/kernel/liveopp/arm_step6
echo varm=0x3f > /sys/kernel/liveopp/arm_step7
echo varm=0x3f > /sys/kernel/liveopp/arm_step8
echo varm=0x3f > /sys/kernel/liveopp/arm_step9
#

4.

#!/system/bin/sh
sleep 90
echo varm=0x32 > /sys/kernel/liveopp/arm_step4
echo varm=0x3f > /sys/kernel/liveopp/arm_step5
echo varm=0x3f > /sys/kernel/liveopp/arm_step6
echo varm=0x3f > /sys/kernel/liveopp/arm_step7
echo varm=0x3f > /sys/kernel/liveopp/arm_step8
echo varm=0x3f > /sys/kernel/liveopp/arm_step9
#

Bevore u start setting frequency or make tests.. check at first in the slot.. (1x should be enough) so the new values are setted.. after a reboot it can take a while.. around 30 sec. !

If the last script doesn't work too, u have no chance.. every CPU has a limit.. u can not OC every CPU @ 10000 Mhz :D
[Galaxy Ace II Android Development] AtEExll:
With 09test kernel, max 1000mhz absysplug / deadline 0 reboots!

Good job!

Sent from my scientific calculator using buttons 0 and 1
[Galaxy Ace II Android Development] Master-ZizO:
Testing Build 09-Test.. No reboot till now
[Galaxy Ace II Android Development] zwliew:
it is not a bug. when u switch on ur screen by pressing home, it assumes you are checking your notifications and switches bln off. anyway it will be quite annoying to have button lights blinking at you while you're using your phone :p

yes it works well :]

yay :] stable problem-free builds from now on? :highfive:
[Galaxy Ace II Android Development] Eselter:
But buttons should light normally (without blinking, if you have backlight buttons enabled).
[Galaxy Ace II Android Development] borkins:
[MENTION=5840412]ace2nutzer[/MENTION], thank you, now maybe i am on the right way!

Looks like it's important to change not only the last 4 steps. I tried many times changing only for 1.1, 1.15, 1.2, 1.25 GHz,

but when trying your settings looks the cpu works more stable at higher frequency.

I don't know what is my CPU ( good or bad ), but seems the precise frequency and voltage scaling leads to better results.

I'll make more test with lower CPU frequency ( 1100-1150 MHz ), to find out is 1200 Mhz too much for my CPU.

With the varm settings above, CPU at 1200 MHz - pegasusq/row, GPU at 250-500 MHz - AutoBoost, i get this:
[Galaxy Ace II Android Development] zwliew:
i don't get what you're saying, please elaborate. what are your configurations for both backlight and bln, and what are you experiencing?
[Galaxy Ace II Android Development] Rox:
[MENTION=5840412]ace2nutzer[/MENTION]

You guys should write to cocafe about that voltage stuff. maybe you can help him to make it completely stable
[Galaxy Ace II Android Development] ace2nutzer:
Well !! But testing stability with this tool, is not the right way.. Because the CPU Runs all the time @ max. speed ! But when u using your phone, u use it with scaling like CPU Governor ondemand, pegasusp etc.. so the freq. is scaling and the voltages too.

You can find with this tool a stable voltage for all steps.. (when u make different test.. with another max. freq.) but when u are done and switching on ondemand.. u have problems ! You see it work not stable ! Because on scaling mode the steps needs more Voltage !!

Therefore i make all my steps by this way stable:

set min. 200 and max. 800 --> ondemand..

Voltages all by default !

now, make UV only for step0 (200mhz) and to test stability:

open and close very quickly all your apps what u have !! Make this in a loop for around 10 minutes! After That, if u have no FC, freezes or reboot, add +12.5mV on this stable step0 so 200Mhz .. example: 0x0c was stable --then save it in your script as: 0x0d ! So in this way the step is 100% stable !! And so with the another steps !! 400, then 600, etc. until u have FC freeze or something else !!

So u can find very easy and quickly the max freq and the max. UV !! And when u are by 800 and done.. set the max. @ 1000Mhz then make the same procedure ! , then 1050 etc.. until u can not make it stable... that's it !

For GPU stability:

make UV over NT- APP and then changing a freq.. example: u are running on 500Mhz and u would change the voltage: set the new UV.. then switch zu 480 and back to 500 MHz .. now the new Voltage is setted on 500Mhz.. u can check all this stuff in kernel with Text editor... /sys/kernel/mali/ the mali_gpu_vape and mali_gpu_clock

And to check the new voltage and freq. is running without Artefacts :

Run with stability test CPU / GPU test and now watching on a rotate graphic for min. 20 minutes... until this time, if u don't see weird things.. the new GPU freq and voltage is OK !! But make sure before u OC / UV GPU that your CPU is 100% stabel.. if not u gonna creazy.. believe me !!

So, i hope this will help many users :p :D

[MENTION=4947931]Rox[/MENTION]

okay i do this later... now cocafe is back :good::good: time to fix problems :D
[Galaxy Ace II Android Development] str3tch72:
On latest Carbon Wi-Fi not working with test build.

Wysłane z mojego GT-I8160 przy użyciu Tapatalka
[Galaxy Ace II Android Development] S.AMU:
Something strange: since today BLN is only blinking 3 or 4 times then it stops...
[Galaxy Ace II Android Development] zwliew:
probably rom problem/incompatibility with cm ramdisk i guess? not kernel problem

is it same while charging? bln works on wakelocks, if there is no wakelock at the time, it can't blink. it can only blink when there is wakelock on your phone.

try while charging, since charging forces a wakelock on your phone. if it continues blinking while charging, there is nothing wrong with bln.
[Galaxy Ace II Android Development] ace2nutzer:
+1 on stock kernel
[Galaxy Ace II Android Development] S.AMU:
Also WiFi not working