yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] karthi89:
Looks like the find7 touchscreen firmware has been merged. Will come along with the next nightly... :)
[ONE Original Android Development] andip71:
But as I stated already a few days ago - irrelevant for our opo.

Andi
[ONE Original Android Development] molonad:
Why irelevant?
[ONE Original Android Development] kurtextrem:
http://xdaforums.com/showpost.php?p=61963919&postcount=5753 see the answer for the first quote :)
[ONE Original Android Development] andip71:
The Oppo Find7 has it's own touchscreen firmware. So when they upgrade the firmware, it is not even used when you build a OnePlus Kernel.

Andi
[ONE Original Android Development] kantjer:
[MENTION=947981]Lord Boeffla[/MENTION] I have been testing your kernel for a few days now and I like it very much.

If it's OK with you I would like to build the kernel from source for Slim and SlimSaber (of course with all credits to you)

Can you guide me to what to change to be able to build a Slim compatible Boeffla-kernel from stock.

(I have seen this post from you but not 100% sure what to change in the source)

Thanks in advance
[ONE Original Android Development] mp3deviant721:
I can answer this, pull the init.environ.rc file from Slim's ramdisk and insert it into Boeffla's. That's the only change you need to make. The kernel gets compiled as normal. [MENTION=4876554]Mrwargod[/MENTION] told me how to do this so all credit goes to him.

OnePlus One | Euphoria OS x Boeffla edition™
[ONE Original Android Development] andip71:
And make sure somehow mpdecision gets renamed to it's proper name again [emoji6]

Andi
[ONE Original Android Development] kantjer:
Thanks, the init.environ.rc part I get but no idea what/where to fix the mpdecision part.

I always thought that was part of the kernel.
[ONE Original Android Development] andip71:
No. Mpdecision is a userland binary coming with the rom, located under /sys/bin.

Andi
[ONE Original Android Development] Mrwargod:
On slimsaber i never had problems with the mpdecision part, it seems to be working as intended.

But since i use zz hotplugging i can't really say.
[ONE Original Android Development] kantjer:
Have you checked if changing zzmove Hotplug settings makes any difference. From what I nothing changes. For example when I set it to zz Hotplug 3 cores minimum it still falls back to the default 2 cores online when idle.

Edit default Hotplug settings seems to work, but zzmove settings don't seem to be changing anything compared to stock settings.
[ONE Original Android Development] kantjer:
I tried it but when compiling the kernel the init.environ.rc is overwritten again. So building the ROM with Boeffla inline isn't going to work this way.
[ONE Original Android Development] andip71:
You need to exchange it in the ramdisk.

Andi
[ONE Original Android Development] kantjer:
Thanks, got it, my kernel build is up and running on SlimSaber
[ONE Original Android Development] andip71:
Kewl. Congrats.

Andi
[ONE Original Android Development] hafini:
Been using the kernel for a few days and I really like it. Only 1 thing is when I use Antutu benchmark, the phone always reboot mid test. Is that normal? I am on CM12S YNG1TAS2I3 and use the stable kernel.
[ONE Original Android Development] magnamentis:
you shall not use antutu would say the lord ( the real one ) JK

change governor to performance and scheduler to fiops and gpu governor to performance as well and try if it works
[ONE Original Android Development] thedoctor.gz:
In this way the test go on until the end, and the result is 37000 pts more or less. If I change to power extreme preset the phone reboot.

I'm on latest BlissPop and beta 12 Kernel, nothing else.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] Mrwargod:
Nice, i know that good feeling. :good:

Has for the hotpluging, i've only used zzmove native default, never tryed another profile. That one i know it keeps down to 2 cores online and ramps up when needed.
[ONE Original Android Development] magnamentis:
now you put the phone to the freezer and go again and check the difference, if you get between 45000 and 50000 after that it's the summer heat (thermal throttling) and i assume you live in a warm place LOL
[ONE Original Android Development] thedoctor.gz:
The problem is the reboot not the pts. Anyway fresh beer for everybody :D

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
Guys,

if you wonder where the kernel updates this week are... they are a bit delayed.

I am still finalizing a new feature (touch key control) which allows you to light the touch keys only up when you press them, and not when you touch the screen.

You will be able to configure whether it should behave normal, only enabling the touchkey lights when you touch the screen, or whether they will be hard off.

