yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] flar2:
Glad to know it works, I didn't test it myself.
[One (M7) Original Android Development] ABQNM:
Yep you got it right. I'm probably the only one using it, but I appreciate it nonetheless. I hope it wasn't too much work.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] millicent:
How should I increase the min cpu while screen off? Apparently I need to do that in order to prevent Bluetooth streaming skipping and other issues. Thanks

Sent from my HTC One
[One (M7) Original Android Development] ABQNM:
[MENTION=4684315]flar2[/MENTION] get ready... Looks like Lollipop for GPE is on its way right now. Hopefully kernel source won't be too far behind.

https://twitter.com/Ethan__j99/status/540719598383792128

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] flar2:
Good news is: source is already posted.

Bad news is: I have to go to sleep, and then I have to work, and then I have guests at my house until Monday.

But I will probably find some time late tomorrow night and hopefully it will be relatively easy to apply my patches to the new source.
[One (M7) Original Android Development] ABQNM:
Wow, that was fast. I was still looking for the link to the source when you replied (I don't keep it handy since I can't do anything with it anyway).

Now I'm all sad and happy at the same time. I really want Lollipop, but will miss xposed and (for a while) ElementalX, especially now that I have a powersave mode, but I guess I won't need that with Lollipop anyway. I wonder if HTC decided to leave tap to wake in there? That would be neat. I doubt it, but it would be nice if they did. As long as SuperSU works without a kernel patch I think I can survive with the stock kernel until you have time to work on it. You have a life to live that comes first, so I don't expect you to give that up and make a Lollipop GPE kernel instead. I'll find plenty to play with in the mean time.

HTC has officially taken my day off tomorrow from me though since now I will be spending all day playing with putting this thing back to stock so I can try out some Lollipop.

Anyway, have a good night and I look forward to some Lollipop flavored ElementalX when you get some time to work on it.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] cannondaleV2000:
hey you satw my tweet XD i have worked on lollipop kernels a bit. your patches should go fairly easily. theres verry few changed between the kk kernel and the L kernel. i have already compared them
[One (M7) Original Android Development] belek1979:
OMG, you are right! I was thinking of screen buttons...

Any way to get rid of that bar with buttons?https://docs.google.com/file/d/0B6Ojd4m34YkrblZGTXhBZGh1WGc/edit?usp=docslist_api
[One (M7) Original Android Development] exglade:
I've been using ElementalX on my HTC One M7 (with Stock ROM) for around 2 months. And I like it, thanks flar2.

However, there is a minor nuisance. Sweep2Wake will always be enabled even if I unchecked all the options in the setup.

Today, I decided to take a look into it.

Here is the log:

Fri Dec 5 21:03:11 MYT 2014
PVS: 2
Powersave bias is
Button Light Notification enabled
USB Fastcharge disabled
Sweep2wake
DoubleTap2Wake fullscreen enabled
Wake gestures disabled
Logo2Wake enabled
Pocket detection enabled
Sweep2sleep left and right enabled
logo2menu disabled
HTC color enhance enabled
FIOPS io scheduler
Stock GPU
Ondemand GPU Governor

From my understanding, 99elementalx suppose to write "Sweep2wake 15" (as example) according to "echo Sweep2wake $S2W >> $ELEX_LOGFILE;". As seen from the above, there is no integer following.

I suspect there is nothing wrong with "grep" so I removed the "cut" statement (and hardcoded "echo 3" as my desired setting just to avoid outputting inappropriate value for the config):

S2W="`grep S2W $ELEX_CONF`"
echo 3 > /sys/android_touch/sweep2wake

The result is the log able to display "Sweep2wake S2W=3". Strangely, I don't think there is anything wrong with the "cut" statement either.

Any clue? Sorry that I don't have much experience with Linux environment.
[One (M7) Original Android Development] synt3k:
How dare you invite guests over for the weekend when a new system update has been released!? I searched, but I couldn't find the thread where you were asking XDA for permission to have a personal life. What nerve! Get back to work. /s

