yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Mikanoshi:
Yep) remount succeeded! Final list:

supolicy --live "allow shell block_device dir search"
supolicy --live "allow shell labeldfs filesystem remount"
supolicy --live "allow adbd block_device dir search"
supolicy --live "allow adbd usb_device dir read"
supolicy --live "allow adbd capability adbd sys_admin"
supolicy --live "allow adbd block_device blk_file { read open ioctl }"
supolicy --live "allow adbd labeledfs filesystem { mount remount }"
supolicy --live "allow adbd adbd capability sys_admin"

and this one too)

supolicy --live "allow adbd kernel process setsched"
[One (M7) Original Android Development] kairi_zeroblade:
nvm..geniuses here at work..not for kids..
[One (M7) Original Android Development] Mikanoshi:
Is there a way to just allow everything for adbd?) adb remount works, but adb pull and adb push require a lot more permissions, open/read/write for different files and dirs
[One (M7) Original Android Development] flar2:
I think so:

supolicy --live "permissive adbd"

But why do you need all that? Everything works fine for me with the few things I added to the ramdisk in recent versions. I think it was maybe five or six policy statements.
[One (M7) Original Android Development] Mikanoshi:
Why? ADB complains that permission is denied)
[One (M7) Original Android Development] flar2:
I haven't switched to the latest base yet, so maybe it's that, but all the adb commands work fine for me since whenever I patched selinux in the ramdisk. On stock kernel/ramdisk, I couldn't do anything. No adb push, no connection from Android Studio, etc.
[One (M7) Original Android Development] Mikanoshi:
Maybe. I was on permissive the whole time, just switched to test something.
[One (M7) Original Android Development] beletruz:
Gestures

Gestures are not working. Can you help me please? They are crucial for me :crying:

Viper 8.0.0
[One (M7) Original Android Development] Aisfkhan:
any news for sense 7 m7?
[One (M7) Original Android Development] Droidcore:
Its work for sense 7

First flash 19.4 and flash 19.5
[One (M7) Original Android Development] MaratabHashmi:
Anyone have 19.4 kernel link?
[One (M7) Original Android Development] Polarbert:
Its at the top of this page. :rolleyes:

http://internet.5v.pl/internet.html

I've been having the same issue as well regarding the not booting. I tried 19.4 but it wouldn't boot, 19.5 is booting but only after a fashion.
[One (M7) Original Android Development] pondikos:
https://www.androidfilehost.com/?w=search&s=ElementalX-m7-19
[One (M7) Original Android Development] oc2:
Hi

Possible to add the drivers in this kernel that we can install "SnoopSnitch" ?

SnoopSnitch can detect IMSI catchers, silent SMS and SS7 attacks.

Thx
[One (M7) Original Android Development] :
Nice to hear that :)

Did you find the 'stuck at splashscreen' problem?
[One (M7) Original Android Development] flar2:
There's nothing I can do about that and maintain compatibility with various roms, it's a bootloader problem. This problem was blown all out of proportion, as the kernel works perfectly fine after you reboot. I hope it will be gone with the new release tonight, I will again standardize on a the most common base.
[One (M7) Original Android Development] Mikanoshi:
Will you add something to change adbd policies or we should just create init.d script? I'm not the only one with this problem)
[One (M7) Original Android Development] flar2:
I installed ARHD 91, so that will be my base for testing when I try out the new kernel tonight. I'll add whatever needs to be added to make it work.
[One (M7) Original Android Development] pankozin:
Hello. It is only me facing a bug that lie in not reducing the CPU clock, when power saver (14%) is on (EX19.5)? It still can ramp to maximum clock even with powersaver active. I hardly remember, there was a same bug on early KitKat, but then it was fixed.:confused:
[One (M7) Original Android Development] flar2:
Update!!!

Update with the latest source from HTC.

Also includes some more selinux fixes (mostly for adb commands)

Download:

ElementalX-m7-20.0-Sense

Changes:

-update source from htcdev

-update ramdisk to latest base

-more selinux fixes
[One (M7) Original Android Development] :
I'm afraid to say it, but my M7 still stucks on splash screen :(

Any trick I have to do before or after I flashed the kernel?

Edit: Okay, after 8minutes my phone is booting. I was probably a little too fast with my post, sorry :)
[One (M7) Original Android Development] flar2:
If it sticks there's nothing I can do. The kernel works perfectly, the bootloader has problems and there's no way I can fix it.

I reboot the phone less than once a week, so I don't really consider it a problem.
[One (M7) Original Android Development] mitchst2:
Had 19.5 issues myself. 20 flashed and booted no problems without wipe. Thanks [MENTION=4684315]flar2[/MENTION]

Sent from my HTC One
[One (M7) Original Android Development] Wickii:
Stucked at 1st boot. I held the Power Button till screen off, booted then. Running great. Thanks Kernel-Master! :)
[One (M7) Original Android Development] PhillyFlyer:
[MENTION=4684315]flar2[/MENTION], any shot we could pull this off with the new Sense7 SD port?
[One (M7) Original Android Development] MaratabHashmi:
Working for me
[One (M7) Original Android Development] jujak82:
I have 2 questions:

1. This is the latest sense base or stil gpe base?

2. Is better to use sense toolbox wake gesture or the program made by flair?
[One (M7) Original Android Development] panbambaryla:
TWRP 2.6.3.3 again

Flar2 could be right. Going back to TWRP 2.6.3.3 gives me no reboot-freeze problem.
[One (M7) Original Android Development] Sebby:
but a little quistion

but why is the kangaroo kernel booting up normally ,and not your kermel (i know you say bootloader)

so poondog did something to prevent this....

only asking...
[One (M7) Original Android Development] flar2:
This problem happened to me once out of the dozens of times I've flashed this kernel. If it was the kernel, I should be able to replicate it.

Also, I'm using the same exact changes I've been using for months.

I suspect it occurs if you don't wipe caches or something doesn't get unmounted properly in recovery

It reminds me of the old problem with aroma and twrp that caused so much grief.

In any case, the solution is very simple. Hold the power button until it reboots. People need to have a little patience and not freak out and incorrectly call it a bootloop.

The kernel works 100% and is 100% stable, so I'm getting really tired of people going around saying ElementalX is buggy.
[One (M7) Original Android Development] alex6600:
[MENTION=4684315]flar2[/MENTION] with ElementalX20 and ElementalX app ZRam option are appear. And default is ZRam on with swappinnes 60.

Is kernel support zram? And zram should be default on ?

http://prntscr.com/6gkbkw
[One (M7) Original Android Development] mitchst2:
I think you may be onto something there. More often than not the aroma installer does not exit to recovery properly. You end up with a black screen and have to reboot using the power button.

However 20 returned cleanly to recovery and booted absolutely fine for me.

Kernels others say never have this issue are simple flashable zips.

Might be worth doing a simple flashable for those with issues. Could pinpoint dirty exit from aroma as culprit.

Sent from my HTC One
[One (M7) Original Android Development] Sebby:
thanks flar

months ago i flashed twrp

