yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] ARCANAAA:
Im having the same problem, when i hit flash and load the downloadbar pops up for a half second then just dissapears and nothing happens anymore.. Where do i get the bc log so i can post it here

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Android Development] simono_pl:
[MENTION=947981]Lord Boeffla[/MENTION] is possible to use profiles from Boeffla application with Tasker?
[Galaxy S III Android Development] The Thug:
Something which I've noticed regarding the available free RAM on my S3.

Under Boeffla Config, I have 149MB available and after pressing my home key it reflects 213MB with the only app running being Boeffla Config

Why such a large discrepancy?
[Galaxy S III Android Development] Darkseth:
Heya.. Found an annoying Bug with the Boefflia Sound engine.

Using the latest Kernel with CM11, and on every Restart, the sound engine is deactivated, and the Headphone volume level is down to 50. (Yes, i use the option "load on start", but it gets ignoried).

Also, wenn im turning on DAC direct, DAC oversampling, and FLL optimizing, the FLL one is turning off itself whenever i scroll down, and back up.

Can anyone confirm that, or even know how to fix it?

Edit: Found it myself... Using Boeffla Config V2 app, which has an Boeffla-Sound part in it (i think that wasn't always). Anyway, using the Sound engine app is not working (for me), so there might be a bug or something
[Galaxy S III Android Development] VirusPT:
Hi,

Can I use the last kernel version on Temasek v24?

Or I need do upgrade the rom to a newer version?

Thanks.

Enviado do meu GT-I9300 através de Tapatalk
[Galaxy S III Android Development] ARCANAAA:
Wrong thread sorry

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Android Development] andrewwright:
Cm11 kernel works with aokp 4.4.2 rom. No FC ATM. Camera works too :thumbup::D didn't try omni yet.
[Galaxy S III Android Development] lchiocca:
Hi Andi,

Sorry for bothering you on your holidays... This is NOT urgent and the answer can wait, just in case.

Here my setup: cm11 (nightly 2014-01-05) with boeffla kernel cm2.1 beta9.

Here the issue: I don't like the capacity buttons to light at all (I know where they are and really don't like them to light up). So I disabled them in cm (settings->buttons->backlight->Illuminate buttons=false). But when I do that the button timeout seems to be infinite instead of zero. If I use the standard cm kernel, then it works.

If you have any idea if I'm doing something wrong, I'd be glad to know.

Thanks for this wonderful masterpiece of yours!

Loris
[Galaxy S III Android Development] drgreenth:
Use boeffla config app and from led+display section disable option kernel controls lights (for buttons) if thats what u mean..
[Galaxy S III Android Development] jonjonthegreat:
HI all,

I would like to know if UMS mode under Boeffla-Config V2 is working or not.

I came from 4.3 XXUGML2 firmware before going back to SlimBean 4.3.build.2.2-OFFICIAL-1743 because it lacks UMS functionality.

Before flashing the latest Samsung ROM, I had SlimBean and Boeffla Kernel setup. UMS working properly back then.

Please note full wipe was performed before flashing SlimBean and Boeffla Kernel.

If this was answered before, please point me to the right direction as I searched with no results.

Thanks in advance!
[Galaxy S III Android Development] szkrable:
Sametimes I have boot loop. Temasek 4.4.2. Kernel beta 9.

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] SuperAce609:
Sorry for the noob question, but which kernel version for Super Nexus (AOSP)?
[Galaxy S III Android Development] MBurns2:
sorry if i go a little off topic.

I was trying stock pegasusq governor, i see that it use 3 or 4 core for most of the tasks.

I noticed that my cpu stay on low frequency if it use more cores.

this doesn't allow to save more battery than work on higher freq with only one core ?

Maybe is it only my impression (that pegasusq stock use lower freq for normal task)?

I noticed that pegasusq boeffla moderate/battery use less core but stay on higher freq.

Thanks for answer !!
[Galaxy S III Android Development] tisazalay:
Yes, you can use the latest (Omni 2.1 b9a), it will work on v24.

It's advisable to update ROM (it's v29 already) if you can.
[Galaxy S III Android Development] titijuli:
As far as I know UMS will be available in the last boeffla config app only if the version of your kernel is supporting this feature. otherwise will be hide.

Enjoyneering
[Galaxy S III Android Development] andip71:
Sure you hit test and not stable version?

There are no official stables yet.

