yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] FreakyFreakGA:
Is there a setting to apply one or the other in the system, or is a a "flash this kernel and your GPU will be OC'ed to said speed on every boot"? Or is it something I have to edit in the android files. And I don't necessarily "want" a UI, but a simple UI for changing GPU clock speeds on the fly for like putting it in standby to save battery or something like that.
[Nexus 7 Android Development] Metallice:
In addition to some tweaks to things like up_threshold percent and other ondemand parameters, it hard-codes the sampling rate to a fixed value instead of being a calculation based on sampling and latency. I noticed a weird bug on my device where the sampling rate would sometimes get huge for some reason and which means really slow frequency switching and a massive hit to performance/responsiveness.

It's not something that could be scripted in. Don't worry about it... I'll have a new build (mr1?) out today. Don't have class until Wednesday for elections :)
[Nexus 7 Android Development] Metallice:
You don't have to edit any sysfs entries or files, but It's also not "flash this kernel and your GPU will be OC'ed to said speed on every boot" like you said.

It's only a change to the MAXIMUM GPU frequency. The GPU frequency scales just like CPU frequency. On stock the GPU can run at 228MHz, 275Mhz, 332Mhz, 380Mhz, or 416Mhz depending on what's needed.

For example, while playing an intensive 3D game the GPU will run at 416Mhz, while idling at the homescreen the GPU will be running at 228MHz, and while in standy the GPU will be COMPLETELY OFF.

So, there is absolutely zero point to lowering the GPU speed on the fly to save battery in standby as the GPU turns itself off anyway.

Anyway, if you flash M-Kernel_a8_446GPU_620LP.zip, the maximum GPU slot will be 446Mhz instead of 416Mhz. If you flash M-Kernel_a8_520GPU_620LP.zip, the maximum GPU slot will be 520Mhz instead of 416Mhz.
[Nexus 7 Android Development] stonebear:
mispost
[Nexus 7 Android Development] bervin:
Do you see any benefits in adding the same system UV that clemsyn has implemented in his battery savings kernel and if so would you be able to implement it easily?
[Nexus 7 Android Development] FreakyFreakGA:
AH, okay I get it now, im use to just flashing custom roms/kernels on phones/overclocking CPU's I have yet to own a tablet, but am getting the N7 and wasn't sure how it worked, so all it is, is the default GPU values are modified in the system so that when you play a high def game or something instead of it running at 416, the default highest stock clock it gets bumped to 520, right?
[Nexus 7 Android Development] Metallice:
Right. Either 520 or 446 depending on which version you download.
[Nexus 7 Android Development] Metallice:
FYI it seems disconnecting a usb stick causes a hard reset on a8. I'll fix it.
[Nexus 7 Android Development] nphil:
Just an observation I've made. The LP core seems to idle at 620 mhz constantly. Is this expected behavior? Does it not scale any lower? I'm on your latest alpha running interactive governor. (Really enjoyed your kernels on the old tab 2 7 inch btw)

Oh also, in addition to the tablet locking up when disconnecting usb sticks, it doesn't mount at all for me.
[Nexus 7 Android Development] Metallice:
Well it mounts for me fine. Whatever... it's probably the same issue regardless. It looks to be an issue with Google's source, as compiling the newest source without any modifications whatsoever still results in a kernel that locks up when removing usb drives. Looking into it. Seems to be an issue with usb baseband support.

And no the LP core should not idle at 620Mhz constantly. How do you know that it is the LP core and not the G cores, as the G cores can run at 620Mhz as well? Are you sure that it is the LP core?

The only way to make sure would be plug it into your computer and let it idle. Then open a command window and type: adb shell "cat /sys/kernel/debug/clock/dvfs | grep cpu_lp" (with quotes), read the result, and do it a few more times (up arrow key and then enter key) to confirm that it is the LP core and that it is stuck on 620Mhz.

Then try ondemand and see if the issue persists.

