yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] mad_ady:
Hmm, you're using lazy umount - I'll have to try it out. The rest of the steps are the same as mine. Do you do specific checks to see which is the correct device or to see if the card was unmounted?

Also, are the commands triggered when the checkbox is triggered, or when the usb cable is inserted or removed?

I will do more testing and report back
[Galaxy S III Android Development] andip71:
mad_ady: The commands are triggered once the checkbox status is changed, yes. Very dumb solution, but seems to work most of the time.

I am not doing specific checks on the device, as I know the vold numbering of my kernels, so I can also go easy here.

Andi
[Galaxy S III Android Development] Math_Apolo:
Sorry this noobish question but

I'm using CM11 Temasek ROM which kernel should be better for me?

03 - boeffla-kernel-2.2-beta2-Omnirom-i9300.CWM

03 - boeffla-kernel-2.2-beta2-CM11.0-i9300.CWM

and if is possible what difference between they?

Thanks
[Galaxy S III Android Development] ekie84:
For temasek only use the omnirom

Send from my GT-I9300 using Tapatalk 2 (AOSP NeatROM v2.6.1 / 3.0.101 Boeffla-OmniRom v2.2-beta2)
[Galaxy S III Android Development] marenp:
For NeatROM should install Omni kernel, am i right? Thanks in advance
[Galaxy S III Android Development] ekie84:
Yes,omnirom,temasek,neatrom(slimkat) should use omnirom kernel

Send from my GT-I9300 using Tapatalk 2 (AOSP NeatROM v2.6.1 / 3.0.101 Boeffla-OmniRom v2.2-beta2)
[Galaxy S III Android Development] karwankar:
Does this kernel supports call recording
[Galaxy S III Android Development] tisazalay:
Hmmm, it depends, let me explain:

The kernel itself doesn't support call recording but if you use a rom like temasek's (right now I'm on v45, with andi's omnirom 2.2b2 kernel) you can use app's like skvalex call recorder with alsa mixer and recording works, so I think yes, the kernel allows call recording by working with the right apps.

Maybe other apps work but it's not straightforward as with the above mentioned.
[Galaxy S III Android Development] gitlygit:
Resolved this. I did a clean install of Temaseks CM 11 V45 and 2.2.2 of the kernal and everything is fine. Sorry for the bother.
[Galaxy S III Android Development] andip71:
No, and it never will as this is illegal in some countries.

I will never put anything illegal in the kernel.

But as you have been told by other users, there are apps and roms providing this functionality.

Andi
[Galaxy S III Android Development] mad_ady:
[MENTION=947981]Lord Boeffla[/MENTION] (and others): I have played a bit with the UMS check box and indeed, it works everytime without reboot, but one (worrying) thing I found was that when the card was mounted on the PC it remained mounted (visible under mount) and completely accessible under the phone as well. This suggests that the lazy umount was too lazy and didn't cut off access.

I also copied a file from the PC to the phone and on unticking the checkbox the file was visible on the phone. Also apps that had files under .android_secure contined to work as well.

My concern is that without umounting the card we can do data corruption by writing to the FAT tables from two "directions". Has anyone experienced problems/corruption with this UMS method?
[Galaxy S III Android Development] szunyi77:
So why Samsung into the kernel? Samsung rom does the voice recorder. It is not illegal? Samsung's free?

Sorry for my bad english..
[Galaxy S III Android Development] andip71:
I do not use it often, but never had any issues with it.

And also not got any reports about it.

I do not know what Samsung does in all countries.

However, in Germany for instance it is illegal and it is not in German firmwares at all.

Andi
[Galaxy S III Android Development] andip71:
2.2-beta3

Hi all,

small maintenance update (both Omnirom and CM11 versions):

Version 2.2-beta3

Boeffla sound engine 1.6.6: Allow full range volumes for speaker and headphone amplifiers

Optimized some compiler and linker flags (more smoothness?)

Enjoy

Andi
[Galaxy S III Android Development] szunyi77:
Ah so I understand. Hungarian firmware allow the call recorder .. Thank you

Sorry for my bad english..
[Galaxy S III Android Development] andrewwright:
Just updated kernel running biftor ROM 4.4.2 and running well.
[Galaxy S III Android Development] Erik1805:
probably posted before, but when someone calls me the ringtone goes on but the screen stays black for a while. At least 5 sec.

Anyone have this? Using lastest beta Boeflla and temasek
[Galaxy S III Android Development] andip71:
Is it different with the "stock" kernel that comes with Temasek's rom?

