yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] magnamentis:
my workaround

this should not sound as THE solution but it's A solution for me:

a) min CPU Frequ 422MHz + interactive gov + MPD +Touch Boost Hysteris Value set to 0 ( worked well with 2 also but went to max to be on the safe side )

b) Sync Threshold 1728MHz + Input Boost 1728MHz

c) overvolt bei 0.25 ( did not test lower values because this works and i have 1% in 9 hours over night now, before recent cm updates it was 2% )

d) Read Ahead Buffer 2048 + deadline + Random + RQ Enabled + GPU Minimum 330MHz + GPU Performance Gov + Z-RAM 200MB + FSYNC Disabled + No Temp Throttle + VM Heapsize 768MB

not all of the settings influence the responsiveness of the display while in deep sleep but i think the min frequencies of gpu and cpu and the boost values do, as well as the voltage. you can play a bit with the settings to find out which-ones you really need but i would start with those, as [MENTION=3685904]ak[/MENTION] mentioned, raise the frequencies, it's included here.

for those being afraid for their battery, no huge impact here because while at work the frequencies are well above minimum thus does not matter and in deep sleep cpus are mostly off-line, so again does not matter. as i said this is not meant as a once and for all and for everyone solution, so i'll not take part in any back and forth arguing on singled out specific values i mentioned above. just wanna assist those who ask, to get mostly rid of the touch lag.
[ONE Original Android Development] ak:
You have to tune also the governor and disable multicore power saving ...

ak@a0001
[ONE Original Android Development] magnamentis:
just to let you know :)

not meant to contradict but my responsiveness is very well now albeit i have multicore powersaving set to aggressive.

nevertheless i changed it now to see the difference, thanks for the tip.
[ONE Original Android Development] Saythis:
Proof/link?
[ONE Original Android Development] magnamentis:
hi

thanks for the above quoted PM, i'm gonna answer this here because it might be of interest for others.

as i understood MPD (MPDecision) and other setting which do the same thing are not compatible and should not be used at the same time.

since i'm not a kernel dev i would let [MENTION=3685904]ak[/MENTION] confirm that this applies to AutoSMP as well, it says "replacement for MPD...." so i suppose so.

hysteris value is under Touch Boost next item, no idea if it's working under MPD but if yes i set it to lowest for faster hotplug response, if it's not functional under MPD it does not do any damage :) again if [MENTION=3685904]ak[/MENTION] could clarify this specific setting whether it works under MPD. i'm not sure because it's under Intelliplug main title and that is disabled while using MPD (should be in your case as well)

as for FSYNC it's in the "MISC" Section above "USB Fast Charge" while read (not radio) ahead buffer size is in the I/O section first item "Read-ahead Size"

generally i recommend to learn about the possibilities of your kernel by going through all the menu items in each tab and google what you don't know yet, there will be little left unexplained :)
[ONE Original Android Development] ak0r:
How to change color profiles? Default settings are bit saturated for me.
[ONE Original Android Development] Genericxx:
Change it via Synapse?
[ONE Original Android Development] madsponge26:
Flash kernel. Uninstall UKM. Install UKM. Reboot and set your settings!
[ONE Original Android Development] ak:
i'm a teaser:

https://github.com/AK-Kernel/AK-OnePone/commits/ak-12.1-official
[ONE Original Android Development] niko2931:
Oh you teasing, you!! :victory::victory:
[ONE Original Android Development] JoyFull117:
I did and it works but now i have a heavy battery drain oO is it normal? Can i use another TCP congestion?
[ONE Original Android Development] bombadier:
Minx :D
[ONE Original Android Development] cerealguy:
Teasing is your way of life! [emoji13] [emoji13]

Sent from mine BlissPopped 1+1, pumped up by Ak Kernel!
[ONE Original Android Development] xlollomanx:
Only I noticed an excessive battery drain on lastest cm bacon firmware (19-03-2015)?Deep sleep is OK but when I use the phone the battery % decreasly very rapidly. Reverted to older 09-02-2015 and battery drain seems returned normal. I' m on lastest cm11s build.

