yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] willverduzco:
[MENTION=4684315]flar2[/MENTION] - I'm absolutely loving 1.1, and I have been enjoying this kernel quite a bit from the start. As a side note, I gave a brief shout-out to this kernel on the XDA Portal when I wrote an article about the AROMA installer today.

Regarding the multi-touch issue upon crossing/nearing axis, I haven't noticed any change whatsoever between stock stock JSS15Q, JSS15Q + ElementalX 1.0, and JSS15Q + ElementalX 1.1. This tells me that the build's multi-touch filtering changes are responsible for the improved performance near/on axis, rather than the touch panel driver changes.

The problem can is best visualized by going to developer options and enabling Pointer location. Do this, and then keep track of the precision measurement. Normally, this is in the range of 0.10 to 0.25 with single through 10-point multi-touch--so long as no point crosses axis with another point. However, if you put your fingers on either the same x or the same y coordinate (i.e. cross any axis), the precision error goes up to over 1.0, depending on how on-axis they are. Luckily, the filtering has improved considerably such that it doesn't cause jumpy multi-touch gestures in most instances.

My personal real-world test is opening Reader+ and scrolling the left and right panes simultaneously. Before the filtering wasn't as strong and keeping a stationary left finger while the right finger crosses the horizontal axis of the left finger caused left panel jumpiness. Now, the jumpiness is reduced to a pixel or two, whereas before it was about 5-10 pixels. I'd say this is as good as it can get with an inherently flawed touch panel. I'd also say that this problem is so minor, especially now with the tweaked filtering, that we shouldn't worry about it unless it affects us in daily usage. The only time I can imagine this being a problem is with certain games. However, we're all rooted and should be using sixaxis anyway. :D
[Nexus 7 (2013) Original Android Development] jlevy73:
How right you are, just confirmed against 15Q stock and 15Q + 1.1 and precision using pointer location is identical. I used google maps as my real world and precision ranged between 0.10 and 0.30 unless I crossed the axis where it would jump over 1.0. That being said, I tried the same test with my HTC One and GS4 and both of those had precision between 0.25-0.40.
[Nexus 7 (2013) Original Android Development] Marck527:
Anyone know if over locking to 2.2ghz is stable? I m currently O'clcked at 2ghz with no problem.
[Nexus 7 (2013) Original Android Development] tiny4579:
Think about it for a second. It's 700mhz more than the normal max. And only you will know what stable overclocking levels are for your phone. It can vary and some might not be able to handle even 2.0 GHz. I'd personally say this is too high and only for the daring or tweakers.

Edited as I thought this was the HTC one which has a normal max of 1.7. The nexus 7 has a max of 1.5.
[Nexus 7 (2013) Original Android Development] bclark:
Is there a way to adjust hotplug settings? I'd love to be able to run dual core for normal activities and bump to the quad during intensive apps. I tried adjusting /sys/devices/system/cpu/possible but it doesn't stay
[Nexus 7 (2013) Original Android Development] flar2:
For normal activities it will rarely, if ever, use more than one or two cores.
[Nexus 7 (2013) Original Android Development] matrix.bharath:
Guys can we add Faux Audio on this kernel. can i install the app from the market will it work with this Kernel? can some one suggest.. any other volume increase hack?
[Nexus 7 (2013) Original Android Development] y3mita:
Giving faux a try... I've been getting random FCs on some apps with this kernel. I may be back to this on later versions.
[Nexus 7 (2013) Original Android Development] username8611:
Id like this too, I'm used to being able to customize hotplug settings on my n4, it'd be awesome to have it on the n7 too.
[Nexus 7 (2013) Original Android Development] tiny4579:
Force closes are almost never kernel related. Instead of blaming the kernel get some logs so others can investigate.
[Nexus 7 (2013) Original Android Development] Ankit Tulsian:
Even i am waiting for this. Hope flar2 adds this soon.
[Nexus 7 (2013) Original Android Development] railed:
Can I have some people list their preferred settings, I'd like to to see what everyone else is running.

