yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] chenrp:
Boeffla,

how come you decided that the OPO can charge only at 2.0A?

i see devices with PM8941 that can get 2.5A...

when i use 2.0A i get 2.0A (tested with external device)

maybe i can get more current if the limiter be higher?
[ONE Original Android Development] andip71:
Nope. I tried it with my USB current meter. 2.0A is the maximim the OnePlus One allowed.

Andi
[ONE Original Android Development] Klobal:
The original EU wallcharger should be rated with 2,2A, while the US or Asia Version is only rated 2,0A, if I remember correctly. I'm curious why it is different.
[ONE Original Android Development] andip71:
Well, different versions, designs, whatever.

But a wall charger that can deliver 2.4 A (like mine here for example) does not deliver more than the phone requests anyways.

Andi
[ONE Original Android Development] Ben_Li:
Flashed the stable and beta. Just reboots back to recovery
[ONE Original Android Development] andip71:
Sorry, but then something must be completely messed up.

There is no reason a device would itself boot into recovery at all when boot loaders, rom and kernel are matching.

Something is wrong. But as you use an old snapshot version from April, which is about 3 months old already - I would expect all sort of issues.

My kernels are made for nightlies, not for snapshots.

So you would need to find a kernel version old enough to match approximately your snapshot date. But I took them probably off already as I would not recommend using that old roms without latest security patches anyways.

Andi
[ONE Original Android Development] kryshnakishore:
Badly waiting for any kernal app

I do charge my opo at 2050mah with original charger & cable on Resurrection remix rom. 0-100 % in 90mins. Max opo can take upto 2100 I guess on RR ROM
[ONE Original Android Development] andip71:
you can configure it that high. But it will still not use more than the hardware limitations allow.

Andi
[ONE Original Android Development] siddharth.srivastava:
Does this work with cm13 6.0.1?
[ONE Original Android Development] andip71:
No, only with CM 10.1. Sorry...

:D

*sarcasm-end*

Have you ever looked at the kernel page www.boeffla-kernel.de, whether you find a CM13 kernel there?
[ONE Original Android Development] andip71:
Anykernel arrived

Hi all,

it is time for the first CM13 kernel with the new anykernel concept.

Before you start, make sure you have read and understood the following:

http://boeffla-kernel.de/index.php/70-know-how-about-new-anykernels

If you ask questions which are addressed in this article, or you have issues which are a consequence of not reading the article, I will not answer. It is your responsibility to understand what you do BEFORE you do it.

