yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andrea90:
How could I set PerApp frequencies?

App like Maps or some games use top frequencies, so phone is getting hot and sucks battery... Maybe I could find a sweet spot with lower frequency
[ONE Original Android Development] TheCrazyLex:
Hey,

i saw the ext4 tweaks in your features list :)

However I couldn't find them in the kernel source..

Can you please point me to the commit(s)?

Alex
[ONE Original Android Development] casshern94:
hi lord boeffla.

i tried your kernel with conservative/lionheart/pegasusq/zzmoove/interactive governor,and even tried the same with zanezam uber build.

i wonder why the temperature of the device is lot higher when using boeffla kernel compared to AK kernel (cuz i used AK kernel previously)

note: no offend lord boeffla, im not here to compare kernel,i take AK cuz i used it previously. im just curious.
[ONE Original Android Development] davebugyi:
What do you mean a lot higher? Running here without installing other kernels and temp is OK. Currently at 36 Celsius.

When coming from a different kernel make sure you clean up all configuration and settings from the previous kernel.
[ONE Original Android Development] casshern94:
hi, i mean i can feel alot hotter at the camera area when using the device with boeffla kernel.

btw i did a dirty flash rom with cached wiped prior installing this kernel
[ONE Original Android Development] andip71:
Not at all with out-of-the box functionality.

But - you can use tasker to switch different profiles of boeffla-config as you like. It is the most flexible way, but needs some learning first.

Read FAQ on the homepage.

It is in the ramdisk, so it is a super huge commit.

But basically look into the boeffla-init.sh script:

mount -o remount,commit=20,noatime $CACHE_DEVICE /cache

mount -o remount,commit=20,noatime $DATA_DEVICE /data

In fact data and cache partitions are mounted with a commit time.

Nothing I can comment here. I do not have hot phone and never used any other kernel than mine or stock.

Andi
[ONE Original Android Development] casshern94:
ic,thanks anyway.

i enjoyed using your kernel :)
[ONE Original Android Development] alexbk66:
---------- Post added at 03:41 AM ---------- Previous post was at 03:35 AM ----------

https://plus.google.com/+AlexCruz/posts/19Pd67NxyU2

---------- Post added at 03:43 AM ---------- Previous post was at 03:41 AM ----------

Tasker?
[ONE Original Android Development] merikgvr4:
LB your kernel all of a sudden doesn't work with slimsaber. Is there anyway you can look into it? Worked wonderfully before the switch to 5.1 LP.
[ONE Original Android Development] andip71:
But you have read anything else than official cm is out of scope for me? [emoji6]

So, not likely as I have to prioritize my little time carefully.

Andi
[ONE Original Android Development] andip71:
New CM12s and CM12.1 test kernels !!

Hi all,

there are new test kernels for CM12s and CM12.1.

Please note, I exceptionally (!!!) compiled them as well in a second version with the touch drivers that fix the touch issues for many, but use lots of more battery.

If you want this version, download the version that is called "touch-workaround" in the download directories along with the normal versions. I did that because many people asked for it.

Note: Use that on own risk, nobody knows what else is fishy with that touch driver which CM reverted back due to the high battery drain.

CM12s/COS12 -- Version

3.0-beta9

25.05.2015

Tripndroid scheduler added (some basic infos here)

BFQ scheduler updated to version BFQ-v7r7

Fixed bug in cpufreq which impacted overclocking (via ZaneZam, credits to neobuddy89)

CM12.1 -- Version

4.0-beta17

Note: Only for CM nightlies of 14.05. or newer (and custom roms having these new changes in)

25.05.2015

Tripndroid scheduler added (some basic infos here)

Updated with latest 4 official CM kernel commits as of 19.05.15

BFQ scheduler updated to version BFQ-v7r7

Fixed bug in cpufreq which impacted overclocking (via ZaneZam, credits to neobuddy89)

Ramdisk updated to official CM12.1 version of 25.05.15

Enjoy

Andi
[ONE Original Android Development] dickenam:
You are the best! :good:
[ONE Original Android Development] andip71:
Well, thanks for spotting the update [emoji2]

Andi
[ONE Original Android Development] dickenam:
Thanks for making the update: 99Y83966SN408364X
[ONE Original Android Development] andip71:
Many thanks my friend. Appreciated a lot [emoji2]

Andi
[ONE Original Android Development] kurtextrem:
Our quest now: Finding the best scheduler for the OPO with the lowest battery usage, yet an acceptable perf. :D
[ONE Original Android Development] andip71:
Zen maybe, although scheduler impact on battery is almost zero.

