yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Philaphlous:
No random reboots for me yet on 1.5. Running 1.83cpu and 520gpu, no issues!
[Nexus 7 (2013) Original Android Development] Mayday_XL:
The v1.5 runs fine with stock settings, but uses more power than the stock kernel ?! :confused:
[Nexus 7 (2013) Original Android Development] flar2:
Does it use more power than previous versions of elemental?

As has been mentioned before, s2w and dt2w cause a bit more idle drain.

Disable them if you need your tablet to last a really long time. Otherwise you have to pay a small price for the convenience.
[Nexus 7 (2013) Original Android Development] Mayday_XL:
S2w and dt2w are disabled.
[Nexus 7 (2013) Original Android Development] flar2:
Check your wakelocks then
[Nexus 7 (2013) Original Android Development] tni.andro:
FYI: Battery Gauge enhancements

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

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

Actually, no. Only deep sleep (display off) power consumption is increased, since the touch controller isn't suspended. When the display is on, there is no difference.
[Nexus 7 (2013) Original Android Development] flar2:
That's what I meant.

I'm going to try out the battery guage enhancements tonight, looks interesting
[Nexus 7 (2013) Original Android Development] penguin449:
Well with multitask and gaming, the kernel still holds battery [MENTION=4149147]1.8[/MENTION]Ghz incredibly well! Dayumm... 100% brightness.. Them stats <3

Sent from my N7 2k13
[Nexus 7 (2013) Original Android Development] nikr123:
Hey

Have anyone tested the otg host mode charging?

I think it sounds like an awesome feature.
[Nexus 7 (2013) Original Android Development] jssingh:
I'm on CleanRom 1.6 and this kernel. To enable faux sound, do I just install the faux sound app from the app store or the trickster mod donate key? That simple?
[Nexus 7 (2013) Original Android Development] jlevy73:
Use his sound app, has more features.
[Nexus 7 (2013) Original Android Development] spartacus279:
the latest version of this kernel is simply amazing , 1.8ghz overclock and battery is amazing and no random reboots or multitouch problems, keep up the great work!!:D
[Nexus 7 (2013) Original Android Development] cobyman7035:
Just had another reboot.. it freezes my screen 3 secs then reboots

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] flar2:
Please post /proc/last_kmsg and which version you are using rather than simply saying you had a reboot. Other users will see it and think the kernel is unstable, which it is not. Also make sure you use stock frequencies for cpu and gpu.

I'm pretty sure the reboot was not due to the kernel. I've used and abused this thing like crazy and never had a reboot. I honestly treat my N7 like crap, and my five year old daughter uses it a lot too. The patches I've added are well tested at this point. Version 1.4 has over 4,500 downloads and no major complaints.
[Nexus 7 (2013) Original Android Development] GSLEON3:
Multi-boot support...

Hey Flar, Wazup?

[MENTION=4684315]flar2[/MENTION] , any chance on implementing multi-boot? I am curious & would love to hear about what you think about the kernel mod/hack found here: http://xdaforums.com/showthread.php?t=2457079

Would be cool to test out new releases without having to permanently flash. What do you think?
[Nexus 7 (2013) Original Android Development] Vaykadji:
Hello flar2 !

I'm using your kernel for the "double-tap to wake" option, it's soooooooo goooooood (I would gladely add more o's here, trust me, many many more).

I was wondering if you could do (for me and certainly others) a patched version of your ElementalX Kernel with the Kexec-hardboot-patch from Tasssadar and his brand-new MultiROM (here for MultiRom /!\ FRESH)

The patch can be found here.

It would be really nice to have your kernel on my main Stock ROM, so I can use "double-tap to wake" along with MultiROM (pleaaase?)

I imagine this may be more work for you, but I really think it could only better your awesome kernel, and it would really make me happier than I already am.

Thank you !

Cheers from the beer-and-fries country
[Nexus 7 (2013) Original Android Development] flar2:
I saw the thread and will add it in the next release.
[Nexus 7 (2013) Original Android Development] L-ViZ:
hey guys :)

