yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] jassycliq:
They only apply that one time. Only gamma settings on N4 were applied at each screen on.
[Nexus 7 (2013) Android Development] 0.0:
Forgive me for not searching the thread. I'm on the app. Does this kernel work with fauxdisplay? Can I control screen colors?

Sent from my Nexus 4
[Nexus 7 (2013) Android Development] jassycliq:
Nope. N4 only feature (hopefully not for long?)
[Nexus 7 (2013) Android Development] compuguy1088:
Here's another mirror for Version 5 if anyone needs it:

https://owncloud.compuguy1088.com/public.php?service=files&t=b36b0350f8166e70a73d4df322d44867
[Nexus 7 (2013) Android Development] Covart:
Sweet Kernel. I applied your settings and jumped 7000 points on Antutu. Pretty impressive jump from bone stock settings to CM10.2 on Jassy Kernel. Stability and temps remained very good throughout the test as well. Images below.

Total = 24113

________________________

Posted from my Chromebook
[Nexus 7 (2013) Android Development] Imppy:
How's the battery with this setting

Sent from my Nexus 7
[Nexus 7 (2013) Android Development] Covart:
I don't know. Only just put this kernel and rom on today, and altered settings. Gotta give it a few days to settle in.

Most important thing to me was stability and temperature variations. And this kernel, with this rom gave very good results (on my Nexus 7² anyway.) I am pleased.
[Nexus 7 (2013) Android Development] jassycliq:
I was playing GTA Vice City with full resolution and graphics for 3+ hours and battery was nearly done (mabye 20/30%, don't remember) So I guess its decent, I'll be trying netflix streaming all day later today though, so I'll see how it does then.
[Nexus 7 (2013) Android Development] ÜBER™:
Giving this a whirl since im sick of stock throttling every 10 minutes.

Is there a perfered app to control the kernel? I have every one in existence pretty much... faux, franco's, morific's, bigeyes etc etc.
[Nexus 7 (2013) Android Development] teh roxxorz:
Trickster mod is working nice; but no access to the snake charmer setting, which you can access in the faux app.
[Nexus 7 (2013) Android Development] ÜBER™:
Kk, read the features a little more closer and looks like most features come from faux so ill use his app. Not really a fan of his kernels, more of a Franco kernel user.. but this will hold me over until Franco puts out a FLO kernel. Pretty unbiased when it comes to kernels anyways :good:
[Nexus 7 (2013) Android Development] Imppy:
I'm using faux app

Sent from my Nexus 7

---------- Post added at 09:39 PM ---------- Previous post was at 09:39 PM ----------

I'm confused what is shake charmer

Sent from my Nexus 7
[Nexus 7 (2013) Android Development] justibasa:
I was wondering the same thing.
[Nexus 7 (2013) Android Development] teh roxxorz:
I've never used either of their kernels, from the devices I had in the past, so i'll wait and see. Though I'm pretty easy on kernels, try em out and see which i like best, between features and performance. There's one in the original dev section with swipe to wake / sleep, which looks interesting, but lacks performance features, so staying here for now.

To the last 2 quotes: snake charmer is a setting that will cap all the cores at X frequency.
[Nexus 7 (2013) Android Development] jassycliq:
I love using faux's kernels personally but I find that sometimes he just makes too many changes which tend to start causing issues as time goes on (at least for me) so usually I just kang his main features :)
[Nexus 7 (2013) Android Development] teh roxxorz:
There we go. We need the BREAD to live...butter is a bonus.
[Nexus 7 (2013) Android Development] matthew0776:
Flashed V5 with new cm build and is running great...thanks for the kernel. :thumbup::beer:

Sent from a Candy Painted N7 (2013)
[Nexus 7 (2013) Android Development] dark2099:
Everything is better with butter.
[Nexus 7 (2013) Android Development] Waynato:
Then only kernal app you should us with this kernel is faux, it doesn't have mp decision customization but whenever I mess with that it jus makes things worse
[Nexus 7 (2013) Android Development] angellsl:
How is the battery life with this kernel?
[Nexus 7 (2013) Android Development] pilotgav:
Do we need to know all this to use this kernel? :) All I know how to do is change the CPU/GPU frequencies lol.
[Nexus 7 (2013) Android Development] teh roxxorz:
Technically no. Setting your frequencies is a good base, but the moar you know, the better. ;)

