yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] metalgearhathaway:
Yeah, some quick tests show issues with graphics, stutter and lag, won't be testing this further.

Ondemand is definitely my bag, its strong, dependable and gets the job done! No other governor offers the all round performance and stability, some have better singular credentials, but only ondemand has the full package!

I won't be trying anything else out on the S3, not on Boeffla at least, I think my V4 nails it! :)
[Galaxy S III Android Development] aliw32619:
Cool :sly:
[Galaxy S III Android Development] IceFresh:
There is a setting in Boeffla app either on loudness and led..

Wysłane z mojego GT-I9300
[Galaxy S III Android Development] andip71:
Guys, finally I am back again. Sorry, took some days longer than expected.

I try to catch up on the most important posts now (or the ones where I have answers straight away on).

If you feel I missed to answer a specific post, please point me to it again.

Yes it does. If you are running a NG kernel, only a NG kernel update will be shown and loaded.

And vice versa.

Most probably yes. This is on the todo list to investigate.

Difference in the ramdisks... well, as this is constantly changing nobody can give a definitive answer I think. Unpack the two ramdisks and diff them, that is also how I would do it as I do not have sources for it.

But be aware, the CM11 Boeffla kernel e.g. does not work on Omnirom based roms.

The other way round (Omnirom kernel on CM11 based roms) does work, but with minor glitches (which some probably do not even notice, file systems are apparently mounted a bit different etc.)

This has been answered almost trillion times.

Whether this is shown or not is always a combination of what age your rom is + what age the kernel is.

2.3 kernel supports the older roms (approx before 08.07.), 2.3a kernel the newer ones.

2.4betas of course the newer ones only.

Because of backward compatibility. Some people still like to use them. So why not keeping them in, they do not harm if not used.

Because I do not see a reason to have it enabled and face potential side effects. So it is disabled in all my Samsung source based kernels.

Yes, this was always like that in my kernel and is by intention.

If you manually lock the phone to e.g. put it into the pocket, I want this touch-wake functionality to be disabled. Makes perfect sense to me.

I have to look into that. Got it reported already a while ago but could not replicate that time.

No, for CM10.x there are separate kernels available by me. But they are not maintained anymore, CM10.x is dead.

Anyways not a kernel issue. ART as well as Dalvik is above the kernel layer.

But to complete it: I tried ART, no issues. But also did not see any improvments.

Different initramfs, and if you do not use the NG kernels, different code base provided. So, not really explainable, but also not a big surprise (assuming paranoid is based on CM11 source base, which I do not know).

Unfortunately nothing I can help with now. I do not own a Gear, so cannot test it at all. Sorry.

Bluetooth however seems to be a consistent issue in the CM/Omni world.

I am doing fine (again). Sorry, was planning to be back earlier, but underestimated the move somehow.

Now slowly gearing up again.

Lucky you. Just be warned, it can break with every new version of PAC due to the mentioned reasons. You never know what they introduce...

Andi
[Galaxy S III Android Development] andip71:
NG beta2 soon...

Hi all,

just to let you know, I will soon make an update available for you on the NG kernels that fixes the two known issues:

- mobile traffic indicators not working

- auditd crashing and restarting all the time (flooding logcat)

I am doing some final testing today and maybe tomorrow you can have it...

Andi
[Galaxy S III Android Development] gtsfreak:
[MENTION=947981]Lord Boeffla[/MENTION] please fix battery charging animation too and low speaker volume :D big fan of your omni kernel
[Galaxy S III Android Development] andip71:
If you have read my long posting today carefully, you should have noticed:

- battery charging animation is fixed already long time ago!!! You just have to select the correct kernel version which fits your rom.

- low speaker volume is not something I am aware of.

Andi
[Galaxy S III Android Development] d1rekt0r:
Archi and dhiru already started implementing r4 Mali drivers , maybe you can look into it?

Personally I didn't like them much , but according to other people they are better than old ones.
[Galaxy S III Android Development] andip71:
What do you mean by "Personally I didn't like them much"...?

Is it not working, not stable, ...? Please elaborate a bit.

Thanks

Andi
[Galaxy S III Android Development] gtsfreak:
I'm using dirty unicorns ROM 7.8 what kernel should i flash for battery animation as I'm using omni kernel ng 2.4 one :D:confused:
[Galaxy S III Android Development] d1rekt0r:
Well , they do score much higher on antutu ( overal fps higher by 2-3 ), but ui is more stuttery , when its smooth its really smooth , but stuttering occurs more frequently.

