[EOL] [KERNEL] [I9300] [Lineage14/CM13,12,11,10/Omnirom] Boeffla-Kernel (28-03-2018)

[sirdragon]

simple issue : skipping frames in youtube & facebook videos & imdb videos..... etc is it kernel issue or the rom issue is thier any fix ?

i9300 temas v41 & Boeffla

Same here

Inviato dal mio GT-I9300 utilizzando Tapatalk

 

[just4u32]

Hey @Lord Boeffla,
First, I'd like to thank you for your kernel and sound modifications (which I've been using for a long time).

I'm having some issues with all CM11 version roms (Temasek's, Probam, clean Omni and some more). I'm getting very bad battery life with either temasek's kernel or your omnirom kernel.
I have no idea what's wrong. I've UC to 1200, and UV both CPU and GPU quite heavily. Running zzmove (on various battery saving settings). I have also greenified all apps that were running in the background beside BBS and Whatsapp.
FastDormancy is off as well.

I am losing a lot of battery with very little screen on time.

I'll be also posting this on Temasek's thread as he might have different thoughts. You can watch it here (on page 5568) http://forum.xda-developers.com/showpost.php?p=50188341&postcount=56674

Here are two BBS dumps of a full (or nearly full) cycle. Hope you can help with what's wrong as I want to maximize my battery life for a trip I'm going to very soon. Thanks!!!

http://www.pasteall.org/49378 or on dropbox https://www.dropbox.com/s/ohk2ekcfrw6ylr2/BetterBatteryStats-2014-02-08_092357786.txt
http://www.pasteall.org/49379 or on dropbox https://www.dropbox.com/s/qg9aovgiqlyi18z/BetterBatteryStats-2014-02-09_224627414.txt

 

[andip71]

@Lord Boeffla
Hi Andi,
Is there any option to disable dynamic fsync on this kernel?
I'm asking since afaik there is a risk of curreption on a hot reboot if dynamic fsync is enabled (I actually faced this problem in the past on another kernel)

Thanks!!!

Not in the app. You would need to use an init.d script doing the following:

echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active

I never heard of issues from users so far, that is why it is not configurable in the app and switched on by default.

simple issue : skipping frames in youtube & facebook videos & imdb videos..... etc is it kernel issue or the rom issue is thier any fix ?

i9300 temas v41 & Boeffla

I do not know. How is it going with kernel that comes with Temasek?

I am using them as Cm build. I have tried using version 2.2.1 and have a stutter when using this kernel. (like a freeze frame type effect) I refreshed the rom and all was fine, went back to 2.1.10 and still stutters, again refreshed rom and all fine.
Anyone else had this issue? What can be causing it?

Sent from my GT-I9300 using xda premium

What rom are you using?
I recommend for almost all roms to use the Omnirom kernel, unless you are on pure Cyanogenmod 11.

Hey @Lord Boeffla,
First, I'd like to thank you for your kernel and sound modifications (which I've been using for a long time).

I'm having some issues with all CM11 version roms (Temasek's, Probam, clean Omni and some more). I'm getting very bad battery life with either temasek's kernel or your omnirom kernel.
I have no idea what's wrong. I've UC to 1200, and UV both CPU and GPU quite heavily. Running zzmove (on various battery saving settings). I have also greenified all apps that were running in the background beside BBS and Whatsapp.
FastDormancy is off as well.

I am losing a lot of battery with very little screen on time.

I'll be also posting this on Temasek's thread as he might have different thoughts. You can watch it here (on page 5568) http://forum.xda-developers.com/showpost.php?p=50188341&postcount=56674

Here are two BBS dumps of a full (or nearly full) cycle. Hope you can help with what's wrong as I want to maximize my battery life for a trip I'm going to very soon. Thanks!!!

http://www.pasteall.org/49378 or on dropbox https://www.dropbox.com/s/ohk2ekcfrw6ylr2/BetterBatteryStats-2014-02-08_092357786.txt
http://www.pasteall.org/49379 or on dropbox https://www.dropbox.com/s/qg9aovgiqlyi18z/BetterBatteryStats-2014-02-09_224627414.txt

You are having all sort of issues I can see.

First, your ProximitySensor was active for 40 minutes. I read something about it on other threads for Temasek rom, but I did never pay attention a lot.

Then you are having wakelocks caused by the modem. This can be an improper modem for your provider, or a RIL mismatch, oder just bad signal etc.
Threads are full on that issue everywhere and what all to try (switch off fast dormancy etc.)

Hope that helps.

Andi

 

[Yank555]

if dynamic fsync is enabled (I actually faced this problem in the past on another kernel)

This is not quite true...

A hotreboot is just a Dalvik VM restart, so OS (Linux, kernel) is not involved and not restarting, so no risk from dyn. fsync.

