yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
Well, I think I explained it already:

The kernel is completely built from scratch by not using CM or Omnirom kernel sources anymore, but pure Samsung code. This is the main reason for NG.

On top there will be the latest zzmoove beta in, updated initramfs, the double-tap-to-wake feature.

But there will be a "normal" (non-NG) version with all that features as well, so no worries.

Andi
[Galaxy S III Android Development] nicola1989:
So translating this, means better performance and battery! Right?
[Galaxy S III Android Development] andip71:
The testers will report, maybe, maybe not... I do not yet know after a few hours only :)

Andi
[Galaxy S III Android Development] nicola1989:
Damn I'm curious, now I have to try it

????
[Galaxy S III Android Development] andip71:
Hehe ☺
[Galaxy S III Android Development] dhirend_6d:
That is just awesome.:good::good: I was hoping you would release one based on Samsung sources. The performance and battery is bound to increase.

Also, will the new kernel be supported by the Boeffla app for tweaking??
[Galaxy S III Android Development] andip71:
Yes, it will have all the features of the known cm and Omnirom Boeffla kernels.

And of course fully customizable with the app.

Just the foundation is completely different.

All functions and comfort for the users, as always ☺

Andi
[Galaxy S III Android Development] lovegurulavdev:
does not boot with the latest carbon nightly .. stuck on boot screen ...

thanks ..
[Galaxy S III Android Development] nicola1989:
Boot fine on m8 cyanogenmod, as first impression, I see more., smooth than the last stable kernel! I will test battery
[Galaxy S III Android Development] JustArchi:
It's not like I want to fight, I mostly base my opinion on opinion of my users. If they say that battery drastically improved and kernel is more snappy and stable than ever before, I have to agree with them.

smdk4x12 is a crap base and we all know it. Somewhere around Update7, when codeworkx stopped actively maintaining sources, they got desynced from the upstream Samsung updates. I'm not even mentioning that they updated 3.0.15 to 3.0.64, while pure stock is based on 3.0.31, so again, mismerges are strong with this one.

As for now I just fixed everything I wanted to keep in-sync with AOSP ROMs, this includes haptic support and regulating vibration strength, SELinux, backlight etc.

Right now I simply don't want to go back to crappy smdk4x12 sources because I have no reason for doing so. My kernel based on top of Update13 sources is better in every single thing, battery, performance and stability. We all know that smdk4x12 is currently abandoned, by both CM and Omni. Nobody is working on it, nobody wants to fix all this mess that has been created since codeworkx left. I decided that it's pointless to even try to fix this, so I started on Update13 sources and slowly started merging all things I wanted/needed to keep compatibility while not having to make any tradeoffs.

And now?

I have my own big menu for everything I want, so building Sammy kernel from this source is as easy as changing target system to Samsung. Wooho :victory:.
[Galaxy S III Android Development] Hatef.PR:
Flashed the latest stable version (2.3) on my phone and working fine! ;) My ROM is CarbonROM and had no problem!
[Galaxy S III Android Development] ScratMan38:
With the Next Gen 2.4 beta1, everything seems to work fine. Battery seems to be good, but I did not make a charge cycle, so there are some old battery stats remaining. Everything is smooth.

So far, looks exactly like ArchiKernel 1.2, but with working Touch2Wake :victory:
[Galaxy S III Android Development] flither:
[MENTION=220904]andi[/MENTION], I would definitely say your 2.4 NG test version is much ready for being a daily driver, at least for me :) how did you do this magic in less than 24h? :laugh::good:

[MENTION=3609110]ScratMan38[/MENTION], congrats on T2W working, but it seems not working for me (you're on CM though).

EDIT: I meant KnockOn not working, T2W is fine. Straight-after-out-of-the-bed posting, my bad :o
[Galaxy S III Android Development] ScratMan38:
Yes, I'm using AD 2.5.0, based on CM11. I activated both of the Touch2Wake options (enable and permanent when plugged on USB), and its working fine.
[Galaxy S III Android Development] andip71:
So, what is not working with knockon?

Note: It is not what you might expect. It is the same than touch-to-wake, just that you need a double tap instead of a single tap.

Andi
[Galaxy S III Android Development] flither:
yes I know, but it's not working for me - I tried knock on with different delays, with and without security lockscreen - no luck. Maybe it has something to do with built-in double-touch-statusbar-to-sleep in the ROM? or because I flashed it over the previous kernel? i've no idea.

On the other hand i'ts not something I cannot live without, but may be important to the others:)
[Galaxy S III Android Development] 2phazt:
2.4 CM is working great for me!

So far i have tested and found working: oc 1704, zram, camera (snap cam) and all apps seem to work properly.

Also the handset might work a bit smoother - maybe placebo but who cares ;)

