yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Kord:
[MENTION=947981]Lord Boeffla[/MENTION]

So, I checked audio behave with default kernel settings and it didn't help. At morning (7am to 10am, 1 hour playing music) , audio was ok, not even simply stutter, but when I came back to my house, audio stuttered 2 times (2pm). Before the audio started stuttering again, I surfed in the net and watched some films on the youtube. What I know, is fact, that downloading in background when screen is off isn't raising amount of audio stuttering, also turning on Antutu in background and turning screen off also does not affect amount of audio stuttering.

Maybe there is a problem with deep sleep itself? When I set min freq to example 500Mhz, phone will deep sleep with this value or will downclock to his own "deep sleep" freq? Maybe power management or clogged memory, really, I don't know...

I can also provide logcat if it would help solve this problem, m8 :)

Oh, and thanks for new beta of course :) !

Regards :good:
[Galaxy S III Android Development] andip71:
qrashers, no, a log will not help me.

There is only one thing that would help... and this is having the problem myself too. But I never had it, so there is not much hope I can provide a solution for your specific case.

Something must be different on your side which most of the others do not have. Just the question is: What?

Andi
[Galaxy S III Android Development] RSDamasceno:
I have problems. When I receive a call while connected to wifi the call is automatically rejected as soon as I answer.

If I turn off the wifi I can meet and talk in the call.

This is a problem related to the kernel (2.2-beta6 with cm11)?
[Galaxy S III Android Development] AES256thetic:
I have noticed the audio stuttering issue sometimes appears to be triggered by switching radios. E.g., as I walk out of my workplace with music playing, I often get stutters when I leave the wifi range of my office and change to 3G/H+, then again when I arrive home and go the opposite way, from 3G to wifi.

This doesn't always happen, but maybe matches what you experienced coming back to your house? Bumping the minimum CPU frequency for zzmoove governor to 300 has gotten rid of all the rest of the stuttering, so my current hypothesis is that the transition requires a momentary spike in background processing by the S3, and the governor doesn't react fast enough - so audio performance suffers.
[Galaxy S III Android Development] RSDamasceno:
Here is the log.
[Galaxy S III Android Development] raviainani:
Mr Lord, amazing beta 6.... Here's the antutu benchmark after flashing your kernel...

i9300-cm11- boeffla-kernel-2.2-beta6-CM11.0
[Galaxy S III Android Development] granadier:
Do you guys have try the latest cm11 nightly to see if it work?? Cuz I want to flash this kernel and the latest nighty right now but don't know if it'll work
[Galaxy S III Android Development] andip71:
This is not a kernel function at all, sounds like an issue in the rom.

What are you using? CM11 is known to have all kind of weird issues at the moment, unfortunately.

Yes, I test the kernel on almost every nightly that comes out. It works, but you have to take beta5a or beta6 at least.

Andi
[Galaxy S III Android Development] sajju73:
Just to confirm CM 2.2b6 works perfect with Temasek v51b1.

Got the best power saving last night.
[Galaxy S III Android Development] andip71:
Many thanks, sajju73.

Good to hear :)

Andi
[Galaxy S III Android Development] krige:
I also had the "Unfortunately, the process com.android.phone has stopped" problem with the newest 20140310 nightly Carbon KK and Boeffla kernel 2.1 Omnirom. The problem has gone after installing Boeffla kernel 2.2 beta 6 Omnirom.
[Galaxy S III Android Development] andip71:
Yes, also Carbon implemented the MSIM framework meanwhile. That was why.

These days are quite hard days for kernel developers to keep up with latest developments in different areas and trying to somehow stay compatible...

Andi
[Galaxy S III Android Development] krige:
Can you tell us more about this framework? I can't find any documentation about it.
[Galaxy S III Android Development] andip71:
Not really a lot as it is not a kernel but a rom function.

Maybe you can google for "telephony-msim", you will get lots of hits.

Andi
[Galaxy S III Android Development] joriswagter:
Hey there, can anyone tell me what the max safe charging amperage is for the i9300?

GT-i9300, CM11, Boeffla
[Galaxy S III Android Development] andip71:
This depends on your charger. If you charger supports it, you can go up to 1600 even.

Stock charger is crap however, I would not go higher than 1100...

Andi
[Galaxy S III Android Development] andip71:
Not getting sod on Slimkat on my side with beta6.

Did you undervolt? If so, do remove it.