But like he said, single core in sleep = must have.
[Nexus 7 (2013) Android Development] jassycliq:
No, if you leave the stock hotplug driver (MPDecision) then you're fine just flashing and adjusting frequencies. What i was talking about is for people who like more control whether it be better battery or better performance, even a middle ground.
[Nexus 7 (2013) Android Development] teh roxxorz:
Right, that's what I was talking about. Probably sounded better in my head then when exposed to the real world.
[Nexus 7 (2013) Android Development] jassycliq:
Its alright haha, just want to clarify to avoid confusing.
[Nexus 7 (2013) Android Development] prstorero:
Where can I get a log of a hot reboot? I can't remember what its called (something like ksmlog or something?) I've been using the kernel for days and tonight just started getting random hot reboots for some reason. It happened twice while playing monster blade and once while on the xda app
[Nexus 7 (2013) Android Development] ÜBER™:
/proc/last_kmsg

Pull that file and rename it a .txt and attatch it here.
[Nexus 7 (2013) Android Development] prstorero:
Got it. Its actually just kmsg now (at least for me).

http://cl.ly/text/46351e1U0b09
[Nexus 7 (2013) Android Development] ÜBER™:
No that's another file... It's what I said it was.
[Nexus 7 (2013) Android Development] prstorero:
Last_kmsg doesn't exist for me

prshosting.org
[Nexus 7 (2013) Android Development] ÜBER™:
Odd... Must of not created a log for some reason.
[Nexus 7 (2013) Android Development] prstorero:
Guess I'll check again after it happens. If nothing comes up, I guess I'll be stuck :P

prshosting.org
[Nexus 7 (2013) Android Development] jassycliq:
last_kmsg is only available on the first boot after the reboot.

Edit: Were you undervolting? Anything new you've installed? A lot of factors come into mind. Just asking because you said it ran fine for a few days.
[Nexus 7 (2013) Android Development] prstorero:
I haven't done any reboots after the random hot one. No extra mods installed and no undervolting. I may do more default settings to see if it continues

prshosting.org
[Nexus 7 (2013) Android Development] jiggytom:
I flashed v5 on minimus rom and now I get stuck on Google logo with unlock icon. I tried wiping (data system and factory reset) and reinstalling the rom and I get the same thing. Also flashed v3 and same result.

What can I try next? Could the higher CPU freq fried it?
[Nexus 7 (2013) Android Development] Waynato:
The only ROM that doesn't suck with this kernel is the unofficial CyanogenMod release, well all kernels I've tried tdo significantly better with cm
[Nexus 7 (2013) Android Development] teh roxxorz:
Can we refrain from making pretentious comments that completely discredit all personal opinions?

sent from the 7th nexus of 2013
[Nexus 7 (2013) Android Development] ÜBER™:
V5 worked just fine for me on Minimus. Maybe try Faux's enhanced stock kernel. Its not a bad alternative, I happen to be using it myself.
[Nexus 7 (2013) Android Development] jiggytom:
I can't do anything to get passed Google boot logo though. I wiped and flashed another rom and still the same thing. I'll try another kernel later but I thought that would have over wrote what I flashed.
[Nexus 7 (2013) Android Development] jassycliq:
It wasn't flashing my kernel that did that. The kernel boots up with stock voltages and stock frequency.

On top of that, the fact that you flashed another ROM (which include their own kernel) and it's still stuck on the google logo is another sign. Check out one of the threads elsewhere where they have a restore script or something, to check whether you can boot stock firmware.
[Nexus 7 (2013) Android Development] jiggytom:
Flashed minimus and I booted fine.. Then rebooted and flashed the kernel. I just flashed clean rom, still stuck at Google boot logo. I think the next step is the fast boot restore from another thread.
[Nexus 7 (2013) Android Development] teh roxxorz:
Are you sure you don't have a bad download?

sent from the 7th nexus of 2013
[Nexus 7 (2013) Android Development] jiggytom:
Restored to stock using the ADB program and I was able to boot. Then installed minimus from the same zip as before and it worked. Installed v4 of this kernel and i,m up and running...will try v5 later again...not sure what caused all this
[Nexus 7 (2013) Android Development] conan1600:
o I have tested and retested my butt off on every kernel available. So far this kernel even at its lower CPU OC is the fastest IMHO. Due mostly to the GPU OC. A 87MHz GPU > 200 MHZ CPU. The kernel also seems to run smoother in CM 10.2 to me as well in real world environment. Of course the other kernels are still being developed but interesting stuff none the less to a novice such as i.

I'm curious, do you intend to keep developing this Jassy? Also any plans to raise CPU to 2.1 since the tablet seems to boot to it well? Perhaps other mods?