before it was philz recovery (and have no problems with philz recovery's at all)

now i flashed philz recovery back

and see there your kernel boot's up

so no twrp for me anymore....

:D:D:D:D:D:D
[One (M7) Original Android Development] DeeZZ_NuuZZ:
[MENTION=4684315]flar2[/MENTION] one question....do you know if fauxsound works with latest roms on m7? or is it not compatible with lollipop because faux didn't update it?
[One (M7) Original Android Development] Lossyx:
FauxSound doesn't work for me. It says my kernel(elemental x) isn't compatible.
[One (M7) Original Android Development] DeeZZ_NuuZZ:
yes because it's not implemented, therefore i asked flar2 if it's already compatible with lollipop or if we have to wait for faux123 when he updates it...
[One (M7) Original Android Development] adambala:
Just flash ver 20 and my m7 boot up fine no more pressing power to reboot....Hope that's ok and not random...
[One (M7) Original Android Development] shivasrage:
delete
[One (M7) Original Android Development] Lossyx:
Ah. I read it wrong. My apologies

.but I was talking about kitkat, and if you see the website for kernel and xda post. The one on website it says faux123 sound control and not on this post. So I guess he removed support for it on. But I dint know,he (faux or flar) maybe will add support for 5.0
[One (M7) Original Android Development] slurpdroid:
Just flashed this amazing kernel couple hours ago

I am on ARHD 91.1, with 4.4.3 firmware base

Flash using TWRP 2.4.8

Wipe cache, wipe dalvik cache, and as I expected it stuck at splash screen

Hold power button and then the device turned off

Hold power button again to turn on my device, the key here is patience, after couple minutes my device booted up, and I am happy now [emoji1]

Thanks a lot!
[One (M7) Original Android Development] flar2:
That's quite possible.

Has anyone had this problem flashing the express installer from the ElementalX app?
[One (M7) Original Android Development] flar2:
Zram is on by default. You can disable it in the app. I was thinking of disabling it, but lollipop likes the extra memory. It might be va idle snappier without it, but trade off is occasional redraws.
[One (M7) Original Android Development] flar2:
Fauxsound hasn't worked for a long time so I dropped it.

There are other sound mods you can use
[One (M7) Original Android Development] mtpektas:
Sense 7?

What do you think about Skydragon's new rom? We can't use ElementalX but we absolutely want!! :laugh: :laugh: :laugh:
[One (M7) Original Android Development] :
You can use ElementalX on Skydragon's ROM...
[One (M7) Original Android Development] Mikanoshi:
cat /proc/last_kmsg | grep avc
[ 3.295101] c2 1 type=1400 audit(1426343330.190:4): avc: denied { setattr } for pid=1 comm="init" name="mmcblk0p19" dev="tmpfs" ino=8136 scontext=u:r:init:s0 tcontext=u:object_r:mmc_block_device_healthd:s0 tclass=blk_file permissive=0
[ 3.377842] c2 1 type=1400 audit(1426343330.270:5): avc: denied { setattr } for pid=1 comm="init" name="mmcblk0p19" dev="tmpfs" ino=8136 scontext=u:r:init:s0 tcontext=u:object_r:mmc_block_device_healthd:s0 tclass=blk_file permissive=0
[ 3.378208] c2 1 type=1400 audit(1426343330.270:6): avc: denied { setattr } for pid=1 comm="init" name="mmcblk0p19" dev="tmpfs" ino=8136 scontext=u:r:init:s0 tcontext=u:object_r:mmc_block_device_healthd:s0 tclass=blk_file permissive=0
[ 3.378452] c2 1 type=1400 audit(1426343330.270:7): avc: denied { setattr } for pid=1 comm="init" name="mmcblk0p19" dev="tmpfs" ino=8136 scontext=u:r:init:s0 tcontext=u:object_r:mmc_block_device_healthd:s0 tclass=blk_file permissive=0
[ 3.378666] c2 1 type=1400 audit(1426343330.270:8): avc: denied { setattr } for pid=1 comm="init" name="mmcblk0p19" dev="tmpfs" ino=8136 scontext=u:r:init:s0 tcontext=u:object_r:mmc_block_device_healthd:s0 tclass=blk_file permissive=0
[ 3.378879] c2 1 type=1400 audit(1426343330.270:9): avc: denied { setattr } for pid=1 comm="init" name="mmcblk0p19" dev="tmpfs" ino=8136 scontext=u:r:init:s0 tcontext=u:object_r:mmc_block_device_healthd:s0 tclass=blk_file permissive=0
[ 3.379063] c2 1 type=1400 audit(1426343330.270:10): avc: denied { setattr } for pid=1 comm="init" name="mmcblk0p19" dev="tmpfs" ino=8136 scontext=u:r:init:s0 tcontext=u:object_r:mmc_block_device_healthd:s0 tclass=blk_file permissive=0
[ 46.334930] c0 144 type=1400 audit(1426343373.225:148): avc: denied { read write } for pid=144 comm="kworker/0:2" name="mmcblk0p19" dev="tmpfs" ino=8136 scontext=u:r:kernel:s0 tcontext=u:object_r:mmc_block_device_healthd:s0 tclass=blk_file permissive=0
[ 52.405188] c0 144 type=1400 audit(1426343379.292:149): avc: denied { read write } for pid=144 comm="kworker/0:2" name="mmcblk0p19" dev="tmpfs" ino=8136 scontext=u:r:kernel:s0 tcontext=u:object_r:mmc_block_device_healthd:s0 tclass=blk_file permissive=0

[ 52.405218] c0 144 unable to open file: /dev/block/mmcblk0p19
[One (M7) Original Android Development] mtpektas:
But I always going boot loop when I need to restart my phone...
[One (M7) Original Android Development] joriq:
how about reading any of the last ten pages or so? :rolleyes:
[One (M7) Original Android Development] maxpaynezm:
+1 ,skydragon sense 7 rom
[One (M7) Original Android Development] kishorsidu:
i was on 4.4.3 stock and had my phone rooted ( checked with root checker )

i installed corresponding elemental x kernel using twrp.....no problem while installing and booted normal...got swipe to lock and tap2wake features......

now i lost my root access....might this be due to kernel?? shall i try to root again???

btw...the kernel is cool...i feel my phone being more smooth....
[One (M7) Original Android Development] Wickii:
Just flash/install SuperSU. No need to investigate wether the kernel could eventually be responsible for that.

http://xdaforums.com/showthread.php?t=1538053
[One (M7) Original Android Development] mtpektas:
My Fix

I fixed it. If you use twrp material designed and if you forgot install twrp theme zip you can boot loop easily. If you don't want to go boot loop you can change your recovery guys.

Unfortunately, opening is very long (11 minutes) devs must find fix for that.. :o :o
[One (M7) Original Android Development] Mikanoshi:
Forcing Wake gestures to off on boot was a bad idea, because now it's either a delay before activation or a failure to activate if I try make it closer to boot animation end and it happens too soon.
[One (M7) Original Android Development] shree.cse:
Or Use Trickster Mod app.
[One (M7) Original Android Development] ArmedandDangerous:
Does anyone have a flashable zip of stock 1.29 kernel? ElementalX breaks my camera unfortunately ):
[One (M7) Original Android Development] spbhutia:
its a known issue... flash the kernel again choosing the option Camera fix in aroma... should work..
[One (M7) Original Android Development] ArmedandDangerous:
It doesn't work for my firmware unfortunately. With and without camera fix and nothing changes. Many of those having the issue come from my country and no amount of flashing the kernel fixes the camera.

