yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] sherlock5545:
Thanks for the latest kernel, working perfectly fine so far. Hopefully will be getting better battery life too.

Sent from my GT-I9300
[Galaxy S III Android Development] andip71:
Mhhhhh... why should you?

Energy costs money, and "money makes the world go round" :)

Just kidding :angel:

Andi
[Galaxy S III Android Development] djclark25:
Just noticed, I had set my MDNIE settings to Natural / UI. After a reboot they have reverted back to Dynamic / Standard.

All other settings have stuck, only the MDNIE settings have reverted.

Running Temasek V6, latest Boeffla Cm11 kernel and ART (If that makes a difference)
[Galaxy S III Android Development] andip71:
Jepp, unfortunately you have to live with that.

There is a good reason why it is stated (only for CM10.2).

The newer roms overwrite the settings again during startup, so they are not sticky.

I cannot do anything from the app on that. Only, I could consider to remove it completely to avoid confusion (but this would have bad impact on other users, so do not want to do that).

Andi
[Galaxy S III Android Development] amppen:
CM-2.1-beta1-cm11.0-r3p2

Kernel seems good, however the graphics performance is not as good as it could be for me. Facebook scrolling is stuttering and benchmark shows lower points than expected. I'm going to reflash the ROM and this kernel after it to be sure. I flashed this on top of temasek's kernel after deleting /data/.temasek, maybe that's causing some issues. I also experienced a 3-4 second lag with screen waking up when i received a call.
[Galaxy S III Android Development] djclark25:
Ok no problem. Dont reboot that often so not a major issue. just thought I would let you know in case was a bug

Thanks
[Galaxy S III Android Development] RohanAJoshi:
andi, I am using same settings as I used for omni base kernel for temasek.

but this cm based release giving me more battery drain than omni base for on screen use..

will test deeper..

.

but sharpness and buttons lights are working fine, thanks. :)
[Galaxy S III Android Development] andip71:
Seriously... the kernel is out for a few hours now. You cannot really judge battery consumption after that time.

For a serious answer you need at least 1 charging cycle or 36 hours.

It can be, the kernel drains more, of course. But the changes would not explain it. It should at least not drain more than the CM10.2 kernel which was the basis for it.

Andi
[Galaxy S III Android Development] mikesoccer25:
Battery issue....im asking u guys what might be the problem....i let my battery drain completely and turn off by its self but when i plugged in the charger it showed me i have 40% and started to charge from 40...with the phone turned off....what do u think its the cause of that? And another question...is it ok to recalibrate battery after flashing new rom or kernel? Tnx

Galaxy I-9300 Temasek v6 Rom , Boeffla 2.1 beta 1 CM Tema kernel
[Galaxy S III Android Development] andip71:
That one sounds like a defect battery to me, mikesoccer.

Battery cannot hold voltage anymore under some current pressure, so it switches off. Then it recovers quickly again.

This is at least the typical effect with battery.

Just an idea, cannot guarantee.

Andi
[Galaxy S III Android Development] mikesoccer25:
Only when its turned off...when its on it doesnt behave like that...i was thinking that its because i flashed too many roms and kernels lately and i messed up the battery somehow

Galaxy I-9300 Temasek v6 Rom , Boeffla 2.1 beta 1 CM Tema kernel
[Galaxy S III Android Development] JustArchi:
Andi.

I think you should keep performance with a little addition to bring 4 cpu cores online. It's exteremely useful in benchmarks and long-run tests. Just my little request if you think same.
[Galaxy S III Android Development] andip71:
Do a full recharge cycle for 1-2 times, when it recovers - fine. If not, get an additional battery for 10 dollars to cross-check.

I need to think about it. I am not into benchmarks at all, so if - I bring back this one governor unchanged. Do not want to put work into this, honestly.
[Galaxy S III Android Development] mikesoccer25:
I will tnx...im flashing too much anyway...roms....kernels...

Galaxy I-9300 Temasek v6 Rom , Boeffla 2.1 beta 1 CM Tema kernel
[Galaxy S III Android Development] JustArchi:
If you're not going to force it to bring all cores online then yeah it's not worth a while.
[Galaxy S III Android Development] andip71:
Update for Omnirom kernel

Good evening,

last update before I will disappear for 7 days now (weekend + 5 days UK next week).

I ported the touchkey led settings from CM10.2 kernel into the Omnirom kernel, so please update your Omnirom kernel to version:

2.1-beta1a

Change log