I personally like tripndroid alot these days.

Andi
[ONE Original Android Development] kurtextrem:
I was running with fiops a longer time... now with SIO. No scientific study, but I feel like SIO is better.
[ONE Original Android Development] bloof:
Battery isn't the main focus for IO, speed is.

Zen has a lot of good reviews. Trepndroid (or something like that, just added by boeffla) is apparently really good too.

Beyond that try changing the readahead:

- to smaller number if you don't use big apps (but will make larger files slower)

- to larger number if you do

Just try with different readahead and see if it impacts your performance.
[ONE Original Android Development] tracerit:
would the scheduler have any impact on write speed in recovery? lately my backups have been super slow at 13MB/sec for file system rate. My friend's OPO is at 42MB/sec.
[ONE Original Android Development] andip71:
No. Schedulers in normal kernel is not used in recovery.

Every recovery has it's own kernel.

Btw, placebo or not, since updating to twrp 2.8.6.1 I also feel backup speed is slower.

But not for sure, did never stop watch it.

Andi
[ONE Original Android Development] davebugyi:
It is confirmed over in the TWRP thread - Backup is indeed slower, probably because of encryption commits added. Also if you want to restore Firmware from backup, the whole process will fail (you have to delete the firmware backup file before restore).
[ONE Original Android Development] pinoymutt:
NEVERMIND -- I should have read your post more carefully :) I found the answer.
[ONE Original Android Development] awaisuk:
I read that the touchscreen firmware had an effect on the battery life. Is it the same for CM11? I want to flash the CM11s firmware with the touchscreen fix, but I want to know if it will reduce battery life? thanks.
[ONE Original Android Development] adinkwok:
Yes it probably will because it comes from the touchscreen driver which isn't ROM specific. But, some have reported that disabling Doubletap2wake and ambient display won't cause a drain.
[ONE Original Android Development] alexbk66:
How can you restore if you delete the file before?
[ONE Original Android Development] fmc000:
You don't. The firmware is included in every nightly so the backup is rather pointless.
[ONE Original Android Development] andip71:
Yes. Regardless of rom it will drain your battery.

Andi
[ONE Original Android Development] fmc000:
Thank you very much, working perfectly.

I'm testing it right now, so far so good. Thanks again, you're the best.
[ONE Original Android Development] sathish804:
What is the difference between boeffla-kernel-4.0-beta17-CM12.1-bacon-touch-workaround.recovery.zip and boeffla-kernel-4.0-beta17-CM12.1-bacon.recovery.zip on download page??
[ONE Original Android Development] andip71:
Just read the last change log here in the thread, then you would know.

Thanks

Andi
[ONE Original Android Development] flyaway718:
Does anyone know what is Wakerlock:xxxxx? I see a bunch of them within wakelock on v17 build.
[ONE Original Android Development] andip71:
Be more specific, maybe then somebody can elaborate a bit more on it.

Or send a screenshot, that is best.

Andi
[ONE Original Android Development] flyaway718:
Here is the screenshot of them within wakelock.
[ONE Original Android Development] andip71:
Nope, these numbered wake locks are not helpful.

Usually they have some more (not much more, but a bit) meaningful names.

Other apps like BetterBatteryStats show them differently.

But - seems these is just a list of available wakelocks anyways, not reflecting your current situation.

Andi
[ONE Original Android Development] brisac:
[MENTION=947981]Lord Boeffla[/MENTION] so every new updated kernel will have new touch drivers that cause battery drain? (Except the one pushed on 18th this month?)
[ONE Original Android Development] Salty Wagyu:
Look at the download links, the one with the touch drivers are named "touch-workaround", the ones without are not named as such, e.g.:

boeffla-kernel-3.0-beta9-CM12s-bacon-touch-workaround.recovery.zip

boeffla-kernel-3.0-beta9-CM12s-bacon.recovery.zip
[ONE Original Android Development] konman21:
Beta9CM12 kernel anyone notice WiFi bug where it disconnects
[ONE Original Android Development] andip71:
This is soooooo old.

No, there is no general wifi bug.

Zero issues here.

Read up in the thread to find more about it.

Andi
[ONE Original Android Development] SLBoy:
Hi there, updating the kernel through the app will get me the normal beta9 or the one with battery drain?
[ONE Original Android Development] andip71:
Always the normal one.

The one with the new reverted touch drivers and the drain is an exceptional compile only. So it will never update to this.

Andi
[ONE Original Android Development] andip71:
Todays Cm12.1 nightly (27.05.)

