yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] jackpollard:
Man I'm waiting patiently for the update, seems like a pretty big one, can't wait! It may be time to unfreeze synapse to check out all the new kernel features, synapse its so unstable for me most of the time where the built in Benzo utility is solid. I usually cross my fingers on boot that I don't get that dang "last boot setting did not work" (or something like that) in synapse.

Anyway, thanks as always for the work.
[Nexus 6 Android Development] Xileforce:
Hoping to release 2.0 shortly. Gonna merge in latest lean kernel and Franco stuff. Just realized imoseyon has supported fku for a bit in ramdisk. Likely just fku needed an update to support it.
[Nexus 6 Android Development] Xileforce:
Okay guys 2.0 is out! Out of pure curiousity I've uploaded a build compiled with the existing toolchain (Linaro 4.9.3 with Graphite) and another build compiled with the brand new SaberMod 5.0 (No Graphite Flags Until They Are Fixed) SM 5.0 is based on the new GCC 5.0, a new major version of the compiler. The files are labeled as such in the downloads folder. Please share which you think is better (Smoothness, battery, etc) 2.0 Is a huge update with well over 100 commits oh! and it will display your bin number on the front page of synapse now!. As Usual the changelog is posted in the second post ;) If ur wondering why intelliplug got removed its because the testers were reporting issues with it, and I was having some weird issues with it as well and its very inactively developed by Faux123 atm. MSM Hotplug has been recommended and seems like a good replacement for now. Enjoy!
[Nexus 6 Android Development] jlokos:
Thanks for the update; I just DL'd and flashed the sabermod version. I was going to report to you an issue I had with build 1.9.2 relating to OTG not working for me. However, I flashed the 2.0 and OTG is working again. I'll let you know how things go with the new build.
[Nexus 6 Android Development] le1tho:
Is it possible that i can run 1728MHz at 600mV? Because i tried setting voltage both using trickster and system tuner and it simply is stable at Antutu with Performance governor locked at 1728MHz all cores.
[Nexus 6 Android Development] gamewarden234:
How do you guys see the current cpu frequency. I can see current for gpu but can't find cpu in synapse
[Nexus 6 Android Development] Xileforce:
I use system monitor lite. But noe that I think of it I can probably add the current CPU frequency into synapse. I'll look into it.
[Nexus 6 Android Development] Xileforce:
Ummm that's like a 300mv UV I can't even run 300mhz at that.......what bin are u?
[Nexus 6 Android Development] Grubbdog:
0.o he must be like bin 20....
[Nexus 6 Android Development] Damon13:
I am giving V2.0 SM5 a try so far I am impressed. I made a few tweak such as min Freq 98 MHz and max at 2880 MHz, running 4 cores (Mako Hotplug Load Threshold Set Back To 0) and GPU set to 700 MHz. My CPU bin is 9 and my Nexus is running smooth and fast. I open up waze and here maps and they are lag free.
[Nexus 6 Android Development] Xileforce:
I personally feel like the Sabermod Build is faster but its really hard when u can't run them side by side.
[Nexus 6 Android Development] Xileforce:
If u want a little extra performance u can turn off power efficient workqueues under CPU settings in synapse. Glad to hear its running fast for you though :)
[Nexus 6 Android Development] le1tho:
I think something wierd is going on there, because when i undervolt 2265, 2496, 2572, 2649 MHz steps and test their stability with performance governor it fails when i set too low voltage, but somewhat this doesn't apply to 1728MHz and lower steps, but when i switched to ondemand it froze. Would be good to have something better to read real voltages and not what some software just thinks it set to...

I have bin 8 reported by the terminal command, but i set the the voltage values according stock bin 15 but from 720-300 i set voltages even lower by 20mV and 2496, 2572, 2649 a little higher. I have been testing every step with antutu, but i skipped some steps between 300 and 1728.

