yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Metallice:
It is the LP core. Your device can't handle it. YouTube for example uses the LP core exclusively, mostly at max freq. I'll have to release a lower clock for those with wimpy chips.
[Nexus 7 Android Development] MrDrift42:
Is it possible to do something similar to the gpu where we can set it manually? I wonder at what point it starts acting up. The weird part is that I've run your lp overclock a lot longer than I've had the problem with youtube. It's only started since 4.2. Wonder if something isn't playing well together. Also why would switching governors fix it if the LP core is at max freq either way?
[Nexus 7 Android Development] nextelbuddy:
What do you mean those with wimpy chips? Don't we all have the same chips with the nexus 7?

I am using #a15 and I'm getting a pause and buzzing sound a lot in YouTube and other videos in MX player. I'm totally stock not rooted and temp booted into twrp using wug fresh toolkit Just to flash the kernel as well.

Which kernel should I be using to avoid this? And why would some nexus 7 not have this issue vs others? Do some people have different chips or cores?
[Nexus 7 Android Development] Stuphologist:
A17 seems to be inop with AOSPA beta 6. Hangs on boot. I'll try A16 next.

Update: A16 boots. Tried A17 twice, wiped caches both times, no joy. But A16 worked fine.

I know ironing out these inconsistencies with the ROMs is a pain, especially with everyone adjusting to Google's big shift with 4.2. Thanks again, many thanks again, for all your work.

Dave
[Nexus 7 Android Development] Metallice:
No, every chip is unique in its capabilities and tolerances. That's why some people can overclock to 2.0GHz and some can't get up to 1.5GHz. If all chips were the same there would be no such thing as overclocking as all chips would have the exact same maximum possible frequency, and they would be set to that by default. The same thing applies to the LP core.
[Nexus 7 Android Development] Metallice:
Maybe for you and your chip. Using PA beta 6 right now with a17.
[Nexus 7 Android Development] Stuphologist:
How? I didn't oc the GPU and a post just a little while ago (not you) said that the A17 default is 446, same as the A16 I'm running now, and I ran A14 520/620. Also, until beta 6 came out I was running A17 on AOSPA beta 5 with no problems.

It would be fairer to say that AOSPA beta 6 broke your kernel - at least for me - than the other way round, and I'm reporting that on their thread when I get done reloading gapps.

Dave
[Nexus 7 Android Development] xfrancis14:
This kernel will still be continued right?
[Nexus 7 Android Development] _motley:
Thanks for your help and hard work on the kernel bro! Glad you were around to "keep the dream alive" as another stated. I'll look through the commits you did on github when I have time. Trying to figure out what I want to do next as I have some time. Looks like the devs have been busy and coming out with some good innovations (usb charging, gpu control etc.).

One quick question...whats the gig with the audio cracking patch? I have never had an issue with that (knocks on wood).

Cheers,

motley
[Nexus 7 Android Development] EvanA:
Metallice, will you be providing support for the next version of multirom? Details here: http://xdaforums.com/showthread.php?p=34897653

Sent from my Nexus 7 w/ PA and m-kernel
[Nexus 7 Android Development] MrDrift42:
No problems here on a17 and beta 6. Works flawless for me.
[Nexus 7 Android Development] EvanA:
A16 620 worked fine, so maybe that's the sweet spot.

Sent from my Nexus 7 w/ PA and m-kernel
[Nexus 7 Android Development] Kearkan:
Running a17 with pa beta 6 and its running perfect.

First flash caused 2 hangs (had to hold power button to force a restart) but after a format and reflash of everything its all sweet.
[Nexus 7 Android Development] R3dbeaver:
A17, 600 GPU made some improvements on Shadowgun palace level, ultra high.

But too hot my liking battery sucks. About 10% for a couple of rounds?

Going back to 575 and High settings.

PS: no issue with YouTube here.
[Nexus 7 Android Development] Metallice:
Thank you and you're welcome. Not entirely sure to what patch you're referring. There was an intermittent issue with audio popping on unlock and losing sound... but google fixed it. The problem would arise randomly with no specific change causing it.
[Nexus 7 Android Development] Metallice:
Why wouldn't it be?
[Nexus 7 Android Development] Metallice:
LP overclock. 666MHz up from 475MHz
[Nexus 7 Android Development] xfrancis14:
Idkk I was worried it would since motley is back, but thank you so much for this kernel its by far my favorite kernel and I would hate to see it end
[Nexus 7 Android Development] Metallice:
At this point it's a whole lot more not motley than motley.