installed v1.5. just had this black screen again. now i may know why i had this, cuz i disabled fsynch. just a little guess :) gonna let it enabled and disable it via trickster after first start. dunno if someone had this blackscreen before :) i had it a few times and i think these black screens could be related to disabling fsynch in aroma :)

edit: oooor not xD it seems display just turns of. so must be a problem between twpr and aroma installer
[Nexus 7 (2013) Original Android Development] flar2:
What do you mean by black screen? When does it occur?
[Nexus 7 (2013) Original Android Development] L-ViZ:
directly after setup, so after pressing "finish"

edit: btw, when i need to install superuser, i always install after kernel, dunno if this will have conflicts with aroma installer

it think the screen just turns off after aroma installer, cuz when i get the tablet to boot up, superuser has been installed eventhough it should have been flashed after kernel. so i just raised the time of screentime out in twpr xD
[Nexus 7 (2013) Original Android Development] crypticc:
I got some fc on currents and chrome. Something about adreno 200 men alloc error on the logs. To early to say if is this kernel.
[Nexus 7 (2013) Original Android Development] Devers:
I always have black screen after installing kernel. Just need to press and hold power button.
[Nexus 7 (2013) Original Android Development] Vaykadji:
I had this too. I just pressed the power button for like 15sec, and then it boots perfectly. This only appears with the installation steps, after that all works fine, never got black-screen again.
[Nexus 7 (2013) Original Android Development] flar2:
It's probably an aroma bug or something. I wouldn't worry about it, the installation seems to be fine.
[Nexus 7 (2013) Original Android Development] matrix.bharath:
Plus 1 it would be great to also have Tablet look for TWRM on this Recovery.. http://xdaforums.com/showthread.php?p=45887036
[Nexus 7 (2013) Original Android Development] flar2:
I noticed that some of the other kernels have added s2w and dt2w, but only applied the first commit, which is basically what I came up with on the first night I had the tablet.

The crucial change is in this one: https://github.com/flar2/flo-ElementalX/commit/cac2c6fb5f4169edd7f0ae95bb6cb4fe1e6bd6cd

All these should be applied to work out the bugs:

https://github.com/flar2/flo-ElementalX/commit/1466cb8f7ec251104818354eb2208f0f395fedcd

https://github.com/flar2/flo-ElementalX/commit/7be0a51bf758782009d3a8a36c433592cd4f2967

https://github.com/flar2/flo-ElementalX/commit/cac2c6fb5f4169edd7f0ae95bb6cb4fe1e6bd6cd

https://github.com/flar2/flo-ElementalX/commit/bae6cd4196ad0379d60d24997f71caf03e485cb7

https://github.com/flar2/flo-ElementalX/commit/0fcface89785227cd887f52f0383cbce56154901
[Nexus 7 (2013) Original Android Development] flar2:
Also, I hope to release a new version tonight or tomorrow, before I go on a mini vacation.

I will include [MENTION=3418703]Tasssadar[/MENTION] 's patch, among other things.
[Nexus 7 (2013) Original Android Development] cobyman7035:
I'm on elementalX 1.4 now uv 850. 1.7ghz… amzing stanby battery, only lost 1% in 16hrs.!

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] GSLEON3:
Thanks Flar! Hope you enjoy the vacation! BTW, I am amazed at how fast double tap to wake responds. Just as fast, if not faster, than hitting the power button. I had been looking for a way to easily turn the device on in a custom formed dash insert I fabricated. At the time, I forgot the buttons were near the back side of the device, so there was no way to access them. Thought I was going to have to start from scratch on my design. 2T2W solved that issue!
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
[MENTION=4684315]flar2[/MENTION] thanks for this.

I have an issue. Unable to install the kernel. Aroma crashes every time after I click finish. Tried both 1.4 and 1.5. I'd appreciate any help , thanks.