BTW: I don't really understand this stupid restrictions from xda forum for posting messages, attach files and external links or links to images for new users. Why should i lose my time writing to some useless threads before posting to usefull threads? It's contraproductive and doesn't really have any benefit, just really bothers new users.
[Nexus 6 Android Development] Xileforce:
I tried to thank you but. I ran out of thanks for the day...one second lemme steal one of my thanks back from grubdog. And yes I couldn't agree more on getting a program that actually directly showed the voltage being used. Though I'm not entirely sure how this would be done. As for the weird voltage deal...I'm not entirely sure. I'm guessing this would be the same on all kernels but as for why it occurs I have no clue.
[Nexus 6 Android Development] Damon13:
Xileforce you have outdone yourself! I am usually an LK and Hydra fan but this kernel is running smooth. There are no hiccups and battery is efficient as well. I will give your suggestion a try but will battery take a dive.
[Nexus 6 Android Development] Xileforce:
Hard to say. There's actually instances where it may improve ur battery life since ur in 4 core mode. Basically what it does is try and queue processes onto core0 but if ur using 4 cores all the time and disable that it will spread the load more evenly. Most times more cores at lower frequencies is less power than less cores at higher frequencies. TLDR. I have no clue. It could go either way lol
[Nexus 6 Android Development] Grubbdog:
[MENTION=3627473]le1tho[/MENTION] bothered me too haha but 10 doesn't take long to get :)
[Nexus 6 Android Development] le1tho:
What are your voltage settings so far Xileforce?

BTW: I read that a lot of people are concerned about the PSV or Bin value, but i think it's the same as with GPUs and ASIC quality, which are just a theoretical number, thus Bin 5 can reach lower voltages stable than Bin 8 or higher and people should not really post only the UV value - this can be highly misleading, because different SOC Bins have different stock voltage values, thus the absolute voltage value is different, so post the actual voltage setting.
[Nexus 6 Android Development] Damon13:
Your explanation is good enough for me, will give it a try and will report back. You nailed it with V2.o SM5!
[Nexus 6 Android Development] jackpollard:
So as always love the update, you spoil us.

I did have, what I consider an odd occurrence. I initially flashed the SM version, however using mako and even setting threshold to 100%, cores 3 and 4 were just pegged at 2649. I then flashed the other 2.0 kernel and back to seeing cores 3 and 4 offline. Not sure what happened with that. I also tried turning MSM hot plug on, but it would not stay on once I went out of the app.
[Nexus 6 Android Development] Mistertac:
I'm on the latest SM version as well and noticed my 3 and 4 core were set to performance governor in Synapse. Wasn't sure if that was just something I did from all my tinkering around, but check that out if you haven't already. Sounds like that's what you may have had going on as well.
[Nexus 6 Android Development] jackpollard:
Thanks Mistertac, appreciate the response. I had synapse frozen, I was just using the Benzo kernel util, I refreshed the SM version and unfroze synapse. When I checked, cores 3 and 4 were offline as they should be. I then just froze synapse again and all looks well. When I did check my cores they were not on performance, so at least I had that right. I will chalk it up to a flash anomaly and keep an eye on it.
[Nexus 6 Android Development] Mistertac:
Yep that seems to happen too lol well either way you're up and running good now. Thanks for checking on that anyways.

Latest SM version absolutely flies!
[Nexus 6 Android Development] Admiral2145:
Really like the sm version.. Also intellactive is my fav gov....
[Nexus 6 Android Development] MarceloSiciliano:
Wow lot of new settings that i dont know what then mean on the SM build hahahaha does any one here have a guide for the new hotplug?
[Nexus 6 Android Development] Xileforce:
Dude idek what the hotplug ones do...... BTW sm and linaro build are exactly same features wise. Just different compiler optimizations and tool chains. Linaro version actually has more optimizations (graphite and loop nest optimizations) but that may be overcome by the sheer performance that GCC 5 brings to the table over GCC 4.9.3 stock google tool chain is 4.8 lol.
[Nexus 6 Android Development] Xileforce:
Yea SM seems to be the most popular so far. But that could also be because nobody's trying the Linaro version cuz SM 5 is all sorts of new and fancy ATM :) intelliactive Is a solid choice ;)
[Nexus 6 Android Development] :
Using Sabermod 5 version on Terminus rom and maaaaaaaan is it butta!!! :sly: Tks op and everyone else who had anything to do with this bad boy. :thumbup:
[Nexus 6 Android Development] Xileforce:
Awesome to hear that and glad that your enjoying it!
[Nexus 6 Android Development] Admiral2145:
With the screen off it stays @ 35mjz however, when I turn the screen on it goes to 300mhz... Not sure how to fix this issue...
[Nexus 6 Android Development] sparksco:
That statement sounded a little biased TBH. I honestly don't think linaro or SaberMod will have that much of a difference in terms of performance. Gnu is the real winners here for developing and releasing gcc 5.0. SaberMod generally tends to make it available and tries to find fixes in the source to make it work and compile before others. Releasing a toolchain is one thing, getting it to work is another.
[Nexus 6 Android Development] Mistertac:
How are you monitoring that? I have no problem here running Mako with 2 cores. I have my min set to 98 right now and the 2 cores idle there.
[Nexus 6 Android Development] sparksco:
[MENTION=4517211]Xileforce[/MENTION] are you using strict-aliasing in the kernel? If so how do you do this? I never could get it to work in kernels..

