yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] flar2:
That's right, only the lowest voltage is changed. The CPU spends most of its time at the lowest frequency, so using less voltage there is an effective way to save battery. And almost every device will be stable with a slight undervolt at 384MHz.

The one danger, and I don't know if it's true on the Nexus 7 or not, is lowering the voltage too much can affect bluetooth and sound. This is the case for some people on HTC One, and a lot of people on HTC One XL, One S and EVO 4G LTE. All of these have Qualcomm/Krait boards.

You have to experiment on your own for undervolting other frequencies, that's far too risky to have as an installer option.

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

I'm going to play around some more with the thermal. I've never seen a device that throttles so quickly. But we still have to protect the hardware, so some degree of throttling will happen. I'll try to make it less noticeable.
[Nexus 7 (2013) Original Android Development] :
Nexus 4 throttled a lot so its the same issue it seems. It might be throttling but it has never for me on the stock kernel -shrug
[Nexus 7 (2013) Original Android Development] Poser:
I have witnessed the "throttling" via monitoring tools... But it has not adversely affected either the UI or UX...in any discernable way (in my completely subjective opinion). Overall... The flo has easily been the smoothest android experience I have had (I have owned EVERY galaxy iteration, n10 and tft700)...in no small sample size.
[Nexus 7 (2013) Original Android Development] :
Will you ever add an option in the kernel to tune the touch screen via Move Filter etc..? There are many of us that have touch screen issues. Many of us are almost sure its a problem introduced in the kernel in the latest OTA update...

I have your kernel running right now. Still same issues.

But other than that. I love it. Keep up good work. Thanks:)
[Nexus 7 (2013) Original Android Development] ac7822:
Has anyone been having screen flickering running this kernel?

Elemental 0.8 + cm 10.2 and I'm getting some screen flickering every so often. The tablet doesn't lag or anything when it happens just flickers. I think its the cm build I'm using but wanted to see if anyone else was getting this before I go around changing up my whole setup. I never noticed any flickering on the stock rom and kernel setup and I ran that for about 3 days
[Nexus 7 (2013) Original Android Development] creeve4:
Is there any way to adjust the touchboost frequency? I read a lot of comics on my N7 and notice that the CPU spends about 40% of the time @ 1026 MHz during the time that I am reading/scrolling thought the comics. I know I can use intellidemand, but thought I'd ask.

As a followup to the high CPU usage during video playback, I have not been able to reproduce it after a reboot, the CPU sits at 384 MHz now.
[Nexus 7 (2013) Original Android Development] poondog:
No because it's set by mpdecision binary and is closed source from google/qcom
[Nexus 7 (2013) Original Android Development] mrshades812:
Hey guys, I noticed that if I swipe right on the top status bar it puts the tablet to sleep. I only noticed it because I use a swipe status bar for brightness mod. Every time I want a brighter screen, the screen gets really dark! lol

Anyone else have this going on, or am I on an island here? :)

Using Cleanrom and 2.6 of this here kernel.

Thanks.
[Nexus 7 (2013) Original Android Development] areizer0:
Can confirm. Swiping from left to right on the top of the screen will turn off the display.
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
Only have this when Sweep2Sleep is enabled and holding the device upside down :good:
[Nexus 7 (2013) Original Android Development] Ned_Flanders:
Will this kernel work for stock kitkat 4.4.2 (unlocked and rooted) on Nexus 7 2013 WIFI?

If so I just flash in recovery or fastboot like I do with my Xperia S?

Thanks :cool:
[Nexus 7 (2013) Original Android Development] poondog:
Will work. Only flash in recovery, no bs fastboot or anything this is a nexus :)
[Nexus 7 (2013) Original Android Development] Ned_Flanders:
Please help!

I flashed in recovery, followed the steps and it got the end of flashing and now it just turned off and wont turn back on.

What to do now?!

EDIT: nevermind I think it's back on, the TWRP seems to dim the screen too quickly and the buttons became unresponsive and nothing worked to get the screen on, now it just magically came back on in recovery. I need to check if there is a way to stop the screen dimming in recovery because that is just annoying.
[Nexus 7 (2013) Original Android Development] xanthrax:
wait for a minute or two and then touch the screen, it should bring the recovery menu... is flashing