Anyone got stock kernel I could flash maybe? ^^
[One (M7) Original Android Development] happyendin21:
won't boot with custom kernel

Hello all

Trying to load a custom kernel on my tmobile htc one which is unlocked and rooted running trickdroid 7.0 . I have tried two that say they should work with my tmobile htc one. However I am getting a bootloop type thing. Where it just flashes the white htc screen with red writing across the bottom them flashes capacative buttons and then turns off. I can't fix this until i reflash the rom. no other kernel will boot other than the stock one that comes with the rom..... any ideas why this is happening. This is not my first rodeo. I have been rooted since the g1, just never seen this exact problem. Thanks in advance for the help.
[One (M7) Original Android Development] ArmedandDangerous:
There is no kernel for 4.2.2 ROMs yet, so the ROMs flash the stock kernel instead. All currently released kernels only support 4.1.2
[One (M7) Original Android Development] happyendin21:
Sigh....Thanks

thanks. I will be more careful next time...
[One (M7) Original Android Development] skyline72:
When will it support 4.2.2?
[One (M7) Original Android Development] godofwar424:
NEVER! I'm saying this because you haven't even bothered to just SEARCH before posting questions that have already been answered repeatedly..

Search before asking!

Now to answer your question, when HTC release new sources, new kernels will come, until then. Nothing is going to happen, so moan to HTC why they are not following the Android GPL and withholding the latest kernel sources.
[One (M7) Original Android Development] Radikaal:
Does not work to underclock for me. Changing speed in setcpu etc works but it still ramps up to max speed like normal. Just for me or known issue?

