yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] magnamentis:
i had a feeling whow.....

hi andi,

i could make it very long but will keep it short:

your kernel fits exactly

like i somehow suspected ( hoped for ) this morning when i came across it on my weekly search :good:

so as promised and since you've just used all the money for the dev opo ( I had several [positive] big laughs about that term if you know what i mean ) i think it's about time to refill your wallet for a few beers ;) and perhaps a martini for you wife )

what else can i say:

THANKS

PS: your little encounter with "FraFra" just has proven once more that attitude wins over talent, the more if the first is good :) and the latter is present :highfive:

here it comes:

[IMG="beer and martini"]http://xdaforums.com/attachment.php?attachmentid=2981124&stc=1&d=1413997697[/IMG]
[ONE Original Android Development] andip71:
Thanks for the confirmation.

However, thanks to a user who PM'ed me, a glitch has been found which only occurs on the cm11 kernel. CPU Max Frequency does not stick due to different mpdecision behaviour.

The good message however is, I think I already fixed it (it is an app issue, not a kernel issue) and will be able to roll out a new app already tomorrow.

For all that urgently need this functionality on the CM11 kernel already now, please fall back to app version 2.1.49 for the time being.

Many many thanks for the very kind donation. Thats all I can say. Very much appreciated.

And I try to really give these money back to you guys straight away,.... after I have the dev OPO now, I can give the CM11 kernel to you and can support it.

Cheers!!!

Andi
[ONE Original Android Development] andip71:
Update: Ok, I am already testing app version 2.1.51... which now sets CPU max frequency also sticky on CM11 apparently.

Still testing with a few users till tomorrow, then I will release it :)

Cheers

Andi
[ONE Original Android Development] Setting.Out:
I use synapse to control the kernel, and never had a spike in frequency... I know CM11/S has an option to let it decide the "best" settings per app being used.. Either in combination to a different kernel control app or rom, this is/was a non issue for me..
[ONE Original Android Development] andip71:
Ts ts ts... Synapse ☺

If it works for you, fine. But there are many functions you can only configure with my tailored App, just for info...

Andi
[ONE Original Android Development] Setting.Out:
It honestly is easier to test against other kernels due to saved profiles.. (Hangs head in shame).. ;)
[ONE Original Android Development] andip71:
Understand. No problem at all.

I am just worried you will not be able to unleash all kernel features by this way ?

Andi
[ONE Original Android Development] Setting.Out:
If benchmarks and read/write speeds mattered, the beast is out of the cage.. ;) I'll freeze synapse and try your paid version of the app.. ;)

*edit*.. I'm blind, I can't find the donate section of the app.. ?
[ONE Original Android Development] andip71:
You need to install the normal version from the homepage.

Donation key will be emailed to people that donate (PayPal).

In theory donation can be purchased as well in play store, but this will feed Google with 30% fee, so I don't recommend this.

But: donation version is not required if you do not want to unlock some comfort features...

Andi
[ONE Original Android Development] andip71:
I am on a new version with latest commits and ramdisk now.

Good, as I cannot do anything from tomorrow onwards till Friday due to a business trip.

Andi
[ONE Original Android Development] andip71:
Will release soon... Working with latest official nightly as you can see [emoji3]

Andi
[ONE Original Android Development] demon507:
Turning off the ambient mode will stop the wakelock. :thumbup:
[ONE Original Android Development] bloof:
Yes, that's the one that worked, thanks.
[ONE Original Android Development] andip71:
CM12.1 update

Hi,

in order for Boeffla-Kernel to work with latest official CM12.1 nightlies, here we go with beta8.

Version

4.0-beta8

19.04.2015

Note: You need this version to work with CM12.1 official nightlies !!

Update: Updated with latest 29 official CM kernel commits as of 19.04.15

Ramdisk updated to official CM12.1 version of 18.04.15

I hope this will be stable for some days, I am going on a business trip tomorrow morning for 5 full days without access to my dev environment. So I will not be able to do something on my kernels for 5 days now.

Enjoy

Andi
[ONE Original Android Development] beany>:
Safe journey, and thanks as always. I think it's really good of you to give [MENTION=3279788]ZaneZam[/MENTION] a break.... :D
[ONE Original Android Development] Hexxer:
Hmmm, if you are running am CM12 than you get display problems. If that is happend? Looks like there is a solution - but i guess CM12 wont work with a CM11 Modem?

https://forums.oneplus.net/threads/...en-wake-issue-power-button-double-tap.246703/
[ONE Original Android Development] andip71:
Guys, I am on a business trip the next 5 days now. Away from my development box. I will follow the thread and answer questions with delays. However I cannot provide any new builds during the next 5 days.