Sent from my Oneplus One
[ONE Original Android Development] sabrefresco:
Goddamit ak! I had to change my pants:crying:
[ONE Original Android Development] Genericxx:
You can try. Westwood was afaik default at KitKat and before, while Cubic is Lollipop defaut Congestion when driving stock kernels. Dunno how other Congestions work out. If you want to solve your battery drain, try monitor using Better Battery Stats or similar Apps.
[ONE Original Android Development] cerealguy:
Here you can get more informations about TCP algorhitms

http://androidmodguide.blogspot.it/p/tcp-algorithms.html?m=1 [emoji106] [emoji106]

Sent from mine BlissPopped 1+1, pumped up by Ak Kernel!
[ONE Original Android Development] black.ic3:
:good:

Waiting to try out with CM12.1 :D
[ONE Original Android Development] yonoshiro:
I have no idea why but on 136, slim governor was smooth whilst interactive pro was choppy and now on 137, slim governor is choppy and interactive pro is smooth XD. It isn't an issue, it just cracked me up. Lol!

Thanks again [MENTION=3685904]ak[/MENTION] for your incredible work. Also, stop teasing us with your upcoming cm12.1 build you minx! The anticipation is killing me! :D
[ONE Original Android Development] acuicultor:
Just fyi ;)
[ONE Original Android Development] ahepas:
Try the 210315 firmware...it is working great here
[ONE Original Android Development] Jameswgm:
You got a link for that, I've searched xda on my phone but got nothing?
[ONE Original Android Development] NickosD:
See at the links of blisspop rom.

Sent from my bacon!!!!!
[ONE Original Android Development] MBurns2:
latest uber release + conservative governor is awesome! i even reduced touch boost and hotplug but i cannot see any lags.. awesome works ak! Thanks a lot
[ONE Original Android Development] chikimonke:
FYI, the 0321 firmware has the same modem as the 0209 firmware. In fact, 5 of the 8 files are the same as the 0209 firmware. The only ones that changed are sbl1.mdn, rpm.mbn and emmc_appsboot.mbn. Never really seen a good explanation as to what the 8 different files all do other than NON-HLOS.bin (modem) and logo.bin (1+ boot logo).

---------- Post added at 01:10 PM ---------- Previous post was at 12:56 PM ----------

There was a brief moment in time, 0319-0320, that had a new modem among other things, and it even improved my indoor LTE signal quite a bit, but it broke the prox sensor, even on stock CM12 builds from those 2 days, so they reverted back to the old modem. I'm guessing we get a new working modem in a week or so when the official CM12S and OxygenOS releases happen...
[ONE Original Android Development] ahepas:
Just in case...

https://docs.google.com/file/d/0B5vLL639Ya_LWWxPR0hZb2o4WnM/edit?usp=docslist_api
[ONE Original Android Development] ak:
thanks guys for support.
[ONE Original Android Development] TheKnux:
[MENTION=3685904]ak[/MENTION] for some reason I am having huge lag and freeze ups using the 137 kernel. 136 was like it as well but not this bad. Using BlissPop 2/22 wiped system, cache, and dalvik. Flashed rom, gapps, kernel, ukm, xposed zip, and viper4android. I've tried tweaking every setting in synapse and nothing seems to work.

What settings are working for you?
[ONE Original Android Development] dickenam:
I hope you mean 3/22. If not, month old ROM is the problem...
[ONE Original Android Development] TheKnux:
Yeah, that's what I meant. My bad.
[ONE Original Android Development] dickenam:
No worries. Maybe try ROM Gapps kernel ukm. Let it boot, then all your other stuffs afterwards?
[ONE Original Android Development] TheKnux:
Dude, you're the ****. I don't know why I never thought if that. I was about to throw this thing against the wall. Thanks so much. ?
[ONE Original Android Development] cryogeno:
@ak,