sent from my Darkside of Nexus 7 LTE
[Nexus 7 (2013) Original Android Development] poondog:
This kernel still uses aroma right? It seems to crash randomly, leading a black screen. When the device is black, its not responding then hold power and vol down until it gets you to fastboot
[Nexus 7 (2013) Original Android Development] Ned_Flanders:
Thanks, yeah its back on I just panicked a bit, really the recovery should keep the screen alive at all times.

Thanks for the tip :good:
[Nexus 7 (2013) Original Android Development] jutley:
Quick question i flashed the qualcomm dalvik patches on stock if i flash this kernel do i need to reinstall the dalvik patches again?
[Nexus 7 (2013) Original Android Development] poondog:
Just answered same quejstion in n4 forum hahaha

Those patches are rom side, so flashing kernel won't touch them. Like, do I need to change my seat covers when I get new wheels for my car :P
[Nexus 7 (2013) Original Android Development] jutley:
I tried disabling my case magnetic flip open close cover but it wont work keeps shutting and on screen with case any ideas i edited the config file to 0 but still magnet cover seems to work?

Here are my benchmarks antutu stock 4.4.2 Elemental kernel 1.7ghz oc.
[Nexus 7 (2013) Original Android Development] GSLEON3:
It is not crashing. The screen is timing out in TWRP, which used to have a slider, but now defaults to 60 seconds. That is a TWRP issue, not kernel, not Aroma. I think you can change the value in the config file, don't remember which one. Or you can wait a long second & tap the screen, at which point, the TWRP lock screen will pop back up.
[Nexus 7 (2013) Original Android Development] billgs:
[MENTION=4684315]flar2[/MENTION]

Thanks a million for this superb kernel and your continuous efforts to further improve it. Are there any plans to add gamma control for nexus 7 2013 in the upcoming releases?
[Nexus 7 (2013) Original Android Development] Gareee:
I just tried flashing this with the latest cm11 nightly, and I get a garbled boot screen, and have to reflash cm11 to get a normal boot.

I was using this with cleanrom, and had no issues before with a modest cpu and gpu overclock.

Has something changed so this isn't compatible with cm11?
[Nexus 7 (2013) Original Android Development] Co.Tibi:
@ flar2. I read that there's this component on the nexus 7 motherboard: Qualcomm Atheros WCN3660 WLAN a/b/g/n, Bluetooth 4.0, and FM Radio Module. Can the FM Radio module be enabled?
[Nexus 7 (2013) Original Android Development] flar2:
Yes

It has never worked with cm, use Bruce's non-CAF version

already tried, unfortunately the answer is no
[Nexus 7 (2013) Original Android Development] KingVeto:
Ok I guess I need help...I have the Feb variant of the n7 and I'm running Team Gummy ROM...I tried to flash 2.6, but it won't boot...what am I doing wrong? Thanks guys...
[Nexus 7 (2013) Original Android Development] papikev:
Must ask the obvious but sometimes it can be overlooked....there are 2 versions of Team Gummy, one for Flo and one for Deb. You are sure you flashed the Deb version right?
[Nexus 7 (2013) Original Android Development] Gareee:
Whew! I was thinking it was me doing something stupid, or having a hardware issue.

Where would I find this? (Link?)

(I'll google it, but the info is vague and may not get me the results I need.)

EDIT: Think I found a link at www.33b3e3.com, but apparently they are over their traffic allotment, and google can't pull up the info.
[Nexus 7 (2013) Original Android Development] KingVeto:
Haha I know some people can be dense, man, but yeah it was the right version. The ROM wasn't the problem it was that I was trying to use a CM based ROM when the kernel only supports AOSP roms. I figured it out on my own.
[Nexus 7 (2013) Original Android Development] Nedlinin:
http://xdaforums.com/showthread.php?t=2545197
[Nexus 7 (2013) Original Android Development] KingVeto:
Much obliged, sir!
[Nexus 7 (2013) Original Android Development] Gareee:
Thanks!

Edit: This is for the old CM11 ROM, right? What I'd need is the non caf elementx kernal to flash over the cm 11 nightlys instead though, right?
[Nexus 7 (2013) Original Android Development] Nedlinin:
ElementalX *is* a non-CAF kernel.

CM11 is a CAF kernel by default.

Bruce has a non-CAF build of CM11 (the one I linked).

Match CAF/non-CAF roms and kernels.

So, ElementalX + Bruce's CM11 will work great (it's the config I use daily).
[Nexus 7 (2013) Original Android Development] balek:
Hi, just a quick question:

My non 'Y' OTG cable does not work when i enable otg+charge but it is working with this option desabled. I presume that I need to switch this option depending on wich cable i use. Is that right?

Tkx
[Nexus 7 (2013) Original Android Development] Nedlinin:
OTG+Charge disables host powered to the slave device.

OTG+Charge should work great if youre supplying power to both your N7 *and* the slave device on the other side of the OTG cable.
[Nexus 7 (2013) Original Android Development] balek:
I am using an usb stick, so i can not power it. So it should work with an external powered disk.

Thx
[Nexus 7 (2013) Original Android Development] Nedlinin:
Yep. Or even use a powered USB hub :)
[Nexus 7 (2013) Original Android Development] balek:
It is not working with my hub, i will try another one soon...
[Nexus 7 (2013) Original Android Development] Gareee:
Thanks for explaining that. Sounds like if I want to use the night lies, I need to find a different kernal, or I need to switch to his version of cm11 instead.

Not sure which is the best option, but it didn't look like Bruce's had been updated for a month or so.

I can probably dirty flash his cm11 though, so at least I won't have to set everything up again.

Something to mull over, I guess.
[Nexus 7 (2013) Original Android Development] Nedlinin:
Not sure why you think he hasn't updated in a month..

http://nedlinin.com/files/bruce2728/files/Mako/ - The newest build was.. yesterday
[Nexus 7 (2013) Original Android Development] Kev1000000:
Does anyone else have horrible standby battery when using OTG+Charge mode? Using BBS, I see an "msm_otg" wakelock that is eating everything up.

I realize OTG+Charge mode is a bit tricky, but is there a way around this?
[Nexus 7 (2013) Original Android Development] :
Reboot and it still go away.
[Nexus 7 (2013) Original Android Development] mirco_pa:
Hey guys, I want to switch from Franco's kernel to this. I know how to install it, but I don't know what should I do in case I want to go back to Franco's or stock kernel. I'm asking this because I saw that this kernel is not a single boot.img, but is divided into more parts. Can someone kindly help me?
[Nexus 7 (2013) Original Android Development] konradsa:
You need to wipe boot and system. For instance, Franco disables mpdecision. If you now flash this kernel without wiping first, your cores won't hotplug.
[Nexus 7 (2013) Original Android Development] flar2:
You don't need to wipe it, just dirty flash
[Nexus 7 (2013) Original Android Development] AarSyl:
But caches still need to be wiped, right?

_______________________________________

Phone: HTC EVO 4G LTE

Sense 5, S-Off

Tablet: ASUS Nexus 7.2

Rooted, Custom Rom & Kernel

_______________________________________
[Nexus 7 (2013) Original Android Development] schlager:
[MENTION=4684315]flar2[/MENTION], would you like to add support for usb wifi adapter? if not, could you point us to the kernel sources so i could give it a shot building the modules?
[Nexus 7 (2013) Original Android Development] nikr123:
There is already a person that have modified this kernel to do that.
[Nexus 7 (2013) Original Android Development] schlager:
tried searching but no luck... i am assuming its not just simply plug and play?
[Nexus 7 (2013) Original Android Development] balek:
Hi,

I would like to know if "Logitech Unifying" are include in this kernel? or in any kernel for KK

Tkx
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Caches dont matter for a kernel.