The antutu that is the highest score in almost all ways is Jassy R5. The lower scored Antutu is Faux123
[Nexus 7 (2013) Android Development] Imppy:
How does it compare to faux?
[Nexus 7 (2013) Android Development] Waynato:
Its works better for me my CPU scores are at least 4k higher than faux on quadrant... That's way better however I get worse GPU score cause the GPU clocks won't stick...and the thing I wrote about cm ROM is just plain fact I have not seen any other ROM with better performance I tried each of them, the other ROMs appear to just be for customization
[Nexus 7 (2013) Android Development] Imppy:
What settings are you using?

---------- Post added at 11:39 PM ---------- Previous post was at 11:39 PM ----------

And how's battery?
[Nexus 7 (2013) Android Development] conan1600:
Faux123 is still very beta I would say but runs well, just not as well for me as this one. Given a few hours Faux 123 might come up with mind blowing stuff though so you never know. As far as how they compare in my PERSONAL experience this Kernel kicks arse atm. On CM 10.2. I only tested cm not any other Roms sooo
[Nexus 7 (2013) Android Development] jassycliq:
Yes, I'm continuing with support.

I'm testing a new kernel release as we speak. I actually just finished all the crap for building -O3 (linaro with linaro), s2w, and removing some debugging.

I will keep my method of OC instead of going with faux's, no need for it IMO. What we have now is better as far as we can tell so we'll stick to it :)

I might release in a bit, but I do have a beta I'm going to ask someone to test for something so let's see how that goes :)
[Nexus 7 (2013) Android Development] conan1600:


As far as battery goes I get 9 hours screen on time, heavy use with video and browsing, no gaming. good idle time as well.
[Nexus 7 (2013) Android Development] jassycliq:
90C is pretty high for core throttling o.O
[Nexus 7 (2013) Android Development] Waynato:
Dunno what you do differently but it works, I appreciate the effort...

---------- Post added at 06:58 PM ---------- Previous post was at 06:54 PM ----------

That's what it is on default though...
[Nexus 7 (2013) Android Development] jassycliq:
Oh damn, didn't even see that... Let me fix that!!!
[Nexus 7 (2013) Android Development] prstorero:
Just wanted to throw out an update on my hot reboot issue. I believe the problem was being caused by twrp for some reason. After my last hot reboot, I still had no last_kmsg so I decided to reboot. Once I did that, all went down the drain. It no longer booted, wiping all 4 areas did nothing, wiped all 4 again and flash the ROM fresh, that did nothing. Even restored my stock backup, still no boot. Nothing I did could make it boot so I started completely fresh with flashing stock images. The reason I think the issue is twrp is I had the same issue on my S4. After any ROM flash, if I rebooted the device would be done for; causing me to odin back to stock. After the third or fourth time I switched to oudhs. The problem was instantly solved. Now I'm doing the same on my nexus and am hoping for the best. I know neither the kernel nor ROM I used could have caused an incident like this.

prshosting.org
[Nexus 7 (2013) Android Development] conan1600:
I may have raised that with a misplaced thumb, I did raise it to 70 on frequency throttle limit but gonna back that down to 65. Doesn't really matter though as I don't see my tab getting there anyway so hasn't had an effect. Going to test out my undervolts next and see if I can find spot
[Nexus 7 (2013) Android Development] teh roxxorz:
Here if you need bodies thrown at it.
[Nexus 7 (2013) Android Development] jassycliq:
It's a test for CIFS. I don't use it so I don't know if it works.
[Nexus 7 (2013) Android Development] Waynato:
Went from full charge to 70% in 2 hours doing nothing but benchmarks with a lil bit of web browsing on a bit harsher settings than what was just shown as in I had all CPUs on and at 1.9ghz
[Nexus 7 (2013) Android Development] teh roxxorz:
Oooo. I don't use it either; so I may / may not be as helpful, this pass around.
[Nexus 7 (2013) Android Development] jassycliq:
http://xdaforums.com/attachment.php?attachmentid=2163038&d=1375571057

Test kernel with S2w and doubletap to wake if you wanna try it.
[Nexus 7 (2013) Android Development] teh roxxorz:
On it shortly

sent from the 7th nexus of 2013

---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------

Double tap is working great. Sweep to wake isn't working for me.

sent from the 7th nexus of 2013
[Nexus 7 (2013) Android Development] jassycliq:
Check with trickster to see if its on. I just tried both and they work.
[Nexus 7 (2013) Android Development] JesseTron:
Working great! Very smooth! Thank you.

Double tap to wake is pretty slick. Doesn't work all the time though it seems. Guess that's why it's still in testing phase. Great addition!
[Nexus 7 (2013) Android Development] teh roxxorz:
Sweep to wake. Slide you finger across the side of the screen closest to the led.