I have a big problem with your kernel: it fails to discharge my battery!

Do you need kmesg?

[emoji1]
[ONE Original Android Development] kalpik:
Can reproduce this bug myself. 2 hours out of the charger, with 40 minutes screen on, and battery still at 100%! Will this cause harm to my battery? Worst kernel ever :P
[ONE Original Android Development] niko2931:
Yea well nobody can be as perfect as my old htc one m7, that runs dead in a couple of hours.. ;):good:
[ONE Original Android Development] gianton:
My HTC One m7 running strong here after 2 years with my limited usage with it I get 2 days total time.
[ONE Original Android Development] NickosD:
Actually you may need to reset the battery stats. ?

It will soon start to drain like crazy just because it was at 100 for that long.

Sent from my bacon!!!!!
[ONE Original Android Development] niko2931:
Well my HTC one, Isn't really good anymore.. Was close to loose it, from dropping it on a boat :good:
[ONE Original Android Development] kalpik:
Haha! I know about battery stats. It didn't drain like crazy. Still going strong :D

Sent from my A0001
[ONE Original Android Development] NickosD:
It will happen eventually ^^

Sent from my bacon!!!!!
[ONE Original Android Development] Beaster:
@ak,

Latest release seems to have fix the sleep of death issue i was having since v126.. Not sure what was causing this.. I switched kernels so i missed a couple of your latest releases, so i dont know which version solved this issue!

Thx!
[ONE Original Android Development] niko2931:
Horrible spelling on my part, but you guys get the jist of it :good::good:
[ONE Original Android Development] ak:
Do you have changed also the rom ver?
[ONE Original Android Development] Beaster:
Yes.

I usually flash the current cm12 nightly at the time i flash a new version of a kernel. Currently running 22/3 nightly.

Thx again
[ONE Original Android Development] ak:
Because i never exp a sod, the problem was related to an old rom nightly.
[ONE Original Android Development] black.ic3:
Runs very good with CM12.1

Thanks ak :good:
[ONE Original Android Development] ak:
Thanks a lot I have see you have doing a good job with your cm12.1

Sent from my A0001
[ONE Original Android Development] dickenam:
[MENTION=3685904]ak[/MENTION] is there a 138 for CM12? Github seems to say yes. Your site, newest version is 137.

Thanks!

ALSO: I have that issue with the inability to edit min_sample_time in the Conservative gov to 10000 from 50000
[ONE Original Android Development] JoyFull117:
Thx for your help!

Now with the latest version 136 and the Cubic TCP it's working like a charm and battery life is also awesome =)
[ONE Original Android Development] chikimonke:
Why not version 137? :D

---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------

Are you using the latest version of UKM from [MENTION=3685904]ak[/MENTION] ?
[ONE Original Android Development] dickenam:
I am! 3.8.1.2 Special
[ONE Original Android Development] JoyFull117:
Sorry i use 137. forget it^^
[ONE Original Android Development] chikimonke:
Try this. Clear Synapse data, then reboot to recovery, flash the UKMv2 uninstall, flash AK137, flash UKM 3.8.1.2 SE, reboot. Now see if you can make the change.
[ONE Original Android Development] dickenam:
good plan, should have tried that. will do so and let you know the result.
[ONE Original Android Development] indian84:
Just to break 14 hours of silence in the thread.

It shows no issues for people to report..

[MENTION=3685904]ak[/MENTION] rocks..
[ONE Original Android Development] ak:
\m/

Sent from my A0001
[ONE Original Android Development] gargeya_369:
True
[ONE Original Android Development] Nos_20:
One and a half hours on battery....

Straight line

Lol!!
[ONE Original Android Development] g.ott:
\m/
[ONE Original Android Development] demon507:
Is it me..or yours actually went up? Lol.

AK magic.
[ONE Original Android Development] Nos_20:
It did didn't it!

