yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] thearc77:
Hi Andy

I saw the changes for the next Omni build and will be awesome, Mali drivers

to be included in next nightly:

NH2: WiFi (android_device_samsung_smdk4412-common)

Enable continuos focus for touch (android_device_samsung_smdk4412-common)

LPM: KitKat bootloader compatibility fix (android_device_samsung_smdk4412-common)

Cleanup & boot optimization (android_device_samsung_smdk4412-common)

Video snapshot & Optimizations (android_device_samsung_smdk4412-common)

omx_core: fix heap corruption when unregistering component (android_hardware_samsung)

samsung_battery: Attemp to fix LPM (off charging mode) with KitKat bootloader (android_kernel_samsung_smdk4412)

s3cfb_ops: Attempt to fix LPM (off charging mode) graphics issue (android_kernel_samsung_smdk4412)

cpuidle-exynos4: calm down some logspam (android_kernel_samsung_smdk4412)

smdk4412: fix build (android_kernel_samsung_smdk4412)

smdk4412: update mali driver (android_kernel_samsung_smdk4412)

dm crypt: optionally support discard requests (android_kernel_samsung_smdk4412)

dm table: share target argument parsing functions (android_kernel_samsung_smdk4412)

dm: ignore merge_bvec for snapshots when safe (android_kernel_samsung_smdk4412)

dm: suppress endian warnings (android_kernel_samsung_smdk4412)

smdk4412: update fimc_capture and sr130pc20 cam driver (android_kernel_samsung_smdk4412)

smdk4412: remove some logging I added (android_kernel_samsung_smdk4412)

smdk4412: fix mag cover turning screen off (android_kernel_samsung_smdk4412)

Touchwake updates (android_kernel_samsung_smdk4412)

mc1n2: Allow swapping of microphone ADC channels (android_kernel_samsung_smdk4412)

Revert "Revert "smdk4412: sound: update soc & codecs"" (android_kernel_samsung_smdk4412)

http://omni.cmxlog.com/4.4/i9300/

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] ayoubij:
This fixes the HWC or what
[Galaxy S III Android Development] FDisk80:
I guess Lord got some updating to do. :o
[Galaxy S III Android Development] andip71:
Yeeeeeh, maybe. When I see this kind of change log, I am always very nervous whether they have it under control and deliver quality.

But in case - yes, of course.

We will know in a few days...

Thanks

Andi
[Galaxy S III Android Development] FDisk80:
Well, I tested Nameless on another device that updated the mali drivers a while ago and I can say that the latest builds are very smooth and stable.

If OMNI did what Nameless did it all should be fine. :good:
[Galaxy S III Android Development] FDisk80:
Just a heads up, flashing the 17th omni nightly kills the baseband and IMEI. (with stock omni kernel).

Reflashing the 16th nightly brings it back to life.
[Galaxy S III Android Development] andip71:
Thanks FDisk80, valuable information!!!

Cheers

Andi
[Galaxy S III Android Development] thearc77:
Is a pitty the mess about IMEI, works so smooth :(

Reverted to 16th...
[Galaxy S III Android Development] Mostafa Wael:
Omni is merging r4p0 mali drivers in next nightlies??

Wow!!!
[Galaxy S III Android Development] FDisk80:
They already did but don't update to the 17th nightly for now. You will loose the baseband and IMEI.

Read last couple of pages on omni thread. Something went wrong.
[Galaxy S III Android Development] Maarren:
The commits look like R3P2 driver?
[Galaxy S III Android Development] FDisk80:
Looks like it.

https://gerrit.omnirom.org/#/c/9792/

Hmm :-\
[Galaxy S III Android Development] thearc77:
Ppl my bad, the 17/10 build doesn't have the new H/W composer but a lot of new binaries.

Sorry for the confusion
[Galaxy S III Android Development] iamdutchy:
this update crashes the app :(
[Galaxy S III Android Development] JustArchi:
https://github.com/JustArchi/ArchiKernel/commit/b4da9b22f1837d547e7c3453b8927c295ca89c8c

Looks familiar?

We implemented that around 11 July, Andi has this in Boeffla as well since AGES.
[Galaxy S III Android Development] abhibnl:
Big LOL! And people were expecting r4p0 without even reading full commit

Sent from Galaxy S3 Powered by AD 1.x + Boeffla
[Galaxy S III Android Development] andip71:
Well, not for me and almost all others...

Uninstall and reinstall it for a test.

Or tell me more when it crashes for you and when etc...

Andi
[Galaxy S III Android Development] DonHuan:
Boeffla-Config V2, version 2.1.49 works fine for me! Thanks for new functionality, [MENTION=947981]Lord Boeffla[/MENTION]!
[Galaxy S III Android Development] XDAMaxe:
Carbonrom (i9300) with boeffla kernel 2.4b6a Omni-NG and ConfigApp V2 2.1.49 runs perfect as always (and big thanks for the wifi scan interval edit option) :)
[Galaxy S III Android Development] Richard_10:
Hi Andi,

I have an annoying problem with my sd card "Sandisk Extreme 16GB". It's always getting kindda unmounted. I have to reboot to make it work.

If I use the settings to unmount it the system soft reboot.

Ps: it's Exfat formated.

Please help. It happened 3 to 4 times a day.
[Galaxy S III Android Development] kornkid:
I got a weird error flashing the latest kernel from the boeffla app, I guess it flashed the version for 10.1 and I'm on 10.2 so I lost my WiFi connection... :eek:

I solved it by downloading the proper version from Andy's site and flashed via recovery. Maybe it's something Andy should check out.
[Galaxy S III Android Development] andip71:
Well, flashing the 10.1 kernel on a 10.2 firmware is clearly not a very good idea :)

