yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] nkirk:
Yes it does, but expecting a new version from Andy since the ramdisk is one month old.
[Galaxy S III Android Development] andip71:
... After I return from holidays, yes ☺
[Galaxy S III Android Development] HorstiG:
Hi

There is a small ZIP File to remove Problems charge the Battery in Offline Mode.

It´s not a Kernel Problem. It´s a Problem from Carbon and other ROM´s with CM 10.2

http://xdaforums.com/showthread.php?t=2137018&page=177
[Galaxy S III Android Development] rascal0pl:
haha, what?

Yeah it will be pointless when MHL driver sources gets released, but now dual booting is must have for me (and not only me).

Why ? :(

I know that, there are many alternative kernels, but your control app is the best (and sound recording in videos also)
[Galaxy S III Android Development] andip71:
Quite easy, quoting the OP:

The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. It aims more for a good mix of all, not sacrificing stability and functionality in the end.

And - most important: It aims to stay quite close to stock !!! Which in fact for the CM kernel means now... close to CM kernel sources.

Dual boot is not close to stock anymore.

But most important: I only include in the kernel what I also will use. And I am not interested in dual boot.

Andi
[Galaxy S III Android Development] rimad:
Dual boot is STUPID! Stupid on computers and even more on the phones!
[Galaxy S III Android Development] andip71:
Well, I do not think it is stupid. But I do not need it and the massive changes required for it are not worth the work and hassle.

Andi
[Galaxy S III Android Development] striked0wn:
It isn't stupid.. Very useful on computers.. Linux and windows (use it by myself).. But on phones it's (in my opinion) solved very bad..:/.. And the method on computers is completely different.. There you're usually have "real partitions".. And on phone it's just an virtual partition in img file.. You have one kernel for different systems.. And 2 or up drivers eg for gpu..

Sry for very bad explaining in english.. There are much more differentials.. But my english is too bad.. :P.. (Search for "MBR".. For method on computers).. On phone the kernel loads an image from an existing partition from the 1st rom..
[Galaxy S III Android Development] JustArchi:
Hey Andi.

Could you take a look? :o Just an update should fix this issue. It's important for me to get either "root" or uid "0" instead of such string.

Especially because...

It's printed in stderr... :eek:

Thank you.
[Galaxy S III Android Development] shitman66:
I'll try it again,my lord. And if there is anything weird, i'll tell you. :D
[Galaxy S III Android Development] andip71:
Archi, sure. When I am back home again :)

What does it break for you?

Btw did not touch this command at all. So I am a bit surprised.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] JustArchi:
https://github.com/JustArchi/ArchiD.../0/ArchiDroid/Scripts/ArchiDroid_FstrimAll.sh

This :o. And not only this but all my scripts which rely on "whoami".
[Galaxy S III Android Development] andip71:
Archi,

Ok. When I am back home again I will check it.

Just for me: new issue or was it always the case and you just started using it?

Thanks

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] JustArchi:
It worked fine on temasek kernel (and stock as well I guess) but this is the first time using a script on your kernel so I guess it's rather old issue than new one.

It's a misc issue because as you can see native CM's whoami works, just your ramfs one doesn't.
[Galaxy S III Android Development] andip71:
Well, then I know already how to fix it.

Will just not symlink it to the busybox anymore. That is super easy.

But in the end it is a busybox problem even. Not nice :mad:

Busybox is a b****... I constantly say that. Hehe

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] andip71:
Archi, you have a PM with a test kernel for the reported issue :)

Andi
[Galaxy S III Android Development] alirezaafkar:
One leg in home, one in UK :D
[Galaxy S III Android Development] andip71:
Yeah, unfortunately. Will even not be the last time :mad:

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] JustArchi:
Enjoy your trip, it's free, right? :D
[Galaxy S III Android Development] HorstiG:
Schwimmflossen nicht vefgessen

HGT - Galaxy S3 blue - Carbon-JB 4.3.1 - Boeffla Kernel CM10.2
[Galaxy S III Android Development] andip71:
Yes... Free. Company pays, but they want me to work there... Grrrr :)

Btw - will soon have a new test kernel for you mate. Sammy version in testing already.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] andip71:
New CM12.1 alpha

Hi all,

as promised, a new alpha for CM12.1 based on latest unofficial CM12.1 build 11 by JustArchi as of 10.07.15.

Version 4.0-alpha7

11.07.2015