yes, look into documentation how to do it. I described what you need to setup (a special intent to be sent).

No, cannot fix it. Boeffla sound control app is a third party app not developed by me.

Please contact Simone201 for this.

Other open questions will be answered of course when I return next week.

Best wishes from holidays

Andi

Gesendet von meinem GT-N8000 mit Tapatalk
[Galaxy S III Android Development] ahmed.haggag:
i cant use it on latest probam, its CM based
[Galaxy S III Android Development] andip71:
Ahmed, whazis the effect?

In cm10.2, Probam was explicitly not supported because of a proprietary framework included.

Maybe it's the same again now with CM11.

Cannot look further into it currently as I am away from home these days.

Andi

Gesendet von meinem GT-N8000 mit Tapatalk
[Galaxy S III Android Development] n0stalgia:
Any way to control the hardware (analog) sound volume directly with the volume rocker?
[Galaxy S III Android Development] ktmbikerman:
Someone reported "yes", a few pages back
[Galaxy S III Android Development] lchiocca:
Sorry that I didn't mention it, but I tried all the possible combinations:

Touch LED controlled by kernel=off & cm Illuminate buttons = false -> LED always on

Touch LED controlled by kernel=off & cm Illuminate buttons = true & cm timeout=1sec -> LED on for 1sec

Touch LED controlled by kernel=off & cm Illuminate buttons = true & cm timeout=3sec -> LED on for 3sec

Touch LED controlled by kernel=on & cm Illuminate buttons = false -> LED on for 3sec

Touch LED controlled by kernel=on & cm Illuminate buttons = true & cm timeout=1sec -> LED on for 1sec

Touch LED controlled by kernel=on & cm Illuminate buttons = true & cm timeout=3sec -> LED on for 3sec

As soon as the cm "Illuminate buttons" is turned off, the key backlight is always not what I would expect.
[Galaxy S III Android Development] andip71:
Set min cpu frequency up to 400 and it should work for you with zzmoove as well.

Known effect, will put this into faq section soon...

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] simono_pl:
I think it is general, also for pegasusq (on this governor I have also sometimes problem while listening music). I will test with profile switched from Tasker (profile with min CPU 400MHz), I want solution for listening music using BT headphones.
[Galaxy S III Android Development] djclark25:
I installed ProBAM KK 1.2.3 yesterday to give it a try and running the latest beta 9 of the CM11.0 kernel and no problems here so far. All running really well with great battery (So far)
[Galaxy S III Android Development] andip71:
It is a general setting.

But zzmoove clocks very low when screen is off, so it has good effect here.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] andip71:
You tell us :)

You should not have a big difference, if any at all.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] ZaneZam:
Hi m1l4droid,

the zzmoove battery profile has pretty rough screen off values, it's purpose is to save battery as much as possible of cause at cost of performance.

instead of rising min freq to 400 u could also try to rise zzmoove freq limit to for example 800mhz and/or turn on Fast scaling sleep to 4 and/or lower up threshold sleep to 85 or lower. in addition u could use a value of 2 in sampling rate sleep multiplier. one, some or all of that changes should fix your problems...

or simply use yank battery profile it's well balanced and the difference to battery profile should not be that much ;)

I guess I should make this also somewhere sticky in my thread as I think I wrote this the fourth time yet, will search for the best version and link it :)
[Galaxy S III Android Development] stuckedinsweden:
How to install???

I cannot for the love of me find any kind of help on how to install this?

I want the CM11 latest beta version installed:

So, from http://www.boeffla-kernel.de/ I download...? and install what?

I mean, I see there are two files, a .zip and a checksum file...

I guess I just download the .zip file to my internal sd card on phone and flash via CRM?
[Galaxy S III Android Development] GoodSoul:
Titel: [KERNEL] [I9300] [CM11.0/Omni/CM10.2/CM10.1] Boeffla-Kernel 2.10 stable (27-12-2013)

I guess you need to update your Compatibility section [MENTION=947981]Lord Boeffla[/MENTION] . ;)
[Galaxy S III Android Development] scorpionhd2:
Hey guys this seems like a great kernel, and I wanted to know if it supports fast charge. I searched but didn't see anything about that.

Thanks in advance
[Galaxy S III Android Development] karwankar:
You can change charge current both AC and usb
[Galaxy S III Android Development] andip71:
In short - yes.

You can configure charge rates of ac, usb and wireless charging as you want in the config app.

