yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] indian84:
Loll.. That's the best wish [MENTION=3685904]ak[/MENTION] would have received.. :)
[ONE Original Android Development] rohan9kulkarni:
Can someone please give perfect settings for Performance/Battery/Balanced usage?

Settings for CPU governer/ Cpu Boost/ Cpu hotplug/ Thermal/ Gpu governer / I.O Scheduler for all the three profiles! Or even one profile which gives performance as well as battery will be helpful!

I have installed the L-speed mod, will it have any effect and is it needed?

My phone is heating up a lot, any suggestions?

Thank you ￼
[ONE Original Android Development] abhi08638:
New GPU commits working flawlessly
[ONE Original Android Development] ak:
i have pushed to git the fix + unused state tab.
[ONE Original Android Development] storm119:
Mind telling me....which file/folder should i edit this...?

TIA
[ONE Original Android Development] ak:
you can check on my git:

https://github.com/anarkia1976/AK-Ukm/commits/UKM-Special-essential
[ONE Original Android Development] storm119:
hahaha....thank you...i owe you and abhi a thanks (button)...i've used all thanks for today can give no more.... LoL :D
[ONE Original Android Development] kantjer:
Or flash this
[ONE Original Android Development] abhi08638:
You can redownload it from the UKM link I posted earlier. I updated the zip file with the fix but not the unused states
[ONE Original Android Development] darshan_dex:
I read all the posts after the update. I'm a new OPO user. So I'm sorry I'm confused with Normal kernel and the one with "OLD-TC"...can anyone explain please?

And also suggest which one to flash

Thank you! :)
[ONE Original Android Development] 1337jay:
Both will be ok, the OLD-TC is for people who never had touchscreen issues. I did not have them either, but the new firmware is still more responsive and works better for me.
[ONE Original Android Development] jdtimothy:
I just noticed in the ak updater app that they're is a new version 265 that reverts the per panel touch screen fix... Why is this being reverted? It really fixed my touch screen.
[ONE Original Android Development] hallow:
See http://xdaforums.com/showthread.php?p=61391676
[ONE Original Android Development] storm119:
[MENTION=289782]kanjer[/MENTION] [MENTION=4732904]abhi08638[/MENTION] ,

Thank you for your generous offer....but i need to learn from the hard way.... :D

I already merge (3 files) from the [MENTION=3685904]ak[/MENTION] git to abhi UKM-265 (old) and yes i like the *unused states* which offering more infos....:good:

Thanks guys.... luv you all (no gay...LoL) :p
[ONE Original Android Development] oediv:
Well I tried dirty flash and it didnt work :/

I have installed slimsaber then installed latest AK with old tc and I got bootloop.. Any idea?
[ONE Original Android Development] EotT:
[MENTION=3685904]ak[/MENTION] I want to thank you for this amazing kernel! Amazing long battery in idle. 0.3%/h! So I think I can say that you certainly reached your goal of 0.4%/h! :good:

Almost 6 days and 50% left. I used v262. Never switched off wifi or used airplane mode.

(I know that this very very low usage is not realistic for a normal day. I just wanted to test the idle batery life.)
[ONE Original Android Development] rkubica91:
+1

Thanks AK!! :good: :good: :good:

..

Now I'm on v.265, but yesterday and today I got 2 random reboots with version 262.. here is the last_kmsg: https://gist.github.com/anonymous/3ca0a38615f803a3b936 :confused:
[ONE Original Android Development] preacher65:
Thanks, yes I read that it the thread - but the app downloads the normal (new TC) version, and the changelog seems to be saying it's the old TC version. So the changelog didn't appear to match the download, and I just wondered if it was meant to say that or not, our if I was just misunderstanding things. Anyway it's not a big deal. :)
[ONE Original Android Development] PhantomGamers:
Hey [MENTION=3685904]ak[/MENTION] , thanks so much for your work.

I was just curious what ROM are you currently running with your kernel?
[ONE Original Android Development] Naman Bhalla:
Exodus ? Vanir and Exodus are different now ... http://xdaforums.com/showthread.php?p=61055586
[ONE Original Android Development] ak:
i know, my mistake i have edited my previous post.
[ONE Original Android Development] KenjiHannya:
"CAF is Code Aurora repository. It's the place where Qualcomm releases source code for their phone processors. It's directly supported by Qualcomm and it's generally a more optimized branch for Snapdragon phones."

"Actually, there are two main baselines for support of Qualcomm devices:

CodeAurora (CAF) - These are Qualcomm's reference sources for their platform. This is what they provide to OEMs, and what nearly all OEMs base their software off of. As a result - nearly all non-Nexus devices are running kernels/display HALs/etc. that are derived from a CAF baseline.

Google's software baseline, or AOSP - Usually when Google starts working on a new Android version, they'll fork from CAF at the beginning. Very often Google will be adding "new" features specific to the new Android version, while Qualcomm will continue with performance enhancements and bugfixes against the "old" baseline.

So when a new Android revision comes out, you have two baselines: CAF which is usually "ahead" in performance but "behind" in features, and AOSP which is the opposite.

Starting with 4.3, CM started mixing code between CAF and AOSP. They put some CAF features/capabilities into their baselines for AOSP-supported devices (Nexus devices), and started putting AOSP patches into their baselines for CAF devices."

Rooms for testing based on CAF

http://xdaforums.com/oneplus-one/orig-development/rom-kernel-unofficial-cyanogenmod-12-1-t3120259

http://xdaforums.com/oneplus-one/development/rom-kernel-euphoria-os-1-1-3-4-0-caf-t3134828
[ONE Original Android Development] Draje0:
Only think it's the kernel since flashing it is what seems to trigger the encryption corruption. This is coming from the latest CM nightly + TWRP 2.8.6.1.

Perhaps it's got something to do with TWRP?
[ONE Original Android Development] DemonPhoenix:
AK, With the GPU boost Disabled it stays on 200Mhz when it needs to go higher ._.

Like in the previous builds when scrolling it goes up to 330Mhz or 462 Mhz but with GPU Gaming Boost in the current AK 265 disabled it does not

but with the GPU Boost enabled it always go to the max frequency 578Mhz even when i set the Max as 462 Mhz

Its like the GPU Gaming boost doesn't respect the max frequency ._.

Its just a minor thing as i wanted scrolling to be smooth for my next profile but mostly when GPU Boost is enabled it continues to stay on 578Mhz all the time till its disabled
[ONE Original Android Development] chachin:
what's different+fixed from the one that ak gives us on v265? and how would i go about upgrading to this one :P
[ONE Original Android Development] daltonhrrll:
Mine hangs at 200 quite often but it does go higher. Never goes over 330 though.
[ONE Original Android Development] 1337jay:
It fixes the GPU section.
[ONE Original Android Development] ryaneu:
With GPU Boost disabled mine only stays on 27 Mhz and 200 Mhz. And with GPU Boost enabled it stays on 27 Mhz and 578 Mhz. Not sure if this is the correct behavior though as it seems to be skipping the frequencies between 200 and 578 Mhz.

Please advice.
[ONE Original Android Development] abhi08638:
This is the correct behavior. The governor was tuned for battery and the GPU boost is for gaming only.
[ONE Original Android Development] ryaneu:
Just a small favor. Is it possible to add another option for the default behavior of scaling between 200 Mhz and 578 Mhz?
[ONE Original Android Development] abhi08638:
Yes but its not really needed because you can enable simple governor tunables to change the way msm-adreno-tz behaves. If you want it to be more aggressive in scaling then decrease the ramp threshold and if you want to be at higher frequencies for longer amounts of time, increase the laziness

You can teat and see which values work best for you
[ONE Original Android Development] geokilla:
I may have missed it while I skimmed the thread, but is anyone's OnePlus One getting a sleep death? It starts by being slow to wake up from deep sleep, then it won't wake up at all. The capacitive lights come on but that's it. Only way to fix it is to hold the power button for around 8 seconds so it'll do a force restart.
[ONE Original Android Development] DarKAngel1234:
I get a few every now and again.

QUOTE=geokilla;61407721]I may have missed it while I skimmed the thread, but is anyone's OnePlus One getting a sleep death? It starts by being slow to wake up from deep sleep, then it won't wake up at all. The capacitive lights come on but that's it. Only way to fix it is to hold the power button for around 8 seconds so it'll do a force restart.[/QUOTE]
[ONE Original Android Development] opensourcenoob:
Flashing Exodus right now

But then it got me thinking...

You're telling me that your v265 is working for AOSP ROM as well?

I thought it's CM-based ROM only

*Mind Blown*
[ONE Original Android Development] 1337jay:
Well done, ak!
[ONE Original Android Development] ChefChaudart:
irritating

Hi,

I would like to mention an irritating issue I got. Is it kernel or ROM (Euphoria) I do not now ...

