yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] rensen:
Thanks simone201, too. Super work.

Stanley08

You need to add some more data.

You ave keep battery saving option activated?

Only 2g? in the conection?

And the brigthness?

Wat the congif of your kernel...

I are now with a rom stock, ELLA, 19 hours of activation, 55% battery and 3:30h of screen...brightness at the minimun and with some times battery saving option activated. ( cpu and screen )

Appart, nice new options in the new tool of kernel..maybe a good idea a COMPLETELLY wipe, system, data, cache, all...some people only ave the stock recovery...

Thanks, still trying.

A greeting here to all.
[Galaxy S III Android Development] massaro33:
Re: [KERNEL] [Samsung JB] Boeffla-Kernel 2.6 (17-01-2013)

Where can find apps for adjusting boefla kernel? ty !
[Galaxy S III Android Development] ahac85:
Re: [KERNEL] [Samsung JB] Boeffla-Kernel 2.6 (17-01-2013)

Hands down this is the best kernel. Battery life is amazing on default settings. My s3 is sleeping extremely well lol. Loving the phone again.

Also if I don't adjust speaker sound settings and I've edit the defaultgain.conf file manually using the gvm app which controls the sound volume will those settings be applied or does the kernel keep it as 57 stock?
[Galaxy S III Android Development] bcs2112:
Hi Andi ,

Is there any chance to make "led fading effect" working properly by the stock applications?

--

regards,

bcs
[Galaxy S III Android Development] andip71:
Hey rulala, no reason to be worried. Your english is just fine. Believe me, sometimes I get mails where I do not understand anything. With you it is quite easy to understand.

Many many thanks! Appreciated, very much!!

Thanks for the suggestions. Will think about it, but as I do not have control on the tweaks app (as much as I want), I cannot put a confirmation window in. So it is too dangerous for things like wipe.

But I more and more consider to do my own tweaks app, then this can be in.

Just (after your reboots two times) look in your app drawer, the app is called "boeffla-tweaks".

Thanks for the feedback. If you never activate boeffla-sound (means no changes in the boeffla-tweaks app or the config file), it never touches anything as it is then switched off. So, the value from the defaultgain.conf file should be taken.

But bear in mind, I read many times this does not work anymore with firmware versions XXELLA or higher.

So, I would recommend to forget about this "old way" of doing it and just use the boeffla-sound features for it.

By that you have much better control on it.

Honestly, I do not know. And it is probably not very likely.

I do not know currently (needs further investigation) what Samsung does different with their stock apps. Maybe they trigger the LED in another, undocumented way. So, I cannot promise this can be done currently.

(or do you think it is kernel related, do you know another kernel where it works with Samsung stock apps? that could speed up things)
[Galaxy S III Android Development] ahac85:
Re: [KERNEL] [Samsung JB] Boeffla-Kernel 2.6 (17-01-2013)

Correct', on ella the mod didn't work but on ellc the old way works again. But thanks anyway
[Galaxy S III Android Development] rab1412000:
Re: [KERNEL] [Samsung JB] Boeffla-Kernel 2.6 (17-01-2013)

On 2.6 stable since yesterday. Haven't gotten to testing it much but I believe I'm noticing slightly better wifi.

Andi, is it possible to add a core switcher for those who want to use less than 4 cores?

Sent from a Galaxy far, far away
[Galaxy S III Android Development] Steve46xda:
R: [KERNEL] [Samsung JB] Boeffla-Kernel 2.6 (17-01-2013)

Great results for the first cycle!

75% wifi 25% 3g, uv cpu -100, uv gpu -50, few games, internet...

Inviato dal mio Galaxy SIII!
[Galaxy S III Android Development] doki81:
Re: [KERNEL] [Samsung JB] Boeffla-Kernel 2.6 (17-01-2013)

After update to the new sound app. Dont know why my system hang after boot up. Then it will auto restart.

Just uninstall the app then wipe cache and now system is back to normal. I am using the app along with 2.7 beta 1.
[Galaxy S III Android Development] drakester09:
Re: [KERNEL] [Samsung JB] Boeffla-Kernel 2.6 (17-01-2013)

