yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Frostyeo:
Hi! Coming from 1.0 to 1.6, I flashed it, and wiped dalvik and cache, but when I reboot it, it seems to stay quite a long time at the Google logo :/ is this normal?
[Nexus 7 (2013) Original Android Development] dirwdirw:
I have a magnetic case. could you make another version of the kernel, that without the s2s/s2w/dt2w that sombody doesn't need?
[Nexus 7 (2013) Original Android Development] nikr123:
Just turn it off lol
[Nexus 7 (2013) Original Android Development] dirwdirw:
turn it off in the trickstermod can stop it eating battery?
[Nexus 7 (2013) Original Android Development] elcom:
I think the meaning was to turn it off in the aroma installer.
[Nexus 7 (2013) Original Android Development] nikr123:
Or in /etc/elementalx.conf
[Nexus 7 (2013) Original Android Development] tni.andro:
Yes. Keep in mind, whatever 'thing' trying to control the setting last 'wins'.

The ElementalX config from the Aroma installer/elementalx.conf is applied first, Trickster will apply settings after everything is started up (so Trickster settings will overwrite the stuff from Aroma).
[Nexus 7 (2013) Original Android Development] nikr123:
I think if you change a setting in Trickster it gets reset to the ElementalX config after reboot. Only if set on boot is on.
[Nexus 7 (2013) Original Android Development] tni.andro:
Yes, that's right.
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
When you disable Sweep2Wake during the flashing of 1.7 you also lose the Sweep2Sleep and DoubleTap2Wake options.

So I manually edited the .conf file like:

Sweep2Wake = 2

Shortsweep = 1

DT2Wake = 1

PWR_Key = 1

And now all is well. Pressing hardware Power button to sleep the device disables DT2W and S2W, while the device is on and you let it sleep by using S2S also DT2W is active. Blissssss :cool:

Ahem... Didn't see the added submenu when you DO enable Sweep2Wake... After that you can still enable/disable the things mentioned above. Great work, my bad! :highfive:

By the way, when using ElementalX 1.6 (without the power saving feature that is) while using an active DT2W the idle battery drain is minimal as well, as can be seen here:

Losing 3% in almost 10 hours with "everything" (syncs, widgets, mail etc.) on I find rather okay :good:
[Nexus 7 (2013) Original Android Development] zicoxx:
very thanks [MENTION=4684315]flar2[/MENTION] for adding dvb support..

i download it and testing dvb support..

i have modules from kernel 3.1 but i think that don't work,right?

however i can test it because i have usb dongle dvb (rtl2832u and dib0700) so if work other users can buy dongle that works good (personally i choose rtl2832u that works good also for SDR-FM radio)..:)
[Nexus 7 (2013) Original Android Development] ziantic:
Some issues came up.

my first try with ver 1.6 : 1.7 ghz CPU, no undervolt, 450 mhz GPU, Elementax X L2 overclock, s2w enable ... I reboot 2 or 3 times

2nd try 1.5 ghz stock, GPU 400 Mhz stock, no undervolting, no L2 overclock, no addtional options, I tried to make the specs similar to stock specs. reboot 3 times.

All dalvik cache wiped.

and this happen, I had to reflash the ROM again ( AOKP build 10/12/13 latest )

As you can see I got the blue BSOD right after the Google Lock came up, with tiny green line. I was like " wut ??? BSOD ? ":laugh::laugh::laugh:
[Nexus 7 (2013) Original Android Development] hopscotchjunkie:
This kernel won't be compatible with AOKP until they remove the CAF stuff and go back to AOSP source (assuming that's the intention from the poll on their site).
[Nexus 7 (2013) Original Android Development] Tasssadar:
[MENTION=4684315]flar2[/MENTION]: Hello, I'm very grateful that you merged the kexec-hardboot patch, but unfortunatelly there's a problem with the version you used. Can you please merge this fix? http://xdaforums.com/showthread.php?p=45920207#post45920207
[Nexus 7 (2013) Original Android Development] cobyman7035:
Is it bricked or u got it reflashed

I'm on 1.6 now but had a weird freeze. lockup… press power button 5 sec to reboot, but luvkilyluckily it just unfroze back to normal now

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] FireBlast:
According to battery enhancer thread the patch adds a new sysfs control: '/sys/devices/i2c-0/0-006a/float_voltage'. I'd flashed v1.6 of ElementalX kernel and didn't find any file with the same name in that location. Did you implement this patch or not? Can I simply add such file by myself?
[Nexus 7 (2013) Original Android Development] tni.andro:
You need version 1.7 Beta, it's not in 1.6:

http://xdaforums.com/showpost.php?p=46389703&postcount=1145

The control file will automatically appear.
[Nexus 7 (2013) Original Android Development] FireBlast:
Flar2 can you add some options for this patch in Aroma e.g. 4100,4200,4300?
[Nexus 7 (2013) Original Android Development] thedan55:
Can someone please help.

I'm on stock with elemental kernel but I still can not write to an ntfs USB stick. What am I doing wrong

Edit. So I can write to the ntfs USB stick but I can only copy files, I can't create folders or copy folders like my titanium backup folder

Do I need to have a custom rom or is a custom kernel enough
[Nexus 7 (2013) Original Android Development] goofball2k:
Maybe try flashing the kernel using TWRP, reboot, then go back into TWRP and select Fix Permissions?
[Nexus 7 (2013) Original Android Development] thedan55:
Did that but still can't create folders or copy folders to the USB
[Nexus 7 (2013) Original Android Development] ziantic:
I reflash it then it's okay now

---------- Post added at 07:01 AM ---------- Previous post was at 06:59 AM ----------

Weird, they told me AOKP is from AOSP source, with a little help from Cyanogen with the kernel.
[Nexus 7 (2013) Original Android Development] guyd:
CyanogenMod uses caf (and so does AOKP apparently). That's why an aosp kernel will blue screen on the latest AOKP builds.
[Nexus 7 (2013) Original Android Development] ziantic:
That explains :good:
[Nexus 7 (2013) Original Android Development] mjc2251:
power saving

Could you extend the new power option feature of shutting down swipe to wake to the closure of the magnetic cover as well? If my cover is closed I don't need to use double tap to wake or swipe to wake. It is also more convenient than having to hit the power button every time.

Thanks for all you've done so far!
[Nexus 7 (2013) Original Android Development] pietropizzi:
I agree if it stays an OPTION as my screen doesn't wake up when opening the magnetic cover again in a situation where whether wifi is connected to an AP or bluetooth is enabled. ( a known bug )
[Nexus 7 (2013) Original Android Development] bobloadmire:
Does anyone know if we will get a CAF version of this kernel? I love CM and this kernel.
[Nexus 7 (2013) Original Android Development] FernandoMiguel:
is it possible to have double tap while power key disables s2wake?

also, swipe2wake seems to be enable ANYWHERE, not just at the bottom/top bar and it doesnt respect the orientaion (so if you are upside down, it's still right to left, not left to right)
[Nexus 7 (2013) Original Android Development] xbs:
Having dt2w enabled while s2w is disabled doesn't make any sense as the purpose of the power button toggle is to save power, if one of them is enabled there's power drain.
[Nexus 7 (2013) Original Android Development] situman:
Loving the features and speed! What governor and io scheduler would you recommend? Stock is Ondemand and CFQ I believe.
[Nexus 7 (2013) Original Android Development] jassycliq:
[MENTION=4684315]flar2[/MENTION] can you push source? :)
[Nexus 7 (2013) Original Android Development] mbwsutherland:
Alright flar . I am very impressed by your work. Never had a kernel install with aroma. It is very sweet to have the ability to pick through all the settings you would have to through with a third party app. Just wanted to say thanks and I'm sure I speak for Eveyone when I say we appreciate it. .4 is running absolutely great very snappy and smooth.
[Nexus 7 (2013) Original Android Development] Waynato:
Using ParanoidAndroid ROM clocks stick at 1.7 for 3 out of the 4 cpu's when gov is set to performance
[Nexus 7 (2013) Original Android Development] oneandroidnut:
i was at that time yes. on carbon now with this .4 beta kernel runs great!
[Nexus 7 (2013) Original Android Development] sciphonic:
Sorry to bug you again but were you using a kernel management app? If so what settings are you using. If not, what settings did you use in the Aroma installer?

My runs were done at 2.1 GHz, no undervolt, and 487 on the GPU. The tablet started getting pretty hot so I stepped down to 1.9 GHz with an undervolt today. My Quadrant score dropped slightly but the heat went away and Sunspider got even better.
[Nexus 7 (2013) Original Android Development] oneandroidnut:
i had it on kernel tuner and on 2.1 ghz, undervolt to 850 min, stock gpu. mine barely got warm at top of device