EDIT: and let me know what you find with all of this. Thanks.
[Nexus 7 Android Development] h.debnath:
I'm getting sleep of death issues when my device is in sleep for couple of hours
[Nexus 7 Android Development] nphil:
Thanks for the detailed response. I turned off the screen and monitored the clocks via terminal and it seems to scale properly. As for when the screen is on, and the device is idling. the clock stays at 620mhz but I'm assuming this is due to background processes etc. I ran the command a bunch of times with the screen on, got the same reading every time. CPU usage is idle too. For reference this is a completely stock ROM with about 10 apps installed.
[Nexus 7 Android Development] Metallice:
Alright. Can you try ondemand and see if it displays the same behavior for you?
[Nexus 7 Android Development] dSlice:
A8 520/620 gets really hot. I'm going to try the 446/620.
[Nexus 7 Android Development] Metallice:
I lowered the voltages on the bottom slots a bit in a8. I thought it wouldn't be a problem. Try raising the voltages of each slot +25mV with system tuner and let me know if that fixes it for you.
[Nexus 7 Android Development] nphil:
Switched to ondemand and tried testing again. I can't make sense of the results. With screen on, and idle, the frequency jumps between 620 mhz and 102 mhz, 90% of the time its at 620 mhz. With screen off, I let it settle for about 5 mins before running the command. I got 0's everywhere at first because i assume the LP core wasn't active (??). After running the command a couple of times, its the same as with screen on again - mostly 620 mhz.

Is there any way to record LP core frequencies and time spent in each state? This way I could just test over an extended amount of time and see what's really going on. I know its possible with the G cores. I'm not sure if this is affecting battery life in any way, I only just started using your kernel.
[Nexus 7 Android Development] MrDrift42:
This may be unrelated but on a8 I get terrible wifi download rates. I'm getting only 5 Mbps up and down and on a5 I was getting 20Mbps up and 5Mbps down.

Edit: -----------------

I flashed a5 back to back with a8 and it definitely borks my download rates. Not sure why...
[Nexus 7 Android Development] Metallice:
Not that I know of. The only thing close is CpuSpy, but it can't differentiate between the lp and g cores and just shows the total for both as one.
[Nexus 7 Android Development] Fracta1:
Played some Dead Trigger earlier. Pretty choppy :( I'll probably flash a7 again until the milestone is released.

EDIT: Flashed a7. Things are great again.
[Nexus 7 Android Development] nphil:
On a slightly different note, is there any way you could be convinced to release a 650/600 mhz GPU version? I just got a replacement 32GB unit and I need to see if it can handle it, even if the performance gains are nothing to write home about.
[Nexus 7 Android Development] Metallice:
Yep. Same here. Must be the new source :/ I'll see what I can do.
[Nexus 7 Android Development] prestige777:
a8 just came out

and this crazy,

nothing works right

a9 maybe?

lol

---------- Post added at 07:57 PM ---------- Previous post was at 07:51 PM ----------

You know you sang that in your head lol
[Nexus 7 Android Development] Metallice:
I take it back. My download speeds are exactly the same on a5 as a8.
[Nexus 7 Android Development] MrDrift42:
I noticed it first in YouTube. I couldn't watch anything without heavy buffering. That led me to check my speeds they were horribly inconsistent. One minute I was getting 10Mbps and then it was 5Mbps and really wasn't getting any better. Flashed back a5 and it's consistently 18+Mbps. Flashed back and it was back to 5Mbps. Back to a5 and it was back up. I'm at max signal, my router is a few feet away. Like I said it could be unrelated.
[Nexus 7 Android Development] phonic:
I'm still on A5 and happy. No issues or pops. Granted I just upgraded to the 32GB unit and never experienced a pop on it yet.
[Nexus 7 Android Development] opz187:
Same thing here. DL speeds are struggling.
[Nexus 7 Android Development] Metallice:
a9 up. A few fixes here and there for ondemand, usb mounting, usb otg charging, and others.

On the topic of wifi - I flashed a5, stock kernel, and franco, and they all consistently gave me about the same DL speed.

Anyone having issues, please try a9, a7, a6, and a5. It would helpful to know exactly where the problem started for you.

EDIT: or maybe a9 fixes it?
[Nexus 7 Android Development] opz187:
Other than that I'm looking the new kernel. Very smooth and no screen flicker any more. Great job metallice!
[Nexus 7 Android Development] MrDrift42:
Well, whatever the reason a9 seems to have fixed the wifi issue. It did hang at the google screen on first boot. Flashed is still the same. Seems to run about the same as a8. Will report back again when I get some more time on it.
[Nexus 7 Android Development] Billchen0014:
I got some weird slow down in the youtube player, the scrolling related vids while watching video gets super sticky from a8, wonder if anyone else have the same problem, and whether its fixed in a9 or not. im running aokp latest milestone build if it matters
[Nexus 7 Android Development] opz187:
On latest a9 gpu520... Games are extremely laggy.
[Nexus 7 Android Development] Metallice:
What game? I was just playing NFS:MW and it ran fine. Same as a8 for you or worse?
[Nexus 7 Android Development] prestige777:
I downloaded a podcast from my signature 163mb in under two minutes on a 20mb connection, I wouldn't say that's slow at all. I also downloaded a dozen songs with the music monster app, they all downloaded almost instantly. I would of been the first to complain, if there was a connection problem. I bent the contacts up to better connect the attennae last time I had my case open, but I doubt it made that much difference if at all. This was on a8.

---------- Post added at 10:05 PM ---------- Previous post was at 10:00 PM ----------

Does flash work on a9?
[Nexus 7 Android Development] Metallice:
"would of" *cringe*

But thanks for the feedback anyway. wifi seems fine for me too :)
[Nexus 7 Android Development] JohnShaft69:
goodness

