yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] krapcius:
And how do i know that s my vertion? just try another? one more question. I did n pushted ROM it s original . is it a problem?

---------- Post added at 04:19 PM ---------- Previous post was at 03:22 PM ----------

Thanks, it worked. just flushted other vertion :)
[Nexus 7 (2013) Original Android Development] DroidIt!:
Yep :) Figured that was the issue. Done that myself a couple times on accident ;)
[Nexus 7 (2013) Original Android Development] krapcius:
One more problem, i can't flush any rom it starts and ends with error 255. what dose it mean?

Then i strated my recovery and it the same error 255
[Nexus 7 (2013) Original Android Development] xMayonnaise:
I can't install Xposed framework to this kernel. Is it not compatible?

I can't install Xposed framework to this kernel. Is it not compatible?
[Nexus 7 (2013) Original Android Development] Hatshipuh:
No problems with xposed.

Tap-a-talked from my Nexus 7
[Nexus 7 (2013) Original Android Development] xMayonnaise:
Thanks for replying.

My Nexus 7 2013 was running on MM 6.0.1 using this kernel when I flash Xposed framework (xposed-v83-sdk23-arm.zip), I get an error message. But using the stock kernel (after I flash-all.bat from factory image), I could flash Xposed framework without a problem. So I guess, the version of this kernel for MM is not compatible as of now.
[Nexus 7 (2013) Original Android Development] Hatshipuh:
I'm posting from latest 6.0.1 running latest version of this kernel with Xposed, v83 worked, updated recently to v83 and it's working too. Nothing wrong with the kernel.

Tap-a-talked from my Nexus 7
[Nexus 7 (2013) Original Android Development] vali_ics:
Just flashed PureNexus + elementalx kernel + xposed v84 (I think) all working flawless.
[Nexus 7 (2013) Original Android Development] xMayonnaise:
i think i will just have to try my procedure again

---------- Post added at 12:24 PM ---------- Previous post was at 12:20 PM ----------

i will try again.. i am currently using kitkat.. i want to switch to marshmallow
[Nexus 7 (2013) Original Android Development] DroidIt!:
If you're using KK I think you want SDK 21. Lolli SDK 22 and MM SDK 23. I think that's probably your problem. I've not seen flar's or any other kernel ever cause a problem with xposed. It's always a ROM conflict. ;)
[Nexus 7 (2013) Original Android Development] xMayonnaise:
I am using Nexus 7 2013 <MM>, I am installing the sdk23, what I don't know is which arm will I install. (arm/arm64/x86). I think this is the part where I am making mistake.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Just ARM, which is the only version of the three that will ever possibly work for flo/razor, same goes for gapps packages.
[Nexus 7 (2013) Original Android Development] xMayonnaise:
thanks
[Nexus 7 (2013) Original Android Development] xMayonnaise:
this is the part where i get an error message while flashing the Xposed framework (see attached file)
[Nexus 7 (2013) Original Android Development] quickdraw86:
Wipe /system and reflash your ROM, also, make sure you have enough free space in the /system partition for xposed to fit.

Edit: BTW, you need 6-10mb in

/system to fit xposed.
[Nexus 7 (2013) Original Android Development] r80ies:
Has anyone seen any WiFi related issues while using 5.11, while running MOB30J? I keep disconnected while running Chrome, and practically all other apps. Using Stock kernel now and no issues. Any feed back is appreciated.
[Nexus 7 (2013) Original Android Development] krapcius:
Hi i'm using MMB29Q with elementalX and i have one problem, it's not suporting any flush dirve or hdd. I tryed a lot of apps like sitck mount, but it not working. may be someone have a solution?
[Nexus 7 (2013) Original Android Development] nigelhealy:
How sure are you have the filesystems supported? Do you know if is exFAT, NTFS, FAT, or a linux filesystem (ext4, ext3....) ?

You might need to tick the elementalx filesystem options on the last screen of the install.