Originally I was going to keep it similar but I guess I got carried away...
[Nexus 7 Android Development] xfrancis14:
Ohh I see, I really like this kernel I've only tried stock Franco and this but this is definitely the best in my opinion can't wait for more updates
[Nexus 7 Android Development] Metallice:
You forgot to add "for me" to the end of that sentence. I have no issues up to 700MHz.

Next release will have LP max options.
[Nexus 7 Android Development] xfrancis14:
Quick question does this kernel support otg? Cause i ordered one off amazon today and it should be arriving in about 2 weeks so I wanna know if I'll be able to use it with this kernel
[Nexus 7 Android Development] laill:
Sigh...... I always press the thanks button accidentally.

OTG us working great, for usb flash drives, mobile HDD and xbox controller

Cheers,

L
[Nexus 7 Android Development] Fallon9111:
Awesome!

Nice one XD

Thanks, keep up the excellent work :D
[Nexus 7 Android Development] olgunozcan:
my nexus has 4.2.1 stock rom and rooted.

can i flash this kernel?

this kernel support usb otg (fat32, ntfs r/w) ?
[Nexus 7 Android Development] Stuphologist:
OK, I'll try that next.

Dave
[Nexus 7 Android Development] Kastytis75:
So the problem with display flickering did not sloved in last version too :(
[Nexus 7 Android Development] Billchen0014:
+1

Xxx oops! accidentally beamed from my awesome NEXUS S! xxX
[Nexus 7 Android Development] Metallice:
Anyone interested in a custom UV interface for GPU, LP core, and RAM? :D
[Nexus 7 Android Development] mishko:
Bring it! :)
[Nexus 7 Android Development] Metallice:
Haha that was quick. FYI that question was kind of rhetorical... but I'm going to assume you knew that. :)

Aaaaaaand it's up! :)
[Nexus 7 Android Development] mishko:
Thank you, sir!
[Nexus 7 Android Development] sert00:
i'm one f the beta testers of trckster,if you want i can ask the devs to add uv control for companion core...
[Nexus 7 Android Development] 850T5m:
Would be great!

Sent from my SGH-I747
[Nexus 7 Android Development] Metallice:
Why just the companion core? What about RAM or GPU? But thanks that would be great.
[Nexus 7 Android Development] 850T5m:
Metallic, stupid question, since we can OC the companion core, the main cores and the gpu, is it possible to OC the ram? :)
[Nexus 7 Android Development] Metallice:
Not a stupid question at all. You'd think it would be possible, but not currently. The RAM frequency tables are hard coded on the chip and read from on boot... unlike every other frequency table...
[Nexus 7 Android Development] 850T5m:
Ah that's too bad lol

Thanks!
[Nexus 7 Android Development] Metallice:
Yes. That's why I clicked thanks the last time you posted this.
[Nexus 7 Android Development] EvanA:
Definitely forgot I posted that already. :D Sorry!

Sent from my Nexus 7 w/ PA and m-kernel
[Nexus 7 Android Development] azoller1:
I tried flashing this on pa beta 6 and it got stuck at the Google loading screen, but leankernl 0.8 works and i also wiped cache and dalvik and tried not wiping ideas?
[Nexus 7 Android Development] Metallice:
Haha no worries. I'll add it soon.
[Nexus 7 Android Development] Metallice:
Did you try both versions?
[Nexus 7 Android Development] T41NT:
What is a good benchmark application? I have been using quadrant and getting 5300 for a score.
[Nexus 7 Android Development] Sultanxda:
Antutu
[Nexus 7 Android Development] T41NT:
I just got my first freeze up and reboot running the a18 666. Going to the lower one now...
[Nexus 7 Android Development] T41NT:
I've been using nofrills cpu to OC, any recommendations on a better, more in depth app?
[Nexus 7 Android Development] rebel1699:
Exactly what will this consist of? I only ask because I am running your kernel and using multirom to dual boot ubuntu just fine as is. Is there something else that needs to be done? Sorry for my ignorance on this.

---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------

