yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] HitFan:
Governor

Which governor is better? PegasusQPlus or PegasusQ with boeffla-moderate preset?

And I have one more question, is there any app, that shows now many cores are running now?
[Galaxy S III Android Development] ScratMan38:
Eagerly waiting...:p
[Galaxy S III Android Development] viktor92:
Because if it releases unused memory again, it will be a better performing, and any help for the good old S3 is welcomed, am I wrong ?? :)
[Galaxy S III Android Development] zaid.oj:
[MENTION=1045701]lordbo[/MENTION]effla , sorry if am going out of topic but, am considering to buy Asus zenfone 2.

Am not asking if you are going to develop for it, but do you know if it's developer friendly, specially when it's intel processor?
[Galaxy S III Android Development] andip71:
In theory. But I recall arter had lots of trouble using vnswap on the s3. I think in the end he reverted it again or wanted to do it.

And: there are two things why it is not likely I will do it:

- First paragraph in OP of this thread

- when I am not completely wrong, vnswap is not available in 3.0.x kernels. And I do not like backporting stuff from higher Linux versions, refused to do that on f2fs all the time too.

I have no clue, honestly. I would need to educate myself first.

But try to find out quickly on xda how the development scene looks like. I.e. are there many custom roms/kernels/mods you can find, or almost none.

That should help in your decision.

Andi
[Galaxy S III Android Development] MBurns2:
delete please.
[Galaxy S III Android Development] darkbahamut:
I seem to have come across a new issue with kernel v2.7 CM11 NG with the recent google play services update. If you have this kernel installed, install the google play services update then reboot the device will never go to sleep again with 'systemupdateservice' keeping the device awake constantly (100% wake time). It's a kernel issue because if you use a different kernel like the CM11 default one then the issue doesn't occur.

We have two galaxy S 3's here both running CM11 with Boeffla 2.7 and both show the same issue with I can repeat with 100% success even after a clean flash with the following steps:

1. Format data + cache

2. install CM11 (snapshot 12 & latest nightly both have the issue)

3. Update stock google apps and google play services then reboot device

4. Device will function normally and will go into deep sleep.

5. Reboot to recovery and flash Boeffla kerenl 2.7 CM11 NG

6. Device will shows 9 seconds deep sleep but will never deep sleep again (Still 9 seconds after 3 days)

The issue only occurs once you have both the latest play services and Boeffla install and then reboot. If you install the kernel first, then the play services update but do not reboot then the device will behave normally untill you reboot, then it will fail to deep sleep again.

Hope you get a chance to look at this issue even though CM11 is mostly out of development now. It ran really well till this happened a few days ago :(
[Galaxy S III Android Development] andip71:
Wrong. Not kernel related at all. Google play update issue which is well known. It happens on all devices with all kernels.

Cm already included a fix in the latest cm12 roms. Will soon reach cm11 too.

There is a good working workaround till the fix gets into the next nightlies.

Go to my OnePlus kernel thread to search for the link of the workaround.

Andi
[Galaxy S III Android Development] myshakugan:
I'm on cm11 and I can confirm that google play services prevents the device from going to deep sleep.

Lord Boeffla, sorry for the ot, but I was wondering, if I use privacy guard and deny the google play services permission to keep the device awake, will that help solve this issue?

Edit: Never mind, I just searched your OPO thread and saw that a user used the same technique on cm12 and got good results, so I'm gonna try it on cm11 too. :)
[Galaxy S III Android Development] ZaneZam:
The cm12 method might not help entirely. I had to deny autostart in addition for play service in privacy settings on cm11s ;)
[Galaxy S III Android Development] myshakugan:
I denied wake up and keep awake and rebooted the device, and it seems to be working now, didn't bother to deny autostart as it says 'never used'. :3
[Galaxy S III Android Development] sashundera:
Why do apps open so slowly after flashing CM 12 NG? Its laugable, sms app takes 10 seconds to load.
[Galaxy S III Android Development] Gokulbalram:
Messenger takes 3 seconds here
[Galaxy S III Android Development] sashundera:
After tweaking with the settings it opens fine now, but the capacitive buttons are constantly lighting up. On my temasek ROM I made them so they light up only when I touch them and disappear after a second. But it doesn't work now!
[Galaxy S III Android Development] myshakugan:
You need to disable light up on touch from the boeffla config app.
[Galaxy S III Android Development] sashundera:
I did but its still the same.
[Galaxy S III Android Development] andip71:
Press power key after having done the settings.

Andi
[Galaxy S III Android Development] sashundera:
I'll try tomorrow and report on it, thanks !
[Galaxy S III Android Development] keronja:
I installed omni ng kernel now I can't boot to system. After S3 boot screen I get only black screen.
[Galaxy S III Android Development] andip71:
What rom do you use?

