yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] madsponge26:
You flashed the kernel? Flashed the old drivers
[ONE Original Android Development] jukiewalsh:
Just want to say great job on the last couple kernels [MENTION=3685904]ak[/MENTION] I've been on the same ROM with the same use patterns and settings but I've been getting an extra whole hour of SOT somehow! Thanks for this
[ONE Original Android Development] Bloodykiller86:
Yeah I installed the latest kernel but because the drivers are now loaded per panel, I'm not getting the fixed touchscreen drivers. I'd prefer not to have to use a kernel from last month for the remainder of the time I have this phone. I don't mind that dt2w drained battery since I have that off anyways and this phone lasts me all day but having to touch buttons on the screen 2-3 times to get it to register my touch is ridiculous
[ONE Original Android Development] crisahan:
when flash AK 270 to latest AICP 0626 build, its causing bootloop and won't pass 1+ logo screen
[ONE Original Android Development] Formhault:
This is a little bit off-topic, but I feel like this is interesting & need to share it with you guys.

So I was out with my parents today. Grabbed my mom's SlimKat rocking Nexus 7 2012 3G and turned on the Wi-Fi hotspot (unlimited data SIM in it).

NO Wi-Fi dropouts for like 8 hours straight. Not a single one!

I get home. Connect to my home Wi-Fi (to which none of my previous devices / actual existing devices in my house had or have any issues connecting and maintaining a stable connection)... I use it for like 5 minutes, turn off the screen (and carry on using WhatsApp Web)... after ~5 more minutes, Wi-Fi is out (WhatsApp Web disconnected).

I am going nuts. :)
[ONE Original Android Development] frogerra:
On latest build I don't have Simpli Governor Tuneable, there's anyway to fix this? Reflash kernel, clear app data and cache but the resut still the same.
[ONE Original Android Development] DemonPhoenix:
thats adreno idler tunables. Not Simple Governor
[ONE Original Android Development] stab244:
Simple was removed in the latest kernel in favor of adreno idler.

Sent from my bacon
[ONE Original Android Development] Charmacas:
Video und Image recording was bad with v270. Reverted to v269 again. Don't know what made the difference.
[ONE Original Android Development] sneakerspark:
I kinda second that.
[ONE Original Android Development] ifukdup:
sorry for my ignorance but could i flash this is i'm on 12.0?
[ONE Original Android Development] Siddarth Malik:
are u on exodus ROM? I am facing the same issue on exodus rom both on stock and ak kernel
[ONE Original Android Development] ghismo83:
[MENTION=3685904]ak[/MENTION] i have fixed the battery charging with your kernel. Thank you. I have only a question. Why you don t use aroma install with a preset of options (scheduler, voltage) like the elementalx? I don t like synapse or similar apps..
[ONE Original Android Development] madsponge26:
Better to use synapse..:D
[ONE Original Android Development] mrasquinho:
What happened with AK Updater on playstore?
[ONE Original Android Development] crisahan:
Was gonna ask that since 250...
[ONE Original Android Development] 1337jay:
It's gonna be back soon.
[ONE Original Android Development] Formhault:
Latest CM12.1 nightly. It's the same on Resurrection, AICP, Euphoria... I tried those too, yeah.
[ONE Original Android Development] Bloodykiller86:
Is there any way you could make a script or small guide to replace the touchscreen driver with the one from last month? That one actually worked for me. The new one does absolutely nothing for me. I'm back to having to touch this 2-3 times to get it working
[ONE Original Android Development] Kks#techSolutions:
Just flash it on blisspop 3.6 .....:good:
[ONE Original Android Development] Paoliz:
Is this kernel compatible with latest stock cm12s, or it's only for cm12.1 (and based)?

Inviato dal mio OnePlus One
[ONE Original Android Development] bombadier:
I am not going to tell you but see if you search the thread you will find out the answer as this has been asking (well when you search you will see how many times its been asked)
[ONE Original Android Development] N_lover27:
if im nt wrong few people are using it on their stock cm12s

but do keep a backup of ur boot.img so that u can flash using fastboot if the kernel doesn't work
[ONE Original Android Development] jark99:
Do most people just flash and run this kernel stock? Is it good battery live without editing the settings?
[ONE Original Android Development] bombadier:
http://xdaforums.com/oneplus-one/general/ak-kernel-profile-synapse-t2858674