Andi
[Galaxy S III Android Development] Erik1805:
using boeffla-kernel-2.2-beta6-Omnirom-i9300 and Temasek V51b2 and all is running very smooth. Also lost the lag when i recieve a call and it takes a few seconds for the screen to light up. :good:
[Galaxy S III Android Development] andip71:
No, something else must be wrong. I use SlimKat on my dev S3 almost all the time. Zero issues, but flash the Omnirom Boeffla-Kernel, this is important.

Also, if you are still having trouble: Reset the kernel settings in the app (menu settings -> reset). Then try to use a few hours with standard settings first. When stable, apply your settings again step-by-step.

Andi
[Galaxy S III Android Development] andip71:
Just quick, I am uploading a maintenance release right now:

Version 2.2-beta6a

11.03.2014

Back to proven and stable Google gcc 4.7 stock toolchain (have some doubts on gcc 4.8)

Andi
[Galaxy S III Android Development] RSDamasceno:
Nightly 10, 9, 7. The same thing.
[Galaxy S III Android Development] andip71:
Could be... still not kernel related :)

Andi
[Galaxy S III Android Development] Erik1805:
Thanks,do you need to update? Have no issues with beta6

Erik
[Galaxy S III Android Development] andip71:
No, if all is perfect for you, no need really.

But remember, if one day you have something strange, ... then you should not forget to update first.

I have in the Samsung area already 3 reports of people that had strange issues with beta6, which now reported everything normal with beta6a.

Just to put a stake in the ground :)

Andi
[Galaxy S III Android Development] akz1x1:
com.android.phone has stopped

After flashing today's nightly,

I flashed Boeffla kernel as I usually do...

But when the boot finishes I can't get pass this screen...

First I thought it was the problem of today's nightly...

But when I flashed the nightly without flashing Boeffla Kernel solved the problem. ..

Please help

Sorry for my bad English
[Galaxy S III Android Development] andip71:
Did you flash latest version of Boeffla (i.e. beta6a)?

Because I flashed today CM11, Temasek CM11, Omnirom and SlimKat weekly successful with my beta6a kernels.

Andi
[Galaxy S III Android Development] akz1x1:
I flashed 2.1 stable...

Will try beta6a and report back...

Btw.. Are beta versions good for daily use?
[Galaxy S III Android Development] andip71:
Ok, that cannot work anymore. CM team has implemented Multi-SIM framework in the nightly of 04.03.14, which broke all custom kernels that day.

So you have to use the latest beta of Boeffla (and also of all other custom kernels as we all had the same issue).

It is also described in the change log:

(If you are on CM11 nightly of 04.03.2014 or newer, you need to use version 2.2-beta5a or higher !!!)

And yes... last betas are stable enough for daily usage.

Andi
[Galaxy S III Android Development] akz1x1:
Thanks... Flashing the latest beta solved the problem...
[Galaxy S III Android Development] joriswagter:
I have a car charger that can deliver 2100, I will try 1600 and see if the battery won't get to hot

GT-i9300, CM11, Boeffla
[Galaxy S III Android Development] Kord:
Thanks for advice, but I wrote before, that I raised min. CPU freq, but I didn't notice any improvement.

Anyway, why not to try again? I will report back how it will work :)

Yup, good question :)

I will try again raising min CPU freq as AES256thetic said, but if that doesn't help I will try to prevent S3 from deep sleep while playing music. Do you know some apps that will help me?

Regards :good:
[Galaxy S III Android Development] mad_ady:
Tasker can do the trick.
[Galaxy S III Android Development] andip71:
And just one more: If you have the Donation version of Boeffla Config, you can even go in tunables mode and manually configure the minimum setting for the frequency when screen is off.

The tunable is called freq_sleep_limit.

Andi
[Galaxy S III Android Development] Kord:
No, I haven't, but it isn't told I will not buy ;)

Still testing and seems that raising helped, but it can be just a luck, need more time to check.
[Galaxy S III Android Development] andip71:
You can also use an app like Trickster mod to maintain tunable values. Just be cautious of side effects.

But usually raising the min CPU frequency should always help.

Andi
[Galaxy S III Android Development] sajju73:
Hi Andy

Just to inform CM 2.2 b6a works fine on Temasek v51b2 but with omni 2.2, I HV fc.
[Galaxy S III Android Development] andip71:
Omni 2.2?? What is this?

With Omnirom Nightlies, I test every day and it is working fine.

Andi
[Galaxy S III Android Development] Nic2215:
most likely i think he intended to say that using boeffla Omni 2.2 version Causing FC

1.*i have fc during booting up CM11 (temasek logo, v51 beta 2 ) while using boeffla omni 2.2 beta 6 :crying: [pull battery and reboot then no issue agn]

