yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Gareee:
I wonder is its cleanrom causing the slowdown then?

When I flashed it, I just went to recovery, flashed r5, and then rebooted.

That the correct procedure?
[Nexus 7 (2013) Android Development] squashpile:
6089 Quadrant on r5 Stock ROM. Settings are basically defaults in Faux app. I'm about to try r6. I'm not so worried about quadrant. Tablet is very smooth.
[Nexus 7 (2013) Android Development] Gareee:
So I should also run faux, and use it's oc defaults as well?
[Nexus 7 (2013) Android Development] squashpile:
I'm not sure about that..ha. I just got the app and I'm still learning it and all the options of this kernel.

I have a question..

Can't I use TWRP and backup/restore boot.img to move between these kernels?
[Nexus 7 (2013) Android Development] Gareee:
Hmmm.. I just ran faux, and it shows the clock speed at 1512, not the speed of the r5 release.

Seems odd.

Everything has always run smooth on the tablet, so its hard to see if I've seen any speed increase or not.

I'll try reflashing r5 and see what faux reports.
[Nexus 7 (2013) Android Development] squashpile:
Also check Thermal the throttle limit was way high on default.
[Nexus 7 (2013) Android Development] whittikins:
Hmm I think I wasn't doing a long enough swipe :).

Can you allow a shorter swipe and perhaps other areas of the screen? Thanks for the work!
[Nexus 7 (2013) Android Development] jassycliq:
Yes, backup boot.img. I find it easier to just flash the kernel releases though :)

Yes, it boots up with 1512mhz default. I had forgotten to get rid of that step newer kernels wont have that issue.

Yes,another thing fixed in the test kernel.

I'll attempt it. Though [MENTION=4684315]flar2[/MENTION] said that his new version supports swiping anywhere on the screen to turn on (from edge to edge) I'll ask him if he can add support so that fauxs app can mess with those parameters so you guys can fine tune.
[Nexus 7 (2013) Android Development] djdisturbed:
I see version 6 listed in change log...but don't see a download for it
[Nexus 7 (2013) Android Development] acdcking12345:
Can I run this on a stock ROM, even after I had rooted it?
[Nexus 7 (2013) Android Development] Gareee:
Using conan's faux settings, I'm up to 6787 on quadrant now. Not as high as others, but still a significant improvement.
[Nexus 7 (2013) Android Development] squashpile:
Yup...

I'm on r6 now. So far so :good:
[Nexus 7 (2013) Android Development] acdcking12345:
Yeah, I dont see the version 6 either.

---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------

Where can I get Version 6?
[Nexus 7 (2013) Android Development] squashpile:
http://xdaforums.com/showthread.php?p=44319010
[Nexus 7 (2013) Android Development] jassycliq:
Its a test, well at least the one I released to some people to test. I'm trying a different combo. Performance seems OK (its not a benchmark type kernel as defaults) I'm hoping for more juice out of the battery though. I'll be fine tuning some stuff first because as is, it currently lags a bit while steaming Netflix. For me that's where I see the most battery saving honestly, I watched a whole movie and the battery went from 30% to 14% which is significantly better for me compared to stock.

But from the looks I may actually use aroma. I'll have a regular kernel that defaults to what we have now. Performance with a bit of juice sacrificed. Then I'll have an aroma installer for those that want to fine tune during install. Currently kernel adds init.d support then checks if busybox is installed. If it isn't it'll alert you. It also checks for a little hack to allow apps to mount a directory system wide which isn't possible stock. If its supported in the ramdisk it won't add anything if not it'll add it. I was trying to find out if it worked but I don't use CIFS so I will need other who do use it to comment on that.

I'll see about other things though.
[Nexus 7 (2013) Android Development] squashpile:
I have Netflix running now on a 45 min show. How long was that movie? Just curious..