Good work, Andi - two thumbs up! ?
[Galaxy S III Android Development] vboyhn:
I flash lastest boeffla kernel and install lastest app config.

Why do not turn on knock on?

Gửi từ GT-I9300 của tôi bằng cách sử dụng Tapatalk
[Galaxy S III Android Development] andip71:
Sorry for my harsh words now, but tired to answer the same question every day again.

Use search, it has been answered already many times.

It is not yet implemented in the kernel!!! Also stated in the change log of the app itself.

And if you keep me busy with answering the same questions over and over again, I will not bring it even this week as planned, as I do not have time left from answering the same questions over and over again.

Andi
[Galaxy S III Android Development] vboyhn:
So sorry for my stupid. Thank you so much.

Gửi từ GT-I9300 của tôi bằng cách sử dụng Tapatalk
[Galaxy S III Android Development] boyheadkick:
To add to this, when testers want to give feedback regarding the new sammy source based experimental kernel i think it's better if we just pm Andi instead of replying in this thread as it might cause confusion with other users who are on the stable release..there are features in the experimental that have not been implemented on the stable release and others might confuse those features with the stable release..just saying :D

-aL

tapatalked from my super duper palm top computer
[Galaxy S III Android Development] ScratMan38:
There is no feature added in the 2.4 beta1 vs 2.3 stable. Only the source is changed from smdk4x12 branch to Samsung stock. Kernel features are the same (except the MDNIE override which gives different results due to different source).
[Galaxy S III Android Development] andip71:
Nope, not true. Then you have not tested "properly"... :D

I think I wrote it yesterday, the 2.4-beta1 (either NG or not) will have the following stuff on top:

- zzmoove 09.beta3

- knock on feature

- negative mdnie mode fixed

Andi
[Galaxy S III Android Development] Pablo.x:
When will be released that beta version for everybody Andi? :)
[Galaxy S III Android Development] andip71:
There is a golden rule on XDA... never ask for an ETA.

It is there when I uploaded it.

Plan was for this week, but maybe it is getting later. Not yet sure.

Andi
[Galaxy S III Android Development] abhibnl:
Okay i've done a full cycle on test CM version according to my daily usage, so here are my views:

1. Kernel is definarely smoother even on 25uv.

2.Battery lyf is as good as i get on a stock version. It's just the wifi who sucks more battery but that's a problem i face on rom side i assume.

3. Screen colors are a better than previous version on CM version( can be placebo)

4. Sound n Deep sleep are working fine!

Bugs/problems

1. Videos recorded with H.264 codec on cm11s camera app(Rohan's fix version or manual installation) are not playable by stock video player. With other codecs it's fine!

2. Knock on.feature not working. Tried double tapping. T2W and knock on both are on.

3. Sometimes phone doesn't play audio at all for 1-2 seconds while playing songs. Tried on different media players. Was trying to.set new ringtone, again I started getting any sound aftr 2 secs!

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] andip71:
Thanks for the feedback, although I was asking to send it to me via PM to not confuse people.

On the bug side:

1) Can you check with todays CM nightly please? The German CM board is full of messages like "with todays nightly all my cam problems are gone". I can also confirm it works flawlessly for me with CM11 stock camera. Multiple pictures, multiple videos - all fine.

2) Working perfectly fine for me. Please post screenshot of your configuration in Boeffla-Config and how you tested it.

3) This could be an interesting one: May I ask how you configured kernel logger please? If it is off, set it to on again and test again please.

Thanks

Andi
[Galaxy S III Android Development] abhibnl:
1. Will try today's nightly for sure! And will report via PM.

2. It's working now, turned off, reboot, turned on and now it's working.

3.kernel logger is off, as i always turn it off! Will try with logger on.

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] andip71:
Thanks abhibnl.

To 1) Another user here just confirmed with todays CM nightly his camera works flawless finally.

