yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Th3DaRk_Vampire:
[MENTION=1045701]lordbo[/MENTION]effla stupid question... You update your 12S kernel version with the last update right?

The question is: your last kernel is full compatible with the las 12s version?

I'm using the latest version of cyanogen 12s and when my OPO this in my pocket the screen turns several times, this because I imagine it not working the option to avoid accidentally turning on the screen, which has to do with the proximity sensor, will be the kernel may cause this? I'm trying to find a solution to this problem

before flashing CO12S was using Exodus nightly 06/17

any suggestions? Thanks

Sent from my One+ One
[ONE Original Android Development] NeGriTa79:
I wanted to know if it was possible to implement the ability to turn on the LEDs of the keys ... only when touched .... but if I touch the screen are off ... (this option was present in the Samsung Galaxy S2, with kernel Dorimanx)
[ONE Original Android Development] sui81:
Guys can you tell me something about Bfq7vr6.

What are the Benefits ? I think it's a Scheduler right ?
[ONE Original Android Development] Moster2:
Ye, its an IO scheduler. They claim to be faster than the usual schedulers like cfq, deadline, etc.

http://algo.ing.unimo.it/people/paolo/disk_sched/results.php
[ONE Original Android Development] Herr Olsen:
Especially if you have a harddrive in your phone. (-;
[ONE Original Android Development] Vonnegut:
Check the last test..
[ONE Original Android Development] Setting.Out:
I've tried it on another kernel and it did provide good performance, but I didn't find it to be more/less responsive than row or fiops..
[ONE Original Android Development] Roman91:
andi,

do you think the AudioFX is a kernel equalizer (like boeffla sound for i9300) or it's a simply software eq??
[ONE Original Android Development] andip71:
Software afaik.

Andi
[ONE Original Android Development] Roman91:
so we need your magic touch :)

always if it's possible
[ONE Original Android Development] andip71:
I would be more than happy to implement more Boeffla Sound features on the OPO.

But the issue still remains: I have no documentation about the used audio hub (wdc9320).

For the Wolfson Micro audio hub used in the various Samsung devices, I had some documentation to work with.

You get me the technical documentation and I can work on it. Deal? :)

(honestly, you will not get anything from Yamaha without being a company signing an NDA... same was with Wolfson, but could get hold of docu somehow anyways)

Andi
[ONE Original Android Development] Roman91:
****,

I did not think that there was no documentation for a qualcomm chip XD

can we try to ask for documentation directly to oneplus?
[ONE Original Android Development] Moster2:
Asking is always possible, but they probably wont answer, since they have to follow some stupid agreement to keep the documentation private.
[ONE Original Android Development] andip71:
Exactly, asking can be done, but it will not give any results.

I made the same experience with Wolfson Micro long ago. They are just ignoring you.

But still - feel free to try it. It would certainly help the whole community.

Andi
[ONE Original Android Development] andip71:
New beta scope...

Hi all,

I though yesterday I closed the scope already for the next beta, but I could not resist to put some more things in today morning.

I am still testing it, but it is looking good.

So finally the scope will be (release targetted for tommorrow if all goes well with testing by tomorrow):

hotplug features with lots of profiles (Default, Optimized, 1 core, 2 cores, 3 cores, 2 cores on, 3 cores on, 4 cores on)

notification led control (brightness, speed, fading)

GPU 27 MHz step added (idle freq)

readahead buffer default increased to 1024

new touchscreen firmware as of 28.10.14

all cm patches up to 28.10.14

few smaller bug fixes

Stay tuned

Andi
[ONE Original Android Development] mdv53:
Wifi doesn't work on bèta 5 cm11s. Revert wifi drivers doesn't work. After i install bèta 5 other kernels wifi doesn't work anymore. I muss install The basic r38 rom. Other kernels wifi work not on bèta 5

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] andip71:
What what what?

Wifi works perfectly fine on cm11s with beta5 if you have still a unmodified rom !!!

If wifi does not work with beta5, most likely some wifi firmware has been hacked by other kernel and that is the main reason.

So if it does not work with beta5, you will have all possible issues with stock kernel and some other custom kernels as well.

If the wifi firmware restore script could not fix the issue, all you can do is to flash the rom over again to bring everything back to normal.

