yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
2.1-beta2 for all variants...

Hi all,

as promised, there is a new beta version available for all 5 kernel variants now:

Boeffla-Kernel Change Log (CM 10.1 version)

Version 2.1-beta2

03.12.2013

Charge level information added (you need Boeffla-Config V2 app 2.1 or higher for it), this shows you the detected charger + the negotiated charge rate between kernel and charger

Bit more relaxed timing during kernel initialisation

Some minor bugfixes

Boeffla-Kernel Change Log (CM 10.2 version)

Version 2.1-beta2

03.12.2013

Charge level information added (you need Boeffla-Config V2 app 2.1 or higher for it), this shows you the detected charger + the negotiated charge rate between kernel and charger

Bit more relaxed timing during kernel initialisation

Some minor bugfixes

Initramfs updated final CM10.2 version

Boeffla-Kernel Change Log (CM 11.0 version)

Note: This version is NOT for Temasek CM11 roms of Version V5 or higher !!!

Version 2.1-beta2

03.12.2013

Charge level information added (you need Boeffla-Config V2 app 2.1 or higher for it), this shows you the detected charger + the negotiated charge rate between kernel and charger

Bit more relaxed timing during kernel initialisation

Some minor bugfixes

Initramfs updated to version of 02.12.13

SELinux set to permissive

Boeffla-Kernel Change Log (CM 11.0-r3p2 version)

Note: This version is for Temasek CM11 roms of Version V5, V6, V7 or higher !!!

Version 2.1-beta2

03.12.2013

Charge level information added (you need Boeffla-Config V2 app 2.1 or higher for it), this shows you the detected charger + the negotiated charge rate between kernel and charger

Bit more relaxed timing during kernel initialisation

Some minor bugfixes

Initramfs updated to version of 02.12.13

SELinux set to permissive

Boeffla-Kernel Change Log (Omnirom CM11 version)

Version 2.1-beta2

03.12.2013

Charge level information added (you need Boeffla-Config V2 app 2.1 or higher for it), this shows you the detected charger + the negotiated charge rate between kernel and charger

Bit more relaxed timing during kernel initialisation

Some minor bugfixes

Initramfs updated to version of 01.12.13

SELinux set to permissive

As always - Enjoy

Andi
[Galaxy S III Android Development] JustArchi:
I'm more than happy to see that you're actively supporting at least 5 different AOSP branches (not even talking about Sammy's right now). Andi, you're the best :good:.
[Galaxy S III Android Development] andip71:
Yeah, currently I am maintaining 8 kernels:

2 Samsung kernels for the S3

5 CM/Omni kernels for the S3

1 Samsung kernel for the n801x

Thats quite enough currently :)

Andi
[Galaxy S III Android Development] JustArchi:
BTW I saw some folks on OmniROM gerrit merging your boeffla engine into stock kernel :D.
[Galaxy S III Android Development] andip71:
Yeah, why not making it a defacto standard :)

Can only be good...

Andi
[Galaxy S III Android Development] Royal.Bengal:
Excellent Work!

Just flushed the latest beta for Temasek and can report back that external SD - etx4 gets mounted properly. Mobile Odin sees external SD too, but no luck with SMS Backup Pro. Proberbly a lot of apps are not updated to read and write the Kit Kat way. Keep it up and all well wishes for you.
[Galaxy S III Android Development] thearc77:
Lord Boeffla

First at all thank you for the new release for Omni and I hope your engine came to the source tree like Archi said.

My all issues dissapear (system full access) and I feel relieved because I can use your sweet config app, the simplest one for a kernel.
[Galaxy S III Android Development] tisazalay:
Thank you very much, I'm really pleased the battery temp reading issue is gone, also, as was mentioned before, Mobile Odin can access the external SD Card (mine is fat32).

:good:

This one should be stock too! Congratulations!!!

I'm on Temasek's v14
[Galaxy S III Android Development] shaarky:
+1 battery temperature readings are fine now, excellent, than you !
[Galaxy S III Android Development] carbonize:
Why do we have the ability to set mDNIe via your app? It says that in Samsung ROMs and CM10.1 you can set it via settings but you can in 10.2 as well.
[Galaxy S III Android Development] andip71:
Because there was some time when cm10.2 had this feature removed.

Then I built it in, a few weeks later they brought it back.

And I am quite reluctant to remove things as some might still use it.

