yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
Kernel/Rom mix. I will look into it.

And no, it is not really perfect. That is why I look into it.

Andi
[Galaxy S III Android Development] andip71:
Found it already. Just compiling alpha6. Should be up soon (if the fix works).

Andi
[Galaxy S III Android Development] whatsgood:
This kernel does work with nameless rom, but I feel as though it's not fully compatible. Sometimes I find that when I press reset on LMK settings it won't reset.
[Galaxy S III Android Development] marenp:
Read couple of posts before. Boeffla working on fix.
[Galaxy S III Android Development] whatsgood:
No, that's not what I mean. I am aware of the bug with alpha 5, I'm talking about an issue exclusive to nameless rom. Maybe it's just because boeffla kernel is designed to work with cm12.1 roms. But it occurs on every version of boeffla on nameless rom. I try to reset lmk and it says restart to fix this. I restart and i still can't reset lmk
[Galaxy S III Android Development] andip71:
Correct. If Nameless is not 100% compatible with CM12.1, then there is nothing I will do about it.

I cannot support building individual kernels for many roms. Just not possible.

But still I think, with the alpha6 and the new Boeffla-Config App I just pushed, the LMK topic should be even history on Nameless.

Andi
[Galaxy S III Android Development] andip71:
...alpha6 arrived

Hi,

to fix the Low Memory Killer issue of alpha5, I pulled alpha5 and replaced it by alpha6.

Please note, to reset your LMK properly, you also need to update to Boeffla Config App 2.1.81 which I just pushed too.

Version 4.0-alpha6

01.06.2015

NOTE: This kernel only works on roms that have latest CM commits as of 31.05.15 included, like e.g. JustArchi/Moster unofficial CM12.1 version of 31.052015.

For all "older" roms, you still need to use alpha4 !!!

Fix Low memory killer setting in Boeffla-Config

(if you have trouble resetting it, make sure you upgrade to Boeffla-Config 2.1.81)

Enjoy

Andi
[Galaxy S III Android Development] superchandan007:
Thankyou [MENTION=947981]Lord Boeffla[/MENTION]...

Now its ok. Working

Sent by Chandan 007 using GT-I9300
[Galaxy S III Android Development] matt1966:
Just like to confirm that alpha 6 is also working with Bliss Pop nightly from 18.05

Not tested with nightly from 27.05!
[Galaxy S III Android Development] kadopt:
New zzmoove governor available as well.
[Galaxy S III Android Development] andip71:
Yes, I know.

But you know, I am not actively developing new functions in the kernel anymore.

Maybe, if I find time, I will sneak it into one update, but cannot promise.

Andi
[Galaxy S III Android Development] TheTurbanater1298:
For someone who doesn't actively work on our S3, you sure give it a lot of love with timely updates when CM updates. I think a little part of you still has massive amounts of love for the device [emoji14]

Thanks for the amazing work. I don't think I'd listen to music how I'd like or even save as much battery as I do without your Kernel. Thanks man [emoji173]

Sent for the sweetest Lollipopped SGS3 i9300
[Galaxy S III Android Development] Gravaze:
new alpha 6 kernel makes bootloop and i can't fix via wipe. i flashed alpha 3 again and there is no problem. i don't know, it's a kernel issue or rom issue. i'll try alpha 6 with other cm12.1 roms and decide what is the problem.
[Galaxy S III Android Development] andip71:
LOL, you do not need to "decide" what is the problem.

I can already tell you, alpha6 works fine as long as you are using the correct rom.

The only one I test is build 9 of JustArchi CM12.1.

Every other rom can work or not, depending on its development state.

Everything is super clear stated in the change log.

Andi
[Galaxy S III Android Development] Gravaze:
i decide my or my phone's problem, i'm not capable to decide kernel's fault or problems of course. :) i'm using cm12.1 build 7, i'll flash build 9 now and check it again.

