yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] NickosD:
That's only happen at AK thread because he doesn't have a cm11 kernel and his kernel is universal. Here if you try it you'll probably end to bootloop. Also here there isn't any reason to do that because boeffla updates his cm11 / cm11s version while AK isn't.

Sent from my bacon!!!!!
[ONE Original Android Development] waterdaan:
When trying to turn off kernel samplepage merging in cm-performance settings, it turns itself on again. So I tried to make an init. d script to turn it off. And to run it on boot.

#!/system/bin/sh

#script to disable kernel samplepage merging

#and set permissions of /sys/kernel/mm/ksm/run to read only

echo "0" > /sys/kernel/mm/ksm/run

chmod 0444 /sys/kernel/mm/ksm/run

echo "DONE"

I've added

touch /data/local/tmp/initd_test.txt

echo "Hello Android" > /data/local/tmp/initd_test.txt

To see if it runs on boot , and it does, but I think it somehow gets overwritten or something.

Help appreciated

Or is there an easier way to turn ksm off

I'm running cm05Q
[ONE Original Android Development] jmtjr278:
Thanks.
[ONE Original Android Development] andip71:
Quite frankly this seems to be a phenomenum (bug?) with 05Q firmware. Yesterday people already reported since 05Q, switching this off is not sticky.

As init.d is executed before the rom starts, it is quite obvious the rom during start overwrites the setting again which you pipe into the sysfs.

There is a way however (if a change after the rom loaded remains sticky):

Use delayed init.d script loading technique.

Basically, there is a script variant of an init.d script that spawns an own process which waits for the rom to be loaded first, then waits for another few seconds, pipes the value to the sysfs and terminates.

JustArchi built such kind of scripts in the past, I need to dig it out during the day. But it should finally give you a solution then.

Andi
[ONE Original Android Development] Fenvarien:
Or [MENTION=5507140]waterdaan[/MENTION] could use an app like scriptmanager to run his script with root and a delayed execution time. https://play.google.com/store/apps/details?id=os.tools.scriptmanager
[ONE Original Android Development] :
this I got this from a guy on xda (or girl)

#!/system/bin/sh

# Disable SElinux on boot

/system/bin/setenforce 1

seems to work

ofcourse in proper init.d folder and propper permisions( same as other files thereb)
[ONE Original Android Development] andip71:
Kernel updates !!!

Hi folks,

yesterday I smelled new kernels, now they are here:

Updates for CM11s, CM11 and CM12 kernels.

Note: The cm11s kernel is a complete rebuild, based on latest cm11s source branch with some code cleanup. Although I do not expect bugs, I cannot promise.

In any case, this is now the cleanest way to stay as close as possible to 05Q stock.

CM11s - Version 2.3-beta2

17.02.2015

Complete new rebase from scratch on latest stable/cm-11.0 kernel source branch as of 16.02.15 (not shipping branch as before) - most clean code possible

CPU min frequency back to 300 from 268 MHz (268 MHz step removed again; was only for a test a while ago, and device wakes up better with 300 MHz) - manually check and adjust in Boeffla-Config after kernel flash

Hotplug control internal performance improvement

Toolchain changed to arm-eabi-4.7 toolchain (from arm-linux-androideabi-4.7)

Added some compiler flags for performance

Source repo commits cleanup

CM11 - Version 2.3-beta1

17.02.2015

CPU min frequency back to 300 from 268 MHz (268 MHz step removed again; was only for a test a while ago, and device wakes up better with 300 MHz) - manually check and adjust in Boeffla-Config after kernel flash

Hotplug control internal performance improvement

Toolchain changed to arm-eabi-4.7 toolchain (from arm-linux-androideabi-4.7)

Added some compiler flags for performance

CM12 - Version 3.0-beta11

17.02.2015

CPU min frequency back to 300 from 268 MHz (268 MHz step removed again; was only for a test a while ago, and device wakes up better with 300 MHz) - manually check and adjust in Boeffla-Config after kernel flash

Hotplug control internal performance improvement

Ramdisk updated to official nightly of 16.02.15

Added some compiler flags for performance

Enjoy

