yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] kryshnakishore:
Completely wrong.. Anyway as u said u are on custom recovery since 2 years... Wait for full zip then
[ONE Original Android Development] molonad:
Thanx for Dont helping me ? anyway i Will wait.
[ONE Original Android Development] kryshnakishore:
Hey buddy what help u need? U said u dnt want to install stock recovery then its not possible to update till date so i said to wait for full zip... What u need letme know
[ONE Original Android Development] Aavion:
Safe way to update:

- Download 2k1 factory image

- Download 26M incremental

- Download 2JK incremental

- Make sure "Update CM-Recovery is checked in Dev options

- fastboot flash 2K1 system.img, recovery.img & boot.img (data remains untouched, so no data loss)

- boot into recovery (NOT into system, as it'd produce a lot of errors because of the "downgrade")

- flash 26M incremental

- reboot into system once (to let it update stock recovery)

- reboot into recovery

- flash 2JK incremental

(- you may reboot into bootloader now to flash twrp again)

(- you may now use twrp to flash boeffla kernel and superuser, 5.0b3 works well on this build)

- Reboot & Done.
[ONE Original Android Development] cybersonic2k:
Great!

But have anyone stock recovery from 26m?

Its needed for the update!

I have tested the 2k1 and cm13 recovery. No success.
[ONE Original Android Development] molonad:
Hello Mistr boeffla, iam now testing cos13 with your kernel. I noticed that if u set up all cores online and frequency above 2,5, only one core is above 2,5 and three other cores are still on 2,5. I tried 4 cores min with performance governor.
[ONE Original Android Development] andip71:
Most likely mpdecision capping max frequencies due to thermal reasons.

I also saw, this gets pretty quickly reduced. But a cool phone runs with high frequencies on all cores.

Andi
[ONE Original Android Development] Aavion:
How-To go back to stock recovery:

- Make sure "Update CM-Recovery" is checked in developer options

- Make sure "/system/recovery-from-boot.p" has not been renamed by TWRP. If it is, rename it back!*

- Reboot once. Stock recovery will automatically get flashed during boot process.

*) TWRP renames that file to recovery-from-boot.bak, so it wont get replaced by stock recovery at every boot. Just rename it back to recovery-from-boot.p
[ONE Original Android Development] cybersonic2k:
Thx, i made it so.

But its don't work ?

Have you test this?
[ONE Original Android Development] cloudx720:
I've recently acquired a S5 lte-a 901f with the snapdragon 805 soc I really love my opo o need to sell one of them really finding it hard to choose lol :(
[ONE Original Android Development] kewinhdorff:
i would go with the Oneplus one (if i were you) juste because of samsung knox, samsung not being fully opensourced?

to me oneplus one is just much better than samsung :)

i have had samsung before and i must say i would rather root and flash on my oneplus one than on a samsung device. :)
[ONE Original Android Development] Matteo_666:
Stick to the 1+. Theres not even an official cm available for the 901... And yea, Knox sux :)

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
No question, I would sell Samsung and keep the oneplus.

