yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Osama Zabin:
I was having similar behaviour with Extreme Power Saving Mode, haven't tested this with the regular Power Saving Mode.

I'm using sense ROM not GPE, this was fixed with one of the sense toolbox versions.

It could be similar despite of the difference between sense and GPE.

Maybe [MENTION=5386198]Mikanoshi[/MENTION] can explain what the problem was and how he fixed it.
[One (M7) Original Android Development] flar2:
No slimbus tweaks in 18. I noticed poondog went a different way with the sound tweaks, and changed the sound stuff a lot, and didn't want to make that many changes, so I left it alone.

Oh yes, on HTC the vib can only be reduced, not disabled. Thanks for the feedback, I never tested this on HTC because I use Sense and powersave mode is disabled in the app on Sense.

So tell me if I have this right: you have vibration set to something (say 75%) and set to apply on boot, when you enable powersave, it changes to 39% (the lowest setting), then when you disable powersave mode, the vibration remains at 39% and the set on boot flag is cleared. It should be restored to 75% with set on boot.

Powersave mode in the app is disabled in Sense, since it is essentially the same as the built in powersave feature. You may be thinking of vibration for the wake gestures.
[One (M7) Original Android Development] ABQNM:
Yes, that is pretty much it, except I was mistaken in that set on boot was being cleared, when it is actually staying set.

So, my exact scenario is, I have vibration set to 100% at boot. Power save comes on and drops vibration to 39%, and when power save is disabled, the vibration remains at 39% with set at boot flag remaining enabled. This is actually worse than if it returned to default since it now sets the vibration to 39% at boot.

Thanks for your help!

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] Mikanoshi:
Good. That tweak was against any logic, it should even increase power consumption.
[One (M7) Original Android Development] warriormuzu:
I didnt a see in option for double tap 2 wake when I flashed it I only saw the sweep one
[One (M7) Original Android Development] shiningarmor:
any idea whats this?

insertcoin 4.4.3
[One (M7) Original Android Development] ABQNM:
What in particular concerns you? Try changing your frame of reference to "since unplugged," rather than "since boot." The pm8921_eoc wakelock should only appear when the phone is charging. Trickle charging or running off AC/USB power when the phone is fully charged, to be exact. That is the wakelock that the phone holds while the charge cycle is complete but is still being powered by the charger. It isn't draining your battery, but because you are looking at "since boot" instead of "since unplugged" you are seeing this wakelock.

The others just look like normal data and app usage wakelocks, but again, with an inaccurate frame of reference, they really don't mean anything.

Remember not all wakelocks are bad.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] shiningarmor:
im terrible in putting my thoughts into words haha. i didnt realize that wakelock is there and i wonder what is draining my battery so quick. called someone in the past hour and after that , i simply put it to sleep and left it in my pocket. the next thing after unlocking my battery dropped a whopping 2x% in just 3 hours sitting in my pocket doing nothing. checked the power usage history, phone was awake all that time and the battery graph was going down steep.

i was outside working and didnt know what actually happened.. sorry if i cant provide much insight about this haha
[One (M7) Original Android Development] ABQNM:
When trying to figure out random battery drain, usually kernel wakelocks are not the issue. We need partial wakelocks since unplugged, and the actual Android battery stats screen and the full graph. It sounds like an app kept your phone awake, but there isn't enough information here to really track anything down.

Also, do you have any sort of tap to wake enabled? It may be possible that the phone was waking up in your pocket. I have had that happen when I am working and my phone is in the pocket of a real loose pair of pants or shorts, causing the pocket protection not to be triggered and the phone wakes up from hitting my leg. Just a thought.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] jabdulk:
Sprint User Flashed 18.0 Boot Loop

Sprint user, flashed 18.0, any idea how to fix....

Tried wiping and flashing new rom and kernel, no luck.
[One (M7) Original Android Development] ABQNM:
What exactly are you experiencing?

