yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] CasseTrop:
Hi,

I'm using this Kernel with CandyRom and a Y OTG cable (In my car).

I am getting the Tablet charged but very slowly and when I check the battery settings it doesn't say it's charging.

I enable the Y OTG and the Fast Charge in Aroma when I installed it but it doesn't charge really well.

Anything I'm missing here ?
[Nexus 7 (2013) Original Android Development] mdamaged:
My guess is not enough voltage is being delivered, and/or it's some kind of wakelock. Either way, not the correct thread to post this in.
[Nexus 7 (2013) Original Android Development] CasseTrop:
Voltage is fine when I don't use an OTG cable.
[Nexus 7 (2013) Original Android Development] mdamaged:
Maybe the OTG cable, maybe you're using one of those China made cables that suck? Either way, still not the right place for this.
[Nexus 7 (2013) Original Android Development] BladeRider:
[MENTION=4684315]flar2[/MENTION], would like to know are there any plan to update the kernel to fully support 5.1? Thanks ?
[Nexus 7 (2013) Original Android Development] CasseTrop:
Are you mad ?
[Nexus 7 (2013) Original Android Development] mdamaged:
Absolutely insane!
[Nexus 7 (2013) Original Android Development] DaveImagery:
Thus far, I've noticed no issues with ver 3.05 on 5.1.
[Nexus 7 (2013) Original Android Development] pieces of cake:
Can someone please explain what the "Power Amp Gain" adjustment (under Sound settings) does?
[Nexus 7 (2013) Original Android Development] mdamaged:
Adjusts gain for headphone amp.
[Nexus 7 (2013) Original Android Development] pieces of cake:
Considering the fact that the adjustment right above "Power amp gain" is labeled "Gain," I don't think your answer is accurate. Under "Headphones," in the "Sound" section, "Gain" is set by default to 0. "Power amp gain" has a default setting of 3.

Can someone who is familiar with this kernel please explain the difference between these settings?

Thanks in advance!
[Nexus 7 (2013) Original Android Development] mdamaged:
Sounds like you got it all figured out. This is based on faux's patch so that is what it is according to faux, and I'm thinking he knows more about it than you do, but whatever creams your twinkie.
[Nexus 7 (2013) Original Android Development] pieces of cake:
Exactly how does your response explain the difference between "Gain" and "Power amp gain?" That's my question, you brilliant shining star, you!

Anyone with a lot more knowledge and a little less attitude care to help out with explaining the difference between these two adjustments?
[Nexus 7 (2013) Original Android Development] mdamaged:
Not sure who put sand in your panties, but, one is at the hardware level, the other software.
[Nexus 7 (2013) Original Android Development] pieces of cake:
You might know the dude, actually. It's all good now though, because he just vacuumed most of it out. Wasn't a particularly gentle cleansing, but at least he made the effort to do the right thing.
[Nexus 7 (2013) Original Android Development] notbrodie:
has anyone gotten f2fs data/cache working with elementalx yet?
[Nexus 7 (2013) Original Android Development] kindofabuzz:
So the new version of the app got rejected by Google?
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

Sometime, I want to make a few more changes, but I don't have time right now. I feel performance could be improved a bit.

For Android 5.1

Download:

ElementalX-N7-4.00

Changes:

-lollipop-mr1 update
[Nexus 7 (2013) Original Android Development] flar2:
No, the existing app was removed on a technicality. It's gone from the Play Store, but you can still use it.

Anyone who purchased it and needs the apk can download it:

http://xdaforums.com/showpost.php?p=60137782&postcount=17522

http://xdaforums.com/showpost.php?p=60160313&postcount=4785﻿

I will be releasing a new app soon.
[Nexus 7 (2013) Original Android Development] kindofabuzz:
Is this just the last version before it was removed?
[Nexus 7 (2013) Original Android Development] DroidIt!:
So what did you end up deciding to do with the goog sitiation if you don't mind me asking. :) Just curious is all. :angel:

...oh, and great to see a 5.1 version btw. Thanks for keeping the flo together ;)
[Nexus 7 (2013) Original Android Development] prototip1974:
And there will be a new kernel for CM 12.1? Or 4.0 suitable for SM12.1?
[Nexus 7 (2013) Original Android Development] drewski_1:
OP says this is just for stock/AOSP based so not suitable for CM 12.1
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Dude your app is amazing, and essentially the same as every other kernel maintainer. What issue could Google gave possibly had with it?
[Nexus 7 (2013) Original Android Development] mdamaged:
I think flar2 mentioned it may have had something to do with the permissive setting.
[Nexus 7 (2013) Original Android Development] cee43ja1:
Eventhough I just flashed this when it was just released, those improvements you want to do will only refine this solid kernel. No hiccups, no stuttering, no random reboots.

