yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] aoryx:
If want to add a line to ramdisk/service_contexts

Can I do it thru adding this line in ur file edit_ramdisk.sh

echo "\n xprivacy453 u:object_r:system_server_service:s0" >> /tmp/ramdisk/service_contexts

Any help is appreciated!

Thanks!
[One (M7) Original Android Development] artur0588:
What is wrong with EX 19.5? I have round reboot after splash screen. Stock 5.0.2 firmware 7.19.401.2

EDIT: installed EX 19.4 and it's stuck on boot animation now, no matter usb connected or disconnected. I have log in attachment.

EDIT 1: Installed EX19.5 over EX19.4 and it's now stuck on boot animation with same log error:

Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.server.SystemServer" on path: DexPathList[[directory "."],nativeLibraryDirectories=[/vendor/lib, /system/lib]]

try wipe cache and dalvik now.

Finaly it boots after wipe cache and dalvik, now under upgrading apps. So all who have similar issue i recommend wipe cache and dalvik after kernel flash.
[One (M7) Original Android Development] shivasrage:
flar2 said its a problem with bootloader and he isn´t able to fix this,

but I personally don´t understand why.

because I tested xceed, stock and the older EX (19.2)

they all boot up with the same bootloader without any problem.

otherwise I´m not a pro like far2 I´m sure if you ask him to explain exactly

what the problem is...he would do it.
[One (M7) Original Android Development] artur0588:
As he explained before the problem is stuck on splash screen and it's easy resolve by just rebooting device 1 or few times. My issue is completely different.

Finaly it boots: look here http://xdaforums.com/showpost.php?p=59191819&postcount=14049

Any way make this kernel adbd insecured?
[One (M7) Original Android Development] Kornelije23:
Help

I need a favor, can some one please make that in aroma last button: intall elemental kernel, be on the bottom of the screen. My digitizer do not work on top of the screen so I can t flash kernel. I hope this is not a big work thank you in advance.
[One (M7) Original Android Development] requa3r0:
boot loop

I am also caught in the endless boot loop. They take around 30 sec each

I have also tried to wipe cache + dalvik both before and after install, and have re-installed EX 19.5 many times.

Phone just goes into an endless boot loop what ever i do.

Have tried different hboots, without any difference.

Started on 1.44 so i could boot on recovery without flashing, and the new 1.61. Same issue on both hboots.

Have reverted back to stock.

NB: Did my install with the new openrecovery-twrp-2.8.5.0-m7.img

Could this be an issue?

Hopefully there will be an update soon.

I really miss the EX kernel.

M7, S-OFF, hboot 1.44 for boot on recovery without flashing, and stock 5.0.2 version 7.19.401.2
[One (M7) Original Android Development] khandelwalsiddharth:
How come you are on stock lollipop with hboot 1.44?
[One (M7) Original Android Development] BanBoo:
Flash 19.4 and wipe cache afterwards flash 19.5! Worked for me on stock lollipop.
[One (M7) Original Android Development] requa3r0:
To keep stock recoery for a while

As mentioned...to avoid flashing over the new stock recovery at first.

I am S-off..so I can flash any hboot I what.

When going to 5.0.2 this is what I did.

I flashed a stock nandroid 4.3.3 backup, fount in the ONE ROM list, then updated with OTF 5.0.2 update, then I did a factory reset.

Before doing anything else, I flashed the 1.44 hboot, which is pretty special, because with this one you can boot on any recover without flashing and overwriting the new original 5.0.2 stock recovery.

Like this

flashboot boot recovery.img
[One (M7) Original Android Development] CloggieUK:
Call me simple but surely if the issue isn't there in the older versions, something must have been changed in 19.5 to cause the issue...

Sent from my HTC One
[One (M7) Original Android Development] requa3r0:
Thanks.

also Flashed 19.4 and wipe cache afterwards. Then flashed 19.5 no wipe!

Worked for me 2 on stock lollipop.
[One (M7) Original Android Development] oc2:
GPE , and since i have updated from 19.1-GPE to 19.3-GPE my little wakelocks are now gone. Great Kernel now. Thx
[One (M7) Original Android Development] avi16679:
KCAL

Flar can you please add Support for kCAL advance color control
[One (M7) Original Android Development] harmenator:
Wow..amazing!

Thank you veeeeeeerrry much!!!

Using sense lollipop version of your kernel..

Awesome, no issues :sly:
[One (M7) Original Android Development] Javi22:
I'm noticing an important issue that is happening only with your kernel, I don't get whatsapp messages with screen off, or I get them delayed

