yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Aavion:
Maybe just a voltage missmatch due to temperature differences... As this it the first time ever i've seen sth like that, I don't think it really matters... 5 days uptime without any issues is pretty good ;)

Gesendet von meinem Schinken.
[ONE Original Android Development] andip71:
CM13 kernel update

Hi folks,

before I disappear for the next 4 days (business trip again), please let me serve you another updated CM13 kernel. CM team pushed some changes, so with that kernel you are fully up-to-date again.

Version 5.1-beta2

01.02.2016

Important: This kernel works ONLY from CM nightly of 30.01.2016 onwards!!!

For older nightlies, you need to use the old 5.0 series.

Update: Updated with latest official CM kernel commits as of 01.02.16, 8am CET

Update: Ramdisk updated to official CM13.0 version of 01.02.16

Enjoy

Andi
[ONE Original Android Development] atulclassic:
happens to me a lot..almost every two days...COS 12.1.1, zzmove governer, uv-75, fiops scheduler

but i use xposed too so can't get support from Lord..
[ONE Original Android Development] andip71:
You would also not get support due to your heavy undervolting.

You are really surprised you have trouble? :confused:

Just leave this f***ing undervolting for a start.

Andi
[ONE Original Android Development] Aavion:
try disable undervolting and if the problem persists, try interactive ;)

for me as it technician it looks like a voltage missmatch which leads to ram r/w failures... never seen that on andoid before, but my old laptop had such hyroglyphic messages very often during winter (running ubuntu) when I took it running from the cold outside into the warm inside :D overvolting by 50mv solved this problem (old laptop with intel pentium quadcore) :D so give disabling uv a try ;)

E: Another possible solution would be to keep your device away from strong electromagnetic fields, as these MAY cause similar behaviour...

if that all doesn't help then i've got no idea...

Gesendet von meinem Schinken.
[ONE Original Android Development] ZaneZam:
xposed and uv that's a double jackpot here! :D

ehm ok then u as a technican should know about device temperature acclimatation to avoid condensation, but well if overvolting solved it then u found another method :)

speaking about voltage mismatch: do u setup "no undervolting" in cpu tab or custom? just asking as people had issues with previously set (and forgotten) values which were still used

and didn't got reset. beside of that: i also never saw that and i saw a lot of bugs - mostly very good self produced ones (the best of them all!) :) running COS12.1.1 kernel build with uber 5.3.1 toolchain +

max compiler optimization stock settings except: zzmoove optimized / zzmoove native hotplug / tripndroid sheduler / display/audio stuff adjusted. as a daily config with no proplems

since a veeery long time (months!). just to give an opposite example ;)

maybe u guys with that strange problems try to start from scratch by resetting the app settings (why ever but that also often helps!) and leave it running on stock settings, and see... if that works well try to adjust things again ;)
[ONE Original Android Development] chopin00:
After 20h testing 5.1 beta2 (with Temasek 3.7).

Terrible battery drain.

On beta2 after 6h of night battery lost 24%!

On beta1 after 7h of night battery lost only 2% with morning alarm.

Governor: interactive

I use a greenify to kill running process.

Back to beta1.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] andip71:
Not kernel related. No drain on official CM13 at all.

Andi
[ONE Original Android Development] Hilmesh:
hello all. i am sorry for this OT. but can some one please guide / direct me to how to use the inbult su in CM 12.1 official. i am dirty flashing the updates right now due to mic issues and would like to try this instead of flashing chainfire's SU file. Thanks in advance. Sorry Lord for this OT but i felt that here i will surely get some answer.
[ONE Original Android Development] Aavion:
you'll need a debuggable kernel (like boeffla kernel :D ) and the su-binary (you may manually put it in /system/xbin/ or use the flashable zip here (http://jak-linux.org/cm/cm-unofficial-12.1-YOG4PAS3JL-bacon-signed-superuser.zip) which also contains a su binary.

IMPORTANT IF YOU USE THAT ZIP FILE:

It flashes an outdated stock kernel image which is debuggable, but OUTDATED. Do not try to boot into your system, unless you flashed abother kernel AFTERWARDS ;)

You may also use any su binary from official cm12 or cm12.1 releases and manually push it to /system/xbin (filename: /system/xbin/su). no other files needed ;)