Edit: sorry,Got it to work
[Nexus 7 (2013) Original Android Development] tni.andro:
That's what people were talking about a couple pages back. The kernel should be installed just fine (Aroma hangs or crashes after the installation is done).

For me, 1.4 did that rarely, with 1.5 it happens 90% of the time.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Oops,my bad. I got v4 to work though. V5 kept crashing almost every time.

Maybe [MENTION=4684315]flar2[/MENTION] might want to ditch aroma and save him the bug reports,lol ;)

Either way, i love this kernel. Been using it since i unlocked my n7. Went testing some new ones, but couldn't settle on any other than eX.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] Ronde90:
I'd figure I'd share my battery stats on 1.4. Phenomenal with ds battery saver.
[Nexus 7 (2013) Original Android Development] Vaykadji:
Do you think I can use sweep2sleep without a navbar? (I'm using control-pie) I don't need it but I'm curious ^^
[Nexus 7 (2013) Original Android Development] flar2:
Yes, it's always active along the edges of the screen.
[Nexus 7 (2013) Original Android Development] donbowman:
partial success

So i tried. With the 'dead-short-pin 4/5', the tablet does not supply power out (correct). The device shows up on USB if the power is supply externally (correct). but the tablet does not charge (sad). (log below).

W/ the 124K pin4-5, the tablet charges, but does not see the usb peripheral plugged in (sad) if the power is not there *first*. if the power is plugged in, then the peripheral, and then whole cable is plugged in, it worked (happy). so there's some cases missing i guess.

<6>[ 389.004058] msm_otg msm_otg: USB in low power mode

<5>[ 402.697235] smb345_charger: [smb345_inok_isr] VBUS_DET = L

<6>[ 402.699707] msm_otg msm_otg: USB exited from low power mode

<6>[ 402.964874] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host

<6>[ 403.294677] notifying plugin

<4>[ 403.294952] [usbhost_charge_mode]: Do not supply power in host mode

...

<5>[ 427.367279] bq27541_get_psp status: Not charging ret= 0x0200

<5>[ 427.368499] bq27541_get_psp status: Not charging ret= 0x0200

<5>[ 427.369873] bq27541_get_psp voltage_now= 4295000 uV

<5>[ 427.371063] bq27541_get_capacity = 100% ret= 99

<5>[ 427.372375] bq27541_get_psp temperature= 278 (0.1¢XC)

<5>[ 427.374542] bq27541_get_psp current = 323 mA

<5>[ 427.377929] bq27541_get_capacity = 100% ret= 99

<5>[ 427.381988] bq27541_get_psp voltage_now= 4295000 uV

<5>[ 427.386138] bq27541_get_psp temperature= 278 (0.1¢XC)

<5>[ 427.387878] bq27541_get_psp status: Not charging ret= 0x0200

<5>[ 487.525421] bq27541_get_psp status: Not charging ret= 0x0200

<5>[ 487.526824] bq27541_get_psp status: Not charging ret= 0x0200

<5>[ 487.527984] bq27541_get_psp voltage_now= 4301000 uV

<5>[ 487.529327] bq27541_get_capacity = 100% ret= 99

<5>[ 487.530487] bq27541_get_psp temperature= 278 (0.1¢XC)

<5>[ 487.532562] bq27541_get_psp current = 323 mA

<5>[ 487.536010] bq27541_get_capacity = 100% ret= 99

<5>[ 487.537506] bq27541_get_psp voltage_now= 4301000 uV

<5>[ 487.539123] bq27541_get_psp temperature= 278 (0.1¢XC)

<5>[ 487.540618] bq27541_get_psp status: Not charging ret= 0x0200
[Nexus 7 (2013) Original Android Development] flar2:
It's a hack, so it has to be done exactly like this:

-turn on host mode charging

-connect standard otg adapter to y cable

-connect power source to y cable

-connect perhipheral to y cable

-connect otg adapter to tablet

Works every time for me, I just tried it now.

If it doesn't work, try again.

The part of the code that detects a cable with the resistor between pin 4 and 5 is disabled (aca mode), I think that cable should still set the ID bit (otg host mode). Looks like it did for you.
[Nexus 7 (2013) Original Android Development] cobyman7035:
Is there elementalX kernel. For nexus4?

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Nope.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] shyd:
The battery spikes are persistent. I am running v1.4 with stock rom on deb.

