yashsingh1/xdaforums huggingface dataset:
[OnePlus X Original Android Development] CertifiedBlyndGuy:
1. After reboot.

2. I didn't have this enabled, but after enabling it settings stuck... weird (should have had the opposite affect)

I have no idea what it could've been.

BTW, when compiling from source for NetHunter support I only had to apply one patch and modify the defconfig... Your build script handled everything else. Thanks for making such a great kernel and providing clean code
[OnePlus X Original Android Development] andip71:
Yep, this does not make any sense, so let's investigate it.

Can you please create a debug info file in Boeffla-Config (it is last poin in Action menu) and send it to support@boeffla-kernel.de

I want to see what happens, please untick the overwrite option again and reboot before you create the file.

Thanks

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Will do

---------- Post added at 06:02 AM ---------- Previous post was at 05:44 AM ----------

Found the issue:

>[20160310_13:45:14.580588]@1 elevator: switch to fiops failed due to Boeffla hard value set to deadline

But why would that be occurring?
[OnePlus X Original Android Development] andip71:
Ok, bug confirmed.

I have not yet put the lock function in which can handle external sd cards (was taking the code from my OPO repo, and the OPO does not have it).

The fix is existing already in my S5 repo, will pick from there and it will be fixed with the next kernel update (which I might release soon due to that).

Thanks for the help in nailing that down

Andi
[OnePlus X Original Android Development] andip71:
Kernel update

Hi all,

new kernel for you:

Version

4.0-beta8

10.03.2016

Note: This kernel only runs on Oxygen OS 2.2.0-x for the OnePlus X - nothing else !!!

Note: You need at least version 2.2.35 of Boeffla-Config V2 to allow all functionalities to be available

Fix: Scheduler not always sticky is resolved

Change: Cleanup of ramdisk after removing legacy files

Enjoy

Andi
[OnePlus X Original Android Development] rockuppl:
Yoppp!! Smooth ..... :D

Literally counting days as of when Official CM nightly will come out and so your Kernel!! 0_o

Bored of Oxygen !!!(Good battery, low on functionality) Cm13(high on functionalities but low on battery)
[OnePlus X Original Android Development] andip71:
When it gets official, it will not take me long.

I prepared already my personal alpha which I have in testing :D

Andi
[OnePlus X Original Android Development] faber.cpu:
I'm testing your kernel (beta8) and all is good, speed, battery etc.

But have some issue with Wifi when I have Wifi Off on Android sleep mode.

It seams than Wifi have big problems to wake up. Sometimes it shows wifi icon ok with full range but no data transfer, sometimes wifi turn off after some time.

When I set Wifi always ON then all is ok.
[OnePlus X Original Android Development] andip71:
Cannot comment, I never used this setting as it does not make sense for my usage pattern.

But as this depends on so many factors, starting from wifi router hardware, network strengths etc, I cannot provide any helpful for you.

Andi
[OnePlus X Original Android Development] faber.cpu:
yeah, today I work on other Wifi and its ok, so router settings issue, router is the same model but have other settings. Will check this.
[OnePlus X Original Android Development] animesh1558:
came back to OOS from CM12.1 & now my mobile charges at only 1000mAh(earlier it was 1450mAh). Even after flashing this kernel & increasing the charging value in the app its still the same. Has my battery degraded?? i did a clean install (except internal storage wipe)
[OnePlus X Original Android Development] andip71:
Quite unlikely, as the OPX is still a brand new device.

It can be dirt in the plugs or something with the cable. No clue to say that from here, sorry.

Andi
[OnePlus X Original Android Development] icharlesi:
Hello, as for new ppl in here with this device (im one of these) I would like to have more detailed information about the governors, sehdules I/O and that kind of characteristics this beutiful kernel alow us to customize. Could you tell me where I could check what specifically each governor do? Just to find a good balance between performance and power saving.

Also as a suggestion I would propose a post in where the experienced ppl in this matter, would post their stables customization and purpose for it, just to have a better reference. I would be glad of opening it if you find it a good idea.

See you!
[OnePlus X Original Android Development] jonrodz:
I/O schedulers: http://androidmodguide.blogspot.com/p/io-schedulers.html?m=1