i'm very big fan of you. deciding which rom i use, first of all i check can i run with boeffla kernel.
[Galaxy S III Android Development] shaarky:
[MENTION=947981]Lord Boeffla[/MENTION], Andi - my brother is getting boot loops on latest Beta 9 from JustArchi on CM12.1, seems it's Kernel related... can you please take a look ?

http://pastebin.com/iUpuVkZT

Note - seems it was happening while connected via BT (HR belt)

Thank you ;)
[Galaxy S III Android Development] andip71:
First of all: No indication the kernel triggers the reboot here. No panic, no errors, log is clean.

Second: I cannot provide support with only that log. I would need a full boeffla config debug file created.

Third: If you have a boot loop, how have you been able to provide a log file that was running for > 5000 seconds?

Fourth: You know, I am not giving any official support for the CM12.1 kernel. If it runs, fine. If not, ... sorry.

And last: Bluetooth in my kernel is 100% stock. Never had any issues with bluetooth, but also almost never used it.

Andi
[Galaxy S III Android Development] shaarky:
OK, just thought LAST_KMSG is created only in case of Kernel crash, my bad, no offense.

I have full Andylog, would that help? Anyway, will post it soon.

As for the support, I understand that but not sure what it means... just trying to help here, naturally it can be also out of your kernel problem...
[Galaxy S III Android Development] andip71:
For the support it means:

When it does not run, I will not look further into it :)

I do not want to waste time giving support for a kernel that bases on jellybean basis enriched with kitkat code that runs on not officially maintained CM12.

I guess you get the point? If it runs fine, if not... well, then it can by everything.

Why it is not the kernel? Easy - many hundred users that use it without issues, me included. On build 9...

I guess you have done the usual stuff:

- reset the kernel configuration to default

- no undervolting, no overclocking

- no weird stuff like other mods, xposed etc.

Andi
[Galaxy S III Android Development] shaarky:
OK Andi, got it...still based on my experience, sometimes an error is overlooked, people are lazy, not providing logs, are afraid of expressing their opinion not to offense a key developer on their device (like you are and no - I'm not "assoholic" here ;) ) etc. Here for example I'm trying to help my family, that's it...they are now 200km far away from me, that's why AndyLog.

So still, let me try it and provide the the log and I APOLOGY IN FRONT ;) in case it's not Kernel related... which is based on user experience and no complain very likely.

This log contains (always separated by string "---------------------------- SECTION NAME ----------------------------"):

LOGCAT

BUILD_PROP

CPUINFO

SYSCTL

KMSG

LAST_KMSG

DMESG

UPTIME info

...I wonder what is LocalFingerprints, will probably do some research on my own.

Btw - no overclock, no undervolt, no XPosed...
[Galaxy S III Android Development] andip71:
Hey,

all is good. I just wanted to make the point: CM12.1 kernel is unsupported.

Usually I do not even look into provided logs for it.

But I did and could not spot anything. No kernel errors, no panics, all logs are quite clean.

But the missing part is: The configuration, which would be contained in a debug info file boeffla-config creates. Maybe I could see something in there.

But for so far - nothing that indicated where a reboot is coming from.

Andi
[Galaxy S III Android Development] matt1966:
Bluetooth boot loop is an issue of Governor.

Try it with intelliactive.

Working for me.
[Galaxy S III Android Development] JustArchi:
No, bluetooth bootloop is an issue of deadlock with unknown culprit. Forcing 2 CPUs+ is only a workaround for it.
[Galaxy S III Android Development] volcram:
You can set "min_cpu_lock 2" on tunable profile with the pegasusq governor in boeffla config.

I think it is the same workarround that FadeFx has made with his script.
[Galaxy S III Android Development] shaarky:
Seems that reboots while using BT while using other governor then pegasusq (as proposed here by [MENTION=4658644]matt1966[/MENTION] - intelliactive ) are gone after quick check of my brother (remotely...). Anyway, here is debug log from Boeffla after sudden reboot, not sure however it will helps to anything if it is well know already - http://pastebin.com/GGWBxk8B
[Galaxy S III Android Development] Maxpawner:
After wipe all working fine with weekly 9 + beta 6 :)