It looks like this, see attachment.

Are there any news about getting rid of those?
[Nexus 7 (2013) Original Android Development] kratos_12:
sorry for the noob question but is this stable with cyanogenmod rom? im using this on cleanrom and it rocks. but planning to try a different rom
[Nexus 7 (2013) Original Android Development] Sh0X31:
Why TricksterMod doesn't save my settings if I reboot (Set on boot is on)?

tapatalked with my Nexus 7 (2013)
[Nexus 7 (2013) Original Android Development] teh roxxorz:
Did you click the green check mark to apply the changes before hand?

sent from the 7th nexus of 2013
[Nexus 7 (2013) Original Android Development] Sh0X31:
Yes, I hit the Nike icon :D

tapatalked with my InsertCoined HTC One
[Nexus 7 (2013) Original Android Development] yellowdie:
The spikes have nothing to do with the kernel. It's a hardware issue with the Nexus 7 itself. This is the worst I have seen on mine. Being hardware, I don't expect it to ever get fully resolved--without an update from Google or ASUS directly (maybe).

View attachment 2284339

EDIT: I had similar spikes the first day I pulled it out of the box (stock everything); not as bad as this, but still spiked.
[Nexus 7 (2013) Original Android Development] shyd:
[MENTION=4110932]yellowdie[/MENTION]:

OMG this looks horrible!

It seems I never had these with the stock kernel for about one month. So I thought this might be the issue.

---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------

[/COLOR [MENTION=4110932]yellowdie[/MENTION]:

OMG this looks horrible!

It seems I never had these with the stock kernel for about one month. So I thought this might be the issue.
[Nexus 7 (2013) Original Android Development] tni.andro:
Are you using some additional battery monitoring app? The battery gauge driver lacks locking and may return invalid data when multiple apps read battery stuff at the same time.

If you have dmesg output, it would be helpful, if you could post that.
[Nexus 7 (2013) Original Android Development] GSLEON3:
This appears to be the result of a bad flux capacitor, causing a spacial vortex where your N7 is co-existing in the same space-time with a N7 from another reality that is fully charged at that particular point in time, as the crossover/merging occurs. The only fix is to purchase a case that is insulated with Terelium-D.
[Nexus 7 (2013) Original Android Development] yellowdie:
As you can see, I already got in an replaced the original Flux, so that shouldn't be a problem any more.

But I think you're on to something with the case. I went the cheap route and only got something with Trellium-

F

; maybe Trellium-

D

would have been high enough quality to fully protect the battery calibration signal waves from interfering. Good thinking!

:):D:laugh::good:

____________________________________________

And [MENTION=5288329]tni.andro[/MENTION]: No, I've never used another battery monitoring app. And for the record, I wasn't complaining about my battery--it doesn't bother me at all. I was replying to [MENTION=671062]shyd[/MENTION] that the calibration issues were not kernel related.
[Nexus 7 (2013) Original Android Development] flar2:
Added the patch needed for multirom support and a patch that will give more detailed battery stats.

Also changed the GPU frequencies a bit, I didn't test much on this device but these ones were a bit more efficient on the HTC One.

Otherwise this has the same additions as the 1.5 beta (usb host mode charging option, battery saving tweaks and AVS still disabled)

I've been too focused on my other kernels this week to really test the battery differences on 1.5/1.6 betas vs. 1.4 stable.

There is a setting for the hostmode charge option in /etc/elementalx.conf if you want to use it all the time and have it set on boot.

Download:

ElementalX-N7-1.6 *BETA*