Update: Ramdisk updated to unofficial build 11 of 10.07.15

Fixed dm-crypt not accepting discard requests which resulted in failed encryption (CM10.2 regression) - by JustArchi

Enjoy

Andi
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION], Archi and Dhiru had made some changes to Bluetooth. Thought you'd want to know. Bluetooth is snappier and supposed to fix Streaming (I'm not sure about the streaming part).
[Galaxy S III Android Development] senthilaca:
Working fine AS USUAL with RR 5.50 .. Thank you [MENTION=947981]Lord Boeffla[/MENTION] :)
[Galaxy S III Android Development] andip71:
Could not see any obvious commits in ArchiKernel for it. So not sure. But if you can point me to it, I am happy to check.

Otherwise it might be completely in the rom, I do not follow i9300 development regularly anymore.

Andi
[Galaxy S III Android Development] matt1966:
Also working with Bliss Pop 3.5 nightly from June 16
[Galaxy S III Android Development] rpdroky:
Excuse me sir ,i don't want to be rude , but could you update zzmoove governor to?

Cheers :highfive:
[Galaxy S III Android Development] JustArchi:
Because there are none.

All kernel-related commits can be found in AK source tree, as my CM uses ArchiKernel as stock kernel (simplified, stripped off custom features such as OC).

Most fixes are related to device tree though, our kernel just missed some core parameters that were introduced in newer vold currently used in CM12.
[Galaxy S III Android Development] Gokulbalram:
The new stuff is in the device trees. You always said Bluetooth sucked on the S3 so I thought I'd let you know about this :P
[Galaxy S III Android Development] sperelli:
so, could latest ad + latest boeffla kernel solve bt issues or better stay on ak ?
[Galaxy S III Android Development] andip71:
First, this kernel is not in active development anymore.

So I am not sure if that will ever come.

And for sure it doesn't come before it is clear why latest zzmoove versions do not yet run stable on the Galaxy s5.

I don't want to open a new issue for nothing.

Andi
[Galaxy S III Android Development] andip71:
Ok. So asking again... No Kernel related changes to bt then?

Andi
[Galaxy S III Android Development] rpdroky:
Roger that , BTW the latest alpha is rock stable ! :victory:

Cheers :highfive:
[Galaxy S III Android Development] mhmd_azmi:
Is this kernel work with temasek unofficial cm12.1?

Sent from my GT-I9300 popped with Temasek Unofficial Cm 12.1
[Galaxy S III Android Development] Yahoo1:
Yes, alpha 7 version.
[Galaxy S III Android Development] tejas999:
[MENTION=947981]Lord Boeffla[/MENTION] ZRam isn't working in alpha 7 (for me atleast :p)
[Galaxy S III Android Development] andip71:
Cannot confirm that.

See screenshot attached.

Andi
[Galaxy S III Android Development] tejas999:
I enabled it, then it was stuck on 'This can take several minutes, Do NOT interrupt' for 10 minutes, then I pressed back, disabled it (it was not actually enabled) and tried enabling it again and it worked this time :)
[Galaxy S III Android Development] KURDKiNG:
So like lets say if we oveeclock it too much and it keeps freezing and rebooting witch file do we delete da config file?? And wer is it
[Galaxy S III Android Development] ansh1996:
I think there's a flashable reset zip under /sdcard/boeffla-kernel data, that you can flash in case you run into a boot loop.

Hit thanks if i helped ! :)

Sent from a blisspopped I9300 with the power of xposed.
[Galaxy S III Android Development] KURDKiNG:
Thnx mann dat helped
[Galaxy S III Android Development] andip71:
All explained on the homepage in faq section.

Sorry guys, but have not written that for not being used.

Andi
[Galaxy S III Android Development] Mad_Lion:
Hi [MENTION=947981]Lord Boeffla[/MENTION]. I have one small question. I know this is just cosmetic and minor thing but still: Is possible to move SELinux strict toggle to left side where there is free space? That way app would have better look if those two toggles would've been side by side , as empty area in green lines could be removed.

Anyway, would there be any negative consequences if I always have Enforcing mode enabled? I through It's turned on by default but when I checked It wasn't. Or is this because I flashed xposed? Gave "SELinux strict" a test now and I will see if it breaks anything.

BTW: Thank you for all your hard work and your kernel. Using it since ancient TW times and I think S3 would be useless without it :)
[Galaxy S III Android Development] andip71:
Hehe,