CPU/GPU governors: http://androidmodguide.blogspot.com/p/blog-page.html?m=1
[OnePlus X Original Android Development] Naman Bhalla:
There is a profiles thread existing in the general section. ?
[OnePlus X Original Android Development] icharlesi:
Oh really I must be blind did not see it. anyways thx
[OnePlus X Original Android Development] Vennesch:
Boeffla, could you please look into this (disable green led when battery is full)? http://xdaforums.com/showthread.php?t=3333792 I would be very grateful!
[OnePlus X Original Android Development] andip71:
The kernel cannot control that as it cannot distinguish if something is a battery full led or coming from something else.

But you can put led brightness to 1 in my kernel, which would make both the red charging light as well as the green battery full light disappear.

Blinking / fading notifications would still work fine.

That is the workaround you can have.

Andi
[OnePlus X Original Android Development] Vennesch:
Works! You are a hero!
[OnePlus X Original Android Development] chinmai560621:
......mmm

I'm a heavy gamer and my opx drained like 7% battery each game of FIFA 16 and the phone used to overheat upto 45 degrees on 1-2 games itself. The boeffla kernel too overheated until I kept the settings proper. It helps a lot and keeps the phone below 36 degrees while gaming which is very very very good. The phone is very stable now though I find battery drains. I would like to share my kernel profile as I hope it might be useful to many here who face problems with high battery loss and overheating.

At idle and normal usage state :

CPU Governor: zzmoove

Governor Profile: battery yank extreme

CPU Max freq. : 1574mHz

Hotplug profile: zzmoove default max 2 cores

Tweaks: none

At gaming state:

CPU governor: zzmoove

Governor Profile: game

CPU max freq. : 2572mHz

Hotplug profile: zzmoove default

Tweaks: mattiadj

Permanent:

GPU minimum: 27mHz

Vibration: lv15

Voltage: Undervolt medium

Charge rate: 1600A(plugpoint) - not of much use

