yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] andreasy:
I too confirm that turning amplify into system app, makes it work again. That's good workaround until we have a fix
[Xposed Framework Modules] The_Keeper86:
Strange I just double checked and it's a system app. I'm not sure if it's working. Aren't those 0s in my screen shot supposed to not be 0s? Thanks for replying!
[Xposed Framework Modules] cryptyk:
Try to reset stats after you make it a system app.

In any case, I'm working on a legitimate fix.
[Xposed Framework Modules] andreasy:
If it's working you'll see entries in wakelocks, alarms, etc.
[Xposed Framework Modules] The_Keeper86:
Hmm tried that and it doesn't do anything. What are you guys using to convert to a system app? I used Titanium Backup and it hung on converting forever so I force stopped Titanium but it shows it as a system app.

Maybe I should uninstall Amplify and try again this time converting using a different method?
[Xposed Framework Modules] Smultie:
I expected positive results as well, that's why I'm surprised my battery life seems lower. The thing is I do see way less wakelocks, but the steepness of the battery decline shows higher battery consumption while the screen is off.
[Xposed Framework Modules] Pkt_Lnt:
Can you turn it off and get a BetterBatteryStats baseline dump for a few hours, then turn it on and get a second battery dump to compare? Then we can probably help,but from this brief description, I have no one has a clue what could be wrong, sorry.
[Xposed Framework Modules] darkilong:
sorry about that one here is the dump file from BBS
[Xposed Framework Modules] wilkster:
Your battery drain is caused by your phone not sleeping at all. Looking at the BBS file you provided the main issues are below which aren't network location service related:

================

Kernel Wakelocks !!! wakeup_sources !!!

================

GPSD (): 1 h 41 m 16 s (6076 s) Cnt:(c/wc/ec)0/0/0 76.3%

l2_hsic (): 48 m 2 s (2882 s) Cnt:(c/wc/ec)6821/0/6821 36.2%

I am not familiar with the Galaxy S4 but you may be able to find help on some of the S4 or BBS threads on XDA (or google). Others here may have better experience with these wakelocks.
[Xposed Framework Modules] darkilong:
thank you, i wish someone can help me figure out the solution.
[Xposed Framework Modules] spupuz:
I have good battery stats using greenify and this module.

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Xposed Framework Modules] dimm0k:
do you have GPS turned on in your location settings?
[Xposed Framework Modules] Pkt_Lnt:
Have you tried the BBS thread and S4 forums? Post that BBS dump there and you should get assistance.
[Xposed Framework Modules] Mistertac:
Check out this thread

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

Possibly could fix that for you.

- Tapatalked from the G3

---------- Post added at 03:10 PM ---------- Previous post was at 03:08 PM ----------

Also for that other one check this out

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

Seems your problems could be modem related

- Tapatalked from the G3
[Xposed Framework Modules] darkilong:
just followed the steps on the link you posted will check if it will fix the issue

not yet mate i will try the solutions mentioned here and monitor it

yes i have it off and location aswell

thanks guys
[Xposed Framework Modules] Pkt_Lnt:
if you have location and GPS off, this module does nothing for you.
[Xposed Framework Modules] RASTAVIPER:
Is Alarm Manager affected by any way from this module?

In 19 hours of use Wakelock detector shows 14.216 counts for this item.

I guess this is the reason that my Nexus 4 is getting high Android System near at 20% and SOT only around 2.5 hours with use solely of WiFi.

Unleashed from Onda v957m on TDT
[Xposed Framework Modules] trjlive:
Having Android system at 20% is not a problem, and in fact,

the higher the percentage for the Android system, the better

. The Android battery chart is not saying that Android system is using 20% of your battery. The chart is the "Battery Usage" chart, it is showing what is responsible for total usage. It is saying that "of the battery percentage used, Android system used 20% of

that

".

So if your battery is down to 10%, and Android system is showing 20%, then that means that Android System used 20% of the 90% of battery used. This means that Android System used 18% of your battery. The remaining 80% of the 90% of used battery was used by apps and other processes. The used percentages should always add up to about 100%, which is 100% of the battery percentage used. If you've only used up 10% of your total battery, and Android System is showing 20%, then that means that Android system has used up 20% of the 10% of used, or only 2% of your battery.