Andi
[ONE Original Android Development] molonad:
Hi, lord, please why it was necessary to remove 268 step, if someone has problem with that frequency, he can increase.. Iam typing this becouse I like that idea of lowered frequency and about longer wakes i Dont Care. I noticed that zzmove governors are wakeing slower than others, especially battery ones, is it true, or just my bad feeling?
[ONE Original Android Development] andip71:
Honest answer?

Because it is my kernel and I did not like the 268 anymore :)

When you read back the change logs, it was stated it is a test only.

And I had absolutely zero differency in battery consumption, on the other hand 300 MHz is better for device to wake up and also when playing mp3 in the background etc.

So there is not a single compelling reason for it.

So my view was to remove it.

(sorry for being a dictator here, but that's how it is :)

Andi
[ONE Original Android Development] molonad:
Ok if battery is as same as on 300 is everything ok ☺ so now better wakes and battery same, ok thanx for answer, Dont have any other questions and iam sorry about my Last one ☺
[ONE Original Android Development] andip71:
No problem, mate.

All questions allowed and valid :)

Andi
[ONE Original Android Development] molonad:
That Last sentence about dictator is funny ??

---------- Post added at 10:05 AM ---------- Previous post was at 10:03 AM ----------

And how about zzmove, do you think that wakes are slower than on interactive and etc? On girlfriend's s3 is that fact obvious, on oneplus i have small feeling too ☺
[ONE Original Android Development] Clark789:
I love those sympathetic rationale.... :) :) Clear and simple... :)

Btw: thanks a lot for the new beta!!!

Cheers

Clark
[ONE Original Android Development] andip71:
Yep. I think [MENTION=3279788]ZaneZam[/MENTION] is the best to answer.

But zzmoove cuts the cpu frequency during screen off. So until screen is on, the phone can only work with lower frequencies = slower wakeup.

Of course you can switch that feature off too.

Andi
[ONE Original Android Development] ZaneZam:
exactly my lord, zzmoove always had and still has strictly "sleep" settings (switchable of course), so there might be delays yes how long these delays are depends also on which setting is used. for example on "battery*" settings the sampling rate is much "lower" (before someone asks: value is in fact higher, its an delay-multiplier *g*) to save bat and that might increase that lag when coming out of suspend. for me with "optimized" setting there is almost no wakup lag or at least one i can take :) as stated couple of weeks (ehm or months? cant remember *g*) i consider to do a re-work of all the settings for opo but dont kill me if they will not be ready till tomorrow :)
[ONE Original Android Development] bloof:
You have two sampling rates? One for idle and one for screen on?

At least that's what i see in "tunable" settings.

and indeed your rates seem high, i have for "zzmove performance" 60000 and "current" at 100000... Those are pretty high, i would have expected 40000 to 50000 for a performance driven gov, maybe even 30000 for "insane" :)

Or am i reading this all wrong?
[ONE Original Android Development] Setting.Out:
Do I smell pie?.. I love when you bake up something new.. ;)
[ONE Original Android Development] DjDiabolik:
Hey boys... i have a little problems whit my OPO and latest CM11S 05Q installed by OTA.... i try to explain what's appened :)

My OPO It's rooted and i have the SuperSU 2.45 and when i turn on my OPO at start after 5 or 6 seconds the notify of "Default" profile has been loading appears.......... if i click on this notification the config app it's been started............ the screen of my OPO become completely black and after some seconds i can a trouble message on screen that says:

There is some problems for obtain a Root Access....... bla bla bla... SuperSu binaries has been reinstalled on next boot.... ecc. ecc. and you need to reinstall SuperSU from Playstore.

I can choose between YES or NO............ i ever choose NO and the config app closed...... i relaunch it and all back to normally and supersu working whitout problems.

I have this trouble only the first time i lauch the config app........... and i can't understand because ?? I have a root problems ?

From SuperSU i have already tryed to re-assign the root access to Config app but it's can't help me whit this trouble........... i have also tried to watch some setting from SuperSU app and the only strange value i find it's i have the SuperSU installed at system app and i can't understand how i obtain this and if it's this cause this trouble........
[ONE Original Android Development] ZaneZam:
Did u try to reflash supersu via recovery if not, do it. i guess u lost root after the update, pretty normal. ;)

---------- Post added at 02:07 PM ---------- Previous post was at 01:52 PM ----------

yes there are two but the idle one is only for screen on "idle times" there is only one (the normal "not idle" one will be overwritten for that) active at suspend

