yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
While I understand you, doing this change would stop me from using KK roms myself.

I cannot stand this swap as it messes up all things for me and 99% of my users would also not understand why and what.

So, really sorry

Andi
[Galaxy S III Android Development] jun_ng_1208:
No worries my lord, I totally understand your point :) I shall just hold on further till some other solutions come out for KK ROMs in the future...
[Galaxy S III Android Development] lchiocca:
I'm using omnirom... the reboots are happening a couple of times a day... can't seem to be able to reproduce it. But _mostly_ it happens when the screen is off. e.g. This morning I happend to see the omnirom boot screen animation.... So I took yet again a copy of the last kernel messages.

After the last three kernel logs I can make out the following thing: each time a reboot as triggered, an "emergency remount R/O" was logged.

<6>[23575.571590] c0 SysRq : Emergency Remount R/O

<6>[23575.580818] c0 EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)

<6>[23575.585647] c0 EXT4-fs (mmcblk0p8): re-mounted. Opts: (null)

<6>[23575.587903] c0 EXT4-fs (mmcblk0p10): re-mounted. Opts: (null)

<6>[23575.631217] c0 EXT4-fs (mmcblk0p12): re-mounted. Opts: (null)

<4>[23575.704380] c0 Emergency Remount complete

<6>[23575.779721] c1 REBOOT Notifier for CPUFREQ

<6>[23575.780622] c0 REBOOT Notifier for BUSFREQ

<6>[23575.780792] c0 modem_if modem_if.1: shutdown +: platform_drv_shutdown+0x0/0x20

...etc...

So it was an "actual" reboot and not a kernel panic. Andy, like I mentioned, I'm not sure at all where the boundary between kernel and rom is, so if you tell me that I should rather file a omnirom issue rather than continue in this thread, I will.
[Galaxy S III Android Development] andip71:
The emergency remount was a consequence of something that happened before.

It would maybe help to check what was logged before this. It was for sure no kernel panic as this would look different.

What configuration are you using? Somehow I feel it could have been memory pressure? Do you use zRam, do you use Frandom?

It can be sooo much...

Thanks

Andi
[Galaxy S III Android Development] lchiocca:
I use both zram and frandom... but there commonality in the logs before that (one it's mali regulator_set_voltage, the other two times it was s5p-ehci: host_phy_susp:4). I'm currently doing a tail dump of the logcat... let's see if that brings up something.

Andi would it be possible to add a timing information for the android logger (a bit like for the kernel one)? If's that's not a kernel thing, then I'll definitely file a omni jira issue.
[Galaxy S III Android Development] scorpionhd2:
I have the GT-I9300 running Validus13 Rom V4.2 and when I flash this kernel, I cant get past the boot animation. Tried clearing everything. No change. Any ideas?

On Validus13 V4.1 with Boeffla 2.1, all was gravy.
[Galaxy S III Android Development] andip71:
I think the only fair solution before filing a bug with Omnirom team would be:

- run their stock kernel for a day and see if you have issues

- run boeffla kernel in stock configuration and see if you have issues

Only if you see issues with the stock kernel, you should potentially raise a bug request.

Which kernel variant have you flashed? CM11 or Omnirom?

Andi
[Galaxy S III Android Development] scorpionhd2:
CM11

However, I re-flashed the Validus13 V4.1 and then your 2.2 kernel and it boots fine. Would this classify as a ROM issue?
[Galaxy S III Android Development] andip71:
I would not go that far.

As I wrote before, the CM11 KK roms are under heavy development and we have to expect surprises really every single day.

I would ask the Validus team what they changed between 4.1 and 4.2 which could break custom kernels.

Maybe they require a newer ramdisk, a different one or what ever. Hard to say, unfortunately I cannot look at all roms floating around. Impossible, time-wise.

Andi
[Galaxy S III Android Development] scorpionhd2:
No prob Andi, I'll shoot them a message. Thanks!

EDIT------

Ok this is strange, I took a nandroid and flashed the OMNI test build variant. It works!

WOW.....Much Confusion....Very Working
[Galaxy S III Android Development] ZaneZam:
yeah that's right nothing "removed" yet regarding this andi but the opposite will be soon the case, there will be "something" in addition added in beta 9 to hopefully nuke this "problem" forever! at least for all concerned users then :) will see, testing is a bit difficult as we (obviously lucky ones *g*) never had and still haven't such problems (well for me at least not related to zzmoove "sleep settings"!) so i guess we will have to wait for user replies on next beta version of boeffla kernel then ;)
[Galaxy S III Android Development] sherlock5545:
I had music stuttering but increasing the minimum clock speed to 300Mhz actually solved the problem.

By the way, thanks for the latest beta. Smooth as always and great battery life. Best combination with CM-Temasek or Omni.