What ROM and kernel did you try to flash? Have you tried flashing the ElementalX kernel for Sprint linked at the beginning of the OP? I don't have the Sprint version, so I am not really familiar with it, so I can try and help as best I can. You may also have more luck with help in the Sprint HTC One forum as I'm sure someone has made this mistake before.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] flar2:
Yes, go to the Sprint forum. This is the GSM version.
[One (M7) Original Android Development] emmanueldmc:
I have exactly the same problem, the ambient light sensor is always active, it consumes more battery the whole system, I tried three different roms and all have the same result ... By the way, I have the automatic brightness off without pocket detection enabled :(
[One (M7) Original Android Development] shezaad879:
Light sensor

I am not sure if this will help but did you use your phone (as in to make calls) at all? I think the light sensor is used to turn the screen off when you are on a call. I am pretty sure the light sensor is also used for other things than just adaptive brightness.

Also, you have got 1 day 5 hours with 3+ hours of SOT. That's pretty much the average for most people. Doesn't look like there is anything wrong here. Maybe try searching what else use the ambient light sensor apart from adaptive brightness?
[One (M7) Original Android Development] emmanueldmc:
I think for the least use my cell phone is to make and receive calls, I just use it as an entertainment center ... The automatic brightness have always manually so do not think that's it, no longer likely to cause the problem ... I've come to think that might be a bug in the oficial firmware from HTC, but I don't see someone else with the same problem with the light sensor.
[One (M7) Original Android Development] shiningarmor:
for some reason im getting really fast battery drains while the screen is online. from 100 it drained to 88 in about 20minutes on web browsing only.

and if i left it sleeping overnight, tahts about 8 hours, it drained about 9% cant seem to find the reason why..

checked my syncs, rogue apps and stuff and i still cant find any. even on a clean rom
[One (M7) Original Android Development] aftab565:
Excellent battery life with ARHD.

No experimental setting applied.

18.0 [emoji2]
[One (M7) Original Android Development] ABQNM:
[MENTION=4684315]flar2[/MENTION] I had another minor suggestion for the app, if you can do it. I like the widgets for powersave and performance modes, but would it be possible to create shortcuts (or expose a toggle activity) for them? I would like to integrate then into my quick settings with Gravity Box, but I can't since they don't have a shortcut and the only exposed activity for the ElementalX app is the main app activity.

It isn't a huge issue, but it would make for some tighter integration with the ROM, rather than having to keep the widgets on the screen. No worries if you can't or don't want to do it, but I figured it couldn't hurt to ask.

Also, what is the low battery level that is used to enable power save automatically? I haven't gotten low enough for it to come on automatically yet. Is there any way to set a manual value for this?

I really love how seamlessly this app integrates with all functions of the kernel and the fact that it doesn't continue running all the time after it sets the custom values at boot. Well worth the money. I also just sent over an extra $5 donation too, as your work on the app and kernel are very much appreciated. Thanks again.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] flar2:
First, thanks for you support and for helping out in the thread here.

To answer your questions, can you use intents? The powersave and performance modes are enabled/disabled by intents. I'm actually not sure if these intents can be called by other apps, but I'm sure I could make them publicly accessible if they aren't currently.

flar2.elementalxkernel.powersaver.DISABLE_POWERSAVE

flar2.elementalxkernel.powersaver.ENABLE_POWERSAVE

flar2.elementalxkernel.performance.DISABLE_PERFORMANCE

flar2.elementalxkernel.performance.ENABLE_PERFORMANCE﻿

The auto powersave comes on at 15% (could be different on some ROMs if someone messes with android defaults). This is when the system broadcasts ACTION_BATTERY_LOW. The reason I use this is because the app doesn't have to monitor the battery level at all (ie: no service or background stuff running). Powersave mode is called by the android system itself when the time comes.
[One (M7) Original Android Development] ABQNM:
Thanks. That tells me what I need to know. As for the intents, they don't appear to be working from other apps, as I just tried to call the powersave intent from Tasker and I couldn't get it to enable. If you could make them public, that would be great. I will try them another way later in case it was just Tasker, but I don't think they are available to other apps.

And good choice on how you implemented the low battery method. As I said, having the app not running all the time is nice, so that is a great way to do it. Now, I just hope the vibration issue can be resolved with the powersave mode and then everything will be perfect!

Thanks again.
[One (M7) Original Android Development] flar2:
The vibration thing should be an easy fix. I'll also find out how to make the intents public. The update will probably come in the next few days.
[One (M7) Original Android Development] ABQNM:
Awesome, thank you sir.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] themachinist:
[MENTION=4684315]flar2[/MENTION] MPdecision selected as performance when flashing kernel, however shows as default in your app. Not sure if the app is not showing it correctly or it's something else.
[One (M7) Original Android Development] ABQNM:
Can't you just change it to performance (and set at boot) in the app?

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