Some ideas default settings are more towards being battery friendly, ultimately depends on how you use your phone, the link should have some ideas if you want to tweak for performance etc
[ONE Original Android Development] Formhault:
Can someone please link me to the v265 build? I'm going back to KK. Or... maybe the latest (v270) works?! :eek:
[ONE Original Android Development] xlollomanx:
If I'm not wrong the lastest kernel's version working on kk is v.239

Edit: Download just check here http://ak.hiddenbytes.org/OPO.php
[ONE Original Android Development] Formhault:
Oh, right, there's an archive too. Thanks!

Well, someone said v265 works just fine, so... :p

-----

I'm going to give Temasek CM12.1 a try first. See if it at least helps with Wi-Fi dropouts... if not the mobile radio active bug (hahahahahahaha right!).
[ONE Original Android Development] ak:
i don't think this is a kernel problem because nothing is changed from this point of view.

can you try to disable adreno idler?
[ONE Original Android Development] anshad666:
What is this popping up?

using aicp latest + ak latest..
[ONE Original Android Development] Charmacas:
Okay. I'm on v269 now but I will give it a try and disable adreno idler. I'll report back as soon as the results appear.
[ONE Original Android Development] FloorFox:
Same error here
[ONE Original Android Development] ak:
this is a logcat, what is the problem with kernel?
[ONE Original Android Development] Paoliz:
Flashed version 270 on latest official cm12s, no problem at the moment

Inviato dal mio OnePlus One
[ONE Original Android Development] Formhault:
Back to KitKat (Temasek CM11). With AK v270.

Dear UI smoothness, battery life and Wi-Fi stability, come to me!
[ONE Original Android Development] abhibnl:
Complete OT:

Could you please point me to the last KK temasek version available? Please send me a PM rather than posting here. Also if possible, please send some ss of the features available if the time permits. Thanks!

Sent from OnePlus One
[ONE Original Android Development] KenjiHannya:
Test

Exodus Room 2015/06/28

AK Kernel 270

With profile MixMash v10

Changelog:

- Adreno Idler Tunables Tuned

Enable

- Arch Power

- Adreno Idle

-Abhi's UKM as it is needed to tune Adreno Idler Tunables:

http://xdaforums.com/show...postcount=3522

build.pro

﻿
[ONE Original Android Development] IllUMINATUz:
Hey [MENTION=3685904]ak[/MENTION]

