yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] Nikorasu:
Thanks, ATM I'm using it to change my scheduler to SIO and use the Boeffla sound engine. Most of what's in the Boeffla config are like airplane controls to me.

Would be nice if someone comes up with a guide with recommended settings.
[Galaxy Note 10.1 Android Development] kalashenicof:
It this capatible with GT-N8013?
[Galaxy Note 10.1 Android Development] GodSlayer:
Finally a kernel for the N8010 and not the N8013. I know they are the same, but still :P
[Galaxy Note 10.1 Android Development] Nightf0x_007:
hope to have n8000 version of this kernel
[Galaxy Note 10.1 Android Development] dbolivar:
WOW, great to see you here with a kernel for our device! I'm aware of your work for the Galaxy SIII. Gonna test the kernel NOW! Thanks!!
[Galaxy Note 10.1 Android Development] sbreen94:
Looking good boss!
[Galaxy Note 10.1 Android Development] andip71:
Honestly, I do not know. The 8013 seems to be the US variant of the 8010. Usually, kernels of US vs. European variants cannot be exchanged.

But I guess nothing can go wrong if you give it a try (do a nandroid backup first, so you have the current kernel safe).

If you tried it, please report back.

Only if you guys put some buck together and buy me a n8000. Seriously.

I have a golden rule of thumb: I only develop for devices I have myself, as this is the only way to do proper testing and ensure quality.
[Galaxy Note 10.1 Android Development] andip71:
Hi,

well, it is a wide topic. That is why I recommended to head over to the S3 thread and search a little bit through it.

Also there is plenty (partially outdated) information on the kernel homepage under configuration as well.

However, my personal configuration currently is:

- governor zzmoove

- governor profile zzmoove -battery yank

- scheduler internal to row

- scheduler external to bfq

- read ahead buffer internal 512

- cpu idle mode to aftr+lpa

- boeffla-sound of course, but this is very much subjective

- touch boost down to 400 (to save some juice)

Andi
[Galaxy Note 10.1 Android Development] GodSlayer:
Actually, about the europe and US variants - they appear to be absolutely identical. I personally purchased mine in Germany (obviously the N8010 europe variant), but I've been using a ROM and a kernel for the N8013 (US Variant) for quite a while and haven't lost any functionality or encountered any problems.

But it is very good that we do have a kernel for the europe variant finally.
[Galaxy Note 10.1 Android Development] esgie:
++ for N8000 version as it lacks of kernels witch such funcionalities ;(
[Galaxy Note 10.1 Android Development] andip71:
Documentation up-to-date

Hi all,

after many hours of hard work, I am now happy to announce, the documentation is now fully updated again.

Help on both Boeffla-Config app as well as every single configuration option with background information is now available on your finger tips.

How to get there?

1. In Boeffla-Config app go into menu, select help. This displays the Boeffla-Config app help to you. If you click the first link on that page, you are moved to the configuration section for all settings.

2. Just go on homepage www.boeffla-kernel.de and select from the left-hand menu.

3. Follow these links:

Boeffla-Config App help

Boeffla-Kernel Configuration

Hope it is useful for you. At least I will now point all people asking questions answered in these sections to that sections only.

Thanks

Andi
[Galaxy Note 10.1 Android Development] andip71:
1.0-beta2

Hi all,

before I disappear into the weekend, a new beta version for you :)

1.0-beta2

Change Log

Added Zen scheduler

Added system fs to display asv level in Boeffla-Config app

Upstream to 3.0.97 Linux kernel from 27.09.13

Major cleanup

As always - get it via Load&Flash or grab it from the Kernel homepage.

Cheers

Andi
[Galaxy Note 10.1 Android Development] evoliphant:
I was going to give it a shot on my 8013 and see if it would work. I'm not sure about something though. Your file for the kernel has "CWM" in the title. I am using TWRP. I didn't know if you HAD to use CWM for some reason or if TWRP would by okay? I guess I can change the recovery, but in the past I've seen people say CWM for this or that and TWRP worked fine. Want to be sure before I flashed it with TWRP.
[Galaxy Note 10.1 Android Development] andip71:
Ups. Never used this recovery honestly. So I really do not know.

Maybe someone else can comment... :confused:

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy Note 10.1 Android Development] kalashenicof:
Check the OP at the download section, after dig a bit you get this link:

http://www.boeffla-kernel.de/index.php/2012-10-31-06-13-16
[Galaxy Note 10.1 Android Development] andip71:
2.2-beta1

Hi guys,

