yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Pkt_Lnt:
Install it again, activate, reboot. Save the Xposed installer log.

Start a logcat, make a call. Save the logcat.

Post both logs here for [MENTION=526666]cryptyk[/MENTION]
[Xposed Framework Modules] RoxAbout:
need more info please....

Would you mind giving some hints as to the following information:

1] device

2] software version, rom,kernel,modem

3] installed software, xposed,any modules installed

I'm sorry but our crystal ball's are cloudy with little chance of helping you, short of driving over to your house and taking a look. But since you left out that information also, your secrets are safe.

Alas were not mind readers and are unable to tell you anything at this point.

Please read ALL of the OP [original post = page 1 of this thread] and try again please , filling in the gapping blanks you left for us. Someone will be able to help you much better at that point.

Have a great day!

:highfive::good::highfive:

---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------

I type too slow... :)

your post beat mine :)
[Xposed Framework Modules] jayyo:
Module works great.

So I got a Nexus 5 about 2 weeks ago and have been disappointed with its battery life, especially when compared to my previous phone, Nexus 4. I started tweaking different things, mostly kernel related stuff, to attempt to increase the battery life. Then started disabling location related things. At some point I saw something about an app called unbounced and lion tamer. At the time I didn't try it. Eventually when nothing else was working to my satisfaction, I re-found this app which is now Amplify. Installed it a few days ago. Just using the default settings made a big difference. I don't really like the idea of having to disable all the features and hardware/tools just to have decent battery life. That's just making my smart phone dumber.

Long story short, THANKS for this app and your work. Enjoy the coffee. I limited a couple more things and will let time tell what it does. My only suggestion would be to being able to swipe through the screens, as well as navigating with the hamburger menu. If not, no problem whatsoever. Thanks again. Off to Google Play to review.
[Xposed Framework Modules] cryptyk:
Good to hear! I'm glad it's working for you.

Can you elaborate a little on both of your suggestions? Swipe through which screens, and navigate from where to where via the hamburger?

Also, the play store review makes a big difference to me. So does the coffee. Thank you for that.

Thanks!

Ryan
[Xposed Framework Modules] jayyo:
So, right now you can navigate to whatever screen with the hamburger menu to wherever: wakelocks, alarms, services, settings. What would be nice is if you were in the wakelocks screen, swipe right to go to the home screen, swipe left to go to the alarms screen. Then in alarms, swipe left to go to services or swipe right to go to wakelocks. Now you have to press the hamburger, then press the screen you want to go to. It would be nice to be able to have both navigation options. Thanks again.
[Xposed Framework Modules] cryptyk:
Got it. Thanks.
[Xposed Framework Modules] Celestial Fury:
Any examples of these "very high level security tweaks" or better yet a thread about them?
[Xposed Framework Modules] kingvortex:
He does say he won't disclose them in the section of his post that you quoted. I don't think he will tell you. ;)

If I'm wrong, then I'm interested also. :D

Sent from my C6603
[Xposed Framework Modules] Tinchoska:
I Don t know how to tweak it... Using it default, what will it do?
[Xposed Framework Modules] cornelito:
Hi.

I have been using this module on my N9005 for weeks without any problems.

Since i swtiched my mobile phone to N910F something wierd is happening :

After activating Amplify in Xposed and setting up all wakelocks, alarms and services i'm unable to install any other application, "install" button becomes in-active and cannot be pressed however "Cancel" button works fine. Same happening to SuperSU when it asks for root permission "Grant" button cannot be pressed.

As soon as i clear Amplify Data in Apllication Manager everything works fine.

Any idea?

Thx in advance

Resolved : the problem occuring after unbouncing alarm "com.vito.lux/CompatibilityCheck"

This alarm comes from LuxAutoBrightness.apk
[Xposed Framework Modules] rignfool:
You have a screen overlay on
[Xposed Framework Modules] Al Arsyadi:
[MENTION=526666]cryptyk[/MENTION] May i request new feature? Please add search feature on amplify, It will usefull to search wakelock/service/alarm items.

Thanks in advance.
[Xposed Framework Modules] vitoski:
[MENTION=3095254]Cryp[/MENTION]ryk I would like to thank you for this module. I was trying to lower my battery usage while idle and thx to Amplify I got 0.4% which for me is great!