and yes u see that current 100000 mostly at idle times (for example u look at the values in the config app *g*) when the idle threholds were reached. if u stress

the system then u should have the value in sampling_rate which is accurate for performance as 60000 is the minimum possible rate for that governor (on opo platform),

all your expected values would be too low ;) the big difference between these two idle/full sampling rate values is my attempt to get both performance and bat saving

depending on the current situation.
[ONE Original Android Development] bloof:
Thanks!

While I have your attention, would you consider zzmove to be more or less battery friendly than intellimm, smartmax?

And is it better performance than intellimm, smartmax, interactive, intelliactive?
[ONE Original Android Development] ZaneZam:
Sry but honest answer: I don't know :) due to ongoing development (beside of 2 kernel flashes per day minimum *g*) and constant stability/settings testing I'm always using zzmoove and didn't compare yet. If u don't want to try out them self one by one maybe someone else which did that already can give u the answer. But as always it also depends on the personal usage pattern/system so u might get many results/opinions. that brings us at the end again to the suggestion: better do a test by yourself and find "your governor".
[ONE Original Android Development] DjDiabolik:
But have read all my reply or not ? I have already reflash the SuperSU from TWRP................. but i continue to have this trouble....................

*EDIT*

I'm also have another trouble whit SuperSU binary...... from terminal emulator "su -v" output it's "2:45:SUPERSU"...... but i have flashed the 2.46 zip... at this point or it's been updated only the APP or i have the app updated but not the binaries.........
[ONE Original Android Development] bloof:
:)

Just trying to write my thread. Can't test all governors and hotplugs either :) Just trying to give opinions on which governors are battery oriented and which are more performance.

Almost finished my thread if you want to have another look.
[ONE Original Android Development] ZaneZam:
well u wrote that u have installed "SuperSU 2.45" and i assumed only the app :) ok u are sure that u got a root problem ? it could also be just the warning that the kernel config isn't ready loaded yet. that is a precaution lord boeffla included to avoid problems after boot when users open the app "too fast" (yes i was one of them so blame me for that warning *gg*) before they are all applied and this led to crahses or changed/resetted values. so i would wait a minute or so after boot then u shouldn't get that message again. about the other problem "su -v" etc. never checked that but maybe this is normal, if there is an update to su binary needed supersu app should inform u about that, just follow that update with the "normal" method - that worked for me every time (but only after doing the cwm flash beforehand when starting from a non rooted system) actually i have to do that supersu binary update almost every day for the cm12 nightly installation, so for me its proven that it works :) but i never did a version comparison..
[ONE Original Android Development] ramblinman:
I've had to flash (in recovery) supersu on the past 3-4 nightly updates. There does seem to be be an issue with the last OTA though. I'm on Slim LP and it flashes fine. My girlfriend is stock rooted with Boeffla on the latest Cm OTA update and I'm having a problem getting Supersu to stick too. I haven't messed around to figure it out but I can verify that there's something going on and that the usual fixes aren't resolving it.

---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------

How much does touch boost help? I can't seem to notice a difference with it on or off during normal phone use. Is it battery efficient to leave it off or does it not matter either way.
[ONE Original Android Development] ZaneZam:
No issues for me just did it again ;) and I never faced such on cm11s stock only thing which comes to my mind is selinux, my experience is it really has to be set to moderate (permissive) to have 0 issues with root and root apps on cm12, fortunately lord boeffla has set it to this mode per default so we don't have to care.

I think touchboost does help to have a stutter free and fluid experience when using the phone. feeling no difference is again subjective, fact Is it ramps up the cpu scaling freq to the touch boost freq regardless if the system "needs" it at the moment when u touch the screen so yes disabling would save battery from a logical point of view, if it counts is another story and depends again ;)
[ONE Original Android Development] Chillz88:
zzmove has easily better performance than the rest for me. I didnt compare the battery lfe between the governors, because i loved the fluidity of zzmove that i started hating the rest. And batterywise i dont have complains and i bet it will be more improved when stable cm12 version come out. Hail Zzmove.:)
[ONE Original Android Development] Giocarro:
During the last three weeks I used zzmove performance and smartmax, and in my opinion the latter is a bit smoother than the former. I guess mileage could vary from app to app, though.
[ONE Original Android Development] kurtextrem:
I found IntelliMM is pretty solid as well, but ZZMove (Optimal) comes back to a lower frequency faster after the last touch / screen off, which results in better battery :)