Andi
[ONE Original Android Development] GirishSharma:
... but friends, be cautious of overpraise too! example : Microsoft and Google...
[ONE Original Android Development] kurtextrem:
Do we have an internal cm root zip for cos13 already?
[ONE Original Android Development] Aavion:
Just use the ZIP from [MENTION=947981]Lord Boeffla[/MENTION] s website. As it contains only the cm su-binary, it'll work fine until cm/cos push huge changes to their root-implementation :)
[ONE Original Android Development] Aavion:
PS: it's this file.
[ONE Original Android Development] mp3deviant721:
Aww. Boeffla homepage is down. :(

OnePlus One | Powered by: Euphoria OS x Boeffla
[ONE Original Android Development] Ely-droid:
Guys, I need a little help from you (because i'm in bootloop and i haven't old working kernel). Can I ask for Boeffla-kernel (COS-YOG4PAS3JL) mirror?
[ONE Original Android Development] andip71:
No mirrors please.

Thank you

Andi
[ONE Original Android Development] Ely-droid:
Ok, no problem! I was asking for a mirror because "http://www.boeffla-kernel.de/" is down.
[ONE Original Android Development] ZaneZam:
even though its not the official version maybe this can help u out

https://www.mediafire.com/folder/s2c5mb1sm5o0j/bacon -> old obsolete versions ;)

https://www.mediafire.com/folder/68s0on2p15qzf/stable -> latest
[ONE Original Android Development] andip71:
I know, my web hoster has big issues with the database servers for the last 2 days. They are working on it.

I put up a static emergency page now, to make at least all download links working again.

Andi
[ONE Original Android Development] Dedzdedz:
Just flashed kernel, trying zzmoove (standard) with -25mv undervolt on CM13, no issues flashing the kernel by the way. Feels very snappy

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] molonad:
Phone is cool, i didnt use that for a few hours and i tried again performance 4 cores min and still only one core is on 2,7 rest of them on 2,5.
[ONE Original Android Development] cloudx720:
The features the 901F has is pretty awesome tho like cat6 LTE way better gpu (andreno 420) fingerprint scanner. The only con I can think of is no official cm support :( I can't bring myself to sell my opo might just keep both lol
[ONE Original Android Development] andip71:
Even if you think the phone is cool... you are using performance governor.

This means - the governor always runs all cores on highest frequencies (as performance is not a real governor, it just pushes cpu to max, thats it).

So that means, as soon as you switch on your phone, all cores get enabled and run with overclocking frequency.

It is very obvious, this will be detected very soon in significant temperature changes and then mpdecision will bring this back to normal to not overheat your phone.

Things you cannot "feel", but internally it happens.

I would NEVER suggest to use performance governor, especially not with overclocking. This breaks the whole concept of a governor.

Samsung = never again for me :cyclops:

Andi
[ONE Original Android Development] ch-vox:
Hi Andi,

I'm really interested in using DND Helper as I miss this feature in COS 13 too.

When do you plan to release it please ?

Have a nice day ;)
[ONE Original Android Development] ptrueber:
Hello,

I've compiled the kernel myself with the arm-linux-androideabi-4.9 toolchain and it boots fine. However, neither I am not able to load any modules build by the build process itself (e.g. asix) nor can I load my build modules. Both result in the error: "insmod: can't load module: bad address". Do you have an idea whats happening?

Thank you for your work!
[ONE Original Android Development] andip71:
Yes. CM built-in Toybox has a broken insmod command for quite some time.

You need to use busybox to do the insmod. Then it works.

Andi
[ONE Original Android Development] andip71:
Check your PM please.

Andi
[ONE Original Android Development] andip71:
Maintenance update for CM13 kernel:

Version 5.1-beta18

25.04.2016

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

Update: Ramdisk of official CM13.0 build of 25.04.16

Enjoy

Andi
[ONE Original Android Development] molonad:
I Only tested overclocking, i Dont use performance governor at all. Only for this little test. Also with interactive and overclock, still only 1 core overclocked. Rest of them normal frequencies. But I dont Care about it. Iam using stock frequencies, i was just curious. Thank you
[ONE Original Android Development] ptrueber:
Thank you; that worked and thus helped a lot!

Best regards
[ONE Original Android Development] andip71:
Good evening guys,

finally two COS updates today, then I call it a day for now :)

COS12.1.1 receives a new final stable release, COS13.0 a new beta version.

COS13.0 -- Version

5.0-beta4

25.04.2015

Note: You should update to COS13 version ZNH0EAS2JK to use this kernel version !!

Change: Ramdisk updated to rom version COS13 ZNH0EAS2JK

Change: Internal kernel tick rate (HZ) bumped from 100 to 300

COS12.1.1 -- Version

4.3 stable - final

25.04.2016

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

Change: Internal kernel tick rate (HZ) bumped from 100 to 300

Enjoy

Andi
[ONE Original Android Development] agentg1001:
Latest cm13 4/25 kernel "feels" fast. Or is it just me ?. Either way, great work Lord Boeffla, I appreciate your help keeping this device going, I see no good reason for me to upgrade for a good while.
[ONE Original Android Development] andybfmv96:
Does this kernel by chance support kexec?
[ONE Original Android Development] Pablo.x:
Yes.

Enviado desde mi OnePlus One.
[ONE Original Android Development] andybfmv96:
Thanks and sorry! I re-read the OP and found it
[ONE Original Android Development] atulclassic:
isn't there going to be a test version with tick rate or you made it permanent?

