yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] dave-:
Just flashed the 1.8 beta on my LTE running latest stock ROM (rooted) and at the end after saving the log file, you hit finish, see aroma drop back to TWRP and the screen turns off. First time I had to force off holding the power button as it wouldn't respond. Just flashed again with same options and it did it again. This time plugged it into my PC and was able to communicate via ADB and reboot to bootloader. Just flashed another 2 times, 4th and final try didn't blank screen. [MENTION=3735978]Spyr0s[/MENTION] was right, 4th time I flew through it and beat the twrp screen timeout. All the other times I sat there reading the options and thinking about it lol.

Moving on, options taken: default cpu core/frequency, elementalx, 850 undervolt, default thermal, stock gpu, default s2w options, enable exfat & battery life. The install result screen showed enabling usb fastcharge after the s2w options but neither exfat or battery life. So thinking just an aroma config typo?

But don't think the shortsweep option is taking hold:

adb shell cat /etc/elementalx.conf
SHORTSWEEP=1

even after a reboot:

adb shell cat /sys/android_touch/shortsweep
0

I also don't have a log file generated?

root@deb:/ # ls -l /data/local/tmp/
ls -l /data/local/tmp/
-rwxrwxrwx root root 20116 2013-10-20 22:10 init.rc
drwxrwxrwx root root 2013-10-20 20:44 usbotg_debug
root@deb:/ #

I should add that I had trickster mod installed but removed it and have nothing other than the 99elementalx file in /etc/init.d
[Nexus 7 (2013) Original Android Development] Spyr0s:
Just disable screen timeout in twrp settings.
[Nexus 7 (2013) Original Android Development] spajdr:
Main download link is down.

Are there any mirror links?

Thanks in advance

Spajdr
[Nexus 7 (2013) Original Android Development] GoldElocks:
Has anybody tried experimenting with the gpu governors (ondemand & interactive)? I just noticed the interactive governor for gpu. Also, is there an app to monitor gpu frequency in real time? Basically I'd like to compare behavior between ondemand and interactive gpu governors. TIA

Sent from my N7 Flo
[Nexus 7 (2013) Original Android Development] hasenbein1966:
I have Trickstermod, and it's not possible to switch the GPU governor to something else than the default ondemand. It always switches back immediately.
[Nexus 7 (2013) Original Android Development] BigJPNut:
Try CoolTool in market

---------- Post added at 07:02 PM ---------- Previous post was at 07:01 PM ----------

Reflash kernel...im running simple governor and its nice
[Nexus 7 (2013) Original Android Development] mihaianti:
1.8 beta

since i had installed version 1.8 beta i have no deep sleep , only 384 mhz , anyway battery life is good .Wakelock detector say that battery widget wake most frequently the tablet so i unistall battery widget , reboot , and now it seem that i have depp sleep .All in all very good kernel my usb modem zte mf 110 also work with ppp widget.
[Nexus 7 (2013) Original Android Development] codenamezero:
could you implement the Wheatley governor?
[Nexus 7 (2013) Original Android Development] cobyman7035:
can anyone tune up my setttings?

I'm on interactive cpu

thx

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] codenamezero:
What do you want as a tune up...? better battery or better performance...?

If anything, just set Boost and Input_Boost to 1, that should be a no brainer for performance the rest u should just try them out, but you probably won't notice much difference. XD
[Nexus 7 (2013) Original Android Development] Windsor1959:
Since installing 1.8, I have encountered one minor glitch, which may not even be kernel-related. I'm also running CleanROM 1.7, if that helps. My glitch is that, when I recharge my N7, the battery charge indicator stops at 94%. I let my N7 run down to 19% battery, which took almost three days of occasional use (damned excellent battery life!), and it still stopped at 94% when I recharged it. Should I even be concerned? Could anyone suggest something else I can try? Thanks!
[Nexus 7 (2013) Original Android Development] roofrider:
vvvv

To disable it:

*Open /etc/elementalx.conf

*Find "Battery Life Extender Settings"

*Change BLE=4200 to BLE=0

*Reboot.

On Carbon i never really notice it, once it reaches 93/94% it says charged. It doesn't show 94% or anything to indicate that it has not reached 100%.
[Nexus 7 (2013) Original Android Development] Windsor1959:
Okay, I knew about the battery life extender feature, but didn't know that it would produce the 94% effect. No need for me to disable it if it is doing what it was designed to do! Thanks.
[Nexus 7 (2013) Original Android Development] banny7000:
My battery life on 1.8 occed at 1.7ghz. outstanding not had this much battery since my Xoom in fact better than that.
[Nexus 7 (2013) Original Android Development] KedarWolf:
Fix For Elementalx.conf Being Empty

