yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Nazo:
Well, this is why I like using a software solution such as SetCPU instead of something at the kernel level for voltage control. If things go wrong with SetCPU there are a lot of backup options including the ability to install a safe mode file from the recovery that makes it disable all functionality long enough for you to reconfigure it.

Lowering voltages further increases battery life, yes, but it also is easier on the CPU. Less heat, less wear, etc. Maybe a subtle difference overall, but I like to make my hardware last. On that subject though, less strain on the battery is also a good thing -- especially since these are much harder to replace (yes, you can open it up and connect a new one (in fact, if it's like the 2012 model it's not even soldered in, but I haven't opened my 2013 Nexus 7 to see.) I can easily buy third party and even first party batteries for my phone for very cheap, but last time I looked for a Nexus 7 battery (back with the 2012 model) I couldn't find any for less than $70 or so at the time.

But also I was hoping there was some way to get SetCPU to do it because you can control the voltage at every speed individually. I'm still testing, but it looks like on my phone I can actually lower all the voltages a lot more than I ever even thought. Up to 756MHz in fact I have everything set to the minimum of 700mV. At the 1026MHz I usually have as the maximum speed (not many things show any visible benefits from higher that I can tell) it's still only 875mV. (So far it has passed a fair stability test at all speeds from the minimum up to the stock maximum -- I won't be overclocking, so I didn't test beyond that.)

It's not really issues. I just liked the settings I came up with on my phone with a slightly reddish, overall darker feel. It's more comfortable to me. (Though I guess supposedly it's supposed to be better for battery life to use less of the other colors besides red anyway. I forget why, but the LEDs that produce red use less power than blue or green -- I guess due to the lower frequency, longer wavelength. I doubt it makes any really noticeable difference, but it's a nice thought and it is the screen that uses the most power by far outside of games after all.)

Anyway, I guess I'll take another look at the Trickster control. I mostly didn't like it because so much is locked away in a paid version even though this is for a tool that just doesn't work in most kernels... I really liked the idea of it being built in though and I'm kind of wondering why my phone running the same nightly as my tablet shows it while the tablet doesn't.
[Nexus 7 (2013) Original Android Development] NovaSlim:
I am getting an interesting result with Battery life extender on my Nexus 7

SlimKat 6.4 Weekly+ElementalX 2.13 w/ Battery life extender enabled(BLE=4200), undervolted to 850mv with every other setting stock.

This theoretically should limit my Battery to 93% & below 4.2V but now it charges to 100% and stays below 4.2V at the same time( I have discharged to below 90% and charged back to full a couple times with this same result).

Attached a screenshot, Is this an expected behavior and is anyone else getting this result?
[Nexus 7 (2013) Original Android Development] ecs1984:
BLE hasn't worked for me in ages (mostly on SlimKat, occasionally DJL's; sometimes UV'ed, sometimes not), but it's not the reason I use ElementalX so I didn't really mind. [MENTION=4684315]flar2[/MENTION] If I can give info to help troubleshoot, I am happy to do so.
[Nexus 7 (2013) Original Android Development] rajat_delhi:
I have a question.

note 3 has leap authentication but Nexus 7 does not have it. Due to this we cannot connect to leap authenticated wifi networks. Can we port leap wifi from note 3 to Nexus? If yes, can anyone please advice how?
[Nexus 7 (2013) Original Android Development] bleuxeon:
If someone know this.... :

What are exactly the thermal throttling policies applied when you choose between :

cool

default

hot

?

I have changed it in Trickster and would like to know what are the defaults values for the 3 modes.
[Nexus 7 (2013) Original Android Development] Phoenix09:
cool: 80, 82, 90, 100

default: 80, 85, 92, 102

hot: 85, 90, 97, 105

default frequency limits are: 1512000, 1350000, 918000, 384000 respectively
[Nexus 7 (2013) Original Android Development] bleuxeon:
Thanks a lot!

In fact without knowing the default values, I did set it up much lower ... :

80, 84, 88, 92 :cyclops:

Now, I wonder if ElementalX's defaults are the same in stock rom's kernel.
[Nexus 7 (2013) Original Android Development] Nazo:
Wouldn't the Nexus 7 be using a 4.35V li-po battery? I assumed it would just change what the system perceives as 100% to a lower value. If so, it's just saying that it's charging to roughly 93% the capacity of the battery, but not necessarily saying 93% in the software then. (But I would imagine that if you were to look in the recovery menu you'd see the real value then.) I'll try to do some testing on mine to see what results I get too as I've also turned on that option. I actually went all out though and erased the battery stats, then completely discharged my tablet, so now I'm still waiting for it to fully charge. EDIT: I can't find any actual details on the battery (I got curious about it and something else I wanted to double check along the way so finally opened up my tablet -- btw, the battery does use a connector rather than being just directly soldered in or anything.) If I look on the cell itself it says 3.8V which to me kind of implies that it might be the higher charge (since the "3.7V" number is supposed to be something of an average I would expect manufacturers to use 3.8V to indicate a higher maximum charging voltage, but there isn't really any standard and I've seen it on some 4.2V batteries I believe.) EDIT2: Found this. It probably is a 4.35V battery, so if you're getting a charge of 4.2V it's probably exactly what you should be seeing: http://xdaforums.com/showthread.php?t=2469261
[Nexus 7 (2013) Original Android Development] WSZR:
What application to color & gamma control?
[Nexus 7 (2013) Original Android Development] DrErect:
https://play.google.com/store/apps/details?id=com.nexus4displaycontrol
[Nexus 7 (2013) Original Android Development] WSZR:
It doesn't work.
[Nexus 7 (2013) Original Android Development] mdamaged:
Faux123 KEP...not free though... You can also look at voodoo calibration...but that's still very much in early development.
[Nexus 7 (2013) Original Android Development] DNarsingh:
I do believe trickster mod also allows for color control and it's free.
[Nexus 7 (2013) Original Android Development] w0ng3r:
hey flar2, any chance USB OTG Hosting will be updated so that we don't have to replug the USB cable from the tablet each time it loses power?Thanks
[Nexus 7 (2013) Original Android Development] fradbari:
Hi, i've Last paranoid release, and Franco kernel r17; can i flash aosp o cm last Version?

Thanks
[Nexus 7 (2013) Original Android Development] jayplusone:
Dirty flash your rom. If PA is CM based then flash the cm version. If not flash the AOSP version. I'm don't stray from stock rooted rom.
[Nexus 7 (2013) Original Android Development] StopHammertime:
So, that's what's been happening to me. Interesting. Glad to know it's not something I was doing wrong, at least.
[Nexus 7 (2013) Original Android Development] bkob024:
unstable

After flashing this multiple times in order to try to stop the reboots my device became ridiculously unstable even after choosing very few options (might as well not even use it in that case). Every app would stop responding as soon as it boot. It also caused my ROM to go to the setup page. It got so bad in a matter of 10min that I had to restore my device to a backup because I couldn't just reflash my ROM image to overwrite the kernel, problem persisted.

Using a nexus 7 2013 LTE, running CM Snapshot M8
[Nexus 7 (2013) Original Android Development] flar2:
Not sure what's going on with your device, but thousands of people use this kernel without issue and it is 100% stable.
[Nexus 7 (2013) Original Android Development] InkSlinger420:
The only time I ever had app fc issues was when I undervolted too far..Made a mess of things...otherwise I've been using this kernel for a looonnnnggggg time on multiple Roms without a problem ..just my 2¢.
[Nexus 7 (2013) Original Android Development] curtdragon:
I'm on liquid ROM 4.4.4 deb and this breaks wifi
[Nexus 7 (2013) Original Android Development] mdamaged:
Sounds like you applied that wifi zip fix that was going around, you have to revert that since that 'fix' breaks kernels that support the proper wifi setup.
[Nexus 7 (2013) Original Android Development] curtdragon:
No I didn't. Clean flashed Liquid and PA Gapps then flashed the kernel. Did it twice and same results.
[Nexus 7 (2013) Original Android Development] mdamaged:
The rom might have that fix baked in. You may also have used a kernel which messes with the ramdisk in which case flash stock kernel first before ElementalX. It's definitely not the kernel at fault.
[Nexus 7 (2013) Original Android Development] curtdragon:
Um okay, thanks for the analysis.... If it works before the Kernel then it's something with the kernel. Not a big deal though I'll try another ROM. Just thought this was where you say hey I tried your kernel with this ROM and it does this.... but I'm obviously wrong
[Nexus 7 (2013) Original Android Development] mdamaged:
It's not quite that simple. Previous kernels can leave things behind, and elemental uses whatever ramdisk you had, so if it changed something like how it uses wifi, it will break other kernels that do not mess with your ramdisk... anyhow I'm just trying to help.
[Nexus 7 (2013) Original Android Development] jayplusone:
Might be the something you flashed or did you come from another custom kernel? If so dirty flash your rom again THEN flash the kernel. I've used ElementalX on 3 devices without issues. If I could flash it on my toaster I would.

Exactly!
[Nexus 7 (2013) Original Android Development] curtdragon:
Again thanks. I'll just use another ROM.

I did these exact steps

Prior to flashing I deleted everything on the SD card except the downloads folder which is where I have the ROM and other files that I need to install.

I rebooted into recovery and did a data wipe.

I flashed Liquid 3.0 then logged in and connected to wifi

I let Google auto download my apps.

I let it settle for a few, I didn't configure anything and then rebooted and flashed the Kernel

wifi doesnt work at all. I dont mean it wont connect I mean you can't even turn it on.

I did this procedure twice and nothing.

What ROMs are you guys using because this one doesn't work with the current version of the kernel
[Nexus 7 (2013) Original Android Development] jayplusone:
I'm on stock rooted rom from scrosler
[Nexus 7 (2013) Original Android Development] StopHammertime:
I swear, something about this Kernel and fastcharge just don't work. I've tried two different versions of the kernel, with two different ROMs, and all sorts of different charging hardware, and it is just plain not working. Stock kernel and ROM charge fine, so I know it's not a hardware issue on the tablet itself.

Anyone else with similar issues?
[Nexus 7 (2013) Original Android Development] Cryptecks:
I can personally say that I've never had Fast-Charge not work, running Stock rooted or PA latest. Just FWIW.
[Nexus 7 (2013) Original Android Development] StopHammertime:
Well, that's good to know, I suppose. Wonder if perhaps the indicator just isn't updating correctly. I did see that happen last night at one point.
[Nexus 7 (2013) Original Android Development] mdamaged:
Stock from google with xposed+GB.
[Nexus 7 (2013) Original Android Development] curtdragon:
I used Dirty Unicorns and that seemed to work great. Thanks
[Nexus 7 (2013) Original Android Development] mdamaged:
No problem. Glad it worked out for you.
[Nexus 7 (2013) Original Android Development] wantabe:
Damn... I love this kernel! Getting some pretty decent battery life with mixed usage. Today spent close to 1 1/2 hrs thrashing the hell out of my N7 playing some games and ended with 73% battery left which I don't think is bad considering the overclock. Running stock 4.4.4, stock voltages, ondemand governors, Xposed+GB, OCed 1728/450. Very much appreciated [MENTION=4684315]flar2[/MENTION], thank you sir!
[Nexus 7 (2013) Original Android Development] fradbari:
So, you solve this problem changing based rom?

I've last paranoid android and have the same problem......
[Nexus 7 (2013) Original Android Development] En Kee:
I use ParanoidAndroid and this kernel and don't have any issues.
[Nexus 7 (2013) Original Android Development] tashik19:
Fix it soon

Hey [MENTION=4684315]flar2[/MENTION] , I am facing touch issues. Please include this in your kernel as soon as possible. :( :( :( http://xdaforums.com/showthread.php?t=2800308
[Nexus 7 (2013) Original Android Development] ezas:
Well that is a bit abrupt.

Let me rephrase - I have stated having touch screen issues. I was wondering if you had considered adding this feature to your kernel. I know that it would be helpful to me, and maybe to others.

I love your kernel and thank you for your hard work.
[Nexus 7 (2013) Original Android Development] fradbari:
what?

i've done a clean installation of last paranoid android, after that, i've flashed elementax aosp kernel, twice, ad wifi still doesn't works!!!

Maybe i must do some particular action?
[Nexus 7 (2013) Original Android Development] En Kee:
I didn't do anything more. Flashed PA, then PaGapps, then ElementalX and reboot... Nothing more.
[Nexus 7 (2013) Original Android Development] tomic22:
The screen of my Nexus 7 2013 broke. Since the digitizer is not working the screen is still 100% functional.

Is there any way to install elemental X without Touch?
[Nexus 7 (2013) Original Android Development] mdamaged:
Yes. TWRP supports a mouse via OTG...it should work in Aroma, I guess you'll find out for sure if you try. Let us know if it works.
[Nexus 7 (2013) Original Android Development] tomic22:
My mouse (although perfectly working in android) didnt work in Aroma. I was with a little trial and error able to navigate using the volume and power button. It would be hhelpful if a retangle like around the checkboxes would also be around the buttons in the bottom.

Thanks for the help! :good:
[Nexus 7 (2013) Original Android Development] flar2:
You can also use the volume buttons to navigate and the power button to select
[Nexus 7 (2013) Original Android Development] mdamaged:
No problem. Maybe you can click on Feature Requests tab up top and ask for that stuff (though, that might be something that might have to be added by Aroma dev rather than the kernel dev, in which case try the Feature Requests tab here.)
[Nexus 7 (2013) Original Android Development] douger1957:
Forgive me if this has been asked and answered. Search hasn't revealed an answer. Is there a way to enable QI wireless charging and USB OTG?
[Nexus 7 (2013) Original Android Development] Nazo:
Well the author says an installer app is coming in the near future. When it comes out obviously there would be absolutely no troubles installing with a keyboard and/or mouse (or, for that matter, probably even a gamepad.)

I'm kind of curious what you can really do with a tablet without the touch interface working anymore though. Well, don't get me wrong, there's a lot it could technically still do, but it's a lot more trouble to do it and a cheap netbook would generally be better once you start attaching peripherals...
[Nexus 7 (2013) Original Android Development] Karlmadur:
NOOB

Sorry for this simple question, but when using this kernel on SlimKat, do I flash stock/ASOP or CM ?

Best regards and thanks in advance,

Karlmadur
[Nexus 7 (2013) Original Android Development] mdamaged:
http://xdaforums.com/showthread.php?t=2512241

First paragraph.

You should always do a nandroid of your /boot and /system anyway before trying a new kernel.
[Nexus 7 (2013) Original Android Development] KnifeFed:
Is this kind of battery usage / awake time normal? During install I chose default / stock everywhere. I'm mainly interested in swipe2wake but not if it costs this much battery.
[Nexus 7 (2013) Original Android Development] mdamaged:
Usage varies from user to user and rom to rom, so noone could really tell you what is or is not normal for you and your device. That being said, normally at idle my N7 2013 uses .3% per hour, with the 2wake options, it doubles to .6%.
[Nexus 7 (2013) Original Android Development] KnifeFed:
Well in that case, this is definitely not normal seeing as the kernel is responsible for such a high percentual drainage as well as keeping the device awake for 12 hours.
[Nexus 7 (2013) Original Android Development] mdamaged:
A BBS dump might show something I could work out, that screenshot doesn't help me much. Sorry.
[Nexus 7 (2013) Original Android Development] bland.life:
Not sure about USB OTG but my meenova USB card reader works.

So I suppose USB OTG is supported by the EX kernel.

Qi charging works too but I never thought that it is linked to the kernel.

Wireless charging my Flo right now :)

I never need to enable them.
[Nexus 7 (2013) Original Android Development] douger1957:
Yeah. I can get OTG to work or I can get wireless charging to work. I can't get both to work at the same time.

It'd simplify my automotive installation if both worked at the same time.
[Nexus 7 (2013) Original Android Development] hollywood084:
I'm having severe battery drain issues on this kernel. This is a daily occurrence. Check out attached screenshots. Does anyone else have similar issues. My N5 has the same problems with this kernel. All tap 2 wake and similar features are disabled. Stock ROM. Maybe its a rogue app. Hell if I know, I only have a few installed
[Nexus 7 (2013) Original Android Development] mdamaged:
Install BBS as system app, charge the device, let it sit idle for 4 hour or so, then post a BBS dump to BBS' thread and ask for help.
[Nexus 7 (2013) Original Android Development] Megaflop666:
Didn't see this question when quickly perusing through here...

Is there going to be an update to allow this kernel to play nice with android runtime?

I installed the kernel over top of stock clean ROM which was running with android runtime and it caused the system to go nuts and revert back to dalvik and it won't allow me to revert the system back to ART.

Other than that, great kernel, my nexus loves it. :good:

thanks
[Nexus 7 (2013) Original Android Development] flar2:
The kernel works fine with art or dalvik. Doesn't matter to the kernel whatsoever
[Nexus 7 (2013) Original Android Development] Megaflop666:
Strange... That's the only mod I've made since I installed clean ROM and switched to ART. I'll try again tomorrow, wipe, flash the ROM again, then the kernel. If I'm still having the issue, or if it resolves itself, I'll let y'all know.

Thanks

... let me play with your evil inside ...
[Nexus 7 (2013) Original Android Development] bleuxeon:
I can confirm that Cleanrom ART+ ElementalX works like a charm.

[MENTION=4684315]flar2[/MENTION] : I have made some tests with Glitch's test kernel that allow voltage as low as 500mV.

What I found is that, on my device that is PVS=3 so the most present PVS, 384MHz frequency was stable @ only 637.5mV :good: (600mV for 162MHz...)

Could it be possible you consider allowing at least 650mV in your kernel?

EDIT : here are the tests resluts attached
[Nexus 7 (2013) Original Android Development] Megaflop666:
Thanks for the info. I completely wiped the system again, installed clean ROM and elementalX kernel, and was able to switch the system to ART. Best I can figure is I did something wrong on the first two tries or something residual from cm11 & elementalX was on the nexus 7 and causing an issue.

... let me play with your evil inside ...
[Nexus 7 (2013) Original Android Development] KnifeFed:
I'm having the exact same problem as you can see from a few posts back.
[Nexus 7 (2013) Original Android Development] hollywood084:
I posted on the bbs thread as well, but haven't found a solution yet.
[Nexus 7 (2013) Original Android Development] just lou:
No issues here. I get almost 10 hours with the stock ROM.
[Nexus 7 (2013) Original Android Development] hollywood084:
Can you tell me a little bit about your advanced wifi settings? It's looking the kernel awake time has been reduced to minutes (double digits I think) from hours when I turned on wifi-optimization. Kernel is still number 1 though, with over 50%.
[Nexus 7 (2013) Original Android Development] just lou:
WiFi optimization is on, and WiFi is off when sleeping and not plugged in.
[Nexus 7 (2013) Original Android Development] Megaflop666:
What does your battery usage say in your settings? What settings did you select at install?

I have the opposite issue, my battery never wants to show. I have it currently OC at 1944 with the 850 UV on Clean ROM and I plug my tab in a couple times a week at most, and I use it all the time in the morning and evening when I'm home.

... let me play with your evil inside ...
[Nexus 7 (2013) Original Android Development] hollywood084:
No luck from the suggestions over there.

I re-installed the stock kernel and I'm still at 100% after one hour standby with no kernel drain. As I suspected, it's something to do with the kernel.
[Nexus 7 (2013) Original Android Development] mdamaged:
No, if it was the kernel, we'd all have the issue, and we do not. So while it may happen to you only with this kernel, it does not mean it is the kernels fault. This is obviously an app, ramdisk, or rom issue.

Do a full factory restore with all stock, no extra apps, then install the kernel.
[Nexus 7 (2013) Original Android Development] flar2:
There's got to be something going on with your setup, as the latest version doesn't have any changes from stock that would cause issues. All tried and tested and used by many thousands of people. I even got an email from some huge aerospace/military company that uses it for some reason (too bad I made it free, lol). I would do a clean install, wipe caches and see if that helps.
[Nexus 7 (2013) Original Android Development] hollywood084:
I got my n7 barely 2 weeks ago now, and I haven't even played with it too much. I rooted and fresh installed a few apps. I installed this kernel first thing as well. I have done cache and dalvik cache wipes with no luck. I have already tried reinstalling elemental with default settings and no special wake features (prior to reinstalling stock kernel).

My N5 had high kernel usage with elemental as well (not quite as high as the n7 though.). I installed Franco and its currently at 6 percent usage after 3 hours; much lower than elemental was.

I really like elementalx, but something is wrong. I'll probably give it another go tomorrow and do some more trial and error, but if I can run everything the way it is right now on stock just fine, then it should run just as good, if not better on elementalx.
[Nexus 7 (2013) Original Android Development] InkSlinger420:
I get 12 hours on this kernel oc'd no UV with 5-6 hours screen on time...by far the best kernel for my flo...this was my best day so far..

And my last idle test
[Nexus 7 (2013) Original Android Development] Megaflop666:
I haven't been able to use my tablet much since I unplugged it, but here's my stats since I last unplugged it 31 hours ago, and I won't need to plug it in for another day or so probably.

Sorry about the volume bar in the way, just noticed, let me fix that.

... let me play with your evil inside ...
[Nexus 7 (2013) Original Android Development] Megaflop666:
Better picture...

For some reason, couldn't delete the pic from the old post to upload the new one...

... let me play with your evil inside ...
[Nexus 7 (2013) Original Android Development] NekroWolfen:
I've been using .8 since it was released and I've read the change log, I know it has changed since then but... noticeable? I've got no problems at all with it, I'm too lazy to download updates unless they're very noticeable. :)