And for the 2-3 days I had EX 3.05 on 5.1, it was working just great, regardless of not using the new 5.1 sources.
[Nexus 7 (2013) Original Android Development] DaveImagery:
So rumors of 5.1.1 already floating around?

http://www.androidauthority.com/android-5-1-1-references-googles-site-601945/
[Nexus 7 (2013) Original Android Development] Traxex_:
Does anyone know where to find the stock kernel for Android 5.1 cause chroma uses Franco kernel as default.
[Nexus 7 (2013) Original Android Development] mdamaged:
https://developers.google.com/android/nexus/images
[Nexus 7 (2013) Original Android Development] Traxex_:
I meant already extracted as a flashable zip [emoji14]
[Nexus 7 (2013) Original Android Development] mdamaged:
Just extract it from the image and flash it yourself.
[Nexus 7 (2013) Original Android Development] alancai:
Any chance that f2fs is supported please?
[Nexus 7 (2013) Original Android Development] mdamaged:
It already is, cat /proc/filesystems
[Nexus 7 (2013) Original Android Development] alancai:
Thank you.

How come when I use twrp to change cache partition to f2fs it is automatically reverted to ext4 when system reboot completes?
[Nexus 7 (2013) Original Android Development] txpxsx:
any good tweak combination for deb ElementalX-N7-4.00 ?

currently leaving all settings as default

thx
[Nexus 7 (2013) Original Android Development] lollimolly:
Not working anymore

Hello i just flashed the new 20150420 cm 12.1 and after flashing the kernel the device stops at google logo then it restarts into twrp

without the kernel it boots up fine without problems

i just flashed back the 18/4 version with elementalx and its working fine

ps. this thing happened yesterday too

CyanDelta gave an 19/04 update for my tablet which wasnt posted on the cm download site so i thought it was a faulty update

but now they posted the 20/04 version and its the same problem...

any help please?
[Nexus 7 (2013) Original Android Development] mslatter:
Same happened for me on another cm spin off. I'd guess Kernel is no longer compatible with latest Cm base. I'd rather use aosp anyway :)
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Look at the title of the thread. AOSP only. CAF based ROMs are no longer supported.

---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------

You can do this with the factory image directly from your device without needing a "flashable zip".

- Download factory image to device

- Unzip the archive

- Unzip the archive within the archive

- Copy boot.img to root of your SD card

- Install Flashify

- Run Flashify

- Tap flash kernel, from storage

- Select the boot.img from the factory image that you copied out

- Flash it, reboot, and prosper.

I've done it before without issue. Should work just fine.
[Nexus 7 (2013) Original Android Development] flar2:
I will do a caf version as soon as I have time
[Nexus 7 (2013) Original Android Development] notbrodie:
you need to have a kernel with f2fs ramdisk entries installed prior to elementalx. however, elex isn't compatible with any of those kernels. i even tried a dummy kernel with just ramdisk entries and it still didn't work. unless something changed between 3.05 and 4.00, it still doesn't work.
[Nexus 7 (2013) Original Android Development] Traxex_:
Which app are you guys using to load color profiles? I'm normally using FKU or Display Control, but none of them is working even that I enabled color control in aroma.

In case someone wants the stock 5.1 kernel: https://docs.google.com/file/d/0B78D-aajjVnPZFhkRVh4UzkyaWc/edit?usp=docslist_api
[Nexus 7 (2013) Original Android Development] DroidIt!:
Well, two things. When you install flar's kernel make sure you use the aroma version and tick the option to enable color control. I think it's on the last screen in the installer. Then I use flar's app. He posted the links in post #4551 in this thread ;)
[Nexus 7 (2013) Original Android Development] Traxex_:
I need to wait til we are able to buy the app again.