If you have your ROM or Trickster mod etc. set to apply CPU governer settings or any other settings at boot when you install the ElementalX kernel the elementalx.conf file will be empty and the settings you choose when you install the kernel will not take effect.

The fix is to turn off the 'Apply On Boot' settings, fully reboot your ROM, then after you have rebooted check to make sure any 'Apply At Boot' settings are disabled. Then after you are sure they are AND have fully rebooted once, reboot into recovery and reinstall the kernel. Check your elementalx.conf and the settings you applied should be there now. If you don't do this this I don't believe the settings you use when you install the kernel actually take effect. I know in Trickster Mod the settings I chose do not show as enabled when I installed the kernel with the Trickster Mod 'Apply On Boot' enabled and the elementalx.conf was empty.

AFTER you have done all this then you can make changes in Trickster Mod or your ROM and use the 'Apply On Boot' settings. The elementalx.conf will still be there with the settings your choose and the Trickster Mod etc. will be applied after. After I do all this I always set a delay in Trickster Mod when I use 'Apply On Boot' of at least 30 seconds so that it lets the elementalx.conf settings to be enabled first, then the Trickster Mod settings.

Hope this helps some. :D

Peace.
[Nexus 7 (2013) Original Android Development] tni.andro:
That's definitely not the issue. Trickster Mod doesn't have any influence on the config file being written by Aroma or not. EXT4 traditionally has issues with empty files when the file system isn't synced properly (e.g. when Aroma hangs).

---------- Post added at 09:58 PM ---------- Previous post was at 09:50 PM ----------

Yes, it's expected. The battery gauge is independent from the charger and shows the charge level relative to the maximum charge the battery can have (at the full 4.3V charge voltage). It doesn't take the lower charge termination/voltage from BLE into account.
[Nexus 7 (2013) Original Android Development] galza:
tried to install the kernel latest version on my flo with vanir rom and i get inverted colors...any fix for that?
[Nexus 7 (2013) Original Android Development] KedarWolf:
Why Does The Op Say Trickster Mod Can Interfere Then?

Then why does it say right in the OP "If settings are not sticking, make sure the file permissions for /etc/init.d/99elementalx are set to execute. Every time the settings are applied, a log file is created at /data/local/tmp/elementalx-kernel.log. Problems can be diagnosed by looking at the log file. Please check to see if any /etc/init.d scripts or apps (such as Kernel Tuner or Trickstermod) are interfering with your settings." and until I disabled 'Apply On Boot' my elementalx.conf was empty? I had 'Apply On Boot' enabled before I installed the kernel.
[Nexus 7 (2013) Original Android Development] Slavon-93:
So, I opened Trickster Mod, disabled 'Set on boot', rebooted, opened it again to see if anything is applied - nothing was, rebooted into recovery, installed kernel and once again elementalx.conf is empty plus install log is empty too. So I think it's all about my personal device incompatibility with AROMA. Thanks Gods, I have a copy of elementalx.conf in dropbox.

I think it just happened but had nothing common with disabling or enabling something in Trickster. On v1.4 sometimes AROMA finished properly and I saw TWRP buttons. And starting from v1.6 AROMA always shuts the tablet down and I have to hold Power button for 30 sec to start the device. And if tni.andro is right, I can understand why files are empty.

P.S I looked at Elementalx logs, which are created when settings are applied on boot and the last one was created on 18 october. That's strange because turning T2W off with power button is working well and everything else was set by Trickster. And it twice as strange because /etc/init.d/99elementalx has all permissions enabled and Trickster had a small delay. So I'm a bit confused in what's going on with the kernel, logs and Trickster.

P.P.S I deleted logs in /data/local/tmp, rebooted and nothing new appeared there. But settings were applied by /etc/init.d/99elementalx (tested on T2W).
[Nexus 7 (2013) Original Android Development] meekrawb:
Did you turn off the screen timeout in TWRP settings? That worked for me.
[Nexus 7 (2013) Original Android Development] Slavon-93:
Hmmm, seems to work for me too. Don't know how it is connected with AROMA, but I saw the Reboot system button. Thank you. If I will reinstall the ROM and have to flash the kernel I'll check if it works again.

P.S and the logs are working now...
[Nexus 7 (2013) Original Android Development] Zirowe:
Hi, I have flashed the kernel and the dvb-t add on, installed droidtv apk and connected an usb dvb-t stick with otg cable, but nothing happened when startng the app.

