yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] juliatan:
With this kernel 5.05 on stock 6.0 I cannot mount Truecrypt and VeraCrypt containers on my Flo with EDS. Is there a fix for this. On stock there was no issue at all mounting encrypted containers.
[Nexus 7 (2013) Original Android Development] Shinson:
Yap. This is nice if you lose power on the way, re-plug and then have the "USB not recognized anymore issue".

My problem is:

If I plug everthing in and then boot the device, everything plugged in is working, but the N7 is not charging. I have to unplug N7's connector (having OTG cable, hub, dac, etc. behind it) and re-plug it for OTG + charge mode to work.

I "just" have to unplug and re-plug it.

...but of course I don't like to. It's driving me nuts. :eek:

Suggestions? Anyone?

PS: I also have to re-plug it after deep sleep for OTG + charge mode to work.
[Nexus 7 (2013) Original Android Development] 623baller:
did you try the method yet?

i had the same issue you described and it worked at least in my set up, the script basically unplug and plugs the usb cable without you having to do it physically.

either im coming from a reboot , deep sleep , if only one of the function be it OTG or charging works, i execute this script to work around the issue. this is a work around not a fix. but you can probably build it in tasker so it's automatic.
[Nexus 7 (2013) Original Android Development] andy_rose:
Where can I find the express version?
[Nexus 7 (2013) Original Android Development] :
Our nexus has just revived official cm13. Will caf mm version be released? Thanks in advance! :)
[Nexus 7 (2013) Original Android Development] quickdraw86:
There isn't one for flo...
[Nexus 7 (2013) Original Android Development] Shinson:
Yes I did. Actually it worked one time (I don't even know why). Since then script is giving me errors:

[IMG="script errors"]https://static.dyp.im/UGTAVYVVWR/0c952c1d29b27024c34755586f41bce7.jpg[/IMG]

Makes sort of sense, because after resetting the very first entry in line (or 001/001 => OTG y-cable) all other entries get new names as you see here:

[IMG="files change"]https://static.dyp.im/etKaQqjQ82/0c52ea90e5f9b8a9f025aad8628e6654.jpg[/IMG]

(First I listed all devices, then I did a reset to the very first in line 001/082 and listed all devices again. Result is new names starting at line three.)

I guess that's why the "while loop" of the original script line is producing errors... but I don't know why script is working on other devices.

I even tried to reset them all by hand but none of them reacted on the charger. It still only helps to disconnect and re-connect the OTG y-cable.

The only time usbreset is affecting charge mode and works as you say is when you boot the N7 with OTG cable and power connected only. After executing

# usbreset /dev/bus/usb/001/001

power is triggered and showing up. Afterwards you can plug everything you want and just works straight away.

Well, at least last paragraph still proves that the setup is working, but I'm not getting the picture how to express that manual plugging in code OR what I probably missed. :confused:
[Nexus 7 (2013) Original Android Development] Krunk_Kracker:
Well, after a total wipe and reinstall of the rom and ElementalX, I no longer have the issue. So there's no telling what it may have been. I'll start reinstalling my Xposed modules one by one and see.
[Nexus 7 (2013) Original Android Development] 623baller:
i would double check you have the usbreset in the /system/bin folder with super user privillege. based on your error output, it looks like it cant find usbreset file after it executed sleep 18 command. i do get some permission errors when i run the script but it still works. also i do not plug or unplug any of my OTG device or OTG cable. if all else fails, i guess try to contact the original poster to see what he thinks. one other thing i would try is maybe create another usbreset file and remove the sleep 18 command.
[Nexus 7 (2013) Original Android Development] treehugger38294:
Is anyone getting random soft reboots lately? I might factory reset and see .
[Nexus 7 (2013) Original Android Development] _jis_:
Not at all. I read in another thread that one reason could be using Greenify xposed module in MM.
[Nexus 7 (2013) Original Android Development] seriosbrad:
Not sure why, but when I install EX5.05 after installing CM13 (with data/cache wipes) it boots very slowly. The CM13 boot animation is very slow, when it gets to choosing a WiFi network it just hangs. Installing CM13 without EX5.05 boots normally.
[Nexus 7 (2013) Original Android Development] Phoenix09:
because there isn't a CM version yet
[Nexus 7 (2013) Original Android Development] quickdraw86:
Derp. Post removed.
[Nexus 7 (2013) Original Android Development] klaust58:
?

Lollipop: 4.05

Marshmallow: 5.05

:cowboy:
[Nexus 7 (2013) Original Android Development] quickdraw86:
You're right. Post fixed, need sleep I guess.
[Nexus 7 (2013) Original Android Development] marsaltito:
I just hope donation helps little to get CM 6.0 (MM) kernel soon ! ;) (i can wait for mnth not problem just it arrives ) :)
[Nexus 7 (2013) Original Android Development] quickdraw86:
Sigh. If you're going to donate, donate because you support a developer's existing work, not because you want/expect something in return...
[Nexus 7 (2013) Original Android Development] marsaltito:
? i used ex kernel long time and now i have money to donate . and its just wish not demand !!