And this requires some more testing...

Andi
[ONE Original Android Development] abhibnl:
Awesome! I was wondering why there was no new post about it and i thought you completely forgot about it. :P But now i know you didn't, Great work Andi! :fingers-crossed:
[ONE Original Android Development] magnamentis:
hi andi,

i probably miss the point but the light would be to find the keys in the dark or where exactly they are situated so what sense will it make if they are coming on after i touch them, that's exactly when the light is not needed anymore LOL, just "enlighten" me which point i missed or misunderstood if you find the time :)

everything is working great as usual, still worth to mention once in a while so i took the opportunity, thanks for all :good:
[ONE Original Android Development] andip71:
It is more for the people that like to read in the dark for instance.

Scrolling through a long text, and they do not want to have the touch key lights switching on just when they scroll down a bit.

It is not that prominent on the OPO, as the touchkey lights are quite dim here. On the S3 it was a bigger issue (and it is on the S5, so will address it there too).

As it is fully configurable, everyone can use according to his/her taste :)

Andi
[ONE Original Android Development] magnamentis:
well, that explains it :) thanks for that one. since i'm already on it again, i will have the "2" within the next few days, do you have the intention to take that path alos? i'm just curious because it would safe me the hassle to seek out a good kernel for it LOL ;)
[ONE Original Android Development] twowheeler:
Dude, whether or not I will use it. It's awesome that you're putting so much work in.

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] andip71:
Clear maybe, I don't have an invite so far.

But I consider the oneplus two more than any other phone, yes.

Andi
[ONE Original Android Development] magnamentis:
great, i think i buy it anyway but then rom and kernel availability are as well part of my evaluation processes :) since it will be dual sim the more interesting it is, getting tired of updating 6-7 devices LOL
[ONE Original Android Development] andip71:
New betas for cm12.1 and cm12s

Hi all,

finally found some time to implement a little new feature - touchkey led control.

So now you can configure to not enable the touchkey leds when you do not touch them (but only touch the screen). On top you can, hard from kernel side, disable touchkey leds in general. Or - you leave it as it is defined by the used rom.

Note, you need latest Boeffla-Config 2.1.90 for this new functionality to be configurable.

CM12.1 -- Version

4.1-beta13

28.07.2015

Implemented Boeffla touchkey LED control (you need Boeffla Config app 2.1.90 or higher for this)

Updated with latest official CM kernel commits as of 24.07.15

Ramdisk updated to official CM12.1 version of 28.07.15

Kernel build process now able to use ccache

CM12s/COS12 -- Version

3.1-beta8

28.07.2015

Implemented Boeffla touchkey LED control (you need Boeffla Config app 2.1.90 or higher for this)

Kernel build process now able to use ccache

Enjoy

Andi
[ONE Original Android Development] karthickkatta:
[MENTION=947981]Lord Boeffla[/MENTION] i found a bug in led control ...the light disables when touching the screen screen is fine ..the bug is when i touch the key the light emits and immediately keep on touching the screen the led wont off ..if i release my hand the led offs
[ONE Original Android Development] andip71:
It should just take "longer" for the LED to go off, but it should go off.

At least I could not reproduce what you report here.

The thing is:

The kernel triggers to switch the LED on now (in your selected mode).

However, still the rom controls when it should go off. And every time you touch the screen, the LED timer in the rom gets restarted.

There would be only one way to change this: Let the kernel control the LED completely. But this is not what I intend, as I cannot make the LED duration then controllable via the rom still. And this is something I do not want to lose.

(unfortunately a long time ago CM team decided to put touchkey LED control into the rom and take it out from the kernel, so we have to live with that "hybrid" now).

So, it is how it is :)

Edit: Maybe I should also allow the kernel to take over full control in a future version of the touchkey led driver. I already have an idea... :)

Andi
[ONE Original Android Development] Stroky:
Thanks Andi for that great update!

Everything works fine here in Hamburg :)
[ONE Original Android Development] thedoctor.gz:
I've just updated the Kernel and the app and everything works fine! Thanks

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] Clark789:
Hi Andi,

the new beta works perfect for me! Thanks a lot!! I appreciate the new feature very much, because i'm reading with my OPO and in the dark the LEDs are a little bit annoying... ;)

