yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
I still have not analysed the changes in detail, however somehow Samsung seem to have made a lot of things right with this last code drop.

After my personal experiences and also user reports, this source drop seem to be game changer in terms of smoothness.

I still hope, Sammy will come out with Kitkat for the S3. But then this might be really the end...

Andi
[Galaxy S III Android Development] orangerot.:
[MENTION=947981]Lord Boeffla[/MENTION] I just wanna report that the lags are gone again with the latest Beta :)

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] andip71:
Good. Thanks for reporting. Seems like Samsung did a good job with the last source drop which I implemented...

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] ginzo:
No lags with beta 4 and cm11 45.1 by temasek :)

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] andrewwright:
My results with beta4 omni and biftor Rom v3. Only three hrs screen time but it's oc to 1600 and the phone was used as a daily phone so calls and Tex's and what's app was used in them three hrs. Great job on the kernel.
[Galaxy S III Android Development] Scarface1991:
[MENTION=947981]Lord Boeffla[/MENTION]

Latest Beta works really great. Smooth as a baby-butt :D

Is it normal that when you use the Boeffla Sound Engine EQ inside the Boeffla Config App, that when you play Music the Sound Engine only kicks in after a couple of seconds? Before that the music would play but without the EQ Settings enabled. It's really not a big deal. I'm just wondering if this is normal or not.

Using Temasek's V 45.1 with latest Boeffla Beta
[Galaxy S III Android Development] andip71:
Scarface, yes - this is normal and intended on CM kernels.

CM kernels otherwise where not stable in terms of EQ. Thats why my colleague Yank about half a year ago proposed to implement a short delay for the CM kernels.

On Samsung kernels, this delay is disabled as there are no issues.

Andi
[Galaxy S III Android Development] Crythar:
1 day standby and almost 6h screen on time with latest beta (2100mah). And the best thing: no lags. Awesome. Thank you!
[Galaxy S III Android Development] mad_ady:
[MENTION=947981]Lord Boeffla[/MENTION]: again, I'm trying to do unusual things with your kernel - this time I want to loop-mount an ext2 image. I was able to do it back on 4.1.2, but so far I have failed on 4.4.2. I tried to run the mount command through your busybox and through the rom's busybox, but I got the same results. Here's what I tried (two variants):

/sbin/busybox mknod /dev/loop5 b 7 5

/sbin/busybox losetup /dev/loop5 /mnt/cifs/Kits/teste/teste.img

/sbin/busybox mount -o rw -t ext2 /dev/loop5 /mnt/cifs/teste

mount: mounting /dev/loop5 on /mnt/cifs/teste failed: Operation not supported

and this:

/sbin/busybox mount -o rw,loop -t ext2 /mnt/cifs/Kits/teste/teste.img /mnt/cifs/teste

mount: mounting /mnt/cifs/Kits/teste/teste.img on /mnt/cifs/teste failed: Operation not supported

I'm not sure what opperation not supported means in my case or what I should try to start troubleshooting, but I wanted to ask - is loop mounting supported?
[Galaxy S III Android Development] SuperAce609:
I noticed that too. Thought it was a problem with something else.

Is it okay to use eargasm on boeffla and a different EQ on the music player? Does one overwrite the other or can they play simultaneously?
[Galaxy S III Android Development] Choristav:
[MENTION=947981]Lord Boeffla[/MENTION], the changelog link to the omni kernel is broken.
[Galaxy S III Android Development] Scarface1991:
I use my own EQ settings in the Boeffla Config App and I also use Viper4Android's EQ. They work together like a charm giving me awesome sound with my cheap 5$ Galaxy S4 Headset. So yes, you can use 2 EQs at the same time.
[Galaxy S III Android Development] n0stalgia:
Boeffla EQ uses the hardware EQ functionality of the Wolfson DAC of the SGS3. I think Viper4Android uses software EQing which is lower quality. It would be advisable to just use the Boeffla EQ.
[Galaxy S III Android Development] andip71:
The honest answer is: I do not (yet) know. Never tried to access a loop device on my S3 so far.

Maybe the busybox needs to be recompiled with loop device support, maybe not. I need to check this out.

Have you ever tried with another busybox, e.g. Stericson? Just for a cross-check.

And it seems I have to go on a business trip very soon, followed by a weekend going to Poland, so I will not be able to look into that before next week. Sorry.

Boeffla-Sound EQ activates the hardware equalizer provided (but not used by Samsung by default) of the WM8994/WM1811 audio hub. So it would not interfere with other sound mods that are based on software solutions.

The only thing that can happen: The effects multiply if you use both together, and the sound gets really bad in the end. But this is something that you can control.