a9 is fast and stable. tyvm
[Nexus 7 Android Development] Billchen0014:
hmm, what ROM are you using? AOSP based, or CM10 or AOKP?
[Nexus 7 Android Development] Metallice:
Right now? CM10. Used to run PA a lot.
[Nexus 7 Android Development] Billchen0014:
have you tried this kernel in AOKP roms? it didn't seem to work well, i guess others who also had wifi speed problems are also running aokp roms
[Nexus 7 Android Development] prestige777:
I am on Cookies and Cream 1.3.0 it seems faster than PA to me. I am going to flash the lastest PA and see if its better now.
[Nexus 7 Android Development] Metallice:
No I haven't. Have you tried the kernel with a non-AOKP ROM? I don't bother with AOKP since they messed with the navbar button size.
[Nexus 7 Android Development] MrDrift42:
PA 2.532 here.
[Nexus 7 Android Development] Billchen0014:
I don't have any non-aokp, since they often dont come with the brightness slider, i am still amazed by the fact that one small feature keeps me from flashing CM10 or aosp roms. PA is okay, but too gimmicky with the hybrid mode and i can't be bothered to set it up correctly.
[Nexus 7 Android Development] opz187:
OK you're gonna think this is funny.. But I was playing dragon fly lol. Not really a graphic intense game.. But it was hiccuping a lot. Fps kept dropping to 50.. IDK if the matters. But its a very simple game but like I said, lagged out hard. On sgt7.. Stock settings. Other than that it was extremely smooth browsing online and whatnot. A9 gpu520
[Nexus 7 Android Development] MetalPainis:
Yesterday morning I flashed a8, worked without any problem, tomorrow morning I had sod. Then I flashed latest PA and a9, went to my university (about 1h travel) and it was in sod state again when I just unpacked it. Both times I used 520GPU_620LP variant. No other issues so far :)

sent from a Nexus 7 via Tapatalk 2
[Nexus 7 Android Development] Metallice:
I need to know if raising voltages fixes it.
[Nexus 7 Android Development] Metallice:
Get the game to lag, and then open up terminal and type dmesg. See if you see a lot of dc underflow errors. If that's the cause than I think I've got it fixed for next time.
[Nexus 7 Android Development] Jay Aristide:
Just put it through it's paces with a few runs in Need for Speed: Most Wanted

Seems to be running great and battery life is fantastic. Running 446/620, not overheating or misbehaving at all
[Nexus 7 Android Development] dbrickg:
Likewise, except I was using the cm10 nightly rom. Had to hold down power button for a long time, then do the powerbutton+vol-down and shut off power, then restart. Rebuilt with a5 and seems to be fine
[Nexus 7 Android Development] Metallice:
To anyone with SODs on a8/a9:

Alright guys... please. I appreciate you all letting me know you're getting SODS, but I need you to help out if I am going to fix it since I can't reproduce any SODs myself... my tablet slept fine overnight and during the day yesterday.

Please let me know if raising the voltages (across the board, at specific frequencies, whatever) gets rid of the SODs. I need to know whether the cause is the changes I made to the voltages and DVFS tables or if there is another cause.
[Nexus 7 Android Development] ortrigger:
Anything past a5 doesn't seem to like AOKP M1. A9 is better than A8 but still shows a significant drop in RAM and CPU performance (according to quadrant and antutu) compared to A5. I'm doing a clean install of A9 with AOKP to see if that makes a difference.

PS: I forked your repo, Metallice. I hope that's okay. I'm starting the process of learning to develop and mostly I'm just looking through the files to get a handle on kernel architecture.
[Nexus 7 Android Development] R3dbeaver:
i didnt check the thread for a few days and it went from a5 to a9? lol...