Maybe it needs more work or its just me , but i installed some games for sake of testing and less performance is obvious.

Archi is experimenting with it , but his tests are based on 1600mhz too idk how reliable results are.

I say you look into it and see.
[Galaxy S III Android Development] abhibnl:
Well the biggest news you might have missed is that we finally have working HWC! And that uses malo r4p0 drivers. Archi is already working to merge them. Also there's some news of google releasing 3.10 linux kernel sourcea for chipseta including exynos 4.

Sent from Galaxy S3 Powered by Temasek + Boeffla
[Galaxy S III Android Development] andip71:
Well, if it does not work with 2.4 NG kernel, then try the 2.3 stable one.

It should work either with

2.3a stable / 2.4-beta1 NG / 2.4-beta1

- or -

2.3 stable

Yes, when there is the right time, I will look into it.

OK, now I have to out myself as a "noob", hahaha.

But what do you mean by HWC??? And do not tell me it is about gaming, hehe :)

Andi
[Galaxy S III Android Development] d1rekt0r:
Apparently Hardware composer is working on nameless rom , fixed by dhiru scot and javi ? It was supposed to bring true GPU rendering of UI and make everything smooth as silk, but as i told you above , its kind of a let down imho.
[Galaxy S III Android Development] Maarren:
I always assumed it was like in this link. http://pierrchen.blogspot.nl/2014/02/android-graphic-composition-hardware.html?m=1 case1 is what I think we always had in some form. Case 2 is now also possible with hardware composer, resulting in maybe slightly better performance and possibly slightly better battery. But then again I'm a noob with this stuff. But it would explain why there are no very large improvements. I would really like if someone with more knowledge could explain things better.
[Galaxy S III Android Development] Moster2:
Yes, you are right. A working hwcomposer is not going to magically make the smartphone feel like a nexus 5.

It basically just allows UI rendering directly via the hardware and not going via opengl (software).
[Galaxy S III Android Development] d1rekt0r:
Well from what i understand

CPU in all aosp roms atm is doing all the job including rendering ? This causes more battery drain too.

But with Hardware composer GPU is rendering lots of stuff and that means smoother graphics and better performance because CPU is under less stress?

But im juat as noob as you are i could be wrong.
[MENTION=4898097]arter97[/MENTION] and [MENTION=5161352]JustArchi[/MENTION] are proffesional in this department , maybe they care to explain better :D
[Galaxy S III Android Development] abhibnl:
Haha. No no bro! It's the good ol'. Hardware composer. Working now on nameleas rom

Sent from Galaxy S3 Powered by Temasek + Boeffla
[Galaxy S III Android Development] Maarren:
But then the whole deal is to actually use the gpu less? (Not rendering screen layers with opengl/gpu, when they are not updated)? And therefore keeping more resources available and saving battery? Quite confusing stuff! By the way, sorry for offtopic I will stop.
[Galaxy S III Android Development] VictorLapin:
Nothing to be sorry about, maybe I've just tuned my i9300 to be "too deep sleep" :D

I just need to compare slim kernel settings and my boeffla profile to find the differences.
[Galaxy S III Android Development] Moster2:
Ye, kind of. The hwcomposer helps to offload overlay composition to some dedicated hardware (could be in the gpu or anywhere else, depends on hardware manufacturer).

The usual way would be to go via the opengl libraries, then gpu driver, etc. With the hwcomposer the overlays can be directly composed in hardware. This helps to decrease general load on the GPU and also CPU (in case it needs to calculate some opengl stuff, etc.)
[Galaxy S III Android Development] andip71:
Sure. Or just create a new profile with default settings and load it for a test.

Andi
[Galaxy S III Android Development] gtsfreak:
I will try 2.3a I hope it works:thumbup:
[Galaxy S III Android Development] andip71:
Likely not. If it was not working with 2.4-beta1, you need to try 2.3 without a!

Andi
[Galaxy S III Android Development] AssassinGEO:
HWcomposer should actually make the device smoother,as it makes sure that everything is running on steady 60fps throughout all operations.
[Galaxy S III Android Development] IceFresh:
Is kernel anyway related to Bluetooth headset loudness? I mean is it possible to make it louder via Boeffla config app?

Wysłane z mojego GT-I9300
[Galaxy S III Android Development] andip71:
No, this is not kernel controlled.

It is a purely digital signal transfer, so I can't influence it by the kernel as it is possible with the analog path (Boeffla sound).