Sent from my Nexus 7²
[Nexus 7 (2013) Original Android Development] z31s1g:
Just tried it out. Doesn't work. Same ROM/Kernel combination (PSX&ElementalX) on Nexus 5 works. Maybe flar can make it work for N7 too?
[Nexus 7 (2013) Original Android Development] tashik19:
Please bring support for Wimax 4G modem! How will I connect 4G modem? :(
[Nexus 7 (2013) Original Android Development] Gareee:
I missed there were updates. Good to a now, because ia given up on a current cM11 and elementx combo. I'm living the c!11 night lies, but if he is staying current, then I'll probably switch to that cm11 build instead.

Performance of Cm11 is good, but some games are more fluid with the faster kernal installed.
[Nexus 7 (2013) Original Android Development] konradsa:
I think he was asking about coming from Franco. You need to wipe system, Franco changes some files there, for example mpdecision which he doesn't use.
[Nexus 7 (2013) Original Android Development] Kev1000000:
A reboot does not solve the msm_otg wakelock for me with this kernel while the device is still plugged in with the OTG cable (but not charging).
[Nexus 7 (2013) Original Android Development] Dovigoldberger:
Is it possible to use the febon 100 to connect a camera using this kernel?
[Nexus 7 (2013) Original Android Development] Kev1000000:
flar2, the msm_otg wakelock bug appears to be a known issue, and was fixed with this commit:

https://github.com/ktoonsez/KT747-JB/commit/f735dd79b031409263bf531f557af85a39e93321

Is it possible to include this fix for this kernel? I'll definitely throw some money your way for this fix.
[Nexus 7 (2013) Original Android Development] combatdeity:
Anyone have any idea how much battery roughly using the elementalX overclock for L2 cache and bus uses?
[Nexus 7 (2013) Original Android Development] tranhuy:
Flashed the latest version tonight with mostly default settings except I enabled sweep 2 sleep and double tap and fast charge...after kernel installed successfully my screen turned off and I cannot seem to power on my device even when plugged in...Can someone please help..thought I would give this kernel a try since it runs so smoothly on my nexus 5
[Nexus 7 (2013) Original Android Development] flar2:
Hold the power button down until it reboots. This is a known recovery bug, it will be fine and the kernel is installed correctly.
[Nexus 7 (2013) Original Android Development] tranhuy:
It worked..Thank you so much flar! Should have dug deeper into the thread but there are to many post and I would have never thought the issue was with recovery.
[Nexus 7 (2013) Original Android Development] just lou:
Thanks. This was driving me crazy also. Will installing a different recovery or version fix this? I'm searching, but can't find any info.

Excellent kernel BTW. :)
[Nexus 7 (2013) Original Android Development] quickstang:
Don't think so. I'm on the latest & get it as well. Still drives me crazy. Luckily I don't flash as much as I did with my phone or I probably would have switched.

Sent from my Moto X
[Nexus 7 (2013) Original Android Development] z31s1g:
I had the Aroma installer crashes with TWRP as well, till I disabled automatic screen timeout.

Weird enough, with the Multirom TWRP I'm using now, I can leave screen timeout enabled without the installer crashing at the end.
[Nexus 7 (2013) Original Android Development] ObiDanKenobi:
In TWRP settings, set the screen timeout to none - problem solved.
[Nexus 7 (2013) Original Android Development] just lou:
Battery life with this kernel is sick. I've got a couple hours of use in this afternoon, and still have 90% left.
[Nexus 7 (2013) Original Android Development] 1sik5Series:
I have a problem with OTG charge, every time I reboot the nexus it doesn't charge, I have to unplug it and the replug it for it to start charging. Also I have a 160 GB HDD hooked up, and every time it goes to deep sleep and the screen wakes up, I loose connection to the HDD, I have to reboot the nexus in order to reestablish connection. Anybody having the same problems?
[Nexus 7 (2013) Original Android Development] pingaan:
I can't seem to get my USB stick with exFat to mount, anything I'm missing? I'm running 4.3 so the choice of kernel version is 1.8, obviously.

I'm using Stickmount.

Cheers.
[Nexus 7 (2013) Original Android Development] schlager:
could be due to the lack of usb hot plug support. try bruce2728 rom and enable otg charge in either /sys/module/msm_otg/parameters/ or /system/etc/init.d/99kernel

let us know if it works

EDIT:

seems that i am seeing your issue as well. with the otg+charge cable connected at boot time, the tablet wont trigger charging. only once just the charger is connected, then the otg+charge cable will charge correctly
[Nexus 7 (2013) Original Android Development] dy2592:
Can you please tell me what exact settings you use or is everything default? I am very new to this. Thanks
[Nexus 7 (2013) Original Android Development] just lou:
Pretty much default. The very long battery life seems to be due to the ElementalX Governor. It rarely ramps the CPU to the max frequency.
[Nexus 7 (2013) Original Android Development] dy2592:
Thanks for confirming, thats what I chose too. Most of the options had are selected by default as well as having "default" next to the option but for undervolting, it didnt seem to specify so I just left all the options to what ever was chose first. I did turn off all the S2W and T2W options as the first page indicated they are major battery drains. If I am wrong please correct me.
[Nexus 7 (2013) Original Android Development] just lou:
I use the minimum amount of undervolting, and turned off s2w and t2w too. I don't think they are major battery drains though. I just don't use them.
[Nexus 7 (2013) Original Android Development] dy2592:
I guess I might be interpreting this statement wrong, but from the first page with the explanation of each option.

