yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] YUIGNOREMYMEMSETLINKS ;p
[Samsung Galaxy Nexus] thagringo:
a few more things to play with in case you are interested :

- fuse-linker-plugin - this one is mainly to improve accuracy and quality of the code and can be combined either with the ld linker or the before mentioned gold linker.

- linker flags : -Wl,--hash-style=gnu -Wl,-O1 -Wl,--as-needed - final objects should be more accurate & provide quicker lookup. Probably final binary size will be bigger too. Make sure you dont overwrite the ones provided by the linux kernel build kit and just append these.

- -ftree-vectorize : this one is included in -O3 since 4.7 iirc and should finally work as intended. In case it doesnt work bad things are going to happen and you will notice inmediatillly. Same for -ftracer or -funroll-*-loops

- a few more : -ftree-loop-distribution, -fivopts and -ftree-loop-vectorize ( in case you dont use -ftree-vectorize)

- kde & qt rely heavily rely on these 2 since gcc 4.1 : -fvisibility=hidden -fvisibility-inlines-hidden. Not sure if this makes sense for c source, its more for c++ code IIRC.

how about extra debug flags or hardening flags ?

i mean, how is android building their stuff, are they actually using -fstack-protector for example ?

just a few ideas.

cheers guys
[Samsung Galaxy Nexus] büscher:
Like 10 pages back you discussed the mpo interactive settings.

I had to try both, Nephilims and mpo's default settings with antutu. ran antutu 3 times each with both settings and the differences are always this huge...

With Neph's settings:

With mpo's setings:

edit: Do these governor settings really have such a big influence on the overall speed of the phone (gpu is faster, storage i/o, ram operations...)??

edit 2: and these are the original settings of dirty_V

[MENTION=2853378]Nephilim[/MENTION]: Are you focusing on battery life or performance with your settings? (the only thing I did not apply from your settings is fiops, I use sioplus instead)

all tested with Dirty_V 4 SR
[Samsung Galaxy Nexus] bsmitty83:
Mine is 85 and it sticks
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=3317173]büscher[/MENTION] Yeah, it seems Mpokang's settings for Interactive are very good.

I set it on Franco kernel. On default settings i get 12500 points, on Mpokang settings got 13000 points.
[Samsung Galaxy Nexus] büscher:
[MENTION=4608636]bsmitty83[/MENTION]

On your devhost you have two versions of Dirty_V SR Version 4:

DirtyV4-SR-Linaro.zip and DirtyV-SR4-Linaro.zip

I think you wanted to get rid of the status 7 by making a new zip?

But as I can see these two kernels are not the same? In the DirtyV4-SR-Linaro.zip has less options to configure Interactive governor than the DirtyV-SR4-Linaro.zip.

I know this is an old version but still the "DirtyV-SR4-Linaro.zip" is the smoothest for me even If I have to flash an old cwm recovery to install it ;)
[Samsung Galaxy Nexus] Nemed:
I also tried to change it with terminal emulator and it says 'permission denied'

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] bsmitty83:
Root ? Need to be root "su" to change it I believe
[Samsung Galaxy Nexus] sajty:
Same behaviour as described.I set 85,apply and its immediately back to 0.
[Samsung Galaxy Nexus] Nemed:
Same result, i even tried to change permissions and owner with solid explorer, it doesn't change…it seems to be read only. I remember i had the same problem with 'sampling_rate' on conservative...
[Samsung Galaxy Nexus] osm0sis:
Or you could just remove the bad "dump_image" line from the updater-script and stay on the newer CWM. ;)

Two possibilities:

1) This is your underlying ramdisks not supporting target_loads so the correct permissions aren't being set to the sysfs file on boot to allow you to change it without root.

2) You are on the older version of Dirty/Smitty that has the 3.4 interactive, which uses a string to dictate different loads values at different frequencies. Someone said Trickster and some other apps don't show this correctly and it instead displays as a 0.

As I said, they may seem fast, but they abuse the governor and should result in worse battery life due to constant frequency-load oscillation, so I wouldn't exactly call them "good". :p :)
[Samsung Galaxy Nexus] sajty:
I am on latest dirty + Carbon.
[Samsung Galaxy Nexus] büscher:
sometimes the solution is so easy ... :silly:
[Samsung Galaxy Nexus] osm0sis:
From a command prompt then:

su;
ls -al /sys/devices/system/cpu/cpufreq/interactive/target_loads;
cat /sys/devices/system/cpu/cpufreq/interactive/target_loads;
chmod 666 /sys/devices/system/cpu/cpufreq/interactive/target_loads;
echo 85 > /sys/devices/system/cpu/cpufreq/interactive/target_loads;
cat /sys/devices/system/cpu/cpufreq/interactive/target_loads;

And paste me all the output.
[Samsung Galaxy Nexus] Nemed:
1 - I don't know what that means lol

2 - I'm on the latest dirtyV, i opened that file and yeah there's a string '70 92000:80 1200000:99' but as i said i'm unable to change it. (maybe because of point 1? xD)
[Samsung Galaxy Nexus] GilGameshn1:
Hell yeah

Sent From My Nexus Prime
[Samsung Galaxy Nexus] sajty:
Will install terminal emulator and post result.
[Samsung Galaxy Nexus] Nemed:
Well, it worked, thanks mate!
[Samsung Galaxy Nexus] sajty:
Confirming,works.Thanks man.
[Samsung Galaxy Nexus] pianistaPL:
So... go_high_speed load set to 75 will be good compromise? :)
[Samsung Galaxy Nexus] osm0sis:
Interesting. Didn't realize The latest was using that even newer interactive again. Yes option 1 is why though haha.

Bingo, option 1 it is. :)

Yes please! I still want to see that output. :good:

Nope. go_hispeed_load cannot be lower than target_loads or you're doing it wrong. Go back and read what I wrote to Nephilim about the gap between those values and the margin above and how they affect ramping.
[Samsung Galaxy Nexus] pianistaPL:
I have target_loads set to 75 too. That's wrong too?
[Samsung Galaxy Nexus] Nemed:
[MENTION=4544860]osm0sis[/MENTION] so, let me understand… if i use a string like: "40 230000:45 350000:50 525000:60 700000:75 920000:90 1200000:99 1350000:100" this will set precise ranges? Am i doing it right? xD
[Samsung Galaxy Nexus] Sik-1:
Yes target is supposed to b lower than go_hispeed
[Samsung Galaxy Nexus] sajty:
Is the log still valuable,when its already set to 85?Even Trickster is now showing 85.
[Samsung Galaxy Nexus] fracama87:
You've done this test with last version of dirty-v sr kernel? And you have charged just interactive settings? Anyway could you share mpokang settings for interactive? Thanks :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
I don't have much experience with this newest interactive but yeah that looks right! :)

Edit: You would never ever want target_loads as low as 40 though. That'll ramp up your CPU too much to keep the load low. 75 is honestly the lowest I'd ever conceive of, then go_hispeed_load around 10-15 points above that.

Reboot and see if you can recreate the issue. It should reoccur on every boot because the ramdisk isn't setting the correct perms. So I'd definitely like the output to demonstrate that for sure. (This is also why some devs prefer to include their own ramdisk).

Nope. mpok's are garbage. Don't use them. Read back to my posts yesterday about all this.
[Samsung Galaxy Nexus] pianistaPL:
So finally:

go_highspeed 78

target 75

Good? :)
[Samsung Galaxy Nexus] Nemed:
Ok, thank you. I'm gonna make some tests.

But there's a problem: values don't stick after a reboot (even though i'm using an init.d script) :(
[Samsung Galaxy Nexus] osm0sis:
Nope. Too close. Go back and read those posts. You're going to want at least 10-20 points between them, so go_hispeed_load 85 to 95.

Add the chmod command from my other post to the init.d script before you try to set it. Should work.
[Samsung Galaxy Nexus] fracama87:
I know! Absolutely!

Maybe I wrote bad (sometimes it happens to me with English). I don't want use mpokang kernel.

I've understood they have used interactive settings from mpokang ON dirty-v so just the settings! and if they can share the settings I would try that experiments... I don't think that would be so bad....

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] sajty:
Hm, you are right again. Reseted to 0 after reboot...

Sent from my GN
[Samsung Galaxy Nexus] osm0sis:
Nah I specifically meant the interactive settings as well. They're garbage. Please go back and read those posts I told you to. :)

Yup yup. Output from those commands please. ;)
[Samsung Galaxy Nexus] aosp:
Check the logs right after booting up or use SuperSu logging to make sure no apps are making changes on bootcompleted
[Samsung Galaxy Nexus] osm0sis:
Most ramdisks don't have target_loads perms in either init.rc or init.cm.rc with the other interactive tunables. Definite downside to using AnyKernel is it's easy for users to get stuck with a poor ramdisk that doesn't support the kernel's features.
[Samsung Galaxy Nexus] Rushead:
Please go back and read this...