Andi
[Galaxy S III Android Development] Erik1805:
I will test it and let you know.
[Galaxy S III Android Development] 8afri:
Boeffla-Omnirom is my favorite kernel. Works fine and never failed me.
[Galaxy S III Android Development] Erik1805:
Just gave it a test and it is the same. It is not kernel related i guess
[Galaxy S III Android Development] andip71:
Thanks, Erik. And yes, I knew this is not kernel related.

But instead of saying that and hoping you would believe, I find it better you see yourself :) This makes you not only believe but KNOW it.

Andi
[Galaxy S III Android Development] mad_ady:
[MENTION=254166]Lord[/MENTION] Boelffa: are there known success stories with nfs and your kernel? I'm currently looking for a busybox build that has nfs mount support? (it looks like sterricsson's busybox doesn't have it) - any reccomandations?

root@android:/data/data/stericson.busybox/files/bb # strings busybox | grep -i nfs
Stale NFS file handle
root@android:/data/data/stericson.busybox/files/bb #
[Galaxy S III Android Development] andip71:
mad_ady: Yes, I have my personal success story with NFS :)

And I deliver everything you need with the kernel, of course.

So, why not just using the busybox I deliver with the kernel? It can mount a nfs share without any issues.

Here an example:

/sbin/busybox mount -o nolock,ro,hard,intr,vers=3 -t nfs 192.168.1.1:/home/mad_ady /mnt/nfs​

Of course create a folder /mnt/nfs first.

192.168.1.1 is the IP of the NFS server, home/mad_ady the share.

And do not forget to load the nfs module in Boeffla-Config V2 first.

Works fine, just tried it 5 minutes ago :)

Andi
[Galaxy S III Android Development] mad_ady:
Pff, thanks! I forgot you had your own busybox... I'll give it a try asap!

---------- Post added at 06:51 PM ---------- Previous post was at 06:02 PM ----------

Update - with your help (and your busybox) I was able to mount my nfs shares - I am in your debt once more :)

You are making it harder for me to have the motivation to start a development environment, but I will find something you haven't implemented yet!

In NFS related info I still have some questions:

1. How do you create your mount points? By a custom init.d script or via some tool like cifsmanager?

2. Do you use some sort of uid mapping to make the remote files accessible to all your apps, or do you just set the permissions so that the files are world readable? I honestly haven't found an elegant solution for this problem, except if you have the same uid on all systems.

Thanks again!
[Galaxy S III Android Development] andip71:
Honest answer:

I am not using NFS myself at all. I just put it in to enable it for others.

But if so, I would probably create an init.d script (which must be a bit tricky as it needs to either load nfs modules first or wait until they are loaded, but the script then needs to work in the background, JustArchi posted a nice way of doing this a while ago in the Boeffla Samsung kernel thread).

2. As I said, I am not using it. But you might want to try to mount it not on /mnt/nfs but another mount point that are seen by the apps.

I think, to use this really in a productive way, some more thoughts are required :)

Andi
[Galaxy S III Android Development] ayoubij:
So its ROM related? did anyone test this on stock Omni or CM roms?

