yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Raj joshi:
What an average SOT you guys are getting?
[ONE Original Android Development] vickeye:
3-5 hours SOT
[ONE Original Android Development] Pablo.x:
Ah sorry, I understood upside-down your answer

Enviado desde mi OnePlus One.
[ONE Original Android Development] Gawd:
I'm getting a lot of stutters on 5.2 beta 2-CM13.

The experience suddenly became very jittery after flashing this build. I didn't have any problems on the previous one. And I've been using Zanezam's version of your kernel. But I don't know after I updated my ROM (currently on RR 26 July build), his kernel gave me bootloops, idk why. So I tried the original one (your kernel) and no bootloops but the stutter is very noticeable. I don't know what is causing this. I want the functionality of this kernel, it seems perfect, but since this is very jittery and the other one is causing bootloops, I'm stuck. The original RR kernel has a very slow charging rate and I can't live with that. I think I'm gonna try the previous versions or some other kernels. It would be great if you look into this. Thank-you.
[ONE Original Android Development] atulclassic:
set Input boost to =>1400
[ONE Original Android Development] andip71:
And make sure min gpu frequency is 200 and not 27.

Andi
[ONE Original Android Development] chenrp:
when choosing 2000mah charging current, i am getting ~1850.

but when i choose 0 (default) the charging drops to 1200mah...

any reason the default is so low?

thanks
[ONE Original Android Development] andip71:
Yes. When on default, the stock charging logic kicks in. This logic is trying to charge the battery in a way it is most secure. Based on temperatures, current battery level etc, the charging current will be controlled and is not a fix value anymore.

This is why I usually recommend to stick to stock charging logic, unless you have a strong need for faster charging in a specific situation.

Andi
[ONE Original Android Development] chenrp:
thanks for explaining that.

but what is the logic algorithem? is it really temperature related? where can i see the algorithem?

i am on 80% battery and the charging is at ~1850.

now i am at 90% and it went down to 900mah.

this is lithium battery charging method... i don't think it is software related (connect 90% battery to an external PSU and get same results).
[ONE Original Android Development] karoli:
Even without the boost, the last stable branch is snappy, no lag noticed on COS 13.1 (ZNH2KAS1KN).
[ONE Original Android Development] andip71:
You can study the charge driver. It is complex, so expect it takes a lot of time.

And it is, for sure, always a mix of hardware and software.

Andi
[ONE Original Android Development] Fenvarien:
No lag, stutter or hiccup here, I'm using the latest CM13 nightly with Boeffla kernel 5.2 beta 2. I even use GPU min. 27 MHz max. 389 MHz and the optimized hotplug profile.

There's probably a rogue app, service or misconfiguration hurting the performance of your device.
[ONE Original Android Development] kalapapa:
Are you using xposed

I've noticed xposed with this kernel causes theses issues
[ONE Original Android Development] Gawd:
Xposed, maybe. But this didn't happen on the previous build, or even Zanezam's build of this kernel.
[ONE Original Android Development] Fenvarien:
Lord Boeffla explicitly refuses any kind of support if someone is using Xposed, that's clearly stated in the first post.
[ONE Original Android Development] Gawd:
Yeah, I know. Xposed isn't officially compatible with anything, although it's a great framework. Thanks, anyways.
[ONE Original Android Development] andip71:
Hi all,

updates for COS13.1 and CM13 kernels.

COS13.1 -- Version

5.2-beta5

01.08.2015

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

Change: Removed Boeffla Notification LED control

Reason: CM built-in LED control is much more powerful nowadays (and Boeffla LED control conflicts with it), so use this in future to configure notification LED speed and brightness

Change: Internal download URL changed for kernel

CM13 -- Version 5.2-beta3

01.08.2016

Change: Removed Boeffla Notification LED control

Reason: CM built-in LED control is much more powerful nowadays (and Boeffla LED control conflicts with it), so use this in future to configure notification LED speed and brightness

Change: Internal download URL changed for kernel

Enjoy

Andi
[ONE Original Android Development] Dhairya:
site is down sir :(
[ONE Original Android Development] andip71:
No, it is not. At least not here...

Andi
[ONE Original Android Development] parvesh:
[MENTION=2936357]dhar[/MENTION]iya Can confirm site is working just downloaded :) [MENTION=947981]Lord Boeffla[/MENTION] Thanks sir for another masterpiece
[ONE Original Android Development] chenrp:
still seeing 1200 in the limiter...