no, this is not possible as this area is only free for users that do not have the donation app version.

Users with donation app see here more information displayed about latest stable/test kernels and get a color indication when a new kernel version is available.

On Android L, selinux is set to enforcing by default. So nothing is wrong, actually it is recommended for L.

But yes, for some stupid xposed (yes, I confess again I am not a xposed liker, hehe) modules you need to fallback to moderate as they otherwise do not work. Only I have been told that, I stopped using xposed 2 years ago completely, so can only second what I heard.

Andi
[Galaxy S III Android Development] robikewl:
I have been using JustArchi's and now arter97's CM12.1 roms. I installed the kernel 4.0-alpha7 few days ago, I appreciate improved sound quality.

The issue I am facing now is that- when a call comes in the phone starts ringing, but the screen takes about 10 secs to come up making accepting calls a hit-or-miss.

I did not notice issue with stock kernels on JustArchi's and arter97's ROMs, I am using the arter97's latest v12.3.

After installing the kernel and app, I had only enabled Boeffla sound(and some Miscellaneous options in it) and unchecked the 'SELinux strict' to set SELinux status to Permissive, other options were the default. I loaded the 'Standard' from Presets option in Menu also later- didn't help.
[Galaxy S III Android Development] JK-FINN:
Is there a smaller kernel version that only includes Boeffla sound? I would like to use such version with JustArchi CM 12.1.
[Galaxy S III Android Development] andip71:
No. There isn't, at least not by me.

Andi
[Galaxy S III Android Development] JK-FINN:
Could someone please check, what are the default LMK values with latest boeffla: for foreground and visible applications, secondary servers, hidden applications, content providers and empty applications?
[Galaxy S III Android Development] sleeper994:
This is a CM based issue with some devices (including our GT-I9300, OnePlus One, etc.), this has nothing to do with kernel.
[Galaxy S III Android Development] robikewl:
Ok, I have reverted to backup of arter97's 12.3 with stock kernel, not hitting the issue now. Will lookout for the fix from CM
[Galaxy S III Android Development] andip71:
Don't expect any fix coming from CM anymore.

The S3 is dead for a long time regarding official CM.

Andi
[Galaxy S III Android Development] kusakhan:
kindly update driver mali r5p2-00rel0.....
[Galaxy S III Android Development] andip71:
Kindly read this kernel is only in maintenance. So no new features will be added anymore.

Until something gets broken and is fixable, there will not be new versions anymore.

Andi
[Galaxy S III Android Development] 2phazt:
I can somehow understand you, Andi - but it's sad that you let the s3 die since you are one of the most important maintainers of the device. ?
[Galaxy S III Android Development] shaarky:
Is there any motivation which would convince you?

Eg. doing something as the only one of the planet, that is nice, isn't it? ?
[Galaxy S III Android Development] andip71:
Yes. Convince cm team to officially support the s3 again, then everything is back under control a bit more.

But no,... the s3 had it's life. And every life comes to an end.

I have two other main devices to actively develop, no Exynos devices, so I have to focus myself on that.

Thanks for understanding

Andi
[Galaxy S III Android Development] mcqaissi:
I'm on cm 12.1 and using arter97-cm

My question if I can use boeffla sound control?
[Galaxy S III Android Development] senthilaca:
Yes you can use.. arter97 kernel supports boeflla sound engine..
[Galaxy S III Android Development] TheTurbanater1298:
[MENTION=947981]Lord Boeffla[/MENTION] will you be getting the One Plus Two?

Sent from the sweetest lollipop'd SGS3 i9300
[Galaxy S III Android Development] Gokulbalram:
Getting CM to officially support the i9300 is near impossible considering that CM specifically said that they'd be dropping support for devices with PIE dependencies (hardware).

Yes, i9300 has PIE dependencies.
[Galaxy S III Android Development] andip71:
Yep, I am fully aware of that.

And as I do not want to support all different unofficial CM based roms (which are rarely compatible anymore), I stopped active development for it as well.

Without an official CM maintainer which people follow with their development the situation is just getting more and more chaotic - which is a waste of time for me.

So: No official CM = no actively developed kernel anymore. As simple as that :)

Andi
[Galaxy S III Android Development] rp158:
Andi, save your answer - maybe you can use it again :)
[Galaxy S III Android Development] Gokulbalram:
We do get official Omni though :P
[Galaxy S III Android Development] SirKunon:
Thanks Andi for support. I have my old s3 on the shelf and sometimes play with your roms. I see you are tired with maintaining this device but I must admit that you can do miracles with this oldtimer.

