yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] tiny4579:
Bulletproof is designed to be a more out of the box kernel with no voltage control and stock settings. As I understand from these threads, ElementalX tends to be more experimental and trying features here first. So I find it odd that Bulletproof had logo2menu first.
[One (M7) Original Android Development] flar2:
Bulletproof is stock-ish, primary goal is stability with some added features, no oc or risky performance tweaks, no init scripts or other things that could cause problems.

Elemental will have tons of options and all kinds of ways to get into trouble. Bulletproof is almost finished, I'm just getting going here.
[One (M7) Original Android Development] flar2:
The logo2menu code is simple, it won't cause any troubles. I have it on elemental too (with more options) but I want to finish up a couple other things before I release.

Perflock is enabled because I haven't looked through the code to see what all it does and it doesn't seem to have any ill effect. I've left it enabled on my other kernels recently also.
[One (M7) Original Android Development] Nekromantik:
So you have basic version of logo2menu on here already?
[One (M7) Original Android Development] flar2:
not released yet, it will have full options, I might have time today or, more likely, late tonight to work on this.
[One (M7) Original Android Development] jaythenut:
If you can do logo2wake and logo2sleep like someone else say no names that would be great
[One (M7) Original Android Development] flar2:
You'll be able to choose between logo2wake and sweep2wake
[One (M7) Original Android Development] jaythenut:
Do you think you will do logo2sleep in the future :)
[One (M7) Original Android Development] flar2:
Logo will sleep/wake.
[One (M7) Original Android Development] SPARKY892:
I have the same problem sometimes on EE in the UK using ARHD 9.4 and only use HTC logo as menu and sweep2wake/sleep.
[One (M7) Original Android Development] Pointlol:
Hey flar2, thanks for the great kernel

I was wondering if you could make it possible to allow cpu clocks to stick when setting them manually in an app in your future releases. For most apps this is not needed since the cpu clocks quite smart, but some low demanding games have the cpu running on max speed for some reason (bad programming probably), that's why I'd like to be able to make some Setcpu profiles with lower clocks for them.
[One (M7) Original Android Development] eshiku:
hi flar2. is there any way to change the vibration intensity/strength after i flashed the kernel? this phone's vibration is too powerful, it would even mask the ringtone/notification even if i set up one click or two click above silent.

Thanks! :)
[One (M7) Original Android Development] thejosh86:
Use Trickster Mod from the Playstore dude.

Sent from my HTC One M7
[One (M7) Original Android Development] baste07:
I'm using system tuner pro to set governor and uv all freq

from my incredible mobile
[One (M7) Original Android Development] gatoradeboy:
I'm using stock 4.1.2 rom, do I delete just the files in those directories or delete the whole directory? I tried installing bulletproof with and without camera fix, both times the camera would not work (wifi 5GHz also stopped working).
[One (M7) Original Android Development] ArmedandDangerous:
Can't seem to get my camera working as well. Regardless if I select Camera Fix or not, the camera does not work on stock rooted >.<

1.29.707.16

I also keep getting a HTC Error Report notification every reboot.
[One (M7) Original Android Development] Mrkrackie:
Anyone experience the home button occasionally stops responding when using this kernel?

I am using stock speed undervolted to 850
[One (M7) Original Android Development] ilai:
I hope me too...
[One (M7) Original Android Development] eshiku:
Thank you! :) exactly what i am looking for.
[One (M7) Original Android Development] ossy1337:
This Camera is killing my battery with permanently using light sensor. Is there any fix?
[One (M7) Original Android Development] ArmedandDangerous:
My camera won't even work lol..
[One (M7) Original Android Development] baste07:
camera fix is included in the aroma installer right?
[One (M7) Original Android Development] eshiku:
Yup, i remember seeing a camera fix option in aroma
[One (M7) Original Android Development] MrKudinGTO:
Hah, finally you caught up in my past situation :P I can say the fix is totally not working in .707.16 base. Either change to a custom rom, or downgrade to .707.3 base using RUU. And the camera problem will be fix. (As I remember using .707.3 base w/ this kernel and got no problem w/ the camera, not a even a single fix applied.)
[One (M7) Original Android Development] baste07:
have you tried the flashable camera fix? separate file that is flashed in recovery
[One (M7) Original Android Development] MrKudinGTO:
Tried like, all of them. None of them is giving a solution. :banghead:
[One (M7) Original Android Development] baste07:
hmmmm that's wierd.
[One (M7) Original Android Development] dado750:
Hi guys .....