I also have same problem on temasek rom and boeffla kernel. :(
[Galaxy S III Android Development] andrewwright:
If it helps I'm on biftor rom 4.4.2 with latest omni boeffla kernel and have no problems with this issue.
[Galaxy S III Android Development] josipborac:
Just got new 2100mAh battery. First cycle. Almost forgot how awesome this kernel is
[Galaxy S III Android Development] vinella:
I want to try and debug intermittent phone freezes Ive been getting with temasek v45 and boeffla 2.2 beta 3

ive enabled Android logger using the v2 config app but cant seem to find info on how to use the logs etc ... are there any links for this ?

or should i be using something different to generate logs and debug ?
[Galaxy S III Android Development] Visse0704:
Hello.

Can someone tell me please, what it is with the option "Init.d Script handling" !?

I use ProBAM rom v 1.2.9

Is it normally better to run init.d from the ROM or via the kernel!?

And what exactly can be worth or better by Deleting/wipe the existing init.d !?
[Galaxy S III Android Development] Erik1805:
Also installed Biftor with latest Boeflla. To bad, same problem :crying:
[Galaxy S III Android Development] andip71:
Android Logger will not help you to find phone freezes, quite certainly.

The Android Logger data can be read via adb connection, there are no single files somewhere which you can look into.

You should look at the output of the dmesg command, and also check cat /proc/last_kmsg as these are the kernel logs. Maybe you find something useful there.

Apart from that: First try is to always reset your configuration to standard settings in the settings menu of boeffla-config. And let this run for 1-2 days, seeing if you still have freezes.

Freezes can come from kernel, but also from rom (even more likely as roms are more complex in itself) or many other factors.

Last to say: I am running beta3 on Temasek 45 as well without any freezes so far.

Andi
[Galaxy S III Android Development] andip71:
This option decides whether the kernel should execute the scripts in init.d or not.

Most, I think even all, current CM roms execute init.d on their own, so I would suggest to leave that off.

Just if you come across a rom once that has no init.d support itself built in, you can still enable here and the kernel will take care.

I recomend to wipe most of the init.d files from this directory as many roms are carrying tweaks in the files that conflict with Boeffla kernels internal tweaks.

But you should know what you do when you wipe your init.d.

Boeffla-Config can wipe it for you, and even it creates a backup of the files so you can place them manually back if you want.

What is it again? Delay when getting phone call or so?

Well, seems to be something in the current CM base codes, no clue as I am not a rom developer.

Andi
[Galaxy S III Android Development] andrewwright:
Are you on beta3 and done a full format of system/data? That's all I did and no lag here.
[Galaxy S III Android Development] HorstiG:
OT sorry,

Only one set, Made in Germany, Porsche, Mercedes, Audi and Boeffla :good:
[Galaxy S III Android Development] JustArchi:
Simply awesome.

Masterpiece, Andi :good:

I'm also going to use it as my daily driver so I'll make sure any issues attached to my rom will magically disappear. I promise, if there are any... ;)
[Galaxy S III Android Development] PacketJ:
Hey guys just want to ask what's the new boeffla config app feature (multicore powersave) does? Thanks.
[Galaxy S III Android Development] andip71:
You can look this up in the documentation in detail.

App - help is one way, link in tge OP second way, or go on homepage ;)

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] zuluman:
I have nmap host scanning problem. Didnt have this problem with sam rom and boeffla kernel. This issue appers kernel or rom side ?
[Galaxy S III Android Development] Ubimo:
I'm using ArchiDroid and this kernel. Best ROM ever!

I was using Omegas ROM for a looong time but this combination is the best so far for me.
[Galaxy S III Android Development] andip71:
Hm, very good question. Never tried that.

Maybe make sure, you enable Android logger in Config-App again. It COULD make a difference.

Then you will probably like the latest info, Archi and myself are in close contact now to fine tune our combination further :)

Andi
[Galaxy S III Android Development] n. tympanicus:
Stuck at max cpu frequency?
[Galaxy S III Android Development] Kyle07:
I get this occasionally. Switching governors seems to do the trick.
[Galaxy S III Android Development] amppen:
+1

I was stuck at max freq with pegasusq, now with my custom zzmoove (ahem, I donated) it's all good.
[Galaxy S III Android Development] Techniques:
I flashed this over Fusion and all the gapps literally stopped working and uninstalled themselves. I tried to reflash the gapps and the same thing happened.
[Galaxy S III Android Development] andip71:
Interesting. Never had that.

Can you please let me know if this started with latest beta or if it was already an issue with former betas?

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] JustArchi:
+1. I'm getting this occasionally as well.
[Galaxy S III Android Development] andip71:
Mmmh.

Looks like I should look into that tomorrow. And hope I can replicate.

Still, would help me to understand if this is a beta5 problem or an older one.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] CroW_D:
Hey in the latest beta 5 my Phone needs very long to load why?

Gesendet von meinem GT-I9300 mit Tapatalk 4
[Galaxy S III Android Development] andip71:
Loading time is normal for me.

Anybody else?

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] JustArchi:
I'm trying to help you find a culprit Andi. It happened for me while changing governor from zzmoove to pegasusq now. Will keep you updated if anything new will pop up. Maybe it's not pegq issue if other reports problem with zzmoove as well.

BTW, I'm using Cool Tool to update frequency twice per second. If anybody wants to help I'd suggest using this tool as well, very useful.
[Galaxy S III Android Development] Techniques:
It happened in older betas too.
[Galaxy S III Android Development] Kyle07:
For me it's been happening since Alpha phase. I noticed it when my phone would charge suuuuuper slowly. After some investigation I noticed the slow charging was caused by the CPU being locked @1,6GHz on all four cores. I thought I was an isolated case as no one else ever mentioned it - so never reported it. I was on zzmove in each instance.
[Galaxy S III Android Development] HorstiG:
When i charging ofer USB (PC) and WLan is on, the Charging is verry slow. (475mAh) ??