finally, with version 2.2 I moved the source code basis from n8010 to n8000 (at the same time I ordered a n8000 so I can ensure testing in future).

This means: Version 2.2 of this kernel should work on your n8000 as well now, with all functions like 3g and telephony !!!

This should result in the following devices working with this kernel:

n8000, n8010 and n8013

Version 2.2-beta1

Change log

Kernel basis moved from n8010 source code update3 to n8000 source code update7 (hence, compatibility with n8000)

Initramfs taken from n8000 firmware XXCMJ3

Sharpness tweak from Galaxy S3 implemented (tx to hardcore for mdnie tables), however not such a big effect than on S3

Wireless drivers updated to the ones of n8010 (seem to be more stable to me)

Please note, a source basis change is not a piece of cake, so please flash on own risk, I cannot stress this point enough. So far the kernel is only remote-tested and not tested by me on a n8000.

Thanks and enjoy

Andi
[Galaxy Note 10.1 Android Development] tcchuin:
Does that mean it's possible to have a cm kernel? ?
[Galaxy Note 10.1 Android Development] andip71:
No. I have only one n8000 in future, not two.

The n8010 goes to my wife.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy Note 10.1 Android Development] axibde:
Testing on N8000 .... Thanks
[Galaxy Note 10.1 Android Development] andip71:
Away...

Ladies and Gents,

I will say good-bye to you for the next few days. We are travelling for our new year's eve party tomorrow and will return on Thursday throughout the day.

But I wish a happy new year 2014 to everyone. Let's see what it brings for the Android world.

CU soon

Andi
[Galaxy Note 10.1 Android Development] kstephens98:
Happy New Year Andi
[Galaxy Note 10.1 Android Development] weihan1102:
Thanks for this awesome kernel :)

it seems very stable

and the awesome xbox 360 controller controller supprt :good:

but i need to type insmod /lib/modules/xpad.ko in terminal every time i reboot?
[Galaxy Note 10.1 Android Development] andip71:
Hi,

two questions: What device do you have? n8000, n8010 or n8013?

And no, if you select the module to load in the Boeffla-Config V2 app, you should not need to do this at every boot.

Are you using Boeffla-Config V2?

Thanks

Andi
[Galaxy Note 10.1 Android Development] weihan1102:
Thanks , i have used the Boeffla-Config V2 and it is working fine :)

I have N8000

thanks a lot :)
[Galaxy Note 10.1 Android Development] andip71:
Cool stuff, thanks for letting me know.

In another board I have a user claiming xbox controller support does not work for him with version 2.2-beta1 of the kernel anymore.

So you say it is working fine = this is what I thought (cannot test myself, have no xbox controller)

Thanks

Andi
[Galaxy Note 10.1 Android Development] gorcutt:
Working very well with my N8000. I've downloaded the app from Google Play but still didn't mess with it. I think I'm pretty happy with the defaults that comes with the kernel.

My tab seems very stable and, placebo effect or not, faster.

Thanks for your work.
[Galaxy Note 10.1 Android Development] romskii:
great to see you here

Gesendet von meinem GT-I9300
[Galaxy Note 10.1 Android Development] GodSlayer:
Can you add Double Tap to Wake please?
[Galaxy Note 10.1 Android Development] andip71:
No, I am sorry, i cannot.

LG put a hardware circuit in to enable this without draining battery.

Galaxy devices do not have this, hence I would need to prevent deep sleep completely to keep the touch screen responsive = high battery drain.

This is, unfortunately, a physical limitation of our device.

Andi
[Galaxy Note 10.1 Android Development] GodSlayer:
I see many different kernels implement this for different devices, even my old Motorola Defy. It still enters deep sleep with sweep2wake enabled.

Maybe reducing the responsiveness when the display shuts down or something like that?
[Galaxy Note 10.1 Android Development] andip71:
Maybe. If you find a way, let me know please.

I at least do not know how to overcome the hardware limitations on that device.

:)

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy Note 10.1 Android Development] bokbacken:
Thank you for this Kernel!!!

Finally something new and stable for the N8000, a small token of my appriciation: 58F8627418407683R
[Galaxy Note 10.1 Android Development] andip71:
Thanks. Any donation helps to continue the project.

Thanks a lot

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy Note 10.1 Android Development] andip71:
2.2-beta2

Hi all,

short maintenance/stability update out for you:

Version 2.2-beta2

Stability update (if you sometimes got stuck at the Galaxy Note boot logo, this should now be fixed)

Enjoy

Andi
[Galaxy Note 10.1 Android Development] MaluNoPeleke:
+1