must flash the latest and see if it helps with my gaming.
[Nexus 7 Android Development] stonebear:
I found that too, but it actually "feels" at least as fast.
[Nexus 7 Android Development] Metallice:
I base everything on feel. Not benchmarks. I watch for lag of any kind, stuttering while scrolling through lists and on the homescreen, responsiveness, gaming performance, fps and smoothness during normal use and on home screen, load times, etc. etc.

Sure I'll check a benchmark once in a while, but they usually show or tell me nothing.
[Nexus 7 Android Development] Metallice:
From kernels a6 and on, I included a packaged ramdisk that replaces whatever one is there. It's possible that there is some incompatibility in the ramdisk causing issues with AOKP. But if flashing a9 and then a5 right after still gives you better performance than that's not it.
[Nexus 7 Android Development] ortrigger:
True. It may be a device issue though because I can't get either a5 or a9 to boot with aokp. I will update later with my results. If you need them I can probably get a logcat.

Sent from my lg spectrum rocking ics.
[Nexus 7 Android Development] Metallice:
wait what? How can you say you have a performance decrease on aokp past a5 without being able to boot up a5 or a9?
[Nexus 7 Android Development] phonic:
Yes and no. While it's certainly true that benchmarks don't really mean a whole lot - especially in regards to device comparison or real world performance, they do have value. While certain settings can easily be tweaked to give an unnatural boost to the score, and trying to achieve some high score doesn't necessarily mean you have great system performance, they can be used to gauge the difference that certain settings changes make.

If you routinely get a score of X (+- a small percentage), and you make a kernel change regarding the CPU and suddenly your score jumps/drops a significant amount, that's a good indication that the change you made is either good or bad.

While I personally don't care what my score is, I do like the fact of using it as a change meter.

But you make a very good point that real world performance is paramount. If someone's happy with how their system functions, no reason to make a change just because of a bad score.
[Nexus 7 Android Development] MetalPainis:
Sorry I was really busy today, after university I went home and now, 15h later, I took my device out of the backpack and it was deadly sleeping again. I now downloaded system tuner like you suggested and increased overall voltages by 25mV. I'll let you know after this night if the SODs returned.
[Nexus 7 Android Development] dbrickg:
I've always been undervolting everything by 100mV, starting w/the original motley kernel, and continuing w/yours. Everything up-to-and-including a5 worked just fine w/that. When I isntalled a8, I noticed that you'd already dropped the voltages, so I didn't drop them myself. I know that this isn't conclusive, but might give some indication. My current voltages, w/a5, according to System Tuner Pro run from 700mV at 520MHz to 1137mV at 1.6Ghz. Oh, and I'm using the 520/620 kernel
[Nexus 7 Android Development] Metallice:
I never said they don't have value. I was trying to say that I usually never bother checking as they are mostly worthless, but should occasionally anyway. I find that most real changes fall within the standard deviation of test scores. So I often tend to not bother checking as they rarely show a difference, unless you do a tweak for the sole benefit of increasing scores that in reality has virtually no real performance gainlike noauto_da_allocation.

Its not only that "real world performance is paramount", but that real use and blind testing often tell you more about the effects of changes.

On that note I flashed A5 and got the exact same scores that I did on A9.
[Nexus 7 Android Development] ortrigger:
It just started today after flashing from a9 to a5 on a clean install of aokp. I updated my bootloader yesterday so that might be it. Or, maybe I just need to wipe absolutely everything including sd. I'll get a logcat later and see if I can find what's causing it to hang on boot.

Sent from my lg spectrum rocking ics.
[Nexus 7 Android Development] noodles2k:
I'm currently getting 13k in Antutu, which is normal. Also everything's great so far, no sods or pops etc :)

Do you mean the status bar brightness slider? As Kaos Droid has it and it might be in CM10.
[Nexus 7 Android Development] haledroid:
a9 is running good. Not sure if this will help anyone, but I wiped the cache partition after installing the kernel. Didn't hang at the Google screen for me
[Nexus 7 Android Development] rootbrain:
Tried a9, no SODs but battery not good. Wake_locks causing android system to use most of the battery with screen off, never goes to deep sleep at all. Also, system tuner seemed to not work correctly, couldn't update cpu, was on 102 & 105000, would not let me update max to anything higher, only lower. Stock ROM, SuperSU, MKERNEL a9. Switched back to classic 446, battery back to normal with screen time using the most as it should.

Rootbrain
[Nexus 7 Android Development] matique:
Any mirrors for a9 520 gpu? Would love to try this kernel out. Goomanager keeps stating that I have an invalid md5. A mirror would be great!

Nexus 7 | Paranoid Android | Trinity Kernel

GNex | Paranoid Android | Franco Kernel