anyone else?
[ONE Original Android Development] rolarocka:
Hello, I'm using the latest cos beta on Resurrection Remix wich is cm. It's so smooth and battery life is insane ? it's the best I have since trying out Rom's (with the battery saving preset)... But is this the correct kernel for this ROM or should I use the cm beta one ???

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Gawd:
Why is this?
[ONE Original Android Development] Dhairya:
working fine was on old website thanks !
[ONE Original Android Development] illanxr:
Really sorry about that.

I hope this helps:

https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/

Looking forward to your fantastic new kernel!
[ONE Original Android Development] gianton:
If you send it back under warranty and have it repaired?
[ONE Original Android Development] OberstGrausam:
OnePlus won't repair it under warranty, atleast not, considering what they posted. Since he didn't run unrooted stock settings, OnePlus will most likely refuse to repair it under warranty.
[ONE Original Android Development] artyfarty:
fro OPO site

Warranty & Repairs Will rooting or unlocking the bootloader void my warranty?

The technical process of rooting or unlocking the bootloader does not void the warranty of the OnePlus One. However, we strongly suggest for you to only root or unlock the bootloader of the OnePlus One if you are confident that you understand the risks involved.

By accessing resources regularly unavailable to software, the process may damage your hardware during or after the procedure, which is not covered under warranty. In warranty handling, we will need to verify that any faulty behavior is unrelated to rooting / unlocking first.
[ONE Original Android Development] OberstGrausam:
You're right. I just wanted to point out, that since he flashed a custom recovery and other custom made software they will most likely refuse to repair it under warranty.
[ONE Original Android Development] gianton:
If it doesn't boot they won't know. I believe that they don't pay much attention anyway.
[ONE Original Android Development] artyfarty:
I believe that they don't read much XDA forums ;)
[ONE Original Android Development] andip71:
Hi guys,

thanks for all crossing their fingers.

I got it up and running again. Well, it just booted up cm11s successfully 2 minutes ago. So a bit early to say if all is fine, but I would say... looking good now.

Was also a nice experience to have Coloros installed (this is required as an intermediate step), haha. I could not read anything as all is Chinese.

However, I lost all my nandroid backups, so it will now take me a few hours today evening to set everything up again.

So, if all goes well, beta10 tomorrow then :)

Thanks to all for the mental support again.

BTW, if anyone has the same issue one day, this thread helped me to get it achieved:

https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/

(although I had to grab other usb drivers as the ones here did not work for me, also had to install Windows XP again on one of my PCs to make it work, bummer).

Cheers

Andi
[ONE Original Android Development] jgcaap:
I think they solve this on RMA. Did you contact them?
[ONE Original Android Development] Aavion:
i had sth like that once with my nexus 4..flashed a kernel (someone mentioned later that it was packed with a faulty zip format that the image wasn't able to align proper onto the partition layout)..

what i've done was to connect it to a linux box and ran gparted on it and ended up in dd'ing all the partition images back :D

Aavion@eXsomnis - 1+ One 11S Boeffla Kernel
[ONE Original Android Development] andip71:
Yeah, but this only works if you have still some kind of higher level connection.

But anyways, I hope I do not need to do this procedure any time again. It is painful with Win XP, baaaah.

Andi
[ONE Original Android Development] gianton:
Great news, glad you got it working again!
[ONE Original Android Development] andip71:
Yes, and as this is now another level lower than flashing the factory images, I feel somehow "immortal" now. At least, I am not shocked when it happens again one day :)

Andi
[ONE Original Android Development] andip71:
Quick update....

cm11s installed again and running with boeffla beta10 for test.

cm11 nightly 17.11. installed again and running with boeffla beta10 for test.

Looking good for the release now tomorrow. Finally :)

Andi
[ONE Original Android Development] molonad:
Thanx for kernel

Hi your kernel is best of all I tried, only think I miss is gpu overclock and gpu governors, will you develop this overclocking? Thanx for answer
[ONE Original Android Development] andip71:
Hm, let's see. It is honestly not on any short term roadmap as I am not into gaming at all.

So, have some other priorities at the moment. But when they are done, I might look into it. No promises though.

