yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] maxver0:
No, nobody opened a ticket. You've been doing some hard test, does it affect you too? Tell me, which rom are you using? I will flash ak 068 and will see if issue is still there.

---------- Post added at 02:08 PM ---------- Previous post was at 01:27 PM ----------

https://www.dropbox.com/s/wvs6hja49reqrn4/2014-12-26-13-35-19ak68.txt?dl=0
[ONE Original Android Development] prstorero:
I believe he uses tamesake as his daily.
[ONE Original Android Development] maxver0:
Just flashed AK.039 and it works just fine, 2 hours now. Gonna check AK.050 again.

edit: AK.050 issue is there

edit2: It's on ak.039 too ...
[ONE Original Android Development] chachin:
iwonder if we gona reach v1.00 by new years :P
[ONE Original Android Development] schmitzekater:
Had some terrible reboots the last two days with temasek and ak065 with interactive or slim governor.

Ended up clean flashing temasek 3.3.1 without ak but still had reboots with interactive.

Switched to performance governor and haven't had a single reboot today.

Gonna test ak068 tomorrow with performance governor.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] chenrp:
latest kernel has issues with double tap wake up. not waking up every time.
[ONE Original Android Development] altajer67:
[ INSTALL STEP-BY-STEP - ANYKERNEL FORMAT ]

go to recovery

flash your kernel ROM

flash AK kernel

reboot

finish

--------------

what mean by flash your kernel ROM ? my CM V : 44S .. and kernel V : ak.077.opo.cm11

can i flash AK.068.OPO.SKULL.CM12.zip via recovery without any problem

please tell me i am a noob :D
[ONE Original Android Development] cd69:
When you flash your rom you flash the kernel too. If you are on another custom kernel then you need to do this. Otherwise just flash ak from stock.

Hope this helps.

Oneplus Nexus 5
[ONE Original Android Development] altajer67:
so AK.068.OPO.SKULL.CM12.zip can be flash on CM version : 11.0-XNPH44S

i mean that the ak kernal for cm12 and my stock rom cm 11s does it work ?
[ONE Original Android Development] maxver0:
No. CM12 is for lollipop CM12 only
[ONE Original Android Development] dickenam:
Nope. V68 works with 44S.
[ONE Original Android Development] troyolson92:
any of yall want an invite pm me
[ONE Original Android Development] maxver0:
:eek:
[ONE Original Android Development] bigmase521:
Sleep of Death on v68?

I am getting semi-frequent SOD's on v68 running on Blisspop. Device won't wake up and have to hold power to hard reboot. Will try and grab a log next time.
[ONE Original Android Development] Spaulding89:
Totally wrong!!!

CM12 AK Kernel runs on all Roms.

Sent from my lollipopped Bacon with loaded AK Kernel
[ONE Original Android Development] nikeman513:
I think he meant AK Cm12 lol, but you're right and it runs on cm11 too

---------- Post added at 12:56 AM ---------- Previous post was at 12:55 AM ----------

Had same issues on cm12 daily. I just switched kernels until its fixed. Drained my battery too
[ONE Original Android Development] Spaulding89:
I meant the CM12 AK Kernel ;) I edited my post for more details

Sent from my lollipopped Bacon with loaded AK Kernel
[ONE Original Android Development] tracerit:
Same here. Had no issues when on 65 for a few weeks but experienced one SOD a day after 68.
[ONE Original Android Development] Synnexo:
Experienced it last night too.

Running MK44.4 with AK 068, phone went dead, gotta boot into recovery & restart from there.
[ONE Original Android Development] akarol:
Same here. Weird thing is, it's fine for 3 days or so, and then it's constant and sods.
[ONE Original Android Development] chenrp:
also sod and wont double tap wake and from bbs i see that the phone uses lower and maximum freq. no mid freq.
[ONE Original Android Development] osmosizzz:
Just got out of work and came to report. Had constant SOD. had to turn my phone off because it would SOD and then it would run warm. They are frequent now. Pretty much after using the device if I leave it there for 5 minutes, it won't wake up.
[ONE Original Android Development] ek69:
What settings for the kernel?

