yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] abhi08638:
Re: [KERNEL] [04/03] [3.4.106+] [SM4.9] ☆ AK ☆ [v.123]

Yes, that one. Let me try reinstalling synapse

Edit: nope still didn't work, are you on the latest version of synapse?
[ONE Original Android Development] pcarenza:
Boot loop here as well
[ONE Original Android Development] :
I can set MSM Limiter with .123 + Synapse 0.40 + UKM 3.7.1b1
[ONE Original Android Development] DominiCOne:
Sure but MSN limiter is missing in UKM 3.8.1
[ONE Original Android Development] abhi08638:
More Amoled color profiles
[ONE Original Android Development] ak:
wow .... thanks a lot.! :silly:
[ONE Original Android Development] chikimonke:
Liking your extreme AMOLED profile, thanks!
[ONE Original Android Development] ak:
Op updated

[ KCAL COLOR PROFILES ]

You can set these settings with synapse.

Infos: Link

thanks a lot @savoca

Cool Amoled Style:

Colors: 256,256,256

Min: 35

Contrast: 258

Hue: 0

Saturation: 275

Value: 251

thanks a lot @abhi086387

Warm Amoled Style:

Colors: 253,246,243

Min: 35

Contrast: 258

Hue: 0

Saturation: 275

Value: 251

thanks a lot @abhi086387

Extreme Amoled Style:

Colors: 256,256,256

Min: 35

Contrast: 264

Hue: 0

Saturation: 290

Value: 242

thanks a lot @abhi086387
[ONE Original Android Development] Mayex:
Will they recover it in future?
[ONE Original Android Development] chikimonke:
Yes http://xdaforums.com/showpost.php?p=59219781&postcount=2650
[ONE Original Android Development] cerealguy:
Nope... 3.7.1b1

Great! Thanks for sharing! I really love mine OnePlus Galaxy One! [emoji1]

Sent from mine BlissPopped 1+1, pumped up by Ak kernel
[ONE Original Android Development] azsl1326:
Updated to Temasek's 8.3 and it's running now.

Thanks!
[ONE Original Android Development] abhi08638:
Cool Amoled should be

236 248 256
[ONE Original Android Development] NickosD:
Anyone can confirm that 123 is working at stock rom after flashing cm12 firmware?

Sent from my bacon!!!!!
[ONE Original Android Development] madsponge26:
Im using kitkat so i think it is working in cm12 nightlies

Sent from Bacon Machine
[ONE Original Android Development] NickosD:
Huh?

Sent from my bacon!!!!!
[ONE Original Android Development] Stylo King:
[MENTION=3685904]ak[/MENTION] All of a sudden this problem is pursuing a lot.

When I click on X on synapse ( to cancel the settings) device reboots itself.

It is now happening again and again.

I have attached a logcat via pastebin http://pastebin.com/NqzC9MuZ

Hope this helps in finding out the culprit.

Rom - Euphoria OS

Kernel - AK v122

Sent from Blisspop's Lollipopified Bacon
[ONE Original Android Development] expiredd:
CPU:

Min CPU freq: 146

Max CPU freq: 1958

CPU boost: disabled

Governor: smartmax

Hotplug:

Intelliplug: Enabled

Intelliplug profile: Conservative

CPU VOLT:

-75

I/O:

Read-ahead Size: 1024

Scheduler: sioplus

GPU:

GPU Max freq: 462

GPU Governor: powersave

BUILD.PROP:

Wifi scan interval: 300

Don't forget Greenify and Privacy guard :good:
[ONE Original Android Development] kd8bny:
The x doesn't cancel settings. It reloads the last saved. Which are different then the default at boot. Kinda confusing
[ONE Original Android Development] chikimonke:
Hey [MENTION=3685904]ak[/MENTION] , [MENTION=1228651]fusionjack[/MENTION] has an interesting new feature on his rom called Live Display, which looks like it could be fun to play with. Says the kernel needs Live Display commits though. [MENTION=4911350]RobbieL811[/MENTION] would need to add support to SlimLP as well, but you three seem to enjoy one another's company. What say you AK and Robbie? :D
[ONE Original Android Development] Spaulding89:
Man you are fast I wanted ask the same lol[emoji111]