Can you please reupload your kernel updater?? It looks like its disappeared from the play store... :(
[ONE Original Android Development] Stylo King:
This has been discussed many times here, The app got removed from the play store due to some reasons and the dev has been already trying to sort things out. It will be back to play store soon.
[ONE Original Android Development] reaper90:
I'm pretty sure the CPU cores (or anything else on this SoC) do not run using only 100mV or even 10mV. Not that sure about actual manufacturing details, but what i know is that a transistor needs certain voltage in order to operate and what i've learned at university, this is around 700mV, maybe a bit lower on newer technologies but definitely higher for higher frequencies. There's probably a limit in hardware that prevents too low voltages, which can't be changed by software and again i can't explain in detail but i think it's pretty easy to imagine that you can't create any voltage you want out of nothing. So depending on circuit design to create those voltages there's definitely an upper limit and probably also a lower limit for available voltages.
[ONE Original Android Development] sVenose:
That makes sense

That makes sense. There might be a hardware limit.

But I just ran the test again, setting 300MHz to 10mV, cycling the cores on and off once made my device hang and reboot. Whereas doing the same on ANY of the frequencies lower than 300MHz, that is: 69Mhz/146MHz/223MHz had zero effect.

And as you said, the SOC does not run on any of those voltages then why do they work fine when I set them. That might mean the voltage is not being applied, but it clearly is for 300MHz and above. Or that the frequency is getting stuck at 268MHz as stated above.
[ONE Original Android Development] reaper90:
Probably the hardware can't set those values, or interprets them as lower as its limit, so the lowest possible voltage is used. This may be enough for everything below 300 MHz so your device does not freeze while 300 is already too high.

Can't tell anything about this frequency stuck at 268 MHz issue.
[ONE Original Android Development] ak:
if you want to montior freqs you need to use:

root@A0001:/ # cat /sys/kernel/msm_limiter/live_min_freq_0
cat /sys/kernel/msm_limiter/live_min_freq_0
69600
root@A0001:/ # cat /sys/kernel/msm_limiter/live_min_freq_1
cat /sys/kernel/msm_limiter/live_min_freq_1
69600
root@A0001:/ # cat /sys/kernel/msm_limiter/live_min_freq_2
cat /sys/kernel/msm_limiter/live_min_freq_2
69600
root@A0001:/ # cat /sys/kernel/msm_limiter/live_min_freq_3
cat /sys/kernel/msm_limiter/live_min_freq_3
69600
root@A0001:/ # cat /sys/kernel/msm_limiter/live_min_freq_4
cat /sys/kernel/msm_limiter/live_min_freq_4
69600

Frequencies below 300Mhz are not natively supported by the soc:

msm8974pro: cpufreq: ignore rounded calculation for underclock min frequencies

for the question with voltages i need to investigate.

thanks a lot

for the time spent in testing, really accurate and precise.
[ONE Original Android Development] Formhault:
I'm using -75 mV across all frequencies. CPU still gets hot.

Back when I had the Galaxy Note 1... I remember I was able to undervolt by 100 mV, and it was a LOT cooler!

So yeah... maybe the SoC is smart. "Haha, you're trying to give me lower voltage? I'll show you!"
[ONE Original Android Development] sVenose:
I've had this issue with the OnePlus One in the past myself. The problem was my synapse configuration kept all the cores active almost all the time while the display was on.

Undervolting didn't help. I fixed it by configuring synapse in a way so that if I'm not touching the screen, or using anything intensive, that there should only be 1 core active. I check that by using the "CPU Z" app from the store.

Try downloading that app and checking how many cores you have on at any one time when your phone is idle. That is, only CPU Z is open and you aren't touching the screen or doing anything else in the background.

Less cores online is waaayyy better than undervolting alone for heat management. At least for our OnePlus One. This from my experience with my device anyway. :good:
[ONE Original Android Development] Formhault:
Alright. I installed CPU Z.

CPU 0 is either at 300 MHz, either at 1728 MHz (it jumps around). The other cores are either offline, either at 300 MHz (mostly @ 300 MHz), either one of the other 3 is at 1728 MHz and the remaining two offline / @ 300 MHz. Looks pretty good to me... although not PERFECT, I'd say.

But CPU Load seems to spike up - 20~40%, when there's nothing happening... which, of course, causes CPU 0 to jump at 1728 MHz. CPU load doesn't sit at 0% for more than a second at a time.

Indeed ! I set the "active number of cores" to only 2 the day before yesterday. Didn't really made a huge difference in battery life and temperature... I was expecting otherwise, lol.
[ONE Original Android Development] sVenose:
I'm guessing 20~40% is normal depending on which ROM you're using and what services are running in the background. Mine load is in about the same range while I'm looking at the app right now. It's actually more 20~50% for me.

But only CPU 0 is active unless I touch the screen or some very rare random spikes.

I'm using Bricked Hotplug Driver.

I did that by increasing the "Runqueue Threshold Hotplug CPU[1-3]" and "Runqueue Threshold Unplug CPU[1-3]" by 8 for each of those.

That means I changed "Runqueue Threshold Hotplug CPU1" from 12 to 20 and did the same for the rest adding 8 to the default value. I didn't touch any of the other options.

But even then with your settings your phone shouldn't be getting too warm. Maybe check if you have wakelocks. Also check your GPU settings. Mine stays at 27MHz in CPU Z unless I touch stuff.

Good luck.

I'm thinking of sharing my Synapse profile in the other thread but I still need to tweak some stuff first.
[ONE Original Android Development] Formhault:
I'm on KitKat. Huehuehue :)

Yeah, me too. It's enabled by default.

Alright. I'm gonnado the same. "Runqueue Threshold Hotplug CPU4" was 0. I guess it's not really useful :silly:

It's getting warm when I'm USING it. Not when idle, of course.

Yeah! :p

---------- Post added at 10:31 AM ---------- Previous post was at 10:30 AM ----------

[MENTION=3685904]ak[/MENTION] Small typo :p

Under "HOTPLUG" tab in Synapse... check the "Runqueue Threshold Hotplug" settings for each CPU.

The first CPU is labeled CPU1 on one slider, then all the others are offset by 1. So core3 is named CPU4. Check it out :p
[ONE Original Android Development] sVenose:
Just so you know, it should start at CPU1. Because at least one CPU should always be on (plugged) while the phone is not in sleep state, there is no point in creating a "Runqueue Threshold Hotplug CPU0" setting, because CPU0 is always on (while phone is awake).

Also that is why the default value for "Runqueue Threshold Unplug CPU0" is 0. Changing it should do nothing since you can't turn CPU0 off while the phone is awake.

The labels are correct CPU1 is for the 2nd core, CPU2 is for the 3rd core, CPU3 is for the last core. (CPU0 is for the first core)

CPU4 points to nothing and that is why it's default value is 0. Changing it should have no effect whatsoever.:good:
[ONE Original Android Development] acuicultor:
hi ak here is my thread gith github link and proper credits to you,thanks. If you encounter something inappropiated let me know and i´ll fix it or remove inmediatly.

http://xdaforums.com/oneplus-one/development/radioactivekernel-team-nuclear-t3119830
[ONE Original Android Development] ak:
all good :good:
[ONE Original Android Development] ak:
commit 75433e9b8ebfcd8d014d1a9f23b71d5849f7e869

Author: anarkia1976 <stefano.villa1976@gmail.com>

Date: Mon Jun 29 11:52:37 2015 +0200

drivers: usb: Use Android device as USB keyboard/mouse

Adapt to 3.4.y 8974/bacon

Base project: https://github.com/pelya/android-keyboard-gadget

Required app: https://play.google.com/store/apps/details?id=remote.hid.keyboard.client

Steps:

* Start ADB Debugging

* Start app

* Connect device to system via USB cable

All credits to [MENTION=2683775]pelya[/MENTION] for this sweet hack.
[ONE Original Android Development] ak:
no problem from my poiny of view, this is the scenario:

cpu1 cpu0 cpu2 cpu1 cpu3 cpu2 cpu4 cpu3

NwNs_Threshold[8] = {12, 0, 20, 7, 25, 10, 0, 18};

TwTs_Threshold[8] = {140, 0, 140, 190, 140, 190, 0, 190};
[ONE Original Android Development] abhi08638:
Cpu cores always start from 0 so we would have cores 0-3. Although cpu0 is always on so there's no point in adding parameters for it and cpu4 doesn't exhaust exist. This is the reason I removed these options in my UKM
[ONE Original Android Development] poondog:
This is a powerful quad core phone, it will produce heat no matter what. Its not just the CPU that produces heat remember
[ONE Original Android Development] cerealguy:
[MENTION=3685904]ak[/MENTION] can you add in next version Cpu Boost disable option, please? :)

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] Formhault:
Right. So CPU4 is there because...? That's what led me to believe it's a typo.