Jus ignore it and you are good.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] faddys123:
On Temasek rom I have used your kernel and yanks and I encounter the same problem, when I charge my phone it starts on 900mah and gradually goes down to 100 mah output,. I increased the output from your app., which didn't make a difference, however, what I did find out was if I set ignore unstable power on then It will charge at 1000mah however it won't charge above stock. But on yanks he doesn't have the option to ignore unstable power.
[Galaxy S III Android Development] tisazalay:
Hi Andi, just a curiosity,

I've set charging currents for AC at 1100, USB at 900.

When I plug the AC charger it's working fine (I guess), and Current Widget reports a 1098 current (as usual) but Boeffla Config reports 700.

When I plug it to a USB port, Current Widget reports 899 (normal) and Boeffla Config reports 900.

Now, I'm perplexed by the AC report since: 1. It charges faster than USB 2. My USB is 2.0 (don't think it's supposed to deliver 900 but it's working)

Thanks
[Galaxy S III Android Development] andip71:
Thanks for the report. But do not know what I should do with it.

All sounds quite logical to me. Your charging power is not stable enough, maybe a bad cable or charger or whatever, so the soft regulation come into place and reduces the charging current down.

The ignore function prevents from going into soft regulation, so you can load with 1000.

Please monitor that for a longer time. It can be it only went once into soft regulation and reduction of charging current to 700.

All current widgets and apps cannot read the real charge current from the device as there is no sensor.

Of course, I might have still a glitch in my implementation as well. we will see over the time.

I thought it might be useful information though.

Thanks

Andi
[Galaxy S III Android Development] pulsation:
External SD formatted with ext4 also mounts correctly now with lastest omni nighlies using your v2.1-beta2 kernel. Thanks a lot [MENTION=947981]Lord Boeffla[/MENTION] :)
[Galaxy S III Android Development] andip71:
Ok, quick one: I found an interesting case when I tried to load my S3 just before.

Soft regulation is re-initiated periodically again. So I need to put some small changes into the implementation soon.

Andi
[Galaxy S III Android Development] tisazalay:
You were right, I unplugged and when I plugged back in, it's reported as 1100. Now I think the charger might be faulty (I have it since my Galaxy Mini 5570 days :D), because I have ignore unstable and safety margin, and as you mention it really is useful information because it's the kernel who negotiates the power (learned that here).

Thanks
[Galaxy S III Android Development] ImShadix:
Hello, for Temasek V15, I have to take : - CM11.0 kernel

or

- CM11.0-r3p2 kernel

Thanks a lot guys :)
[Galaxy S III Android Development] danierakes:
Cm11.0-r3p2 kernel
[Galaxy S III Android Development] xeizo:
Beta 2 works fine here with Temasek V14+update using ART ! Thanks for this amazing kernel/configapp :)
[Galaxy S III Android Development] ImShadix:
Oh, nothing I found the link
[Galaxy S III Android Development] titijuli:
here

http://www.boeffla-kernel.de/index.php/2012-10-31-06-13-16

Enjoyneering
[Galaxy S III Android Development] danierakes:
http://boeffla.df-kunde.de/sgs3/boeffla-kernel-cm/cm11.0_r3p2_download/Test/
[Galaxy S III Android Development] faddys123:
Getting boot loop :-\
[Galaxy S III Android Development] dkionline:
Test with 10.2

[tapatalk]printed, scanned and faxed...[/tapatalk]
[Galaxy S III Android Development] zulmajdi:
Tested on resurrection remix rom based on PA,AOKP,CM10.2 and it working just fine. Btw thank you for this kernel. Been waiting you to release it yay.
[Galaxy S III Android Development] cerealguy:
Are sure that your Miui rom is based on CM 10.1?!?

Inviato dal mio GT-I9300 usando Tapatalk 4
[Galaxy S III Android Development] faddys123:
Check for yourself

http://xdaforums.com/showthread.php?t=2396162

[ROM] [PORT] [4.2.2] MIUI v5 3.9.13
[Galaxy S III Android Development] andip71:
CM10.1 Version is now also updated to beta2.

Everything the same as beta1, just based on latest CM 10.1 kernel sources from 21.09.13.

Andi
[Galaxy S III Android Development] cerealguy:
Very strange... I've tried this rom with Temasek kernel for CM 10.1, and all works good... :-\

Inviato dal mio GT-I9300 usando Tapatalk 4
[Galaxy S III Android Development] djclark25:
Hi Andi.

Great to see your kernel for CM based ROMS. Still have my bookmark in Firefox that says Boeffla-kernel1.0 (30.12.2012)!!

Cant test at the moment as awaiting a important phone call, but will this new beta work with MIUI?

Like a previous post has said, the best version of MIUI for S3 is CM10.1 based and would be great if we could use this kernel with it.

