yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] timrock:
It doesn't work for me with carbon and this rom. I need to mount it with stick mount

Disregard. It works fine. Sick mount not needed
[Nexus 7 (2013) Original Android Development] hasenbein1966:
Yeah, any kind of toggle-ability via app would be really great.
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
Or the regular right-left sweep to sleep the device keeping DT2W/S2W on and a swipe from left to right to sleep the device using the power-button style :cool:
[Nexus 7 (2013) Original Android Development] anko184:
Except that i am using a rom with usb stick support: http://xdaforums.com/showthread.php?t=2447521

Proof: https://www.dropbox.com/s/oi0twwb5426y6s5/2013-10-17 09.48.19.png
[Nexus 7 (2013) Original Android Development] goofball2k:
Maybe it is something with the cable, not 100% sure as I was also using AOKP from scar45 and could not get any usb stick support from the ROM directly. It wouldn't mount automatically, nor when I tried to force it in settings -> storage. I only have one cable so I didn't get a chance to try another, though it is weird that this cable has worked on previous N7, this N7 with other AOSP based ROM's, with stickmount on stock ROM's.
[Nexus 7 (2013) Original Android Development] anko184:
I'm pretty sure that is not the cable cause i tested with two different cables that both work on my phone.

But in N7 i only get read access and only with the use of stickmount. Without stickmount nothing the N7 sees the stick but doesn't mount it.. :crying:
[Nexus 7 (2013) Original Android Development] Merkoen:
Having a few issues.

I've tested all; ElementalX 1.6, 1.7 Beta and currently using the 1.8 Beta, but i still can't charge through my OTG cable while i mount USB devices to my nexus.

if I reflash the kernel with out checking "OTG + Charge", then i can use USB Devices, if i Check it, then i cant use it.

Anyone know whats going on? Shouldn't I be able to use both Charge + USB Devices at the same time using the OTG Y Cable? :)
[Nexus 7 (2013) Original Android Development] Mayday_XL:
The v1.7/ 1.8 uses more energy (Deep Sleep), than the 1.6 :confused:
[Nexus 7 (2013) Original Android Development] Spyr0s:
I just tested one NTFS formatted USB stick on JSS15R and it mounts with Stickmount, it's visible with the file exporer on /sdcard/usbStorage/sda1, i can listen to an mp3 but i can't write. Permissions and ownership seems ok, definitely something is not right.
[Nexus 7 (2013) Original Android Development] Philaphlous:
Hey guys real quick, what's the latest version of the build? I'm on jss15j...
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
1.8-beta

http://xdaforums.com/showthread.php?p=46479549

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] Philaphlous:
Well apparently I didn't know that ota updates fail when you have a custom recovery? I downloaded the stock kernel for js155j build that I've got and that fails to flash back to stock... So my only real fix is to unroot, factory reset, install all the ota updates, then unroot? Ugh, what a hassle...
[Nexus 7 (2013) Original Android Development] KedarWolf:
Dark Jelly And 1.8

Will the 1.8 beta work with the Dark Jelly ROM anyone know? Reading it has trouble with the latest CM 10.2s.:confused:

Peace.
[Nexus 7 (2013) Original Android Development] timrock:
did you try flashing stock recovery using wugs toolkit?
[Nexus 7 (2013) Original Android Development] GSLEON3:
You know you can flash just about anything via fastboot, right?

>fastboot flash recovery recovery.img
[Nexus 7 (2013) Original Android Development] Philaphlous:
Im gonna research it next week and figure it out, I've got wugs toolkit but I gotta reinstall it, I just updated to win 8.1...
[Nexus 7 (2013) Original Android Development] flar2:
^^I don't know much about OTA's, but before you wipe everything try restoring the stock boot.img and recovery.img and see if it will apply.

The kernel provides the ability to do it, whether this happens automagically or not depends on software (ie: ROM or apps)

Someday I'm going to make an app. So far I've gotten as far as "Hello World"

Make sure you're in usbhost charge mode (/sys/module/msm_otg/parameters/usbhost_charge_mode should be set to Y)

Also make sure you have the correct cables. Does OTG work with your cable in regular self powered mode?

Then make sure you have the power hooked up to the Y-cable first before you plug the otg adapter into the tablet. If it doesn't work, pullout the otg adapter and plug it in again.

Not for me, check your apps and wakelocks. I haven't done any powersaving changes since version 1.5 (other than the s2w toggle with power button)