we still don't know the effects on battery life.
[ONE Original Android Development] andip71:
It is already permanent.

General opinion is, there is no to only very less impact on battery.

It is getting more and more included by cm team officially as well.

Andi
[ONE Original Android Development] Crazy_Oni:
Since the new tick rate im facing random freezes with your kernel on the latest cm13 nightlies. With the stock kernel everything works fine. They are so strong that i have to hard reboot my opo.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Interesting as I

- did not change the tickrate commits of CM at all -> these are the original ones

- have no freezes here so far

Andi
[ONE Original Android Development] Crazy_Oni:
Hmm okay. So I reflashed your latest kernel, resetted amplify back to normal and gebootet. let's see what happens now.

Gesendet von meinem X98 Pro mit Tapatalk
[ONE Original Android Development] kaneelias:
Running RR CM13 Nightlies, I flashed your kernel and I am stuck at the 1+ start screen, any advice?
[ONE Original Android Development] kryshnakishore:
Reboot to twrp recovery and flash original stock cm13 kernal, this time make sure u flash correct version
[ONE Original Android Development] kaneelias:
Sorry, are you saying I need to flash the stock before I can flash Boeffla? sorry I am a little new to this, I appreciate your help.
[ONE Original Android Development] kryshnakishore:
No, u might have flashed wrong kernal... You should flash kernal based on your rom.. Search for cm13 stock kernal and flash it or download boeffla-kernel for cm13 and flash it.
[ONE Original Android Development] kaneelias:
So I flashed this version CM13.0 - Stable:	5.0 from the Boeffla website

I am currently running this rom [ROM][6.0.1_r30][BACON][OPTIMIZED]RESURRECTION REMIX M [5.6.7][CM13]

As far as what I have read from that thread, it is compatible.
[ONE Original Android Development] akash4357:
Most probably the stable version is too old and no longer compatible with latest CM13 changes. Flash the lastest test version.
[ONE Original Android Development] kaneelias:
Ok, I did not even consider that. Thanks for the help.
[ONE Original Android Development] kryshnakishore:
I dnt know exactly but he mentioned "This kernel will NOT work on stock COS13 but only on genuine CM13.0 builds !!!" for cm13 - stable 5.0
[ONE Original Android Development] Sander9847:
But ResurrecrionRemix is a cm13 build.

It works you have to use the latest 5.1 beta and flash it after you've let RR boot up once and have let it optimize apps. Only then you can flash Boeffla and be sure not to wipe caches after this (rom might bootloop again).
[ONE Original Android Development] andip71:
RR is not fully compatible. They changed things to break full CM compatibility.

Wrong, it is not anymore.

They changed things in the ramdisk which cause the known effects.

So it bases on CM, but is not 100% compatible anymore.

And once again - sorry guys: I do not care if other roms than official CM work or not. I am very rigid here.

Andi
[ONE Original Android Development] kaneelias:
Thanks for clarifying, that is why I was getting stuck. I appreciate your work. Cheers.
[ONE Original Android Development] cloudx720:
Sorry to say I sold my opo maybe I'll be back one day on the oneplus 3! Peace.
[ONE Original Android Development] andrew2511:
Hi [MENTION=947981]Lord Boeffla[/MENTION] I've a weird bug about soft keys light using latest COS13 b

4

[über typo was here] but happening since first release.

When I power on my Opo, after the boot, I start using it and the lights are on, I continue using it but the light (after the 25 second I set) go off even if I'm continuing using it. Only method to light them up again is to shut off the screen and unlock again. Then it works as it should.

I'm not sure if I explicated well the bug... May you look into this? Thank you :)
[ONE Original Android Development] andip71:
I cannot change this. The kernel settings need to be applied first after the reboot and then the screen must be off at least once to initialize the logic.

So this is a one time glitch after a reboot when combined with super long light durations.

Andi
[ONE Original Android Development] atulclassic:
Where is COS13 b5?

last release is beta4
[ONE Original Android Development] andip71:
Correct. Must have been a typo he did. I never released a b5 so far :)

Andi
[ONE Original Android Development] Aavion:
Maybe he is time travelling like our May 1 security patches :D
[ONE Original Android Development] hellcat50:
I know, I know... ;)
[ONE Original Android Development] andip71:
Good good :D
[ONE Original Android Development] twowheeler:
What does changing the tickrate do? Does this mean the amount of times the kernel checks for changes?