Who should I use it and what kind of sticks are supported?
[Nexus 7 (2013) Original Android Development] L-ViZ:
tested ex v1.8 on psx beta1+s4 patch, all stock cpu/gpu. 8316p in quadrant and everything fast and smooth. will be my daily driver, haven´t found any bugs or weird things. everything works :)
[Nexus 7 (2013) Original Android Development] banny7000:
I know I posted my battery stats yesterday.but I still can't believe the juice u get out of this kernel,I always charge at 50% and my screen on time yesterday was 7hrs 5 mins with 51% left.but when gaming I get about 4-5hrs thanks

Sony Ericsson w800,LG viewty,Nokia 5800,HTC wildfire,HTC desire s,Motorola xoom,nexus 7,nexus 4,Xperia z,nexus 7 2
[Nexus 7 (2013) Original Android Development] aorifan:
Amazing, what ROM are you using?
[Nexus 7 (2013) Original Android Development] banny7000:
These are my settings what are yours?

Cores-default

Oc 1.7

L2 and bus elementalx

Stock GPU

No s2w or anything else all unticked
[Nexus 7 (2013) Original Android Development] KedarWolf:
I updated CarbonRom to the latest nightly, forgot to disable Trickster Mod 'Apply On Boot' and when I reinstalled the kernel the Aroma installer never went back to recovery after I installed ElementalX and I had to hold the power button down 20 seconds to reboot. When i did the elementalx.conf was empty and the settings hadn't stuck. I disabled 'Apply On Boot' in Trickster Mod, rebooted into recovery, reinstalled the kernel and it went back to recovery and I rebooted from there. The elementalx.conf had all the settings and wasn't empty.

It may not be the Trickster Mod 'Apply On Boot' setting that is causing the trouble, I'm not sure why it would, but this is the reason why I think it may be a problem.

Edit: I just saw the post about the TWRP screen time-out, I wonder if this is the problem and having to hold the power button down to restart messes things up.
[Nexus 7 (2013) Original Android Development] adulel08:
im running cm 10.2 official nighties and when i flash this all my colors get messed up along with major input lag etc had to flash cm10.2 over to correct, guess the kernel doesnt work together
[Nexus 7 (2013) Original Android Development] dud3me:
Cm is no longer supported due to caf changes.

Btw I tried CM and I did think it was faster compared to stock, so I don't really mind having a rom using the more experimental sources even if it breaks kernel support for some. That being said, I can't get over the lack of PA features and of course prefer the ability to use all the kernels. :)
[Nexus 7 (2013) Original Android Development] KedarWolf:
What ROM Are You Using With ElementalX

I'm using CarbonROM but I find it sometimes ghosts touches and does things it shouldn't in games even with the multi-touch fix. Rebooting fixes it but then at times it happens again. I just replaced my Nexus 7 so I'm not 100% sure it is a problem with the ROM or the device. I'm thinking of trying a different ROM with the kernel see if I still have that trouble. What are you currently using and what have you tried? Any suggestions would be greatly appreciated.

Peace. :confused:
[Nexus 7 (2013) Original Android Development] farenteria:
It shouldn't have anything to do with the ROM or kernel

You can try this:

http://xdaforums.com/showthread.php?t=2428133
[Nexus 7 (2013) Original Android Development] meshdub:
For those interested, my Fiio E10 DAC works on this kernel with CarbonROM. Woot!

Didn't even have to boot with it connected. It just plugged and played. Tested with Play Music streaming.
[Nexus 7 (2013) Original Android Development] L-ViZ:
psx beta1, it was no public release. you could ask the dev for sharing or i could share it with u if u want to. final bench was 8600p after making my final setup.

using deadline/2048rab/interactive
[Nexus 7 (2013) Original Android Development] tni.andro:
Trickster doesn't do anything with the config file. It doesn't even use init.d scripts to apply its settings (it gets started on boot as Android app).

If you hold down the power button and force a power off/reboot, the filesystem isn't synced; so chances are pretty high that you end up with the empty config file.
[Nexus 7 (2013) Original Android Development] ktkr:
Is PSX still being updated for flo? I thought it was dropped until the arrival of Kitkat.
[Nexus 7 (2013) Original Android Development] roofrider:
Sometime dt2w doesn't work properly, only after multiple tries (2 or 3) does the screen turn on. Happening to anyone else?

Is there a way to figure out whats causing this?

