yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] funCrash93:
it is USB Charge Related, not AC.

check your Battery Stats and you'll see the difference when charging from Wall Charger and when from Computer/USBs ;)
[ONE Original Android Development] capitanouncino:
Yes I know that is related to USB charge...but below it says "for wallcharger use 1500ma as MAX"
[ONE Original Android Development] ak:
What ROM?

ak@a0001
[ONE Original Android Development] Stylez Ray.:
Latest Mahdi. All kernel settings are default.
[ONE Original Android Development] cerealguy:
Flashed now on Blisspop... Over 140... Test in progress... ;)
[ONE Original Android Development] ak:
nb

Ps:

FB Notifier --> Experimental --> in case of problems disable it

root@android:/ # cat sys/module/state_notifier/parameters/use_fb_notifiercat sys/module/state_notifier/parameters/use_fb_notifier
Y

root@android:/ # echo "N" > sys/module/state_notifier/parameters/use_fb_notifier

root@android:/ # cat sys/module/state_notifier/parameters/use_fb_notifier
cat sys/module/state_notifier/parameters/use_fb_notifier
N
[ONE Original Android Development] Spaulding89:
Booted fine on Robbies CM12. I hope you killed the random reboots

---------- Post added 7th April 2015 at 12:05 AM ---------- Previous post was 6th April 2015 at 11:49 PM ----------

All is superior smooth till now. Tomorrow i can say More.
[ONE Original Android Development] DanielFran:
CM11S, same issue with Google services!
[ONE Original Android Development] LookedPath:
I have two invites that are going to expire in less than a day. If someone needs them please let me know.
[ONE Original Android Development] :
C'mon. Please don't quote full post...

Reboot testkernel.

https://www.dropbox.com/s/k2y5qh379g40et7/last_kmsg-2015-04-07.02.46.21.txt?dl=0
[ONE Original Android Development] chikimonke:
More random reboot logs @ak
[ONE Original Android Development] dickenam:
SO fast, SO smooth. So reboot. Let me know if you need any additional infos!

Here's ma pastebin of 2 last_kmsg from the past half hour :eek:

ROM: 4/4 Robbie Uber12.1

AK: 200 test v1

Synapse: All default except - Row 512kb, GPU 389 max, kcal cool AMOLED, Franco sound all +1

last_kmsg1

last_kmsg2
[ONE Original Android Development] mannyalba:
Lol, nice one...
[ONE Original Android Development] Formhault:
Kantjeeeerrrrrrr

---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------

Hey [MENTION=3685904]ak[/MENTION]

Not sure who else to take this up to, so I'm asking you... Maybe you know something.

Both 5.0.2 and 5.1 are having this problem. KitKat works fine, though. Tried various Lollipop ROMs... to no avail.

Say you have two identically named Wi-Fi SSIDs but on different channels. The phone can see one, but fails to establish a connection. :eek:

Not sure if this is kernel or ROM related... In any case, it would be very awkward if Google effed up on this one.
[ONE Original Android Development] MBurns2:
from latest changelog: "myfluxi - cpufreq: cpu-boost: Use hotplug thread infrastructure"

does it mean that ak has added myfluxi hotplug (msm hotplug) ? thanks
[ONE Original Android Development] Genericxx:
[MENTION=3685904]ak[/MENTION] If you got some minutes, please take a look into this thread by me regarding WiFi issues. Anything known about by you? CodeAurora released new WiFi drivers which may or may not fix this issue. As seen here, Steve Kondik already merged something regarding this for CM12.1. Would be eager to test if this commit or new WiFi drivers would solve this issue.
[ONE Original Android Development] dickenam:
Delete!

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

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

A kernel based on CAF CM12 Bacon branch.

Download: AK.202.OPO.CM12.1

[ SMALL CHANGELOG ]

nb: only essential features for now

rebased from scratch

3.4.106 linux

sound control

voltage control

new uber toolchain gcc5.0