To 2) Good, don't know what it was. Lets monitor.

To 3) Well, at least with my CM/Omnirom kernels this was never possible so far to switch it off. As it was causing the sound issues since CM10.2 already. So I removed that option in normal CM11 kernels and hoped, on the Samsung based kernels this issue would be gone. But seems it is not, so for safety reasons I will remove this kernel logger option again, just as it is with all previous CM kernels I provided.

But will wait for your feedback on it with kernel logger switched to on.

Thanks

Andi
[Galaxy S III Android Development] nicesoni_ash:
Fine here with kernel logger on so apparently it looks like disabling it might have caused it.

_____________

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

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] abhibnl:
I can confirm too that latest nightly fixes video record bug! Though Google camera was continously FCing but cm11s camera worls flawlessly!

About the audio issue, i'll report tomorrow. Have turned logger on.

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] andip71:
The next version beta1b is up on dropbox for the testers. Kernel logger setting is now disabled again to avoid sound issues.

Cheers

Andi
[Galaxy S III Android Development] flither:
This didn't solve the problem in my case in Omni's variant.

Psssst, hint...let's prepare for some sensational battery life here :)
[Galaxy S III Android Development] you_man:
Strangely, I have disabled both loggers and there is no sound problems
[Galaxy S III Android Development] andip71:
What rom do you use?

I use Omnirom variant on pure Omnirom, working fine...

This is sporadic, sometimes it works fine for hours, but it comes back from time to time.

It drove me crazy when I started my first CM kernels, and took me long time to find out and pinpoint.

Andi
[Galaxy S III Android Development] you_man:
Hmm, okay.

In any case, stay on b1, for me it's wonderful.
[Galaxy S III Android Development] andip71:
yes, and on beta1b (which is on dropbox for the pre-testers now), the kernel logger cannot be disabled anymore. problem solved :)

Andi
[Galaxy S III Android Development] flither:
Latest NeatRom 6 AOSP, based on SlimKat.

Video recording is totally broken in my case as well(it is recording, but...), probably have to wait for new weekly.
[Galaxy S III Android Development] andip71:
This camera, photo, video recording issues are a neverending story.

Guess what I say: This will never be running fine for more than 90% of all the users.

The issues are known for such a long time now, if it were simple to fix, somebody would have done it already.

Instead, both CM and Omnirom teams do this, do that, there are independet "camera fixes" and and and around... quite a messy situation indeed. And not convinced that will ever change somehow.

Sad, but true.

Andi
[Galaxy S III Android Development] abhibnl:
Broken on beta version or stable 2.3?

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] flither:
Yeah yeah, it is like a big kitchen with many fridges, people taking things from here and there - some make delicious tasty dishes and some make fish&chips ;)

---------- Post added at 07:34 PM ---------- Previous post was at 07:24 PM ----------

Regular video recording is fine with 2.3 stable, just high frame and timelapse broken. With 2.4 betas all video functions are broken.
[Galaxy S III Android Development] andip71:
Interesting how different that behaves for different users, or?

On my side, with the 2.4 NG betas camera and video is just working fine.

However, I have NO "cam-fixes" etc installed. Maybe thats why. I have fresh roms only, no hacks, no custom roms etc.

Andi
[Galaxy S III Android Development] cloudx720:
kernel/samsung/smdk4412

•*0ef0f07 smdk4412: fix build

•*3de5d09 Merge "smdk4412: update mali driver" into cm-11.0 latest cm11 nightly, seems really smooth and fast with stock kernel now or is it just me lol?

This change seems good :)
[Galaxy S III Android Development] nicola1989:
It's a next nightly change?
[Galaxy S III Android Development] abhibnl:
I guess that is entirely rom related! Though i'm not sure if kernel must be updated too.

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] flither:
yes, you cannot satisfy everyone, there are too many variants/combinations/hacks out there. There is only one thing always staying on my phone for sure - Boeffla Kernel! :)
[Galaxy S III Android Development] cloudx720:
Yeah newest nightly from today :)
[Galaxy S III Android Development] andip71:
... And since this nightly my cn stock camera is working without a glitch.

Andi
[Galaxy S III Android Development] andip71:
No. There is a kernel commit but this is for tge 4210 exynos as far as I could quickly see.

So mostly rom thing.