Same happened here. :(

Phone started to lock up out of nowhere... Thought I had SDS :( then I isolated the issue to the app
[Galaxy S III Android Development] stanley08:
You guys should not undervolt, i have found out that even if you undervolt, your battery life will remain pretty much the same thing. I have done several tests! UV to me is not the best way to save battery.
[Galaxy S III Android Development] doki81:
Re: [KERNEL] [Samsung JB] Boeffla-Kernel 2.6 (17-01-2013)

ERM...then what shall we do?
[Galaxy S III Android Development] gsw5700:
Re: [KERNEL] [Samsung JB] Boeffla-Kernel 2.6 (17-01-2013)

UV saves very little battery life, maybe 2% I read somewhere. The advantage is a cooler running phone. My own phone can take -100mV for cpu and -75mV for the gpu but I only uv the cpu by -50 and gpu by -25 for stability

Sent via TCP/IP
[Galaxy S III Android Development] pabgar:
Sorry but you contradict to yourself. Cooler running processor and/or GPU means less power dispersed into heat = less battery consumption. This is physics.

I don't know if it is 2% or 5%, but I strongly believe, that it depends how you use the phone.

I suppose that for light user undervolting has no special use as CPU and GPU mostly spend time in deep sleep and battery is consumed by other hardware ( i.e. radio ) so there is no gain from lower power level.

For heavy user frequently pushing CPU and GPU to it's limits undervolting is more significant.

But that is only my speculation :)

So maybe for one undervolting means 2% battery gain, for other 5% but all that power saving policy is based on gaining together small advantages.
[Galaxy S III Android Development] simone201:
R: [KERNEL] [Samsung JB] Boeffla-Kernel 2.6 (17-01-2013)

The sound app doesn't even start during boot, but after boot is finished, so it is something else

Inviato dal mio Nexus 7 con Tapatalk 2
[Galaxy S III Android Development] Cosolord:
Cifs is working on beta1 (i was on beta1, skipped beta2). Upgrading to beta3 i have found this issue. And yes, i use the same path (/mnt/cifs/).

Now i'm back to beta1 without any problem to cifs. Thank you Andi :good:
[Galaxy S III Android Development] Zeus1098:
Sorry load and flash wasn't working
[Galaxy S III Android Development] andip71:
Hmmm, as said. I just used CIFS fine with beta3.

How do you use it? Using CIFSManager app? What is your error message?
[Galaxy S III Android Development] andip71:
Ok, thanks. Sorry for asking, but with many hundred users asking all kind of different things I cannot recall every individual again.

So, I can see already the App is not allowed to write to the sd memory. As I even cannot see log files created by the app. So this is the problem, because of course the kernel needs to be written to the sd memory as well during download.

So still, something is blocking it.

Could be apps and frameworks like XPrivacy etc. But what exactly, I cannot see unfortunately.

Please go through all your apps and check if you have apps installed that can block other apps in any way.

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

I downloaded and diffed the code. It is not massive, but some interesting changes done.

For those more interested in technical details, here are the changed files:

arch/arm/include/asm/assembler.h | 12 +++-

arch/arm/include/asm/domain.h | 8 +--

arch/arm/include/asm/futex.h | 8 +--

arch/arm/include/asm/uaccess.h | 56 +++++++++++-------

arch/arm/kernel/perf_event.c | 11 +++-

arch/arm/lib/getuser.S | 27 +++++----

arch/arm/lib/putuser.S | 34 ++++++-----

arch/arm/lib/uaccess.S | 82 +++++++++++++--------------

drivers/net/wireless/bcmdhd/include/epivers.h | 2 +-

drivers/net/wireless/bcmdhd/wl_cfg80211.c | 7 ++-

kernel/power/wakelock.c | 3 +

Hence, I decided to give it a go and merged this SEA Update2 in my kernel. So next beta4 will base on SEA Update2 codes for a test.

So far, but it might be placebo, the phone feels snappier. But we will see.

If will give it a few more hours sanity checking, then I could publish beta4 even.

Andi
[Galaxy S III Android Development] gieffe22:
well...i think it's time to going back to boeffla kernel :fingers-crossed::laugh:
[Galaxy S III Android Development] Cosolord:
I use CIFSmanager and with beta3 i can mount the directory but it is empty. Same steps with beta1 but in this case i can see my files. :confused:
[Galaxy S III Android Development] andip71:
Nooo noooo. I think F2FS is much more important to you, isn't it? ;)

Hm, very interesting thingy. I just copied successfullly 200 MB over CIFS.

Next question: What basis is your firmware? I am on UGNA7...

Andi
[Galaxy S III Android Development] viktor92:
I'm running the CPU at 1.5ghz with -100mv UV, and GPU stock with -100mv UV. With the same settings since many month ago, I've never experienced any freeze or reboot running antutu and everything with Googy Max or Yank kernel. To be more specific, the first freeze was with a broken screen in the 3D test and with beta 2, the second was when antutu showed the bar results, folowed by a reboot, but this time with beta 3 linaro. The weird thing is allways all antutu numbers are very good, except the 3D test (this is the area with the biggest improvement from 4.1.2 to 4.3 rom as I could see) where the results are very poor and ruins the final score.
[Galaxy S III Android Development] Abo3mood:
-100mv for GPU is really hard
[Galaxy S III Android Development] andip71:
Sorry Victor, but if you test with heavy undervolting.. what should I say?

It does not surprise me if you get freezes...

So sorry I am a bit harsh now, but stating the OP:

I will refuse to give support if you do any undervolting and experience freezes or hot reboots.​

Try again without undervolting pls.

Andi
[Galaxy S III Android Development] gieffe22:
...eheh,new sources compensate for f2fs :p ...your kernel is more "refined" in general(more governors and lmk...but if someday you will use this f2fs...ahahah,this is the end of the world friend!)...

...so i wait for your new beta and turn back here!
[Galaxy S III Android Development] Cosolord:
I use the last omega rom (ugna7) and usually i flash your last kernel over the previous version wiping cache and dalvik cache before and after.

It's so strange. Omega rom flashed with a FULL wipe...

I try again with beta3 (this is 4th time). Thanks for your help, Andi.
[Galaxy S III Android Development] andip71:
Weird stuff. Please also try beta2, I just enabled it again in the download section for you.

Would be interesting to pinpoint where potentially the issue is.

Andi
[Galaxy S III Android Development] Cosolord:
Done !

Thank you Andi. I have flashed before beta2 and after beta3 and it works (don't ask me why eheheh).

Thank you again :highfive: :good:
[Galaxy S III Android Development] andip71:
Weird stuff... but ok. Glad it works.

Sometimes, not all things can be explained unfortunately.

One of the biggest Pro's of Android sometimes is also one of the big problem - due to its flexibility and open approch so many things can change and potentially go wrong, side effects, conflicting stuff.

It is much different in the closed Apple ecosystem - but, who wants that??? :D

Andi
[Galaxy S III Android Development] Cosolord:
holy words !!!
[Galaxy S III Android Development] PIRATA!:
Thank you very much.

So no easy way to identify them in the /system/xbin/ folder watching at them? Is it something regarding their contents, their properties, their names?
[Galaxy S III Android Development] andip71:
With the right app (in my case Root Explorer) it is very easy.

You can clearly see, the files are pointing to busybox instead of being real files.

Andi
[Galaxy S III Android Development] malachow:
[MENTION=947981]Lord Boeffla[/MENTION]

May I have a question? ;) Let's imagine such situation - my headphones are stick in, I'm listening to music & suddenly a call comes, music stops playing and I hear ringtone in my headphones and S3 speaker too. I know, that in Boeffla Config I can set privacy mode ON which disables ringtone in speakers, but is it possible to make something totally opposite? I mean mode which would prevent ringtone playing through headphones but only in device speaker.

Thanks for any reply. :)
[Galaxy S III Android Development] andip71:
Malachow, yes, this is technically possible.