and yes i expect update , why not ?
[Nexus 7 (2013) Original Android Development] DroidIt!:
:) Not to go ot, but this kernel on flo has been stable and had all the features on a kernel I could imagine for a LONG time. There's not much need for work on this kernel really. If you look at ALL of flar's other threads, in other words all the other devices he supports, he's doing a lot of work on getting ElX for those devices up to his standards of stability and usability that his kernel for the flo already enjoys. In short, he does ALL of this for free and so I'd agree too that it would be more proper IMO to just donate if you feel so inclined and be patient and appreciative of the work he has already done for the flo and what you are able to do with your device as a result of his work. To EXPECT more than what flar has already given for this device is just rude...no more from me, and no offense intended, just my view and I suspect the view of many others :)
[Nexus 7 (2013) Original Android Development] flar2:
I will get to the cm version sometime. I always have a long to-do list and this will come around soon.
[Nexus 7 (2013) Original Android Development] Diljinder:
I'm facing an issue with this kernel. When my device (Nexus 7 2013 running Stock Marshmallow) is laying down for a considerable amount of time & it goes to sleep mode, it becomes unresponsive when it try to wake it up.

First, DT2W gesture doesn't work although enabled. It wakes up through power button but touchscreen doesn't register unlocking gesture. Basically the touchscreen just goes off.

Only solution is to power it down & boot again. It is now happening on daily basis. Hope dev [MENTION=4684315]flar2[/MENTION] would resolve it.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Two things I could think of :) 1. What's your screen off freq set at? It might be too low. 2. Do you have any sort of doze mod or any other mod that is supposed to make your tablet sleep deeper? Those are really the only two things I can think might do that. I would think it'd have to be some mod or app on your end though...:) With two N7's on ElX for a year and a half I've not experienced that at all.
[Nexus 7 (2013) Original Android Development] _jis_:
I cannot confirm this.
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

For latest Cyanogenmod

Download

ElementalX-N7-5.05-cm

Changes:

-Cyanogenmod/CAF support
[Nexus 7 (2013) Original Android Development] ranaxda200:
Latest (Dec 7) cm nightly got bootlooped though the previous build worked fine. Anyway thanks again for this undoubtedly best kernel.

Edit: problem solved. It was my fault, no problem with the kernel. ?
[Nexus 7 (2013) Original Android Development] NovaSlim:
upload your last.kmsg after your recover from bootloop please, just saying you got a bootloop does nothing to help developer debug the issue.
[Nexus 7 (2013) Original Android Development] flar2:
Then you should be using the previous build. The latest one is only for cm.
[Nexus 7 (2013) Original Android Development] yiannis1621991:
How can i run the express installer?

Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk
[Nexus 7 (2013) Original Android Development] NovaSlim:
Express version for Nexus 7 are only available through the ElementalX Kernel Manager app. When you want to use it, just download/install it through the app(ElementalX->Click the middle tab-> Choose Express->Download). There is an option to automatically install it after downloading, or you can uncheck that and boot into recovery for installing it yourself.

Express versionuses either the default setting(if you have not previously installed EX kernel) or your previous EX kernel setting.
[Nexus 7 (2013) Original Android Development] readonly24:
I just installed this kernel on current CM13 nightly, but my exFAT USB stick is not recognized. DT2W and S2S works nice.

Thanks for all your work, I already use your kernel on my Nexus 5
[Nexus 7 (2013) Original Android Development] just lou:
JFI, 5.05 seems work OK with Android 6.0.1. I haven't noticed any issues.
[Nexus 7 (2013) Original Android Development] milliman:
Did you root your Nexus 7? I installed 5.05 and SuperSu and ended up in a boot loop.
[Nexus 7 (2013) Original Android Development] NoobieExtraordinare:
Ok will give that a shot.

