yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] robbieast:
What's suppose to give better battery life, yankactive or interactive?

Sent from my bacONe device
[ONE Original Android Development] xlollomanx:
Yankactive if I'm not wrong is an interactive governor tweaked for battery life, so I think yankactive is better.

Sent from my Oneplus One
[ONE Original Android Development] tsimitsangaz:
In my opinion try with the default AK settings without tweaking anything and you will notice that you get better battery than stock kernel
[ONE Original Android Development] Super_Commando:
Please tell me which is the latest AK kernel that can be flashed on kitkat, I'm running slimkat now.
[ONE Original Android Development] nickporwal:
I have tried both, i got same battery life . Better go for interactive. I am getting 7hrs SOT consistently.
[ONE Original Android Development] fiz:ik:
Kind of impressive :angel:
[ONE Original Android Development] tsimitsangaz:
what settings?
[ONE Original Android Development] bombadier:
ak239 and for my fellow intrepid kitkaters thats the end of the road, I just tried with the updated firmware from yesterday and a kitkat radio and got a bootloop so its been a good run but ak239 seems to be the last stop

How are you finding slimkat ? An improvement on CM 11S ?May try it as I am fed up with CM
[ONE Original Android Development] iker_92:
i'm on cm11 remix with ak 246 and no problems here ;)
[ONE Original Android Development] bombadier:
Wow then you are the only one as anything above 239 bootloops on cm11

tapatyping fae the bacon
[ONE Original Android Development] zaska_:
I mentioned earlier about heating issues in TWRP during backups. I didn't realise recovery uses different kernel (of course...) but after some of ak's last builds heating issues were gone. :confused: Everything works great now and touchscreen is suberb btw! Thanks [MENTION=3685904]ak[/MENTION] ! :highfive:
[ONE Original Android Development] preacher65:
I think there's some confusion - I've been using the Oxygen modem on my device for a while, but the question was about whether the Oxygen modem and the new CM12.1 modem are the same. They display the same baseband version number, but I wasn't certain if it was the same file being flashed, as apparently sometimes different files have the same baseband version number (see note at bottom of OP).

So I extracted the NON-HLOS.bin files from Oxygen and the new CM12.1 nightlies and compared them in Diffmerge, which reports that the files are identical. They also have the same checksums:

Oxygen NON-HLOS.bin
MD5 Checksum: 1A1ECEFFB2C6CC9BDE761B6160B781D6
SHA-1 Checksum: 4B3D04C97940BF44BAAB2B91A78EA151798F9B21
SHA-256 Checksum: 55D4327F18E6CD6FB93C45BAF105348CF60717A566EE02332C038DFA2FBE09F9
SHA-512 Checksum: 645708082DAE9BF143B11422B40B7ECF6D36647E07CC4C6C5D67507FD04245455780D11B25F062E4C700FEC58189AF40621953A6A59D49CCD6E2A0B5A75AA54B

CM12.1 NON-HLOS.bin
MD5 Checksum: 1A1ECEFFB2C6CC9BDE761B6160B781D6
SHA-1 Checksum: 4B3D04C97940BF44BAAB2B91A78EA151798F9B21
SHA-256 Checksum: 55D4327F18E6CD6FB93C45BAF105348CF60717A566EE02332C038DFA2FBE09F9
SHA-512 Checksum: 645708082DAE9BF143B11422B40B7ECF6D36647E07CC4C6C5D67507FD04245455780D11B25F062E4C700FEC58189AF40621953A6A59D49CCD6E2A0B5A75AA54B

That's not surprising, as they both report as DI.3.0.c6-00241 in Settings/About on the phone, but I was curious to see if it was actually the same file. It seems it is.

And this is really off-topic for a kernel thread, so I'll apologise now and stop. :o
[ONE Original Android Development] Super_Commando:
I was on Cos12, had horrible battery life. Now quite good on slimkat around 6-7 hr sot, with some gaming and 3g always on. No difference noticed in terms of smoothness/lag. Phone also heats less. Stock kernel

