yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Dovidhalevi:
Weird. Maybe try rugby and see if that makes a difference. Maybe croquet :)

I have a few teams active for testing purposes. American football plays once or twice a week, basketball more often. I have not seen any scores for a while. During the summer when baseball, which plays daily is active, did not notice an increase in battery drain. In any event, Google Now is a battery drain is everyone's book. I have tasker toggling location while phone not in use so location reporting (likely not active) or any other tracking is not a factor.
[Xposed Framework Modules] codified:
Do I need to keep this module installed after I have made the changes? Or do the changes persist even after you have uninstalled the module?
[Xposed Framework Modules] Hawaiihemd:
You need to keep it installed.
[Xposed Framework Modules] yanleites:
I red a lot and still didn't understand.

If I use lollipop, I have to install some Linux addon to use the app?
[Xposed Framework Modules] cmstlist:
If you use Lollipop and you are not patient enough to wait for the developer to release a version that solves this issue, then you must do some tinkering to ensure it has the permissions to access the files it needs to. I will just go with the patience route.
[Xposed Framework Modules] yanleites:
Got it, will wait...
[Xposed Framework Modules] aeoveu:
I guess you're right - I removed the cricket scores, and removed Fllickr and Facebook (had refresh and notifications disabled from within the app), and it still seems to drain the battery.

This all began when the new bluetooth low energy scanning began in Google Play Services. I've now disabled Google Now (in addition to Location Reporting) and will see tomorrow how the battery drain goes.

Google Play Services are screwed up!
[Xposed Framework Modules] voland66:
[MENTION=5009022]yanleites[/MENTION]

You do not need a linux addon but you do need to do some tinkering. There are essentially 3 options until Ryan releases an updated version.