can you add support for drivedroid? kernel patch is available in the main thread at the bottom:: http://xdaforums.com/showthread.php?t=2196707
[One (M7) Original Android Development] ABQNM:
While I am not the developer, I vote strongly no. Simply because it requires USB mass storage mode, which isn't used by this phone at all, and will likely break more things than it will benefit users trying to use their phone to host a Linux iso. That is what they make USB thumb drives for.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] flar2:
It already has drive droid support.
[One (M7) Original Android Development] PocehNeheb:
i'm having issues with it though. with the stock kernel, I got a CD-ROM drive using the app. With this kernel, I get a USB drive only. Can't seem to get a CD-ROM even though the app shows the option.

That's fine and dandy. No big deal. But the mounted ISO or IMG file seems to disconnect shortly after being mounted. This was a problem with the stock kernel as well. In the case of this kernel, it disconnects during writing whereas the stock disconnects during reading. Well, maybe during reading as well. Have not tested yet.
[One (M7) Original Android Development] shiningarmor:
lol guys. 14% drain overnight. im seriously at a loss of ideas now.

anyone?
[One (M7) Original Android Development] khandelwalsiddharth:
You still on a good side. I lost 40%. But I think its due to the third party app and not the kernel.
[One (M7) Original Android Development] shiningarmor:
im pretty sure my drain isnt caused by an app. this is a clean install of insertcoin rom
[One (M7) Original Android Development] flar2:
I'm absolutely sure your drain is not caused by the kernel.

You need to investigate with an app such as better battery stats. Your phone is obviously being kept awake by something.
[One (M7) Original Android Development] themachinist:
I can. But it'll change back to default after awhile when I check the app again
[One (M7) Original Android Development] shiningarmor:
Yes im using bbs. The highest drain is on powermanagerservice , which according to google is a collection of multiple wakelock sources. I cant find anything peculiar though..

The other wakelocks look very normal except ab unusually high active time of browser sync. Is it caused by chrome?
[One (M7) Original Android Development] shezaad879:
I'm not sure that 14% is out of the ordinary here. 11:37 at an average of 1% per hour, that's just under 12%. The other 2% can be attributed to your 17min screen on time. You do have an awake time of 58m and that's not too bad either if you consider 1hr per 12hr of awake time. However, if this is unusual according to you, I suggest try full clean install, then add apps and sync etc one at a time until you find the culprit if you have the time.

Otherwise though, the battery seems very good to me. Also try setting it on airplane mode overnight to test. Could be your network signal that also drains battery if it's weak.
[One (M7) Original Android Development] ABQNM:
[MENTION=4684315]flar2[/MENTION] I just installed the updated app and the vibration feature being restored when disabling power save works perfectly now on GPe. Thanks!

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] shiningarmor:
Found out whats causing the sync loop. Now theres this msm hsic wakelock problem.

Been up for 40 minutes with only 5mins screen time..
[One (M7) Original Android Development] firstcolle:
Hi,

i'm trying to update the kernel witn the 18.8 (previus i had 17.2). but at the installation is bloked o 0.00% and still in "please Wait"... what i have to do now??? o can't reboot the phone....

thanks
[One (M7) Original Android Development] Reiki13:
Hello,

small return on this kernel that I like ^ ^

time to time back home and buttons do not respond ...

we must wait and press and hold it for it to return

(identical to the bulletproof problem)

Thanks for work :)
[One (M7) Original Android Development] flar2:
I don't think so