Andi
[ONE Original Android Development] andip71:
By the way... just to make everyone relaxed about my hard brick yesterday.

Now I know what it was, because I bricked it again (this time recovery took me only 30 minutes in total, haha, I am getting experienced).

And to make you happy: It was my own fault. Typical copy&paste error in a build script I first time used yesterday. Bamm. Now I feel good, because I know what it was and how easy it is to recovery a fully bricked opo.

And... yes, not a good idea to build a kernel boot.img for the OPO with parameters from Exynos platform, hehehe :D

All good!

Later I will upload beta10.

Andi
[ONE Original Android Development] andip71:
Beta10 arrived !!

Hi all,

with some delay, but finally it is there:

2.0-beta10

for both CM11s and CM11 kernel variants:

CM11s kernel is now optimized to work with XPNH44S, however works still fine on 38R too.

CM11 kernel has been completely rebuilt based on a new kernel branch, but looks nothing got broken due to that.

CM11S version 2.0-beta10

17.11.2014

Important note: Make sure you use Boeffla-Config V2 version 2.1.53 !!

zzmoove governor updated to 1.0-beta3 (bugfixes, credits to ZaneZam)

Initramfs updated to firmware XNPH44S

CPU max freq handling hardening done (please check and re-adjust your max cpu freq if you changed it from defaults)

Pushing default settings for readahead buffers and charging rate removed again, as we should assume, all have used beta9 kernel in the meantime

Merged latest CM11 patches in

Minor internal bug fixes

CM11 version 2.0-beta10

(For this kernel version, you should have CM11 nightly of 10.11.2014 or higher !!!)

17.11.2014

Important note: Make sure you use Boeffla-Config V2 version 2.1.53 !!

zzmoove governor updated to 1.0-beta3 (bugfixes, credits to ZaneZam)

Complete rebase on latest cm-11.0 kernel source branch (not shipping branch as before)

CPU max freq handling hardening done (please check and re-adjust your max cpu freq if you changed it from defaults)

Pushing default settings for readahead buffers and charging rate removed again, as we should assume, all have used beta9 kernel in the meantime

Ramdisk updated to version of nightly 17.11.2014

Minor internal bug fixes

This might very well be the last beta kernels for CM11 before I release them as stable. Depends on your feedback about bugs of course.

Enjoy

Andi
[ONE Original Android Development] Setting.Out:
Yes, bricking your phone twice does make flashing even more appealing.. Lol.. Though, I generally don't report my mistakes.. ;)

I am glad you've recovered again and found the error (especially before releasing it) and aplaud your honesty and openness in your builds for us..

You make the best kernels I've had the privilege to use.. ;) thanks for another build.. ;)
[ONE Original Android Development] andip71:
Well, it was such a stupid copy&paste error, I had to tell the world how stupid I am :)

Have no problem laughing about myself when I deserve it. And this was really... well, unbelievable.

Just to make clear: I only use this build script for my internal purposes, never when I compile official kernels. So there was never any danger for anyone, just for my little dev OPO.

Now I am back working on the first beta version of the CM12 kernel. It is almost done, just the Lowmemorykiller configuration is either broken or by intention not available anymore. I want to investigate a bit on that now.

Cheers

Andi
[ONE Original Android Development] CoinCoin88:
Hi,

I'd like to raise a bug in the qcrypto.c driver part. It seems CM kernel has been crippled since cm13.0 (at least) with a bug preventing the phone to go into deep sleep when it's encrypted (I've confirmed this with a friend of mine and also here on XDA + on the CM JIRA, with rather condescending answers). This results in a fd440000.qcrypto kernel process that keeps the phone awake for 99+% of time. Oddly, disabling data connection and wifi solves the problem. (Before you ask, I've confirmed that on full-system-wipe clean installs multiple times)

Overall, I *believe* the fix lies in this commit in the CM13 GitHub repo. Looking at the sources of your kernel on GitHub, I see the incriminated lines are still in the sources you use to compile your kernel, in boeffla-kernel-cm-bacon/drivers/crypto/msm/qcrypto.c (see e.g. line 459 which has the pm_stay_awake call). This fix has been committed in CMOS sources in early June but somehow has not been implemented in the latest build. It is unclear if/when it will be released in a future OTA, and CM communication is... scarce, to say the least.

Hence, two questions:

1) is it possible the commit could fix this behaviour, and if so...

