yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] stab244:
Power consumed by the CPU is a product of the frequency and voltage. That's just how the physics is. If you're using a higher frequency, you'll consume more power even at the same voltage. Of course there's the whole issue of the CPU needing to run longer in some cases but at idle if you can get the frequency lower, you'll consume less power.

Sent from my bacon
[ONE Original Android Development] JaylanPHNX:
Alright, [MENTION=3685904]ak[/MENTION] and others, I after flashing 140 and testing call quality, I flashed back to 205 and tested again. This time, everything sounded fine. I have no idea what's different. One thing I've learned over the years is that every flash is different. Reflash the same setup three times, each time will have some different quirk than the other two times. Carry on.

From my SlimTab Pro 8.4
[ONE Original Android Development] Ofthecats:
Voltage is electric potential, not current (amps). Higher frequency requires higher current because more work is being done.

I'm not sure how correct I am. I thought if something needs more work done it needs more current but also more potential. I guess using the water analogy for electricity explains how you can get higher flow (current) with same pressure (potential) in a faucet.

Sorry for ot lol I can't resist scientific discussion. Its why I'm a tinkerer in the first place :o
[ONE Original Android Development] kd8bny:
+1

This is a good analogy and you are correct.

Source: I'm an electrical engineer
[ONE Original Android Development] ak:
Can you explain what is the problem?

i can see themald logs:

<3>[11809.017538] CPU0 hotplug is not supported

<4>[11809.017592] _cpu_down: attempt to take down CPU 0 failed

<6>[11809.017721] msm_thermal:store_cc_enabled Core control enabled

<6>[11811.912422] msm_thermal:store_cc_enabled Core control disabled

<6>[11811.918211] msm_thermal:store_cc_enabled Core control enabled

<6>[11811.918800] msm_thermal:store_cc_enabled Core control disabled

<3>[11811.919643] CPU0 hotplug is not supported

<4>[11811.919856] _cpu_down: attempt to take down CPU 0 failed

<6>[11811.920351] msm_thermal:store_cc_enabled Core control enabled
[ONE Original Android Development] vagelis74:
Great kernel [MENTION=3475639]ak.[/MENTION]
[ONE Original Android Development] chenrp:
Watt = i*a, but we need whatt per hour... Meaning, lower frequency will cause the cpu to work at less current but significant more time. We need a formula in order to calculate if we are gaining anything here...
[ONE Original Android Development] poondog:
Hi guys

Dynamic power consumed by the cpu is approximated by:

P = C * V^2 * f

where C is capacitance which is constant, so basically

P = V^2 * f

so where voltage is squared, lowering of voltage can lower power and heat a lot. However, remember CPU is not the only place the heat and power goes, so in the end the battery saved by voltage drop/freq drop is pretty negligible

ps I didn't make this up :)

http://en.wikipedia.org/wiki/CPU_power_dissipation
[ONE Original Android Development] yarpiin:
Thanx for that im just courious on every cm12 nightly i have date problem on 204 kernel , its sets up to proper after synapse boot completed message. With 204 kernel boot take much longer than in stable 140. There is no problem with date on 140 while same rom with 204 gives bad date :/ what is a reason of such long boot on 204 kernel ?
[ONE Original Android Development] chenrp:
It is still not straight forward. In low frequency the cpu will make the same task longer. Just like driving slowly in a car but for a longer time...

It depends on the ideal cpu time, and waking up time and much more.

Long story short, i think that there is no point going lower than 300mhz frequency. It will do more harm than good to the battery life.

Quoting :

The Cyanogen team studied this, and determined that any improvements were placebo only. Under-clocking makes the phone use less power per second, but then the processor has to run longer to do whatever it was doing.

permalink

[–][deleted] 6 points 2 years ago

That's where CPU Governors tend to have the most effect.

With an "On Demand" governor (which is default), it works in much the way you explained, but a power saver governor will slow the voltage more abruptly when it's no longer needed (although it scales up slowly when needed) and the performance governor will keep the voltage up higher than needed as it scales down slowly when there is no longer any demand.
[ONE Original Android Development] aakazh:
Hello guys

M new to this community

Just flashed ak kernel v204 on temaseks unofficial built

But I wasn't able to find all the Governor and io schedulers listed in op

Does experimental builts don't include them?
[ONE Original Android Development] poondog:
This is the race to idle theory. It depends what the task is. The cpu governor will select the best freq for the tast anyway (in theory)