To be honest, I haven't tried other ROMs, I used stock for a few weeks then installed Renovate and it had everything I needed so I just kept it. There are a bunch of great ROMs for this phone. ARHD and TrickDroid seem to be most popular, but I've heard good things about Insertcoin as well.

Is it working again? I can't help you out because I'm at work with limited access.

The buttons are a problem on custom kernels. Let's hope we don't have to wait too long for 4.2.2, and a button fix, and updated camera driver, etc.
[One (M7) Original Android Development] casperr:
Any chance this can be updated to be compatible with ARHD 10.0 with 4.2.2? Thanks
[One (M7) Original Android Development] LiquidSolstice:
He literally just responded to this a page back...
[One (M7) Original Android Development] h0l:
Yep. Working again by the miracle of waiting and F5.
[One (M7) Original Android Development] MasterThiefGarrett:
So far pretty happy with the kernel, good standby also thanks to undervolting and stuff :)

keep up the good work :)
[One (M7) Original Android Development] barondebxl:
I select "no" in aroma for removing the 3dots but they aren't here anymore....
[One (M7) Original Android Development] spbhutia:
Must be th rom... Check under settings-> display gestures n buttons.....
[One (M7) Original Android Development] barondebxl:
Thanks for the reply. Still not working, I'm on trickdroid 5.6.1 (no android 4.2.2)
[One (M7) Original Android Development] flar2:
Go into /system/build.prop and delete any instances of qemu.hw.mainkeys=1
[One (M7) Original Android Development] barondebxl:
Thanks man, I just reflashed the rom without wiping anything. Will flash the kernel now and if I run into the issue again ill dot it. Cheers!
[One (M7) Original Android Development] gatoradeboy:
If I install elementalx and something goes wrong like camera not working, can I restore my nandroid backup to get rid of elementalx and get my phone working like before the elementalx install?
[One (M7) Original Android Development] flar2:
No, you'll be stuck with it for life.

I'm joking of course. Restoring your nandroid backup of /system and /boot, or dirty flashing your ROM, will get you back where you were.

But you should be able to get the camera working. Custom ROMs with .16 base need the camera fix. If you're on stock then don't select the camera fix. If you're on the latest stock AT&T I'm not sure what you need. I do know that there is a way to get the camera working no matter what ROM you have.

If you're not sure, try without the camera fix, see if it works. If it doesn't, reflash with the camera fix.
[One (M7) Original Android Development] hasan_abeer:
Hi sir please I hope to hear good news about call recorder feature progress in your amazing kernel. ...
[One (M7) Original Android Development] asciicode:
Nooo. I tried but it didnt work and its not easy booting in fastboot after i flashed
[One (M7) Original Android Development] spbhutia:
What dint work?? this kernel is not yet compatible wid 4.2.2.. if that's what u ment.. else th kernel is FLAWLESS..
[One (M7) Original Android Development] asciicode:
sorry i was about the quote one of the questions.
[One (M7) Original Android Development] chaostan:
Im in stock rom with root access. My camera doesn't work after installed although I don't select the camera fix. Please help!
[One (M7) Original Android Development] spbhutia:
Flash th kernel again only this time select camera fix..
[One (M7) Original Android Development] chaostan:
I tried to flash again and select camera fix. But it still doesn't work. Please advise
[One (M7) Original Android Development] asgardr:
Carefuly read OP again,

there, such event (and way ou)t is described?
[One (M7) Original Android Development] ABQNM:
[MENTION=4684315]flar2[/MENTION] sorry to keep bothering you about the app, but I have a new concern.

Previously I have kept my phone at 1890MHz all the time. Recently, I have found that it is really unnecessary so I want to keep it at 1728, but I want to keep those higher frequencies unlocked so I can use them with performance mode in the app. So, I set the frequency in the app to 1728 and set at boot. It doesn't stick though. It keeps resetting to 1890 max within a few seconds. I even tried changing the ElementalX.config and that made no difference. Is this an issue with the app? I know I can set it in the aroma installer to a max of 1728, but then I will be limited to a max of 1728 period, and I can't go higher for performance mode. Do I have to disable the pnpmanager to set a lower frequency than the max, but still keep the higher frequencies unlocked for use with performance mode? Or is this a bug in the app causing it to be overridden?