Good to know it's possible to switch color profiles with it.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Yah, I've not tried a different app with flar's kernel. I honestly bought the app at the same time as I flashed the kernel because I like to see what a dev has on the table. There should be some way to manually change the values wherever the kernel is installed to. In my experience, the kernel apps are really just a GUI that make it easier for users to change configurable values in the kernel.
[Nexus 7 (2013) Original Android Development] DaveImagery:
Wanted to add my thanks flar, 4.00 works flawlessly.
[Nexus 7 (2013) Original Android Development] nokiagye:
I have a bug on lollipop if I enable the gamma on aroma and boot the tab many times I can't unlock the tab the screen is black and only a hard reboot fix it without the gamma it working great. On yours working good?
[Nexus 7 (2013) Original Android Development] flar2:
The color control has never worked well on this device, that's why it's not enabled by default
[Nexus 7 (2013) Original Android Development] Woody:
Yup. I remember once when I first got this tablet and put on color control with some of my N5 profiles (through Franco's kernel), then locked the screen. Came back with all black. :eek:

I did find that [MENTION=1240506]thegingerbreadman[/MENTION] had some color profiles that were pretty good on the N7. I haven't applied them on ElX, but if anyone wants them, I'll upload later on. Being that the option isn't there on ElX.apk, it might be hard to apply them. ;) [MENTION=4684315]flar2[/MENTION] Do you want me to just send them to you for review and then you can make the decision?
[Nexus 7 (2013) Original Android Development] DroidIt!:
What seems to work for me is from a reboot, let it boot all the way up until you see the lockscreen and don't touch the tablet, just let the screen go dark. I give it about 30 more seconds or so and then start playing with the tablet and I notice the color affects have applied and no blank screens. :)
[Nexus 7 (2013) Original Android Development] flar2:
Sure, send them and I'll look at the format

I think the problem shows up more if you change things several times. Applying one change and leaving it will usually work.

Cyanogen tried to add their color control code to this device, but reverted it due to these issues. If kondik doesn't know how to fix it, its probably a difficult fix
[Nexus 7 (2013) Original Android Development] jlevy73:
I agree with all the comments, superb kernel. 40 hours off the charger with 40% still left, 4 hours on screen time and 90% of that was gaming. I have everything OC'd like crazy...can't imagine the results if I actually dialed it down a bit.
[Nexus 7 (2013) Original Android Development] NekroWolfen:
Can you tell me your complete settings? ROM, cpu, gpu, volts, everything?

That's awesome! I've been using this kernel since .6 but I've never dare to OC past 1.7 :)
[Nexus 7 (2013) Original Android Development] jlevy73:
I'm using CleanRom 1.3, this kernel with the following settings:

CPU: 1836/384, on-demand

I/O: deadline

Read ahead buffer: 1024

UV: -50mV

GPU: 487, simple

The rest I didn't touch (using Trickster Mod to modify CPU/GPU settings)

In aroma I chose L2 ultra and S2W, short sweep 2 wake, DT2W and for thermal settings, run hot

Hope that helps
[Nexus 7 (2013) Original Android Development] NekroWolfen:
Sure it does! Thanks a lot!
[Nexus 7 (2013) Original Android Development] jlevy73:
One thing you should check is what your CPU is binned at. Some lowed binned chips will not be able to handle significant OC. I am lucky in that my chipped is binned at PVS5.

To check yours follow the directions in the OP here: http://xdaforums.com/showthread.php?t=2381501&highlight=pvs
[Nexus 7 (2013) Original Android Development] NekroWolfen:
Mine's PVS3... not much luck :)
[Nexus 7 (2013) Original Android Development] Marck527:
Thanks for this, love the double tap to wake feature. Also is editing the configuration file the only way to change settings? Or can I perhaps use something easier like Stweaks from the store?
[Nexus 7 (2013) Original Android Development] lpachuong:
Has the mult-touch issued been fixed or my screen protection solved it out :D?
[Nexus 7 (2013) Original Android Development] flar2:
I think Trickstermod can change the setting. Or reinstall the kernel and make a different selection.

I didn't make any changes to the kernel.
[Nexus 7 (2013) Original Android Development] lpachuong:
I'm currently on PAC 3.94 and using your kernel but somehow the multitouch screen bug disappeared. The other thing i did was to apply the extreme guard screen protection which i don't think it make any different. So really curious what solved the problem :)
[Nexus 7 (2013) Original Android Development] sgt. meow:
TricksterMOD works for changing dt2w.
[Nexus 7 (2013) Original Android Development] ktkr:
Has anyone tried this on the newly released pa 3.98? It's a mixture of jwr and jss build so I'd like to know if elementalx runs on that.
[Nexus 7 (2013) Original Android Development] sageDieu:
works great for me
[Nexus 7 (2013) Original Android Development] GoldElocks:
+1

Sent from my Nexus 7 Flo
[Nexus 7 (2013) Original Android Development] flar2:
Was there an OTA?