Thanks
[Galaxy S III Android Development] andip71:
djclark25, give it a try.

I did not test with anything else than official CM versions. Unfortunately have no bandwidth to test every custom rom out there (apart from the fact I am personally anyways not a big fan boy of custom roms...)

Andi
[Galaxy S III Android Development] djclark25:
OK, will give it a try after I recieve my phone call. I think its only a little tweak to get it working with MIUI. Googly_Anas tweaked his kernel to work with MIUI a few version ago.

Once tested, will let you know.

---------- Post added at 10:05 AM ---------- Previous post was at 09:14 AM ----------

Had bootloop with the new beta. If you could include the tweak to work with MIUI it would be much appreciated. Obviously, up to you as your kernel!!

Cheers
[Galaxy S III Android Development] mikle_01:
Beta 2 with 10.2 (Temasek v44) absolutely no Problems; very good :good: Have to observe battery drain ;)

Good job, Andy!!!
[Galaxy S III Android Development] lkirra:
Can this kernel be use on the 4.3 beta of cm?

Really surprise me, i just visited the main boeffla site.

It had 3 kernels now..

I mean wow, another series of test!..hehe
[Galaxy S III Android Development] FlemishDroid:
It's for cm10.2 so yes.
[Galaxy S III Android Development] Tuga2010:
I tottaly agree. Best aosp kernel right now. Stable , smooth and almost without glitches in this ROM
[Galaxy S III Android Development] agam1308:
In slim beam 4.3 the light of hardware buttons is always on... I can't turn them off.

Sorry for my bad English.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] cink40:
Known, read some page back - Yank
[Galaxy S III Android Development] agam1308:
But yank has fixed this problem in his kernel, Andy maybe could do the same... :)

Sorry for my bad English.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] mikle_01:
Batterie drain seems high (higher as with Temasek Boeffla suport) - wlan is always on (but choose "not active" in Sleep mode).

12% without any use in 3hrs
[Galaxy S III Android Development] Egozy:
Get us a BBS (Better Battery Stats) log if you want any assistance
[Galaxy S III Android Development] mikle_01:
BBS

Here it is
[Galaxy S III Android Development] ImShadix:
Thanks, I like you reactivity
[Galaxy S III Android Development] Marashlim:
What is the difference between series 1 and series 2 on the download page? I'm on CM 10.1.3.
[Galaxy S III Android Development] andip71:
Series 1 is the older version of the kernel, which worked with the older Configuration App. This series is out of maintenance, although still works.

Series 2 is the current branch which is actively being developed, and requires Boeffla-Config V2.

In short: Take the series 2 branch, it is newer :)

Andi
[Galaxy S III Android Development] lchiocca:
Yep.. I meant the change info... sorry for that. I'm keen on getting the next beta... great thing!

EDIT: Tried to download the latest beta http://boeffla.df-kunde.de/sgs3/boeffla-kernel-cm/cm10.2_download/Test/ but the page is empty... well there is a disclamer but no content. Looked at the returned HTML but no files references.

The two profiles are simply put: {defaultProfile = Presets("Standard"); nightProfile = Presets("Battery saving"); nightProfile.gpu.freqProf = "54 only";}

I managed to notice that the GPU is probably the cause of the lag. When changing the gpu frequency profile from "160/266/350/440/533 (default)" to "54 only" it works instantly, but not the other way around. Somehow it needs a screen-off-on to get it working.

Just to give you a bit of background: I'm automatically sending an activity at night to change the profile and turn it back on in the morning when the screen is turned on.
[Galaxy S III Android Development] andip71:
First issue: I am currently uploading beta3 already, it should be up in around 15 minutes. That is the reason why currently the page is empty.

Second issue: Ok, it might very well be, the GPU needs a screen-off and screen-on again to apply the new settings sometimes. Could be a glitch in the GPU frequency/voltages interface. But as one day there will anyways be (likely) a new implementation for the newer mali drivers, it does not make sense to spend lots of time on that now (my opinion).

Andi
[Galaxy S III Android Development] andip71:
2.1-beta3 for all variants

Hi all,

new betas for all 5 kernel versions (cm10.1, cm10.2, cm11, cm11-r3p2, Omnirom) are out for you.

Version 2.1-beta3

04.12.2013

Correction to the charge level information interface (cover for periodical reset of soft regulation loop)

Enjoy

Andi
[Galaxy S III Android Development] lchiocca:
Oops... I read through four pages of posts and saw that you already posted the new version and saw another post saying "trying it now"... so I assumed... my bad.