Ported the touch key backlight handling settings from CM10.2 over to Omnirom kernel

Settings in Boeffla-Config are (lock screen 1-2 times after changing the settings):

"Touch LED controlled by kernel" = on,

"Touch led when touch screen" = on -> LED is on when pressing touch keys or using touch screen (default)

"Touch LED controlled by kernel" = on,

"Touch led when touch screen" = off -> LED is on only when pressing touch keys

"Touch LED controlled by kernel" = off,

"Touch led when touch screen" = n.a. -> LED is always off

That was the only change, but I hope people that were missing this feature in Omnirom are again happy now.

Cheers

Andi
[Galaxy S III Android Development] fndpena:
This happened to me only once. Rebooted more 2x times after that and MDNIE settings didn't reverted. :)
[Galaxy S III Android Development] Guihardrock:
lord boeffla said me that his (awesome) kernel is not suported in pacmanrom :crying::crying:
[Galaxy S III Android Development] andip71:
Absolutely correct. And there is no discussion about that, refer to OP.

The same applies for Yank, Googy, Devil, Agni, Temasek kernels... we all do not support the approach every rom team has it's own framework implementation.

Quoting:

IMPORTANT

: As per notice of 01.11.2013, my CM10.2 kernels do NOT support proprietary Custom Rom frameworks anymore. So if your Custom Rom did not implement the generic framework class framework-2.jar but his own naming convention, you will receive a boot loop. Do not cry about this here but advise your Custom om cooker to fix this. I will not change this ever again.

The most prominent custom kernels for CM will follow the same approach (aligned between Yank555, Googy, Teufel, Psndna, Temasek and me).
[Galaxy S III Android Development] maddes1402:
Thanks for the update! Have a nice trip! ;)

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] djclark25:
If your anywhere near wales, pay me a visit! I'll buy you a coffee for all your hard work :)
[Galaxy S III Android Development] tisazalay:
Hi Andi (@Lord Boeffla)

I was having some headaches with a strange problem, couldn't mount /system rw on ES File Explorer, the only workaround I knew of was making a write access on File Manager and when it was granted root, /system kept mounted rw.

Even the mount -o remount,rw /system (from Terminal, after su) didn't catch up....

Then I simply turned off ext4 tweaks in Boeffla config and after reboot, ES File Explorer mounted /system rw right away.

I just wanted to report in case some logic regarding the ext4 tweak was in place (for me that setting interfered with many calls involving mounting /system as writeable, for example from within SuperSU to make it a /system app).

Thanks, I'm enjoying the latest Boeffla CM11 on temasek's v7 now.
[Galaxy S III Android Development] sayaksark:
Oh no.... Im going to miss you.... Lord.... Have a happy journey.... Tc
[Galaxy S III Android Development] Undermyoath:
That's what I was trying to say, bro.

The older versions before the dev's deadline are still suitable though, that was what I was trying to make clear ^^

And have a good and safe trip, Lord Boeffla!
[Galaxy S III Android Development] thearc77:
Already reported some of this to the thread

The thing is if you repack the built kernel from your KitKat rom the RW access is restored. Today I wiped again enterily my device (/data+internal storaga+system/cache), flashed omni+gapps+Boeffla 2.1 at once with TWRP 2.6.3.1 and Titanium, Es Explorer, X-Plore have RW access to system but no from terminal emulator, then I update the kernel to 2.1a for those awesome settings for touch and lost tottaly RW access to /system. Only restore from and adb remount or adb shell remount -o remount,rw /system but when I reboot then go away again.

One my skilled friend with same Omni Build and Boeffla kernel have the same issue and repacked the original Omni Kernel with modules and the RW access is here again and don't go away with reboot.

Is good to now the module affecting this is ext4 tweak and affect all Kitkat.

TY and testing right now

Edit: No luck on Omni :(
[Galaxy S III Android Development] JustArchi:
No, just sometimes it's not possible to remount filesystem (if something is using it). If you try to remount a few times it'll work.
[Galaxy S III Android Development] thearc77:
I try several time, finally got RW from adb remount or adb shell mount -o remount,rw /system.

Sorry but this happen with Yank and Temasek kernels too.

Reverted to the repacked Omni kernel and RW access restore.

Edit: My friend will try pack later a kernel without that module to test
[Galaxy S III Android Development] JustArchi:
Actually I agree. I can't remount rw some time after boot as well.
[Galaxy S III Android Development] tisazalay:
I'm more confused now. The first boot with Ext4 tweaks off, rw was working, after I toggled it on again it didn't have any effect. I made a complete wipe to install new Rom from philz and reinstalled temaseks + gapps (without boeffla kernel) and as thearc pointed out, rw is working fine again...

This is very weird but will keep without the kernel for a while to be completely sure.
[Galaxy S III Android Development] andip71:
Maybe SELINUX causes that.

At least on Omni I did a kernel (for internal use) with removed SELINUX. Then some file system operations were working which did not before.

But let me test more pls.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] sherlock5545:
Is that SElinux even necessary? We never had it back in the past and everything was fine. All ROMs/Kernel now have it.

