yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] zicoxx:
hey [MENTION=4684315]flar2[/MENTION],thanks for kernel..

Works great..

I want to ask you if possibile add dvb-t support for nexus 7 2013 as in this thread http://xdaforums.com/showthread.php?t=1841759

i think that it'll be cool use dongle usb dvb-t on flo as for "old" nexus 7..
[Nexus 7 (2013) Original Android Development] tni.andro:
Undervolting

The undervolting setting doesn't really make a difference in power consumption. Snapdragon has Adaptive Voltage Scaling. The undervolt setting will set the initial voltage after a frequency switch but immediately after that, AVS kicks in and automatically adjusts the voltage to the optimal value (the CPU has some circuitry that simulates the critical timing path, determines the necessary voltage for that and then sets the core voltage to that value).

So you may crash your CPU if the initial voltage due the undervolt setting is too low, but don't get a power benefit since the voltage will be adjusted automagically afterwards anyway. The adjustment is fast enough that my power measurements are basically identical for different undervolting settings.
[Nexus 7 (2013) Original Android Development] flar2:
Good info, thanks. I'll have to take a look at the avs code and see what it does.

What's your measurement setup?
[Nexus 7 (2013) Original Android Development] tni.andro:
I have a power monitor that's hooked up to the USB port measuring voltage and current. I've also used the battery gauge chip that's built in, the bq27541. That chip has an 'AverageCurrent' register that's updated every second (since it's measuring battery current, you need to run on battery). It's hooked up to '/sys/class/power_supply/battery/current_now'. (There is a public datasheet for the bq27541.)

I've done measurements for idle power, GPS logging and video decoding (HW and SW decoding).
[Nexus 7 (2013) Original Android Development] kingston73:
Hi, I need some serious help. I downloaded and tried to flash this kernel, I was unlocked and rooted. It seemed to flash fine but when I rebooted it just turned off and now won't turn on at all. Nothing. What do I do now?

I've tried using Wugs Toolkit to reboot into both recovery and just reboot, I've tried the volume up/down/power button method as well. Nothing at all.
[Nexus 7 (2013) Original Android Development] BigJPNut:
Try this if all else fails....

http://xdaforums.com/showthread.php?t=2381582
[Nexus 7 (2013) Original Android Development] kingston73:
I appreciate the help but it doesn't boot at all, it's just a black screen. It was at 65% before this happened, so I'm off to best buy to see if they'll take it back.
[Nexus 7 (2013) Original Android Development] BigJPNut:
It doesn't have to boot to use the link i gave you.

Have you tried to put it into fastboot?
[Nexus 7 (2013) Original Android Development] kingston73:
I couldn't get it to turn on at all, and the directions in that link said"turn tablet on". I have no idea What was wrong or what happened but a 30 minute car ride to best buy and plugging it into power for a minute and it turned back on.

I'm not new to flashing or android but I have no explanation what happened here. Can anybody give me a reasonable explanation?

Ps- loving the double tap wake.
[Nexus 7 (2013) Original Android Development] flar2:
Beta release, for guaranteed stability, use version 1.4 posted in the OP.

Lots of options, let me know if there are bugs.

I added USB host mode charging, new GPU frequencies, disabled AVS, and added a few small tweaks.

We'll see what happens with AVS disabled. This is the adaptive voltage scaling, which apparently overrides any undervolting by automatically setting voltages. Not sure yet if there are any ill effects from having it disabled, we'll find out.

GPU overclocking

I added more GPU frequencies, using [MENTION=4325945]ktoonsez[/MENTION] overclocking method, also thanks to [MENTION=3847629]Tk-Glitch[/MENTION] for making me aware of this.

There are two modes: stock and overclocking. If you pick stock GPU freq (400MHz) you won't be able to overclock. Conversely, if you pick one of the overclocking frequencies, you won't be able to use the stock 400MHz frequency. You have to reflash if you want to change this.

These are the frequencies I've added: 447, 487.5, 501, 528, 555, 582, 595.5

If you're in overclock mode, you change these on the fly with TricksterMod. I don't recommend 555+ for daily use. Too hot and probably unstable for most.

USB host mode charging:

As requested a couple weeks ago, I've added a hack to allow usb host mode charging. Since not that many people are going to be using this, it needs to be enabled manually. This will allow you to charge the tablet while a USB peripheral is hooked up to the OTG cable.

To use it, change /sys/module/msm_otg/parameters/usbhost_charge_mode to 1.

You need a Y-cable and OTG adapter. This will be handy for people who use their tablet in the car and need to keep it charged.

First connect the Y-cable to your OTG adapter and a power source, then plug the OTG adapter into the tablet. You can then attach a USB peripheral. Both the tablet and the peripheral will be powered by the Y-cable, allowing the tablet to charge

I'd appreciate some thorough testing and feedback on this.

Download:

ElementalX-N7-1.5 *BETA*

Changes:

-option to allow usb host mode charging

-add more GPU overclock frequencies

-latest googlesource update

-update freezer and cpuidle

-disable AVS

-update installer
[Nexus 7 (2013) Original Android Development] penguin449:
GPU frequencies not quite right yet, selected 5xx and in apps like trickster only showing 450 max!
[Nexus 7 (2013) Original Android Development] bcvictory:
Is there a way to adjust the hotplug like on Franco?
[Nexus 7 (2013) Original Android Development] xbs:
On 1.4 in landscape mode the sweep2sleep is active on the button area and also on the side.

Does this will happens in 1.5?

BTW on portrait mode you can only s2s over the buttons so there must a bug in landscape mode that doesn't deactivates the side sweep area.
[Nexus 7 (2013) Original Android Development] w0ng3r:
I'll give the OTG charging a go sometime this weekend!
[Nexus 7 (2013) Original Android Development] bcvictory:
What battery life are you guys getting? Not sure if I have a faulty battery or something else.
[Nexus 7 (2013) Original Android Development] penguin449:
About an hour I've had it and here's my stats
[Nexus 7 (2013) Original Android Development] bcvictory:
What about screen on time?
[Nexus 7 (2013) Original Android Development] penguin449:
40minutes of that was on screen with full brightness. Clocked at 1.5ghz

Sent from my N7 2k13
[Nexus 7 (2013) Original Android Development] bcvictory:
Wow. Okay. Something on mine is flawed.
[Nexus 7 (2013) Original Android Development] flar2:
The battery life should be improved on the beta.
[Nexus 7 (2013) Original Android Development] killflaker:
Gpu overclock locked to 450Mhz max whit Elx 1.5
[Nexus 7 (2013) Original Android Development] flar2:
For some reason trickster mod is not showing the available frequencies

You can change it manually.

There actually is no 450 frequency on this build
[Nexus 7 (2013) Original Android Development] L-ViZ:
wanted to install v1.5, had a few blackscreens after setting up aroma

those blackscreens seemed to be pretty random. after 4th install it worked.

---------- Post added at 09:49 PM ---------- Previous post was at 09:41 PM ----------

i set stock 400 but it is shown as 447. is that normal?

edit: kk, could be an error of trickster :)
[Nexus 7 (2013) Original Android Development] flar2:
The frequencies seem to be throwing trickster for a loop