Changes:

-battery guage enhancements (thanks [MENTION=5288329]tni.andro[/MENTION] )

-adjust GPU frequencies

-kexec-hardboot patch (thanks [MENTION=3418703]Tasssadar[/MENTION] )

-update installer
[Nexus 7 (2013) Original Android Development] shyd:
#AWSM

Just wanted to ask about it :)

Trying just now!
[Nexus 7 (2013) Original Android Development] tni.andro:
Well, ElemX 1.6 has my fix for the battery gauge driver locking issue. It will be interesting if that fixes the spikes.
[Nexus 7 (2013) Original Android Development] BigJPNut:
Hey flar2 when I use Rom toolbox or trickster to check CPU frequencies they show1026MHz for the low. I'm on 1.6 beta, is that correct?
[Nexus 7 (2013) Original Android Development] matrix.bharath:
Does the Beta Kernel have Bugs? why is it Beta?
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
It's beta because the changes are untested(partially) or is under testing.
[Nexus 7 (2013) Original Android Development] jlevy73:
1.6 working well thus far. I noticed that when I install the kernel trickster reports mpdecision as off. Is that correct? My understanding [MENTION=4684315]flar2[/MENTION] is that should be on by default?
[Nexus 7 (2013) Original Android Development] BigJPNut:
Same here. Also showed fsync off and 1026MHz as min cpu frequency. I think trickster is buggy....not sure
[Nexus 7 (2013) Original Android Development] shyd:
1.6 beta is working fine on deb with multirom!

And no battery spikes last night!

Max screen off freq is 702000, MPDecision is on
[Nexus 7 (2013) Original Android Development] sgt. meow:
[MENTION=4684315]flar2[/MENTION]

Regarding s2w or dt2w, the kernel has to be "awake" for it to work right? If that's the case and seeing as how awesome it works on this device, is there a wakelock or something keeping the kernel awake even after the timeout is passed? If not how do you wake the kernel because tapping once isn't doing it for me?
[Nexus 7 (2013) Original Android Development] teh roxxorz:
You have to double tap actually. Though if the tablet is in deep sleep, you may have to tap, then double tap.

sent from the 7th nexus of 2013
[Nexus 7 (2013) Original Android Development] tni.andro:
No. The difference is that the touch screen controller is not suspended, the main CPU still enters deep sleep, just like without s2w/dt2w. The touch screen controller wakes the main CPU, when there is input.
[Nexus 7 (2013) Original Android Development] sgt. meow:
Yeah the first tap isn't working on the OG Nexus 7. DT2W works superb when the device isn't in deep sleep. The first tap is meant to activate the "dormant" kernel and then the next two taps bring you to the lock/homescreen. I'm waiting on a test by a user to determine if a wakelock can be used here. Basically to make it work all the time (without the first tap) the kernel would have to be active all the time, which is bad news for your battery. A timed wakelock if such a thing is possible would be the better alternative IMO.

My bad, when I say kernel, I basically mean the device. Kernel inactive = Device in deep sleep = Main CPU inactive. Thanks for pointing out the mistake [MENTION=5288329]tni.andro[/MENTION].
[Nexus 7 (2013) Original Android Development] tni.andro:
The problem is not deep sleep per se. A double tap often works just fine in deep sleep.

Normally, the kernel log is disabled during the suspend/resume phase, so you don't don't see the large list of I2C errors. What appears to be happening when d2tw is not working, is that some data from the touch screen controller is lost and it takes a bit to resync the communication protocol.

There are a number of messages like:

<4>[ 2547.030700] [ektf3k]:[elan] Get unknow packet {0x62, 0x01, 0x01, 0x22}

<4>[ 2547.031036] [ektf3k]:[elan] Get unknow packet {0x37, 0xB6, 0x00, 0x00}

<4>[ 2547.031433] [ektf3k]:[elan] Get unknow packet {0x00, 0x00, 0x00, 0x00}