The app can't handle what the kernel doesn't include.
[Nexus 7 (2013) Original Android Development] krapcius:
ElementalX have option to enable exFAT. So i think it should suport. And in that kerlnal description writen: NTFS r/w and exFAT support.
[Nexus 7 (2013) Original Android Development] flar2:
I don't know, it should work with stickmount. Both exfat and ntfs are built in the kernel.
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

May security update

Download

ElementalX-N7-5.12

ElementalX-N7-5.12-cm

Changes:

-May security update
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Thanks Flar...this work with the latest bootloader?

Thanks again.
[Nexus 7 (2013) Original Android Development] nigelhealy:
I know it is your kernel Flar2, but the exFAT support must be enabled in the last set of options, it is not enabled by default.
[Nexus 7 (2013) Original Android Development] flar2:
Right you are, I have it build as a module.

It can be enabled like this:

su
insmod /system/lib/modules/exfat.ko
[Nexus 7 (2013) Original Android Development] 8thphloor:
thanks a lot for this endless support. really appreciate. i have a little question. any chance to see kcal support?
[Nexus 7 (2013) Original Android Development] Jesus65:
About OTG with Charge

Hi flar2,

First, a big thank you for your work ! Almost all I need you have made on your kernel modification :)

But I have a problem with OTG+Charge.

I try in first order simple OTG for check hardware, a simple OTG cable (ID to Ground with 0ohms resistor) and generic Usb Hub and Usb Key with FAT FS. -> All works, lsusb found all device.

I mod the OTG cable with 127Kohms between ID and Ground for ACA OTG.

Kernel see ACA Cable, so charge work, but Usb Host not working anymore.

In /sys/kernel/debug/msm_otg/

For information, in no usb cable mode :

otg_state = b_idle

chg_type = INVALID_CHARGER

In ACA :

otg_state = b_idle

chg_type = USB_ACA_A_CHARGER

(I try to set "enabled" in aca "file" in same folder, no success)

I try to let the ACA OTG cable attached to Nexus 7 and reboot, I find the kernel dmesg see the usbkey (and usb hub), but after around 10-20sec on boot, kernel remove all usb chain and lsusb still empty.

I can make more test to find the problem.

I running 5.12 with MOB30J build (Google rom) and TWRP recovery.

In advance thanks you :)

J.

---------- Post added at 12:29 PM ---------- Previous post was at 12:25 PM ----------

I have try 5.11 before flash the 5.12 version, I not found any trouble with wifi. I have rssi -84 in my office, and I have stable wifi cnx.

in dmesg you have errors ? (adb shell, su, dmesg)

J.
[Nexus 7 (2013) Original Android Development] flar2:
Color control is supported, do you have ex kernel manager? This is an old chip so it's implemented a bit differently than modern devices.

This is an old thing that's been discussed a lot. There might be some workarounds if you search through the thread.
[Nexus 7 (2013) Original Android Development] 8thphloor:
thanks for your answer.

yes, of course i have ex kernel manager. but i only see RGB controls. and if I try some specific app for "classic" kcal tuning it says something similar to "your kernel doesn't support kcal".

so only RGB controls are tunable on this particular old chip?

thanks in advance for this useful clarification and keep it up! this kernel is awesome ;)
[Nexus 7 (2013) Original Android Development] drewski_1:
yes, it does.
[Nexus 7 (2013) Original Android Development] flar2:
Yes, only RGB for this one, and it's a bit sketchy because you have to turn the screen off and on, and sometimes it gets stuck.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Thanks.
[Nexus 7 (2013) Original Android Development] Q8-V08:
I hope ElementalX-N7-5.12 is more stable than ElementalX-N7-5.11, I was geting nothing but device shutdowns and it getting really hot whilst browsing with Opera on MMB29V, the only change I made was overclocking the gpu to 450mhz everything else stock settings.

