yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] seroesh:
Agreed... getting 4.4.4 was a stretch on S3 and now 5.0.2 is beyond everything, so you are totally right, but in my instance... having shared my concerns have benefited me, as increasing the swippiness and zram memory has made the phone fluid and lag free!! Thanks to you all guys! I've undervolted and the phones seems to working fine.. but it still heats up, I guess that's a genuine S3 fault, which I would have to live with.

---------- Post added at 01:58 AM ---------- Previous post was at 01:56 AM ----------

Yes, it has barely exceeded 300 on my device, always beneath 275 with swippiness at 90, i'll check a few days and then try 300.

---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------

You should give CM12 another go, with alpha9, set zram to 800 and swippiness to 90! it has resolved my issues of lag! even I have OC 1600 and uv -25 and it's still working very fluidly!
[Galaxy S III Android Development] buukarim:
If i were to revert back to cm12 weekly 2 from weekly 2.1. Do i have to revert to alpha8?
[Galaxy S III Android Development] Stevica Smederevac:
Of course,NO.
[Galaxy S III Android Development] Gokulbalram:
Not necessary :)
[Galaxy S III Android Development] andip71:
All correctly said by some others here, but just wanted to confirm: No.

Andi
[Galaxy S III Android Development] sevenshorseman:
Have a safe trip. I think they have much snow right now.

We have it in NRW in the moment?
[Galaxy S III Android Development] andip71:
Yep, supposed to be cold and snowy there.

I will see :)

Thanks

Andi
[Galaxy S III Android Development] senthilaca:
Happy Journey !! :)
[Galaxy S III Android Development] Gokulbalram:
Ah, happy journey (If you like the cold!)! Your slow replies will surely be noticed :P

EDIT: Look at the page number :eek: the satanic number @_@
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION], don't you think the title is rather misleading? It makes it look as if we have a CM12 stable kernel. Just saying :)
[Galaxy S III Android Development] andip71:
Yes and no. People need to read through the thread + read the kernel homepage too.

I cannot make it idiot proof without starting an extra thread (which I won't do).

Andi
[Galaxy S III Android Development] Gokulbalram:
You got a point.

I just saw Slim LP for i9300. Do we need another kernel for that or can we just flash the CM kernel?
[Galaxy S III Android Development] andip71:
Don't know. I am not using thesroms, only vanilla cm.

But try with cm12 kernel and let us know...

Andi
[Galaxy S III Android Development] Gokulbalram:
I just changed to CM and I'm too settled to move and try Slim. If I do decide to test, I'll try the kernel :)

Although Omni won't boot with any other kernel
[Galaxy S III Android Development] SharpBang:
Music player volume focus problem com CM12

[MENTION=947981]Lord Boeffla[/MENTION],

I have this problem (so does many people that manifested on CM12 topics) consisting on music player volume focus on CM12.

The problem is, when another application gains focus for its notifications, music player volume decrease (loose it focus) normally. However, when music player gains focus again, it volume goes raising without limit until it distorts. An annoying workaround is just one-press on any volume buttons and volume restore to its default level.

Could it be fixed, please?! This is the only major problem I consider with CM12 ROMs.

P.S.: It is sometimes intermittent (When deepsleep/screenlock) it occurs less frequent, but during phone usage it occurs more often.
[Galaxy S III Android Development] andip71:
But this is something you need to address to rom developers, not kernel devs.

This is not at all handled by the kernel.

Andi
[Galaxy S III Android Development] Gokulbalram:
Hey guys, I got a tip for the light users out there, I recently decided to under clock stuff as follows:

CPU- 1000MHz (Zzmove)

GPU- 266/350MHz

I also enabled ZRAM to 300 MB 4 devices. I get GREAT battery life, phone is still smooth.

If you think the phone must become really unstable, you're wrong. I'm able to play games like Clash of Clans, Real Racing 3 without much lag. Also ZRAM is doing a great job. Whilst typing up the post (Google Chrome), I forgot to upload and post the screenies, so I uploaded to imgur through a new tab and when I returned to the tab which I was typing on, the page was still there (That's a first. It always used to reload).

BTW, I'm using CM12 Weekly 3. Peace out! :D
[Galaxy S III Android Development] myshakugan:
Yep that's the same thing I did when I was on cm, set zram to 300mb 4 devices and underclocked cpu. Really helps improve battery life. ?
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION], tried Slim and Boeffla, all's good :)
[Galaxy S III Android Development] b0unty:
strange problem