So with this in mind, you actually WANT android system to be higher than everything else. If you had Facebook using 40% and Android system using 20%, then that means that Facebook is using up twice the battery as your device just idling. When Android system is showing the highest percentage, this means that most of your battery is being used by the system (for keeping your device turned on, connected to the networks etc), and not by runaway processes or apps.

The lower the number for the Android System will mean that other apps and services are using a higher percentage, which is counter-productive. So don't spend so much effort and worry about Android system being high, that is entirely by design and is actually what it's supposed to be. If you want to see the real usage of your device, you need to use an app like BBS or Gsam and actually look at how much of the battery the various services and processes are using.

But worrying because the Android built-in battery monitor is showing high percentage is like worrying because your checking account shows your highest expenditure percentage is your mortgage. The only way to reduce the percentage of your mortgage compared to your entire income (without increasing income) is to increase all your other expenses, like car payment, etc. then instead of your mortgage being 40% of your total expenses, all those other increased expenses will reduce your mortgage percentage to 30% of your total expenses. But in doing so, we haven't gained any additional money, and in fact we've lost more by having to spend more on other things.
[Xposed Framework Modules] cryptyk:
I'm sure folks would rather see a new release than a new video but wanted to share some more progress from the 1.1.6 version. Check the video to see some progress. I'm hoping to release this weekend. Fingers crossed!

[YOUTUBE]V8bRaed7uaA[/YOUTUBE]

Thanks,

Ryan
[Xposed Framework Modules] Mistertac:
Wow man that looks like one very well polished app you've been creating.

I think this is awesome you're incorporating a different UI that has explanations about the WL along with very easy to use On/Off and timers.

Keep up the great work I'll definitely send you a donation within the next couple days.

- Tapatalked from the G3
[Xposed Framework Modules] kmarc33:
Hi Ryan,

2 things:

1) orange screen describing the wakelocks: "information" ;)

2) I think it's been mentioned but an option to reset all counters after fully charging and unplugging.

Thanks
[Xposed Framework Modules] dimm0k:
[MENTION=3306157]cryptk[/MENTION] not sure about everyone else, but I think it would also be nice to have the counters reset upon a device reboot...
[Xposed Framework Modules] Mistertac:
Could also have something like the "Google It" option like in Wakelock Detector...

I think most apps should have that feature built right in! [emoji16]

- Tapatalked from the G3
[Xposed Framework Modules] Bleedos:
Please guys, file your feature requests on bitbucket (link in the op) or vote for an existing one! :sly::D
[Xposed Framework Modules] m0han:
thanks a bunch. great that you're working to give ''power' to the people'! :good:
[Xposed Framework Modules] Portgas D. Ace:
As far as I remember, there is a Magisk module for this (App Systemizer?). If you are running Magisk, give it a try.
[Xposed Framework Modules] Ciamabhishek:
How to set selinux to permissive?Is there any way to flash zip?
[Xposed Framework Modules] dusman13:
Magisk SElinux Permissive Script modul.
[Xposed Framework Modules] Ciamabhishek:
Where can i get it?
[Xposed Framework Modules] dusman13:
Do you have magisk?

https://xdaforums.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
[Xposed Framework Modules] The_Keeper86:
I tried that module after rebooting it hangs in the LG boot screen before Android starts booting. I'm not sure what else to try :/ I might just wait for your update.

Edit. Tried an older version of app Systemizer and didn't freeze in the LG logo this time. I'll report back if amplify works.
[Xposed Framework Modules] andreasy:
TB always freezes at this point but after restart, your app should be system. Anyway, I didn't use TB this time but a Magisk module named AppSystemizer
[Xposed Framework Modules] The_Keeper86:
Yeah, I hate how it freezes. I tried to completely uninstall Amplify so I can reinstall it from scratch but it won't uninstall now that it's a system app. I've even tried deleting com.ryansteckler.nlpunbounce.apk in system/apps and it won't let me. Not even in twrp.

Slightly off topic but is there a way to delete this so I can start from scratch? I'd hate to reinstall my rom. Lol
[Xposed Framework Modules] freeop:
Not for sure if this will work for you, but I installed and uninstalled Amplify as a System app and then uninstalled it after finding out it didn't work. I used Solid Explorer to do this, but I am on a stock rom. It might work. Can't hurt anything to try :)
[Xposed Framework Modules] The_Keeper86:
Gave that a try and it wouldn't delete it either. I'm also in a stock modified rom. Ie generally tried deleting it into wrong and dark gives me an error 1 lol. I've never seen such a persistent file to delete ?

