yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
Probably be easier to incorporate it into say a stock cm11 kernel . it looks like its from the days before a hardcoded over clock was introduced. I dont know if it would be any better or not .

To add it to a stock cm11 kernel would be easy I would say , if you just wanna check out how it works .
[Samsung Galaxy Nexus] ashclepdia:
I would be crazy stoked to try that on dirty if u ever felt like giving it a shot
[Samsung Galaxy Nexus] osm0sis:
For whatever it's worth, in my experience IVA on the GN never leaves 133 MHz.

In my undervolting testing I found that only changing the lowest step (so 133) seemed to have any effect (I could reduce the other two to 0s with no apparent instability, even in gaming), and I even wrote that IVA freq export to userspace to watch it and it never moves. :confused:

[MENTION=4374757]Edward Stanbury[/MENTION] can back me up on that.

/sys/devices/system/cpu/cpu0/cpufreq/iva_cur_freq
[Samsung Galaxy Nexus] krweby:
I'm still seeing with DirtyV-R after the phone has been running for a while and I reboot it bootloops at the Google logo. This has been doing this since after 4/19 build. And I'm not running CM.
[Samsung Galaxy Nexus] cujo6801:
The last line of this post made me laugh

If you ever read CM's thread you'll understand why he posted it.... Lol

Sent from the "DOG" pound
[Samsung Galaxy Nexus] metalspring:
Well thats wierd... running cat /sys/devices/system/cpu/cpu0/cpufreq/iva_cur_freq returns a value of 133 MHz, but viewing the file with root explorer shows it as 266 MHz... And I do remember some kernel control app (cant recall offhand which it was) that could show all the current freqs of cpu, gpu and IVA and IVA did indeed change

Edit- also if you're referring to the live overclock thing, it wouldnt matter if it changed steps or not, the live overclock simply increases each freq step by whatever percent you put in (which could be part of the reason it made things seem quicker :P)

Edit2: also according to trickster mod, the IVA voltage changes sometimes too, which I dont think is possible without changing freq speeds as well?

And edit3- I think I also remember IVA freq is related to gpu speed so if its set to the stock value, IVA freq may not change then or at least its much less likely to change (I am running 512 MHz max for the gpu btw)
[Samsung Galaxy Nexus] Ashtrix:
I could't believe that Live OC made Gnex perf outstanding. I also had tried the Live OC on GlaDos & even on the AK's but i'm sorry to say this device just doesn't perform as well as my old GTi9000 SGS which also had Live OC but it used to work damn good....

P.S : AFAIK in my 2years of nexus prime's usage this device can't work good @ 512MHz GPU OC and Live OC features
[Samsung Galaxy Nexus] osm0sis:
Can you screenshot that for me? I added MPU as "CPU Voltage" in tonight's Synapse commit, but now I'm toying with the thought of giving all the current voltage outputs their own page in the Dev Tools switch interface.

I kinda don't like the extra clutter in the CPU section it adds either, but it's growing on me. :p

What do you and everyone else think?

[MENTION=4328678]metalspring[/MENTION] I just sat with IVA freq and voltage live output in Synapse for awhile and tried OCing GPU to 512, and playing music and all sorts of stuff but didn't see it move. :confused:
[Samsung Galaxy Nexus] metalspring:
You mean this at the bottom in trickster I guess?

Also, I got the IVA voltage to at least change by toggling the recents quickly a few times (more graphics intensive I guess?)
[Samsung Galaxy Nexus] osm0sis:
Ah good. What I've got in Synapse is on par with that at least. :good:

I'll try IVA again with the Recents and see if I can get that result too. :)
[Samsung Galaxy Nexus] Edward Stanbury:
This is all too true! haha damn its been awhile :P sold my gnexus awhile ago and joined the n5 team, i still miss this side of the forum though ! ill post here more often now i think just because its super friendly (: but yeah IVA freq never budged no matter what load was put on etc new quite understood why but it never effected media decoding and what not
[Samsung Galaxy Nexus] osm0sis:
Still no luck here. IVA just sits... GPU voltage jumps around minutely without a frequency change quite often though.. I guess because it's actually the CORE voltage? Same goes for the reported MPU voltage I think because maybe it's averaged from both CPU cores or something.

More annoying to watch than interesting, which is why I left them out of the commit. :p

I'm open to suggestions though!

Good to see you buddy! :)