If I need to disable pnpmanager, are there any downsides to doing so? Is the stock implementation more effective? I would rather leave it as it is if it would be more stable or battery friendly if I leave it enabled. If it is an app bug, let me know what information you need and I can provide it for you.

To summarize:

In aroma, I have set the following:

1890 max, all 4 cores the same

pnpmanager enabled

mpdecision default

Gpu 450 (sets properly)

In the app, I have attempted to set the following:

1728 max, set at boot

this resets to 1890 set at boot after a few seconds, regardless of how many times I change it

ElementalX.config has been set to a value of 4 (1728) for all 4 cores, but this seems to have no effect at all.

Performance mode is set to 1890/477 in the app and works properly.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] flar2:
I need to patch the kernel for that to work. I was initially not going to do any GPE updates until lollipop, which seemed imminent, but now who knows.
[One (M7) Original Android Development] ABQNM:
Don't worry about it then. Lollipop is going to be here soon enough. I will stick with my current setup for now. It has been running fine for months. I was just hoping to try to take advantage of the performance mode and reduce my normal running frequency, but if it requires a kernel patch, just roll it into the Lollipop kernel. I'm not in any rush. I was just exploring the app to see how I could better utilize the features it offered and wasn't sure if that was how it was supposed to work. Performance mode still kicks it up a notch by keeping all 4 cores online all the time anyway, so that is enough of a boost as it is. I'll just reinstall in aroma back to 1728 and leave it there for now. Heck, I have been finding that even at 1300 max that powersave gives me I haven't even had any performance issues, so I'm not really sure I ever even needed to overclock to begin with.

Thanks for the quick reply and I'll be looking forward to the Lollipop kernel when the GPe update drops (hopefully very soon).

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] belek1979:
There was no hide_nav_bar in my settings.db so I added it with value "1".

After reboot 3 dot bar is still visible.

What is android.provider.Settings.System.putInt(context.getContentResolver() ?

Any idea to get rid of that 3dot bar when HTC logo for menu is enabled?

Of course qemu.hw.mainkeys=1 in system/build.prop works, but recent apps disappear, too :(
[One (M7) Original Android Development] Mikanoshi:
It's a Java method to manipulate system settings, you can do the same from adb:

adb shell settings get system HIDE_NAV_BAR
adb shell settings put system HIDE_NAV_BAR 1
[One (M7) Original Android Development] Potapson:
I do this with Trickster Mod.
[One (M7) Original Android Development] Mikanoshi:
"Disable 3Dot Menu" in Screen Wake Control? It's the same build.prop tweak, has a problem with recents I guess.
[One (M7) Original Android Development] flar2:
That trickster setting will break other things, don't use it.

You shouldn't see that 3-dot menu. I haven't seen it in months.

Make sure you have busybox installed properly and that the 99elementalx script in init.d is running. If you ever see the 3-dot menu, try rebooting. There is a possible race during startup where the tweak I do to get rid of the 3-dots doesn't work. If the tweak in my init.d script doesn't get rid of it, then either the user or the ROM has changed something they probably shouldn't have.
[One (M7) Original Android Development] Mikanoshi:
Is it "setprop persist.sys.navbar.hide true"?

root@m7:/ # ls -al `which setprop`
lrwxrwxrwx root root 2014-11-11 02:55 setprop -> toolbox

Doesn't look like busybox, it's stock toolbox.
[One (M7) Original Android Development] flar2:
I can't remember exactly at the moment, but that's probably it. IIRC, the timing was the key, so there is something in the script that makes it wait. The reason we need busybox is for the init.d script (does not execute without busybox)
[One (M7) Original Android Development] ABQNM:
[MENTION=4684315]flar2[/MENTION] thanks for updating the app again and exposing the powersave and performance mode intents. I was able to make a toggle task in about 2 minutes in Tasker that I was able to assign to a custom tile in the Quick Settings with Gravity Box, so now I can toggle powersave on and off any time I want from quick settings on GPE without having to rely on a homescreen widget. You rock!

Sent from my brain using human to phone transport technology.