[MENTION=947981]Lord Boeffla[/MENTION]

hi Andi,

today i've experienced a problem with your kernel NG 2.6 & 2.5 for CM11

i use the latest CM11 from Markox89.

with your kernel i can't access to the recovery via the boot menu . it power off the phone after some minutes

without your kernel i can access the recovery via the boot menu as normal

my recovery is twrp 2.8.4.0

i hope it can help

thx for your great kernel

PS i don't have the knowledge to know if it's a kernel problem or CM11 (bug) problem

i also posted a message to Markox89 thread about this problem
[Galaxy S III Android Development] cookiepuppy:
Hi there Andi, i have a question about boeffla config app, i know that there an option to change charging value for AC charge and usb charge, my problem is that i use 2A charger but the config app limits at 1600mA tops, so i cannot enjoy the rest of my charger capabilities, is there a way to solve it?

Thanks

Sol
[Galaxy S III Android Development] Moster2:
If you want to toast your battery, boeffla can for sure help you. I wouldnt risk it though :P
[Galaxy S III Android Development] cookiepuppy:
Why toast, this is origonal samsung charger and our battery is more than capable of using 2A charger, in tbe same way i can say why set it by default to 1100mA or higher when using 1A ac charger, it can ruin the ac charger.

The only thing is noe with the config app i cant go above 1600mA when my ac can supply me 2000mA.
[Galaxy S III Android Development] Gokulbalram:
Why would the default setting of 1100mA ruin a 1A charger?

It's all your choice now, if it works, well and good. If it doesn't, instant regret.
[Galaxy S III Android Development] cookiepuppy:
I didn't say that it does ruin, i was answering to moster7, read his post, and i say again but let me rephrase :

If my current AC charger is 2A = 2000mA my battery of 2100mA is more then able to charge without blowing it or even getting heated. If moster7 says it can harm the battery then i think he is wrong, and if i continue his thought, even using 1A AC charger and changing the charging rate in boeffla config to 1100 or even 1200mA it can also harm the battery.

Imo the only difference will be how fast my device will be fully charged.

But my problem as mentioned above posts is with the config app that limits the charging rate only up 1600mA so can use my charger at full capacity.

In theory 2100mA batt. And 2A charger can fully charge it in 1 hour and a bit. And also not in theory as long as something is not restricting the current to charger from your wall socket or in my case the config app

Was this explanation more clarify things for you [MENTION=5231921]Gokulbalram[/MENTION]?

And i didnt mean to answer angry only wanted for you to understand
[Galaxy S III Android Development] nkirk:
You seriously need some reading on the Battery charging subject. Google is very friendly mind you ;)
[Galaxy S III Android Development] Gokulbalram:
First of all, it's 2100mAh. Second, I don't think the S3 supports such high input. I'm not very sure about this topic, but I suggest you wait for [MENTION=947981]Lord Boeffla[/MENTION] for this. Your device could get damaged like [MENTION=4604352]Moster2[/MENTION] said, due to such high input.
[Galaxy S III Android Development] ScratMan38:
Your theory is wrong.

First thing, when your battery mentions 2100, ir corresponds to the capacity of the battery (the size of the energy tank). The unit is mAh, that means milli-amperes for hour. Your 2100 mAh battery is able to provide a 2100 mA current during one hour from full charge to fully empty ; or 4200 mA during 30 minutes ; or 1050 mA during 2 hours.

Second, the charging capabilities of a battery does not depend on the total capacity. It depends on the cell's technology. Newly developped batteries can stand higher charging current than old technology batteries.

Third, the limiting factor in the final phone is not the AC wall charger, neither the battery. The weakest point in the charging loop is the battery charger device embedded in the phone. It's a DCDC converter, it converts the +5V from the wall charger into a variable voltage from 2.5V up to 4.8V suitable for the battery, and it controls the current injection in the battery vs applied voltage to control the different phases of battery charging protocol (you cannot just apply a voltage and let it charge, it would just blow).

This DCDC needs several external components, like coils, capacitors, sometimes power MOS switches, etc... in order to work. All these components are designed to be able to withstand a max current.

The phone manufacturer may select different limits depending on the capabilities of all the components.

For example, they may take :

- 2A AC wall charger, because they already have one available in production, used for a tablet, so design reuse is less expensive