Never had this happen with ElementalX-N7-2.15 on kitkat v4.4.4
[Nexus 7 (2013) Original Android Development] flar2:
Elementalx is 100% stable, every version. Don't overclock and make sure you have a clean install.
[Nexus 7 (2013) Original Android Development] Jesus65:
USB Otg fail ? Resistor is the key !

About USB Otg, I check the latest version of Google stock kernel, and have FastCharge while OTG. Just 100KOhms between SENSE and GND pin on micro usb connector. :D

With elementalx, same result now.

Where is my problem ? => The ****** resistor, android usb otg host ACA Dock is not between 122-126KOhms, but around 100K... why not...

With 124K, ok on stock, not on ElementalX... same hardware, same registers, I check three times, and same results :eek:

Now all work, and I use ElementalX for double tap wake and swip to sleep. :p

(USB Audio ok, USB Key ok, USB hub ok)

Step used :

Factory rom flash (all)

Flash TWRP

Flash SuperSu from TWRP

Boot Android, check su (and install adb wifi for debug, optional)

Reboot in TWRP, flash this Kernel, all default parameters (but fast charge + otg while charging checked)

It's time to mount on dashboard :) :fingers-crossed:

J.
[Nexus 7 (2013) Original Android Development] alancai:
any 5.12 for f2fs please?? thank you.
[Nexus 7 (2013) Original Android Development] litzer.rubicon:
Doing your steps, but it doesn't work. It doesn't charge. What can I do? I want it on my dashboard :(
[Nexus 7 (2013) Original Android Development] nigelhealy:
Attached is 5.12 for f2fs. I'm running this myself so it is tested.

Attached also is the same mod for CM version, I've not tested so beware (say take a full nandroid backup if you're concerned).
[Nexus 7 (2013) Original Android Development] Q8-V08:
Idk then, I installed it via twrp v2.8.7 along with SuperSU v2.65 and latest busybox.

I'll try 5.12 with MOB30J.
[Nexus 7 (2013) Original Android Development] Jesus65:
Hi,

I make some change in my setup, specialy for usb disk.

In Android 6.x Vold make hard to browse usb disk, after one day to find a solution, I swap to Android 5.x, and on CyanogenMod 12.1.

I add tasker for

* when charging, set volume, turn on speaker, wait 8sec (for usb disk mount), start GoneMad Music Player, start screen, resume music, turn on auto brightness (with Lux for fine steps).

* when unplug, set volume to 0, pause music, turn off speaker, set brightness to 0 (if case of tablet wake in my car, I live in bad city :/, someone can break window to take my tablet), turn off gps/wifi, go to sleep.

And because I no need anymore Double tap to Wake and SweepToSleep, I not use anymore ElementalX kernel.

With my otg cable, fastcharge and OTG work without problem.

Remember, use Y cable, short wire between Charger (12v->5V) to micro usb connector. You need at lease 5.15v at connector for FastCharge (see this website : sites.google.com/a/mst.edu/robert_ruark/projects/google-nexus-7-charging) And put 100K resistor between Ground and ense pin (4).

Below 95K and over 105K, FastCharge and OTG will not work ! I try other value. Attention, some Y cable have already resistor, check value !

You can see in dmesg if you cable is ok. for check dmesg, use ADB over WIFI, get shell with root access and run this when unpluged : "dmesg -c" . After that, plus you cable, wait 10sec, and run "dmesg" (without -c), and post here the result.

I have USB current and voltage checker, I up to 1.25A and 5.25V when tablet use at maximum (gps, navigation software, usb disk, usb audio, HID keyboard, and music run)

Remember, with this OTG cable, the FastCharge and USB Host, work out of box on Stock Rom ! (5.x and 6.x), CM12.1 only for better usb disk mount)

Here schematic of OTG cable with FastCharge

sites.google.com/site/sonicboomworld/_/rsrc/1345753009582/my-projects/otg-diagrams/Y_OTG_CABLE.png