Trickster Mod is really nice. System tuner pro would be my second choice.
[Nexus 7 Android Development] Sultanxda:
Metallice, what files do I modify in your source for pixclock and CPU frequencies? I'm terrible at finding files :silly:
[Nexus 7 Android Development] Metallice:
Why would you ever want to do something like that anyway?
[Nexus 7 Android Development] Metallice:
*shrug* there's a patch. And it can't hurt to add it.
[Nexus 7 Android Development] rebel1699:
Rofl, thats as fair an answer as I could ask for. I could only think maybe something when flashing it to a secondary rom. Thanks metallice.
[Nexus 7 Android Development] MrDrift42:
Tried the new 550 lp and I'm still having this issue while using on demand. It sucks because battery life isn't so good with interactive but the audio issue is annoying.
[Nexus 7 Android Development] Metallice:
I can try a stock LP version... But it is looking like something else might be to blame... I wish I could replicate the problem myself :(
[Nexus 7 Android Development] Sultanxda:
The pixclock overclock made my UI and games MUCH MUCH smoother. The lack of pixclock overclock is driving me crazy and now that I've successfully made a kernel for my phone I want to try making one for my tablet.
[Nexus 7 Android Development] Kearkan:
I'm noticing something interesting.... Running a18 666lp, and when I try to oc the GPU over about 600 it just locks up.

On a 17 it would go all the way to 700 no trouble =S

Surely the LP wouldn't affect that? If
[Nexus 7 Android Development] nphil:
I have the same issue, I'll try and grab a logcat/kmsg. Can't really go above 600mhz GPU either, while I can on Trinity kernel. Possibly a voltage issue? I just noticed that you added a voltage table for the GPU, the default 1600mv for 700mz doesn't seem to work, perhaps a 50mv increment? If only I knew what the default voltage for trinity was..

---------- Post added at 08:08 AM ---------- Previous post was at 08:04 AM ----------

No offense, but are you sure it's not placebo? I think the tablet's screen is limited to 60hz, so you wouldn't really be seeing any improvement in UI or game framerates with a pixclock overclock.
[Nexus 7 Android Development] Sultanxda:
It is most certainly not a placebo (I can easily tell without fail when there is a pixclock overclock and when there is no pixclock overclock) and the pixclock IS the refresh rate of the screen, so a pixclock overclock would increase the refresh rate beyond 60Hz. Since the Nexus 7 hits the 60 FPS (at 60Hz) ceiling quite easily with most tasks and with rendering the UI, having a refresh rate of 60Hz, in my opinion, defeats the purpose of overclocking the GPU to insane speeds. What's the point when you can't even see the full extent of the speed increase?
[Nexus 7 Android Development] nphil:
The UI already runs at 60fps, but I doubt the hiccups you see are related to hardware performance, I think it's mostly a matter of software optimization, as seen here http://www.curious-creature.org/2012/12/01/android-performance-case-study/ Also about the refresh rate, it's a hardware limitation, so raising the refresh rate would do nothing.

As to answer your question on GPU overclocking, its useful because demanding games like Horn, Dead Trigger etc. do tax the GPU on the Nexus 7, with average frame rates of around 20-22 depending. After overclocking my GPU to 700mhz, I've noticed improved frame rates, though nowhere near 60fps. As long as you don't hit a frame rate cap on games, a GPU overclock is always helpful.

But hey, I guess an option to overclock the pixclock wouldn't hurt?
[Nexus 7 Android Development] poondog:
Isn't the refresh rate a hardware limitation not a software thing? Would you even be able to tell the difference anyway?

Sent from my Infected ViperVivo
[Nexus 7 Android Development] Sultanxda:
Increasing the pixclock does not increase performance but it makes it more visible (at least for me). Pixclock overclock won't make a difference for games that are that demanding (since it can't hit 60 FPS), but for things that are not demanding in the least (such as rendering the UI) you can see a difference.

Slap me if I'm wrong, but the pixclock is the refresh rate (what else could it be?). Saying it's a hardware limitation would be like saying CPU and GPU clocks are a hardware limitation (RAM speed, however, in the case of the Nexus 7, is a hardware limitation, but that's different). And yes, for me there is a night and day difference between having a pixclock overclock and not having a pixclock overclock.
[Nexus 7 Android Development] laill:
Report:

The a18 kernel is running perfectly fine here, much smoother here. Will keep an eye on the battery:laugh:

Running at 666-1200 MHz for CPU, 580 MHz for GPU.

Stupid questions:o

Is lagging normal when scrolling in the Widgets list in the stock launcher?:(

How can I test the maximum bearable GPU and RAM frequency? Step by step to increase and run benchmark several times to see if it reboots?:cowboy:

I guest lots of tester would like to know how we can push to/break the limit.

And sorry for being a noob to ask this, but about linaro tool chain, it is not used to compile the kernel, I guess. Would it be a good idea to use it?:o

Once again thank for your work, you kernel is marvelous.

Cheers,

L
[Nexus 7 Android Development] Metallice:
The screen is limited by 60fps as a hardware limitation. Having the device render 70fps will not be visible as the screen itself can't display that many frames per second. The GPU will be producing the frames, but the device won't be showing them to you as it physically cannot.

You can't "see the difference" as it is physically impossible.

But I can't stop you from doing it. The value is in board-grouper-panel.c. Placebo may be all in the head but if that placebo makes you enjoy your device more, I'm not going to try to stop you.
[Nexus 7 Android Development] Metallice:
1) depends on a million other factors. Smooth for me with nova, but you can always switch to interactive.

2) you can't change the RAM frequency. You can test your device's GPU tolerance like you describe.