- 2100 mAh battery withstanding maximum charging current of 1800 mA

- DCDC converter device able to drive a battery with charging current up to 2.2A (2200mA)

- coils with small size and low profile to keep a very small application but withstanding 1.5 A as max current

In this case, the maximum current the full charging system can withstand is the max current from the weakest component : the coil will limit the max current to 1.5A

But as 1.5A is already a maximum rating, the manufacturer will have to keep a margin to avoid the aging of the coil., and they will limit the current to 1200 or 1300 mAh, by writing the correct settings in the DCDC converter configuration registers.

But then if a guy simply takes the specifications from the manufacturer of the DCDC, and sees it can go up to 2200 mA, and then decides to use this maximum value in his kernel, in order to have a faster charging, the DCDC will then force the current in the battery at 2200mA, much above the capabilities of the coil !! and at the end, the coil will wear faster than normal, it will drift, and it may burn, damaging other components around.

That's why dealing with kernel is not safe, and why you need to keep margins when changing such settings.
[Galaxy S III Android Development] cookiepuppy:
I guess....hehe since i didnt search google.

[MENTION=2135483]scart[/MENTION]man

thank you for the enlightenment, it's always nice to have good explanation.

so in order to try keep my battery but still have a faster charge time with so 2A charger, do you recommend set the limit in config app to 1400-1500mAh ?
[Galaxy S III Android Development] Stevica Smederevac:
Don't go above 1300-1400
[Galaxy S III Android Development] myshakugan:
I set it to 1600 in the config app, didn't face any issues yet.
[Galaxy S III Android Development] fonfox:
On short time this will go.

suggest you dont want kook your Phone. For longer time i am sure you damage it.

Against half a year i set Booth power options in APP and set 1200mA loading over night my phone was kooked all near the USB plug was blowing up.

Now i have a New mainboard and i ( just for me ) never set above 1100 mA .
[Galaxy S III Android Development] myshakugan:
I see. Guess I'll reduce it to 1300-1400 then. :/ Thanks for the heads up. ??
[Galaxy S III Android Development] d0pecr4wler:
Sounds weird, 'cause I am on CM11 NG v2.6 w/ Archi Droid v3.0.2 and I can easily access the recovery via the boot menu. But my recovery is TWRP 2.7.1.0.

. : Sent via Samsung Galaxy S3 w/ Tapatalk : .
[Galaxy S III Android Development] ayoubij:
I always set my charge limit to 800mA since both ways i do it overnight so i dont need speedy charges and hence i save my battery for longer :D
[Galaxy S III Android Development] andip71:
You mean, SlimLP and Boeffla CM12 kernel? Or which combo exactly?

Well, the reboot into recovery from the boot menu not working is a known issue of CM since nightly of 15.01.15.

It seems, with latest nightly they have partially fixed it, so it does sometimes work, sometimes not.

In any way, the boot menu does not use any kernel functionality to trigger that function. So I think you are getting the sporadic issue here. Sometimes works, sometimes not.

I am sure it will be fixed in an upcoming nightly.

Well, almost all has been said already before by others.

But just to explain why I do not allow to go higher than 1600.

It is not only about the charger, the cable and the battery itself.

Most important, there is one more piece in between: The charging circuit, a Maxxim chipset.

And I am sure, you do not want to fry this chipset by overloading it, or?

Battery, charger and cable you can replace, this chipset not, it would mean a irreversible hard brick.

And I promised when starting with my kernels, I will never put something in that would potentially break or damage hardware. That's why :)

Andi
[Galaxy S III Android Development] Gokulbalram:
Yes, SlimLP and Boeffla 3.0 A9 :)
[Galaxy S III Android Development] cookiepuppy:
Thank you for explaining, about the charging issue, as i said previously to scartman38, much easier to understand when there is a good explanation.

I do want to keep my phone happy.... Like my wife ;) so I'll do whats you recommended, not over 1000 or 1100 for charge rate.
[Galaxy S III Android Development] MALditoNica:
New Rom. Should I revert to sock kernel?

I'm about to install Slimkat (I've had it with CM11). However, I have your CM11 Kernel installed. What should I do? Uninstall Boeffla first and revert to stock kernel? And if so, how? What's the default kernel for CM11?

Thanks!

BTW, I'm switching ROMs because of 2 things: camera doesn't work (well) and constant black screens. Reading this post I found out that the black screens might be because of the kernel?
[Galaxy S III Android Development] andip71:
You can just flash SlimLP over, it will install the kernel which comes with Slim.