..Sarcasm aside, GPE 5.0.1 seems surprisingly stable for me so far, can't wait to have ElementalX when you get a chance to build it. I know you have a tendency to post "unofficial" updates inside the thread, will the ElementalX app be able to find these or should we just stay up to date on this thread? Again, thanks so much for an amazing kernel with an incredibly professional app to control the settings. :good:
[One (M7) Original Android Development] ZaneChua:
Having some issues as I can't seem to get usb to work. The last time i remembered it had something to do with fast charge being enabled. Any Ideas flair?
[One (M7) Original Android Development] ABQNM:
That is a pretty vague question. You need to provide details. What ROM and kernel version? Do you have USB fast charge enabled? What happens when you connect to the PC? What OS is on the PC? Have you tried a different cable? A different PC?

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] ZaneChua:
Tried over 4 different cables, no difference.

Using both Windows and OS X.

Both see nothing in either adb or fastboot.

I had USB Fast Charge enabled but I've since tried to flash other ROMs to see if that would solve the problem but it doesn't.

If I remember correctly, the only way to solve the problem was to flash a full default RUU over. I can't do it because fastboot usb isn't even detecting my phone

I was running GPE 4.4.4 with Elemental X 15.1 Kernel.
[One (M7) Original Android Development] stefanorickeets:
Do you have ADB and Fastboot installed on your PC? If not, download and install this --> http://xdaforums.com/showthread.php?t=2588979. For ADB, make sure USB debugging is enabled under Developer options settings.

Also, you can try flashing the GPE 4.4.4 OTA zip again via stock recovery to fix the fastboot not being detected issue. You can find the GPE 4.4.4 OTA (KTU84P from KTU84L) in this thread --> http://xdaforums.com/showthread.php?t=2532491. If the fastboot problem is hboot related then the OTA will flash a new undamaged hboot.