I installed the kernel on the maximun, everything ok

only one thing, but to change the options, Sweep2Wake, or Logo2Wake, what should I do? where you change?

:):):):):):):)
[One (M7) Original Android Development] inffy:
Read the OP and 2nd post :):):):):):)

*sigh*
[One (M7) Original Android Development] Osama Zabin:
Ok, but maybe you posted some instructions on how to overcome the bootloader problem?
[One (M7) Original Android Development] flar2:
Hold down the power button until it reboots. That's it.

I'm not sure if wiping caches will prevent it or not.
[One (M7) Original Android Development] yooyo3d:
Hi flar2, does this commit really fix turning screen on during phone call?

https://github.com/flar2/m7-GPE-5.0.1/commit/036ecb4ebca4356d3c5f0195fae4169dfbe40323

Im using gpe and I still have this problem with screen.
[One (M7) Original Android Development] flar2:
I think so, but if it doesn't work, try the s2wphonecalldisabler app I made in the nexus 6 forum.
[One (M7) Original Android Development] ABQNM:
Hey [MENTION=4684315]flar2[/MENTION] I just wanted to say all has been well on 19.3 GPe.

There is one minor issue, and that is with the app. The app keeps telling me a new version is available and it wants me to download 19.1 when I am already running 19.3. So it seems that the app has lost track of what the current version is.
[One (M7) Original Android Development] yooyo3d:
Is this commit related with any gestures and features you add in eX? Right now on my m7, all eX features is disabled.
[One (M7) Original Android Development] ABQNM:
The screen turning off on calls issue was fixed in the very first public Lollipop ElementalX release for GPE. I can say that the proximity sensor seems more sensitive on Lollipop though, making it easier to turn the screen back on if you hold the phone in such a way that the proximity sensor isn't covered completely. I had to adjust how I hold my phone slightly once the Lollipop update came out. And this same calibration applied to the stock GPE ROM, so it isn't the kernel causing it.

If you are having issues where the screen isn't shutting off at all in calls, then that would likely be related to the ROM you are running (if it isn't stock) or an app that is modifying the behavior of the proximity sensor. It definitely works with stock GPE, aside from the calibration change that came with Lollipop, as explained above.
[One (M7) Original Android Development] flar2:
I was just waiting for someone to confirm it all worked.

Uploading now, via SSH, from the airport
[One (M7) Original Android Development] ABQNM:
Thanks, sir! Have a good trip!
[One (M7) Original Android Development] yooyo3d:
Im using gpe converted m7 using this rom:

http://xdaforums.com/showthread.php?t=2358781

I didn't notice screen on issue with this rom, but i didnt use stock gpe kernel more than a day.

After that I flashed eX and I have screen-on issue during phone calls. Sometimes, when screen is off on incoming phone call wont turn on.

I tried to flash back stock gpe kernel and modules, then home button does not work... When I press home button it select icon on home screen or nothing happens if im using any app.

Ill try to build eX kernel from git without that commit.
[One (M7) Original Android Development] ABQNM:
OK so maybe I'm misunderstanding your issue. Is the issue when you are in a call or that the screen doesn't wake to alert you when you first receive an incoming call? If it is the latter, are you using anything like Xposed & Gravity Box? I know GB has a setting that makes it so the screen won't power on if the proximity sensor is covered, and though it has an option to disable this on incoming calls, it may not be ready for primetime yet.

As for why your home button doesn't work, this kernel changes some system files too, so you need to reflash the whole /boot and /system partitions to restore the stock functionality.
[One (M7) Original Android Development] yooyo3d:
Both issues.

- In the call screen turns on and I can push onscreen buttonwith my cheek.

- incoming call does not turn on screen.. not frequently.

Is it possible to flash changed files from stock rom instead flashing whole partition? Im looking into eX install script and im trying to make list of changes. After that plan is to extract changed files from stock rom and prepare flashable zip. Will that work or its better to flash stock system and boot img using fastboot?
[One (M7) Original Android Development] ABQNM:
The first part seems like you are experiencing the issues I was having when I first updated to Lollipop. The proximity sensor in calls is more sensitive. I had to start holding the phone so that the proximity sensor (black dots on top left side of phone) stays against my ear. If I try to hold it with my shoulder, the proximity sensor pulls away about an inch and that is enough to activate it since the 5.0.1 GPE update. On Kit Kat, it wasn't quite as sensitive, so it would still recognize as covered when I held it against my shoulder, even if the proximity sensor was an inch or so from my head.

