yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
Quick search would have given you the solution.

The checkbox on the overview page is not meant to be sticky but only on-the-fly.

If yout want it sticky, you need to configure it in the app settings under kernel startup options.

Andi
[ONE Original Android Development] rolarocka:
Tyvm Andi for all your work.

A0001 - Tapatalk
[ONE Original Android Development] cloudx720:
well that sux :( thoughts Andi? ?
[ONE Original Android Development] andip71:
Not a new information.

GPU scaling is controlled via the trusted zone, so it seems the overclocking has no effect.

I was just too lazy to remove it.

Andi
[ONE Original Android Development] cloudx720:
Aww nevermind kernel is still awesome ?
[ONE Original Android Development] andip71:
But was a good reminder I have to take it out...

Andi
[ONE Original Android Development] inad ila:
Hi [MENTION=1045701]lordbo[/MENTION]effla can you plz merge this http://click.xda-developers.com/api...github.com/KINGbabasula/andr...2b01536620ebf5
[ONE Original Android Development] cloudx720:
If u read op its already supported.
[ONE Original Android Development] andip71:
Implemented since ages.

Andi
[ONE Original Android Development] cloudx720:
Anyone on latest cos12.1.1 notice high idle battery drain?
[ONE Original Android Development] andip71:
Not really... But explain what "high" means to you?

Andi
[ONE Original Android Development] infatality:
Maybe it's doesn't not matter.. But seems like those on cm13 with random reboot, try to set selinux to permissive.. Seems to help with the random reboots. [emoji6]
[ONE Original Android Development] shiromau:
thanku sir for ua lovely work... just wanted to say Kernel works gre8... using on Resurrction Remix Marshmallow Built it actually giving good result as compare to stock kernel... :)
[ONE Original Android Development] eagledipesh:
More than 10% battery drain overnight. I have greenify xposed module activated. Not sure if it's the kernel or rom
[ONE Original Android Development] andip71:
I can only say - it is not the kernel.

Sometimes using tools like greenify, amplify, xposed do more harm than good.

CM13 is NOT at all a stable rom yet, needs a lot polishing.

So for the time being this is what we have.

Andi
[ONE Original Android Development] eagledipesh:
Do you have similar issue, do you use greenify xposed modules?
[ONE Original Android Development] andip71:
No. I h*** xposed, will never ever use it (many times explained in all my threads, so no further explanations now).

So,no such issues here.

Andi
[ONE Original Android Development] floyd372:
Can I use this with Sultan's cm 12.1 CAF builds?
[ONE Original Android Development] cloudx720:
Nope.
[ONE Original Android Development] hellcat50:
lol, can't use the search function anymore:

vBulletin Message

An error occurred while performing a Searchlight query:

connection to 10.0.100.17:9312 failed (errno=111, msg=Connection refused)

If you followed a valid link, please notify the administrator.
[ONE Original Android Development] JackDidi:
Great kernel
[ONE Original Android Development] raiashu92:
great kernel. One problem though if i flash it on cm nightly, whatsapp notification stop coming after some time after device sleeps. The app has to be opened to recieve notif. After opening app, it will work fine until some minutes after devuce sleep then again same thing. Not happens on stock cm kernel. Can anybody provide any solutions?

Kept whatsapp in not optimized under battery optimizations in both kernels to avoid doze from kicking in. Other than this all working fine. Awesome work [MENTION=947981]Lord Boeffla[/MENTION]
[ONE Original Android Development] infatality:
Well.. This has nothing to do with kernel anyhow. Try updating your whatsapp to the latest available at apk mirror.. Has no such issues on my end. [emoji6]
[ONE Original Android Development] raiashu92:
i am using 367 version from playstore, latest on apkmirror day before yesterday was 401. Which one are you using?? Will try out 401 in the meantime. Also, do you keep whatsapp out of optimization or in, in the battery optimization tab. It's for doze feature right?

You on CM 12.1 or Cm13?(your signature)
[ONE Original Android Development] andip71:
CM13 kernel update

Hi all,

update to the CM13 kernel available for you:

CM13 -- Version 5.0-beta22

13.01.2016

Fix: Fixed improper file permissions in ramdisk (improve stability)

Update: Updated with latest official CM kernel commits as of 13.01.16, 9am CET

Update: Ramdisk updated to official CM13.0 nightly version of 13.01.16

Enjoy

Andi
[ONE Original Android Development] andip71:
COS12.1.1 kernel update

Hi all,

also the COS12.1.1 kernel receives a small bugfix update now.