what kernel app were you using?
[Nexus 7 (2013) Original Android Development] sageDieu:
for the s2w anywhere idea, what about making it swipe2wake anywhere but to sleep it has to be in one spot? i mostly use the feature for wake, and it would help in the dark to not have to figure out where the bottom of the screen is.
[Nexus 7 (2013) Original Android Development] sciphonic:
Those screenshots were made with no kernel control app at all. I then tried Set CPU and FauxClock. I used Fauxclock without tuning and with his Nexus 4 settings (also tried his new N7 kernel but it's much slower and has some lag in its current state). Even with the apps set to performance mode and the "force GPU" setting turned on in the Developer settings I can't hit 7000 on my N7. Go figure. I'm not using any out of the ordinary apps and have the most recent SU and Busy Box. I'll eventually wipe everything and try some ROMs to see if I can put down better numbers. My tablet is running great with this kernel at the moment, just can't get above about 6700 on Quadrant.
[Nexus 7 (2013) Original Android Development] oneandroidnut:
Yeah mine on carbon right now is running so smooth and I love s2w android needs to make that a stock feature I think.

And I'm not a fan of setcpu at all try kernel tuner and see what happens using it
[Nexus 7 (2013) Original Android Development] TechSilver13:
I can't get over 6400 so don't feel bad. The device feels like 20000 points so I'm happy.
[Nexus 7 (2013) Original Android Development] sciphonic:
Gave Kernel Tuner a try and got similar results. It's my ROM or just my hardware. Thanks for the responses though. This is still the fastest and smoothest Android device I've ever used so I'm happy.
[Nexus 7 (2013) Original Android Development] jlevy73:
Quadrant sucks anyway, I don't think that app has been updated since the dinosaurs roamed the planet.
[Nexus 7 (2013) Original Android Development] oneandroidnut:
No problem and yes it is one of the smoothest and fastest I've used. The s4 on aosp runs pretty darn fast too. Going to take s4 back to stock and try some roms out one of these nights that I get some energy and time lol
[Nexus 7 (2013) Original Android Development] d1ez3:
sweep2wake is awesome, it encourages me to use my tablet since I don't need to look for the tiny hard to reach power button. Curious to see how much power is used while idling with this feature.
[Nexus 7 (2013) Original Android Development] flar2:
This one needs some extensive testing because I switched to the linaro 4.8 toolchain and built with the -O3 optimization level. It should be alright, but I worry a little when I switch to a custom toolchain.

Sweep2wake now works anywhere on the screen to turn the device on. It's still left to right only for turning the screen on. I adjusted doubletap2wake again, let me know if there is a difference.

I also added gpu overclock to 533MHz. Careful, 533 could be unstable and may have lower performance than stock.

Download:

ElementalX-flo-0.5

Changes:

-build with linaro 4.8 toolchain

-O3 optimization

-add GPU overclock to 533MHz

-fix for app-mounted directories (thanks [MENTION=1951402]mkasick[/MENTION])

-s2w works anywhere on screen when screen is off (still left to right only)

-adjust doubletap2wake
[Nexus 7 (2013) Original Android Development] sageDieu:
mfw people are wasting space in this thread talking about benchmarks, especially quadrant

http://i.imgur.com/zKWbnTh.jpg
[Nexus 7 (2013) Original Android Development] willverduzco:
Thanks so much for adding the 533 step for trial. As expected, you were completely correct about the performance issues when using it. 480 is about 40% faster than 533, likely from throttling of some sort.
[Nexus 7 (2013) Original Android Development] prstorero:
Running well so far. Only thing I've noticed is trickster live frequency will show 1728 MHz even though max is 1.5. Other than that it seems to be running well :)

Edit: ran antutu for people to reference. I never go purely by benchmarks, but I know some prefer them more than others :)

http://cl.ly/image/1u2B2h2B0I1E

The app gives me issues with uploading in full size, so I gotta use a link.
[Nexus 7 (2013) Original Android Development] jlevy73:
Indeed, when going to 533, Egypt dropped to 31fps from 45 (when compared to 487)