Sent from my GT-I9300
[Galaxy S III Android Development] Erik1805:
What are your ideas about battery saving with your kernel in combination with greenify? Does greenify make a difference or is your kernel with battery savings settings good enough?

Thanks

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[Galaxy S III Android Development] Moster2:
If you have an app that notoriously drains battery, the kernel wont help much. But if an app actually isnt doing anything in the background (it does not cause battery drain), greenifying it wont do anything anyways. So, you need to know if it helps you or not.
[Galaxy S III Android Development] MD500:
Which kernel version i need in Slimbean 4.3 estable build 2? And proban 4.3 ,which kernel version i do use?

Sorry for my english..

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] andip71:
Slimbean = cm10.2 Boeffla kernel.

Probam will likely not work at all. Read thread backwards to find why roms like probam, pacman etc are not supported by custom kernels anymore.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] SuperAce609:
I was using 300mhz by default but it didn't work. Switched governor to lulzactiveq and everything works great. Phone's a little zipper as well.
[Galaxy S III Android Development] ZaneZam:
then u might be a very good tester for the new soon upcoming zzmoove version! ;) I'm curious about if it fixes your problems. would be very nice if u could give it a try then.
[Galaxy S III Android Development] SuperAce609:
Yessss!!!!!! I'd love to! Let me know whatever i can do. Zzmove ftw :D

Andi, i have no idea what was wrong with me. I've been looking for awesome equalizers all over the net and Google play. And just now messing with the GPU settings i noticed there was an EQ setting in the sound tab. The Eargasm profile is definitely absolutely incredible.

Funny how what you're looking for is where you'd least expect. After using Boeffla kernel for so long I'd think i should've memorized everything in the app by now.

Just another reason to love boeffla. Thank you so much Andi.
[Galaxy S III Android Development] akz1x1:
Is this kernel flashable with twrp?
[Galaxy S III Android Development] andip71:
Yes it is.

Andi
[Galaxy S III Android Development] anybuddy:
Hi Andi, I just want to say Thanks for creating such a great Kernel and App. Also, I am very impressed with your friendliness and your constant willingness to help. Keep going that way.

Here is a small thing for you:

3MJ9282791754403K

--------------------------------------------------

Gesendet von meinem GT-I9305

ROM: | CarbonRom | Kernel: | Boeffla-Kernel |

If I've helped you, please press the Thanks Button!
[Galaxy S III Android Development] tsch:
I just want to thank you. This kernel is totally awsome. My phone is twice as snappy as with stock CM11. Incredible!

(And I still can fine tune all The settings...)

Thanks to The (Over)Lord Boeffla!
[Galaxy S III Android Development] wongsyrone:
Andi,

Can you add support for F2FS? Im looking forward to that.
[Galaxy S III Android Development] Crythar:
Answered in post #2262 and the following comments
[Galaxy S III Android Development] andip71:
My tendency after following the threads here and there is unchanged so far.

Not short-term. Too many issues (which are normal in a very early stage) and as many backporting needs to be done from higher Linux kernel versions, maybe never.

Too early to say.

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

Slightly OT. Hope you won't mind too much.

I just installed you latest Omni test build into my GT-I9300 and all is good so far.

Any chance of a N8010/13 compatible version?

-
[Galaxy S III Android Development] abogrhen:
Hi lord boeffla

I want to ask you if you have plan to support apt-x codec

For Bluetooth as the stock rom

Have it but the aosp don't
[Galaxy S III Android Development] andip71:
For n801x (and n8000) I only provide Samsung based kernels, no CM.

I am out of available time meanwhile, cannot support and work on more.

Hm, what is your exact use case for it?

Are you using this to stream audio to your automotive audio device, or what exactly do you need it for?

I never looked into it as I barely use Bluetooth at all. But open to hear what you would need it for...

Thanks

Andi
[Galaxy S III Android Development] abogrhen:
Thanks for fast reply

Will I use is it for Bluetooth headphones

That have apt-x on them

The sound quality is amazing for Bluetooth

But without it the sound is so terrible

And I use it in my car too, but not too much

I mess the codec so much that I thought about going

Back to samsung rom

---------- Post added at 11:01 AM ---------- Previous post was at 10:50 AM ----------

In here they have it working on omni with little problems

But not on cm

http://xdaforums.com/showthread.php?t=2557407
[Galaxy S III Android Development] andip71:
I had a very brief look... Samsung does not implement apt-x in the kernel but as a shared library in the rom.

So, I will not be able to do anything here as apt-x is proprietory, closed code.

Sorry

Andi
[Galaxy S III Android Development] abogrhen:
Oh, thanks i was hoping for it
[Galaxy S III Android Development] andip71:
Understand, but Samsung put the codec into the shared lib

libbt-codec_aptx.so

and this is not part of the kernel. As said, there is no source code available for it to my best knowledge, so this is where we currently end...

Better to ask CM or Omnirom developers if they see any chance of including this shared lib in their roms.