Version

4.2-beta2

13.01.2016

Note: It is required to update to COS12.1.1 version YOG7DAS2K1 to use this kernel version !!

Fix: Fixed improper file permissions in ramdisk (improve stability)

Enjoy

Andi
[ONE Original Android Development] suaverc118:
Check if you have WiFi scanning on. Sometimes it will stay on after activating GPS. If its on, turn it off
[ONE Original Android Development] varund7726:
[MENTION=947981]Lord Boeffla[/MENTION]

i was wondering if you had a closer look at this?

https://github.com/CyanogenMod/andr...mmit/7d013e0cb7e3f2656b350da44a118222babbbb72

Seems like a major clean up

I see youve merged this into your repo but not into your personal defconfig

any specific reason why?

Im asking because i tried to use this defconfig with my kernel and im getting really strange errors

arch/arm/mach-msm/perf_trace_counters.c: In function 'tracectr_cpu_hotplug_notifier':
arch/arm/mach-msm/perf_trace_counters.c:32:18: error: 'CPU_TASKS_FROZEN' undeclared (first use in this function)
if ((action & (~CPU_TASKS_FROZEN)) == CPU_STARTING)
^
arch/arm/mach-msm/perf_trace_counters.c:32:18: note: each undeclared identifier is reported only once for each function it appears in
arch/arm/mach-msm/perf_trace_counters.c:32:40: error: 'CPU_STARTING' undeclared (first use in this function)
if ((action & (~CPU_TASKS_FROZEN)) == CPU_STARTING)
^
arch/arm/mach-msm/perf_trace_counters.c: In function 'init_tracecounters':
arch/arm/mach-msm/perf_trace_counters.c:173:2: error: implicit declaration of function 'register_cpu_notifier' [-Werror=implicit-function-declaration]
register_cpu_notifier(&tracectr_cpu_hotplug_notifier_block);
^
arch/arm/mach-msm/perf_trace_counters.c: In function 'exit_tracecounters':
arch/arm/mach-msm/perf_trace_counters.c:181:2: error: implicit declaration of function 'unregister_cpu_notifier' [-Werror=implicit-function-declaration]
unregister_cpu_notifier(&tracectr_cpu_hotplug_notifier_block);
^
cc1: some warnings being treated as errors
scripts/Makefile.build:307: recipe for target 'arch/arm/mach-msm/perf_trace_counters.o' failed
make[1]: *** [arch/arm/mach-msm/perf_trace_counters.o] Error 1
Makefile:968: recipe for target 'arch/arm/mach-msm' failed
make: *** [arch/arm/mach-msm] Error 2
make: *** Waiting for unfinished jobs....
AS arch/arm/kernel/sleep.o
[ONE Original Android Development] andip71:
Yes, I looked at it... complete bull****.

In fact they split one single simple defconfig into multiple. This makes things complex and error prone.

I will not do that with my defconfig as I prefer to have everything together in one file.

Andi
[ONE Original Android Development] varund7726:
Yeah its stupid

They made a different defconfig for debugging

BTW just our of curiosity. What do you think caused this error?
[ONE Original Android Development] andip71:
What exactly did you do? A "make cyanogenmod_i9300_defconfig" ?

I assume this is not enough anymore. But I have not looked into it further as I don't like the approach at all and decided to not follow that nonsense.

Andi
[ONE Original Android Development] infatality:
I have 2 opo. One is on cos 12.1 another is on cm13. I kept whatsapp in optimization, default setting.. Notification and whatsapp still coming in as per normal.
[ONE Original Android Development] cloudx720:
Does this mean stock kernel is bugged? Or bug fixed in your kernel? ?
[ONE Original Android Development] andip71:
Fixed in my kernel.

Stock kernel is ok.

Andi
[ONE Original Android Development] infatality:
Finally.. Got hold of this baby! [emoji7]
[ONE Original Android Development] pilspeda:
Quick question:

On CM13 (TEMASEK) stock kernel, I get system rw to work.

On your latest beta, system rw does not work (cannot delete/edit files through ES File Explorer with root enabled).

Any Idea if this can be fixed ?
[ONE Original Android Development] infatality:
Are you using Supersu or?
[ONE Original Android Development] pilspeda:
Latest SuperSU 2.66 in use.
[ONE Original Android Development] infatality:
I don't thinks it's kernel related.. Working fine on my end.
[ONE Original Android Development] stab244:
Does the app have a scheduled reboot option? I thought I saw it before but I can't find it now.