I'll test this later, but I think it's something to do with the system, not the kernel. Like I said earlier, the kernel just provides the ability to mount NTFS. The other thing could be that NTFS write support is very limited in linux. If you need additional functionality look for the NTFS-3G module.
[Nexus 7 (2013) Original Android Development] Merkoen:
Thanks.

Wasnt aware that i needed to go into USBHost charge mode. thought everything was configured during the installer \ setup wizard. :)

the "OTG Adapter" is included in the Y cable (normally) right? I don't need another OTG adapter that is connected to the tablet, then to the Y cable? :)

Oh and the usbhost_charge_mode - just open it in Text Edit and change the content to "Y" and save and then retry?

thanks for clearingfying :)
[Nexus 7 (2013) Original Android Development] flar2:
Yes. But if you selected that option in Aroma, it should be set to Y already.

Could somebody double check to see if that install option is working correctly?

I have a separate y-cable and otg adapter. The otg adapter accepts a usb plug and the other end connects to the tablet's usb port. The Y-cable plugs into the otg adapter and has two leads coming out: one is a regular usb plug that you connect to a power source, and the other accepts a usb plug (for the perhipheral device)

Here's a pic from my old phone:
[Nexus 7 (2013) Original Android Development] Merkoen:
Oh. Looks like you have a different Y cable than what i do.. Mine is just a Micro USB B, Micro USB B Female and a USB Female.

Will see if i can get my hands on same as you, maybe then i can get it to work :)
[Nexus 7 (2013) Original Android Development] r00ler:
I'm using this kernel and seeing about 11% battery drain for 24 hours idle. My tablet is going in to my car permanently in the near future and I'd like to extend idle time as much as possible. I've got tasker configured to shut off the radios when power is removed, but everything else I've experimented with hasn't gained me any battery life.

Any suggestions on squeezing more life out of idle time?
[Nexus 7 (2013) Original Android Development] jdkadius:
Do you have s2w or dt2w on?
[Nexus 7 (2013) Original Android Development] r00ler:
Yes - having them available is important to the installation as I won't be able to access the physical buttons. If they're a major power hog I suppose I could rely on tasker waking and sleeping the screen based on USB power and just never having it sleep when the car is on. Would rather not have to do that though.
[Nexus 7 (2013) Original Android Development] roofrider:
I guess you have this one. http://www.amazon.com/Micro-Cable-P...B00CXAC1ZW/ref=pd_cp_pc_0/185-8451351-2964109 Can't get it to work huh?

Maybe flar can come up with something to support these kinds of cables too?

I've been looking looking for a otg cable too, guess i'll have to go with separate OTG and USB Y cables like flar has.
[Nexus 7 (2013) Original Android Development] Synergy510:
Just wondering if having the smart cover on, or just magnetic lock in general disables s2w/dt2w like pressing the power button.
[Nexus 7 (2013) Original Android Development] hasenbein1966:
Oh oh, not a good idea!

You'll NEED the power button if Android crashes and you have to reboot by pressing the power button very long!
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
Yes, flash ElementalX 1.6. As another user above also noticed: the latest version consumes more battery than 1.6, that is, well apparently at least for us.

Yesterday using 1.8 the tablet lost 10% of battery in 12 hours. This night, same settings, same frequencies, only another kernel, it lost 3% in 10 hours. That's with DT2W on (S2W off though).

No idea why as nothing has been changed power-wise in the kernel but maybe worth a try, if you don't need the new 1.7/1.8 features. Maybe it's all placebo, don't know, for now sticking with 1.6 though :cool:
[Nexus 7 (2013) Original Android Development] roofrider:
Personally, i'd prefer to disable dt2w etc through the power menu instead of the button (cmiiw, but this can only be implemented in the rom sadly :(), cuz i have a habit of pressing the power button to lock the device instead of letting it timeout and auto-lock. Guess i should reduce the screen off timeout. But an app would be nice too. :D
[Nexus 7 (2013) Original Android Development] hasenbein1966:
I think it should be possible to install ElementalX without the wake functions, then install the app "Touch Control" from Play Store and then from that app enable / disable wake functions, or am I wrong?

Would that solution have disadvantages in regard to battery life?
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
No. The device will always have to check if there is any swyping/tapping going on so will use (some) more juice anyway. Only with the touch screen/soft buttons completely "off" you will have the best possible idle battery drain.
[Nexus 7 (2013) Original Android Development] hasenbein1966:
OK, I formulated my question misleadingly... :silly:

I meant: Will having the "Touch Control" app consume more battery than ElementalX's built-in wake functions?
[Nexus 7 (2013) Original Android Development] Spyr0s:
You were absolutely right, after installing latest PAC stable, everything is working out of the box (without stickmount). I cant mount NTFS USB and read/write, it seems that there is a problem with SuperSU on stock roms, while CM's Superuser handles it right.
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
There's only one way to find out for sure... ;)
[Nexus 7 (2013) Original Android Development] timrock:
i turned off the battery save option, but it still wont show a charge past 93.
[Nexus 7 (2013) Original Android Development] tni.andro:
Do a:

cat /sys/devices/i2c-0/0-006a/float_voltage

in a terminal (or look at the file with something like ES Explorer). If it shows 4200, the battery save option is still enabled. If it shows 4300, you should charge completely.
[Nexus 7 (2013) Original Android Development] timrock:
it shows 4200, can i change it manually?
[Nexus 7 (2013) Original Android Development] tni.andro:
You can - but that will only last till the next reboot.

Take a look at:

/system/etc/elementalx.conf

It should say:

##### Battery Life Extender Settings ######

# 4200 = 93% charge

# 4100 = 83% charge

# 4000 = 73% charge

# 0 for full charge (default)

BLE=0
[Nexus 7 (2013) Original Android Development] timrock:
it says that, but BLE=4200
[Nexus 7 (2013) Original Android Development] flar2:
Change it to BLE=0
[Nexus 7 (2013) Original Android Development] roofrider:
Someone help a noob understand.

can't create /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq: No such file or directory
can't create /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq: No such file or directory

Is something amiss here or is it all fine?
[Nexus 7 (2013) Original Android Development] flar2:
Nothing to worry about
[Nexus 7 (2013) Original Android Development] hasenbein1966:
Er... in the configuration file there is also a flag for sweep2wake, dt2wake etc...

Shouldn't it then be possible to toggle these wake settings during runtime by, for instance, calling the 99elementalx init file from Tasker (after toggling the value in the conf file, also by Tasker)??

Or does running 99elementalx cause interruption (e. g. kind of reboot)?
[Nexus 7 (2013) Original Android Development] tni.andro:
You can do that. You can also just directly write to the sysfs files (e.g. '/sys/android_touch/sweep2wake' and '/sys/android_touch/doubletap2wake'), if you don't need the settings to survive a reboot.
[Nexus 7 (2013) Original Android Development] roofrider:
I don't use tasker, but running the 99elementalx file wont cause a reboot.
[Nexus 7 (2013) Original Android Development] hasenbein1966:
Ah, I just looked into the 99elementalx file.

Shouldn't it suffice to run a script with

echo 1 > /sys/android_touch/doubletap2wake;

echo DoubleTap2Wake enabled >> /data/local/tmp/elementalx.log

in it for enabling DT2W during runtime? (And the same, only with "echo 0", for disabling it.)

This would be a very simple solution - just create a widget or a power toggle which runs the script...
[Nexus 7 (2013) Original Android Development] roofrider:
^^This.

If you wish to change the settings on the fly and want it to stick after a reboot you also need edit the conf file to reflect the changes made in the /sys/android_touch/ files.
[Nexus 7 (2013) Original Android Development] flar2:
You don't need the script, to change on the fly you just directly edit the /sys/android_touch.... files

The other stuff is to set things automatically at boot based on your installer choices. Because I'm an old fashioned linux guy, I put a config file in /etc, a script in /etc/init.d and a log file in /data/local/tmp/ (not sure where else to put it, I don't see /var/log/ directory on Android)

It keeps things clean and organized
[Nexus 7 (2013) Original Android Development] roofrider:
Hmm.. sounds simple, one widget for disabling it before sleep and another one for enabling it in the morning. Echoing this in the log isn't necessary because we know is happening when we run that script, instead i'd echo this change to the .conf file so it's a clean change but this will be a pita if i wish to change the other settings like s2w etc. :|

I'm not good in scripting, i wonder if there is a way to change DT2WAKE=1/0 alone in the conf file without having to echo everything else that's in it.

But how to run a script from the power menu (i'm assuming that's what you meant by power toggle), i'm on Carbon but have not explored all of it's options yet.