S2w is working. I was using the wrong side. Is it possible to have it at the bottom in landscape view?

sent from the 7th nexus of 2013
[Nexus 7 (2013) Android Development] jassycliq:
Slide you're finger across the nav bar right to left (<-----) to turn off the screen and vice versa to turn on. Double tap around the same area to wake it up also.
[Nexus 7 (2013) Android Development] jassycliq:
You'd have to ask flar2. Its his work and I'll leave it be.

Don't want to sound so direct but I can't write code like that. I'm a n00b compared to him or any other kernel dev.
[Nexus 7 (2013) Android Development] teh roxxorz:
Fair enough. I can do that.

sent from the 7th nexus of 2013
[Nexus 7 (2013) Android Development] JesseTron:
It works perfectly once I know how to use it right. Thank u guys!
[Nexus 7 (2013) Android Development] Imppy:
Does sleep to wake uses up battery?
[Nexus 7 (2013) Android Development] Deathman20:
Just my experience, running stock kernel I have tipped 66c on the cores gaming and charging. Still ran like a champ.
[Nexus 7 (2013) Android Development] farmer bobathan:
Does this kernel include loop device support?
[Nexus 7 (2013) Android Development] jassycliq:
Every android device since at least a year or two ago if memory serves me right has had loop support.
[Nexus 7 (2013) Android Development] jassycliq:
Yes, of course. The question should be "how much more does it use" When done right, it should be a negligible amount. Then of course if you don't want to use it then you can turn it off :)
[Nexus 7 (2013) Android Development] Waynato:
I have not been able to mount any IMG on a loop device it keeps saying operation not supported so I dunno
[Nexus 7 (2013) Android Development] jassycliq:
I'll double check then.
[Nexus 7 (2013) Android Development] Imppy:
Conan still using those settings you posted?
[Nexus 7 (2013) Android Development] jassycliq:
Taken from my defconfig

You're looking for " CONFIG_BLK_DEV_LOOP"

#
# Default contiguous memory area size:
#
CONFIG_CMA_SIZE_MBYTES=16
CONFIG_CMA_SIZE_SEL_MBYTES=y
# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
# CONFIG_CMA_SIZE_SEL_MIN is not set
# CONFIG_CMA_SIZE_SEL_MAX is not set
CONFIG_CMA_ALIGNMENT=8
CONFIG_CMA_AREAS=7
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
[Nexus 7 (2013) Android Development] rubene66:
Running good here with aosp oc perfect for gaming thanks for the great kernel
[Nexus 7 (2013) Android Development] Waynato:
What keeps causing this?

Edit: that screen doesn't show the operation not supported but it usually says that to but regardless it doesn't work, I just don't understand if maybe there is a different command for the nexus 7 2013 to mnt loop devices

Sent from Razor
[Nexus 7 (2013) Android Development] conan1600:
Mostly. Backed thermal down some but other than that. I keep meaning to undervolt but get to doing other things.
[Nexus 7 (2013) Android Development] Imppy:
Mightr try your settings'...9 hours on screen with oced CPU and gpu is quite amazing...let me know your UV values
[Nexus 7 (2013) Android Development] farmer bobathan:
I get similar errors on faux's kernel and this kernel both with the unofficial cyanogenmod build. I wonder if it's an issue in the busybox?
[Nexus 7 (2013) Android Development] Imppy:
Conan your settings are amazing...good battery ans performance...did you start using?
[Nexus 7 (2013) Android Development] conan1600:
My settings are mostly jassy's setting my friend. A few small changes on what I linked but not a lot. As for my UV testing I'm still in it, not a lot of free time today. but so far so good. By the way I've had more success with the noop I/o scheduler lately. Try it out.

Also I have found that a global -24 MV under clock is safe and stable FOR ME. Benchmarks haven't suffered a bit and I haven't had any hangs in the few hours I've played with that. Good place to start if your interested. I haven't done a battery test on it but I'd imagine another 10 or 15 minutes with the way I use my tablet. If you get a hang on your it will probably be because of the lower values in your lowest. Lock just kick it up by 12 or even back to 900 default
[Nexus 7 (2013) Android Development] Imppy:
Nice going to try that and let you know

---------- Post added at 11:41 AM ---------- Previous post was at 11:38 AM ----------