I also forgot to update the exfat module, will fix that later. Only affects people who connect exfat volumes
[Nexus 7 (2013) Original Android Development] Ekinnoxx:
Running for test 1.5 beta CPU [MENTION=4149147]1.8[/MENTION] and GPU @487 on AOKP without problem all night long
[Nexus 7 (2013) Original Android Development] cobyman7035:
How's battery life at 1.8ghz in 1.5eX

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] El Ha$on:
Been running into a issue lately. And the last 2 times I've just reflashed ROM and kernel but now its the 3rd time so I guess it must be something different.

Last night everything was working perfect. I'm on CleanROM latest one and this kernel. I wake up this morning and of stuck on boot screen. I turn it off and back on stays stuck at boot screen. I wipe cache in recovery. Same. Go back into recovery to wipe dalvik AMD now it went further but got stuck at starting apps. Any help??
[Nexus 7 (2013) Original Android Development] flar2:
Make sure you have all stock frequencies.

Other than that, it's more likely a Rom issue. You likely need a factory reset.
[Nexus 7 (2013) Original Android Development] El Ha$on:
Its annoying to have to factory reset it a 4th time. I guess over clocking doesn't work across all. Bummer

Sent from my Droid DNA on 4.3!!!
[Nexus 7 (2013) Original Android Development] smalldroid:
I used this kernel on my nexus 7 2013. But sometimes my nexus 7's touchsreen doesn't work. I must connect my nexus 7 to my PC to reboot it. After rebooting, its touchscreen works again...
[Nexus 7 (2013) Original Android Development] Tysovwik:
smalldroid, it's problem of our device, not a kernel.
[Nexus 7 (2013) Original Android Development] cobyman7035:
Knock on wood… eX kernel has really helped… I don't get anymore random reboots! On. 1.2eX

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] bcvictory:
Are you going to add the colour/gamma control from Faux's kernel? Eco mode would be nice too. I can't think of anything else would want in a kernel!
[Nexus 7 (2013) Original Android Development] flar2:
The colour control from faux is his own private implementation. However, I will make sure my kernel is always compatible with this: https://plus.google.com/communities/103123288128442067861
[Nexus 7 (2013) Original Android Development] bcvictory:
Isn't that breaking GPL or some open source thing in some way? I could be wrong but yeah. I use that app with your Kernel at the moment but is it going to have colour temperature and gamma controls eventually?
[Nexus 7 (2013) Original Android Development] flar2:
If it's his own code he can do what he wants with it. It looks like supercurio's app will have many controls, but it's still a work in progress.
[Nexus 7 (2013) Original Android Development] jlevy73:
Is that the letter of the law or the spirit, just joking :D