Andi
[Galaxy S III Android Development] IceFresh:
Thanks for fast answer. I just thought that I'd there are some sound loudness settings in app this may be controlled too:)

Wysłane z mojego GT-I9300
[Galaxy S III Android Development] gtsfreak:
I tried both 2.3a and 2.4 omni ng 1 no battery animation still :confused:
[Galaxy S III Android Development] andip71:
Use 2.3 without a, as written above. Please.
[Galaxy S III Android Development] Ayaz ansari:
I flash kernel on c ROM but where find my ext SD card
[Galaxy S III Android Development] andip71:
Hopefully in your external sd card slot of your s3?? :)

Now seriously... what exactly is the issue now? With this small explanation, nobody can give you help.

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

I have already an idea on that... just to go sure: which rom are you using? Omnirom as it is stated in your signature?

Thanks

Andi
[Galaxy S III Android Development] Choristav:
Welcome back andi!

i9300 is getting some real love thanks to nameless rom, check them out sometime.
[Galaxy S III Android Development] leleobhz:
20140803 Omni now.

I discussed this in another thread, I just can't understand why the hell does Omni mount sdcard in a non-standard path and uses fuse to map the card to right place. Fuse overload kernel, remove control from kernel to io optimizations, since fuse runs in a space that kernel does not control and we'll, except for ntfs (ugliest thing in earth), it's a mess.

And a creative solution I saw in a Rom (omni for p1ln in my signature) was the LVM usage, surely more efficient (far efficient) than fuse and also solve free space issues keeping control into kernel.

Anyways, the trouble - I think - is the path omnirom is using to mount the SD block device, as I saw, non-standard standard place for Rom's.

---------- Post added at 04:55 AM ---------- Previous post was at 04:52 AM ----------

Ref.: http://xdaforums.com/showthread.php?p=54614311

Mapping manually things using adb shell worked like a glove.
[Galaxy S III Android Development] andip71:
Well, I did already a change for the next beta kernel to also properly unmount in Omnirom (and CM11).

Just stay tuned for the next kernel version :)

Andi
[Galaxy S III Android Development] gtsfreak:
[MENTION=1045701]lordbo[/MENTION]effla thanks will try your next omni ng kernel soon hope it fixes all my bugs :p:D
[Galaxy S III Android Development] andip71:
What all bugs do you think you have?

I know about battery charging animation, which is not a bug but caused by a change of the CM/Omni team a while ago (not backward and forward compatible).

What else?

Andi
[Galaxy S III Android Development] gtsfreak:
Dropping of Mobile signals slow charging maybe that's not kernel issue and some battery life improvement :p:thumbup:
[Galaxy S III Android Development] andip71:
Dropping of mobile signal is purely modem, not kernel related

Slow charging - cable issue, charger issue, improper charging configuration in the kernel...

All issues will not change for you with next beta as I am not working on this, as these problems do not occur for 99% of the rest.

Andi
[Galaxy S III Android Development] gtsfreak:
[MENTION=947981]Lord Boeffla[/MENTION] okay no problem bro :D still love your work just hate battery animation issue:thumbup:
[Galaxy S III Android Development] andip71:
Have you ever tried once stable 2.3 without a, and then the one with a?

One of them MUST work (depending on how old your rom is). If not, something is wrong in the rom.

Andi
[Galaxy S III Android Development] Lycidias:
One Question: what means NG?

i want to flash your kernel on my brothers new S3 witch archidroid v2.

thank you :)

by the way: the old S3 times were awesome with your kernel ;)
[Galaxy S III Android Development] kadopt:
New generation. It uses Samsung sources instead of older ones.

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] szotaa:
Please, point me where is it said that nameless ROM has HWC fixed, I couldnt find any info about it.
[Galaxy S III Android Development] FDisk80:
http://xdaforums.com/showpost.php?p=54541620&postcount=2
[Galaxy S III Android Development] szotaa:
AFAIK hardware composer doesn't equal Mali driver. Graphics drivers are kernel level modules while hardware composer is rom level module which uses GPU drivers to compose user interface.
[Galaxy S III Android Development] Moster2:
https://github.com/NamelessRom/android_hardware_samsung_slsi_exynos4/commits/android-4.4

Improved gralloc is also mentioned in the features
[Galaxy S III Android Development] d1rekt0r:
According to gerrit that is not merged yet ?

https://gerrit.nameless-rom.org/#/c/9064/
[Galaxy S III Android Development] Moster2:
That's something else.