Good morning,

I just want to pre-warn people already which are on CM12.1.

Today's nightly (27.05.) seems to be a bit fishy. After installing it, I had already some unmotivated reboots. Also a German user reported the same.

So I went back to yesterdays nightly again and all is fine.

So - you were warned :)

Andi
[ONE Original Android Development] TorchaOne:
I had those too yesterdays when I applies those wifi configurations fro 27th day to /etc + /etc/wifi. So I am not going to even try todays build, maybe :)
[ONE Original Android Development] HaTrED_:
The culprit seems to be the new gps/new Wifi commits... that are causing soft reboots for some! :rolleyes:
[ONE Original Android Development] acuicultor:
Hi, i'm start building kernels from source i'm just a Noob willing to learn and I will very grateful if someone can point me to some info to change/add splash logo on a kernel for our device. I really look for the answer on the net but I found nothing helpful for me. Thanks in advance

Sent from my Crispy Bacon
[ONE Original Android Development] Phazonclash:
I'm experiencing the these reboots with 05/27 + Boeffla beta 17. I'll try the stock kernel for a while to see what happens ;)
[ONE Original Android Development] andip71:
Yeah, good idea.

Please let me know if they are gone with stock kernel. I would assume No, but we never know.

If so, I would need to push another update with a new ramdisk. But quite reluctant still to do that as no kernel code changed as such.

Andi
[ONE Original Android Development] Phazonclash:
Didn't take long on stock kernel either. My phone restarted in less than 2 minutes after a reboot :P
[ONE Original Android Development] andip71:
Confirming my assumption, something is fishy in the latest nightly as well.

Glad, do not need to update the kernel today at least :)

Andi
[ONE Original Android Development] Phazonclash:
Thanks for your hard work Boeffla, I love this kernel a lot. And I guess it's time to roll back to CM12.1 05/26 + Beta 17 for now ;)
[ONE Original Android Development] andip71:
Thanks my friend.

And yes, that is exactly what I did around 10 minutes after installing 27/05 nightly. Restore backup :)

Andi
[ONE Original Android Development] TorchaOne:
Some ppl have tried 26th day WCNSS_qcom_cfg.ini and no reboots. I tried 27th WCNSS_qcom_cfg.ini to 26th and reboots, with our kernel and stock. I am staying at 26th with beta17 :)
[ONE Original Android Development] DemosZevasa:
Reboots stopped for me with stock kernel, will report if I do get a reboot later today.
[ONE Original Android Development] andip71:
Interesting because other people (read up) also do have them with stock kernel.

We will see over the time.

Andi
[ONE Original Android Development] Shiningbro:
I have also Random Reboots with Nightly 27.05.2015 and the 12.1 Beta kernel 17

EDIT: I think its a issue with CPU Undervolting with the boeffla kernel App.

Since i changed the UV Profil to "None" the Oneplus is Stable.

Hope it helps a bit. :)
[ONE Original Android Development] andip71:
Haha, that was a good one.

Of course undervolting always is bad. And that is why I refuse giving support when people do undervolting (see OP).

And it is not a "bug" with the app or the kernel, it is a known thing not all devices can do undervolting.

But still 27/05 nightly is fishy, it gave also reboots for me and I NEVER do undervolting.

Andi
[ONE Original Android Development] Shiningbro:
All Clear, you are the Profi.

Thanks for your quick reply. You do a good job with your Kernel. :good:
[ONE Original Android Development] DemosZevasa:
Update: Did reboot right after posting my previous post, must be something in ROM side
[ONE Original Android Development] andip71:
Yes, it is, and discussion is already ongoing in development as you can see here:

http://review.cyanogenmod.org/#/c/99264/

So I wonder whether it will be reverted back for the next nightly :)

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

I know you're not gonna like my request, but I'll still ask :)

It's around the dhcp issue that some people are facing (but not me). It seems that the commit 10cb9e2aee0739415d9862a05acc9743528f67e4 in android_external_dhcpcd is the probable cause for the issue. Could you create a test-kernel with that commit reverted and see if the users with the issue say it is solved? The commit was only introduced in cm12. I know that you are not replicating that repository, hence I know it's a bit more work.

Loris
[ONE Original Android Development] andip71:
If I could... it looks like that was a kernel and not a rom commit.

However, cannot quickly find the whole commit in github somewhere, to ensure I am not talking rubbish...

Anyone?

Andi
[ONE Original Android Development] lchiocca:
Here's the cm commit in github: https://github.com/CyanogenMod/andr...mmit/10cb9e2aee0739415d9862a05acc9743528f67e4