If you're on a highway thats limit is 100, you car is perfectly capable of going 80, even 60. But you, (the governor) will choose a speed (freq) thats probably going to be anywhere between 90 and 110

imo you can have that speed able to be selected.. when you're just staring at some web page, you want the CPUs online to be at the min freq (69MHz or whatever) and this will be ramped up when you need it. The problem you speak of about being too low and having to remain at the freq longer will happen when you have limited the CPU freq (esp with screen off freq being low)

BUT

qcom have set the min for a reason and I always trust them for my kernels.. its been tried and tested along with the voltages for stability in all conditions

edit: as with your edit, imo the small power savings available with using loewr freqs are far outweighed by the stability issues that may come.. which is why qcom set the min freq at this. Another thing, the S810 in the HTC M9 has 2 different clusters

Cluster1 --> a53--> 300MHz - 1.5GHz

Cluster2 --> a57--> 633MHz - 2Ghz
[ONE Original Android Development] gargeya_369:
You are right indeed...

And you can try v.205 ..

Here is the link...

http://xdaforums.com/showthread.php?p=60009520
[ONE Original Android Development] HamsterHam:
I was on a call for approx 15 mins and my phone randomly rebooted.

MP-Decision( 1565): Error locking minimum cores
[ONE Original Android Development] fireforhire:
+1 I reported the same
[ONE Original Android Development] ak:
Please post settings. I don't have problems. Mp.Dec is disabled at boot, seems your phone rebooot because you have reach thermal limit.

Sent from my A0001
[ONE Original Android Development] TheWilkieWay:
I had a random reboot last night on v205 and I think my last_kmsg caught the error at the very end. It mentions there being an internal error and then other things, but still says 'no errors detected' which seems odd. Anyway, here it is:

https://docs.google.com/file/d/0B8-DeeLz0wbGdnlfSXREM2ItUXM/edit?usp=docslist_api
[ONE Original Android Development] ak:
Thanks a lot this is the right mod of post logs. The reboot is related to row scheduler .... It will be fixed into new release.

Sent from my A0001
[ONE Original Android Development] TheKnux:
[MENTION=3685904]ak[/MENTION] would it be too much to ask if you could update 140 some more whilst doing your own thing with 205? Some people (like myslef) love changes that made 140 what it is today, and some people like what you're doing with 205 to make it what it's going to be.
[ONE Original Android Development] ak:
v205 will be the new 140 ... You have to wait for now ... Sorry. I can merge for now only the new patches from cm12.1 if you want .... Let me know .... [emoji4]

Sent from my A0001
[ONE Original Android Development] TheKnux:
Well I'm still on CM12 but if it helps with things with CM12 as well then that's what I meant. I wasn't saying bust your hump and add a bunch of changes since that's what 205 is about, I just meant merging fixes, patches, etc. I don't really know much about this stuff and that was the best way to word it without sounding like an idiot. ?
[ONE Original Android Development] ak:
No problem so it will be merged ...

Sent from my A0001
[ONE Original Android Development] TheKnux:
If it's too much to ask or too much work don't worry about it. Just thought I'd ask.
[ONE Original Android Development] TheWilkieWay:
Cheers! [emoji106]

OT but I have an invite for a bamboo styleswap cover if anyone wants one, just pm me
[ONE Original Android Development] AhmedFaiz:
Flying on the latest test build here for a day on the slimsaber all smoother than stock experience.
[ONE Original Android Development] liver20:
Excuse me, but with ak e204 not see custom i/o scheduler and governor

not smartmax, zzmove, ........ not fiops, .....
[ONE Original Android Development] indian84:
Not implemented yet. A little bit of reading would have helped..
[ONE Original Android Development] solar666:
@ak, v205 is a masterpiece of work. I already thought that v140 couldn't be better but you found the room to improve :)
[ONE Original Android Development] Jole7:
[MENTION=3685904]ak[/MENTION] I have 1% battery drain over 8-9 hours on v140 great work man!!!! Didn't try v205 coz i 'm on F2FS.
[ONE Original Android Development] TheKnux:
[MENTION=3685904]ak[/MENTION] also if you do merge the patches with 140, could you possibly add your sweet ak/skull kernel splash logo?
[ONE Original Android Development] nickporwal:
Battery life is superb on v204. All stock except the max frequency capped at 1.9ghz. Also earlier i had wifi always showing as "ON" in battery stats even if its OFF. It seems to be fixed with new kernel.
[ONE Original Android Development] NickosD:
So... You quoted the whole post just to thank him while there is a button for this job?