Andi
[Galaxy S III Android Development] ssmcrak:
I am on temasek v45 using beoffla 2.2 beta 1 can anybody tell me which profiles should i use
[Galaxy S III Android Development] Crythar:
Why don't you first upgrade to latest beta4? Its really worth it
[Galaxy S III Android Development] andip71:
Where?

Just tried in web + in Boeffla-Config app. Both times working fine.

Andi
[Galaxy S III Android Development] alirezaafkar:
Again to England? :D
[Galaxy S III Android Development] andip71:
Yes, this time to London.

But I will move on to Poland on Friday with my wife until Sunday evening.

Busy times :)

Andi
[Galaxy S III Android Development] Yeti47:
Don't forget to bring your rain gear, can enjoy our floods :(
[Galaxy S III Android Development] cKenny:
Report:

Flash boeffla kernel version 2.2 beta 4 for cm11, then unable to switch on wifi. Same for beta 3. Then i didnt try beta 2 and go back to beta 1. After that wifi can be switch on.
[Galaxy S III Android Development] ayoubij:
Oups, so we have to wait for one whole week for another release :(
[Galaxy S III Android Development] andip71:
Question:

What rom do you use?

How did you flash? (always flash in recovery if you have issues, to make sure modules which are required for WIFI are copied)

Wifi works just fine with all betas...

Andi
[Galaxy S III Android Development] andip71:
Yes, indeed. But I think currently there is no urgent need for a new release at all :)

Oh dear, is it still that bad? I was reading somewhere, it should be better tommorrow?

Andi
[Galaxy S III Android Development] Yeti47:
It still quite bad in some areas along the Thames west of London, but central London should be fine. Been much drier since the weekend.
[Galaxy S III Android Development] mad_ady:
I checked with sterricson's busybox mount and I get the same message - operation not supported.

Have a nice trip!
[Galaxy S III Android Development] Choristav:
This, in the first post

"Change log for Omnirom: KLICK HERE"

leads to

http://boeffla.df-kunde.de/sgs3/boeffla-kernel-omni/cm11/changelog.htm

instead of

http://boeffla.df-kunde.de/sgs3/boeffla-kernel-omni/omni11/changelog.htm

Are you using crossbreeder?
[Galaxy S III Android Development] cKenny:
Hi,

At first, I'm using cm11-m2 rom and try to update boeffla kernel from 2.2 beta 1 to beta 4. After flashing everything looks good, only problem is cannot switch on wifi. Then i try beta 3 samething happen.

I wonder what happen and go read more on your change log, then find out that you have merge in some m3 things.

As such, I upgrade my android to cm11-m3. Flash beta 4 again still no luck. And so i just flash back to beta 1.

I flash both rom and kernel in cwm recovery only.

---------- Post added at 10:57 AM ---------- Previous post was at 10:56 AM ----------

Nope, i didn't
[Galaxy S III Android Development] andip71:
Ok, you are completely right. In the OP the link was broken, I corrected it meanwhile.

I am running out of ideas. I flash every milestone and nightly build of CM11 and never, with any of the kernel versions, had any issue enabling wifi.

Maybe you should redownload the kernel zips again, maybe something has broken the download. No clue.

Andi
[Galaxy S III Android Development] dan55:
thanks dev.. kernel installed with Neat rom and call sound seems much better... wifi working ok too :)
[Galaxy S III Android Development] cKenny:
haha, nvm, i'll try to download again later. anyway, this kernel still is one of my fav kernel :)
[Galaxy S III Android Development] andip71:
Naaaah, not without working wifi...

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] mad_ady:
Grrrr!

<rant>I am getting fed up with android's recursive-slave mountspace "improvement" which seems to block all my mounting attempts. On closer analysys I am able to mount Cifs, NFS and even LUKS images but I can only view them from the process that mounted the image/share. The loop-mounting I was complaining earlier probably works as well, but I was trying to mount it from a Cifs share and it might have been inaccessible at that point</rant>

Now, that I got that out of my system, I'd like to learn what my options are. I found a thread from where Lord Boeffla quoted before:http://xdaforums.com/showthread.php?t=2106480 which explains what's going on (even if some of the terms are above my mere mortal comprehension level).

For the record, I'm running the beta4 version of this kernel and Neatrom 2.8 (Based on Slimkat 2.8 - android 4.4.2).

I'd like to ask the following:

1. Does this kernel implement this namespace patch so that only things mounted under /storage are "protected"? I tried to mount my shares and files under /mnt (/mnt/cifs, /mnt/nfs). Also I tried to mount it under /storage/sdcard - same result). Also, selinux is set to permissive. I'm guessing the answer is yes, since it was done in your kernel for 4.3, but it doesn't hurt to ask.