My I have a feature request for 'Time elapsed' indicator for each alarm/wakelock? It should be in the 'Device Stats' table under or above 'Alarms acquired' and 'Alarm blocked'. RESET button that is there should also reset the 'Time elapsed' stat.

Why I see this useful? Well when you adjust alarms/wakelocks one by one you can rest stats for individual alarm/wakelock. This would give you a better clue how many wakelocks/alarms have been acquired and blocked during given period of time.

I know there is a global stat that provides overall time period, but it cannot be used for granular adjustment.

I hope this makes sense to you.

THX

EDIT:

Also I would like to request adding 'day' indicator to global stats. Currently 'stats collected for' restarts agree 24 hours.

Sent from my XT1052
[Xposed Framework Modules] furboom1240:
Hi there! After reading and catching up on this thread, I am a bit thrown aside by the many suggestions that this app has ads. Well, I also use MinMinGuard. However, unlike some, I take the flags with a grain of salt. Seeing is believing.

Regarding Google Play Services, I nipped this issue in the bud with not only Amplify, but Greenify as well. I will explain how:

Install and activate Amplify from Exposed Repo - I'm sure you've done this

Find Greenify in the Xposed Repo, install it, and to make it more feature rich, you can get the donate version from Google Play. Make sure you have boost mode enabled and grant it Superuser.

Here's the fun part. Greenify Google Play Services. Yup. To do this, add a program by launching it from the app drawer, then tap the notification while that program is still open. You WILL get a warning, since it's a system app. Please insist and do it anyway.

Earlier, when my Relay was on a roll, I posted some stats on an older post. People also asked me what happened as an after effect, and I did answer these questions:

Push notifications still go through

Sync for Google services still happens

And I'm confident enough to say that if you do this, you will see a difference over time.

Good luck. Don't hesitate to ask any further questions.
[Xposed Framework Modules] magnamentis:
naja ?

albeit there is nothing to say against a search function, what comes to my mind reading your request is: why ?

i mean the wakelocks and alarms are from top down longest and/or most frequent and the safe ones are next to limited.

after all if you check the safe ones and go to the unknowns which are the ones amongst which searching would make sense, there are perhaps 5-10 which are frequent enough and long enough to be considered. or in other words, if you don't find it there is nothing to limit :)

in short, the search function would search for those which are not easy to find and since they are then way down in the list they are neither frequent enough nor long enough to be on top and thus irrelevant as far as this app is concerned.

by the way i was thinking to start a totally different request, a bit OT here but still matters for most users. why in hell did google put that hamburger menu to the top-left corner. i mean devices get bigger and bigger and i cannot understand why one of the most important spots in an app must be the farthest distance for my thumb :) ok, the world will not tumble because of that but IMHO it's a really bad decision to put that menu there, considering that it sooner or later affects every user, females with small hands on 5" devices as well as everyone with a larger display. thing is that i can still make it up there but only with balancing the device on the small finger which depending on the current postition, like i.e. laying on a sofa, comes with a certain risk of droping the thing, it slipping from that postition.

yeah i know, no big deal but yet something that crosses my mind each day and each time stumble across the word "hamburger menu"

any thoughts? those who find the topic useless don't have to make their point, i'm trying to find out whether it's only me or perhaps worth to start a topic in various platforms to make google aware of that. top-right would be more convenient if for some reason not bottom right.

---------- Post added at 02:27 PM ---------- Previous post was at 02:24 PM ----------

if you were catching up so why did it go past you that many people, including 2 moderators, desperately tried ( until now successfully after all ) to close that topic (in this thread) ? grrr....... uhhhh.....
[Xposed Framework Modules] marosteeha:
Delete
[Xposed Framework Modules] tboooe:
This is a major alarm for most people. Does Lux still work for you if you Unbounce it? It stopped functioning properly for me and others.
[Xposed Framework Modules] milojoseph:
to the people who maintains the Google doc. Can you add that it's unsafe to unbounce lux. It prevents you to install apps and grant root permission when you unbounce it. Just a heads up
[Xposed Framework Modules] trancinguy:
I'm not sure what you mean here? You used greenify on the Google search and play services?

Sent from my USCC Note 3

I Greenified everything and turned on the experimental futures except Google Play Services and search and messages and let Nlpunbounce deal with them.
[Xposed Framework Modules] xordos:
Thanks for the log.