Zu kompliziert auf englisch, aber auf dem s3 meiner Frau lief nichts mehr mit weekly 9, mega lag bis random reboot alle paar Minuten.

Habe jetzt gewiped und als frisch gemacht incl. Boeffla beta 6, und bis jetzt (2 Stunden) läuft alles super!
[Galaxy S III Android Development] h4yfans:
i have unofficial temasek i9300 cm12. boeffla kernel still work?
[Galaxy S III Android Development] ivano949:
Yes it works...

Cm12: use the last 3.0 Boeffla version

Cm12.1: use 4.0 beta 6
[Galaxy S III Android Development] h4yfans:
hi, i use this rom. http://xdaforums.com/galaxy-s3/development/5-1-x-cyanogenmod-12-1-t3066864

which version i should download 4.0-beta18 or 3.0-beta10?
[Galaxy S III Android Development] kadopt:
Use 4.0 alpha 6

http://boeffla.df-kunde.de/sgs3/boeffla-kernel-cm-ng/cm12.1_download/Test/
[Galaxy S III Android Development] sajju73:
This is to confirm temasek unofficial v12.3 works fine with boeffla alpha6. Last 12hrs no probs.
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION], after trying to change governor, my device hard rebooted. After coming back on, just a few seconds later on the lock screen, it hard rebooted again. I was forced to reset my preferences.

Not sure if this is a ROM side issue, but just thought I'd let you know
[Galaxy S III Android Development] cébé:
On my CM12.1 bad sound quality, few bass, EQ inoperative → install kernel boeffla 4.0a6 → install boeffla apk → go to the right tab (

I don't understand most of the other settings) → active EQ (eargasm setting), direct DAC → EARGASM → Donation :)

Sometimes (one or two per day), I have random reboot but I don't know if it's the kernel or CM12.1.
[Galaxy S III Android Development] Motodoido:
[MENTION=947981]Lord Boeffla[/MENTION] I'm on cm12.1, when I connect in my usb car sound, with original kernel my S3 mount as usb disk, but with boeffla kernel I get "usb error". Same happens with arter kernel... How to solve this?
[Galaxy S III Android Development] andip71:
As my cm12.x kernels come without support... Probably nothing you can do.

I would suggest you stick to the kernel where it is working then.

Sorry

Andi
[Galaxy S III Android Development] Motodoido:
I prefer stay without mounting usb ;)

Thanks
[Galaxy S III Android Development] shaarky:
Andi actually will it ever be supported or there is some specific reason behind... sorry, I simply didn't read about that anywhere and also you have right to explain nothing, but still I'm wondering. Thank you anyway.

Correction :

From your pages : http://boeffla.df-kunde.de/sgs3/boeffla-kernel-cm-ng/cm12.1/changelog.htm

This kernel is also HIGHLY experimental, same as the currently available CM12.1 roms !!!

Therefore, this kernel comes to you completely unsupported !!!

Still I was considering CM12.1 rather a beta, but I'm sure you have got very good reason.
[Galaxy S III Android Development] andip71:
As long as cm12 is not officially maintained by cm, my kernel will stay an alpha.

In general, development of my kernels on s3 is over. I keep them alive but will not put new functions in anymore. Also will not fix non-critical bugs anymore.

Andi
[Galaxy S III Android Development] Kimenyi:
A death knoll for the S3, if ever I've heard one. Andi, many thanks for the work you've done - and will continue to do - to keep the S3 as up to date as it is running your kernel.

Although many of us don't say so, contributions such as yours have saved us all a pretty penny and have gone a long way to keeping us abreast of the best in the Android world. It is much appreciated.
[Galaxy S III Android Development] andip71:
Thanks buddy.