http://xdaforums.com/showthread.php?p=50102720

...and this...

http://xdaforums.com/showthread.php?p=50103095

Sent from a flashead cracker.
[Samsung Galaxy Nexus] Nemed:
Doesn't work…

Sorry if i'm bugging you anyways lol
[Samsung Galaxy Nexus] Kustaa:
Sorry for the old topic but this thread grows too fast lol. How did you get that ridiculous scores of +12000 or 13000 on antutu with mpokang?? I barely past 11000 with stock settings on 1080 version, and 10000 with latest dirtyV :( I did a factory reset and clean install but still the same
[Samsung Galaxy Nexus] aosp:
By removing it and flashing SmittyV ;)
[Samsung Galaxy Nexus] GilGameshn1:
Hi ... Pls mention your installed ROM ... And kernel settings ... I am noob but I reach 12500 with dirtyv in omnimetal latest nightly kk ROM .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
Thank you! Someone who knows how to search and read. :D

Must be too early in the boot for it. Throw in a sleep 60 or something.
[Samsung Galaxy Nexus] metalspring:
Maybe you need to go all the way back to stock, then reroot, etc. Sometimes that helps

On my custom build of dirty v v6 ;)
[Samsung Galaxy Nexus] fracama87:
Sorry I've found out now that post. This thread is going to fast and I miss something often :(

I immaged it was a trick, I've asked since I'm curious and I like to understand, also to learn....

And I'm totally agree with your post and I ever think the same when I try to adjust my settings (it's the same for down/up threshold of others gov)

That's also why I don't want give too much importance to antutu... Not to total result anyway.

logic reasoning with real experience support are better :) antutu can help for analyse results of some important parts...

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] GilGameshn1:
Simply wow ... Could u possibly copy/paste ur settings :thumbup::D

Sent From My Nexus Prime
[Samsung Galaxy Nexus] Nemed:
Man it worked! I owe you one :D
[Samsung Galaxy Nexus] Kustaa:
Im on CM11. Latest DirtyV version? Or SR one?
[Samsung Galaxy Nexus] GilGameshn1:
Happens to me ... If you dirty install ROM please factory reset . if a factory reset not an option then u must flush trickster settings cache or reinstall kernels and clear dalvik and cache in recovery mod . and try with stock settings the kernel come with and let the device cool off before benchmark .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] sajty:
target_load set is working for you after reboot?Where did you put that mentioned line?

---------- Post added at 05:03 PM ---------- Previous post was at 04:58 PM ----------

Will do,when i get back at home.
[Samsung Galaxy Nexus] Nemed:
Create a new init.d script

#!/system/bin/sh
sleep 30
chmod 666 /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo "85" > /sys/devices/system/cpu/cpufreq/interactive/target_loads

Don't forget to change permission to -rwxr-xr-x
[Samsung Galaxy Nexus] osm0sis:
Yep. Give me that output first though please.
[Samsung Galaxy Nexus] sajty:
I am heading to the pub now (we have already evening here), so i will do it when i get back (or when i will be able to do it, lol). But i will not forget, i promise :).

Sent from my GN
[Samsung Galaxy Nexus] juju2011:
Holy lol.. yah I like the mega starting to get some good rom support finally but my digitizer is finished lol called around and was told 350 to fix :/ so using my good old gnex and my note to surf the web going to fix the mega eventually when price drop on fixing it do you do any Dev for the mega?...
[Samsung Galaxy Nexus] Rushead:
Drink a pint for us Yanks!

Sent from a flashead cracker.
[Samsung Galaxy Nexus] cujo6801:
8:35am. West coast US...

So..........

You got it.......

Cheers.....

sent from the DOG pound
[Samsung Galaxy Nexus] Grarak:
I ported cm to mega and released a kernel with many features. So I didn't do much..
[Samsung Galaxy Nexus] adoboyo:
650am, Hawaii.

Drink up! Plan on drinking a few tonight myself.
[Samsung Galaxy Nexus] Nephilim:
EDIT* Post modified, was unaware all tests were done on DirtyV