Update: installed, booted normally. Weird. Thanks flar2
[Nexus 7 (2013) Original Android Development] ophidia:
Glad it worked for you. Absolutely refuses to boot for me on the 8/19 nightly. :(.

Edit: I guess I was too hasty. Booted now. Derp.
[Nexus 7 (2013) Original Android Development] mumumusuc:
bad news, pa3.98 is based on jwr66v,so 1.1 doesn't boot with this rom.

I tried and stuck in Google screen
[Nexus 7 (2013) Original Android Development] flar2:
Reboot again, it'll work

Very minor changes in the kernel update
[Nexus 7 (2013) Original Android Development] rubaboo:
Anyone with SlimBean b2 Weekly? Stuck on Google. Tried holding power, no avail. Back on 1.0 boots no prob.

EDIT: Repeated install again after installing 1.0 and booting successfully. Now it works. :good:

I swear, the first time I waited long and reset (holding power) several times, it wasn't going anywhere. :confused:
[Nexus 7 (2013) Original Android Development] jlevy73:
Out of curiosity, was the touchscreen fix apart of kernel changes made in the last OTA? Based on the release notes for 1.1, I'm assuming yes.
[Nexus 7 (2013) Original Android Development] bounti:
OK great. Can you test to see if you're getting any improvements over stock?
[Nexus 7 (2013) Original Android Development] mumumusuc:
Ok,trying again

Yes,it works, thank u
[Nexus 7 (2013) Original Android Development] lpachuong:
After rebooting couple times, she managed to escape from the Google Screen :) However, I notice wifi signal strength is weaker than before, could be a problem from my end?

Touch screen issue seems till exist using multi touch tester
[Nexus 7 (2013) Original Android Development] Clienterror:
None, still getting way lower scores :(
[Nexus 7 (2013) Original Android Development] bobloadmire:
TWRP won't let me install. It says install failed. I downloaded it a few times UT it fails on all 3 downloads to install in TWRP
[Nexus 7 (2013) Original Android Development] ktkr:
What did you do to make that happen? I couldn't reproduce that on my device.
[Nexus 7 (2013) Original Android Development] sevenslugs:
I installed 1.1 with clean rom 1.3.............hung at google screen on first bootup after flash...........held down the power button and it restarted fine.............everything is smooth ...........
[Nexus 7 (2013) Original Android Development] lpachuong:
Hi ktkr, I used multitouch test program, put the tablet in portrait, the two fingers left hand, two fingers right hand, try to align them in to a vertical line, the bug appears again.
[Nexus 7 (2013) Original Android Development] jlevy73:
Very interesting, you are very right. I could reproduce the bug using the instructions you provided. Guess the multitouch issue is not resolved.
[Nexus 7 (2013) Original Android Development] ktkr:
Looks like it's also on mine, only in landscape mode. Now let's wait for the next update from google.
[Nexus 7 (2013) Original Android Development] Truthiswithin:
Same here... The zip file is corrupt, tried opening in file browser, says it's bad.
[Nexus 7 (2013) Original Android Development] Philaphlous:
Doesn't work for me either. Hi Google screen, nothing more after that shows....
[Nexus 7 (2013) Original Android Development] wintermute000:
Did you have the problem with stock kernel / JSS15Q build? i.e. did the new build resolve your problem, you flash this kernel and bug comes back? Or are you one of the unlucky people who JSS15Q didn't work OR you never went to JSS15Q
[Nexus 7 (2013) Original Android Development] flar2:
Download with a different browse or from your pc

Hold down the power button and reboot, it'll work.

Not sure why it's doing that, it only happens once (first time installing) I can't reproduce it.
[Nexus 7 (2013) Original Android Development] just lou:
I'm running OMJ's stock rooted ROM. http://xdaforums.com/nexus-7-2013/development/rom-bad-boyz-nexus-7-stock-rooted-t3219148
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

Update for Android 6.0.1

For stock ROM:

If you want root, you must use SuperSU 2.61 found here:

http://xdaforums.com/showpost.php?p=64161125&postcount=3

Flash SuperSU 2.61 in recovery, then flash ElementalX in recovery

You only need to install SuperSU the first time. Once you are successfully rooted, you can install any future update of ElementalX without reflashing SuperSU again.

If you install other kernels after this, you must flash stock boot.img, then SuperSU 2.61, and then ElementalX.

For pre-rooted custom ROM:

Just flash ElementalX

Download

ElementalX-N7-5.06

Changes:

-update for Android 6.0.1
[Nexus 7 (2013) Original Android Development] DaveImagery:
Thank you flar, your incredible.
[Nexus 7 (2013) Original Android Development] pilotv:
Do we have always enforcing option enabled in EX, to be able to run Mm 6.0.1?

Sent from my N7 + ElementalX + Multirom + MM6.0
[Nexus 7 (2013) Original Android Development] flar2:
I always run with selinux enforcing
[Nexus 7 (2013) Original Android Development] Billybobjoe13245:
Great Work!

I love this kernel. Keep it up. Also quick updates for when new android versions come out.
[Nexus 7 (2013) Original Android Development] marsaltito:
Tested on CM13 (6.0.1) and works .

Thx . i did try some other kernels for CM just not good like yours !

My next step is to buy app from store . :)
[Nexus 7 (2013) Original Android Development] Maurizio1953:
Is there a version for Samsung galaxy note 3 with stock lollipop rom?