Sometimes, when I activate the phone, the screen turns on normally, but does not react :confused::(

I have to press power button a second time to be able to use the phone :silly:

Anyone else have this ?

p.s.

I do not use Livedisplay, and switched off acccidental wakeup.

Cheers
[ONE Original Android Development] indian84:
I had this when I was using Euphoria even on Stock kernel.. So probably ROM related.
[ONE Original Android Development] ak:
Its rom side, probably related to gestures. I'm using Exodus now and before slim and i never see this problem.
[ONE Original Android Development] expiredd:
You could try raising "Suspend Max Frequency" to 729Mhz if you set a low value like 300Mhz. You can also try to enable Wakeup boost :good:
[ONE Original Android Development] darshan_dex:
Loved the kernel much appreciated [MENTION=3685904]ak[/MENTION] ! :D

But please remove the "GPU Boost" thingy in the next update, it's annoying. :(
[ONE Original Android Development] ak:
why? hurt your sensibility. :)
[ONE Original Android Development] bombadier:
Sorry not sure what went wrong for you, I did exactly the same and all I can suggest is to just flash katjer's build and see if that boots, not sure why the old-tc could cause a problem as I use the normal one
[ONE Original Android Development] darshan_dex:
Cause it's not giving us flexibility, if it's disabled then it's like on "power save mode" locked on 200mhz or else 578 only when needed literally high performance.

And if it's enabled it's locked on 578 like "performance mode"

You know all this. :|
[ONE Original Android Development] ak:
there isnt a powersave mod, gpu work like normal. if you want to play game you can choose boost.

so, what is the problem?
[ONE Original Android Development] the_Calen:
Hello, I switched to this kernel to counter the high android system battery usage on paranoid android 5.1 but I'm unable to find the best settings for battery saving and smoothness. I'm using zzmoove as governor and noop as scheduler because it was mentioned in the PA thread, is this a good combination?
[ONE Original Android Development] ak:
you can use ak profile thread for this.
[ONE Original Android Development] Lookitfast:
I always use fiops & smartmax myself..Not trying to much to overthink the kernel settings I've found to be the best thing. AK pushes out the best kernel pretty much with simply default settings.;)
[ONE Original Android Development] lullo88:
Which are the best settings for the Dirty Background Ratio and the Dirty Ratio? I would like to have an even smoother user experience...

---------- Post added at 11:44 AM ---------- Previous post was at 11:39 AM ----------

I agree with Smartmax and fiops to make it even better, i can also suggest also a Swappiness of 1% and a Cache Pressure of 50%... Because we have 3GB of ram and it would be better to use the ram even more..

Maybe a good choice could be to use IntelliPlug but i don't know how much better it is compared to the stock settings.

I also use z-ram with 512MB but I'm not sure how much it makes the difference..
[ONE Original Android Development] darshan_dex:
No, you didn't get it right. Sir, [MENTION=3685904]ak[/MENTION] .

Look there are two options, Enabled and Disabled GPU boost.

When it is Disabled, it is stuck on 200MHz, unless and until I run a benchmark like Antutu which takes it upto 578MHz.

And because it is stuck at 200MHz, the system animations(like scrolling) aren't good enough, scrolling is kind of laggy(slightly). Even some other guy mentioned the same a lil earlier.

I want the Frequency to hover between 200MHz and 578MHz. But it's not being at those frequencies, it's stuck at 200Mhz unless and until it is pushed hard to reach 578MHz directly(no in between frequencies touched).

All the above problems I've mentioned are about "Disabled GPU Boost".

Hope I explained properly.

But maybe your perspective towards the "GPU Boost" thingy is different. So I might be wrong too.

Just letting you know my experience and what I want.

Thank you so much for your amazing kernel and your surprisingly great support!! :D :)
[ONE Original Android Development] gargeya_369:
I didn't use gpu boost...

But this how my gpu scales...

And I'm happy with scrolling...

No issues or lags....

I'm using [MENTION=6687598]DemonPhoenix[/MENTION] profile....
[ONE Original Android Development] darshan_dex:
How can it be smooth at 27MHz? o.O

Btw please proivde the link for the profile you're using.
[ONE Original Android Development] lullo88:
I can confirm that, my gpu stay at 200MH at 99% of times (with boost disabled). When i enable the boost it stays at 578 when i use it and it shows 27 when i don't touch the screen.
[ONE Original Android Development] abhi08638:
No lag here either, if you want more aggressive scaling just enable simple governor tunables and find a value that fits your needs, that's whats its there for
[ONE Original Android Development] darshan_dex:
Okay, I'll try!
[ONE Original Android Development] gargeya_369:
It scales accordingly....

When idle it idles at 27MHz...

And here is the link for all the profiles...

