yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] morfic:
Be careful with other sources, like even just recently someone who claims to know what he is doing for confused with the old 480 MHz and the current 487.5MHz, just because he seems to have missed that the math being the same, the different base clocks obviously creating different output....

Just paste your 533 MHz from the table with the pll you based it on, math either comes out to 533 or not.

Reason I'm curious? One frequency you can create is 520MHz (iirc), either way, it was lower and never stable, I stopped looking into voltages, so I'm curious, my experience together with theirs about no change to 487 noticeable has me even double curious.
[Nexus 4 Original Android Development] morfic:
Coming from Franco, dirty flash your rom (to get the rom's ramdisk back that Franco replaced) (also gapps if needed), then flash trinity and all will be fine.

Flashing straight over other kernels that replace the ramdisk can be problematic, when in doubt, the dirty flashing of the rom will always make it safe.
[Nexus 4 Original Android Development] simms22:
tf7c http://goo.gl/pKEeEF

its the latest one being tested in the thread. release kernels you can find at www.derkernel.com

then theres this guy..
[Nexus 4 Original Android Development] morfic:
While there is no "FSB", there are busses/interconnects on arm SoC that will affect the performance if they are changed.

Dude note: Thinking of cpu/gpu overclocking in terms of FSB and multiplier on arm can lead to mistakes, as usually you create a high clock from which you divide down (you may have noticed I mentioned that in my reply to Hartley up there)
[Nexus 4 Original Android Development] hartleyshc:
I am a dev by no means. Im just plugging numbers.

I will however do the math and see what I get. Just sticking in 545 over 533 gives me the same results as 487. running 667mhz gpu bandwidth at this speed.

Thanks for the lesson. Always appreciated. :good:
[Nexus 4 Original Android Development] siddharthbball:
si dirty flash means installing om again ?
[Nexus 4 Original Android Development] simms22:
yes, but without wiping anything.
[Nexus 4 Original Android Development] albundy2010:
Just reflash the rom right over top. Flash kernel and reboot. CM backs up your gapps when you flash a rom ( as far as I know they still do at least)

You don't have to "install" the rom. That term can mean anything from a full wipe and a fresh install to who knows what else.

Dirty flash means just flash zips right over what's there and reboot. Nothing else needed. .
[Nexus 4 Original Android Development] hartleyshc:
So 533Mhz GPU is BS.

Its using pll15 (97500000) 1 , 2

97500000 / 2 = 487500000 or 487.5

Again, thanks for pointing me in the right direction. Came across a rant from faux, and it filled me in quite a bit on how to correctly overclock the gpu.

:good:
[Nexus 4 Original Android Development] simms22:
sorry but last photo of the night, i swear :angel:

ethereal beast in blue..
[Nexus 4 Original Android Development] morfic:
Yeah Chad Goodman was ragging on him when actually Chad Goodman was making the mistake he so high and mighty likes to accuse others of.

Now he has his bandits go around cry wolf about people not pushing she for......hold on.....a whole, solid......two..........DAYS......

Poor GideonX, what a frivolous claim, if they were truly interested in gpl violations, they would go after hisense USA who has yet to publish since for the tegra 3 tablet they sell at Wal-Mart.

Two days "late" vs no source at all....

Well, it's not about the gpl at all, Chad Goodman is just butt hurt that he is banned from xda and somehow thinks his hiding behind "private releases only, not public" bullshít makes him a good guy, fúcking please, it's shady, like corporations using loopholes on their profits to not pay taxes being legal still are shady.

Edit: yes,I speak in anger, because out of all the people they could pick, they had to get on GideonX, they're were other, bigger names that more than once his their innovative features for weeks, even preferring their thread gets closed before "giving up" their code (that they are legally required to present), losing their "RD" over offenses, but not getting banned, I can see how it can be frustrating how inconsistent xda applies rules.....But pick on the right guys, those who intend to hide code, not those who wait two days to be sure all works well before they commit and then have to revert if it doesn't.
[Nexus 4 Original Android Development] albundy2010:
Sshhh you're going to get in trouble for saying that name. Bad morfic. Bad boy

---------- Post added at 07:31 AM ---------- Previous post was at 07:20 AM ----------

And I see they're talking about you too
[Nexus 4 Original Android Development] Kocai:
Edit: never mind

Sent from my Nexus⁴
[Nexus 4 Original Android Development] hartleyshc:
[MENTION=1122306]morfic[/MENTION]

Well I wrote down all the PLLs and their values and did the math.

533 (533.333) is a valid speed, I searched through several sources, and all the ones I came across have the wrong pll settings. They all just did what I did and put 5330 over 4875, or added an additional line without changing the pll settings.

Someone has to have the right settings, or how would they even get the 533 number?

After looking through like 5 gits, I couldn't find anyone who had it right, so here it is.

F_GFX3D(533333000, pll2, 2, 3),

800000000x2/3=533333000

Changed the settings in clock-8960.c and in board-mako-gpu.c

Is there any additional places to make changes? I'm testing using performance in trickster, but it seems Im still getting similar benchmarks as on 487.5

Running 1.5/1.5, performance, thermal off, hotplug 4/4. Just so the gpu is the only variable.
[Nexus 4 Original Android Development] morfic:
They are now?
[Nexus 4 Original Android Development] morfic:
Are you at max fps on basemark taiji yet? If not, it's quick and heavily gpu dependent for testing.

It's sensitive enough to pick up any small real changes.

What test do you use for gpu oc checking? (Don't say quadrant or I'll have to slap you (no really,I can't refuse to do it, it's a requirement))
[Nexus 4 Original Android Development] SpaceCeph:
Simms, for me governor was set to ondemand, and there was no scaling. Is this the recommended one?

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] simms22:
no scaling?
[Nexus 4 Original Android Development] albundy2010:
On demand is default. Not scaling is not.

