yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] flar2:
Slightly better performance, probably minimal effect on battery. Not sure if either is noticeable to be honest. Once the device gets as fast and powerful as this, little tweaks have less of an impact.

If you're happy then stay with 0.8.

There are basically two changes since 0.8.

First is kernel-based thermal control, which means thermal throttling is a bit more gradual and less noticeable. This won't affect you if you don't play games or do anything CPU intensive.

Second is a small fix to sweep2wake, which makes it not work if more than one finger is touching the screen. This helps prevent accidental wakes.

After that, I probably won't be adding much more to the kernel. Unless there is something really interesting that comes along. I will probably make a Bulletproof kernel for this device as well.
[Nexus 7 (2013) Original Android Development] Okaham:
yep i did...

Kernel (Android OS) taking up 28.3%
Google Services taking up 11.3%
Android System taking up 10.4%
System (*wakelock*) taking up 6.2%
System UI taking up 3.3%

my battery went from 81% to 61% overnight...
[Nexus 7 (2013) Original Android Development] flar2:
That's too much. I would suggest doing a full wipe and reinstall, there is definitely something wrong with your system.
[Nexus 7 (2013) Original Android Development] Okaham:
full wipe and reinstall of my ROM or the kernel?

i'm thinking maybe to switch to CleanROM...or something haha
[Nexus 7 (2013) Original Android Development] flar2:
Wipe and reinstall your ROM. Then reinstall the kernel.

I'm still using stock ROM while I develop this, just for consistency and to rule out other factors. I will start checking out some ROMs once the kernel reaches version 1.0.
[Nexus 7 (2013) Original Android Development] BFirebird101:
Hey guys I installed v10 but I started getting a ghosting effect immediately. Any idea why? I'm on stock

Sent from my AOSP'd Droid DNA

ROM: Pio's PAC-Man HALO 7.13.13

Kernel: CRPalmer 3.0.2: Interactive, deadline
[Nexus 7 (2013) Original Android Development] A.C.Sanchez:
My minimum CPU frequency seems to revert back to 1026 no matter what I select. I tries top make the minimum 384 but it doesn't seem to save. Am I missing a setting? This is in CyanogenMod using their performance menu in settings.

Using v.10
[Nexus 7 (2013) Original Android Development] flar2:
I've developed a lot of kernels, but I've never heard of anything like that before.

That's normal if you're using ondemand. It will go back to 384 when you're not using it.
[Nexus 7 (2013) Original Android Development] boykomac:
A quick report: running .10 for two days now, zero issues, good battery life and great performance.

Any hint on what to expect in future releases?:)

Thanks,

B
[Nexus 7 (2013) Original Android Development] masri1987:
What's a bullet proof kernel
[Nexus 7 (2013) Original Android Development] Jonnyredcorn:
So I just had a random reboot but my tab wouldn't boot back up it got stuck at boot logo. I'm running cleanROM I've been running the kernel for 3 days or so and had no issues. Couldn't get a last kmsg because it wouldn't boot back up.

Also I tried to restore a backup with twrp recovery 2.6 or whatever the latest is and it fails at restoring my backups when it gets to /data, it restores /system then fails at data for ALL my backups including my duck backup. Does anyone else have this issue? Is there a more preferred recovery? I've always used twrp but it was giving me issues on my gs4 so I switched to philz.

AT&T Galaxy S4 Running Google Edition Kangbean 4.3 w/ ktoonez's kernel.
[Nexus 7 (2013) Original Android Development] TechSilver13:
With TWRP don't ever wipe the actual data of the phone to where you have to type yes. Did you check compress data? If so I think that could be your issue.
[Nexus 7 (2013) Original Android Development] oias.heeda:
A feature request I would love is screen Calibration. Not sure how hard this is to apply.

Btw fantastic Kernal. Love it
[Nexus 7 (2013) Original Android Development] Philaphlous:
Why does everyone think the screen is bad...this is by far the best screen I own...

Seems like 1.73ghz is the best performance, anything over that and it just throttles too quick, can someone else confirm that? Seems that geekbench goes up at higher clocks and antutu goes down...
[Nexus 7 (2013) Original Android Development] TechSilver13:
The reviews say the screen is bad so it must be! For 230 bucks this screen is fantastic. I love it. Sorry to the people that don't. Samsung has nice screens grab the galaxy tab 3.
[Nexus 7 (2013) Original Android Development] jlevy73:
Yes, the screen is good screen calibration is not IMO. Whites are more like beige but overall I am very happy with the screen. Not as good as my HTC one but I wasn't expecting that in a tablet (at least not at this price range).