Andi
[ONE Original Android Development] P1nGu1n_:
Can't wait, you're the best! :D I'm wondering what the difference between default and optimized hotplug profile will be
[ONE Original Android Development] _Beni_:
Also merged http://review.cyanogenmod.org/#/c/75465/ ?

I read in francos kernel it increase the battery life feelable.

I know your kernel should be similar to stock, but isnt it also a custom kernel? :)
[ONE Original Android Development] andip71:
Default is full cm11s / cm11 stock - which means mpdecision holds 2 cpu cores active always. This is the default behaviour as said.

The "Optimized" profile changes that in a way I force mpdecicion to mainly rely on one core if there is not a lot of cpu load. If load comes up, I let mpdecision do its normal work again and up to all cores are getting utilized again.

So basically it optimizes by ensuring there are no 2 cores active when not required.

Rest is - hopefully - self explaining. 1 core limits the system to 1 core always, 2 cores to 2, 3 cores to 3...

And 2 cores on means, whatever the system load is, even in idle there are 2 cores always plugged in. Same goes for 3 and 4 respectively.

Hope that makes it clear...

Thanks

Andi
[ONE Original Android Development] andip71:
Nope, this is not in my kernel. And yes, it is going too far away from stock in my opinion - sacrificing my design targets.

I do not want to create a battery saving monster, nor a highest performance kernel, but a good mix.

So sorry, this is not in my roadmap for the time being.

Custom kernel definition can be interpreted quite different. Eh?

Thanks anyway for the suggestion.

Also in the S3 world in the past 2 years I did not want to put things in for a long time and one day I changed my mind for some of the proposals. So, we will see.

Andi
[ONE Original Android Development] davebugyi:
Check if you have correct firmware and disable ambient display. You can use an app to test the sensors, like Sensor Sense.
[ONE Original Android Development] maxver0:
C)

http://www.xda-developers.com/android-m-brings-much-improved-standby-time-to-nexus-5/

http://www.reddit.com/r/Android/comments/39qo7b/conclusion_of_nexus_5_doze_test/

http://www.reddit.com/r/Android/comments/38lsi1/android_m_doze_test_with_nexus_5/
[ONE Original Android Development] FunkyRasta:
Hey ! This the only kernel that gave me nexus 5 like smoothness. I want it to run with 4 cores on all the time, but 1 core on when screen is off (music listening etc) . How do I do that ? There is no "screen off single core" in kernel app. Currently I'm running "4 cores min" as zzmove 4 cores doesn't make all 4 cores online all the time.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] twowheeler:
Don't know if it's a kernel bug but when I delete all recents, switch off and on again the phone ends up in a bootloop. Doesn't happen without deleting all recents or when rebooting normally.

I'm on latest 12s(with the touchscreen fix) and beta 5

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] andip71:
Create two profiles in Boeffla Config and switch them according to screen status in tasker.

That is the only way I can think of atm.

It is 100% compatible. Same code basis, same ramdisk.

What are recents? (sorry, using my phone with different language settings usually).

But very certain this is a bug in the rom as this is not at all on kernel layer level.

Andi
[ONE Original Android Development] twowheeler:
The recent apps ;)

Thought so too, but still thought i had to share for if it wasn't a rom bug.

The kernel is freakin amazing btw. First one i tried on the opo, so far gives me great battery
[ONE Original Android Development] GForceXIII:
I just noticed a bug, proximity sensor doesn't block the screen from waking up with power button. This doesn't happen on cm 12.1 stock kernel.

Edit :

I'm on boeffla 4.1 beta 5.

CM 12.1 20150618
[ONE Original Android Development] shoman94:
Not true... Works just fine.
[ONE Original Android Development] GForceXIII:
Really?

It's not working on mine when waking up the phone with power button.

But it does block the phone from waking up with double tap.
[ONE Original Android Development] shoman94:
Well well.... I just tried it again and now it stopped.... Doesn't work for either wake up....Ugh. I can't have that....

Is this only on beta 5?

I give up.... It's intermittent.
[ONE Original Android Development] FunkyRasta:
Huh ? I don't quite understand your answer, however still happy to have a reply, thanks :).

I wanted to know if there is only one core on when screen is off, even if I set hotplug to 4 cores min :)

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] andip71:
Most probably you need to flash correct firmwares.

Works fine here and is even not controlled by kernel but rom.