Make sure a app isn't setting the cpu settings to the same min and max. Default is not that way.
[Nexus 4 Original Android Development] californicated:
Maybe he means the phone mostly uses min and max freq
[Nexus 4 Original Android Development] hartleyshc:
No, not quadrant. Its all fun to break 10k, but for testing gpu its always been worthless.

Been using just the gpu test of antutu 4, and their separate 3d ratings opengl 3.0 test. i also use 3d rankings, but for this test, its a bit too long.

will check out taiji.
[Nexus 4 Original Android Development] SpaceCeph:
Problem is that it uses only max. I am on my way to university so the massages are a little bit short...

Gesendet von meinem Nexus 4 mit Tapatalk 4

---------- Post added at 09:45 AM ---------- Previous post was at 09:44 AM ----------

I use tkt, min max settings are OK.

Gesendet von meinem Nexus 4 mit Tapatalk 4

---------- Post added at 09:46 AM ---------- Previous post was at 09:45 AM ----------

I use tkt, min max settings are OK.

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] spupuz:
is that only for jss and not for jwr?
[Nexus 4 Original Android Development] superbobup:
True. I just meant that (I assumed) most of the performance increase was from physical/design differences rather than higher speeds with the same design.

BTW, did you major/focus in EE for your studies? I always assumed you worked in a field with more of a mechanical background. Just wondering, as I need to strengthen my design background, so it's kind of cool whenever I see other people talking about stuff like this :D
[Nexus 4 Original Android Development] Detailed:
Try using GLBenchmark as it reports how many frames were rendered as well as the frames per second. Antutu 3Dbenchmarks always fluctuates for me while GLBench doesn't. I tried 533mhz/487mhz on neo and all I got was either 970-971 on off screen for the TRex one on both frequencies. No thermal throttling + Used 1.7ghz @ 4/4 to ensure no cpu "bottlenecks". Used performance governor for everything too. *Kernel used was neo 012*
[Nexus 4 Original Android Development] qu3becker:
That'd be very interesting when taking picture with the Nexus 5.

http://www.phonearena.com/news/Nexu...t-on-a-phone-Lytro-like-functionality_id47900

I just wish the MPs would be a bit higher this time around but taking better picture, quicker than any phone around is really great and it may result in better picture than the iPhone 5s or the SGS4. Always focused photos: how great is that?!
[Nexus 4 Original Android Development] Karo.:
well. installed the last version TF4h-4.3 on CM10.2 last nightly (cm stock kernel)

in screen all red color appears as blue -_- !

screen bug after unlock screen , opening apps and .. means after touch app icon and while it gets open

flash 1 more time.. no change

flash rom 1 more time then flash kernel .. no change

WTF goez wrong?
[Nexus 4 Original Android Development] simms22:
sounds like you have some color options enabled in cm..