The Charing Time ofer (Steckdose) Power Point is normal. (1000 mAh).
[Galaxy S III Android Development] Erik1805:
Yes full wipe (full wipe before flashing new ROM: wipe user data + format /system and /preload.) with Philz recovery and on beta3. Strange

---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
[Galaxy S III Android Development] andrewwright:
Yes strange thing.
[Galaxy S III Android Development] Proud2bNoob:
I'm having trouble with the WiFi since I flashed this kernel, I'm running cm11 m3. I can not toggle WiFi and it doesn't search for any networks. Is this a known issue? Other than that I can only recommend this kernel.
[Galaxy S III Android Development] andip71:
Nope, not a known issue. I am running CM11 M3 (or was running, I stepped up to latest nightly already) fine as well with b3.

But sounds like the modules have not been copied over during installing the kernel.

Can you pleae flash the kernel again in CWM. Can you, before, check if your download was ok by verifying the md5 checksum.

Thanks

Andi
[Galaxy S III Android Development] Erik1805:
I am not sure if i have asked this before, but what are your ideas on using apps like greenify? I have been using Greenify and now i have removed to test it just using your kernel with battery saving settings.
[Galaxy S III Android Development] Proud2bNoob:
Seems there was a problem downloading the first time. Re downloaded and flashed and it now works, thanks
[Galaxy S III Android Development] andip71:
Well, I do like it. And I use it myself to greenify a few processes (only 4-5 of them, so I am not a heavy user of it) that I do not want to wake up etc (like my work email app etc).

It is a good piece of software.

Cool. Glad it was easy to fix.

Andi
[Galaxy S III Android Development] Prowler:
Andi, would be difficult make a kernel build for N7100?
[Galaxy S III Android Development] andip71:
It would not be difficult in general.

But it would be impossible for me as I do not have this device (and I only develop for devices I personally own as many times pointed out).

Andi
[Galaxy S III Android Development] bihslk:
Wich one works on neat aosp rom?

Skickat från min GT-I9300 via Tapatalk
[Galaxy S III Android Development] orangerot.:
Just wanna report that I also get random freezes with temasek v45 and Beta3 (also Beta2). Also everything's lagging and slow. Even the bootanimation is laggy.

After going back to Beta1 everything's back up to normal again (same kernel settings)..

Could it be possible that it's caused by the updated source or the new compiler?

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] nicesoni_ash:
No because everything is fine here with beta3 and Temasek v45.

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] vinella:
My phone was fine until it would freeze ... so no

note that I have made one change to my config - changed govenor to zzmoove-optimal from yank ... so far havent had another freeze
[Galaxy S III Android Development] ekie84:
The Omnirom kernel

Send from my GT-I9300 using Tapatalk 2 (AOSP NeatROM v2.8 / 3.0.80+ sale)
[Galaxy S III Android Development] piats:
My wife is having troubles to hold still her phone with beta3 & Temasek's v45.1. It seems to be really slippery and fast to fly out her hands.
[Galaxy S III Android Development] andip71:
Yep, it "could".

Basically there are two changes between beta1 and beta3 which could cause significant changes in behaviour:

- updated initramfs

- updated toolchain from 4.7 to 4.8

However, I have so far no issues on Temasek v45. Just about to install v45.1 now, to see how it goes there.

Andi
[Galaxy S III Android Development] andip71:
I am "really sorry" for that. Will try to implement some more grip in next kernel version :D

Andi
[Galaxy S III Android Development] XDAMaxe:
maybe a security belt helps :p
[Galaxy S III Android Development] bihslk:
Ah okey. Thanks mate
[Galaxy S III Android Development] orangerot.:
Okay thanks for the answer. Let's see if it works fine for you on 45.1. Please let me know your results. If it's still fine for you I'll try Beta 3 again with a cleanup before updating.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] XDAMaxe:
may I please ask if there's any link where I can download older kernel versions (like beta1) ?

Unfortunately until now I deleted the older ones once a newer version was released (already blamed myself...)
[Galaxy S III Android Development] andip71:
It may disappoint you, but running without issues, lags and freezes since this morning. On Tema V45.1.

Any version you are specifically looking for?

Typically I do not give support to beta versions that are not the latest one. But if you need a specific one, I can make it available again.