S2W/DT2W power key toggle

If enabled, turning the screen off with the power button disables s2w and dt2w to save battery (since s2w/dt2w cause significant battery drain)

Also you used the lowest undervolt? so whats it the 850min? or the lower ladder on the bot?
[Nexus 7 (2013) Original Android Development] just lou:
I did not notice "significant drain" when it was active, but if you don't use it, disable it.

Yes, 850.
[Nexus 7 (2013) Original Android Development] dy2592:
Oh, I also forgot to ask, did you happen to overlock yours? like to 1.7 or did you keep it at 1.5 or lower?
[Nexus 7 (2013) Original Android Development] just lou:
1.7. Gpu 450.
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
Battery consumption is at least twice as high, when those functions are enabled. Which makes sense, the device doesn't sleep (as much) anymore.

So if you consider double to not be significant, then yes, it's not significant. I think it is, but still use it as the power buttons s*cks enormously :good:
[Nexus 7 (2013) Original Android Development] nikr123:
I don't think the power consumption with these features enabled is that bad.
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
What is "bad"? Let's say you lose 4% a day without these features and 8% a day with. Is that bad? No. It is significantly more? Yes.

P.S. Tested this myself ad nauseam so it isn't guessing or something. Plus it's completely logical as well so I don't fully understand the issue anyway.
[Nexus 7 (2013) Original Android Development] just lou:
When I had it enabled for about a day and using the ElenentalX governor, it did cut my battery life in half. It was negligible. I used my N7 for an entire day with over 8 hours of screen time, and still had battery left. Maybe it uses twice as much during sleep, but it's still insignificant.
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
No kidding? When using the device it won't make ANY difference. Only idle drain is affected (much). So moot point.

Halve the battery life is not a significant difference? Okay, discussion can be closed, easy :good:
[Nexus 7 (2013) Original Android Development] just lou:
For the last time, it does not cut your battery life in half. If your tablet normally drains 2% during sleeping for 8 hours (which mine does), and it increases to 4% using s2w, it is completely insignificant. The normal user will probably see a 5% decrease in battery life if he uses his N7 every day and charges it every other.
[Nexus 7 (2013) Original Android Development] pschatz12:
Tried installing on the newest cm and I get a weird all blue screen with some lines on boot and then it is so laggy and unusable I have to flash stock cm kernel. I'm new to nexus bit have flashed cm before on other devices. Did cm update there kernel and maybe this kernel needs updating? Thanks in advance.
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
4 / 2 = 2. Double the idle-drain battery usage.

I charge after a week/ten days. So the added drain I surely notice. If you play a game for seven hours probably it will be "a bit less" noticable, sure.
[Nexus 7 (2013) Original Android Development] just lou:
Yes. If your charge your N7 to 100%, turn it on and let it sit idle without using it all until the battery dies, then "your" battery life will be 1/2.
[Nexus 7 (2013) Original Android Development] Larz2.2:
Since I edit battery threshold to 4100 to get 93% for every nightly I do and installing ElementalX, it would be nice if I could select it in Aroma...
[Nexus 7 (2013) Original Android Development] NovaSlim:
This kernel should be used with AOSP Roms, CM Roms are best with CAF kernels(including the stock cm kernel).
[Nexus 7 (2013) Original Android Development] Titchener17:
This ElementalX kernel/governor combined with SinlessRom (also found that I really like Clean Rom) with Operation Killjoy installed/ entropy on/rndg, while using DnsQache (w/out running polipo), and about forgot to mention Greenify (am super used to it on both of my devices by now) is straight-up awesome ! So far that seems to be the best combination for my personal taste and I have enjoyed experimenting with various great works shared by the many good folks of this wonderful community. Device works GREAT. Recently didn't pick up the FLO very much for a few random reasons and was blown away with how long/good battery life proved to be-bigtime kudos & giving thanks ! Opened it for anywhere from about ten minutes to half an hour (RARE/VERY LIGHT usage compared to normal in my case) every evening and sparingly on the weekend. This OKJ'd SinLess ElementalX'd out bad boy would just keep on keeping on. Thank you very much for your contribution I really appreciate your work !