Edit: Seems the new toolchains support it
[Nexus 6 Android Development] Admiral2145:
Synapse and setcpu
[Nexus 6 Android Development] Admiral2145:
On top of this it won't sleep at all
[Nexus 6 Android Development] dsmitty166:
Yeah that would not be kernel related.
[Nexus 6 Android Development] Admiral2145:
What rom you running? I'm on meanpop...
[Nexus 6 Android Development] dsmitty166:
The only good one! Lol jk

The one that I am part of, Euphoria...
[Nexus 6 Android Development] Admiral2145:
Delete
[Nexus 6 Android Development] crossen0:
I'm enjoying the Linaro build, fwiw
[Nexus 6 Android Development] Xileforce:
Haha no I think sm is faster too. What I was trying to say is everyone was reporting that they were running the sm version and it was super fast. But likely nearly everyone is trying the sm version because its the new one so nobody is even trying the linaro. Not being biased, just making an observation :P as for strict aliasing. It was a huge PITA. I had to manually disable it for each individual file that broke with it. Took me several hours.
[Nexus 6 Android Development] Xileforce:
This is possibly an issue with your gapps. They've been causing weird issues lately.
[Nexus 6 Android Development] sparksco:
OK yes about strict-aliasing. How do you disable it for each file? I enabled it and it made my mobile data stop working... Could this be the reason some people are having issues where their mobile data stops working randomly?
[Nexus 6 Android Development] Xileforce:
U have to figure out which file is not working then find the make file for that file. Then u would add this to the make file. CFLAGS_filename.o := -fno-strict-aliasing lowercase filename. And its .o not .c or if you don't want to bother fixing each individual file. You can just disable it by directory. So if u get some aliasing errors in the net folder. U can just add CFLAGS_KERNEL := -fno-strict-aliasing to the net make file for instance.
[Nexus 6 Android Development] sparksco:
Hmm OK I'll have to test more. I'll most likely add -Werror=strict-aliasing to make sure it all gets fixed... But you never answered my other question [emoji3]