Edit. Silly me forgot to unchecked mount system as read only in twrp . It worked LOL
[Xposed Framework Modules] freeop:
The only way I got Amplify to work at all was to use the SELinux Switch. As soon as I installed it and changed my phone to "permissive", Amplify worked and is working perfectly.

If you haven't tried SELinux Switch yet, you can get it from here: https://xdaforums.com/android/apps-games/app-selinux-switch-t3656502

But Google will complain about this app and you will have to disable the security for it to NOT delete it. It is Approved by XDA so you can be sure it is ok.

Hope this helps.
[Xposed Framework Modules] The_Keeper86:
Thanks after installing that and run in it permissive was greyed out so I assume it's already set? Maybe it just doesn't want to work with Weta rom? I also use Resurrection Remix too but haven't tried it yet. Any other ideas?

I'm sorry for being a pain.

Edit. Each time I convert it to a system app the app disappears lol.
[Xposed Framework Modules] Lgv20user:
The developer is working on an update. Let's be patient.
[Xposed Framework Modules] The_Keeper86:
I know that. I was trying a suggestion he suggested.
[Xposed Framework Modules] Thanostsak:
Converting amplify into a system app seems to be working partially.A device reboot resets all the stats including the configurations.I am really confident cryptyk will figure all this out,I am just pointing this out for those who want to try alternative solutions.

Edit: Disabling and enabling the module in xposed solves the issue so it was most likely my fault
[Xposed Framework Modules] The_Keeper86:
How did you go about converting it to a system app?
[Xposed Framework Modules] Thanostsak:
Any explorer with root access will do.I use root explorer.You just move the amplify folder located in /data/app to /system/priv-app then reboot .Enable amplify module in xposed, reboot and you are good to go
[Xposed Framework Modules] The_Keeper86:
Hmm after moving it to that folder xposed says the module was updated reboot so I do that and amplify disappears as if it was never installed lol. I think I'll just wait for a new update. It's no big deal. Just wanted to get some better battery life. I used to use Amplify on my note 5.
[Xposed Framework Modules] cryptyk:
Hey all,

Just wanted to give you a quick update before I turn in for the night. I have the new communication structure in place and Amplify now records wakelocks, alarms, and services without requiring any special setup (SElinux or System app). There are still a few kinks to work out:

- UI isn't hooked up to the new system yet

- Logging wakelocks, alarms, and services during bootup doesn't work yet

- There's a couple of changes in Nougat that I need to handle: Alarms have a different signature and getting the package of a wakelock is deprecated (bummer).

- I'm using the old file structure. I want to change it to be a database and now seems like a good time to do that. I'll probably do this as a followup release

- I'm also doing some general clean-up of the code as I go. I removed all of the old code for global stats because I took that server down ages ago.

Thanks for your patience. I'll try to get a build out for testing tomorrow night.

Thanks,

Ryan
[Xposed Framework Modules] friscoboi:
Mine Works without converting to system App. Just Had to Set selinux to permissive.
[Xposed Framework Modules] mackalilar:
We are waiting you thanks.
[Xposed Framework Modules] Lgv20user:
I hope everyone who's been bombarding you sends a donation your way for all your time and help. This goes for all developers who do this on their own accord.
[Xposed Framework Modules] ronyscomparim:
I did all the procedures and gave me this message! Help
[Xposed Framework Modules] cryptyk:
Hi folks,

Attached is an alpha version of Amplify that fixes the problems with SELinux. It would be awesome if a few of you could test it to make sure it's working. Before you do, though, here are some things you should know:

1) It's only tracking wakelocks right now. If this method works, I'll go back and fix alarms and services the same way.

2) Performance might not be great. In fact, Amplify might end up using more battery than it saves right now because I haven't optimized the new communication method yet.

3) It's pretty easy to mess something up when you're writing an Xposed module. Amplify runs very early in the boot process and much of the code runs in the system process. If it's critical that your device is stable, don't install this version. It's very unlikely it will do any permanent damage, but you might end up in a soft boot-loop where you need to disable Xposed and uninstall Amplify for get stable again.