Yeah, I think almost 2,5 years active development for a kernel for a device that is already older than 3 years and not supported by the vendor anymore is quite ok.

I enjoyed that time a lot. And I have to say: I will ensure the kernel run till then end of the year. Then I consider stopping that as well. I think it is time to move on to new devices meanwhile (although the s3 is still a very good phone).

Andi
[Galaxy S III Android Development] Gokulbalram:
Right now our hopes are Cbalster, Dhiru and Archi, Moster
[Galaxy S III Android Development] TheTurbanater1298:
I can't even think how it will be not being able to use your kernel. ?

Are you sticking around for Android M for this S3, if it comes into existance?

Sent for the sweetest Lollipopped SGS3 i9300
[Galaxy S III Android Development] andip71:
Not yet decided.

But I do not believe CM will have an Android M maintainer for the S3, just like they do not have for CM12.x.

So it is not too likely. But time will tell.

Andi
[Galaxy S III Android Development] TheTurbanater1298:
Yeah I doubt anyone is going jump on being a maintainer for a almost 4 year old phone.

But thanks for the reply. ?

Sent for the sweetest Lollipopped SGS3 i9300
[Galaxy S III Android Development] Warren_Orange:
Can I use Kernel 4 Alpha 3 with the latest BlissPop ROM that was released yesterday? I tried with Alpha 6 and MGH_CM12_Intelliactive_v3_(oc_cpu) profile but my phone gets warm a lot.
[Galaxy S III Android Development] matt1966:
I guess that will break your WiFi connection.

Make a backup and try it.
[Galaxy S III Android Development] Warren_Orange:
I've backed up. Just deciding now whether to try it.
[Galaxy S III Android Development] rp158:
[MENTION=4120014]Warren_Orange[/MENTION]: imho you've no choice: if alpha6 runs, 3 and 4 won't (because of different RAM-disk design).
[Galaxy S III Android Development] Warren_Orange:
I backed up before I flashed alpha 6. So I have a nandroid of stock bliss pop.
[Galaxy S III Android Development] matt1966:
So I tried it myself.

Alpha 3 will boot but it is impossible to get a WiFi connection
[Galaxy S III Android Development] Warren_Orange:
Damn. OK thanks for that. I might try Archie instead.
[Galaxy S III Android Development] KURDKiNG:
Da s2 is 4 and a half a years old and still got lollipop 5.1.1
[Galaxy S III Android Development] TheTurbanater1298:
So? What's your point here? We're talking about maintainers for this device. And seeing as I many people and devs are leaving and upgrading it's getting less likely.

Not saying it's not going to happen, just getting less and less likely by the second.

Sent for the sweetest Lollipopped SGS3 i9300
[Galaxy S III Android Development] KURDKiNG:
Quick quetion, So wen note 2 gets official lollipop are we gnna get bettet support for our lernel cuz our flagships almost da same? Lol nice kernel btw
[Galaxy S III Android Development] arminbih:
The end is near for s3, don't think so :-/
[Galaxy S III Android Development] andip71:
I decide when the note2 really gets lollipop. If I ever gets it...

Andi
[Galaxy S III Android Development] Gokulbalram:
Offtopic:

To the guys discussing about official support, CM had stated they wouldn't be supportikg devices which require PIE binaries (hardware related, not the Slim feature)

---------- Post added at 06:24 AM ---------- Previous post was at 06:20 AM ----------

Also, you guys might want to check for updates here
[Galaxy S III Android Development] JK-FINN:
Is there a way to have an equalizer to bluetooth speakers, when I'm using Boeffla kernel?
[Galaxy S III Android Development] ScratMan38:
You need to use AudioFX or Viper4Android.
[Galaxy S III Android Development] andip71:
As already said by a user above - no way from kernel side.

Bluetooth is a completely digital signal path, Boeffla-Sound can only work on signals that are converted to analog finally (speaker, headphones). And this is done to modify some registers of the audio DAC (which is not used for bluetooth).