Yes, now I see. Unfortunately the 4.1.2 build will throw above Exception, because the API change. For above class, it signature is like this in different version:

(I checked from here: http://grepcode.com/project/repository.grepcode.com/java/ext/com.google.android/android/ )

com.android.server.PowerManagerService

4.1.1

4.1.2

com.android.server.power.PowerManagerService

4.2.1

4.2.2

and up include kitkat

i.e., for that hook, actually Kitkat build should work, but Kitkat build will throw error at different places.

So, due the continuously API change in each android release, this will happen. I will try to make a build to handle all these different signature, and catch the Exception if NoSuchMethodError/ClassNotFoundException etc is thrown. But, really, that will be a buggy/massive change, and will add too much noise to this thread. But maybe that's the way xposed module need to do if they want to support different Android version.

Anyone any thought?
[Xposed Framework Modules] pugsang:
My opinion is that you have to make a build also for 4.2.2 since it is the only one unsupported on this thread. Then the build will be available here and the OP will be back this weekend. Lets let him decide what he wants to do with his module. But first of all we have to make sure that this module works across all different API versions without any errors.
[Xposed Framework Modules] xordos:
Agree, I just updated post 281 to OP mentioned the same.
[Xposed Framework Modules] xordos:
UPDATE on 09/01/2014, this unofficial build is retired, please check first post to see latest versions!! :)

Can you (or anyone using pre-Kitkat version) give this build a quick try?

Please verify the log after reboot. It will throw some error with "Please ignore unless your device is version xxx". Those are expected if condition matches. so check if you got any other unexpected errors.

UPDATE: adding diff file here, looks like it is working as expected for at least one 4.2.2 device.

As mentioned in previous build, the JB build is not 100% equivalent to OP kitkat build.
[Xposed Framework Modules] xordos:
Good, that error can be ignore as it is for 4.1 device, so your 4.2 hook registration didn't throw exception.

So, later you should see 3 types of "Allowing...." in the log. (for pre-Kitkat, 2 alarm is integrated into 1)

Following is the log in my 4.1.2 device:

Aug 29, 2014 6:02:42 PM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'cm_p930-userdebug 4.1.2 JZO54K eng.miroslav.20131023.195826 test-keys' with fingerprint 'LGE/i_skt/i_skt:4.1.2/JZO54K/LG-SU640-V30c.1e63311706:user/release-keys'
Loading modules from /data/app/com.ryansteckler.nlpunbounce-1.apk
Loading class com.ryansteckler.nlpunbounce.nlpFix
NlpUnbounce: ignore this error unless your device is 4.2.x/4.3.x: de.robv.android.xposed.XposedHelpers$ClassNotFoundError: java.lang.ClassNotFoundException: com.android.server.power.PowerManagerService
at de.robv.android.xposed.XposedHelpers.findClass(XposedHelpers.java:52)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:136)
at com.ryansteckler.nlpunbounce.nlpFix.handleLoadPackage(nlpFix.java:146)
at de.robv.android.xposed.IXposedHookLoadPackage$Wrapper.handleLoadPackage(IXposedHookLoadPackage.java:20)
at de.robv.android.xposed.callbacks.XC_LoadPackage.call(XC_LoadPackage.java:34)
at de.robv.android.xposed.callbacks.XCallback.callAll(XCallback.java:70)
at de.robv.android.xposed.XposedBridge$2.beforeHookedMethod(XposedBridge.java:228)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:611)
at com.android.server.ServerThread.run(Native Method)
Caused by: java.lang.ClassNotFoundException: com.android.server.power.PowerManagerService
at java.lang.Class.classForName(Native Method)
at java.lang.Class.forName(Class.java:217)
at external.org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:823)
at de.robv.android.xposed.XposedHelpers.findClass(XposedHelpers.java:50)
... 8 more
Caused by: java.lang.NoClassDefFoundError: com/android/server/power/PowerManagerService
... 12 more
Caused by: java.lang.ClassNotFoundException: com.android.server.power.PowerManagerService
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:61)
at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
... 12 more

