yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] dudas89:
What do you need, ak?

Btw, I'm experiencing that clock bug too. When my phone boots the clock shows like 6am and it was 1h30pm. After a few seconds the clock auto corrects itself.
[ONE Original Android Development] fireforhire:
No problems with 204 on slimsabre 4/8 build...
[ONE Original Android Development] MBurns2:
version 204 is giving me awesome battery life during screen on, where is the trick ? best version until now (imo) ! During 50 min on tapatalk/opera my battery went down only 6% (i have scaled down touchboost and hotplug)

thanks ak for the hard work, i will let you know if i will have any wakelocks.

(my rom is latest euphoria with google slim gapps without bloatware)
[ONE Original Android Development] ak:
For the clock questions i have reply before. No bug, Rom need to be updated for support latest official android/cm12.1 changes.

https://android.googlesource.com/kernel/common.git/+/69e80b0b102c0eadf7a5ea8984e5f3dd9109fe43
[ONE Original Android Development] real_pac:
Mixed F2Fs compiatible?

[MENTION=3685904]ak[/MENTION] Is the build 204 2P Mixed F2Fs ready?

I read about you have already implemented new F2Fs drivers but wont work for me.

Sticking on bootloop...

Just did a clean flash etc.

Tried almost everything thats the last reason for me why it wont work.

Thanks

regards
[ONE Original Android Development] DerRomtester:
For the new f2fs patches new mount options are necessary inside the fstab ( Cl3kener Uber said that).
[ONE Original Android Development] ak:
So do you think we need to update rom fstab?
[ONE Original Android Development] malavan:
Yes I'm on latest resurrection remix all stock and have time problem so it's not kernel problem
[ONE Original Android Development] real_pac:
Danke! Good to know helps me a lot!

so, that means i have to unpack boot.img of Ak kernel and change fstab?

regards
[ONE Original Android Development] Eru Ilúvatar:
No no, mine it's not a problem of cores :p

If you look at the screenshot (http://xdaforums.com/attachment.php?attachmentid=3253392&d=1428576857) you can see that there is, under MSM MPDecision, a double setting "min CPUs online at any time" and double "max CPUs online at any time". Is it really supposed to be like this? Shouldn't be only one "min CPUs online at any time" and only one "max CPUs online at any time"?

By the way I already have done the above passages (uninstall UKM, flash new kernel, etc.) plus cleared the synapse data.
[ONE Original Android Development] Shadowghoster:
Had the same drain here but it was caused by bad applied synapse-settings after flashing 204 over 202 and just pressing x on synapse without checking all settings again. Min freq was set to 19xx MHz what was over the freq for activating other cores, so all cores stayed online at this freq over night.... Instead of testing deepsleep behavior I got 15% battery left after 8h of sleep :D

So check your synapses settings ;)
[ONE Original Android Development] ak:
My kernel use anykernel format, no ramdisk.

you have to unpack ramdisk rom.
[ONE Original Android Development] Spaulding89:
I had the same. Now all is fine again.
[ONE Original Android Development] AhmedFaiz:
Feedback here soon?...
[ONE Original Android Development] Mecca EL:
See if this helps:

Go into Developer Options, and turn on Local Terminal

If the icon wasn't created on your device desktop, search for it in App Drawer

Open Terminal and type: su

