yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] kzakhar:
The 2nd number is the 5th LP (low power) core overclock (default max frequency is 475 MHz).

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

I'm running a2 579/446, PA 2.23 and Jay's script with disabled fsync, /data and /cache mounted with discard, zRam swap is 64 MB, CPU governor is interactive, elevator is deadline, 100-1300 MHz core frequencies, -50 mv undervolt across the board. Just ran the benchmark and got 5459.

If you get low benchmark scores, make sure you don't overclock the CPU too much and always supply it with enough voltage, have fsync disabled, /data and /cache mounted with discard option. Fsync and discard will significantly affect your storage performance, which will affect the total benchmark score.
[Nexus 7 Android Development] Metallice:
In the OP and the file name it is listed as "LP" which stands for low power core. The higher the number/frequency, the better the battery life and performance.
[Nexus 7 Android Development] stonebear:
Have you removed the download link for Motley-Kernel classic?

I can't see it.
[Nexus 7 Android Development] kzakhar:
Unfortunately, after working with 579/446 for the whole day (I asked my wife to check the sound a few times every now and then), the sound suddenly stopped when I opened a movie in MX player after doing other things for 10-20 minutes (the sound was ok all the way). I checked the logs and kernel messages, but there was nothing unusual, thus I'm not sure what's happening.

Please let me know if I can look for some hints somewhere on my device, as this is the only major issue I'm having with this kernel, which is the best kernel I tried :(

---------- Post added at 08:16 PM ---------- Previous post was at 08:15 PM ----------

Yes, the classic 4.1.2 version has been removed: it introduced some boot issues.
[Nexus 7 Android Development] MrDrift42:
I started again from scratch with the new a2 kernel and jays new procedure and got it all fixed up. 6100 in quadrant now :D.
[Nexus 7 Android Development] Jay Aristide:
Performance/deadline 200-1600, no zRam, no uv will net a 6300 with my recipe :)
[Nexus 7 Android Development] noodles2k:
Any idea of what changes Motley made to deadline?
[Nexus 7 Android Development] Jay Aristide:
None, whatsoever, but since he did it, deadline outperforms sio by leaps and bounds.
[Nexus 7 Android Development] kzakhar:
You don't have to do much for that: sio elevator is inferior to deadline in both sequential and random access to flash drives in real-world applications (not specific to Nexus 7).
[Nexus 7 Android Development] Metallice:
https://github.com/faux123/Nexus-grouper/commit/d01d92538789060b0b7bca3c7e6c92eef34b40a1
[Nexus 7 Android Development] Metallice:
Try the 513Mhz LP version. I doubt you'll see any logs as it is a hardware issue. (Doesn't mean the cause can't be software or that software can't exacerbate the problem)
[Nexus 7 Android Development] kzakhar:
Sorry, I'm currently back to stock PA 2.23 kernel (whichever that is), as I need sound tonight and PA kernel doesn't have the weird pop/crackling/no-sound issue. I will flash the 513 MHz LP version tomorrow morning and post some results.

Thanks!
[Nexus 7 Android Development] MrDrift42:
I was running interactive/deadline 100-1600, 128 zram. That was with my normal running programs and live wallpaper too. :D
[Nexus 7 Android Development] notko:
If i want stock CPU voltage settings - this can be done via System Tuner - Voltage - Reset all /Clear button?
[Nexus 7 Android Development] Metallice:
Thanks. Lots of stuff going on there. Looks like you were pressing the power button a lot though... thanks I'll take a longer look later.
[Nexus 7 Android Development] leonbarroso:
any chance to have pixclock overclock ?
[Nexus 7 Android Development] tobitronics:
Still having sound pop issue after upgrading to a2. Running 513lp520gpu with 102-1600 interactive deadline no sound mods.

Beamed from my Paranoid Google Nexus 7
[Nexus 7 Android Development] O2Blevel:
How much battery life are you guys getting with the M-Kernel?
[Nexus 7 Android Development] xfrancis14:
Apparently Firefox works for but idk cause I don't use it, and yes the min will revert after audio is finished and user means set your own gpu with something like trickster the default is 446, and for lp core download 666 as is supposedly has better battery life then 555
[Nexus 7 Android Development] berkos:
huh i was using lp with 555 because i thought it's more battery friendly, tried to search why 666 should be more easy on battery, is it because it completes tasks faster?
[Nexus 7 Android Development] knitler:
Its because it can do more work itself with out having to power on the other cores.
[Nexus 7 Android Development] R3dbeaver:
just FYI, i switched my GPU from 650 to 666, still holding at 1350mV and although GPUMark is still the about the same, but ShadowGun and Most Wanted are MUCH MUCH smoother....
[Nexus 7 Android Development] thisguy23:
So coming from the gnexus where we needed to save every drop of power, I'm curious what other voltages and speed everyone is using. I just got this n7 a few days ago so I'm still testing how low it can go on voltage. Attached is what I'm currently using.
[Nexus 7 Android Development] Sveke:
Why bother? The battery lasts forever.

