yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Axel85:
OK, perfect, I clean installed 2 days ago with last cm13 nightly+ 5.08 kernel. I will clean install another time ,but I can't understand where those errors came from because I ve done everything in the right way
[Nexus 7 (2013) Original Android Development] drlenny:
FWIW, I couldn't successfully flash anything but a base ROM on twrp 3 official, I had to go back to 2.8.7.0 and like magic everything worked again. I've run latest nightly cm and crdroid with open gapps, ex 5.09, and SuperSU with no problems.
[Nexus 7 (2013) Original Android Development] EisDave:
Nobody had the same problems and was able to fix it? :(
[Nexus 7 (2013) Original Android Development] Arthur4ik:
Would you recommend Pure Nexus over CM13? Which is the most simple with good battery life?
[Nexus 7 (2013) Original Android Development] marsaltito:
Im on CM13 and never installed supersu , there is one that is with CM .

Everything works !
[Nexus 7 (2013) Original Android Development] Anta:
[MENTION=4684315]flar2[/MENTION]: any chance to have the DVB modules and easycap modules compiled by you?
[Nexus 7 (2013) Original Android Development] lynxetto:
The OTG charge mode did not work after rebooting the Nexus 7, if it's pluged the whole time to the OTG charge cable (doesn't charge, until reconnection). This is a big problem for the fixed installation in my car, because it is not easy to dis- and reconnect the OTG cable. Also USB devices are not found, if the power of the car is shutted down and the USB devices turned off. When I start the car again the Nexus 7 doesn't search for USB devices, so they didn't work until I reconnet the Nexus.

I hope you can help me with my problems

Thanks
[Nexus 7 (2013) Original Android Development] studiorat:
Any issues reported with Android Pay and this kernel regardless of Rom

---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------

PersonallyI have been a daily driver on Pure Nexus for a few months and its my go to ROM as I am constantly changing and flashing things .....but always come back....the dev is awesome!
[Nexus 7 (2013) Original Android Development] lynxetto:
The OTG charge mode did not work after rebooting the Nexus 7, if it's pluged the whole time to the OTG charge cable (doesn't charge, until reconnection). This is a big problem for the fixed installation in my car, because it is not easy to dis- and reconnect the OTG cable. Instead, the USB peripheral devices are found, and the USB devices turned on.

I have elementalx Stock/AOSP (Android 6.0.1) ElementalX-N7-5.09

I hope you can help me with my problems

Thanks
[Nexus 7 (2013) Original Android Development] solidxsnake13224:
Regarding USB devices, try this. It works for me.