Must've thought only been on battery for an hour and a half, get yourself back to 100% :thumbup::thumbup::thumbup:
[ONE Original Android Development] chikimonke:
Hey all, just a quick semi-related issue. The primary SlimLP maintainer for our beloved 1+1, [MENTION=4911350]RobbieL811[/MENTION] , has managed to drop his phone, breaking the screen and the digitizer. If you've been enjoying Slim on any of your devices and have always meant to donate one of these days, now would be a great time to throw a couple $ Robbie's way. Thanks!
[ONE Original Android Development] ak:
its @RobbieL811 time.

ps+

twitted!

ps++

http://xdaforums.com/showpost.php?p=59700546&postcount=2119
[ONE Original Android Development] krxz:
Is there a way to add UKM in a backup script so that I don't have to reflash it everytime I flash a Rom update? Tried adding

etc/init.d
etc/init.d/UKM
xbin/uci

to gapps-sh or backup-sh but neither of them worked. Always got "No UCI Support" in Synapse
[ONE Original Android Development] TheWilkieWay:
Just hitting 'restart synapse' in synapse settings, then closing it manually does the trick for me
[ONE Original Android Development] yonoshiro:
I haven't used his ROMs as yet but I respect him for all the time and effort he puts into his craft and his generosity in sharing with the community. As such, I donated towards the cause and I urge my peers here on xda to do so as well. These devs have lives and families of their own and yet they still make personal sacrifices to give us all the android goodies we love. The least we can do is give them something back! XDA is more than a forum, it is a family. Let's help our brother out! :)
[ONE Original Android Development] jukiewalsh:
[MENTION=3685904]ak[/MENTION] just sent you a small donation in addition to robbie. Thanks for this awesome kernel!

1D32097947912000B
[ONE Original Android Development] ak:
yesssssssssss thanks a lot! :)
[ONE Original Android Development] minieod:
Read in another thread that this is working on 12.1 / 5.1

Can anyone confirm? Hard to search numbers on here to find info on it.

Thanks
[ONE Original Android Development] ak:
yes it work.
[ONE Original Android Development] jenaplisken:
Pure cm11s roted by Calkulin with AK137 Stock values..... This is the first charge cycle .... Good job
[ONE Original Android Development] andyfmking:
Sleep of death

My screen doesn't turn on after leaving the phone for a while (like over night)

OK AK 137 and temasek v9.2 , always getting this issue with custom kernels except for stock, nice screen color calibration and battery life, but its useless having a good looking phone that doesn't turn on when needed. Going back to stock kernel. Wish it had same screen color calibration
[ONE Original Android Development] byAidan:
Post a log next time it happens and maybe AK could look into what is causing it so you don't have to go back to stock kernel ;)
[ONE Original Android Development] andyfmking:
Thanks for the advice ? , Does the log stay after a reboot? Because I have to reboot before the phone becomes usable,
[ONE Original Android Development] ak:
SOD can't be logged, but the problem isnt related to kernel.
[ONE Original Android Development] jgcaap:
Where can I get that?
[ONE Original Android Development] bombadier:
http://xdaforums.com/oneplus-one/general/guides-mmwolverines-opo-mods-tips-tricks-t3027926
[ONE Original Android Development] jgcaap:
Thanks. You guys notice improvements?
[ONE Original Android Development] ahepas:
Not sure but it works nice until now...
[ONE Original Android Development] Aditya Srinidhi:
Try a clean flash with temasek 9.3v2 ub, can't be the kernel, this kernel is SMOOTH af and I don't wanna switch ROMs because some are not compatible with this kernel, have no issues whatsoever with anything :o
[ONE Original Android Development] fiz:ik:
Actually this kernel should work with any ROM due to its universal RAMdisk (Anykernel format). It works even on CM11 ROMs with some tricks
[ONE Original Android Development] Aditya Srinidhi:
Yeah, but I have a lot of bootloops when I have synapse enabled on some other ROMs :/ not the kernel, but still isn't as good as it is for me on temasek
[ONE Original Android Development] casshern94:
on temasek v9.3 sabermod and ended up bootloop while using ak kernel 137.