I'm using supercurio's app and it has made big difference especially with whites.

---------- Post added at 05:41 AM ---------- Previous post was at 05:39 AM ----------

That's correct, not all devices were created equal. Overclocking and undervolting are the two main causes for instability. What is your cpu binned at?
[Nexus 7 (2013) Original Android Development] cobyman7035:
Is there new 4.3update ota? So if u use voodoo app I can get ipad ish blueish colors?

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] bcvictory:
I got approximately 6 hours of screen time running @1.4 and GPU underclocked at 320. I played games for around 30 minutes but isn't this battery life a little on the low side? I'm wondering what everyone else is getting on average.
[Nexus 7 (2013) Original Android Development] flar2:
I made some improvements to battery life in the 1.5 beta, but it's not my primary goal. As has been noted, s2w and dt2w will cause a bit more idle drain. there's always a tradeoff between features/convenience and battery.
[Nexus 7 (2013) Original Android Development] Tysovwik:
Have a question about this AVS driver. I am intersting, is it enabled at faux123 kernel with custom hotplug driver? Faux igrored any questions about adaptive voltage scaling in his kernel :( Any possitive feedback about AVS disabled in your rom? Can it improve the battery life at 384 freq?
[Nexus 7 (2013) Original Android Development] flar2:
I haven't got much feedback about the 1.5 beta yet, so I'm not sure if disabling avs makes a difference or not.

For my own device, idle drain is improved, but that could be due to some other patches I added.

For avs, I'm more concerned about the higher frequencies. There is a possibility that disabling it could lead to higher drain or instability. I haven't seen that on mine, but every device is different and problems don't usually become apparent until hundreds of people try it.
[Nexus 7 (2013) Original Android Development] Tysovwik:
I will download your beta version and check it. I am reading a lot, because of that i am interesting in 384 freq. By the way, what do you think, the AVS driver is enabled in all kernel by default? (the custom hot plug drivers don't matter in this case)? If i am right, you are the first one who disabled it.
[Nexus 7 (2013) Original Android Development] El Ha$on:
When I was having the issues I was over clocking at 1728 and I was undervolted at 850.

Sent from my Droid DNA on 4.3!!!
[Nexus 7 (2013) Original Android Development] flar2:
I don't know if the others have disabled it or not. It's just a config option, so very easy to do.
[Nexus 7 (2013) Original Android Development] tni.andro:
Chances are it's enabled. If you don't mind building your own kernel, there is a kernel config option 'CONFIG_MSM_AVS_HW' that you can disable.

It's very unlikely that there will be any substantial difference. E.g. the franco kernel that has a second CPU core running all the time only has about 45mW (13%) higher idle power consumption (at 0% brightness).

AVS is about choosing the lowest voltage where the CPU still works correctly. So, unless Qualcomm chose the safety margin a little high, you won't be able to get power savings.

Also, AVS is just for the CPU cores themselves, not GPU voltage, L2 cache and all those support chips...

(I haven't looked at ElemX 1.5 - not on GIT yet.)
[Nexus 7 (2013) Original Android Development] Tysovwik:
Can i disabled it manually with faux kernel? What should i do?

---------- Post added at 01:39 PM ---------- Previous post was at 01:36 PM ----------

Never did it before, can you make an instruction how to make it? :)
[Nexus 7 (2013) Original Android Development] flar2:
Qualcomm always errs on the side of caution, they need guranteed stability for a huge number of users.

Whoops, thanks for reminding me about udpating git, it's up now.

You actually have to build the kernel to disable it. It's not hard to build a kernel, but if you're not familiar with toolchains and linux it can be difficult to get started. There are many online guides.
[Nexus 7 (2013) Original Android Development] Tysovwik:
I already running your new 1.5 beta version kernel, but i want to try faux kernel with AVS function turn off. You thinking that is will hard to manually turning off avs in his kernel?

To be honest, i'd like faux kernel because of 2 main things: custom thermal and hotplug drivers. (great battery life in IDE and sleep mode). Dont like a qualcom drivers. It is a pity that you do not have this alternative drivers in your kernel.
[Nexus 7 (2013) Original Android Development] flar2:
I have a custom thermal solution. When it comes to hotplugging, IMHO mpdecision is the best.
[Nexus 7 (2013) Original Android Development] Tysovwik:
Is it ok to dirty install your kernel? (the previous one was faux), is it clean all the files that faux kernel created?

I am going with [ROM][CM10.2][4.3][CyanogenMod Kangs]. Any known bugs with CM roms?
[Nexus 7 (2013) Original Android Development] tni.andro:
Turning the option off is the trivial part. Setting up a working development environment is the tricky part. I would say, if you don't have Linux development experience (and a Linux machine) - don't bother. If everything goes right, it's not difficult. But I had several problems getting a working toolchain, from compiler crashes with the Google toolchain to compile errors with my current GCC 4.8 toolchain.
[Nexus 7 (2013) Original Android Development] Tysovwik:
Sad story, i dont have any Linux development experience, but never mind thanks for answer :)
[Nexus 7 (2013) Original Android Development] tni.andro:
When switching between the kernels, you should (dirty) install the ROM before the kernel (with TWRP, you can select multiple files at once, ROM first, then kernel).
[Nexus 7 (2013) Original Android Development] Tysovwik:
yes i know, but i see the change log of this kernel:

August 10, 2013 - ElementalX-flo-0.8

-cleanup from other kernels

and because of that i asked about it. So in any case it is necessary to dirty install the rom, right?

---------- Post added at 02:36 PM ---------- Previous post was at 02:21 PM ----------

one more thing about fsync. It is disabled by default, but in instruction of first post said: """I recommend leaving it enabled unless you are sure"""" What the better way, enabled or disabled this function?
[Nexus 7 (2013) Original Android Development] tni.andro:
Unless you know what garbage a kernel leaves behind, it's better. A lot of kernels put at least some config files into init.d and some replace system binaries that are part of the ROM.

You are risking serious data corruption if there is a crash with disabled fsync (e.g., when you are playing with undervolting ;)). A lot of apps rely on fsync to maintain a certain write order. Disabling fsync breaks that and you may deal not only with a little lost data, but all data in files that had outstanding writes at the time of the crash may be completely corrupted/useless. And then you end up with something like Mediaserver draining your battery because it's constantly crashing (and getting restarted) due to a corrupted database.
[Nexus 7 (2013) Original Android Development] flar2:
I try to cleanup from other kernels, but just to be sure you should dirty flash your ROM first. There are a lot of kernels out now, so I can't keep up with all of them.
[Nexus 7 (2013) Original Android Development] tni.andro:
I've looked at ElemX 1.5 idle power, compiled with AVS and without AVS.