What ROM?

Any logs?

I don't have any sod problems on latest temasek and AK kernel

Sent From Lollipopified Bacon Goodness!
[ONE Original Android Development] osmosizzz:
Rom : paranoid android

Settings : all stock

Logs : none

The last 5 posts are different people having SOD.
[ONE Original Android Development] akarol:
Changing CPU gov to interactive fixes sods for me. Apparently it switched to performance for some weird reason.
[ONE Original Android Development] venky61:
My OPO display turns warmer (yellowish) when I flash AK kernel with CM11s 44. Tried ak77 and also ak 65 skulled. Happend with both. Its annoying. Is there any solution??
[ONE Original Android Development] fiz:ik:
UKM > Synapse > GAMMA > set to 1
[ONE Original Android Development] venky61:
Sorry.... What is UKM?? Where is that setting ??

Sorry again if its a noob question
[ONE Original Android Development] Criton30:
why is v068 not publicated in the first page?
[ONE Original Android Development] Spaulding89:
Because ak doesn't have the time to update it yet.
[ONE Original Android Development] Svid:
Random reboot. Tried to wake the phone, nothing happened so i had to hard reboot it.
[ONE Original Android Development] Adrian312:
See first post. U can download it from AK page and flash thru recovery.

After that use Synapse and change gamma to 1

Sent from my One
[ONE Original Android Development] ak:
new kernel online

[ CM12 CAF KERNEL - v.070 SKULL ED. ]

A kernel based on CAF CM12 Bacon branch.

CM12: AK.070.OPO.SKULL.CM12 > CM12

[ SMALL CHANGELOG ]

merged default bricked hotplug with neobuddy86 work

re-added msm limiter

fixed all bugs reported by users

ecc ecc
[ONE Original Android Development] ak:
flash the latest.
[ONE Original Android Development] Spaulding89:
Thanks [MENTION=3685904]ak[/MENTION] for the update. Best kernel so far.

Sent from my lollipopped Bacon with loaded AK Kernel
[ONE Original Android Development] ak:
thanks a lot I did everything possible to fix everything! even though you know that Christmas is always Christmas! ;)
[ONE Original Android Development] :
Thanks :thumbup:

Just to be clear. Single core off screen unchecked and CPU max online at any time "1" are new stock settings?

Or are my settings corrupted?
[ONE Original Android Development] Spaulding89:
That's my settings there:

I touched nothing so they are stock.
[ONE Original Android Development] ak:
you can choose with UKM how many cpus when the screen is off.
[ONE Original Android Development] :
There ist something wrong with my system. LS shows ak70. Synapse still shows ak68 with these settings. Although i had single core checked and max cpu 4 before. Try to reinstall ukm and synapse now.
[ONE Original Android Development] Spaulding89:
Go to Tools and then try to restart Synapse and if this not works clear synapse data

Sent from my lollipopped Bacon with loaded AK Kernel
[ONE Original Android Development] Svid:
On 68 when we Un-checked the Single core screen off and moved the bar to minimum 2 cpu cores, phone had BSOD (Black screen of death) and we had to force reboot.

Now i see this Tick option is gone and only the bar that we can configure how many cores are online (Use 2 for the audio glitch issue).

The issue is adressed, right? (no option single core screen of so i assume yes?)
[ONE Original Android Development] ak:
This is ****ing flat

Sent from my A0001
[ONE Original Android Development] ak:
yes ... now you can choose:

- min max cores when the screen is on

- max cores when the screen is off (1 by default)
[ONE Original Android Development] RobbieL811:
[MENTION=3685904]ak[/MENTION] Was there any specific reason that you did this https://github.com/anarkia1976/AK-OnePone/commit/d8ae41a7306e0fc114230991762d083ec8bc7bd4 in regards to the new mpdecision? Now my users are having problems w/ the phone waking up due to time keeping. Are these commits that move cputime64_t to u64 absolutely necessary. Can you explain to me why they are moved? I don't fully understand.
[ONE Original Android Development] Svid:
You just made my day :)

Thanks for all of your hard work even on holidays :)