Sent from my bacon!!!!!
[ONE Original Android Development] TheKnux:
[MENTION=2556801]nickporwal[/MENTION] what theme are you using?
[ONE Original Android Development] yesh8352:
Which rom your using? Can you give me the link?
[ONE Original Android Development] ak:
selinux is the problem of net time:

<4>[ 620.415512] type=1400 audit(1428764029.080:225): avc: denied { read write } for pid=1608 comm="NetworkTimeUpda" name="rtc0" dev="tmpfs" ino=9226 scontext=u:r:system_server:s0 tcontext=u:object_r:rtc_device:s0 tclass=chr_file permissive=0
[ONE Original Android Development] Technowhiteboi:
I have a question for you, if i update through OTA, do i still need to flash the radio? Wouldnt the radio and everything come with the OTA?
[ONE Original Android Development] gyakusetsu1215:
Yes, radio/firmware is uprated with OTA
[ONE Original Android Development] ChrisAr:
So, if we disable it (or change it to permissive ) will that fix the time bug?

Edit:

Well, it does not... :P
[ONE Original Android Development] nickporwal:
Its the coalfield theme "Coalfield - CM12 Theme" - https://play.google.com/store/apps/details?id=com.kohlewrrk.coalfield"
[ONE Original Android Development] Technowhiteboi:
So I can just flash Ak' Kernel? or do i need to do one of these steps mentioned here http://xdaforums.com/showpost.php?p=58756020&postcount=10504
[ONE Original Android Development] nickporwal:
I am using temasek v9.5 build. Its based on 5.1.

http://xdaforums.com/oneplus-one/development/rom-cm11-temasek-build-t2870743
[ONE Original Android Development] slave2007:
Hello, I use the same Phone and Rom, but I get FC on Synapse, it works only by the first open after installation. [emoji33]

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] ak:
I have the same problem ... But I don't know why.

Sent from my A0001
[ONE Original Android Development] kantjer:
LOL, I was baffled why today's SlimSaber build with AK baked in felt much snappier than yesterdays build until I looked at the source code and found smartmax is added back and was set as default :good:

Now I can use my favourite smartmax/fiops combo again.
[ONE Original Android Development] Genericxx:
Gief! [emoji4]
[ONE Original Android Development] sam razzy:
Ak I just want to let you know that the date and time problem comes only due to Oxygen Modem. I had no such problem but few minutes back I flashed Oxygen Modem and I had this same problem which all had reported here..
[ONE Original Android Development] nickporwal:
I dnt have any fc. For me everything is fine
[ONE Original Android Development] dado82rm:
ak.204cm12.1 ho installato questo kernel sembra tutto apposto tranne il fatto che si setta la data 28 febraio 1970 e esce errore google services e on funziona piu il play store
[ONE Original Android Development] CounterC:
I dont have Oxygen Modem, still I have this date problem....
[ONE Original Android Development] Eru Ilúvatar:
English, mate...

Try to install the newest experimental version: AK.205.

By the way, turning on the WiFi fixed the date for me...

Otherwise you can use the stable version 140.
[ONE Original Android Development] dado82rm:
sorry i did't realized that i was writing in italian, any way with the 140 stable everything is working great it only appens with the experimental 204 havent tried yet the exp 205 il give a try now

Thanks
[ONE Original Android Development] Eru Ilúvatar:
Figurati, you're welcome :p
[ONE Original Android Development] dado82rm:
any way 205experimental did not fix the problem
[ONE Original Android Development] :
Wrong date only happens on mobile data for me. On Wifi i don't have this problem.
[ONE Original Android Development] sam razzy:
Are you sure ? Bcoz this problem persisted when I flashed modem. And I'm running 5.0.2 euphoria.
[ONE Original Android Development] CounterC:
Very sure mate. Flashed ak and clock was wrong at boot. Then connected to the Internet and set automatic clock. Time was corrected...
[ONE Original Android Development] nuwan32:
hmm i think the time problem is probably a rom issue. i was on temasek 9.5 and ak 205 earlier and was getting it after every reboot. now i upgraded to 9.6 and same ak 205 kernel and it doesnt happen anymore.
[ONE Original Android Development] magnamentis:
ok :)

