[Galaxy S III Android Development] andip71:
Yes, but it is not really a kernel task. This is rather a rom task. And as there are modified versions of phone.apk around, I would suggest to use these.

Could you please test latest kernel version and report if you still have this issue? I did some more tweaks on it, maybe it resolved your issue now.

And making it configurable... would be a nice idea. Maybe I can look into that in the future after version 3.0 of the kernel and the app are both final.

Thanks, always nice to read such positive comments as well :)

Yes, I have zRam enabled with 300 MB. Not that I personally need it, I am not the kind of user having many apps open at the same time. But it does not hurt, so I have it switched on.

How I debloat my rom:

Well, honestly I made a CWM flashable script which I just run after having installed a new rom. I am a bit reluctant to share this, as it is really deleting everything I do not need. This includes also apps like GMail, so most of you would not be able to use it.

But you can debloat also with tools like TitaniumBackup, System tuner or there are even some specialist debloat apps available doing that job.

Honestly, I did never experience this. And during testing my app I frequently do that.

Also in theory, it does not make lots of sense as long as the profiles are not completely different (which could justify performance differences reducing smoothness).

Can you elaborate a bit more on that please? I fear I do not understand well enough what you want to achieve, sorry.

Cool, that would mean the tweaks I mentioned above might have been successful.

The thing is: Google Play is a biiiiiiiiiiiiiig system with apparently a CDN (content delivery network) behind, which need synchronisation around the world. Also Google is doing some automated checks on each uploaded apk.

So in short, when I push an app to Google Play, it typically takes 1-3 hours before it is available. Also, it is not available at the same time around the globe due to the synchronisation. Google, to be fair, even tells me every time I push an app, it can take several hours.

So, all we can do is wait for it to show up :)

Finally I changed (and hopefully improved) the root gaining routines during startup. So in my tests, I now get the Supersu window after the restart again when I upgraded the app. This avoids any issues in future, hopefully.

Will come in the next version.

See one post above, I think removing rights for Boeffla-Config in SuperSu and regranting it by opening Boeffla-Config will solve your issue as well.

Yep, min cpu frequency will be in the next update.

If you have paypal, you can also get the donation version from AndroidPIT. www.androidpit.com

Thanks buddy, much appreciated.

To 1) not the 0.6a version as Yank already explained, it makes not difference for a S3 device.

2) This is maybe something I can try with one of the next betas. Although I am a bit concerned about it as on the modem side at least the MG4 seems to be very special. If also in the ramfs, we would bring many users in big trouble.

Hm, I personally think it runs a little bit smoother. But worth upgrading? Not really I would say.

I still cannot comment on it. Never used neat rom. Is there any neat rom user out who has the same issue (or can confirm it runs for him)?

I still do not understand why especially neat does not work, but all other roms apparently do.

Also I cannot think of any modification in the kernel that could cause this... weird.

If that is the case, then it is indeed a bug.

If you could mail me all your bc.log files from your boeffla-kernel-data folder, it would probably help already. Also please let me know then what the name of the disappearing profile was.

Good, so finally you have choosen to take a good rom. Appreciated :)

Well, all detail parameters a governor offers to be configured. It is many options (e.g. 31 for zzmoove, a bit less for pegasusq and lulzactiveq), but it is really up to experts that want to tune the governor even more than by using the predefined governor profiles. I will attach a screenshot to give you some idea...

No problem. It is only half your problem, as it shows to me it was not intuitive enough. So I added a test on the lefthand side of the button in the next update, to explain a bit more about it.

Yes, indeed. Have not yet uploaded stock kernels for emf6 and emg4. Will do that during the course of today.

Andi