Oh and by the way: https://forums.oneplus.net/threads/back-button-not-working-properly.266500/ Someone else with a similar issue? It wasn't from the beginning, it startet happening ... anywhen using 44S. It is still there with 05Q.

TL;DR: If the screen is off for a while and the screen is turned on again, the back button isn't working if an app is already open. (Menu and home, however, are working)
[ONE Original Android Development] DjDiabolik:
Yeah...... i usually opened the config app whit a tap on notification immediattely after a boot up my phone and i never have this problems before :)

Now from two days i have this trouble and don't know if it's normal or not.

At this point i don't know if it's problems whit Root...... on next boot i try to wait some seconds after notification has been appears....
[ONE Original Android Development] andip71:
Flash Supersu 2.46 once again in Recovery.

And open Boeffla-Config only after there is a notification in the notification bar indicating, the kernel loaded the configuration successfully.

If you do that before, start of Boeffla-Config is blocked with a message anyways.

Andi
[ONE Original Android Development] DjDiabolik:
mmmmmmmmmm..... i can retry to flash super 2.46 zip :) Otherwise in the SuperSu thread some other member has confirmed that..... the 2.46 it's the APP but the binaries it's not changed and it's 2:45:SUPERSU.

Otherwise i ever wait to open the boeffla-config........ usually i open the boeffla-config whit a TAP directly on notification when it's been appears and i never obtain this problems whit root access..... on next boot i try the notification of profile applied and i try to TAP on yes after about 1 minutes to see the result.
[ONE Original Android Development] MrMarkEdward:
I get this in notifications and if i tap on it it just goes away and I never have any problem with root. May try deleting everything that relates to the Config app. And start fresh.
[ONE Original Android Development] S1ay3r666:
[MENTION=947981]Lord Boeffla[/MENTION] do you like to add the new kcal control or is it not important for you?
[ONE Original Android Development] orangerot.:
[MENTION=3279788]ZaneZam[/MENTION] is there a documentation about the tunables in your governor? Most of them are self explaining , but for some I guess I'd need a documentation to mess with them ^^

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] DjDiabolik:
Exact.... i usually:

- Boot my Phone

- Wait this same notification

- Tap on This and the config-app it's been lauched right ?

At this point i obtain the problems whit root access.... at this point i need to close the config-app and re-launch...... very strange because before i install the OTA 05Q i never obtain this problems and it is as if my opo goes some seconds to give the root access with some latency.

I have try to restart my opo......... wait the notification and wait about 30 seconds to TAP on here and no problems but if i TAP on notification almost instantaneously i have the exact trouble i explain.

I have also tryed........ from setting i have try to reset the config-app.. it's no help me.

I haven't tryed to complete uninstall the config-app.. reboot my phone and reinstall from apk........
[ONE Original Android Development] MrMarkEdward:
Just because it doesnt open from a tap doesnt mean its not working. All you need to do is look at the supersu log and see if it was started. If it was in the logs then you good to go. Just open the config app from app drawer.

---------- Post added at 02:47 PM ---------- Previous post was at 02:39 PM ----------

Actually I just waited about 45 sec and tapped on notification and it opened the config app. Try enabling supersu at boot in the supersu app.
[ONE Original Android Development] bloof:
I promise last question on these topics [MENTION=947981]Lord Boeffla[/MENTION] and [MENTION=3279788]ZaneZam[/MENTION]:

The hotplugs in the kernel, namely zzmove native default, default and optimized:

1. what are their rankings for battery saving vs performance? zzmove native default seems the most aggressive, followed by default and then optimized, but that could be just an impression.

2. they all have 1 core on idle/suspend or just zzmove and optimized?

3. for zzmove "battery friendly" governors, would default or optimized add to the battery friendliness?

Thanks! And apologies for all these questions if they bother you, just trying to finish my thread... :)
[ONE Original Android Development] DjDiabolik:
mmmmmmmmmmmmm...... it's not a big problems but at beginning I thought I had a problems whit root permission on my OPO and i need some feedback :)

I ever tap on notification usually every day when i turn on my phone for check if it's present a new kernel release or new config app and after the notification it's been appears i immediately tap on notification but it's not a big problems if i need to wait :)