How did you flash 246 on cm11/kitkat?
[ONE Original Android Development] Kyu Jong:
what's ur profile/settings ?
[ONE Original Android Development] funCrash93:
it's there any reason not to include the installer by default in the kernel along with the UKM.?

like flashing the kernel will be one zip that 1. uninstall_vX 2.AK_kernel 3.UKM

(as 2 and 3 is already implemented, so why not adding 1.? )

A0001?bacon
[ONE Original Android Development] ak:
I don't think this is good because probably you can loose ukm settings .

Do you have try to see if there is diff if you flash uninstaller before?

Sent from my A0001
[ONE Original Android Development] k_flynn:
[MENTION=3685904]ak[/MENTION] have you changed the basic colour configuration in last kernel? Colours on my screen seems dull/faded compared to ak 239
[ONE Original Android Development] MBurns2:
in gamma section you have some profiles to try..
[ONE Original Android Development] k_flynn:
I tried "cool amoled" but green and blue mostly are not the same. I just have to adapt to the new patterns then! :)
[ONE Original Android Development] iker_92:
i only follow this valide guide

http://xdaforums.com/showpost.php?p=58756020&postcount=10504

i used cm11 m11 snapshot instead of calkunun's cm11s and no probl
[ONE Original Android Development] funCrash93:
what do you mean UKM settings? (synapse config.?)

I'm on BlissPop, and my all time update procedure is :

1. Uninstaller

2. BlissROM

3. GApps

4. AKernel

and everything always seems fine, no settings lost or anything like that.

just making sure there are no hiccups on Synapse side applying the old settings to the new UKM and new Kernel.

A0001?bacon
[ONE Original Android Development] bombadier:
That makes no sense how you have it working,as others have reported the same as me ie a bootloop, I have just tried flashing ak246 and as expected a bootloop, I am using the same firmware so no idea how you are the only one to of got it to work :confused:
[ONE Original Android Development] iker_92:
before using this guide i used aux kernel 0.8 exp always with cm11 remix because i thought i couldn't install ak on it..only these steps..

1-flashlast firmware cm 12 avaiable before the lastest of yesterday

2-flash ak kernel

3- reboot bootloader

4- fastboot flash modem cm11s

5- reboot et voilà

:)
[ONE Original Android Development] bombadier:
And that gives bootloops so congratulations on getting it working
[ONE Original Android Development] Crazy-Silver:
Ak can you make a stock profile that we can import when we have problems? It should be very useful and helpful.
[ONE Original Android Development] ak:
If you can make it I can merge into the installer into config dir.

Sent from my A0001
[ONE Original Android Development] Crazy-Silver:
I need it now [emoji22] if I'll be able to return on stock settings I'll make it.
[ONE Original Android Development] kalpik:
Delete /data/UKM from root Explorer, and clear data of synapse. Then reboot, and re-flash kernel. You'll be on stock settings :)

Sent from my Oneplus One
[ONE Original Android Development] androizers:
Hey [MENTION=3685904]ak[/MENTION] , its good that we have lowest frequency as 69Mhz, and its great for idle state. But with this lowest frequency, there comes a demerit that telephony doesn't let the screen wake instantly when we receive a call (there's always a 3-4 seconds delay in waking). So I was wondering, with another cool feature which u introduce in UKM bout the frequency for individual core, do u exactly know, which particular core handle the telephony services, so that we can increase the min frequency for that core and njoy the telephony exactly the way it is meant.. (y) Watchu say?
[ONE Original Android Development] johnb380:
You could try to set the max screen off cores to 2 instead of 1 and see if that helps friend. If not try just Editing core 0 to 300mhz or maybe cores 0 and 1 to a min of 300mhz each... Also you can try to enable wakeup boost it seems to help me with dt2w's responsiveness also!

Good luck friend hopefully one of these will help you!
[ONE Original Android Development] ratty123:
Then u're doing it wrong.