... And more of course.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] ahmed.haggag:
nothing happened, when i try to run the config app i got the its not compatible msg, i like probam but i guess im gonna install another rom that supports ur kernel i got used to it, its a must have kernel :D

---------- Post added at 03:58 AM ---------- Previous post was at 03:57 AM ----------

u mean the built in kernel? yeah its good but im used to boefella kernel :D

---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------

no its not working here, i got the incompatible kernel msg
[Galaxy S III Android Development] djclark25:
No, I am running boeffla kernel, the latest cm11.0 beta 9 version. Installs fine and runs perfectly!
[Galaxy S III Android Development] MrxSiN:
I'm curious about sharpness in Omni Kernel. The sharpness is too sharp. Than I'm trying CM kernel on Omni. Sharpness good.
[Galaxy S III Android Development] andip71:
Easy: Omnirom kernel has update 13 with the new mdnie tables included, hence the sharp and crispy display.

Cm11 still uses the older tables.

In Omnirom kernel you can try to enable the sharpness tweak option to make it look a bit less sharp.

Andi

Gesendet von meinem GT-N8000 mit Tapatalk
[Galaxy S III Android Development] ahmed.haggag:
strange! mmm...

maybe ill flash probam again and give it a try
[Galaxy S III Android Development] endymion2k5:
I see two options under the boeffla sound tab, within the boeffla config v2 application (omni 2.1-beta9a, slimkat). Those options are called 'DAC Direct' and 'DAC Oversampling'.

What do these options do?

Do the options work on a headset or the main speaker?

Thanks in advance
[Galaxy S III Android Development] andip71:
The options are explained in the documentation.

And they work on the headset.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] endymion2k5:
Yes im sorry, found it :S (my bad)
[Galaxy S III Android Development] NickName98:
which version of this kernel with resurrection remix?
[Galaxy S III Android Development] andip71:
Depends on which base resurrection is built on.

General advice: try Omnirom kernel first, uf it does not work, take cm11 kernel.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] krugdenis:
Great kernel, but latest beta not working correctly with latest cm11 nightly on my device. It's just freezes every second, device is completely unresponsible :( don't know why, maybe there is a trick to make it fly again?
[Galaxy S III Android Development] andip71:
No such a problem for me with latest beta.

Reset your configuration to defaults, just to go sure.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] krugdenis:
I've deleted boefffla config folder before flashing, and one question: is it necessary to clean init.d before flashing kernel?

EDIT: Solved, deleted hidden boeffla folder in /data and reflashed kernel :)
[Galaxy S III Android Development] lchiocca:
Hi Andi

Sorry to bring this up again... Were you able to reproduce it or is there a something I can provide that might help solve this? I've also tried this on omnirom but getting even weirder behaviours.
[Galaxy S III Android Development] Choristav:
Andi, did you change anything related to UMS in the .9a beta? I'm afraid UMS stopped working for me (as in, the checkbox stopped sticking whatsoever, so I can't enable it longer than a few seconds, it gets reverted immediately.). I reverted back to .8 and it's working fine now.
[Galaxy S III Android Development] simono_pl:
Is save to use this kernel with Xposed framework on CM11?
[Galaxy S III Android Development] andip71:
Hi,

not by intention. But very likely, due to the new ramfs, the internal device pathes have changed (was same with Samsung 4.3 kernel).

So I will check and if it is the case, will fix it for the next version (planned for maybe tomorrow).

Andi
[Galaxy S III Android Development] drgreenth:
Hi Andi! Have you thought about f2fs support? Its soooo fast!
[Galaxy S III Android Development] NickName98:
omni version seems to work great :victory:

thanks!

nice work!
[Galaxy S III Android Development] andip71:
Any reference for me?

Andi
[Galaxy S III Android Development] ahmed.haggag:
headset :)
[Galaxy S III Android Development] drgreenth:
Derteufel is implementing f2fs to devil kernel so his github might give you some hints. Or merge his source and credit him? Ive heard that f2fs makes these phones FLY. I mean literally.
[Galaxy S III Android Development] sqlpro:
last time i tried settings (phone settings) crashed on me and few other issues. can you check everything works even after another reboot ? also try go into settings (NOT boeffla settings) and about device.

Thanks.
[Galaxy S III Android Development] NickName98:
you're right