So when I unlock screen, just at that moment, I receive all messages. If I don't unlock screen in X time (it depends... Sometimes it's 5min or 60min...), the whatsapp arrives, but delayed

This has happened in the past too, but sometimes it worked fine. Even with the same kernel version, sometimes have worked and sometimes not

Any idea?

PS. Using 19.5 with MaximusHD 52 (installed perfectly at first time)
[One (M7) Original Android Development] Osama Zabin:
Is " Data Connection" enabled under power saver mode?

Also check " Keep WiFi on during sleep" under Advanced WiFi options.

These two options can affect data connection, and as a result, the push notification messages
[One (M7) Original Android Development] Javi22:
Yeah, checked everything

Indeed, this issue comes just when flashing this kernel. Then I go back to stock kernel and... It's fixed

Forgot to mention it only happens over wifi. With mobile data is ok
[One (M7) Original Android Development] shinji257:
I tried to install this but I ended up in a boot loop. I installed it using TWRP 2.8.5.0 on Developer Edition Lollipop rom from HTC. I used the Sense 6.0 for 5.0.2 kernel. Help?

For now (so I have a usable phone) I reflashed stock kernel via fastboot and the phone is working again
[One (M7) Original Android Development] PhillyFlyer:
Same issue here.

Update: flashed 19.3 and it works. Guess that will have to do for now.
[One (M7) Original Android Development] truelies1:
flashed 19.3. on boot loop
[One (M7) Original Android Development] Haik0:
Bootloop after flashing ElementalX on Stock settings

Hey guys.

I am getting a bootloop after installing the ElementalX on my HTC One m7 (5.0.2).

I am setting all the options on Stock, not even Default, I am not undervolting , nor overclocking the CPU or the GPU ! The only option I leave checked it the Double tap to sleep (Full screen) and I am always getting bootloop.

I tried restoring the system and re-flashing the ElementalX, but I am getting the same result !

Can someone help me with an advice ?

Thanks
[One (M7) Original Android Development] Olaff666:
Hey guys. Will i achieve wake gestures on stock 5.0.2. ROM without sense 6 toolbox? Just by installing the kernel.
[One (M7) Original Android Development] cyrusct82:
Yep. And you can use this app to set it http://xdaforums.com/showthread.php?p=58836857
[One (M7) Original Android Development] Haik0:
Fix for Bootloop ???

So ? No solution to this Bootloop issue ?
[One (M7) Original Android Development] popokrew:
You guys are stuck at the splash screen or it keeps restarting? For me when I have a boot issue it just sits at the splash screen. I hold the power button till the phone restarts then hold the volume down to enter the bootloader. I then go to power off the phone option. Wait a few seconds then power the phone back up and it always boots.
[One (M7) Original Android Development] Haik0:
No, it keeps restarting in my case and as I can tell mostly everyone else has the same problem after flashing the 19.5.

Is there any official announcement about this issue? Will this be fixed ? or that's it, we don't have ElementalX for out M7 any more ????
[One (M7) Original Android Development] edvinn:
There is no issue with ElementalX here. 19.5 sense works just fine. Sometimes is stuck, but it's a bootloader issue, not kernel. Solutions that work are:

- hold power button to force restart

- do not use restart, instead turn off your phone, then power it on

- when stuck on splash screen, plug in/out your charger or usb cable.
[One (M7) Original Android Development] Haik0:
But the main problem ppl are having here is not that it stuck's on slpash screen, but it boot loops right after flashing the kernel (with stock settings !!!) and in my case I also tried clearing the cache and dalvik before and after flashing the kernel, it still bootloops every single time.
[One (M7) Original Android Development] shinji257:
I actually changed ROMs but for me it was looping at the bootloader screen. It wasn't even getting to the boot animation.
[One (M7) Original Android Development] shivasrage:
When this is a bootloader problem, why do the older versions boot without issue?

For me EX 19.2 boots without any problem...so i guess there must be a change in the kernel also..

greets
[One (M7) Original Android Development] JCDenton_GR:
I am using ARHD 91.1 with the latest kikkat firmware because i am still S-ON and i don't have any problem with 19.5.

The second time i rebooted my phone i think, it was stuck in htc logo.But it restated perfectly after holding power button till the end of blinkng capacitive buttons.

No need to boot from recovery or anything and this thing happened while i was in kitkat too.

Maybe everyone having bootloops writes down their config so devs could find the issue?
[One (M7) Original Android Development] G3R0:
If it is boot looping: Try to install ElementalX 19.4, clear cache and dalvik. Boot the phone twice as it requires the setup. Then install ElementalX 19.5, clear cache and dalvik. This trick does work for me.
[One (M7) Original Android Development] Olaff666:
Where do i get the 19.4 that works with stock 5.0.2? 19.5 caused me a bootloop.
[One (M7) Original Android Development] shivasrage:
Look here:

https://www.androidfilehost.com/?w=search&s=ElementalX-m7-19

:good:
[One (M7) Original Android Development] Olaff666:
Thank you!
[One (M7) Original Android Development] :
Any one has xprivacy working on latest kernel version? I read that elementalx is supporting this, but I can't get it to work. But I also don't know how to modify the kernel. ._.
[One (M7) Original Android Development] fireattack:
Hi guys, I'm new to elementalX. I just flashed 19.5 on my 5.0.2 sense phone (was stock kernel) followed by the steps and tricks mentioned above, every thing is smooth!

However, I got a problem: the feedback vibration of my buttons (vibrate on touch option in sound & notification) now are very weak.

Is there anyway to bring this back to stock status?

Thanks!
[One (M7) Original Android Development] BanBoo:
Try the trickster mod app from playstore and you be able to adjust the vibration strength to your liking.
[One (M7) Original Android Development] themachinist:
Does anyone overclock and notice the max cup frequency don't stick sometimes after boot?

I'm not sure what's making it drop from 1890. It's definitely not thermal throttling or power saver cause it drops even when the phone is idle and cool. I try setting the elementalx kernel app to set on boot as well but it changes after boot like hours later so doesn't help.
[One (M7) Original Android Development] letmeknov:
Flashed 19.5 to a clean stock 7.19.401.2 RUU, and it caused bootloop Flashed 19.4, cleared cache afterwards and the bootloop gone, but instead device was stuck on HTC boot logo, did more than 5 restarts and it never booted. So I flashed stock kernel through fastboot and my device boots as it should now.

Never had bootloops before on MaximusHD 50 and 52.
[One (M7) Original Android Development] Haik0:
This totally worked for me, THANKS!

1. Downloaded 19.4 from here https://www.androidfilehost.com/?w=search&s=ElementalX-m7-19

2. Boot to recovery, wipe cache and dalvik (wile on stock recovery)

3. Flashed 19.4, wipe cache and dalvik again

4. Flashed 19.5, wipe cache and dalvik again

and it works now.
[One (M7) Original Android Development] malkder:
After flashing the kernel my Battery draining so fast

What is the best solution for this problem OR What are the best choices to take from kernel option to keep my battery works well
[One (M7) Original Android Development] pankozin:
Hello. And i noticed a huge amount of wakelocks in ARHD 91.1 with EX19.5. I got this activity when screen off 24\7 no matter wifi or 2g im using. and its really draining faster the battery than it was in KitKat.... Who knows, how to solve this? Reflash? Roll back to KitKat? The most draining kernel wakelock is msm_hsic_host, in KitKat this wakelock was draining alot too, but it was like 1500 wakelocks in 8h, and now it is thousands and thousands of wakelocks. Up to 10^4

Can somebody screenshot your screenoff activity, so i can conform or not, thats only my issue

Im on arhd 91.1 and 19.5 kernel. Other people report their bat life as fine.(mb stock kernel??)

Can u screenshot your wakelock activity in the standart bat journal?
[One (M7) Original Android Development] malkder:
Give me at least 15 to 30 min To give you more clearer Graph
[One (M7) Original Android Development] pankozin:
The minus of this graph is, if u will hold it too long it will extend with a forecast of battery life, so the measured scale will collapse (
[One (M7) Original Android Development] malkder:
Here You go :)
[One (M7) Original Android Development] pankozin:
It is right what i tried to say - it collapsed coz of forecast ) And there is no opportunity to see the "Awake" state when screen is off
[One (M7) Original Android Development] malkder:
Right now what do I do For you ?

---------- Post added at 09:49 PM ---------- Previous post was at 09:45 PM ----------

bootloop after flashing EX19.5 on stock 7.19
[One (M7) Original Android Development] pankozin:
Do u use some battery monitoring app, like gsam battery monitor? if yes, plz go there and look, which kernel wakelock is the most active
[One (M7) Original Android Development] kasemben:
problem !!!??? after installing ElementalX-m7 | 19.5 my htc one m7 wouldn't start

problem !!!??? after installing ElementalX-m7 | 19.5 my htc one m7 wouldn't start the phone rebooting to the recovey mode plllllz i need a help ..... :'(
[One (M7) Original Android Development] malkder:
No, I Don't use like this apps , I Just installed Now For you to see
[One (M7) Original Android Development] malkder:
Do not panic !! :)