However, yes... sometimes the kernel really needs to be flashed in recovery (which is - by the way - the standard for Android in general) as sometimes the app cannot delete all the modules properly.

So, all having wireless issues after flashing in the app: just enter recovery, flash there again, and all should work. I will add a note to the OP tomorrow when I release version 2.0-beta1 for all of you.

Andi
[Galaxy S III Android Development] donalgodon:
Just to ask, will the beta support 10.1 and 10.2? I'm thinking about flashing back to 10.1.3 Stable, but I won't do it if I have to live without Boeffla.
[Galaxy S III Android Development] indigold:
thanks a million. that temasek guy updates too much .lol he is dedicated
[Galaxy S III Android Development] FlemishDroid:
I updated my cm10.2 to latest nightly today. I flashed the cm10.2.zip then I immediately flashed the stable 1.0 kernel and after reboot there was no wifi signal/icon. So I flashed the kernel a second time and wifi works again. I always install the kernel trough cwm recovery so it's not only when you update with load and flash. I've had this "problem" several times in the past but after a second install wifi always works again.

Verstuurd van mijn GT-I9300
[Galaxy S III Android Development] andip71:
Yes, I will bring both versions - for CM10.1 and CM10.2 - tomorrow.

Andi
[Galaxy S III Android Development] beerlao:
Hi Lord Boeffla,

I wonder if it was possible for Boeffla Kernel to support changing the output volume of the earpiece (just like it does support changing speaker and headset volume). The reason is I have sometimes a hard time to understand callers on my phone, I just can't tune up the volume loud enough. I tried raising the output volume of the earpiece device in /etc/sound/m0, but I'm not sure if that's the way to go.
[Galaxy S III Android Development] andip71:
2.0-beta1

Good morning all!!!

Time to start with the "next generation" Boeffla-Kernel 2.x now. So please find now:

2.0-beta1

Before I come to the change log, most important: You need a new Boeffla-Config App for it (V2). You can get it from Google Play. It will not work anymore with the app you are currently using. Of course donation keys still work with the new app as well. Details please see in the change log below.

Change log (vs. last stable 1.0)

IMPORTANT: You need the V2 version of Boeffla-Config from playstore for this kernel. Export your profiles into files first, deinstall the old app and import your profiles into the new app version afterwards !!!

This next generation kernel will NOT work anymore with the older version of Boeffla-Config !!!

Completely changed the way Boeffla-Config app and kernel communicate during phone startup (get rid of issues due to missing root rights)

Upstream to 3.0.100 Linux kernel from 13.10.13

Compatibility with PAC man rom (only CM10.2 kernel)

Why do I call it next generation kernel?

Because the way app and kernel work together during system start is completely replaced by a new approach. This approach does not require the app anymore being active (and requiring root) during phone start up. This will finally get us rid of all issues that occured due to that. It just works now, regardless if app has rights or not.

Of course when using the app to configure, root is still required, just mentioning before you ask :)

Enjoy - as always load it from homepage (which is now fixed in terms of downtimes my provider told me) - or load&flash.

Cheers

Andi
[Galaxy S III Android Development] andip71:
Do you mean a bluetooth connected earpiece?

If yes, then I have to regret, I cannot influence this with Boeffla-Sound.

Bluetooth is a completely digital signal path. Boeffla-Sound however only works on the analogue audio hub.

Or did I misunderstand you?