Sent from my bacon
[ONE Original Android Development] andip71:
No. Never had it.

Andi
[ONE Original Android Development] stab244:
Alright. Been having reboots at night but I can't seem to figure out why. Last_kmesg says no errors detected.
[ONE Original Android Development] andip71:
Cm13?

Then it is a known cm13 issue still. At least for some. You will not find anything in any logs unfortunately, as not the kernel is the trigger for it.

Andi
[ONE Original Android Development] suaverc118:
Are you using greenify?
[ONE Original Android Development] stab244:
Yeah. I thought those issues were all solved but I guess not. At least the reboots are at night so it's not too big an issue.

No.
[ONE Original Android Development] varund7726:
I fixed my error with the cms new defconfig

apparently

this kernel debugging needed to be enabled

strange

CONFIG_DEBUG_KERNEL=y
[ONE Original Android Development] Mecca EL:
What theme are you using? If you are, it could be causing a system crash.
[ONE Original Android Development] andip71:
CM13 kernel update

Good evening,

before the day is gone in Germany today, another CM13 kernel update for you:

Version 5.0-beta23

15.01.2016

Change: Removed some debug logging, according to CM strategy for production kernels

Update: Updated with latest official CM kernel commits as of 15.01.16, 11am CET

Update: Ramdisk updated to official CM13.0 nightly version of 15.01.16

Enjoy

Andi
[ONE Original Android Development] raiashu92:
Awesome, i dnt knw what happened and i knw benchmarks dnt affect real life performance but after this update, antutu score jumped frm 57k to 71k. :good:cool:::laugh::victory:
[ONE Original Android Development] infatality:
[KERNEL] [Bacon] [CM13/COS12.1/CM12s/CM12.x/CM11s/CM11] Boeffla-Kernel (15-01...

YOG7 full zip is out.

http://xdaforums.com/showthread.php?p=64832767
[ONE Original Android Development] andip71:
Yup, I was the first one last night to inform Spannaa about it, who maintains the firmware download thread :)

Andi
[ONE Original Android Development] twowheeler:
Just flashed it with boeffla beta 2. Really curious if all the horror stories about battery life are true, cause so far it's running as good as usual

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] cloudx720:
Running better than ever on my opo :) just waiting for MM now ?
[ONE Original Android Development] bloof:
Quick one : is SuperSU 2.66 only for 6.0 or works on 5.x too?

Thanks.
[ONE Original Android Development] infatality:
5.x.x compatible.. No issues on COS 12.1.1 and OOS 2.20.
[ONE Original Android Development] cloudx720:
Works with 5.1.1 too :)
[ONE Original Android Development] atulclassic:
OT

but TB 7.3.0 doesn't works with SU 2.66
[ONE Original Android Development] andip71:
I really do not understand why people still user SuperSu (which I have to say is getting slightly worse with the latest approaches, sorry) with this rom.

There is an easy zip file to flash that enables CM internal superuser together with my kernel, and this one works like a breeze.

Just in case someone is interested, flash the attached zip first (ignore the file was made for a different rom, as you will replace the contained kernel anyways with mine again), then straight away Boeffla kernel again. Of course SuperSu must be completely removed before.

Andi
[ONE Original Android Development] infatality:
Working fine here.. The trick to use Tb on super su is to set the file storage to external storage not legacy.
[ONE Original Android Development] bloof:
Is this a special implementation of the CM native root for your kernel or does it just enable the standard CM root in "developer options"?

There is an option in superSU to "respect CM root settings" in developer options. If I do that and just enable the native CM root, would that achieve the same results as removing SuperSU and flashing this zip?
[ONE Original Android Development] andip71:
It is an implementation to uncover the only hidden root in COS.

It requires a changed property file and a supporting kernel.

What this SuperSu option does, no clue. I am not using SuperSu anymore for ages.

Andi
[ONE Original Android Development] Aavion:
I always used to use cm's internal superuser since the very first time i flashed cm on my first android phone (htc dream) :D never had another superuser tool on my phones, except on non cm based roms (like touchwiz) :D

you just need to put the SU binary from official cm nightlies to /system/xbin on cos and a kernel that has debuggable-flag set. finished xD

Gesendet von meinem Schinken.
[ONE Original Android Development] Renosh:
There's an updated superuser that was posted for latest COS12.1.1