Then type: uci reset ( make sure there's a space between the phrase )

Then type: uci

Then: exit

Make sure you hit Enter, between each command line to execute.

Should clear up and reset Synapse, without having to uninstall everything.
[ONE Original Android Development] real_pac:
thanks Ak! :cowboy:
[ONE Original Android Development] Eru Ilúvatar:
Tryed, thanks, but nothing changed (and I cleared again Synapse data).

Maybe it's not an issue, but I don't see the point to have twice the same options... If i set firstly "min 1 cpu online at any time" and "max 3 cpu online at any time" and then "min 2 cpu online at any time" and "max 4 cpu online at any time", didn't conflict each other? :confused:
[ONE Original Android Development] robbieast:
How do I get the an kernel updater app to stop showing the notification that there is a new version of 140 even though I am on 140?

Thanks

Sent from my bacONe device
[ONE Original Android Development] DerRomtester:
Yep i think so. https://github.com/DerRomtester/ramdisk_one_plus_one/commit/f5179e7a75490d990ae545d2790c874756889ccb

These were the changes i made. I have only tested the cache partition because i don't want to format internal data media things.
[ONE Original Android Development] nuwan32:
getting a massive wakelock with "nextalarmtracker" and "audiomix" anyone know how to fix this? on v204.

[IMG="asd"]http://i.imgur.com/QsLi8qn.png[/IMG]
[ONE Original Android Development] didicola:
i confirm NextAlarmTracker massive wakelock regarless of rom 5.1 on many roms it appears!
[ONE Original Android Development] ak:
is this kernel or rom wakelock?
[ONE Original Android Development] Spaulding89:
I think rom Wakelock. In BBS it stands under Partial Wakelock.
[ONE Original Android Development] sam razzy:
Can someone post their synapse profile for 204 ?
[ONE Original Android Development] ak:
i think the same :rolleyes:
[ONE Original Android Development] didicola:
it happened to me on two differnet 5.1 roms so probably rom dependent?
[ONE Original Android Development] ak:
I'm a teaser

Look at min freq

Sent from my A0001
[ONE Original Android Development] allanski:
oh my .... cant wait for this. we dont need deep sleep anymore ??

your kernel rocks !!
[ONE Original Android Development] nuwan32:
dam.. that wouldnt cause SOD?
[ONE Original Android Development] ak:
No ... if you don't drink so much :D:silly:

also no glitch with one core and poweramp! so damn ****!
[ONE Original Android Development] nuwan32:
haha cant wait to give it a try! whats the voltage difference from 300mhz?
[ONE Original Android Development] ak:
this is the voltage table for my cpu speed/bin:

qcom,speed3-pvs6-bin-v1 =

< 0 0 0 >,

+ < 69600000 735000 26 >,

< 146400000 745000 36 >,

< 223200000 755000 56 >,

< 300000000 775000 76 >,

but you can find your cpu limits with testing.
[ONE Original Android Development] Poesini:
Can we do this fstab in like, SlimSaber so it can mount if its F2FS or ext4 no matter what, or will it have conflicts?
[ONE Original Android Development] abhi08638:
So let's say we're able to run 600000 for 300mhz. Since we can't go below that voltage, would that freq still help in any way?
[ONE Original Android Development] ak:
Im testing it with music play with screen off and the battery never seems to die ... damn ****! :silly:

freq limiter -> min 69 -> max 729
[ONE Original Android Development] kantjer:
That's not a minimum frequency, thats hibernation :D
[ONE Original Android Development] ak:
if there is any user who is not afraid of danger, I can post the new kernel?
[ONE Original Android Development] kantjer:
bring it on

BTW, new UBER is out. Build 204 with it. It's running so smooooooth
[ONE Original Android Development] Jole7:
Bring the new speed Ak :)
[ONE Original Android Development] ak:
supertest kernel - 69Mhz

only the brave:

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

small changelog:

fastcharge

ovuc min 69Mhz - max 2880Mhz

full changelog:

Project name: AK KERNEL
anarkia1976 - Kernel Version: AK.205.OPO.CM12.1
anarkia1976 - msm8974pro: cpufreq: set safe frequencies at boot time
anarkia1976 - msm8974pro: dts: cpufreq: added new 69Mhz low step
anarkia1976 - msm8974pro: dts: cpufreq: fix voltages related to 146Mhz step
anarkia1976 - msm8974pro: dcvs: increase max dcvs freqs
ak - msm8974pro: dts: cpufreq: added new 146Mhz low step
ak - msm8974pro: dts: cpufreq: replace 268Mhz with 223Mhz step
ak - msm8974pro: cpufreq: ignore rounded calculation for underclock min frequencies
ak - msm8974pro: dts: cpufreq: enable middle steps for CPU frequencies
ak - msm8974pro: dts: cpufreq: enable low steps for CPU frequencies
andip71 - msm8974pro: dts: increase cpu voltags for OC frequencies by 25 mV
anarkia1976 - msm8974pro: dts: cpu overclocking to 2880Ghz
anarkia1976 - msm8974pro: dts: cpufreq: added qcom cpufreq reference table
savoca - msm8974pro: dts: cpufreq: introduce 268MHz clock
anarkia1976 - ak_bacon_defconfig: enable FAST_CHARGE
anarkia1976 - fastcharge: limit the max charge level to 2100 mA
anarkia1976 - fastcharge: backported and adapted for OnePlus One
[ONE Original Android Development] dickenam:
i love danger
[ONE Original Android Development] DerRomtester:
Downloading now this new monster :)
[ONE Original Android Development] ak:
I have push the new code to git my friend! happy testing. :highfive::highfive:
[ONE Original Android Development] cerealguy:
I love 69!! [emoji57] [emoji57]
[ONE Original Android Development] phoenixita:
I'll wait the brave testers lol even if i'm tempted to try this.
[ONE Original Android Development] ak:
or

[YOUTUBE]MJsdZ2FR3WM[/YOUTUBE]
[ONE Original Android Development] chikimonke:
Challenge accepted...

Also, are you going to super charge it further with the updated UberTC as [MENTION=3306843]kantjer[/MENTION] suggested :D

MOAR POWER!
[ONE Original Android Development] ak:
i have merged new uber 5.0 ... official kernel will be compiled with the TC.
[ONE Original Android Development] chachin:
Can you share your settings?
[ONE Original Android Development] kantjer:
Stock only set min. frequency and enabled fast charge.

EDIT: also changed TCP congestion algorithm to hybla
[ONE Original Android Development] Mecca EL:
Outside of the weird Clock divergent after reboot, everything works great.
[ONE Original Android Development] sam razzy:
Which app is that ? :P please let me also view that app.
[ONE Original Android Development] CapnMarius:
AK205 on CM12 official

Damn the latest kernel is running smooth on ma Bacon!

Haven't had a single problem so far!

CM12 official 08-04 nightly

69MHz min - 1190 MHz max

I made a simple profile for it :D

https://www.dropbox.com/s/5bnrkum4dsqf4xa/AK205_smoothAndEfficient.tgz?dl=0

Thanks [MENTION=3685904]ak[/MENTION] for this new masterpiece:cool:
[ONE Original Android Development] mannyalba:
That's what I'm talking about, thx [MENTION=3475639]ak.[/MENTION]
[ONE Original Android Development] NickosD:
Just flashed. I'll report back tomorrow after a long night with -100 at all voltages. I hope it won't get SOD or anything.

Sent from my bacon!!!!!
[ONE Original Android Development] Peri-:
Stand back, fastest computing unit on earth is on its way.
[ONE Original Android Development] CapnMarius:
1 core stuck at 100%

[MENTION=3685904]ak[/MENTION] one core is constantly stuck at 100% load, I have checked my background tasks but nothing is using more than 5%

I have all cores online

69mhz - 1190mhz

edit:

It happens only when I lower the max CPU speed.

No problems with the default settings ;)
[ONE Original Android Development] NickosD:
I lowered it to 1500 and I don't have any issue...

Sent from my bacon!!!!!
[ONE Original Android Development] JaylanPHNX:
Is anyone getting reports of bad call quality from people on the other end? My wife told me it sounded bad, but speakerphone was okay. I tried adjusting mic volume in sound settings, but no good. I flashed back to 140 and she says it sounds fine, now. Can I get a confirmation?