3) I am already.
[Nexus 7 Android Development] Metallice:
At 600 the voltage increases. It is probably is conflicting with the new custom user voltage interface for the GPU added with a18. Now that GPU voltage should be user controllable, there is no reason for the voltage to be automatically increased at 600 anyway. I'll just remove it and all should be fine.
[Nexus 7 Android Development] laill:
1)I did have a try, but almost no different:(

2)I guess I mean the voltage of RAM, as you mentioned that the frequency is hardcoded:o

And for the emc_UV_mV_table, There are only three frequencies and each one appears several times?

3)We are also ready to test sir, all the time!

Today I even flashed m18 when I was waiting to present my project

Cheers,

L
[Nexus 7 Android Development] Metallice:
I meant I am already using the linaro toolchain

And yes frequencies appear multiple times. Its how nvidia does it. Hard to explain.

Also why would you set your min to 666MHz? Do you have something against decent battery life? The frequency ramps up to 666 on touch anyway.
[Nexus 7 Android Development] laill:
I raised the min frequency to 666 because I have lots of background apps running and I can plug my devices most of the time, so I keep killing the battery......Just to ensure I can use the device smoothly:o
[Nexus 7 Android Development] jombo2323:
Hehe you guys are both wrong. The pixclock being the fps limiter, would cause the GPU to skip or not draw certain frames...... So.. Let's say you get 60fps on the home screen. When you scroll it drops down to 50. The pixclock might be telling it to not draw some frames to keep the fps right, causing it to drop multiple unfinished frames causing the lag spikes. Turning up the pixclock would just give it a 10 fps buffer. Its kinda like vsync causing games to lag
[Nexus 7 Android Development] Metallice:
Not really. I was referring to benchmarks like quadrant whet you could get fps scores like 70. These gains are imaginary. Also your description is either completely incorrect or not described well. Not sure.

And the pixel clock rate isn't vsync. It doesnt tell anything to do anything at all. Please don't tell people they are wrong without understanding what you are taking about. I.e. not vsync. Its more accurate to say it is the maximum bandwidth of the display. It doesn't let any more than 60 frames go to the display per second. Which is a good thing.

This theoretical buffer or drop to 50fps will never happen as you describe it. It will just stay steady at 60fps as long as it can handle it.

You could have just started with "From my understanding..." or similar, but, no, you decided to go with the condescending "hehe you guys are both wrong"... I just don't understand people sometimes...
[Nexus 7 Android Development] SpikeySpy:
Just wondering, i have currently flashed my kernel to m-kernel a18 and whenever restart after using android tuner to configure the cpu freq. to 1.6ghz it will be reset to 1.3ghz again.

Why is that the case?
[Nexus 7 Android Development] Stuphologist:
The screen refresh rate is fixed, but even if it wasn't your brain can't process frame rates above 30 or so FPS. Running LCDs faster than that reduces persistence blurring and screen driver processing artifacts, and is a step toward 3D (maybe), but has no effect on the perceived framerate as such. If you're correct when you say you can reliably detect pixclock overclock, and I'm not saying you aren't, I wonder what that overclock is doing, and what you're actually detecting.