---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------

Read this: http://xdaforums.com/showthread.php?t=2233665
[Nexus 7 (2013) Original Android Development] flar2:
I agree with 1.7 as the sweet spot. Any higher and you're generating a lot more heat for barely noticeable performance improvement, which is then countered by throttling anyway.

I'm going to add some thermal options (default, run cool or run hot) next release.

***************

I might take a look at that touch problem this weekend too. I didn't notice anything but I'm not using a case yet either. Consensus is that it's a grounding issue. I tested and it is less responsive if the tablet is on a non-conductive surface and you only touch it with one hand. MIne's not bad enough to worry about, but it's noticeable enough that I can try to fix it.

****************

Also ordered a slimport adapter, will test that this weekend as well. Don't expect that will need any tweaking on this device like it did on HTC One.

***************

Screen calibration is more of a future project. Don't know if it's even possible

***************

Other than that, the kernel is running flawlessly for me, so there's not much more to do.

.
[Nexus 7 (2013) Original Android Development] Jonnyredcorn:
I know that and I never compress my backups. I week say that when I actuary backed up it finished successfully very quickly. But it said successful.

AT&T Galaxy S4 Running Google Edition Kangbean 4.3 w/ ktoonez's kernel.
[Nexus 7 (2013) Original Android Development] ecs1984:
Yessir, hardly a beta anymore in my eyes! ;) Kernel has been flawless for me as well since I started with 0.7. I really appreciate you sharing your work, cheers.
[Nexus 7 (2013) Original Android Development] Szighy:
Is there a way to force the 3rd CPU core online when playing heavy games? I found the ElementalX kernel the best for gaming (dead trigger 2 runs smoothly even with tegra effects), but it lags when only two cores are active in Modern Combat 5. The 3rd core only jumps in for like 1-2 seconds, and then the game runs smoothly.
[Nexus 7 (2013) Original Android Development] InkSlinger420:
You can use the performance governor to max your cpu when it engages, may help..
[Nexus 7 (2013) Original Android Development] idCyber:
I'm using this kernel and it's amazing, makes my "flo" fly. Thank you flar2.

Sorry for the off topic but can a gamer that plays "resource hungry" games, recommend the best Android 4.4.4 custom rom for the "flo" ? Please PM me if you want to help me so we won't fill this topic with "bloatware". Thank you in advance and sorry for the off topic once more.
[Nexus 7 (2013) Original Android Development] Szighy:
Tried that already, doesn't trigger the 3rd core. Only makes core0 and core1 run on the highest frequency, and the 3rd one jumps in only for 1-2 seconds (just like on elementalx governor).
[Nexus 7 (2013) Original Android Development] upNsmokeAllDay:
I had same issue with only 2 cores being used, then I tried this kernel http://xdaforums.com/showthread.php?t=2809979 and all 4 are used properly.
[Nexus 7 (2013) Original Android Development] Szighy:
I tested it, I used System Monitor to monitor the usage, it really shows all cores are running, but it says all 4 are always running on the highest frequency all the time, however, performance was not better at all.
[Nexus 7 (2013) Original Android Development] bleuxeon:
Disabling fsync is not the default choice and 450MHz is higher than stock GPU frequency.

I don't say that the roots of your battery drain but at least start your tests with fsync enabled and GPU @ 400MHz.

Gsam Battery Monitor won't help you that much.

You need something to narow down your wakelocks reading : BetterBatteryStats would be the best for that.

Then you will know exactly what's keeping your device awake looking at wakelocks, partials wakelocks and even alarms when your screen was off.
[Nexus 7 (2013) Original Android Development] danaff37:
Also, elemental kernel uses a different cpu governor by default. There is an option in aroma to set it to stock (on demand I believe)
[Nexus 7 (2013) Original Android Development] flar2:
You should be getting about 0.2-0.3% drain per hour while idle with those settings. I don't know what the problem might be, but as suggested, try something like Better Battery Stats (free XDA edition is available) to get more details about the sources of drain.

Also try installing with no undervolting and use the elementalx governor.
[Nexus 7 (2013) Original Android Development] flar2:
Question for you guys:

Does the latest version of this kernel work fine on deb (the version with mobile connection)?

I can't remember if there were some differences introduced by the 4.4.3/4.4.4 updates.

Also, what else did I promise for the next update?