Also if the kernel panics, still should be fine, fsync will catch it and flush the outstanding write operations before the kernel reboots the device.

Only things that would be a bad idea is a plain battery pull while screen is on or a very hard kernel crash still while screen is on, which really happens extremely seldomly, really.

Also a regular Nandroid is never a bad idea, whatever dyn.fsync is set to.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu AOSP v0.91-beta2 kernel.

 

[andip71]

2.2-beta2

Hi all,

time for a new beta (both Omnirom and CM11 versions):

2.2-beta2

Change log

• zzmoove updated to version 0.8-beta10 (credits to ZaneZam) + Profiles reworked
• Compiled with Google gcc 4.8 (instead of gcc 4.7)
• su updated to version 1.93 (credits to Chainfire)
• Fixed permissions in Boeffla-Config app fixing app permissions in /system/app and /data/app now
• Omnirom version: Initramfs updated to version of 09.02.14
• CM11 version: Initramfs updated to version of snapshot M3 from 10.02.14

Enjoy
Andi

 

[cheese458]

Hi all,

time for a new beta (both Omnirom and CM11 versions):

2.2-beta2

Change log

• zzmoove updated to version 0.8-beta10 (credits to ZaneZam) + Profiles reworked
• Compiled with Google gcc 4.8 (instead of gcc 4.7)
• su updated to version 1.93 (credits to Chainfire)
• Fixed permissions in Boeffla-Config app fixing app permissions in /system/app and /data/app now
• Omnirom version: Initramfs updated to version of 09.02.14
• CM11 version: Initramfs updated to version of snapshot M3 from 10.02.14

Enjoy
Andi

Installed safely!

Sent from my GT-I9300 using xda app-developers app

 

[limitedMUSCL]

Hi, I'm running cm11 latest nightly, and would like to enhance sound.

I've seen that omnirom original kernel has the sound engine available. Does CM have the same? I couldn't find it clearly here, so I'm guessing it does not, but I would like to confirm this really.

And, how does one set the sound parameters in omni? Using the kernel config v2 too? I didn't quite get it in the post from @f0xy here...

And I may be veeery incompetent with the search in this forum but does the kernel need to be reflashed at every new nightly update?

Thanks

Inviato dal mio GT-I9300 utilizzando Tapatalk

 

[f0xy]

Hi, I'm running cm11 latest nightly, and would like to enhance sound.

I've seen that omnirom original kernel has the sound engine available. Does CM have the same? I couldn't find it clearly here, so I'm guessing it does not, but I would like to confirm this really.

And, how does one set the sound parameters in omni? Using the kernel config v2 too? I didn't quite get it in the post from @f0xy here...

And I may be veeery incompetent with the search in this forum but does the kernel need to be reflashed at every new nightly update?

Thanks

Inviato dal mio GT-I9300 utilizzando Tapatalk

If your using the omni kernel, I haven't tried the boeffla v2 app to adjust just the sound so I can't comment

I used the boeffla sound app which was enough to enable the engine but could not make use of all the features as the app may need updating, bear in mind that the sound app isn't made by Andi.

Someone may be able to give you a more clear concise answer here and also may correct anything I have said if it's incorrect

The easiest method would be to use boeffla kernel with the v2 app as it is perfect ?

Sent from my GT-I9300 using Tapatalk

 

[oae08]

great beta as always

 

[andip71]

Hi, I'm running cm11 latest nightly, and would like to enhance sound.

I've seen that omnirom original kernel has the sound engine available. Does CM have the same? I couldn't find it clearly here, so I'm guessing it does not, but I would like to confirm this really.

And, how does one set the sound parameters in omni? Using the kernel config v2 too? I didn't quite get it in the post from @f0xy here...

And I may be veeery incompetent with the search in this forum but does the kernel need to be reflashed at every new nightly update?

Thanks

Inviato dal mio GT-I9300 utilizzando Tapatalk

Very simple - all my kernels for S3 (Samsung, Omnirom, CM11) and n80xx (Samsung) have the same sound engine on board - Boeffla-Sound 1.6.5.

I recommend clearly to install the free Boeffla-Config V2 app as this will give you access to all configuration options of the kernel, of course also sound.

After you flashed an Omnirom update, you need to reflash the kernel, yes.
If you flash Omnirom in CWM, you can directly flash the kernel afterwards before you reboot again.
This is due to the fact, Omnirom replaces the installed kernel always by it's own one.

Andi

 

[limitedMUSCL]

Very simple - all my kernels for S3 (Samsung, Omnirom, CM11) and n80xx (Samsung) have the same sound engine on board - Boeffla-Sound 1.6.5.

I recommend clearly to install the free Boeffla-Config V2 app as this will give you access to all configuration options of the kernel, of course also sound.

