yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Philaphlous:
So I flashed to 2.7 last night and my tablet was powered off over night... I had to get into recovery to power it back on... I thought maybe the alarm clock app drained the battery but the battery was fine...so random reboot and it didnt reboot... Also, touchscreen issue was 10x worse on 2.7. I'll try it again at a lower clock but I couldn't even type or use it at all...
[Nexus 7 (2013) Original Android Development] thecdn:
flar, I know this isn't very important but I was wondering if you might have an idea about what's causing it. I run slimkat and use the dashclock widget with the storage extension enabled.

On the stock kernel, and with bricked, the % of free space shown is correct. With your kernel, and with glitched, the display is always at 0%. This situation is consistent across several roms that I've tried in my multirom setup.

As I said, not particularly important, and your kernel is great otherwise but I thought I might mention it.
[Nexus 7 (2013) Original Android Development] SickBeast:
Can we use the same steps to enable f2fs as what you would do on the Nexus 7 gen. 1? If someone has a guide I would really appreciate it.
[Nexus 7 (2013) Original Android Development] flar2:
The changes in 2.7 were all features, they shouldn't affect stability, touch screen or battery drain while idle (battery drain during use might be slightly different because of the governor change).

Do I have to install slimkat or can I get install that widget on a different ROM?

I'm not really sure what's involved, but I'm guessing you need a recovery with f2fs support to get started. Not sure if this exists for the N7.
[Nexus 7 (2013) Original Android Development] AarSyl:
Dash clock is available on the play store. Hopefully, that's the app that you were talking about.

https://play.google.com/store/apps/details?id=net.nurik.roman.dashclock
[Nexus 7 (2013) Original Android Development] thecdn:
Yes, that's the one I'm talking about. And the storage extension is downloaded separately from the play store.
[Nexus 7 (2013) Original Android Development] GSLEON3:
Compiling the recovery is easy enough. The kernel needs to be patched to support F2FS. However, I would hold off. There have been some comparative benchmarks that actually show EXT4 as being faster than F2FS with write actions. I have not compared the structures to determine if F2FS is beneficial in other areas, but especially larger write & copy operations seem to be looking favorable for EXT4.
[Nexus 7 (2013) Original Android Development] siravarice:
How do we flash the new version? Simply stick the .zip on the device and flash the new kernel? Wipe dalvik before doing so etc?

Just don't want to lose all my data as it has happened before on older devices!
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Make a nandroid backup and then flash away. Don't need to wipe anything.
[Nexus 7 (2013) Original Android Development] SickBeast:
So are you saying that f2fs is possible with the latest twrp? How do you do the format and the backup? This kernel is already patched for f2fs. BTW f2fs is definitely much faster than ext4.
[Nexus 7 (2013) Original Android Development] kylealanr:
EXT4 vs F2FS

Here's some information for those interested in performance, this is the best I could find.

The AnandTech review of the Moto X detailing the usage if F2FS

http://www.anandtech.com/show/7235/moto-x-review/9

phoronix.com performing I/O tests on the same hardware with different file systems

http://www.phoronix.com/scan.php?page=article&item=linux_f2fs_benchmarks&num=1
[Nexus 7 (2013) Original Android Development] Orihalcon:
Thanks for latest version!

On 2.6.5 has anyone experienced it that the dt2w stops after tab has been off for extended period of time? Using it with CleanRom at present and running into this. Will update now and check if still an issue.

Anyone else had that?
[Nexus 7 (2013) Original Android Development] GSLEON3:
NO. I am saying that compiling a recovery to include the F2FS formatting option is a fairly straight forward task, not a whole lot to it. Personally, I do not see any need for F2FS atm. Until other aspects of it are improved, you aren't likely to see to much of a performance gain. Maybe if your device memory is nearly full, it might hold some benefit for you, but there are other aspects that need to be refined to equal or better EXT4, or a number of other formatting options.
[Nexus 7 (2013) Original Android Development] meekrawb:
Does anyone else's magnetic cover not work with 2.7?
[Nexus 7 (2013) Original Android Development] paaaulo:
@up quite often it doesn't work for me.
[Nexus 7 (2013) Original Android Development] flar2:
That's not a kernel issue, most likely an issue with your cover. The only change I made to that code is to turn it off or on. It's a very simple driver, no parameters or anything. My cover works every time.

I seem to recall an issue where it doesn't work if you disable WiFi during suspend.
[Nexus 7 (2013) Original Android Development] meekrawb:
I guess I will be sticking with 2.6 then, because it has zero problems with my Moko cover.
[Nexus 7 (2013) Original Android Development] poondog:
There are already a few kernels for grouper that support f2fs