For me, OTG charge works fine on the stock EX kernel, HOWEVER it doesn't look like it's charging (the charging icon doesn't change and the tablet doesn't think it's charging). The problem is in bq27541_battery.c. I've recompiled the kernel (for v4.05, since I'm running SlimLP on my Nexus 7), and now the tablet recognizes it's charging.

flar2: The fix is in the following lines in bq27541_battery.c (around 609 in the EX-4.00 branch):

Change:

val->intval = bq27541_device->bat_vol;
}
BAT_NOTICE("voltage_now= %u uV\n", val->intval);
}
if (psp == POWER_SUPPLY_PROP_STATUS) {
ret = bq27541_device->bat_status = rt_value;

if ((ac_on || usb_on || wireless_on) && !otg_on) {/* Charging detected */
if (bq27541_device->old_capacity == 100) {
val->intval = POWER_SUPPLY_STATUS_FULL;
} else {
val->intval = POWER_SUPPLY_STATUS_CHARGING;
}
} else if (ret & BATT_STS_SOCF) { /* Fully Discharged detected */

to:

val->intval = bq27541_device->bat_vol;
}
BAT_NOTICE("voltage_now= %u uV\n", val->intval);
}
if (psp == POWER_SUPPLY_PROP_STATUS) {
ret = bq27541_device->bat_status = rt_value;

//otg+charge - allow charging while otg
if ((ac_on || usb_on || wireless_on)/* && !otg_on*/) {/* Charging detected */
if (bq27541_device->old_capacity == 100) {
val->intval = POWER_SUPPLY_STATUS_FULL;
} else {
val->intval = POWER_SUPPLY_STATUS_CHARGING;
}
} else if (ret & BATT_STS_SOCF) { /* Fully Discharged detected */

Easy fix that will help a LOT of N7 users making a fixed-installation setup. With this fix, the tablet recognizes it's charging, which allows users to set up e.g. Tasker profiles based on power status.
[Nexus 7 (2013) Original Android Development] steeven01:
I hope flar2 can add this fix in his next release it would be very helpful to all with a fixed car install.
[Nexus 7 (2013) Original Android Development] lynxetto:
Thanks for the reply.

I have a Nexus 7 2013 with wifi flo version of Android 6.0.1.

I installed the Nexus Root Toolkit v2.1.4 kernel and elementalx Stock / AOSP (Android 6.0.1) ElementalX-N7-5.09.

I have this configuration.

Can you tell me what steps I have to perform and which version to install with any links?

thank you
[Nexus 7 (2013) Original Android Development] solidxsnake13224:
You need to build the kernel from sources to fix the charging indication in OTG+Charging mode, or wait for flar2 to implement the fix into the kernel. It's a very simple change in the code, but you need to rebuild the entire kernel from scratch to implement it.
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

Update to test OTG+charge fix from [MENTION=7366301]solidxsnake13224[/MENTION]

Many thanks for someone finally fixing that. I don't know if this is a complete fix or not. I have not had time to test it, so I'm not pushing this out to the app yet, please try this out whether you use OTG+charge mode or not, just to make sure everything is good. Then I'll make a full release.

I also didn't include the latest security update, it will be easier if I just wait and merge Google's changes all at once next week. The update is not urgent as long as you are just using apps from the Play Store. I honestly wouldn't be using apps from outside the Play Store anyway, unless you really trust the developer.

Download

ElementalX-N7-5.10

Changes:

-OTG+charge fix (thanks [MENTION=7366301]solidxsnake13224[/MENTION])

-update installer
[Nexus 7 (2013) Original Android Development] lynxetto:
I tested the version 5.10 but I have the same problem . after turning on the tablet are recognized through the usb cable otg y but the phone does not appear on the charge icon.only after disconnecting the cable otg charge and reconnected to the tablet charging and USB are functioning. the problem remains. Thanks
[Nexus 7 (2013) Original Android Development] EisDave:
Thanks for the fix, i will also test it today, but do you have any ideas for my stereo sound problem with USB DACs, witch I posted 1-2 sites earlier.
[Nexus 7 (2013) Original Android Development] lynxetto:
I saw that when I turn on the tablet, the charging icon does not appear, but the percentage of the charge increases, the tablet charge.

I have ElementalX-N7-5.10
[Nexus 7 (2013) Original Android Development] katsooba:
Can this somehow be implemented to a cm12.1 kernel?
[Nexus 7 (2013) Original Android Development] steeven01:
It worked once strangely. But otherwise it's not working for me tablet boots up from off state and doesn't see that it's being charged.

My nexus 7 car install doesn't have the internal battery I'm using a buck converter to power it but I was hoping to use charging as a way to turn it off when I turn the ignition off.

I will try a clean install to see if that makes any difference.
[Nexus 7 (2013) Original Android Development] studiorat:
This Kernel for me is kinda Bleh!... It did not play well with my particular Nexus 6
[Nexus 7 (2013) Original Android Development] flar2:
There is no such thing as not playing well with your device. The hardware is the hardware and the code is the code. Elementalx is always stable and problem-free. Any issues are caused by user error. And this is a Nexus 7, which is entirely different than a Nexus 6.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Agreed :) It's either user error or a hardware problem. I've lost count of the number of devices, versions, ElX flashings and everything else I flash along with ElX. Between ALL the roms, manufacturers, xposed's etc. etc. I've never had a problem with EX. Maybe a VERY occasional app bug, but fixed usually the next day, and I haven't even seen one of those in quite awhile. I would go back to a clean slate. Clean flash ROM, gapps, ElX and nothing else. Wait two or so days before putting apps on to see if you still have issues....not you [MENTION=4684315]flar2[/MENTION] the poster :) If issues persist go stock. If issues, it's hardware. If you do OK, slowly add apps back in and see what doesn't work or look at your settings. Now I'm not bashing, just what I'd do. I've flashed EX on too many devices for too long to believe it's EX as flar said. ;)
[Nexus 7 (2013) Original Android Development] studiorat:
Uhmmmm, Yeah!!!!! Ok Cool for you maybe!!! But Thanks, It obvious they are different devices, I was merely stating my opinion This Kernel for my device doesn't interact well with my N6 It didn't seem to add any kind of anything or speed despite the OC and my Benchmarks were lower with it when compared to my stock scores , we can argue semantics all day but ya know I just don't care all that much, It's lovely your condescending tone how ever it's always user error, doesn't seem logical because the same Kernel on some other device may be fine, and issue free, I have Elemental on my Tablet and it's fine , I have it on my N7 and it's OK too I have Elemental for N6 on my N6 and it's not performing as expected or as hyped by others enough said!

I don't feel it's necessary to argue or post how it's user error to take the blame off the Dev, It's not his or her fault, it's just the way it reacts to my phone and apps.....No wonder I barely come here, Call me confrontational call it what you will But who are you to tell me that it's my fault when I have the same devs Kernel across 3 devices for said devices and all is well but my N6 to me it's just simple My device doesn't operate properly with Kernel, FC and Lag so why bother .....Just use the ROMS Kernel it's problem solved!
[Nexus 7 (2013) Original Android Development] DroidIt!:
:) As an example, I flash EX on Nexus and HTC devices. But what I do for a procedure is I ALWAYS clean flash, that just eliminates a lot of possible issues. So, just go to twrp and wipe all except internal storage. Then I flash my ROM, latest nano open gapps, EX, systemless su binaries (I believe 2.67 is the latest), flar's permissive kernel hack, and xposed. Wipe cache/dalvic and reboot. Once I get the EX app on, I leave all the settings stock minus playing with screen colors and maybe vibration (if applicable). I've not had any instability or battery or performance issues in quite some time. Now that's the procedure I've used with EX on the N5, N6, N7, N6p, N5x, and the HTC One M9 and works good on all, so I'd suggest to try going a similar route and see how it works. ;)