2) would you consider implementing it in your sources ?

I don't have the required environment to build a kernel here for now, but would be willing to give it a try if necessary. I'll also open an issue on your github repo, just in case it's a better place to raise this bug.

Many thanks !

Nb : this is a c/p of my previous post that I mistakenly put in the i9300 thread. Apologies for this.
[ONE Original Android Development] infatality:
If there's anyone who's keep complaining about battery life.. Probably something is very wrong with your opo configuration.

Here's mine battery life on my almost 3 years opo.
[ONE Original Android Development] CoinCoin88:
If that's a comment to my previous post... are you encrypted ? Probably not.
[ONE Original Android Development] andip71:
Sorry to correct you, but this patch is indeed applied in my repo, straight after it came out.

I think you looked at the wrong branch (as the default branch when opening the repo was an old CM12s kernel, not the CM13 one).

I now moved the default branch for someone opening the repo to boeffla_v5_cm.

Take a look yourself at the file:

https://github.com/andip71/boeffla-kernel-cm-bacon/blob/boeffla_v5_cm/drivers/crypto/msm/qcrypto.c

The lines you mentioned are of course deleted in my repo as well.

So looks like something else is "guilty" for your issue. However, not related to this crypto driver as - you can check yourself again - it is not touched at all.

Andi
[ONE Original Android Development] andip71:
Either mpdecision cannot load because of a wrong version (unlikely).

Or some script/app/something kills it after start again.

Boeffla-config app checks the running processes (by running the command "ps | grep mpdecision"). If mpdecision is not running, it complains.

So for whatever reason, your rom does not seem to load mpdecision.

Are you on an original CM/COS rom or something else?

Andi
[ONE Original Android Development] CoinCoin88:
Thanks for taking the time to check and let me know. In your repo, I was looking at the boeffla_v5 branch (I had switched from the default branch which was indeed cm12-based). I was looking at the v5 (and not v5_cm) because the release tags matched those of your website (5.2-beta5).

So that means I was mistaken looking at the v5 branch and should have looked at the v5_cm?

Thanks
[ONE Original Android Development] andip71:
Yes.

boeffla_v5 is COS13.1 branch.

boeffla_v5_cm is CM13 branch.

Andi
[ONE Original Android Development] CoinCoin88:
Then for COS13.1, it seems to still be in the source file: https://github.com/andip71/boeffla-kernel-cm-bacon/blob/boeffla_v5/drivers/crypto/msm/qcrypto.c#L459 (line 459 for pm_stay_awake, and 494+498 for pm_relax).

