yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Dissmeister:
Faux Sound, V4A and ERA

I know this is a bit of a late reply and maybe others have done before me, but just to straighten out the facts with the three in subject and provide my opinion on the matter. If the kernel supports fauxsound (my rom is GPE on ElementalX, so it does), it does have a huge effect, mainly volume increase. Not noticeable with external speaker but with headphones and in-call speaker volume, it makes a world of a difference. However, there are a few bugs with it, like the effect not taking control immediately. I have found the best fix for this- set the volume level on the FS app while the music is playing, then make a quick call and cut the line. This pauses the music and when it resumes, the volume increase effect is there.

If you're a master of V4A, you have the perfect audio out already. I understand yours backfired, but Im sure this is not the case for the majority of users. Combine ERA with V4A, especially Impulse Responses (I have Zeros presets currently), DDC (Mine is on Monster Diesel Vectr), and Dynamic System, and you get some serious audio quality out. Tinker around with every option to get that perfect quality out. Once you master the learning process, you are good to go.

Of course ERA makes everything better, but to me, the Dolby enhancements significantly degraded the audio quality (again, my opinion here), so I have disabled it and switched back to the old IRs and DDC with V4A and never looked back since :)
[One (M7) Original Android Development] ABQNM:
I thought flar2 confirmed that faux's sound mod was not active in this kernel and hasn't been for some time. The framework for it is still there so you can change the settings, but they don't actually do anything. Maybe I misunderstood though, but that is what I took his statement to mean.

[MENTION=4684315]flar2[/MENTION] can you confirm if faux's sound mod is or is not active? As I understand it, the mod hasn't been active for some time now.

I do like the Dolby effect on the speaker output where the enhancement is noticeable and distortion is not noticeable on the tiny speakers. I believe I would probably get better quality on the line out if I used V4A and IRS. Maybe it will work more reliably on Lollipop now. I think my issues with V4A was that it was getting killed off by the system on Kit Kat (GPE) so I would lose the audio tweaks randomly. With Lollipop GPE, memory management seems much improved and so far I haven't had anything get killed by the system, so it may be more reliable and it may be worth trying again.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] Dissmeister:
Interesting, I'm not sure why, but I'm on the 15.1 GPE on Sinless 4.4.4 and its working fine (after the call/cut thing usually). Sound jumps up to nearly double the loudness after that. I think it was the same deal with Sense, but I wont confirm this because I havent used that in a while. Maybe somebody can try it out.

Not sure why it kills yours. I have used others like Noozxoide and had those issues but V4A for me have always had a deeper integration with the system. Have a look at RAM usage, maybe try forcing on V4A if it closes randomly. Or 3rd party apps could be interfering. I use Clean Master, and have set it on ignore. if you havent tried any of those out.

Flashing lollipop on mine now. Hopefully there will be no issues. Good luck
[One (M7) Original Android Development] rambo69:
Thnx flar2

19.0 works great with 5.0.1
[One (M7) Original Android Development] Thijssie909:
hi flar, noticed a small bug. I use logo2sleep and sometimes when I put it to sleep the screen instantly jumps back on.

Everything else seems to work fine!
[One (M7) Original Android Development] jdgreat4:
Hey. I'm getting a huge battery drain after flashing the kernel even when screen is off. Any way to fix it or any settings to change?
[One (M7) Original Android Development] jdgreat4:
What is over counted?o.O
[One (M7) Original Android Development] maymaymay:
+1
[One (M7) Original Android Development] mitchst2:
This happens if you lift off too quickly. Hold a little longer.

Sent from my HTC One
[One (M7) Original Android Development] odm3xda:
Works like a champ on my m7 GPE lollipop.. Overlooked cpu and gpu under volted and made my m7 feel as fast as a stock m8
[One (M7) Original Android Development] drvalianto:
I only have that one issue: the capative keys lights remain off most the time. but when there's notification, it keeps blinking together with the LED light. after i open the notification, it still keeps blinking, even after the screen is off.