From my SlimTab Pro 8.4
[ONE Original Android Development] fireforhire:
On 205 I just had a random reboot while in call. Back on 140 for now.
[ONE Original Android Development] fiz:ik:
Nice! (10% missing, anybody knows why?)
[ONE Original Android Development] Maestropcxp:
Good kernel (205), but every time i reboot the phone i need set the date.
[ONE Original Android Development] mannyalba:
Well well well, [MENTION=3685904]ak[/MENTION] I think this AK205 is your finest work so far :P., 12.1 Rom by Robbie +Ak205. Keep up the hard work mate.
[ONE Original Android Development] NickosD:
If you sum up all the 0% you'll get the 10% you are looking for. That freqs have still been used, just not enough to reach 1%

Sent from my bacon!!!!!
[ONE Original Android Development] nuwan32:
205 does not have the new ubertc?
[ONE Original Android Development] chenrp:
Can we set lower voltage than 600mv?if not, what is the added value of using such a low frequency?
[ONE Original Android Development] ak:
search the thread for your answer

post log otherwise the problem isnt the kernel

the problem is bad setting you have to tune cpu/cpu-boost and hotplug drivers if you want to go lower

not safe

no
[ONE Original Android Development] ak:
no problem for me ... slimsaber + cm12 modem , but i need some more testing
[ONE Original Android Development] chenrp:
Not safe? So what is the added value of using such a low frequency?
[ONE Original Android Development] funCrash93:
hey, speed and pvs are the same as mine :D
[MENTION=3685904]ak[/MENTION] do you use UV.?

does your minimum voltages correspond with the default in the kernel.?
[ONE Original Android Development] ak:
I'm using stock

Sent from my A0001
[ONE Original Android Development] stab244:
Less power consumed. Voltage isn't the only thing that dictates how much power is used.
[ONE Original Android Development] isoladisegnata:
Tooo much battery drain sistem Android with nightly...
[ONE Original Android Development] sam razzy:
Battery draining quickly overnight, I'll report back using this for one more night
[ONE Original Android Development] ak:
These posts lead nowhere ... i do not have any drain with SlimLP.

Please test it with default frequencies before commenting.

Also, You have to collect and post informations about your kernel configuration.
[ONE Original Android Development] pSyCh¤_O_O:
[emoji108]
[ONE Original Android Development] Genericxx:
Don't you said that you need a rest from SlimLP a few days ago? :P
[ONE Original Android Development] Genericxx:
Just curious why SlimLP and not SlimSaber, which is compiled with UBER-TC.
[ONE Original Android Development] indian84:
Is that MIUI layer theme?

Sorry for OT Master...
[ONE Original Android Development] chenrp:
Can you please explain?
[ONE Original Android Development] ak:
what?
[ONE Original Android Development] kantjer:
@ak, 205 is running fabulous :good:

Nothing to complain about
[ONE Original Android Development] simarilon:
Just to let you know:

I had the same problem, the phone call sounds choppy on the other side.

--> SlimLP 1.11. , new Oxygen Modem and Ak205.

I flashed back to 140. I will test now.
[ONE Original Android Development] Genericxx:
[MENTION=3685904]ak[/MENTION] Dude, according to your bias to Metal Music you definately want to watch this :D

I love this Guy... :good:

KLICK

Edit: YT-Tags won't work. Suxx :(
[ONE Original Android Development] chenrp:
Can you please explain?

And another bug... Really slow charging even using wall 2.1a charger.
[ONE Original Android Development] DrNinjaa:
Did u forgot to kiss ur phone before charging?? ;);)

I did and its charging the pace it usually do... :)
[ONE Original Android Development] ak:
Can you test with the stock modem?
[ONE Original Android Development] ak:
date and whatsapp

NB for ALL:

the problem with the date and whatsapp is related to google services/application, not rom or kernel.

I have the same problem with my Galaxy S3 Mini with stock rom and kernel.

Thanks a lot

Ak
[ONE Original Android Development] :
Battery draining? :D

Check your apps. It's not the kernel.

http://up.picr.de/21546797ua.jpg
[ONE Original Android Development] simarilon:
Dear AK I tested it right now with the 140 Kernel, there is everything fine.