Currently, the speaker amplifier is switched to 0 when a call comes in to achieve that.

The same could be done with the headphone amplifier. But - it will then also stop music etc. during that time, so the headphones would be completely "dead" when a signal comes in.

Andi
[Galaxy S III Android Development] malachow:
That's the solution I was looking for, cause I knew it would be impossible to play music at the same time along with ringtone through device speaker.

But... now another question appears - how can I configure my own Malachow-privacy mode? I mean I'm not able to see any amplifier value change in Boeffla Config. :)
[Galaxy S III Android Development] andip71:
LOL, well... I said - it is technically possible. I did not say it is possible NOW.

For this I need to include some more logic into the Boeffla-Sound Engine to take care of that. Let me put it on the list for a deeper technical check, ok? If it is simple I will put it in one day, otherwise I come back with the news to you.

However, please do not expect something soon, I am not at home a lot in the next 2 weeks. So minor to none time for proper programming.

Andi
[Galaxy S III Android Development] malachow:
Sorry then for bothering you, I didn't mean it. ;) I've just misunderstood words "technically possible", nothing more.

Again, thanks for help, I'll calmly wait for any solution in future.

P.S About expectations & hope.. In times when month by month I see some great devs stating they stop support for our S3 I generally use to not to expect much for my outdated device. :cowboy:
[Galaxy S III Android Development] andip71:
It is good. I still have my S3 these days, and I will not stop developing it until I have a new phone. Even then, let's see.

There must be a few devs left, right?

As said... will look into it once I find some time again. Currently I can only do some minor work, such as updating the app from time to time and implementing small things into the kernel.

