yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] noneabove:
I wouldn't worry too much about it, from my understanding, unless this is done differently, it should only drain battery when the screen is being touched (while the screen is off) because once there is contact made with it, the cpu turns on to see if you're following the proper pattern, if you are then you're waking it up anyways, if you aren't then you're wasting cycles, but it won't waste cycles unless you touch it :)
[Nexus 7 (2013) Original Android Development] jlevy73:
Just flashed the newest FW from Google then reinstalled this kernel. I can say that any of the multitouch weirdness I was having is no more. Also, DT2W works whether laying on a table or in my hand. So whatever secret sauce Google used seems to have done the trick.
[Nexus 7 (2013) Original Android Development] Marck527:
Where did you get the stock kernel to flash before updating?
[Nexus 7 (2013) Original Android Development] ktkr:
The kernel changes do exist but they are not on the source yet, https://android.googlesource.com/device/asus/flo-kernel/+/d312e61
[Nexus 7 (2013) Original Android Development] Philaphlous:
So this update is a kernel update? If it gets pushed through Google do I jus update as normal? It'll show as a system update right? Will I have to reinstall busy box and super su? Then obviously flar will have to update this kernel for the newest change right?

Lol lots of questions
[Nexus 7 (2013) Original Android Development] jlevy73:
Interesting, so the changes to fix the touchscreen are located in the kernel. Good to know. Guess I should stay stock until [MENTION=4684315]flar2[/MENTION] merges the changes.
[Nexus 7 (2013) Original Android Development] ktkr:
I'm not sure what did the Android team changed in the queue update but I'm sure devs will update once the change gets on the source. What we have to do is waiting patiently, if the issues are really serious on your device you can temporarily go back to stock, latest one of course.
[Nexus 7 (2013) Original Android Development] tiny4579:
That's the prebuilt. The kernel source is in kernel/msm. I don't think the fix us in the kernel.
[Nexus 7 (2013) Original Android Development] jlevy73:
If the fix is not in the kernel, where would it be?
[Nexus 7 (2013) Original Android Development] tiny4579:
You said with the update and this kernel you are not noticing the multi-touch issues. That says to me that the fix isn't in the kernel.
[Nexus 7 (2013) Original Android Development] tvisforme:
Thanks for the quick response. Sounds very reasonable.
[Nexus 7 (2013) Original Android Development] just lou:
Just a note, 4.03 seems to work fine with the new LMY48I build.
[Nexus 7 (2013) Original Android Development] ptmax13:
Has anyone tried 4.03 with the latest LMY48L for DEB?
[Nexus 7 (2013) Original Android Development] flar2:
No, but it will work. No kernel changes in recent update
[Nexus 7 (2013) Original Android Development] Z23:
Strange problem after installing on newest stock rom. Device shut of on first reboot and did boot only after I startet bootloader. No overclocking. Now its working fine.
[Nexus 7 (2013) Original Android Development] Alex 90:
Good morning, If I flash the ElementalX kernel on my nexus 7 2013 flo and later If I want to go to the stock kernel how can I (with a backup from the recovery)? Thanks,
[Nexus 7 (2013) Original Android Development] obaz:
I have a strange bug - usb not work on my Flo with this kernel. but it for on 5.1.1 cyagenmod - I wonder why ?
[Nexus 7 (2013) Original Android Development] marsaltito:
Flash rom again or find default kernel.tip for the same (tip search for kernel on forum where you downloaded rom ).

---------- Post added at 05:56 PM ---------- Previous post was at 05:54 PM ----------