Sent from my GT-I9300
[Galaxy S III Android Development] __Michael__:
I am using temasek's 4.4 ROM.

I flashed the CM11.0 r3p2 version , the boeffla config V2 worked , but after i have updated the superSU app i am getting this?:
[Galaxy S III Android Development] XDAMaxe:
hmmm, SELinux comes from NSA and should give additional process control in security manners (protection againts 'bad' programs, 'unwanted' system access etc.).

don't know if it is opensource (and therefore editable) but the involvement of nsa seems - at the actual point of view - quite suspicious ...
[Galaxy S III Android Development] MBurns2:
hey Andi, thanks for the adding of pegasusqplus governor. I really like it !
[Galaxy S III Android Development] djclark25:
Anyone else having a issue with the led in touch feature? Seems to be working 80% of the time but the buttons will light up at random times when touching the screen. Doesn't seem to be consistent with any particular app, multi touch, swipe etc

Temasek v6 with latest kernel
[Galaxy S III Android Development] DerTeufel1980:
Interesting, I had to fix similar behaviour yesterday. Do you get this, when you have set "kernel controls backlight"?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Android Development] sherlock5545:
I created an automated script that disables the touch LEDs at every boot, since somehow with Boeffla I can't disable them the typical way. Not an issue.

Sent from my GT-I9300
[Galaxy S III Android Development] andip71:
Hi,

try the following:

- enter Supersu and remove Boeffla-Config from the list of allowed apps

- start Boeffla-Config again and wait for SuperSu to ask for rights

- grant rights

Let me know if that worked for you, then I would change the message the app displays slightly.

Andi
[Galaxy S III Android Development] andip71:
I will anyways compile my CM11 kernels quickly with SELINUX switched off as an experimental version.

So you guys can try it if you want.

Andi
[Galaxy S III Android Development] __Michael__:
It is working now :)

Thank you !
[Galaxy S III Android Development] andip71:
Thanks, sometimes this happens.

I will change the message in the app and include these instructions.

Thanks for the quick feedback.

Andi
[Galaxy S III Android Development] andip71:
Hi all,

just to let you know, in the download area you will find all my CM11 kernels now also in a version with disabled SELINUX.

Note: This is experimental !!! So only install if you are curious.

CM-2.1-beta1-cm11.0-noselinux

CM-2.1-beta1-cm11.0-r3p2-noselinux

Omnirom-2.1-beta1a-noselinux

So, feel free to give it a try and please report any differences to the normal versions. Would be specifically interested if it breaks anything.

Thanks

Andi
[Galaxy S III Android Development] sayaksark:
can u tell me what are u using to change the fonts because for me the app font installer is not working anymore in 4.4

---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------

what is the difference between normal kelnel and noselinux?
[Galaxy S III Android Development] andip71:
Humm, the SELINUX layer is disabled in these experimental version.

Let's see how this changes things.

Please read:

http://en.wikipedia.org/wiki/Selinux

Andi
[Galaxy S III Android Development] __Michael__:
ifont :)
[Galaxy S III Android Development] tisazalay:
Hi Andi, I just installed the noselinux cm11 on temaseks v7 and the problem mounting /system rw popped in immediately.

I use ES File Manager and the root Explorer doesn't stick rw for /system with boeffla, it does for stock kernel with Rom.
[Galaxy S III Android Development] andip71:
tisazalay, then I have no immedate idea anymore.

But what do you mean with "doesn't stick"? Why would you leave system mounted as rw all the time? This is against all security in general.

Andi
[Galaxy S III Android Development] SuperAce609:
Woooowwww. That's just ridiculous. That's how you know money changes people. Thank God stock Samsung roms have kernels like these so feature packed that makes CM piratically useless to me.