This is the typical symptom of flashing a wrong kernel type.

Andi
[Galaxy S III Android Development] Gokulbalram:
I have a feeling he flashed your 4.4 Omni kernel on 5.1 Omni
[Galaxy S III Android Development] daniel.mota:
Well, I've been using Marcox89's cm11 rom with 2.7 NG kernel and I don't think I've ever had such issue.

I also use xposed with greenify, although I don't greenify the google services.
[Galaxy S III Android Development] Killerdog:
Hi Lord Boeffla, can you add the possibility to emulate a CD-ROM please il your build (instruction Here)

I really need it for my daily use (IT tech) as i use Drivedroid for my work, I'm stuck with Sammy Rom 4.x.x (official or not, currently N4 Port by Blekota with aGNi PureStock 5.5 it's the only one i found with cd-rom emulation capability.

I want to update to lollipop with BlissPop or NamelessROM but i'm stuck for this functionnality.

Apparently i'm not the only one to want this possiblility (maybe we are two :p )

If you already experiment this function, and have it working in one of any configuration (but 5.x LP) please give me your matching solution.

Thanks
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION] had stated that he wouldn't be adding features in his OP.
[Galaxy S III Android Development] iamdutchy:
the beoffla config app shows you how many cores a re running, what speed and the time in state.
[Galaxy S III Android Development] MTsCetin:
Dear [MENTION=947981]Lord Boeffla[/MENTION]

thank you so much for the kernel, it's fast and stable but I have to report a problem.

I'm using Temasek's CM 12 with Boeffla kernel a9 everything is fine (pegasusq / deadline 128 /Zram 4X 600Mb / Swappiness 85) It is fast and responsive.

But with Boeffla kernel a10, all I can see is "mmcqd/0" on most recource intensive processes [Cool Tool] It is very laggy, opening apps takes so much time so on...

if you want I can reinstall a10 and provide logs. Thank you...
[Galaxy S III Android Development] andip71:
But it is the truth.

Next cm11 nightly has the fix included to be back to normal.

And yes, the issue popped up with a recent update of play services only.

Sorry, I am not including new features anymore in the s3 kernels. See op.

Really? Then you know more about my app than me [emoji2]

It shows how much time was spent on which frequency, but not how many cores are online etc. For that you need a 3rd party tool like Chainfire's perfmon etc.

Maybe Temasek is not getting along well with the currently included ramdisk.

A log would not help here.

Stick to alpha9 for now when it works for you (makes me wonder if you use an old version of Temasek btw). And then try a11 again once it comes out.

Andi
[Galaxy S III Android Development] Killerdog:
Thanks for your answer.

I understand your position, and hope for somebody add this to cm12 (it's natively supported in CM11 Snapshot M12)
[Galaxy S III Android Development] andip71:
CM12 NG kernel update

Hi all,

quick update of the CM12 NG kernel (the non-NG kernel version is not updated as I consider to remove it completely).

CM12 - Version 3.0-beta11 NG

24.03.2015

Internal kernel busybox updated to latest version 1.23.2 (self-compiled from sources, www.busybox.net)

Update: Ramdisk updated to unofficial weekly 9 of 24.03.15

Compiled with completely new build process (this is now contained in my repo)

Enjoy

Andi
[Galaxy S III Android Development] 4rch0:
thanks for the update

CM12_V3_alpha11 --> Bootloop temasek cm12 v8.8 return to alpha10 everthing fine

anyone else?
[Galaxy S III Android Development] andip71:
Just once again... My cm12 kernel is optimised for unofficial cm12 by JustArchi/Moster2.

And alpha11 is optimised for werkly 9 that came out today.

If Temasek 8.8 does not boot, it is too old or incompatible. Then you need to stick to alpha10 until it gets compatible again.

Andi
[Galaxy S III Android Development] motshek:
ArchiDroid 3.1 cm12 bootloop in alpha11. Work good alpha10...
[Galaxy S III Android Development] sevenshorseman:
Flashed on latest RR.

No problems?
[Galaxy S III Android Development] fonfox:
For me alpha11 works fine with temasek V8.8

Has anyone tried new 5.1 cm from arter whith this kernel
[Galaxy S III Android Development] superchandan007:
Latest RR means. Which build bro?

20150319 or 20150324???
[Galaxy S III Android Development] voorhees13:
Flashed the update through action>load &flash kernel in your app,all went fine.Running temasek 8.8 :good:
[Galaxy S III Android Development] ivano949:
Hi [MENTION=947981]Lord Boeffla[/MENTION], love so much your Kernel... I'd like starting playing with tunable governor and I have a question: is there any tutorial explaining what is expected when modifying every single setting in this screen?

Thank you
[Galaxy S III Android Development] sevenshorseman:
What does "latest" mean to you? Not the one before the latest build, the latest build.
[Galaxy S III Android Development] superchandan007:
Hello [MENTION=1470009]boeffla[/MENTION]

What is UMS mode mean... I didn't get what is it till now...:D:confused:
[Galaxy S III Android Development] Gokulbalram:
If you're had an old Android device, you'd understand. UMS is another mount technique, which mounts your Storage as a separate partition on the PC. It's much much faster and better. It's more preferable than MTP
[Galaxy S III Android Development] khanmein:
no such issue on v8.8 & is working. i can also confirm is either u or phone issue.
[Galaxy S III Android Development] andip71:
There is no single resource about tunables of governors on the web up to my best knowledge.

The tunables are specific to the individual governor, so you need to learn about every governor and it's tunables individually.

For zzmoove, ZaneZam has an own thread here on XDA where he explained also the tunables.

For the rest of the governors, you need to try and google. You will get some results...

Andi
[Galaxy S III Android Development] tommi.a:
I'd like to use the TWRP actions to update to latest CM11 and afterwards reinstall Boeffla-Kernel.

How is the order I have to follow?

I guess:

0. Tick Queue mode

1) Backup <accept default name>