However, if you have black screens and read somewhere it is related to the kernel, I would like to see where this is stated to kick in.

I have NO blackscreens at all, so it is not a general kernel issue but something else. Otherwise everyone would report that.

Just wanted to say before wrong information spreads.

Andi
[Galaxy S III Android Development] MALditoNica:
Danke! I'll flash slimkatright now.

About the black screen. I wouldn't know if it is because of the CM11 (snapshot) or Boeffla. I flashed them both at the same time. Before I was with CM11 (installer) and I didn't have problems with black screens.

They usually happen when the phone is under heavy load. When opening facebook, when 3 or 4 apps are running, etc
[Galaxy S III Android Development] Gokulbalram:
"I would like to see where this is stated to kick in." S**t just got real :P

By the way, I used Boeffla+Slim and had zero problems, now shifted to Temasek which has really awesome features!
[Galaxy S III Android Development] nilesh.remo:
fqrouter2 (wifi repeater) app not work. Any solutions.? Or add support in kernel .
[Galaxy S III Android Development] rp158:
funny, such demands
[Galaxy S III Android Development] daniel.mota:
People must realize that most of the problems, bugs, features, apps, etc come with the rom.

You should always double check a problem/bug with the rom stock kernel, before requesting something to the custom kernel developer...
[Galaxy S III Android Development] andip71:
Ask the developer of the app, whether he requires any specific support for it (modules, drivers etc.) in the kernel.

When I have this information I am happy to check if I want to include it or not.

But without more information, this is put on hold for me.

Thanks

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

I have cm 10.1, with the cm kernel. I've flashed boeffla 2.1 (from here ) using CWM, and after booting (and cache and dalvik resetting) the wifi has stopped working.

I've flashed again from inside the config app, same results.

Any tips?

Regards!
[Galaxy S III Android Development] andip71:
Check if you have file dhd.ko in folder /system/lib/modules

If not, wifi cannot work. If yes, it should.

However, don't get me wrong... CM10.1 is not supported anymore for more than a year, from both CM and kernel side. It is Android 4.2 only.

I am not sure why you want to install such an old and outdated combo?

Andi
[Galaxy S III Android Development] leitor79:
Hi Lord Boeffla, thank you very much for your answer. For now I've came back to my old kernel, but I'll try your suggestion on my next attempt.

I'm using CM 10.1 because I got it for a year or so, and it runs smoothly like the first day. I have it heavily personalized (dark apps from teamblackout that does not work on other versions of android, for example), and I've tried several other ROMs that did not satisfied me (slim, liquidsmooth, cm10.2, cm11, carbon, aokp, cm12 a few days ago, to name a few I remember I tried)

Thanks again for your answer and also for your great work!
[Galaxy S III Android Development] leitor79:
Hi Lord Boeffla,

I've reinstalled your kernel, still no wifi, the dhd.ko is there where you said (542.48kb), I've flashed it twice more (without empty the cache), I don't know that else to try... I'll aprecciate your help, or help from any other user that maybe got the same issue! thank you very much!
[Galaxy S III Android Development] Gokulbalram:
Which kernel and which ROM?
[Galaxy S III Android Development] andip71:
I am really sorry to say... I cannot help further a lot.

The kernel is end of development and in general I would not recommend to install such an old rom anymore (security etc.).

But it is up to you of course. Just, I have no idea why it does not work for you anymore. And I cannot even test for you anything anymore.

Andi
[Galaxy S III Android Development] metalgearhathaway:
CM12 Intelliactive profile

Guys, if you are using CM12 then I would love you to try out my new boeffla profile, if you are not a donate app owner then you are missing out on the ability to tune the governor to get the very best out of the lollipop builds, so far everyone is extremely happy with the amendments I have made to intelliactive, I've impressed myself even on this occasion!

Have a look at the Boeffla profile thread, here is my post: http://xdaforums.com/showpost.php?p=58670212&postcount=1502

File attached here for convenience as well, but discussion only on profile thread please! :angel:

For those who care and want to see the amendments I have made to the governor, take a look at the screenshot and compare to standard configuration, [MENTION=947981]Lord Boeffla[/MENTION] i'd be intrigued by your opinion on the alterations I have made here. :cowboy:
[Galaxy S III Android Development] andip71:
Update time !!!

