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

I want to build the Nexus 7 2013 LTE in my car.

Ignition (connected with a 12V-5V DC-DC converter over OTG cabel with the Nexus) should turn the Nexus on and off.

Everything is connected over a 7x-USB Hub. (e.g. the Behringer USB DAC)

When I disconnect the 12V, then reconnect it and try to start playing music the sound comes out of the Nexus speakers and not out of the Behringer USB DAC as it is supposed to.

When I then disconnect the cable from the Nexus and reconnect it, USB audio is working again.

It seems like Android doesn't recognize the USB devices anymore once the voltage is disconnected and the reconnected.

Does anyone know if there is a solution to my problem? Like an Android/ ElementalX setting?

I have tried with Android 5.1.1/ ElementalX 4.05 and Android 6.0.1/ ElementalX 5.05/ 5.07 so far.

Thank you.
[Nexus 7 (2013) Original Android Development] efan3719:
On latest kernel backlight goes totally black when set low and adaptive brightness on. I even turned off back light dimmer via the kernel manager app but it'll still go black instead of its normal dimmest setting. With adaptive brightness turned off the lowest brightness is normal and doesn't go black at all.

Currently on Pure Nexus Rom and its AOSP based. Updated via kernel manager app.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Heya Efan. :) Yeha it's always been the case that backlight goes lower when the auto brightness is on and backlight dimmer is on. I can't remember the reasoning for that, but there it is. Did you try clearing the app cache and/data. I always keep the dimmer turned on myself so can't really comment too much, but I'll take a look in a bit myself. :)
[Nexus 7 (2013) Original Android Development] flar2:
It must be your panel, because mine does not go all the way black with the dimmer enabled.
[Nexus 7 (2013) Original Android Development] efan3719:
Disabling it in the app, setting it on boot, and rebooting seems to have fixed it. Must be something weird with my set up.
[Nexus 7 (2013) Original Android Development] apexcell:
Does the same with mine (5.07, Pure Nexus Rom). Totally black, can't see a thing.
[Nexus 7 (2013) Original Android Development] efan3719:
maybe there's something goofy with pure nexus and this kernel.
[Nexus 7 (2013) Original Android Development] Debanka:
Did you notice the screen kinda flickering when you browse ? I am noticing this, I thought it was a rom problem. I am also on pure nexus

---------- Post added at 12:55 AM ---------- Previous post was at 12:54 AM ----------

Not just his.. The same thing happens with mine too
[Nexus 7 (2013) Original Android Development] efan3719:
maybe it's a rom issue. we should take the discussion to the Pure Nexus thread.
[Nexus 7 (2013) Original Android Development] flar2:
Easy solution: just don't use the backlight dimmer. On my hardware + stock ROM, I set the lowest possible brightness slightly brighter than black.
[Nexus 7 (2013) Original Android Development] efan3719:
even with it disabled my device still goes full black at times. i dunno what's causing it but it might be something with the rom.

***edit. clean wiped and just flashed the ROM. no brightness issue. after flashing the latest kernel on top of that i get the brightness issue. and this is without enabling the back light dimmer. though i also noticed that it doesn't start until i use my magnetic cover to turn off the screen. logcat is attached. dunno if that's what would be needed in this case. if you dont wanna bother with it since it's not a stock rom i'll stop bringing i up. no worries. :good:
[Nexus 7 (2013) Original Android Development] flar2:
I installed latest pure nexus. Tried with and without backlight dimmer enabled, with and without adaptive brightness, with and without magnetic cover. Everything works perfectly.

If you have an issue with screen going all the way black, it is some other mod or your hardware is darker at the same brightness level.

If you don't enable the backlight dimmer, your brightness will be exactly the same as the pure nexus stock kernel. I checked their commit history and they have not modified brightness at the kernel level.
[Nexus 7 (2013) Original Android Development] ricki13th:
Hey flar2 I'm a huge fan of elementalx kernel and its features. This update has new settings for the display that could improve battery life. I'm all for that... so ideas it possible to tweak those settings right now or do I have to wait for the update to your app thank you and keep up the good work. ?
[Nexus 7 (2013) Original Android Development] DroidIt!:
Actually, N7 has an LCD screen. The screen darkening/using a darker theme or background only works with oled's. The reason being that in order for an LCD panel to work, the entire display must be lit up, even in black areas for the screen to display the blacks. On an oled only the pixels that are showing anything other than "pure" black need to be lit to display an image. Soooo, the entire LCD display is used when it's on and the oled only parts are used where displaying color. So darkening an LCD display won't produce battery savings. You'll want to try a different way with the N7. ;)
[Nexus 7 (2013) Original Android Development] nigelhealy:
So I can't be on the latest version due to bad screen blackness issue. In my case if I'm on latest then if I sent the dimmer option then when I adjust dimness via the slider then mine goes black at about 25%. If I don't enable dimmer then that problem goes away but when I turn screen off and on its then black and I have to turn on off a few times to see anything.