After you flashed an Omnirom update, you need to reflash the kernel, yes.
If you flash Omnirom in CWM, you can directly flash the kernel afterwards before you reboot again.
This is due to the fact, Omnirom replaces the installed kernel always by it's own one.

Andi

Wow, answer directly from the master! honoured!

I'm using CM here, but I guess it'll be the same, I'll need to reflash kernel at every nightly update, right? Omni has automatic flash after, I guess CM does not...

And from the answers I can also assume that the CM *own* kernel does not include your sound engine (like omni does), right?

Just for curiosity, I didn't get it: The sound engine in the omni *own* kernel (not boeffla kernel) requires v2 config app too?

Thanks

Inviato dal mio GT-I9300 utilizzando Tapatalk

 

[2rgman]

Not in the app. You would need to use an init.d script doing the following:

echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active

I never heard of issues from users so far, that is why it is not configurable in the app and switched on by default.

Thanks!
Do I need to set it on every boot (with init.d or something)? or this settings are saved?

 

[andip71]

Hi!

Yes, same for CM. Also after a CM update, the kernel needs to be flashed again.

The CM own kernel does not have a hardware sound engine included. Omnirom developers however have cherry picked my sound engine, yes.

If you want to use the kernel that comes with Omnirom, you cannot use Boeffla-Config as this requires a full-blown Boeffla Kernel to be installed.
For this, I guess, you would need to fall-back to the 3rd party app "Boeffla Sound" by Simone. But expect some limitations as the app was not updated for more than half a year.

Andi

 

[andip71]

Thanks!
Do I need to set it on every boot (with init.d or something)? or this settings are saved?

Well, I wrote:

Not in the app. You would need to use an init.d script doing the following​

So, yes, this needs to be set during every restart in init.d

Andi

 

[2rgman]

This is not quite true...

A hotreboot is just a Dalvik VM restart, so OS (Linux, kernel) is not involved and not restarting, so no risk from dyn. fsync.

Also if the kernel panics, still should be fine, fsync will catch it and flush the outstanding write operations before the kernel reboots the device.

Only things that would be a bad idea is a plain battery pull while screen is on or a very hard kernel crash still while screen is on, which really happens extremely seldomly, really.

Also a regular Nandroid is never a bad idea, whatever dyn.fsync is set to.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu AOSP v0.91-beta2 kernel.

Sorry, I guess I used the wrong term, I mean when the phone stuck and I need to click 10 seconds on the power button the device will reboot. (I guess it's the same as battery pull). Anyway, thanks for the clarification!

---------- Post added at 06:21 PM ---------- Previous post was at 06:17 PM ----------

Well, I wrote:

Not in the app. You would need to use an init.d script doing the following​

So, yes, this needs to be set during every restart in init.d

Andi

Ooops...

didn't see that, sorry...
Thanks again!

 

[f0xy]

Hi!

Yes, same for CM. Also after a CM update, the kernel needs to be flashed again.

The CM own kernel does not have a hardware sound engine included. Omnirom developers however have cherry picked my sound engine, yes.

If you want to use the kernel that comes with Omnirom, you cannot use Boeffla-Config as this requires a full-blown Boeffla Kernel to be installed.
For this, I guess, you would need to fall-back to the 3rd party app "Boeffla Sound" by Simone. But expect some limitations as the app was not updated for more than half a year.

Andi

This is the more in depth answer I was looking for you

 

[limitedMUSCL]

This is the more in depth answer I was looking for you

Exactly! Straight from the kernel chef!

Inviato dal mio GT-I9300 utilizzando Tapatalk

 

[gitlygit]

What rom are you using?
I recommend for almost all roms to use the Omnirom kernel, unless you are on pure Cyanogenmod 11.


I am using Tamaseks unofficial CM 11, both build 42 & 43 suffered the stuttering.



Sent from my GT-I9300 using xda premium

 

[andip71]

And what with the kernel that comes with Temasek rom?

Have you tried exactly same settings?

Many times one compares apples with pies.


Sent via Tapatalk2 from my Galaxy S3 IPhone killer

 

[mad_ady]

@Lord Boeffla: I wonder if you could explain it to me how the USB mass storage mode works internally in your kernel/app .
I know that for S3 one needs usb gadget support (activated by echoing the device path to /sys/devices/platform/s3c-usbgadget/gadget/lun0/file for instance), but the problem I experienced with it was with unmounting the sd card before switching to UMS mode. I use a tasker script and I used to do it through the umount command ( checking that there aren't open files with lsof), and it works, but just the first time. After remounting the sd card (and running vold) I am unable to unmount it cleanly with the umount command. Also, any apks that use the .android_secure mount point stop working until I reboot.

I'd like to know what you are doing differently (because using the UMS checkbox in your app works fine all the time) and how you are managing the sd card being remounted (I might learn a thing or two).

I'm asking mostly out of curiosity - I'll probably retire my tasker scripts anyway...

Thanks