(and also read this for more background: http://boeffla-kernel.de/index.php/69-new-concept-kernels-new-app)

Side note:

Although the kernel is now likely to be much more compatible with custom roms using CM basis, I will not change my support conditions at all. If you report an issue on a non-original CM rom, do not expect me to react (http://boeffla-kernel.de/index.php/support/support)

Ensure you update to latest Boeffla-Config App 2.3.1 BEFORE you flash the new kernel !!!

Enough threatening now, here we go:

Version 5.2-beta1

12.07.2016

Note: This is the first Boeffla-Kernel with the new anykernel concept.

Make sure you read and understand the basics: Boeffla-Anykernel Know-How and New concept kernels/New app

Note: You have to use Boeffla-Config version 2.3.1 or newer in order to use all functionality !!

This kernel as exactly the same functionalities as the last stable kernel release

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

Enjoy

Andi
[ONE Original Android Development] Grobie13:
One question lasts for me, is the new anykernel for COS too or only for cm? That's the point I can't find out by myself, although the documentation is very well written.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] atulclassic:
for CM only since COS13 has no new changes in kernel and COS 5.1 stable is running perfect already hence no need of anykernel (till now)
[ONE Original Android Development] kryshnakishore:
Installed new app & flashd any kernal on my RR ROM, works perfectly even after cache wipe.

I mean to say for any roms can u provide " boeffalo configuration app ".. With out flashing your cm kernal I should be able to use boeffalo config app for other roms.. Ex. kernal auditor app which works for any rom
[ONE Original Android Development] andip71:
No, there will be a separate OOS kernel coming for it.

OOS kernel code is not the same as CM13.

Ok, this will not happen.

My app ties so deeply into my kernel, it only works with my kernels also in future.

It will never work with non-Boeffla kernels.

Andi
[ONE Original Android Development] kryshnakishore:
Hmm that's OK .. Thanks for solving(new anykernal version) bootloops in RR ROM
[ONE Original Android Development] MMWolverine:
5.2 beta running great on latest ResurrectionRemix as secondary rom, no bootloop after wiping caches. I'm so glad you finally decided to use anykernel. :D :good:
[ONE Original Android Development] kryshnakishore:
Just asking : (using RR rom + Boeffla cm13 kernel)

Is cpu temp related with kernal?? temp is waking around 60'c..

---------- Post added at 01:00 PM ---------- Previous post was at 12:58 PM ----------

Can u check ur cpu temperature.. Before it used to be around 50c, with anykernal on RR ROM Its around 60c now
[ONE Original Android Development] andip71:
Well, was not my intention of doing anykernel, but it is a pleasant side effects for you.

CPU temperature is related to CPU work load, not kernel.

Andi
[ONE Original Android Development] MMWolverine:
55°C maxed after playing Real Moto for 10 min, with cpu/gpu freq considerably reduced & zzmoove-relax + native hotplug.
[ONE Original Android Development] kryshnakishore:
Thank u for sharing.. Now it's normal for me too... I play asphalt with no changes in kernal profile, It goes upto 62c...can I know at what temp should I really worry ( if it reaches 70 is that ok)

---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------

Lord can we get config-app widget so that we can change profiles based on usuage in a handy way
[ONE Original Android Development] andip71:
80 C is still ok.

And no widget as misusing a widget is the wrong approach here.

You can achieve what you want already now. You can place homescreen shortcuts for your profiles.

All in the documentation on www.boeffla-kernel.de

Andi
[ONE Original Android Development] kryshnakishore:
Thank u opo is really a beast.

Got it, I missed it all these days
[ONE Original Android Development] hellcat50:
so far it's working fine on dirty unicorns, will test it further and report back.
[ONE Original Android Development] iwjy:
Flashed 5.2 Beta-1, Boeffla Config 2.3.2 always fail to initialize. Always ask to reboot, done it multiple time with no success, All permission are already given and doesnt greenify it (have it installed).

I'am on fresh install CM 13.0 0712 nightly, using built in root. Currenty reverting back to 5.1 without problem.
[ONE Original Android Development] silvagroup:
Any chance we'll get this great kernel on OP3 ?

Have two OPO's running it and it's awesome. Now need it for the 3 if possible ???
[ONE Original Android Development] feed3:
Face the same issue few hours ago. Reflashing it again (5.2 beta) fix it. Maybe not properly flashed by twrp on first flash. (Reflash the nightly first to get the stock kernel before reflashing boeffla)
[ONE Original Android Development] Nichie:
I know the COS anyKernel is not out yet but just wanted to ask this.

I read that for anyKernel is best to be flashed from stock kernel. What about it the previous kernel was a boeffla kernel?

Is it still better to flash stock ROM first then flash anyKernel version?
[ONE Original Android Development] kryshnakishore:
Yes, He mentioned to flash stock rom first & then flash anykernal
[ONE Original Android Development] andip71:
Going back is not a solution.

If Boeffla-Config complains about this, there is a reason for it.

And the reason is, it could not start or load the initialization script during last boot.

A minority of people report this, so I would be eager to find out why.

Did you Greenify the Boeffla-Config app?

Did you install anything else that might break apps starting at boot time?

Have you followed all of this?

http://boeffla-kernel.de/index.php/70-know-how-about-new-anykernels

I answered that many times already.

Currently I do not have capacity to do anything. And seeing how the OP3 behaves with stock kernel, I do not even see an immediate need for a custom kernel.

http://boeffla-kernel.de/index.php/70-know-how-about-new-anykernels

Majority of your questions should be answered here.

Thanks for not reading :(

And yes, ideally you flash OOS stock kernel first (or flash OOS rom dirty over again).

Andi
[ONE Original Android Development] Nichie:
I did read the whole thing just thought that if coming from boeffla non anykernel was required or not.. thanks anyway! :)
[ONE Original Android Development] iwjy:
Got it working after flashing 5.2 over 5.1, nothing else changed. I did read all the expalnation on the link you provided, and have checked for permission, root access, greenifiy etc. The app doesnt seem to load the default profile.

And as I've said, the problem seems to be solved after flashing the beta over 5.1. After that tried reflash the nightly and then 5.2 beta, and it works.

And thank you for providing this great kernel.
[ONE Original Android Development] Renosh:
I'd love it if you elaborate on this piece of info you've dropped about the OP3 stock kernel on how it behaves and performs
[ONE Original Android Development] andip71:
Simply, it behaves almost perfect already.

The only thing I want to be able to change is LED blink speed.

Rest is fine for me. So the question is, whether I ever need to do a kernel for it.

Andi
[ONE Original Android Development] kryshnakishore:
Start a poll or donation before developing kernal & keep threshold like $100. If u reach then start kernal for op3. Hardworking Is never free. The right/needy person donates you. #Myopinion only for Lord
[ONE Original Android Development] kurtextrem:
Yesterday the full zip for the new COS Update came out. Would you say we should wait for anykernel version? :D
[ONE Original Android Development] andip71:
Oh yes, because the kernel code was not changed. Only the ramdisk, hence the anykernel version of the kernel makes the kernel 100% perfectly compatible.

It will still come out today.

Andi
[ONE Original Android Development] kryshnakishore:
After reboot, Clicking on Boeffla default profile applied on notification bar doesn't open the app
[ONE Original Android Development] andip71:
Correct. And it should not open the app.

This has been removed already, uff... maye 1.5 years ago.

Clicking the notification just closes the notification.

Andi
[ONE Original Android Development] kryshnakishore:
1.5 yrs ago..OMG I missed this too,noticed today. (using app since 2015)
[ONE Original Android Development] andip71:
Anykernel arrived

Hi all,

it is time for the first COS13.1 kernel with the new anykernel concept.

Before you start, make sure you have read and understood the following:

http://boeffla-kernel.de/index.php/7...new-anykernels

If you ask questions which are addressed in this article, or you have issues which are a consequence of not reading the article, I will not answer. It is your responsibility to understand what you do BEFORE you do it.

(and also read this for more background: http://boeffla-kernel.de/index.php/6...ernels-new-app)

Side note:

Although the kernel is now likely to be much more compatible with custom roms using CM basis, I will not change my support conditions at all. If you report an issue on a non-original CM rom, do not expect me to react (http://boeffla-kernel.de/index.php/support/support)

Ensure you update to latest Boeffla-Config App 2.3.3 BEFORE you flash the new kernel !!!

Enough threatening now, here we go:

COS13.1 -- Version

5.2-beta1

13.07.2015

Note: This is the first Boeffla-Kernel with the new anykernel concept.

Make sure you read and understand the basics: Boeffla-Anykernel Know-How and New concept kernels/New app

Note: You have to use Boeffla-Config version 2.3.3 or newer in order to use all functionality !!

This kernel as exactly the same functionalities as the last stable kernel release

Enjoy

Andi
[ONE Original Android Development] kalapapa:
You can change the speed of light blink by using light flow app

Highly recommend pro version for best experience
[ONE Original Android Development] andip71:
I purchased it years ago. But would like to avoid it and prefer a kernel driver for it.

But good tip nevertheless.

Andi
[ONE Original Android Development] siddharth.srivastava:
Yeah i did see it. Just wanted to confirm lol

Thanks for answering
[ONE Original Android Development] alvin182:
This works in the last

cm-13.1-ZNH2KAS254-bacon-signed.zip. ??
[ONE Original Android Development] teXew:
Yes

Sent from Oneplus One
[ONE Original Android Development] andip71:
Absolutely. And the nice thing about the anykernel concept is - it works 100% as it should with the latest kernel. I do not even have to do an update as only the ramdisk changed, which you will automatically get with the anykernel method.

So, it already saved me from releasing a dedicated kernel for ZNH2KAS254, it is just not neccessary anymore :)

Andi
[ONE Original Android Development] alvin182:
Thanks Lord Boeffla;)
[ONE Original Android Development] chenrp:
New beta kernel is not working 4 me. The rom boots but the boeffla config is saying that there is an error and that i should try to reset the phone again.
[ONE Original Android Development] andip71:
Yes. Then there is an error and you need to fix it.

As you did not at all provide the information we need (listed under support on kernel homepage), nobody can help you.

As the kernel works for many hundreds of people, it must be an issue with your installation.

Andi
[ONE Original Android Development] andip71:
BTW, the message for sure does not say you need to "reset" the phone. I know all messages I put in.

I am sure you did also not read the article on what you need to take care of with the new kernel...

Andi
[ONE Original Android Development] NickosD:
I get this error. I am using jgcaap rom and already checked everything. All permissions granted. How can I fix this?
[ONE Original Android Development] kalapapa:
Jgcaaps ROM won't be fully compatible anyways as he uses different camera hal
[ONE Original Android Development] NickosD:
Thanks for the tip. Didn't know that.

ZaneZam already released a version with coloros blobs. It's not a kernel issue to post it there, app issue.
[ONE Original Android Development] Pablo.x:
It stills happening after rebooting?

Enviado desde mi OnePlus One.
[ONE Original Android Development] chenrp:
Not reset, reboot again. The new beta kernel is not working 4 me. The stavle does work.
[ONE Original Android Development] chenrp:
Attached!
[ONE Original Android Development] andip71:
When this message comes up, SOMETHING IS WRONG.

I do not know why people say it is a problem.

You have to make sure the app is allowed to start after boot and has full root rights. No greenify, no blockers etc.

Also you need to be on latest app version.

If all that is true, do the following:

- delete file /boeffla-kernel-data/bc.log

- restart device

- wait for 3 minutes, do NOT start Boeffla-Config

- usually a notification like "profile xxx has been applied" should show up in the notification bar (let me know if not)

- send me the bc.log file which has been created after start (not the bc.log.1 or 2 or 3 files!!!)

- if you cannot find a bc.log file after a few minutes, the app is blocked to start and that is the whole problem which YOU need to fix

But it is "nice" to see everyone ignors apparently what the app tells. The app says:

- first reboot

- if it does not work, check for permissions, greenify etc.

- and if it still does not work, you should behave like described here: http://boeffla-kernel.de/index.php/support/support

- why should I provide any support if people ignore what I request and need? I am SICK of that.

Andi
[ONE Original Android Development] NickosD:
Calm down man, I am not a noobie. Here the logs. The file was created after the boot. Version 2.2.51 opens. I had it in my downloads and I tried it.

https://www.dropbox.com/s/58zfm8aqgtrsral/boeffla-kernel-data.zip?dl=0
[ONE Original Android Development] chenrp:
As i said, i ahve the same issue. Tried reboot and what the app said. Someone's angry! Lol
[ONE Original Android Development] andip71:
Ok, the logs look very clean and normal.

And you say, when you now start the app, it still complains?

If so, please send me bc.log once more.

Thanks

Andi
[ONE Original Android Development] Renosh:
Stop being disrespectful with jokes in such a situation. Did you dirty flash ROM before installing Boeffla kernel? Also why aren't you providing the requested information? Describing the issue is not helpful if the dev isn't experiencing it, he won't bother fixing it, so check the site and follow procedure.
[ONE Original Android Development] NickosD:
Ohhh didn't tried to reopen it before. It works now. Maybe deleting the file did the work. Thx ?
[ONE Original Android Development] andip71:
It is only a log file, which does not serve any functional purpose.

So this was for sure not the reason.

What could be the reason however is:

- did you open Boeffla-Config first thing after start when the device was still coming up?

There could be a chance, when the configuration still loads (and this takes around 20 seconds), this message comes up.

I will put some hardening in now.

Andi
[ONE Original Android Development] NickosD:
No, I waited till the message pop up for profile, then checked for the log, and long after that I opened the app.
[ONE Original Android Development] andip71:
Yes, ok, I understand.

I meant, when you had the problem before: Was it there, you were also waiting for the profile loaded message to come up? Or did you open straight first thing after system boot?

Thanks

Andi
[ONE Original Android Development] NickosD:
In the 2-3 reboots that I did, I open it once after the profile was loaded. I didn't know what happened now and it opened. Only thing that I did was deleting the log and reboot the device but I waited much longer. More than 10 mins. Thx tho.
[ONE Original Android Development] hellcat50:
Just noticed that your kernel breaks usb debugging on cos. (iu.uploadsmanager insufficient permissions)

Only flashed your kernel + cos superuser
[ONE Original Android Development] andip71:
Not enough information.

Which cos version, which kernel version? How did you want to debug, with android studio or something else?

Does it work with stock kernel?

I might know why, and might look into that during next week when I find time.

But as usually nobody uses adb debugging, it is not a big priority for me currently.

Andi
[ONE Original Android Development] hellcat50:
Flashed latest cos (ZNH2KAS254) - your newest cos kernel (5.2 beta 1) - latest cos superuser enabler (COS13.1-enable-internal-superuser-bacon.zip)

Here is the log:

E/DatabaseUtils(2712): Writing exception to parcel
E/DatabaseUtils(2712): java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/images/media from pid=6147, uid=10089 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission()
E/DatabaseUtils(2712):	at android.content.ContentProvider.enforceReadPermissionInner(ContentProvider.java:605)
E/DatabaseUtils(2712):	at android.content.ContentProvider$Transport.enforceReadPermission(ContentProvider.java:480)
E/DatabaseUtils(2712):	at android.content.ContentProvider$Transport.query(ContentProvider.java:211)
E/DatabaseUtils(2712):	at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112)
E/DatabaseUtils(2712):	at android.os.Binder.execTransact(Binder.java:453)
E/iu.UploadsManager(6147): Insufficient permissions to process media
E/iu.UploadsManager(6147): java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/images/media from pid=6147, uid=10089 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission()
E/iu.UploadsManager(6147):	at android.os.Parcel.readException(Parcel.java:1620)
E/iu.UploadsManager(6147):	at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
E/iu.UploadsManager(6147):	at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
E/iu.UploadsManager(6147):	at android.content.ContentProviderProxy.query(ContentProviderNative.java:421)
E/iu.UploadsManager(6147):	at android.content.ContentResolver.query(ContentResolver.java:493)
E/iu.UploadsManager(6147):	at android.content.ContentResolver.query(ContentResolver.java:435)
E/iu.UploadsManager(6147):	at idi.a(PG:112)
E/iu.UploadsManager(6147):	at com.google.android.libraries.social.autobackup.FingerprintScannerIntentService.onHandleIntent(PG:82)
E/iu.UploadsManager(6147):	at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:66)
E/iu.UploadsManager(6147):	at android.os.Handler.dispatchMessage(Handler.java:102)
E/iu.UploadsManager(6147):	at android.os.Looper.loop(Looper.java:148)
E/iu.UploadsManager(6147):	at android.os.HandlerThread.run(HandlerThread.java:61)
[ONE Original Android Development] Mandrake2010:
hi andy, i have problem with last cos 13.1 and 5.2 beta 1 anykernel and debug usb.