Gesendet von meinem Schinken.
[ONE Original Android Development] deepu458:
HI [MENTION=947981]Lord Boeffla[/MENTION], im really impressed with the Kernel and Kernel Config app. I just want to ask you if possible can u add the option of increasing the MicroPhone gain like the Volume gain option to the config app. So tht we can increase or decrease the gain instead of editing the Mixer_Paths every time.
[ONE Original Android Development] andip71:
Sorry, not likely.

The mixer file is on rom level.

My app should only configure kernel settings and not interfere in any way with the rom.

So either I find a way to manage something similar on kernel level (which is not very likely), or I am afraid I will not be doing it.

I really want a clean app, not mixing in various things.

Sorry, lean and clean and proper architecture is one of my primary goals.

I broke that paradigm already once and quickly regret it.

Thanks for understanding

Andi
[ONE Original Android Development] infatality:
Any notices revoked usb authorisations is missing after flashing boeffla kernel? It was there on stock kernel. It happens both on cos 12.1.1 and cm13. [emoji54]
[ONE Original Android Development] Renosh:
There's an updated superuser version that is available from that same guy I posted not too long ago, why are you using the one from the previous COS12.1?
[ONE Original Android Development] Aavion:
Because it's just the SU binary and it still works without any issues :D Nothing changed here between 12.1 and 12.1.1, the "new version" just contains an updated debuggable kernel image, but as I always copy over the su binary manually, there's no need to download another version xD And if you flash boeffla kernel right away, there's no need for you, too[emoji14]

Gesendet von meinem Schinken.
[ONE Original Android Development] Renosh:
I'm using SuperSU 2.67 at the moment on COS12.1.1 so cannot test but can you confirm if you have the navigation bar issue described in the thread

https://forums.oneplus.net/threads/...egrated-superuser.297089/page-6#post-14354001
[ONE Original Android Development] andip71:
I am using the internal superuser in cos, no issue with tge switch to on screen buttons.

Andi
[ONE Original Android Development] Renosh:
Just to clarify you're using the older COS12.1 internal superuser?
[ONE Original Android Development] anagramgenius:
That navigation bar issue is due to the YOG4PAS3JL kernel running in YOG7DAS2K1. Nothing related to su binary.
[ONE Original Android Development] Renosh:
Where did you here that? That's definitely false I don't have an issue with onscreen navigation bar either. People are claiming the option disappeared when the su binary for YOG4PAS3JL is used on YOG7DAS2K1 so just want to confirm with the [MENTION=2707213]Aavion[/MENTION] if he's also experiencing it
[ONE Original Android Development] anagramgenius:
Same su binary is being used in both versions. Check the md5
[ONE Original Android Development] Renosh:
Definitely not true

Downloaded both from

http://jak-linux.org/cm/
[ONE Original Android Development] anagramgenius:
Obviously. Because they contain different debuggable kernels. Not the zip file's md5. su binary's md5
[ONE Original Android Development] Renosh:
Now I get what you mean, thanks bro.

Hence the comment if you use Boeffla COS12.1.1 kernel it wouldn't affect you ?
[ONE Original Android Development] andip71:
Exactly.

It requires a combination of

- a superuser binary (this can be almost any not-too-old versions, it does not affect options showing up or not9

- a kernel that matches your rom version, which is debuggable. So with my latest kernel you would not have any missing options on latest firmware. (to be precise, the decision point whether something shows up is a combination of kernel sysfs interface and selinux context/file permissions etc., which is part of the ramdisk which I incorporate in my kernel)

So in short:

- install the rom

- install any of the existing superuser enabler sripts (I took one which was for a quite old COS12.1 firmware even)

- install Boeffla-kernel

Done.

Andi
[ONE Original Android Development] Aavion:
No issues here because of:

excactly ;) but if you're using latest boeffla kernel (i guess that's why we're all here in this thread) you will have a 2k1 based kernel ;)

not the su binary, but the kernel, which is also packed into that flashable zip file, that's why I explained to flash a new kernel afterwards :D

Same as I told you. Nothing changed in superuser binary between cos12 versions. it hasn't been updated/changed since the very first first cos12 version. you may even use the binary from any cm12, 12.1 or 12.1.1 rom/nightly out there, they'll all do it's job ;)