I see some people are having a similar issue I was having where their mobile data would stop working randomly here in the nexus 6 forums. Could strict be the cause of this?
[Nexus 6 Android Development] Xileforce:
I haven't had an issue with the data deal personally. It may have been for a variety of causes previously. For instance some experimental network commits and some wakelock related stuff for the cellular driver. I use error on strict aliasing so ive fixed all the errors additionally the data issue only popped up on the move to 5.1 to the best of my knowledge. My testers hadn't reported an issue in the past few days since I did those changes.
[Nexus 6 Android Development] le1tho:
I tested your v2 Kernel, but seems the issue with performance is that, GPU decreases the frequency by itself, like i set it to 700MHz but it random decrease to 430 or 500MHz, even when i set it to 600MHz still the performance in antutu is like with 430/500MHz, i get only around 40-44k total score and around 12-15k for graphics, this doesn't happen with ElementalX kernel, i wiped cache+dalvik after flashing via TWRP.
[Nexus 6 Android Development] sparksco:
I see what you mean now. The errors with all the include files I have to track down the .c files and also build with -j1 lol :eek:
[Nexus 6 Android Development] Xileforce:
Hmmm that's interesting. I score around 19k for 3D graphics in antutu. Let me check if it lowers itself for me. When I benchmark I set my min and max frequency for CPU and GPU to the same frequency so it can't underclock. It could be thermal related maybe. Either way I'll look.
[Nexus 6 Android Development] Xileforce:
Yea....there was a ton....what I did was I started off just disabling mass amounts at once by disabling for the make file. So if net folder had an error I just disabled it for whole net folder in the net make file. Then dirty build and do that for next. Then at the end I would go back through and remove the strict aliasing disable flag I added to the net make file for instance and then just fix the individual files there and move on to the rest....like I said hours lol though worth it IMO. Its one of the biggest optimizations you can do.
[Nexus 6 Android Development] le1tho:
What program do you use to set frequencies/voltages? In trickster there is only option to set maximum frequency for GPU and even with performance governor for GPU it doesn't stay at maximum.
[Nexus 6 Android Development] Xileforce:
I use synapse. I just benchmarked with antutu on 700mhz performance and it did not lower afterwards. Maybe its people with lower GPU bins can't run it stable so it automatically reduces itself when it gets unstable. I'm not a GPU expert by any means. May have to check my logs and see what's happening.
[Nexus 6 Android Development] sparksco:
Probably depends on the kernel. I like to take my time and take breaks so maybe hours could turn into days for me lol [emoji3]
[Nexus 6 Android Development] Xileforce:
Lol yea who knows if u will have more or less. I actually did it over the course of several days. My first commit had a very broad removal of strict aliasing. Over the next few days I refined it so that only the actual broken stuff wasn't compiled with strict. I would suggest using my commits for it but its likely different :(
[Nexus 6 Android Development] wrongway213:
I've been curious about thermal throttling. I get better results using 80 to 90 degrees C, but I am unsure why default is 70. Is there any benefit to setting it at 70 or risk of raising it to 80 or even 90? Seems 70 is standard for kernels but only info I can find is that itself, that 105 degrees is the danger zone where shutdown happens and info on disabling entirely with nothing about consequences or risks. If you have any ideas I'd appreciate it. You're usually pretty good at dumbing stuff down for a kernel dev lol
[Nexus 6 Android Development] Xileforce:
I'm not entirely sure why 70 is the chosen value. I'm guessing that's the qcom value so devs play it safe. Likely its not good to run the CPU at high temperatures because it probably reduces the lifespan of the CPU. But I'm no expert.
[Nexus 6 Android Development] le1tho:
Xileforce: Can you check temperature throttling ? I think the gpu and cpu low performance would be throttling related, on your kernel it starts to throttle at lower temperature, i think 70C and even when i adjusted it with synapse it still started to throttle at the same temperature.
[Nexus 6 Android Development] Mauijpm:
Make sure you don't have both Thermal settings enabled (Intelli and Qualcomm). I unknowingly did and it dropped my Antutu down to the low 30's. Unchecked Intelli in Synapse and my results are back to normal. :)
[Nexus 6 Android Development] Xileforce:
Did you enable intellithermal before raising the throttle temp? And I'll look into the thermal stuff. Its just typically its not good to run hot like that for risk of damaging the CPU. That's why it tries throttling it to cool it down and if that doesn't work it just turns a core off to lower temps.
[Nexus 6 Android Development] clnzx2:
Latest SM running great. Not sure which is better, SM or L yet though.
[Nexus 6 Android Development] sparksco:
[MENTION=4517211]Xileforce[/MENTION] I noticed you have this setup for stack protector

https://github.com/XileForce/Vindicator/blob/master/Makefile#L600

Is this enabled? And also have you tried -fstack-protector-all ?

I was reading the gcc documentation and was wondering if I should try both flags (-fstack-protector and -fstack-protector-all) or just one of them. Thanks.
[Nexus 6 Android Development] Xileforce:
Yea I have stack protector enabled. Idk really anything about that stuff tho so I just leave it on. Pretty sure lean kernel has it on too. I haven't tried fstack-protector-all.
[Nexus 6 Android Development] sparksco:
Well it's a security feature to protect against stack buffer overflow attacks..

http://en.m.wikipedia.org/wiki/Buffer_overflow_protection