DON'T YOU EVER LEAVE US ANDI
[Galaxy S III Android Development] striked0wn:
It was aosp.. Now its only an a.. Without osp.. :(..
[Galaxy S III Android Development] faddys123:
can i use this with miui ? the port that is based on cm 10.1
[Galaxy S III Android Development] cerealguy:
Yes.. Of course... Download CM 10.1 version..

Inviato dal mio GT-I9300 usando Tapatalk 4
[Galaxy S III Android Development] mikle_01:
[MENTION=797171]Andy[/MENTION]: Couldn't find the "Boeffla-Kernel 1.0-beta" at your website. Am I blind!? Section "Test versions CM10.2" is empty :D

EDIT: Found....
[Galaxy S III Android Development] abhibnl:
Wi Fi not working with Probam Rom(4.3), everything else is working fine. The On/OFF button remains grey all the time
[Galaxy S III Android Development] andip71:
Will fetch latest CM sources again tomorrow for beta2.

Maybe this will fix it for you.

So far I support CM original only (officially).

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] andip71:
As there were no votes to include the existing mdnie settings in the config app, I assume I can skip this work. Right?

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] STAticKY:
I vote for you to add it please

TP.
[Galaxy S III Android Development] alatariell:
Hey Andi,

Just bought the donation version of your app and its working great with your CM kernel just like it did on the Sammy roms.

If you could add mdnie settings that would be really great. CM colors are a bit flatten out compared to the Sammy rom colors.....but thats very personal i guess. Thx for the great work!
[Galaxy S III Android Development] cink40:
I am using SlimBeam now so I really do not need it, and there is also workaround with terminal emulator. By the way beta 1 work very good with Slim 4.3.
[Galaxy S III Android Development] clarionero:
Hi. Im using ProBam ROM too. All is working right here. No issues. And the battery is wonderfull too.

Enviado desde mi Transformer TF101 usando XDA Premium HD app
[Galaxy S III Android Development] martimo:
I thought thanking the post would be enough xD

How about a test-picture next to the setting? So the user can see the difference :)
[Galaxy S III Android Development] andip71:
1.0-beta2

Hi all,

just to let you know, I just rebuilt beta1 with latest CM kernel sources from 21.09.2013 and uploaded it as new

1.0-beta2

for you.

I guess the issues reported before (missing data arrows) etc. should be fixed now.

Happy flashing and testing.

Cheers

andi
[Galaxy S III Android Development] Kyle07:
Please add it, Andi! It would be great...
[Galaxy S III Android Development] Eleve11:
Wifi went down after updating. Can't turn it on again!
[Galaxy S III Android Development] cink40:
Did you change anything regarding backlight? Option to turn it of in slimbeam does not working anymore...

Scratch that, does not work with beta 1 either...
[Galaxy S III Android Development] Yank555:
Slim uses kernel-handled backlight management, CM shifted that to the ROM in latest nightlies.

JP.
[Galaxy S III Android Development] FlemishDroid:
I had the same problem after flashing beta 1...so I flashed it again and then it works. Now I gonna try beta 2.

---------- Post added at 10:35 PM ---------- Previous post was at 10:29 PM ----------

With beta 2 wifi works immediately.
[Galaxy S III Android Development] Eleve11:
Okay! I'll try to flash the Beta 2 again.:fingers-crossed:
[Galaxy S III Android Development] tisazalay:
It doesn't ever permit rw operations. For example, if I try to rename a script in init.d folder it says Task is failed.

In es file manager there's an option to invoke root Explorer setting so you can mount system rw if you select it, go back and open again, it's back to ro.

Edit : Most operations involving mounting system rw fail (for example from within bbs to make it a system app, tibu won't change user apps to system, etc.)

The only app that does mount system rw that I've noticed is the stock file manager. (I'm not completely sure if adaway is working, will recheck)
[Galaxy S III Android Development] cink40:
Adfree working, also Root Explorer...i think that is the problem of ES explorer app

Oh, and old version of root explorer also had problems, so something obviously changed in 4.4
[Galaxy S III Android Development] Guihardrock:
well definitely i love your work so i install temasek unooficial v7 to have the option to use your kernel but, could you give us the diference between:

boeffla-kernel-CM-2.1-beta1-cm11.0-r3p2.CWM.zip and boeffla-kernel-CM-2.1-beta1-cm11.0-r3p2-noselinux.CWM.zip? Please and thanks :p:p
[Galaxy S III Android Development] andip71:
Install the one without "selinux".

Please refer to post here:

http://xdaforums.com/showpost.php?p=47759004&postcount=1177

I think I will create a folder called "experimental" to move the selinux trial version into it.