re-added splash logo

kcal v2

new bricked hotplug

new state notifier

new cpu boost driver

new msm limiter driver

min/max/boost for cpus indipendent from each others

governor for cpus indipendent from each others

ecc ecc ecc

[ FULL CHANGELOG ]
[ONE Original Android Development] ak:
I have see the code, i haven't problem to merge it.

i think is necessary wait rom side also.
[ONE Original Android Development] RobbieL811:
Where is the source? I'm about ready to try this in the ROM!
[ONE Original Android Development] Genericxx:
Here you go
[ONE Original Android Development] ak:
https://github.com/CyanogenMod/android_kernel_oneplus_msm8974/commits/cm-12.1
[ONE Original Android Development] Genericxx:
Meh... My fault :D

Anyway... Installed v202 on latest SlimLP... Boots up, but when screen goes of, device is dead. Only able to reboot via adb. Although it states "no errors", here's dat last_kmsg
[ONE Original Android Development] Formhault:
Since we're talking Wi-Fi issues, have a look here, please!
[ONE Original Android Development] kantjer:
No such problems on today's SlimSaber build.

For now it's running fine with all stock settings.
[ONE Original Android Development] LookedPath:
For me it isn't booting.

I'm on 4th of April nightly and the only different thing that I have on my phone is that I'm on F2FS.
[ONE Original Android Development] kantjer:
I'm having that exact situation here at home 3 WiFi AP, same SSID but different channels.

No issues, the phone is nicely roaming between the three AP's
[ONE Original Android Development] Spaulding89:
Phone is not dead when screen turn off. I had think the same but after 1-2 minutes the screen turns on again. I'm on Robbies CM 12.1. I needed something new ;)
[ONE Original Android Development] Genericxx:
F2FS support is not implemented in v202 i guess. AK stated that there are currently only basic features..
[ONE Original Android Development] LookedPath:
That was my doubt.

Let's see what does Stefano say.
[ONE Original Android Development] Formhault:
My phone (on 5.0.2 / 5.1, at least) only sees one SSID. Some times, two show up on the list, but that's extremely rare - hence why I am assuming there are two SSIDs with different channels. It tries to connect, then goes back to "Saved" :( . On KitKat (SlimKat, for example), it works perfectly! iPhone 5S, Galaxy S3, S4, BlackBerry + some other models can connect to it just fine, too!

It must be a Lollipop issue.

I know this isn't related to @ak's kernel (and for that, I apologize), but it's the only way to get to the high ranked devs, you know...
[ONE Original Android Development] nuwan32:
[MENTION=3685904]ak[/MENTION] why does the OP say ak 203 but everything else i can only find a 202? :p
[ONE Original Android Development] aamitabh28:
Test kernel running smooth so far on euphoria beta 5.1

Will report as to how it goes from here!

Thanks man
[ONE Original Android Development] ak:
No f2fs for now ... but i want to merge official into next release.
[ONE Original Android Development] ak:
Fixed.

I can remember sometime ago a suggestion by user about an app to avoid this problem, but in this moment i cant remember the name.
[ONE Original Android Development] ak:
New source is up and running:

https://github.com/anarkia1976/AK-OnePone-Reborn
[ONE Original Android Development] ak:
I can merge latest wifi drivers, and make a test kernel. stay tuned.
[ONE Original Android Development] HaTrED_:
I think it isn't mate because your page and link stills redirects us to:

http://ak.hiddenbytes.org/downloads/AK.202.OPO.CM12.1.zip

:confused: :p
[ONE Original Android Development] AJ RIMMER!:
Yeah, that is correct. The v.203 in the title was wrong...
[ONE Original Android Development] ak:
thanks guys

my error, sorry :p
[ONE Original Android Development] Formhault:
That'd be awesome. Thanks!