Cannot donate ATM but i will soon
[ONE Original Android Development] :
Clearing cache and data didn't work out. But after reflashing ukm everything is ok now.
[ONE Original Android Development] Spaulding89:
+1

Sent from my lollipopped Bacon with loaded AK Kernel
[ONE Original Android Development] ak:
The problem is related to the driver itself, unfortunately the old version did not work well when you do not have the default settings, all crashing into kernel panic, too difficult to debug ... so I turned and made a mix between driver to showp1984 and neobuddy89 .... sorry for the inconvenience.
[ONE Original Android Development] RobbieL811:
It is ok. I was just wondering what was happening there? So those commits are absolutely necessary to make msm_mpdecision work properly? Also, I will need all of the timekeeping related commits after those. I am trying to fix this problem here.

http://xdaforums.com/showpost.php?p=57766822&postcount=2597

Edit - Note that it's the second part of that post. Not the first.
[ONE Original Android Development] ak:
logic in the driver was fine for hammerhead but was not suitable to work well with the sources of Oneplus much closer to the CAF than GOOGLE.

I graded the driver with a merge.

the problem is not due directly ktime_get routine but at the same driver hotplug.

To be honest, the code of the bricked kernel was too complex to debug.
[ONE Original Android Development] RobbieL811:
Well, that's b/c a f***ing rocket scientist wrote it. Lol. Not saying that you aren't cut from the same cloth lol. You know what I mean. Ok. So, if I pick the time commits from your repo, it SHOULD fix the errors that I am getting related to timekeeping???
[ONE Original Android Development] ak:
I think the best is rebase all and convert to bricked_hotplug .... timekeeping commits are good ... so i think you can merge it.

ps:

the new branch is:

https://github.com/anarkia1976/AK-OnePone/commits/cm-12.0-skull-evo
[ONE Original Android Development] RobbieL811:
I will pick the timekeeping commits and test them. It is hard for me to just rebase and start from scratch after I merge all of the commits into Slim's git. Doesn't really work that way. I still have the commits up for review on Gerrit. I guess I will leave them that way until we figure out what it will be for final. Sound good?
[ONE Original Android Development] ak:
I didn't realized they were already officially on gerrit. sorry [MENTION=4911350]RobbieL811[/MENTION]. It's crazy to debug where is the problem.

i think you can cherry pick timekeeping commits and merge into the bricked_hotplug msm_mpdecision with their commits.

the best thing is to test everything 7/15 days yet before saying that everything is stable.
[ONE Original Android Development] RobbieL811:
Yeah. I already have them up there. It is easier for me to work w/ the commits on gerrit. I pull all of the open commits w/ a script. I hope you didn't mind. Lol. A little late for that. Lol.

https://gerrit.slimroms.net/#/q/status:open+project:SlimRoms/kernel_oneplus_msm8974,n,z
[ONE Original Android Development] schmitzekater:
Fresh install of temasek 3.4 with ak070. Had a reboot with default settings (guess ondemand_eps is default) .

Now switched to interactive to see if it's good again.
[ONE Original Android Development] xlollomanx:
Try changing your governor....if I don't make a mistake this cause reboots.

Sent from my Oneplus One
[ONE Original Android Development] schmitzekater:
That's why I switched to interactive. The other governor was set after install.

So far, so good. ;)
[ONE Original Android Development] NikoZBK:
AK 070 + Temasek's CM12 running smooth like a baby's bottom
[ONE Original Android Development] CounterC:
WiFi drops resolved?
[ONE Original Android Development] dev0lver:
Flashed latest kernel on cm12 temasek, so far, smooth as fu*k :D

Really enjoying lollipop, flashed it on christmas, couldn't wait for official version from cm for opo
[ONE Original Android Development] swayjd:
very frequent reboots on the 70. Was 100% fine before.
[ONE Original Android Development] ak:
No one for me ... Can you post last kmsg? or you can try to change governor.

Sent from my A0001
[ONE Original Android Development] niko2931:
[MENTION=3685904]ak[/MENTION] I hope It's okay for me to ask you this!

But what kind of tweaking and other stuff, have you done to your rom settings etc.