it crashes... :(

but, is that really an issue?
[Galaxy S III Android Development] Choristav:
Understood, I'll lurk to find your newest beta.
[Galaxy S III Android Development] sqlpro:
May be,may be not. I dont know. It means that its not fully compatible and may have side effects . Ofcourse andi would know better.
[Galaxy S III Android Development] krugdenis:
Hi, Andi. Yesterday I've posted about lags and stuttering on my device with latest cm11 and boeffla kernel, and after resetting settings everything was back normal. But now I've played a little with presets and noticed that phone become very laggy and slow after switching to "power extreme" preset. I know that my device can handle this settings, because I've used it with stock Samsung firmware and boeffla for Samsung kernel. But seems that cm11 doesn't like this kind of overclock.
[Galaxy S III Android Development] ImShadix:
For temasek is the CM11 Kernel ?
[Galaxy S III Android Development] andip71:
Not yet, have no CM based rom currently on my dev device as I am about to bring out a new Sammy kernel first.

After that, I will look into it.

Yes, I have thought about it. But not planning for it due to the following reasons:

- partitions need to be reformatted -> far away from stock and hence against my objective to stay close

- the reformat can only be done in a special recovery, I do not deliver recoveries like DerTeufel and do not plan to do

Yes, it might be with the new mali drivers you still need a bit more GPU voltage. You could try to first select the power extreme preset, after that increase GPU voltage even by 25 or 50 mV more. Or maybe less, you have to play a bit with it I guess.

Also you could try to move from lulzactiveq to pegasusq, which seems to be improved a bit.

No comment, I never installed resurrection remix so I do not know this rom.

I test on CM Nightly, Slim, Temasek and Omnirom. There everything works.

Andi
[Galaxy S III Android Development] andip71:
No, take the Omnirom kernel for Temasek.

Almost all custom roms switched over to Omnirom base.

Omnirom Boeffla-Kernel for:

- Omnirom

- Archidroid

- Temasek

- SlimKat

CM11 kernel for:

- CM11 nightly

Andi
[Galaxy S III Android Development] ImShadix:
OK thanks :)
[Galaxy S III Android Development] ikador:
Boeffla kernel that I installed the capacitive buttons light off :(

Rom:fousion boeffla
[Galaxy S III Android Development] andip71:
Did you read in the documentation and set your settings correctly in Boeffla-Config?

Andi
[Galaxy S III Android Development] ikador:
Yes andi

Boeffla config settings exist in this

case?

The problem was solved

Thank andi :D:p
[Galaxy S III Android Development] xzork:
Would you like to add double tap to wake feature to this kernel ? Thanks.. I'm on temasek rom CM11
[Galaxy S III Android Development] andip71:
xzork, if you use the search function in my threads, you would know: Already answered a few time.

No, this is not (in a usable way) possible due to S3 hardware limitations. Please look up for the detail explanation via search.

Andi
[Galaxy S III Android Development] ZsDaniel:
What do you think about SuperNexus?

If it's CM based what would happen if I flash the Önbizalom kernel?

Thanks!

Tapatalked from SGS3
[Galaxy S III Android Development] andip71:
Either it boots and works fine. Then you could stay with it.

If you have a boot loop, you just flash the CM11 kernel and then it should work.

So, worst that can happen is a bootloop which you can escape by flashing the other kernel.

Andi
[Galaxy S III Android Development] dhirend_6d:
I finally found out why my setting in the Governor I/O tab gets reset.

Case : - Using Temasek v31 with latest Boeffla Omni Kernel.

Governor, Pegasusq standard.

Scheduler, row for both internal and external SD.

ZRAM, Enabled.

Boeffla Sound, Enabled.

All else is default values.

Test and problem : -

1) Installed Smart App Protector from market.

2) Added Boeffla Settings v2 app into locked apps list with values as stated above.

3) Exited app, cleared everything from recents list. Additionally started lots of other apps to make sure Boeffla app is removed from RAM.

4) Started Boeffla v2 app, entered key to unlock app (which took about 5 - 10 seconds).

5) On opening the app, found that the settings in Governor I/O tab are different, i.e. governor set to lulzactiv and scheduler set to cfq, cfq.

I don t know whether its just cosmetic or does it actually gets changed. Attaching log in few minutes.

EDIT : - Don t know whether it is correct or not because I made the logs using CATLOG app from PlayStore. Logs attached.
[Galaxy S III Android Development] xzork:
Ok.. Thanks for your answer.. Sorry for not searching..
[Galaxy S III Android Development] andip71:
2.1-beta10 for Omnirom and CM11 Boeffla-Kernel