Skickat från min HTC One via Tapatalk 2
[One (M7) Original Android Development] shree.cse:
I think it's an issue, I only got freq locked using trickster mod premium key.
[One (M7) Original Android Development] razer1224:
Hey

Does this kernel contain 2.17 ramdisk?
[One (M7) Original Android Development] shree.cse:
2.17 ramdisk? For one, there's no need, cause we can flash the kernels through recovery, unlike one x. Anyway this kernel doesn't work with 2.17 base, don't try.
[One (M7) Original Android Development] razer1224:
i know i can flash kernels without cmd

Thanks Anyways :)
[One (M7) Original Android Development] s7yler:
Strange problem

I have a strange problem, when I flash the kernel it works fine in the beginning, after some use, suddenly it sometimes dont work anymore. Doubletap2wake and sweep2lock. I dont know if its a software problem or my touch on my device maybe? or maybe when the screen gets hot? But buttons and screen work fine in normal use. If I restore my backup of my ROM and again install the kernel it again works for some time, and then suddenly it can happen that it again dont work. Strange or? Using stock 4.1.2 rom, but still have S-ON.
[One (M7) Original Android Development] choboii:
Which kernel provides better battery life for those who have used both this one and the bulletproof one? I had this one but switched to bulletproof because I had an issue with my phone. Also it seems that bulletproof doesn't show the battery percentage. Is. This an option only for ElementalX? Thanks
[One (M7) Original Android Development] choboii:
Actually I can't even get the battery percentage to show on this kernel. I went to power to see if there was an option to turn it on and couldn't find one. And it never asked me in aroma. I don't what the problem is.
[One (M7) Original Android Development] revamper:
Battery percentage is related to the ROM, not the kernel.
[One (M7) Original Android Development] choboii:
Damn, I feel like a dumbass now. Lol. thanks
[One (M7) Original Android Development] KindaJackedForANerd:
Flar you still with us?
[One (M7) Original Android Development] the playa!:
Hi,