Sent from my Nexus 7 (2013) with XDA Premium
[Nexus 7 (2013) Original Android Development] bclark:
Exactly, also it will allow us to limit some of the heat that causes the quick throttle.
[Nexus 7 (2013) Original Android Development] SupWiz17:
What ROM are you running because I'm getting a lot of FCs lately also.
[Nexus 7 (2013) Original Android Development] SupWiz17:
I dont have any logs right now so I'm not much help but the FCs stopped when I went back to 1.0 they all stopped. So its something with 1.1. I'm on the latest cm10.2 nightly but I plan on flashing psx 4.1 later tonight. I will let you know if it happens on that ROM.
[Nexus 7 (2013) Original Android Development] tiny4579:
I didn't have any issues on stock so it might not play well with that Rom. It's possible if it's a boot.img kernel and something is missing that exists in the cm ramdisk. [MENTION=4684315]flar2[/MENTION] did you pack the kernel here as boot.img or zimage? I don't have the ability to check it right now.

Then again if it were a ramdisk issue it'd happen on v1.0 as well.
[Nexus 7 (2013) Original Android Development] y3mita:
As you said "almost"

Kangabean JSS15Q

FCs stopped switching to Faux kernel.
[Nexus 7 (2013) Original Android Development] tiny4579:
How about the second part of my statement? Logs are nice. Logcat is ideal for force close issues.
[Nexus 7 (2013) Original Android Development] PizzaDroid:
same here
[Nexus 7 (2013) Original Android Development] alancai:
any kernel for f2fs please? thank you.
[Nexus 7 (2013) Original Android Development] flar2:
Sorry, it caused problems for others, so I had to remove that.
[Nexus 7 (2013) Original Android Development] flar2:
Does it work now?
[Nexus 7 (2013) Original Android Development] alancai:
So need to go back to ext4?
[Nexus 7 (2013) Original Android Development] Pkt_Lnt:
Yes, thank you.

Downloaded, rebooted to recovery, and installed.
[Nexus 7 (2013) Original Android Development] mageus:
I am using a Y-cable with external power. On an Nvidia Shield K1 , OTG+charge works correctly with this cable/power and peripherals (USB DAC and USB flash drive). On the Nexus 7 without OTG+charge, OTG works fine with the peripherals.
[Nexus 7 (2013) Original Android Development] Aerobatic:
So then I can only guess the problem is in the value of resisitor inside Y-cable. I have never had any problems with ElX of various versions in 2 different N7II with different OTG-cables and different active USB-HUBs (long time ago I decided for myself that Y-cables are unsafe and tricky, using different resistors for different devices and having no protection for overpower).
[Nexus 7 (2013) Original Android Development] manfio:
guys anyone know profiles to elemental x app to nexus7 flo? profiles to better performence and good battery life?
[Nexus 7 (2013) Original Android Development] DroidIt!:
Really I've never seen better performance than with ElementalX gov and preset values for everything else. The preset values have always worked great for gaming and keeping battery from draining. That said if you want a bit more performance without much more battery drain, I think going with Simple for CPU and ondemand for GPU is a good combo too. You don't need to change any of the other values, just switch the govs up. Well, that's been my observations over the years using ElX on the flo. :)
[Nexus 7 (2013) Original Android Development] machbret01:
I updated from 5.12 to 5.14 on cm version on my nexus 7 Flo and the auto rotate display orientation stopped working, it just stayed on portrait mode. So I back to 5.12 kernel version and I got working auto rotate mode fine again. Weird.
[Nexus 7 (2013) Original Android Development] flar2:
It was just a few minor security updates.

The sensors are not handled by the kernel anyway, definitely a userspace issue.
[Nexus 7 (2013) Original Android Development] litzer.rubicon:
For all people with OTG+charge problems, in the past I had problems with a 3 point cable... now I have a new one Y cable charging and connecting. So, maybe you need to get another cable.
[Nexus 7 (2013) Original Android Development] marsaltito:
Yes its cables they are bad !!! I bought 3 from difrent source and just one work !

I foun out best are
[Nexus 7 (2013) Original Android Development] MrHeaven:
Is this Kernel compatible with Samsung Galaxy S7 edge SM-935K? Did anyone successfully install with S7 edge?
[Nexus 7 (2013) Original Android Development] gyakusetsu1215:
This kernel is for the Nexus 7. You're in the wing section for your device, you need to be in the specific version forum of the S7 that you own.
[Nexus 7 (2013) Original Android Development] Aerobatic:
.... or just a usual OTG cable + active USB-HUB with external power.
[Nexus 7 (2013) Original Android Development] KoKoMaster:
Any one else having trouble with double tap to wake? It's not working for me on 5.14. Sweep2wake works though.
[Nexus 7 (2013) Original Android Development] Pkt_Lnt:
Not at all, it works fine for me. I use Pure Nexus that also supports dt2w and I had to disable it there so it would not interfere with ElementalX. Is it in your rom too?
[Nexus 7 (2013) Original Android Development] KoKoMaster:
No, I'm on stock Ota. The only option I changed during flash was battery saver and disable slide2sleep
[Nexus 7 (2013) Original Android Development] katsooba:
hi guys