Sent from my Slimlollipopped Bacon with AK
[ONE Original Android Development] RobbieL811:
Yes. I would probably need to add support in settings, but I'm wondering if [MENTION=4316709]savoca[/MENTION] commits to change color already cover what CM just implemented???
[ONE Original Android Development] chikimonke:
That's why I summoned you all, so it can be talked out :D :good: :highfive:
[ONE Original Android Development] abhi08638:
Looks like the only thing that need to be implemented is the replacements for the adaptive display and and sunlight enhancement
[ONE Original Android Development] chikimonke:
There seem to be color controls at the bottom of the screenshot too. They mention contrast, hue, saturation and so on.
[ONE Original Android Development] abhi08638:
These are already implemented with the new kcal update, which is why I made those Amoled profiles
[ONE Original Android Development] savoca:
LiveDisplay's RGB backend is literally the same as KCAL's. The only difference is that LiveDisplay scales from 0->32768 and KCAL scales from 0->256. (Take a KCAL value, multiply it by 128) I use the lower scale because it's been around longer and I can absolutely not see a difference between two steps, 255/254 for example. So seeing the difference between say 32766 and 32765 would be humanly impossible.

Other than that, KCAL is now natively supported in [MENTION=631273]Chainfire[/MENTION]'s CF.lumen... ;)
[ONE Original Android Development] RobbieL811:
So basically, if I am using your color code, I gain zero functionality by adding CM's new LiveDisplay feature? Thanks for clarifying this for us lol.
[ONE Original Android Development] savoca:
Correct & no problem!
[ONE Original Android Development] sam razzy:
I see everyone is facing problem with latest 123 kernel. I'll wait for next kernel. :D
[ONE Original Android Development] kalpik:
Umm, no problems here, at all.
[ONE Original Android Development] Khizar:
You may wanna get your eyes checked cuz you're seeing something nobody else is seeing, haven't seen a single report of problems with version 123.

Flashed it the second it was released and haven't had a single issue so if someone does in fact report an issue, it's probably user error and not kernel error.

Edit - BTW version 124 is up.

Sent From Dark Bacon With Blissed AK Awesomeness To All You Wonder Nobodies!!
[ONE Original Android Development] ak:
new kernel online

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

A kernel based on CAF CM12 Bacon branch.

CM12: AK.124.OPO.SKULL.CM12 > CM12

[ SMALL CHANGELOG ]

merged latest cm12 patches

small fixes

ecc ecc ecc

[ FULL CHANGELOG ]
[ONE Original Android Development] ak:
v123 is a manintanance release, nothing inside can create problems.
[ONE Original Android Development] Ofthecats:
My colors just went crazy. I assume some sort of amoled settings were forced. I heard about the changes coming from cm.

Any idea how to revert? V124
[ONE Original Android Development] aosimon:
Same colour issue here with v124 as well. Was fine with v123.
[ONE Original Android Development] gianton:
Disable "Sunlight enhancement" and it will be back to normal.
[ONE Original Android Development] Ofthecats:
Did not seem to work, and I already reverted to v123, but thanks
[ONE Original Android Development] gianton:
It works fine on Vanir Exodus you just have to wait a bit till it adjusts.
[ONE Original Android Development] ak:
Sre is removed by cm commit. I don't have problem with it disabled. I'm using slimlp

Sent from my A0001
[ONE Original Android Development] sabrefresco:
So what happened to the skull logo?:silly:
[ONE Original Android Development] Nos_20:
124 is working smooth here to, also SlimSaber by [MENTION=1228651]fusionjack[/MENTION]

No colour issues all good [emoji106] [emoji106]
[ONE Original Android Development] ftarules:
Had a random reboot on 123. Kmesg here: last_kmsg-2015-03-05.00.55.47.txt