http://jak-linux.org/cm/cm-unofficial-12.1-YOG7DAS2K1-bacon-signed-superuser.zip
[ONE Original Android Development] jokermithun:
hello sir right now im on COS 12.1 latest YOG7D version with stock cm recovery n unlocked bootloader...do i need twrp recovery to flash above zip to get root access????:o
[ONE Original Android Development] andip71:
As this is a self-signed zip, and not an officially signed one (only OnePlus has the key for it), you need a custom recovery to flash it.

So the answer is: yes, yo need twrp ideally.

Andi
[ONE Original Android Development] twowheeler:
Yeah, i'd also like to know how to switch to that from SuperSu. Also what are the benefits of either of them?
[ONE Original Android Development] andip71:
I think everything is explained there:

https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/

Benefits? For me the main benefit of NOT having SuperSu anymore is: Everything works, no issues anymore, it is just lean and simple. And one App less...

Andi
[ONE Original Android Development] andip71:
Hi,

may I ask where you found it? Is there a thread for it on XDA? One OnePlus forum, the thread is kinda outdated and not maintained with new versions anymore.

Thanks

Andi
[ONE Original Android Development] Renosh:
The same thread which you quoted

https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/page-6

on the last page he announced a new version, there are newer versions but I think he just forgets to update the OP
[ONE Original Android Development] jokermithun:
which twrp version do u recommend for COS ????
[ONE Original Android Development] andip71:
Ok, indeed I did not look into the latest posts, thought the OP will be updated.

Good to know, thanks for the answer :)

I always use TWRP 2.8.6.0 on all my OPOs, because it can flash modems without issues and also the scripting engine is fine. With higher versions, things started to get broken.

Andi
[ONE Original Android Development] jokermithun:
yes ur right...i ws using twrp 2.8.7.0 with cm mm roms and few days back trying to flash firmware then lost imei with baseband...came back COS
[ONE Original Android Development] twowheeler:
One question. What is the effect of the "change power settings depending on app" mode? I mean, can the rom change power settings? And should we disable it to not make it mess with the kernel?
[ONE Original Android Development] Aavion:
i think, on boeffla kernel this option is quite useless, as in standard config, the kernel doesn't accept any overrides that are not done using the boeffla config app ^^ you may disable this override protection, but then your own settings won't be sticky as cos would override them every now and then :D

Gesendet von meinem Schinken.
[ONE Original Android Development] :
I clean flashed (deleting internal storage too) the COS 12.1.1 via fastboot. Then flashed the Boeffla kernel and the config app. In the config app, everything is untouched including the profile. But for some reason the Max CPu frequency is showing as 2.88 Ghz instead of 2.4. Again, i haven't touched anything in the config app. Although, the device is not going above 2.4GHz but it still shows as 2.8.

Attaching the images.

PS: I just flashed stock kernel to check if it's ROM issue or kernel. And turned out that with stock kernel, CPU frequency are showing as it supposed to be.
[ONE Original Android Development] infatality:
Nothing is wrong.. It's the same on all opo running boeffla kernel.. The default is 2.5ghz. 2.8ghz is the max freq the phone support thus you see it in cpuz. You can't change it.. It's coded in the kernel.. You don't see it on stock is because stock kernel don't support overclock.
[ONE Original Android Development] thedoctor.gz:
This is very interesting. Can I ask you which one do you use?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] :
Thanks for the reply. But with previous versions of kernel and COS it used to show 2.4 Ghz (which is the max frequency). Also i just flashed the stock kernel and it shows 2.4 Ghz.

Thanks anways, i thought i messed up something.

Attached is the image with Stock kernel
[ONE Original Android Development] infatality:
Boeffla kernel support over clocking up to 2.8Ghz and that's the max frequency boeffla kernel. And also snapdragon 800s soc has to to be modded to support overclock and such. Thus the boeffla kernel and like that support overclock will show higher frequency than stock kernel on apps like cpuz but the actual frequency is definitely default frequency whatever the devices is on, ie: opo 2.5ghz.
[ONE Original Android Development] andip71:
I recommend 2.8.6.0 for COS and CM. It is the only TWRP version (in my opinion) that is free of bugs.

Well, it has been explained already - all is fine.

CPU-Z, as well as all other tools, show the maximum possible frequency according to the frequency table. It does not mean it will be used.

What will be used or not is completely controlled by Boeffla-Config.

And no, this is the same for all custom kernels + it was always like that, also for previous of my kernels. Even my first S3 kernel around 3 years ago showed - of course - exactly the same behaviour.

It is system immanent and normal. Nothing to worry about.

Stock kernel, of course, does not allow higher frequencies, so CPU-Z shows the maximum stock kernel can do = 2,4 GHz.