I recall:

- add the ability to flash touch firmware

-support logitech unversal hid

Anything else?
[Nexus 7 (2013) Original Android Development] BladeRider:
I am using Deb and I don't see any differences at all.

You had stated all the promises for the next update. How about an ElementalX tuner app?
[Nexus 7 (2013) Original Android Development] mdamaged:
A better world.

Also a ElementalX app like the fellow above me mentioned, I use Faux right now, and it works, but I'd certainly like one made specifically for this kernel, only because I'm not 100% sure how many of the functions actually are supported, I mean even though they show up in Faux app, I'm not always sure they'll work, like the battery charge heat throttler thing.

Anyways whatever you decide it's still my favorite kernel and I'll be happy either way.
[Nexus 7 (2013) Original Android Development] flar2:
The app is coming. I have beta releases for a couple of phones I support. Right now it's an installer/updater app that will notify of updates and allow you to download and install them in two clicks. I have a bit more work to do on the tablet UI before I release it for the N7. I will also be adding the ability to modify settings, but not right away. The aroma installer feature and elementax.conf will continue to be available for those who don't purchase the app.
[Nexus 7 (2013) Original Android Development] milan*SK:
Kfvj
[Nexus 7 (2013) Original Android Development] manueltts:
I'm with you bro...
[Nexus 7 (2013) Original Android Development] trjlive:
Thanks for the replies, guys. I bought BetterBatteryStats and will use it to figure out what's keeping my device awake when flashing this kernel.

I did notice something odd, though. In the Aroma selections, I was specifically disabling any of the swipe2sleep or double-tap2wake features. Then I would just boot up the device, assuming all is well, and let the device sit in standby for 24 hours to test drain.

Well, I installed TricksterMod just to look and see what the kernel settings were set to after flashing, and noticed that dt2w was enabled, which if I understand correctly, holds the device awake so it can monitor the screen for taps.

This might explain the extra drain I'm noticing. Just to make sure I wasn't accidentally enabling the option in Aroma, wiped the device and ran through the clean install steps, installed the kernel and made very sure to disable those options in Aroma. Booted up, immediately installed Trickster, and sure enough, dt2w shows as enabled. So disabling the feature seems to stick just fine after additional reboots. Just odd that even when disabling it in Aroma, it still boots up for the first time with it enabled.

Anyway, I've got a few other things going on today so I probably won't get a chance to test this again using these tips until this weekend sometime. But I will come back and post the results of what I find. BBS seems to be a lot more detailed than Gsam, thanks for the recommendation! :good:
[Nexus 7 (2013) Original Android Development] bleuxeon:
allowing lower voltage? :o

: http://xdaforums.com/showpost.php?p=54414732&postcount=3568
[Nexus 7 (2013) Original Android Development] flar2:
The wake functions only cause about 0.3% per hour extra drain, it's still something else
[Nexus 7 (2013) Original Android Development] trjlive:
Hmm, ok well now I'm really curious to figure out what it is! I'll let you know what I find out after I've done some more testing this weekend. :)
[Nexus 7 (2013) Original Android Development] boardlord:
How can I check if the gamma module is actually loaded? I downloaded faux's app, and it tells me that it this kernel doesn't support gamma adjustment (and gamma is set to 1 in elementalx.conf)... Thanks!
[Nexus 7 (2013) Original Android Development] flar2:
in terminal or adb shell type:

lsmod

you should see msm_kcal_ctrl listed.

colour and gamma definitely work, just check with fauxclock. With other apps, only RGB colour works (no gamma).
[Nexus 7 (2013) Original Android Development] mdamaged:
I can confirm, gamma works perfectly fine with faux123 KEP.
[Nexus 7 (2013) Original Android Development] boardlord:
Yep, strange. Faux's display app doesn't work,but KEP works.. But I am using Synapse to set the tweaks, and those two apps can conflict each other.. Ah well, decisions, decisions...
[Nexus 7 (2013) Original Android Development] mdamaged:
Well to be fair the store page states it's only for Nexus 4 and 5. IIRC they handle gamma totally different than the N7 does.
[Nexus 7 (2013) Original Android Development] boardlord:
I bought the app a while back for my N4.