---------- Post added at 04:13 PM ---------- Previous post was at 04:06 PM ----------

That was a little over the top :) Not responding angrily or arguing here, but it probably is user error. Android, ROMs and kernels change over time. Some things I did only a year ago, including apps I used to use, some don't work properly any more. I've had to adjust my procedures and apps I use with the times is all. I've been on EX on my N6 since flar started making kernels for the N6 and have only ever had a minor issue here or there, but probably nothing in the last 6 or 8 months. :) Don't be so quick to switch away, try to think up a way to change up what you do a bit. By investigating what your issue is, you'll likely find an app that hasn't been coded right/updated that you'd probably be better off without using anyways. Look for alternatives. Well, that's my suggestion. Stay with EX and try to figure why your setup isn't working good with EX. I think you'll be better off for it in the long run. ;)
[Nexus 7 (2013) Original Android Development] BS86:
if you really flashed this kernel on an N6, it is clear that it does not work well (I wonder if a N7 kernel might even boot on a N6 ... )
[Nexus 7 (2013) Original Android Development] roofrider:
Lol, you use his kernel on 3 of your devices and still come here and complain about it without providing logs or trying to debug it yourself. Why are you even posting your N6 problems in an N7 thread? Besides, you don't make any sense. Just because you have flar's kernel on 3 different devices with different ROMs and apps installed, you expect it all to function the same? LOL. (Oh, I don't mean to say flar's kernels are flawed for some devices; not at all!)

Wait, I hope you are not trying to flash this N7 kernel on your N6 and whatnot.
[Nexus 7 (2013) Original Android Development] flar2:
No, your post was pointless except to troll me.
[Nexus 7 (2013) Original Android Development] njgalaxy:
so i have a noob question: if i flash this kernel over my stock 6.0.1 rom, will i be able to use otg adapter to both transfer data and charge the tablet at the same time (using y-adapter or otherwise)?

i need the otg function to make the nexus 7 act as host for backup camera. so perhaps i'll connect a usb hub to the otg, and all this will be inaccessible once i install in the car.

thanks in advance
[Nexus 7 (2013) Original Android Development] quickdraw86:
USB OTG+charge is listed as a feature in the OP. I've never used that feature, and you should probably try it to make sure it works to your expectations prior to sealing the tablet, cables, and components of your setup into your car's dashboard/wherever.
[Nexus 7 (2013) Original Android Development] njgalaxy:
yeah, i saw the OP was gracious enough to continue posting and providing support.

that's why i wanted to ask here before flashing the kernel. if the feature is buggy, and i have to unplug otg each time the tablet reboots, that won't be very practical for me.