Tell me if you have success :)

(Sorry for link, I can't use URL tag, because I don't have enough post)

**EDIT**

I need to use ElementalX kernel, because on CM11.2 the kernel have a bad handler about power lost when OTG is on. When power lost (5V lost), the kernel want to go OTG host and provide 5V, but in fact no 5V provided. So I do not have flag to check if power is on or not.

With elementalX 4.05 (for CM 11.2), all work fine now. Now I mount in my car, and pray for not problem with heat.
[Nexus 7 (2013) Original Android Development] MikiGry:
I"m running Pure Nexus rom. To make my Nexus detect pendrive (usb OTG) i need to reboot the tablet. When i unplug it , then plug again it wont work (i need to reboot). What could be wrong ?

Edit

Do not check OTG+charging module

It beaks OTG .
[Nexus 7 (2013) Original Android Development] r80ies:
WiFi still choppy

I saw that the update in 5.12 was a revert change in your WiFi driver. Well, I am reporting I am still having really shaky WiFi connection and reverted back to stock kernel. I even bought EX kernel manager and tried to pull logs, but it is so random I cannot upload without it being cut off. I moved the logcat to my comuter via USB, but I cannot use any Internet apps without a dropped connection. Please let me know if you would like me to attach the logcat. So far with stock kernel I am able to run, Chrome, Kodi, Netflix without the app FC or connection being lost. Let me know if I can be of any help.
[Nexus 7 (2013) Original Android Development] just lou:
No WiFi issues here with 5.12.
[Nexus 7 (2013) Original Android Development] Z23:
No WiFi issue with CM13
[Nexus 7 (2013) Original Android Development] flar2:
I've never had a wifi issue and the kernel makes no changes to wifi.
[Nexus 7 (2013) Original Android Development] krapcius:
I have the same problem

Someone have an idea?
[Nexus 7 (2013) Original Android Development] MikiGry:
[MENTION=7451325]krapcius[/MENTION]

Make sure , that this module is DISABLED.
[Nexus 7 (2013) Original Android Development] krapcius:
Ok i will try thanks

---------- Post added at 01:09 PM ---------- Previous post was at 01:03 PM ----------

Nop it not workin

now its not charging and no usb host
[Nexus 7 (2013) Original Android Development] DrEVILone81:
Thx 4 the amazing work since 3years for the m7 and the nexus7 ...could it be possible flair to introduce a reliable signature for the downloads....???.....for example sha 256 ?... md5 and sha1 are not reliable anymore....!!!please consult the mod or someone else. Or give me the adress to the person.....

Thx for your efforts....
[Nexus 7 (2013) Original Android Development] khaytsus:
Nonsense, the signature for the download is to verify corruption which MD5 is perfectly capable of doing. He's not creating secure hashes.
[Nexus 7 (2013) Original Android Development] DroidIt!:
You're verifying you're corrupt!?! If only it were that easy to verify a corrupt person with a hash! :)
[Nexus 7 (2013) Original Android Development] Jesus65:
Little information,

On 4.05-cm (because Android 6 with new OTG function make usage of USB Disk very hard), a bug for OTG + FastCharge on boot.

I apply patch on 5.xx Kernel to 4.05-cm (commit d1e7c89472030b911486528e62a7073dec990a91), and change the initial value of variable :

static bool usbhost_charge_mode = true;

(in msm_otg.c)

Now, when boot OTG work, fastcharge work and android user space see Charging.

May we can better patch, because this modification force to fastcharge at boot, even user unselect option in installation.

--EDIT--

Add file, if anyone want :)

--EDIT2--