Yeah, we're still having all sorts of good old fashioned fun over here. ;)
[Samsung Galaxy Nexus] cujo6801:
5/3 smittyV

Not bad...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] krweby:
Yes I understand but the last time I posted it was glazed over because of it. And that is the reason for the last line. ;)
[Samsung Galaxy Nexus] ashclepdia:
Iva isn't just sound processing chip.

It handles video playback acceleration and I think when recording video.

So you might not see that freq change at all if you aren't watching video, playing game, doing something that requires it to run at higher rate. Just cuz it doesn't change when we are looking at it doesn't mean it isn't using the other freqs at all
[Samsung Galaxy Nexus] Czechnolog:
Was anybody able to ENABLE Double Tap 2 Wake on Galaxy Nexus?

I found only this below, but I would like to find some kernel that supports Double Tap 2 Wake without additional settings and applications:

https://play.google.com/store/apps/details?id=me.paranoid.touchcontrol

Thanks.
[Samsung Galaxy Nexus] ashclepdia:
[MENTION=1143630]osmosis[/MENTION] I was able to grab this screen by opening game SmashHit and I put its graphic settings on high, played for 30secs, then hit recents and jumped back to root explorer and quickly tapped the iva_cur_freq in sys ;)
[Samsung Galaxy Nexus] osm0sis:
Nice one! Thanks! Good points all around. :)

Any recommendations on what to do with the voltage outputs so they're not cluttering sh*t up like in my screenies? :p
[Samsung Galaxy Nexus] metalspring:
Well I wonder if just changing the clockspeed values for IVA inopp4xxx_data.c and/or enabling the higher frequencies (which may need extra work as the little note in code says) would actually work to make them run at a higher speed? Maybe [MENTION=4608636]bsmitty83[/MENTION] could shine some light on it, who knows maybe slightly increasing IVA speed would speed things up?

FYI, I'm talking about these lines in /arch/arm/mach-omap2/opp4xxx_data.c

OPP_INITIALIZER("iva", "virt_iva_ck", "iva", true, 133000000, OMAP4430_VDD_IVA_OPP50_UV),

/* IVA OPP2 - OPP100 */

OPP_INITIALIZER("iva", "virt_iva_ck", "iva", true, 266100000, OMAP4430_VDD_IVA_OPP100_UV),

/* IVA OPP3 - OPP-Turbo */

OPP_INITIALIZER("iva", "virt_iva_ck", "iva", false, 332000000, OMAP4430_VDD_IVA_OPPTURBO_UV),

/* SGX OPP1 - OPP50 */

OPP_INITIALIZER("iva", "virt_iva_ck", "iva", false, 332000000, OMAP4430_VDD_IVA_OPPTURBO_UV),

And

OPP_INITIALIZER("iva", "virt_iva_ck", "iva", true, 133000000, OMAP4460_VDD_IVA_OPP50_UV),

/* IVA OPP2 - OPP100 */

OPP_INITIALIZER("iva", "virt_iva_ck", "iva", true, 266100000, OMAP4460_VDD_IVA_OPP100_UV),

/*

* IVA OPP3 - OPP-Turbo + Disabled as the reference schematics

* recommends Phoenix VCORE2 which can supply only 600mA - so the ones

* above this OPP frequency, even though OMAP is capable, should be

* enabled by board file which is sure of the chip power capability

*/

OPP_INITIALIZER("iva", "virt_iva_ck", "iva", false, 332000000, OMAP4460_VDD_IVA_OPPTURBO_UV),

/* IVA OPP4 - OPP-Nitro */

OPP_INITIALIZER("iva", "virt_iva_ck", "iva", false, 430000000, OMAP4460_VDD_IVA_OPPNITRO_UV),

/* IVA OPP5 - OPP-Nitro SpeedBin*/

OPP_INITIALIZER("iva", "virt_iva_ck", "iva", false, 500000000, OMAP4460_VDD_IVA_OPPNITRO_UV),
[Samsung Galaxy Nexus] ashclepdia:
How about having the voltage show NEXT to the frequency.