wish google baked in this feature directly :(
[Nexus 7 (2013) Original Android Development] flar2:
There is another kernel that has this feature fully working, but I think you have to pay for it.

The OTG+charge is something I worked on a long time ago, and it worked for my needs, but doesn't work well for permanent installations. Lots of people have asked for a fix, but the problem is at this point I don't have the time to work on it. It's one of those development things that will take quite a bit of time, because I have to find all my cables and test many setups and scenarios and reboot many times to test changes. Plus I've completely forgotten how the usb driver works, so I'd have to read through tons of code to get back up to speed.
[Nexus 7 (2013) Original Android Development] njgalaxy:
thanks for replying. that's what i was trying to find out, if there were any recent developments.

i know timur's kernel has that feature, but i'd prefer if i didn't have to shell out $25 for it while the tablet itself cost me $30 (craigslist!) :D

any idea if wireless charging plus otg will work at the same time? i can test that on stock when i get back home later today.
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

Minor changes for the April security update.

Download

ElementalX-N7-5.11

ElementalX-N7-5.11-cm

Changes:

-April security update

-update installer
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Thanks flar for your continued support for Flo...
[Nexus 7 (2013) Original Android Development] Aerobatic:
TY, [MENTION=4684315]flar2[/MENTION].

I assume code changes from experimental 5.10 included?
[Nexus 7 (2013) Original Android Development] flar2:
Yes
[Nexus 7 (2013) Original Android Development] magnamentis:
i'm using EX on my N6 and it interacts absolutely great as it always did on all devices i'm using that kernel and i recommend to troubleshoot and/or provide logs if you really think it's kernel side (which it's not) but then there is no reason to post this anyways, just change the kernel.

i'm posting this because for all really interested and "readers" it's obvious that this is the most stable and hasslefree kernel around. other perform well too but none has so few issues and then experience shows that it's mostly the setup or other user space issues that could couse trouble.

EDIT: and it's definitely the wrong thread to have any positive impact for others, so one has to assume it's a form of venting frustration to post such statements in other threads.

if there are issues you should post this in N7 thread with LOGs
[Nexus 7 (2013) Original Android Development] DaveImagery:
Thank you flar, for your continued awesomeness.

Anybody know why Google yanked the April image from the developers site?
[Nexus 7 (2013) Original Android Development] quickdraw86:
You posted this same question elsewhere, and the answer is that no one really knows, as Google never offered an explanation. The pull included factory images for fugu, volantis, and possibly others that all share that same version number with flo's April factory image.
[Nexus 7 (2013) Original Android Development] DaveImagery:
Yes I know I posted it elsewhere. ARREST ME!!
[Nexus 7 (2013) Original Android Development] alancai:
Any f2fs kernel please?
[Nexus 7 (2013) Original Android Development] nigelhealy:
Attached is the non-CM one. I edited the edit_ramdisk.sh to uncomment Flar's commented out of F2FS. I'm using this one myself. Attached are screenshots showing the kernel version and the filesystems are f2fs for /system and /data.

I can't attach both CM and non-CM so my next reply will be the CM one which I'm NOT using so its not tested.

[/ATTACH]
[Nexus 7 (2013) Original Android Development] nigelhealy:
This is the CM version, I don't run CM so this is

not tested

. It has edit_ramdisk.sh edited to uncomment Flar's commented out of F2FS.
[Nexus 7 (2013) Original Android Development] Steffen_2009:
Is Cifs (now?) possible with ElementalX kernel 5.11?

Or is there no way to get Cifs under Marsmallow?
[Nexus 7 (2013) Original Android Development] nigelhealy:
CIFS as in Windows shares?

You can use an app for that like ES File Explorer.
[Nexus 7 (2013) Original Android Development] Steffen_2009:
No, I mean integrated CIFS support inside the kernel. Giving us the functionality using mountpoints in all apps with access to Android file system.

Not just apps like ES file explorer which are specially coded for that.

It was integrated in ElementalX 2.15, then we had something like an android issue. I don't know if the functionality was possible in any later release in ElementalX kernel.

Does anyone know if integrated CIFS is possible , is there a chance to get this again?
[Nexus 7 (2013) Original Android Development] flar2:
The newer Android security model doesn't allow it to work, AFAIK.
[Nexus 7 (2013) Original Android Development] Steffen_2009:
Hhm, well so with the new Android security model we won't get any integrated CIFS support inside any kernel? Does someone know if we really have this hard limitation now?