What are the changes?
[Nexus 7 (2013) Original Android Development] jlevy73:
Only reference I have seen for an update is this: http://www.androidcentral.com/android-43-jwr66y-security-update-landing-some-nexus-phones

Just looks like some security update. So far only the N4 has received it, nothing for N7 or N10 as of yet.
[Nexus 7 (2013) Original Android Development] sageDieu:
it was actually the build that came on the nexus 7, when you first open it up there are 2 ota updates you get. jss is the final one everyone is running but it has the random freezes, PA devs figured out that the initial build doesn't so they made a hybrid of both since there are not that many changes.
[Nexus 7 (2013) Original Android Development] ascar1s:
First, huge apologies for how out of date this post is. Just haven't gotten to even touch my tablet since then, but ... I tried flashing .10 with stock. And I soon noticed that when I scrolled in a forum of XDA app that threads would disappear as they scrolled (or, more accurately, they would white out, so to speak). I tried installing .8 tinking this might have to do with the newly added thermal stuff. Same thing. I tried but switched everything to stock levels (from the aroma defaults). Same thing. I reflashed stock kernel and the problem was gone.

So, should I try 1.0 or should I try bulletproof?
[Nexus 7 (2013) Original Android Development] ggreenwood334:
Gesture control in the play store supports this of running Franco kernel or other supported ones.
[Nexus 7 (2013) Original Android Development] Frostyeo:
Hey guys! Just flashed this kernel and it's super smooth :)

However, I tried to set the minimum frequency to 384, but when I look at system panel, the CPU seems to be always around 800-1000 even when there's like nothing using the CPU. This is on all the default options ticked in aroma when I was installing the kernel. Is this normal? And how much drain you guys get on standby? On stock with wifi I drain only 2% overnight (10 hours) , but now with wifi off somehow it drained like 4% in 6 hours standby ://
[Nexus 7 (2013) Original Android Development] mdamaged:
I can confirm that this is how I've successfully been dealing with it.

Incidentally, I have read here, something that leads me to believe that zaclimon may have figured it out with his kernel, or it's just sheer coincidence. Nevermind, the gentleman below and in the referenced post has confirmed the issue pops up again, sorry.
[Nexus 7 (2013) Original Android Development] nokiagye:
I install this kernel it worked fine with gamma for a while and after few days the bug pop up again.

---------- Post added at 03:53 PM ---------- Previous post was at 03:50 PM -----------------------New 5.1.1 optipop http://xdaforums.com/showthread.php?t=2958190
[Nexus 7 (2013) Original Android Development] mdamaged:
Thanks for the update. Luckily, I can live with it the way it is, leaving it alone for a few minutes after boot is worth this kernel's pros.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Yeap ☺ Never bothered me much either. It doesn't happen very often. I don't reboot my tab too much and everything else is smooth sailing ?
[Nexus 7 (2013) Original Android Development] poondog:
I can't find optipop in that link
[Nexus 7 (2013) Original Android Development] nokiagye:
Here is the link http://xdaforums.com/showthread.php?t=2958190

I don't know what was the other the same link
[Nexus 7 (2013) Original Android Development] adomol:
That link definitely provides an optiPOP, just not the one you were looking for!
[Nexus 7 (2013) Original Android Development] DroidIt!:
Thanks for sharing the pic, that IS a nice schoolbag. Wonder where I can pick that from? [emoji14]
[Nexus 7 (2013) Original Android Development] poondog:
maybe [MENTION=4795439]nokiagye[/MENTION] knows.. I have not researched much :P
[Nexus 7 (2013) Original Android Development] php5_developer:
No caf version?
[Nexus 7 (2013) Original Android Development] flar2:
I will get to it, I'm incredibly busy right now
[Nexus 7 (2013) Original Android Development] DroidIt!:
Yeah, shhhhh! Don't bother him, he's making his new app. Library rules are in effect till he finishes that. ?
[Nexus 7 (2013) Original Android Development] darkmage1991:
i wanted to go ahead and let you know, here is the usbreset.sh file that was linked in that Russian forum. i have not tried it i have only downloaded it and had it to use. if you dont mind posting on if it works or not? here are the instructions from that forum (note: these were translated from russian in google translate so its rough)

throw it in / system / bin / expose it right 0755 (for performance)
Ps from the archive do not forget to remove.

Next, set up an event in Tasker load over -> Script -> Run Shell
in the command string: usbreset / dev / bus / usb / 002/002
Chough root.
Hit digging to check if the first run, then allow Root Access application, exit, reboot, and voila ... the flash drive in place