Or displayed as Freq/Voltage (if that makes any sense... Meaning it would show for example 153Mhz/949mV)

Would keep things closer together
[Samsung Galaxy Nexus] metalspring:
Yeah, similar to what I did, except as soon as I checked it again via terminal, it read 133Mhz again, so I checked with root explorer again and it still said 266Mhz.

Its weird, it seems terminal always reports it as 133, but root explorer always reports 266???
[Samsung Galaxy Nexus] ashclepdia:
Yea those are the lines I had seen that got me wondering.

Now I see that apparently the 266Mhz is the top that is allowed for now. And has me wondering how much better performance for video playback and gaming and such we could see by having one or more of the higher freqs enabled. I'm def willing to test, and I could care less about battery or if it fries my gnex lmao, new job soon and I'll be buying new device anyways.

---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------

Not for me

In root explorer it shows both 133 AND 266, depending on how quick I am to get back and tap it.
[Samsung Galaxy Nexus] osm0sis:
Hmm yeah, f.Ku used to do it like that back in the day. Good idea, just not sure how to do it for CPU though since we report on both cores. I'll mess around with it.
[Samsung Galaxy Nexus] Edward Stanbury:
haha hard out its been awhile ! :) good thing i sold ol beast to a good friend thats local, hes always asking what i use to run on it. ill be sure to send him here but for now im just catching up on all the excitement :P
[Samsung Galaxy Nexus] gautam_nexus:
[MENTION=4544860]osm0sis[/MENTION] just noticed I cant change IO tunables or Governor tunables in Synapse. Am I missing something?

Using the latest No-Mem build.

Thanks
[Samsung Galaxy Nexus] Hetalk:
FAQ on post#2 updated. Please let me know if some stuff is outdated or incorrect.

Ever since last week (maybe 10 days) every build has been flawless and can be termed a "fallback" build for me.

As of now I'm running latest dirtyV with latest AOSPA and it's running like a champion on drugs. No issues so far. Thanks [MENTION=4608636]bsmitty83[/MENTION]

I've been using synapse for the last week or so and it looks a lot refined since I used it last (probably month or so back). Awesome job [MENTION=4544860]osm0sis[/MENTION] Thank you.

Am not able to test [MENTION=2853378]Nephilim[/MENTION] settings as I've been quite busy with work, so don't get time to test stuff out. All the time I get is used to read this thread and flash a new dirty build or a new AOSPA weekly (Probably the reason I chose AOSPA, so that I dont keep checking for updates, like I did for Vanir every day).

All in all I see very good progress here and hopefully on the 3.4 kernel thread (quiet=work being done). Thank you [MENTION=2838735]aosp[/MENTION] for making it happen. [MENTION=4608636]bsmitty83[/MENTION]

You have the wrong [MENTION=4544860]osm0sis[/MENTION] linked on the OP. :D
[Samsung Galaxy Nexus] scarcry:
for gnex I don't know of any. for mako (nexus 4) Stefano's AK kernel supports it (exposed via synapse) which I'm currently running.

Mako running LS on AK Exodus kernel
[Samsung Galaxy Nexus] osm0sis:
How about these?

http://m.imgur.com/tSeelbq,MURevfO

I cheated with the spacing in the CPU one by sticking an empty variable on the end of the string so it would parse the extra spaces. Pretty happy with the resulting pseudo-columns. :D

Working great here.. You tap on the value and it edits it on-the-line. Screenshot? :confused:
[Samsung Galaxy Nexus] gautam_nexus:
I am able to edit the values but the tick in the top s not coming and when I select another tunable to change the value of previous one changes back. :confused:

I am gonna reset synapse and do it again.
[Samsung Galaxy Nexus] osm0sis:
You have to press Done on your keyboard. ;)
[Samsung Galaxy Nexus] gautam_nexus:
Opps...I knew it that I was missing something. LOL. Thanks again.

I am testing Nephs Settings.:p
[Samsung Galaxy Nexus] osm0sis:
You may now uninstall Trickster. :cool:

http://v.ht/osmod
[Samsung Galaxy Nexus] DR3W5K1:
Wow your fast man. Looks good works good.

Sorry about earlier guys. I was in a bad place my dog at my stuff if you know what I mean.
[Samsung Galaxy Nexus] Ziyan:
Thanks, just woke and saw this :fingers-crossed:

Yeah well that was the reaction of most of my friends, now we're watching it together :p it's a completely new thing, not the old ****. With an awesome fandom, Example... another one, oh and another one :silly:
[Samsung Galaxy Nexus] metalspring:
Ubuntu 14.04 has only been out like 3 weeks and already a kernel update? Seems kinda soon, too bad we are nowhere close to that kernel version 3.13.0.24.29 vs our 3.0.101 lol (btw, I think the last decimal place refers to ubuntu specific changes)

FYI, also compiling a test kernel with all IVA overclock freqs enabled... Do NOT use if I post it unless you arent afraid of possible big issues- you have been warned lol
[Samsung Galaxy Nexus] DR3W5K1:
Pshh 1080 whatever... 4K here we come LOL

---------- Post added at 05:58 AM ---------- Previous post was at 05:56 AM ----------

If this goes wrong metal might be getting a new phone sooner than later
[Samsung Galaxy Nexus] metalspring:
Or you can test it, people would be unhappy if I couldnt make a final version of my rom because my phone died on a test kernel lol :P

(Btw, I really havent tested it yet but I will right now)

FYI, as said earlier, this may cause issues since it enables IVA frequencies that require voltage higher than what our phones are normally set up to use (although that may have been fixed by some commit at some point)

http://www.mediafire.com/download/j00csmetizict0r/SmittyV-NoMeM-5.3.14-IVA-TEST.zip
[Samsung Galaxy Nexus] DR3W5K1:
Wait where's that troll from the other day. We can make him a Guinea troll and get him to flash it

---------- Post added at 06:19 AM ---------- Previous post was at 06:10 AM ----------

I would test if I wasn't at work without a backup device
[Samsung Galaxy Nexus] metalspring:
Seems to work fine except for breaking smartreflex lol
[Samsung Galaxy Nexus] DR3W5K1:
Graphics benchmark increase?
[Samsung Galaxy Nexus] metalspring:
It shouldnt really effect graphics performance, IVA is more for encoding/decoding media like recording video, video playback, audio recording, audio playback, etc. So those might be smoother
[Samsung Galaxy Nexus] DR3W5K1:
Of I get a few free minutes I'll check it out. Would be awesome of it fixed the screen off audio lag/stutter
[Samsung Galaxy Nexus] Funnydwarf:
I did as you said and installed the resulting zip from recovery, as usual: the phone has booted and runs fine but I noticed that under > about phone the version shown is still the old one (I was using 27 feb dirtyv). Double checked with both zImage from DirtyV and SmittyV, same result. I'm a little puzzled because it looks like the old kernel is still here.
[Samsung Galaxy Nexus] ILA:
Could you please elaborate what you are trying to acomplish? :confused:

Isn't everything above working just fine?
[Samsung Galaxy Nexus] NeverSeparate:
It's the same result I had. He's aware of it.
[Samsung Galaxy Nexus] Funnydwarf:
woops I had missed that part, I was incorrectly assuming you were having bootloops, my bad ;)
[Samsung Galaxy Nexus] xxSAKISxx:
is just me or with ditryV 5/3 i have much much faster boot?
[Samsung Galaxy Nexus] aosp:
That posted about it ?
[Samsung Galaxy Nexus] ashclepdia:
OH YEAH(kool-aid man style)

Looks much better!

For the CPU, do u HAVE to report for each core? Well...I guess for those who use the mcps. I was thinking since they usually run same that u could just put one there... but nevermimd, looks great anyways, way better than it did
[Samsung Galaxy Nexus] danvrez:
[MENTION=4544860]osm0sis[/MENTION] does your current kernel settings apply for dirty?

because you have them since you where with f.kernel.

and there are your complete settings? because the kernel supports some more options like multicore power saving or suspend_trim (synapse)