http://1drv.ms/1BTKStO
[ONE Original Android Development] dudas89:
I updated now and Im experiencing the same strange colors, even with amoled configuration from the first post.

Edit: Have disabled the Sunlight Enhancement and the colors are great again.
[ONE Original Android Development] gianton:
Read back a page for a solution.
[ONE Original Android Development] aosimon:
Thanks for the solution. Display colours are fine on v124 now that Sunlight Enhancement is disabled. No need to revert to older versions.

Sent from my A0001
[ONE Original Android Development] elcom:
Had the same problem. Disabling sunlight enhancement works, but I really liked that feature. Works great when needed (in the sun).
[ONE Original Android Development] NickosD:
Sunlight enchantment works only at full brightness. Disable auto brightness so you won't have problem.

Sent from my bacon!!!!!
[ONE Original Android Development] ak:
This feature will be abbandoned by CM in the future.
[ONE Original Android Development] pcarenza:
Bootloops are a problem, if I'm not mistaken...
[ONE Original Android Development] bombadier:
? could you explain a bit more ?
[ONE Original Android Development] indian84:
Yea.. Bootloops are a problem. Your phone is supposed to stay on..

Good info...
[ONE Original Android Development] Khizar:
Sent From Dark Bacon With Blissed AK Awesomeness To All You Wonder Nobodies!!
[ONE Original Android Development] sam razzy:
If I wait for the next release, do you people have any problem....? :D omg! I know how hard ak works. But if I don't get time to flash 1kb file why do you have any problem? I saw many reporting and now I get a new version with 124.. :D
[ONE Original Android Development] oopstairs:
[MENTION=3685904]ak[/MENTION] and [MENTION=4519152]Khizar[/MENTION] ... hmmm good old gnex days :D
[ONE Original Android Development] pSyCh¤_O_O:
:sad: Because of battery drain? Or why will they abbandon it?

I find it so usefull not having to bump my brighteness up manually when in direct sunlight :sad:...

I live in south Spain... This feature is a must over here [emoji20][emoji12]

Latest version is running great as usuall[emoji106] [emoji106]

Thanks ak
[ONE Original Android Development] ak:
oh yeah my friend.!
[ONE Original Android Development] Khizar:
I don't have problems mate but you either do or you are here to troll. I don't care what you do, flash or don't flash, whatever. But I will again say nobody, NOBODY reported issues.

This isn't just about the fact that I am a long time supporter of Stefano/AK kernel, it's the fact that you keep repeating false information. You say you saw many ppl report issues with version 123, right? Please quote or screenshot those posts.

Anyways I don't have time for this childish argument, so don't bother replying unless you prove that you're right and ppl did report issues, as I won't be continuing this off topic and useless discussion.

Did you change your username? Your name doesn't ring any bells... But yeah so many gnex users in this thread, sad they are all silent.

Funnily enough that feature never worked for me.. Haha

Man I see the gnex thread getting bumped every now and then, ahh.... Memories.
[ONE Original Android Development] abhi08638:
[MENTION=3685904]ak[/MENTION] in case you forgot,

Cool Amoled should be

236 248 256
[ONE Original Android Development] Bhavit:
Having an issue with AK

Anyone seen this error before? Any thoughts on how to fix it?

Noob here and trying to learn/become independent ASAP.

thanks in advance.
[ONE Original Android Development] ukhoughsx:
I had that, not sure if it was to do with permissions? Rebooted and all ok
[ONE Original Android Development] Mojar7070:
That's normal. Press the "x" on top to revert back to previous settings.

Sent from my 1+1
[ONE Original Android Development] bombadier:
You will get that every time you flash a kernel and is more a warning as error, it just means that the previous settings will not be used and so "default" kernel settings will apply, you then need to reload your profile in synapse (can take a bit of getting used to that app)
[ONE Original Android Development] akarol:
Every time I use the kernel updater app to update the kernel it shows the newest kernel as the installed kernel on the app and the previous kernel on Synapse. Tried clearing data, etc, tô no avail. The only solution is manually flashing to fix Synapse, which defeats the purpose of the app.