i currently own 2 nexus 7 2013

one with a cm12.1 with the ElementalX 4.05 kernel

and one with the cm13 with the latest ElementalX kernel

i intend on using them as a USB audio source in my vehicles

my problem is as follows

the cm12.1 one works okay, sometimes it plays continuosly with no problems, but sometimes it cuts the audio off the USB, at first i suspected the USB DAC [Hifimediy Sabre USB DAC] but when the audio cut happened, i connected my NOTE 3 and audio works no problem, and on the CM12.1 not, only after a few minutes of dissconnection from the tablet it regains its audio.

on the CM13 tablet USB audio does not work at all [i use same settings for both tablets]

when i connect the USB audio to my sound processor it detects the diginal input, but once i hit play [no matter what player i use] it says audio FX has crashed, and digital signal is lost from the processor.

anyone know any fixes for the situations?

Thank you
[Nexus 7 (2013) Original Android Development] beren:
semi ot:

anyone can suggest a otg+power cable with an L connector?...or any other good idea to not have a long connector coming out from the tablet (for car installation)
[Nexus 7 (2013) Original Android Development] KoKoMaster:
Looks like kernel was not fully installed due to low system space. I removed all the built in keyboards to free up space. Everything is working now.
[Nexus 7 (2013) Original Android Development] tni.andro:
elementalx.sh not executed

How is elementalx.sh supposed to get triggered?

I'm using Dirty Unicorns (DU_flo_6.0.1_20160610-1542.v10.3). ElementalX-N7-5.14 seems to install properly. /sbin/elementalx.sh and /system/etc/elementalx.conf exist. A /init.elementalx.rc is there as well and has a service definition for elementalx.sh.

However, elementalx.sh is not executed during/after boot. If I invoke it manually from a command line, it works and properly applies settings.
[Nexus 7 (2013) Original Android Development] Hatshipuh:
To enable f2fs again, is it enough to uncomment the two entries in edit_ramdisk.sh?

Tap-a-talked from my Nexus 7
[Nexus 7 (2013) Original Android Development] nigelhealy:
Yes. I do it often. Warning , I'd you do it wrong it reformats to ext4 so be careful in dirty flashing.
[Nexus 7 (2013) Original Android Development] tni.andro:
I was looking through the installer. The edit_ramdisk.sh script is using sed to insert 'import /init.elementalx.rc' after 'import init.trace.rc' in init.rc. 'import init.trace.rc' doesn't exist in the DU init.rc, so the elemx import isn't added.
[Nexus 7 (2013) Original Android Development] Hatshipuh:
I uncommented it, but got stuck on boot logo. When I flashed the one edited by you it booted without problems. All I did was removing the #. When compared side by side the edit_ramdisk.sh was the same as in your version.
[Nexus 7 (2013) Original Android Development] nigelhealy:
You might not have edited it. If you open a zip, open a file but in the zip it extracts to a temporary file which you saved and not saved in the zip? Open the zip again and see if your edit is there. I save as the edited file and then add it back to replace and then open the zip again to be sure.
[Nexus 7 (2013) Original Android Development] Hatshipuh:
Yeah it was saved correctly. After editing and saving, I opened it from the zip again to compare.

Tap-a-talked from my Nexus 7
[Nexus 7 (2013) Original Android Development] nigelhealy:
Upload / share it and I'll take a look. I've been editing many times just fine. If you did actually save in the Zip then the other options is you somehow managed to remove executable bit, or its a DOS vs Unix LF / CRLF type conversion on your computer. I only edit on Linux machines personally to avoid any such issues.
[Nexus 7 (2013) Original Android Development] Hatshipuh:
I'll share it in Pm, don't want anyone here who skip the reading, download it and complain about bootloops lol.
[Nexus 7 (2013) Original Android Development] nigelhealy:
So I got it from you via PM and I can't spot what happened in your edit, so its just weird. However I am on N7 f2fs on 5.14 and its booted fine. I attach here as working. If anyone wants me to edit the CM version shout out.

I just open the zip, open that file, remove those 4 #, save-as to a folder, and then add it back to the zip, close the zip, open the zip, open that file and check its edited, all done on a Linux system.