2.(for temasek v 51 beta 1, changed to 6a had two fc up till now if use boeff CM version 2.2 5a no issues

Using pegasusq + zen all the time

is it due to rom issues :confused::confused: at the mean time will beusing cm2.2 5a:good::fingers-crossed:
[Galaxy S III Android Development] andip71:
Most probably... I have no FC on Omnirom, Temasek and SlimKat with beta6a of Boeffla-Omnirom kernel.

Also all well on CM11 with beta6a of Boeffla-CM11 kernel.

:confused::confused::confused:

Andi
[Galaxy S III Android Development] mrbojangle69:
I do not know if using GCC 4.8 affects the mobile network signal or not, but with Boeffla 2.2. beta6 I couldn't connect correctly on 2G mode (request data out but no data in) and had problems with EFS folder. Now with 2.2 beta6a everything came to normal state, 2G functioning ok and EFS is allright at the moment.

Lord, please keep using stable GCC 4.7, that issue made me mad yesterday all day long. I cursed for having a Samsung smartphone, S3 will be the last, next one will be one having pure Android experience.
[Galaxy S III Android Development] andip71:
Frankly, all you say is only related to the used modem. Mobile connections + EFS maintenance is purely done by the modem, which was not changed by the kernel.

So, very unlikely that was related to the toolchain in my opinion. But well, you never know... of course there is some communication between modem and kernel as well, maybe that's why.

For sure I will stick to the 4.7 gcc for the next future, no question on that :)

Andi
[Galaxy S III Android Development] rjames123:
I saw FC's with beta6a and omnirom nightly Mar10 . I did one more reboot , it optimised around 30 apps and all was fine after that .
[Galaxy S III Android Development] NickName98:
I have a suggestion for the app..

I would like it to automatically change profiles whenever something I have chosen changes on the phone..

For example..

Whenever it is charging I want it to be on stock settings (or any other profiles I had created)

Whenever I unplug it, I want it to set a battery save profile I I have also created...

Or when I turn on wifi, to automatically set another profile.

That kind of stuff..

I would also like it to have "per app modes" like Franco kernel..

Overall I think it's the best kernel for the galaxy s3 :D

Just amazing :D

*sorry for any mistakes I made in my English.. :-/
[Galaxy S III Android Development] andip71:
You can do all of that already by using tasker.

Based on tasker events (which are quite a lot) you can trigger the load of any profile created in the app.

Howto is in the FAQs on the homepage or in the online-help of the app...

(what is a "per app mode"??? never heard that)

Andi
[Galaxy S III Android Development] NickName98:
:eek: :eek: :eek:

Sooo quick answer :D

You're awesome ;)

https://play.google.com/store/apps/details?id=com.franco.perappmodes

I think it would work much better if it was in your app. I mean, something similar to this one..

It basically changes some hardware settings like cpu frequency every time you open the app you had chosen.

Watch the video.. :D
[Galaxy S III Android Development] andip71:
Hi, I see. So it basically does the same as Tasker and Llama apps do.

I think, with the integration of tasker you can achieve the same with my app, even much more.

I put it on the long-term list, but I rather prefer to code a plugin for tasker instead of reinventing the wheel again.

Andi
[Galaxy S III Android Development] tsch:
No problem with M4 and Beta6 so far for me...

Edit: currently flashing 6a...
[Galaxy S III Android Development] mortoss:
I dont know the real cause but I experience poor and unstable WiFi performance on the beta and stable kernels. Anyone has any idea how to improve?
[Galaxy S III Android Development] Scarface1991:
Had some serious battery drain today and a lot of heat, so I started up CPU Z and saw that all 4 cores were trapped at 1,4GHZ

I used zzmove and thought switching to pegasusq might help but it didn't. Then I rebooted and the problem seemed to disappear for now.

Using latest Boeffla Beta and latest SlimKat ROM

Have you guys experienced something like this with the newest beta or is something wrong on my side maybe?
[Galaxy S III Android Development] MBurns2:
mate, no problem with the latest beta.. (zzmove yank)

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] Hari23:
My S3 running temasek v46 + boeffla-kernel-2.2-beta6a-Omnirom-i9300.CWM.zip

I couldn't find "Boeffla Config app" on my app drawer, Should i install from play store?

https://play.google.com/store/apps/details?id=de.andip71.boeffla_config

https://play.google.com/store/apps/details?id=de.andip71.boeffla_config_v2

Which one?

Thanks for help
[Galaxy S III Android Development] Hbohd:
V2 of course :)