---------- Post added at 12:48 PM ---------- Previous post was at 12:48 PM ----------
[ONE Original Android Development] ak:
Sometimes it can happen ... You have to reflash ukm

Sent from my A0001
[ONE Original Android Development] akarol:
Every time I've tried it has happened. Having to reflash UKM every time also defeats the purpose of the app. Why not force flash UKM when a flashing a kernel via the app. Wouldn't be hard to implement it.
[ONE Original Android Development] zerocoolak:
No need to reinstall UKM. Just "restart synapse" from within the app. Think it's on the tools page. The newest version installed will show after :highfive:
[ONE Original Android Development] chikimonke:
I like to think I make a fair amount of noise in here [emoji1] I may not be as memorable from the GNex thread though, I sadly only found it a few months before [MENTION=3685904]ak[/MENTION] stopped working on GNex and jumped to the N4.
[ONE Original Android Development] playya:
oh hellllll nah I am on crdroid 5.4 with v31 and I have had no issues at all and I actually have been testing my phone with battery life and my normal weekend usage. I took it off the charger at 12 on Friday night and its been running fine ever since and at 50%. I lost 3% on Friday night Saturday morning and lost another 3% last night and this is with everything on. I don't see why I should have to shut things down to enjoy my phone. I check with wakelock detector. :good:
[ONE Original Android Development] RobbieL811:
Well, that didn't help me much lol. I guess I'll try to find it.

Sent from my 1+1
[ONE Original Android Development] ryaneu:
Correct me if I'm wrong. V.031 stable was created before the release of 33R OTA. thus its missing some additional battery saving commits.
[ONE Original Android Development] sambaeallegria:
I hope so because when I was on 33R and AK I had this problem too.
[ONE Original Android Development] chikimonke:
[MENTION=3685904]ak[/MENTION] has already provided the lines to [MENTION=5658634]apb_axel[/MENTION] and should be in the next update to UKM.
[ONE Original Android Development] sien1996:
This one haha. Not recent at all man :p Just the fix haha. You probably know about this already :p

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/BACON-599

Sent from a Device codenamed Bacon!
[ONE Original Android Development] RobbieL811:
Lol. Thanks. I'm trying to find the commit that fixes it on Github so I can add it to my ROM.

Sent from my 1+1
[ONE Original Android Development] sien1996:
Aye. You could ask [MENTION=1228651]fusionjack[/MENTION] , he has it included since his 08/20 build if I'm not wrong. :)

Sent from a Device codenamed Bacon!
[ONE Original Android Development] RobbieL811:
I have already asked. Waiting on a reply. Wondering if it was on the kernel side of things. Probably so. I build w/ AK as my kernel and if it is, I'm sure he has already taken care of it.

Sent from my 1+1
[ONE Original Android Development] jlevy73:
Not fixed yet, better, but still has some work to go: https://jira.cyanogenmod.org/browse/BACON-857
[ONE Original Android Development] unavix:
This kernel is fantastic. My 1+ has incredible stamina. Thank you for a great job. :good:
[ONE Original Android Development] ak:
thanks a lot

I have a new beta, i'm testing in this moment.

pre changelog:

Project name: AK KERNEL
anarkia1976 - Kernel Version: ak.032_b09.opo.cm11s
anarkia1976 - ak_bacon_defconfig: disable USB_STORAGE_DEBUG and SCHED_DEBUG
anarkia1976 - Kernel Version: ak.032_b08.opo.cm11s
anarkia1976 - cpufreq: smartmax_eps: added new governor based on ondemand and smartass2 - powersave version
anarkia1976 - cpufreq: smartmax: remove early suspend and tuning
anarkia1976 - Kernel Version: ak.032_b07.opo.cm11s
anarkia1976 - makefile: add -DNDEBUG to KBUILD_CFLAGS
anarkia1976 - ak_bacon_defconfig: enable ZRAM II
anarkia1976 - ak_bacon_defconfig: enable ZRAM
anarkia1976 - Kernel Version: ak.032_b06.opo.cm11s
Waiman Long - SELinux: Reduce overhead of mls_level_isvalid() function call
Junxiao Bi - writeback: fix race that cause writeback hung
Dave Kleikamp - aio: fs: don't plug the I/O queue in do_io_submit()
dorimanx - binfmt_elf.c: use get_random_int() to fix entropy depleting
dorimanx - mm: vmscan: when kswapd is awoken due to reclaim by a running task
anarkia1976 - makefile: adaptation to full neon-vfpv4 support
anarkia1976 - block: disable add_random for more performance on SSD's
Mel Gorman - mm: slub: Default slub_max_order to 0
[ONE Original Android Development] mittimus:
Waiting for a intelliactive version on AK :P
[ONE Original Android Development] :
I'm also waiting for this.

Gesendet von meinem OnePlus One mit Tapatalk
[ONE Original Android Development] treChoy:
+1 :)
[ONE Original Android Development] Vortex1969:
I know 80% want more battery life but for me even on my N4 and 5 I tweaked for performance and if you have ever owned one of them the battery life was never the greatest. But I would rather have performance. I guess having a charger at home in the car and in my office. I have never like at it in that way.

The great thing about ak kernel is that you can tweak for ether.
[ONE Original Android Development] timothydonohue:
Well, this is on 33R , stock. So, until AK adds the commits to his stable that cyanogen put in, I'll stick with this. I'm getting great battery life :)

http://imgur.com/bAhbQCE
[ONE Original Android Development] ak:
What are these commits?

all from cm11 are inside ....
[ONE Original Android Development] Vortex1969:
I still see many post about 33r having battery drain problem and even running ak's kernel tweaked on the performance side I have great battery life. Not really sure I see the problem.... I see a lot of wakelock problems still in 33R.