I hate to say it, but for me, AVS/no AVS/1.4/1.5/stock voltage/725mV/850mV doesn't make a difference.
[Nexus 7 (2013) Original Android Development] flar2:
Perhaps undervolting is overrated

Have you tested undervolting on other devices?
[Nexus 7 (2013) Original Android Development] 7786:
I personally think swiping to wake in any direction and anywhere on the screen would be fantastic on this tablet. The 7" blackberry playbook had a similar function and it worked great. My 2 cents, great work nonetheless!
[Nexus 7 (2013) Original Android Development] flar2:
That would be easy to do, I might make it an option. The reason I haven't as of now is because I don't want the screen turning off while swiping between homescreens, or while playing a game.

I'm also thinking of making it work along all the edges, so it doesn't matter which way you hold it.

In the meantime, I'll have a new release tonight. I've been working a bit with doubletap2wake, and a couple of fixes for thermal throttling and frequencies stuck at 1512.
[Nexus 7 (2013) Original Android Development] flar2:
Download:

ElementalX-flo-0.4 *BETA*

Changes:

-adjust doubletap2wake

-increase thermal limits

-fix frequencies stuck at 1512
[Nexus 7 (2013) Original Android Development] wy2sl0:
Gonna give this a shot tommorow. By Ottawa do you mean Canada's capital? I am from the same area, go Canada!!!
[Nexus 7 (2013) Original Android Development] TechSilver13:
Thanks for the update. This thing feels so much faster than my s4 GE but I know for a fact that it isn't. Your kernel is SICK. thanks for all you are doing and keep it up.
[Nexus 7 (2013) Original Android Development] yojoe600:
Great kernel keep it up
[Nexus 7 (2013) Original Android Development] sciphonic:
So far this is the fastest and smoothest feeling kernel I've tried. For a beta I'm very impressed. Keep up the good work.