Windows 10 (pro 32bit) dont see opo when plug with debug enable, I have reflashed stock kernel and with debug usb enable i have popup rsa key and i can use adb with prompt.

After i have flashed 5.2 beta 1 but windows dont see it.

problem with secure in default.prop??

Sorry for my bad english.

P.S: i have remove all driver, reboot windows, opo etc but i cant see it with anykernel.
[ONE Original Android Development] andip71:
Ok. I have a suspicion already.

Will look into that next week.

Andi
[ONE Original Android Development] atulclassic:
same here..when plugged to computer, usb debugging not detected and no drop down for changing usb connection until usb debugging is toggled on/off
[ONE Original Android Development] andip71:
See above, problem noted and investigated next week.

Andi
[ONE Original Android Development] Mydnytefantasy89:
I know this isn't your normal setup, Boeffla, but I'm trying to be able to use Android Pay, so I use SuperSU, and it seems that the enable system root I used in the S1KN update stuck around through the most recent update, so my question is: how do I get rid of the system root from developer options? I'm not even sure how it's there if it isn't functioning.
[ONE Original Android Development] Brian325:
I'm using your CM 13.0 beta kernel with the ROM I build for myself. I build the ROM from the stable ZNH2K branch with the kernel from the nightly branch. Everything is stock CM except I use Uber Toolchains. Everything feels great switching to your kernel. I've got all settings in your app at default. Its a really good combo without the random nightly bug. Thanks for your work on this kernel.
[ONE Original Android Development] andip71:
In order to get rid of the system root again, manually delete the following files:

/system/bin/su

/system/xbin/su

Then disable it in the developer options and reboot.

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

although weekend, I quickly fixed the adb debugging issue for COS13.1 kernel.

So here we go for a new version:

COS13.1 -- Version

5.2-beta2

13.07.2015

Note: This kernel version runs best on COS13.1 firmware ZNH2KAS254

Fix: Broken adb debugging fixed

Enjoy

Andi
[ONE Original Android Development] atulclassic:
confirming by another user isn't a mistake?
[ONE Original Android Development] andip71:
Not a mistake, but when I have already acknowledged an issue it doesn't help anymore [emoji3]

Andi