and whats your bug afrer unlocking? your issues here are all most likely user related, since you are the only person ever to report this issue. and tf4h isnt the latest, search the thread for tf7c.
[Nexus 4 Original Android Development] TheDarkDefender:
These issues are cm related only.

Cm has switched to implementing caf kernel and caf media drivers which is conflicting with Trinity, since it doesnt include these patches. Hence the weird colors. The entire forum is going berserk over this. Aokp and Carbon have adapted to cms way too. Your colors will be fine with stock cm kernel. Rest others will cause issues.

Cm is no longer using the aosp kernel source like it used to.

Sent from my Nexus 4
[Nexus 4 Original Android Development] morfic:
I'm a journeyman machinist, while the education included things like electro hydraulics/pneumatics that we based electro mechanical systems on to pass (we also used logic controls in school), my real secret weapon might just be my age, my first pc motherboard required me to pull the 16MHz quartz and replace it with a 20 MHz quartz, I always had to make sure I research what I want to manipulate, so I know how to manipulate it.

Kernels were similar, when I started building my first kernel, something like 18 years ago, I had to learn what to do to get what I wanted, learn from the "well, that didn't go as promised at all", some of the things I do to the kernels now I really didn't realize until the dawn of 64 bit computing led me to test where what optimizations are applicable and where they don't make a difference.

Same again when I worked for gentoo on various architectures, I built for arm long before my first android phone.

Long story short, my background is not in EE, but everything I do now I picked up years ago, before most other xda guys installed their first Ubuntu in vmware/virtualbox recently.

I know what I know only because I like to do things right and learned stuff for longer than some of those guys are alive.
[Nexus 4 Original Android Development] Karo.:
nope no color options enabled.. all stock cm rom and kernel

flash tf7c .. no changes ! still screen flicker and no red color:eek:

seems trinity makes something wrong on cm

maybe a trinity kernel for cm base roms works better:confused: tanx at all
[Nexus 4 Original Android Development] simms22:
its more along the lines as cm does something wrong for trinity. actually, ill restate that, cm does something wrong for the android modding community. since they are now a private company, they are looking to make money, not to improve android for the benefit of android. there wont be a trinity kernel just for cm.
[Nexus 4 Original Android Development] eminembdg:
This sucks. Why did they have to mess with crap.

Screw you cm.

Off to another Rom now.

Any suggestions?
[Nexus 4 Original Android Development] zygis10:
PSX
[Nexus 4 Original Android Development] eminembdg:
Cool, downloading now thanks
[Nexus 4 Original Android Development] simms22:
just so you know, psx is a jwr rom.

and you know my suggestion, if psx doesmt do it for you, rasbean :)
[Nexus 4 Original Android Development] albundy2010:
We had a stand off.
[Nexus 4 Original Android Development] simms22:
i see the feline won.. :silly:
[Nexus 4 Original Android Development] morfic:
This is going to get messy, considering how many roms are simple cm derivatives.

Sure,I get it, you gotta do what you gotta do to make your non nexus devices perform its best, but if anyone dares say again that cm doesn't break nexii just to break them, I'm gonna flip.

You have full source from the device manufacturer, yet you switch to sources from the SoC manufacturer for no reason other than to entertain yourselves?

Go fúck yourselves.
[Nexus 4 Original Android Development] Mantulis:
I know right, fùcking mind blowing!

I was biggest fan of CM. Fùck you CM and CAF'S bullshet. Enough is enough.
[Nexus 4 Original Android Development] albundy2010:
At least now people don't need to accuse them of stealing caf code and claiming it their own anymore I suppose.

Edit. Damn app /server
[Nexus 4 Original Android Development] californicated:
Omg..

Had a reboot while using the phone for navigation. Forgot my pin --> ****ed up three times, had no phone the whole day

..:silly:

No log, already rebooted several times. Flashed TF7c :)
[Nexus 4 Original Android Development] albundy2010:
It was a draw. After I took the photo I went up and petted the cat.
[Nexus 4 Original Android Development] deani77:
As for now Vanir ROM played well with Trinity Kernel even it use some of it source from CM. Maybe I need to look for another alternative if Vanir become incompatible with Trinity.
[Nexus 4 Original Android Development] trillo69:
I think I've missed something about CM, can anyone point me to any additional information?
[Nexus 4 Original Android Development] stark_br:
Try this.

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