I don't notice any lag at all.
[Nexus 7 (2013) Android Development] jassycliq:
It was around 2h and maybe 1/4 of another. I have someone else reporting the lag also so I'll just do a little tweak to make sure its not there :)

Anything input?
[Nexus 7 (2013) Android Development] squashpile:
After a little over an hour on Netflix battery went from 92% to 80%. Looks like two cores used most of the time and I have those @ 1.7 max. I'm not sure if that even tells you anything. I really didn't test on stock kernel. I may throw that back on to try it.

I do not notice any lag at all so that is interesting.
[Nexus 7 (2013) Android Development] ac7822:
What's the stock kernel's clock speed for the gpu? I have the GPU at 487 and on simple governor and during regular use the battery is really good but gaming just chews up a ton of battery. Should I change the GPU governor to something else?

On my old nexus 7 and galaxy nexus I gamed a lot with the gpu overclocked so I know battery gets eaten up by gaming it just seems really bad right now.
[Nexus 7 (2013) Android Development] jassycliq:
Stock is 400mhz. You also have to remember the amount of pixels you're pushing here ;) then there's the adreno 320 part. Either way 400mhz is stock and 320mhz should be fine though :)
[Nexus 7 (2013) Android Development] stayRooted:
Nice work
[Nexus 7 (2013) Android Development] ac7822:
True I didn't think about all those gorgeous pixels and I don't know much about the adreno GPU just that it's a nice one, I'll assume it sucks more juice than a tegra 3. Compared to my previous devices this Qualcomm chip has so many different settings that can be adjusted I have much to research about it and this kernel
[Nexus 7 (2013) Android Development] jassycliq:
From my experience the adrenos do suck more juice. I could be wrong though o.O
[Nexus 7 (2013) Android Development] ac7822:
Edit- delete
[Nexus 7 (2013) Android Development] Imppy:
Is clear vfs cache automatically enabled in this ROM? Its automatic enabled every time I restart using faux app
[Nexus 7 (2013) Android Development] qwerty123321:
where is the download to release6?
[Nexus 7 (2013) Android Development] prstorero:
It's back some number of pages. It was a beta so you won't find it in the OP. You can do a search for it, though.
[Nexus 7 (2013) Android Development] jassycliq:
I'll do an official release today. Was playing with the kernel settings to make sure there's nothing wrong.
[Nexus 7 (2013) Android Development] Imppy:
Jassy would you mind posting your settings (with faux app) for v6 once you release with?
[Nexus 7 (2013) Android Development] jassycliq:
Shouldn't be enabled. Plus swap isn't activated on my kernel.
[Nexus 7 (2013) Android Development] jassycliq:
Release 6!

Big changes here guys!

We've gone away from mpdecision. Now we're using the in kernel solution (msm_mpdecision) it allows more fine tuned control. We will be playing around with it to see if we can get more juice out of these tablets without giving up any performance. If you guys don't want to use it, I'll upload a second kernel that will re-enable mpdecision and set the default governor back to ondemand.

I've also included the fixes that [MENTION=4684315]flar2[/MENTION] has made for sweep2wake and doubletap2wake.
[Nexus 7 (2013) Android Development] Imppy:
Can we now choose mpdecision off in faux? Or we should use trickster?
[Nexus 7 (2013) Android Development] jassycliq:
Its off by default. Like I said, I'll release another kernel with it on by default if you guys don't like this new one.
[Nexus 7 (2013) Android Development] Imppy:
Should I use trickster to control this or faux turning off will be good enough?
[Nexus 7 (2013) Android Development] sherpa:
Unless my eyes are playing tricks on me, but, I have gone through all the posts and I cannot find any free app mentioned that supports this kernel. Could you please help me? I'm still new to this kernel thing. :)
[Nexus 7 (2013) Android Development] jassycliq:
Trickster to both of you. Faux just has snake charmer which allows you to lower the max CPU freq and keeps it there.
[Nexus 7 (2013) Android Development] Imppy:
Thanks for your reply...what settings are you using for trickster ?
[Nexus 7 (2013) Android Development] jassycliq:
Right now defaults.
[Nexus 7 (2013) Android Development] yuyuyuyu1:
Any problems running Release 6 on the stock ROM?
[Nexus 7 (2013) Android Development] ac7822:
Is temperature throttling on by default in your kernel. In Trickster the soc temp limit toggle is set to off. But in the thermal control menu it says thermal throttle is set to 70* and frequency is at 384.