It's in the dhcpcd code... as far as I understand it, the dhcp client daemon is in the kernel, right?
[ONE Original Android Development] andip71:
No :(

It is not part of the kernel sadly. It is a compiled binary that comes with the rom.

Saying that, it is placed under /system/bin (which is not a kernel level directory).

I saw your initial comment that time already, but could not do anything in the kernel with it.

Sorry

Andi
[ONE Original Android Development] lchiocca:
Darn it ;)... Well, I try to continue to convince the cm guys to revert that commit through the BACON-3269 jira issue. Thanks anyways for taking the time to check.
[ONE Original Android Development] andip71:
BTW, now suspicion moved to a GPS related change... thrilling :)

http://review.cyanogenmod.org/#/c/99254/

Andi
[ONE Original Android Development] andip71:
I will hook up to that, maybe alltogether we can make it more urgent.

Andi
[ONE Original Android Development] fards:
I suspect background WiFi location scanning is causing the issue. Not had any reboots with WiFi all day.
[ONE Original Android Development] andip71:
They reverted indeed the WiFi commit for today's nightly.

Andi
[ONE Original Android Development] TorchaOne:
Yes. No more fooling aroung. But what you think, is beta17 okey for today build too? You were talking about ramdisk (?) updates by cm lately. At least I dont see any kernel commits.
[ONE Original Android Development] andip71:
Yes, it is absolutely fine. I already use it with 28/05 nightly.

Andi
[ONE Original Android Development] TorchaOne:
Thanks. I have found a peace with zzmove opt and Tripndroid scheduler :) Sleeps well and enough kick to play world of tanks.

Thanks.
[ONE Original Android Development] hasta_guy:
I have used this amazing work of yours on BlissPop Rom. Today I have flashed Dirty Unicorns ver 9.3 latest weekly update. Will latest Boeffla Kernel work with latest Dirty Unicorns?
[ONE Original Android Development] andip71:
Maybe someone can share experiences here?

As I only use original CM, I cannot comment myself.

Many thanks!

Andi
[ONE Original Android Development] flyaway718:
I am using Boeffla v17 with Blisspop.

How come Selinux strict is checked off? Even when I unselected it, it selected again on boot.

the phone is SELinux is set to enforce on each boot even after manually set to permissive mode.

What do I have to do to make it stay on Permissive on boot?
[ONE Original Android Development] andip71:
Just do it right ?

Go in menu of Boeffla Config, kernel startup options, configure it there.

On overview tab it is for quick toggling but not staying sticky.

Andi
[ONE Original Android Development] ironwick:
I installed yesterday the beta 9 for cm 12s with the touchscreen fix. Well, I have noticed a huge difference in the battery life. Really promising this beta, the best kernel revision I have tried so far in CM 12s. Works really smooth and stable. Combined with the improvement of the battery life and no touchscreens issues.

Amazing job Lord Boeffla!! :)
[ONE Original Android Development] kurtextrem:
Haha what? With the new touchscreen drivers the battery life is worse as it drains even while idling.
[ONE Original Android Development] fards:
For some people. Not everyone
[ONE Original Android Development] fmc000:
For you maybe, certainly not for me.
[ONE Original Android Development] kurtextrem:
Hasn't the CM team stated that?
[ONE Original Android Development] andip71:
Yes, 30 mA idle consumption. But it seems only if you have double touch to wake enabled.

That is why people that are not using d2tw see obviously not a lot of difference.

Andi
[ONE Original Android Development] lucap00:
can someone take a look at this, please? http://review.cyanogenmod.org/#/c/99607/

Does it mean that a new touchscreen driver is incoming?
[ONE Original Android Development] andip71:
Yes. And not even that... now they put a hardware detection in to determine which TPK touchscreen is in fact built in (seems there are three variants).

Based on it, three different firmwares get loaded accordingly.

And the three new firmwares are all newer than the one which we currently have + the reverted one that caused the battery drain last time.

Hopefully exciting stuff (I am about to do a test build for myself with it. mmmmh...)

Andi
[ONE Original Android Development] fmc000:
LOL

Currently we have 1222, the workaround build has 1227 and the new is 1242, if they increase the numberings one step at a time there should have been many commits on this new fw.

Please share the new kernel when it's ready :D
[ONE Original Android Development] jrn2k:
Woohoo! Can't wait! Need some beta testers ? [emoji14]
[ONE Original Android Development] fmc000:
BTW, jdi panel on my OPO.
[ONE Original Android Development] andip71:
Wait... what did I say? :D