now if you can actually speak russian and want the untranslated stuff here it is

Решил косяк старым добрым костылем usbreset, ...кидаем его в /system/bin/ выставляем на него права 0755 (на выполнение)
P.s из архива извлечь не забудьте.

Далее в таскере настроил событие Загрузка окончена -> Script -> Run Shell
в строка команды: usbreset /dev/bus/usb/002/002
галка root.
Жмем копку проверить, если первый запуск, то разрешаем рут-доступ приложению, выходим, перезагружаемся и вуаля...флешка на месте

В итоге после полной загрузки системы у нас выполняется скрипт, который ресетит(передергивает) хаб.
Отдельно флешку ресетить не помогает..
[Nexus 7 (2013) Original Android Development] Aerobatic:
Just my variant of manual interpreting. Sorry, do not use Tasker, thus may misinterpret terms back from ru.

Resolved the "glitch" using good old "crutch" usbreset ... drop it into /system/bin/ (do not forget to extract from archive), set permissions to 0755 (for execution)

Then in Tasker (net.dinglisch.android.taskerm) set up event action "Boot finished -> Script -> Run Shell" and type in command string:
usbreset /dev/bus/usb/002/002
check "root permission".
Push "Test" (or "Try"?) button, in case of 1st run allow root access per request. Exit, reboot and enjoy ... SD in place.

As a result, right after cold reboot we have USB-hub reset
Resetting single SD does not work.
[Nexus 7 (2013) Original Android Development] darkmage1991:
awesome that makes it alot more understandable. i didnt wanna try interpret for anyone as i didnt wanna screw something up =P
[Nexus 7 (2013) Original Android Development] Gorgtech:
Android 5.1.1 is here :D
[Nexus 7 (2013) Original Android Development] just lou:
4.00 is working fine with it so far.
[Nexus 7 (2013) Original Android Development] flar2:
Looks like there are a couple minor kernel changes for 5.1.1, I'll try to update ASAP. And do a CAF version too.
[Nexus 7 (2013) Original Android Development] mdamaged:
[MENTION=4684315]flar2[/MENTION] Regarding the gamma bug, where the screen can turn black and unresponsive, I realize this is a device issue, but it occurs to me that when I used francos kernel tool (before you made yours), the way his dealt with that bug, was to not apply gamma settings unless the screen was off. It is my belief that particular bug is triggered when gamma is applied while the screen is on. Just a thought. And as always, thanks for your work!
[Nexus 7 (2013) Original Android Development] DroidIt!:
I noticed with gamma tweaks off a full reboot that when I boot up and put my pattern in to unlock the device, I wait about 20 or 30 seconds for everything to boot and then I can see the gamma adjustment kick in. It seems as if I start playing with apps before the gamma adjust takes place, that's where I run into problems...my observations :)
[Nexus 7 (2013) Original Android Development] flar2:
I'll try something different with the color control in the new build.

Was there anything else I was supposed to do? I can't remember if I promised any other changes for the next version.
[Nexus 7 (2013) Original Android Development] mdamaged:
Sweet, thanks. FWIW, I came to this conclusion partly due to the fact that in his app, it states in the gamma section, "changes will not take effect until you turn the screen off then back on again".
[Nexus 7 (2013) Original Android Development] flar2:
I think it's the same on my kernel, this is faux's driver based on some code from LG. But I'll see what I can do.
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

A minor update for 5.1.1

I've changed the color control a bit, it is now built into the kernel and it's cleaned up a bit.

You actually have to turn the screen off, then on, then off, then on again to see the colors change.

If you set the color to apply on boot in the EX app, let the phone boot up and don't use it until the screen times out. Then turn it on. Otherwise the screen may become unresponsive. This seems to be a problem with my app trying to set the control bit. Unfortunately I can't update the existing EX app. I will try to get it working better with the new app when it is released, and add some color profiles too.

Download:

ElementalX-N7-4.01

ElementalX-N7-4.01-cm

Changes:

-update to 5.1.1 source

-clean up color control and build into kernel
[Nexus 7 (2013) Original Android Development] mdamaged:
Just flashed and booted, I did not let it go to blank screen before messing with it, gamma applied while screen was awake, yet no black screen, of course next time it may or may not work so well as the bug was not always a 100% chance of happening, but so far so good! Thanks.

N7 2013 flo, 5.1.1.

EDIT: Now when I open the app and look under graphics, the color palette (color control section) does not show up anymore, it's all grey (not a big deal for me at all fwiw).