I wish to have such a knowledge. Even if you will drop future updates you made a great work and thank you for all your efforts.

Wysłane z iPhone za pomocą Tapatalk
[Galaxy S III Android Development] JustArchi:
And I'm glad they decided so as the i9300 situation is utter crap.
[Galaxy S III Android Development] Gokulbalram:
Isn't it fun?
[Galaxy S III Android Development] JustArchi:
It was fun a year ago, now the only thing that is common is being angry and wanting to throw i9300 into a trash.

Same what happened with codeworkx, xplodwild or entropy512.
[Galaxy S III Android Development] Gokulbalram:
Ouch.

We know who to thank for that.
[Galaxy S III Android Development] nicesoni_ash:
Hi Andi,

I have a query related to your app and the value it shows for charging current. By default S3 had about 1000 mA and it shows the same in different apps while charging including your Kernel config app too.

I recently purchased a chager that givers 2.1 mA power so I increased the charging capacity to The 1600 in your Kernel config app and charge with it. Problem is your apps shows the current as 1600mA but other apps still shows the power as 1000.

So what's wrong, s3 not able to get charged more than 1000 or what?

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
I think this has been answered trillion times already.

The apps you mention cannot really determine the charge current, as the S3 has no sensor to measure it.

So they interpolate the voltage over the time and try to calculate charge rates. Sometimes works, sometimes not, but it is not very precise.

The current shown in my app is what the charging driver "negotiated" with the charger. So I would assume this is more real than anything the other apps show.

However - the only real test is:

Charge the phone with your new charger and 1600 mA from 0 to 100% and stop watch the time.

Then do the same with 1000 mA stock value and compare.

I say - it will charge much faster if all goes well.

Be careful to not fry your phone btw :)

Andi
[Galaxy S III Android Development] nicesoni_ash:
I will be careful. Thanks for your reply. [emoji3]

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] Darkened_Sky:
[MENTION=947981]Lord Boeffla[/MENTION]

I have a queston concerning the compilation of your cm kernel.

My problem is to set the correct version string (name) for the kernel, because I know the string must start with "Boeffla-Kernel" sot that it gets recognized by your config app. Normally I use in the menuconfig the localversion option, so that it gets appended, but for some reason it won't be displayed in "About Setttings" (only the linux kernel version is displayed) and the config app does not work.

If I first use "export KBUILD_BUILD_VERSION="Boeffla-Kernel-........."" the config app works and displays the whole name but in "about settings" "kernel version unavailable" is displayed.

I hope this sounds not totally noobish, but I really tried so many possibilities to work it out by myself :) So maybe you could explain me how to do it correctly? :)
[Galaxy S III Android Development] andip71:
Easiest is to look in my build script in the root folder (called bbuild.sh).

Basically I replace some text parts in file /scripts/mkcompile_h to achieve a completely custom kernel name.

Hope that helps

Andi
[Galaxy S III Android Development] andip71:
New cm12.1 NG beta kernel

Hi guys,

a new beta kernel for CM12.1 (NG version) is available for you.

Version 4.0-alpha8

04.08.2015

Note: You need Boeffla-Config app 2.1.94 or higher to use the new features

Enabled a bunch additional tcp congestion algorithms that can be selected in Boeffla-Config app (click here and here for more information)

Update: Ramdisk updated to unofficial build 13 of 31.07.15

Kernel build process now able to use ccache

Internal build script enhancements

Have fun

Andi
[Galaxy S III Android Development] puhu:
Whts new tcp settings mean?

puHu
[Galaxy S III Android Development] craP_cillA:
just flashed alpha 08 but after that the wi-fi isn't working at all!! :/ it doesn't connect and i also cannot activate it via the quick tile or via the system settings..

i'm using the latest boeffla app and blisspop rom 3.7!
[Galaxy S III Android Development] andip71:
I put two links in the change log to describe that.

Blisspop seems not compatible with Justarchi build 13...

Sorry, nothing I can and will do. You know why...

Maybe an updated Blisspop will solve that one day.

Andi
[Galaxy S III Android Development] craP_cillA:
ok thanks! :)
[Galaxy S III Android Development] rpdroky:
I just flashed alpha8 on Dokdo Project 6.5.3 and i don't have any problem , everything works including Wi-Fi