Just flash kernel that belong to your current rom besides erase cache

CMDs Command

Fastboot flash boot boot.img

Fastboot erase cache
[One (M7) Original Android Development] Warlock5822:
Same here, any solutions yet?

---------- Post added at 08:13 PM ---------- Previous post was at 08:04 PM ----------

Hi, I haven't found a proper solution to the ElementalX Kernel yet, but after having my phone stuck in a bootloop many times trying to sort it out what I sound is the best way is to have a backup before hand in my case TWRP and then if the kernel causes problems then boot back into TWRP hit restore and only restore the boot partition and that should get things working again. If not then try just restoring the system.

Sorry again that I can't help with the kernel but at least this will get your phone back into working order :)
[One (M7) Original Android Development] peca_slo:
Anybody know why wake gestures not working with last elemental and viper one.

It says service cloud not start
[One (M7) Original Android Development] Haik0:
Yes there is some sort of solution.

This totally worked for me, THANKS!

1. Downloaded 19.4 from here https://www.androidfilehost.com/?w=s...ementalX-m7-19

2. Boot to recovery, wipe cache and dalvik (wile on stock recovery)

3. Flashed 19.4, wipe cache and dalvik again

4. Flashed 19.5, wipe cache and dalvik again

and it works now.
[One (M7) Original Android Development] de.dari:
I am sorry if this is a sily question as i dont flash kernels that often.

I downloaded this kernel and since I am S-on i did not find the boot.img there to flash on my mac via fastboot.

Could anybody give a hand?

Cheers
[One (M7) Original Android Development] beletruz:
Viper 8.0.0 wake gestures

WAke gestures are not working, any idea? I mean after I reboot they work but after leaving my phone untouched for 5 min they stop responding. Please help!:eek:
[One (M7) Original Android Development] alray:
You don't have to flash the boot.img directly. Install the kernel using the aroma installer in custom recovery.
[One (M7) Original Android Development] •Zanna:
I was in the same situation of de.dari, I spent a lot of time to search for boot.img and I've never thought about flashing via recovery. Thank you very much, it works!
[One (M7) Original Android Development] Beast Power:
Better link to ElementalX 19.4 : https://www.androidfilehost.com/?fid=95916177934531753
[One (M7) Original Android Development] ultrasound1991:
Info

The latest version has FUSE support?
[One (M7) Original Android Development] carlowise:
I have this kernel on 2 htc one phones, and dtw option and logo to wake and button notification option.

on one device my screen was dead at the bottom, changing colours etc. and on other device back button dies

both devices I returned on service

I'm interested could that be because of the kernel? does the screen and buttons have power all the time because of the gestures nad screen dies becuese of it?

just asking, TNX
[One (M7) Original Android Development] Sebby:
the only problem with 19.5 is if i shutdown the phone (completely turned off) en then press the power button to turn it on

then it stuck on the splash screen

then if i hold the power button to turn it off again ,and then if it turns on again then it goes past the splash screen and boots up

i tryed all tricks on this threat but no go
[One (M7) Original Android Development] HzeMaffe:
Tried plugging and unplugging USB-cord?
[One (M7) Original Android Development] Sebby:
i have it not on the usb

from viperone 8.0.0 i turn it completely off

then i turn it on en it is stuck on splash

i had the same problem with kitkat ,but with lollipop kernel it is worse
[One (M7) Original Android Development] melando:
Someone suggested (instead of shutting down) rebooting into bootloader and then selecting power off from bootloader... then it should boot up OK
[One (M7) Original Android Development] dena994:
Is multirom supported by this kernel?
[One (M7) Original Android Development] melando:
Yes
[One (M7) Original Android Development] angelsomething:
having the same problem. Any ideas?
[One (M7) Original Android Development] RyuzakiTA:
Flash 19.4 , wipe dalvik and cache, flash 19.5, wipe dalvik and cache
[One (M7) Original Android Development] afcrib:
Flash 19.4 then 19.5. If still doesn't work then flash-wipe-flash-wipe. Worked for me!

Cheers

ps- [MENTION=4329711]RyuzakiTA[/MENTION] was faster :) follow his advice
[One (M7) Original Android Development] MrFoF:
I like it. Thanks!
[One (M7) Original Android Development] panbambaryla:
Instead of doing such tricks could someone script-tallented check what's the difference between install rules and give us the solution, please? [emoji6]
[One (M7) Original Android Development] fabioaalves:
Me to!