**Never mind. Problem's solved. I turn off the option Backlight Notification in TricksterMod settings, but still keep the option Pulse Notification Light ON in the Settings. Then, when comes the notification, only the LED light blinks, like usual.
[One (M7) Original Android Development] monacoo:
Works great on M7, upgraded to 5.01 using Nand backup from xda. Since Lollipop on M7 has issues with keys backlight, maybe this could be solved with next version of this kernell?

But I have one additional question. Possibility of change settions is only througs fresh flash and Aroma or could be changed some other way? I've read about changing /etc/elementalx.conf but I am not sure if that is it
[One (M7) Original Android Development] dena994:
Is Battery better with elementalx 19 than stock kernel?
[One (M7) Original Android Development] D€INOS:
what overclock and voltage did you choose?
[One (M7) Original Android Development] odm3xda:
I can't remember exact number but cpu is 2.1xxx and gpu 5.xxx voltage did not change kernel default which says undervolted
[One (M7) Original Android Development] monacoo:
Same here, but I do not have any Tricker mod or something. But capacitive keys still blinks (but on the other hand when screen on they do not work - lollipop bug for M7)
[One (M7) Original Android Development] ABQNM:
Disable the button light notification in the aroma installer.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] odm3xda:
This is not kernel related, capacitive buttons light does not light on lollipop, and couldn't find any option to change that in settings
[One (M7) Original Android Development] ABQNM:
They are disabled by HTC, yes, but it seems that if you enable the button light notification option in the aroma installer or using an app like trickster mod or the ElementalX app to enable button light notification, that they will blink with the notification light. I just verified this with the ElementalX app.

So, it is kernel related, but only if you are using the button light notification setting. This doesn't fix the capacitive backlight that HTC broke in the update.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] JeffreyM:
Flashed the kernel but the buttons are always lighting up.

Even with no notification.

Lollipop on GPE 5.0.1
[One (M7) Original Android Development] monacoo:
I actually did that, but now I do not have button light notification anymore. The problem is that light was blinking all the time, even when was no notification...
[One (M7) Original Android Development] flar2:
What's the deal with the lights exactly?

Are they using the onscreen buttons instead (sorry, I have not had a chance to install lollipop and check it out)
[One (M7) Original Android Development] Keasby:
On stock ota gpe edition the lights are disabled by default and there is no option to turn them on at the moment...

The lights are off if the screen is turned on.
[One (M7) Original Android Development] flar2:
I think its a ROM thing then, as the driver is still available in the kernel. HTC is starting to pay less attention to this device, I think. Hopefully the Sense version doesn't have such problems.
[One (M7) Original Android Development] dragonballz2k:
Do I wipe dalvik cache on lollipop still?
[One (M7) Original Android Development] ABQNM:
No, they just forgot to enable them in the build. The capacitive keys still work, and everything is still programmed for the capacitive keys, but HTC didn't enable the capacitive key backlight at all. Usually there was a setting under "display" for the capacitive keys--whether they shut off after a few seconds or were always off. They forgot to build this into the rom entirely, probably because the M8 doesn't use it.

And this seems to be breaking the button light notification for those that try it as well since they aren't programmed to work normally.

Sent from my brain using human to phone transport technology.

---------- Post added at 02:57 PM ---------- Previous post was at 02:54 PM ----------