There's a sysfs interface for cover on this kernel, did you try that?
[Nexus 7 (2013) Original Android Development] flar2:
It's your choice, but I'm telling you there is no change between 2.6 and 2.7.
[Nexus 7 (2013) Original Android Development] meekrawb:
It's cool, maybe it is just my device. Same settings for both versions, different result. Still the best kernel for my usage!
[Nexus 7 (2013) Original Android Development] Scottchy014:
If anyone is interested, I have a simple video going over the installation of ElementalX. Here it is: http://goo.gl/VAFV1N Enjoy!
[Nexus 7 (2013) Original Android Development] NovaSlim:
Most likely it is your device(although try to reflash the kernel with cache/dalvik wiped to make sure), I have a moko case too and after 2.7 the wake/sleep feature works the same.
[Nexus 7 (2013) Original Android Development] meekrawb:
I have never done a cache/dalvik wipe when flashing a kernel. Just tried it though, no change. I'm stumped.

Particulars:

Slimkat 3.6 weekly

Aroma screen 1- no

Screen 2- 1512

Screen 3- stock

4- stock

5- default

6- 400Mhz stock

7- on demand stock

8- CFQ stock

9- all unchecked

10- all unchecked except battery life extender and disable gboost

These are mostly the same settings I have always chosen since I started using this kernel in September. Again, not a big deal. Just reporting my experience.
[Nexus 7 (2013) Original Android Development] Swimboy46163:
Anyone else having trouble with double tap to wake not working. I had it checked when I installed it.
[Nexus 7 (2013) Original Android Development] flar2:
Not working at all, or not working sometimes?
[Nexus 7 (2013) Original Android Development] Swimboy46163:
Its not working at all.
[Nexus 7 (2013) Original Android Development] flar2:
Then it must be a configuration problem. Check that you don't have any other apps changing the setting

It should say 1 in /sys/android_touch/dboubletap2wake

also, make sure you're not turning it off with the pwr button if you have the pwr button toggle setting checked.
[Nexus 7 (2013) Original Android Development] Swimboy46163:
Would anything in gravity box that could be causing this? Because it does say 1 in the system file. And there's nothing in the power button toggle about doubletap2wake.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
I confirm that magnetic cover wake doesn't work for mine too. While it worked flawlessly on 2.6.

It isn't random, it just doesn't work at all.
[Nexus 7 (2013) Original Android Development] En Kee:
Weird, it works everytime here.
[Nexus 7 (2013) Original Android Development] lmulli:
+1
[Nexus 7 (2013) Original Android Development] Batfink33:
Works fine for me.
[Nexus 7 (2013) Original Android Development] rom08:
works fine here too.
[Nexus 7 (2013) Original Android Development] teddy0209:
Everthing works,,, maybe it's something on your end, try reinstalling the kernel...
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Damn. Reinstalled it too. Still no. I'll try dirty flashing the rom and then the kernel.
[Nexus 7 (2013) Original Android Development] Cryptecks:
I may as well chime in and say that my Moko magnetic cover/case is working 100% fine here, seems to be a strange issue.
[Nexus 7 (2013) Original Android Development] GialanG:
My Nilkin cover works properly with both 2.6 and 2.7. No problem at all!
[Nexus 7 (2013) Original Android Development] El Nino1977:
Stock rom and my mag cover works every time on flar kernels. Don't think it's ever failed me yet
[Nexus 7 (2013) Original Android Development] dud3me:
Works fine for me as well. Although, I think my screen was left on for the night since I got over 10h screen on time somehow :p

Anyone know how prone to screen burns this lcd is?
[Nexus 7 (2013) Original Android Development] flar2:
I think I know what might be causing the magnetic cover problem for some and not for others.

I changed one of the default options to disable s2w/dt2w when magnetic cover is used. Maybe something is broke with that.

I'll check when I get home tonight.

In the meantime, maybe someone could doublecheck their settings and test this theory,

The other possibilities:

-you have wifi set to disable during suspend (known issue since this tablet came out)

-something else is disabling the magnetic cover (exposed modules?, Scripts? App?)
[Nexus 7 (2013) Original Android Development] paaaulo:
I use Franco's Per-App Modes. I'd like to change hotplug behavior for a particular app. What's the name of tunable responsible for hotplug?

I guess it is located in /sys/devices/system/cpu/cpufreq/elementalx
[Nexus 7 (2013) Original Android Development] meekrawb:
Which settings should I check, specifically? I have been trying all different kinds with no luck so far.