I was thinking maybe the soc temp toggle was the stock throttling and the thermal control menu was your way of implementing it into the kernel. I just want to make sure there's some sort of throttling enabled so I don't cook my tablet
[Nexus 7 (2013) Android Development] JesseTron:
Can you explain how smartmax works vs ondemand? Got a huge boost on quadrant when I switched from smartmax to ondemand. Thank you for all your hard work.
[Nexus 7 (2013) Android Development] jassycliq:
Basically my main reason for choosing smartmax over ondemand is because ondemand simply goes to max cpu freq quite often.

Even while watching Netflix I felt like it spent too much time on higher frequencies. Smartmax will ramp up/down easily to 594mhz (while screen is on)

Reason it doesn't lag much is because it still goes to higher frequencies, but also because msm_mpdecision has a touch boost. By default core0 goes to 1026mhz and core2 810mhz (hopefully saving battery, without too much hit on performance, if it does I already have a few things we can do to make it smoother)

Any and all benchmarks will suffer because of this. Is there a impact on performance? Yes, but in my experience it isn't major seeing as I can play Vice City full resolution without a hiccup. Once again if you guys have issues tell me and we'll see about fixing it.

The kernel uses intelli-thermal. It does a better job than thermald and allows for more fine tuned control (if wanted). I'm not sure how Trickster messes with those settings honestly so I cant tell you. Though I just realized that I haven't turned intelli-thermal on by default(Qcoms thermald is though) -_- don't worry though by default there is a thermal solution present and running (so your setting is wrong, it shouldn't boot that way)
[Nexus 7 (2013) Android Development] jassycliq:
Adding to my other response. The kernel actually has a fix that [MENTION=4195844]show-p1984[/MENTION] created for a bug that all kernels have when turning off thermald. Which means that if you're on a kernel that doesn't have that fix, if you turn it off then back on, it'll never throttle...
[Nexus 7 (2013) Android Development] ac7822:
Weird cuz I uninstalled my kernel control apps reinstalled the kernel and the temp throttle toggle (soc temp limit) is still set to off by default. So should I just go ahead and toggle it on so I have temp throttling?
[Nexus 7 (2013) Android Development] jassycliq:
Yes :)
[Nexus 7 (2013) Android Development] Gareee:
So for release 6, we just flash the new version, reboot, install trickster, start it and grant superuser permissions. No setting adjustments at all?

(When I do this, my quadrant score dropped down to 4717, probably stock settings.
[Nexus 7 (2013) Android Development] jassycliq:
Like I said before, benchmarks will take a hit. The question is if the ui is as smooth as before?
[Nexus 7 (2013) Android Development] Gareee:
The ui has always felt smooth on my nexus 2013.

But its my R6 quadrant score almost the same as the standard clock out of the box version?
[Nexus 7 (2013) Android Development] jassycliq:
If you want quadrant to go back up then try using ondemand instead.
[Nexus 7 (2013) Android Development] conan1600:
So all in all this kernel is pretty smooth. Should post some really good battery life running smartmax and defaults. Personally I lean to power rather than battery so for now I'll stick with R5 with mpdecision on but this release is awesome for the battery lovers. You have lots of power and lots and lots of battery
[Nexus 7 (2013) Android Development] show-p1984:
[MENTION=3424800]jassycliq[/MENTION]

Need buildbot? :)
[Nexus 7 (2013) Android Development] pilotgav:
Lol. Ya we all thought it
[Nexus 7 (2013) Android Development] jassycliq:
Lol yeah... Just a bit xD I'm going through some personal issues right now though so I'll have to get in touch with you some other time. Thanks! :D
[Nexus 7 (2013) Android Development] Gareee:
I just had a random reboot on facebook (first ever with my tablet) and after rebooting, I decided to check this thread for news or updates.