Andi
[Galaxy S III Android Development] beerlao:
Yes, sorry, seems that I mixed things up. I mean the front speaker which you use during calls when holding the phone to your ear ;) Since I use CM volume during calls is really low. Is it just my impression?
[Galaxy S III Android Development] GTMoraes:
Thanks for the kernel update!

Sent from my Nokia 1100 using Snake II
[Galaxy S III Android Development] BioVolt:
I thought the new update would solve my bootloop problem with Boeffla but unfortunately it is still not working on Fusion Rom, oh well I will keep trying new updates, hopefully it will work again someday, I need my Boeffla fix └(^o^)┘
[Galaxy S III Android Development] andip71:
Well, would have surprised me, because I did not put anything in for this rom.

I guess it would (as many roms these days) require changes to the bootpath variable.

But I have not investigated as I do not have the time to investigate compatibility issues with every rom around, this is just impossible.

Andi
[Galaxy S III Android Development] BioVolt:
I understand that it is impossible, just thought I might be lucky what with the Rom being a culmination of CM10.2 etc..

Is there anything I can ask the Rom developer that would help in making Boeffla compatible? I don't mind getting the necessary information for you, let me know.

Or is there any information that I can extract from the Rom itself that will help?

Thank you.
[Galaxy S III Android Development] andip71:
BioVolt, sure... go ahead for it. If the changes required do not cause any other impact, I am more than happy to incorporate them (as I did with Pac man rom as well).

If you can grab this information for me, then it would be a big help and time saver for me.
[Galaxy S III Android Development] cerealguy:
I'm on last Bam Rom 1.0.0 RC3 and last beta don't work on it... Is there the possibility to make it work? :rolleyes:

Inviato dal mio GT-I9300 con Tapatalk

---------- Post added at 11:32 AM ---------- Previous post was at 11:27 AM ----------

EDIT: If I can help you, last temasek kernel work on this rom...

Inviato dal mio GT-I9300 con Tapatalk
[Galaxy S III Android Development] cheese458:
lord, (haha)

does the 2.0 kernel have any actual performance/battery improvements? Is it much of an upgrade from 1.0 stable?

thanks
[Galaxy S III Android Development] andip71:
Guys, to say it again: Yes, of course there is always the way to make the kernel work somehow with every rom.

But if I follow that route, I am doing nothing else anymore than investigating why the kernel does not work with ram abc, xyz etc. This is not what I wanna do.

I make sure the kernel works with the 3 roms listed in the OP, as they are pretty much standard.

If you want your specific rom to work with the kernel as well, please be active and contact the rom developer to get instructions about the specific requirements for the rom. With that, I am happy to check and decide about putting it in or not.

Thanks for understanding.

Andi
[Galaxy S III Android Development] andip71:
I would certainly recommend to step up to 2.0 kernel, as the way app and kernel interact with each other is significantly improved and should cause less issues.

But if you are happy with 1.0, you can of course also stay there. Up to you :)

Andi
[Galaxy S III Android Development] wallah:
After flashing kernel 2.0 beta 1 on probam rom, his brake many aplication, like apex launcher etc....
[Galaxy S III Android Development] @non4:
Its the damn phone. This is why I upgraded early, i need my sdcard and it was just unmounted and corrupted constantly! Samsung card too! So it's not the rom, your phone's days are numbered [emoji90]
[Galaxy S III Android Development] andip71:
Something seems to be wrong with the card etc.

Have a 64 gb card exfat and it never unmounted.

But yes, heard many times tge s3 can be very picky with sd cards...

Sorry, but I think I cannot help.

Unless you tell me with previous kernel versions it was different?

Andi
[Galaxy S III Android Development] VanXamar:
Hi guys

I switched to omni 4.4.4 omega. And I'm using this kernel 2.3a. What I don't understand is when my battery is empty and the phone is off battery won't charge. And if I want to turn on the phone I have 2 pull my battery. Does anyone know a work around? I need to charge my phone when it's empty.

Thanks in advance
[Galaxy S III Android Development] Ping_2000:
Hey, i had also trouble with my sd-card.

System told its unformatted all the time.

Then I replaced SD slot, replacement was under 10euro and now every thing is fine again.

Maybe this will help you too?

Greetz
[Galaxy S III Android Development] andip71:
Known issue with some rom/kernel/bootloader combinations.

Make sure you never discharge to the very end (not good for the battery).

Andi
[Galaxy S III Android Development] Richard_10:
I'll give it a try. Thank you man.

---------- Post added at 04:32 PM ---------- Previous post was at 04:29 PM ----------

