yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] akarol:
Got an SD with latest as well. No logs unfortunately. Also noticed that BT stutters here and there. Synapse was also not opening. Reverted to 140 and all is gravy.
[ONE Original Android Development] Zootopia:
SD here also with 203. Only noticed this morning when I got up.

Anyway, this looks very promising...
[ONE Original Android Development] 1Nexus:
I'm not getting any SODs on SlimSaber either. Every other 5.0.2/5.1 rom I had gotten them but I didn't take any logs before I swapped roms!
[ONE Original Android Development] laulau42400:
Hello, with version 203, the screen remains black after a few minutes without use. There's just ? home buttons, menu and back that light?

Tapaltak and Lollipop ? One+
[ONE Original Android Development] AJ RIMMER!:
I had SoD with SlimLP on 202. I went back to 140, as it is my daily driver
[ONE Original Android Development] ak:
Sod problems are know guys .... Please if you want to test and report play with setting and post log and suggestions ...

Thanks a lot to this fantastic thread.

PS

Please for all don't spam others threads or make negative comments .... Its exeperimenral for now.

Sent from my A0001
[ONE Original Android Development] TheWilkieWay:
Got this last_kmsg from my sod with v203, doubt it will show anything though, at the end it said something about bricked hotplug being disabled?

https://docs.google.com/file/d/0B8-DeeLz0wbGUnhzcXVJUlNQS2M/edit?usp=docslist_api
[ONE Original Android Development] pSyCh¤_O_O:
203 is newer....

I had one time on 202 where screen was black after pressing power button. Its not really a sod. Waited a few seconds and it turned back on. On 203 so far not a single issue.

This is how i flashed:

Unticked apply on boot from synapse menu

Wiped synapse data

Flashed UKM_uninstaller_v2

Flashed 203

Flahed UKM 3.8.1.2 special Edition

Booted

Opened synapse and pressed X

Why row backwards when everyone is going forwards [emoji12]
[ONE Original Android Development] Genericxx:
[MENTION=3685904]ak[/MENTION] latest v203 fixes my WiFi Issues! :D
[ONE Original Android Development] ak:
One positive side ... I have an idea for fix problems with sod .. But I'm at work for all day ... I think to work on it tonight ....

Sent from my A0001
[ONE Original Android Development] Genericxx:
Ye. That SoD thingy seems to go away after a couple of seconds. For the moment i'm adventurous enough to stay with v203 and test further. If something unusual happens, i'll drop in a few logs
[ONE Original Android Development] kantjer:
Im also having a few issues on SlimSaber like unresponsive touch screen and RIL crash after screen off.

disabled MSM MPDecision Hotplug now to see if that fixes it.
[ONE Original Android Development] isoladisegnata:
On temasek with 203 the boot continues to optimize applications continuous reboot...in secondary multirom why?