The second part, could be any number of causes. The most likely being that the phone needs to be rebooted. Unfortunately Lollipop still eats up memory and slows down over a few days. It isn't as quick as the Nexus 5, but it does eventually run out of memory and start closing programs and generally being slow to load processes due to limited RAM. Rebooting every other day seems to help. It seems like HTC is holding off on an update until 5.1 is finished, so hopefully this will be addressed.

Also, it could be even just an excess of background apps causing it. If you have many apps doing things when the screen is off, it can cause the incoming call process to lag, not turning the display on, the same as if it is out of memory due to the above issue. Both low memory and high CPU usage could both cause a slow incoming call screen. I have experienced it once, but that was before I started rebooting regularly. I think my phone was up for over a week when it happened. If it wasn't over a week, it was definitely close.

And this happens irrelevant of the kernel. It is either due to the ROM memory bug or programs taking up excess resources. The kernel is definitely causing this behavior.

Edit: and as to your flashable zip idea, it could work, theoretically. I have done that before many times over the years. Just make sure it gets everything. And if something isn't working right, then reflash it the proper way. And then remember to flash SuperSU again if you go this route (if the ROM doesn't include it already).
[One (M7) Original Android Development] yooyo3d:
Thanks on detailed informations. I have flashed boot and system from stock kernel and I'll use it few days to check how it works.
[One (M7) Original Android Development] salmanati:
ElementalX 19.5 Working Fine And Smooth As Always In Latest Insertcoin Build 7.19.401.2 Thanks Again Flar For Updates And Thid Awsome Kernel
[One (M7) Original Android Development] G3R0:
Yesterday installed Lollipop on HTC One M7. Then I installed ElementalX 19.5(Sense 6 Android 5.0.2) in the way as always before for KitKat (ElementalX version was 18). I wiped cache and dalvik cache. Installed ElementalX and waited 15seconds before finish and reboot.

But it is not working. My phone is in boot loop. The HTC sign is showing and the rebooting. I tried it several times and the result is the same every time. Finally then restored boot.img with TWRP (2.8.5.0) so now I can use my phone. Please help me, why is ElementalX 19.5 no working on HTC One M7 Loilliop (7.19.401.2)?

What am I doing wrong? The previous versions of ElementalX on previous versions of Android always worked.

Sorry for my bad english...
[One (M7) Original Android Development] shivasrage:
Read first Post......

flar2 writes in big letters:

"Occasionally it can take a long time to boot. It's something to do with HTC's bootloader. If it doesn't start after a few minutes, just hold down the power button until it restarts. Don't worry, it will boot."

but no worries I also "overreaded" it..
[One (M7) Original Android Development] G3R0:
Thanks. But my problem is not the same. My phone is boot looping and not waiting a long time to boot. It shows HTC splash screen and reboots....
[One (M7) Original Android Development] G3R0:
Thanks for everybody.

Installed ElementalX 19.4, cleared cache & dalvik. Rebooted 2x.

Installed ElementalX 19.5, cleared cache & dalvik. Now I am waiting to finish optimizing apps. I think it will work now. Finnaly.
[One (M7) Original Android Development] commencal661:
That was happening to me too. Weird, and I couldn't find a solution.
[One (M7) Original Android Development] G3R0:
Installed ElementalX 19.4, cleared cache & dalvik. Rebooted 2x.

Installed ElementalX 19.5, cleared cache & dalvik. Now it works finally. I don't know why did it not work directly from ElementalX 19.5 install.
[One (M7) Original Android Development] commencal661:
Thanks, I'll try that method later when I can.
[One (M7) Original Android Development] RyuzakiTA:
Hi, I'm on 19.5, s-off and lollipop (maximusHD 52), but if I try to do something in sys, for example overwrite a file, it says that I can't..
[One (M7) Original Android Development] aoryx:
Any one has xprivacy working on 19.5?
[One (M7) Original Android Development] ABQNM:
Unless you set the SELinux status to permissive, you can't write to anything but the /sdcard partition, and even then, you can't access things like the TWRP directory without setting it to permissive. This can be done from the aroma installer.
[One (M7) Original Android Development] Mateo20w:
my phone doesn't boot after instaling 19.5, what can i do now? i don't make any backup from lollipop rom, now i have bootloop :/ my phone restarting every time and still nothing, i try to do factory reset and no way. any help?