i use your settings and my phone runs very fast :D and for the rest of the settings that you dont specify i use the ones that nephilim have in his thread but i want to set it fully in the way you have :P
[Samsung Galaxy Nexus] osm0sis:
Thanks for the interest! My settings here aren't anything too crazy. ;)

DirtyV-SR. Using Synapse:

Using f2fs on cache and data.

1350 Max, 230 Min, 230 Min Screen On.

All SR Highvolts on, SR Mins 725 MPU, 800 Core, 825 IVA.

384 GPU OC. -22 Trinity, 4 OMAP Gamma, 230 235 340 Multiplier.

westwood TCP CCA. 100 Vibration, 1 Headphone Boost.

1 Fast Charge. KSM enabled.

0 Swappiness.

All others are defaults.
[Samsung Galaxy Nexus] Ziyan:
I've enabled ambient temperature reporting in Cool Tool, but it's a bit buggy: it only refreshes itself if I do something that reads the pressure (for example, I start a barometer app) - so just like if temperature data calls would just report the last read temperature, and only pressure calls would refresh that temperature variable :rolleyes: or it is just Cool Tool bugging?

It's a pretty cool thing anyways - just turn off the phone, put it to a desk, and you get the current ambient temperature in 10 minutes (when the phone cools down) with 1 °C accuracy, according to my findings :good:
[Samsung Galaxy Nexus] danvrez:
Thanks to you, you are amazing!

i just suggest you to keep them updated in the link on your signature (http://xdaforums.com/showpost.php?p=34951507) ;)
[Samsung Galaxy Nexus] osm0sis:
Nah. That's only for f.K (it's in the f.K thread). ;)

I'll add a link to the above post in it somewhere though.
[Samsung Galaxy Nexus] osm0sis:
Tried to manually merge LMK donotkill back in today and failed. The crazy "ENHANCED_LMK_ROUTINE" in use hooks into the normal LMK in all the same places so it's beyond my skills to make them coexist. :(

[MENTION=4608636]bsmitty83[/MENTION] In case you didn't already catch it, I noticed some extra ~ files crept into your ramdisk again on 5.3.14, they're in the synapse directories. :good:
[Samsung Galaxy Nexus] bsmitty83:
You gotta come proper to hack my tuna Oz , lol ..

Yea I never added it back cause of that and I really didn't think it was necessary anymore

But I'm going to take a look at lmk again and see what I can whip up .
[Samsung Galaxy Nexus] osm0sis:
It's the only interface I built for Synapse that we don't have added to it currently, so it's been on my mind. :p

I'm going for 100% completion here ;):

Thanks Smitty. :cowboy:
[Samsung Galaxy Nexus] aeroxr1:
[MENTION=4608636]bsmitty83[/MENTION] now i'm using super RAM version , can this version of kernel lead problems to YouTube ? Or vevo ? I ask beacause i had a YouTube issue ( video didn't started) and after reboot the problem's has disappeared . is it a coincidence ? :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] JustinXu:
I love TouchControl too,that's the only reason i still stay with Mpokang.
[Samsung Galaxy Nexus] Nephilim:
Alright, so the Toro Liquidsmooth booted without issue in ART, unfortunately it was SOD city within a few minutes. I've tried 3 different governors and all still SOD after the screen is off within 2 to 3 minutes. Even the power, volume up and volume down buttons do nothing, a full battery pull is needed to boot back up. Josip Lazic, the person that built the Maguro version was helping out and building a Toro for us so we could try it out. Hopefully something he added might have caused the issue and once our normal compiler rkpeterson gets a new build up ART will work properly.

It has to be something with Toro because Josip has been using my kernel settings with the 4.7 Linaro DirtyV kernel on the Maguro version of LiquidSmooth since he flashed the rom and has not had a single SOD.

Sorry guys.

Also, sorry Smitty for hijacking your thread.
[Samsung Galaxy Nexus] bsmitty83:
NP , I dont mind OT at all .

sucks about your SOD issues with liquid , i havent had any issue with my vanir since I reverted art to a time I know it worked . im building right now since my computer is free ,

I havent messed with alot of setting in DirtyV but its running great
[Samsung Galaxy Nexus] Nephilim:
So you build the newest Vanirs but just change the ART settings back to how they were in the previous builds that worked for you?