I guess it's laziness doing the talking, a script manager widget will do this change in a single touch iirc. :D
[Nexus 7 (2013) Original Android Development] thecapitalr:
Sorry for the newbie question but Im a little confused. Does this work with the newest PAC man builds 4.3.1? Thanks!
[Nexus 7 (2013) Original Android Development] Spyr0s:
It works flawlessly
[Nexus 7 (2013) Original Android Development] flar2:
Since version 1.7, all you have to do is turn off the screen with the power button and s2w/dt2w are disabled. They are re-enabled when you turn the screen back on.
[Nexus 7 (2013) Original Android Development] Slavon-93:
AROMA is making me crazy. Installed v1.8 twice and twice /etc/elementalx.conf is empty. Looks like the only way to make it right is to write everything manually.
[Nexus 7 (2013) Original Android Development] Gareee:
I don't see anything in the instructions for the dvb modules. what are they, and do I need to install them?

[EDIT: found the mention about them in the thread]

(coming back now that I can with the 10-4 kang cm)
[Nexus 7 (2013) Original Android Development] KedarWolf:
ElementalX Not Working On Dark Jelly ROM.

I enabled AOSP kernel support when installing the Dark Jelly ROM, tried both 1.6 and 1.8, really terrible lag even when I have it on stock CPU and GPU settings. :(
[Nexus 7 (2013) Original Android Development] GialanG:
The same for me, I think it's the incompatibility with multirom. Are you running multirom too?

Can someone give me the content of elementalx.conf please?
[Nexus 7 (2013) Original Android Development] BigJPNut:
After you click finish in Aroma let your device sit for minute. Then try to reboot. Its the only thing that worked for me. That and wiping cache and dalvik before install. Hope this helps! :thumbup:

Edit: Also delete your elementalx.conf file before installing.
[Nexus 7 (2013) Original Android Development] jlevy73:
And what a huge improvement in battery life I have seen. I'm currently on 4.5 days @ 17% left (granted only 1.5 hrs on screen time). Before this addition I was getting probably 2 days worth before I had to charge.
[Nexus 7 (2013) Original Android Development] chrisnk204:
My screen is freezing eveytime I get a notification. Is this a known issue? I have mostly everything stock I'm over clocked to 1.6 and the GPU is at 450 that's the only changes I chose
[Nexus 7 (2013) Original Android Development] hasenbein1966:
Then probably your individual device can't handle the overclock... happens...
[Nexus 7 (2013) Original Android Development] Slavon-93:
I'm not using multirom, just a usual TWRP.

Here's my elementalx.conf. I made it from scratch.

#############################

#ElementalX Configuration

#For settings to take effect, you must execute /etc/init.d/99elementalx as root. If you don't know how to do that, just reboot.

#S2W
##### Sweep2Wake Settings #####
# 0 to disable sweep2wake
# 1 to enable sweep2wake and sweep2sleep (default)
# 2 to enable sweep2sleep and disable sweep2wake" >> $CONFIGFILE

SWEEP2WAKE=0

#Shortsweep
##### Shortsweep Settings #####
# 0 to disable Shortsweep
# 1 to enable Shortsweep

SHORTSWEEP=0

#S2W Orientation

##### Sweep2sleep Orientation Settings #####
# 0 to enable portrait and landscape
# 1 to disable sweep2sleep landscape mode
# 2 to disable sweep2sleep in portrait mode

ORIENTATION=0

#DT2W

##### DoubleTap2Wake Settings #####
# 0 to disable DoubleTap2Wake
# 1 to enable DoubleTap2Wake

DT2WAKE=1

#S2W Power key toggle

##### DoubleTap2Wake Settings #####
# 0 to disable DoubleTap2Wake
# 1 to enable DoubleTap2Wake

PWR_KEY=1

#USB Fastcharge
##### Fastcharge Settings ######
# 1 to enable usb fastcharge
# 0 to disable usb fastcharge

FC=0

#Magnetic on/off
##### Magnetic on/off Settings #####
# 0 to disable Magnetic on/off
# 1 to enable Magnetic on/off

LID=1

#exFAT support
##### exFAT support #####
# 0 to disable exFAT support
# 1 to enable exFAT support

EXFAT=1

#Fsync Settings
##### fsync Settings ######
# 1 to enable fsync
# 0 to disable fsync

FSYNC=1

#USB Host mode charging
##### USB OTG+Charge Settings ######
# 1 to enable USB host mode charging
# 0 to disable USB host mode charging

OTGCM=0

#Battery life extender

##### Battery Life Extender Settings ######
# 4200 = 93% charge
# 4100 = 83% charge
# 4000 = 73% charge
# 0 for full charge (default)

BLE=4200

#Thermal Control
##### Thermal Settings #####
# 0 for default thremal throttling
# 1 to run cool
# 2 to run hot

THERM=0

#GPU Governor
##### GPU Governor #####
# 1 Ondemand (default)
# 2 Simple
# 3 Performance

GPU_GOV=1

#GPU OC
##### GPU Settings ######

GPU_OC=477

###############################
[Nexus 7 (2013) Original Android Development] dpaik:
battery life is AMAZING on 1.8 beta...thx so much and awesome work in implementing the DT2W/S2S/S2W toggle with the power button...awesome....this kernel gives me superb deepsleep battery life....device has been off the charger for 8.5 hrs....5% used...17 min of screen on time...craziness...1.6 wasn't that great....1.4 was much better for battery life...but 1.8 takes the cake so far...nice job man :highfive:
[Nexus 7 (2013) Original Android Development] cobyman7035:
damn I'm on 1.6now, I don't usually install betas

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] jlevy73:
Definitely install, the battery life on 1.7/1.8 is rudunkilious. Make use of the power off button to kill S2W/D2TW when not needed. That added about 2X the amount of battery life for me.
[Nexus 7 (2013) Original Android Development] SkaDiZ:
Hi guys, when I check my device on Trickster Mod I notice that only 2 cores are running instead of 4 cores. I tried to swipe around the menu and it still showing 2 core running at Max 1728 Mhz. Is this normal?