i always used to enable the integrated superuser using the su binary from nightlies starting back in cm11s times :D

Gesendet von meinem Schinken.
[ONE Original Android Development] rsrishabh:
https://github.com/OnePlusOSS/android_kernel_oneplus_one

Please do see this update kernel source for OPO OxygenOS V2.1.4 Android L 5.1.1..

To make a better custom kernel for us
[ONE Original Android Development] andip71:
I am very well aware of that.

And you are just in the wrong thread for this topic, you need to jump on the OOS Boeffla-Kernel thread.

Andi
[ONE Original Android Development] rsrishabh:
Sorry lord boeffla
[ONE Original Android Development] andip71:
No issues.
[ONE Original Android Development] cloudx720:
Hey Andi does your kernel break power saving mode in cos12.1.1 if I'm using stock settings? Thanks ?
[ONE Original Android Development] infatality:
I doubt so.. Been using it.. Don't seems to have any issues.
[ONE Original Android Development] hsarora95:
is any kernel development going on for oxygen os 2.1.4????
[ONE Original Android Development] andip71:
I don't know, but likely as I don't allow frequencies to be changed by anyone else than Boeffla Config. Same for governor and scheduler.

You can allow overwriting though.

I myself do not use this power saving mode.

Not yet, no time yet.

But you are in wrong thread, there is an own thread for my oos kernel.

Andi
[ONE Original Android Development] mp3deviant721:
So I modified the ramdisk of 5.1b2 to boot with DU 10.0 and it boots correctly. But I can't get the config app to work with it. It gives me the error where the app cannot detect the kernel. The name of the kernel shows as expected in the about page of the ROM settings and the config app so I'm not sure what's going on. Any help?

OnePlus One | Powered by: Euphoria OS x Boeffla
[ONE Original Android Development] andip71:
It is by far more complex. You need the other ramdisk changes too, the bccontroller.sh script etc.

Andi
[ONE Original Android Development] Aavion:
you have to merge those two ramdisks, as the scripts boeffla config use to modify kernel settings as well as a lot other stuff is on boeffla kernel's ramdisk ;)

Gesendet von meinem Schinken.
[ONE Original Android Development] mp3deviant721:
So to clarify, are you guys saying I need to modify the ramdisk of the ROM I want to use Boeffla on or Boeffla's ramdisk?

Edit: what I did was take the init.environ.rc file from Dirty Unicorns ramdisk and replaced the one in Boeffla and flashed that.

OnePlus One | Powered by: Euphoria OS x Boeffla
[ONE Original Android Development] Aavion:
if it's only this one file you replaced on boeffla kernel's ramdisk, then you have to merge them instead. should be pretty easy, since they're just plain text files... just find the differences in the dirty unicorns' version and try to port them over to boeffla kernel's file...