---------- Post added at 12:32 AM ---------- Previous post was at 12:10 AM ----------

when i try to to factory reset (twrp) and try to reboot twrp write no OS instaled, i don't know what to do now.
[One (M7) Original Android Development] joriq:
dirty flash the rom?

push the rom via adb, if you deleted the rom file from SD? :confused:
[One (M7) Original Android Development] Mateo20w:
i was stupid, my htc is S-on ,today i get OTA software update to lollipop, after this i install TWRP and i install elemental and i have bootloop., now i think i fix it i just plug phone to pc and i have my old file 6.09.401.12 and i transfer it using twrp in mount option, phone is boot with kitkat, i'm gonna push one more time OTA to lollipop, do a backup and push elemental 19.4 version. Thanks for reply and sorry for trouble, i think HTC one is hard to brick.and sorry for my english i'am from Poland.
[One (M7) Original Android Development] deeevan:
I'm having issues with tethering (over Bluetooth and Wifi), any ideas on how to troubleshoot this? I wasn't able to track it down until I did a ROM update and had to reflash everything and tested tethering after each flash.

Flashed ARHD 91.0 (tethering OK), santod040 mod#10 (OK), EX 19.5 (tethering failed).

Devices connect to the phone, get IP address and gateway settings over Wifi, but are unable to access the internet. Was previously on ARHD 90.1 and EX 19.2/19.4 with the same issue. I can't see any particular EX Aroma options that touch the network?

Edit: Go figure, I swapped order around and tethering is fine.

Flashed ARHD 91.0 (tethering OK), EX 19.5 (OK), santod040 mod#10 (OK)
[One (M7) Original Android Development] niravnn:
Adb stopped working after flashing this kernel. Did I disabled it in aroma?? I'm noob

---------- Post added at 02:23 PM ---------- Previous post was at 01:54 PM ----------

Edit :- started working
[One (M7) Original Android Development] RyuzakiTA:
I'm on permessive..
[One (M7) Original Android Development] dtbinh:
I've cleared cache & dalvik, my device still can't boot.
[One (M7) Original Android Development] :
[MENTION=4684315]flar2[/MENTION]

Is this kernel source useful for you?

http://www.htcdev.com/devcenter/downloads/
[One (M7) Original Android Development] niravnn:
It's for developer edition. So I think it won't be useful for m7u or m7ul
[One (M7) Original Android Development] flar2:
Yes, it will definite help. But I'm 2000 miles from my computer for the next week.
[One (M7) Original Android Development] Mikanoshi:
I also have that bug when it's stuck on splash screen, but I just connect USB (or disconnect if it's connected) and it goes to bootanimation and boots just fine :)
[One (M7) Original Android Development] guy4jesuschrist:
You probably already saw this [MENTION=4684315]flar2[/MENTION], but just in case you didn't...

http://www.androidpolice.com/2015/0...lipop-kernel-source-one-m7-developer-edition/

Enjoy! :)

EDIT: Oops, forgot to skip forward to see if anyone else had already mentioned it, and thought I was already on the most recent page.
[One (M7) Original Android Development] crybert:
I have a little question. I am using the ElementalX app but I can only apply the included performance mode. The included powersave mode is not available. Is this a normal behaviour because this feature isn't supported yet? I'm on MaximusHD 52 and ElementalX 19.5.
[One (M7) Original Android Development] okmat:
Loooooooong time to boot

In my case this is not an occasional thing, it happens just about every time I restart my phone. The problem goes away when the phone is plugged in to the charger/USB port. I'm using Android Revolution HD ROM with lollipop 5.0.2.

With the stock Kernel this problem does not exist. Is there any fix for this? this is a big deal for me, please anyone?
[One (M7) Original Android Development] ABQNM:
Are you powering it off completely and back on or using some software method to "reboot" the phone? I have found that the Lollipop bootloader doesn't like restarts. I had to stop using Gravity Box advanced power menu reboot command since nearly every time I did, it would hang on the splash screen. If I power off and then back on as it was designed, it never hangs on the splash screen. It always boots properly as long as I power it down completely rather than "rebooting" it.
[One (M7) Original Android Development] okmat:
I'm rebooting my phone normally, as it was designed, by pressing and holding the power button for a couple of seconds, then selecting "restart" from the menu. After reading your post I've tried the "power Off" option and it hung in the splash screen anyway.