I am about to do a test build for myself with it. mmmmh...

The key word here is "myself" :)

I do not want to be guilty if the patch is faulty and breaks your devices. I will try here first...

Andi
[ONE Original Android Development] andip71:
Where did you check that?

I would like to show that in Boeffla-Config as an information, but thought I need to hook into the driver to get hold of this information.

Thanks

Andi
[ONE Original Android Development] fmc000:
dmesg|grep -i panel

(root needed)
[ONE Original Android Development] jrn2k:
Yeah i know m8, it's just that i need that firmware on my 1+1 , the reverted firmware works great here! But i miss the gesture , ill wait for youre release [emoji4]
[ONE Original Android Development] andip71:
Allright, JDI panel for me too.

Hm, I dont want to do a dmesg, so I have to implement something small to get this info out.

When I want to do that at all, not yet sure. Makes only sense when there are other panels than JDI built into the OPO (which I do not know).

Andi
[ONE Original Android Development] Stroky:
I can confirm the JDI Panel as well.

Bought my Phone on 03/15
[ONE Original Android Development] magnamentis:
the battery drain comes with the touch experience so for now it's a matter of personal choice, cm reverted the commit due to the 30mAh extra drain.

but then there is antother compromise, not valid for me but still for some. if you switch off all screen-off gestures like camera circle, flashligt V and the dt2w feature, the drain will be gone. so obviously the applied the fix to a common core instead to the low power core which is necessary to have screen-off gestures at marginal battery costs.
[ONE Original Android Development] andip71:
Test build on CM12.1 with this commit started well, all working normal.

I am doing a CM12s/COS12 test build for my second OPO as well now.

Then I could decide if I give it to you as an inofficial test version, everything on own risk. What do you think?

Andi
[ONE Original Android Development] jrn2k:
Youre choice , users should always use kernel/ roms at their own risk [emoji106]
[ONE Original Android Development] andip71:
I decide in 45 minutes :D

Andi
[ONE Original Android Development] andip71:
Unofficial versions with the new touch drivers !!!

Hi all,

ok, I put the new, split touch drivers into an unofficial test version of my CM12.1 and CM12s kernels.

These split touch drivers are not yet in the official CM kernel code branches but still under code review !!! So it is absolutely completely unofficial and experimental. Especially as we never know whether they will show up like that ever in the official CM repo.

However, both kernels are so far working fine for me. I never had touch issues, so I cannot comment if the new firmware is better or not.

So, if you want to give it a try, remember again: At your own risk! Experimental !!! Everything can happen, the hell can break lose :) !!!

And there you go:

http://boeffla.df-kunde.de/test_unofficial_opo/

Enjoy, curious what some brave users report back.

Andi
[ONE Original Android Development] jrn2k:
Thanks m8! Running great here! Response is awesome, how can i monitor the drain?
[ONE Original Android Development] andip71:
Only by monitoring whether your battery goes down fast than normal.

Nobody of us has the technical equipment to really measure the drain between phone and battery (I guess, at least I do not have).

Andi
[ONE Original Android Development] rahulrai:
Always ready to test
[ONE Original Android Development] fmc000:
Wait and see.... leave the device alone with dt2w enabled and look at the battery graph after some hours. It should be pretty noticeable if present.

---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------

It would be nice if other users verify their panel manufacturer and post impressions. So far only jdi panels have shown up.
[ONE Original Android Development] jrn2k:
Same here , JDI panel..
[ONE Original Android Development] Hilmesh:
hello when i am trying to use dmesg command using android terminal i am getting permission denied? My phone is rooted though.
[ONE Original Android Development] jrn2k:
Type : "su" in terminal first
[ONE Original Android Development] andip71:
You need to first enter "su" and press enter (whithout quotation marks).

Then the dmesg command...

Andi
[ONE Original Android Development] Clark789:
Thanks, Andi!

Installed it on CM12S and what should i say: you're damn right: HELL HAS BROKEN LOOSE!! :)

No, kidding... Runs very fine, better responiveness than before! I'll report back, when i see the battery drain...

Cheers

Clark
[ONE Original Android Development] Formhault:
I did run that command and it doesn't do anything... :eek:
[ONE Original Android Development] andip71:
Then your last restart might have been away for some time already, and the log was already overwritten.

(explanation: the dmesg kernel log is a rolling log, so if it gets full, the oldest records get overwritten).

You can restart your phone and try again straight after it is back.

Andi