That so disappointing. Think it's related to the sd card speed. When it's too fast the slot cannot manage it.
[Galaxy S III Android Development] Buckycasuals:
[MENTION=947981]Lord Boeffla[/MENTION]

Quite an interesting article on Android L and kernel compatibility. https://plus.google.com/+Chainfire/posts/VxjfYJnZAXP
[Galaxy S III Android Development] fcaronte:
Is the battery life better than stock cm11?
[Galaxy S III Android Development] cloudx720:
Think andy will ever make an S5 kernel? I miss it lol
[Galaxy S III Android Development] andip71:
Cloudx... Future will show.

Very short term it will not come unfortunately.

We have now 3 OnePlus One devices in house, kernel work for them is currently very exciting...

But never say never.

Andi
[Galaxy S III Android Development] andip71:
New beta kernels

Hi all,

2.4-beta7 is now ready for you (all 4 kernel variants - CM11, CM11 NG, Omnirom, Omnirom NG).

Change log is the same for all 4 kernels.

Version 2.4-beta7

22.10.2014

Update zzmoove to version 1.0-beta1 (credits to ZaneZam)

Update exFat driver to 1.2.9

Update the flash binary in the boeffla-kernel-reset recovery script, bump to version 3.1

Updated ramdisk to version of nightly 21.10.14

Enjoy

Andi
[Galaxy S III Android Development] nicesoni_ash:
Getting this error..

It's showing me offline but my net is working fine..

_____________

Sent from my "GT-I9300/1+1" powered by Temasek/Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
Well, then just try again a bit later (30 minutes).

Likely, you cannot access my site where I store the content at the moment.

I guess you have not removed rights from Boeffla-Config by any other app like xprivacy or so...

In any case, you can manually download and install as well.

http://boeffla.df-kunde.de/bc/

Andi
[Galaxy S III Android Development] khanmein:
what's asv/psv level? mine shown 5 instead of 7
[Galaxy S III Android Development] andip71:
I suggest you read the documentation about ASV level on the kernel homepage, or google for it.

It shows how good your CPU is manufactured. Everyone can have different values here. 7 is slightly better than 5, so the CPU can operate with slightly lower voltages.

There is nothing you can do about it, also there is nothing to worry about. It just says how good your cpu was manufactured.

Andi
[Galaxy S III Android Development] ayoubij:
I was wondering if we can know before buying a device? Lets say at the store, and he show you cpu 2 phone can you kno without software?
[Galaxy S III Android Development] andip71:
There is no way to find that out without a kernel that supports that reading or grepping the dmesg.

At least I am not aware of any other way.

Andi
[Galaxy S III Android Development] ficko_98:
Installing new boeffla cofig works great, thank you andi. :)
[Galaxy S III Android Development] khanmein:
i don't think so. i saw alot 3. maybe due to the mobo & different region handset. so far s3 served me quite well so no need change.
[Galaxy S III Android Development] HaarisTheBoss:
I have this problem where some cables charge the phone whole other don't. If I increase the charge current do you think it will help to solve this problem5
[Galaxy S III Android Development] andjeomilosrdja:
You should increase current for usb to 1000 in Boeffla settings i then it will work with any cable.
[Galaxy S III Android Development] smajlo:
Since update to Omni NG test 7 this morning I'm experiencing this wakelock. Any ideas?
[Galaxy S III Android Development] andip71:
This wakelock comes from the modem, although listed as a kernel wake lock.

I doubt this has to do with the kernel due to that, could be some changes your provider did, or fast dormancy changed or or or...

You can fallback for a day to beta6 to check if it is gone then.

And if so, go on beta7 again for a day and see if it comes back.

Andi
[Galaxy S III Android Development] smajlo:
Its strange, as I haven't seen it ever before and all that changed in my setup today it's the kernel. Currently on Omni non-NG test 7. Will see tomorrow.
[Galaxy S III Android Development] khanmein:
try update betterbatterystats. i don't have the wakelocks. observe one more day. cheers.
[Galaxy S III Android Development] smajlo:
Wakelock is gone for now. Don't know if it is thanks to kernel change or maybe just rebooting my phone helped ;)
[Galaxy S III Android Development] andip71:
What does it mean... kernel change? Did you go back to beta6 or stayed on beta7 and just rebooted?

Cheers

Andi
[Galaxy S III Android Development] smajlo:
As I said above, changed first to Omni beta 7 (was on NG version) and with kernel change I had to reboot my phone. If everything will be ok in the evening, I will go back to the NG version again.
[Galaxy S III Android Development] andip71:
Allright, thanks!

Let us know pls when you switch back.