Andi
[Galaxy S III Android Development] Yeti47:
Yep, I can also confirm. Used to lock when taking lots of quick shots. Fine now. ?
[Galaxy S III Android Development] nicola1989:
Try video
[Galaxy S III Android Development] Yeti47:
I did, shot 2 in succession and also took pictures during the process. Faultless.

But what works for me may not for others...
[Galaxy S III Android Development] andip71:
Exactly. With Codec on mpeg4 I get great video results too...

Andi
[Galaxy S III Android Development] Buckycasuals:
[MENTION=947981]Lord Boeffla[/MENTION] What has changed in todays nightly to give the excellent result in camera on CM?
[Galaxy S III Android Development] abhibnl:
Google> search for "CM11 I9300 Nightlies Changelog"> and there we go! You'll have the full details!

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] Yeti47:
Direct link, went into this mornings nightly

http://review.cyanogenmod.org/#/c/67495/

?
[Galaxy S III Android Development] Buckycasuals:
Thanks m8
[Galaxy S III Android Development] JustArchi:
Andi, you may want to cherry-pick this for your NG.

https://github.com/JustArchi/ArchiKernel/commit/04a702574fa2bd4de984d62dcf8bf08790a65f60

:cool:
[Galaxy S III Android Development] andip71:
To all pre-testers of the NG kernel !!!

I just uploaded a version beta1c for you.

This has the not properly working h.264 codec fixed now.

Means: video recording and playback using that codec should work without issues again now.

Thanks Archi, will look at it during today. I saw the commit already in the CM11 kernel repo, however different of course.

Andi
[Galaxy S III Android Development] JustArchi:
Yeah, different is a key word here... Now you know why I hate smdk4x12 sources :).
[Galaxy S III Android Development] andip71:
Yeah, hm, somehow I had the feeling for quite some time, you do not really like the smdk4x12 sources... lol :D
[Galaxy S III Android Development] abhibnl:
I was waiting for you.to say this! [emoji12] you like cursing smdk sources don't you archi [emoji13][emoji13][emoji13]

Sent from Galaxy S3 Powered by Archi + Boeffla

---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------

I'm having a feeling andi will! [emoji3]

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] JustArchi:
In smdk4x12 world everything is different.

"Archi, why you hate smdk4x12 so much, it works!"

Yes, it does.

You should've seen my face when I booted my first alpha version based on Update13 sources on AOSP and it worked.
[Galaxy S III Android Development] abhibnl:
[emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23]

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] andip71:
And to make it even more convenient for the pre-testers, I have now enabled the integration in the app for the NG kernels as well.

You can see new versions in the app and directly flash them via load&flash as usual.

And... you can also access the change log now in the app already.

Andi
[Galaxy S III Android Development] flither:
Andi, you're genius. Video recording is working fine now with beta1c! :good: EDIT: Both for h.264 and MPEG4

ROM in my sig;)
[Galaxy S III Android Development] marenp:
I would really like to try new kernel :D

Sent from my GT-I9300 using ArchiDroid 2.5 powered by latest Boeffla kernel
[Galaxy S III Android Development] tisazalay:
I'm getting a 404 when selecting kernel changelog, also a -- Offline -- from latest config (.45), is it already up for Omni version?

Thanks a million
[Galaxy S III Android Development] andip71:
Typo on my side, sorry. Please try again, now should work.

Andi
[Galaxy S III Android Development] abhibnl:
I condirm both H.264 issue and no audio due to kernel logger issues are fixed with 1c.

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] tisazalay:
Thanks, it's perfect now.
[Galaxy S III Android Development] andip71:
Thanks. Seems like it is coming close to a public beta for all... Hm, need to think. Did not want to do that really before my relocation-holidays start mid of next week as I will be out of business for a quite long time. Hm. :confused:

Thanks, was a stupid typo I did. Sh*** happens :)

Andi
[Galaxy S III Android Development] abhibnl:
Yup! Quite stable for a public beta. However Andi just out of curiosity, are there any future optimizations/tweaks planned for this kernel, since this is still freahly baked from stock sources? Any plans for an experimental upstream to 3.4 or higher? After your relocation ofcourse!

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] nicola1989:
For what I see last c beta, it already good to be public. Battery is good and for my device camera is fixed
[Galaxy S III Android Development] andip71:
No plans to go for risky upstreams like a 3.4 upstream. It does not bring any known and proven benefit while carrying lots of risk for broken functionalities.