Enjoy the free time ?

Andi
[ONE Original Android Development] alexbk66:
Yeah, pretty happy with my latest setup finally. That was night sleep, 100% deep sleep!

Even for normal use I get 89% which is great.

Secret is - don't use "battery saver" apps. Also I set "WiFi screen off" to never.
[ONE Original Android Development] scorpionhd2:
Do you mean that the Wi-Fi is set to "turn off during sleep" in the WiFi advanced menu?

If so, do you keep data on?
[ONE Original Android Development] maxver0:
Hey boeffla, how much did touch drivers changed since february?

I've got this issue with double tap to wake. I have to tap like multiple times Between 10 and 20 taps, which is annoying, it should wake screen after 2 taps!

I've been using blisspop early february build which had issues with double tap to wake, I have been reporting it on blisspop thread but they said they can't reproduce this issue. But when I flashed your kernel, issues were gone. But it was back in february, then you have released some updates with kernel which have bring back this issue. And since then, no matter which kernel I can't wake my device properly. Even on CM12.1 nightlies or CM12S.

CM12S with boeffla CM12s 3.0 beta 3. Double tap to wake issue is still there, also there is issue with swipe to left. If I lock it wait a sec and double tap, it will do just fine, but 5-10 seconds more and this issue starts. So it might have to do something with sleep state (too deep deep sleep)?:D

Also it happens without prevent from waking up device

I will send you catlog, maybe you will catch something. Check PM.
[ONE Original Android Development] bloof:
Thanks for sharing.