Good morning,

after releasing the new kernel for Sammy based roms, here comes the same for both Omnirom and CM11 Boeffla-Kernels:

Version 2.1-beta10

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

Fixed UMS mode

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

Initramfs updated to version of 14.01.14

Compiled with December 2013 linaro toolchain

Enjoy

Andi
[Galaxy S III Android Development] lchiocca:
Hi guys,

I've got a really stupid question (for which I googled first and search the forum as well). As you might guess, I've got a i9300 and was playing around with the early suspend delay and set it to the max. Naturally the crt-effect took place but then something looked weird. The screen was black, but not completely black. That intrigued me and I started to play around and displayed a complete black (#000000) picture. It "looks" black, but when seen in the darkness you clearly see that the screen is still emitting some light. That's what I would expect from a lcd display but not from an amoled one. Does anybody have an explanation?

Thanks

Loris
[Galaxy S III Android Development] Kord:
Hey!

[MENTION=947981]Lord Boeffla[/MENTION]

I know that you ended developing for CM10.2, but I found bug with display. SharpnessTweak is tuning off always, when screen is turned off. Also I'm checked settings in Boeffla Config and the button, even when ST was turned off after screen off, is still marked as "on". And what is strange, the button, after screen off, is replaced. I mean, to turn on ST i must turn it off. After next screen off, button is again replaced.

Also, I don't know why I have numbers instead of text in Mdnie scenario

SS:

https://www.dropbox.com/s/1wrtaf7z9fca4ee/Screenshot_2014-01-15-12-27-54.png

Regards :good:
[Galaxy S III Android Development] andip71:
Hi,

thanks for reporting this. As almost everyone moves on to CM11 / Omnirom meanwhile, I ended development on the CM10.2 kernel.

Personally I never encountered this glitch, however I also never use sharpness tweak (my opinion on it is widely known). So please understand, I will not investigate anymore on 10.2 issues.

About the numbers in the MDNIE display: This was changed in the app with version 2.1.3 of the app, and also communicated in the Google Play change log for it. Reason was, there is no common translation of the codes to meanings across various firmwares (Samsung, CM, Omni etc.) and different MDNIE implementations. So I decided to just provide numbers as anyways all options need to be tried out to find the personal preference.

Thanks

Andi
[Galaxy S III Android Development] Kyle07:
Great update. Running smoothly on SmartassV2 so far. Thanks!
[Galaxy S III Android Development] alexferdean:
Is there a way to make Real Racing 3 audio work good in CM11? Or maybe the game needs to be updated to 4.4? Is terrible now.

Sent from my S3
[Galaxy S III Android Development] dhirend_6d:
Ofcourse it emits some light its natural. :D. Only if you see in complete darkness you will notice it. If you don t turn off the screen, it still is using power. Its not a black body is it. :P
[Galaxy S III Android Development] lchiocca:
But isn't the idea of an amoled, that when the entire screen is black that it doesn't consume anything (because it doesn't have to actively enable any leds)?

EDIT: In case you're wondering why I've posted this in this thread: this is probably something in the kernel and if boeffla kernel could be even less power consuming then it would be perfect! :)
[Galaxy S III Android Development] Gastozz:
deleted
[Galaxy S III Android Development] andip71:
Gastozz... this picture does not say anything.

We need to know: From which level to which one was the battery going in which time?

What was the screen on time?

What does BetterBatteryStats say?

Which version of Temasek are you using?

Which version of the kernel?

....

....

Andi
[Galaxy S III Android Development] raphman:
Hi Boeffla Lord,

First, thanks for your amazing work. I just noticed on the changelogs the following mentions :

http://boeffla.df-kunde.de/sgs3/boeffla-kernel-omni/cm11/changelog.htm =>

Note: Use this kernel for Temasek CM11 and also for SlimKat !!

http://boeffla.df-kunde.de/sgs3/boeffla-kernel-cm/cm11.0/changelog.htm =>

Note: If you use Temasek inofficial CM11 or SlimKat, do not use this kernel but the Omnirom Boeffla-Kernel !!

I have installed the CM11 kernel over the unofficial temasek v31, without any problem at all.

Please can you explain why it's better to use the omni one ? What are the differences between the two kernels ?

Thanks in advance,

Bests,