No beta5 issue whatsoever.

Andi

Then the answer is: no

4 cores on means 4 cores on, regardless if screen is on or off...

Andi
[ONE Original Android Development] lchiocca:
Ahhh.... another (never ending) touchscreen commit popped up:

http://review.cyanogenmod.org/#/c/101396/
[ONE Original Android Development] andip71:
... and it is already merged into CM-12.1 brach officiall.

So will be in my next CM12.1 kernel, and will also backport it into CM12s kernel.

Andi
[ONE Original Android Development] andip71:
And by the way... to stop the "whining" about color control, I have now decided to add KCAL2 support.

Teaser attached.

Andi
[ONE Original Android Development] beany>:
I can't believe you caved... ;)

Now people will think you'll give in on everything. But you and I know that's not gonna happen.
[ONE Original Android Development] andip71:
No, for sure not.

The thing was simply: I wanted to put it in for the less powerful roms like Oxygen OS, which does not have any color control options.

So, when I did it for Oxygen anyways, there was no need to not put it into my other kernels as well. Effort is zero.

Andi
[ONE Original Android Development] andip71:
- deleted -
[ONE Original Android Development] andip71:
New betas

Hi all,

new betas for CM12s/COS12 and CM12.1.

Main changes: Color control v2 is now implemented (credits to Savoca), note you need latest Boeffla-Config App in version 2.1.86!

Also a new governor has been added: impulse governor

CM12s/COS12 -- Version

3.1-beta6

22.06.2015

Color control V2 implemented (you need Boeffla Config App 2.1.86 or higher) - credits to savoca

impulse governor added (Click here for more info)

Updated with latest official CM kernel commits as of 21.06.15

CM12.1 -- Version

4.1-beta6

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

22.06.2015

Color control V2 implemented (you need Boeffla Config App 2.1.86 or higher) - credits to savoca

impulse governor added (Click here for more info)

Updated with latest official CM kernel commits as of 21.06.15

Ramdisk updated to official CM12.1 version of 22.06.15

Enjoy

Andi
[ONE Original Android Development] cr0wnest:
Keep up the good work with these updates! Excellent battery life as always and I love the customisation boeffla app has to offer. Booting up with 4.1-beta6 now :)
[ONE Original Android Development] maxver0:
Uh, uh, few new commits in upcoming nightly regarding WiFi, but it doesn't look like it's going to fix WiFi drops in deep sleep :/
[ONE Original Android Development] magnamentis:
hi andi,

i'm not that easy to impress but that saturation thingy makes it look like my note 2's amoled, great job and thanks a lot for this one, a real improvements since i like saturated colors a lot.
[ONE Original Android Development] ghul21:
Some nice values ?
[ONE Original Android Development] twowheeler:
Might be a stupid question, but do i need to whipe cache after flashing the update in twrp? And no need to change anything in the app right (already updated that one)
[ONE Original Android Development] ghul21:
Just flash it ?

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] fards:
That's display not touchscreen. It's designed to remove flickering when even is really dark
[ONE Original Android Development] rahulrai:
Hi andi is it ok to use it with latest BlissPop of 21.06.2015. I know that you are using stock but just a little help required. Thanks for the gift.
[ONE Original Android Development] andip71:
I don't know. It should be ok but someone else would need to confirm to be sure.

Andi
[ONE Original Android Development] Chikko:
i need you help, i flashed latest beta release, but it was instable for me, so i flashed over the beta release before, beta 5 over beta 6. Now i'm in a bootloop without recovery access. Can someone help me?
[ONE Original Android Development] andip71:
Was probably a bad flash or incompatibility with your rom.

You should restore your last nandroid backup. Something more is corrupted at your side.

Btw beta6 reported to be rock stable otherwise (on original cm / cos).

Andi
[ONE Original Android Development] rahulrai:
yes it works fine. One question andi...............is there any good refrence for setting up the new added feature in the colour menu of the app. I am not good at setting up colours.
[ONE Original Android Development] kurtextrem:
Finally. That thing annoyed me for ages.

And a HUGE thank you for the kcal support! Finally I can use cf.lumen with the best performance... my eyes will like that :))
[ONE Original Android Development] Roulianooo:
Thank's a lot for the new beta6