Andi
[Galaxy S III Android Development] x7moodx:
Sorry for disturbing but since cm ng beta 6a and I am facing too much heat it wasn't there on beta 6 I don't know about the normal beta without ng but tried to roll back to ng beta 6 and the heat and all other symptoms gas gone
[Galaxy S III Android Development] andip71:
You should use beta7 already, not the oder beta6 versions :)

Andi
[Galaxy S III Android Development] x7moodx:
I am on beta 7 already and I won't downgrade for such a problem thanks for replying

You are the best
[Galaxy S III Android Development] andjeomilosrdja:
No problems what so ever,just wondering is there anything that doesn't belong here.
[Galaxy S III Android Development] andip71:
Well, yes, some could be suspicious... if you want me to look into them, zip and mail them to me (support@boeffla-kernel.de)

Cheers

Andi
[Galaxy S III Android Development] NoxOn3:
Hey there, got some problems with music players get killed while opening any browser app. I'm on PacMan 4.4.4 rc2. Previously was on PacMan 4.3 and you're kernel. Never had this problem...

I'm on your latest beta. (tried both versions non-ng and ng.) anybody who has the same problem?
[Galaxy S III Android Development] andip71:
Hm. Then seems pac team changed memory management in between the versions.

You could try to activate zram...

Andi
[Galaxy S III Android Development] lsalamun:
[MENTION=947981]Lord Boeffla[/MENTION] to conclude, is the camera quality in cm related to NG version? Because i know the quality in AOSP based roms is poor because lack of drivers, is NG version fixing that or is it somewhere inbetween? I am asking because i'm a heavy snapper haha :)

Regards.
[Galaxy S III Android Development] 2phazt:
Which kernel should I use for AOGP rom? It is CM based, so I tend to the CM kernel but if someone has allready made experiences with this new rom and could share this, it would be helpful.
[Galaxy S III Android Development] Buckycasuals:
Omni Kernel or OMNI NG series
[Galaxy S III Android Development] andjeomilosrdja:
I am using Omni Ng.
[Galaxy S III Android Development] ayoubij:
I use snapchat all the time and ive got no problems

Once in a while maybe every 100 times you might get cant connect to camera error, so just download restart camera apk by temasek and install it it would restart the camera and then you can use it again.
[Galaxy S III Android Development] XDAMaxe:
ums mode

idk if it was on earlier versions too (cos I hadn't tried) but UMS mode (usb mass storage mode for accessing ext. sd card) doesn't work.

What I have done:

1. every option for mtp and ptp mode in settings-storage disabled

2. UMS in config app enabled

3. all went as usual (message in the notification bar for usb debugging and so on) after connecting usb cable to pc (win xp with latest Samsung usb drivers)

4. drive icon appears immediately on windows workplace but no access possible (message 'please insert drive')

5. logcat attached fyi

phone: i9300 carbonrom (nightly 20141026)+boeffla omni ng 2.4b7

[MENTION=947981]Lord Boeffla[/MENTION] do you have any idea ?
[Galaxy S III Android Development] lsalamun:
I get restart camera almost every time when i tra to use other camera software, ike google camera or better camera (because it provides hdr), i stoped once again using aosp just because of hdr lacking and no manual focus in video.
[Galaxy S III Android Development] evilperro:
freezes, reboot

getting freezes and soft-reebots. Have not changed any configurations, except enabled UMS (only reason I got Boeffla).

According to a CM S3 forum post, I have to reinstall entire CM to get the default kernel back. Is this true?

What can I do to stop the freezes and reboots? Is there another kernel which makes UMS possible?

S3 i9300 CM 11 M10
[Galaxy S III Android Development] mad_ady:
I'm using Snap Camera trial with no issues. It has hdr support (on NeatROM AOSP)
[Galaxy S III Android Development] 2phazt:
Im using the pro version - its a really good camera.
[Galaxy S III Android Development] adripred:
The only bug I found in Snap Camera is hang when changing the image size. I had no problem using normally.

Regards!
[Galaxy S III Android Development] Adam3Sixty:
Dunno if ur interested or not, but OmniROM is now available for the OnePlus One, using basically the same stuff as the Oppo Find 7.

Not asking for u to do anything for the Oppo, but ur OmniROM kernel for the S3 is legendary, so u could bring that same magic to the OnePlus, which I know u already work on :)

http://dl.omnirom.org/find7op/
[Galaxy S III Android Development] 200:
Slimkat

2.4b7 working flawlessly on i9300 Slimkat.... and fwiw, no camera issue whatsoever on SlimKat8 with boeffla (using it daily for a month now). :)