so you think it's an app problem, makes sense, will do :)
[ONE Original Android Development] micr0g:
Hello, is it possible to make this kernel react like stock mpdecision of Nexus 5?

I mean 2 cores online (0,1) , touchboost on 1256Hz etc.

Because i believe nothing compare on smoothness like stock kernel of N5.

Or maybe someone has some better settings to share with me?

Thanks in advance
[ONE Original Android Development] AhmedFaiz:
Running smooth on 32 beta 10. Did try beta 12 but felt much better with beta 10 mostly on scrolling side and overall performance.

Oneplus one/PA 4.5 beta 3/AK
[ONE Original Android Development] RobbieL811:
[MENTION=3475639]ak.[/MENTION] What did you do to figure out building with the 4.9 toolchains? Did you just change the optimization level like some of the other users were talking about?

Sent from my 1+1
[ONE Original Android Development] ak:
Yes but I have re-switched to 474 and -O3 ... More fast and stable.

ak@a0001
[ONE Original Android Development] Vortex1969:
Does that mean new build coming. I only ask because I was going to go back to 10.

Thanks
[ONE Original Android Development] ak:
Yes tonight or tomorrow.

Problems with gcc4.9.1?

ak@a0001
[ONE Original Android Development] latenightchameleon:
Anyone else having issues with Synapse not re-applying settings after a reboot or two?

When I try to manually apply, there's two icons on top when I enter the app - checkmark and an X, both reset my settings.

Switched to trickster mod for now.
[ONE Original Android Development] ak:
Yes .. Related to faux sound a fixed ver of UKM is coming.

ak@a0001
[ONE Original Android Development] Vortex1969:
No I misunderstood a post. No it's running fine for me.
[ONE Original Android Development] latenightchameleon:
Thank you very much, getting amazing performance and battery life out of OPO thanks to you and crDroid:good:
[ONE Original Android Development] ak:
pre-release

enjoy with this v.033 pre-release + beta UKM v.3.3b6 :D

View attachment UKM_v3.3b6.zip

View attachment ak.033.opo.cm11.zip

View attachment ak.033.opo.cm11s.zip
[ONE Original Android Development] nazfalas:
Amazing :D trying now
[ONE Original Android Development] ak:
changelog here for now:

https://github.com/anarkia1976/AK-OnePone/commits/ak-11.0-stable
[ONE Original Android Development] mittimus:
Will try it tomorrow :D

OT: Is the entire Kernel wrote in C language? Just curiosity:good:
[ONE Original Android Development] ak:
http://en.m.wikipedia.org/wiki/Linux_kernel

C + assembly

ak@a0001
[ONE Original Android Development] chachin:
Is it ok if I have synapse and trickster installed at same time? or is it recommended to not have both installed and one or other?
[ONE Original Android Development] Vortex1969:
I don't know what you changes or how you do it but 33 is fast.[emoji15][emoji12]
[ONE Original Android Development] teh roxxorz:
You can have both installed at the same time. You can use one, the other, or both to tweak it. But synapse is only really useful if you flash the ukm zip.
[ONE Original Android Development] shaker2k:
Does anyone use FKU along with synapse? I want to use it for Pam(per app modes). If so, which one takes precedence?
[ONE Original Android Development] f41lbl0g:
Ak kernel running smooth with v205 undervolt as well as 69mHz min freq on Temasek 9.5. Having no issues (no time/date issues). Going to update temasek and see if anything changes.
[ONE Original Android Development] ak:
A new kernel is ready but i need some testing ... too things to check ! stay tuned ...

alarm is fixed ,,, i have reverted last cm12.1 changes related to this driver.
[ONE Original Android Development] cerealguy:
I'm here m8! :D
[ONE Original Android Development] dickenam:
I still love danger!

Sent from my A0001
[ONE Original Android Development] Eru Ilúvatar:
We are brave users :p
[ONE Original Android Development] Spaulding89:
I'm awake and brave so give it to us ;)

---------- Post added at 01:35 AM ---------- Previous post was at 01:34 AM ----------

@lookedpath [emoji38] 2 guys 1 thought
[ONE Original Android Development] JaylanPHNX:
Except the kernel is for the OPO, not the M8. [emoji13]

It's baconnn!
[ONE Original Android Development] LookedPath:
Ahahahahah when this kind of thing happens it always amaze me.