Second issue: No worries... I can live with that. Just out of curiosity: are you using the mali drivers from update12?
[Galaxy S III Android Development] neoavi7:
:cowboy:

Lord, Out of curiosity which ROM you use as the daily driver. :)
[Galaxy S III Android Development] andip71:
My main S3 still runs on 4.1.2 XXEMG4 Samsung Stock rom (debloated) with my kernel.

For me still the best compromise of stability and functionality with best battery life.

Andi
[Galaxy S III Android Development] Boldizzle:
Hi Andi,

I'm running archidroid and Boeffla Kernel 2.1beta1 and quite frequently my read ahead buffer keeps setting both internal and external to the maximum setting.

I'll reset it back to 256 and can almost guarantee that within a few hours it will set it self back to maximum again.

Is there a reason why it would do this?

Thanks.
[Galaxy S III Android Development] andip71:
Tell me what you have in your init.d folder please, most likely you installed a mod or scripts causing that (i.e. Crossbreeder was one of them in the past).

Also, any other apps that can cause this?

In the log files you could see what settings are done by the kernel. But if lateron some other process comes and changes it... no chance.

Andi
[Galaxy S III Android Development] Boldizzle:
I haven't directly installed any scripts in this folder but I have definitely installed crossbreeder as part of the installation of this rom.

Here's a list of what's in my init.d folder.

I also unaware of any apps that I have installed that could cause this, I mainly listen to music and play games on my device.

I'll check out the logs if you could please point me to where they are stored?
[Galaxy S III Android Development] andip71:
You can see in the kernel start logs (boeffla-kernel.log files in /boeffla-kernel-data folder) to which values the kernel sets the buffers during start.

Do me one favour please: Remove the scripts from init.d for a test and you will see all is well. You can put them back again after it.

Andi
[Galaxy S III Android Development] Boldizzle:
Checked the logs and the kernel initially sets it at my preferred setting but as this is one of the first processes that applies during startup, any one of the init.d scripts could be causing it as they run directly after the kernel sets the setting.

Should I restart my phone now that I've temporarily moved the init.d scripts?

The other thing is, this just happens at random without even having restarted my phone so you could be right and an app I have installed may be causing it.
[Galaxy S III Android Development] muncheno:
Hi Andi ,

Recent update to beta2 & 3 solved my issue with solid explorer accessing ext. Sdcard.

I'm using now Cm11 v15 from termasek.

Thank you.
[Galaxy S III Android Development] andip71:
Good, I somehow expected that :)

Andi
[Galaxy S III Android Development] Xami:
Is it possible that you add Vibration intensity option in next update but it doesn't apply on call or notification vib. intensity
[Galaxy S III Android Development] andip71:
I still have the strong opinion, this should be rom thing to implement.

I remember on CM (or Slim...?) this option was possible.

Maybe in far future if no rom developer puts it in...

But so far I do not want to cause another conflicting settings option, I have it already with the MDNIE settings and I regret already I have done it.

Andi
[Galaxy S III Android Development] JustArchi:
Always poke rom creator firstly, especially if you're running heavily modified rom like ArchiDroid.

This "bug" has been fixed in this commit, 17 days ago. I can see it merged both in 1.X-STABLE and 2.X-STABLE branches so latest AD versions are fine.
[Galaxy S III Android Development] Xami:
Either way it's totally fine because Omni has neither vib. Intensity option nor MDINE option and thanks to your kernel for that so don't say that you did wrong
[Galaxy S III Android Development] Boldizzle:
Thanks Archi.

All fixed now! :)
[Galaxy S III Android Development] adripred:
Hi,

I found a problem in Boeffla-Config V2: The UMS option is unchecked sometimes when the usb cable is disconnected.

I´m using the 2.1-beta3 version in Temasek V15, but this problem also happened in 2.1-beta2 version in Temasek V14.

I did a full wipe before installing the latest version of the kernel and the Temasek rom.

Regards!
[Galaxy S III Android Development] andip71:
There is nothing I can do about this.

The app only controls some logic in the rom, and reports the status back. All the rest is outside of the apps control.

Unfortunately we have to live with it.

Andi

Gesendet von meinem GT-N8010 mit Tapatalk 4
[Galaxy S III Android Development] adripred:
Could you create an option in preferences to set this UMS option checked by default at startup?

Regards!
[Galaxy S III Android Development] shaarky:
Hi, is the latest version of Boeffla V2 config working for you on beta3 ?