Do you also have any widgets (weather, clocks, etc?

And sync is off?

And no automatic titanium backups?

Do y you count greenify as battery saver app?

I get ~95-96% with all the above and wifi/data 100% of the time. Just really curious how you get 100%, everything must be turned off...
[ONE Original Android Development] fards:
had a very quick look at the oxygenos kernel source,

the dts are in the wrong place by the look of things,

The files appear to be valid (don't have option to set up a *nix box to test this at the moment as my pc is dead and my tablet won't cope!) but it might be worth copying them to the ./project/14001 folder as that's where they are expected according to this commit.

+$(warning JACK: $(DTS_NAMES))
ifeq "$(KERNEL_USE_OF)" "y"
-DTS_FILES = $(wildcard $(TOP)/kernel/arch/arm/boot/dts/$(DTS_NAME)*.dts)
+DTS_FILES = $(wildcard $(TOP)/kernel/arch/arm/boot/dts/project/$(PROJECT_NAME)/$(DTS_NAME)*.dts)
+#DTS_FILES = $(wildcard $(TOP)/kernel/arch/arm/boot/dts/projects/MSM_14001/$(DTS_NAME)*.dts)
+# ifndef VENDOR_EDIT //Song.Xinhua modify
+#DTS_FILES = $(wildcard $(TOP)/kernel/arch/arm/boot/dts/$(DTS_NAME)*.dts)
+# else
+#DTS_FILES = $(wildcard $(TOP)/kernel/arch/arm/boot/dts/projects/$(OPPO_TARGET_DEVICE)/$(DTS_NAME)*.dts)
+# endif
DTS_FILE = $(lastword $(subst /, ,$(1)))
DTB_FILE = $(addprefix $(KERNEL_OUT)/arch/arm/boot/,$(patsubst %.dts,%.dtb,$(call DTS_FILE,$(1))))
ZIMG_FILE = $(addprefix $(KERNEL_OUT)/arch/arm/boot/,$(patsubst %.dts,%-zImage,$(call DTS_FILE,$(1))))
[ONE Original Android Development] maxver0:
Also I have tried all different modems, kitkat doesn't boot at all :cyclops: All other modems, like CM12 nightlies or OPO L5 alpha modem doesn't change anything,
[ONE Original Android Development] andip71:
I can just confirm, my kernels now use all latest touchscreen drivers.

We found out already in the past, this is good for many, and not so good for some.

But as long as there is no firmware available that works fine for both groups of people, always someone will lose.

Funny is, I never felt any difference, for me all touchscreen firmwares seem to be equally good.

Pretty sure I also tried that. But not 100% sure anymore as I for sure tried something like 10-15 different things.

So I can give that another try once by from my business trip.

Andi
[ONE Original Android Development] fards:
Yeah it looks so obvious it can't be that :)
[ONE Original Android Development] donmargarito:
So.... will we have boeffla for oxygen soon? or until Oneplus doesn´t give you what you need you won´t be able to do it
[ONE Original Android Development] maxver0:
Is it possible to grab old touchscreen drivers from January? Are they avaliable somewhere?

If they're accessible I guess it won't be a problem to build with cm12.1?
[ONE Original Android Development] andip71:
If they would give complete and working kernel sources, then yes.

The kernel is already done, just it does not work because device tree blob is missing/incorrect.

See here, I asked oneplus directly:

https://forums.oneplus.net/threads/oxygenos-kernel-source.296969/page-4#post-10910921

You can always revert back to older touch screen drivers in the kernel code.

But then you need to build the kernel from scratch.

Andi
[ONE Original Android Development] Mohdsultan:
I love this kernel, this kernel and lord boeffla bought life to my oneplus one. My oneplus was taking 5 hours to charge but when I flashed the kernel and tweaked the charging profile then it got the life back.

Now it charges at 1000 amps.

Thanks [MENTION=947981]Lord Boeffla[/MENTION].
[ONE Original Android Development] EdgA#1:
Moin andi,

it is like The good old S3 times, kernel and support is great!!!!

No problems here!!

thank you!!!

And ZaneZame is still here with his zzmove ...GREAT Team!!
[ONE Original Android Development] karthi89:
How can i uninstall this kernel? Is there any zip package available? Flashing the stock boot image will not uninstall modules isnt it?
[ONE Original Android Development] alexbk66:
I do have weather widgets (i.e. Aix Weather Widget) but I set to update only when screen is on. Titanium backup I do manually.

Regarding Greenify - sure it is "battery saver app", but I found before that Greenify was actually contributing to wakelocks (alarm) more than anything, after Google of course.

Amplify is a good app too, but only if you get wakelocks which you can't fix without artificial wakelock blocking. Because most apps (Goggle for example) become more even crazy if try to interfere with their internal life...

BTW, I uninstalled Google search app completely, it was using too much battery. Same for "Sound Search for Google Play". And I used "Bloatware Removal Script".

Sure 100% Deep Sleep was achived at night with Airplane Mode On (I use Tasker to switch Airplane Mode when phone is screen down at night).

But during the day I still get 89%-95% Deep Sleep.
[ONE Original Android Development] mishko:
In Boeffla app: Settings>App maintenance>Prepare complete removal. Then reflash stock kernel or your rom.
[ONE Original Android Development] alexbk66:
Yeah, that's what I mean - "Keep Wi-Fi on during sleep" set to Never.

But I try to minimize data use, i.e. configure weather widgets to update only with screen on, OneDrive to upload photos on WifI and power connected, Gmail - manual sync, etc.

---------- Post added at 08:28 AM ---------- Previous post was at 08:27 AM ----------

What does "Prepare complete removal" do? Doesn't reflashing ROM overwrite the kernel?
[ONE Original Android Development] ZaneZam:
not necessarily need. boeffla kernel uses modifications in the ramdisk to "hook" into the init process/apply settings, so if u flash back a stock kernel these "hooks"

are gone and all the boeffla related files/settings are doing nothing but just beeing there. its even comfortable if u want to use

boeffla kernel again because then all settings are restored after falshing it again.

it removes all leftovers (config files etc.) from the boeffla kernel, and yes as stated above if u re-flash stock kernel u have stock kernel and nothing more ;)
[ONE Original Android Development] gondsman:
I MIGHT have an issue with the latest kernel for CM12.1, but I'm not sure as it's kind of annoying to test. I'm running an uber build from the 17th and I've noticed in the last two days that in the morning my alarm clock (Timely) didn't go off. After I manually woke up the phone, the alarm finally started ringing. I reverted to beta7 and I tried setting up an alarm and leaving the phone alone for half an hour. The alarm rang normally in this case. Do you think there is any commit relevant to this issue in beta8? Or is it a ROM bug that happens randomly?

Thanks!
[ONE Original Android Development] ZaneZam:
may i kindly remind u that u use the "Uber" builds from my workshop and that we have to treat that seperate from the offical stuff here. no one can/will give support here (even not me *g*) :)

so what can u do now? flash the original builds from lord boeffla and see if your issue goes away. hope u understand linaro/uber is experimental stuff with no warranty to work 100%
[ONE Original Android Development] gondsman:
You're right, sorry. I was indeed using your builds, but I made an "apples to apples" comparison as the two kernels I'm referring to were both built with the same toolchain. Anyway, I'll try with the build from this thread and report back. :)