Note: You can use the app Flashify (http://xdaforums.com/showthread.php?t=2349847) to flash the stock recovery image (which you can find in the firmware.zip file in the OTA zip).
[One (M7) Original Android Development] ABQNM:
There is no need to flash am ruu to disable fast charge. There are plenty of easier ways, but reflashing the rom would have turned it off (assuming you didn't also flash the kernel with the option enabled again).

I'm not familiar with Mac, other than typically when you plug it in, it shows up right away, no drivers needed. On Windows, when you were in the bootloader and you plugged the phone in, what exactly happened? Did you get the beep like it was connected and a message about drivers being installed? Or a message about failed driver installation? Does the phone appear in the Device Manager? If so, does it have an exclamation point indicating a driver issue?

If none of this happens when you connect it and it isn't recognized at all--in device manager, no beeps, etc., it sounds more like a hardware issue, either with the cable or the USB port.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] patience88:
[MENTION=4684315]flar2[/MENTION] hello sir, i've a problem with the licening off your app. It states that there are problems with the licensing i've got to buy the app. Can you help me? Thanx for all your help

Sent from my HTC One using Xparent BlueTapatalk 2
[One (M7) Original Android Development] ABQNM:
I assume you purchased the app originally, correct? License issues like this can happen if there is no network connection when the license check runs. Make sure the phone is connected to the network (wifi or cellular is fine), the Play Store is signed in using the account you purchased the app with and try opening the app again (you may need to force close the app first or reboot the device).

If that doesn't help, maybe flar2 will have a better answer, but that is the most common procedure to resolve a license check issue.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] patience88:
Thanx for your answer. Yes i purchased the app. But your sollution did not work

Sent from my HTC One using Xparent BlueTapatalk 2
[One (M7) Original Android Development] flar2:
Make sure google play services is running and thst you are signed in with the account you used to purchase. Could also be an issue with network connectivity or googles servers.
[One (M7) Original Android Development] patience88:
Thanx but that did not help. I Uninstalled the app and re installed. But still no luck.

Sent from my HTC One using Xparent BlueTapatalk 2
[One (M7) Original Android Development] flar2:
If you've been trying over and over again, google will lock you out. You probably will have to wait for a few hours now.
[One (M7) Original Android Development] patience88:
Ok i'll try later again. Thank you very much

Sent from my HTC One using Xparent BlueTapatalk 2
[One (M7) Original Android Development] ZaneChua:
How would you use the stock recovery to flash the OTA zip though? Can the OTA Zip be stored in internal storage for flashing?

I'm not sure if it's a hardware issue because I have had this before and solved it with an RUU. My fastboot OS- line is showing me blank. So it might have something to do with that.
[One (M7) Original Android Development] stefanorickeets:
Yes, you can flash the OTA manually by storing the zip on the device's internal storage and following the instructions mentioned in this article --> http://www.androidcentral.com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat.
[One (M7) Original Android Development] ZaneChua:
Okay. Hmm. I think I'll need to find a 4.4.4 GPe TWRP Backup then. I've already used a 5.0 Backup to update. I'm only concerned is the phone's firmware isn't updated and of course that the OS - Line in Fasboot is still blank.

EDIT: That probably wouldn't matter anymore. Have a phone with TWRP 2.7.1.1 with no OS in it and adb or fastboot doesn't detect it. Looks llike a real bricked phone here.
[One (M7) Original Android Development] Osama Zabin:
The blank OS version in fastboot is known problem with twrp 2.7.x.x versions, it's just a cosmetic problem, if you want to bring it back, reflash your firmware ( if you remember it) then flash twrp 2.6.x.x or 2.8.x.x, these two series DON'T wipe OS version.
[One (M7) Original Android Development] ZaneChua:
I see. So my device has it's own issues I guess. There's something really weird going on with the usb port right now. It's not detecting adb or fastboot, but it detects when I plug in an OTG device but it refuses to mount it. Now I'm just trying to find out what's the device name but can't seem to.
[One (M7) Original Android Development] mitchst2:
Lollipop SD fix http://xdaforums.com/showthread.php?p=57307929

Sent from my HTC One
[One (M7) Original Android Development] patience88:
[MENTION=4684315]flar2[/MENTION] i still have the problem with licence. Its driving me nuts. Can you please look into it?

Sent from my HTC One using Xparent BlueTapatalk 2
[One (M7) Original Android Development] Rix70:
Hi guys, the MUST KERNEL EX 15.1 is compatible with LOllipop 5.0?

Thanks in advanced..
[One (M7) Original Android Development] Shizophren:
Whats a MUST Kernel?

In the first post theres nothing metioned about Lollipop.

Just:

Google Play Edition Android 4.4.3/4.4.4
[One (M7) Original Android Development] Rix70:
SORRY...for me EX is THE KERNEL....i use only this on my ONE..

I'm Italian and I explained bad little ago!! :p

Flar is the number ONE.

I hoped it was compatible to try GPE 5.0.

wait for the new version for EX 5.0 and then try.

still excuse..
[One (M7) Original Android Development] flar2:
Lollipop kernel is coming soon
[One (M7) Original Android Development] flar2:
Make sure you are still a member of the g+ community and signed up as a beta tester and logged into google play services and have an internet connection and that google play services is running and signed in, all with the same account you bought the app with.

I'm not sure why you're having trouble, but there's not much I can do because it is google that has the licensing mechanism.
[One (M7) Original Android Development] flar2:
Update!!!!

For Android 5.0.1 Lollipop Google Play Edition

Same changelog as the latest Sense version

Source: https://github.com/flar2/m7-GPE-5.0.1

Download:

ElementalX-m7-19.0-GPE
[One (M7) Original Android Development] Artc0re:
Do you also used the sd fix from last thread page?
[One (M7) Original Android Development] Thijssie909:
Awesome!
[One (M7) Original Android Development] ABQNM:
Confirmed touchscreen patch during calls is working. All is good now. Thanks!

Sent from my brain using human to phone transport technology.

---------- Post added at 11:54 AM ---------- Previous post was at 11:53 AM ----------

What is that supposed to fix exactly?

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] Artc0re:
[MENTION=587643]ABQNM[/MENTION] it fix the mout of the storage for file explorers and for the computer
[One (M7) Original Android Development] ABQNM:
Ah OK. I was just curious as I didn't notice any issues with the stock kernel or while testing ElementalX when using a file explorer. Though I didn't try connecting to the PC. I don't even know the last time I connected with a USB cable.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] Thijssie909:
Everything seems nice and smooth! Thanks a lot!
[One (M7) Original Android Development] cakaostojic:
Uninstall app for day or 2 then install it again that will do it. Something is messed up with google licensing
[One (M7) Original Android Development] mitchst2:
Thanks for this. I'm sure everyone appreciates you finding the time to get this done so quickly.

Sent from my HTC One
[One (M7) Original Android Development] Helmut_TuT_GuT:
short guide how to install ? or just flash through twrp
[One (M7) Original Android Development] ziaulh.ch:
Flash.

Button notification is in the aroma but we don't have button light? [emoji3]
[One (M7) Original Android Development] ABQNM:
Yeah the button lights were broken by HTC. Probably forgotten when they split the software branch off for the m7 from the m8 (that has onscreen keys). I personally disable the capacitive keys and enable the onscreen navigation keys anyway so it doesn't bother me.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] Helmut_TuT_GuT:
stupid question i got gpe 5 ota with all stock, flashed now recovery.

Do i need to be root to install the kernel ?

If yes what do i have to do know to gain root acces ?

If not i would still like to know how to gain root acces
[One (M7) Original Android Development] ABQNM:
To root, install SuperSU 2.37 from this thread. http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Just flash in recovery and reboot. Then flash the kernel and reboot twice. You don't have to have root for the kernel, but you need it for most of the advanced features of the kernel, so it is recommended to have root before flashing the kernel.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] datrix:
The root is not necessary.

I have flashed from recovery without performing any rooting procedure.

[MENTION=4684315]flar2[/MENTION]

Thx for your awesome work!
[One (M7) Original Android Development] ABQNM:
Yeah you only need root if you want to customize the features of the kernel. You can just flash it and use it as is without root.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] sikander3786:
S2W settings not sticking in GPE 19.0