-WiFi smart cover bug was fixed with the 4.4kk bootloader. Even with WiFi on no change.

-I uninstalled xposed framework and there was no change.

I also installed multirom and flashed the latest Carbon. Stock Carbon kernel, cover works as expected. Flash 2.7, cover doesn't work.

Strange that it only happens two of us!

Edited to add: Installed kernel tuner and trickster mod and didn't see any settings related to smart cover.
[Nexus 7 (2013) Original Android Development] teddy0209:
Maybe not, because i have that set and it is working fine... Maybe it's in the rom they're using...

---------- Post added at 01:12 AM ---------- Previous post was at 01:08 AM ----------

Try reinstalling the kernel with the power button to toggle some wake options unchecked...
[Nexus 7 (2013) Original Android Development] Galaxysm:
Where can I find the CAF version ._.?

Sent from my Nexus5™.

" Nothing's ever locked..."
[Nexus 7 (2013) Original Android Development] NovaSlim:
ElementalX for Nexus 7 2013 don't have a stable CAF version yet, you can try the test build flar2 posted on post #2606

link: http://xdaforums.com/showpost.php?p=51016866&postcount=2606
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Did that too. No change. How can we blame the rom when 2.6 is working flawlessly with it?

Tried your theories too. Still no. P.s I have gboost and max off freq disabled.

Aaron, I also found a small bug where when you enable BLX in aroma, the n7 charges to 92 only, when it should actually charge till 94.

Btw, the deep sleep is friggin 99%. Screw the cover wake, I'm not giving up on this kernel ever!
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
2.7 is working great with today's MIUI release if anyone was wondering :D
[Nexus 7 (2013) Original Android Development] teddy0209:
That is really weird, just done a reflash going back to omni after trying some other roms, it works just fine...

Have you tried flashing the Stock 4.4.2 kernel then flashing over the ElementalX 2.7?
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Yes I did. :/
[Nexus 7 (2013) Original Android Development] Aggror:
DoubleTap2Wake not working.

Dude for some reason DoubleTap2Wake isn't working, though it's enabled.
[Nexus 7 (2013) Original Android Development] teddy0209:
You probably checked the power toggle when you installed the kernel...
[Nexus 7 (2013) Original Android Development] Swimboy46163:
I have the same problem. Still unresolved.
[Nexus 7 (2013) Original Android Development] meekrawb:
Dt2w works for me.

S2w=works

Magnetic cover=doesn't work

Weird stuff.
[Nexus 7 (2013) Original Android Development] flar2:
I can't understand where these problems are coming from. I didn't change these things in the new version.

Nothing has changed and everything works perfect for me. I'm baffled.
[Nexus 7 (2013) Original Android Development] travster119:
I don't have no problems everything is working exactly the same as before :)
[Nexus 7 (2013) Original Android Development] guyd:
I suspect PEBKAC

;)
[Nexus 7 (2013) Original Android Development] mdamaged:
Regarding 2.7 (flo), my Moko cover works fine here...I don't use the *2w stuff so cannot comment on that. Everything else seems fine so far.
[Nexus 7 (2013) Original Android Development] teddy0209:
Deb here, everything works for me either, just like the previous versions...
[Nexus 7 (2013) Original Android Development] Swimboy46163:
Serious question here. Would anything in gravitybox cause doubletap2wake to misfunction?
[Nexus 7 (2013) Original Android Development] teddy0209:
I think none, i never had any problem with it installed, though i only use gravity box on stock as most custom roms are complete with tweaks...
[Nexus 7 (2013) Original Android Development] miesa:
Works great for me. Nothing's different except the timeout. I love the timeout option as forget to press the power button when putting the phone away sometimes.
[Nexus 7 (2013) Original Android Development] hayabusa_ryu:
Everything is working fine except for Sierra modems, still the same problem (driver not found issue). Thanks for the update, looking forward to the problem fix.
[Nexus 7 (2013) Original Android Development] Aggror:
Oh yeah it was :p thanks bro. Sorry for being a noob :p
[Nexus 7 (2013) Original Android Development] kidrobot52:
Try flashing back to stock with this kernel and see if it does the same thing. Maybe a ROM issue. And your using gravitybox and a custom ROM?

Sent from Odin's Beard
[Nexus 7 (2013) Original Android Development] drawde40599:
I'm on 2.7 , stock ROM and gbox 2.99 , having no issues
[Nexus 7 (2013) Original Android Development] flar2:
[MENTION=1174353]hayabusa_ryu[/MENTION]

I don't have the modem, if you want it to work you need to provide details.