On the earlier version then it behaves well, so this is a bug in new version, I'm sitting out of the current version and will try the next.
[Nexus 7 (2013) Original Android Development] flar2:
I can't reproduce this. I can only guess its the cyanogenmod screen stuff I added, so I'll remove that.
[Nexus 7 (2013) Original Android Development] nigelhealy:
Thanks.

Is there anything I can post like a log file or upload a video showing it?

Note my N7 is the very latest newly made in October, its got that weird problem where I had to use the multirom twrp recovery version.

Stock current ROM, then supersu then elementalx, nothing else.
[Nexus 7 (2013) Original Android Development] gorilla p:
Yeah, I had to setup a couple of those. That was a pain in the Ace.

It took a good amount of searching through "can't mount in twrp" posts before I finally got to the issue.

I wish TWRP would come out with a frickin update for it already. It's a popular device and its already due for 2872 update.

I feel your pain. That was a very frustrating couple days for me...

---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------

It may not be related, but I think I recall dealing with something like this on the Mako. Some issue with Incremental vs exponential brightness settings.

If not, disregard.
[Nexus 7 (2013) Original Android Development] creeve4:
This is a screenshot from today. I refreshed multiple times.
[Nexus 7 (2013) Original Android Development] zwliew:
On CM, I encountered the same screen blacking issue. To fix it, the minimum screen brightness auto-adjustment was bumped from 1 to 2. https://github.com/CyanogenMod/andr...mmit/72c0add5848c0df07bd1ee4433ba043f262a1649
[Nexus 7 (2013) Original Android Development] :
i was wondering, can systemless root be flashed with this kernel? sorry for noob question
[Nexus 7 (2013) Original Android Development] flar2:
Yes, of course
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

A small update to revert cabc and sre options. These seem to have caused display issues for some users.

Download

ElementalX-N7-5.08

ElementalX-N7-5.08-cm

Changes:

-revert cabc and sre
[Nexus 7 (2013) Original Android Development] nigelhealy:
I can't seem to get f2fs on /data to work.

I've tried a few different methods. I've tried

- from a fully working ext4 based system, in TWRP recovery, taking a working /data ext4 backup, format to f2fs, restore, when I boot it takes a long time and eventually comes up reformatted back to ext4 all data lost.

- fresh build, flash stock, then twrp recovery, change /data to f2fs, takes a long time to boot and comes up ext4.

It is as if Android 6.0.1 looks at the /data filesystem and if not ext4 changes it to ext4.

Don't have this issue with /cache, I can format cache to f2fs and boot and its stays f2fs.

Ideas?

[ Update]

Tried a few more times and seems stock 6.0.1 ROM has no f2fs support and even with ElementalX's f2fs kernel support, stock 6.0.1 just reformats the filesystems ext4.
[Nexus 7 (2013) Original Android Development] Hatshipuh:
The ROM has to support f2fs too. There are apps in the Store that can convert your zip into f2fs iirc. Used it back then on my Galaxy Nexus and worked, don't know if it's still working.

Common Custom ROMs support f2fs though.

If you restore an ext4 backup, of course it'll be back to ext4 as it'll format before restoring.
[Nexus 7 (2013) Original Android Development] Co.Tibi:
[MENTION=4684315]flar2[/MENTION] will the sound settings from nexus 5 come to n7?
[Nexus 7 (2013) Original Android Development] flar2:
Is there something wrong with the sound here?