You can find [MENTION=6687598]DemonPhoenix[/MENTION] profile there...

http://xdaforums.com/showthread.php?p=61253204
[ONE Original Android Development] darshan_dex:
One question. o.O

If I dont enable the addon by faux123, will be be able to adjust laziness and ramp threshold and affect properly?

---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------

Thank you(not able to press the button, reached 8 thanks giving for today :( ) !
[ONE Original Android Development] abhi08638:
No the add-on needs to be enabled and only works with msm-adreno-tz
[ONE Original Android Development] ak:
Please pay attention:

the kernel-level GPU has always worked well and in this way (27 idle, and than based on load to high freqs), so let's post constructively.

I just made sure to use min power frequency of 200Mhz.

thanks.
[ONE Original Android Development] darshan_dex:
Alright Thank you everyone for helping me! :)

(not able to press the button, reached 8 thanks giving for today :( )

Special thanks to [MENTION=3951473]AK![/MENTION] :D

And sorry for creating the mess, if I did. :)
[ONE Original Android Development] ak:
No problem, thanks a lot for your support.

if you use tapatalk you can thanks without limits. :silly:
[ONE Original Android Development] capitanouncino:
I have tested both versions (with new touch drivers and without). My OnePlus is perfect, so I'm interested only to battery drain.

But I haven't found any differences between the two versions, I have used battery monitor widget and it says that in deep sleep the drain is around "16-19 ma" for both versions.
[ONE Original Android Development] ak:
Thanks a lot, this confirm my personal test.
[ONE Original Android Development] fiz:ik:
I'm using this GPU settings for months and I never experienced any lags. More over I would say that lags in scrolling or switching between apps is a pure cpu governor thing.
[ONE Original Android Development] darshan_dex:
Okay, off to tapatalk then! :v:p
[ONE Original Android Development] Spaulding89:
Limitless Thanks like me. [emoji2] [emoji109] [emoji111]

8 Thanks per Day is really not enough for such good work in the threads i use.

Sent from my slimmed Bacon
[ONE Original Android Development] storm119:
!...i second this....8 thanks is so little compare to awesome works from awesome developer/people...:D

@ak

nah!....its time for me to use tapatalk....;)
[ONE Original Android Development] lou2s:
I think the old tc version give me like an extra sot of 40min (from slightly more than 6hr to 6hr 40min). May be placebo...

Sent from my AK-Skulled Euphoria 1.1 A0001
[ONE Original Android Development] abhi08638:
Have you tried the new touchscreen one? I'm pretty sure the increased Bart rely if from the gpu tweaks, not the touchscreen firmware
[ONE Original Android Development] cerealguy:
+1! And the phone is more smooth with new touch drivers! :)

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] storm119:
I do agree with both of you....about the new driver per-panel (and yes i'm using the one with new driver although my bacon dont have the touch issue ) and i already raised this as my previous post and quoted below...i just dont want get offended by others....peace :D

On side note its all up to [MENTION=3685904]ak[/MENTION] to decide wither to release 2 versions on every release.... ;)
[ONE Original Android Development] JaylanPHNX:
Actually, I have to back him up on this. I put the scaling way low and it won't hit anything other that 200 mhz. The usage readout says 200mhz for 28 hours, 100% of usage. I don't know if it's a display/logging issue, or if I'm really stuck at 200mhz.

From my SlimTab Pro 8.4
[ONE Original Android Development] darshan_dex:
You're actually having some problem then, no one has faced such problem.

Maybe try uninstalling with the uninstaller and then flash it again.

Or wait for some experienced person to reply, since I don't have much experience with Ak. :)
[ONE Original Android Development] abhi08638:
Yeah I'm trying it too and I think it might be a little too conservative since the simple governor tunables don't seems to work now

[MENTION=3685904]ak[/MENTION] any insight on this?
[ONE Original Android Development] fabbius:
Panel calibration

Very interesting. I was looking for a way to set the color temperature of the screen to a given value, let's say 5000 K or 6500 K.

Since Lollipop, the system setting of LiveDisplay has been introduced. This tool, even if it is presented as a way to automatically match the changing sun color temperature throughout the day, it can be used as well to (roughly) calibrate the screen to a known temperature by disabling the automatic adjustment and using a fixed setting. I really liked it, since it is very simple and provided reasonable results.