I'm using the 32 GB model, stock ROM, 2.1 GHz CPU, 487 MHz GPU. Here are some benches:
[Nexus 7 (2013) Original Android Development] oneandroidnut:
I got 7xxx + in quadrant don't know how you got only 6400???
[Nexus 7 (2013) Original Android Development] willverduzco:
Fantastic kernel.

In my experience with it, it seems as the limiting factor in these overclocks is the thermal, which makes it throttle after a minute or so at anything over 1.8 (on my device) at full load, according to the Stability Tester app. No crashes at any speed--just throttling. But as your OP says, there's little gain to be had by going higher on CPU anyway. GPU is what makes a bigger difference in my usage.

[MENTION=4684315]flar2[/MENTION] I was wondering if you'd please consider adding another GPU OC step for those of us who can run 600 successfully on other kernels.

Many thanks for the great work!
[Nexus 7 (2013) Original Android Development] nhidog:
There is no gain going past 487... I know I benched 450 487 533 600... all very similar number... just increased heat.
[Nexus 7 (2013) Original Android Development] teh roxxorz:
Double tap to wake is much mor responsive on .4 beta.

sent from the 7th nexus of 2013
[Nexus 7 (2013) Original Android Development] flar2:
I haven't tried 600 yet, but I tested 400 450 480 487 and 533. I didn't have good benchmarks with 533. In GL Bench 2.7 Egypt offscreen, I manged an extra 4 or 5 fps with 487 compared to stock.

I'll test 600 and probably add 533 in one of the betas anyway, just so people can try it out for themselves.

It still doesn't work reliably from deep sleep.
[Nexus 7 (2013) Original Android Development] willverduzco:
Many, many thanks!

Battery life seems to be great in this kernel with the undervolt options as well.
[Nexus 7 (2013) Original Android Development] codya321:
Doubletap2wake works perfectly on 0.4. Love this kernel on my HTC one, awesome to see it here as well, thanks!
[Nexus 7 (2013) Original Android Development] teh roxxorz:
I can get it to come out of deep sleep, though the area to wake is still finicky. I said it was improved, not perfect. I know the feature still needs tweaking.

sent from the 7th nexus of 2013
[Nexus 7 (2013) Original Android Development] flar2:
In deep sleep, I usually have to do a pre-touch to wake it a bit before it works.

You have to be pretty exact on 0.4, both taps have to be within about 75 pixels, I think it was 150 on version 0.3.

It should be simple, but this touch driver doesn't seem to know when you lift your finger. I've worked with several touch drivers on different devices and this is the most basic touch driver I've seen. Simple is usually good, but I may have to do some extra work to get this functionality working perfectly. At least s2w is good, I'm going to get to work on some new options later this week.
[Nexus 7 (2013) Original Android Development] JohnnyHempseed:
I'm hitting over 8000 in quadrant.
[Nexus 7 (2013) Original Android Development] jassycliq:
I've already tested those speeds and none of them are as good as 487mhz. They just create excess heat causing thermal to kick in much too quickly. People were saying that the UI felt smoother with 600mhz but gaming was a horrible experience.
[Nexus 7 (2013) Original Android Development] ctexpa:
Loving the kernel but I'm experiencing WiFi drops on 802.01 network. Works well on the open network though.
[Nexus 7 (2013) Original Android Development] sciphonic:
Could be a few things. I haven't even begun to optimize my tablet. Are you using the stock ROM?
[Nexus 7 (2013) Original Android Development] tni.andro:
Android? - No. My Laptop - yes, makes a big difference.

I wonder if AVS is always active on the current S4 Pro and the kernel stuff is just there from older CPUs. Of course, there isn't any public technical information on the Qualcomm stuff...
[Nexus 7 (2013) Original Android Development] cobyman7035:
I think UVing only lessens the heat buildup.. doestn save battery life… but its nice not to feel the device so hot wen gaming or playing a video long time

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] flar2:
sounds like there's a good possibility it is built into the hardware
[Nexus 7 (2013) Original Android Development] cobyman7035:
Damn just had a reboot! 1st time in couple weeks

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²