Inviato dal mio SM-N9005 utilizzando Tapatalk

---------- Post added at 07:38 PM ---------- Previous post was at 07:27 PM ----------

The flashable zip for permissive mode is also for galaxy note 3 with stock lollipop rom? May I use it safely?

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Nexus 7 (2013) Original Android Development] montbazon:
Which version did you try??
[Nexus 7 (2013) Original Android Development] aabuk:
Hello, first, im sorry for bothering but could any developer try port elementalx to mako? Thanks and sorry.
[Nexus 7 (2013) Original Android Development] marsaltito:
5.05 !

5.05 CAF is for 6.0 and cm13 after 8.12.2015 is 6.0.1 .

Now im on cm13 date :11.12.2015
[Nexus 7 (2013) Original Android Development] flar2:
It's too late, the nexus 4 is discontinued and I don't have one.
[Nexus 7 (2013) Original Android Development] flar2:
The permissive zip only requires SuperSU.

I don't develop for Samsung phones, only Nexus and HTC.
[Nexus 7 (2013) Original Android Development] aabuk:
oh, that's, bad, :( well if u could try i could test :) atleast some alpha builds, thanks, i know its bad to build kernel for device you dont have but if you could try i would be very happy and i think some people would apreciate it too, so thanks and i will be tester if anything to test :D
[Nexus 7 (2013) Original Android Development] flar2:
That's why I don't do it. I also don't have enough time.
[Nexus 7 (2013) Original Android Development] readonly24:
Hi flar2, I'm using latest cm nightly and ElementalX 5.05. Though I configured exFAT and DT2W timeout, both seems not to work.
[Nexus 7 (2013) Original Android Development] aabuk:
[MENTION=4684315]flar2[/MENTION] oh thanks anyway and goodluck in future! Have a nice day. :)
[Nexus 7 (2013) Original Android Development] Purplezigar:
So I'm on the latest CM13 nightly (Dec 11.) with your kernel (5.05-CM), and Netflix isn't displaying video for me. Does anyone else have this issue? I know that I'm on 6.0.1 and the kernel is built for 6.0. Could that be the issue? Also thanks flar2 for this kernel. Great work ☺
[Nexus 7 (2013) Original Android Development] efan3719:
hmm it could be. you could try returning to the kernel that comes with CM13 and see if that makes the video show up again. though, since it's a nightly, maybe you just found a bug. :p
[Nexus 7 (2013) Original Android Development] Purplezigar:
Just went back to stock CM. Still not working. Found a bug I guess. Yay.....
[Nexus 7 (2013) Original Android Development] marsaltito:
Are you shore its bug ?

I dont have that with or without elementalx !
[Nexus 7 (2013) Original Android Development] Purplezigar:
What nightly are you on?
[Nexus 7 (2013) Original Android Development] marsaltito:
13.12.2015
[Nexus 7 (2013) Original Android Development] Purplezigar:
Huh. I couldn't watch Netflix on 11.12.2015, but I can on 13.12.2015. Thanks for pointing this out! It works with EX, which I'm happy about. :good:
[Nexus 7 (2013) Original Android Development] marsaltito:
netflix and chill ! ;)
[Nexus 7 (2013) Original Android Development] PoedelPCS:
I got a problem with my battery showing percentages of 4 digit numbers.

OFW 6.o.1 on Nexus 7 2013 16GB

your latest kernel

supersu 2.62