V1 was used for some old kernel versions 1.x probably for aosp :)
[Galaxy S III Android Development] Nic2215:
V2 mate
[Galaxy S III Android Development] andip71:
Yes, as the others said: V2.

Version 1 is only for kernels of version 1.x for CM and up to 3.x for Sammy kernels. But it is also mentioned in the play store description.

And second yes: You have to install from play store, I am not packaging the app with the kernel.

Andi
[Galaxy S III Android Development] Hari23:
Thanks Andi. :good:

I was going through your FAQ page on your website and couldn't find this info.

Thanks for the help. :angel:
[Galaxy S III Android Development] andip71:
So you do not have this with the stock kernel coming with your rom?

If so, I have bad news: Then your wifi router (or its configuration) seem to be incompatible with my wifi tweaks. There are some rare reports on it, but for >99% of the users the tweaks are fine and save battery.

So you could try if you have the issue in all wifi networks or just yours. And then we could draw some conclusions...

Hmmmm... in the OP of this thread... quoting:

Features

* To tweak and configure the kernel, load the app "Boeffla-Config V2" from Google play store (or androidpit.com)

​

Should be enough, or? :)
[Galaxy S III Android Development] Hari23:
Ah ! Sorry my bad :D

Thank you
[Galaxy S III Android Development] andip71:
No issue, mate. Can happen :)

Andi
[Galaxy S III Android Development] Kord:
So, [MENTION=947981]Lord Boeffla[/MENTION] and [MENTION=5016308]AES256thetic[/MENTION]

Many thanks for your help!

Finally, third day without audio stuttering!

Looks like rising min CPU freq to 400Mhz solved the problem. Also I'm undervolted to -50mV so I have less power consumption even when I will be on 200Mhz min. and stock volts. Probably previosly, when I tried to raise freq for CPU, settings was not changed for some reason, dunno why. Anyway, I'm very glad I can now listen music in peace :)

Regards :good:
[Galaxy S III Android Development] ayoubij:
I just experienced the same but didnt know what to do or how to inverstigate.

Im using omni beta 6a with carbon rom, tweaked my governor a bit chose zzmove then switched to pegasusq. However after several hours of using pegasusq i take out my phone from pocket and its really hot. The temp is 10° outside so you can feel the 50° mobile clearly.

I think it turnedd off automatically from over heating. What do you think the solution?
[Galaxy S III Android Development] andip71:
For a solution it is too late now, or better to say: for an investigation.

Next time when this occurs, try to find which process is running crazy.

For this, I would advice you install an app like "OS Monitor" on your phone soon. This app can list all processes running and shows you how much CPU is used by the process.

Clearly one process must have existed that went to 100%, and this needs to be found next time.

I am also sure, it is coming from a rom process, not kernel :)

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

I think i found a tiny bug in the "touch wake charger mode". I personally like the idea that you can touch to wake when the charger in connected. But _only_ if the charger is connected. Here is how to "break" it:

* precondition: touch wake status=true; touch wake chager mode=true; touch wake delay=infinity;

* turn on screen & pass keyguard

* connect charger

* turn screen off with power button

* touch screen (screen correctly turns on)

* turn screen off again

* while screen is off, disconnect the charger

* touch screen (screen turns on, but the changer has been disconnected - bug ;))

* turn screen off again

* touch screen (touch wake is no longer active now and screen correctly doesn't turn ok)

The other way around also doesn't work (screen off -> charge -> touch wake doesn't work).

Don't take this the wrong way, but me, as a dev, I like to know if people use certain features and if they don't then I like to know why. I know it's a small user thing (but requires more code changes than expected), but that's the reason why I'm currently not using it.

Other than that: great as always!

Cheers

Loris
[Galaxy S III Android Development] andip71:
lchiocca: Thanks for the very detailed description. This is a prime example how a description needs to be for a dev to quickly understand the report.

And you found indeed a little glitch.

Because, the way the implementation works is: Touch-wake logic is the "master", it just checks if a charger is connected when the screen goes off. It does not check this again when a charger gets disconnected.

In order to fix this glitch, I would need to develop a hook back from the samsung battery driver into the touch wake module. Doable, but quite a huge effort to fix this little glitch. And the risk to implement another side effect.

So please understand, as this is a very rare scenario (by the way... strange, because for me when I disconnect the charger, screen goes on which automatically triggers the correct status internally again - did you switch that behaviour somewhere off in the rom by any means?), I would rather put it on the list of "known issues" instead of putting a lot of engergy into making this from 99,8% to 100%.

Hope you concur.

Thanks