i did tried 0209 and even the 0315 cm12 firmware but still no luck.

did i missed anything?
[ONE Original Android Development] ak:
The problem isnt related to firmware, but can it be related to ramdisk.
[ONE Original Android Development] casshern94:
thank you mr ak for reply.

so,does that mean the rom and the kernel isnt compatible ?
[ONE Original Android Development] funCrash93:
have you tried latest recovery version.?

maybe your recovery is outdated (as I can remember some members having issues with old TWRP as for example), my guess ;)
[ONE Original Android Development] krxz:
Rom and kernel fit completely perfect :)
[ONE Original Android Development] IllUMINATUz:
Mah Battery!!! Almost 2 days..

Muhahahaha.... Lovely.. never had THAT kind of battery in ANY android!!!

You Are Awesome @ak
[ONE Original Android Development] reaper000:
Using Temasek 9.3uber and AK137 atop firmware 20150321 -- absolutely no issues whatsoever. I'd check the MD5 of each file. Maybe you got a bad download?
[ONE Original Android Development] sam razzy:
Sorry.. I was on a vacation. so I couldn't read all the comments on this thread. So please if you don't mind can someone tell whether this supports the cm12.1 unofficial builds ?
[ONE Original Android Development] indian84:
Nandroid - Flash ak. Let everyone know.

I am sure it will work..

I tested with 5.1 TN ROM who is based on CM12 and it works..
[ONE Original Android Development] flolep:
I tried ak 137 with omni 5.1. Doesn't work. Well. No big deal. I guess I will wait for temasek cm12.1. Thx ak for your hard work!
[ONE Original Android Development] indian84:
None of the CM12 kernels will work on Omni. Omni uses different device tree to build ROM for OPO.
[ONE Original Android Development] flolep:
Oh. I didn't know. Thanks for answer :)
[ONE Original Android Development] jocarog:
I'm on [MENTION=5291611]CraZY_BoY^[/MENTION] unofficial 12.1
[ONE Original Android Development] mak725:
AK137+Temasek Uber V9.3 great combination :D:D
[ONE Original Android Development] flolep:
Yeah I liked it too. But I went to 5.1 as soon as I could because I had a bug with my contacts that Google only corrected into 5.1. Omni unofficial was the first 5.1 rom for One Plus One... So... But. Well. Let's try another one! :)

Have a good day all!
[ONE Original Android Development] logikism:
I always get boot loop, still..... Actually with all the kernels I try
[ONE Original Android Development] casshern94:
just to share my experience.

my recovery outdated XD

now im using the latest one and everything works like a charm :)
[ONE Original Android Development] zoological:
testing ak 137 with latest Uber temasek: it works like a charm
[ONE Original Android Development] redline2097:
I think this is awesome:
[ONE Original Android Development] Thunderbolt:
which rom? stock settings?
[ONE Original Android Development] issawillwin:
Can't find any Q&A thread about this kernel so i'm asking this here . why do you guys choose UBER toolchain instead of sabermod or Linaro. Is UBER giving more GPU performance than other toolchains? There isn't any informations about it that i could find, video review neither.
[ONE Original Android Development] CounterC:
That's actually very bad battery life. Your Google services is keeping your phone awake for 7 hours while your screen on is only 2h39...
[ONE Original Android Development] gianton:
It's the opposite.
[ONE Original Android Development] redline2097:
This is not my screenshot, it's from Exodus thread. Specs: Exodus, stock settings, stock kernel and greenify.
[ONE Original Android Development] CounterC:
How can a phone be less awake then the screen on time?
[ONE Original Android Development] gianton:
That's how the app shows its stats.
[ONE Original Android Development] CounterC:
OK man. These are my stats.