All sound mods do the exact same thing. Nexus 5 just has a quirk that is handled better by one than another.
[Nexus 7 (2013) Original Android Development] DJMartini:
Don't know what was changed but my color settings POP right now on this last update and the screen looks beautiful (like AMOLED) love it! Thank you!
[Nexus 7 (2013) Original Android Development] Co.Tibi:
Sometimes settings won't stick. I thought it had the same issues as the n5.
[Nexus 7 (2013) Original Android Development] yiannis1621991:
Anyone tried this kernel with omniron?

Edit: I am asking because omni requires supersu 2.67 (systemless) for rooting. If i flash elementalx should i flash supersu again?
[Nexus 7 (2013) Original Android Development] gorilla p:
I created and added Kernel Adiuter profiles for latest 5.08 kernel. Added to bit.ly/makostuff.

Is there an easy way to export profiles for EX Kernel Manager?
[Nexus 7 (2013) Original Android Development] Voklav:
can you add this ? :) for us :D

http://xdaforums.com/showthread.php?t=1841759
[Nexus 7 (2013) Original Android Development] flar2:
I build the dvb modules from time to time.
[Nexus 7 (2013) Original Android Development] JMERCIER:
I have a newly purchased Nexus 7 (FLO) with N7-5.08 on it.

Problem: I can't get USB OTG to detect my mouse, this is odd because the same mouse and OTG cable did work on stock ROM (of course without charging). It still charges through the OTG cable.

I have tried toggling fastcharge as well as OTG + charge mode in EX Kernel Manager without any effect.

Please advise how I should proceed.

Thanks
[Nexus 7 (2013) Original Android Development] szili9992:
Anyone having trouble booting the kernel with the latest cm nightly? My nexus 7 is just booting endlessly. Haven't tried flashing without kernel, hat to run to take an exam.
[Nexus 7 (2013) Original Android Development] Blaat1:
I have exactly the same device, software and problem. Also USB stick is not detected using OTG cable, however did work on stock rom without charging.

Any help is very much appreciated!
[Nexus 7 (2013) Original Android Development] lollyjay:
Hi fwiw I'm having no problems with USB stick on OTG cable.
[Nexus 7 (2013) Original Android Development] justmiike:
I'm having an issue where my Nexus 7 won't pick up the OTG USB. I solved it a few times by toggling OTG + charge mode on and off in EX Kernel Manager. But, this doesn't work anymore. StickMount doesn't find anything to mount.

Is there something I'm doing wrong? I'm on ElementalX-N7-4.05. Is there another way to enable OTG?
[Nexus 7 (2013) Original Android Development] JoseRebelo:
On official CM13, clean install with just SuperSU + ElementalX 5.08 + Gapps, the screen won't rotate. It used to rotate again after reboot, but now it is just stuck. CPU-Z finds the sensors, but there are no values. I installed AOSP + ElementalX and the problem is gone.

Any way I can find out what is causing this? I saw some reports of the same issue, but no solution.
[Nexus 7 (2013) Original Android Development] flar2:
You need to use the cm version
[Nexus 7 (2013) Original Android Development] JoseRebelo:
Yes, sorry if I wasn't clear enough, but I was using the cm version on cm13 and the non-cm version on AOSP. I had been using the same cm/kernel combo for some time, the sensors stopped working out of nowhere, and they wouldn't be fixed by a reboot as they used to, not working even after a clean rom install.
[Nexus 7 (2013) Original Android Development] JMERCIER:
Any reply for those of us with OTG issues?
[Nexus 7 (2013) Original Android Development] FrenchSparda:
Dont forget if OTG + charge is enabled, phone must be powered with wall charger otherwise OTG will not work, And devices not being recognized....as stated in Aroma installer ;)
[Nexus 7 (2013) Original Android Development] flar2:
No. Otg works. The otg + charge mode works, but with quirks.

It's all been addressed ad nauseam in this thread.
[Nexus 7 (2013) Original Android Development] dadeo1111:
I had the same experience and it ended up being a hardware issue, but easy to fix on my Nexus 7 2013. Adjust your search accordingly for your device and you may find similar solution for yours.
[Nexus 7 (2013) Original Android Development] Kmias:
I tried that too. It seems that cm13 homescreen is not rotatable. Im back with pure nexus + elementalx kernel
[Nexus 7 (2013) Original Android Development] nigelhealy:
I had that problem. It was cm13 Trebucket launcher. If you go to Play Store and install Nova launcher then you get rotated home screen.