CM version used : 12.1-20151117-SNAPSHOT-YOG7DAO1K9-flo
[Nexus 7 (2013) Original Android Development] htb2050:
Love your governor. The stock cm kernel was severely under powered on this device and the device was Kathy all around. Flashing this made the lag go away and even keep the battery life great. Thanks.
[Nexus 7 (2013) Original Android Development] r3zd0g:
I just upgraded to Stock 6.0.1, and then installed v5.12 of the kernel. OTG seems to work with charging, but the battery icon does not show charging, and there is no battery information. I believe the N7 is still getting power but no feed back about charging. If I plug a charging cable in directly, I see the charging indicator. Has any one else seen anything like this?
[Nexus 7 (2013) Original Android Development] d1dd1:
good to know

[MENTION=4684315]flar2[/MENTION]: is that the solution to our no tog fastcharge problems on boot?

Could you add some kind of setting to AROMA or EX Kernel Manager ?

Yes, this was reported several times. Also e.g. Tasker does not detect that the tab is charging :(
[Nexus 7 (2013) Original Android Development] r3zd0g:
Sorry for submitting an issue again. Is there a place to report issues beyond this thread?
[Nexus 7 (2013) Original Android Development] Jesus65:
About my fix,

On the original kernel (by flar2), the fastcharging is disabled at boot, and the init script (elementalx.sh), set fastcharging to on after boot. So otg work, yes (it's stock kernel), but fast charging not, because the detection of VBUS is around 3-8sec after kernel start, and the init script run around 15-20sec after boot.

It's not easy to have same kernel with modified value inside kernel before start, unless you change in ramdisk used for boot (cmdline, ...)).

Maybe compile two version of kernel (for permanent installation, like car, boat, rocket (yeah !)) ?

--EDIT--

If someone want test, I can compile the last version (5.12) with this fix to check if work at boot. Tell me :)
[Nexus 7 (2013) Original Android Development] beren:
what is the max charge (in mA) that i can expect when using the otg+charge?

i am going to put the N7 in my car and power with a 2 amp charger from cigarette plug.
[Nexus 7 (2013) Original Android Development] Z23:
Does somebody else having strange battery behavior? I just watched 30 minutes video and still it shows 100%. This is new to my device. CM13

Edit: Even recovery shows 100%. Strange.
[Nexus 7 (2013) Original Android Development] Jesus65:
The maximum I can reach is 1490mA when battery charge and use the tablet at maximum (all core is maxed in frequency), gps running, music playing, brightness to max, gpu usage at max, ... (I have precise current monitor for usb).

On TWRP or CM12.1 (or 13 when I use but usb storage is not good for my application), I not noticed a problem with battery monitor.
[Nexus 7 (2013) Original Android Development] Z23:
Now percentage goes down but battery is definitly misscalibrated. I never had this before. Maybe a bug in battery life extender function? I choosed it in aroma installer, but did not activate it in the app... I found on the net that "nethunter kernel" had simular issue... Never heard of "nethunter", but perhaps this is kernel related. Did not use strange apps or something, just a bit MXPlayer and Chrome.
[Nexus 7 (2013) Original Android Development] litzer.rubicon:
It would work for stock 6.0.1 ??? I will be interested
[Nexus 7 (2013) Original Android Development] beren:
i don't have an hardware monitor, i use Ampere app (probably only stimate) to measure the charging rate.

from my 2A car charger i only get 700mA, so was wondering if it's possible to increase, maybe need more power from the charger?
[Nexus 7 (2013) Original Android Development] Jesus65:
You need a good cable, and low voltage drop (diameter of cable is important !)

Use DMM on usb micro (not on charger side, but on nexus 7 side) and mesure voltage, and use https://sites.google.com/a/mst.edu/robert_ruark/projects/google-nexus-7-charging for current available.

With 5.25V in my case, with fast charge, up to around 1.5A.
[Nexus 7 (2013) Original Android Development] beren:
thanks a lot...

but how to measure voltage on micro usb?
[Nexus 7 (2013) Original Android Development] Jesus65:
With DMM (Digital MultiMeter) or Voltage Meter.

You can make male-female adapter with open wire, or like me, a open micro usb connector and check before close the connector.

In fact, if you have around 5.25V at charger, and less than 1m of cable, with good section (I use cat6 cable, and work fine, because I'm computer company owner ;)), you rule fine.

Do not forget, some charger, make a voltage drop when current increase (the cheap charger make this... everytime !). You need good charger, not a cheap DC/DC. Open your charger, if you see big capacity (470µF at least), and big inductor (a piece with thin wire), you have not too bad charger.
[Nexus 7 (2013) Original Android Development] beren:
thanks again, so i just need a female microusb connector to check.

btw i suppose my car charger doesn't provide enough voltage, because it's very cheap one...will check asap.
[Nexus 7 (2013) Original Android Development] Jesus65:
But you need to check WHEN is plugged to Nexus 7 ! Because voltage drop is in relation to current.

Use bigger cable (AWG 20-23 depend of length of your cable), directly to usb micro (you can open usb micro easily with cutter or razor blade (take attention ;)). I made this on three usb micro (because I make three different OTG cable).

98% of cable in the market is 800mA maximum, make your cable is better way if you have skill for weld in little space. (Not so hard ;)).

If cable is rated for 2A (and not low cheap cable from china) it's good, the price is between 9-15$ at least. Forget 2$ cable, if you find good cable at this price, share the link =).
[Nexus 7 (2013) Original Android Development] d1dd1:
I would be very happy to test, as I have a permanent car install (CM13) :D
[Nexus 7 (2013) Original Android Development] Jesus65:
Here the zip file, 5.12-cm with patch.

Remember, always fastcharge at boot.
[Nexus 7 (2013) Original Android Development] d1dd1:
Works like a charm, thanks a lot !!
[Nexus 7 (2013) Original Android Development] mageus:
OTG+charge doesn't work

Nexus 7 '13

Android 6.0.1

ElemX 5.1.2

When the OTG+charge option is enabled, OTG doesn't work. Android doesn't recognize any devices plugged in. LSUSB notices the difference when something is plugged in (1d6b:0002, the hub is enabled), but doesn't show the actual device that is plugged in.

With the stock kernel, or ElemX without OTG+charge enabled, OTG works fine. I tried multiple cables. The OTG+charge cable works fine on a Shield K1.

My OTG cable has the ID pin shorted to ground. Does ElemX require a cable with a resistor?

I did not enable any other options during the ElemX install.
[Nexus 7 (2013) Original Android Development] Aerobatic:
This is how it should be. unless you use Y-cable or active USB-HUB with external power. USB devices need +5V to operate, while in "OTG+charge" mode gadget stops providing power (it needs external power to charge)
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

June security update

Download

ElementalX-N7-5.14

ElementalX-N7-5.14-cm

Changes:

-June security update
[Nexus 7 (2013) Original Android Development] gx211:
The express download is failing on the Elemental app. Just FYI Nexus 7 2013
[Nexus 7 (2013) Original Android Development] MatVekk:
Thanks!

Inviato dalla mio Xiaomi RedMi Note 2
[Nexus 7 (2013) Original Android Development] Pkt_Lnt:
[MENTION=4684315]flar2[/MENTION] Yes, confirmed download failure here as well.
[Nexus 7 (2013) Original Android Development] DJMartini:
+1 same
[Nexus 7 (2013) Original Android Development] noneabove:
People who started getting touch issues in 1.1 like myself, are you running the latest version of the ROM or before the touch fixes were implemented? I was running the old version so I'm going to wait for the ROM I'm using to be updated then try this again to see if it works well then
[Nexus 7 (2013) Original Android Development] jlevy73:
I was using cleanrom but then installed the stock version of the new FW, then installed 1.1 of this kernel. I don't notice any touch issue problems but when I test it using the myriad of multi-touch test apps, it fails them. So I'm not sure where the issue is. I might just reflash the stock FW and see if the multi-touch tests still fail.