S2W and DT2W are much much improved. Love the new implementation of S2W, works great.
[Nexus 7 (2013) Original Android Development] guyd:
I think the answer to that is no.
[Nexus 7 (2013) Original Android Development] kingston73:
In using the 1.7 beta and trickster mod. In coming from faux kernel. I remember reading this somewhere but can't find it, with this kernel should mpdecision be on or off?
[Nexus 7 (2013) Original Android Development] akarol:
On. Flar prefers the way it handles the cores.
[Nexus 7 (2013) Original Android Development] FernandoMiguel:
But swipe is too sensitive so I like to disable it with power key but keep double tap for quick enabled
[Nexus 7 (2013) Original Android Development] flar2:
You can disable s2w and enable dt2w, or have sweep2sleep and dt2w
[Nexus 7 (2013) Original Android Development] FernandoMiguel:
But that disables it permanently, and not on power key, correct?
[Nexus 7 (2013) Original Android Development] mjc2251:
I had the touch screen go non responsive twice yesterday on 1.7 beta, back to 1.6 for now. Is this related to the new power saving tweaks. Both time I had put my device to sleep with the power button only to find it in responsive when I woke it.
[Nexus 7 (2013) Original Android Development] tiny4579:
How long was it unresponsive. I've had it unresponsive before on the stock kernel. Sounds hardware related to me. You may want to try experiencing with different touch firmware. In fact I should try it but I don't remember the link right now.
[Nexus 7 (2013) Original Android Development] flar2:
Minor update. Fixed up installer, fixed up kexec-harboot (multirom support) and built in some stuff needed for 3G USB modem. I added an installer option to set lower charge voltage (4.2V). Theoretically this will make your battery have a much longer lifespan (not longer battery life in the sense we normally discuss here, this is about the battery not wearing out as fast after hundreds of charge cycles--this is for people who plan to keep using this tablet for years). There is also a module pack that will install drivers for many USB DVB dongles. This is only for people that want to turn their Nexus 7 into a TV. I don't have one of these, but it should work. You'll be mostly on your own getting the modules loaded and getting it setup, but do feel free to post in the thread for help.

Download:

ElementalX-N7-1.8 *BETA*

Changes:

-fix-up for kexec-hardboot (multirom)

-aroma option for battery life extender

-update installer

-3G USB modem drivers (built-in)

Download:

DVB modules add-on

Install this if you want to use a USB DVB dongle.
[Nexus 7 (2013) Original Android Development] oTeMpLo:
Which 3g modem is best or which are supported?!
[Nexus 7 (2013) Original Android Development] crazyyyk:
I Installed 1.8 and in aroma I selected option for battery life extender. But after boot in file /sys/devices/i2c-0/0-006a/float_voltage I saw 4300 instead 4200... Is it normal?
[Nexus 7 (2013) Original Android Development] nikr123:
I just installed and I can say that I didn't have that problem.
[Nexus 7 (2013) Original Android Development] oTeMpLo:
there is correct value of 4200
[Nexus 7 (2013) Original Android Development] crazyyyk:
I manually change the value to 4200, but after reboot it is still 4300...
[Nexus 7 (2013) Original Android Development] cobyman7035:
Please help! Can I install official ota update with ex1*6 kernel? Font want brick

Via my NeXus⁴ using Tapatalk² app
[Nexus 7 (2013) Original Android Development] crazyyyk:
After reinstall the kernel everything woks fine!
[Nexus 7 (2013) Original Android Development] CubicNexus:
First I want to thank you for you're great work, the kernel gives me really smooth performance and a great battery life, when the screen is on.

But the standby drain is higher than stock... I lose about 4%-6% per night (about 8 hours).

Am I doing something wrong with my settings?

Governor: intellidemand

Frequencies: stock / 384 MHz undervolted to 725000

MP-desicion off

Sw2s and Dt2w on

The rest is stock.
[Nexus 7 (2013) Original Android Development] roofrider:
Flar has advised to leave mp decision on.

The idle battery drain is due to dt2w and s2w features, it's a trade-off.
[Nexus 7 (2013) Original Android Development] flar2:
That's from s2w/dt2w, the touchscreen doesn't completely go to sleep. There is a new feature in version 1.8 that allows you to put the touchscreen completely to sleep by using the power button. This allows you to keep using s2w/dt2w, but temporarily disable it when you're not using the tablet for a long period.

With this feature, you'll only lose 1% or 2% overnight.
[Nexus 7 (2013) Original Android Development] goofball2k:
With the option for charging with USB OTG, that means that any USB storage device has to be powered using the OTG+charging cable and not just regular OTG cable? I can't just use a regular OTG cable with a USB flash drive? I still don't have my OTG+charging cable yet, so I'm curious about this option.

Love this kernel.
[Nexus 7 (2013) Original Android Development] zicoxx:
[MENTION=4684315]flar2[/MENTION]

Soon i will test dvb support and 3g dongle support..thanks for support dvb dongle and 3g..i hope that in future also other stuff is possible adding to your kernel..

Unfortunately my nexus 7, 2013 died, now it's in RMA .. i'm waiting that return on my hand..

Yesterday it went off and i didn't start it again .. It was in QHSUSB mode and it was impossible to restore it .. (And any key combination has worked)..
[Nexus 7 (2013) Original Android Development] flar2:
Yes, with host mode charging, the usb device is powered externally and the tablet also charges at the same time.

Leave it in regular mode if you just have an otg adapter. The tablet will power the connected usb device.

Someone confirmed via pm that the 3g dongle works.