Still waiting for the full cos13 zip, but just being able to stick with your kernel is worth it. Might move to cm though

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] andip71:
Useful article on it here:

https://lwn.net/Articles/145973

And yes, it is on a very high level pretty much like you said.

Andi
[ONE Original Android Development] kingsathurthi:
System R/S issue

I'm in latest build Cos13 ZNH0EAS2JK having issue

How to fix this? Is this kernel working fine?

Attached below

[IMG="issue"]http://img4.imagetitan.com/img.php?image=13_screenshot_20160428-160732.png[/IMG]
[ONE Original Android Development] andip71:
Something prevents the app to access the system partition properly.

If a reboot does not help we need to understand what rom you are using.

Andi
[ONE Original Android Development] kingsathurthi:
Reboot doesn't help!

I'm currently using Cyanogen-os 13 ZNH0EAS2JK ROM

Kernel version : boeffla-kernel-5.0-beta4-COS13.0-bacon.recovery
[ONE Original Android Development] andip71:
Any mods installed, custom busybox etc? Xposed?

Something is wrong.

Andi
[ONE Original Android Development] kingsathurthi:
Yes sir

1.Using busy box pro

2.Xposed v83
[ONE Original Android Development] andip71:
:)

Then my mission ends here... see OP pls.

Andi
[ONE Original Android Development] kingsathurthi:
Haha OK sir

But i used Boeffla kernel in cos 12.1 3jl build

With xposed n busybox app

There is no problem like this!

I think cos 13 may be having a issue to access the system partition
[ONE Original Android Development] andip71:
Not in general, nobody else reported this so far.

You can go to a terminal and type the following command:

su

mount -o rw,remount /system

mount

... and send me the output of that. Maybe we can spot the issue then.

Andi
[ONE Original Android Development] andip71:
you missed a space in this command:

mount -o rw,remount/system

it should be as I wrote:

mount -o rw,remount /system

Please redo.

Andi
[ONE Original Android Development] kingsathurthi:
Sorry sir

Now I entered properly :)

id: unknown ID 10149

10149@bacon:/ $ su

root@bacon:/ # mount -o rw,remount /system

root@bacon:/ # mount

rootfs on / type rootfs (ro,seclabel,relatime)

tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1455496k,nr_inodes=140484,mode=755)

devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,seclabel,relatime)

selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)

debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)

none on /acct type cgroup (rw,relatime,cpuacct)

none on /sys/fs/cgroup type tmpfs (rw,seclabel,relatime,size=1455496k,nr_inodes=140484,mode=750,gid=1000)

none on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)

tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1455496k,nr_inodes=140484,mode=755,gid=1000)

none on /dev/memcg type cgroup (rw,relatime,memory)

none on /dev/cpuctl type cgroup (rw,relatime,cpu)

none on /sys/fs/cgroup/bfqio type cgroup (rw,relatime,bfqio)/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (ro,seclabel,relatime,data=ordered)

/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type ext4 (rw,seclabel,relatime,noauto_da_alloc,errors=panic,data=ordered)

/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type f2fs (rw,seclabel,nosuid,nodev,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,extent_cache,active_logs=6)

/dev/block/platform/msm_sdcc.1/by-name/persist on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,nomblk_io_submit,nodelalloc,errors=panic,data=ordered)

/dev/block/platform/msm_sdcc.1/by-name/modem on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)

adb on /dev/usb-ffs/adb type functionfs (rw,relatime)

tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1455496k,nr_inodes=140484,mode=755,gid=1000)

/dev/block/loop0 on /su type ext4 (rw,seclabel,noatime,data=ordered)

/dev/block/loop0 on /system/xbin type ext4 (rw,seclabel,noatime,data=ordered)

/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)

/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)

/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)

/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)

root@bacon:/ #
[ONE Original Android Development] andip71:
Ok, so here it comes in the result:

/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (ro,seclabel,relatime,data=ordered)

After what you entered, the red marked part should be rw and not ro (read-write vs. read-only).

Something blocks the system volume to be mounted read-write. And this is what the app - rightly - complains about.

But what exactly causes that block, I do not know.