Otherwise now from Config app i have make a complete uninstall...... and i have re-install the config-app from apk download from site........ i have try to reboot my OPO and now seems to be much better.

For now i can only thanks you for all feedback you give to me :)

---------- Post added at 10:09 PM ---------- Previous post was at 09:58 PM ----------

Inside the settings i have also found this little bug on translation....

The exact it's Scansione...this it the screenshoot fronte mi opo :

[IMG="Little translation bug"]http://i.imgur.com/G0PF2oR.jpg[/IMG]
[ONE Original Android Development] andip71:
I don't use color calibration myself, so didn't follow.

Where is it, what is the functionality of the new kcal?

Andi
[ONE Original Android Development] DerRomtester:
Check my thread or source there is a great video about it.
[ONE Original Android Development] Ofthecats:
Anyone experiencing a return of audio stutter on Bluetooth with latest version?
[ONE Original Android Development] ZaneZam:
hi orangerot, u got an opo now? :)

for all the information u can go here: http://xdaforums.com/galaxy-s3/development/info-cpu-governor-zzmoove-t2326544

there is also an not so uptodate german version on hubo.in ;)

for the beta 6 preview features you would have to follow the links in the changelog on github : https://github.com/zanezam/cpufreq-governor-zzmoove/commit/75c431aeff8354f224e4c688faa1559ac463ab8a

but as stated they are WIP and might have bugs, but they will be finished in next version ;)

making a ranking is difficult cause the question is how much impact on battery hotplugging really has here and if its good to have cores offline to save energy (no core no energy consumption, but tasks needs longer to finish and other cores might have higher load/freq then)

but again from the logical point of view i will try to sort it:

1.)

"zzmoove native default" might be kind of both (depending on used zzmoove setting) and yes its the most aggressive one as it is controlled by the governor itself is optimized and actually

was always a part of all the zzmoove settings, so this fits together best ;)

"default" means here the default mpdecision stock hotplug behaving, i guess its the most balaced one

"optimized" also mpdecision logic and uses most of the time only one core so might be the most energy saving one (?)

2.)

yes just zmoove (strictly limit) and optimized (most of the time)

3.)

good question, but as mentioned in 1.) native hotplug completes all the zzmoove settings, therfore might be better (?)

all without any reliable tests made by me so more kind of specualtion :)
[ONE Original Android Development] Ofthecats:
Blisspop 2.16, Boeffla sabermod unofficial beta 11, max audio mod, camera next v11 mod, patch pie, n6 sounds, PA gapps 2.15, supersu 2.46,

Reverted xposed and I still have Google play music issues. Caught 3 logs

I forget which events occurred where, but did 3 separate logs for toggling Bluetooth and launching Google music.

Also limited log level to at least warn/error

Brb have to upload somewhere else cuz xda

Edit:

https://docs.google.com/file/d/0Bw_7kQg5zZe6VGN6WVRGNDRra2M/edit?usp=docslist_api

https://docs.google.com/file/d/0Bw_7kQg5zZe6YVlVeG5wTmFzVjQ/edit?usp=docslist_api

https://docs.google.com/file/d/0Bw_7kQg5zZe6MDB5WENtcU5XZEU/edit?usp=docslist_api

Please feel free to enlighten me on an easier way to post logcats. You would think xda would have an institution and efficient way to post ?
[ONE Original Android Development] waterdaan:
Thanks

Running the script on boot with smanager works
[ONE Original Android Development] MrPhilo:
Low CPU, High GPU

So, if I was to clock my CPU to like 1.5Gmhz and my GPU to 678mhz would that damage it in the long run due to the GPU speed? Or would it even matter? For example, GTA SA seens to work pretty well with this speed compared to a stock 2.5ghz and 587Mhz
[ONE Original Android Development] aswinrulez:
http://xdaforums.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080

http://xdaforums.com/showpost.php?p=58907845&postcount=10779

http://xdaforums.com/showpost.php?p=58907635&postcount=10776
[ONE Original Android Development] orangerot.:
Thanks, I'll check that out :) yes, I got mine like 3 months ago, wasn't able to stay with my S3. Lags and reboots everywhere. And then, 2 days after I got the opo it didn't even turn on. So the new phone came perfectly at the right time :D

Gesendet von meinem A0001 mit Tapatalk