Also akind request to the dev. the snapdragon 801 chipset is capable of fastcharging. It would also be useful if you can add the feature to the kernel(I really don't know if it can be added). The RAM usage stats is not working also.
[OnePlus X Original Android Development] andip71:
I do not think this can be added.

Whilst the SoC is able to do it, and the code is enabled in the kernel, no dev ever was able (since the OnePlus One already, and here we have a huge developer community) to enable more than is possible now.

I would be happy to stand corrected, but pretty sure this will not gonna happen.

Andi
[OnePlus X Original Android Development] andip71:
No, it is just I was able to tweak the non-blinking LED control

And the battery LED is the first thing I switch off in all roms usually, so here I had to do something as OOS does not support that :D

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Could this be merged possibly? It isn't QC but it forces fast charging

https://github.com/Snuzzo/funky_kernel/commit/66ba8328ca1318a7282658014cac47585017077d

Oh and could a frequency step down (168mhz I believe) be added as well? I think it may help with battery life on standby
[OnePlus X Original Android Development] nasif69:
Which I/O scheduler you are using? ROW or FIOPS? Readahead buffer size?
[OnePlus X Original Android Development] andip71:
I doubt this commit has any effect on the opx. I will check in code in the next days to prove it.

I think there is no more to achieve than what we have already.

And down cpu step = no.

In the past with other phones that was never a good idea.

Thanks for the ideas anyways. But I really put only in what convinces me.

Andi
[OnePlus X Original Android Development] chinmai560621:
I use FIOPS and 1024KB during normal usage. Zen while gaming. I've been able to do games well with 1024KB so it aint bad at all. There is also stability.
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Readahead on internal is somrwhat subjective. For daily use 128kb is enough. External storage seems to benefit far more from it
[OnePlus X Original Android Development] chinmai560621:
Are there any chances for the commit to work?
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Give him some time to look at it. I doubt it, but I will keep looking for commits like these
[OnePlus X Original Android Development] andip71:
I thought I said I will look into it over the next days?

I usually do not work at all on kernel stuff during weekends. This time is fully dedicated to real life and my wife.

But as I said: Chances are almost zero when you ask me, as I said already.

Just trying to enable a functionality that is not implemented makes zero sense.

But I also said, I need to confirm that in code first.

But not with priority, I do not need faster charging than it is now already (also not good for battery).

Andi
[OnePlus X Original Android Development] andip71:
As I said already, this option would have

zero effect

, see screenshot.

It is not known anywhere in OPX code.

And it would be automatically thrown out again from the defconfig, as it is not registered at all.

So, my first assumption was completely correct..

Andi
[OnePlus X Original Android Development] chinmai560621:
Tysm!
[OnePlus X Original Android Development] v1zca1n0:
Lord Boeffla I was thinking in flash a CM13 ROM in my OnePlus X (for example Purity or Exodus) Any chance you develop a Kernel for this? Will be a pity lose your kernel because don´t match with those ROMS... Thank you
[OnePlus X Original Android Development] ZackoFF96:
I thought Lord Boeffla made it clear in a lot of posts that he'll only develeop kernel for CM only when CM for Onyx has started having official builds?

although he said that he already developed alpha in case of official CM builds.

CMIIW.
[OnePlus X Original Android Development] andip71:
Alpha Version is ready, but I want to ship it only when the rom becomes official for many reasons.

But to answer the question: yes, there will be a kernel for cm13 one day.

Andi
[OnePlus X Original Android Development] v1zca1n0:
Clear as always. Thank you Lord Baeffla for your work and answer
[OnePlus X Original Android Development] Vennesch:
Is there anything you could do against the echo problem? I think the standard in call volume levels are very high even on the lowest. Thanks in advance!
[OnePlus X Original Android Development] CertifiedBlyndGuy:
So recently I had an idea,

Zzmoove is a great governer. You can alter it to work any way you want it to work, but options are always great so long as they're practical.

I remember back when I used an HTC DLX with the SmartassV2 governer and how great battery life and performance was (the former being a huge issue with the DLX), and was curious about whether or not it could be implemented in Boeffla.

I've also been hearing that ElementalX is pretty good as well.

Thanks,

RJ
[OnePlus X Original Android Development] andip71:
No. This is a rom or hardware issue.

I see no way to do something in kernel.

Andi
[OnePlus X Original Android Development] andip71:
I had smartassv2 in my Galaxy S3 kernels.

That time the governor worked fine on a 3.0 kernel version with hotplugging logic in the governor.

For the Qualcomm area and 3.4 kernels (or higher) it does not seem to be a good fit.

What was the kernel version in your HTC DLX, and which cpu was used in that device?

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I believe it was 3.4 and the processor was a Snapdragon 400. I think Zarboz may have made the kernel, but I can't check his kernel source as he abandoned ship recently. I haven't had the device for over a year now so it may have very well been 3.0 but wasn't 3.4 sort of set as a basis with 4.1+?

Thanks,

RJ
[OnePlus X Original Android Development] andip71:
Main reason behind my question was: I cannot implement the S3 version of SmartAssV2 as this contains hotplugging logic for the S3 Exynos CPU, i.e. it is not ready for our phone.

And I wonder whether anyone has ported it to Qualcomm with external hotplugging implementation. If so, I could cherry-pick it and give it a try.

But if not, I don't think the work to port it is justifyable.

Andi
[OnePlus X Original Android Development] andip71:
Hi all,

quick copy and paste from Twitter:

Boeffla-Universe... OP2 and OPX closed alpha testing will start soon. Stay tuned here to react when I open the slot to apply, 10 people each.

Source:

https://twitter.com/andip71/status/710127523703738368

So, stay tuned.

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I'll be sure to get on that :)
[OnePlus X Original Android Development] andip71:
*** CM13 closed alpha test for OPX - apply by mail to alphatest-opx@boeffla-kernel.de. NOW :) Mail will close down soon again. ***

Hurry up.

Andi

We are full now, many thanks for applying and the interest.

All others: Next time maybe :)

Andi
[OnePlus X Original Android Development] ashwin007:
Hey!

I'll be rolling out nightlies within a couple of days , so hope many would taste this very soon :P
[OnePlus X Original Android Development] andip71:
That is really good news.

All testers that apply to test my kernel are already adviced to install your rom only.

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Damn it. Where I'm at there's a block on Twitter. Maybe next time :)

Oh wait... Never mind. That was just a source

---------- Post added at 06:37 PM ---------- Previous post was at 06:33 PM ----------

Will we see the code on GitHub soon?
[OnePlus X Original Android Development] andip71:
Code will only be made public once the kernel is released officially for public.

Check your pm too.

Andi
[OnePlus X Original Android Development] rockuppl:
Edit- Deleted !!! [MENTION=7054841]Boeffla[/MENTION]