Shame but you get what you pay for ☺ I guess I'll live without gamma for now ☺
[Nexus 7 (2013) Original Android Development] fradbari:
hi, is possible to set manually the amper of the charge? Maybe decreasing it below 1.3 A?!
[Nexus 7 (2013) Original Android Development] draco259:
Does this kernel support audio through USB?
[Nexus 7 (2013) Original Android Development] NovaSlim:
Not at this moment, will have to wait until Android L becomes official.
[Nexus 7 (2013) Original Android Development] Divine_Madcat:
Is this related to a problem you are having? Heat?

You wont' gain any real increase in battery longevity by dropping the charge current. The battery (well, entire sub system) is designed to take 2A, and is not harmed at running at rated spec. Also keep in mind, that a lower current will limit the ability for the device to run and charge at the same time...
[Nexus 7 (2013) Original Android Development] meshdub:
Not to beat on a dead horse, buuuuut... How about deep sleep on power loss for those of us running tablets in cars? :)
[Nexus 7 (2013) Original Android Development] fradbari:
thanks for your answer; really i've no problem with charging.

However i know that there is a little connection between battery life and charging time.

I don't know how i can set this value manually. Can i?
[Nexus 7 (2013) Original Android Development] andyman_187:
Anyone else have issues with games (specifically Injustice, Batman Arkham Origins and Into the the Dead) on the latest CM11 nightly? Those games won't start at all for me on the CM version of ElementalX. On stock kernel they work fine and on nightlies before Aug. 3 with ElementalX installed. Same issue with the Facebook app as well. Any feedback is highly appreciated, thanks!
[Nexus 7 (2013) Original Android Development] hypophysis:
Yes it does. OTA USB cable -> USB DAC. Works flawlessly.
[Nexus 7 (2013) Original Android Development] draco259:
Sweet, thanks!
[Nexus 7 (2013) Original Android Development] flar2:
Didn't Timur release something that solves this problem? I know it costs money, but this requires practically rewriting the usbhost driver, which is a major undertaking. I just don't have enough time to do it.

Honestly, I wouldn't worry about the battery life (as in the lifespan of the battery, not how long you can go on a charge). My wife watches 90% of her tv and movies on this tablet, often letting movies play all night while even she's sleeping (it can be annoying, lol), which can amount to many hours a day screen time. I see no battery degradation yet.

If you are concerned, enable the battery life extender option, which will only charge to 93-94% and prolong the battery's life.

Running cm for the past few months and having no problems. I haven't updated recently though.