Cheers :highfive:
[Galaxy S III Android Development] andip71:
Some roms are compatible, some not yet, some maybe never.

Andi

Gesendet von meinem A0001 mit Tapatalk
[Galaxy S III Android Development] andip71:
Strange thing is... a user reported incompatibility with Temasek CM12.1, wifi not working.

So I installed Temasek for a quick test and surprise... wifi working fine for me, see screenshot.

Anyways, JustArchi released a new build 14 yesterday, so I will push a maintenance update out soon again.

Andi
[Galaxy S III Android Development] andip71:
New alpha

Good morning,

as indicated already, after JustArchi pushed build 14 out yesterday, here we go for another maintenance release of my CM12.1 kernel.

Version 4.0-alpha9

05.08.2015

Note: You need Boeffla-Config app 2.1.94 or higher to use the new features

Update: Ramdisk updated to unofficial build 14 of 04.08.15

Note: If that does not run on other roms than JustArchi CM12.1, please report but do not expect me to change anything. I selected JustArchi CM12.1 as one and only reference, and as long as the kernel runs fine here I consider it being ok.

Enjoy

Andi
[Galaxy S III Android Development] 2phazt:
I'm on Temasek v15.3 by Darkened_Sky with boeffla alpha8 u600 by ZaneZam and Wifi works fine.

Btw which TCP congestion do you recommend for 90% wifi usage?
[Galaxy S III Android Development] andip71:
Westwood. Westwood is default in my kernels for years already, for a good reason (while cubic is the stock standard).

Andi
[Galaxy S III Android Development] entermetallica:
Sorry for the newbie question, but how do you get root privileges on this kernel? Do I have to follow the same procedure as the stock root method?
[Galaxy S III Android Development] andip71:
Yes.

Easiest is to flash Chainfires SuperSu.zip in latest version in recovery. Done.

Andi
[Galaxy S III Android Development] craP_cillA:
just a little update on "my" problem: alpha 09 and blisspop v3.8 works perfect!! no wi-fi problem anymore! :) :D
[Galaxy S III Android Development] andip71:
Cool. Thanks for sharing.

Andi
[Galaxy S III Android Development] whatsgood:
[MENTION=947981]Lord Boeffla[/MENTION] I know you say you're not adding features anymore for your cm12.1 kernel, but I'm asking because it's a feature that we previously had before, but got removed because it affected WiFi behavior. I wanted to know if you could add frandom back as I don't think the WiFi issue is present anymore.
[Galaxy S III Android Development] andip71:
What makes you believe, this is not existing anymore? Any pointers?

I also had the same on the OnePlus with frandom, had to remove it there as well. And I consider CM on the Bacon top-notch.

Andi
[Galaxy S III Android Development] whatsgood:
Well, on archis AD 3.1 he has frandom activated as a default option in the archidroid app, and I haven't seen any complaints about WiFi on the thread, so it lead me to believe that frandom doesn't cause WiFi issues anymore.
[Galaxy S III Android Development] andip71:
I can try it once more, but I am not very optimistic.

We will see.

Andi
[Galaxy S III Android Development] flopponator:
[MENTION=947981]Lord Boeffla[/MENTION] is it possible to get Boeffla sound on all devices like v4a? I absolutely loved it on my s3 and still wanna keep it.
[Galaxy S III Android Development] andip71:
V4a is a software driver, not running in kernel space.

Boeffla sound is a hardware kernel driver.

So it is completely different things and hence the answer is no.

If you like v4a, just use it as it is?

Andi
[Galaxy S III Android Development] myshakugan:
I think he meant that he wanted to use Boeffla sound on all roms, regardless of whichever kernel he's using.

---------- Post added at 03:45 AM ---------- Previous post was at 03:43 AM ----------

Since as Lord Boeffla already mentioned that it's a kernel specific feature, you can only use it on roms whose kernel has boeffla sound built in. Some of the s3 roms I know has boeffla sound built into the stock kernel, for example, Blisspop and the unofficial temasek builds by Darkened_sky.
[Galaxy S III Android Development] andip71:
Well, are you sure frandom is also active and used in Archidroid?

Because I just compiled it in again, and same effect as before - no wifi working.

So, when you are on AD again with his kernel etc, can you please try to do the following in the terminal and let me know the output:

lsmod

ls -la /dev/random

ls -la /dev/urandom

Thanks

Andi