I am at work right now. I will try the test with 205 and stock modem after work. Sorry :o

I hope this is ok...

Best regards
[ONE Original Android Development] ChrisAr:
I think Input Boost Drivers are interfering somehow with min max values...I set minimum @69Mhz and it is working... But when I return to synapse I see this (check attachment).

Keep in mind that the frequency does not change if I don't hit apply again.

Kernel Version: 205

Firmware: 9-4-2015

ROM: CM11S latest

Installation: UKM uninstaller, install, wipe dalvik cache, etc etc
[ONE Original Android Development] kantjer:
If that's the case I think it's a Synapse issue. I'm using Kernel Adiutor and for me minimum frequency stays nicely at the set 69Mhz (even after a ROM a ROM flash)
[ONE Original Android Development] abhi08638:
I can confirm, it happens when you set the CPU input boost to a high value like 1000ms
[ONE Original Android Development] NickosD:
No problem all night. Alarms triggered successfully ^^

Sent from my bacon!!!!!
[ONE Original Android Development] sam razzy:
Okay, I'll try and report back
[ONE Original Android Development] demon507:
OC??

Sent from ONEPLUS ONE SlimAK'ed
[ONE Original Android Development] JaylanPHNX:
I hope it's not the modem, cause the new one actually improved signal stability for me. But I would think if it were the modem, being on speaker vs ear piece wouldn't make a difference.

From my SlimTab Pro 8.4
[ONE Original Android Development] ak:
with stock modem and the latest slimsaber i dont have problem with phone quality.
[ONE Original Android Development] Formhault:
You mean the problem where WhatsApp doesn't receive messages in time; you have to open it up to see them coming in? If so, same happens here, on CM11S with Boeffla kernel.
[ONE Original Android Development] kantjer:
Just finished a call and the sound was crystal clear.

I'm using the Oxygen 1.0 modem.
[ONE Original Android Development] :
I had that on certain gapps with whatsapp, now using paranoid full I don't get that anymore.
[ONE Original Android Development] JaylanPHNX:
I'll do some more testing after work, see if I can't narrow this down more. Thanks, guys.

It's baconnn!
[ONE Original Android Development] simarilon:
Oh I made an mistake, I was on 204 not on 205 with the choppy phone sound on the other side.

Ok once again:

With 204, Oxygen modem and SlimLP 1.11 I had this choppy sound by phone calls.

I hear everything clear but my partner has this choppy sound.

I reverted back to 140 and everything is fine. UNtil now I did not have the time to test with stock modem and 204.

Sorry for the mistake in the kernel version :eek:
[ONE Original Android Development] Formhault:
Well, CM11S has its own Gapps... since CM11S is considered stock, I'd say those Gapps are proper. And even so, I do get delayed WhatsApp notifications (if at all). Or at least used to... now, they seem to cone in just fine.

I was using Resurrection Remix + PA Full Gapps yesterday and what do you know : same problem :laugh: .

Date & time was correctly set, though.

Anyway, it's definitely not kernel related. :p
[ONE Original Android Development] kalpik:
That's not entirely true. The date resetting to 1970 happens only on this kernel. If I use reader kernel, I don't get that problem.

Sent from my A0001
[ONE Original Android Development] Formhault:
Speaking of modems... Does the modem have anything to do with Wi-Fi behaviour & such? Or that's solely the kernel's job?
[ONE Original Android Development] kantjer:
Not 100% sure, I know for the S4 the modem influenced WiFi performance also. But this is a different beast.
[ONE Original Android Development] ak:
@kalpik

Strange, i have update google apps on my s3 mini, used at work and bam whatsapp date error.

ps:

it probably related to cm12.1 not update to last aosp lollipop?, or its related to outdated whatspp?:

staging: Remove the Android alarm-dev driver

The functionality provided by the Android alarm-dev driver
should now be present in the timerfd interface (thanks to
Greg Hackmann and Todd Poynor).