Thanks again for your patience. Let me know how the app works and I'll keep moving forward tonight after work!

Ryan
[Xposed Framework Modules] freeop:
Tried a few times to install, and every time said: "Installation Corrupted". Downloaded .apk twice and turned SELinux to "Enforcing". Rebooted a few times also. Got the corrupted message every time.

Sorry couldn't give you better feedback.
[Xposed Framework Modules] ATP4:
I just tested.

Config test:

- Oneplus 3

- Resurrection Remix 7.1

- EX Kernel

- Magisk last stable version

- Xposed 88.1 Arm64 (official branch)

- Setlinux: normal, no "permissive"

Once rebooted, the smartphone runs well for a minute, Amplify looks Ok and counts the wakelocks, but after one to two minutes the smartphone completely freezes and forces to force the smartphone again.

So I uninstalled it. Waiting for a new test version.
[Xposed Framework Modules] cryptyk:
Do you mind grabbing a logcat for me if you get a chance? Ideally during the freeze, but don't worry about posting too much. I can dig through it.

Thanks,

Ryan
[Xposed Framework Modules] ATP4:
Unfortunately, the freeze arrives too fast and completely paralyzes the phone. I have to keep the button on / off a few tens of seconds to restart the smartphone and everything is frozen during that time).
[Xposed Framework Modules] rav101:
Hey buddy,

Using Xposed 88.1 on OP5 with PureFusionOS. I have attached a log. I limited both default NLP wakelocks to 7200.

I had one crash. The second time I watched it and I saw that the counter reset after a minute or two.

Hopefully something in there that helps you

Edit for link as it doesn't want to upload: https://my.pcloud.com/publink/show?code=XZL7jX7ZWYqNWcg7iGmnbJFQFEBt0X5xs7Yk
[Xposed Framework Modules] ATP4:
Apparently something happens after one to two minutes. For you it stops counting the wakelocks, for me it blocks the smartphone. A track to follow?
[Xposed Framework Modules] cryptyk:
That's helpful guys - Thank you!

I see the crash from [MENTION=5582262]rav101[/MENTION] 's post. That one should be pretty easy to track down and fix.

The two minute thing is odd and I don't see anything obvious in the logcat. I'll take a look, though. I'm hoping that some of the instability is just because I haven't optimized the performance yet. Basically, Amplify is doing a lot of work and writing to the file system with every wakelock. I'll knock that back a bit and get a new release out tonight.

I appreciate the testing. If anyone else can take a look and provide feedback+logcat, it will still be helpful. These things are easier to triangulate where there are a couple of different logcats from different devices.

Thanks!

Ryan
[Xposed Framework Modules] mackalilar:
Wow! We are waiting you real king :)
[Xposed Framework Modules] rav101:
No problem buddy,

I've only just installed Xposed (was waiting for Amplify). I'm on 7.1.2. Not sure if that makes a difference to anyone on any older version of Nougat.

I've also noticed that I have to soft reboot after a reboot to get Xposed going so I think I also have issues there.

Lastly, my phone froze after I had put my phone down for a while. Again, nothing to say it was either Amplify or Xposed but just for info.
[Xposed Framework Modules] Muledog17:
Just tried it on my V20, caused my phone to freeze a few seconds after booting. I wasn't able to get a logcat.
[Xposed Framework Modules] Deus.:
Tried to install it but got a previously reported "package error".

I didn't try to run 'adb install <package>' so far.
[Xposed Framework Modules] cryptyk:
Can you post a screenshot of the "corrupted" error or logcat?
[Xposed Framework Modules] freeop:
This is all I get when I try to install...
[Xposed Framework Modules] Prattham:
Download again may be a bad download
[Xposed Framework Modules] freeop:
That's what I thought and have downloaded 3 times now with same results each time. I get the message from the installer that it wants to Update the app, goes through the install progress bar, then the above dialog.

Should I uninstall Amplify first?
[Xposed Framework Modules] cryptyk:
Definitely uninstall first. You can back it up with TiBackup if you want to keep your settings.
[Xposed Framework Modules] freeop:
Yep found that out. That is why it wasn't installing. As soon as I uninstalled then installed the new one, it installed.

Testing now...
[Xposed Framework Modules] freeop:
After amplify ran for about 3 or 4 minutes, I checked the wake locks and was running good. Permissive was off and SELinux was Enforcing.