1. Run with selinux in a permissive mode. You can do that by by installing SELinux Mode changer ( https://play.google.com/store</url/apps/details?id=com.mrbimc.selinux).

2. Switch to permissive mode only when Amplify UI is in foreground. To do so install tasker (https://play.google.com/store/search?q=tasker&c=apps) or a similar app and have it execute a shell command when Amplify app is running in the foreground. To switch to permissive mode the command has to be "setenforce 0". When the app is not in the foreground tasker (or whatever you use) has to run "setenforce 1" to go back to enforcing selinux mode. Both shell commands must be run in a root mode.

3. Install Terminal Emulator (https://play.google.com/store/apps/details?id=jackpal.androidterm) or a similar app. In the emulator run the command "su", this will make you a root user. Then run the commands in this post:

http://xdaforums.com/showpost.php?p=59025734&postcount=4298

Actually, it may be sufficient to run only the last command in the above post. This keeps enforcing selinux mode but changes the context of the amplify's data file(s) so that system processes can write to them. This only needs to be done once unless you uninstall-reinstall/restore from backup/do phone factory reset.
[Xposed Framework Modules] yanleites:
Again... I will wait...
[Xposed Framework Modules] cryptyk:
Ok. Attempt #2 to fix the SELinux problem. It works not on my HTC M8 with SeLinux enforcing, but that's slightly different than a "pure" selinux device like the Samsungs. Unfortunately, I can't root any of the Samsungs I have access to.

Here's the 3.0.3 that should fix it. It runs the chcon commands after boot is complete, rather than at boot time. This is necessary because SU isn't available until after boot completes.

Give it a try and lets see if we've fixed it!!!

Thanks,

Ryan
[Xposed Framework Modules] bgiesing:
Doesn't show any items in the list and stats reset. I say it didn't work.

EDIT: Works after rebooting a couple times and regranting SuperSU.
[Xposed Framework Modules] voland66:
[MENTION=526666]cryptyk[/MENTION]

Works on stock Nexus 4.

I uninstalled manually fixed version, made sure that I deleted all the remnant folders from earlier installations and intalled 3.0.3.

After the first reboot (through xposed message to activate and reboot) it did not look like the fix was working: the stats were not updated and file contexts were unchanged. Rebooted again. During the reboot process realized that there was no SuperSU access request and that such a request was a necessary condition to successfully run chcon commands. After reboot completed went into the app again and this time got SuperSU prompt (but it was not immediate, I had time to check stats, click refresh button and go into settings). Stats got updated immediately. I am not sure whether I did not wait long enough the first time, whether the fix is only done after the second reboot, or whether being in settings triggers supersu.

Yuri

---------- Post added at 02:55 PM ---------- Previous post was at 02:26 PM ----------

[MENTION=526666]cryptyk[/MENTION]

Ryan,

I noticed that restoring data from the (titanium) backup kills the fix. It looks like after restore one at least needs to reboot and wait until supersu asks for the access permission before stats get updated (I made supersu forget the permission in my test when it did not seem to do anything right away). I might have been too impatient, maybe waiting longer would be sufficient. It would be nice to have a way to force context fix manually from settings (a couple of times I did get supersu request when clicking on the selinux info line in settings but I'm not sure if it was a coincidence).
[Xposed Framework Modules] cryptyk:
Nice! It sounds like it's working. Right now it's setup to only reset the file context after the system is complete booting. That happens roughly 30 seconds after your launcher is up and running.

I'll add some other "fix" points like when Amplify starts. That should fix the other situations you're talking about, like restoring settings, etc. I'm guessing that most people launch Amplify after doing something like that.

Thanks for testing! Can someone on KitKat also verify that 3.0.3 doesn't break anything?

Lastly, a HUGE thanks to [MENTION=4747897]voland66[/MENTION] who came up with the fix. Give that guy some karma! In fact, go to the post above this one and push Thanks! His name is also in the credits on the settings screen in Amplify.

Thanks,

Ryan
[Xposed Framework Modules] Steady Hawkin:
Just started using this today and have a quick question. I installed the app, and have the Xposed module checked. After rebooting, and then opening the app, it goes through the series of checks, and everything is good to go. The counters all seem to be working, and everything else seems to be working as it should. However, the app never asked for or was granted root access (said checking for root when I first opened the app). Is this normal? Thanks!

(Nexus 6, SELinux set to Permissive)
[Xposed Framework Modules] voland66:
If I recall correctly, the only time it explicitly asked me for the root access is when it needed to change the selinux file contexts. If everything else appears to be working, I would guess that app applies file context fix only if selinux is set to enforcing.
[Xposed Framework Modules] sordna:
Nexus 4 4.4.4 here, downloaded 3.0.3 from this thread and seems to work fine. It did not ask for any SuperSU access.
[Xposed Framework Modules] cryptyk:
Beautiful. I'll clean it up a bit, add the context setting to the app launch, then push 3.0.4 to the repo/play store.

Thank ya'll!
[Xposed Framework Modules] Pkt_Lnt:
Confirmed Amplify 3.0.3 fine on Android 4.4.4
[Xposed Framework Modules] sordna:
If you add the context setting does it mean it will start requesting SuperSU access and throw toasts even with KitKat?
[Xposed Framework Modules] cmstlist:
Yup looks like it's fixed on my Nexus 5. Thanks! Also Tasker integration is working now as far as I can tell.
[Xposed Framework Modules] Ninja_Gundam:
As I thought, I get less battery drain if I block play store than the work that amplify do after a week of test. So , until no separate app to check license, or another way to keep play store blocked i have to stop using Amplify. Hope the author will look foward to this for us users who send contributions and others who have problems with activation.

Chooo
[Xposed Framework Modules] aeoveu:
Alright - I've thrown in the towel. Alarm_wakeup_locator just refuses to budge, and this seems to be the root cause of Now draining the battery like hell. Also, I saw that my kernel activity increased as well as the data traffic - which was another cause for the battery drain (because the phone never really sleeps).

I suppose I managed to find a workaround: turn off Google Now from my phone, but leave it enabled in Chrome - that way, I get SOME of the cards (especially the cards that I want) and not have the battery drain. Of course, I can't have those cards readily available, but... it's something.

Has anyone else managed to reduce their GOogle Now Drain on their phone? I'm on Nexus 5, stock Lollipop and kernel, and all that.

Edit: forgot to mention that when I disabled Google Now, the battery drain went down all the way to 0.7% per hour - with Facebook's app installed (disabled refresh and notifications from within the app, and greenified it for added measure). Turning Google Now on began to drain the app.

That's not to say that this app isn't useful anymore - but I wonder how bad the drain must be when this isn't installed! Besides, you can throttle other wakelocks too!
[Xposed Framework Modules] cryptyk:
FWIW, Amplify only needs to check licensing then the UI runs. Once you have things setup the way you like, you can block Play Store Services and Amplify will run correctly in the background.

Thanks,

Ryan
[Xposed Framework Modules] 4r44444:
What things do you guys limmited on KitKat without issues and how much seconds?
[Xposed Framework Modules] jacauc:
Hi there geenyous,

Did you ever find a reliable and robust way of blocking the checkins or reducing battery drain while in China? I'm rooted, so any type of application or service blocker is acceptable.

Thanks!
[Xposed Framework Modules] cryptyk:
Hi all,

I just pushed 3.0.5 to the Play Store, Xposed repo, and OP. If you were having problems getting your wakelocks and alarms under control on SELinux Lollipop, it's probably because of a bug I just fixed. Please give it a try again, and I apologize for the time you may have spent wondering why you couldn't block certain things.

There's still one issue that shouldn't affect most of you: If your system boots in Permissive mode and then you change to Enforcing mode, Amplify will not be able to block your wakelocks or alarms. If your system boots up in Enforcing mode and stays there, you should be ok.

Thanks everyone for the help testing the new versions!

Ryan
[Xposed Framework Modules] yanleites:
So it should work now without any problems?
[Xposed Framework Modules] cryptyk:
Yep. Although I just got a report that it might have broken Amplify for Xposed version 2.4.1. I'll need to look into that.
[Xposed Framework Modules] yanleites:
Well, I don't really care about old version. I use lollipop!

Thanks!
[Xposed Framework Modules] aeoveu:
I'm sure there are others who do care... Not everybody's on lollipop.
[Xposed Framework Modules] Ninja_Gundam:
***delete ***
[Xposed Framework Modules] s2d4:
I am sure people will return the favor when you have issues that they don't have. Lol.
[Xposed Framework Modules] yanleites:
I was waiting for 4 month for Xposed, and few weeks for Amplify... so I think I can enjoy the working version !
[Xposed Framework Modules] cryptyk:
False alarm. Everything is working properly even on older versions :)
[Xposed Framework Modules] SysAdmNj:
How do I allow an app to run in the background without amplify denying it?
[Xposed Framework Modules] mistermojorizin:
I just updated to latest version through the playstore. I was surprised when boot manager told me that I have a new app that wants to load at boot because i don't believe that the previous versions of amplify did. Is it necessary to let it load at startup or would it still work if it's blocked from running (since i don't think previous versions needed to run at startup)?
[Xposed Framework Modules] cryptyk:
Amplify needs to run at boot time if you're using SELinux in Enforcing mode. Otherwise, you can block it.

In any case, it just changes some file permissions and exits. It doesn't stick around long :)
[Xposed Framework Modules] jadejarj:
When I open the services tab the app unexpectedly stops working other things works perfect...
[Xposed Framework Modules] xDark_:
Is there a paid version without IAP? Because it flat out doesn't work on my device. OnePlus One 44S stock rooted if that helps
[Xposed Framework Modules] Cyclu:
I have reported this some time ago never got the response Ryan can you look it please and someone can confirm this behavior?

I have rechecked these wakelocks with Android Tuner and they are also under Play Service.

Even on Kitkat or it's mandatory only on Lollipop?
[Xposed Framework Modules] sjors86:
I recently started to use amplify on my nexus 5 and I notice it it blocks quite some wakelocks and alarms, but still during the 22:30 hour of data collection, it allowed 06:02: hours of wakelock and blocked 0.56 hour. Is 6 hours on 22 hours normal behavior, it sounds abit high, i have been playing some games though?

And another question, what does it means of it says "Wakelock time allowed: 01:01:26" can it keep my device up for that long and can't I lower this to lets say 5 minutes? Or does my phone go to sleep if I use the app actively for more then 5 minutes?
[Xposed Framework Modules] IndianHacker:
I am on Temasek's unofficial CM12 version 8 ROM and flashed the zip he had provided recently.

I have this issue..... Can someone please point me to something that I can try to resolve this?
[Xposed Framework Modules] voland66:
I believe KitKat has selinux in a permissive mode, so no, amplify does not have to run at boot on kitkat. On the other hand, its running at boot has negligible effect on performance since, as Ryan explained, it quickly exits after changing file contexts.
[Xposed Framework Modules] Cyclu:
No it's in enforcing mode it was always like that and I think is obligatory only on Lollipop

because Amplify works perfectly on KitKat in enforcing mode since beginning.
[Xposed Framework Modules] darkeingel:
Hello [MENTION=526666]cryptyk[/MENTION]

I'm glad to see that the app works now correctly on my Nexus 5 running Lollipop with the latest update 3.0.5.

Sadly I see that although I've donated in the past - when the app name was different and it wasn't published on PlayStore - now I cannot use the donate features anymore. Is there any way to make my past donation be recognized by PlayStore or do I need to donate again so that the IAP to be recognized?

Thanks,

Alex.
[Xposed Framework Modules] Andypandiiee:
I seem to be having an issue at the moment. I donated to get the pro version, and then I added another google account. Now when I cannot use the pro package even though I donated as it shows that I havent purchased on that google account, and I got no idea on how to change this. Thank you!
[Xposed Framework Modules] Puzzlegirl:
Did you install via the Play Store or the Xposed installer and have you checked out the OP under FAQ?
[Xposed Framework Modules] plantator:
Mayby thread owner or admin can add this film to first post? https://www.youtube.com/watch?v=h2lds7s_Yjk
[Xposed Framework Modules] darkeingel:
Sadly my corner case it's not covered in FAQ.

Seems like the billing method back when I donated for Unbounced was supported, but the new IAP from Google Play it's not anymore.

What remains to be done in this solution? Well I don't know as it seems like I cannot donate now - the application will crash - and I really don't want to do this two times.
[Xposed Framework Modules] Cyclu:
Ryan should add to FAQ another case: if you use XPrivacy allow your Google account for Amplify. Maybe is your problem;)
[Xposed Framework Modules] darkeingel:
I'm not using XPrivacy.
[Xposed Framework Modules] Wh1t3Rose:
And you don't use Lucky Patcher or any Apps that disables Services? Have you modified Play Services in anyway? Do you use a firewall or a boot manager?
[Xposed Framework Modules] cryptyk:
You can't, really. Google In App Billing leave a lot to be desired.

Send me your order number to gotcode+amplify@gmail.com and I'll refund it. Then you can re-purchase and it should work.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
Done. Thank you!
[Xposed Framework Modules] voland66:
Thanks for clarifying. So it was a change in selinux policy between kitkat and lollipop...
[Xposed Framework Modules] darkeingel:
Nope to all of the above.
[Xposed Framework Modules] Cyclu:
Here is logcat of force close (when pressing donate and even after exiting Amplify) which I posted some time ago and and from what I've read it happens even for those without XPrivacy for me it's obvious because when I allow my Google account for Amplify (It also applies to all applications with InApp Billing) the force close stops.

I'm not expert of logcat but it's clearly appears that Amplify for some don't found Google account why I don't know.

[MENTION=526666]cryptyk[/MENTION] Why do you ignore my question about wrong package name can you respond please because I can't use Amplify for those wakelocks have donated if it matters I just want to use Amplify fully.
[Xposed Framework Modules] siealex:
My phone freezes at boot or immediately after boot with this module. It doesn't respond neither on touchscreen nor on adb. How can I get logs? Galaxy Nexus, PA 4.6 (4.4.4).
[Xposed Framework Modules] MustangLife03:
I started using Amplify maybe 2 weeks ago or so maybe 10 days ago. The standard free version but I haven't really noticed any less of a battery drain in standby. I have the preset alarms and wakelocks enabled. nipwakelock, nipcollectorwakelock,and in alarms wakeup locator and wakeup activity but before this app I was getting basically a 1% drain on standby and still the same 10 days to 2 weeks later about 1% drain and hour. I use 3c toolbox pro for battery specs as it has alot and than some than betterbatterystats and the other battery stat apps. The mA drain in standby is basically the same. With or without the app. Seems a large number of my wake locks is locationmanagerservice and RILJ in red and GCoreFlp. In alarm send_events is is alot. There are a couple services that seem to have a large number of wakelocks but in the app it says there isn't any information yet on it.

In conclusion testing this app in free form doesn't have a benefit to me. Some other devices might still have a benefit. But being in the android world and ios world as a tester and modifier I can't buy an app unless its proven to work in free form. Which this has not. I reset statistics about an hour ago to look at how much has been acquired and blocked and the numbers seem big but those pre set only available through the free version aren't doing much on battery. The presets are set on 240. From looking at the specs this app does work. But like a mentioned above I can't buy an app without proof it does what its supposed to do. And thats keep battery standby down.

With the paid version does being able to set wakelocks and alarms for locationmanagerservice, RILJ, GCoreFlp, AudioMix, Icing and in alarms send_events? Also there are a number of services that have a good amount of wakelocks/alarms does the paid version have more info or pre set setttings for services.

In simplest terms is the paid version gonna help my battery past the regular 1% drain on standby that I'm getting
[Xposed Framework Modules] eemgee:
I have the donate version and to be honest I don't see any improvement, same goes for greenify.

Only Battery saver I use that helps is leandroid, but I lose some functionality. My drain it 0.6% with light use.
[Xposed Framework Modules] MustangLife03:
I saw a difference with Greenify with less used ram on apps that like to open and sit in the background on there own Facebook and Messenger, but that never really helped my battery life but I'm running a performance gov at max and GPU at max frequency. With screen on I'm using 10% an hour and screen off 1% an hour. So basically I can use my phone screen on constant for 9-10 hours non stop and a 100 hour standby if not. Sometimes depending on apps and how we have things set we can't improve on our battery life. Some things just can't be improved some can. I use 2 widgets one is weather and one is 3c toolbox pro that updates like every minute or so maybe that lists my battery temp, cpu frequency, etc. Turning off gps, data, and keeping wifi only and a powersave gov with screen off i still can't improve my 1% an hour battery drain.
[Xposed Framework Modules] siealex:
Try replacing the battery.
[Xposed Framework Modules] II12yanII:
I'm currently running on a 4.4.4 Rom and I'm going to switch to a 5.0 rom. I'm just wondering if my settings in amplify will keep or if I'm going to have to redo all of them even if I use a backup of the app.
[Xposed Framework Modules] Wh1t3Rose:
I smell a troll ;)
[Xposed Framework Modules] fndpena:
I'm new to this app... Would be cool to know what are you guys are limiting/blocking on lollipop.

I did some tests myself, but I would like to hear from experienced users.
[Xposed Framework Modules] cryptyk:
If you block Amplify from using your Google account, it's going to break Amplify. I could fix it to change the force close into an error message, but that's not a high priority. If you want Amplify to work with the Pro features, you need to let Amplify access Google Play Store and your account. In the OP, I put a list of reasons I've seen that stop Amplify from working.

Regarding the wrong package name, can you explain in more detail? Is the problem just that the package name is wrong in the description?

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
Yea - If you're already at a really low idle drain (i.e. 1%/hour or less), Amplify isn't going to help much. It's most useful for those people who have a lot going on in the background and are seeing idle drain of ~5% / hour.

There's a point of diminishing returns. Nothing in the world is going to get you to .01% / hour idle time :)
[Xposed Framework Modules] cryptyk:
Ti Backup works great. If you want to backup manually, just copy the /data/data/com.ryansteckler.nlpunbounce/shared_preferences/* files and restore them.
[Xposed Framework Modules] HIcycles:
Has anyone tried amplifying Tasker anoffcheckorum?
[Xposed Framework Modules] blumenkasten:
I use it with locale and it's working.
[Xposed Framework Modules] haoyangw:
[MENTION=526666]cryptyk[/MENTION]

Somehow in CM11 nightlies and with Google Play Service 6.7.76 Amplify cannot find any NLP wakelocks or services or alarms. Any ideas? Didn't use to be like this.
[Xposed Framework Modules] Cyclu:
Yes I understand that exactly what I said all applications with InApp Billing must have access to our Google account to use the Pro features just I don't understand why for some people's even without blocking Google account with XPrivacy and without the problem from the list of reasons in the OP Amplify still displays InApp Billing error and force close.

Thanks in advance for changing the force close into an error message it will be great for those who want block the account with XPrivacy that I do not advice it's best to donate;)

Yes I don't know if is only cosmetic issue because I don't tried to amplified these wakelocks thinking it will cause problems.

See attached screenshot please.
[Xposed Framework Modules] cryptyk:
I'm still not entirely sure what your concerns are.

For issue #1 that you describe, I want to make sure you realize I can't fix the problem. All I can do is put an error message instead of a force close when people push donate even after the warning says that Pro features won't work.

For issue #2, I don't think there's a problem. The process making the request is the Android System, and that's being reported correctly.