I'm getting a little frusturated with my settings being compared to mpokang, yes, I aim for a happy medium between battery and performance but I steer a little more towards performance. You based your comparison inaccurately first off because I never use 1.5ghz and all your benchmarks read 1.5ghz. Second, I have multiple benmarks from when I still used v4 and not a single one is below 12800 for a score, so I have no idea how you ran the benchmark three times and got that terrible of a score with my settings. Thirdly, v4 is missing governor control tunables that weren't introduced until v6, so the settings you are using on v4 are outdated. Finally, I compare based on daily usage, not numbers. I will take my settings on DirtyV over Mpokang any day, they provide a comparable if not better performance experience than mpokang and battery life is much better.

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] Kaemo:
Kinda... Scared now.
[Samsung Galaxy Nexus] GilGameshn1:
Hey bro pls don't bother . We people need to have best things for cheapest price available so we compare 2 things that even is not comparable .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] juju2011:
Sweet I'll give the kernel a shot does it work with tw I still have the mega stock firmware installed I kinda noobed the recovery lol been to lazy to fix apparently cwm doesn't work well with it.
[Samsung Galaxy Nexus] Grarak:
No currently just for 4.4 aosp roms

But I am planing a tw kernel too
[Samsung Galaxy Nexus] juju2011:
Oh sweet let me know when your done and If need tester I'd be happy to help mega is my TV remote and voice search machine for now
[Samsung Galaxy Nexus] pianistaPL:
Dude, take it easy! You never has been criticized or something that. [MENTION=3317173]büscher[/MENTION] just shared with us results of different settings, that's all. That's nothing wrong to compare different configurations and settings.

You can only kill the people who created benchmarks apps ;)
[Samsung Galaxy Nexus] Nephilim:
EDIT, I was not aware these tests were all done on dirtyv.

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] pianistaPL:
Just one thing - custom Interactive settings from Mpokang aren't unfair.

Don't compare governor settings with some false RAM speed hacks.

Buscher wasn't testing Mpokang kernel just his governor settings.

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] pianistaPL:
I don't know what are you talking about - he only tested Dirty_V Kernel with three different settings, that's all. As i said, there's nothing wrong with that http://xdaforums.com/showthread.php?p=50122935

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] Nephilim:
Double post

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] Nephilim:
He is also running the settings on 1.5ghz which my settings have never been. Also, I have never ever had settings that low even on v4. To be honest my settings on v4 were always 12800 to 13111 on antutu with v4 so I simply cannot see how my settings are bringing him that low of a score. As soon as I get to my pc I will post 3 separate benchmarks from v4 and none of the are below 12800.

Sent from my Android 4.4 Galaxy Nexus[/QUOTE]

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] pianistaPL:
So what that CPU was set to 1,5GHz?... There is no big difference between 1,4GHz and 1,5GHz.

Anyway... I want to just tell that you shouldn't be so angry and upset because buscher had a right to share the results and he didn't critized you and your settings. He just asked.

EOT ;)
[Samsung Galaxy Nexus] fracama87:
Aren't unfair but are wrong!

We have just discuss about few pages ago.

And osmosis explained that very well on post #2255 ;)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] pianistaPL:
Right ;) But the point is that buscher didn't knoe that Mpokang settings aren't so good as benchmark showd. And he didn't tell that... i don't know, that Nephilim settings are wrong and bad or something that

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] fracama87:
read here

http://xdaforums.com/showthread.php?p=50102720

and here

http://xdaforums.com/showthread.php?p=50103095

[MENTION=4544860]osm0sis[/MENTION] hope it's enough for my redemption :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Nephilim:
I have modified my initial post to reflect I was unaware of the tests all being done on dirtyv. I still feel the tests were inaccurate though, due to a few different things.

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] fracama87:
Oh yeah right... ;)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Nephilim:
As said above. My initial post has been edited.

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] fracama87:
I feel the same. We could write a big book about the reasons which made the antutu test inaccurate!

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] pianistaPL:
So... Peace :) Everything is fine, guys :) We are one big family of Gnex :)

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] antypas:
[MENTION=1143630]osmosis[/MENTION]