My tablet is now frozen on chrome on this thread. The power button does not respond, and of course I can't even do a battery pull.

(This was on cleanroom 1.3)

Is there any other way to power down a frozen tablet?

The only thing I can think of is to wait for the power to die, and then recharge it.
[Nexus 7 (2013) Android Development] show-p1984:
Long press POWER + VOL DOWN until you see the bootloader.

boot into recovery (select recovery with VOL DOWN/UP keys and acknowledge with POWER).

connect to your pc.

adb pull /proc/last_kmsg

upload here.

Jassy will take a look I guess :)

That's ofc if there was even a last_kmsg generated, sounds like a wtf error. (What a Terrible Failure)

The hard reboot would have definitely generated a last_kmsg, except if kgsl crapped out.
[Nexus 7 (2013) Android Development] Gareee:
I managed to do the long press power down after about 10 minutes.

Its booted normally again, but I'm going to roll back to r5 for a while.

The worse thing was if I had to return it, I was stuck displaying the first page here on overclocking the tablet!
[Nexus 7 (2013) Android Development] squashpile:
Just received a Netflix update for 4.3 fixes and optimization. Thought you may be interested since you were talking about testing Netflix and battery.
[Nexus 7 (2013) Android Development] Gareee:
I ended up just flashing the stock kernal here, and here is a quadrant screens hot incase anyone wants to Compare stock to results.
[Nexus 7 (2013) Android Development] squashpile:
The volume is too damn high
[Nexus 7 (2013) Android Development] Gareee:
LOL.. just saw that and removed that attachment. taking screenshots on this tablet is a pita.

EDIT: Screenshot power + volume down is MUCH easier than power+ screenshot UP. D'oh!
[Nexus 7 (2013) Android Development] jassycliq:
You should install release 5 :) I think you'd like it better. I'll be playing with aroma installer this week for the first time trying to get the installation set up then.
[Nexus 7 (2013) Android Development] jassycliq:
Renaming version 6 seeing as some of you guys don't like the changes.

Will add 2nd one soon with Qualcomms mpdecision instead :P
[Nexus 7 (2013) Android Development] qrsy2k:
Hi jassy thanks for your nice work. I am having trouble in editing the config file for sweep2wake/doubletap2wake. I used rootexplorer to edit but it always revert back to its original values.
[Nexus 7 (2013) Android Development] squashpile:
I have had no issues with 6 that I'm aware of.

I did just reflash r5 cleared davlik and now all cores are stuck @ 1.5..lol. Uninstalled and re-installed Faux and same thing. I'm about to put 6 back on.
[Nexus 7 (2013) Android Development] jassycliq:
adb shell
su
mv /system/bin/mpdecision_bck /system/bin/mpdecision

or if you're using terminal emulator

su
mv /system/bin/mpdecision_bck /system/bin/mpdecision

Since I was moving away from MPDecision on version 6 i had to get rid of it. There are three ways for this:

1) Rename it. By far the easiest and more user friendly considering that its something most users can undo.

2) Remove entry from ramdisk. Just as simple for me, but it comes at a price. Normal users won't be able to undo this since they probably don't know how to pull the boot.img and undo the changes in the ramdisk.

3) Use an init.d script. I guess I could've gone this route but msm_mpdecision was set as the default so if the init.d script didn't kick in soon enough both msm_mpdecision and Qcom's mpdecision would be running at the same time! o.o

I chose the first one.
[Nexus 7 (2013) Android Development] squashpile:
Thanks for the info jassy. No /bin here. I'm looking..