As of Lollipop, AOSP can make use of the timerfd if
alarm-dev is not present (though a fixup for setting the
rtc time if rtc0 isn't the backing for _ALARM clockids has
been applied post-Lollipop).

Thus, we should be able to remove alarm-dev from staging.

Cc: Greg Hackmann <ghackmann@google.com>
Cc: Elliott Hughes <enh@google.com>
Cc: Todd Poynor <toddpoynor@google.com>
Cc: Android Kernel Team <kernel-team@android.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
Acked-by: Mark Salyzyn <salyzyn@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Change-Id: Ia905d4b809cc1614ddde01ccb791fc56ac292fa8
[ONE Original Android Development] kalpik:
No idea :(

Seems to affect only those who have set the phone to get time from network. It seems like since it takes some time for phone to catch network, till then, the time remains in 1970.

Most kernels I tried on 5.1 have this issue. Only render kernel seems to not have it. Maybe you can compare what's different there?

Thanks for looking into it :)

Sent from my A0001
[ONE Original Android Development] acuicultor:
Why you sentence that without have proof? I have this bug with other kernels too, included render.

This bug occurs only in certain Roms, didn't know the culprit but I know ak kernel isn't it.
[ONE Original Android Development] kalpik:
Is it so? I seem to have not have this issue on render kernel. Are you sure we're talking about the same issue? I'm talking about the issue where at boot, the phone date seems to be set to the year 1970, and Whatsapp complains that date is wrong.

Sent from my A0001
[ONE Original Android Development] demon507:
Using slimsaber and render no issue here.

Yesterday was on ak204 and the date issue with whatsapp was there even the facebook refused to open in browser saying the date and time doesn't match.

I disabled network time and manually set time and everything got ok.

Didn't tried 205 so don't know if fixed or not.

I don't know what's the issue but reporting things as they are on my end. Hope it helps.

Sent from ONEPLUS ONE SlimAK'ed
[ONE Original Android Development] dejavx:
Same problem with every boot and reboot...

OnePlus 1 by T4p4t4lk
[ONE Original Android Development] Shadowghoster:
I'm on latest slimsaber too with ak205 and never had any date and time problems (even not with 203 or 204).
[ONE Original Android Development] nickporwal:
Same problem came on nexus 5 long time back. It was problem related to time service in ROM.
[ONE Original Android Development] etiii:
hi :D

may i ask for an advice .. i'm currently running SlimSaber ROM(latest version).. if i want to flash AK kernell, do i need to wipe everything? or can i just re-flash the latest version, and than(without reboot) flash over the kernel and needed zips?

also.. what partitions should i backup when flashing a kernel? :)

Thanks for the help :)
[ONE Original Android Development] NickosD:
Just flash the zip. If you want to update your rom then just flash the zip.

Sent from my bacon!!!!!
[ONE Original Android Development] etiii:
i just flashed AK... and idk if its just me or something.. but i feel an improvement.. not sure tho.. :D

so far it feels great, and love all the settings :) why didnt i use custom kernels before? .. haha
[ONE Original Android Development] chenrp:
Stab, I'm still waiting for your explanation about this statement...

What are you gaining if you use the same voltages but lower frequency?
[ONE Original Android Development] stab244:
Am I not allowed to sleep...

Anyways, power consumed by the cpu is dependent on both voltage and frequency. If lower either one power consumed is lower. Not much more to it
[ONE Original Android Development] HamsterHam:
Hey @ak

Using [MENTION=3306843]kantjer[/MENTION]'s SlimSaber build which uses your kernel.

The bug report has some kernel issues.

I have attached it so you can take a look.

Thanks.
[ONE Original Android Development] sam razzy:
What do you mean stock modem ? Is that alpha or the new oxygen Os modem ? Let me know which our master use :)
[ONE Original Android Development] chenrp:
Cant see how frequency is related to power... If using multiple frequency on same voltages i prefer using the highest frequency available.

Maybe it is minor if so.

And no! You are on xda! You cant sleep! It is not allowed! ?