Not ElementalX fault. No need to dump CM13
[Nexus 7 (2013) Original Android Development] sunilknj.273:
i have nexus 7 2013 lte(deb) version and stock rom.I overclock cpu to 1898mhz and gpu at 477mhz and other things are default.

but after flash its shows force close google play apps specially google play service again and again.

please help.........i used to play heavy games and play lots of apps at times....for which overclocking is required
[Nexus 7 (2013) Original Android Development] flar2:
That's not a kernel problem. However, stuff like that can happen due to overclocking.
[Nexus 7 (2013) Original Android Development] JMERCIER:
I suggest adding a note on your website where it's listed as an optional feature, implying that it works reliably:

"optional USB OTG + charge mode".

Not sure how I'd expect "works, but with quirks" from that. If I had known that the feature I need most was hit and miss I could have gone another direction.

I purchased your kernel manager to support you sight unseen and I don't have a huge problem with that but I have to say I would have appreciated full disclosure in this case. You would have received my donation had I have been able to use your kernel for my project as is fair but honestly I'm annoyed that I spent time trouble shooting a feature that's listed as if it's fully functional.
[Nexus 7 (2013) Original Android Development] flar2:
It does work for my needs and does just what it says. I'm sorry if it doesn't work for your specific needs but I am only one man and I work on this in my spare time. All of my spare time. If I had more time I would perfect it. But I don't have more time, so I have to prioritize my projects. This one would require many hours and there are only a relatively small number of people who need this. Plus there are two solutions available. One is free and refenced here in this thread if you search. The other is another kernel, which costs $60 dollars or something like that.
[Nexus 7 (2013) Original Android Development] JMERCIER:
Please don't take my comments as adversarial or mean spirited, they were not intended that way. I understand and appreciate independant developers such as yourself and I do realize I'm not discussing a commercial product here. My main point is that if a feature is listed it should be clearly noted that there are/may be issues getting it to work, if that had been the case I could have decided whether to take my chances or go in another direction - nobody wastes any of their time that way.
[Nexus 7 (2013) Original Android Development] valk791:
Hi [MENTION=4684315]flar2[/MENTION]! Hi guys!

I have a deb in fix installation car. I use the zooper dac through OTG to give the signal to the amp. The dac works well but only after tablet boot because the kernel doesn't support hot plug otg. Do you have in plan to implement that feature? It would be great because many many people are installing N7 in the car as head unit and up to now only timurs kernel has the hot plug option. Timurs kernel is fine but your is even better because of continous updates and the possibility to suggest what implement. Please check this out.
[Nexus 7 (2013) Original Android Development] Aerobatic:
I somehow hesitate to interfere into discussion, considering answers from both [MENTION=4684315]flar2[/MENTION] and [MENTION=4190734]FrenchSparda[/MENTION], but.... sometimes simple obvious facts are just skipping our minds...

So, don't beat me for a question, I'm just trying to help:

- Is it not the case that You have switched "OTG+USB charge" ON, and then are trying to plug-in a mouse via a simple OTG-cable?

- Not an Y-cable with external +5V on, nor a simple OTG cable in pair with active USB-HUB with external +5V on?

If this is the case, there won't be +5V available for mouse to operate. Power is taken either from N7II when option is off, or should come from external source when option is on.

And yes, our beloved ElX kernel does not have special tricks implemented to react on ext/power on/off as needed e.g. for in-car installation, as [MENTION=4684315]flar2[/MENTION] have already mentioned above and as is discussed in appropriate threads.
[Nexus 7 (2013) Original Android Development] pk-sanja:
[MENTION=4684315]flar2[/MENTION] Would it be possible to add a more heavy l2 bus OC to get a little nice CPU boost for your wounderful kernel. It should be safe on most socs. I know Glitch does have this Option... If not then still nice kernel :).

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] nigelhealy:
I edited the zip's boot/edit_ramdisk.sh to uncomment the F2FS on /data and /cache.

It would be good if you could this in the official release, as some people might find it tricky to edit the zip file's contents, it took me a few goes to find a method which worked (simply editing doesn't work, have to add the edited file back in after you saved is somewhere).

Why is F2FS commented out anyway?

I've just done an Antutu benchmark, stock ROM+ElementalX I got score around 34000, a custom tuned ROM (Pure Nexus) and I got the same score. I then switched /data to f2fs and no performance gain, and when I switched /cache to f2fs then the score shot up to 45000, it tracing back to I/O performance.
[Nexus 7 (2013) Original Android Development] flar2:
I had to remove those lines because it broke encryption.