root@flo:/ # su

su

root@flo:/ # mv /bin/mpdecision_bck /bin/mpdecision

mv /bin/mpdecision_bck /bin/mpdecision

failed on '/bin/mpdecision_bck' - No such file or directory
[Nexus 7 (2013) Android Development] jassycliq:
blah sorry forgot system

adb shell

su

mv /system/bin/mpdecision_bck /system/bin/mpdecision

Forgive me, not being myself at the moment :l
[Nexus 7 (2013) Android Development] yellowdie:
I installed v6 and didn't have any issues. I like it as it is. The only weird thing is that my gov was still ondemand as default. I cleared Trickster's app data and rebooted--still not defaulting to smartmax (I changed it manually and it sticks, it just wasn't default). Thoughts?
[Nexus 7 (2013) Android Development] jassycliq:
Could be that the governor overrides weren't removed from the ramdisk :(

If you're running CM or anything with the performance tab it might be that you have ondemand ticked on boot? Not sure honestly, plethora of reasons come to mind.
[Nexus 7 (2013) Android Development] squashpile:
Good to go :good:

Thank you!
[Nexus 7 (2013) Android Development] Gareee:
I probably will tomorrow, since it gave me at least 100 points higher on quadrant, which means I should see some performance boost.

After that freeze earlier, I'm spooked, so I'll give dicking around with it a break for the rest of the night, and just enjoy it as it is now.. ;)
[Nexus 7 (2013) Android Development] ac7822:
So far v6 is running good for me. Performance wise putting the governor back to on demand gives me the same benchmark scores as version 5 in the 8,000s on quadrant. But on v6 with the gov on smartmax in real world use I didn't notice any performance drop off, playing some 3d games I didn't have any stutters or anything performance was flawless. Haven't had v6 long enough to really test the battery. Theoretically should mpdecision off save battery even if we put the governor back to ondemand?

Awesome work man
[Nexus 7 (2013) Android Development] squashpile:
8K on Quadrant on Stock ROM? What clock speeds?
[Nexus 7 (2013) Android Development] yellowdie:
[FACEPALM] Gotta love user error issues... Yep, it was the SlimRom Performance option that was set on boot. :eek:

So, once again, I'm likin' v6. :D Good work!
[Nexus 7 (2013) Android Development] ac7822:
DJ_I forgot the rest of his names unofficial cm build 8-4. Cpu 1.89 gpu 487 force GPU rendering on ondemand using thermald at 70*. I get 7000-7200 using smartmax with the other settings all the same.
[Nexus 7 (2013) Android Development] jassycliq:
Theoretically yes. Reasons:

1) MPDecision boosts the min cpu freq to 1ghz on touch for 2 seconds. That's a long time when it comes to things like this.

2) It automatically turns on core1 (2nd core) and does what 1st reason says.

Compare that to msm_mpdecision core0 boost to 1ghz (for fluidity) and core1 boosts to 810mhz for only 1 sec (and only boosts core1 if it was already on). On top of that, I've tweaked the numbers so that core2 and core3 would require a lot more load for a longer time to turn on.
[Nexus 7 (2013) Android Development] Gareee:
How did you take the larger screen shot? Is there a setting for that?
[Nexus 7 (2013) Android Development] jassycliq:
Just an FYI guys,

I've seen some other kernels say they do certain things and a lot of times it's either half-butt(ed) things, where only half of what should be done is done and that's why you guys see such performance compared to mine. A lot of the times I won't even mention what I do, sure I OCed the GPU but I also increased the bandwidth. I removed some debugging from the wifi driver, from the kernel itself also. I did -O3 optimizations on release 5. I added a lot of snapdragon optimized flags. So yeah... ;) just wanted to tell you guys that it's not just simple adding governors or removing certain things. :)
[Nexus 7 (2013) Android Development] ac7822:
I have no idea what your talking about. I just took a screen shot the normal way and inserted it as an image in tapatalk.
[Nexus 7 (2013) Android Development] qwahchees:
Can we get s2w on this?