First of all, thanks for this Kernel. Have been using it for almost half a year now and am very pleased with the performance and stability. Can't appreciate enough.

Noticed a small bug in GPE 19.0 version. I only like D2W and leave S2W disabled but am unable to disable it in this version. Selecting none for S2W in Aroma results in "S2W=0" in "/etc/elementalx.conf" but S2W doesn't turn off. "/sys/android_touch/sweep2wake" reads "S2W=15". Editing it manually to " 0" still reverts it to "15" on reboot despite that "/etc/elementalx.conf" still stays at "S2W=0".

BTW, permissions in "/sys/android_touch" read as "rw-r--r--" for some files and "rw-rw-rw-" for the rest including "sweep2wake". Is it meant to be that way?
[One (M7) Original Android Development] Artc0re:
[MENTION=4684315]flar2[/MENTION] do you know what the native powersaver mode of Lollipop does? I want know it because i want compare it with the mode of your app.
[One (M7) Original Android Development] ABQNM:
It is supposed to "reduce performance and background data" but I couldn't see any reduction in cpu speed on the stock kernel. It may change the tuning of mpdecision or governor performance but I couldn't verify this. Since Friday, I have actually been using it in conjunction with the ElementalX powersave mode from the ElementalX app with no negative effects. It does completely disable vibration as opposed to the ElementalX powersave that can only decrease the vibration to a very minimal level. So they both actually work well together in my experience. I have Lollipop's powersave set to come on at 15% and the ElementalX comes on at the same level.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] stefanucci75:
Hi flar2 thanks for your great work. I installed the latest version 19.0 GPE. As usual, everything works great, I only noticed a problem, I have selected to wake up the phone just double tap wake full screen but the phone wakes up also with a swipe up and with a swipe down. Can you fix this?

Thanks, bye.
[One (M7) Original Android Development] stefanorickeets:
Same here.
[One (M7) Original Android Development] ABQNM:
If you have the ElementalX app, you can disable this in the app. If you don't, then it will likely take a fix from flar2.