But still...

Andi
[Galaxy S III Android Development] ahac85:
Hi Andi im currently on mk6 stock with boeffla 5.1 stable, can I flash latest beta to stock mk6 or will I have compatability issues?

Also for those who flash different region roms do you guys change anything like csc? Ive always flashed btu roms ie uk releases, but im really wanting to flash the latest arab na7 firmware, just worried if something will go wrong?? So what am saying is Any downside to flashing to different regions?

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

I do not expect issues on mk6 based firmware, but I would still encourage you to step up. MK6 is quite outdated in our (nerd) terms :)

And on CSC: As long as you flash a CSC which contains your desired product code (for instance I also flash BTU most of the time, as it contains product code DBT for Germany), you should be fine with BTU.

In fact, it might even open up Google play a bit more than with an Arabian CSC (not sure though).

CSC and product codes are only required for KIES and Google Play store afaik. But maybe some rom expert can kick in and elaborate even more.

Andi
[Galaxy S III Android Development] viktor92:
Ok, I've tried antutu again without any UV and it ended without problems with a score of 19775. Then tried again with -100mv at the CPU and the score was 20779 (?!?!). So two things are evident: antutu isn't very reliable (...), and the weird 3D behavior was due to GPU UV. Now I feel a little stupid (to say the least) but I obviously knew the potential unstability that would cause the UV that I've made, but never experienced any problem before, even running antutu. Anyway all is working fine now... :o
[Galaxy S III Android Development] andip71:
Viktor, no need to feel stupid or sorry.

Most important is: It works!!!

Second: Yes, Antutu is not reliable. No benchmark is really reliable. I wrote many times I do not care about benchmark scores +/- 1000 or 2000 as they are within tolerances. Android is a heavily multitasking OS, so it is normal external events can trigger and impact the result.

However, if you would only reach 10000, I would of course look into that.

UV is always a very touchy thing. It can work fine, it even can work fine for a long time. But see, we all are getting older, so do our devices. Not joking, over lifetime of a device some parameters change. So things that worked fine a year ago might not work anymore as you were hitting a threshold meanwhile, due to aging.

Third... other kernels have different other code, tweaks, etc etc. So running -100 mV fine on one kernel does not mean it will run on any other. They are too different in some ways.

My kernels for instance are known to be patched rather conservatively, I upstreamed to Linux 3.0.101, but basically from patching point of view thats it. I only add features.

So... as you can see... many reasons and possible explanations.

However - all that counts is: It works for you now :)

Andi
[Galaxy S III Android Development] gieffe22:
[MENTION=947981]Lord Boeffla[/MENTION]

ey ey!i'm wrong or in test kernels is out the beta 4?...is the SEA2 new one or i miss this release?

EDIT

i see in changelogs that is the new one *_* ...downloading ;)
[Galaxy S III Android Development] andip71:
5.2-beta4

Hi all,

maintenance update after Samsung released a new source drop for the SEA region last night.

Version 5.2-beta4

Implement Samsung source update GT-I9300_SEA_JB_Opensource_Update2 from 14.02.2014

Enjoy

Andi
[Galaxy S III Android Development] bouighil:
Please where can i find andy's profile for 4.3?
[Galaxy S III Android Development] Hidden-Hunter:
Hi Andi

Sorry for many questions

I do not play games , if i use UV Medium for Cpu and Gpu , No problem for my phone? and UV effect for battery saving?

Thanks:highfive:
[Galaxy S III Android Development] Frozenblade33:
No one can tell for sure.

Andi adviced many time to avoid UV

I guess you can try and in case you have problems then dont use it.
[Galaxy S III Android Development] andip71:
Link to the profiles exchange thread is in the OP.

It is easy: Every S3 reacts a bit differently to UV. So some can undervolt more, some less.

If your phone runs stable with medium undervolting, then you are fine. It is not a problem for your phone, the worst that can happen is freezing or hot reboots.

The effect of undervolting for battery is marginal, you can forget about it more or less. That is why I personally do not undervolt anymore and also do not recommend it.

Andi
[Galaxy S III Android Development] PIRATA!:
Wow! Amazing!! I use the same file browser app and never noticed that!

So must I just delete all those link files from /system/xbin/ folder??
[Galaxy S III Android Development] gieffe22:
ok back to boef kernel (obviusly beta 4)... i'm back to home; the feeling is just great, smooth ,fast and no problem.

i miss lmk and zzmove optimal in devil kernel... home is home,even on a cellphone.

Great work as usual Andy :highfive:
[Galaxy S III Android Development] andip71:
When they point to /sbin/busybox, then they are from boeffla already - you can keep them.