I am not a fan of it, also far away from my objective "close to stock".

Apart from that... whenever something is looking interesting and matches my overall objectives, I will consider.

Just do not ask me what exactly, I think the kernel is pretty much in a shape it does not need too many things on top again.

Andi
[Galaxy S III Android Development] flither:
+1, there's no need to hide it from people anymore;). It's as stable as any previous 2.2 betas i tried, great batt as usual, I almost forgotten I flashed it haha:)

only KnockOn left not working for me (seems like I'm the only one ATM;)), so much suitable for official beta.
[Galaxy S III Android Development] WhoDunnit:
SELinux

Andi, just a quick question about the 2.4-beta1c NG: I noticed that SELinux is disabled; is this intentionally? Any problems in enabling it again and switching it to permissive?
[Galaxy S III Android Development] andip71:
Yes, this is by intention.

All my kernels have SELinux switched off, was always the case. Also on the non-NG kernels btw.

And I have no plan to change that. What for? It creates more broken functions than any good.

Andi
[Galaxy S III Android Development] WhoDunnit:
I hate to contradict you, but according to the changelog, since Version 2.1-beta2 SELinux is set to permissive, and I just checked 2.3 stable and indeed SELinux is set to permissive. In 2.4 it is disabled. At least when it is enabled, users can choose to set in to permissive or enforcing.
[Galaxy S III Android Development] abhibnl:
Completely agreed!

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] andip71:
Ok, yes, I was not precise enough.

On the CM kernels based on CM sources, SELinux is permissive. So violations are logged but not prevented.

In the Samsung based kernels I switched it to off completely as I think it is only overhead by logging the stuff that nobody will analyze/read anyways.

Would you like to have it on permissive or enforced? Give me some good reasons please :)

I personally do not see a reason to change it...

Andi
[Galaxy S III Android Development] Buckycasuals:
I think Agni PureCM has the option to change to permissive or enforcing in AROMA. However, i reckon that GoogyMax last version was switched OFF. For whatever reason, I think that NG beta1c is stable enough for official release.
[Galaxy S III Android Development] WhoDunnit:
Well, the real reason why I asked is that my logcat is now cluttering with audit errors "Failed on audit_set_pid with error: Protocol not supported", and just to show my ignorance :o, I proceeded to link it to SELinux being disabled...
[Galaxy S III Android Development] Moster2:
Permissive is ok. With enforced you can get problems with root on superuser. At least this is what I noticed so far.
[Galaxy S III Android Development] :
Why does this kernel doesn't work on PAC ROM if most of this ROM is based on CM ?
[Galaxy S III Android Development] nicola1989:
Try Omni version of the kernel
[Galaxy S III Android Development] Buckycasuals:
It works with proper modification on frameworks.jar. No idea why PAC team doesn't want to change that with a simple line of code.
[Galaxy S III Android Development] ScratMan38:
PAC ROM is based on 3 ROMs : Paranoid, AOKP and CM.

It's kernel is known to be specific and incompatible with many kernels developped for CM
[Galaxy S III Android Development] andip71:
Ah, ok. Good, I did not check that yet, will find out where this comes from (if I have it at all).

Although... you really mean logcat? This is the app log, so it would be good to find out which app is "complaining".

You are sure you do not mean kmesg (= kernel log)?

Very easy: Because the PAC team decided long time ago (when there was still CM10.2 around) to not follow any suggestion we kernel developers gave to establish a common naming convention for additional frameworks.

Most of the rom developers happily followed, but the PAC team was not even not constructive, they really were even trying to threaten us with everything like little gods (what a joke that time, I had a good laugh...). No chance to get in a team work mode with them.

So in short: No support for PAC with custom kernels. Never!!!

Search for a rom that has nice developers which are friendly and constructive, that is all I can recommend you.

Andi
[Galaxy S III Android Development] erezhazan1:
Hey,

How come in the post details the version Boeffla-Kernel 2.3 is also compatible for CM10.x versions (or CM10.2 to be more specific),

and however on the Boeffla-Kernel website it's specifically said that on the CM10.x versions it has gone to the end-of-development, and on the download

page I can't find any download links, except on the CM11 version, which gets me to the question, am I able to flash it on the CM10.2 version ?