I noticed this in testing, but actually thought the app was turning this feature on, not the kernel itself since the elementalx.conf file showed it as disabled and only the app shows it as enabled. When I disabled it in the app, it went away without issue, so I was assuming it was the app causing the issue, which wouldn't affect most people and was easy to turn off if it did. Apparently the issue was deeper than that, as reported a few posts back.

He doesn't have a GPE version of the m7 to test on, so some minor issues can get though. I'm sure he will have a fix available soon enough. Remember he has house guests this weekend and so try not to give him too hard of a time. ?

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] D€INOS:
GPE 19.0 works great!

Thanks flar2, awsome and quick work! 19.0 works like a charm!!

A feature like logo2 recent apps in the works?
[One (M7) Original Android Development] ABQNM:
I'm not going to lie, I was concerned that I wouldn't be happy with the battery life with all the complaints about battery life on the Nexus devices after the Lollipop update. I have been running Lollipop since it was released and ElementalX since Friday night and battery has been great. Better battery life than Kit Kat and performance is also much better than Kit Kat.

Today, I have been using my phone heavily, and am at over 9 hours on battery with just over 4 hours of screen on time, about 30 minutes of GPS, an 8% drop when I was in recovery flashing the release kernel over the test kernel (which could have given me probably another 45 minutes of usage), some phone calls, mixed wifi and LTE data usage and I am still at 20% and the phone says I have 3 hours left. I could easily get another hour of screen on time out of it, maybe even an hour and a half. If I left it completely idle, it would probably go for about 5 hours, not even counting what would happen when battery saver kicks in.

And this is with all of my accounts from multiple apps syncing and background data on and no battery saving apps of any kind in use. Not overclocked. I always felt that the Kit Kat GPE ROM was a bit sluggish and needed constant tending to get decent battery life, but the Lollipop GPE update is FAST (like night and day difference) and battery life is far better than I expected.

This is definitely the update this phone needed. It is a completely new device.

Link to second image since the forum keeps killing off the second image instead of displaying it.

http://imgur.com/LmvHW9h

Edit:

And now my final results. 11hr 2min off the charger to 1%. 5hr 8min of screen on time using adaptive brightness. 2hr 33min of LTE data usage, the rest wifi. Approximately 30 minutes of GPS. And an 8% loss when I was in recovery doing a backup and flashing the production kernel over the test kernel, which likely equated to about 45min of usage that I lost.

So, needless to say, I am VERY impressed with how it handles on a heavy usage day. I can expect to get through a light to medium usage day with plenty of battery to spare. Bone stock 5.0.1 GPE with ElementalX at stock speed and stock mpdecision. No battery saving apps installed. Power saver set to come on at 15%.

Final screenshots.

http://imgur.com/7PuPq4B

http://imgur.com/ILQBnxq

http://imgur.com/uyrvLS0

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] ace-user:
How to u disable capacitive keys and enable on screen keys? I tried lots of ways but most doesn't work well.
[One (M7) Original Android Development] king_david43:
What rom are you using?
[One (M7) Original Android Development] ABQNM:
Bone stock GPE 5.0.1.

Sent from my brain using human to phone transport technology.

---------- Post added at 10:05 PM ---------- Previous post was at 09:59 PM ----------

Add the following line to the /system/build.prop which enables the nav bar.

qemu.hw.mainkeys=0

And then I made a quick zip file to flash in recovery that replaces the key layout file with one that disables the capacitive keys. You have to flash it after flashing the kernel since the kernel includes a key layout file that is used for the logo2menu feature and will re-enable them every time you flash the kernel. https://docs.google.com/file/d/0B90_ZpVR6o9nYWxkTmU0eDFDVVk/edit?usp=docslist_api&authkey=CPim-LQH

Edit: instructions to revert if you don't like the onscreen keys: either flash the kernel again or flash the following file https://docs.google.com/file/d/0B90_ZpVR6o9ncGZZdnc3WlRjT0k/edit?usp=docslist_api&authkey=CMbpg54D

This will restore the capacitive keys. Then just delete the line you added from the build.prop and reboot and the nav bar will be gone and your capacitive keys will be back to normal. (minus the backlight until HTC fixes that)

Sent from my brain using human to phone transport technology.