:thumbup:
[Nexus 4 Original Android Development] morfic:
And I even had to reply to that post
[Nexus 4 Original Android Development] trillo69:
:eek: That sucks, hardly. What's the point of screwing with one of the best things on nexus devices (compatibility)? They are doing it really wrong, even my brother that was a hardcore CM fanboy has moved to other roms because of CM going licensed. I can't see this move causing a different reaction.

I'm glad to see some respected developers making a statement against this.
[Nexus 4 Original Android Development] morfic:
If cm chooses to turn their backs on the community already, then as of right now I have no plans to support their financial endeavors.
[Nexus 4 Original Android Development] hartleyshc:
So after tons of tests, I can confirm 533 is not stable. I get sub 400mhz performance.

I'll try the next one up, (576iirc) but I'm not expecting much. I'll test 576 and 600, but it seems like 487.5 might be our max GPU speed.

[MENTION=1122306]morfic[/MENTION], I forget the file, but the one that controls the BUS. You have the second 533mhz bus commented out, the source I'm building on labels this as 667mhz and is using it as power profile 5. I've tested 533GPU on both bus speeds and get the similar shìtty results. Can you confirm this is actually a 667mhz bus when used?

Edit: its acpuclock-8064.c
[Nexus 4 Original Android Development] morfic:
U

I commented it out because the bump wasn't pretty, things ran like shít with it in use, with our without adjusting the highest vector to match.

Since it worked fine I sgs3 it should work, but it's still on my "list of things to check again later"

Just divide the first value by 533, then divide the second "533" bandwidth by that number instead of asking me ;)