When they point to /system/xbin/busybox, then they are orphaned after you deinstalled busybox, then you should delete them and during next restart they will be created again and point to /sbin/busybox (which is Boeffla's busybox).

Welcome back, my friend :)
[Galaxy S III Android Development] gieffe22:
anyway this SEA2 definitly improve performance...i'm using it hard right now to test smotthness and it's much much better than update13
[Galaxy S III Android Development] pricey2009:
+1

Noticeable jump in smoothness and overall experience seems enhanced
[Galaxy S III Android Development] PIRATA!:
I've deleted all those in system/xbin/ tar where marked as busybox like you showed me with the screenshot of you post. There where only 5 files not like that, and the other where something like 18Mb of links!!

Which are the differences between those pointing to /sbin/busybox and those pointing to /system/xbin/busybox? How can I recognize then?

EDIT:

At reboot now in system/xbin I have all the files created again.
[Galaxy S III Android Development] onesolo:
Just to tell you... maybe it doesn't work as you intended it to work...

I have Supersu, from chainfire, to be disabled for a few minutes at boot.

I tried to start boeflla config with supersu disabled and it complains that there's no Su installed... so I guess that the supersu inbuilt on the kernel doesn't act on that.
[Galaxy S III Android Development] andip71:
No, this is wrong expectation.

The su that comes with the kernel will never be used, unless you want to root your phone one-time (!!) from scratch.

The kernel does NOT come rooted. And this is by intention because there are still people that do not want to have a rooted phone but still use the kernel.

So, sorry... it is not like you thought :)

Andi
[Galaxy S III Android Development] Frozenblade33:
Hi

Beta 4 proved to be better than beta 3 or at least the same?

I didn't understand the tecnical info about sea2 thingy

And beta 3 is awesome
[Galaxy S III Android Development] Nic2215:
I feel much snappier
[Galaxy S III Android Development] mrbojangle69:
Is Boeffla 4.1 (Jelly Bean 4.1.2) supported by Boeffla Config V2? If it's not, where to find the latest Boeffla Config V1. I'm about to build a rescue rom with that base.
[Galaxy S III Android Development] andip71:
Yes, it is.

Boeffla Config V1 was required for Version 3 or lower.

From 4 onwards, V2 is the correct app.

Andi
[Galaxy S III Android Development] mrbojangle69:
I see that 5.2 beta 4 is based on SEA Update2 but I cannot see it on the Open Source Release Center. Is there any other website to watch the kernel sources out when the they appear?

Edit: Now I see it, I am getting old and my reflexes are slowing down, LOL.
[Galaxy S III Android Development] Sleehond:
I just flashed beta 4 over beta 3. Lets see what it brings!

P.S. i'm quit a noob on this, but which governor should I use? The only thing i care about is very good battery life without losing speed... LOL :laugh: I dont play that much games, only candy crush. For the rest alot of browsing and social media etc. So which governor is adviced, it now says pegasusq... keep that?

Hope to hear it!
[Galaxy S III Android Development] GrimPivo:
Why don't you try each governor for a couple of days and decide what is better for your needs?
[Galaxy S III Android Development] Sleehond:
LOL, sorry no, not going to do that. Just curious to hear if 1 of these governors is the best regarding feedback otherwise i just stick with this, no problem :good:
[Galaxy S III Android Development] MIKEMON:
@ Lord Boeffla

Super job to a friend, beta4 is absolutely tuned into a stable release

I do not have any problems

---------- Post added at 07:34 PM ---------- Previous post was at 07:31 PM ----------

First use, built-in menu profiles

My profile is zzmoove optimal, no OC, UV, do not use zram

just boeffla sound and display tuning, modified LMK
[Galaxy S III Android Development] Nic2215:
U can try zzmove battery yank for a decent battery anyway u could check out the thread mainly for sharing the kernel configuration and profile sharing instead of here. :)
[Galaxy S III Android Development] GrimPivo:
If only it were that simple, there would be only three governors - one for battery savers, one for performance lovers, and one for compromises' lovers.

But all things are too individual...

Well, if you ask me - my advice is lulzactiveq.

But many and many people likes zzmoove.
[Galaxy S III Android Development] Hidden-Hunter:
Hi Andi

Really thanks .

I do not use UV , because you have informed me !:good::laugh:

I love my phone and I will not be damaged:D

Thanks:):fingers-crossed:
[Galaxy S III Android Development] MIKEMON:
Yes, lulzactiveq is good, but zzmoove optimal, ideal for battery life and system performance.