2. Does the ROM have to do anything to support this setup? Or is the fix done in the kernel without the ROM's knowledge?

3. Is there a way to do it via adb, but without having the phone connected to the PC? E.g. connect to the adb daemon (which would not be affected) and just issue the mount command? Maybe adb over wifi works locally too...

Is anybody using apps like CifsManager successfully on this kernel and Slimkat ROMs?

Thanks for the help!
[Galaxy S III Android Development] Moopow:
I too am having little issues with wifi.... Wifi will work but when I am switching between wireless routers, the wifi will not connect to the device even though the passwords are save and stored on the device. What have to do to get the device to connect to the wifi is to reboot.... And it will connect automatically....

Any idea as to why this issue is taking place?
[Galaxy S III Android Development] mad_ady:
I just found out there is a workaround to the slave namespace issue done in the latest (1.93) supersu binary:

http://xdaforums.com/showpost.php?p=50447170&postcount=55

I'll need to try it out asap.
[Galaxy S III Android Development] dan55:
Hi guys.

I generally use 2 different Wi-Fi routers, in different locations. Phone seems to be connecting to both ok. I'm using omni stable with Neat rom
[Galaxy S III Android Development] boyheadkick:
Same here..home and work wifi is working, no hiccups..

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] mtxx1:
flashed this kernel.

after i set my prefered settings using the app, can i uninstall the app? will my setting stick after reboot?

i dont need the app because i dont change the settings anymore.
[Galaxy S III Android Development] andip71:
Yes, you can even uninstall the app.

The settings will be set by the kernel during startup, regardless if app is installed or not.

Just make sure you do not delete the folder /data/.boeffla, as there the kernel config is stored.

Hm, wrong information. The app does not set the settings, the kernel does.

The app just checks if the settings got applied and notify the user in the dropdown bar, nothing else.

So uninstalling the app is even safe.

Andi
[Galaxy S III Android Development] Nic2215:
Same here, temasek v46 wanna use your kernel. Flash using Cwm recovery cannot use wifi but can use mobile data. Mobile odin says phone model not recognised
[Galaxy S III Android Development] andip71:
Working fine with Temasek V46 and beta4 of my kernel.

Can you let me know what you can see in folder

/system/lib/modules

please?

Andi
[Galaxy S III Android Development] Nic2215:
Sorry for the late reply. I'm going to reflash it now

---------- Post added at 04:34 PM ---------- Previous post was at 04:20 PM ----------

@Andi

exfat_core.ko

exfat_fs.ko

frandom.ko

lockd.ko

nfs.ko

ntfs.ko

scsi_wait_scan.ko

sunrpc.ko

xpad.ko

all this only...guide me please, and thank you

---------- Post added at 04:37 PM ---------- Previous post was at 04:34 PM ----------

just to add on, i downloaded beta 3 /4 as well. both yield the same results :crying::crying:

i download via your homepage (omni rom/temasek/ and etc
[Galaxy S III Android Development] andip71:
Very interesting. Something seems to block the wifi modules from getting installed. There should be a module called "dhd" or so as well.

But why?

What recovery are you using?

Can you open the zip file you are flashing at a PC and check if the DHD module is also not contained there?

If you have Boeffla-Config Donation version, can you flash the kernel from there pls?

If you do not have, can you flash the kernel again via Boeffla-Config and using the Load&Flash function?

There MUST be a weird thing going on.

Andi
[Galaxy S III Android Development] andip71:
Hi,

I am currently on a business trip, so quite limited in time.

It seems the interesting part of your log is this:

<6>[34415.774562] c0 lcd panel: s6e8ax0_power_off

<6>[34415.922375] c0 lcd panel: -s6e8ax0_early_suspend

<6>[34415.935402] c0 s5p-dsim s5p-dsim.0: +s5p_dsim_early_suspend

<6>[34415.935448] c0 lcd_power_on : enable=0

<6>[34415.935943] c0 s5p-dsim s5p-dsim.0: -s5p_dsim_early_suspend

<6>[34415.935986] c0 s3cfb s3cfb.0: disable power domain

<1>[34415.936038] c0 Unable to handle kernel NULL pointer dereference at virtual address 00000000

<1>[34415.936094] c3 Unable to handle kernel NULL pointer dereference at virtual address 00000000

<1>[34415.936149] c3 pgd = c0004000

<1>[34415.936177] c3 [00000000] *pgd=00000000

<0>[34415.936210] c3 Internal error: Oops: 5 [#1] PREEMPT SMP

<4>[34415.936246] c3 Modules linked in: dhd

<4>[34415.936279] c3 CPU: 3 Tainted: G W (3.0.101-CM #1)

<4>[34415.936330] c3 PC is at __wake_up+0x30/0xa4

<4>[34415.936362] c3 LR is at 0x0

However, it does not give any clear indiation. Suspicion is a flaw in the display driver. Triggered by something...

But I am afraid we will not find out more based on this log.

Best is to monitor whether this is a reoccuring issue for you or not.

Sorry and thanks

Andi
[Galaxy S III Android Development] Nic2215:
[MENTION=220904]andi[/MENTION]

-i have checked theres DHD.ko + cifs.ko+btlock+ auth rpcgss in my pc, all these are not present in my phone lib/modules:confused:

after i flash the kernel, i can't even open the boeffla app to load and flash like i do in the 5.1 samsung, for this case it crashes :crying:

its mid night in my country but what i can do is, the rest i will have to try tomorrow
[Galaxy S III Android Development] andip71:
Nic, ok. No worries, let's call it a day and continue the next days (I am on a business trip as well, so have almost no time until next Monday).

We figured out the root cause of your WIFI problem meanwhile - it is missing files that are not copied over during kernel flash. So next to tackle is which recovery you are using and if this makes a difference.

Or whether you have any security app / framework etc. in place that removes the files again or prevents them from being written.

Also, app crashes...? What exactly do you press, when does it crash, and what is the message then? I would need a bc.log file from you directly after the crash.

All in all, there are all possible weird things going on at your side, which I do not have any explanation for so far.

But it is interesting as well :)

Andi
[Galaxy S III Android Development] Nic2215:
sorry andi, i think it's my fault not trolling....i factory wiped and reflash the cm11 v46 , boot to cwm and reflash the latest 2.2 boeffla kernel and it works? im not sure why this happent , before this i have factory reset,wipe cache partition. *Sorry for the confusion-its working now

*and i have the x privacy the message did mention something about xprivacy, i guess thank you!
[Galaxy S III Android Development] andip71:
Glad you could resolve it. Although very strange what happened.

I guess we will probably never get an explanation for it really.

Hopefully the last as well. But keep an eye on it pls.

Andi
[Galaxy S III Android Development] MD500:
Anyone have buugk1 Flashable zip modem? Im using movistar 850 band in venezuela

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] K00li79:
Your kinda in the wrong thread here....

Try downloading perkas file stash from play store, it contains alot of helpfull goodies. ^^

If i remember correctly it also contains modems.

Goodluck! ^^
[Galaxy S III Android Development] Yeti47:
Try this thread - http://xdaforums.com/showthread.php?p=50465609, and it does contain modems.
[Galaxy S III Android Development] SanketN8:
andi i have an issue

when installed both boeffla sound and boeffla confiq

if i turn on hw equalizer in boeffla sound the other settings such as flc tuning ,dac direct turns automatically off

and if i scroll up even the hw equalizer turns off :confused:
[Galaxy S III Android Development] boyheadkick:
You cant have both apps at the same time...uninstall boeffla sound, it's integrated in boeffla config app anyways

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] mad_ady:
Good news regaring mounting NFS (and CIFS) shares. I managed to make my shares world-readable with these commands:

#remount the root filesystem rw so that we can create the mountpoint
/sbin/busybox mount -o remount,rw /
#create the mountpoint
/sbin/busybox mkdir -p /mnt/nfs/Download
#make the mountpoint world readable so that all user apps can access it
/sbin/busybox chmod 777 /mnt/nfs
/sbin/busybox chmod 777 /mnt/nfs/Download
#remount / as ro
/sbin/busybox remount,ro /
#mount the actual NFS share (on 192.168.1.5:/DataVolume/Download)
#You need SuperSU v1.93 or later to work around the slave mount namespace issues.
su --mount-master -c "/sbin/busybox mount -o nolock,ro,hard,intr,vers=3 -t nfs 192.168.1.5:/DataVolume/Download /mnt/nfs/Download"
#check that it was mounted
mount | grep /mnt/nfs/Download

Similarly you can mount CIFS shares and they are accessible by any app. I tested with ES File Explorer, QuickPic and MxPlayer.

[MENTION=947981]Lord Boeffla[/MENTION], can you update your kernel documentation and add such an example to the CIFS/NFS module section? Even if most people don't bother reading the documentation it might help others in need and it would help these instructions not get lost in the deluge of posts. :)

I am working on a Tasker plugin to present a GUI and allow me to mount and unmount my shares. I will create a new thread for it and post the link here if people are interested in it.