---------- Post added at 04:56 PM ---------- Previous post was at 04:54 PM ----------

I know. But stock voltage / -75 mV... doesn't really seem to make any difference.

As I said, the last phone I've seen undervolting made a difference was the Galaxy Note 1. Well, the Note 2 and S4 yielded somewhat lower temps, but oh well...
[ONE Original Android Development] fabio.pagliuca:
You can already do it :)

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

Sorry but it doesn't allow me to post an image anyway you have to move the slider all to the left in the cpu boost synapse section and you're good to go
[ONE Original Android Development] IllUMINATUz:
Sorry, I formatted the phone & when I couldn't download the app, I was shocked!! (lost backup too.. :( )

can you please share me the apk.. I hope if ak doesn't mind.. sorry...
[ONE Original Android Development] crisahan:
https://www.dropbox.com/s/knx09i051rz9ccx/com.aldrinholmes.akupdater.apk?dl=0
[ONE Original Android Development] madsponge26:
Mate, did you check if this one is working updates?
[ONE Original Android Development] crisahan:
not sure what u mean...it's the latest version i backed up in my OPO
[ONE Original Android Development] ak:
@sVenose

this is actual configuration and documentation:

[Second Level Nodes]

- regulator-min-microvolt: smallest voltage consumers may set

- regulator-max-microvolt: largest voltage consumers may set