Also an update on that 94% thingy from my side, it charges all the way to 100% (4200mV) and doesn't stop at 94% like it is for a few others.
[Nexus 7 (2013) Original Android Development] readonly24:
It happens to me when I started to usw dt2w, now I think I have "learned" how to do it right.
[Nexus 7 (2013) Original Android Development] tni.andro:
If it charges to 100%, most likely the setting wasn't applied properly.

The file '/sys/devices/i2c-0/0-006a/float_voltage' should contain '4200'. If it's '4300', the setting wasn't applied.

---------- Post added at 02:29 PM ---------- Previous post was at 02:24 PM ----------

From what I can tell, the I2C communication to the touch screen controller sometimes gets out of sync when the controller wakes the main CPU and needs a little time to resync (so the initial touch can get lost).

For me, a triple tap always works.
[Nexus 7 (2013) Original Android Development] roofrider:
It has 4200 in it.

I checked using batter monitor widget and the charging stops (reaches 100%) when the mV reaches about 4200. And also the Battery info you get when you use the code *#*#4636#*#* (battery monitor widget has this feature) also shows 4200mV and not more.

Maybe it's the rom i'm on (Carbon)?

Thanks!

It was kinda frustrating, i was afraid it might have something to do with my device or kernel+rom combination or some borked setting.

I'll play around to figure out a tapping pattern that works best for me lol. Triple tap seems to work!
[Nexus 7 (2013) Original Android Development] flar2:
One of the problems with doubletap2wake and deep sleep is that the kernel stops counting time when it's in deep sleep. I forget exactly what was happening because I haven't looked at it for a while, but it was something like this:

dt2w depends on a time window: inside the time window it turns on the screen, outside the time window and dt2w is canceled and reset. So, what happens in deep sleep is that a tap is registered, the time window is started, and then the device goes to sleep with one tap in the time window. A subsequent tap is sometimes connected to that old tap and it cancels and resets dt2w because the second tap occurred too long after the first tap. Since the kernel was not counting time during deep sleep, not enough time had passed for the function to time out on its own. Then the next tap starts the time window again and another tap quickly after wakes the screen. Three taps.

That's strange, when you say it's "empty" does that mean there is an empty file, or it the file doesn't exist?

/etc/elementalx.conf is created by scripts during installation. Please send me /tmp/recovery.log (while you are still in recovery) if this happens so I can see if there was an error.

1. Most options can be configured during installation, but many people use TrickersterMod for later tuning.

2. Check out supercurio's voodoo screen calibration. It's still in alpha, but works on this kernel.

It does not currently disable the wake functions.

You mean loopback device? I think so, if not, I will enable it next build.

I will check into this.

The add-on contains modules for a whole bunch of devices. I have no idea what is required to get some of them working in Android. I don't have a DVB tuner myself. I suspect you have to load the modules manually.

A start would be looking at the output of dmesg right after you plug in the device. That will at least tell you the name of the device, from there figure out what modules need to be loaded. I would google the name of your device + linux.
[Nexus 7 (2013) Original Android Development] Slavon-93:
That's not. Some pages before it was said that if AROMA crashes, FS is not synced, so empty files are likely to appear. I've just reflashed v1.8 twice and AROMA finished properly, so I don't think logs would help you anyhow. The question is why AROMA crashes, why it stopped after disabling screen timeout in TWRP and why it doesn't even after enabling it again. Well, I'll provide logs if I get a crash and if TWRP doesn't rewrite them on every launch, because if AROMA crashes, I don't have any access to "Copy logs to SD" button and I'm not sure if this file will still exist when I boot into Android.
[Nexus 7 (2013) Original Android Development] flar2:
So aroma completes successfully but /etc/elementalx.conf is empty? Or it doesn't exist? I'm still not clear on that.

Aroma can still complete successfully even if one of the scripts that creates /etc/elementalx.conf fails. That's why I would like to see /tmp/recovery.log The log would show whether any intermediate steps failed.

adb shell cat /tmp/recovery.log > /sdcard/recovery.log
[Nexus 7 (2013) Original Android Development] Slavon-93:
Well, it looks like that: installation is successful, I press NEXT, I see "copy installation log to SDcard" button in AROMA installer, then I press Finish and Tablet turns off. It doesn't return to TWRP as it should. If I want to turn it on, I have to press and hold the Power Button for 20-30 sec. After that, Tablet turns on and boots into Android. And if I go to /etc with Root Explorer, open elementalx.conf with its text editor (or viewer), I see, that it's empty. It exists, but empty. And even more - if I go to /sdcard (or /storage/emulated/0) and open installation log, it's empty too. The problem is that I can't predict if AROMA crashes or not. It behaves the same way every time and I see that everything is bad only after pressing Finish in the installer. So if you want some TWRP logs, please tell me, will it exist in /tmp when Android boots or not. If it will, I'll give logs as soon as AROMA crashes again. At this moment it works, returns to TWRP after installation and configs are written properly.
[Nexus 7 (2013) Original Android Development] flar2:
You have to copy /tmp/recovery log before you reboot to Android.