Otg+charge or just otg?
[Nexus 7 (2013) Original Android Development] obaz:
everything ok now. I`ve reflashed the kernel and things are better now. both otg and otg+charge are working now
[Nexus 7 (2013) Original Android Development] rbross3030:
Hi flar2,

Thanks so much for such a fast and solid kernel. This might be sort of an esoteric request, but on later batches of Nexus 7s to be produced there was an eMMC hardware revision. This is causing a boot loop for those attempting to run 4.4.4 on newer Nexus 7s that shipped with 5.0 pre-installed.

mmc: add 5.0 emmc support

bug: 17968808 Kernel change for new eMMC v5.0 parts for FLO/DEB

Change-Id: Ia18152457fe3ff70401b199c267fa37374b9d544
Signed-off-by: hsuan-chih_chen <hsuan-chih_chen@asus.com>

diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c
index dc4b125..ea1eca7 100644
--- a/drivers/mmc/core/mmc.c
+++ b/drivers/mmc/core/mmc.c

@@ -293,7 +293,7 @@
}

card->ext_csd.rev = ext_csd[EXT_CSD_REV];
-	if (card->ext_csd.rev > 6) {
+	if (card->ext_csd.rev > 7) {
pr_err("%s: unrecognised EXT_CSD revision %d\n",
mmc_hostname(card->host), card->ext_csd.rev);
err = -EINVAL;

a modified boot.img has been posted that fixes this problem the stock 4.4.4 kernel but I was wondering if it would be possible to get a patched boot.img for ElementalX 2.15? If I flash the aforementioned boot.img performance really suffers so I'm guessing its overwriting other stuff it shouldn't be in your kernel. Any help would be greatly appreciated, thanks!
[Nexus 7 (2013) Original Android Development] cobyman7035:
Does exposed framework work on 5.1 android yet?
[Nexus 7 (2013) Original Android Development] Phoenix09:
there's an unofficial build
[Nexus 7 (2013) Original Android Development] DroidIt!:
Yes, it has for quite awhile ;) http://xdaforums.com/showthread.php?p=59901239
[Nexus 7 (2013) Original Android Development] SoftwareFailure:
rbross3030 :

You can try this one : http://xdaforums.com/showpost.php?p=61906525&postcount=94
[Nexus 7 (2013) Original Android Development] paolocorpo:
has this kernel the patch to fix the wakelock baseband_xmm_power ??
[Nexus 7 (2013) Original Android Development] rbross3030:
Ah! Thanks so much, I will try this out!
[Nexus 7 (2013) Original Android Development] Nic2112:
Just to be sure, I'm very new to the Nexus 7 world, I can use the CM version of the Kernel with the Blisspop ROM correct?

I'm 96% sure it's a yes but I always like to make sure. I used to use Flar's kernel in the past and i'm looking forward to running them again.
[Nexus 7 (2013) Original Android Development] idCyber:
CM version works great with Blisspop
[Nexus 7 (2013) Original Android Development] kurci2:
Boot Loop

Hello!

I have just updated Android 5.1.1 from version LMY48G to LMY48I, rooted my tablet and installed Elementalx 4.03.

Now I am in a bootloop.

I have kept all the default settings during installation.

Does any one have an idea why is that happening? Or maybe a solution? I installed Android over once again so i have working tablet, but i would like to also have Elementalx kernel.

I think that you also have to know that I have updated my device using Nexus Root Toolkit yith "NO WIPE" mode enabled.

Thank you!
[Nexus 7 (2013) Original Android Development] quickdraw86:
You didn't provide enough clear information for anyone to offer you anything but a totally speculative answer. Are you coming from a stock rooted ROM, or straight stock? How did you install elemental x? Do you have a custom recovery? Are you certain you are unlocked and rooted? Did you root before android 5.x, or after? If you have a custom recovery, do you mean you looped when you rebooted to recovery, or after flashing the kernel? Which version of the elemental x kernel did you install, AOSP or CM? If you're not sure about some of this information, you can find classification for most of it in this thread OP, stickied flo threads, or the thread for NRT.
[Nexus 7 (2013) Original Android Development] kurci2:
I can provide you all needed information and I am sorry that i did not not do that already.

I come from stock rooted room Android 5.1.1 LMY48I. I installed rom using no wipe option using Nexus Root Toolkit. After installation I immediately rooted the device and installed costum recovery TWRP 2.8.7.0,all also using Nexus Root Toolkit. I am certain am unlocked and rooted, and I use rooted android from the day i got the device with android 4.4.4 preinstalled.

I installed ElementalX Stock/AOSP (Android 5.1.1) version 4.03 from TWRP recovery using AROMA installed and kept all setting default during the installation. The device bootlooped after I restarted it - so after flashing the kernel. I can still boot to recovery.

The ElementalX kernel was the first thing after rooting the device that I tried installing on my device after I installed android version LMY48I. I know I could just make a clean install and begin fresh, but I really do not want to do that - it is the last option.

I would also like to post any useful logs, but I do not know where to find them.

Thank you for your answer.
[Nexus 7 (2013) Original Android Development] quickdraw86:
If you came from stock rooted 5.1.1 LMY48I, why did you have to root again after you installed the ROM? Are you using the multirom version of TWRP... if you were unlocked and rooted from kitkat, you don't necessarily need multirom TWRP unless you use multirom, but those that rooted and unlocked from 5.0 or greater do. Is there an error in the TWRP output before or after elemental x installation? Try using the latest official TWRP to install, of you haven't, or boot back into your stock rooted ROM and make sure you don't have any kernel settings apps set to set values on boot prior to rebooting to recovery to install. Just some ideas. As you said, whipping cache and userdata would be next, but it's worth exploring other things if you want to avoid doing that.
[Nexus 7 (2013) Original Android Development] kurci2:
I am afraid that I do not understand you. I had Android 5.1.1 LMY48G installed and I upgraded to LMY48I. When you upgrade you install stock rom that is not rooted, so you have to root it again. I have always done it that way. Upgrade also installs stock kernel. I have also never used multirom. I have alwayd installed the latest TWRP using Nexus Root Toolkit (I use that toolkit for every update for my device).

I also do not use any apps to change my kernel settings and there were no errors during elementalx installation. It is all very strange.

I guess that a clean install is my only option. I will do it as soos as I create full backup using TWRP and then I will report back if it will work.
[Nexus 7 (2013) Original Android Development] quickdraw86:
I just meant that razor/flo devices that ship with android 5.0 or greater stock have to use multirom TWRP. I realize now that you mean that you always flash stock images through nexus root tool, and root them afterwards, which is why I was curious about whether or not you were unlocked after your most recent visit to stock... If you don't see any error output in recovery, and do see the unlocked splash screen when you boot the device or visit the bootloader, yes, you will likely want to wipe.
[Nexus 7 (2013) Original Android Development] kurci2:
Thank you for all your help. I will wipe my device and start clean and see if it will work.

Thank you!
[Nexus 7 (2013) Original Android Development] quickdraw86:
No problem, glad to help out, and hope you get it going.
[Nexus 7 (2013) Original Android Development] nazfalas:
There have finally been new kernel commits for our device(s): http://www.cmxlog.com/12.1/deb/

Hoping for an updated kernel :)
[Nexus 7 (2013) Original Android Development] brolic925t:
Anyone else get black screen of death when trying to turn tablet on n off fast. Any fix?
[Nexus 7 (2013) Original Android Development] DroidIt!:
No, not here. The only time I ever get a blank screen is when I'm calibrating screen color to my liking. If you wait a couple seconds does it still do it or just turn off and on real quick?
[Nexus 7 (2013) Original Android Development] brolic925t:
It happened like i times yesterday. And a lottt before which is why i stopped using my tablet. But i learned to just take my time turning the screen on again after turning off. Hasnt happened all day. I think it has to do with the gamma settings
[Nexus 7 (2013) Original Android Development] quickdraw86:
You shouldn't have to concern yourself with maintaining a time delay from screen off to on. Obviously, you have an issue with either the kernel, the settings you selected in aroma, or the way you went about installing the kernel...
[Nexus 7 (2013) Original Android Development] tvisforme:
With respect to screen calibration, I just wanted to confirm that my installation is working correctly. Are the options for the screen restricted to RGB or should I see other parameters such as gamma?
[Nexus 7 (2013) Original Android Development] brolic925t:
Well I believe my problem was in aroma. More toward under volt, I reinstalled kernel with all stock settings except screen dimmer and all is good. But! The only way to get black screen now is to turn screen off after applying gamma settings before it says to do so(that's only during initial setup, once its set it won't happen again)
[Nexus 7 (2013) Original Android Development] maigre:
If I try to adjust RGB values via Kernel Adiutor, the screen flashes to the current color I'm adjusting. The only way out is to reboot.
[Nexus 7 (2013) Original Android Development] mdamaged:
Works fine with flar2's app, maybe you should report it to the developer of KA? ...or just use flar2's app.
[Nexus 7 (2013) Original Android Development] maigre:
It's worth knowing that it's fine via flar2's app. I'll report to the KA dev, too.
[Nexus 7 (2013) Original Android Development] kurci2:
Stuck on boot screen after enrypting

Well, now I have some more information.

I have done I clean install of Stock Android 5.1.1 version LMY48I. After installation I rooted and installed TWRP 2.8.7.0. All using Nexus Root Toolkit.

After that I installed ElementalX 4.03 using Aroma installer via TWRP. Everything worked perfectly.

But then I encryped my device (Settings --> Security --> Encrypt device) but I did not set any lock screen option. Only encryption.

After that my device could not start any more. It is stucked on boot screen.

I think that this is a bug. I would like to provide any other information (logs,...) if they are stored my device.

Thank you!
[Nexus 7 (2013) Original Android Development] flar2:
That is not Kernel related
[Nexus 7 (2013) Original Android Development] kurci2:
Thank you for your reply. Do you have any other idea where to find solution for this issue. I can not think of any other possibility than an interference between Android encryption and ElementalX kernel...
[Nexus 7 (2013) Original Android Development] flar2:
There are many possibilities, I never mess wih these things. I just leave it the way it is on a default install.
[Nexus 7 (2013) Original Android Development] LucentBirch:
Anyone else having issues with location / GPS?
[Nexus 7 (2013) Original Android Development] quickdraw86:
No issues here.
[Nexus 7 (2013) Original Android Development] kurci2:
Stuck on boot screen after enrypting

I have some test results I have done.

I have installed clean Android 5.1.1 LMY48I and I did not log in to my google account and did not change any settings. After that I rooted my device and installed TWRP 2.8.7.0.

After that I installed ElementalX 4.03 with all settings default. Everything worked perfectly.

After that I reinstalled a clean copy of Android (the same as is described in the beginning of the post) and the first thing was to encrypt the device. After that I installed ElementalX and I got stuck on the boot screen.

After that I reinstalled Android one again and installed ElementalX. Everything worked great. After that I encrypted my device and got stuck on boot screen.

I do not have your developing knowledge and I can not solve this issue, but I think that there must be some interference between encrypted file system and ElementalX kernel.

I am really sorry if I am mistaken. I hope that someone could try my steps and confirm or deny this issue, so I could solve this and enjoy all the great functions of this kernel.
[Nexus 7 (2013) Original Android Development] LucentBirch:
Wrong thread haha sorry
[Nexus 7 (2013) Original Android Development] fluther:
I've got the same problem with Ex versions 4.02 and 4.03. My flo never gets to the decryption screen. Works perfectly with 4.01.
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

Merged latest Google changes, including security updates

Download:

ElementalX-N7-4.04

Changes:

-latest updates from Google
[Nexus 7 (2013) Original Android Development] quickdraw86:
The purchase of your ElementalX kernel app is becoming an increasingly better investment all the time. Thank you for your work on the flo kernels, the options available through aroma, as well as the overall stability of EX, makes it well worth a try for users old and new alike. Good :)
[Nexus 7 (2013) Original Android Development] flar2:
Thanks!

And you'll be able to get the new update on the app in about 10-15 minutes. My upload speed is really, really slow.
[Nexus 7 (2013) Original Android Development] bleuxeon:
Any plans for the CM 4.04 version or is it a complete different task?
[Nexus 7 (2013) Original Android Development] flar2:
Someone said there are new commits in the cm tree I'll have to take a look and see if they are necessary.

Does 4.03-cm work on the latest CAF ROMs?
[Nexus 7 (2013) Original Android Development] treehugger38294:
Does anyone get Chrome freezes sometimes? The page will hang and if I pull down the notification bar, it will scroll. This is the same as the freezes on my N5 before they were fixed.
[Nexus 7 (2013) Original Android Development] DaveImagery:
Thank you flar for your continued support of Nex 7
[Nexus 7 (2013) Original Android Development] quickdraw86:
Yes, 4.03 cm works fine on the latest CM, and derivatives of it.
[Nexus 7 (2013) Original Android Development] Natakranta:
Update detected in EX app :)

Flashed it on Twisted ROM.

I'll play with it tonight.

Thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Nexus 7 (2013) Original Android Development] nazfalas:
On Exodus for example the nightly from 09-09 has working radio with 4.03-cm, but it stops working on latest 14-09.

Edit:

Well, not getting radio on any version now...so scratch that.
[Nexus 7 (2013) Original Android Development] ptmax13:
Yeah! I get the same behaviour with Chrome. How was it fixed for your N5?
[Nexus 7 (2013) Original Android Development] treehugger38294:
There was some code that needed to be merged in. I remember a few months ago almost all of the kernels had this issue on the N5. I'm using Glitched now and I don't seem to get the freezes anymore.
[Nexus 7 (2013) Original Android Development] flar2:
The chrome thing was not a Kernel problem. There was no fix that I did. Only some people experienced the problem and it just went away. I've never experienced slowdowns in chrome on any of my devices.

I haven't changed anything much on this kernel in many months. If you've started to experience a problemat this point, its definitely not Kernel related. I would suggest wiping cache and dalvik, maybe data as well.
[Nexus 7 (2013) Original Android Development] treehugger38294:
Alright I'll flash again and report back.
[Nexus 7 (2013) Original Android Development] CYoung234:
Yes, I am using 4.03 with Exodus on my Nexus 7, and it works fine. It does not really provide any performance gains over the stock kernel on Exodus, but provides better audio control. That is why I am using it. But it runs well, don't get me wrong.
[Nexus 7 (2013) Original Android Development] marsaltito:
Yes !

12.1-20150915-NIGHTLY-flo work with 4.03-CM .
[Nexus 7 (2013) Original Android Development] garrettcorn:
Hey [MENTION=4684315]flar2[/MENTION]

Would you be willing to add support for https://play.google.com/store/apps/details?id=remote.hid.keyboard.client

Here is the gitHub, which i believe has everything you would need https://github.com/pelya/android-keyboard-gadget

Thanks, great kernel, and lover your app!
[Nexus 7 (2013) Original Android Development] androidfr33k:
What was the last release for v4.4.4? I thought I saw a v3.4 elemental but cannot find it in this thread or on ElementalX.org?

Can someone provide a working link for version 3.4 Flo please. Thanks
[Nexus 7 (2013) Original Android Development] adomm420:
Just a friendly suggestion, you can buy elementalX kernel app from playstore and download latest kernel version through the app.
[Nexus 7 (2013) Original Android Development] androidfr33k:
Will it have all the versions for an older OS? v4.4.4?

Edited:

Apparently v2.15 was the last one made for OS 4.4.4, not sure where I got 3.4 from? I must have seen 3.4 in front of the name which would be the OS Stock Kernel version and after it is ElementalX version, 2.15!!
[Nexus 7 (2013) Original Android Development] szty0pa:
Hey [MENTION=4684315]flar2[/MENTION],

Thanks for all your work on ElementalX!

I believe to have found the bug with the encryption that others mentioned before. On current CM nightlies (I've tried two or three of them) if you set a password for encryption the Nexus7 is stuck at bootanim with ElementalX - without password or with a different kernel everything works fine. (Could it be that the code responsible for user password input is missing or buggy?) I believe it also gets stuck at bootanim when the tablet gets encrypted for the first time after the green wireframe android, before the actual encryption would take place.

Could you please have a look at it sometime?

Thanks! :)
[Nexus 7 (2013) Original Android Development] bsw11:
I am running Clean ROM 6.2. Using Scott's kernel rotating the screen works just fine. Using your kernel it does not work. The compass app I have does not work as well. Any ideas?
[Nexus 7 (2013) Original Android Development] NovaSlim:
Different rom, same kernel. screen rotation and gps works just fine.
[Nexus 7 (2013) Original Android Development] bsw11:
yeah I think it's either a faulty accelerometer or a conflict in my xposed modules.
[Nexus 7 (2013) Original Android Development] ShadowEO:
Great Kernel, I get fantastic battery life. However I am trying to compile it from source to add some kernel features for my Ubuntu chroot, however I can't seem to get it to compile. I am thinking it's my toolchain seeing as the build.config in the source folder is using GCC 4.6 and I was attempting to use the 4.8 NDK toolchain. May I ask where you get your toolchain from? or did you compile it from scratch?

EDIT: Wanted to mention, I am specifically trying to enable XFree86 DRI Support, MSM KGSL_DRM, Framebuffer Console as a module, KSM/SWAP/ZSWAP/ZRAM as modules.

EDIT: Scratch the previous edit that was here, still failing, but I think it's my own fault.
[Nexus 7 (2013) Original Android Development] polygon21:
have that same problem too... a little annoying
[Nexus 7 (2013) Original Android Development] DroidIt!:
Hey [MENTION=4684315]flar2[/MENTION]. Um was just wondering, were you still planning on doing a cm version of 4.0.4? Just curious if that's still on the agenda. :)
[Nexus 7 (2013) Original Android Development] yiannis1621991:
Does this kernel work with the latest 5.1.1 (LMY48M)? What are the main advantages over the stock kernel?

Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk
[Nexus 7 (2013) Original Android Development] kindofabuzz:
Read the very first post.
[Nexus 7 (2013) Original Android Development] yiannis1621991:
I wanted a user's opinion about battery life and performance compared to the stock kernel.
[Nexus 7 (2013) Original Android Development] quickdraw86:
It's always best to try for yourself and form your own conclusions, but I've had a positive experience with elemental x, both on AOSP and CM versions, and have found that elemental x with my preference in settings at install, offers better battery and performance than stock. I won't bother to post battery stats, as that is pointless in my opinion, but I've been overall happy using EX, and have never had any issues with it that I recall.
[Nexus 7 (2013) Original Android Development] tashik19:
Please fix it!

Usb otg works now. Thanks.
[Nexus 7 (2013) Original Android Development] masri1987:
attempting to use the permissive.zip with 4.04 to no avail on the latest dirty unicorns.