Works like a charm on Slim with the [MENTION=4876554]Mrwargod[/MENTION] ported version :D

Colour control is just awesome !

Keep up the good work :good:
[ONE Original Android Development] andip71:
Oh, honestly.. I never use any kind of color control. I just don't need it.

But there were so many people "whining" for it, they should now be able to help you.

As for your personal taste, you can adjust it in a way you like it most. The test picture in the new Boeffla-Config app should show you how the changes in the settings materialize.

Great to hear a happy user :)

Thanks for the words, very much appreciated.

Andi
[ONE Original Android Development] pugsang:
[MENTION=947981]Lord Boeffla[/MENTION]

Sorry if it has been asked before. Would it be possible to add vibration strength control to your kernel?
[ONE Original Android Development] andip71:
Possible is a lot. But I am not planning it, because both COS12 and CM12.1 have it in the rom settings.

And I have a kernel tweak app, which should not conflict with the rom in any way.

Andi
[ONE Original Android Development] pugsang:
Pretty clear. Thanks
[ONE Original Android Development] Chikko:
Thanks, at least i found out how to enter in recovery, i dirty flashed my rom (cm12.1 official release of 20/06/2015) and now everything work fine. Before to flash beta 6 i came to a clean flash and with beta 5 everything was ok.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] fmc000:
[MENTION=947981]Lord Boeffla[/MENTION] : I'm curious about how the app updates the kernel. I'm pretty sure that the recovery script is not involved, as I never see the Philz screens when the phone reboots. Do you extract the new modules and the flash the kernel img like Flashify does, by chance?
[ONE Original Android Development] andip71:
Ok - warning deleted.

After a full fresh install all seems to be ok again. Still interesting what caused exactly the same issue for me on both OPO and S5. Anyways :)

Andi
[ONE Original Android Development] twowheeler:
Could you share your settings? :)
[ONE Original Android Development] andip71:
The app does not use any updater script etc.

In fact it does:

- switch to SELinux permissive

- flash boot.img to boot partition (dd command, done in a kernel script started by the app)

- delete old modules out of /system/lib/modules

- extract the new modules to this folder and set permissions (also done by a kernel script)

- disable dynamic fsync, sync file systems

- wait 1 second to allow file systems sync

- reboot

(if you have chosen to wipe Dalvik/ART cache and cache partitions during a kernel flash, this will be done before the reboot part as well)

Andi
[ONE Original Android Development] kurtextrem:
I didn't set up too much, just for my liking (Sleep time and so on is your personal choice I'd say). The only important thing I've changed is the sundown color filter: to 1900 K (as f.lux says everything above is still too bright for the eyes in the dark)
[ONE Original Android Development] Mrwargod:
A huge thanks to the awesome work and imense help by [MENTION=947981]Lord Boeffla[/MENTION] and [MENTION=3279788]ZaneZam[/MENTION].

:good:
[ONE Original Android Development] fmc000:
Thanks Andi, very clear answer. I still don't understand how you can change the kernel to a live system and still have it run without problems.
[ONE Original Android Development] andip71:
The kernel is running in memory, it gets loaded by the ramdisk. The boot partition where the kernel sits is not required after system has started anymore.

Andi
[ONE Original Android Development] jukyO:
It so annoying.
[ONE Original Android Development] magnamentis:
hehe... funny, exactly the same settings here LOL
[ONE Original Android Development] maxver0:
Found a solution, will share in few hours after work.
[ONE Original Android Development] magnamentis:
6 months perfectly compatible without any hick-ups. you can use this kernel blindly for bliss while a nandroid is recommended under all circumstances whenever updating roms and kernels.
[ONE Original Android Development] andip71:
Curious.... :D

Although I am not affected by wifi drops.

Andi
[ONE Original Android Development] jukyO:
Thanks in advance!
[ONE Original Android Development] magnamentis:
you never have to wipe caches for kernel install, impact is zero, thus no damage done as well :)

just thought it worth to point out that this is general, not kernel specific, hence the "never" :) ;)
[ONE Original Android Development] Chikko:
If i set only 5ghz in wify frequency, wifi stop to work. It come turned off, and if i try to turn it on, it doesn't work. A reboot solve the issue, but i have to select 2.4 or automatic in frequencies, before

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
I cannot contribute, I have no 5 GHz wifi here to test anything.