After about 2 minutes more, the app crashed and I shut it down, via dialog box.

If I knew how to send you the Logcat I would but when I printed it out via adb, the log was over 64mb and I couldn't upload a file that big.
[Xposed Framework Modules] The_Keeper86:
You should be able to copy and paste it into something like pastebin.
[Xposed Framework Modules] ATP4:
Ready to test the new alpha of the module :)
[Xposed Framework Modules] cryptyk:
Not going to happen tonight, ya'll. I just realized that SELinux also breaks the ability to get preferences from the Activity into the system process. The old XSharedPreferences classes don't work anymore. I have a solution (again using ContentProvider), but Android really doesn't like when I call across system processes when it's eager to get a wakelock. I'm working on a caching solution for preferences with a broadcast intent for when preferences change.

Practical upshot of all of that is that:

1) We still have a solution. I'll get it fixed.

2) Probably still a couple of days away.

3) Things won't get blocked or recoreded until after the system has booted.

Thanks and have a good night,

Ryan
[Xposed Framework Modules] gothicVI:
You should contact [MENTION=4419114]rovo89[/MENTION] w.r.t. the no longer working class. Ideally open a github issue.

Eventually that's something he can fix and you wouldn't need to waste time rewriting your functions.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Xposed Framework Modules] nefa91:
Amplify doesnt keep running

Hello, I'm encountering a problem: I recently flashed Xposed (on 7.1.1) and a few modules (greenify adaway and such things), but amplify shuts off on its own, I did find a thread where I read that moving it as a system app would help (earlier it would install it in the sd card drive, thanks to unified storage), which I did, but nothing changed, whenever I open the app, the counter is at 0, refreshing works, but it only keeps track of wakelocks while its open, as soon as I use something else and I go back, everything starts over.

I'm using an Elephone s7, do you have any clues why this is happening?
[Xposed Framework Modules] aeonix_05:
Please read few pages back and you will be enlighten
[Xposed Framework Modules] :
You can try LiveBoot by chainfire. It saves a log during boot. You have to enable this feature in settings.

Unfortunately, i get the "installed but not active" bug in xposed installer. Soft reboot workaround isn't a option for me because my camera stops working after soft reboot.

Maybe i have some time tonight to provide a live log for amplify.
[Xposed Framework Modules] ATP4:
thank you for this information, I will activate it for the next alpha.
[Xposed Framework Modules] nefa91:
I didn't go that back at the time I was writing , sorry for the inconvenience.
[Xposed Framework Modules] cryptyk:
rovo89 is aware of the problem and there are a bunch of github issues on the XposedBridge project. There aren't any perfect solutions yet, but ContentProvider is one way folks are handling it and i think it's the path I want to go down. I suspect that the ContentProvider is also causing the instability in the alpha and I'm working on a caching solution to fix it. Hopefully there will be an Xposed official fix for sharing prefs across processes, but until then we're each solving it individually.

Thanks,

Ryan
[Xposed Framework Modules] Thanostsak:
Do you think that contentprovider would somehow make amplify less effective since it will run after booting up instead of running deep during the boot process?Don't get me wrong i am not trying to undermine your work, I am just curious.
[Xposed Framework Modules] cryptyk:
It's a great question. You're right that it means that preferences, which include which items to block, aren't available until boot. For wakelocks and alarms, it's a very small issue: Amplify won't block anything during bootup, but will start working as soon as the system comes up. That's not ideal, but I don't suspect that wakelocks and alarms acquired during boot, when the system is fully awake anyway, are critical to saving battery life.

The one issue I can think of is service blocking. Some services start early in the boot cycle and Amplify won't be able to block those. They may stay running even if the user would prefer to have it blocked. I'm not worried too much about it: Not many people use service blocking (based on the lack of questions I get), not every service starts at boot, and not all of them stay running. If a service stops itself then tried to re-start after Amplify is booted, we can block it.

So yah - It's not a perfect solution. I prefer it to manually setting file permissions (which I don't think is future proof), or storing it on external storage (which also isn't available immediately in the boot cycle)

Thanks,

Ryan
[Xposed Framework Modules] Thanostsak:
Your response was very enlightening.Personally, it's not a dealbreaker at all.Thanks a lot.