nvm :c
[Nexus 7 (2013) Android Development] dark2099:
Don't want to tell you how to do what you do, but I do believe faux123 is getting one of these, so maybe just use msm-mpdecision, less show-p1984 gets one of these.
[Nexus 7 (2013) Android Development] mmikeee:
it's the lower version of the snapdragon 600 which is meant to be clocked at 1.5ghz. I've heard 1.7ghz, but i don't think this s600 is meant to be clocked at 1.9ghz but who knows!
[Nexus 7 (2013) Android Development] immunityx:
yup google underclock these to 1.5ghz not sure why! i guess for battery life? the default is 1.7ghz for the s600 chips
[Nexus 7 (2013) Android Development] jassycliq:
He's also going to implement faux sound :P

Remember, Its just an option, the kernel will boot with Qualcomm's MPDecision by default. You'll have the option to use the other hotplug drivers though, which is the goal. From my experience some kernel devs will not implement something that another dev has created or done, which sometimes leaves a user wanting. What if I want the best of both worlds? That's what got me started :) If I like it, it goes in (as long as it doesn't hinder performance)

EDIT: to clarify on the last part. This does not mean this is a kangfest kernel with a whole mess of governors and schedulers and all that jass. It just means that the kernel will have the best features :) so no brazillian wax :P

For those of you who don't get the reference, there's a governor or scheduler (can't remember honestly) named brazillian wax.
[Nexus 7 (2013) Android Development] dark2099:
So you are right, not so sure why I posted that, but going to give this kernel a try now.
[Nexus 7 (2013) Android Development] Malvarose:
Is this any better than tiny? Or different? I dunno which to flash.
[Nexus 7 (2013) Android Development] jarjar124:
Look in op to see difference

Sent from my Nexus 7
[Nexus 7 (2013) Android Development] trvbone:
Man with all of the home improvements going on I've barely been able to play with it, now we've got root recovery kernels roms.

I must say the faux sound is a necessity I feel the speakers are kind of quiet can't wait to get rooted and get my kernel on.

This kernel should work with trickster mod right
[Nexus 7 (2013) Android Development] bckrupps:
im just learning about kernels not a noob otherwise lol. if I flash this and bump the processor to 1.7ghz is there and other changes I need to make to offset it or will it even make much of a difference?
[Nexus 7 (2013) Android Development] jassycliq:
Yeah, once faux gets his N7 I hope he creates something more powerful like faux speaker for the N4. Raising the gain isn't the best thing to do. It'll distort music and such. I tried it a few mins ago lol

yes trickster mod should work.

You can change the GPU governor. It also has parameters to increase performance or powersaving. Later on I'll add a conservative gov for the GPU for the battery lovers.
[Nexus 7 (2013) Android Development] Mike318:
Sorry noob question, but I'm used to nightlies... if I flash this kernel and don't like it how can I revert? Running twrp
[Nexus 7 (2013) Android Development] jassycliq:
Backup your boot.img before flashing :) twrp allowed this.
[Nexus 7 (2013) Android Development] Mike318:
Crap...I screwed that one up...got all excited and flashed :)

Can you upload stock kernel?
[Nexus 7 (2013) Android Development] jassycliq:
Yup, give me a min.
[Nexus 7 (2013) Android Development] Mike318:
You rock!
[Nexus 7 (2013) Android Development] jassycliq:
Not by my laptop so here's a zip with the stock boot.img. Just unzip in your twrp directory and restore. Maybe someone will be able to post a flashable zip before I get home?

https://dl.dropboxusercontent.com/u/21516504/xda/stock-boot.zip
[Nexus 7 (2013) Android Development] Mike318:
Thanks. It's not urgent but I'm having some transition effect lag, so I want to flash stock kernel back and see if it persists.