Maybe someone else knows something.

P.S. It would be helpful if you could let people know which kernel you use exactly.

Andi
[ONE Original Android Development] Chikko:
I'm sorry, however i use your kernel, latest beta release over cm12.1 of 20/06/2015. It has been a new clean install.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
Then I am 99,99% sure the same is with CM12.1 stock kernel. I have exactly the same wifi drivers in my kernel, without any changes.

Andi
[ONE Original Android Development] magnamentis:
i'm on beta 6 and have 5GHz only and no problem at all, working flawlessly as always, no disconnections in idle as well.

this means it's not he kernel, otherwise it wouldn't work here either, check your router, starting with a reboot of the rooter and delete the network and make a new connection.
[ONE Original Android Development] pugsang:
I too confirm that these settings work extremely well and give an Amoled Style to the oneplus screen

KCAL COLOR PROFILE

Colors: 255,255,255

Saturation: 285

Hue: 0

Display: 255

Contrast: 264

Gamma: 0
[ONE Original Android Development] fmc000:
Very similar to mine (290,0,255,265,0)

---------- Post added at 03:09 PM ---------- Previous post was at 02:36 PM ----------

There are reports of problems with the latest nightly, mainly FC on all keyboard types and other apps, along with continuous reboots. Anyone here with latest beta has performed the update?
[ONE Original Android Development] andip71:
Yes, me. And I was having also "system UI crashed" errors looping after a dirty flash to 23/06/15 nightly.

Both on my OnePlus One and S5, so something was definitely introduced which is not 100% compatible.

I have done a complete fresh install with 23/05 nightly and since then all is good again. Whatever that means...

Andi
[ONE Original Android Development] fmc000:
So, let me understand: you

dirty flashed the nightly with your kernel preserved by your addon.d script -> FC

clean flash the nightly and then flash your kernel -> all OK

?
[ONE Original Android Development] andip71:
I flashed the nightly with kernel preserved -> system UI crash

I flashed the nightly with the contained kernel -> system UI crash

I formatted system, data, cache partitions and installed from scratch, restored my apps, installed my kernel -> running fine

Andi
[ONE Original Android Development] fmc000:
Quite strange, after all the apps (titanium?) did you restore your kernel profile too? Are there any ramdisk related modifications in the latest nightly?
[ONE Original Android Development] andip71:
Sure.

Don't ask me why... in the German board the guys updated without issues even.

I cannot understand. My specific crash had to do with the in-built super user implementation. Even after I flashed Chainfire SuperSu the problems were gone for me. But this is not a solution I liked.

Andi
[ONE Original Android Development] fmc000:
Which SuperSU version? 2.49? I see that the app hasn't seen an update in months, I thought it was abandoned.
[ONE Original Android Development] andip71:
I used latest stable even, 2.46.

But for me it was not a solution as there is an underlying issue. And I really do not like underlying issues as you never know when they are coming up again and "hit the fan".

Andi
[ONE Original Android Development] fmc000:
Yeah, same for me. And as I have only one phone and I use it for work I am really not inclined to update before the issue is clear.
[ONE Original Android Development] suaverc118:
Doesn't this make the screen a little too blue? On my end it does.

---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------

Never mind, I turned adaptive brightness on.

---------- Post added at 09:53 AM ---------- Previous post was at 09:52 AM ----------

What are your red blue and green set to?
[ONE Original Android Development] pugsang:
No as far as I can see

Check the screenshot below
[ONE Original Android Development] andip71:
Guys, it is pretty obvious here two factors come together:

- personal taste

- hardware manufacturing differences

So values that one find nice are not fine for others. That is quite clear with graphical stuff as well as with audio stuff.

Andi
[ONE Original Android Development] pugsang:
True but regarding the personal taste blue is always blue. And if it is blue you can tell the difference when you have a white background. It is not between white and grey if you know what I mean.

Of course hardware differences are always a factor:good:
[ONE Original Android Development] andip71:
*** Absence notice ***

Hi guys,

I will be going on a business trip, followed by a vacation weekend from tomorrow morning onwards till Sunday night.

While I will try to read and follow as good as possible, please accept delays when answering questions.

Also please note, I will not have access to my build environment, so I will not be able to provide any new kernels etc. during the next 5 days.

Thanks for understanding

Andi