Thanks very much for your answer flar2, I'll stay on your KitKat ElementalX kernel then. A working Cifs integration is essential for me... [emoji4]
[Nexus 7 (2013) Original Android Development] flar2:
Adding support to the kernel is easy, it's user space (Android) that makes it difficult/impossible to use
[Nexus 7 (2013) Original Android Development] Gen5:
Is this kernel based on stock?
[Nexus 7 (2013) Original Android Development] quickdraw86:
required reading
[Nexus 7 (2013) Original Android Development] lynxetto:
I have the elementalx version 5.10 with Nexus 7, 2013 android 6.0.1. I have this configuration: tablet + OTG cable + cable y + hub usb amazon 4 usb. I have the problem with the usb. It is not recognized if I turn off the 'power. the usb is recognized only when I turn on the tablet or only when removing and refitting the OTG cable. How can I fix the problem? conf= OTG + charge = 1 .

if I enter OTG + charge = 0 hub usb working properly but will not accept charge.
[Nexus 7 (2013) Original Android Development] keepcalmrollon:
Anyone tried flashing this on MOB30D yet (flo)?
[Nexus 7 (2013) Original Android Development] Cryptecks:
Flashed 5.11 on OMJ's Stock Rooted which is updated for April and everything is working quite well.
[Nexus 7 (2013) Original Android Development] just lou:
Same here.
[Nexus 7 (2013) Original Android Development] flar2:
There weren't any kernel changes in MOB30D
[Nexus 7 (2013) Original Android Development] d1dd1:
Same issue here with 5.11 ((CM)

USB OTG Charging works after unplugging and replugging the charging cable on the y adapter after bootup, but not directly after boot.

Is it possible to add USB OTG+Charge directly after booting (tablet is in the car and so always connected to hub and charger)
[Nexus 7 (2013) Original Android Development] goto35:
OK totally overwhelming. So i just got a 2013 nexus 7 for the proposes of putting in the car. Biggest thing i want is the power off with engine off and power on with engine on.

So how do i install this kernal? I just have a stock nexus 7 2013 right now.
[Nexus 7 (2013) Original Android Development] Jonnyredcorn:
I've been waking up to my tablet being turned off. I'm running PureNexus and latest elementalX. I had to hold down the power button to reset the device as if it was still on though. Here is my last_kmsg

https://www.dropbox.com/s/getmrz2wzxa32g7/last_kmsg.txt?dl=0
[Nexus 7 (2013) Original Android Development] solidxsnake13224:
Yeah, that was the functionality I had after my previous fix. I did some more tweaking, and I think I've come up with a full fix. Now my fixed-install N7 in my car dash will wake on with power (oem off-mode-charge is turned off in fastboot), and it will recognize as charging while there's power, and not when there's no power. I've uploaded the relevant changes to my GitHub.

This should be functionally working. Next steps to get everything working best would be to force a reset of the USB controller on power loss/restore. I'm currently handling this with a simple Tasker script and the "usbreset" fix, but doing this in-kernel would be considerably nicer. In essence, this is necessary because currently, the msm_otg driver breaks when +5V is lost but the ID pin is still grounded. With a "fixed-installation" flag, the driver could be re-written to switch to a regular idle state (either in host or not host mode, doesn't really matter for a fixed install) when it loses +5V, and enters OTG mode again when +5V is restored. Just more than I feel like dealing with since this works fine for me :p
[Nexus 7 (2013) Original Android Development] htb2050:
The kernel Hz change from 100 to 300hz in various newer Nexus devices, could you please make a test kernel for Nexus 7 with that change too? Or would it not matter for the n7?
[Nexus 7 (2013) Original Android Development] flar2:
It might help, we'll see if Google changes it in the next update. They did it for 6P and 5X in March, then 6 and 9 in April. If not maybe I will.
[Nexus 7 (2013) Original Android Development] akylepsg09:
hi.. before flashing the custom kernel of yours do i need to wipe or just flash it w/o wiping im using stock rom 6.0.1
[Nexus 7 (2013) Original Android Development] flar2:
Just flash
[Nexus 7 (2013) Original Android Development] krapcius:
Hi, I have a problem with kernal elementalx Cyanogenmod/CAF (Android 6.0.1)ElementalX-N7-5.11-cm

I have rooted nexsus 7, i install that kernal via recovery app than reboot. starts very very slow. that color spots moving so slow that it looks like it will stop vorking. after few mins there shows up ANDROID and then black screen. i see that is lighted (its working but there no action) i tried to get back to bootloader, i can do this. but waht s the problem? my android vertion MMB29Q.

Can someone help me?
[Nexus 7 (2013) Original Android Development] DroidIt!:
Sounds like you flashed the wrong version...as in if the ROM is AOSP you need to flash that version and if a CM ROM flash flar's caf kernel. Try downloading and flashing whichever version you don't have AOSP or caf. It'll do everything you describe if you flash the wrong one. ;)