This really works great!
[Galaxy Note 10.1 Android Development] esgie:
Thank you!

It seems to be the first really-rich-featured kernel for n8000 ever!

Random stuff, incl. questions:

- is it possible to enable frandom by default or at least using your config app? It gives a great benefit in responsiveness (at least I can feel it...) but atm it has to be insmodded and linked to default entropy sources using a script (not included in kernel or app) - this prevents non-advanced users of trying it;

- is there any real benefit of using zram on 2gb devices? Pros/cons? Comments i have found about this issue differ between each other;

- same on multicore powersave;

- mdie setting do not stick in quite a random manner (yes, i read an information that it may happen); i thought about refreshing them periodically with a script running in some scheduler (i.e. cron). Can you see any risks related to that idea? Is it possible?

- what is your fav governor, depending on usage policy (mulytitasking/batt.save/performance);

- is it possible to include fiops io scheduler?

Thank you.
[Galaxy Note 10.1 Android Development] andip71:
Esgie, quick answers to your questions:

Frandom: What you want is really not on kernel level anymore. There are mods (Crossbreeder) and scripts that enable it. I would like to rely on this still as the Kernel config app should be only there for configuring kernel stuff.

zRam: I do not believe we need zRam in a 2GB device. But it is there, just in case someone still needs it.

Multicore powersave: I do believe, setting this to aggressive could save some power long-term. At least I have it enabled and do not see any negative impact on performance etc. So, I will keep it personally on.

MDNIE: Yes, this is a known issue with Samsung firmwares. They overwrite MDNIE settings as this configuration is (partially) built into the firmwire and the settings dialog itself. You could, but I do not recommend it, configure an "additional start delay" of up to 60 seconds in Boeffla-Config. This means, the kernel applies the settings potentially after the rom. But this slows down the complete boot process by nature, so it is not a good solution. But yes, you could write scripts that do the same. If you need to know which sys fs interfaces you need to write to, let me know.

My settings: I use zzmoove only, with zzmoove yank battery profile. Combined with ZEN scheduler, no UC, no OC. This is super stable and smooth for me.

FIOPS: If I would include that, I need to update the whole block layer to kernel 3.2 or even 3.4. This is too far away to meet my objective "close to stock" as this does significant changes. I am not considering that at the moment due to this reason.

Thanks

Andi
[Galaxy Note 10.1 Android Development] MaluNoPeleke:
But Crossbreeder needs a kernel module for frandom

Would be great if that could be added
[Galaxy Note 10.1 Android Development] andip71:
It is there. Just use it (crossbreeder normally finds it automatically).

It is called frandom.ko and available in /lib/modules.

That is why the op says "frandom support".

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy Note 10.1 Android Development] andip71:
Ladies and Gents,

I will be leaving today afternoon to a 5 days holiday trip until Sunday evening.

So, I will follow the thread as good as possible, but please expect some delays in my answers.

Cheers

Andi
[Galaxy Note 10.1 Android Development] kstephens98:
Enjoy and stay safe.
[Galaxy Note 10.1 Android Development] esgie:
Thank you very much for feedback, really appreciate it.

It's not exactly what I want (because I know how to do it); in my opinion, frandom gives so great boost to the device that the option of turning it on should be more exposed (or exposed at all...), so the users who were not aware of its real power will just not miss it.

To be exact, it's absolutely not necessary to use whole crossbreeder or something, as the script for enabling frandom is... more than trivial. Let me share my own one (name it as you want, ie. 05frandom.sh, and push to /system/etc/init.d):