Have you tried other kernels (besides Franco's) with the settings you propose?

If yes, have you tried lowering go_hispeed_load (lets say at 60) afterwards in order to make a comparison?

I tried your settings with Dirty V and with Mpokang and I am certain performance suffers.

After trying your settings I lowered go_hispeed_load and I immediatelly noticed the difference.

Franco has separated touch/input boost from go_hispeed_load so someone can do what you propose and still have good performance (on touch immediately CPU=1036mhz for 0.5sec).

BUT with kernels that have the normal new interactive ... the >80 go_hispeed_load causes inferior performance compared to values <60.

I understand what you say about target_loads and go_hispeed_load on Mpokang ... but these settings are still the best performing for me while maintaining good battery life.
[Samsung Galaxy Nexus] lilz4life:
honestly tho man your the one who brings up mpokang in every thread including this dirtyv kernel thread just let it go.

if your so tired of being compared to mpokangs kerne with your settings dont seek the attention like mentioning his name in almost every other post and thread.

This thread is about dirtyv development so lets just focus on bsmitty here and leave mpokang out of this
[Samsung Galaxy Nexus] chongns:
It is obvious that they are originally discuss about the ram speed hack of mpkong kernel, and the topic extended to the kernel setting, nothing wrong about him mention ing it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jhonnyx:
I'm still more smitty-er than ever, bsmitty83, will be having today a new release?

Dirty gang awaits for crackflash-food

;)
[Samsung Galaxy Nexus] antypas:
Ha ha ha. :laugh:

Mpokang kernel has made a huge impact in the GNex community.
[Samsung Galaxy Nexus] Nephilim:
Dude, I don't know who you are but your attitude towards me is getting old, first you claim all I do is post about my settings as if I am bragging because you decided to take my words out of the wrong context, now you are making up stories about my posts involving mpokang that couldn't be further from the truth. 99% of my posts related to mpokang are in response to someone else speaking of him. In the future, please stop butting in with rude posts towards me in response to my posts which have nothing to do with you. Honestly the only thing I've seen you contribute in this thread are two condescending comments to me.

If you actually put time into helping in this community and contributing things as much as I have maybe you would see where I am coming from instead of making inaccurate judgements.

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
Truth is bokang is rock solid and so is smittyV, if we don't compare and contrast then we can't have these kinds of discussions, jus take a break and gather yourselves, any who, I always use Franco settings b4 we have introduced the 3.4 interactive

Which are :

Go hispeed load - 65

Hispeed-700mhz

MinSample- 39062

Timerrate-19531

AboveHiSpeed-19531

The last 3 are my personals based off of my conservative calculations lol
[Samsung Galaxy Nexus] GilGameshn1:
:thumbdown::thumbdown:
[Samsung Galaxy Nexus] bsmitty83:
Agreed , that was my favorite kernel . its given me alot of inspiration , and for whatever reason he chose not to be GPL compliant is not my concern . I'd love to know what he did to get such excellent performance . and maybe I'll be able to get close . but really I'll never talk Bad about anyone even if they are wrong .

Lol I've been having too much fun reading all these posts to build . Im joking of course , but maybe I'll get something out tonight . there's some nuggets of information buried in this thread I gotta find and include or look at . I guess I'll put 180mhz back since it seems to be popular
[Samsung Galaxy Nexus] Nephilim:
Only in a negative way. I would have mad respect for him if he stopped violating GPL and shared his code. The more he avoids doing this the more I believe the people that have hinted at his possible cheating of benchmarks. I really see his ramspeed scores as a faked placebo at this point. Nobody can prove different but him and he refuses to comment. I truly feel that if benchmarks didn't exist DirtyV would be the winner hands down because its wayyyyy smoother and faster.

Please, any mpokang fanboys, if you disagree, feel free to provide factual evidence that the ramspeed is actually boosted by 50% outside of a benchmark score. ;)

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
Can you plz plz plz plz plz plz plz put intelli-demand in your Smitty test kernel since its not recommended for the masses ?
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4443334]Grarak[/MENTION] [MENTION=4328678]metalspring[/MENTION]

Have you tested Linaro 4.9 yet?

Add gcc 4.9

http://goo.gl/mF1prg

Add workaround for gcc 4.9 bug

http://goo.gl/q07hMW

Allow getting gcc from git and fix toolchain-src detection

http://goo.gl/6hd23a

Add patches for gcc 4.9

http://goo.gl/eRz4nK

Add fix for gcc bug 59935

http://goo.gl/2onArd
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=4328678]metalspring[/MENTION] sorry for the Confucius earlier with the memset.S fix , I was half asleep and half stoned so ......yea ;)

Anyways I reverted the commit I used to build on 4.8 linaro when everyone said it didn't work , it fixes the bootloop a few minutes in to bootup , but the random , unstable crap is still present . so if you wanna build with 4.8 you gotta patch your source , you can pick my git I'm doing it now (smittyV)
[Samsung Galaxy Nexus] Nephilim:
Your kernel stomps mudholes in Mpokang as far as performance and speed. F*ck a benchmark when his scores cannot be proven.

Also, could you please re add 180mhz cpu step back in the next DirtyV? Please. ;)

Sent from my Android 4.4 Galaxy Nexus