I restored 1/18 Liquid and it's still rock solid, even using Interactive. Something still has to be in the newer builds that is causing this problem. At least for Toro.

I'm going to wait to see if rkpetersons official unoffical build works though before I make final judgment, since Josip Lazic has a Maguro and primarily builds for Maguro it may just be something he missed. Fingers crossed on that.

Either way, 1/18 is still running great with the new DirtyV Linaro!!!
[Samsung Galaxy Nexus] bsmitty83:
Yep I'm using art from 1/16 vanir and dalvik from UTEP's snappy dalvik , seems to be OK
[Samsung Galaxy Nexus] Nephilim:
Well if you are ever really super hardcore bored, you can take the ART settings from LiquidSmooth 1/18 and put them in a newer version. I hear that is simply the most fun a really super hardcore bored person could possibly have. Just sayin', it's what I heard.....

....don't judge me...
[Samsung Galaxy Nexus] Kaemo:
UTEP's dalvik? What is that? Never heard of that before.

EDIT: Ok, I know what it is now. But how can I install it?
[Samsung Galaxy Nexus] David 617:
can i get a link to that please? pretty please ;)?

i used to love vanir, but lately i've been having issues with it. just flashed 1/25 and i lose 4g every 30 seconds...

btw, your kernel is so buttery smooth that i dropped my phone out the second story window into the snow. i was trying to get reception and i just lost my grip. somehow it survived. now lets try that with an iphone lol.
[Samsung Galaxy Nexus] Nephilim:
Let's not try anything with an iPhone. ;) :p
[Samsung Galaxy Nexus] bsmitty83:
You can rebuild any ROM that uses cm based dalvik ( very useful to jellybean users since they have a jb branch ) by cloning their git and replacing the dalvik folder in your source . but I gotta find my vanir 1/23 its the one that works I misplaced it , otherwise I gotta rebuild . [MENTION=2853378]Nephilim[/MENTION] . I might just do that , I haven't built liquid smooth in a long time
[Samsung Galaxy Nexus] NeverSeparate:
Iphoney!
[Samsung Galaxy Nexus] Nephilim:
That would be real kick-ass of you man. :good:

BTW, I'd like to suggest you add a donation button below your avatar, you have been doing quite alot for everyone and although I'm really not in the money lately I'd be willing to donate a few bucks and I'm sure quite a few others would as well.
[Samsung Galaxy Nexus] pattyboi:):
you do everything dude holy sh*t
[Samsung Galaxy Nexus] bsmitty83:
I only accept donations from the thanks button . man , this is a hobby , I do it for fun and I want to keep it like that . people on here have donated enough to me in knowledge :beer:
[Samsung Galaxy Nexus] Nephilim:
Fair enough man, just wanted to suggest it since you really do alot. Working over in the 3.4 kernel thread, building these epic kernels with multiple versions etc etc.

Anyway, thanks a bunch man. The new DirtyV Linaro is running amazing! I just hope we can eventually figure out what the hell Mpokthws did to his ram to give such insane speeds. Looks like Osmosis and Metalspring have been looking into it.
[Samsung Galaxy Nexus] ahmadairfan:
[MENTION=4544860]osm0sis[/MENTION] said it could be possibly a work from boype's tweaked LPDDR timings. (look his post here http://xdaforums.com/showpost.php?p=42895372&postcount=2674)
[MENTION=4608636]bsmitty83[/MENTION] you could look at this https://github.com/boype/kernel_tuna_kk44/commit/5be729b004b5f4d76ba20e29aa952a091202a692 and my screenshot using mpokang v10

I know I have no idea what I posted, but thank you for your hard work [MENTION=4608636]bsmitty83[/MENTION]!! :D

Never been logged in XDA so may times lately just to keep up with this thread ;)
[Samsung Galaxy Nexus] bsmitty83:
If it is this commit , every kernel since boype authored it has used it , including this one . Its nothing new .
[Samsung Galaxy Nexus] swarlesbarkely:
Doubt it. I had the same issue with about 60% and a decent temp

Also, is there a significant difference between sabermod and linaro? Can't seem to find a good answer