HTC Sensation | Bruce's CMX | Bruce's Kernel.
[Nexus 7 Android Development] ortrigger:
So, I flashed just aokp and then went back and installed a9 and it seems to have cleared up the performance issues from earlier. It certainly feels just as smooth if not more so than a5 now.

sent from my aokp'd nexus 7
[Nexus 7 Android Development] Metallice:
That really makes no sense. 1050 Mhz shouldn't even be an option as it's not a valid frequency in the frequency table. Do you have any apps or init.d scripts that could be messing with things? It may be a bad download. I'd redownload and flash again. Something got corrupted for 1050Mhz to be an option.
[Nexus 7 Android Development] phonic:
You may want to clear data for any system tuner apps (SetCPU, System Tuner, etc.) and reboot. That might help.
[Nexus 7 Android Development] Kearkan:
About to flash a9 so ill see if that fixes this. But I noticed there seems to be a problem with USB otg.

I just got my 32gb and I was using a flash drive to backup/restore. Both tablets were running latest pa and a8, and no matter how I went about it, unplugging the otg cable made the tablet lock up and restart.

Will flash a9 now
[Nexus 7 Android Development] rootbrain:
I agree, no sense. No init.d script for CPU, deleted it and changed system tuner to on reboot instead of init.d for CPU.

If there's apps that messed with it they don't with the classic 446. Still poking around, any suggestions on where/what to look at?

BTW did clear the system tuner app cache but same results.

Rootbrain
[Nexus 7 Android Development] Metallice:
But did you try redownloading and flashing again? As I said it could have been a bad download.

A copy of dmesg aquired shortly after booting would be helpful. You can get it with "cat /proc/kmsg > /sdcard/kmsg.txt"
[Nexus 7 Android Development] Fracta1:
From the looks of things, I'll be sticking on a7 for a while. Especially since there seem to be compatibility issues with AOKP :( And apparently the newer kernels are undervolted at default as well? I already undervolted, so what does this mean for me?
[Nexus 7 Android Development] MetalPainis:
Just woke up but my nexus didn't, ;) sod over night again.

sent from a Nexus 7 via Tapatalk 2
[Nexus 7 Android Development] Metallice:
Please don't "stay on a7". I need as much feedback as possible. Download the new kernel but keep a copy of a7 in /sdcard/ just in case. If something goes wrong or is buggy you can just reboot into recovery and go back to a7.

Anyway, it looks to me like there are no compatibility issues with AOKP. The person having issues with AOKP tried a clean flash of AOKP followed by a9, and that resolved all his problems. This suggests to me that it most likely wasn't the ROM but something else causing issues.

And you can't "already undervolt"? That doesn't make any sense. If you have voltages set on boot they will continue to overwrite the kernel values like always. Regardless, the undervolting is incredibly minor - I believe at most 25mV, and I've already reverted all the changes for the next build :)
[Nexus 7 Android Development] Metallice:
Sigh. Maaaaan, I really do not like your tablet. I reverted all the voltages and DVFS values to stock for the next build. We'll see how that goes.
[Nexus 7 Android Development] MetalPainis:
I don't see why you should do that. I mean, the issue only occurs to me when the device enters (or is already in) deep sleep (can't be sure which one), at least thats what it looks like. So if the issue is really related to voltage or DVD, it should only be necessary to change those values for the cpu-clock that is present @deep sleep, or right before it!? ;)
[Nexus 7 Android Development] yukkio:
Hi, I feel a5 the more smooth kernel version (using the same settings) May be a5 has a better default setting of the interactive governor than other versions?

Benchmarks score equal in all kernel versions. (~= 100 points)

BR.
[Nexus 7 Android Development] 416inversed:
Same here.
[Nexus 7 Android Development] Huey85:
anyone having issues with Need for Speed Most Wanted with this kernel? I'm running SmoothROM with a9 and the reflections/textures of the car seem pretty glitchy. I tried it with the stock kernel that came with SmoothROM and the graphical glitches are not present.

EDIT: the issue seems to be present with all of the custom kernels I've tried.
[Nexus 7 Android Development] Milamber33:
Graphical glitches are generally GPU errors. Have you tried using a lower GPU overclock version? Which one are you on now and which ones of other kernels did you try?
[Nexus 7 Android Development] Metallice:
First alpha of M-Kernel plus available in the OP. :victory:
[Nexus 7 Android Development] Jay Aristide:
Flashed the alpha over the ramdisk you sent me last night. Running great on ParanoidAndroid 2.2 :)