Update : it is,restart solved it
[Galaxy S III Android Development] FlemishDroid:
Every time I update cm11 and I flash Boeffla kernel I have no wifi so I go back to recovery and flash boeffla kernel again and then wifi works again. It's not a big problem to flash it twice every time but I just want to let you know btw I had this problem also on CM10.2 nightlies. ;)

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Android Development] rel0k0:
I saw a few hours ago the last Beta version for CM11 r3p2 (cm2.1 beta3) and flashed it but after that the camera didn't work, I have the stock camera of v15 and Camera Zoom and neither of them work. I flashed again the previous version CM2.1 beta1a and now both cameras work again.

EDIT: none of them now are working, I tried wipe cache and dalvik but nothing, I tried flash again the kernel and nothing
[Galaxy S III Android Development] ddaflorez:
No gpu options for r2p2 version ?

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] MrxSiN:
waiting for sharpness fix on r3p2 mali. Damn. Screen really sharp. I can see its pixel.
[Galaxy S III Android Development] abhibnl:
How to disable soft key backlight on cm 10.2 by kernel side? I've disabled touchkey light from settings>buttons but it still luminates. :(
[Galaxy S III Android Development] andip71:
I could if I really wanted. But it is not recommended as UMS unmounts the SD Card from your system.

Second, Boeffla-Config is not doing anything anymore root-related during startup, so it would not be able to set an option like that without changing the design back to Boeffla-Config V1 again. And as we know, this design was not as stable as the new one.

So the answer would be rater no. You can still achieve it by putting an init.d script in for your specific requirement however.

Of course it is. Otherwise it would be broken and I try to not put broken things out :)

This is very interesting. I do not have that at all.

When you flash and it happens, how did you flash exactly? Via the Config App or other ways...?

I am on Temasek V15 with the 2.1-beta3 kernel. No camera issues at all.

Maybe you need to update your camera firmware, sometimes this helps. There is a dial code to open the menu for it, search... should be somewhere around in xda.

Exactly, not GPU options for the r2p2 and Omnirom versions.

I am still puzzled why people keep on asking this as it is stated in the change logs?

I think I will put something in red colour it to make it more prominent :silly:

Maybe you will wait forever. MDNIE settings have been changed quite alot, so not sure if I can ever implement it again.

And unfortunately the rule is still: I never use it, so I do not have strong motivation to spend days of work on it potentially.

Question back first: What all did you try already?

Andi
[Galaxy S III Android Development] abhibnl:
Well bro i installed stable cm 10.2 today. Flashed gapps> my fav boeffla beta3 all without restarting. To turn backlight off, went to settings>buttons>backlight and then disable it by unchecking the option "illminate buttons". But while touching soft keys, it still illuminates. That's all i've done to disable it.
[Galaxy S III Android Development] andip71:
Did you play around the settings in boeffla-config as well? Did you flip the switch between kernel controlled touch key backlight and rom controlled for instance?

Just tried it, and works as expected for me:

Set Touch led control to rom (= switch set to off).

Lock your display with hardware button on right hand side.

Now it should work.

Andi
[Galaxy S III Android Development] MrxSiN:
aww. that sad. that oversharp UI killing the beauty of KK. :)
[Galaxy S III Android Development] andip71:
Ask Hardcore if he plans to still do a kernel based on 4.3 with his sharpness tweak.

If he does, I can make it switchable again.

But I am personally not a MDNIE expert.
[Galaxy S III Android Development] abhibnl:
This is already set like the ss. Even then on touching soft key, it illuminates.
[Galaxy S III Android Development] andip71:
How exactly did you configure it in the rom?

Did you restart after all these changes?

Andi
[Galaxy S III Android Development] Roman91:
the battery with this kernel is really amazing!!!!!

but I have some question

1) boeffla sound is contained in boeffla config v2, then just install only configv2 for all settings?

2)the terrible lack of sharpness in related to the last mali driver?? so also with the stock 4.3 there is the same problem? or it's only a cm/omnirom problem?

3) resonance frequency of loudspeaker is too high for your speaker tuning. imho I think you must add a High performance option :Dwhere HPF is sett higher. Think must sett F3 at about 500hz:)
[Galaxy S III Android Development] andip71:
Roman:

1) yes, this is sufficient

2) it is result of the new MDNIE implementation, the old hack does not work anymore (same for Samsung 4.3, CM11-r3p2 and Omnirom due to same mali drivers)

3) I think this depends on the S3, resonance frequency is something which varies a lot, I have two S3 here and they sound also different. Impossible to make it perfect for everyone (apart from implementing a fully fledged parametric EQ for the speaker as well)

Andi