UV is a waste anyways, reported gains are little to nothing.

I stopped UV my gnex months ago.
[Nexus 7 Android Development] Metallice:
Little to nothing is still something. Fully optimized undervolting can give you about 2-5% savings for the MPU... and probably more for the Core.

Also core voltage is only one power rail and thus one value. Therefore lowering the value of one component can lower the voltage for the whole core as the core runs at the highest requested DVFS voltage. For example - If the EMC DVFS is at 1000mV, the LP Core DVFS is at 900mV, and the GPU DVFS is at 1200mV, the entire core is running at 1200mV. Therefore, undervolting the GPU would save voltage/power across the board for the core.

You can see all this dvfs debug file... some sysfs... I believe - cat /sys/kernel/debug/clock/dvfs

That file would be the ultimate guide for undervolting

(Also... anyways isn't really a word. I don't know why one would "pluralize" anyway, anyway :) )
[Nexus 7 Android Development] Sveke:
OK, I'll let you handle it on your end.

I didn't understand a word of that so whatever you put it at default is what I run. :thumbup:

Thanks for the grammer check too.
[Nexus 7 Android Development] Milamber33:
It's 'grammar', not 'grammer'. ;) :p
[Nexus 7 Android Development] thisguy23:
Metallice,

Thank you for a great kernel. Again as I'm very new to the n7, I'm curious if you know anything about tweaking the gamma of the display. It's the worst thing about this tablet.
[Nexus 7 Android Development] BlackFire27:
Just fyi I'm running 4.2.1 stock. Could you explain last_kmsg to me please?
[Nexus 7 Android Development] DJLamontagneIII:
Some good info on last_kmsg http://xdaforums.com/showthread.php?t=1520508
[Nexus 7 Android Development] Dr_Nacho:
This may have been asked... does this work with the 16 gb WiFi model?
[Nexus 7 Android Development] cmason37:
Yes it does.
[Nexus 7 Android Development] Stuphologist:
Somebody is sure to shoot me down for this, but I believe gamma correction is somehow not possible with an IPS display...? Color calibration should be possible in the kernel, but the N7 display has been criticized for crummy green rendering and for having limited RGB coverage, and I came away with the impression that it wasn't fixable or it would be a pain to do. That said, I have used an app that let you adjust the color temperature of the screen, and it worked. My N7 had a distinct yellow cast when I got it, and I found an app that let me push the color temp up, and the extra blue countered the yellow. Eventually the yellow faded or I got used to it, and I stopped using the app, and I can't recall the name (sorry).

Anyone know the real answer?

Dave
[Nexus 7 Android Development] Milamber33:
I'm no expert, but from what I've seen a couple of kernel devs saying, with most LCD screens it's not really possible (unless you're talking about some kind of overlay to change the actual image sent to the display), but the Nexus 7 display does have some kind of options available, not sure how much it can be tweaked but some stuff was found in the Google kernel commits or something for adjusting the display. I believe Morfic and Franco are both looking into it now and seeing what they can do.
[Nexus 7 Android Development] LINKSLOVESANDROID:
quick question. As far as multitasking, which would be more effective? 666, or 555? ive always used 666 and felt i slight lag.
[Nexus 7 Android Development] Milamber33:
Probably 555. For multitasking you want the extra cores to come online so it can handle all tasks simultaneously, and the 666 version would wait for higher load before activating them.
[Nexus 7 Android Development] ace-user:
i just flash this kernel on PA...what min and max cpu frequency do u guys recommend? i'm using 102mhz min and 1.3ghz max atm...but 102min seems a bit slow and laggy...so what values do u guys recommend?
[Nexus 7 Android Development] aggrophobik:
lolol
[Nexus 7 Android Development] Dr_Nacho:
How do I check what version of bootloader I'm on? Is this your custom recovery?
[Nexus 7 Android Development] Milamber33:
No, bootloader is the thing that loads either Android or your recovery. Power the device off, then hold both volume down and power at the same time to switch it on. The screen that comes up should have the bootloader version listed.
[Nexus 7 Android Development] ezas:
Is it laggy at 304? But it's not the kernel its something else about your configuration.