By the way, [MENTION=4684315]flar2[/MENTION] is it possible to implement s2w/dt2w disable when the screen off by magnetic? If magnetic ON, the screen will on itself when we open the cover, so touchscreen is totally useless over here...
[Nexus 7 (2013) Original Android Development] cobyman7035:
I have magnetic cover too, but it only works if wifi is on all the time

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] SkaDiZ:
Sorry I think you misunderstand what I mean.. To be clear I am talking about the s2w/dt2w function disable when we close our magnetic cover.. on v1.8 we are able to disable wake touch by pressing the physical power button..
[Nexus 7 (2013) Original Android Development] hasenbein1966:
If you had read the conversation about the config files from yesterday, you would know that it's possible with a little scripting and Tasker.

Programming is fun, try it!
[Nexus 7 (2013) Original Android Development] Draygon:
1. Which app are you guys using to configure this kernel?

Is there any app which let's me activate doubletap2wake?

2. Is it also possible to calibrate my screen color?
[Nexus 7 (2013) Original Android Development] pietropizzi:
cobyman's right, some Nexus 7 2013 have problems with waking up screen with a magnetic cover. They go to sleep with closing the cover but they don't wake up again - wifi has to be enabled and connected or bluetooth must be enabled - a known bug. So it may be an option but not a rule.
[Nexus 7 (2013) Original Android Development] SkaDiZ:
Trickstermod

---------- Post added at 03:48 AM ---------- Previous post was at 03:39 AM ----------

I get what you mean, I know it's not practical but if you disable s2w/dt2w through power button, you still need push the power button to wake up the device because the wake function already disable.. so if we could implement magnetic cover to disable the s2w/dt2w, we still can do the same thing to wake the device by pushing the power button.. at least we don't need to hit the power button to disable s2w/dt2w...
[Nexus 7 (2013) Original Android Development] DeDua:
Does magnetic sensor dissables "s2w/dt2w" options while device is off? i would prefer that to save more energy.
[Nexus 7 (2013) Original Android Development] buckeye_jeff:
Even if I use the power bottom to turn off my N7 and disable the dt2w/s2w it still wakes up by the magnetic when I open the case.
[Nexus 7 (2013) Original Android Development] SkaDiZ:
I didn't say that you can't disable by power button but wouldn't it be easier if you could also disable s2w/dt2w by just closing your magnetic cover? ? ? Why would you want to press the button and close the casing? ?

---------- Post added at 06:26 AM ---------- Previous post was at 06:24 AM ----------

I don't think it have... still waiting for TS reply.... would be great if can disable by magnetic cover too...
[Nexus 7 (2013) Original Android Development] WeRSpecialPeople:
Does this kernel support loop255 needed for LinuxonAndroid?