I left them commented just for situations like yours.
[Nexus 7 (2013) Original Android Development] nigelhealy:
Attached is the edited N7 ElementalX zip with the /data and /cache allowed with F2FS.

How to use:

- You're going to lose all data, everything, so anything important backup via OTG or adb pull/push.

- boot into recovery. I had to use 2.8.7.0 as 3.0.0.0 failed for me.

- do a FULL wipe first, this will scrub any encryption you might have had

- Do some more wiping, in wipe, go into advanced, select everything (dalvik, system,..... internal data) and WIPE

- then click on /data, advanced wipe, change filesystem, select f2fs, wipe. Check it is saying mkfs.f2fs

- do same with /cache

- install the attached zip

- go back into wipe, select cache and ensure it is still f2fs, if ElementalX's wipe of cache defaulted to ext4 then you have to repeat the change to f2fs for /cache

- reboot

Then go through then setup, install your apps, or restore from backup as required.
[Nexus 7 (2013) Original Android Development] steeven01:
Hey guys so I've been getting a nexus 7 2013 ready to install in my car. I'm using stock rom 6.0.1 with elementalx. With otg charging enabled.

I use fastboot oem off-mode-charge 0 so the tablet boots up when I turn on my key. Once the tablet is loaded and shows the home page it doesn't show that its charging unless I turn external power off and back on or I unplug and replug usb cable in. This happens everytime the tablet is booted from an off state that it doesn't see its being charged. I've tried a cyanogenmod rom with elementalx but had the same problem. I want the tablet to see there's a charge on boot so I don't have to do anything and then it will shut down when external power is turned off.

My setup is nexus 7 2013 mounted in dash. Otg y cable to USB hub with sdr stick and USB dac. Otg y cable power comes from a cigarette lighter charger that turns on when key is turn on.

Any ideas if I'm doing something wrong or is this a limitation of the kernel?
[Nexus 7 (2013) Original Android Development] Hatshipuh:
Oh so that's why it was bootlooping for me...

Tap-a-talked from my Nexus 7
[Nexus 7 (2013) Original Android Development] 0xcafebabe:
I had the same problem with elementalx and switched to the Quanta kernel.
[Nexus 7 (2013) Original Android Development] lollyjay:
I take it that this is only for AOSP 6.0.1 ROM?
[Nexus 7 (2013) Original Android Development] nigelhealy:
It's the current AOSP version yes just the text edit to one file to allow F2FS
[Nexus 7 (2013) Original Android Development] nigelhealy:
F2FS for CM version

It is a simple edit for anyone to do but here is it edited for CM. So this allows for F2FS in /data and /cache but from what Flar says this will break encryption. Not tested, I don't have CM.

Most Nexus 7 won't have encryption, because it isn't force like on say a Nexus 9. It took me a real effort to keep forced encryption off on my N9. It is easier with non-stock ROM like PureNexus. CM has forced encryption but I think it doesn't happen on N7?

F2FS improves write performance. The puzzle for me is /cache is meant to be written to infrequently (definition of "cache") I'm guessing but the puzzle for me is that when I converted /data to F2FS, I saw no performance gain, but when I converted /cache to F2FS I saw a huge gain. Odd. Changing /data to F2FS loses all data but changing /cache to F2FS is easy, its just advanced wipe, change filesystem.

Anyhow, reminder, you need a ROM which has F2FS. I think CM does, but say PureNexus which I'm on now does.
[Nexus 7 (2013) Original Android Development] lollyjay:
Hey thanks. I need to confirm that cm13 supports f2fs. By the way were you able to restore the twrp backup to the f2fs /data partition?
[Nexus 7 (2013) Original Android Development] nigelhealy:
Depends.

Encrypted /data partitions, I once attempted to restore once I'd disabled encryption, it nearly almost worked but the screen lock was on and could not be unlocked, despite notifications etc showing the data was restored and otherwise working.

Most N7 won't be encrypted so then if you use TWRP backup/restore it does work but complains about different filesystems.

Probably the best cleanest method is use Titanium backup as that is sitting at the top above the filesystem level.
[Nexus 7 (2013) Original Android Development] lollyjay:
Yes you are correct.