Also, not so sure there are two SSIDs with different channels anymore. Only once, my phone listed two SSIDs in the Wi-Fi menu - so I assumed it's that. I think it's one SSID afterall, just that Lollipop is having a very hard time connecting to that specific router, for some reason. I study electric engineering, so those labs can't possibly have routers so crappy :eek:

I guess they're using some specific router OEM that Google recently had a fight with so they blacklisted some models. LOL. This is crazy. Even an iPhone 4 works just fine with it.
[ONE Original Android Development] expiredd:
Experimental version 202 only working with UKM 3.8 +?
[ONE Original Android Development] ak:
No but its recommended

Sent from my A0001
[ONE Original Android Development] dickenam:
Delete!
[ONE Original Android Development] :
I'm using the exp version (v202) with Temasek CM12 v9.4. Sometimes my device doesnt wake up. What can I do, to fix this? Or is this kernel only for cm12.1?
[ONE Original Android Development] Supranoob:
Does this experimental version contain smartmax and some of the other governors?
[ONE Original Android Development] skeetzor:
Mine isn't waking up either.

On SlimLP (jacks) 6/4
[ONE Original Android Development] kantjer:
Happened to me once after a reboot when I let the screen go off before the boot cycle fully completed.

When forcing the screen on until the boot is fully finished (about 2 minutes) this doesn't happen for happen for me.

Seems to occur under heavy CPU load with screen off.

That would also explain why for some the screen comes back to life after some time when the CPU finishes what ever it was doing
[ONE Original Android Development] ak:
Can you try to disable fb notifier?

I cant reproduce with my phone.

Sent from my A0001
[ONE Original Android Development] kantjer:
I will disable it, but in the about 2 days Run the test kernels it only happened once.

I'm probably not the best tester for this.

If there are other users who see this more often please join this test

EDIT: Disabled
[ONE Original Android Development] kalpik:
No, it doesn't.

Sent from my A0001
[ONE Original Android Development] ak:
Do you use the latest one with ukm values reset to stock?

Sent from my A0001
[ONE Original Android Development] kantjer:
Don't use UKM but I have "apply on boot" switched off for all categories in Kernel Adiutor. Everything should be 100% stock.
[ONE Original Android Development] cerealguy:
One reboots and 2 SOD on Blisspop Rom with last 202... Sorry for no logs but I 've returned to 140 because I need phone working until this evening
[ONE Original Android Development] ak:
test kernel

test kernel:

- added new f2fs

- added new wifi drivers

- change notifier from mdss to backlight

View attachment AK.203.OPO.CM12.1.zip

thanks for testing
[ONE Original Android Development] indian84:
Do you even stop and take rest bro??