Regards from Hamburg as well...

Clark
[ONE Original Android Development] karthickkatta:
[MENTION=947981]Lord Boeffla[/MENTION] so its not a bug ?

please watch this video i spent soo much time uploading .. https://www.youtube.com/watch?v=UzrkOxPdQFM&feature=youtu.be
[ONE Original Android Development] andip71:
I watched it.

Yes, it is designed that way.

As I explained: I leave the control to switch off the LED still to the rom, so the configured timeout there is still valid.

Side effect is: If you do not let the LED go off first and keep on touching the screen, then it will not go off ever. But is this a valid scenario or more a synthetic one? To me it is more a synthetic one.

So, it is not a bug, it is how it is designed at the moment.

As said: I could give the full control to the kernel too, but then the settings in the rom are not having any effect anymore. Which is not what I like.

So I consider a more enhanced version where people even can give full control of it to the kernel (accepting what they configure in the rom is useless) in some future. Not sure if it is really worth doing that though :) Let's see.

Andi
[ONE Original Android Development] andip71:
Ok, it is already pretty much done. Hehe.

Maybe something for next week...

Andi
[ONE Original Android Development] karthickkatta:
Wow awesome ..I love ur kernel ..
[ONE Original Android Development] suaverc118:
Where in the new app can I try the new feature? Display? Not sure what to do

---------- Post added at 12:04 PM ---------- Previous post was at 11:56 AM ----------

Never mind. Found it
[ONE Original Android Development] twowheeler:
just used the load and flash option in the app. Felt kind of weird not to see it go into recovery. OCD me starts to wonder if it did everything correctly that way. But it did, that new option is great!

I love how the leds stay on as long as you keep touching the screen, but go off after a while and only turn on on touch again. Great work again!
[ONE Original Android Development] fmc000:
Post #5440 in this thread.
[ONE Original Android Development] mp3deviant721:
The new feature works pretty good [MENTION=947981]Lord Boeffla[/MENTION]. Even on an outdated ROM. Lol. Thanks a ton!

OnePlus One | Euphoria OS x Boeffla edition™
[ONE Original Android Development] andip71:
Thanks, but should I tell you what?

The load&flash option is already in the app since version 1.0, around 18 months ago :)

Just to mention, hehe.

Andi
[ONE Original Android Development] abhibnl:
Andi i'm also experiencing the same scenario and it's too annoying. What is more annoying is that even after i have turned the switch off in boeffla app to "touch led when touch screen", the behaviour still retians. It stays always ON. Even after a reboot, the behaviour is the same. As of now, i'm forced to completely disable touch led. Would you recomment to roll back to the previous version or would you like us to wait for the next version with complete kernel handling of touch led? BTW i'm using boeffla kernel slim version with latest slimsaber.

Sent from OnePlus One
[ONE Original Android Development] andip71:
What exactly is your issue?

Can you describe?

On my side, everything works as it should !

Maybe once mor a f***ing incompatibility with slim?

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

I bought the donation app and all went fine but I have a question.

1. I create a new Profile with custom governor tunables (donation...)

2. Export the profile

3. Free user imports profile

Does my changes stick in the free version?

thanks in advance.
[ONE Original Android Development] andip71:
Yes, the free version can import your profile with custom tunables and they will get applied.

Just, they cannot be changed anymore in the free version, that is all.

Andi
[ONE Original Android Development] S1ay3r666:
Thats what i thought but i wanted to be 100% sure.

Thanks
[ONE Original Android Development] andip71:
Yes, it is like that.

I do not want to restrict users working with the normal version too much.

And I am not getting rich anyways by my apps :)

But still I think, the users appreciating the work and giving a donation (which is for sure not simple for some too, nobody has money over) should get some small appreciation back by me - by giving them some more comfort features.

Andi
[ONE Original Android Development] S1ay3r666:
Another Question about the Hotplug:

I want to configure if the screen is on 4 cores should be running all the time but at screen off only 1 core should run.

I configured 4 cores min but it looks like 4 cores are running all the time (screen on/off) or am I wrong?

I really appreciate your help!
[ONE Original Android Development] andip71:
The hotplug modes are not supposed to be screen status dependent. So if you put 4 cores min active, 4 cores are switched on always, regardless if screen is on or off.