Dave
[Nexus 7 Android Development] Metallice:
Not because of the kernel. Something going on with your frequency setting app or apps. Use only one and try a different one.
[Nexus 7 Android Development] Metallice:
That 30fps thing has been debated for ages... People in tests say they can't tell, but all people are different and who knows what the brain is actually picking up on? The brain is pretty good at smoothing things out to make them look fluid even I'd they aren't.
[Nexus 7 Android Development] wy2sl0:
How do I change the tables? I tried editing with es root and it says can't save? Sorry for being a noob I am trying.
[Nexus 7 Android Development] SpikeySpy:
thanks that fixed the problem of the cpu frequency but the gpu (i'm using trickster) doesn't stick after a reboot, does it actually change on the fly when i make the changes in trickster?

how do i make the gpu sticks?
[Nexus 7 Android Development] ortrigger:
Check set on boot in the menu.

sent from my eclipsed nexus 7
[Nexus 7 Android Development] SpikeySpy:
seems to stick but one issue is that it freeze the entire system after a restart, i've only configured the GPU to 596 with the 550LP version.

Any ideas why it is causing the freeze/crash?
[Nexus 7 Android Development] Sultanxda:
I was also wondering that. Even though there's that 30 FPS thing with our brains I can still notice a significant difference between, for example, a 60Hz TV and a 120Hz TV to the point where 60Hz bothers me. For me, the pixclock overclock made animations noticeably more fluid (like opening the app drawer and scrolling between screens). :confused:
[Nexus 7 Android Development] Stuphologist:
You're absolutely right about the 30fps limit of human frame detection. Film is even slower, 24fps, and most people can't see the frames. I can, if I focus on seeing "fast" (for want of a better word), and I think it's likely that visual smoothing is, at least in part, learned. If not learned, then at least habituated - people watching HD shot at high framerates report that the scenes look surreal because they aren't seeing motion blur, which only exists in images/video. But when you're up to 60 fps even parrots and dogs see smooth motion.

The point I was trying to make was that he couldn't be seeing framerate as such. First, the lcd scan rate is fixed, in this case at 60 fps. Running it that fast reduces persistence blur and driver artifacts, but in the absence of those you can't see any difference between 50 and 60 or even 70 FPS. If not that, and if he's truly able to tell the difference anyway, then the explanation might be interesting, is what I was trying to say.

Dave

I also want to report that both of the A18s work with my N7. Weird.
[Nexus 7 Android Development] Metallice:
Exactly. Wasn't saying you were wrong or disagreeing, just adding to and clarifying. What you're describing by the way is sometimes referred to as the soap opera effect as they are usually the only things filmed in 60fps. Your brain is so used to filling in that extra information itself (motion blur), thst when it doesn't have to, the picture ends up looking surreal or funny. Motion blur is often added in post processing to make fast action scenes more pleasant.

Getting off topic here, but I couldn't care less :)
[Nexus 7 Android Development] Metallice:
Yes you can notice the difference between 30 MHz, 60MHz, and 120 MHz. Consciously seeing the difference in frame rate? Unlikely because of the way our brain compensates, but its very possible to tell that they look "different".

The thing is, our display can only physically display 60 frames per second. Increasing the GPU to Display bandwidth (what you are doing by increasing the pixclock) to allow the GPU to send 70 frames per second won't change the fact that the display can only show 60 of those frames per second.

I'm not sure if your experiences are placebo or not, but they are something I will look into. It's possible that there might be some secondary effect improving performance in your eyes, and there's no reason that can't be explored in the future. I may possible do a blind test down the road (a ways down the road however)
[Nexus 7 Android Development] wy2sl0:
Noone? I just want to find out how to edit the tables.
[Nexus 7 Android Development] Sultan.Alkhuzaie:
Sorry but how to change the GPU I am using trickstermod
[Nexus 7 Android Development] Metallice:
I honestly don't know if it can be done without using an app designed to modify voltage tables. Hopefully you guys can bug the developers of TricksterMod, system tuner, or whatever other voltage changing app to add compatibility with these new user uV tables.

If you can't change the files with a root-enabled file browser like Solid Explorer, root explorer, etc. or a root-enabled text editor, then I would guess that it has to be done with an app designed to change these voltage tables like the ones listed earlier.

I would try other root file explorers or root text editors to see if they can do it first though.
[Nexus 7 Android Development] Metallice:
Open the TricksterMod app. Grant it root permissions. You are at the tab titled INFOS. Scroll to the right through TOOLS and GENERALS until you get to the tab titled SPECIFICS. There is an option titled "GPU Max Frequency". It should be about the fifth option down. To the right of "GPU Max Frequency" there is a number - 446. That is the current maximum GPU frequency in MHz. Tap the number to bring up a window prompt. Either drag the slider, tap the plus/minus arrows, or manually type in your desired frequency in MHz. Once the number reads as your desired frequency, hit the "set" button. You will be brought back to SPECIFICS tab. Click the checkmark in the top right corner of your screen to apply the changed frequency. To set this value on boot, tap the action bar UI overflow button (vertical elipses) to the right of the checkmark, and tap "Set On Boot".

I hope that was detailed enough :) Didn't want to leave anything out.