EDIT: Although I was referring as a uber built CM12.1 ROM in my message...
[ONE Original Android Development] karthi89:
Thanks for the clarification bud. Going to flash the kernel now ;)
[ONE Original Android Development] Franc38:
Andi, the combination of the last 3beta3 with COS12 is really amazing...

No bugs that I've noticed, phone is very smooth and reactive... and the battery life is now really amazing. I'm at 2 days and 13 hours, 16% remaining, with 3h30 screen on, some phone calls, plenty of mails, not super great network, a bit of 3D gaming.

And with the same settings and CM11S with your corresponding kernel I would have arrived at 16% with this kind of usage in 1 day and 3/4 at most!
[ONE Original Android Development] fabiienb:
When i switched to Cm12 ( temasek 9.4) I noticed double tap to wake work more slowly.

Try to tap more slow???

Kernel related? Rom? I don't know...
[ONE Original Android Development] acuicultor:
Just want to inform:p
[ONE Original Android Development] andip71:
Thanks, Edga. And nice to see you back.

Cool feedback, appreciated. And happy all seems to go perfectly fine for you.

Hard to say. I generally do not test against any roms that is not genuine CM. And at least with CM12 I had no delay ever.

Yes! That is great. I also just flashed latest nightly and all is back to normal again.

It seems, CM team tried to implement something new with the 21.04. nightly, mainly some specific lz4 compression stuff. They reverted that back now as it apparently created a whole bunch of issues.

Andi
[ONE Original Android Development] fmc000:
Just a heads up : the new stable kernel 3.4.107 has been released.
[ONE Original Android Development] andip71:
Already 2 days ago :)

I will update the kernels to 3.4.107 once I am back from my business trip.

As always...

Andi
[ONE Original Android Development] beany>:
I have no double tap issues either, on Bliss 5.1 or 5.1.1, so not a kernel issue.
[ONE Original Android Development] fabiienb:
For me is not a issue maybe placebo effect ^^

But not kernel related yes I think...
[ONE Original Android Development] lou2s:
Just flashed latest cm12s OTA S17L, then boeffla cm12s beta 3, see if they work nicely with each other.
[ONE Original Android Development] *Zapp*:
Got a link to the official OTA for S17L?
[ONE Original Android Development] davebugyi:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS17L-bacon/e816218e8a/cm-12.0-YNG1TAS17L-bacon-signed.zip
[ONE Original Android Development] abhibnl:
Hi everyone, as Andi is on a business trip, could anyone else with the knowledge of kernel sources could check if new COS12 kernel sources are updated as well? Downloading ota atm and will take 3 hours. Did anyone flash boeffla over new ota as of now?

Sent from OnePlus One
[ONE Original Android Development] davebugyi:
There are some updates, but nothing special, that can not wait until the Lord comes back :)

I have flashed 3.0-beta3 right after upgrading and it is working great so far (in the last 6 hours).
[ONE Original Android Development] anshumandash:
I am still getting the event and wlan related wake locks with beta 8 on 5.1 blisspop.
[ONE Original Android Development] magnamentis:
why don't' you post this in any app thread for every app you have installed. would go like: i'm still getting the event and wlan related wakelocks with google chrome on 5.1 blisspop. what i mean is that wlan related wakelocks are not kernel related but userspace related. just does not really belong here IMO, because it makes the impression that you blame the kernel. if anything but an app which is probably the culprit, it would be rom related long before kernel related and since i use the same rom and device i can tell you that it isn't. even kernel wakelocks are usually triggered by activities which have their roots somewhere in the userspace, speak apps most of the time.
[ONE Original Android Development] bloof:
Powermanagerservice wakelock contains all the app related "partial wakelocks" (if i remember correctly) so check all your partial wakelocks, they're the ones giving you trouble.
[ONE Original Android Development] Pepsy89:
Is one plus one cm12s supported ?
[ONE Original Android Development] davebugyi:
Yes, if you read a page back, it was already confirmed (by me), that 3.0-beta3 works fine on COS 12
[ONE Original Android Development] DjDiabolik:
I have read the post about [MENTION=220904]andi[/MENTION] it's out for business untill tomorrow :)

Someone has tryed to flash the 3.0beta3 for CM12s on this "cm-12.0-YNG1TAS17L-bacon-signed" ?
[ONE Original Android Development] konman21:
Curious as well
[ONE Original Android Development] kurtextrem:
Yeah, working fine.
[ONE Original Android Development] davebugyi:
Lol, it's a page back and also above your posts... Srsly guys?
[ONE Original Android Development] konman21:
You're are right, idiot me....... Forgive me
[ONE Original Android Development] novren:
I had touch screen issues, flashed boeffla kernel, all good now
[ONE Original Android Development] alexbk66:
I'm flashing different ROM now, so can't make screenshots. From memory, just reduce max CPU freq. to 1497MHz, coservative governor (not powersave!) and disable CPU boost (i.e. screen on, touch) - it's still pretty responcive. And reduce GPU max freq. to 462MHz
[ONE Original Android Development] MBurns2:
do you use the stock hotplug or the optimized one?
[ONE Original Android Development] Clark789:
Hello,