Anyways, in 2 minutes beta1-3 will be available for you, so you can play :)

Andi
[Galaxy S III Android Development] Kamil194:
Is 1000mA USB charging is safe?

Ofcoruse on USB 3.0, when 1A isn't any problem.
[Galaxy S III Android Development] andip71:
yes.
[Galaxy S III Android Development] XDAMaxe:
Hi Andi,

thanks a lot.

I wanted to investigate increased batt drain while nothing changed here except flashing latest Tema roms and your kernel (always wiping dalvik+cache+system+preload before and wiping dalvik+cache after flashing to avoid any weird things).

idk exactly when batt drain starts but it can't be long ago, assumingly since V43 or V44 (w boeffla beta 1 or 2) or 45.1 (w boeffla beta 2 or 3)

fyi: Before I had max 1% drain/h now 2-3%/h in pure standby - no screen, no data, only wifi and 2g/3g (fast dormancy enabled with resp. nwk_info.db - germany e-plus should support it), all location/push services disabled, greenified most suspicious apps, no xposed framework because of ART), wakelocks and batt stats absolutely unremarkable .... strange....

I'll report later ...
[Galaxy S III Android Development] orangerot.:
Okay, then I'll try again with cleaned up settings :)

Thanks for your investigations.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] andip71:
...or... you wait for 2-3 hours still, then I might come out with beta4. In the beta I included the latest changes of the Samsung source drop last night to SEA (Asian region) and updated the initramfs.

Just if you want a super clean installation :)

Andi
[Galaxy S III Android Development] piats:
Thank you! She is so relieved now ;D
[Galaxy S III Android Development] andip71:
Good good.

It is my present to Valentine's day to her :)

Andi
[Galaxy S III Android Development] andip71:
2.2-beta4

Hi all,

maintenance update for both Omnirom and CM11 kernels after Samsung released a new source drop for the SEA region last night.

Version 2.2-beta4

Implement major parts of Samsung source update GT-I9300_SEA_JB_Opensource_Update2 from 14.02.2014

Initramfs updated to version of 14.02.14

Enjoy

Andi
[Galaxy S III Android Development] andrewwright:
Thank you for beta4.
[Galaxy S III Android Development] Choristav:
[MENTION=947981]Lord Boeffla[/MENTION] I -could- confirm laggy/freezes with .2 and .3 betas using temasek V45 and V45.1. I thought my memory ran out, so I went into apps and it froze. I tried using titanium backup and it froze again. I just scrapped everything, deleted data, system and cache and restored a backup from 07/02/2014, which had .1 kernel.

After that, I updated your kernel just fine and haven't seen the same issues, although I do see a hickup from time to time, especially when loading things.

A blind guess would be something accessing the internal memory, since all my freezes were when I was trying to access apps, during the boot animation or while loading the play store (the spinning circle would freeze and jump from time to time).

Would you like a logcat?

Edit: I had to revert to .1, since .4 was still laggy.
[Galaxy S III Android Development] DirkStorck:
I am using temasek v45 and beta4 and no lags at all.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] Kyle07:
Hi Andi,

What does this update include technically? What has been changed?

Just curious...
[Galaxy S III Android Development] Moopow:
Hi all,

maintenance update for both Omnirom and CM11 kernels after Samsung released a new source drop for the SEA region last night.

Version 2.2-beta4

* Implement major parts of Samsung source update GT-I9300_SEA_JB_Opensource_Update2 from 14.02.2014

* Initramfs updated to version of 14.02.14

Enjoy

Andi
[Galaxy S III Android Development] Kyle07:
Dude, seriously.

I meant the source drop update. I've read the new kernel changelog but I am interested in the changes that came along with the new source code.
[Galaxy S III Android Development] ZaneZam:
you could check this:

http://xdaforums.com/showpost.php?p=50312970&postcount=11387

...but deeper analyses still has to be done ;)
[Galaxy S III Android Development] JustArchi:
Nothing special. And nothing special comes in future, just some small changes, bugfixes and eventually new problems and solutions.

Don't expect anything particular from those source drops, especially because support for SGS3 from Samsung is nearly finished.
[Galaxy S III Android Development] ZaneZam:
Well archi, that applies really only to Samsung, don't it? :D
[Galaxy S III Android Development] JustArchi:
Of course it does. Andi implemented more than Samsung during all source drops apart from the first one.

Maybe with an exception for sudden death fix ;).