Hwcomposer development is not finished yet, but its working already
[Galaxy S III Android Development] andip71:
Beta2

Hi all,

small maintenance release, especially for the NG kernel series (both CM and Omnirom) to fix some hopefully last issues. On top also a small update on the normal series (both CM and Omnirom) to stay in sync.

Version 2.4-beta2

05.08.2014

NG kernels only

Fix network traffic indicators for mobile data not showing up (only for roms showing the indicators)

Fix auditd daemon crashing and restarting over and over (and flooding logcat)

All kernels

Fix external SD card not properly unmounted when activating UMS mode in Boeffla-Config V2

Reworked and simplified debug info file creation

Omnirom kernels only

Initramfs updated to version of 03.08.14

Enjoy

Andi
[Galaxy S III Android Development] you_man:
With the return of Lord.

I do not even know if I should be updated on b1---->b2?

Uptime 100 hours, there were no problems.
[Galaxy S III Android Development] andip71:
Great news, very impressive uptime.

Believe it or not... due to my move, my current uptime is: 331:52 hours !!! Not a single problem during that time.

But you can see in the change log what has been changed. If none of that is relevant to you, just stay on beta1 (I know you cannot resist to flash later anyways :p)

Andi
[Galaxy S III Android Development] szunyi77:
Hello lately there is a problem to re-start after the governor returns to the default setting. I've deleted the settings, I use the timer 20sec. Not a mistake, just a little nervous. What do I try it? I upgraded to the latest NG B2 and thus error ..

Sent from my Galaxy SIII is a real iPhone killer! ;)
[Galaxy S III Android Development] andip71:
Which rom are you using?

Can you make sure you are not overwriting the governor in the CM/Omnirom settings?

Are you sure you have no other app changing the governor?

Are you sure you have no init.d script changing the governor?

99,9999999999% this is something like that. Nothing changed in the kernel with regards to this functionality.

Andi
[Galaxy S III Android Development] you_man:
Great uptime)

You know what hurt, already flash the new beta :D:D:D

BTW, here is the result battery life of ru community. http://4pda.ru/forum/index.php?s=&showtopic=537491&view=findpost&p=32892368

I have a result like this guy + - 10-15 minutes of screen time
[Galaxy S III Android Development] szunyi77:
Thanks for the quick response.

I use the L-rom Droid, Omni kernel.

Does the rom Kernel Tweaker, but it did not activate anything.

Alone is only allowed to Setrenice init.d script ..

I check the init.d script you can and try to re-install on the boeffla config V2 2.1.45 application.

One more question:

Which scheduler recommended average use, most of which are used in general?

CFQ or SIO may ZEN?
[Galaxy S III Android Development] Almin94:
HWC

How to enable HWC? HWC is included in kernels or we must have ROM which support it?
[Galaxy S III Android Development] Scarface1991:
I have to say the NamelessRom sounds really tempting. Gonna try it out. However I read that no custom Kernel works with the Rom as of now because of the new GPU Driver. Would be great if you could add support for the Rom [MENTION=947981]Lord Boeffla[/MENTION]

Gonna try it out tonight and see for myself. What I know already is that dhiru1602 is a very skilled developer who fixed a lot of camera, Audio Stuffs and other stuff for our I9300.
[Galaxy S III Android Development] abhibnl:
Archikernel with Mali r4p0 support should be up anytime! [emoji16][emoji16]

Also Andi, could you try to make a experimental build with mali r4p0 support?

Sent from Galaxy S3 Powered by Temasek + Boeffla
[Galaxy S III Android Development] andip71:
I currently think I will wait until this probably gets officially adopted by the CM and Omnirom teams...

Not yet sure.

Andi
[Galaxy S III Android Development] Scarface1991:
So HorstiG said on the NamelessROM Thread that the NG Version works without problems. How's that? Does the Boeffla kernel replace the new GPU Drivers with old ones thus allowing the ROM to boot up?
[Galaxy S III Android Development] abhibnl:
Well i guess it'll take some time then but i'm sure i can wait till then.

Really? Haven't tried bro! Will try asap!

Sent from Galaxy S3 Powered by Temasek + Boeffla
[Galaxy S III Android Development] boyheadkick:
I tried it yesterday with omni ng and normal versions, rom didn't boot

-aL