Aug 29, 2014 1:03:19 PM NlpUnbounce: Allowing NlpWakeLock.240000
Aug 29, 2014 1:03:19 PM NlpUnbounce: Allowing com.google.android.gms.240000
Aug 29, 2014 1:04:19 PM NlpUnbounce: Allowing NlpCollectorWakeLock.240000
Aug 29, 2014 1:11:44 PM NlpUnbounce: Allowing NlpWakeLock.240000
Aug 29, 2014 1:12:44 PM NlpUnbounce: Allowing com.google.android.gms.240000
Aug 29, 2014 1:12:44 PM NlpUnbounce: Allowing NlpCollectorWakeLock.240000
Aug 29, 2014 1:18:33 PM NlpUnbounce: Allowing NlpCollectorWakeLock.240000
Aug 29, 2014 1:20:33 PM NlpUnbounce: Allowing com.google.android.gms.240000
Aug 29, 2014 1:33:00 PM NlpUnbounce: Allowing NlpWakeLock.240000
[Xposed Framework Modules] pugsang:
[MENTION=3266877]xordos[/MENTION]

OK received the allowing logs.So you mean that if you take away the error log the module will work as expected for 4.2.2?

And now the million dollar question. Does it interfere with tasker's autoactivity plugin detection wich triggeres some profiles?
[Xposed Framework Modules] animefans:
Looks like you don't know what grep is...

I can't really provide step by step instructions that you can just follow to the letter

You will have to do some research/education on your end to accomplish some steps below

download windows grep.exe. Try Grep for Windows Gnuwin32, and download binaries zip file

create directory c:\gnuwin32

extract grep-2.5.4-bin.zip downloaded from step 1 to c:\gnuwin32. Now you should have c:\gnuwin32\grep.exe

add c:\gnuwin32\bin to your system PATH environment variable (you will have to look it up how to do it for your windows 7)

rerun the adb command above

You are welcome to use something other than c:\gnuwin32. If you do so, you need to adjust the steps above accordingly

Hope this help
[Xposed Framework Modules] xordos:
Yes, if you got that 3 allowing type, then it is working fully in your 4.2.2. But as I mentioned in post #74, this JB build is different with original kitkat build as I could not figure out 100% equivalent method when check the alarms.

Thanks for the log confirmation. I will add the diff file to this unofficial JB v2 build.
[Xposed Framework Modules] tonyp:
While it does technically work to determine the Android version and correct class to hook with a try&catch block, it is quite ugly.

A cleaner solution would be to check the Android version at runtime with Build.VERSION.SDK_INT.

import android.os.Build;

// 4.2+
if (Build.VERSION.SDK_INT > 16) {
...
}

See here for more information: http://developer.android.com/training/basics/supporting-devices/platforms.html
[Xposed Framework Modules] xordos:
Yes, I will leave that to OP see how he want to resolve these code compatible issues. Maybe there is some simpler common method to hook and works for 4.x all together. Right now I am stick to as close to original code as possible.

Thanks.
[Xposed Framework Modules] nhoc_huhu:
Today dev come back, wait for his update, nice mod
[Xposed Framework Modules] marbulas:
I think this thread is one of the most hot potato in Xposed forum :P
[Xposed Framework Modules] nhoc_huhu:
I try change value to 4200, and no diffent with 420
[Xposed Framework Modules] knojap:
thank you it's working too. Like Putty ADB. :)
[Xposed Framework Modules] asdfasdfvful:
New to this thread. Out of curiosity, could this module potentially decrease battery usage from background apps like dumpster? It has a high wakelock, but I'm not sure if it's necessary or not for the app
[Xposed Framework Modules] aeoveu:
This module only tackles the location wakelocks. If dumpster engages in other wakelocks (not location related), this won't do a thing.

The OP says what this mod is for. Page 1, post 1, just below the ads (on the desktop browser) or the header (on phones).
[Xposed Framework Modules] diggmc:
Love the module, but can a toggle be added to shut it up. It's so log happy, that xposed crashes when I try to look at the logs. I've got every setting set to 300 and the phone had collected a days worth of noise.

Thank God for tasker, a reboot is the only solution right now.
[Xposed Framework Modules] trancinguy:
N5444elementalx

N5444elementalx;

NLPunbounce stock values, Greenify and Experimental futures turned on root mode, not beta and Inteli3g.