Hopefully you get your replacement quickly
[Nexus 7 (2013) Original Android Development] crazyg0od33:
I have tried to install 1.6 on my LTE N7. On my tablet, it is saying that I'm running elementalX 1.4+ with a date of 9/9/13, so I don't think it installed properly (never went through the DT2W setup, etc.) Don't know what the problem is, maybe a bad download on my side?
[Nexus 7 (2013) Original Android Development] kingston73:
In using the 1.7 beta and trickster mod and tried turning mpdecision on but after reboot trickster says it's turned off. Any ideas?
[Nexus 7 (2013) Original Android Development] goofball2k:
Did you choose the option to "set at boot" in trickster mod?

MP-Decision is by default on, did you change that during installation?
[Nexus 7 (2013) Original Android Development] FernandoMiguel:
are there any good metrics of how much dt2w/s2w add up on the battery usage?
[Nexus 7 (2013) Original Android Development] kingston73:
I don't think I changed it during installation, pretty sure that wasn't one of the options? And I do have "set at boot" checked in Trickster.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
More than double the idle drain, for me.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] dud3me:
Did you have a custom kernel (Franco etc.) installed before flashing elementalX?
[Nexus 7 (2013) Original Android Development] FernandoMiguel:
that's quite a bit.... could be the reason why I have much less battery than on stock
[Nexus 7 (2013) Original Android Development] kingston73:
I had Franco installed before this, I didn't think about that but did it make some type of change to keep mpdecision off? Is it a buildprop value I can change manually?
[Nexus 7 (2013) Original Android Development] dud3me:
Reflash your rom without wipe and boot, then flash elementalX. Had the same issue, Franco has its own alternative for mpdecision so that's why it isn't turning on.

Don't know if it's possible to fix it with build prop changes.
[Nexus 7 (2013) Original Android Development] tni.andro:
That doesn't make sense. The difference with dt2w/s2w is that it prevents the touch screen controller from being powered off in deep sleep mode (screen off). Sitting around idle (e.g. on the home screen) there is no difference in power consumption.

The power consumption difference in deep sleep is about 55mW. Deep sleep with everything (Bluetooth/GPS/Wifi,...) turned off consumes about 7mW (90 days until battery is empty). With dt2w/s2w on you will have 62mW power consumption (10 days until battery is empty).
[Nexus 7 (2013) Original Android Development] flar2:
I lose about 4% overnight with s2w enabled but only around 1 or 2% when disabled.

That's why I added the power button toggle.

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

If you come from Franco, you must dirty flash to get a proper ramdisk. He disables mpdecision

I'll fix this in the next update.
[Nexus 7 (2013) Original Android Development] nklenchik:
Wi-Fi on too? That's not bad at all
[Nexus 7 (2013) Original Android Development] Spyr0s:
WOW!

So we can connect a 3G USB modem and have 3G connection instead of having to tether with a smartphone? Isn't there an UI required, except from the drivers, to configure the access point for the modem to work? How do we achieve this? Im thinking of buying a cheap modem like Huawei E3131 to test this.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
+1

Same question here. Anyone?

Sent from my Nexus 7²
[Nexus 7 (2013) Original Android Development] flar2:
I think wifi is set to turn off when screen is off, but I can't remember for sure and I don't have it with me to check.

Yes. But I don't know the details of using it or which models are supported. The two people who asked me to implement it were using Huawei dongles and one of them responded, confirming that it works.
[Nexus 7 (2013) Original Android Development] CubicNexus:
Thank you for your answer! Now I have installed the 1.8 beta and it gives me amazing battery life :)

Thank you for your awsome work on this kernel!
[Nexus 7 (2013) Original Android Development] anko184:
Can someone please explain why we need stickmount to mount ntfs sticks when their is ntfs rw support on kernel? Is their any chance to have ntfs mount without any extra app?

Thanks..
[Nexus 7 (2013) Original Android Development] goofball2k:
I've used Carbon ROM and CM 10.2 without using any additional app to mount USB sticks. With and without this specific kernel.

I have a Rogers LTE USB modem I will try at work. I know it needs software to run, not sure if it will run on Android without the software.
[Nexus 7 (2013) Original Android Development] tiny4579:
Stickmount is needed on ROMs that don't have usb stick support such as stock. It doesnt matter the filesystem. The kernel support is only for the filesystem and not the usb otg storage support.
[Nexus 7 (2013) Original Android Development] GialanG:
Another idea: can you make an app to turn off screen and disable dt2w, s2w, instead of using the power button? That will be much more convenient. Thanks [MENTION=4684315]flar2[/MENTION]