in the kernel log.
[Nexus 7 (2013) Original Android Development] jssingh:
Same settings are shown by trickster on 1.4.
[Nexus 7 (2013) Original Android Development] bounti:
Quick question. Should mp-decision be left enabled or disabled for this kernel?
[Nexus 7 (2013) Original Android Development] killflaker:
Yes, you can disable or enable mp-decision.
[Nexus 7 (2013) Original Android Development] teh roxxorz:
As far as on / off, the kernel doesn't offer an alternative, so preferred on if you want any kind of effect.
[Nexus 7 (2013) Original Android Development] cobyman7035:
Who's running elementalX. At 2ghz, if yes, how's battery life

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] BigJPNut:
flar2 said mpdecision he felt was the best way to go. You can disable it with Trickster but Id just leave it alone.
[Nexus 7 (2013) Original Android Development] tni.andro:
I would put it a bit stronger than that. You really want to leave mpdecision enabled.

mpdecision is responsible for powering up/down CPU cores. Without it, cores will remain powered up or down in whatever state they were when you disabled it.

AFAIK, there are 2 alternate implementations that do the same thing (that's why the option in Trickster), but ElemX doesn't include those.
[Nexus 7 (2013) Original Android Development] cobyman7035:
i just reflashed 1.4 eX to 1.8ghz o/c and using running cool mode with 850UV, fsync enable, will try these settings....

hopefully battery life is just as good as fully stock factory settings

i kinda got nervous in the setup cuz it was lagging, screen kept saying " please wait...loading" , but it rebooted up fine, im just charging my nex7 right now at 20% >>>
[Nexus 7 (2013) Original Android Development] tni.andro:
Installer crashes, minimum clock frequency not set properly

Actually, it doesn't seem to be fine. The kernel is installed, but I had empty '/etc/elementalx.conf' and '/etc/init.d/99elementalx' files.

This might be the result of that:

since '/etc/init.d/99elementalx' sets the minimum clock frequency.

It appears, that Aroma likes to crash extremely often, when multiple files are installed at once. Flashing the kernel by itself seems to work very often.
[Nexus 7 (2013) Original Android Development] Lexord:
Excuse me, but what language is that?

Awesome results btw.

Got my n7 yesterday and just flashed elemental, so far so good ??
[Nexus 7 (2013) Original Android Development] dictionary:
Everyone talking about the low freq, that's due to the new hotplug. Not sure if flar has a way to disable it, but in trickster you can also just set it to lock frequencies.
[Nexus 7 (2013) Original Android Development] -viperboy-:
On latest beta, 2.2ghz max (capped it to 1.5ghz in setcpu today), 450mhz (I think) gpu, ultra l2, default thermal, fsync enabled, dt2w, and short sweep to sleep only. Using latest PA as well.

Not sure why it shows screen on line but didn't think it was awake most of the time lol (second picture). Did a lot of reddit and Web browsing today. Some YouTube, twitter, and Facebook as well. This would have broken 9 hours screen on time today if I could stay awake any longer lol

Good job, flar2 :)
[Nexus 7 (2013) Original Android Development] celkin:
Unfortunately as of carbon roms Oct 2nd nightly it appears Elemental is no longer happy together :(

After clean rom install and full boot before flashing kernel and of course wiping dalvic n cache, blue screen after Google boot screen.

Anyone know if there is a solution to this?

I love this kernel with carbon! :)

Sent from my i337m rockin Kangabean
[Nexus 7 (2013) Original Android Development] ktkr:
Blame cm!
[Nexus 7 (2013) Original Android Development] celkin:
Bastards! Joking of course ;)

So this is a known issue. Didnt notice anyone else mention it this morning, but uncaffinated is not a good way to be searching xda lol

Sent from my i337m rockin Kangabean
[Nexus 7 (2013) Original Android Development] ktkr:
CM is messing with kernels in various devices so the compatibility with aosp kernels are now nothing but pita. Hope custom rom makers move back to aosp branch.