Can you please try also the following:

su

/sbin/busybox mount rw,remount /system

mount

Curious if busybox pro causes the issue.

Thanks

Andi
[ONE Original Android Development] andip71:
Hi,

good to read that.

And yeah, Boeffla-Config app is pretty smart and detects when something it not fully correct which it needs...

Cheers

Andi
[ONE Original Android Development] kingsathurthi:
I like Boeffla kernel very much, you are awesome sir, Boeffla (kernel) doesn't make my phone(opo) to very hot, but it makes me very happy... LoL
[ONE Original Android Development] fards:
Don't we use dynamic tick by default? I remember the patches when it first changed. Arm code was one of the first to use it.

I admit I've not been keeping up with kernel lately so not sure what stock is anymore.
[ONE Original Android Development] suaverc118:
I noticed recently when I've exited out of the app and then go open it back up, it starts all over again, like starting the app and initializing it. Is that normal and I'm just noticing it?
[ONE Original Android Development] andip71:
No, was never used in Android kernel.

Yes, this is intended behaviour.

It was always the case, just now you see it very clear due to the progress dialog.

Background: remember my design goals for the app - no cpu, memory or battery usage when you don't use it.

To make this absolutely sure, I try to unload as much as possible when someone exits the app.

If you don't exit it but put it to background by touching the home button, you see the difference when you launch it again.

So yes, I want it to behave exactly like that to be as lean and light as possible when not open.

Andi
[ONE Original Android Development] inzaghi89:
I've thinked about this since last few days and I must to ask. In boeffla app there are some presents (predefined settings). Each of them are tested by you Andi or what? I'm just curious about that but didn't find any answer for my question. Lest say I'm using 'standard' present for each day using. But when my phone stays down and I'm not using it I switch to battery saving which should impact on battery life.

Wytapane na Oposie.
[ONE Original Android Development] Dedzdedz:
Can anyone share a custom user setup for both battery and performance? I do not play heavy games...

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] Anlle:
Can i install boeffla kernel to my samsung galaxy trend plus GT-S7580?

Sorry for my dumb question i am noob i just want know if my phone is compatible or supported in this? Or you can suggest what kernel i install:) :good:
[ONE Original Android Development] andip71:
It is plain simple:

When you have a OnePlus One phone (regardless what variant... European, Chinese, whatever...) then the kernel works for you.

If you have a different phone, then not.

I guess you have a OnePlus One when you posted in a OnePlus One kernel thread? :)

Andi
[ONE Original Android Development] andip71:
Hi there,

maintenance update for CM13 kernel:

Version 5.1-beta19

02.05.2016

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

Update: Ramdisk of official CM13.0 build of 02.05.16

Change: Enhancements to kernel build script

Enjoy

Andi
[ONE Original Android Development] Lookitfast:
Personally I run either Smartmax governor & zen, Smartmmax/fiops or ZZMoove/Zen with ZZMoove optimal profile. 2048 Read ahead with charging at max. Love this kernel..best I've tried by far for me. Thanks [MENTION=947981]Lord Boeffla[/MENTION] ;):D;)
[ONE Original Android Development] zertyuiop:
I have a bug on the latest COS: after some time the screen turns off, OPO does not respond. Restart helps. In device manager on computer it looks like bricked.
[ONE Original Android Development] andip71:
I think you said it very precise: YOU have this bug.

We have not. At least have not heard of that from any other user + do not have it myself.

Andi
[ONE Original Android Development] Anlle:
I have a Samsung phone not OnePlus One.

Ok I understand thanks for the information you gave :fingers-crossed: :good:
[ONE Original Android Development] Franc38:
Could be that it froze, and as such blocked everything else?

I had a similar thing happen to me a while ago, with a different app. Was temporary, though, and after 20 odd seconds, everything was working again.
[ONE Original Android Development] BrunoNRG:
I guess the only thing I can do is wait and hope it won't happen again ;)

Thanks! :good:
[ONE Original Android Development] gianton:
I guess as Andi said we have to wait for an update to fully support 44S.
[ONE Original Android Development] andip71:
Well, I quickly checked despite being on holidays.

Code wise Boeffla Kernel is already completely up to date, there were no newer patches to integrate.

Just I will update the ramdisk to the 44 one when I am back.

Andi