I run 102 and 1500 and 520 GPU on the 666 kernel. No voltage tweaks.
[Nexus 7 Android Development] ace-user:
u OC the GPU to 520 and CPU to 1500? will it affect battery life? :confused:
[Nexus 7 Android Development] Dr_Nacho:
So I took or steps and found that my bootloader is 3.3.4. How would I update this to meet the requirements for this kernel?
[Nexus 7 Android Development] Metallice:
Yep multitasking would be the one time 555 would be better. I still prefer 666 personally.
[Nexus 7 Android Development] Metallice:
Min has nothing to do with lag considering touchboost. Either adjust ondemand parameters or fix your setup so 666Mhz is enough for home screen and scrolling.
[Nexus 7 Android Development] Metallice:
There are lots of ways to do that. Find the 4.1.3 recovery install zip here on XDA... Fastboot flash recovery image.. And I'm sure others. Fastboot is safer but more difficult. Up to you.
[Nexus 7 Android Development] ace-user:
can u share ur set up? =)

Sent from both my sexy galaxy nexus and nexus 7 X)
[Nexus 7 Android Development] Metallice:
They're not. They are both busy with other things, simpler tweaks, and other devices like the nexus 4. Gotta make a kernel to sell their app. (And i own all of them :D)

I tried messing with the nvidia drivers and gamma, had little to no effects. I believe Morfic tried something similar. For the most part, devices with gamma correction like the GS3, Gnex, N4, the gamma parameters or values were already present in the display drivers.

Color control doesn't come out of thin air. Interfaces are built around values and controls already present. We just let you change those values.

The nexus 7 doesn't have any of these. Making the chance of color control slim to none. Either someone would have to find gamma correction where everyone else had missed it... Or something would have to be built from scratch.

Sorry. Other kernel devs say maybe... Buy I'm not as optimistic.
[Nexus 7 Android Development] Metallice:
My setup involves a cracked and non-functioning screen. You can try that, but i wouldn't recommend it.
[Nexus 7 Android Development] ace-user:
lol...i oc the gpu to 520mhz...will it have a big decrease in battery life?

and how do i set the LP value? is it fixed and cant be changed?

i'm new to kernel stuff and sorry if i caused any troubles..

btw...hope u get ur tablet fix soon :)

Sent from both my sexy galaxy nexus and nexus 7 X)
[Nexus 7 Android Development] christianlr25:
Switched ROM from ParanoidAndroid to CM 10.1 nightly and I'm still having trouble with auto brightness after flashing your kernel. I've brought it up before, about a week ago. I've been reading around and looks like its a 4.2.1 bug? Its weird though cause this only occurs when I'm using your kernel. :what: idk what to do anymore. Its kinda frustrating. :o
[Nexus 7 Android Development] adstraylight:
You could try LUX Auto Brightness, it is far more controllable than the stock adjustment, and working perfectly well with CM10.1/M-kernel
[Nexus 7 Android Development] Metallice:
I don't know what trouble with auto brightness means.
[Nexus 7 Android Development] Kearkan:
Catching up on the tread... Now waiting for jay aristides name to pop up.

---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------

I had a look at lux, does it have much effect on battery life?
[Nexus 7 Android Development] Stuphologist:
A friend of mine dropped her GNex quite a while ago and, to her and my surprise, it still worked. I thought sure the touch functionality would be dead or randomized, but it worked fine. I gather that your N7 is deader than that, though. Have you tried disassembling and reassembling it? Could be a connector, and a defunct screen can't get more defunct.

Dave
[Nexus 7 Android Development] Metallice:
The glass is glued to the touch sensor and display. If you crack the screen you lose touch input. It's not a bad crack, I'm sure the case helped. I get sporadic touch functiobality in the bottom half, but yeah for all intents and purposes it is done for. And a new glass/display/touch sensor is almost as much as a new device anyway. (Have to admit...Nvidia's kai program is impressive)

And i have taken it apart. Very easy to do. Broke it down into individual pieces and put it together. Just because I can :). That's just who I am. I like to know how things work and break them down. Im sure a few of you like that. Once you get over the fear of screwing up, it:s quite a fun and interesting endeavor. Part of the reason I want to be a doctor and maybe a surgeon.