All you can do is to use Equalizers that already hook into the signal path before it reaches the bluetooth drivers, like you got already recommended.

Andi
[Galaxy S III Android Development] ansh1996:
i got a problem

hey everyone..

i have a problem with my settings in boeffla kernel.

now i cant tell all the settings but here are the important ones..

cpu 1600-200 no UV

gov set to zzmoove battery

io gov set to sio and zen for int and ext respectively

equilizer and other settings turned off

zRam set to 800 with 4 devices

i dont remember the other things because i dirty flashed my rom again (which btw is BlissPop latest 20150616 nightly 5.1.1).

The main PROBLEM i have is that if i multitask a little bit (a really tiny bit) or if i put my phone into sleep while playing music or something like that, it soft reboots. But thats not all, it also refreshes the whole rom again like i wiped its dalvik cache. it 'optimizes' all the apps again. Now this happens quite often and it sucks the hell out of my battery which otherwise gives a really good backup.

So please do reply if anyone of you have had the same problem, any reply would be greatly appreciated.

Thanks in advance.

P.S. the problem occurs more often if i leave the default settings.
[Galaxy S III Android Development] Andii S.:
soft reboots are rom related

Send with a Lollipoped GT-I9300
[Galaxy S III Android Development] andip71:
And as we all know, most of the time related to the small memory of 1 GB of the S3. This is not adequate to properly run lollipop.

So using zRam is a workaround which can improve the situation.

But this is EXACTLY why my CM12.x kernels are alpha and will always be alpha.

CM12.x will NEVER run 100% perfect and stable on the S3. People have to accept that and move on to a newer phone if they want to run lollipop.

Hard, but it is the truth unfortunately.

On my OnePlus One, Lollipop runs like a breeze with its 3 GB ram.

Andi
[Galaxy S III Android Development] Gangplank25:
So u recommend kit kat instead of lollipop for s3?
[Galaxy S III Android Development] ansh1996:
No soft reboots happen on the in-house kernel of the ROM. But there is a problem of overheating and degraded performance with the same. That's why i shifted to boeffla kernel.
[Galaxy S III Android Development] nkirk:
Hi Andy, very true. However I'm yet to experience a single reboot using your kernel with cm12, except couple of times due to too much UV on 1704Mhz. With the right amount of voltage the device is super stable ans smooth even with max oc tbh.
[Galaxy S III Android Development] andip71:
Well, as I said... this is a big tradeoff. You can use stock kernel where you have no reboots (btw I have no reboots here on JustArchi cm12.1 unofficial as well). But then other stuff sucks.

Or you use my kernel and accept the reboots.

This is a tradeoff and you will probably come close to what you want, but not get everything.

As said, S3 is old and outdated and we should be thankful Lollipop runs as it does at least.

I for myself moved on more than half a year ago to not face instable device and still have latest Android.

Andi
[Galaxy S III Android Development] rp158:
One footnote for balance: I use LP&Boeffla and since 03.15 without any Reboot (Nameless, Slim, Hazy, Euphoria, Dokdo, crDroid, Paranoid). With lite apps and optimized for long battery life. There are little lags sometimes and updates with returning bugs (so converging slowly), but stable as JB-TouchWiz.
[Galaxy S III Android Development] glockaki:
just a bit OT to say a huge THANKS lord boeffla for his efforts and work on our galaxy s3!it was time for me to move on,so i got my new lg g4.i wish there was a way to see lord boeffla developing something in the g4.thanks again lord boeffla!

Στάλθηκε από το LG-H815 μου χρησιμοποιώντας Tapatalk
[Galaxy S III Android Development] Gokulbalram:
I do not think RAM is the issue here. I know I sound stupid, but I believe sources are messed up for us. Have you taken a look at the less powerful Moto G? For a device with a gig of RAM, that thing is pretty smooth.
[Galaxy S III Android Development] andip71:
No, I don't have a moto g.