As you can see the screen has only been on 4h52min. The remaining 1h30 the phone is awake by other wakelocks...
[ONE Original Android Development] gianton:
Different apps that show the stats, that's all. BetterBatteryStats and Gsam Battery Monitor show the stats differently.
[ONE Original Android Development] EdgA#1:
In The g+ community from uber u can find infos

https://plus.google.com/+ChetKener/posts/YzMJEkzPQgp
[ONE Original Android Development] 1ceb0x:
same here. the only kernel that does not gives me a bootloop is boeffla.

actually with AK and Render kernel, I cannot even get passed the 1+ logo but dunno why.
[ONE Original Android Development] NoSpamDan:
Sounds like incorrect firmware maybe...?
[ONE Original Android Development] TheKnux:
Anyone getting splash screen reboots after flashing BlissPop 3/28 build and ak 137 kernel?
[ONE Original Android Development] MBurns2:
Which rom my friend?

I use slimsaber and i can install all kernel.
[ONE Original Android Development] jgcaap:
Is it uber tc good?
[ONE Original Android Development] 1ceb0x:
I was on the february one and i just tried the 21.03 firmware but with same result.

darkobas, slimsaber, slimLP, cm12 nightlies, blitzrom, xenonhd...
[ONE Original Android Development] poondog:
Try search the thread for uber, there was a discussion a few weeks ago

Btw you won't find videos on toolchains :)
[ONE Original Android Development] troyolson92:
Synapse breaks my WiFi. I upgraded to new 5.1 uber rom. And Wi-Fi worked great. Once I enable synapse, the check mark, it breaks Wi-Fi. All latest, 137, ukm, etc
[ONE Original Android Development] DrearierJester1:
Force turn off your phone for 2 mins and boot it up again and it should boot normally.

Im actually having this issue even now but doing so resolves the issue.
[ONE Original Android Development] jayaraj.chinna:
I am on Blisspop March 25 build now..clean flashed from March 10 build actually (With new updated firmware)....

When i was on Mar 10 build i was using AK Kernel (AK.127) it was working perfectly and after clean flash to 25 build and flashed AK 137 latest and UKM and rebooted the mobile and it always going to bootloop after flashing kernel.... (When i clean flashed again and on stock kernel ROM works fine)....

Is there anything that this bootloop is due to new firmware along with AK Kernel ??? I tried with earlier versions of UKM also...Same bootloop is happening for me...Is it that problem with UKM or something else???Any one facing the same problem??
[ONE Original Android Development] Thunderbolt:
Somebody try this kernel with euphoria?
[ONE Original Android Development] aamitabh28:
Yes since day 1

Works like a dream
[ONE Original Android Development] Thunderbolt:
Stock settings bro?
[ONE Original Android Development] 1ceb0x:
wow man... this actually worked. thanks a lot dude! now i can run this masterpiece on my opo once again!
[ONE Original Android Development] meetpatel:
Yes,from v137 online. Works without any issues.
[ONE Original Android Development] Thunderbolt:
Can You compare IT with stock euphoria kernel?
[ONE Original Android Development] indian84:
This is subjective. No one can compare ROMs and Kernels for you. You have to try and find out..

You can always dirty flash ROM to have stock kernel if you don't like ak.

Which I doubt will happen...
[ONE Original Android Development] ak:
Why do you want to compare two totally different kernels?
[ONE Original Android Development] Thunderbolt:
Because usually euphoria work better on the stock kernel and im interested.
[ONE Original Android Development] kantjer:
Then compare them and make your choice. Don't ask others to do it for you
[ONE Original Android Development] Thunderbolt:
I asked because maybe someone did it. this test take some time, thats why. I dont ask to do it instead me so relax and take your breath.
[ONE Original Android Development] meetpatel:
If you are sure and interested in stock then why are you asking? Both kernel are totally different. Ak provides more functions then stock.