BTW here in Italy is really late (1AM), so I don't think that ak is going to release the new version right now. I think that you guys need to wait. ?
[ONE Original Android Development] CounterC:
True but I heard he doesn't sleep...
[ONE Original Android Development] LookedPath:
[MENTION=3685904]ak[/MENTION] your are like the Stig, there are lots of myths about him.
[ONE Original Android Development] Spaulding89:
Is [MENTION=3685904]ak[/MENTION] a human? I think he is a cyborg and don't sleep at any time and his only mission is to build the perfect kernel and listen to great metal music. [emoji1]
[ONE Original Android Development] cerealguy:
LOL!
[ONE Original Android Development] NickosD:
M8 = M(eight) = Mate.

Sent from my bacon!!!!!
[ONE Original Android Development] nuwan32:
merged with this to remove the wakelock?

http://review.cyanogenmod.org/#/c/94235/
[ONE Original Android Development] IllUMINATUz:
I got a few questions..

Can we get the CPU lower than 146 MHz? and achieve lower voltage? just curious.. what will happen if we do? and if we cannot do it, any specific cause/reason why we cannot go below that?

This has been bugging me since I've moved from Tegra (yep, Tegra can go till 51MHz..) just curious whether we can get lower than that, coz when listening to music and light tasks, they don't take much resources right?
[ONE Original Android Development] f41lbl0g:
I'd be willing to test if u still need help.
[ONE Original Android Development] nuwan32:
ak 205 has 69 mhz as lowest step. it works fine.

also, would love to try the new update, this constant wakelock is really bugging me :/
[ONE Original Android Development] scott62185:
I want to use ak kernel so bad but every time I do I have an issue where double tap to wake becomes less responsive. Does anyone know if I need to change some setting or something?
[ONE Original Android Development] kalpik:
Great work my friend! That alarm and the time reset were related. So it was a kernel issue after all :)

Sent from my A0001
[ONE Original Android Development] sam razzy:
In my better battery stat I see "timerfd" kernel wake lock... What is that ? Do someone knows ?
[ONE Original Android Development] KewalG:
the latest stable kernel to work with slimsaber build is 140 or 204? as it says cm 12.1 will they work with slimsaber?
[ONE Original Android Development] sien1996:
Anyone facing SOD's with latest v205 and slimsaber after screen off? Only when turning msm limiter on. Or else 69Mhz step is awesome :D
[ONE Original Android Development] kantjer:
Happened to me yesterday, set min frequency to 146MHz now. No issues yet
[ONE Original Android Development] bkayy:
Does any one know how to stop calendar storage wakelock this seems to have started when I flashed ak204 but I don't think it's the kernel but does so thanks
[ONE Original Android Development] MrWGT:
A few posts ago ak206 was announced by ak with fix. Will be released after further testing
[ONE Original Android Development] ak:
[MENTION=3306843]kantjer[/MENTION]

Do you have tested the new v210 compiled inline?

I have made some testing and it seem stable.

Sent from my A0001
[ONE Original Android Development] Renosh:
[MENTION=3685904]ak[/MENTION] will v206 have smartmax governor?
[ONE Original Android Development] ak:
Yes ... I have added into also slim gestures and other things.

Sent from my A0001
[ONE Original Android Development] dragoi90:
[MENTION=3685904]ak[/MENTION] We are waiting for publishing! [emoji14]
[ONE Original Android Development] kantjer:
No not yet, only noticed v210 this morning.

My manifest points to the ak-12.1-official branch, so yesterdays build was done with v206

FYI the SOD I experienced yesterday was when still running the build with v205.
[ONE Original Android Development] Noname2012:
Delete
[ONE Original Android Development] ak:
... i'm thinking to release the new kernel tonight ..... :highfive:
[ONE Original Android Development] kouss77550:
I can't wait ! ?
[ONE Original Android Development] pSyCh¤_O_O:
http://cdn.specktra.net/9/9f/350x700px-LL-9f8884c6_f5-jackhammer.gif
[ONE Original Android Development] nickporwal:
I have one question. The wall charger which comes with opo says the output is 2A. But when i charge through it, i can see in Ampere and gsam app that my phone is getting charged @ 1A. Is this fine or there is some setting to make it charge faster?
[ONE Original Android Development] MBurns2:
I use opo charging current.try to use it and verify if you really have some problem or the problem is related to gsam app