As soon as I plug the charger the boot starts normally.
[One (M7) Original Android Development] Thela7:
Wait just a second. Are you using Lolipop now Mikanoshi? ?

Send from my TV remote control
[One (M7) Original Android Development] Mikanoshi:
Where have you been?)

http://xdaforums.com/showpost.php?p=59099841&postcount=2648
[One (M7) Original Android Development] ABQNM:
Ah, sorry I forgot that Sense included the restart option. Stock Lollipop, like that on my Google Play Edition, only has a "power off" option. On my GPE, I only experience the hang at the splash screen when I reboot using the terminal (su reboot) or using xposed modules that add the reboot option to the power menu. When I power it off normally and back on, it never gets stuck, so I was offering that as a suggestion since it could help if the bootloader issue happened to be the same for Sense & GPE.
[One (M7) Original Android Development] PocehNeheb:
USB changes

can you make the USB gadget driver non-removable(fixed)? I believe the specific change is here: https://github.com/flar2/m7-GPE-5.0.1/blob/master/drivers/usb/gadget/android.c#L1623

Actually I got another idea. Can you increase the number of LUNs from 1 to 2? This would allow clever stuff with DriveDroid like Live Persistence.
[One (M7) Original Android Development] dinoc:
I have ElementalX-m7-19.5-Sense on my HTC One M7, and I disabled all swipe gestures and all swipe to wake or swipe to sleep, and disabled all logo menu pr others related to logo, but I can still wake up the phone by swiping over the buttons, why is that?
[One (M7) Original Android Development] justion:
Same here. Disabled lock by pressing htc logo but it's locking anyway elementalx 18.0
[One (M7) Original Android Development] MaratabHashmi:
Battery life ??
[One (M7) Original Android Development] Mikanoshi:
You are right)
[One (M7) Original Android Development] herwegan:
Hi [MENTION=4684315]flar2[/MENTION], whats the command for the init.d file to set TCP and io readahead in your kernel? :)
[One (M7) Original Android Development] Osama Zabin:
Is it .better with LP compared to KK?
[One (M7) Original Android Development] fabioaalves:
with a big difference ! :)

very nice for a device with 2 years !

i think i am gonna pass the m9. Don't need a new phone. m7 is still , fast, responsive, good battery , camera fine for a phone,, perfect dimensions!

maybe m10 ;)
[One (M7) Original Android Development] darkdevu:
:d very stable
[One (M7) Original Android Development] Mikanoshi:
Really doesn't matter, if on KK there were no major wakelocks.

5 hours of SOT on 50% brightness watching youtube videos over Wi-Fi , 1-2% in 7-8 hours of standby. It was like that when I bought it, it's the same now.

I don't know why so many people say it's a lot better, maybe because I was making it better for myself on every android already))
[One (M7) Original Android Development] guapinoy:
What ROM are you using?
[One (M7) Original Android Development] airwave_88:
Same issue here - Elemental-X 19.5, Maximus 52.0.0. No difference whether a shutdown or a reboot, the phone gets stuck at the splash screen. Once I plug and/or unplug the USB cable, it goes ahead as if it were a jump start.
[One (M7) Original Android Development] herwegan:
Anyone else knows this?
[One (M7) Original Android Development] lagittaja:
I'm having the same issue as these guys are having. Endless bootloop no matter what.

flar2, are we doing something wrong? Or is the stock rom just incompatible with EX?

My phone is completely stock with 7.19.401.2 except for S-OFF / Unlocked / TWRP 2.6.3.3.

adb reboot-bootloader

go to recovery

wipe cache + dalvik cache

install EX 19.5

Phone tries to reboot but endless bootloop ensues.

Also tried to flash with TWRP 2.8.5.0. Still the same story. After flashing I end up with the same neverending prrtt splash screen prrrt splash screen and so on and so forth.

Also I tried wiping cache+dalvik after, different settings in aroma for example the SELinux thingadoodler and so on.

Fortunately restoring boot is easy.

Would have preferred to use stock ROM and your kernel for the time being.
[One (M7) Original Android Development] :
On splash screen plug-in your USB cable.
[One (M7) Original Android Development] lagittaja:
Did not work. Tried everything I could think off.
[One (M7) Original Android Development] maxpaynezm:
This work great
[One (M7) Original Android Development] MaratabHashmi:
MaximusHD 52
[One (M7) Original Android Development] lagittaja:
That actually did the trick. The hell? flar2?

This should be included to the OP, "easy one-time setup" ahem :D