still cm12 nigtly...with 203 continuous reboot...in primary rom......:(
[ONE Original Android Development] gavin-phelan:
Spike too soon WiFi still disconnects and won't reconnect without a reboot
[ONE Original Android Development] Genericxx:
I am using RobbieL811's CM12.1 Build from yesterday and it seems that it doesn't suffer from such issues. But i'll have an eye on this also.
[ONE Original Android Development] isoladisegnata:
:( same problem for me too....:confused:
[ONE Original Android Development] giajp:
Always SOD with robbie's cm12.1
[ONE Original Android Development] Genericxx:
Dunno if it is related to the used App, but i don't have UKM or Synapse installed. Instead i'm using Kernel Adiutor (which is already implemented in Robbie's cm12.1). I've flashed ak v203, entered Kernel Adiutor after boot, setted "everything" to "enable at boot". Settings for me are ak's stock but sheduler (set this to row/1024). Screen stays black for me sometimes but only for a couple of seconds, so til now there was no reboot needed for me.
[ONE Original Android Development] kantjer:
same here, can take some time before the screen comes alive
[ONE Original Android Development] rezor92:
Which version should be used for cm12 nightlies?
[ONE Original Android Development] isoladisegnata:
how AK 203 behaves with SLIMSABER ROM?
[ONE Original Android Development] Formhault:
Stats can not be trusted when the battery is at 100%. Once it drops down to 99%, you'll see what I mean.

Also, charge your phone overnight; after you'll take it out, by the time it reaches 99% you'll have browsed the Web for 30 mins... then, the battery will start to go down, FAST.

At least that's how it went for a lot of phones in my case :) I don't see why the OPO would be different.
[ONE Original Android Development] JaylanPHNX:
YOU let US know. [emoji56]

It's baconnn!
[ONE Original Android Development] kantjer:
reverted back to 140 for now.
[ONE Original Android Development] indian84:
Yea.. True.. Will try that tonight...
[ONE Original Android Development] isoladisegnata:
done..;)
[ONE Original Android Development] pSyCh¤_O_O:
It runs fine for me if i turn on screen with dt2w

If i use Power button sometimes it doesnt kick in untill after a few seconds.

Also Spotify stutters when screen is off after a short period of time.

I grabbed a log using catlog:

https://www.dropbox.com/s/pti462v3m3u0nqz/logcat_and_device_info.zip?dl=0

I stopped the music and logging just after i heard the stuttering. Hope its of help [MENTION=3685904]ak[/MENTION] ;)
[ONE Original Android Development] foomanjackel:
Same here. Ran great for a long time yesterday on v203....but then the SODs started up again.

So I'm back to 140 as well.
[ONE Original Android Development] :
No wake up problems with smart cover till now. Didn't have the time to test screen off music. Maybe tonight.
[ONE Original Android Development] ak:
But you dont have problems with smartcover on or off?
[ONE Original Android Development] Supranoob:
For the SOD issue it might be related to the issue tesmasek 5.1 preview ROM users were having with the unresponsive power button?

http://xdaforums.com/showthread.php?p=59965136

Just putting it out there! Thanks a lot AK for your hard work ?
[ONE Original Android Development] ak:
Thanks a lot for the info. :highfive:
[ONE Original Android Development] :
I don't use smart2cover option in Synapse. I just leave it unchecked. It works anyway. No need to apply it in Synapse setting.

Only thing i notice, when i open smartcover in sunlight it sometimes takes 2 to 3 seconds until screen adjusts right brightness. Is there a way to change responsiveness of adaptive brightness?
[ONE Original Android Development] mapolidori:
I've been on Euphoria and your kernel since the first lollipop build, and I haven't had any SOD issues. I always update both as soon as possible. I have multirom, and haven't had an SOD on any 5.0+ ROM I've tried. I have tried to keep up with firmware updates. I'm currently on the 2-26 firmware. I don't know if that has anything to do with it.
[ONE Original Android Development] marvi0:
Hello, I may say the latest version is running very smooth on my phone running slim lp. Just a quick question. I am using the synapse app and everytime I try and set" performance 4 ", under hotplug. The settings go on" balanced 4" instead any advice please?
[ONE Original Android Development] Cris7ianO:
Hi anybody could share the stock CPU boost values with me? :D

Sent from my Bacon
[ONE Original Android Development] :
http://up.picr.de/21533683ml.jpg
[ONE Original Android Development] Stylo King:
Running v 140 rock solid.

Tried v203 but I reverted back after 1 hour as I was facing issues like SOD and below par battery backup. ?

Will wait for the perfect coming build.

Thanks AK

Sent from Blisspop's Lollipopified Bacon
[ONE Original Android Development] funCrash93:
@ak, tried 203 on latest Euphoria 5.0.2 sadly for me to audio glitching not only got back but also got when worse (music even stops from time to time for a under a second long), and known one for non Slim ROMs The SoD :(

but running smoothly 140 with no issues (not even audio glitching).

Thanks :angel:

bacon?A0001
[ONE Original Android Development] ak:
Its true I have exp the same ... [emoji33] [emoji33]

Sent from my A0001
[ONE Original Android Development] :
Listened 30 minutes to music screen off with TuneIn Radio and Eleven Player. No problems.

Blisspop, AudioFX, MSM Limiter disabled, 2 cores online at any time, max. 3 CPUs off screen, interactive, ROW

Since release of ak 203 no SoD
[ONE Original Android Development] ak:
new kernel online

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

A kernel based on CAF CM12 Bacon branch.

Download: AK.204.OPO.CM12.1

[ SMALL CHANGELOG ]

revert to old msm limiter + powersuspend ecc ecc

[ FULL CHANGELOG ]

Project name: AK KERNEL
anarkia1976 - Kernel Version: AK.204.OPO.CM12.1
anarkia1976 - ak_bacon_defconfig: enable POWERSUSPEND
anarkia1976 - kernel/power/powersuspend: add panel on/off hook registration
yank555-lu - kernel/power/powersuspend: cumulative update to version 1.6 (faux123/Yank555.lu)
yank555-lu - kernel/power/powersuspend: cumulative update to version 1.5
yank555-lu - kernel/power/powersuspend: LCD screen on/off hooks (Yank555.lu)
Paul Reioux - kernel/power/powersuspend: default to userspace for now
yank555-lu - kernel/power/powersuspend: add back userpace control w/ default kernel control
yank555-lu - kernel/power/powersuspend: remove userspace dependency from powersuspend
Paul Reioux - powersuspend: new PM kernel driver for Android w/o early_suspend
anarkia1976 - ak_bacon_defconfig: enable MSM_LIMITER
anarkia1976 - msm: msm_limiter: added new drivers for limit cpu frequencies
[ONE Original Android Development] ak:
msm limiter seems the problem, thanks a lot for your report. :highfive:
[ONE Original Android Development] madsponge26:
Gonna try now! Thanks ak!
[ONE Original Android Development] dragoi90:
Thank you [MENTION=3685904]ak[/MENTION] !You'r the real MVP!
[ONE Original Android Development] dickenam:
You're a genius, Stefano. V204 is amazing. All my wake issues have disappeared, I guess it was the msm limiter. Bravo!

4R034956T2959750H

Sent from my A0001
[ONE Original Android Development] Rhazi3l:
Im getting the same notification over and over =/
[ONE Original Android Development] Supranoob:
Running v204 with stock settings on temasek 9.5. Smooth sailing so far! No SOD or random reboots. Good job [MENTION=3685904]ak[/MENTION] thanks a ton.
[ONE Original Android Development] Mecca EL:
Woohoo, the Skull is back!!! Thanks [MENTION=3951473]AK![/MENTION] Everything is working great again.

Swipe to wake and Fast Charge aren't available anymore, on purpose?
[ONE Original Android Development] chachin:
yay I agree with [MENTION=3317953]dickenam[/MENTION] this kernel v204 is amazing i think i wont update again until maybe 210 or whatever after my 4day of work is over lol.. i like to update every4days when i get free time off work so thanks a lot @ak
[ONE Original Android Development] newellj79:
Just flashed the experimental kernel. Are the lower cpu steps going to be added?
[ONE Original Android Development] Formhault:
AK, I just flashed v204 on SlimSaber and I can't get more than 0.47A off a 1A port and 0.85A off a 2A port.

Testing with a charge doctor.

All is fine with CM11S and Boeffla kernel, for example.

You should implement some sort of charge control (Render for example). :D
[ONE Original Android Development] ak:
Underclock/overclock/fcharge will be inside into next kernel release. :good:
[ONE Original Android Development] nickporwal:
@ak, i flashed v204. Are the settings for gamma and sound going to be included in next release?
[ONE Original Android Development] ak:
Sound and gamma are inside.

Sent from my A0001
[ONE Original Android Development] Formhault:
CM has released some new Wi-Fi drivers just yesterday :eek:
[ONE Original Android Development] NuLLV01D:
[MENTION=3685904]ak[/MENTION]

Any Plans for Link Time Optimizations my friend?
[ONE Original Android Development] ak:
No. i don't see improvements for 3.4 kernels.
[ONE Original Android Development] ak:
204 have all you need, also new wifi.
[ONE Original Android Development] Formhault:
Ah, ok. Thought there are NEWER ones available, lol.
[ONE Original Android Development] cerealguy:
[MENTION=3685904]ak[/MENTION] v204 seems to resolve all my issues on Blisspop tha I had with latest experimental builds! It's a smooth beast! :D Thanksssss!!

P.S. Splash screen is a must!! [emoji13]
[ONE Original Android Development] dev0lver:
Is there something wrong?

I don't have that much of governors to choose, and cpu lowest freq is 300mhz?

Also, app for update keeps showing that I have update for 140v, and I am on 204?

Reflashed ukm, wiped dalvik an cache and cleared app data multiple times, still nothing is different

Is it just me, or all of you have the same situation?

I would like to use smartmax governor, but I have only those options...
[ONE Original Android Development] kantjer:
[MENTION=3685904]ak[/MENTION] 204 is fast and stable again :good:

changed my source code to include it in my next build
[ONE Original Android Development] Genericxx:
v204 is

experimental

and as ak stated before, there are currently mostly

basic features

integrated. If you want to have more governours or features, stay with stable v140 until stable v2xx will be released some day.
[ONE Original Android Development] nonoperez:
204 working great on Robbie uber 5.1, no SODS. THANKS AK!
[ONE Original Android Development] clock51:
AK204 works well on slimsaber 08/04, no lockout no reboot, smooth and fast
[ONE Original Android Development] iker_92:
so far so good with 204..hoping to see again per core control that i like so much ;)
[ONE Original Android Development] marvi0:
Coming from a nexus 6 which I had sold due to its size and bought the oneplus I nearly sold it as I just couldn't stand the choppy lag. This kernel has saved me from selling this phone as it's made my phone just as fast as nexus 6 thanks.
[ONE Original Android Development] Formhault:
[KERNEL] [08/04] [4.x/5.x] [3.4.106+] [UB5.0] ☆ AK ☆ [S v.140] [E v.204]

204 works well with latest Resurrection Remix... But... Same WiFi problem :(

As you can see, at times, there are two networks visible. Rarely...

The WiFi in question is ITEELab. I am going insane.
[ONE Original Android Development] ak:
Thanks a lot guys for all feedback!
[ONE Original Android Development] isoladisegnata:
Hi Stefano...good job..for me in multirom work nigtly-P/cm12.1-S/temasek-S :good:
[ONE Original Android Development] cerealguy:
[MENTION=3685904]ak[/MENTION] I have only one problem with last 204: when I reboot , date and time go crazy... It shows a fake date and time... It's not related to Blisspop Rom because with its stock kernel there is no problems...
[ONE Original Android Development] Eru Ilúvatar:
@ak

Is that normal, Stefano? On latest v.204 there are a x2 "min CPUs online at any time" and x2 "max CPUs online at any time". A lil' redundant, isn't it? :p
[ONE Original Android Development] ak:
No, its setted to 1 core by default, no more glitches now.

You have to reset ukm/synapse.

Go to recovery:

- untick set on boot

- flash ukm unistaller

- flash new kernel

- flash ukm

- reboot
[ONE Original Android Development] funCrash93:
[MENTION=3685904]ak[/MENTION] do we need to flash UKM for the Kernel Auditor app to work.?

bacon?A0001
[ONE Original Android Development] ak:
No,ukm is only for synapse.
[ONE Original Android Development] gianton:
Not needed.
[ONE Original Android Development] ak:
The new official cm12.1 kernel don't have anymore logging and alarm timer. :good:
[ONE Original Android Development] magnamentis:
good day

if you remember the last nights discussion about touchissues and settings to reduce them, i've tested now a bit more in depth intelliplug vs. mpd and i have to say that the mpd settings are (at least on my device) by far better. this might be something to verify and/or keep in mind until this will be finally solved firmware (or hardware) wise. somehow i suspect that it's not only a software issue, often i perform the same commands on 3 devices simultaneously, i.e change settings which i came to a final decision or downloading apps or modules and whatever i do, compared to the nexus 5 (huge) and the n7100 the one definitely lags (touchwise). by the way i'm wondering how touch behaves in case of those who try extreme battery saving profiles with super low frequencies etc.?
[ONE Original Android Development] _Beni_:
Which modem are you using?
[ONE Original Android Development] Ky0sHiR0:
About problems with the screen responsibility:

In my case Nova Launcher (free) caused problems. I'm currently on 1,5 GHz and Google Launcher and double tap to wake works normally. It's really, really weird. I'll try to buy nova launcher because there is option in launcher settings called Double Tap but i dont know how it works...

I feel confused about this ~.~
[ONE Original Android Development] ak:
Double tap in nova is related to gesture, nothing related to kernel wake up drivers.
[ONE Original Android Development] magnamentis:
hi

@ak

what you see in the screenshot below happens more often than not.

it's independent of settings or version

this time i have your stock settings (on boot off/unchecked) and before i had settings on boot, no difference.

it's always GPU Governor, i mentioned i somewhere yesterday as a side-remark.

i tried reboot as well as softreboot, no difference.

BUT

the moment i manually apply a profile, after the frequent failed app restart, all is well again

tell me what else you need and where and at which point in the process to fetch it so that you get appropriate information as to the cause.
[ONE Original Android Development] Ky0sHiR0:
But with low-freq profile on google launcher my dttw is working properly so?...
[ONE Original Android Development] Stylez Ray.:
MPSS.DI.2.0.1.c7-00020-M8974AAAAANPZM-1
[ONE Original Android Development] funCrash93:
happened to me once when updated to b12.

just cleared Synapse (within the app there is an option to Clear Synapse or smth like that) and no more such Red Warning :)
[ONE Original Android Development] _Beni_:
so you never did a modem update?

Update your modem by this link http://xdaforums.com/oneplus-one/help/guide-fixing-opo-cm11s-modem-problem-t2824139

It should fix the problem
[ONE Original Android Development] Vortex1969:
Now that I got through those two chapters of the book forum. I'm all caught up on the post. Lol

Any way 32_b12 running great here.
[ONE Original Android Development] ryaneu:
Wait a minute. the modem update does not change the baseband version in the about phone screen.
[ONE Original Android Development] störte:
I have the same modem. Can you tell me which version is the actual one ?

I thought there was no update.
[ONE Original Android Development] funCrash93:
yes, it doesn't change the version number, but the actual modem is different, I checked files (Hash Sums are different from all ROMs : 22R, 25R, 30R, 33R (or at least the ones that provide that modem :D ))

will try M8 and M9 to see, but a difference in modem is but not version number ;)
[ONE Original Android Development] _Beni_:
The baseband is always the same version.