Do you guess it's because of the kernel?
[Nexus 7 (2013) Original Android Development] _jis_:
Post screenshot please.
[Nexus 7 (2013) Original Android Development] PoedelPCS:
You can see that if you zoom in on the status bar. The battery widget does not work due to that either.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] flar2:
It's because you have 6.0 ramdisk with 6.01 system.
[Nexus 7 (2013) Original Android Development] PoedelPCS:
Ramdisk is a word I know from my gentoo Linux. But why is there the old ramdisk and how can I solve that? I'm quite confused..

Gesendet von meinem LG-D802 mit Tapatalk
[Nexus 7 (2013) Original Android Development] DroidIt!:
You need to flash ElX 5.0.6 not 5.0.5. ;)
[Nexus 7 (2013) Original Android Development] jervis93:
same problem as this http://xdaforums.com/nexus-7-2013/nexus-7-2013-qa/mmb29k-update-root-battery-t3265860

reflash boot img and supersu to fix this issue...
[Nexus 7 (2013) Original Android Development] flar2:
My kernel uses whatever ramdisk you already have. So to fix it (assuming you are on stock ROM), flash the stock 6.0.1 boot.img, then flash SuperSU 2.62 (if root is desired), then ElementalX. On custom ROM, just reflash the ROM, then flash ElementalX.
[Nexus 7 (2013) Original Android Development] PoedelPCS:
thanks to you and all the others! That worked! Great!
[Nexus 7 (2013) Original Android Development] aamir123:
Would it be possible to add interactive governor to this kernel?
[Nexus 7 (2013) Original Android Development] mdamaged:
Sure, the source code can be found here: https://github.com/flar2/flo
[Nexus 7 (2013) Original Android Development] aamir123:
Not sure if this was snippy or not but I was just asking because I have never made anything from source code. I don't want to start with a kernel. Anyways just a harmless request.
[Nexus 7 (2013) Original Android Development] flar2:
I had to remove it because it was conflicting with the elementalx governor.
[Nexus 7 (2013) Original Android Development] petre11:
dont know if its ok to post here but this forum its so big....I have a Htc M8 with viper rom on it.What i want to is to flash this kernel but without sense.It is possible to do this?

Thank you all!
[Nexus 7 (2013) Original Android Development] NovaSlim:
You should be asking that in flar2's HTC M8 kernel thread :http://xdaforums.com/showthread.php?t=2705613
[Nexus 7 (2013) Original Android Development] montbazon:
Hallo flar2

Actually I need to report something issue.

I try to flash latest elementalx for cm.

IMO it works with decrypted device.

After I encrypt my device. And it doesn't boot at all.

I wonder know whether you could fix this issue.

Thanks a lot for your support
[Nexus 7 (2013) Original Android Development] flar2:
It's a known issue, but I don't know why it won't work.
[Nexus 7 (2013) Original Android Development] montbazon:
I figure it out now. Kexec hardboot(Multirom) breaks encryption.

http://xdaforums.com/showpost.php?p=57730938&postcount=76
[Nexus 7 (2013) Original Android Development] edison0354:
Am I the only one who's xposed is conflicted with ElementalX on flo?

1. When flashing xposed first, then ElementalX, the kernel just don't work. It can boot normally but functions like dt2w don't work. Seems that the elementalx.sh is not executed during booting, because when I manually toggle settings in /sys/android_touch/, dt2w just works!

2. When I flash ElementalX first, then xposed, it stucks.

gzip: short write
E:Error executing updater binary in zip ‘/sideload/package.zip'

Have no idea why this happens. I'm using the 6.0.1 factory image flashed by fastboot.

Using SuperSU-v2.62-3, but it still happens without flashing supersu.

BTW, on my Nexus 5, everything works OK.

UPDATE: [SOLVED]

Restart recovery before flashing xposed should just fix it……
[Nexus 7 (2013) Original Android Development] DroidIt!:
No never had a problem here. Are you trying with the new v79 SDK 23?...and don't honestly know if it makes a difference, but I flash all ROM stuffs including kernel and then xposed. :)
[Nexus 7 (2013) Original Android Development] edison0354:
Both v78 and v79 have the same problem, I'm using the multirom modified TWRP, maybe this is the reason? I'll try later with the official one.

update: still failed with official TWRP recovery
[Nexus 7 (2013) Original Android Development] montbazon:
I wanna just know how it will go.

Will you fix this issue??

Or let you them be like now??

In my case my device is forcing into encryption by my job.