For example, the exact model number and dmesg output after you plug it in.

I enabled the driver, but there may not be anything more I can do. It may need additional userspace configuration to get it working. Are you using ppp widget?

EDIT: I think I see what needs to be enabled, will add it next time.
[Nexus 7 (2013) Original Android Development] Flashalot:
[MENTION=4684315]flar2[/MENTION] everything for me is working but USB otg won't work I have tried to reinstall on my ROM (stock aosp 4.4.2)and also on stock it works when the ROM boots up but after it no longer works if you need any logs I'll upload then
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

I figured out why some people had issues with the magnetic cover: there was a typo in the init.d script

The backlight dimmer is now adjustable. Higher numbers make the screen dimmer. The default is 7. I think anything from about 5 to 20 would be reasonable. You can set this in /etc/elementalx.conf

The installer is totally revamped, streamlined, quicker and easier to understand. Let me know if it all works as it's supposed to, I can't possibly try every combination of options.

I added an installer option to set readahead buffer size. This can be changed to whatever you want in /etc/elementalx also.

Download:

Stock/AOSP:

ElementalX-N7-2.8

Cyanogenmod/CAF:

ElementalX-N7-2.8-cm

Changes:

-update installer

-optimize dt2w

-make backlight dimmer configurable

-add Sierra wireless support

-fix magnetic cover option error

-add readahead size option
[Nexus 7 (2013) Original Android Development] flar2:
OTG works fine, just tried it. You may need Stickmount or similar app.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Magnetic cover is alright now ??
[Nexus 7 (2013) Original Android Development] hayabusa_ryu:
Yep, you got the problem. Now it's working. I really thank you for taking your time to fix the problem. The new kernel i.e. 2.8 is working fine. I'm sure it'll carry the elemental legacy of stability, battery backup and performance.
[Nexus 7 (2013) Original Android Development] darzur:
Which one will be working with Paranoid Android 4.1? Stock/AOSP or Cyanogenmod/CAF?
[Nexus 7 (2013) Original Android Development] teddy0209:
AOSP
[Nexus 7 (2013) Original Android Development] Nucleotide:
Hell yeah!! ElementalX for flo. Freaking awesome. Just discovered it. Flashing it now!! ;)
[Nexus 7 (2013) Original Android Development] konradsa:
Hey flar2, I think the backlight dimmer is active by default again in 2.8, even though I did not select it in the installer. How do I turn the dimmer off? Values of 7 and 0 in the conf both don't seem to work.
[Nexus 7 (2013) Original Android Development] paaaulo:
I can confirm. It is dimmer. BLD= 0.
[Nexus 7 (2013) Original Android Development] flar2:
Confirmed, i will fix tonight.
[Nexus 7 (2013) Original Android Development] flar2:
Actually, I'm unconfirming that. I thought I forgot something but I just installed with it disabled, and it was disabled.
[Nexus 7 (2013) Original Android Development] HirogenX:
This kernel has otg support? I tried to mount a stick but nothing happens. I'm using chainfire's stick mount. It was working before but I'm not sure if with this kernel or with the Franco #12
[Nexus 7 (2013) Original Android Development] mdamaged:
OTG works perfect for me with or without this kernel. It's seems it's not the kernel, it's userspace. Clear cache and data for stickmount, uninstall stickmount, reinstall it, make sure your SuperSU is giving it perms.
[Nexus 7 (2013) Original Android Development] HirogenX:
Yes, that's what I did but still don't work. :confused:
[Nexus 7 (2013) Original Android Development] konradsa:
I don't know, it's definitely darker for me. I am using Lux app set to Auto, maybe that has something to do with it.
[Nexus 7 (2013) Original Android Development] mdamaged:
Stock ROM or what?

I might suggest you reflash a stock boot.img, and see if it works.
[Nexus 7 (2013) Original Android Development] HirogenX:
Seems to be a problem in carbon 4.4.2, in the secondary rom (KK4.4.2) it works without any problem. Tomorrow I'll ask in the carbon thread. Thanks for the moment.
[Nexus 7 (2013) Original Android Development] konradsa:
Yes, confirmed, I just went back to 2.7, and normal brightness has been restored again.
[Nexus 7 (2013) Original Android Development] -Loom-:
Darker for me aswell.