:P
[ONE Original Android Development] chikimonke:
I will give this new release a test run, but I had a question on the previous one as well. (excuse my ignorance here, as I can't remember) Does the kernel affect BT at all? Your previous test versions were getting random reboots, which I noticed right away when my Pebble vibrated because it lost connection to the phone. I'd pull the phone out of my pocket and see the boot animation. However, on the latest 202 test kernel, I'd get the disconnect vibration, but when I pulled my phone out I could wake it no problem with dt2w or using the power button. Once the screen was on my Pebble would reconnect. This only happens when on 202 (testing 203 now), and never happened on 140, which is why I'm thinking it's kernel related somehow.
[ONE Original Android Development] nuwan32:
try changing no. of cpus screen off to 2 and increase max cpu freq for screen off? for me, if i lock the screen with camera open, then it takes a while to turn on again. happens every time.
[ONE Original Android Development] Spaulding89:
No SOD with latest Test Version. But i changed my synapse settings before screen goes off to 2 cores on when screen off. I will Report Any issues if i find it.

Edit:

And I enabled Wakeup boost
[ONE Original Android Development] :
I set mine like in ak140. 2 CPUs online at any time. Max. 3 CPUs screen off. It's a maximum, not minimum. In idle 3 CPUs aren't used. Only when playing music, avoids stuttering. I don't have wakeup problems with testkernel.
[ONE Original Android Development] ak:
The music stutter isnt present anymore.
[ONE Original Android Development] ak:
The BT stack is the same, if you have problems please try to diable notifier with terminal.

thanks a lot
[ONE Original Android Development] :
Ok. Will test with stock settings. On Ak 140 i needed max 3CPUs screen off with TuneIn Radio.
[ONE Original Android Development] Spaulding89:
Okay now my phone display was 5 minutes off. And the screen needs a few seconds to turn on but no SOD so far.
[ONE Original Android Development] ak:
You can try with wakeup boost into CPU boost drivers.

Sent from my A0001
[ONE Original Android Development] Spaulding89:
I have Wakeup Boost enabled like I writed in my other post :)
[ONE Original Android Development] TheWilkieWay:
v202 is running so smooth! Getting a few issues like SOD's and slow wake-ups from time to time like other people have mentioned but apart from that my phone is flying :P tried looking at a last_kmsg but it was completely scrambled, said there were unrecoverable blocks at the bottom, anyone know what would cause this?
[ONE Original Android Development] mapolidori:
Is anyone else having the issue in the picture below? I've asked a few times, but no one has responded. AK kernel updater always tells me to update to v140. I even reflashed v137 and flashed v140 again. I have uninstalled the kernel updater, reinstalled it, cleared the app data. Nothing seems to fix it. I deleted the zip and redownloaded through the updater app, and through ak's website, flashed them both separately with the same result. Any ideas? Is it not flashing properly?
[ONE Original Android Development] ak:
Can you try v203? thanks a lot.
[ONE Original Android Development] Spaulding89:
I find out when I disable C1 (Retention) in adv (synapse) screen turns directly on.
[ONE Original Android Development] kantjer:
202 has been running without issues with fb notifier disabled. Installed 203 now. Wil leave fb notifier enabled now
[ONE Original Android Development] ak:
With fb notifier disabled how are the performance?

Sent from my A0001
[ONE Original Android Development] ak:
Strange ... I don't know why.

Sent from my A0001
[ONE Original Android Development] kantjer:
Great didn't notice any difference enabled vs disabled. But I didn't push the phone to its limits.
[ONE Original Android Development] newellj79:
Same here. Looking forward to next kernel just to stop the notifications. ?
[ONE Original Android Development] krxz:
After flashing 203 I get constant bootlops right after boot of the rom. I am able to enter sim pin and then it freezes and reboots. Now I am on 202 and on every boot I get the message that my timesettings aren't correct. I am on temasek cm12.1 Preview and latest oxygen firmware. I have no problems with ak140.
[ONE Original Android Development] mapolidori:
Everything is running smoothly. No issues whatsoever, other than it telling me to update. I'm on Euphoria 5.0.2. The kernel says cm12.1, but I assume it still runs on 5.0.2. Is that an issue?
[ONE Original Android Development] ak:
The only diff can be related to on/off operations

Sent from my A0001
[ONE Original Android Development] kantjer:
LOL, I always thought that was because I build the kernel as part of the ROM and it somehow checked on something else then the version it shows it shows. But if it also does that with the stock kernel it's not due to my build.
[ONE Original Android Development] gavin-phelan:
[MENTION=3685904]ak[/MENTION] can you have a look at this http://xdaforums.com/showthread.php?p=59952735
[ONE Original Android Development] kantjer:
To test the kernel and CPU governors, one of my test is running SD Maid system cleaner.

On the 140 kernel Smartmax gov gave me the best performance with ~1400 op/s compared to ~1100 op/s with the stock Interactive gov.

Now with 203 with all stock settings (using Interactive) it gives me ~1500 op/s.
[ONE Original Android Development] nuwan32:
just tried cm 12.1 preview temasek with ak 203 and got a sod.
[ONE Original Android Development] dickenam:
@ak

I noticed that when charging with the screen off, the device remains in the "Suspend Max Freq" (1728mhz) whereas prior to the 200 level exp. releases, it would stay in 300mhz.