Only way you can achieve that is by using a 3rd party app like tasker to switch between two profiles based on screen status.

As the savings are neglectable, I would not consider even trying it.

But of course, feel free :)

Andi
[ONE Original Android Development] molonad:
I must say mistr Lord Boeffla that this new feature sound very interesting! Great job, you are for me Best dev ever, only thing that I miss is some other build, for example uber or sabermod or linaro etc, but zanezam have taken control of these builds ☺ but maybe is it only placebo effect, i once asked you if other toolchain can make difference, you didn't answer me, can you tell me your opinion about it? Thank you ☺
[ONE Original Android Development] magnamentis:
funny how everyone who wants something starts with a huge compliment. this era ended with the new greek government early this year LOL ( JK )
[ONE Original Android Development] andip71:
Hi !

Well, my opinions on non-stock toolchains are mixed.

Whilst they can give some minor (or major) speed improvements, they always come with a certain risk as well.

And as my kernel aims for superb stability (this is why I do not put all the fancy latest-edge development in all the time), I decided to stick to the correct, corresponding toolchain.

Not saying, recompiling with other toolchains also creates a hell lot of work which I could not do anymore.

Fortunately ZaneZam does always a 1:1 compile of my kernels with other toolchains, so everyone can try and see what fits best.

On another topic:

The enhanced touch key light driver is already complete now, incl. a new app that enables the additional controls. See attached screenshot for a quick teaser :D

Now, the kernel can be configured to a specific light timeout to define after how many seconds the touch key lights should be off again. When this is done, the rom has no control over it anymore, and only the kernel takes care of it. This can only be activated (which is logical) in the special mode when touches on the touch screen should not activate the LEDs anymore.

Andi
[ONE Original Android Development] molonad:
No no, i only start like this in this threat and my favourite rom thread ☺ only for devs whose i think deserve it ☺ and i was just wondering about it, i Dont want to mistr boeffla do it ☺ iam not like others

---------- Post added at 05:12 PM ---------- Previous post was at 05:12 PM ----------

I just want to know his opinion about it.
[ONE Original Android Development] abhibnl:
I described my issue in the previous post already. Even after reverting the switch to activate touch LEDs only when touching them(that means the default behavior, that means i have turned the switch off so that touch LEDs activate even while touching screen) but the phone still keeps LEDs active for long time(like 10 seconds). It may very well be an incompatibility with slim but i highly doubt it. anyways, i'll wait for the next version with the enhanced driver.
[ONE Original Android Development] andip71:
Screenshot of your switches please?

And what the expected result would be (in your opinion) and how it behaves for you?

It is still not 100% clear to me.

Andi
[ONE Original Android Development] abhibnl:
Andi i'll post screenshots in 45-60 minutes possibly. As of now i have fully disabled Touch LED's. Let me explain the issue to you again,

1. First i turned on "Touch LED when touch screen" in boeffla-config. The buttons only lit when i touched the screen but when i touched the buttons, they remain lit for almost 10 secs until i turned off my screen.

2.Now i've turned off the "Touch LED when touch screen" in boeffla-config. But the phone still acts like that option is ON. The touch LEDs remain lit for multiple seconds while in the ROM i've set the timeout to 1 second.

3. Rebooted and the behavior is still the same.

4. Had to disable touch LEDs completely for now.

Let me know if it's still not clear.
[ONE Original Android Development] infatality:
[MENTION=947981]Lord Boeffla[/MENTION] is it normal for the device not to enter deep sleep when charging?
[ONE Original Android Development] Mrwargod:
Yes it is.
[ONE Original Android Development] andip71:
Yes, always was like that.

Andi
[ONE Original Android Development] infatality:
Thanks! I thought I did something wrong.. As I just came over from n5.. And when I'm on n5 the device does deep sleep when charging. [emoji12]
[ONE Original Android Development] andip71:
Possible on N5, yes.

But deep sleep is not required during charging, so it does not matter.

Andi
[ONE Original Android Development] anshumandash:
Not sure how you are getting deep sleep while charging. It never happened in any previous nexus phones. I feel it doesn't happen during charging of any phone as the phone needs to be awake while charging. I still have my n4 and it doesn't deep asleep while charging. Haven't used n5, but it's good if the phone behaves that way.
[ONE Original Android Development] Marek McFly:
Hey guys,