I just think custom ROMs for the One are way ahead of 33r. I know they are look at cm11 code review. And look at cm11s.
[ONE Original Android Development] dickenam:
I remember the GNex days. Boy, was battery life pitiful (even with AK's extensive magicks). But then again, the battery in the OPO is nearly double the milliamp hours of the stock GNex batt...
[ONE Original Android Development] mnhs1010:
Is this support swipe to sleep and wake gestures on capacitive buttons to save battery?
[ONE Original Android Development] RukusX7:
[MENTION=3685904]ak[/MENTION] I have a controller made by gasia co. Ltd. Which is a knockoff of the sixaxis ps3 controller. My moto g 2014, which shares kernel source from cm with the original moto g, currently has support for this gamepad, although I am unable to make it work with the Oneplus One.

Would you be able to add support for this controller? Thank you.
[ONE Original Android Development] TigerV:
I got boot loop with, temasek sm build 8.1 and also with PA. Currently using PA. I tried clean flash also but didn't succeed. Any one know the issue. Help.
[ONE Original Android Development] Khizar:
Oh I remember you, alright. Guess I should've said "most are silent", huh? Haha but man was that thread and phone/kernel a blast..

You say that cuz now you're standards for good battery has increased. Back then it was OK battery, I had switched from the s2 so I didn't really feel much difference but yeah it was annoying that I had to charge 4x a day... Rofl

No I don't think so.

More info? Which version did you flash? Did you try re-downloading the zip?
[ONE Original Android Development] rajdoll:
Does Sweep2wake on hardware buttons work for anyone? It gets set to "disabled" as soon as i set it in synapsis.
[ONE Original Android Development] ak:
S2w never worked on hw button.

Because it work with screen sweep.

Sent from my A0001
[ONE Original Android Development] eliogiac:
Screen colors

Hi,

I am on Temasek v8.1 and just after the installation of AK V.124 the screen colors get too bright.

I disabled sunlight enhacement from dispay setting, played with KCAL on Synapse but it got fixed going back to V.123.

Any idea?

Thanks
[ONE Original Android Development] DrearierJester1:
Flash AK as indicated on the first post then do not boot to system yet, just power off your phone for 1-2 mins and boot it uo again.
[ONE Original Android Development] nhugh406:
I as well am experiencing the same thing.
[ONE Original Android Development] TigerV:
Thanks.. Its work
[ONE Original Android Development] vikash0513:
Can I install ak 124 on cm11s and will I still be able to get ota of my stock rom
[ONE Original Android Development] LookedPath:
Read the first post.
[ONE Original Android Development] rajaa_sekaran:
Same here.. Again back to previous version.
[ONE Original Android Development] stab244:
Only issue I have is that touch sensitivity is a bit wonky on 124. If I type too fast, Swype interprets it as a swipe instead. Was there a new touchscreen firmware? I'm on cm11 nightlies. I'll move to CM 12 once spring break comes around.

Sent from my bacon
[ONE Original Android Development] DerRomtester:
Guys about screen colors just read a few pages back and you will find an answer. I am tired to read the same questions or issues that are no issues.
[ONE Original Android Development] nhugh406:
technically, this is an issue because sunlight "mode" is enabled at all times. disabling it DOES revert the colors back to a "normal" state, but then completely disables an extremely useful feature. i'm sure AK will address it, or something will come along to "rectify" it.
[ONE Original Android Development] elcom:
It seems like it has been addressed. I'm on temasek 8.4 (came out a few hours ago) and sunlight mode is gone. Instead there is a liveview option in display settings that has an outdoor mode. I also had the color problem with the sunlight mode and now with the new outdoor mode it's fine.
[ONE Original Android Development] DerRomtester:
Sunlight mode does not work anymore because cm decided to remove it. Ak only picked the necessary kernel commits for that. And if you are using an up to date rom there are no problems.

It was removed from the kernel but the mode was still inside your old rom so there are problems.

Problems that can exist =

you flash a new kernel over and old rom --> maybe some problems

you flash an old kernel over a new rom ---> maybe some problems

when custom kernel and rom is up to date => no problems

It is so easy :)
[ONE Original Android Development] opee:
The problem is that sunlight mode is still (standard) enabled in synapse!
[ONE Original Android Development] newellj79:
Not for me...

I've never touched anything in this menu...
[ONE Original Android Development] NickosD:
^You need to install the new ukm

It's not enabled by default to me too.

Sent from my bacon!!!!!
[ONE Original Android Development] MrWGT:
Starting with kernel 123 and also 124 I've a sleep of death.

I notice that the device takes longer and longer over the day to wake up and at one point it won't wake up anymore. (or maybe very long and I reseted it before).

With 122 all is fine. I'm using temaseks rom 8.3 and now 8.4 sabermod build from katinez
[ONE Original Android Development] xlollomanx:
With lastest ukm I saw that MSM Limiter function is disappeared, so I reverted to 3.7.1b1. For now I don't have any problems. There are any workaround or I have to wait an update? Thanks.

Sent from my Oneplus One
[ONE Original Android Development] mak725:
Hello, I'm in version V8.4 Temasek Sabermod but can not get into Deepsleep when I do not use phone

Some suggestion which may be the problem?

Enviado desde mi A0001
[ONE Original Android Development] FullWipe:
Reboot in recovery, wipe cache and dalvik.

Or try to remove all these permissions from Google play services like in screenshots

You can found this menu in settings --> app --> all --> Google Play Services --> Modify --> Disable all permissions but not Location (the first one)
[ONE Original Android Development] :
It's not a kernel problem. New google play services 7.+ keeps the device awake.

Block systemupdateservice with built in wakelock blocker. No need to revoke all permissions
[ONE Original Android Development] meetpatel:
I am on uphoria rom and there is no option for modify permission. Please help.
[ONE Original Android Development] indian84:
There is CM privacy guard. Go to Privacy, click on three dots on top right, select advanced and follow the above steps..