*Extremely Sorry

*Appreciate your Help and your Work!!!
[OnePlus X Original Android Development] andip71:
First mistake: I said no feedback in thread!!

People will get confused. I really am not happy you did not follow the instructions. Please stick to the rules.

And regarding your error - not kernel related. In the thread you see you cannot do a clean install of the rom. You need the prev rom version first for installation and then dirty flash latest version over.

But
[OnePlus X Original Android Development] fatino:
Hey Lord Boeffla,

I think my problem is kind of related to the kernel but I'm not sure. I ask here because it would be hard for me to find the answer on different forum as it's kinda uncommon.

I succesfully mounted NFS share using your kernel with enabled module. BUT I can only access that share through command line in terminal from root. Normal user doesn't see mounts.

http://android.stackexchange.com/questions/51106/mounting-nfs-cifs-etc-on-android-4-3

I found that they changed that in Android 4.2 (I used to mount samba in 1.5/2.1). Is there any way for me to access this NFS share from my normal Android apps? I can't ask you to patch your kernel. As you said it's not something you do, but can't hurt to ask anyway :P
[OnePlus X Original Android Development] andip71:
Disable mount namespace separation in supersu settings, reboot.. Then mount your nfs volume to a sub folder in mnt folder, not on sdcard.

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Did you mount it with busybox?

Run this with Termux:

busybox mount -t nfs -o nolock,ro 192.WhateverYourIPis /path/to/desired/directory

---------- Post added at 10:13 PM ---------- Previous post was at 10:04 PM ----------

There. Fixed it for you
[OnePlus X Original Android Development] fatino:
yes I did. Im using nfs4 btw. Now I could copy the file using Total Commander, it prompted some remounts but it copied the file. I can't seem to open the files though. Now root apps as Total Commander see files but can't really open them.
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Try running "chmod 755" in the directory used to mount it
[OnePlus X Original Android Development] fatino:
Tried it, stayed the same.
[OnePlus X Original Android Development] CertifiedBlyndGuy:
My last guess is SELinux

setenforce Enforcing

Should do it
[OnePlus X Original Android Development] fatino:
hehehe I forgot that it changed back to enforcing. I changed to permissive and it works. :D:D

EDIT: Videos won't stream :/ but pictures work. Gotta try it with openvpn :P
[OnePlus X Original Android Development] andip71:
Yes, forgot to say... also I am using CIFS from time to time, so I also noticed selinux must be set to permissive.

In fact, the following steps are required:

- if you use supersu, configure it to not enable mount namespace separation

- switch selinux to permissive (you can do that permantly in Boeffla-Config settings menu, the checkbox on the first overview page is not supposed to be sticky!)

- mount the share under /mnt/something... not anywhere else

Then over CIFS all was working for me, even streaming of videos etc.

Andi
[OnePlus X Original Android Development] andip71:
*** CM13 alpha testers ***

All CM13 alpha testers should make sure they follow me on Twitter (https://twitter.com/andip71) to receive constant updates on new alpha versions etc.

Please note, I am using exclusively Twitter for alpha communication as I want to avoid I have to post the same message over and over again in threads, even confusing people there which are not part of the closed alpha testing.

Thanks for understanding.

Andi
[OnePlus X Original Android Development] reph05:
Hi [MENTION=947981]Lord Boeffla[/MENTION],

I just came to X from other device. I am excited to see someone is making a real good progress here. Although I haven't flash this kernel, from user feedback and changelogs it seems like most of the thing works like it should. May I know what holds you from declaring this kernel as a stable release? Just out of curiousity. :)

- CH -
[OnePlus X Original Android Development] andip71:
Yes, I think, it works pretty well, no major or even medium bugs.

What holds me back, hm... basically nothing.

Maybe I will declare it stable next week.

Thanks

Andi
[OnePlus X Original Android Development] Addys123:
How do I flash it if I am on blu spark kernel? Should I flash the stock kernel and then the boeffla kernel?
[OnePlus X Original Android Development] andip71:
You can just flash over.

But remove all ukm stuff when bluespark uses it (have no clue).

Also you might need to find and rename mpdecision binary again when Boeffla-Config complains about it.

But definitely no need to flash stock kernel first.

Maybe others can comment too, who made this move already (I never had another kernel running myself).

Andi
[OnePlus X Original Android Development] rockuppl:
Clear cache, dalvik.... Then flash over... You are good to go :)
[OnePlus X Original Android Development] ZackoFF96:
I don't know if the newer kernel also includes mpdecision or not. but this was my solution when i flashed beta 2