I tested this by setting it to 729mhz and leaving it for a bit. I have it set to 300mhz currently, will I notice any negative side effects?

TIA!
[ONE Original Android Development] ak:
For now the best use of notifier is directly into drivers, i want to live native support off. With this setting all work like a champ.

I think to release a new update tonight.

thanks a lot for support guys.
[ONE Original Android Development] Pradhan_89:
203 working great here with DU 5.0.2. Earlier versions gave SOD. Till now there are no SOD or reboot. Synapse is not opening. Don't know why.
[ONE Original Android Development] xlollomanx:
Try with uninstall and re-install synapse from play store.

Sent from my Oneplus One
[ONE Original Android Development] Pradhan_89:
Did that. No luck. I have flashed 203 over 140.
[ONE Original Android Development] HaTrED_:
I suffered from exact same issue but under SlimSaber 5.0.2 and with akv202!! Had to revert back to v140... Will see and try newest release.

Tapatalked!
[ONE Original Android Development] Formhault:
Flashed that test build on top of RenderKernel (Resurrection Remix ROM) and all that comes on is the capacitive keys light (screen = dark). Guess this kernel doesn't go well with that ROM... I didn't do my homework, eh? :(

Besides, I'm getting FC's all over the place with this ROM. I'm guessing you guys have already found a keeper - if so, what would that be? I've tried a few and none seem to be stable... except CM11S, of course :(
[ONE Original Android Development] demon507:
I didn't know OPO could time travel. Lucky you.
[ONE Original Android Development] ak:
new kernel online

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

A kernel based on CAF CM12 Bacon branch.

Download: AK.203.OPO.CM12.1

[ SMALL CHANGELOG ]

new f2fs

new wifi drivers from cm12.1 branch

fixed screen on/off

ecc

[ FULL CHANGELOG ]
[ONE Original Android Development] iker_92:
Same issue in 5.1 jgcaap..resolved reflashing ukm 3.8.1.2..this kernel is the fastest i've ever used!! Amazing work AK!!
[ONE Original Android Development] dickenam:
@ak

same as test version?
[ONE Original Android Development] gavin-phelan:
Will this fix the WiFi problems on 12.1
[ONE Original Android Development] ak:
no .. i have added one fix.

In italy we say: "boh" ... you can try and report.
[ONE Original Android Development] funCrash93:
what about NTFS.? :D (me as always ;) )

or maybe it is a part of the default feature pack.? :angel:

---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------

btw, the ability of the phone to "see" Ad-Hoc WiFi Networks (you know, those Windows WiFi..) is driven by the kernel or it's ROM's feature.?

Thank you.
[ONE Original Android Development] ak:
Ntfs is enabled.

Wifi ad hoc is a mix rom/kernel.
[ONE Original Android Development] funCrash93:
awesome, Thanks (booting into Recovery :) )

so, is your Kernel AdHoc Ready, or it is not that easy.?
[ONE Original Android Development] foomanjackel:
with v200 i had reboots. with 202 i had SOD's. so far all good with 203....thanks as always ak :)

i'm on fusionjack's latest slimsaber build (20150406)
[ONE Original Android Development] ak:
What app do you use for ad hoc?
[ONE Original Android Development] funCrash93:
no apps, just from within Windows.

https://youtu.be/o0OdtZDS4JE?t=29s (simple AdHoc)

(something similar in Win8.x but from within the CMD)
[ONE Original Android Development] ak:
I never tested it. :p
[ONE Original Android Development] funCrash93:
I found it very useful (fast and easy 2 or 3 lines from CMD on Win8.x and done, you have a WiFi by your side with no router), but the problem with Android is that those AdHoc are not even visible, or if visible the phone won't connect.
[ONE Original Android Development] Zootopia:
Booted just fine with your latest 203 on Robbie's latest CM12.1 Uber.

Love the booting logo. [emoji12]