2) Install internal cmupdater/cm-11-2015-0323-NIGHTLY-i9300.zip

3) Install internal boeffla-kernel-data/boeffla-kernel-2.7-CM-cm11.0-NG.zip

4) Wipe Dalvik/ART

5. Execute Queue

Is that order complete and correct?
[Galaxy S III Android Development] andip71:
Yes, basically it is correct.

Two comments:

- step 4 (wipe dalvik/art) is not required, the CM rom installer wipes dalvik/art anyways during the installation

- if you want to do it that way, make sure you do not have the kernel survive mode activated (as step 3 would not have any effect then), if you have survive mode enabled you can even remove step 3

My way is always (I have kernel survive mode on):

- step 1 is backup

- step 2 is installation of new cm zip

- execute

Andi
[Galaxy S III Android Development] tommi.a:
Thank you! The short way worked exactly as you described.
[Galaxy S III Android Development] andip71:
Good to hear.

Yeah, this feature is quite cool and convenient, isn't it?

I usually never praise my work, but this somehow makes my app feeling much more "complete".

Andi
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION], I tried my 'AnyKernel' Boeffla zip and the Config app wouldn't recognize the kernel. Apparently it's because SE Linux is set on Enforcing

I'm using CM12.1, any ideas?
[Galaxy S III Android Development] andip71:
No, the app can work with kernels in enforcing mode. My OnePlus and S5 kernels are also in enforcing.

You need to do more changes to the ramfs. Have you included the bccontroller script and the kernel busybox etc?

Andi
[Galaxy S III Android Development] Gokulbalram:
Yes I have. As far as I can remember, the config app used to work with Omni and Slim.
[Galaxy S III Android Development] andip71:
Check the bc.log file in boeffla-kernel-data folder for errors.

Andi
[Galaxy S III Android Development] Gokulbalram:
This is what I get:

26.03.2015-13.23.59: Start Boeffla-Config V2 2.1.68
26.03.2015-13.23.59: Check for root...
26.03.2015-13.23.59: Root found.
26.03.2015-13.23.59: Busybox in /sbin: yes
26.03.2015-13.23.59: Busybox in /system/bin: yes
26.03.2015-13.23.59: Busybox in /system/xbin: yes
26.03.2015-13.23.59: Kernel version: Linux version 3.0.101 (Boeffla-Kernel-3.0-alpha10-CM12.0-NG-i9300-20150310@andip71) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Tue Mar 10 11:45:36 CET 2015
26.03.2015-13.23.59: Exception: java.io.IOException: Error running exec(). Command: [/res/bc/bccontroller.sh, get_kernel_version2] Working Directory: null Environment: null
Message: Error running exec(). Command: [/res/bc/bccontroller.sh, get_kernel_version2] Working Directory: null Environment: null
Line: 211
Class: java.lang.ProcessManager
Method: exec
26.03.2015-13.23.59: Kernel specs: i9300;cm;cm12.0;http://boeffla.df-kunde.de/sgs3/boeffla-kernel-cm-ng/
26.03.2015-13.23.59: zRam devices: 4
26.03.2015-13.23.59: ASV/PVS level: 6
26.03.2015-13.23.59: busybox mkdir /data/.boeffla; busybox chmod 777 /data/.boeffla
26.03.2015-13.23.59: Check for Boeffla-Kernel...
26.03.2015-13.23.59: Exception: java.io.IOException: Error running exec(). Command: [/res/bc/bccontroller.sh, get_kernel_version] Working Directory: null Environment: null
Message: Error running exec(). Command: [/res/bc/bccontroller.sh, get_kernel_version] Working Directory: null Environment: null
Line: 211
Class: java.lang.ProcessManager
Method: exec
26.03.2015-13.23.59: No appropriate Boeffla-Kernel or busybox under /sbin found.
26.03.2015-13.24.09: Exiting Boeffla-Config V2
[Galaxy S III Android Development] andip71:
LOL! Ok, no surprise now.