I don't think the button light notification will work properly until the capacitive keys backlight issue is resolved since they aren't programmed to shut off at a normal rate. So by enabling button light notification, the system doesn't shut it off since the stock timeout doesn't exist since HTC left it out.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] ziaulh.ch:
THE GPE Lollipop kernel is working very good! Thanks a lot [MENTION=4684315]flar2[/MENTION]
[One (M7) Original Android Development] lewonsky:
On 19.0 GPE , last night had a problem with the capacative lights, they kept constantly blinking
[One (M7) Original Android Development] ABQNM:
Did you enable the button light notification feature in the aroma installer or with an app like trickster mod or the ElementalX app? If you did, that is why. You need to disable the button light notification option. It isn't working right due to the fact that HTC left the setting for the capacitive keys out of the rom build.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] VnnAmed:
In comparison to stock kernel this one is fast. It also solves horrible framerate in games. Thing is the most settings from aroma won't sick. Bought an elementalx app and everything sticks except gpu oc. Will reset itself to 400 after a while every time.
[One (M7) Original Android Development] ABQNM:
Make sure you have a current version of busybox installed. I have not had any issue with the gpu sticking. I set it at 450 in aroma and it has stayed at 450 without issue. I don't even have it set at boot in the app as backup.

https://play.google.com/store/apps/details?id=stericson.busybox

Oh and I should probably clarify, what kernel version and rom are you using?

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] lewonsky:
using elemental x kernel , i did not even choose th eoption in aroma . yet is still enabled.

anyway a reboot solved it .
[One (M7) Original Android Development] ABQNM:
I'm glad it went away with a reboot. I haven't noticed the button light notification being enabled for me unless I turn it on. I know there are a few bugs still with some of the settings, so I'm sure they can be worked out in the next release. This was a mostly untested merge since flar2 doesn't have a GPE m7, so as bugs pop up he will work to solve them. The button light issue is just complicated by the fact that HTC left the backlight out of the rom, so it may be causing conflicts with something that would otherwise act normally.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] ace-user:
I am already using 19.0 do i have to reflash it only i can flash ur zip file or i can straight flash the zip file u provided without reflashing the kernel?
[One (M7) Original Android Development] ABQNM:
Just add the line to the build prop and reboot and make sure you get the nav bar first because you don't want to flash the zip and have no way to control the phone. Then reboot to recovery and flash the zip file to remove the capacitive keys. You don't have to reflash the kernel. I just mentioned the kernel because you have to reflash that file every time you flash a kernel update or the capacitive keys will be re-enabled because the kernel includes a key layout file.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] ace-user:
so how do i get back my capacitive keys and remove the nav bar? :confused:
[One (M7) Original Android Development] ABQNM:
The easiest way is to just flash the kernel again and it will restore the capacitive keys. And then just delete the line you added to the build.prop and reboot and the nav bar will be gone. I'll make up a reset zip and add it to the original post in case others want to try it out, but the kernel will reset it too. I never made a reset zip because I made the zip for myself because I hate the capacitive keys.

Edit: I guess I did make a restore zip. I never used it though. https://docs.google.com/file/d/0B90_ZpVR6o9ncGZZdnc3WlRjT0k/edit?usp=docslist_api&authkey=CMbpg54D

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] Rix70:
Flar2... Thank you very mutch for the New version of EX GPE LOLLIPOP. now i can try LOLLIPOP!!
[One (M7) Original Android Development] ace-user:
Wow, thanks so muCn for the help! :o:laugh:
[One (M7) Original Android Development] Guids:
Last call I had made gave a lot of screen on screen off problems. Maybe the light sensor is so sensitive.

Have been running lollipop gpe and 19.0 for a day now
[One (M7) Original Android Development] TheFinderOuter:
after a long time with Viper 7 i decided to get back to stock so i did. did a complete stock with RUU then flashed TWRP to get Root and every thing was working fine so i decided to flash ElementalX to have S2W after flashing every thing is working fine except it unrooted my device any idea how to get rooted again or to avoid this problem?
[One (M7) Original Android Development] khandelwalsiddharth:
I don't know if it is a kernel problem.

From the past 2 days my phone is charging very slow. I plugged in at 15% and after 1hr it was only at 25%. And after a reboot the battery went to 50%. Can someone explain me this abnormality.
[One (M7) Original Android Development] ABQNM:
Were you using the phone at this time? Or was the screen off? What ROM and kernel version? AC charger or USB charger? Have you tried a different cable or charger?

The kernel won't be the problem, that I can assure you. Nothing has changed with the kernel that would cause charging speeds to be reduced. It is almost certainly an issue with your configuration, charging peripherals, or device.