Thanks

Andi
[Galaxy S III Android Development] tisazalay:
Thanks. There are several things going on, perhaps es does need some adjustments but it was working before I flashed boeffla, on stock.

Another quirk is that when I flashed boeffla from philz, it complained about root and I choose not to fix it. (the philz part I can't blame on the kernel because yesterday I installed supersu... But everything was working at that moment and kept running fine with several boots)
[Galaxy S III Android Development] Beharii:
I just installed CM10.2 and a lot of the members recommended your Kernel, problem is after flashing my phone just won't boot, might be a stupid question but what can I do about it?:confused:
[Galaxy S III Android Development] andip71:
Which CM10.2 have you installed?

What is the effect of "does not boot"?

Andi
[Galaxy S III Android Development] djclark25:
Yes I have the config set for the kernel to control the led behaviour. This worked fine on the 10.2 kernels and before temasek v5 with the new Mali drivers but since the new kernel with the new Mali drivers it has been a issue.
[Galaxy S III Android Development] JustArchi:
Looks like I'm the only beta tester here :p.

It doesn't work Andi. /system still can't be remounted as read/write. However disabling of selinux fixed my exfat external sdcard, which didn't work before with selinux enabled.

P.S. On yank's kernel this issue persists as well, however on temasek's one it doesn't, stock is good as well.

Maybe new ramfs?
[Galaxy S III Android Development] thearc77:
Tested experimental build without luck, reverted to builtin and work ok.

Edit: on Omni 23-11-13
[Galaxy S III Android Development] tisazalay:
Does the kernel create stuff on ramfs?

I remember yanks setting in aroma to run init.d either from ramfs or rom itself but I had a severe boot loop when I tried boeffla Omni on temasek v4 and not even dirty flashing the rom fixed it, had to do a full wipe.

I ask that, because when the system rw stuff comes up, even dirty flushing the rom again (supposed to only set stock kernel) and gapps, the system isn't mounted rw. My tests show that only complete wipe & reinstall let's system mount rw.
[Galaxy S III Android Development] JustArchi:
temasek shares ramfs with kernel which is being overwritten, that's why it's universal (any kernel method).

Other kernels don't.
[Galaxy S III Android Development] tisazalay:
I recall temasek mentioned that some time ago, as you mentioned, probably the main problem lies there. The other theories I had were busybox or su binaries.

Let's hope :p
[Galaxy S III Android Development] andip71:
What means without luck? What is wrong?

That was a combintation that cannot work. It was nowhere mentioned.

The OmniTema Kernel was only from V5 upwards. Not for V4.

But now all should be clear. V7 works fine with the CM11-r3p2 kernel I provide.

Andi
[Galaxy S III Android Development] andip71:
Hi Archi,

which kernel version are you talking about now? CM11-r3p2, CM11 standard or Omnirom?

And what is the issue with remounting /system to RW? I tried many time via Root Explorer app and it always worked for me.

Andi
[Galaxy S III Android Development] JustArchi:
CM11 kernel, with and without selinux, without r3p2.

You can't remount system as read/write. Comand finishes without error but system is still read only.

I even used busybox mount, as you can see above (normal doesn't work as well). sysrw does the same as busybox mount -o remount,rw /system, which you can clearly see below.

Only yours and yank's kernel is affected, stock (with selinux) and temasek's (without selinux) are OK, (so it's not selinux issue).

If you need any more information let me know.
[Galaxy S III Android Development] tisazalay:
Yes, nobody mentioned/suggested, actually I wrote it wrong, I tried an Omni alpha on the rom with the new mali (it was v5), it booted but had many FCs with theme and other stuff. It was 100% my fault, then you made the ramfs changes and everything has been fine. (The phone crashed on me after a phone call that day, wednesday), but it's history :D

One question, is boeffla-init.sh (from /sbin) executed on every boot?
[Galaxy S III Android Development] andip71:
Interesting problem.

Two findings:

Do a "adb remount" once, from then onwards it works fine. So adb remount does something "special".

Same with root explorer app: It also works always, so there must be a hidden command that is required or some secret parameter or so.

Not much time for research now, I always remount via Root Explorer, and thus it always works for me.

One day we will find it out...

Yes, it is the kernels init script, so to speak.
[Galaxy S III Android Development] JustArchi:
Unfortunately I need it for auto-deleting of my runonce script. adb remount doesn't work from "inside" android. Is there anything which works from android itself?

BTW, root explorer fails as well for me. adb remount from PC works.