And sure are sources also messed up.

This is the case when nothing is maintained officially anymore.

We are still on 4.4 kernel code...

Andi
[Galaxy S III Android Development] ansh1996:
yeah you are right, i shouldnt expect so much from my little s3. But i was totally fine with soft reboots, what bothered me was that after every soft reboot the dalvik cache got wiped so it took a huge time to get back to normal, just to do that again.

although, i finally found out what the problem was, basically i always dirty flashed your kernel. So with zRam set to 100 (default setting) all my apps tried to occupy it and hence the reboot. So to fix that i just froze most of my apps and then flashed boeflla and applied a profile from the other thread. Now i dont experience any reboots and everything's smooth as butter.

Thanks for this amazing development and sorry if i caused any misunderstanding.
[Galaxy S III Android Development] Gokulbalram:
I'm not exaggerating, but the Moto G is just as smooth as Flagship devices mainly because it's AOSP and has official Moto support.

Meanwhile the S3
[Galaxy S III Android Development] cheese458:
Thinking about getting an s5. still a good device?
[Galaxy S III Android Development] TheTurbanater1298:
If you want to experience the same problems this device has due to its chipset then yeah.

I would say you're better off with an LG 3 or heck even a HTC one m8. It's more than enough and the HTC looks and feels great in hand. Although a work of advice, the one m8 is a little harder to root and ROM because of a locked bootloader. LG has a great display and camera, so either way you're not going with a bad device.

Or hold on for the one plus two. That phone looks impressive. The predecessor of that phone is still adequate. Cheap and great value for money. CM updates that were initially made for the phone, and still has loads of XDA support.

Buy a Nexus 5/6 or wait til next year for the Nexus 5 and 6 replacements. You can never go wrong with a Nexus. Unless it's a bad one like the Galaxy Nexus. [emoji23] But you'll more than likely get timely updates to the newest and best Android has to offer.

I hope I helped you with your decision. There's a lot to choose from and it all depends on personal preference. That's why i love Android.

The S3 at the time for me was the best option for me. It had baller hardware, had the best version of TW to date.it was all around win for me. But then I bought the HTC one m8 because it looked amazing and everything was perfect, expect for that camera. I still use my s3 for the camera. [emoji23]
[Galaxy S III Android Development] viktor92:
Remember that there are two versions, the one with the exynos octacore and the other with snapdragon 801.

Andi (if I'm not wrong) has a boeffla kernel for the snapdragon version, so for me it's a very good phone.

---------- Post added at 11:07 AM ---------- Previous post was at 11:04 AM ----------

As always I follow the LP thread for the S3, but I'm running Blekota Note 4 lite 4.4 (KK 4.4.4) with latest Boeffla 7.6 uber 6, and cannot be happier with it.
[Galaxy S III Android Development] cheese458:
thanks for a good response. I dont want a huge phone and I think the one plus one may be too big. Thinking that nexus 5 could be the phone for me now
[Galaxy S III Android Development] TheTurbanater1298:
I'd wait til the revamped Nexus 5. It's said to be released this year.

Sent from the sweetest lollipop'd SGS3 i9300
[Galaxy S III Android Development] cheese458:
Won't that be around November? Don't really wanna wait that long :P
[Galaxy S III Android Development] TheTurbanater1298:
It's worth the wait. You'll have longer official support and it's better hardware. [emoji12]

Sent from the sweetest lollipop'd SGS3 i9300
[Galaxy S III Android Development] 2phazt:
Have a nice trip ?
[Galaxy S III Android Development] TheTurbanater1298:
Anyone know good LMK values for CM 12.1 build 9?

Sent from the sweetest lollipop'd SGS3 i9300
[Galaxy S III Android Development] 2phazt:
Or for Temasek 11.5 ?
[Galaxy S III Android Development] Maxpawner:
Is boeffla kernel for archi beta 9 still working on archi beta 10?