It does work, I've done it 100 times.
[ONE Original Android Development] ak:
you can set 69mhz for cpu0, 300 mhz for cpu1 2 3 ..... you can have idle and boost.
[ONE Original Android Development] Xperia-S-Tony:
kernel v239 works fine on MIUI v6 but only when my opo is charging. I don't know... when i plug out the power cable, my opo get in bootloop.

Which kernel version works on MIUI v6 X_s offcial release? (5.5.15)
[ONE Original Android Development] ak:
What is the base of the ROM?

Sent from my A0001
[ONE Original Android Development] Xperia-S-Tony:
cm11 or cm11s
[ONE Original Android Development] phoenixita:
Then latest AK would not work.It officially support only cm12.1....cm12.0 works too but cm11/s is another story(outdated). There is a workaround to make them work but you can use the search button for this. :)
[ONE Original Android Development] DrNinjaa:
V246 works on ur kitkat ROM....?? Did u test it, because 245 did give me bootloops, so I thought last one working is v239

#HappyFlashing#
[ONE Original Android Development] shaarven71:
Massive battery drain

Hey guys, does anyone experience massive battery drain during standby with the last few latest kernel. I've tried AK 246 with Resurrection Remix and the latest cm12.1 robbie's build and with both of them, I'm losing 10% - 15% in a period of 7 hours of stanby.. I've checked wake locks and nothing showed up.. I've attached an image showing that.. Please help. Thx :cowboy:

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

I'm sorry. I forgot to attach the image and now I just realized, I don't have the permission :confused:.. Sorry
[ONE Original Android Development] Supranoob:
[MENTION=6371518]shaarven71[/MENTION] yeah I been experiencing high idle drain to too, I clean flashed after I noticed the drain and it is still occurring. I remember someone saying it could be related to the new WiFi drivers?
[ONE Original Android Development] :
Have you installed new firmware from 05/15? I got 0.9%/h drain in deep sleep.

After flashing old firmware with xxx230 modem i get 0.2/h again.
[ONE Original Android Development] ek69:
Would u be able to check the rest of the files too? If CM took the oxygen modem then I am wondering if CM also took some of the other files?

Of course if one/some of these files contain boot animations or something like that it'll be a different file, but I wonder if some other files are the same also.