On a boat right now... About to lose signal... All day fishing trip... Hopefully catch some food with my bro and dad... So I'm going to have to count on you guys to answer eachother's questions :) See you guys at midnight (eastern)!
[Nexus 7 Android Development] Jay Aristide:
There's no 's' at the end of Aristide (Yes, I'm aware you meant Aristide's) :D:D:D
[Nexus 7 Android Development] adstraylight:
Lux has never even shown up on my battery stats, and I think that any drain from the background service is more than offset by the fact that it dims the screen to suit your environment. I've been using it since its initial release and frankly couldn't live without it now.

It works best on the N7 when set to adjust 'ascendingly' btw.
[Nexus 7 Android Development] ezas:
That's a pretty mild OC, especially compared to what others do. It must effect battery life some but I get plenty of battery life for my needs. So I don't worry about it.
[Nexus 7 Android Development] Sveke:
Mine just took a dump at 600 GPU over clock. Froze right up.

520 for me.
[Nexus 7 Android Development] R3dbeaver:
600 and higher needs overvoltage.

Mine works just fine at 666@1350mv and battery life is good. Not noticeable from stock unless i play games continuously...
[Nexus 7 Android Development] christianlr25:
Okay, I'll try that app out. Thanks.

When I have it on auto brightness, it stays on the lowest brightness. It jumps a couple of brightness levels up but then goes back no matter what I do. It doesn't adjust like it should.
[Nexus 7 Android Development] yukkio:
Is there any way to fix flash or we have to wait until metallice fix it¿

Thanks

Br
[Nexus 7 Android Development] -=s-b-h=-:
Well it runs very smooth just need to find best clock speeds for games to be buttery smooth and batt life to be effective one question tho does the kernel support charhing via a y otg cable so icould say use a flash drive and charge at same time ?
[Nexus 7 Android Development] R3dbeaver:
So u would charge your n7 using your flash drive? Is that even physically possible?
[Nexus 7 Android Development] Stuphologist:
It's possible, but not implemented in M-Kernel. Metallice said it caused problems. A Y-cable can let you power a USB device that draws more than the N7 can supply, but not power the N7 while using a device. This was discussed around the beginning of the month, I think. A search will turn up the posts.

Dave
[Nexus 7 Android Development] Metallice:
Yeah dmesg showed OTG failing to turn off some timed leaving it powered on and other funky stuff.

Maybe after mr1.
[Nexus 7 Android Development] NicoGa:
it seems they have been some advance on that side lately:

http://mehrvarz.github.com/

Envoyé depuis mon Nexus 7
[Nexus 7 Android Development] Metallice:
Thanks. The latest patch is different than the one I used before.

Still not gong to mess with it until after mr1 and until after I an able to get a new nexus 7.
[Nexus 7 Android Development] NicoGa:
you are most welcome, it was just to inform you.

Envoyé depuis mon Nexus 7
[Nexus 7 Android Development] Stuphologist:
TWRP 2.3.3.0

I just noticed that TWRP 2.3.3.0 is up for the N7. I use it, and some other people do. Here's a link to the thread. GooMgr will flash it for you, just select the flash recovery script option from the menu.

Dave
[Nexus 7 Android Development] benbailey84:
I flashed it about 3 days ago. So far so good.

Also, flashed this kernel... Awesome!!!
[Nexus 7 Android Development] EvanA:
You should really use AnTuTu instead. Quadrant is outdated.
[Nexus 7 Android Development] -=s-b-h=-:
Got a slight issue my n7 has hung a few times now and had to reboot the screen looked frozen only setting I changed from stock on the rom was gpu max to 520 everything else was standard.

Can anyone advise please
[Nexus 7 Android Development] Keitaro:
Sounds like you need to bump the GPU voltage up a bit.
[Nexus 7 Android Development] dstryrwiz:
I just installed Lux Auto Brightness, and included with that app are night and astronomer modes which color the screen (mostly shades of red). If that can be done with that app, shouldn't there be another way to adjust the overall colors of the device in a similar fashion? I'm not certain whether or not that would be kernel related, but maybe if you contact that developer and find out how they approached that feature, then maybe it could be incorporated into a kernel? It may not work at all, but the fact that that app was able to do that on the Nexus 7 makes me feel like there is potential to do color adjustments if that was able to.
[Nexus 7 Android Development] Metallice:
Drawing a transparent solid color image on top of everything isn't adjusting the display color temperature. Plus, that will kill your battery.
[Nexus 7 Android Development] ace-user:
are brightness control affected by kernels? i was running PA beta 9 with stock kernel but lately i flashed this kernel and auto brightness have been really sensitive...it changes to frequently and it kind of bugg me..never encounter this issue on stock kernel so i'm pretty sure it's not rom related...can anyone help me out with this?