Given your edit looks fine, I'm thinking it isn't your edit but some other reason.

View attachment ElementalX-N7-5.14-f2fs.zip
[Nexus 7 (2013) Original Android Development] Hatshipuh:
I did the same, but on a Windows machine, maybe that made a difference though it's still weird. Your version worked without a hitch. Thanks!

Tap-a-talked from my Nexus 5
[Nexus 7 (2013) Original Android Development] Phoenix09:
maybe your editor put Windows line endings
[Nexus 7 (2013) Original Android Development] nigelhealy:
I spotted it! Yes its you using a Windoze machine you used a text editor which used DOS CR-LF. When I use Linux vi command rather than the gui text editor you can see it. Screenshot you see your edit with ^M LF not in my edit. Use a different editor than you used which doesn't insert DOS LF.
[Nexus 7 (2013) Original Android Development] Pkt_Lnt:
This text editor works correctly in Windows. Notepad++

https://notepad-plus-plus.org/
[Nexus 7 (2013) Original Android Development] Hatshipuh:
That explains everything! Tried editing again myself and it's working now, thank you!
[Nexus 7 (2013) Original Android Development] flar2:
Stupid Windows.

I have to use it at work, but our home has been Windows and Apple free for over 10 years. The only install of Windows is on an old Acer laptop from about 2008, and even this dual boots Ubuntu, with Ubuntu as default.
[Nexus 7 (2013) Original Android Development] marsaltito:
My home free of MS an OsX last 15 years work last 5 ( so im lucky one) :)

N7(flo),N5X CM
[Nexus 7 (2013) Original Android Development] DroidIt!:
Lol, I do all 3. Win for gaming, OSx for work/school stuffs and Linux for play. Nice thing is add Android in and I always get to play with something. Call me a masochist but I like updating stuff for some reason lol :)
[Nexus 7 (2013) Original Android Development] BS86:
We can decide if we want to use Linux or windows at work ;) so yes, Windowsfree at work since 3 years, Windowsfree at home since 2 years (gaming works surprisingly well on Linux thanks to Steam and PlayOnLinux)

Never had any bitten product, so yeah, Mac free since birth :P
[Nexus 7 (2013) Original Android Development] flar2:
Thanks, this code falls under the GPL, so we can try it out.
[Nexus 7 (2013) Original Android Development] flar2:
Actually, maybe you could post your build here for others to test first. I'm going ahead with the usual security update today.
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

July security update

Do not install on earlier ROM builds or wifi may not work!

Download

ElementalX-N7-5.15

ElementalX-N7-5.15-cm

Changes:

-July security update
[Nexus 7 (2013) Original Android Development] Natakranta:
EX 5.15 running fine with Pure Nexus Mod July security patch build. WiFi is working. Posting from it now.

Thanks [MENTION=4684315]flar2[/MENTION]!
[Nexus 7 (2013) Original Android Development] CPGOD:
[MENTION=7366301]solidxsnake13224[/MENTION] [MENTION=4684315]flar2[/MENTION] for the noobs/lazies amongst us, whats the easiest way for me to get this onto stock 6.0.1 with existing 5.15 ElementalX?

Or did you get chance to do a beta now the security patches are done ? ;)
[Nexus 7 (2013) Original Android Development] CZ Eddie:
The Timur USB driver implementation would be outstanding.

Please count me as another who would like to see it added if possible!
[Nexus 7 (2013) Original Android Development] HdSht:
Hi guys, I was checking some things with kernel adiutor when i noticed a setting called Multicore Power Saving(under CPU tab) set to disabled (while on stock kernel was set on aggressive). Was that disabled on purpose ? I've tried to look for the answer in the thread but without luck.

Thanks in advance.
[Nexus 7 (2013) Original Android Development] 53l3c7a:
I hope this is okay, feel free to delete. SHAMELESS O/T PLUG: I made a song a ways back, and named it Elemental after this kernel (sort of). I've used it on two devices, and I've always liked the name. Hope you like it :) https://soundcloud.com/pete-robel/elemental
[Nexus 7 (2013) Original Android Development] solidxsnake13224:
Sorry for the delay! Here's a build of the latest source of EX 5.15 with my port of Timur's USB driver. This is UNTESTED and I don't know if it works, so use at your own risk, but I don't see any reason why it shouldn't work. I believe I've modified the installer to handle everything correctly, but in case it doesn't work, you can change fixed installation mode and fastcharge mode through shell commands in sysfs:

Type the following as root in a terminal to enable fast charge:
echo 1 > /sys/kernel/usbhost/usbhost_fastcharge_in_host_mode

Type the following as root in a terminal to disable fast charge:
echo 0 > /sys/kernel/usbhost/usbhost_fastcharge_in_host_mode

Type the following as root in a terminal to enable fixed-installation mode:
echo 1 > /sys/kernel/usbhost/usbhost_fixed_install_mode

Type the following as root in a terminal to disable fixed-installation mode:
echo 0 > /sys/kernel/usbhost/usbhost_fixed_install_mode

I'll put up another build with EX-4.05 with the driver as well when I get to it (but I imagine that's less in demand since a lot of people are probably running MM by now). I'm still running LP, so I haven't tested this build, but I'd expect it to work. Good luck!
[Nexus 7 (2013) Original Android Development] CPGOD:
Thanks - will give this a go tonight

EDIT - ok managed a quick trial while at work.

Not looking good - installer worked ok, but bootlooping (and seriously slow boot anims)

I'd just applied over my existing CM13 nightly.

Going to try wipe and reinstall

I
[Nexus 7 (2013) Original Android Development] CPGOD:
Nope - did a wipe and update, but still no good - there's some runaway CPU somewhere; device gets very hot.

(Im assuming your update is OK for CM on Deb?)

Tell me what I need to do to help provide diagnostics/logs ?
[Nexus 7 (2013) Original Android Development] solidxsnake13224:
I'm running SlimLP with a the modded version of EX 4.05, so I haven't tested this build... That said, since this is the AOSP build of EX (and not the CM build), I imagine that's probably the issue. When I get a chance, I'll try building the -cm version and posting it up. In the meantime, if you have a backup and wouldn't mind doing some testing, could you try the build I posted earlier with an AOSP Marshmallow ROM? No biggie if you can't, but I'm sure it could help others out there :)
[Nexus 7 (2013) Original Android Development] CZ Eddie:
Great, thank you!

I installed it just fine on AOSP based 6.01 Pure Nexus ROM.

No issues.

Haven't had a chance to test the additional functionality you provided but I'll try to do this tomorrow!
[Nexus 7 (2013) Original Android Development] CZ Eddie:
[MENTION=7366301]solidxsnake13224[/MENTION] is there anything in particular you'd like for me to test with your T1mur patch & Elemental?

My 6.01 PureNexus ROM + your kernel boots fine.

I attached my USB-OTG Y-cable and 2000 MaH charger.

I got something like 800mAH charging.

The other end of the USB-OTG is connected to my USB 2.0 5V powered hub to my 500GB platter hard drive. The N7 is able to browse the drive contents.

I rebooted the N7 and when it came back up the power was charging again automatically. I think that was the major issue/reason for the patch?
[Nexus 7 (2013) Original Android Development] solidxsnake13224:
In addition to the power on, USB devices seem to be detected much more reliably now (at least on my end). I still use my Tasker scripts to reset the USB driver on power-up, but it's not entirely necessary as far as I can tell.

The one other thing that this fixes is deep sleep. When I was using the semi-fixed version of ElementalX that flar2 posted a while back, the USB driver would keep a wake lock when in OTG mode (even if power was removed). The only way to get it to go to deep sleep would be to disconnect the USB cable from the back, which isn't feasible for a fixed-installation like mine. With this new version, simply cutting power will disable OTG mode, and the USB driver won't hold any wake locks, which allows the tablet to enter deep sleep.
[Nexus 7 (2013) Original Android Development] CZ Eddie:
Hey, come to think of it, when I pulled the USB charger cord from the Y-Cable, I did notice the USB-OTG devices all shut off their "connection" LED's on the USB Hub. It's the LED that indicates when they are communicating with the host device.

Good work!

---------- Post added at 06:48 PM ---------- Previous post was at 06:29 PM ----------

I wonder if it is possible to put a 30 second delay on shutting of USB-OTG communication though, or if that is even necessary?

Just to allow the connection to survive when someone is listening to music with ACC on but engine off, and then starting up the engine.

---------- Post added at 06:58 PM ---------- Previous post was at 06:48 PM ----------

Just bought the ElementalX kernel manager at the PlayStore. I like the direction this kernel is headed. :) :good:
[Nexus 7 (2013) Original Android Development] g-one-ger:
can u share your tasker script to reset the usb connections? after every reboot i have to scan my card than my media again in poweramp