IIRC some people were saying the oxygen modem gave some people better signal strength, and someone just reported having higher idle battery drain with the new CM firmware from may 15 2015... Maybe the oxygen/new CM modem just uses more power for the cell radio (explains the boost in signal and increase in standby battery drain).
[ONE Original Android Development] Supranoob:
[MENTION=785380]ek69[/MENTION] I don't think its the oxygen modem, I been running it for a while now, and it never caused me high idle drain until now
[ONE Original Android Development] HaTrED_:
There are several informations regarding that peculiar drain and they seem to be related with the new touch screen drivers... I've noticed it too and reverted kernel to a previous version and battery drain is what it used to be! At least with my setup this seems to be true and I've seen some folks sharing the same feeling...
[ONE Original Android Development] shaarven71:
Yeah i did.. Reverted back to the old firmware . Thx
[ONE Original Android Development] g.ott:
sorry for being noobish but i simply don`t get it and only ask for a better understanding:

i also watch a higher battery drain in the last couple of days but i did not update the last firmware-update. is it possible that AK had it integrated in his kernel?

if so, i would like to also go back to the old firmware but i also had then to stick to an older version of AK. am i right with this?
[ONE Original Android Development] nikhil18:
Hello ak I have got a solution to this idea why not make extra copies of same governor eg interactive,interactive2 etc in the kernel source then we can tune each core differently
[ONE Original Android Development] ak:
touch firmware is inside, but if you dont post stats, i cant see if its a kernel problem or rom .... also we try to be precise and give detailed information of your settings.
[ONE Original Android Development] ak:
its not simple to do, and this isnt a clean solution. we have to find an alternative inline with kernel coding.

why you dont use conservative for core0 and 1 , and interactive for core2 and 3.
[ONE Original Android Development] ak:
Re-enabling of Ondemand governor is on the way, stay tuned. ;)
[ONE Original Android Development] nikhil18:
But when I was on boeffla kernel on demand governor was giving sod
[ONE Original Android Development] fustyler:
can't connect to camera

I'm running the latest Paranoid ROM 5.1 + AK kernel 3.4.107~ak.246.opo.cm12.1.

When I try to start any camera app, I get the error can't connect to the camera. Rebooting doesn't work either. Any suggestion?
[ONE Original Android Development] wcn:
AK.246 is working fine on KitKat in the below setup:-

Primary:

Euphoria-OS-1.1-bacon-20150503

Flashed CM12.1-15.05.2015 firmware

Flashed v.00230 modem

Flashed AK.246

Secondary:

Mahdi 2.9 Final

Flashed O5Q Modem

Flashed AK.246
[ONE Original Android Development] abhi08638:
Im pretty sure it's not the touchscreen driver causing the drain. I have a 0.3% drain on idle but only when WiFi is off. So it could be related to the WiFi drivers that were updated recently. I'm also on an older firmware with the oxygen modem.
[ONE Original Android Development] ak:
this isnt a kernel problem.
[ONE Original Android Development] ak:
yes i know, but i have upated it, 2 gg without problems.
[ONE Original Android Development] :
Yeah. Now, I don't think it's the new firmware from 05/15. Last hours i had 0.8% with old 230 modem, too. With Wifi on.

When i had 0.2% i wasn't at home with Wifi turned off. So it really could be new Wifi drivers.
[ONE Original Android Development] Spaulding89:
Wow this is nice. Cant await it. [emoji2]

But take all time You need for it.

Sent from my slimmed bacon with Ak Power
[ONE Original Android Development] fustyler:
it appears to be kernel related.

I flashed back to PA_bacon-5.1-20150513.zip, the camera works.

I flashed latest AK kernel again, and camera fails right away.
[ONE Original Android Development] thedao:
What rom are you running? Cause i got a pretty big drain on the Android system which uses the CPU all the time
[ONE Original Android Development] abhi08638:
Slimsaber but the drain is pretty inconsistent because I keep having a connectivity service wakelock
[ONE Original Android Development] Ofthecats:
More governor choices is always good! Feel free to add as many as you want!

Its attachments favorite thing to experiment with.

What's your opinion on alucard governor and hot plug ?
[ONE Original Android Development] ak:
The kernel works perfect with all cm12.1 based rom, so the kernel dont have problems. Dont use it over PA if you have problems.
[ONE Original Android Development] chris264:
Kernel works very good with BlissPop Rom. Many Thanks.

OnePlus One
[ONE Original Android Development] kholdstare21:
I'm on euphoria 15.5.3 latest build with latest firmware and latest AK kernel. Overnight drain was 11% drain which is unusually high for me.

I did get a bump on my WiFi download speed from 2mbits to 4mbits. Seems like WiFi may be the culprit for my device. I think I will stick with this as I'm usually near a charger.
[ONE Original Android Development] aakazh:
+1 happens here too
[ONE Original Android Development] ak:
I know, but you have to analyze on your side and eventually report your stats.

dont post only for post please.
[ONE Original Android Development] aakazh:
[MENTION=3685904]ak[/MENTION] bro

I am on temasek 11.5

Overnight drain is too much

On stock settings just read ahead set to 512 and scheduler to fiops

And se Linux is permissive
[ONE Original Android Development] ak:
wakelock and stats?

ps

the only changes that can be create drain are:

- wifi

- touch drivers

without stats i cant verify what is the problem?

but i cant fix nothing i have to wait CM official patches.
[ONE Original Android Development] abhi08638:
As [MENTION=3685904]ak[/MENTION] has already said, you have to monitor your battery rom wise. I have no such drain so you have to use bbs and wake lock detector to see what the cause of drain is. Posts like those are rarely helpful in diagnosing a problem
[ONE Original Android Development] preacher65:
For those not following many other threads, battery drain might be caused by double tap to wake and the new touch drivers. You could try disabling dt2w and see if that helps, possibly also turn off prevent accidental wakeup and anything else gesture related. I've seen discussion in a few CM12.1 threads, some say it fixes it, a few say it doesn't, so looks like there's no 100% answer yet. I've not noticed any battery drain myself, but I've been at home the last few days so charging often.
[ONE Original Android Development] Rex2688:
no difference after touch firmware update.

My phone feels the same as before after new update, happily never had the touch issues. Waiting for sunlight enhancement bug fix now,even Franco kernel has it sadly.
[ONE Original Android Development] aakazh:
Here ak bro
[ONE Original Android Development] Formhault:
Huh?
[ONE Original Android Development] ak:
yes confirmed, wifi + display, we have to wait CM.
[ONE Original Android Development] Mecca EL:
I know you're busy turning lead into gold, [MENTION=3475639]ak.[/MENTION] Don't forget those of us that love the Swipe 2 Wake feature. :fingers-crossed::fingers-crossed:
[ONE Original Android Development] cerealguy:
Same here on Blisspop
[ONE Original Android Development] ak:
miui v6 is officially out, i think a kernel is necessary for this great rom. :silly:
[ONE Original Android Development] Lookitfast:
Up to what version can I safely run on cm12s..Im running 220 atm but am trying to get synapse to work & was inquiring before I installed ukm seperately beings it is included in newer releases.Thank you..
[ONE Original Android Development] ak:
I cant do nothing, we have to wait CM.
[ONE Original Android Development] aakazh:
Official (*_*)

I found a ported ROM on website

Can u lend me the link to official
[ONE Original Android Development] venky716:
So did a bit of testing, here's the inconclusive results.

Clean flash Euphoria 03 build with no gapps.

Nfc, Bluetooth, ambient, day dream, profiles etc off.

First with Wifi and gestures on.

Then Wifi Off and data on 3g.

Then gestures and dt2w off .

Then all off and on 2g standby.

V245

V246

I think Idle drain has increased but neither Wifi or gestures seem to effect it.

Since I did not really have any touch issues went back to 245 happily.
[ONE Original Android Development] ak:
http://en.miui.com/overview.php

Sent from my A0001
[ONE Original Android Development] OldDroid:
Hi folks,

since a week now i'm working on a little project - for this kernel.

Together with [MENTION=3685904]ak[/MENTION] i discussed a few things, especially features.

Little hint:

Comming next weeks ... :cool:

Oh btw, i need a hand full of testers ... (pm me ;) )
[ONE Original Android Development] johnb380:
To anybody that has battery drain and wants to try, I have flashed https://www.dropbox.com/s/o0dkkml7vw0qysr/OnePlusFirmware-20150505.zip?dl=0 which is the 5.05 fw zip and now I no longer have battery drain.

Just trying to help! For me the newest fw seems to be the problem.

That's a Dropbox link so get it now it'll go dead quick.

Good luck!
[ONE Original Android Development] CounterC:
Is it for OPO or still needs to be ported? I love MIUI, and would love it even more with AK running...

Edit: found it:

http://en.miui.com/download-249.html
[ONE Original Android Development] mrsim:
sorry to ask but this is a HUGE thread...am currently running stock Cm12 5.0.2 one my oneplus...am i ok to flash the latest AK kernel onto this device
[ONE Original Android Development] cerealguy:
Flashed! Thanks for sharing!
[ONE Original Android Development] Lookitfast:
Just flashed v245 without any issues at all.I'm running 12s as well :good:
[ONE Original Android Development] mrsim:
:good:
[ONE Original Android Development] LookedPath:
[MENTION=3685904]ak[/MENTION] I just saw that CM made a ****load of commits and there's another update of the wifi driver and some other wifi related commits. The thing that might be a problem for the ones that had touch problems is that they also reverted the new touch firmware.
[ONE Original Android Development] FullWipe:
Hi all!

I've got strange min freq.....it's always at 1958Mhz and never scale down and if you see screenshot, the values in synapse are all 0....it isn't normal....

My Settings (more significants) are:

Min freq 69Mhz

Max freq 1958Mhz

Interactive

Fiops - 512 Read-Ahead

Intelliplug --> conservative (4)

Cpu Boost disabled

Voltage overall -110 (always used without problem)

I've also tried to change some settings, governor, scheduler etc etc but situation is the same....Min Freq is always 1958Mhz also with stock settings.

I've tried to flash UKM Uninstaller and reflash AK 246 but with no success.

I have massive battery drain but i don't know what to do....never happend so far.

this is my log..... [MENTION=3685904]ak[/MENTION] can you take a look, please?

--> https://userscloud.com/p8lov95x4g7e

Thanks in advance mate! :)

EDIT: I reflashed my rom with wipe system, reflashed gapps and AK 246, cleared Synapse data/cache and deleted ukm folder but problem still remains.

Maybe i found the problem.......

stock gamma profile --> Min Freq is ok

If I change the gamma profile --> Frequency goes crazy

Check if the problem is real or just a coincidence or is due to a problem with my rom (SlimSaber)

Thanks!
[ONE Original Android Development] kalpik:
[MENTION=3685904]ak[/MENTION] headsup. CM going to revert new touch firmware due to battery drain: http://review.cyanogenmod.org/#/c/98677/

Sent from my Oneplus One
[ONE Original Android Development] Ofthecats:
? but it's so nice
[ONE Original Android Development] Striatum_bdr:
Yes but d2tw is unstable and causes battery drain.
[ONE Original Android Development] ak:
All new cm patches are merged .... A lot of work and fixes for doing this ... But Seems very good ... No more wakelocks ...

Sent from my A0001
[ONE Original Android Development] ak:
If you underclock you have to tune also CPU boost ... Have you try to donwclock sync threshold?

Sent from my A0001
[ONE Original Android Development] chikimonke:
Ooooo, and I can read this one too [emoji14]
[ONE Original Android Development] ak:
very happy :)
[ONE Original Android Development] Dima_2005:
So touchscreen fix has been reverted as well in ak248?
[ONE Original Android Development] opee:
Why??
[ONE Original Android Development] Striatum_bdr:
Read.

Because it was reverted in CM.

Because it was buggy with d2tw.
[ONE Original Android Development] ak:
drain +30mv.
[ONE Original Android Development] LexusBrian400:
Hmm.. Device not supported in Synapse. Clean flashed Rom, then ak. No go for me
[ONE Original Android Development] Dima_2005:
Drain > non-working touch.

Though, I understand that cherry-picks start making things complicated.

I'll just wait with flashing anything till a new touchscreen firmware comes out.

Would be cool if you'd have a v248T (with touchscreen cherrypick)
[ONE Original Android Development] capitanouncino:
Same here...with v248 touch is unusable
[ONE Original Android Development] rom08:
Same here. The new driver make my phone usable again. I prefer a little drain other an unusable phone. With the old driver my Nexus 4 fly like a rocket compare to the oneplus one.
[ONE Original Android Development] Zootopia:
Did you guys flashed unninstalv4 before flashing the new 248?

So far so good here, thanks AK!

I'm on latest Bliss with xposed.
[ONE Original Android Development] ak:
have a thousand versions is really heavy to manage in terms of staff time, I prefer to follow the details of CM.

If I see a big interest I might reconsider.
[ONE Original Android Development] Crazy-Silver:
For me the touch is OK but I never had touchscreen issues.
[ONE Original Android Development] rom08:
No problem. Personally I will just stay with v246 wich works perfectly in the meantime.