Sent from both my sexy galaxy nexus and nexus 7 X)
[Nexus 7 Android Development] dstryrwiz:
I want certain how they were approaching that color change. I apologize if it wasn't what I thought it may have been. If that's all it's doing, I agree, but I thought it may have done something different than that.
[Nexus 7 Android Development] jamesst20:
Don't know what you have done to it but it is not smooth at all just like motley kernel. I will stick Bricked :p
[Nexus 7 Android Development] Lazy Rich:
Yeah, I have noticed this issue too. Motley is a lot smoother in UI things. M-Kernel feels like the butter is gone :/

I hope this will be fixed soon, I love the GPU control, that is the one thing Motley doesn't offer...

Gesendet von meinem Nexus 7 mit Tapatalk 2
[Nexus 7 Android Development] thisguy23:
I'm still new to the n7, but I noticed everyone is using the ondemand gov with really conservative settings to max battery life. Other kernels and stock use interactive. Which is what I'm using now and it is smooth!
[Nexus 7 Android Development] jamesst20:
Well whatever the governor I use, best are on demand and interactive, it is still not like butter.
[Nexus 7 Android Development] Metallice:
The only difference is the display gets much darker than stock. Which means changes from bright to dark will be more noticeable.
[Nexus 7 Android Development] Metallice:
Please do. I prefer users that actually give helpful, constructive criticism.

You know like a23 is better than a25 or a19 battery life is bad compared to a18. Not "this kernel is slow WTF man everyone use this other kernel its better."
[Nexus 7 Android Development] Metallice:
I just checked and yeah it's just an overlay
[Nexus 7 Android Development] GoldElocks:
Bricked kernel?! Talk about a pos! Especially paired with smoothrom. I hear that dev is a real douche too. ;)

On a serious note a25 is running extremely smooth for me, better than previous builds. :D Trying it out on latest cm10.1 coming from PA and Smoothrom and just as smooth. Also just added Jay's recipe for buttery goodness and although I was sceptical about the zram usage and what not I am noticing some extra smoothness especially noticeable when opening and closing the app drawer.

Now I'm trying to tweak the ondemand governor control but haven't found any settings outside of stock that I really like.

Anybody else find some good tweaked settings there?
[Nexus 7 Android Development] ace-user:
can u fix it so that it's same as stock? it's kind of bugging me..it's like the screen is flickering sometimes...

thx =)

Sent from both my sexy galaxy nexus and nexus 7 X)
[Nexus 7 Android Development] NicoGa:
I love this kernel, all its options and I am learning a lot reading this thread. However I notice similar things a week ago:

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

As a reminder, I notice that what ever the version of your kernel (I tried all of them starting with a18) the UI is notably smoother using interactive governor ... my question was:

Am I loosing a lot of your enhancement by using that governor ?

What can I do to tweak ondemand governor ?

thanks in advance for your answer.

edit: lowering the up_threshold to 85 seems to help

Envoyé depuis mon Nexus 7
[Nexus 7 Android Development] Metallice:
Ehh. I dunno. I like that the brightness can go down to the absolute minimum for night viewing and battery life.

The REAL issue is 4.2. There was never a problem with 4.1 as the brightness changed less frequently and wasn't as finicky and abrupt.

The brightness level changes I made aren't the cause of the problem, they just make it more noticeable at times...

Don't know if the downsides outweigh the benefits for me. Maybe. Need more opinions.
[Nexus 7 Android Development] Metallice:
Nah. Not the same thing. You just said ondemand is slower than interactive. Nothing wrong with that. It's true, especially with the high up threshold.

Its how I like it. I had no lag with PA and the latest BETA of Nova launcher (not play store version) with the default settings, but I understand that other peoples setups might be different.

He was saying the kernel was slow on both governors and bricked was better, with no other information or any semblance of helpfulness.

Edit: if you need or want more performance, lower up threshold and lower sampling down factor. Or just use interactive. Fair warning I messed around with it some and don't really know of it works well. Never use it.