anyone flashed the new update YNG1TAS17L? Are there any interferences between Boeffla 3.0b3 and the update?

EDIT: I flashed it via TWRP, reinstalled SuperSu and finally reinstalled Boeffla 3.0b3. Seems to work without any issues...

Regards

Clark
[ONE Original Android Development] gazou_hb:
Seens ok

But now default config kernel.

Which is the best config for the opo 64g?
[ONE Original Android Development] bloof:
The OTA is a full ROM, isn't it?

I clean flashed it (ie: wiped dalvik/cache/system/data) then flashed the OTA and superSU. All seems fine.

Running boeffla 3 beta 3, everything seems ok, but the boot.img from 17L has different md5 than from first CM12S, so i expect some differences, hopefully improvements.

---------- Post added at 09:53 PM ---------- Previous post was at 09:50 PM ----------

"best" is relative, you always trade off battery vs performance but you can get extremely good performance without sacrificing battery. Depends what you want/need.

Boeffla app comes with some presets you can use (see in menu - > presets, but i would remove the undervolting one applied).

See link in my signature.
[ONE Original Android Development] abhibnl:
Hi Andi,

I was reading AK's latest kernel changelog and he has pushed some updates to Interactive governor. Since interactive is default cm governot and i'm sure like me, many others are also using it as a dd, could you please have a look at those updates once you are back from your trip and start working on the kernel again?

Sent from OnePlus One
[ONE Original Android Development] andip71:
Very unlikely I will change behaviour of the main standard governor, following close to stock objective.

If it is worth having these changes (and this is something I am curious to get reports), I would copy interactive governor into a new one and tweak it.

Like I did with pegasusq to pegasusqplus already long time ago on the Galaxy S3.

Andi
[ONE Original Android Development] Pablo.x:
That would be amazing, you're doing a great work :)
[ONE Original Android Development] kurtextrem:
Has anyone ever heard of the "HYPER" governor?

http://androidmodguide.blogspot.de/p/blog-page.html (and what is zzManX? :eek:)

Maybe HYPER is a look into worth it for this kernel.
[ONE Original Android Development] Clark789:
Alter updating, i got significantly lower Antutu benchmarks. I don't worry about the absolute score, but the change is remarkable. From around 47k points before updating and 35k points after. In different disciplines only the half of points.

Maybe kernel and update don't really fit at the moment?

EDIT1: I think, i found the cause: the governor. I always use zzmove. But now zzmove uses very strict only one core. The other three cores are most of the time offline. Even with Antutu. When i changed the governor to performance, the Antutu result is okay with 49k points and all cores running.

EDIT2: Must have been a hickup. First i tried instead of zzmove native hotplugging profile the 4 cores min. and it works very well with Antutu. Got back to zzmove native brings 3 cores to offline and didn't wake up again. And then i tried a restart, which didn't bring up my OPO. So i switched it totally off and waited some minutes and restarted it. After this everything's fine and Antutu results with zzmove native hotplugging working very well again. Weired, isn't it?

Regards

Clark
[ONE Original Android Development] abhibnl:
Great! You can count me in for a test build!

Well there are actually a ton load of governors out there. I remember about a blog with the list of all the available governors and man i was shocked to see there are 50+ governors out there.

Sent from OnePlus One
[ONE Original Android Development] ZaneZam:
zzmanx is a fork of zzmoove made by dorimanx ;)
[ONE Original Android Development] joefso:
PegasusQ is not listed in the governor. I am running the 3.2-CM12 20150415 on slimsaber using the boeffla config app. Is it obselete now?
[ONE Original Android Development] NuLLV01D:
It's not included
[ONE Original Android Development] joefso:
it supposed to be default according to the documentaiton on the website: http://www.boeffla-kernel.de/index.php/kernel-settings

what profile is recommended now then?
[ONE Original Android Development] NuLLV01D:
The documentation was written at the time the kernel was S3 exclusive. Its mostly invalid now and the default governor is interactive
[ONE Original Android Development] acuicultor:
This information isn't updated since s3 days so what you see there is related to s3 kernel.

Stock settings are good and balanced for good battery life and performance