- qcom,headroom-voltage: The minimum required voltage drop between the input

voltage and the output voltage for the LDO to be

operational, in microvolts. Acceptable values are from

50000uV to 250000uV

- qcom,retention-voltage: The value for retention voltage in microvolts. Acceptable

values are from 465000uV to 750000uV

- qcom,ldo-default-voltage: The default value for LDO voltage in microvolts. Acceptable

values are from 465000uV to 750000uV

- qcom,ldo-threshold-voltage: The voltage value above which LDO is nonfunctional.

Acceptable values are from 600000uV to 900000uV

- qcom,ldo-delta-voltage: The delta used to reduce the requested voltage in order

to derive the LDO output voltage while switching

to LDO mode. Acceptable values are from 1000uV to 100000uV

- qcom,cpu-num: Indicates what cpu this regulator controls

/*

* supply

* from

* pmic

* gang

* |

* |________________________________

* | | |

* ___|___ | |

* | | | |

* | | / /

* | LDO | / /LDO BYP [6]

* | | / BHS[6] /(bypass is a weak BHS

* |_______| | | needs to be on when in

* | | | BHS mode)

* |________________|_______________|

* |

* ________|________

* | |

* | KRAIT |

* |_________________|

*/

krait0_vreg: regulator@f9088000 {
compatible = "qcom,krait-regulator";
regulator-name = "krait0";
reg = <0xf9088000 0x1000>, /* APCS_ALIAS0_KPSS_ACS */
<0xf908a800 0x1000>; /* APCS_ALIAS0_KPSS_MDD */
reg-names = "acs", "mdd";
regulator-min-microvolt = <500000>;
regulator-max-microvolt = <1250000>;
qcom,headroom-voltage = <150000>;
qcom,retention-voltage = <600000>;
qcom,ldo-default-voltage = <750000>;
qcom,ldo-threshold-voltage = <850000>;
qcom,ldo-delta-voltage = <12500>;
qcom,cpu-num = <0>;
};
[ONE Original Android Development] sVenose:
I'm taking an in depth look at the krait-regulator[.txt] documentation. I'll probably mess around with your settings a bit.

I'll only be looking at undervolting. I just finished writing my script and ran the first test on 300MHz and the results were stable at 550mV. [My device is speed3,pvs-bin8]

Of course this wasn't in the android environment so I'm going to be testing it in android. I'm rebuilding your kernel with CPU_VDD_MIN set to 550mV so I can run the android test since yours has that limit at 600mV.

After that I'll see what kind of fun I can have with the lower frequencies. Thanks for the info. :good:
[ONE Original Android Development] ak:
I have checked the vdd undervolt interface, and i'm playing a bit with regulator now:

diff --git a/arch/arm/boot/dts/msm8974pro-pma8084-regulator.dtsi b/arch/arm/boot/dts/msm8974pro-pma8084-regulator.dtsi
index 428a520..bb950ac 100644
--- a/arch/arm/boot/dts/msm8974pro-pma8084-regulator.dtsi
+++ b/arch/arm/boot/dts/msm8974pro-pma8084-regulator.dtsi
@@ -491,12 +491,12 @@
reg = <0xf9088000 0x1000>, /* APCS_ALIAS0_KPSS_ACS */
<0xf908a800 0x1000>; /* APCS_ALIAS0_KPSS_MDD */
reg-names = "acs", "mdd";
- regulator-min-microvolt = <500000>;
- regulator-max-microvolt = <1250000>;
+ regulator-min-microvolt = <400000>;
+ regulator-max-microvolt = <1350000>;
qcom,headroom-voltage = <150000>;
- qcom,retention-voltage = <600000>;
- qcom,ldo-default-voltage = <750000>;
- qcom,ldo-threshold-voltage = <850000>;
+ qcom,retention-voltage = <465000>;
+ qcom,ldo-default-voltage = <600000>;
+ qcom,ldo-threshold-voltage = <900000>;
qcom,ldo-delta-voltage = <12500>;
qcom,cpu-num = <0>;
};
@@ -507,12 +507,12 @@
reg = <0xf9098000 0x1000>, /* APCS_ALIAS1_KPSS_ACS */
<0xf909a800 0x1000>; /* APCS_ALIAS1_KPSS_MDD */
reg-names = "acs", "mdd";
- regulator-min-microvolt = <500000>;
- regulator-max-microvolt = <1250000>;
+ regulator-min-microvolt = <400000>;
+ regulator-max-microvolt = <1350000>;
qcom,headroom-voltage = <150000>;
- qcom,retention-voltage = <600000>;
- qcom,ldo-default-voltage = <750000>;
- qcom,ldo-threshold-voltage = <850000>;
+ qcom,retention-voltage = <465000>;
+ qcom,ldo-default-voltage = <600000>;
+ qcom,ldo-threshold-voltage = <900000>;
qcom,ldo-delta-voltage = <12500>;
qcom,cpu-num = <1>;
};
@@ -523,12 +523,12 @@
reg = <0xf90a8000 0x1000>, /* APCS_ALIAS2_KPSS_ACS */
<0xf90aa800 0x1000>; /* APCS_ALIAS2_KPSS_MDD */
reg-names = "acs", "mdd";
- regulator-min-microvolt = <500000>;
- regulator-max-microvolt = <1250000>;
+ regulator-min-microvolt = <400000>;
+ regulator-max-microvolt = <1350000>;
qcom,headroom-voltage = <150000>;
- qcom,retention-voltage = <600000>;
- qcom,ldo-default-voltage = <750000>;
- qcom,ldo-threshold-voltage = <850000>;
+ qcom,retention-voltage = <465000>;
+ qcom,ldo-default-voltage = <600000>;
+ qcom,ldo-threshold-voltage = <900000>;
qcom,ldo-delta-voltage = <12500>;
qcom,cpu-num = <2>;
};
@@ -539,12 +539,12 @@
reg = <0xf90b8000 0x1000>, /* APCS_ALIAS3_KPSS_ACS */
<0xf90ba800 0x1000>; /* APCS_ALIAS3_KPSS_MDD */
reg-names = "acs", "mdd";
- regulator-min-microvolt = <500000>;
- regulator-max-microvolt = <1250000>;
+ regulator-min-microvolt = <400000>;
+ regulator-max-microvolt = <1350000>;
qcom,headroom-voltage = <150000>;
- qcom,retention-voltage = <600000>;
- qcom,ldo-default-voltage = <750000>;
- qcom,ldo-threshold-voltage = <850000>;
+ qcom,retention-voltage = <465000>;
+ qcom,ldo-default-voltage = <600000>;
+ qcom,ldo-threshold-voltage = <900000>;
qcom,ldo-delta-voltage = <12500>;
qcom,cpu-num = <3>;
};
[ONE Original Android Development] okak24:
Hello ak... What i need do for use your last kernel v270 in cm11s? Its possible do this? Thanks
[ONE Original Android Development] JaylanPHNX:
You need to search more. It's been laid out complete with links to zips more than once.

It's baconnn!
[ONE Original Android Development] stombie18:
Random issue. Not sure of it's kernel related but the fitbit app keeps crashing when trying to sync. Anyone else had this issue with this kernel? Was thinking it may be a Bluetooth issue...
[ONE Original Android Development] Stylo King:
Most probably it is a rom issue.
[ONE Original Android Development] okak24:
Sorry. It's true but my English not perfect, and i search but don't find. I think is something like firmware but i need confirm this. If you can help me please. I thank you
[ONE Original Android Development] JaylanPHNX:
Basically you need new firmware and old modem. And maybe luck.

From my SlimTab Pro 8.4
[ONE Original Android Development] IceFe:
When the merger with the latest nightlies cm12.1 ? :D
[ONE Original Android Development] ak:
No changes from kernel side.

Sent from my A0001
[ONE Original Android Development] IceFe:
I see this :

cm-12.1-20150629-NIGHTLY-bacon.zip

MD5sum: BE58BF894B1E37CDA8312EACF0B77CEC

Built: 2015-06-29 AT 12:06 AM

-msm: vidc: removed the async v4l2 event for session unsupported (android_kernel_oneplus_msm8974)

-ASoC: Avoid wrong map/unmap of ocmem (android_kernel_oneplus_msm8974)