I'm about to start work on this kernel again, as soon as I can find a few spare hours.
[Nexus 7 (2013) Original Android Development] ecs1984:
Any suggestions for the small number of us that are not able to get BLE to work? It worked perfectly for a while, but it's been many moons since BLE has worked for me despite setting it everytime I flash and confirming it in the .conf file. Never switched ROMs or changed anything else with my device, never tried another kernel or installed Trickster/other apps that might cause conflicts :confused: I'm happy to provide any info that might help troubleshoot :)
[Nexus 7 (2013) Original Android Development] NovaSlim:
If your battery is showing 100%, check to see if your battery voltage is below 4.2V(Gsam battery monitor or another monitoring app), if that's the case then BLE is actually working despite showing 100%.
[Nexus 7 (2013) Original Android Development] Larz2.2:
Your device is like my LTE. Assumung you've just updated you're OS, you have to (a) install ElementalX, (b) boot the system up, (c) then edit the elemental config file (or copy one you've modified in the past -- because ElementalX properly overwrites any preexisting one on first start), and then (d) reboot yet again for the change to become active. I change the value to 4100 to get about 93%.
[Nexus 7 (2013) Original Android Development] andyman_187:
ART seems to be the culprit. Switched back to Dalvik and all is well again. Weird though, I've been running ART for a few months now, and no problems until M9 and latest nightly.
[Nexus 7 (2013) Original Android Development] meshdub:
Ahh thank you! Did not know he finally released his solution. Only looked on this forum, which, understandably, doesn't list it.
[Nexus 7 (2013) Original Android Development] Larz2.2:
Thermal Throttle

I wanted to throttle down in temp, so I set it to cool during an ElementalX install. When I tested with a power hog game I play everyday, it ran 70C, instead of the normal 65C. I checked the config file to verify it was indeed set to cool (THERM=1). I then edited/set it to hot (THERM=2), rebooted to test and found it still ran 70C. OK, back to default (THERM=0), reboot and the temp peaked at 65C. Seems like Thermal control is not having the desired effect on my LTE. Temperature was measured by Android Tuner.
[Nexus 7 (2013) Original Android Development] flar2:
UPDATE!!!!

Finally I had some time to update the kernel. I added support for the Logitech Unifying Receiver, added the ability to update the touch firmware (see this thread: http://xdaforums.com/showthread.php?t=2800308) and patched the latest fauxsound updates from faux123. This version is now compatible with the ElementalX app, beta testing is now open to the Nexus 7, see here for details: http://elementalx.org/nexus-7-2013-update-kernel-and-app-support/

For users of the app, please note that you need to install the custom version of 2.14 at least once before the express version in order to get the updated config files. Otherwise the express version will set you up with kernel defaults.

Stock/AOSP:

ElementalX-N7-2.14

Cyanogenmod/CAF:

ElementalX-N7-2.14-cm

Changes:

--latest updates to fauxsound

--support Logitech Unifying Receiver

--security updates and fixes

--installer updates

--ElementalX app compatibility

--support forced touch firmware update
[Nexus 7 (2013) Original Android Development] BladeRider:
BAM! Somehow I wish my Nexus 7 is with me right now...Cat wait for the new kernel and app
[Nexus 7 (2013) Original Android Development] NovaSlim:
Thanks for the updates & EX app support. Downloaded and installed kernel(express version) via the app without issue :good:. One thing that should be added though: the EX app is missing landscape mode which should be added for a tablet app.
[Nexus 7 (2013) Original Android Development] Megaflop666:
Downloading and installing now. Brb...
[Nexus 7 (2013) Original Android Development] flar2:
Indeed, I'll be completely re-doing the UI when I add the rest of the features.

Also note that you'll get default settings if you install the express version first.

You need to install the custom version once in order to get the updated config files.
[Nexus 7 (2013) Original Android Development] Megaflop666:
Running smooth as usual!! Love the new app as well.
[Nexus 7 (2013) Original Android Development] roguesyko:
Flawless on my flo as always! Thanks for the great work!

Sent from my Flo rocking Validus ROM and ElementalX kernel!!,
[Nexus 7 (2013) Original Android Development] bland.life:
Just bought the app for the express installer!
[Nexus 7 (2013) Original Android Development] flar2:
You don't need to buy the app if you don't want to. My kernels will always be free. I do need a source of revenue, however. I've spent a lot of time and money on development. Just this week I bought a Logitech unifying receiver because I needed to test something. It really is to support development, as it was getting a bit unsustainable, especially trying to buy the latest devices.
[Nexus 7 (2013) Original Android Development] lbretth:
LTE Compatability

Will this kernel work with the LTE version of the 2013 N7?
[Nexus 7 (2013) Original Android Development] xanthrax:
It is written in the title so, yes and I'm using it right now on lte

Sent from my Darkside of LG G2
[Nexus 7 (2013) Original Android Development] lbretth:
My bad, I didn't realise that was what deb meant and I didn't read the title that thoroughly. :eek: Thanks for the quick reply.
[Nexus 7 (2013) Original Android Development] marsaltito:
Did anyone tryed latest with kalipwn ?
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Logitech Unifying Receiver is working great for me [MENTION=4684315]flar2[/MENTION]

Thanks for the update ;)
[Nexus 7 (2013) Original Android Development] Divine_Madcat:
Lets keep on topic guys. This thread is not about other Dev's applications; discuss the kernel at hand, and other discussions elsewhere (or better yet, leave some things unsaid...)
[Nexus 7 (2013) Original Android Development] BigJPNut:
Pretty sure you need a modified kernel..
[Nexus 7 (2013) Original Android Development] spartacus279:
Just to be sure is this kernel compatible with the 2nd developer version of android L ?
[Nexus 7 (2013) Original Android Development] jayplusone:
Nope

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] spartacus279:
Thanks for telling me , I was just about to flash it . will android l perhaps be supported in future updates?
[Nexus 7 (2013) Original Android Development] jayplusone:
No problem. I'm sure it will once L is released to the masses :)

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] Birosso:
Working well. Thank you.
[Nexus 7 (2013) Original Android Development] kersey:
Just flashed this kernel but now have no WiFi. I try to turn it on and it just freezes. Am running Cleanrom on my Flo

Sent from my Xperia Z2
[Nexus 7 (2013) Original Android Development] idCyber:
I've used the AOSP version of this kernel on CleanROM 3.6 and had no problem with the Wi-Fi. Also I had no problem on SlimKat 7.2.1 and Paranoid Android 4.5 Beta 2.
[Nexus 7 (2013) Original Android Development] marsaltito:
Double check if its kernel for your device & rom . :)