if you run into problems, report back and please add the init.environ.rc file from dirty unicorns as attatchment then i'll have a look at it (if it's only that one file you require, i'm sure i can tinker sth for you that should do it's job :D ) and do the merge for you. then you just have to repack your ramdisk (use boeffla kernel's as base!) and you should be fine with it ^^

Gesendet von meinem Schinken.
[ONE Original Android Development] thedoctor.gz:
[MENTION=947981]Lord Boeffla[/MENTION]: new TWRP 3.0.0.0 for bacon released. What do you think about?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
Have not yet tried.

I am not missing anything with 2.8.6.0 currently, but will try next week.

Andi
[ONE Original Android Development] Aavion:
seems pretty solid... didn't come across any issues as of now... also those firmware-flash problems introduced in 2.8.7.x seem to be solved now... i'm not a flashoholic, so i didn't run further testings, but at least there're no major issues, so just give it a try :D

Gesendet von meinem Schinken.
[ONE Original Android Development] Renosh:
Everything seemed fine until I tried to restore a backup I did with TWRP 2.8.6.0 with the new 3.0.0-0. Failed giving some error with restoring the data portion. Flashed 2.8.6.0 and it works perfectly. I'll try out ketut Kumajaya's unofficial builds hopefully it works better
[ONE Original Android Development] cloudx720:
Backups and restore only works properly with the version of twrp you backed up with. Using twrp 3.0 and its working great ?
[ONE Original Android Development] Aavion:
->

known problem since ages :D

Gesendet von meinem Schinken.
[ONE Original Android Development] andip71:
CM13 kernel maintenance update

Hi guys,

small maintenance update for the CM13 kernel for you.

Version 5.1-beta3

08.02.2016

Important: This kernel works ONLY from CM nightly of 30.01.2016 onwards!!!

For older nightlies, you need to use the old 5.0 series.

Update: Updated with latest official CM kernel commits as of 08.02.16, 2pm CET

Update: Ramdisk updated to official CM13.0 version of 07.02.16

Enjoy

Andi
[ONE Original Android Development] amnik:
After flashing version 5 beta 2 and 3, the root explorer is not working.
[ONE Original Android Development] andip71:
Nothing to do with the kernel versions really.

Root explorer was never working for me since CM13.

Andi
[ONE Original Android Development] xlollomanx:
I don't know because I'm still on cm12.1, but I'm currently using root explorer and seeing latest changelog it should work on cm13 (version 3.3.8).

Sent from my Oneplus One
[ONE Original Android Development] andip71:
Yup. I saw that as well and was full of hope. But it did not fix it for me on 3 devices.

So I guess the fix ist not yet 100% mature.

Andi
[ONE Original Android Development] amnik:
For root explorer 3.3.8, it is woring on cm13 with original kernel.

It is an update specifically made for cm13 due to the use of toybox instead of busybox. You can check the changlog in google play.
[ONE Original Android Development] andip71:
I know. But it is still buggy then, I do not replace toybox etc.

So it should work. I cannot find out why it does not as the app crashes (or hangs) completely instead of giving a useful message. So, no way for me to look at anything.

Andi
[ONE Original Android Development] andip71:
Ok, the issue with root explorer is:

It cannot handle the mix of cm toybox + the kernels busybox in /sbin anymore.

Many kernels bring their own busybox in /sbin, and also my kernel needs it.

I will try to contact the dev of root explorer on that.

For the time being, you have to decide - either Boeffla or Root explorer.

I personally moved on to Solid Explorer already a while ago.

Andi
[ONE Original Android Development] Crazy_Oni:
Or total commander + plugins [emoji6]

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] rolarocka:
Guys just to tell you that you should give yankactive governor a try, its fast and battery is insane, I usually use smartmax or zzmove but yankactive is amazing. Thumbs up ?

A0001 - oneplus one
[ONE Original Android Development] andip71:
Teaser

Hi all,

nothing to do with the OPO really, but wanted to give some people a gentle teaser :D

Who can figure out what this means?

Have a great weekend

Andi
[ONE Original Android Development] vickeye:
opo x? :)
[ONE Original Android Development] schmitzekater:
More maintenance work for the Lord. ?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] josip-k:
It means you now own an OPX
[ONE Original Android Development] Stroky:
Wow! Time to get a oneplus x as a second Phone :)

Gesendet von meinem SGP511 mit Tapatalk
[ONE Original Android Development] Aavion:
Looks nice, I also had a "X" once (got one of the first invites :D ) but didn't like it much so I decided to give it away... The one and only OnePlus Phone is the ONE :D Even if it's pretty "old" now, it's still awesome ;) Will stay with it until it's life is over :D

Gesendet von meinem Schinken.
[ONE Original Android Development] mani0008:
Tried beta 3 with temasek 4.1 and the device gets really hot even when not being used. No settings changed.
[ONE Original Android Development] andip71:
Then you need to find out which process or app went crazy.

A kernel does not create the heat/load.

But custom roms like yours are also not officially supported, although many run it fine.

Andi
[ONE Original Android Development] andip71:
Guess why I am still on my Opo too.

Best phone I had so far...

Andi
[ONE Original Android Development] Crazy_Oni:
Correct. Im using it since September 2014

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] infatality:
But I believed when op2 got official support from cynogenmod with mm.. It would be the next best things.
[ONE Original Android Development] Aavion:
Me since July 2014 :D

Gesendet von meinem Schinken.
[ONE Original Android Development] Renosh:
Last I checked the main features such as laser focus for camera and fingerprint scanner don't work on custom ROMs so official CM won't fix that. Things might have changed but I doubt Oneplus would open source their source for CM
[ONE Original Android Development] andip71:
Hm. I am not sure this will drive me away from my beloved opo.

Sadly I have the same opinion...

