[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.

zram tuning / tunable: you can configure that already now? What do you mean?

100 MHz support: Nope, does not make sense in my opinion.

Description in the V2 tool about the tweaks, or general for all options? Will not put the descriptions directly into the app as it gets messy then, also would need translations from many people for it. I will continue to explain stuff on the help section on the homepage. And if you are interested in the details, I can send you the changed parameters for VM etc. in a PM. Hope you are a Linux kernel expert, otherwise you will not find it useful.

Change your LMK settings, make sure you have enough zRam enabled.

If you cant get it working, change kernel to another one.

The 6.x kernel is experimental, unofficial, so it has no real priority for me (I am using Android 4.3 still as I do not go unofficial routes on my main S3).

Must be coincidence, have zero issues on my side with it.

Which governor?

There are no changes that would explain that. Or might it be the mali updates? I doubt...

No sorry, I am not looking for a S3 neo at all. Next devices is most likely a S5.

ZaneZam answered already, it is 90C for the first step to kick in.

I am convinced the 90c for the first step and only reducing it to 1200 is fine.

Reason is simple:

There are more steps to kick in, so nothing can go wrong. If the device is still heating up, the next step gets active.

So we can only win, but not lose.

Cannot confirm, working fine since I released latest version.

At least tell us which rom version you are using if you need support.

See above. 6.x kernel does not have my priority, on top I never saw these glitches as I do not play games and do not use browsers like Chrome.

But if I find some time one day, and see this for a first time, I will try to look into it. No promises though...

AFTER it gets available, of course it will be merged into the beta that comes next.

No, it will not damage the hardware. Worst you get is freezing, locking, or a hot phone. But depends on your specific hardware, try it out.

First: Wrong thread, you should post that in the CM Boeffla kernel thread.

Second: Yes, that is normal. Disabling the kernel logger on CM/Omnirom causes sporadic sound issues. I allowed it in the first NG pre-beta kernels to check if the issue is still around. After I got reports, the issue is still there, I removed this option again for good.

Boeffla-Kernel does not come with own LMK settings.

It uses the LMK settings that come with the installed firmware.

When you press Reset in Boeffla-Config, all the app does is to restore the "stock lmk settings" that have been initialized by the rom during startup.

So - it is completely independent of the kernel really.

Again a Omnirom user in the wrong thread??

You guys are using funny roms... "annunaki"... what the hell is that? Never heard that :)

But, it seems something in this rom or your specific device does not allow you to undervolt (anymore). Undervolting is something very at the edge of the knife. It can work well if all is fine, but it can go wrong. I personally tend to discourage people to use it.

But as stated in the OP... UV = no support by me here. The effects are unpredictable.

Just out of curiosity: When have you still be able to successfully undervolt? Which rom/Android/kernel version?

Cheers

Andi