What benchmarking app you use?
[Nexus 7 (2013) Android Development] jassycliq:
For those wondering about battery life with s2w, that was it sitting overnight.
[Nexus 7 (2013) Android Development] looney2388:
yeah my battery drained kinda crazy like that overnight. i was wondering what in your kernel that i enabled made my battery drained, so im guessing it is the s2w cus i got it enabled?
[Nexus 7 (2013) Android Development] jassycliq:
Yeah, I'll be making some changes soon to enable init.d even on stock ROMs then using an init.d scripts to turn it on/off depending on what you guys want. I didn't want to use Aroma but I guess I'll have no choice.
[Nexus 7 (2013) Android Development] jassycliq:
Change of plans. I wanna stay away from aroma so i just turned it off by default. I've made some other changes to the installation method that will hopefully be cool for at least a few users.

Currently I'm having someone test a kernel that will hopefully have great battery life with minimal impact on performance.
[Nexus 7 (2013) Android Development] squashpile:
Just installed Jassy R5 and purchased the Faux app.

Very nice.. thanks for your work :good:
[Nexus 7 (2013) Android Development] whittikins:
Will double tap to wake use the same battery as slide, or are they different implementations? Thanks!
[Nexus 7 (2013) Android Development] looney2388:
question: im running version 5 the latest and my battery drained 3-4% in 8 hours in sleep-mode overnight, is that normal? ive never owned a android tablet before this one so i'm not sure
[Nexus 7 (2013) Android Development] teh roxxorz:
Yea, That's fine. Mine slept 6 hours last night and only drained 2%. If you left it in standby at that rate, you could easily see a week of standby life.

---------- Post added at 07:11 AM ---------- Previous post was at 07:09 AM ----------

No love here? :p lol

Though yea, i agree. Down with aroma.
[Nexus 7 (2013) Android Development] yellowdie:
Hey Jassy, I have v6-test3 installed and s2w/s2s and double tap both enabled. And my tab slept like a baby last night. I even woke it up this morning with a double tap to make sure it was enabled.

3% drop in 9 hours. :):D:laugh::good:

On an unrelated note, I had Wifi OFF the entire night, but it shows as active for the full almost 9 hours (says it's off, but still active). So I don't know how I feel about Google's new 'locate via wifi' feature. Granted, 0.3%/h is still really good drain even with the location setting going!
[Nexus 7 (2013) Android Development] flar2:
Yes, sweep2wake/doubletap2wake will not drain battery unless you are touching the screen a lot while it is trying to deep sleep. If you just set the tablet on a table or something it will be fine.
[Nexus 7 (2013) Android Development] yellowdie:
That's what I figured, and was what I was showing. But the post from Jassy that I quoted was showing high drain that supposedly came from s2w being active.
[Nexus 7 (2013) Android Development] whittikins:
My doubletap2wake is working (not using sweep2wake), but it is definitely intermittent sometimes. It will work great right away sometimes, and other times it takes many many double-taps before it finally wakes up. Does this happen to anyone else, and is there a known cause or solution? I am using ParanoidAndroid currently, but it's a brand new wipe and flash with barely any extras (except this kernel).

Thank you!
[Nexus 7 (2013) Android Development] jassycliq:
I've yet to update s2w. Next kernel release should have some tweaks that flar2 has done. But from what I've heard dt2w does have the hit or miss issues, not sure if the update completely fixed it or not though.
[Nexus 7 (2013) Android Development] flar2:
Doubletap2wake is still a work in progress. If jassy adds my latest commit it works better but not perfect.

Sweep2wake is working well but I intend to make some big changes to it and add some options.
[Nexus 7 (2013) Android Development] Jeeko:
[MENTION=3424800]jassycliq[/MENTION] can you answer to my PM please? :)
[Nexus 7 (2013) Android Development] jassycliq:
Wait up, I'm at work. Only doing small responses when I can. Yours is going to take a bit to write out.
[Nexus 7 (2013) Android Development] Jeeko:
Sorry, doesn't matter, I can wait ;)
[Nexus 7 (2013) Android Development] whittikins:
Ok cool. I actually can't get sweep2wake to work at all currently. I've tried rebooting and it's definitely turned on in trickster. Using the test version provided a few posts back.
[Nexus 7 (2013) Android Development] jassycliq:
Are you swiping along the bottom part where the led is? Swipe along the nav bar.
[Nexus 7 (2013) Android Development] Gareee:
I'm on cleanrom 1.3, and just flashed this, and I'm only getting 5543 on quadrant.

Did I do something wrong?
[Nexus 7 (2013) Android Development] prstorero:
Quadrant can be highly unreliable.

prshosting.org
[Nexus 7 (2013) Android Development] Gareee:
What would you recommend, and what results should I be seeing on r5?
[Nexus 7 (2013) Android Development] jassycliq:
Everybody else is getting 8k+ on quadrant and 24k+ on antutu and 8k on 3d mark o.O don't know what could be wrong. Ive only used stock and CM.