Andi
[ONE Original Android Development] infatality:
Well.. LAF do works now.. As [MENTION=4443334]Grarak[/MENTION] fixed it using h20OS mm blobs.. Now it's waiting for FP.
[ONE Original Android Development] udo 240:
I'll have a try

---------- Post added at 11:11 AM ---------- Previous post was at 11:08 AM ----------

What profile do you use for the governor yankactive? Standard?
[ONE Original Android Development] Gawd:
The smoothest Kernel I've flashed till date. The optimizations are worth it. The best out there. Using it on CM13 10/02 build and it almost doubled the battery life with performance enhancements! Thank you OP.
[ONE Original Android Development] Jole7:
+1 very good kernel and great stability!
[ONE Original Android Development] magnamentis:
LAF is working for a week already and FP is close to, currently running CM13 based rom and it's close to satisfactory, just way faster and snappier as compared to the OPO ( which i have side by side to compare ) and that's on cm kernel LOL.
[ONE Original Android Development] infatality:
200% Agreed.. Just hoping official oxygen mm and source will be out soon.. Have faith and keep calm. It will be out.
[ONE Original Android Development] andip71:
Kernel updates

Hi all,

updates for CM13 and COS12.1.1 kernels for you.

COS12.1.1 -- Version

4.2-beta5

15.02.2016

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

Change: Removed useless GPU overclocking frequency 657 MHz (this was never working and technically also cannot due to locked GPU frequencies on Snapdragon 801)

CM13 -- Version 5.1-beta4

15.02.2016

Important: This kernel works ONLY from CM nightly of 30.01.2016 onwards!!!

For older nightlies, you need to use the old 5.0 series.

Update: Updated with latest official CM kernel commits as of 15.02.16, 8am CET

Change: Removed useless GPU overclocking frequency 657 MHz (this was never working and technically also cannot due to locked GPU frequencies on Snapdragon 801)

Update: Ramdisk updated to official CM13.0 version of 14.02.16

Enjoy

Andi
[ONE Original Android Development] Aavion:
Typo,I guess, since we have a 801 ;)

Edit: Oh I see you've already corrected this :D

Gesendet von meinem Schinken.
[ONE Original Android Development] andip71:
Yes, Typo. And I realized it quite quickly.. have too many devices though, the OP2 has a Snap 810, so I mixed it up.

Andi
[ONE Original Android Development] Aavion:
What is 4.2b6? :D

Gesendet von meinem Schinken.
[ONE Original Android Development] andip71:
Updates

Hi all,

last kernel betas from previous today are pulled and replaced with a new betas already.

COS12.1.1 -- Version

4.2-beta6

15.02.2016

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

Fix: Lower GPU frequencies not properly used with last kernel version is fixed

CM13.0 -- Version 5.1-beta5

15.02.2016

Important: This kernel works ONLY from CM nightly of 30.01.2016 onwards!!!

For older nightlies, you need to use the old 5.0 series.

Fix: Lower GPU frequencies not properly used with last kernel version is fixed

Enjoy

Andi
[ONE Original Android Development] andip71:
See above :)

Andi
[ONE Original Android Development] cybersonic2k:
I installed the new beta6. But after this is root gone. :(

I try supersu 2.46, 2.65 and 2.67.

TWRP is the new v3.

COS12.1.1 version YOG7DAS2K1 is already installed
[ONE Original Android Development] cloudx720:
I'm getting a lot of boeffla app crashes with latest cos12.1.1 kernel and latest boeffla app. Mostly happens when switching between profiles, something to do with the gpu removal changes ?
[ONE Original Android Development] Crazy_Oni:
Andi is working in a fix for this problem.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] gianton:
I get 1241 mA with stock charger on latest beta with default settings.
[ONE Original Android Development] DjDiabolik:
On italian official boards i have post some result about last night charcing from 10/11% to 100%........ but it's all in italian and the value it's set to "default" 1500mA:

If you need i can try to traslate it to english....... but the 1500mA it's only a nominal value i thinks and i thinks it's a great idea, my 1+1 has reach the 100% in about 2 hours (whit wi-fi connected and the config app ever opening in background)....... whit the stock kernel the same charging usually has been completed with nearly 40 additional minutes...

After that i have notified an average value at:

16465 / 15 check = 1097,66666666666666667mA