Andi
[Galaxy S III Android Development] abogrhen:
I will try and ask them
[Galaxy S III Android Development] wadken1:
Perfectly understandable. Sad though as the N80XX platform is in great need. Wish I could do something myself but even if I had the capability, like you, I wouldn't have the time.

Many Thanks for your great work on the S3

Cheers
[Galaxy S III Android Development] karwankar:
Does this kernel support call recording?
[Galaxy S III Android Development] Volpe92:
Hello I am with Cm11 and kernel Boeffla Omni ... and I would like to know how to hear the highest volume ...

With rom samsung, no problem the audio is strong ...

With CM11 is low ...

I would like to know how best to approach the kernel to feel better without distorting

thx :good:
[Galaxy S III Android Development] karwankar:
Use Boeffla config V2 set volume
[Galaxy S III Android Development] Volpe92:
Hahahaha yes I knew this, but I can not get to levels of Rom Samsung ...

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] Gassity:
Hello guys, I cannot charge my phone DURING THE NIGHT! I think it's related to kernel, maybe I should tune some settings in boeffla config? Can you help me with it?
[Galaxy S III Android Development] jun_ng_1208:
Particularly during the night only?? Have you tried enabling the 'Ignore Safety Margin' option in Boeffla App?
[Galaxy S III Android Development] Gassity:
I charge it during the night only, cause it works all day long. I'll try it, thanks
[Galaxy S III Android Development] SuperAce609:
Do you mean the plug has issues and since you use a different one during the day it charges fine?
[Galaxy S III Android Development] Gassity:
No, the plug is one and only and it works great, its something related to software, I think its the kernel settings.
[Galaxy S III Android Development] 2rgman:
[MENTION=947981]Lord Boeffla[/MENTION]

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!!!
[Galaxy S III Android Development] BrhoomHD:
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
[Galaxy S III Android Development] gitlygit:
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?
[Galaxy S III Android Development] sirdragon:
Same here

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] just4u32:
Hey [MENTION=947981]Lord Boeffla[/MENTION],

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://xdaforums.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
[Galaxy S III Android Development] andip71:
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.

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

What rom are you using?

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

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
[Galaxy S III Android Development] Yank555:
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.
[Galaxy S III Android Development] 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
[Galaxy S III Android Development] cheese458:
Installed safely!
[Galaxy S III Android Development] 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 [MENTION=2876905]f0xy[/MENTION] 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
[Galaxy S III Android Development] f0xy:
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 ?
[Galaxy S III Android Development] oae08:
great beta as always
[Galaxy S III Android Development] andip71:
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
[Galaxy S III Android Development] limitedMUSCL:
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
[Galaxy S III Android Development] 2rgman:
Thanks!

Do I need to set it on every boot (with init.d or something)? or this settings are saved?
[Galaxy S III Android Development] 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
[Galaxy S III Android Development] andip71:
:confused: 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
[Galaxy S III Android Development] 2rgman:
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 ----------

Ooops...

didn't see that, sorry...

Thanks again!
[Galaxy S III Android Development] f0xy:
This is the more in depth answer I was looking for you :)
[Galaxy S III Android Development] limitedMUSCL:
Exactly! Straight from the kernel chef! :D

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] 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.
[Galaxy S III Android Development] 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
[Galaxy S III Android Development] mad_ady:
[MENTION=947981]Lord Boeffla[/MENTION]: 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
[Galaxy S III Android Development] se7e:
I've been meaning to ask this. What governor between pegasusq vs pegasusplus would you prefer if you'd want a good balance between performance and battery? While I do want to conserve battery, I'd also prefer a smooth browsing/gaming experience.
[Galaxy S III Android Development] gian90marco:
Which is the best governor for a daily use? I need a good battery life and good performances at the same time.. I'm on pure Cm11 m3.
[Galaxy S III Android Development] lchiocca:
You might want to ask in this thread http://xdaforums.com/showthread.php?t=2621308

All the other users are sharing their experiences and config there.
[Galaxy S III Android Development] andip71:
As a quick feedback, just based on personal experience:

zzmoove - battery yank

or

pegasusq - boeffla moderate

I personally never use pegasusqplus, it was implemented based on user request. But I even consider to remove this again mid-term as I do not see the big benefits compared to pegasusq itself since implemented.

Andi
[Galaxy S III Android Development] andip71:
Maybe it is just the simplicity for the things I use, nothing sophisticated.

To switch UMS mode on:

umount -l /mnt/extSdCard/

setprop persist.sys.usb.config mass_storage,adb

echo /dev/block/vold/179:17 > /sys/devices/platform/s3c-usbgadget/gadget/lun0/file
​

To switch it off again:

echo "" > /sys/devices/platform/s3c-usbgadget/gadget/lun0/file/system/bin/vold

setprop persist.sys.usb.config mtp,adb
​

Thats all.

Andi