and this is Lord Boeffla's updated mpdecision.zip
[OnePlus X Original Android Development] Bitman64:
As told in blu_spark thread installation of that kernel changes an awful lot scripts and other tings, i recommend building the installation up from the beginning. Flash latest full sytem (OOS) zip followed by the updates. Then flash SuperSU and boeffla-kernel. I did and i am very pleased by the result. Thanks to Lord-boeffla.

Greetz B.
[OnePlus X Original Android Development] CertifiedBlyndGuy:
[MENTION=947981]Lord Boeffla[/MENTION]

I noticed that Ashwin synced [MENTION=3873953]eng.stk[/MENTION]'s implementation of F2FS a while back and was wondering what the consequences of implementing it here would be. Obviously using it for /data would be pretty dumb due to data loss, but as /cache I wouldn't believe that there isn't anything that would be detrimental. I understand if you won't, but I think that it is something to consider. Its matured a lot.

Besides that, on OxygenOS you might as well consider the release stable. No bugs on that side of things. Alpha2 is working flawlessly as well.

As usual, thanks for the great work,

RJ
[OnePlus X Original Android Development] Tiongkia:
Thanks Lord Boeffla for the wonderful Kernel.

I was on blu_sp Kernel and moved to this Kernel.

I just wipe cache and dalvik cache, flashed this Kernel. Everything is great. No issues.

After reading the thread, there may be potential issues. So i flashed the full oss rom then ota then whatever stuff and Boeffla Kernel. Feels the same as 1st method. Just sharing experience.
[OnePlus X Original Android Development] Bitman64:
That was the way i went first. But i had reboots (once or twice a day). So i did it the way i mentioned above and until now i haven't had a reboot. Also temperature didn't reached that high amount as it did when kernel was flashed without reflashing rom.

Greetz B.
[OnePlus X Original Android Development] andip71:
Well, people that know me know, I am a big opponent of F2FS.

I personally think it is completely useless for daily usage, but probably adding some risk for data consistency. Ok, you get some higher benchmark, but who cares about that?

Also reading about issues when converting back or forth many times.

As with my previous kernels, I will not implement F2FS ever in my kernel as long as CM does not do it officially. If they do, I follow. But I would never implement it myself.

So, no consequences, but not worth it.

I know it is my very personal opinion and many have other opinions. I stopped discussing that consequently.

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Appreciate the explanation. By chance, did you get that log I sent earlier? I had a look at it myself and everything is enabled during startup however something then cancels out their activation. I just tested it with the NFS, Xbox, and Ethernet module.
[OnePlus X Original Android Development] andip71:
Hm. Did I miss something?

What is the problem and where did you send logs to?

If I missed it, apologize.

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Its with Alpha 2. Kernel modules are deactivated on reboot (NFS, the controller module, CIFS, ethernet, etc...) and whats weird is they're just overwritten as if they were specified by Boeffla Config. I sent a report with an attachment to support@boeffla-kernel.de (the email instructed to send to within Boeffla Config).
[OnePlus X Original Android Development] andip71:
Need to find that mail again. However cannot remember it. Will look tomorrow.

But please, as made clear in the alpha testing instructions, no cm13 alpha testing related stuff in this thread.

It will confuse people, even I was confused as you could see.

Thanks for taking care of this.

Edit: Yes, not a single module in CM13 kernel can load correctly. I will look into that.

Edit2: It seems to be a broken toybox coming with the rom. I can work around that in an alpha3 version, no problem. But his would not happen in a final official product for sure.

Edit3: Workaround implemented temporarily in alpha, look at Twitter for announcement of new alphas.

Andi
[OnePlus X Original Android Development] andip71:
Hi all,

latest beta turned out to be stable and fine, so it is time to release it as new stable release finally.

Version

4.0 stable

22.03.2016

Note: This kernel only runs on Oxygen OS 2.2.0-x for the OnePlus X - nothing else !!!

Note: You need at least version 2.2.35 of Boeffla-Config V2 to allow all functionalities to be available

Same version as beta8

Enjoy

Andi