Well, I do not fully understand. But I use official 2.8.6.0 from here:

https://dl.twrp.me/bacon/

Andi
[ONE Original Android Development] :
Thanks for the detailed explanation :)
[ONE Original Android Development] andip71:
You are more than welcome.

It is part of my role here to educate people when they have questions.

Not that I have to do that, but I believe it is important to create knowledge and trust.

Andi
[ONE Original Android Development] thedoctor.gz:
Sorry, I was talking about the modem.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
I always use the modem that comes with the rom.

So on COS I use the modem which comes with it, same for CM.

I see no point in messing around with different modem versions. I did that in the beginning, but for me signal reception is the same always.

Andi
[ONE Original Android Development] Renosh:
Not related at all to what's quoted but I remember you saying you'd post some info about using Tasker. Some script or something that helps users choose profiles for specific apps e.g. games. Another thing I'd like to ask in relation to Tasker does the app have to be open to run a profile? Or does it run the intent automatically as soon as you enter the app?
[ONE Original Android Development] andip71:
Had not yet time to work on a tasker template which can be reused. Sorry.

And the app does not have to be open. Tasker spins up a background service that works based on the defined rules and actions.

Everything else would be pretty useless :)

Andi
[ONE Original Android Development] andip71:
Updates to CM13 and COS12.1.1 kernels

Heho folks,

updates for you, both for CM13 and COS12.1.1 kernels.

CM13 -- Version 5.0-beta24

21.01.2016

Note: You need at least Boeffla-Config V2 in version 2.2.21 or higher for latest features !

Touchboost (input boost) driver updated to version 2 (input boost pulse duration now configurable - default is 40 ms)

Ramdisk updated to official CM13.0 version of 21.01.16

COS12.1.1 - Version

4.2-beta3

21.01.2016

Note: It is required to update to COS12.1.1 version YOG7DAS2K1 to use this kernel version !!

Note: You need at least Boeffla-Config V2 in version 2.2.21 or higher for latest features !

Update: Touchboost (input boost) driver updated to version 2 (input boost pulse duration now configurable - default is 40 ms)

Change: Removed some debug logging, according to CM strategy for production kernels

Enjoy

Andi
[ONE Original Android Development] Aavion:
Andi? Hello again after some time now :D

Got a few random reboots since I've got my One back from RMA, thought, ZaneZams linaro builds would be the cause, but I was wrong.

At first, kmsg told me sth about Kernel Panic with unrecoverable blocks.

Then, after using a different build, kmsg showed some watchdog reboots because of Facebook app (no reboots after switching to facebook beta channel) but after today's update I'm using your original build and got about 4 reboots...

1st: kernel panic (secondary cores not responding)

2nd: watchdog (pmservice)

3rd: reset, no errors detected

4th:

(... some normal irq stuff...)

"2 corrected bytes, 1 unrecoverable blocks"

and nothing before or after that what could've be the cause...

any idea?

running cos12.1.1

Gesendet von meinem Schinken.
[ONE Original Android Development] andip71:
No idea. I did not have a random reboot for months now...

Did you flash cos12.1 with a higher twrp recovery than 2.8.6.0?

Maybe you have a firmware mismatch. Don't know.

Andi
[ONE Original Android Development] Aavion:
just had two other reboots, now with a different message (as attached).. very strange... everytime it reads different :/

no, flashed factory image using fastboot and did otas using stock recovery...

the only system modifikations i use are your kernel and integrated superuser to make your config app work...

thought that facebook is the black sheep, but i could only see watchdog reboots related to it, as they stopped since i updated to fb beta app...

very strange...

edit: flashed back beta2 linaro build, as with that one i only had reboots once to twice a day and not every few minutes :D
[ONE Original Android Development] andip71:
Something is severely messed up. Have a reboot every few minutes means either hardware or something completely crazy.

I hope you tried kernel default settings as well... Not in the end it is a wrong configuration.

Also try a fresh download and a fresh kernel flash as well, helping wonders sometimes.

Andi
[ONE Original Android Development] Aavion:
yep, tried that... ironically, the linaro build of beta2 causes lesser reboots than your beta3 :D even after a clean flash... i'll test a bit further and let you know, if i figure it out ;)

next step: manually download and flash though twrp (not through app) and test again [emoji1]

i don't think that this could be hardware fault, as stock kernel works :/ except watchdog reboots every few days before updating facebook to latest beta...

Gesendet von meinem Schinken.