Will you guys include Tap2Unlock (http://xdaforums.com/android/software-hacking/kernel-tap2unlock-tap2wake-feature-t2965344) in future builds?
[One (M7) Original Android Development] justion:
It's not a bootloop, you just need 8-10 minutes with HTC logo and after a while everything works fine. Or you just need to press the power button until the phone restarts itself, and again everything should work fine.
[One (M7) Original Android Development] panbambaryla:
Actually it's not bootloop but rather bootstuck. Change TWRP to 2.6.3.3 - the problem is gone.
[One (M7) Original Android Development] flar2:
Can you use the on boot complete intent?
[One (M7) Original Android Development] Haik0:
I have read, I fixed it and I announced it here, too, so thanks for the attention but ignore this this old post it is not relevant already, which you would knew if you were to read the last ten pages :D
[One (M7) Original Android Development] :
Nope. I'm on TWRP 2.6.3.3 and I have the same problem.
[One (M7) Original Android Development] flar2:
Guys, if it doesn't boot right away, then hold the power button to restart. There's no sense waiting eight minutes for it to boot.
[One (M7) Original Android Development] panbambaryla:
It wasn't the solution for me. Even full stop and giving the phone some time to rest/cool down? it was stuck on boot. Cleaning cache was helping to this one boot only. Right after downgrading TWRP to 2.6.3.3 it's rebooting right away.

Forgot to mention ARHD 91.1, s-off, CID=11111111.
[One (M7) Original Android Development] Mikanoshi:
EX already has similar stuff and I already wrote an Xposed mod called Touch Lock that completely blocks device screen (even after reboot) until you tap in a predefined sequence (up to 12 taps).

Mod is in Sense 6 Toolbox. It's still in beta for Android 5.0, Touch Lock mod may be buggy, it will be improved in next beta release to work better with latest EX versions.

Boot complete is received ~5 seconds after you see launcher, not really an instant activation (and your app starts service with additional 10 sec delay?)

With Xposed I can execute code whenever I want, even during boot animation, but SuperSU may block root commands during that time, so now I had to use a postDelay'ed runnable that tries to set wake_gestures to 1, checks the result and posts itself again if necessary :)
[One (M7) Original Android Development] belako:
Hi Mikanoshi, love your Boot Animation (best among all the boot animations in all the devices I've ever tinkered with). I'm interested in your opinion in overclocking. Did you notice better performance at your current clock speed? Does it overheat? Because I actually really want to run my device cool.
[One (M7) Original Android Development] boroboy69r:
GrtdrfgfrsasdytertrerlrtftrrrrgfxffftuihgzsygdxaSSsxfffdddsffffhcccyflfytttrrrx rer
[One (M7) Original Android Development] Mikanoshi:
It becomes warm only if playing 3D games for a long time or making some intensive operations when charger is plugged in.

You can always limit thermal level and it will lower frequency to cool device down)
[One (M7) Original Android Development] Software Guru:
Thanks for the update but can I ask question about v19.5

I've notived a slight glitch in that my Home screen button becomes unresponsive, press it and there is to vibration and no action performed

The only way to resolve it is to reboot the phone, it then starts working for say an hour but then again the same thing happens

I have double tap to wake setup when I loaded the kernel

Is this kernel or ROM related??

Thanks
[One (M7) Original Android Development] reeves1985:
I'm having an issue with the fast charge usb

I'm using a 1a output power jacket case with fast charge enabled but I'm still getting that enjoying slow charge triangle in my notification bar

Not sure what to do next

I'm hating stick lollipop 5.0.2 Rom rooted and have installed elementalx and ena led fast charge etc
[One (M7) Original Android Development] heat57:
I'm running my M7 on Maximus HD 52.0 and had the same problem with EX 19.5 and 20.0. I did a clean install of Max HD 50.0 and upgraded with the OTA whilst on EX 19.4 at the time and I didn't have any boot issues. I then updated EX to 19.5 and started getting these boot problems, although, eventually, it always boots after some trial and error. I then reflashed Max HD 50.0 and left it running the stock kernel; no boot issues. Then I upgraded to Max HD 52.0 and EX 19.5 and had the boot issues back again.

Finally, I decided to flash HD 52.0 again only clearing cache and dalvik and it booted as normal. Then flashed EX 20.0 clearing cache and dalvik, rebooted twice and now I have no problems either rebooting system or rebooting into recover and back to system etc. Btw, I tried different TWRP recovery versions, including going from 2.8.5.5 back to 2.6.3.3 and that did not make any difference.

It looks to me as the Max HD Lollipop ROM is very 'kernel sensitive'.
[One (M7) Original Android Development] maxpaynezm:
problem is this kernel, i try any different lollipops rom,still the same problem,no boot,stuck on splashscreen
[One (M7) Original Android Development] Wickii:
I had the same Problem several times. Seems to be very random, I'm not able to reproduce it. Sometimes it appears after a few minutes, sometimes after several hours. Don't know if it is Kernel-, ROM-, or Xposed related. I recognized a solution to get the button working again without reboot. If we have the same bug, it should work for you too.

If the bug appears, press and hold power button till APM pops on. Press power again to turn screen off. Turn screen on. Button should work.
[One (M7) Original Android Development] Osama Zabin:
I recently started facing this as well.

As advised by Mikanoshi, Plug/unplug your usb cable.