a few days ago I updated the kernel (from 'beta7' to 'beta8') and it seemd that the akkudrain increased, even though I used the same kernel-setting.

Till now I was using the old beta7 to get some akku-stats, and changed it to version beta8.

But could it be at all, that a kernel update de-/increases the akkudrain?
[ONE Original Android Development] andip71:
Not very likely. 99% of the time it is an app or process consuming a good amount of battery.

Install BetterBatteryStats and check for partial wakelocks after a while.

Then check for kernel wakelocks too.

In theory, a ramdisk update could cause some battery drain changes. And yes, I update the ramdisk quite regularly. But it is extremely unlikely.

Andi
[ONE Original Android Development] magnamentis:
no drain here, so it must be a coincidence, something on your side or due to one of the many recent GPS updates.

be assured it's not kernel related, otherwise everyone would encounter the same issue.
[ONE Original Android Development] pugsang:
[MENTION=947981]Lord Boeffla[/MENTION]

So whats the deal with CM12s - Test:	3.1-beta8 and touchkey driver 1.1.0? Is it not included at the kernel? Because in my opo this option is greyed out
[ONE Original Android Development] andip71:
Correct.

The kernel with the new driver is not yet out. When it is out, you can use the slider.

Andi
[ONE Original Android Development] pugsang:
OK thought so from your previous posts but then again I was afraid that I had missed something although I have the pro app version. Thanks for clarifying
[ONE Original Android Development] andip71:
The current OnePlus kernels have version 1.0.0 in, but the next kernels will have 1.1.0 of the driver in.

Then these side effects which were discussed a few days ago on the touchkey lights can be resolved.

Andi
[ONE Original Android Development] andip71:
New betas for cm12.1 and cm12s

Hi,

before the weekend, a small preset for you: new CM12s/COS12 and CM12.1 beta kernels !!!

Don't forget to update your Boeffla-Config to latest version 2.1.92 !!

CM12/COS12 -- Version

3.1-beta9

31.07.2015

Updated Boeffla touchkey LED control to version 1.1.0 (you need Boeffla Config app 2.1.92 or higher for this)

Configuration options:

- current standard settings: LED enabled when using touchscreen or the touchkeys (time controlled by the rom)

- option to enable only LED when touchkeys are used (time controlled by rom, set time to 0 in Boeffla-Config,

special effect: LED will stay on when you use the touchscreen while the LED is still enabled)

- option to enable only LED when touchkeys are used (fully controlled by the kernel, set time in Boeffla-Config)

- option to disable LED always (controlled by the kernel)

This allows the kernel now to take over full control over the LED (when you configure a LED timeout), to avoid the known side-effects.

Internal build script enhancements

CM12.1 -- Version

4.1-beta14

31.07.2015

Updated Boeffla touchkey LED control to version 1.1.0 (you need Boeffla Config app 2.1.92 or higher for this)

Configuration options:

- current standard settings: LED enabled when using touchscreen or the touchkeys (time controlled by the rom)

- option to enable only LED when touchkeys are used (time controlled by rom, set time to 0 in Boeffla-Config,

special effect: LED will stay on when you use the touchscreen while the LED is still enabled)

- option to enable only LED when touchkeys are used (fully controlled by the kernel, set time in Boeffla-Config)

- option to disable LED always (controlled by the kernel)

This allows the kernel now to take over full control over the LED (when you configure a LED timeout), to avoid the known side-effects.

Ramdisk updated to official CM12.1 version of 31.07.15

Internal build script enhancements

Enjoy

Andi
[ONE Original Android Development] Fenvarien:
The new LED control is working great! Thanks for your work and have a nice and relaxing weekend. :)
[ONE Original Android Development] Orphee:
Hi!

I felt the same issue with beta8, did not change anything else... 4%h idle... I just reverted to beta 7 to compare, I will post here the result tomorrow.

Nothing more in BetterBatteryStats than usual.

Thank you
[ONE Original Android Development] andip71:
You should not revert back to beta7 but step up to beta9 :D

Andi
[ONE Original Android Development] AbhishekS:
Sorry for OT but because Boeffla has modems listed on his website I am asking this question.

I was on KitKat. Flashed CM12.1 nightly today and the network keeps dropping. Which modem/firmware or any other file shall I flash?