ps. you kernel settings are the same as the default that comes with the ak kernel right?
[ONE Original Android Development] primo14z:
nope still random reboots, i have changed the governor ...

https://drive.google.com/file/d/0B-4tHFb3lo9NOV9MQlBFeFY4RVk/view?usp=sharing

last ksmg
[ONE Original Android Development] ak:
I don't touch nothing I'm using stock settings ...

Its very strange ... I can use on demand without problems while other users no ...

Sent from my A0001
[ONE Original Android Development] NikoZBK:
I've never had WiFi drops or reboots with temasek and AK, maybe I'm lucky.

Edit: just wanted to add that I always run stock settings, apart from lowering min freq. to 268 mhz
[ONE Original Android Development] niko2931:
I haven't had any problems yet.. Except from one single reboot, but i was installing BetterBatteryStats and was in the app and installing it as a system app, when my phone rebooted. I will test and see if anymore reboots occur!

And i will keep the kernel settings stock except from gamma=1 ;)
[ONE Original Android Development] Criton30:
I use this synapse profil (CM11xCM12's UKM Configuration LINK: http://xdaforums.com/showpost.php?p=56974252&postcount=363) with no issue on v0.70. I have changed CPU Governor: from slim to interactive. CPU Boost is also enabled.
[ONE Original Android Development] troyolson92:
i had major app force closes after install ... installed again wiped caches before and after, also installed ukm again. reinstalled all apps that were fc now just titanium backup fcs in is own. no reboot but a few lockups thats clear up after 20 secs...... running stock settings no changes....

---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------

I'm on temasks cm11 rom.
[ONE Original Android Development] Spaulding89:
Just for info: I can use ondemand_eps without reboots or freezes.
[ONE Original Android Development] ak:
Your reboot are related to thermal ...

Sent from my A0001
[ONE Original Android Development] ak:
No .... You have to use interactive.

Sent from my A0001
[ONE Original Android Development] ak:
This isn't related to kernel.

Sent from my A0001
[ONE Original Android Development] Criton30:
[MENTION=3685904]ak[/MENTION] : what do you mean, this profile is good with Governor : interactive? I am on stock 44S
[ONE Original Android Development] Spaulding89:
Why? Now I'm confused.
[ONE Original Android Development] RobbieL811:
[MENTION=3685904]ak[/MENTION] I switched over to the new branch for my SM CM builds and I just flashed the first build. I am getting constant reboots every time the phone goes to sleep. Here are 2 kmsg that I pulled. Not sure what's going on. And no, I'm not using ondemand.

kmsg 1 - https://drive.google.com/file/d/0B_TAnU7CyM8ubEZJU0NJbzl2b1k/view?usp=sharing

kmsg 2 - https://drive.google.com/file/d/0B_TAnU7CyM8uUk1JUldLc2psZ0E/view?usp=sharing
[ONE Original Android Development] ak:
These errrors are related to soc sound drivers:

[ 3.609488] ------------[ cut here ]------------
[ 3.609534] WARNING: at ../../../../../../kernel/oneplus/AK-OnePone/arch/arm/mach-msm/clock.c:367 clk_enable+0x168/0x174()
[ 3.609598] mdss_ahb_clk: Don't call enable on unprepared clocks
[COLOR=Red][B][ 3.609607] platform fe02c000.sound: Driver msm8974-asoc-taiko requests probe deferral[/B][/COLOR]
[ 3.609701] Modules linked in:
[ 3.609788] [<c0114524>] (unwind_backtrace) from [<c01be364>] (warn_slowpath_fmt+0x64/0xd8)
[ 3.609859] [<c01be364>] (warn_slowpath_fmt) from [<c01262cc>] (clk_enable+0x168/0x174)
[ 3.609931] [<c01262cc>] (clk_enable) from [<c019293c>] (vco_unprepare+0xbc/0x150)
[ 3.610003] [<c019293c>] (vco_unprepare) from [<c01267c0>] (clk_unprepare+0x84/0x1d0)
[ 3.610043] [<c01267c0>] (clk_unprepare) from [<c012688c>] (clk_unprepare+0x150/0x1d0)
[ 3.610108] ---[ end trace 545d7df185687bc5 ]---
[ 3.610148] ------------[ cut here ]------------
[ 3.610216] WARNING: at ../../../../../../kernel/oneplus/AK-OnePone/arch/arm/mach-msm/clock.c:410 clk_disable+0x150/0x154()
[ 3.610282] mdss_ahb_clk: Never called prepare or calling disable after unprepare
[ 3.610318] Modules linked in:
[ 3.610422] [<c0114524>] (unwind_backtrace) from [<c01be364>] (warn_slowpath_fmt+0x64/0xd8)
[ 3.610463] [<c01be364>] (warn_slowpath_fmt) from [<c0126160>] (clk_disable+0x150/0x154)
[ 3.610532] [<c0126160>] (clk_disable) from [<c0192984>] (vco_unprepare+0x104/0x150)
[ 3.610602] [<c0192984>] (vco_unprepare) from [<c01267c0>] (clk_unprepare+0x84/0x1d0)
[ 3.610671] [<c01267c0>] (clk_unprepare) from [<c012688c>] (clk_unprepare+0x150/0x1d0)
[ 3.610708] ---[ end trace 545d7df185687bc6 ]---

I dont have change nothing related to this code.
[ONE Original Android Development] RobbieL811:
Me either lol. I am pulling straight from your repo. I'm not adding or removing anything kernel wise. And everything else is straight CM code.
[ONE Original Android Development] ak:
Test kernel online:

- removed completely cpu-boost from kernel and left ondemand_eps by default

Can anyone with reboots test this version please?

View attachment AK.070.OPO.SKULL.CM12.TEST.zip

thanks a lot

ak
[ONE Original Android Development] Criton30:
why is cpu boost removed?
[ONE Original Android Development] ak:
"test kernel"

i want to see if there is conflict with ondemand.
[ONE Original Android Development] Criton30:
with the profile in #8689 I have no issue on stock 44S with the v0.70 kernel, and what do you mean about this profile? I have changed cpu gov to interactive and cpu boost is enabled.
[ONE Original Android Development] chachin:
Flashed v070+blisspop+pagappsmini-2014/25/12 and synapse and reboot.. all way clean install.. dont have logcats or anything but thanks for this test kernel.. if i see the reboot happening again i will give logcats thanks [MENTION=3685904]ak[/MENTION] and thanks [MENTION=5168118]Vortex1969[/MENTION] for your awesome job
[ONE Original Android Development] ak:
[MENTION=4911350]RobbieL811[/MENTION]

you have a PM.
[ONE Original Android Development] smint86:
Had a random reboot as well.

https://www.dropbox.com/s/8e99ryptp9cfov4/last_kmsg-2014-12-28.00.45.30.txt?dl=0

(stock v70, maybe due to disabled fsync, trying with enabled now)
[ONE Original Android Development] RobbieL811:
Replied.

Sent from my 1+1
[ONE Original Android Development] swayjd:
Still rebooting!
[ONE Original Android Development] chikimonke:
Ooo, look at the cool kids having a private convo. [emoji2]
[ONE Original Android Development] ak:
if you want ... you can partecipate to testing ... feel free to speak with robbiel811.
[ONE Original Android Development] chikimonke:
I'm just giving you guys a hard time [emoji4] I test for [MENTION=4911350]RobbieL811[/MENTION] quite a bit, I'm sure if there's something worth testing he'll send it over.

---------- Post added at 04:23 PM ---------- Previous post was at 04:01 PM ----------

Alright, so [MENTION=4911350]RobbieL811[/MENTION] 's latest build with [MENTION=3685904]ak[/MENTION] v070 is running really well. Super smooth. I've got CPU boost and ondemand_eps going as well. So long as it stays stable, this is great combo.
[ONE Original Android Development] chachin:
using v070 intellimm no reboots wifi is fine and its really smooth thanks [MENTION=3685904]ak[/MENTION] :D
[ONE Original Android Development] RobbieL811:
Which one do you speak of? Slim build?

[MENTION=3475639]ak.[/MENTION] Ok. I just got back from getting/eating dinner. The source that you sent me in the PM is straight up CM kernel base w/ all of your msm_mpdecision commits added correct?

Edit - Along w/ a few other little things..
[ONE Original Android Development] adinkwok:
[MENTION=3685904]ak[/MENTION] who's/where are you porting msm_mpdecision from?
[ONE Original Android Development] chikimonke:
Yup, your latest SlimLP from today.
[ONE Original Android Development] gianton:
Bricked kernel by [MENTION=4195844]show-p1984[/MENTION]
[ONE Original Android Development] disellusional:
dirty flash temasek 3.4 and ak 70 bootloop reverted back to 68

just fyi haven't read previous posts yet
[ONE Original Android Development] 530farm:
Does anyone have a description of ondemand_eps? Can't find anything on it via Google
[ONE Original Android Development] kishoredroid:
Which version should I be using over CM11 M9? I can see downloads ranging for 11, 11s and 12. I have downloaded AK.045.OPO.CM11.zip. Is this the one I should use?
[ONE Original Android Development] indian84:
You need to read..

CM12 kernel works on CM11 & 11S...
[ONE Original Android Development] kishoredroid:
My bad... Thanks Buddy!
[ONE Original Android Development] schmitzekater:
@ak

Just tested your 070test.

After first boot I cleared data from synapse and enabled ondemand_eps.

As the display switched off, I couldn't wake up the device again and had to force a reboot.

After reboot I checked settings again. 3 minutes later again reboot, I attached logcat and last_kmsg.

Going back to 070 and interactive. :p
[ONE Original Android Development] RobbieL811:
[MENTION=3685904]ak[/MENTION] You awake yet bud? is the msm_mpdecision branch the commits that are needed for new mpdecsion?
[ONE Original Android Development] Svid:
Another random reboot, interactive govenor using latest temasek cm12 unofficial build.
[ONE Original Android Development] gianton:
So far after about 12 hours v0.70 has been rock stable for me, with ondemand_eps or smartmax governors rest default settings. All videos including FB, Youtube, IMDB etc are playing fine on Temasek v3.4. Only minor issue is the sound settings not sticking.
[ONE Original Android Development] efattal:
Same here with interactive_pro. Logs : https://drive.google.com/folder/d/0B8g71puoe1DeNGRadGt6NDZFV0E/edit

Thanks [MENTION=3685904]ak[/MENTION] for looking into this.
[ONE Original Android Development] thejaimes111:
Which version of cm12 are you guys using with this kernel? Or which one is the best?

Regards!
[ONE Original Android Development] Natedog1:
Working great with http://xdaforums.com/showthread.php?t=2858033
[ONE Original Android Development] Texan1:
[MENTION=3685904]ak[/MENTION] Hi mate, any chance you can look at reverting partial-update feature as per below in your kernel please which completely fixed graphical glitches for me. Thanks...
[ONE Original Android Development] dev0lver:
using it with temasek cm12, so far all working really good
[ONE Original Android Development] Deadpool253:
[MENTION=3685904]ak[/MENTION] I know you have a dedicated section for kernel configurations and profiles but I didn't see anything with your recommended settings for anything. Maybe I missed something? Could you maybe recommend a basic setup for your CM12 kernel? That would be awesome and if I missed it, I'm sorry in advance for the clutter.
[ONE Original Android Development] dickenam:
I suspect default is the recommended, basic setup.
[ONE Original Android Development] mikelebz:
I am on SlimLP...version 68 is rock solid for me. I haven't heard it mentioned yet in this thread, but the reboots on v70 occurred for me upon recieving a message, either via hangouts (or sms) or facebook. Hope that helps. I tried several different governors.
[ONE Original Android Development] Natedog1:
I started getting reboots on v70 too. While playing games and when getting hangout messages
[ONE Original Android Development] ak:
I'm working on hotplugging problems with support of @RobbieL811.

I can only do my congratulations to these two developers:

https://github.com/anarkia1976/AK-O...8392ac1532198431f9e134f#commitcomment-9102496 [MENTION=3795148]neobuddy89[/MENTION] [MENTION=2376110]dorimanx[/MENTION]

https://github.com/dorimanx