I also have the same baseband, but i have flashed the one from the thread i posted.

In the log of him there were many thinks about the modem and then a Fatal error about the modem and a fatal error is never good ;)

Also the stacktraces at the and are very bad, someone who has the debug symbols for this kernel could find out in which function exactly the error occured.
[ONE Original Android Development] Vortex1969:
There is no way to know CM does not change baseband number. So you would have to look at the binaries to see if there different.

Which is really stupid on there part.

I am having no problems so I'm staying with what I have.

At least Google would change there baseband number.
[ONE Original Android Development] _Beni_:
i know, but i thought this information was not needed, because finding out the real modem version is complicated than ^^.
[ONE Original Android Development] ryaneu:
there is modem update from the latest CM11 nightly too. wonder what they fixed in the updates.
[ONE Original Android Development] ak:
At this point isn't a problem if kernel ... You can send pm to Nova developer.

ak@a0001
[ONE Original Android Development] ak:
Yes ... Some commits are related to modem.

ak@a0001
[ONE Original Android Development] ak:
Can you post the problem on ukm thread?

ak@a0001
[ONE Original Android Development] cerealguy:
Then I need an update from you? [emoji13] [emoji13]
[ONE Original Android Development] Formhault:
Ak, is it possible for you to implement some option, in Synapse, through which we can select specific Wi-Fi channels the phone can detect? :(
[ONE Original Android Development] Renosh:
Dude change the name of one of your Wi-Fi, stop being dumb
[ONE Original Android Development] Formhault:
Sure. Hang on, l'll ask the dean :)

I guess I'll have to stick to CM11S until Google gets their sh*t together and fix this... Sorry for the hassle :(
[ONE Original Android Development] mefxes:
After reading the instructions I'm not sure wich version of AK Kernel to use with my stock phone, CM11.

"Today I updated my opo to lastest official cm11s rom (XNPH05Q) provided by Calkulin here and flashed the lastest ak kernel v.113. I think to write a little guide to help everybody wants keep rom updated but wants ak kernel too.

-First of all update your rom from ota or download it from Calkulin's thread

-Flash lastest bacon firmware provided by vanir here. Lastest now is "bacon_firmware_update_2015_02-09.zip"

-Flash ak kernel and UKM.

-Wipe cache&dalvik

-Reboot in fastboot(boatloader)

-From Calkulin's thread download "XNPH05Q Radio, etc" and extract the file "NON-HLOS.bin", put your phone in fastboot mode, connect your phone to pc and flash this file with command " fastboot flash modem NON-HLOS.bin" and then "fastboot reboot".

-Done!"

Should I flash the AK.140.OPO.CM12.1 and UKM_v3.8.1.2_special... after flashing the aprils bacon firmware update? Are these the correct files?

Note: I'm just seeking for a better battery life since I got no problems on my device. But I'm having less than 4h SOT.

Thanks in advance.
[ONE Original Android Development] kewinhdorff:
if i have this kernel flashed on my oneplus one

if i then flash cyanogenmod nightly to update my phone will cyanogen stock kernel replace AK ? or will it stay with AK kernel
[ONE Original Android Development] nuwan32:
yes cm kernel will replace it. you have to flash custom kernel after flashing rom, always.
[ONE Original Android Development] kewinhdorff:
okay, but if i have done some tweaking with AK lets say

AK > flashing cm (get cm) > flash AK again will the tweaked settings remain or do i have to redo all the tweaking ?
[ONE Original Android Development] nuwan32:
yes, but if its with a program like synapse, then it saves the settings, and you just have to reapply it when your phone reboots.
[ONE Original Android Development] dudas89:
But I suggest you to install the 140 version on CM Nighlies. I've just installed v204 and the sleep of death is not fixed yet. I had to get back to v140.
[ONE Original Android Development] kewinhdorff:
if the settings are saved why do i have to reapply ? :eek: didn't understand that part
[ONE Original Android Development] nuwan32:
because its saved in the program, not applied.
[ONE Original Android Development] ak:
You are the first and for now the only one with SOD with the new v204. can you post some infos?
[ONE Original Android Development] kewinhdorff:
oh okey. havent got my OPO yet since i ordered it on tuesday. but i most often stick with stable stuff :)

aah i see :) thanks for you guys replying to me and helping me out :)
[ONE Original Android Development] cyablo:
Same Problem to me. Flashed 08.04. CM12 nightly and v204 Kernel and Battery dropped from 85% to 14% in about 5 Hours without Usage.

WakeLock Detector says: 90% Wake since over 7 Hours. There are event0, event0-865 and event2 with nearly 2 Hours waketime under Kernel-WakeLocks, all other WakeLocks look fine.

Also there is a strange Clock Bug when the Phone starts, suddenly many Apps complain about wrong Date or Time and start doing Synchronizations or Alerts with Past Events...