Still exploring, but as initial thoughts go... So far this is as Fluid, Fast as it gets.

No sign of unstability. [emoji106]
[ONE Original Android Development] gavin-phelan:
WiFi bug fixed for me thanks
[ONE Original Android Development] ChrisAr:
Time bug
[ONE Original Android Development] DanielFran:
@ak

In CM11S, Wi-Fi is fixed too.

Remaining issues:

- time

- Google services

Does compatibility with CM11S still valid?
[ONE Original Android Development] TheWilkieWay:
Still getting SOD's with the new v203, the capacitative buttons don't light up this time though, are there any logs that I could post? I seem to remember that SOD's don't show up in logs
[ONE Original Android Development] clock51:
stable, stable, stable with my rom slimsaber 20150406, squirts like a rocket, smooth as oil, AK thanks, for this incredible kernel
[ONE Original Android Development] bombadier:
Don't think 203 is compatible with cm11s at the moment,WiFi and data problems so will stick with 140

tapatyping fae the bacon
[ONE Original Android Development] sam razzy:
Okay.. Finally flashed 203 version on my Euphoria 5.0.3 over 140 v kernel. Happy to see my phone is running smooth like Butter without any other synapse settings. I'm not good in synapse, so last time I had been using someone's profile settings, so now I want a new profile for 203 kernel. So if anyone have a synapse profile which can compromise with battery and performance then I would be very happy to try it.. Thank you
[ONE Original Android Development] AJ RIMMER!:
Yeah. I was. I got tired of the constant prompts, so I uninstalled for now. It was still telling me that the 140 version was the latest, even after installing 202.
[ONE Original Android Development] dudas89:
I tried the last version, the 203 and my Oneplus suffered the sleep of dead. Once it enters in sleed mode, I have to force it to reboot. I'm using CM Nighlies, btw.
[ONE Original Android Development] Mecca EL:
Suffering SOD, attempting to wake my device, using v203. Also, missing features like Sweep 2 wake, and fast charging are missing.
[ONE Original Android Development] TheKnux:
[MENTION=3685904]ak[/MENTION] since a lot of users are going back to 140 because of the reboots and lack of features at this time, I would really like to know if you can make a tweaked 140 version with your kernel splash screen cause it was sick.

If not, no a big deal. Just thought it was sweet. Thanks a lot for all of your hard work man.
[ONE Original Android Development] RenderBroken:
@ak

Tested new build and it ran Great! I don't think I have ever ran a build from you that didn't! Still rocking you on my old N7 2013. Keep up the amazing work! Your commitment really shows through.
[ONE Original Android Development] ak:
[MENTION=5438598]RenderBroken[/MENTION]

Thanks a lot my friend.

I need to find why some users have sod, for now i have 0 problems with slimsaber. :good:
[ONE Original Android Development] RenderBroken:
Any Logs? I use Syslog religiously to gather logs since its really easy to get them. If you get another SoD, could you try to get last_kmsg? I know sometimes it just wont "reboot" to produce said log but if you try to wake it up via power button or DT2W, you can make it reboot due to panic. Thanks!

Yes, it can cause SoD, audio issues, etc. How are you verifying that this is the case?

Same as above. Thanks.
[ONE Original Android Development] RenderBroken:
I will look through your source to see if you have any commits that proved problematic for myself.
[ONE Original Android Development] jesterpaul:
I've tried running 203 on two LP 5.1 ROMs. Nocturnal and Temasek preview. On both of these initially phone seems to fly, but then CPU overheats in rapid time, and thermal control cuts in, slowing the phone to a crawl. Also have dead screen issue at random.

Currently back on 140, but will look to test if I get time and send kmsg for analysis.

Sent from my Blissed out OPO
[ONE Original Android Development] indian84:
I will leave it here.

And no, my battery stats are not broken.

Thanks [MENTION=3685904]ak[/MENTION] and [MENTION=4593553]Mahdi786[/MENTION].