Andi
[Galaxy S III Android Development] lchiocca:
I'm a dev; that's what I would expect if somebody tried to explain a bug to me ;)

I've got omnirom and set the "wake screen when charging" turned off.

I completely understand - I kind of knew what you'd need to do to fix it. And putting this on your todo list ist just as good.
[Galaxy S III Android Development] amargawade90:
Hello Sir , Now just flashed the "Resurrection Remix® 4.4.2 KitKat v5.0.5 " ROM in my S3 ? So which kernel should i used? CM11 or OmniROm ?
[Galaxy S III Android Development] BodjieJed:
Omni version
[Galaxy S III Android Development] querotequila:
I'm using aosb with this kernel but I can't completely disable the menu and back button lights. Anyone have this same problem?

Enviado de meu GT-I9300 usando Tapatalk
[Galaxy S III Android Development] Yeti47:
Hi, giving archi's battery saving profile a go but facing a strange issue after startup. All settings stick, bar the governor, which always goes to zzmoove. If you reapply the profile pegasusq sticks OK.

Have formatted system and reflashed omni nightly, and the last 3 kernel versions but nothing changes, the governor is always reset. Any ideas?

If I stick to zzmoove all is good...

Created a workaround with a llama startup event resetting the profile, but would prefer to find the source.
[Galaxy S III Android Development] MBurns2:
try to increase additional boot up delay from boeffla app.

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] Yeti47:
Thanks, but has no impact. Probably time I did a complete clean and reflash anyway, so will do that after the weekend.
[Galaxy S III Android Development] mortoss:
After enabling hotspot my WiFi does not work anymore. Also hotspot sometimes in unreachable making client wait for IP forever... Any solution?
[Galaxy S III Android Development] szunyi77:
Hello, I found this thread. Have to deal with this? http://xdaforums.com/galaxy-s3/general/fix-nasty-bug-call-battery-drain-aosp-t2680631

Sorry for my bad english..
[Galaxy S III Android Development] Nic2215:
If you are using temasek v51, the v1 fix it's already included. then u don't need it, just don't touch v2,it will make your mic soft, but u got Boeffla sound to enhance and increase the mic volume. I go for v1 and no issues.
[Galaxy S III Android Development] XDAMaxe:
it's a must for i9300 users because it eliminates those extremely annoying after call batt drain issues (right after the first call - received or made - batt drained much more than before - only workaround was to restart phone).

Proceed with V3 and you're done until your rom-dev includes it himself (as far as I understand the next builds/nightlies from cm11,omni+Temasek will have it) so this is fortunately only a temporary but very appreciated solution
[Galaxy S III Android Development] szunyi77:
[MENTION=4900068]XDAMaxe[/MENTION]

I use currently AOSB 3.1.2 rom boeffla omni B6a 2.2 kernel.

Then I need this patch?

Should I use?

If yes, then which one?

Thanks
[Galaxy S III Android Development] Yeti47:
Fixed it by turning all omni performance 'apply at boot' settings on and off. They were all off, but obviously one got confused. School boy error ;)
[Galaxy S III Android Development] XDAMaxe:
imho you can use V3 without any disadvantages. Worst case would be that it's useless but otherwise you will gain batt power :)
[Galaxy S III Android Development] sandeman11:
Well, that's basically the question.

Reading that Boeffla is good kernel for Omega is was wondering if that would change my problem..

i only did a CWM-backup. I assume this is not including a EFS-backup?
[Galaxy S III Android Development] amppen:
I'm afraid so. If you restored your cwm backup and you don't have connection it sounds like your EFS partition is messed up and your backup didn't fix it.

Try searching your sd0 and possibly sd1 for a backup. Many ROMs and such automatically backup EFS.
[Galaxy S III Android Development] sandeman11:
well i gave it a go with the Boeffla kernel 3.1 and now the Mobile Network is working again! :laugh::laugh:
[Galaxy S III Android Development] amppen:
OK. I'm glad your problem was solved :good:
[Galaxy S III Android Development] idiversss:
Where is the link?

Inviato dal mio GT-I9300 usando Tapatalk 4
[Galaxy S III Android Development] malachow:
http://www.boeffla-kernel.de/index.php/2012-10-31-06-13-16/viewcategory/22

:good:
[Galaxy S III Android Development] brujo55:
best profile for pegasus?
[Galaxy S III Android Development] andip71:
There is no "best"... what do you want to achieve? Battery or performance?

Andi
[Galaxy S III Android Development] brujo55:
thx

also why zzmoove stuck at max freq. when playing,tested in all profiles.