Regarding my issues with mounting an ext2 image, I get the same error (operation not supported) with your busybox and the mount-master switch. It would seem it's not the same issue. Would it help if I ran a strace on the mount command?
[Galaxy S III Android Development] andip71:
Mad_ady, we can continue looking into this very special thing next week when I am back from my business trip, yes.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] mad_ady:
Thanks for the help - there is no rush. I was hoping it was related to the master namespace limitation.

Regarding the interface to mount NFS, a shameless plug if I may: http://xdaforums.com/showthread.php?p=50480146 :)
[Galaxy S III Android Development] Kiszonyogor95:
Im using this kernel again, this time with Carbon rom and Im gonna stay with it for the long time I think ;)

Lord, you're the Man! ;)

Great job!

TaPaTaLkEd from my Galaxy S3
[Galaxy S III Android Development] FlemishDroid:
You tried to flash kernel a second time? Because when I update cm11 nightly and flash kernel I sometimes can't switch wifi to on but after flashing it a second time it always works.

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Android Development] sirdragon:
temasek v46 + boeffla beta 4, best combination ever! It seems that the battery life is better than in the beta 3, thanks!

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] boyheadkick:
I updated my nightly yesterday and i didnt experience any wifi bugs

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] cKenny:
i'm facing wifi problem when flashing latest beta 4 kernel few days ago, after see your post, i try to flash the beta 4 kernel in recovery twice without reboot, and "da~da~", it works. wifi now working as per normal. thanks!
[Galaxy S III Android Development] boyheadkick:
Andi, i wanted to try out Slimkat's 4.4.2 stable today so i flashed it and booted with it's stock kernel..then when i flashed your CM kernel and rebooted, i was stuck at bootanimation...is your CM kernel incompatible with Slimkat, or do I need to use the Omni kernel?

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] victor_neves:
init.d is enabled by default?
[Galaxy S III Android Development] BrhoomHD:
the omni one ?

i9300 temas v45 & Boeffla
[Galaxy S III Android Development] zhuoxian:
Sorry to hear that.:(
[Galaxy S III Android Development] ithunter:
however wish your for good time ahead.
[Galaxy S III Android Development] Nic2215:
We will patiently wait for your return, all the best bro.
[Galaxy S III Android Development] dan55:
sorry to hear that LB :( good luck with sorting it all out
[Galaxy S III Android Development] scorpionhd2:
Good Luck Lord, Hope everything works out for you on the best side possible. I'm sure everyone will wait patiently for you to sort everything out and return. (May the thief get what he deserves!)
[Galaxy S III Android Development] caloyskii23:
Can this be used on AOS

---------- Post added at 08:17 PM ---------- Previous post was at 08:16 PM ----------

Can this be used on AOSP?
[Galaxy S III Android Development] rjames123:
Try Omni version kernel
[Galaxy S III Android Development] mad_ady:
Sorry to hear that Lord Boeffla - I hope you get your car back without having to go through all the red tape...

And a bit offtopic - if anybody wants to connect to network shares - forget about Samba. I did two download tests in the same conditions (same distance from the Access Point, same NAS, same file) on my 802.11g Wifi and I got almost double the speed with NFS compared to Samba:

root@android:/ # ls -l /mnt/cifs/Kits/250M
-rw--w---- 503 system 262144000 2014-02-20 20:55 250M
root@android:/ # time dd if=/mnt/cifs/Kits/250M of=/dev/null
512000+0 records in
512000+0 records out
262144000 bytes transferred in 200.061 secs (1310320 bytes/sec)
3m20.62s real 0m0.97s user 0m11.37s system
root@android:/ #
root@android:/ # time dd if=/mnt/nfs/Kits/250M of=/dev/null
512000+0 records in
512000+0 records out
262144000 bytes transferred in 119.271 secs (2197885 bytes/sec)
1m59.30s real 0m1.29s user 0m8.70s system
root@android:/ #
root@android:/ # mount | grep Kits
192.168.1.5:/DataVolume/Kits /mnt/nfs/Kits nfs ro,relatime,vers=3,rsize=16384,wsize=16384,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.5,mountvers=3,mountproto=tcp,local_lock=all,addr=192.168.1.5 0 0
//192.168.1.5/Kits /mnt/cifs/Kits cifs rw,relatime,sec=ntlm,unc=\\192.168.1.5\Kits,username=adrianp,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.5,unix,posixpaths,serverino,acl,rsize=16384,wsize=131007,actimeo=1 0 0

So, thanks Lord Boeffla for the NFS support!
[Galaxy S III Android Development] tisazalay:
Good luck [MENTION=947981]Lord Boeffla[/MENTION]

Take your time, everything is going to be fine.

Real life trolls are worst....