is this kernel related or firmware!? bootloader 1.61
[One (M7) Original Android Development] Sebby:
removed
[One (M7) Original Android Development] tichyline:
I'm using ViperOne8 and after flashing the Elemental 19.5 also stuck on splash screen so I only wait for 4-5 min and then just long press the power off button and then power on -> Rom was starting normal and without any issues.
[One (M7) Original Android Development] Mikanoshi:
So, who knows how to make adb remount work with enforcing selinux and SuperSU?

It only works like that:

> adb shell
# su
# mount -o rw,remount /system

adb is already running as root, but without executing su it still says "permission denied"
[One (M7) Original Android Development] flar2:
paste the kernel log message that occurs when you try this and I will construct a supolicy statement. And I will add it to the next kernel release, which is probably tonight.
[One (M7) Original Android Development] Mikanoshi:
<6>[ 842.682435] c0 321 type=1400 audit(1426168397.925:782): avc: denied { search } for pid=7112 comm="adbd" name="block" dev="tmpfs" ino=7631 scontext=u:r:adbd:s0 tcontext=u:object_r:block_device:s0 tclass=dir permissive=0

and this is when I'm trying to "mount -o rw,remount /system" without su first, but adb is already running as root ("adb root" says that).

<6>[ 1283.852494] c0 321 type=1400 audit(1426168839.095:806): avc: denied { search } for pid=7776 comm="mount" name="block" dev="tmpfs" ino=7631 scontext=u:r:shell:s0 tcontext=u:object_r:block_device:s0 tclass=dir permissive=0
<6>[ 1283.853868] c0 321 type=1400 audit(1426168839.095:807): avc: denied { remount } for pid=7776 comm="mount" scontext=u:r:shell:s0 tcontext=u:object_r:labeledfs:s0 tclass=filesystem permissive=0

Maybe a problem with adb.

# cd /sys/class/thermal/thermal_zone0/
cd: /sys/class/thermal/thermal_zone0: Permission denied

type=1400 audit(1426169085.719:824): avc: denied { search } for pid=7744 comm="sh" name="thermal_zone0" dev="sysfs" ino=15074 scontext=u:r:shell:s0 tcontext=u:object_r:sysfs_thermal:s0 tclass=dir permissive=0
[One (M7) Original Android Development] flar2:
You definitely have to open a root shell to mount. The initial adb shell root may not be enough. There is a ramdisk setting that will automatically start adb shell as root, but since lollipop, you might have to type su to actually get root.

The supolicy statements are constructed based on the log messages, and depend on having SuperSU installed. I'm at work so going off memory here, but I think they're correct.

First denial:

supolicy --live "allow adbd block_device dir search"

The second messages:

supolicy --live "allow shell block_device dir search" "allow shell labeldfs filesystem remount"

And the thermal message (unrelated to remounting system)

supolicy --live "allow shell sysfs_thermal dir search"
[One (M7) Original Android Development] Mikanoshi:
Thermal errors are gone when in real su,

mount

too. So only adb remount is a problem.

After successfully applying first two patches:

type=1400 audit(1426171213.239:2906): avc: denied { read } for pid=7926 comm="adb" name="usb" dev="tmpfs" ino=7739 scontext=u:r:shell:s0 tcontext=u:object_r:usb_device:s0 tclass=dir permissive=0
[One (M7) Original Android Development] flar2:
supolicy --live "allow shell usb_device dir read"
[One (M7) Original Android Development] Mikanoshi:
I got the idea)) shell or adb/adbd? adbd requires a ****load of permissions. I've done already:

supolicy --live "allow adbd usb_device dir read"
supolicy --live "allow adbd block_device blk_file read"
supolicy --live "allow adbd block_device blk_file open"
supolicy --live "allow adbd block_device blk_file ioctl"
supolicy --live "allow adbd labeledfs filesystem mount"
supolicy --live "allow adbd labeledfs filesystem remount"

Now it asks for

321 type=1400 audit(1426172357.580:4092): avc: denied { sys_admin } for pid=8962 comm="adbd" capability=21 scontext=u:r:adbd:s0 tcontext=u:r:adbd:s0 tclass=capability permissive=0

and supolicy fails

supolicy --live "allow adbd capability adbd sys_admin"
supolicy v2.40 (ndk:armeabi-v7a) - Copyright (C) 2014 - Chainfire

Patching policy ...
-allow:adbd:capability:adbd:sys_admin=fail
- Success
[One (M7) Original Android Development] flar2:
You just had two parameters switched around:

supolicy --live "allow adbd adbd capability sys_admin"

You can also chain these, eg:

supolicy --live "allow adbd block_device blk_file { read open ioctl }"

Check out the "how to su" article by Chainfire.

Is this all just to remount system? I can remount it without any of this.