Even with BLD=0 it's never as bright as before with 2.7

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] flar2:
I just looked at the code and, yes, there are no braces around my if..else statements for the backlight dimmer. D'oh!
[Nexus 7 (2013) Original Android Development] Ellobo24:
Hey great kernel you got over here..but i try to install the v2.8 and after setting up everything..my Nexus turn off..i had to press the volume down a the power menu to go to the bootloader and restart the phone..i wipe the cache/delvik cache before installing..can you tell me what i'm doing wrong here?..thanks
[Nexus 7 (2013) Original Android Development] mdamaged:
What ROM, and did you come from a different custom kernel?
[Nexus 7 (2013) Original Android Development] Ellobo24:
AOSP Kangs..and i had v2.6 version before installing v2.8
[Nexus 7 (2013) Original Android Development] konradsa:
Lol... Been there, done that. ?
[Nexus 7 (2013) Original Android Development] flar2:
I think I got everything this time

Download:

Stock/AOSP:

ElementalX-N7-2.9

Cyanogenmod/CAF:

ElementalX-N7-2.9-cm

Changes:

-fix backlight dimmer typo
[Nexus 7 (2013) Original Android Development] mdamaged:
You forgot to upload them, getting a 404 on those links.

Kidding! thanks, but why is it 2MB smaller than the rest of the kernel's zips?
[Nexus 7 (2013) Original Android Development] tiny4579:
Disable screen timeout in your recovery. Pretty sure it's an issue with that and aroma.
[Nexus 7 (2013) Original Android Development] mbdw:
Given that there was apparently just a small typo fix between 2.8 and 2.9, any reason for the big file size reduction (from 11.58 down to 8.9 MB)? Just wanted to confirm before flashing that there wasn't an upload issue.
[Nexus 7 (2013) Original Android Development] mdamaged:
Yeah, I noticed the same thing. The kernel itself is much smaller.
[Nexus 7 (2013) Original Android Development] Ellobo24:
I'm using TWRP..and it happen just when i press finish..1or2sec later it turn off..but hopefully v2.9 will fix it..I'll report later..thanks

---------- Post added at 12:17 AM ---------- Previous post was at 12:11 AM ----------

Well v2.9 fix the problem, it flashed just fine..and thanks for this kernel.. :):thumbup:
[Nexus 7 (2013) Original Android Development] xparagonx:
+1 on this. I had this problem with 2.7 and 2.8. But everything is fine on 2.9. I'm running latest PA and twrp.
[Nexus 7 (2013) Original Android Development] cobyman7035:
Is 2.7 out yet? Been a while on 2.6 huh.. Thx I don't browse XDA much these days

Via my NeXus™ 7 FHD on Tapatalk⁴ Pro
[Nexus 7 (2013) Original Android Development] mrshades812:
Look through the thread a little...?
[Nexus 7 (2013) Original Android Development] quickstang:
Could have read the post above yours to answer your question.

However, I do believe the thread title does need updated. Many times to know if anything is updated, I just read the notifications from tapatalk & see if the titles change with updated dates, version number, etc. Especially if it's a thread which I really don't have any questions on, or issues with the rom, kernel, app, etc.

Just my opinion, but it makes it so much easier if one doesn't need to follow a thread closely. I've never had an issue with this kernel, so it's not followed really close. Luckily I do check on occasion to know 2.9 is out.
[Nexus 7 (2013) Original Android Development] NovaSlim:
Thanks flar2 for the update, 2.9 flashes just fine.
[Nexus 7 (2013) Original Android Development] waz675:
Yup, I never realised versions were out after 2.6 due to thread title. I noticed the last post stating 2.9 flashed fine so off I went into here heh. Mind you, I was hospitalised most of the past week and generally been pretty bad via a stomach thing I've had since I was 6 and requiring surgery in 2000, thought I was a goner recently.

Wife at work, I'm with our 2 kids aged 2 and 4, collapsed on bed, kids think I went for a sleep and they watched peppa pig entire series to pass time (LOL) wife comes home and finds me, ambulance and hospital, back home now but still feel too tender in the stomach.

Valid enough reason to have missed recent updates? Ha.. On, flashing 2.9 and try to sleep ;p
[Nexus 7 (2013) Original Android Development] xda890:
Any plans to add a timeout feature for double tap to wake like you did for the nexus 5? Else this kernel is perfect... :)

Regards,

BTJ
[Nexus 7 (2013) Original Android Development] flar2:
I don't put stuff in the OP right away because I need to know it works before lots of people download it. This thread would have been full of complaints from the small bugs in the last couple betas. But I think it's ready now. Thanks to those who reported stuff, I wouldn't notice some of this stuff without user feedback.

The kernel image is smaller in the latest because I switched to a different compression method. It makes no difference to performance or functionality, it just makes the file a bit smaller.

Hope you will be alright