#!/system/bin/sh
[ -e /dev/frandom ] || insmod /lib/modules/frandom.ko ;
ln -f /dev/frandom /dev/random ;
ln -f /dev/frandom /dev/erandom ;
ln -f /dev/frandom /dev/urandom ;
chmod 644 /dev/*random

Please note that the above operation (hardlinking /dev/frandom to any other random sources around...) operates on nodes created by the kernel itself, so it is not entirely true that the operation is not on the kernel level... truly, it's significantly more kernel-related than, for example, system tweaks options, which IS included in your app..

About interfaces, it's not a problem; I have figured them out according to control scripts, included in the kernel, the first day after flashing it heh :) , as I like to automate various stuff with scripts + SManager widgets :]

Ah... so, as far as I understood you, the MDNIE setting is being overwritten by the ROM only once, during the boot process?? Maybe it's a good idea to delay executing the sysfs writing until boot completed, then? Some time ago, I have created such a one-liner-loop which I use for various init scripts:

...
while [ `getprop sys.boot_completed` -ne 1 ]; do usleep 500000; done;
...

The code below the line (for example: mdie related sysfs writing) will be executed no longer than 0.5 secs after system sets the boot_completed property to 1... it will neither make the boot process longer nor give any serious overhead to the system (well, such a loop, even if executed every 0.5 seconds, which really does nothing more than reading a single system property, cannot have any real influence on the system...).

I will test above along with mdnie settings in some free time...

Well, enabling zzmoove in your kernel was my first contact with this governor ever... and I must say that I am really surprised!

Btw I am using the newest beta 2 atm, very happy with that btw, however, comparing to beta 1 seems that the Triangle Away support has been broken - resetting the counter requires the full procedure of flashing the quasi-kernel, rebooting, confirming with vol button, etc. - afair it was done without need of reboot in beta 1?

Have a good time during your travel!!!
[Galaxy Note 10.1 Android Development] andip71:
Just quick as I am on holidays still:

Triangle away direct suppouwas indeed removed as it caused boot loop issues for some users (including me).

Other open questions I will answer after my return from holidays next week.

Andi

Gesendet von meinem GT-N8000 mit Tapatalk
[Galaxy Note 10.1 Android Development] GodSlayer:
N8010 Stock charging very very slow on 2.1-stable. In fact, it is charging so slow, it actually dropped 1% whilst charging from the wall with the screen on.
[Galaxy Note 10.1 Android Development] andip71:
I do not have this.

Have you checked in Boeffla-Config, first page, which charge rate was being used? And which charger device was detected?

Andi
[Galaxy Note 10.1 Android Development] andip71:
2.2-beta3

Good morning,

after all my other S3 kernels got an update this morning, last but not least, update also for the Tab:

2.2-beta3

Change log

SmartassV2 governor added

Frandom parts of the crossbreeder mod can now be just activated as a "frandom system tweak" without installing crossbreeder

Boeffla-Sound Engine update to 1.6.5 (allows speaker volumes down to 20)

GPU undervolting, lower voltage limit reduced to 500 mV instead of 600 mV

exFat updated to version 1.2.5

Stability fix for interaction with Boeffla-Config app (no more error messages sometimes when starting the app complaining the kernel is not correct)

Correct reporting of CPU frequency limits to other config apps

Entropy levels increased (more smoothness expected)

Other smaller improvements

Compiled with December 2013 linaro toolchain

Enjoy

Andi
[Galaxy Note 10.1 Android Development] esgie:
It seems now it's causing boot loop for others (including me - N8000 4.1.2 deodexed, sammy-based rom)!

After running TA on 2.2b2 (before you have posted info that it has been removed...), Triangle Away shown a pop-up - typical for stock based roms - that it is flashing kernel and then that it will reboot the device; however, Triangle Away has closed (without FC or something), but the reboot didn't happen (it has sent me back to the homescreen, to be precise). I repeated the procedure - still nothing. After rebooting - the device didn't stood up and remained on the bootloader logo ("Samsung Note 10.1"); after a quick investigation I have determined that both kernel and recovery partitions were erased. First time since about a year I was forced to flash them using Odin :) Luckily, no system or data partitions has been damaged or overwritten.

Please be aware that no possibility of flash counter reset = no possibility of using AllShare Cast dongle at all!

As far as I can see, you have released 2.2b3 :) Flashing it in a minute, will be back with feedback in some free time.
[Galaxy Note 10.1 Android Development] andip71:
Strange, but I suspect some kind of side effect.

Never had that, luckily.

Can just imagine maybe TriangleAway used a wrong flash kernel for some reason.

But after removing that TriangleAway direct support, me and many other users have no issues with rebooting the device anymore. So it was correct to remove it atm.

Andi
[Galaxy Note 10.1 Android Development] muop_92:
I had only oc to 1600 and my device was so unstable. I had freeze and some reboot. What should I do now? I m using pegasusq governor, deadline io. No change in voltage
[Galaxy Note 10.1 Android Development] andip71:
Do not overclock then.

You have a device that apparently cannot take it.

Or try to overvolt your CPU by 25mV on the 1500 and 1600 steps...

Andi
[Galaxy Note 10.1 Android Development] muop_92:
I will try

Thank you for your good kernel
[Galaxy Note 10.1 Android Development] andip71:
Guys,

good news for me, maybe bad (or good, haha) news for you:

I am leaving to a 4 days trip to my home city today afternoon, to join a big ball event there.

So, I will follow the thread, but please expect some delays in my answers.

I will be back Wednesday next week.

Cheers

Andi
[Galaxy Note 10.1 Android Development] muop_92:
I have a question:

What is the stock value of charge rate? For our kernel it is 1900 at maximum by default. So I think it is fast charge, right?
[Galaxy Note 10.1 Android Development] andip71:
Default is 1800. But you can put it much higher if you are brave.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy Note 10.1 Android Development] muop_92:
It was like this on my device
[Galaxy Note 10.1 Android Development] Kouya1600:
N8020 Port

Can Anyone Port this to Note 10.1 LTE (N8020)?
[Galaxy Note 10.1 Android Development] andip71:
2.2-beta4

Hi,

a small maintenance update for you:

Version 2.2-beta4

23.01.2014

Improve Frandom System tweaks (internal optimisation of used devices + switching system tweaks can now be done without reboots, a new Boeffla Config App V2 in version 2.1.9 will be released soon to remove the dialog)

Reverted back to proven stable Google 4.7 toolchain as Linaro was long-term causing some side effects (CPU cores not utilized properly, Bluetooth issues etc.)

Enjoy

Andi
[Galaxy Note 10.1 Android Development] vitoski:
Andi just a quick question regarding performance. Have you changed something recently with profiles? I have similar setup to yours (battery-Yank) I experience some lags, specifically with YouTube. Don't know if Google f*cked up something or simply the tablet is choking. Have you encounter any of this?

Wysłane z mojego GT-I9100 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] andip71:
No, I have not. But honestly I never use YouTube.

Then try to switch to PegasusQ with Boeffla Moderate profile for a test.

Sometimes PegasusQ resolves that kind of issues.

Andi
[Galaxy Note 10.1 Android Development] gege0202:
hello, were is the download link? in this thread it says go to "www.boeffla-kernel.de" and in "www.boeffla-kernel.de" it says go to this thread!
[Galaxy Note 10.1 Android Development] Nikorasu:
On the website, click downloads on the left navigation, scroll all the way down for Note 10.1 kernels.

Stable:

http://boeffla.df-kunde.de/n8010/boeffla-kernel/Series 2.x/2.1/

Beta:

http://boeffla.df-kunde.de/n8010/boeffla-kernel/Test/
[Galaxy Note 10.1 Android Development] gege0202:
ok. thanks
[Galaxy Note 10.1 Android Development] MarlinFF:
Would there be any possibility of an AOSP kernel? I have a Note 2 and for a while there wasn't many AOSP kernels but now all the kernels are AOSP + TW compatible. I was wondering if this would be a possibility or not.
[Galaxy Note 10.1 Android Development] andip71:
Technically possible.

Time wise I cannot do that anymore.

4 kernels is enough for my small free time...

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy Note 10.1 Android Development] andip71:
2.2 stable

Hi all,

finally, version 2.2 is declared a stable release:

Version 2.2 stable

27.01.2014

Adjust kernel presets shown in Boeffla-Config V2 app

Enjoy
[Galaxy Note 10.1 Android Development] andip71:
New betas coming soon...

Hi all,

just to let you know, I will in a few minutes start upload of new betas for all devices and variants:

S3 Samsung Boeffla-Kernel 5.2-beta1

S3 Omnirom Boeffla-Kernel 2.2-beta1

S3 CM11 Boeffla-Kernel 2.2-beta1

n8000 Samsung Boeffla-Kernel 2.3-beta1

n801x Samsung Boeffla-Kernel 2.3-beta1

I will post change logs soon...

Andi
[Galaxy Note 10.1 Android Development] andip71:
2.3-beta1

Hi ladies and gents,

let's start into a new version for Boeffla-Kernel with a new beta:

2.3-beta1

Important note: With version 2.3, there is no common kernel for n8000 and n801x anymore!!! There were some features broken for the devices, so I decided to split into two kernels now: one for the n8000, and one for the n801x (n8010 and n8013). Please ensure you download the correct version for your device !!! In terms of kernel features, both versions are 100% identical.

In order to use all functionalities, please ensure you have updated Boeffla-Config V2 to latest version 2.1.15.

Change log

zzmoove updated to version 0.8-beta8 (credits to ZaneZam)

System tweak "Frandom tweaks" removed, replaced by a new option in Boeffla-Config settings menu (version 2.1.15)

Added profiles "no undervolting" for CPU and GPU

Busybox updated to 1.22.1 (compiled from scratch by myself to have in what I want/need)

Busybox can now be configured to be used by whole system (configurable in Boeffla-Config V2 settings menu, version 2.1.15)

su updated to version 1.91

Many internal optimisations

As always - enjoy

Andi