tapatalked from my super duper palm top computer
[Galaxy S III Android Development] Scarface1991:
Did you try it with the newest Beta? Although there are no Mali changes maybe I'll work for some reason. However I will try it in the next hour and report here.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] boyheadkick:
i always use the latest beta
[Galaxy S III Android Development] Almin94:
NG lagg

LordBoeffla@

With NG kernels I have stutter while scrolling pages, playing games and everything other I do on my phone. I haven't any problems when I don't use NG kernel. With non-NG boeffla kernels all things work very smooth without stutter. Is there way to resolve this? Thanks.
[Galaxy S III Android Development] boyheadkick:
even with the same profile?have you tried changing governors?
[Galaxy S III Android Development] nicola1989:
The nameless Rom doesn't boot if the kernel don't have the new driver. So when Lord Boeffla will merge we can try. By the way welcome back Lord
[Galaxy S III Android Development] astankov:
I have the same problem...
[Galaxy S III Android Development] khanmein:
omni NG so far ok
[Galaxy S III Android Development] hisee:
What is ng version?
[Galaxy S III Android Development] andip71:
Thanks, interesting feedback.

About 85% of the users report NG kernel to be snappier and smoother.

About 10% of the users report it is the same perceived performance than with normal kernel.

The rest of 5% claim NG kernel is laggier.

Personally, I count myself to the 10% not feeling a significant difference.

So following the good old IT 80/20 rule, there is nothing I can and will do currently. The majority of users is happy with NG. So I guess your solution would be to go back to the normal kernel, something or somewhat in your phone does not like the NG kernel it seems (maybe a specific app combination, usage pattern etc...)

Thanks

Andi
[Galaxy S III Android Development] andip71:
Yes, just to confirm: Mali drivers are the same in all my kernels, regardless if non-NG or NG.

Andi
[Galaxy S III Android Development] andip71:
Second line in the change log of it:

http://boeffla.df-kunde.de/sgs3/boeffla-kernel-cm-ng/cm11.0/changelog.htm

Andi
[Galaxy S III Android Development] Choristav:
If you want my 2 cents, I'd say the performance difference isn't placebo, but is mainly dependent on one's configuration. Maybe it does memory allocation better, but only those who play very demanding games notice such. Or maybe it causes instability with the same undervolting preset, so people consider it laggier due to unsufficient power and they end up complaining. A fresh reset for all values would be a good start to judge such an experimental release.

Anyhow, goodjob.
[Galaxy S III Android Development] XDAMaxe:
Hi Andi,

just saw the changelog of V1.4 of Archis kernel and Archi wrote that

'ArchiKernel has been rebased on top of latest SEA2 kernel sources from Samsung. # This means that it includes everything what Samsung included'

I am nearly sure that you've already read that ;) ... despite of the V4 mali drivers: is SEA2 an update of NG (based on samsung update 13 sources) ? should one call it NG+ ? worth to integrate/mention it for your kernel ?

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

my NG kernel is - since the very first version - based on Update13 + SEA2 already.

See commit:

https://github.com/andip71/boeffla-kernel-cm-s3-ng/commit/a12e4c46dd7db84473fe1ae73d06201ab4dc0f33

I built this in already at February 14th, the SEA2 update is not really new :)

Andi
[Galaxy S III Android Development] XDAMaxe:
woah, perrrrfect.

ANDI, I LOVE YOU ;)
[Galaxy S III Android Development] lchiocca:
<Mode type="sarcasm">

That is a very good question, and thank god I'm the only one to know the answer.

Lord Boeffla is actually an offspring of Q from star trek. He is able to play god like a kid plays with his toys. When he builds his kernels, he quickly travels to the future to check how the enterprise is configured (yes, the enterprise runs android W!). He found that, to be able to backport some kernel features from android W to kitkat, he needed to make sure our dimension was ready to accept it. So, with his mighty powers, he made sure that 'star trek next generation' was going to happen. He was so proud of it that he even called the backported kernel 'next generation'. Hence, the next generation kernel was born.

But please, don't tell anyone! It's a secret!

</Mode>
[Galaxy S III Android Development] boyheadkick:
Man that cracked me up! Good one.

-aL

tapatalked from my super duper palm top computer
[Galaxy S III Android Development] ScratMan38:
[JOKE MODE]

And you're late, now, as Samsung already released sources for update 14... :D

[/JOKE MODE]
[Galaxy S III Android Development] andip71:
Well, there is no real rush to put update 14 in. It is only changing 14 code lines within 2 files compared to what we have currently. So it is literally nothing.

Of course I will anyway lift to update14 for the next betas...

Andi