Good evening,

after being back from my trip to Munich - updates for the CM11 and Omnirom kernel variants (both normal and NG).

Change logs are:

CM11 + CM11 NG -- Version 2.7 stable

06.02.2015

Toolchain changed back to CM11 standard toolchain gcc 4.7

Implemented new equalizer profile "Flat", which resets the equalizer in Boeffla-Sound to neutral settings

Updated ramdisk to version of nightly 03.02.15 (should fix reboot into recovery via power menu not working on latest CM11 nightly)

Omnirom + Omnirom NG -- Version 2.7 stable

06.02.2015

Toolchain changed back to CM11 standard toolchain gcc 4.7

Implemented new equalizer profile "Flat", which resets the equalizer in Boeffla-Sound to neutral settings

Enjoy

Andi
[Galaxy S III Android Development] leitor79:
Hi Goku, thanks for your answer.

Kernel 2.1, ROM CM 10.1

And, just in case you like to ask, I'm using such and old configuration because It runs very well and I have it very personalized as I like.

Regards!
[Galaxy S III Android Development] viktor92:
Hello Andi, why you've changed back toolchain to gcc 4.7 ?
[Galaxy S III Android Development] Gokulbalram:
What I'd suggest is to use Stock rather than such an old ROM. But yeah, these are the downsides of using an old ROM.
[Galaxy S III Android Development] andip71:
Too many indifferent reports about weird effects since change to toolchain 4.8 for some users.

It was an experiment, but I think it is better to have the toolchain which matches the rom toolchain.

So: CM11 = gcc 4.7 and CM12 = 4.8.

"Close-to-stock" :)

Andi
[Galaxy S III Android Development] leitor79:
I understand. Thanks anyway, and good work!

---------- Post added at 10:02 PM ---------- Previous post was at 09:58 PM ----------

Hi,

I think is not the ROM, since the wifi works with other 2 kernels... and after a year I'm using the same ROM, the phone runs very smoothly... but thanks anyway!
[Galaxy S III Android Development] sunny1234590:
Ac charging

Has anyone tried charging the phone without safety margins and without using 'ignore unstable power' is it safe? :/
[Galaxy S III Android Development] ayoubij:
Ive been charging like that for more than a year now and no problem
[Galaxy S III Android Development] sunny1234590:
Oh great, one more question my charger capacity is 700ma at most can I use it for 1000 ma?
[Galaxy S III Android Development] seroesh:
I use 1600 mA with ignore unstable margins and ignore safety margins both on! Because even if you are on 1600 mA charging, the both margins are not ticked, the charging current will keep varying because of unstable charger or the likes. Can't wait forever for the phone to charge, since it discharges so quickly.
[Galaxy S III Android Development] ayoubij:
I think you can since the charger will limit the current but its better then to keep it 800ma
[Galaxy S III Android Development] d0pecr4wler:
CM11 is GCC 4.7 and CM12 is 4.8?! oO

That's a little bit confusing, 'cause Archis KK ROM is GCC 4.8 and that's a CM11-based ROM.

. : Sent via Samsung Galaxy S3 w/ Tapatalk : .
[Galaxy S III Android Development] ayoubij:
We are talking about official. He cant make a kernel for every Rom
[Galaxy S III Android Development] 80s Baby:
Is it possible to set two separate EQ's? One for the headphone and one for the speaker?
[Galaxy S III Android Development] andip71:
I only consider official roms by cm.

Because everyone can recompile with other toolchains.

But cm official is the reference.

Only one hardware eq in the audio hub.

Only way is with multiple profiles which you switch.

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

Love your work, been using your kernel from the day I got my s3 and cannot go without it if I flash a new ROM. With that said I have just two questions do you plan on doing a material designed version of your app that also works on KK and a logo update to look more materialistic?
[Galaxy S III Android Development] andip71:
First... No. Too much work for no benefit. App size would blow up etc etc. With cm12, you can have material theme.

Icon: maybe, but not very soon. Have to find a way to still have people recognizing the "brand".

So need to be careful with the design...

Andi
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION], I just compiled Omni. Now I'm in dire need of your kernel :/
[Galaxy S III Android Development] andip71:
Well, then you need to also compile the omni kernel this time one your own.

Have no plans to add another kernel variant now, no time left anymore. And heard omni 5.0 is supposed to be very buggy, so not worth the effort.

Sorry

Andi