You are using a super old Config app version!!! This version indeed was not able to work with SELinux enforcing kernels.

Why are you using such an old version 2.1.68? We have already 2.1.72 out for many days!!!

Andi
[Galaxy S III Android Development] ettore88:
Hi guys!!!Boeffla works on CM12.1?(NG CM12)THX in advance!!![emoji6]
[Galaxy S III Android Development] sameer23:
No
[Galaxy S III Android Development] Gokulbalram:
Titanium Backup issues :P

I'll set right away!

---------- Post added at 02:20 PM ---------- Previous post was at 01:56 PM ----------

Works alright now! CM12.1 + Boeffla!
[Galaxy S III Android Development] HammDefy:
Found a "small bug":

When Updating alpha10 to alpha11 zRam is deactivated (big Apps/Games end with FCs). After reactivating zRam everything is fine again.

(BlissPop 2015-03-24, SlimGapps, Boeffla)
[Galaxy S III Android Development] khanmein:
no need enable zram also quite smooth. open certain apps like LINE very slow. previously w/o enable zram really lag but now consider ok.
[Galaxy S III Android Development] Gonnelli1355:
Sorry, where did you find CM 12.1?? Are you talking about OmniROM 5.1?
[Galaxy S III Android Development] boyheadkick:
been quite some time since i've been here :D

running CRDroid LP with NG Alpha10 all good, a little laggy but that's a given

when i flashed NG Alpha11 though, i can't turn on wifi..pressing on the wifi button on the notification shade, nothing happens..cant turn the toggle in wifi settings too..flashed back to NG Alpha10 and wifi works again
[Galaxy S III Android Development] andip71:
Your rom is incompatible with the latest version of the kernel.

This will continue like that and even get worse and worse as there is no standard on CM12, so many teams do what they think and implement things when they think.

It is a bit messy at the moment.

My reference was and is and stays Justarchi/Moster unofficial CM12. So alpha11 is optimized to work with latest weekly 9 of that rom.

By the way: New update in my pipeline already. One is to fix the touchkey lights staying on issue when using the latest unofficial CM12 roms I mentioned.

And then I am experimenting whether the kernel works fine with SELinux enforcing mode (which is also my default in the OnePlus and S5 Boeffla kernels for CM12)... so far looking fine, but need some more days to check it out.

(of course it is configurable, so people that need permissive mode for some reason can switch it :D )

Andi
[Galaxy S III Android Development] boyheadkick:
crap, i thought crdroid was based on archi's sources since it's stated in their OP

oh well, their latest build is a month outdated anyways, and i just probably timed my comeback in the s3 world bad since CM already dropped their support for the i9300

thanks for the clarification [MENTION=947981]Lord Boeffla[/MENTION]

BTW, OT, but i'm sincerely sorry for the loss of your countrymen in the recent plane crash..my prayers go out to their families
[Galaxy S III Android Development] katolink:
Thanks Andi. So I understand that the 'touchkey lights stay on' behaviour was indeed an issue. I encountered it as well (and repored it), but I then assumed my settings were wrong, as I eventually succeded to fix it by turning off backlight in phone's settings and turning on 'touchkeys controlled by kernel' setting in Boeffla config app (although I cannot set the duration of the backlight anymore :D ). All the best!
[Galaxy S III Android Development] andip71:
It is an "effect", yes.

Once you switch the touch key light to kernel controlled, the effect does not show up.

But when you select rom controlled, there was the issue where the lights did not stop lighting up anymore.

Reason was a recent change that has been put into the CM12 rom by the mentioned devs. So all worked - of course - before that was changed. Now I have to follow that change, hoping other individual rom devs also put the change in. Otherwise we will have the "reverse" issue with their roms.

This all is quite frustrating...

Andi
[Galaxy S III Android Development] Gokulbalram:
Not Omni, arter had built an experimental CM12.1
[Galaxy S III Android Development] Gonnelli1355:
Oh, thanks!