If you are using the phone while it is charging, it will charge significantly slower and if it is excessively warm, HTC has designed the phone to charge at a greatly reduced speed to reduce heat in the metal body. Also, charging from USB will charge slower, unless you have USB fast charge enabled and your USB port and cable are able to support at least 1A of current. it could be your cable is going bad and causing the phone to believe it connected to a USB charger (this can happen if one of the wires is broken in the cable or the connector is not making proper contact with the USB port). Try a different cable and charger. Cheap low quality cables often cannot support charging at full power, sometimes being only able to deliver in the range of 500-800mA when the wall charger and OEM cable will supply 1A (1000mA).

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] khandelwalsiddharth:
This is all started after my GPE conversion. I am using original HTC wall socket and oem USB cable. I wasn't using my phone at the time of charging.

---------- Post added at 11:41 AM ---------- Previous post was at 11:41 AM ----------
[One (M7) Original Android Development] ABQNM:
The jump in battery is unusual. Is this happening every time? When you converted, did you use the full ruu to convert that included the proper firmware and then take the OTA? Or did you take a shortcut and just flash the system partition or restore a TWRP backup? This could be affecting the battery reporting and charging if you didn't flash the proper firmware.

Admittedly, GPE does seem to charge slightly slower than Sense, but not by much. It takes about 2.5 hours for my phone to charge from 0 to 100% on GPE (both Lollipop and Kit Kat seem to charge at identical speeds) if I don't touch it at all. If I use it a little while charging, it jumps to about 3, and heavier usage can make it take even longer. I have never experienced an issue where the battery jumped to a higher level after a reboot though.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] khandelwalsiddharth:
Yes I did a full RUU conversion. This jump i have noticed from the last 3 charges. It charged slow so I rebooted and bang battery lever raised.
[One (M7) Original Android Development] VnnAmed:
I am using latest 19th on lolli 5.0.1 gpe. I also have the right busybox, but it wouldn't stick anyway. MPDecision is changing from aggressive to normal almost instantly
[One (M7) Original Android Development] ABQNM:
I'm sorry but I don't really have any more advice to offer other than trying another charger to at least rule it out. Nobody else has reported this issue and I haven't experienced it either. Maybe someone else has some other possible explanation for why this is happening.

Sent from my brain using human to phone transport technology.

---------- Post added at 12:35 AM ---------- Previous post was at 12:27 AM ----------

It seems there are some bugs still in the sysfs values and them not setting properly (apparently due to permissions). I'm sure [MENTION=4684315]flar2[/MENTION] will get to them when he has some free time from his job. Are you using a gpu frequency other than 450? I may not be seeing the problem because I use 450 and that is the default gpu overclock so it automatically defaults to that any time overclocking of the gpu is enabled. If I were to set it higher it is possible I would experience the same behavior. And this is likely why mpdecision is reverting as well. Once he gets the setting of permissions handled for the sysfs values I'm sure all will be well. As mentioned it puts him at a bit of a disadvantage not having a GPE device to test on. The kernel still runs great at stock settings, but we may have to wait a few days to get all the extras working 100%. New code base makes for a lot of work.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] Lacrein:
Thanks for your amazing works!

I wonder if you will make an option that can disable the 3rd and 4th cpu core, only 2 cores of the cpu can be used at most?

also, can you make an option that can turn off the backlight of the keys(back and home)?

Can you even lower the voltage to 700mV, lower the max gpu freqency to 400MHz?

I think that would extend the battery life. I see those options in lyapota kernel for htc one x, how I miss those and hope that they can come true for my htc one m7.

Thank you!
[One (M7) Original Android Development] ABQNM:
I'm guessing you are using Sense. Because the Lollipop GPE update shipped with the key backlight disabled and the option to control it in the display settings absent. If you are on Sense, I heard this app still works for disabling the button lights. It needs root, obviously. https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness

Edit: I just tested the app on my m7 GPe and it makes the button lights work on Lollipop. It allows for off, dim and bright and a set at boot option. They shut off with the screen. So those of you who want your capacitive keys to light up, you may want to give this app a try. You do need root. https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] hitman1376:
Hi There ...

Hi there ... Dear [MENTION=4684315]flar2[/MENTION] do you have any plan to get this into your amazing kernel ? ... Thanks in Advance

With Best Wishes

Hitman1376​
[One (M7) Original Android Development] flar2:
No
[One (M7) Original Android Development] beletruz:
A nice feature

Please have a look at this ;)

http://xdaforums.com/android/software-hacking/kernel-tap2unlock-tap2wake-feature-t2965344
[One (M7) Original Android Development] flar2:
There is some weird stuff going on with security and permissions on GPE lollipop. This prevents the init.d script from applying your chosen settings, so you end up with defaults for everything. I will try to fix it as soon as I can. Probably something with security contexts, but I don't know yet. If you have the elementalx app, it should be able to change the settings and apply them at boot.
[One (M7) Original Android Development] eagle06:
Guys after bln activates ,it is not stopping blinking evn after I clear notification/read message. I'm on gpe 5.01 with 19 kernel

Edit- got the answer from a few pages back.
[One (M7) Original Android Development] opher50:
Yeh!! we want this :)
[One (M7) Original Android Development] flar2:
Sorry, but no. This is something that should be implemented in an app.
[One (M7) Original Android Development] opher50:
Since I don't have enough knowledge inin this topic, isn't this thing a kernel tweak? I mean an app wouldn't work without kernel tweak?
[One (M7) Original Android Development] flar2:
It needs a kernel change, but the actual functionality should be in an app that reads screen coordinates and securely stores the pattern. There is a kernel on the m8 that has had this for months, and another person developed a "knock code" xposed module. I suggested to the xposed module developer that it could interact with my existing wake gestures, but he did not pursue it.
[One (M7) Original Android Development] ABQNM:
Agreed that there should be userspace management of this. It would be too unwieldy and prone to lockouts to leave at the mercy of sysfs values, especially given the current state of those. An app to control things and the kernel support needed to handle and translate the userspace input would make for a nice solution though.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] Mikanoshi:
ElementalX has it from the very beginning of Wake Gestures support) If you didn't disable that touchscreen data during screen off in later versions ofc.

I first wanted to use raw coordinates data to implement different gestures, but then you added gestures detection in kernel and it was a lot easier to use :)
[One (M7) Original Android Development] yooyo3d:
I made full GPE conversion and flashed this ROM:

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

Then I flashed TWRP and after that I flashed ElementalX 19.0 GPE. Now when I try to build simple app in Eclipse Im getting this error message:

Quick fix is ...

su
chmod 777 /data/local/tmp

.. but I have to do it after each phone reboot.

Any idea whats going on? Is this ROM issue or kernel issue? Im asking this because of:

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/311
[One (M7) Original Android Development] flar2:
Same happens to me. It's because of selinux. HTC tightened it up way too much. My app can't even read the cpu temperature. Most of the settings are not applied by the init.d script for the kernel either.

Setting selinux to permissive would probably stop this from happening, but I don't want to do that by default.
[One (M7) Original Android Development] yooyo3d:
Thanks. You are right After executing /system/bin/setenforce 0 it works.

So... yet another workaround is: https://play.google.com/store/apps/details?id=com.mrbimc.selinux With this, permissive survive reboot.
[One (M7) Original Android Development] Philips9:
Are wake gesture work with stock gpe lollipop???

Thx in advance
[One (M7) Original Android Development] mitchst2:
Yes perfectly.

Sent from my HTC One
[One (M7) Original Android Development] Philips9:
But I need xposed such as for sense ROM(with sense 6 tolboox)??
[One (M7) Original Android Development] yooyo3d:
Xposed does not works on Lollipop. ElementalX have kernel support for such gestures.