(I don't have memorized what my last attempt was before I commented it out)

Hmm, I never tried (or don't remember if I did or not) just increasing the last one instead of adding one (usually a good idea to make sure there is not something elsewhere involving the index that would have to be adjusted with a changed array)

Edit: you caught I said you'd have to increase the vector to match that bandwidth, right? For gpu usage
[Nexus 4 Original Android Development] hartleyshc:
Much thanks for the lesson. Your help has been indispensable.

BTW, mentioning old Linux users, my first use was redhat back when there was only redhat. We used it cause my company was too cheap for windows licenses. We were a dialup isp, and we had a huge screenshot webpage made for tech support. My first distro I installed myself was Corel Linux, because of the super easy installer.

I'm a bit younger than you, so these were machines that was were powerhouses compared to what you started with. The most difficult thing I ever had to learn to use a computer was IRQ numbers.

---------- Post added at 09:07 PM ---------- Previous post was at 08:43 PM ----------

@morfic

yes I noticed you said to increase the vector to match, and yeah I noticed in your code just replacing the last one. I assumed it was because of why you mentioned.

Also looking at the code I'm basing on, and looking at yours, I think I'm going to say screw jwr and switch to trinity for a base. I've already found things that look tacked on and things that don't make sense. Like 2 exact if commands with two different values in each one. Like a copy/paste gone bad.

If my questions ever get too much, feel free to PM me and tell me to piss off. I'm a big boy, you won't hurt my feelings. But your simple concise answers help me quite a bit. I might not be able to code for shìt, but I learn really easily, and I can Google and read more into detail elsewhere.
[Nexus 4 Original Android Development] Ticiano:
Just flashed. Using stock 4.3. My screen tremble like Michael J. Fox going downhill racing an uncontrolled supermarket car. I'm scrolling app drawer and getting this earthquake effect since flashed. Anyone know how to handle this problem?
[Nexus 4 Original Android Development] hartleyshc:
Simple answer. You are using a JWR rom, and this is a JSS kernel.

Flash this to fix.

https://docs.google.com/file/d/0B_2NNDoNW6ejenlZZXdSTDRjOVE/edit?usp=sharing

You can also go into developer options and disable hw overlays, and force gpu 2d rendering.

Your choice.
[Nexus 4 Original Android Development] simms22:
thats what you get for flasing a jss/jls based kernel on a jwr rom :p

two ways to fix it.. go to the phones main settings, dev options, and disable hardware overlays. this works but you have to do this after every reboot. or, there is a flashable floating around so you dont have to do this. when i have a chance, ill link you..
[Nexus 4 Original Android Development] Kocai:
simms, are you using the latest build of Rasbean? The JLS36G build? I've been testing jarjar24 test build and much to my surprise, haven't gotten any deadlocks (hopefully not) since I flashed it. So I was wondering if it's the same with Rasbean.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] morfic:
Few quick notes, there never was "just redhat" ;)

Your own initiative, keeping me from spoonfeeding you will keep me from telling you to piss off.

And helping you might help me think about stuff that might turn into good things.

And it might actually improve my motivation which is at an all time low.
[Nexus 4 Original Android Development] simms22:
yea, im using the last. yea, i still get an occasional deadlock, not often.
[Nexus 4 Original Android Development] lazer155:
I just came from stock 4.3's kernel to trinity 4. I've noticed some kind of weird ripple/jagged effect when swiping through the app drawer or home screen. I'm not exactly sure how to describe it so I can't search for it in this thread. I guess it's somewhat like graphics tearing. Does anyone know what might be happening?
[Nexus 4 Original Android Development] simms22:
6 posts above yours :silly: http://xdaforums.com/showpost.php?p=46123879&postcount=23689
[Nexus 4 Original Android Development] lazer155:
:o I completely skipped over that post reading back. That would be the problem. I'll try applying the fix. :good: Is there a revert zip in case I want to go back? Otherwise I assume I would have to reflash my rom and wipe.
[Nexus 4 Original Android Development] albundy2010:
The state of hardware and how smooth the device runs stock probably plays part in being motivated too.

The old days when things were slow there was the craving for more speed. Now with a s4 pro and later that isn't there. UI is not going to be lagging etc. Except if you're running a Samsung octa fail chip. Those would require a constant tinkering to try and undo as much Samsung stupid as possible. Even then it would still be stupid.
[Nexus 4 Original Android Development] simms22:
reflashing your rom without wiping should revert it.

---------- Post added at 01:02 AM ---------- Previous post was at 12:56 AM ----------

i remember the older days, and how people wanted more speed. and how blind many were, leading us to where we are now. back then i was busy breaking benchmarks, showing them how imperfect they were http://www.engadget.com/2011/06/21/nexus-s-hacked-and-tweaked-to-slaughter-benchmarks-reality-be-d/
[Nexus 4 Original Android Development] lazer155:
It runs perfectly now with that tearing fix. Do you have a preferred tuning app like System Tuner pro or Trickster? Or do you make all your changes manually like in your signature?
[Nexus 4 Original Android Development] simms22:
i need to edit that link in my sig, its a bit outdated now. i use the trinity kernel toolbox app(for the majority of my kernel needs), root explorer, and occasionally the terminal emulator :)
[Nexus 4 Original Android Development] lazer155:
I forgot there was an app specifically for trinity. I'll give that a try. It's an awesome kernel by the way. :D
[Nexus 4 Original Android Development] albundy2010:
Not much has changed in that reguards really. Main difference is you didn't need a series of benchmark tests to know that a custom kernel performed much better on that device. Especially after gb.

If you ran stock ice cream sandwich or jellybean on the Nexus S and switched to a custom kernel with bigmem.... I even remember Franco ranting about the galaxy Nexus when it first came out. It runs like bleep. I hate this thing. It improved later with a update but still. That out of the box this sucks, why is this lagging is gone. At least on Nexus devices everybody not Samsung.
[Nexus 4 Original Android Development] simms22:
right :)
[Nexus 4 Original Android Development] davidbar93:
Sorry for this question but I don't have too much time to search it... What is the latest kernel version of this one? It's compatible with JWR roms also?

Thanks!

---------- Post added at 08:49 AM ---------- Previous post was at 08:48 AM ----------

Sorry for this question but I don't have too much time to search it... What is the latest kernel version of this one? It's compatible with JWR roms also?

Thanks!
[Nexus 4 Original Android Development] Teadious:
Is tf7c already undervolted?
[Nexus 4 Original Android Development] simms22:
in a certain sense, yes.

------------------------

looking down, in blues..
[Nexus 4 Original Android Development] morfic:
Not the cpu voltages, they are stock for the frequencies that exist in stock.

Other voltages were dropped
[Nexus 4 Original Android Development] original21:
Hi Simms & Morfic. I just wanted to say thank you for all the support you gave me with all my nexus devices. Trinity was and will always be my favourite kernel.

I just received today my new HTC one. I only hope that one day Trinity will share its love with the HTC one.

I will be in touch. Take care my friends! :)