And how is it working? Did you find any bug as on OmniROM 5.1 (videos, GPS, etc)?
[Galaxy S III Android Development] Gokulbalram:
I'm not sure if it was an issue on 5.1, but I could see tiny glitches on YouTube videos (Not all that frequent, happens rarely). I'm not sure about GPS. Other than that, there were some problems with Package Installer and Clock, but a user managed to upload apks for both, which fixed the issue.
[Galaxy S III Android Development] andip71:
From all what I read so far, it is not yet in a shape to act as a daily driver.

I think we need to give it some more time to become more mature.

Andi
[Galaxy S III Android Development] Gokulbalram:
Yes, I faced only two issues The clock and the package installer which were fixed after replacing apks, it stutters at times (animation stutter). Other than that it was all great, until of course I switched ROMs to something new :)
[Galaxy S III Android Development] andip71:
Your opinion counts

Guys,

I need your opinion quickly.

I have CM12 kernel in version alpha12 in the pipeline already.

Mainly there are two changes:

1) the touch key light control is fixed when switched to "rom controls touch keys" (so the touch key lights not switching off anymore is fixed)

2) the kernel starts by default with SELinux set to enforcing, not permissive anymore (but can be configures in Boeffla-Config to also start permissive again if required). The kernel then finally follows the Android 5.0 security standards.

The second change might mean some frustrations to some as I know some apps (mainly some xposed modules) do only work with the kernel running in permissive mode. So the user has to boot up, reconfigure to permissive and then restart once more.

So the question is... should I release alpha12 with both features included already, are you ready for it?

Of should I just implement the fix for the touch keys and wait with SELinux for the alpha13 release?

Thanks for your opinion.

Andi
[Galaxy S III Android Development] Gokulbalram:
You should implement both. Even if it's going to be a problem. Only an aroma flashable zip would be another option, but that'd be problematic
[Galaxy S III Android Development] sanguinesaintly:
EFS backup from config app

Whereas I'm able to backup the EFS folder directly from TWRP, I don't see any option to do so via the app (donated). Is this by design or am I missing something ? I'm using TWRP 2.8.5.0 and SlimKAT.

Thanks for all your work on the kernel.
[Galaxy S III Android Development] andip71:
There was never an efs backup in the app, and never will.

Once you flash my kernel, the efs backup will be done automatically into folder /boeffla-kernel-data (and if you have an external sd card inserted also to the root of the card).

Andi
[Galaxy S III Android Development] straylight23:
Go for it now. If SELinux mode is changeable via your config app, there shouldn't be any problem for anyone...
[Galaxy S III Android Development] boyheadkick:
imo i think it's safe to go ahead and implement the two changes in the next release, considering that the second change has it's own options in the config app, us users can get by..we reboot our phones all the time anyways, me especially whenever i charge my phone (just to refresh the system)..
[Galaxy S III Android Development] katolink:
I am ready for SELinux enforcing :) I do not use Xposed anyway, especially given its alpha phase. There was an issue with GPS not running in SELinux enforcing mode, but afaik it has been fixed in Weekly 9. Therefore, no frustrations on my side whatsoever! :D On the contrary, my deepest appreciation for your work! Thanks!
[Galaxy S III Android Development] myshakugan:
Go for both. :) As long as there is the option to change it to whichever (permissive or enforcing), I really don't think anyone will have a problem with it.
[Galaxy S III Android Development] andip71:
Thanks for all your opinions, I just started uploading the new kernel :D

Andi
[Galaxy S III Android Development] andip71:
CM12 3.0-alpha12

Hi all,

here we go - CM12 kernel 3.0-alpha12.

Please note, at the same time I decided to finally drop the non-NG version of the CM12 kernel for the S3, as it did not make any sense anymore. So I removed that from downloads and kernel overviews. If you are still on the non-NG CM12 kernel, you will be upgraded to NG automatically if you use load&flash.

Version 3.0-beta12 (NG only)

27.03.2015

Note: You need Boeffla-Config App version 2.1.69 or higher for this kernel !!!

Touch key lights logic fixed (specifically for JustArchi inofficial CM12 weekly 8 and 9 - make sure you switch touch key control NOT to kernel in Boeffla-Config)

This kernel version now boots in SELinux enforced mode by default, according to CM12 standards.

If you want to still run in permissive mode (e.g. for some xposed modules working), you can switch this in Boeffla-Config settings -> kernel startup options and it will be active with next restart.

On-the-fly (and not sticky), SELinux can be toggled as well from Boeffla-Config overview tab.

Minor internal improvements

Enjoy

Andi