There's a few options. The two I listed and one more I found -fstack-protector-strong
[Nexus 6 Android Development] Xileforce:
Is there any downside to activating more of them?
[Nexus 6 Android Development] sparksco:
Not sure. I'm using the all one now without issues. Probably needs more testing. For now I hardcoded mine, but I'll most likely adapt mine to have the call cc-option check like yours does. Mine doesn't have that check to see if the compiler supports it or not.
[Nexus 6 Android Development] MarceloSiciliano:
Xileforce can you help me with an issue? I don't know if its a kernel, ROM, or device issue, but apparently is not a ROM one, because it happens with every ROM. Every time my device reboots because of excessive undervolt it falls in a bootloop that only ends with a ROM reflash. Do you have any idea what causes it?
[Nexus 6 Android Development] Xileforce:
Are u applying voltage on boot?
[Nexus 6 Android Development] sparksco:
Not every device is created equal.. It sounds like a common user error of undervolting a little too much and having it set on boot and it's causing a kernel panic. Some devices don't like any undervolting at all. I'd suggest testing what works for your device then stay with that.
[Nexus 6 Android Development] Xileforce:
Just found a link to a commit in the benzo thread that adds these two lines to the build props of ROMs. dalvik.vm.image-dex2oat-filter=everything and dalvik.vm.dex2oat-filter=everything basically they will make ART compile more stuff when it does that optimizing apps deal. That will speed up pretty much everything because the more stuff you compile the faster it will run. Basically just add those two lines, reboot to recovery and wipe dalvik cache and normal cache to be safe and then boot back up. It may take longer to optimize apps btw.
[Nexus 6 Android Development] sparksco:
I thought dalvik was ditched in lollipop?
[Nexus 6 Android Development] wrongway213:
Yeah, but look in TWRP. Dalvik cache is still a partition
[Nexus 6 Android Development] sparksco:
Probably just for compatibility with older Roms. There's no such partition dalvik on my device ...
[Nexus 6 Android Development] sparksco:
Here's the partition layout of my device on lollipop. There is no dalvik sorry. I don't think this build.prop hack does anything in lollipop. Maybe in KitKat it did when art was still experimental.
[Nexus 6 Android Development] Mistertac:
Not really my area of expertise obviously but have you seen Syko's explanation of this here : https://plus.google.com/+SykoPompos/posts/eDUgU11ZVxQ
[Nexus 6 Android Development] bill3508:
Voltage is one of the things I leave unchecked for applying at boot for that very reason. You can backup your settings within most kernel apps and then restore or just apply your global once booted.
[Nexus 6 Android Development] sparksco:
Ah I see. Well my ROM I'm on now is already pretty snappy so I don't see how much more this can improve things. Also when your apps update from the play store I'm not sure this mod would stick to the updated apps or not. I'll wait to see feedback on how much more things improve with this mod thanks.
[Nexus 6 Android Development] Xileforce:
It works for all apps. The reason for wiping dalvik is to optimize your existing apps . I would imagine you may notice a battery life improvement too though it will take up more space on your phone because the compiled files will be larger.
[Nexus 6 Android Development] henrybravo:
You've got a dalvik cache in Lollipop. Go to /data/dalvik-cache on your phone and you'll see subfolders there with all sorts of stuff. Mine is 1.6 GB.
[Nexus 6 Android Development] 9wire:
Tried 3 times to add the 2 lines to build prop but they don't stick. I save changes, reboot and the 2 additional lines are gone.
[Nexus 6 Android Development] Xileforce:
That's weird....I use build prop editor app to do it. In that app I just put the flags in but remove the "=everything" part and then I put "everything for the value. Obviously no quotes.
[Nexus 6 Android Development] henrybravo:
Make sure the /system partition is in read/write mode. For example, in Root Explorer there is a "mount R/W" button. And whatever editor you're using needs root access, naturally.
[Nexus 6 Android Development] 9wire:
I'll try it again.
[Nexus 6 Android Development] sparksco:
Yes but updated apps replace the old ones on your device... That's why when you dirty flash a new rom update it only upgrades the apps that were updated... So every time your apps update you'd have to force upgrading again by wiping cache which seems like a big pain. I've tested the upgrading a lot in the past. I always like to force the normal upgrading just to update the apps. I just don't know how much better this upgrading is compared to the normal one.
[Nexus 6 Android Development] Xileforce:
Yes but the apps are just compiled when they install. The only reason it compiles the apps on boot is because they have been installed but not compiled which usually happens when you flash a dirty ROM due to the flash wiping cache or dalvik and therew probably something else that forces it to optimize apps whenever you flash a ROM. You can't run an app without it being compile before time with ART. That's why if u install a new app and reboot it doesn't get optimized, because that all goes on in the background during the install process. That's why since art. Apps take longer to install. All this does is changes the existing art compiler setting from speed to everything. So its no different in any way than before, just faster.
[Nexus 6 Android Development] 9wire:
Got it to stick, got the storage error, google app fc, and terrible lag. Reverted. Oh well, worth trying.
[Nexus 6 Android Development] Xileforce:
Wonder why that's happening :/ idk guess we will have to wait and see what sykopompos says. Working here.
[Nexus 6 Android Development] LunaticSerenade:
Stuck for me, seems to have made performance snappier.

I miss the 800 MHz GPU and 3.033 GHz CPU. :P
[Nexus 6 Android Development] Xileforce:
Lol u miss the two things causing half of the people to bootloop :) I had a build with 1ghz GPU that we tested at one point O_o