Just to be sure I'm not looking at the incorrect sources: I'm on the latest OTA released by the Cyanogenmod (is it CyanogenOS? I'm always confused when it comes to their different denominations) team, that is, 13.1-ZNH2KAS254. Therefore, i used your boeffla-kernel-5.2-beta5-COS13.1-bacon-anykernel.recovery.zip (which I believed is based on your boeffla_v5 branch, if I read your last post correctly).
[ONE Original Android Development] andip71:
Ok, so you are on COS (CyanogenOS) and not CM. This makes things different.

The original repo by CM team for cos is: stable/cm-13.0-ZNH0E

And here you can see, they never merged the mentioned commit in:

https://github.com/CyanogenMod/andr...le/cm-13.0-ZNH0E/drivers/crypto/msm/qcrypto.c

Hence, I also have not merged it, as I usually follow CM official repos and do not cross-merge patches.

But maybe you want to test the attached build, I have merged the patch in for you and did a test build. Let me know if it helps.

Andi
[ONE Original Android Development] CoinCoin88:
That's very kind. I'll flash when I get back to the office and will feedback here. Many thanks!

edit: flashed, booted and now leaving the phone idle for a while to see if the qcrypto process still causes kernel wakelocks.

Out of curiosity, have you tested CM13.0 or COS13.1 on encrypted phones (regardless of the kernel), and if so, did you encounter this behaviour as well ? I always have a hard time finding people who actually have encrypted their phones to compare with the behavior I observe in mine.
[ONE Original Android Development] CoinCoin88:
Well, definitely, this build makes the 'fd440000.qcrypto' kernel wakelock disappear from BBS, while it was the 1st wakelock and accounted for 99% of time. I'll go through daily usage and see how it goes, but deep sleep seems to kick in normally now. Thank you again for preparing a test build quickly!
[ONE Original Android Development] andip71:
Good news then.

Well, I would appreciate if you could give me some more feedback in next 24-48 hrs.

If all stays well, I would keep it in the COS kernel in general and spool a new release out.

I am on holidays full next week, so either I will still do it before, or after. Not yet sure.

Thanks

Andi
[ONE Original Android Development] CoinCoin88:
Will do. I'll leave the phone unplugged and restart all my usual sync services, and see how it drains in 'normal' use (my definition of 'normal' includes some wifi/data browsing on coffee break, 20-50 texts/day, some pokemon go on my way between work and home, listening to locally stored music in the subway, and randomly switching the screen on either to look at the time or realize I've missed a text (or thought I'd missed one)). Before your build, I was hardly making it through a day of use (you can see the screenshots in my bug listed on the cyanogen JIRA and also in the thread I referenced here in my first post). I'll update with equivalent screenshots.

Thanks,

Thomas
[ONE Original Android Development] ATeam-MrT:
I just installed beta 5 along with the config V2 app, activated SU and headed to the sound tab to play with the microphone input gain level, when I found that there is no such option, also no EQ presets. What did I do wrong, or am I missing something?
[ONE Original Android Development] andip71:
There is only headphone volume possible on Qualcomm sound chips.

Read faq on homepage to learn why.

Andi
[ONE Original Android Development] andip71:
Good morning,

CM13 Boeffla kernel update again, to be up-to-date with CM patches.

Version 5.2-beta4

04.08.2016

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

Enjoy

Andi
[ONE Original Android Development] CoinCoin88:
Hi Andi,

I let the phone drain yesterday evening with sort of a heavy use. I noticed a couple of odd things. First, i have a PowerManagerService kernel wakelock that is not-so-insignificant (however it's difficult to compare with a normal use since I have been crippled with the qcrypto wakelock for several months now).

Yesterday in the evening i tried to stream some low-res locally-stored MKVs using AllCast (and ooold free version that I've never updated and for which I have kept the apk safely). The video was laggy as hell and I had never encountered such a thing before. Messing around with the wifi (disconnecting/reconnecting/restoring factory chromecast setiings using the Google Cast app) eventually led to an unexpected shutdown of the phone, which was getting very hot. However I'm not sure if all that can be kernel-related, especially not to the very slight changes you made for my test build.

I've recharged fully the phone overnight and am now using it with a normal usage. Deep sleep is definitely kicking in, but I still have the PowerManagerService kernel wakelock accounting for 41 minutes over the last 2h45 (time since unplugged). I'm wondering if it could be the "push sync" settings enabled on two of my 3 e-mail accounts. I've disabled their sync to compare.

Hope that helps a bit. I'll update later today! if i get time over the week-end i'll flash back the stock boot.img from COS13.1 and see if there's anything that improves with my chromecast streaming thing.
[ONE Original Android Development] ch-vox:
Hi [MENTION=947981]Lord Boeffla[/MENTION]

Just for information, do you know if the latest COS13 ZNH2KAS2X1 version work with your COS13 kernel ?

Thank you
[ONE Original Android Development] andip71:
As there are no new sources for kernel out + we have now anykernel method, it should 99,99% work.

BTW, have not even seen there is a new COS13 version out?? Any references?

Andi
[ONE Original Android Development] Hexxer:
Hey Andi,

as you like. I try to flash beta4 but my OPO wont work anymore. All i get is the first OPO Screen/Logo and thats it. Also after 10 minutes - nothing as this.

- adb logcat wont work in this system level

- try flashing more then 5 or 6 times

- try wipe the cashes

- NO warning at flash (beta3 works like charme)

if i shut it down (hold power a while) and go to recovery with the next step and flash beta 3 - after 30 seconds the system is ready.

Regards
[ONE Original Android Development] MMWolverine:
ch-vox is right, there's a new COS update available. I'll flash tonight and report if there are any issues with beta5 kernel.
[ONE Original Android Development] ch-vox:
13.1-ZNH2KAS254 => 13.1.1-ZNH2KAS2X1 Incremental:

http://builds.cyngn.com/incremental/bacon/cm-bacon-9f339bddf2-to-3c3f0aca9b-signed.zip

EDIT:

and thank you for compatibility information :)