On the other hand, I really like the AK kernel + Synapse combo ;) but unfortunately, it seems that the script at boot that applies the settings of Synapse to the system also resets the screen calibration. The setting of LiveDisplay remains where I set it before the reboot, but the screen is actually uncalibrated (judging by my eye, I'd say it returns to the native calibration, as if LiveDisplay=off).

Do you know if there is a way to set the screen color temperature in Kelvin in AK kernel, via the Synapse settings (which do not include an explicit "screen color temperature" setting)?

Otherwise, if I could get an understanding of what that hex string actually means in terms of calibration curves, maybe I could be able to determine which string correspond to a given calibration, like the standard 6500 K, 2.2 gamma, 120 cd/m^2 white level. Does anybody know the coding of the panel calibration hex string?
[ONE Original Android Development] CallMeAldy:
Time to update AK KERNEL UPDATER

I urge everyone who wants to help translating the application to head over to https://crowdin.com/project/ak-kernel-updater and contribute so that I can release the app with some more translations.

Thanks and Cheers.​
[ONE Original Android Development] ak:
I have made some test and simple gov works like it should, probably now with the new kernel msm-andreno is less aggressive.
[ONE Original Android Development] Klobal:
Same here, but in the past on KK and LP I had between 6-9mA idle drain.

So actually we have the double drain.

I also tought it's because of the Touchscreen firmware, but this Release proves it's not.

Any ideas? I also didnt know if this is Rom related or not.
[ONE Original Android Development] BigMacca:
[MENTION=334343]jgcapp[/MENTION] had found a solution to the battery drain issue in his latest kernel

http://xdaforums.com/showpost.php?p=61412690&postcount=2756

It might be worth hitting him up to see what he's done?

Cheers

Macca
[ONE Original Android Development] thryy:
Same Here 20-25mA idle drain with both versions of the kernel. Around 15-18 with airplane mode enabled
[ONE Original Android Development] ak:
i dont think is kernel related, probably rom side.

the drain is the same with exodus.
[ONE Original Android Development] Spider-Vice:
It is ROM side, he said it was Ambient Display that was causing the issues.
[ONE Original Android Development] alatariell:
Back on Kitkat here because i couldnt stand the radio drain from Lollipop, nasty bug. People said that for Kitkat the latest AK that could be flashed was AK239 version. Just did nandroid backup and flashed the new AK265 + Abhi's UKM. I expected a bootloop but........

Cheers AK and Abhi!

ps. tested both the 265 versions and both work on kitkat, 15/5 CM firmware, 44S modem: no bootloop.
[ONE Original Android Development] Formhault:
Where did you find the modem? I'd like to have a link for it, cause I'm tempted to flash back to KK, as well. Seriously, the battery on LP is awful... at least on 3G, which I use the most...

Although I've been spoiled with LP being gorgeous... I'm willing to go back to KK. Especially if the latest versions of AK will work.

-----

But how can a KK ROM work with LP kernel and firmware?!
[ONE Original Android Development] ak:
Because I'm using anykernel format for ramdisk

Sent from my A0001
[ONE Original Android Development] frenzisor:
I'm on the latest stock update YNG1TAS2I3 with stock kernel and I am seeing 5-10mA during deep sleep and 115 - 156mA with screen on with very light usage. So instead of going back to KK stick with the latest update. There are no issues with the touchscreen anymore and (as of know) this seems to be a very solid ROM release from CM.

[IMG="Battery usage"]https://dl.pushbulletusercontent.com/XBvj5KoQyIdAvEW3z6r25C4M8vs24o3H/Screenshot_2015-06-18-16-35-37.png[/IMG]
[ONE Original Android Development] alatariell:
5 simple steps:

1) Flash the full CM 12 firmware 15052015 (including CM 12 modem): https://www.androidfilehost.com/?fid=23991606952604019

2) Flash the kitkat modem of choice from the site of Lord Boeffla. The good man made it easy for us: http://boeffla.df-kunde.de/bacon/modems/ . Make sure you download and flash the file

without "Full"

in the filename, otherwise you get the whole firmware while you only want the modem

3) Flash a kitkat Rom of choice and 4.4.4 gapps. My personal recommandation would be Katinatez Rom based on temasek's : https://www.androidfilehost.com/?w=files&flid=19645. The right Gapps are the latest beta Gapps from Slim: http://104.236.22.120/index.php?device=gapps/kitkat

4) Flash AK's 265 kernel of choice (link in the OP) and Abhi's UKM (http://xdaforums.com/showpost.php?p=61395278&postcount=3186)

5) enjoy and thank the devs :)
[ONE Original Android Development] wcn:
Here is the flashable XNPH05Q_modem.zip

http://www87.zippyshare.com/v/O7YpXaW0/file.html

Currently back to Mahdi-2.9 with AK265-Old-TC on 15th May firmware. Working great!