I have 8 accounts tied to my phone, I Greenified everything except 5 messaging applications that I allowed to push but turned off pulse notification, and for the Google stuff, sync turned off and location on battery saving mode. Wake Gestures on all the time.
[Xposed Framework Modules] cornelito:
Lux worked ok for me. The only side effect was that I could not install any app.
[Xposed Framework Modules] 1ceb0x:
i don't see why you will want to unbounce it in the first place.
[Xposed Framework Modules] Pkt_Lnt:
It is not Lux, lux triggers the tapjacking protection in SuperSU. You can whitelist SuperSU in lux and will have no more trouble.
[Xposed Framework Modules] xxlakis:
Last night I left the phone open and this happened. Wtf????
[Xposed Framework Modules] magnamentis:
http://xdaforums.com/showpost.php?p=56603833&postcount=3380
[Xposed Framework Modules] schlager P.:
I would like to find out why it works with other things but not with lightflow

Sent from the den of inequity
[Xposed Framework Modules] Osama Zabin:
Are you using HTC One M7?

Many users have reported silent calls recently after Google Play Services update and was fixed by clearing cache/data for both:

1. Google Play Services

2. Google Services Framework.

You can try it anyways.
[Xposed Framework Modules] magnamentis:
to limit an app like lightflow, tasker or similar makes absolutely no sense for several reasons like for example:

a) you can manage the apps from within the app settings, like in lightflow you can setup almost everything to your liking in app.

b) lightflow has is probably set to have special permissions in ( settings > security and settings accessibility ) again it does not make sense to remove these, better freeze the app haha...

what i'm trying to say is that if you set up an app to check certain things for you an to perform a taks according to it's findings you cannot cripple that app at random, better setup the app from within to perform less tasks, less frequent, shorter or whatever it is that you want to achieve with the limitation.

BTW i'm using lightflow myself and it's on of the apps i would never limit with amplifier, i want that lights to perform reliably and immediately so that when threre is no blue blinking i wanna be sure that there is indeed no email etc. etc....
[Xposed Framework Modules] aeonix_05:
Been craving to buy you a coffee and unlock the pro features. Thanks for a good app! No regrets buying you a coffee. Hope it helps! I'm so overwhelmed with the pro features and tried to limit all goolge play services. And I think this is not a good idea because when I left my phone all night for almost 5 hours and the google play services hold the wakelock and my phone stayed awake all the time.
[Xposed Framework Modules] milojoseph:
it is lux because lux updated their app to automatically fix the tapjacking. Plus my tapjacking is off at all time because another app has problem when its enable... But try unbouncing lux and install an app and let me know how it went..............................
[Xposed Framework Modules] CHEF-KOCH:
It's also not god to greenify or unbounce google play store/services or the framework, I don't know why people always come with that myth. Almost the same myth that a registry cleaner under windows can speed the computer or the registry itself, it's loaded into the ram, so same here it's needed for other apps because it provides some api's like background updates and such. If you cut this off the app which try to use this services from google wakes this up or can't wake it up so that the result is that the app use more cpu cycles (more battery drain). So it's not always good to kill or cut all things off. There are rare situations that makes sense to kill it, but mostly that means the app you use needs a lot of external services or is buggy coded. And of course not all wakelocks or services are bad, if it was good coded without much external libs or tracking it can show 1000 wackelocks but without much battery, since it may not consumes much cpu cycles. A video player is an good example, it only needs 'much' cycles if you use or watch something but should not produce much background cycles.

So if you kill or unbounce for example an app that controls your display brightness you properly should not wondering why it not works or gets ignored, it's the nature bow Android and these kind of controlling apps are working. If you regular use or need the apps, just leave them if you don't know and ask the dev why it may produce much wackelocks or cycles even if it's not used. This will also helps to improve the product instead of killing the services.

I guess it's not for beginners at all because if one user says it works does not generally means it works for you.
[Xposed Framework Modules] Pkt_Lnt:
I stopped using Lux over a year ago and switched to an app that works better with less overhead and no problems like Lux has.
[Xposed Framework Modules] milojoseph:
care to share?
[Xposed Framework Modules] eongab:
what app is that?
[Xposed Framework Modules] Mike B.:
If you're unhappy with the default auto brightness of your devices and don't need anything as overwhelming and aggressive as Lux, try YAAB (open source available). I've been using that for a long time on a variety of devices and ROMS without any problems at all and no significant hit on performance or battery life.
[Xposed Framework Modules] Pkt_Lnt:
Velis Auto Bright

Very configurable, tasker integration, good support from the dev.
[Xposed Framework Modules] eongab:
tried that before but didn't like it. thanks anyway.