If the tablet is unresponsive, you can probably still get the log by connecting the usb cable and using adb shell to pull the recovery.log

Instead of holding the power button to reboot it, connect the usb cable and type "adb reboot"

Don't save the installation log from within Aroma, that's not the log I need.
[Nexus 7 (2013) Original Android Development] BWA80:
Hi!

I have the same problem... It has happend to me everytime i flash this kernel, from v1.4 to v1.8.
[Nexus 7 (2013) Original Android Development] roofrider:
[MENTION=3732677]Slavon-93[/MENTION] Does it happen even when the screen timeout is disabled in TWRP? You sure Aroma is crashing and it's not the display timing out exactly when you press Finish?
[Nexus 7 (2013) Original Android Development] WeRSpecialPeople:
I can say that I did check and the loopback device is enabled so LinuxonAndroid does work since they updated their app to support 4.3. Thanks though.
[Nexus 7 (2013) Original Android Development] L-ViZ:
yep it is dropped, beta one is a bit newer than v6, but never has been released. for me it´s better than v6 in terms of speed, sometimes browser got an fc, but only on huge webpages, but not a big deal for me. most of the webpages work great.

in this version, like on v6 no s4 patch included. so you need to flash it manually. so i really recommend to flash s4 patch, it gives u an extra boost ;)
[Nexus 7 (2013) Original Android Development] rocksyjj:
Whats the s4 tweak for the flo buddy
[Nexus 7 (2013) Original Android Development] ktkr:
S4 patch? Could you please tell me where to get it?
[Nexus 7 (2013) Original Android Development] Zirowe:
So, dmesg shows this:

RTL2838UHIDIR

On the inside of the tuner I have found this:

rtl2832u fc0013 eztv645 v1.0 2012-11-27

After a while I have found an dvb-usb-rtl2832u.ko about 6mb large, I have loaded it, and nothing happened, androidtv still showed no connected device.

What am I supposed to do, before starting the tv app?
[Nexus 7 (2013) Original Android Development] L-ViZ:
here´s a quote where you can download it from kszaq. didnt work with slim bean, but with psx great. tested it with psx, gives a recognizable boost ;)

this patch works on nexus 4 and flo, that´s what i know. also tested it myself on maguro, but it seems that it only benefits on a few processor types, maguro wasn´t one of them. newer versions of psx got it included (only mako atm i think). but on flo it wasnt included yet, so test it yourself ;) you won´t regret it :)

http://xdaforums.com/showpost.php?p=44063178&postcount=1164
[Nexus 7 (2013) Original Android Development] Spyr0s:
Disable screen timeout from TWRP settings, it has been already mentioned some pages back.
[Nexus 7 (2013) Original Android Development] :
Thanks man! It really does speed up the device (took antutu from ~22000 to 25500!
[Nexus 7 (2013) Original Android Development] bmakk2055:
[MENTION=4684315]flar2[/MENTION] thanks for this, I needed otg+charge because I only have the 16gb n7 I can now install my games on a flash drive. Thanks
[Nexus 7 (2013) Original Android Development] JCon0320:
I've been using the 1.8 kernel for a couple of days. I have to say that I haven't seen the kind of idle time my nexus 7 is having on ANY device that I've ever owned. [MENTION=4684315]flar2[/MENTION], this has been your best kernel for our device to date. The dtw/s2w toggle is a phenomenal feature in my opinion. Well done, good sir.

For folks that are not yet on the latest version of this kernel, here's a quick preview on how effective this one is above any other kernel available right now:

Sent from my Nexus 7 running PAC Rom w/ flar2's kernel.
[Nexus 7 (2013) Original Android Development] currydude:
For those having a black screen after aroma, disable screen timeout in twrp
[Nexus 7 (2013) Original Android Development] netespl:
I know it's not the right topic, but if anyone wants to flash this patch don't do this on AOKP - doesn't work, constant FCs :/
[Nexus 7 (2013) Original Android Development] kaz93:
The same thing goes for carbonrom..nfc force close