yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] shockwaverider:
Hi cryptyk, a couple things... On all versions I've used (and I think I've used every update) starting from 1.1.5, I didn't get notifications about my Google automatic photo backup. They were backing up just fine, but no notification. Reverted to 1.1.4 and it works as it should. Also, and I don't know why this would be and I really don't have any objective proof of it, but it really seemed to me like my battery life took a hit on the 1.1.5 and higher versions. Nothing in BBS to indicate this, that or the other, but I definitely noticed faster drain the past few days, with Unbounce being the only thing that had changed. I've always used default settings, whichever version I've been running. Could it be because of my somewhat antiquated 4.3.1 rom?
[Xposed Framework Modules] Mistertac:
Could be the recent update to Google Play Services as well. Could be your ROM setup.

Simply running this module shouldn't negatively effect your Battery life, course anything you run will require resources but I doubt this module alone is responsible for Battery loss. It should help your Battery.

- Tapatalked From The G3 -
[Xposed Framework Modules] Mistertac:
I have mine now set to 240. I've changed the Spread Sheet to 240 instead of 420 and I've included your issue as a possible side effect.

This WakeLock was one of those that didn't really effect my phone but through research I found that it did effect others so I included it.

Being that it's a System WakeLock used by many things it's hard to guess what all the possible side effects could be so thanks for sharing. Set at 240 on my G3 everything still works including playing music even when the Screen is off.

Im currently looking through what I've already added to the spread sheet to see if I can add more info like this and just fine tune things.

- Tapatalked From The G3 -
[Xposed Framework Modules] cAase:
Unbouncing Audiomix seem to cause problems with music listening. When screen turns off the music stops. I unbounced it and it stopped.
[Xposed Framework Modules] Mistertac:
Yea I've updated that one to say

- Tapatalked From The G3 -
[Xposed Framework Modules] Kocane:
The latest version doesnt start for me. FC immediately. Clearing data didnt help.

---------- Post added at 02:56 PM ---------- Previous post was at 02:52 PM ----------

@cAase when listening music, doesn't your player hold a wakelock? Mine does, which must be why unbouncing AudioMix doesnt create any issues
[Xposed Framework Modules] tboooe:
Absolutely! Remember just because a wakelock or alarm number is high it does not mean you have a lot of battery drain. So if your battery life is where you want it, I wouldnt worry too much about wakelocks and alarms. FYI, at idle I get about 0.2% battery drain per hour. This is even with my device being held awake 10% of the time due to a combination of Kernel, Android System, Google Services, and apps like Gmail. So for me, I have left the unbounce stock settings as is and am just playing around now with settings out of curiosity.

---------- Post added at 06:22 AM ---------- Previous post was at 06:20 AM ----------

Thank you sir! I will try the 240 setting and report back.
[Xposed Framework Modules] cAase:
I don't know, its poweramp. It's always running when looking in greenify of "running processes", regardless of listening to music or not
[Xposed Framework Modules] tboooe:
Good point! Perhaps this is why music stops when the screen turns off and with Audiomix unbounced. I use Poweramp as well but have it set in Greenify to hibernate. So maybe if I unbounce Audiomix but remove it from the hibernate list in Greenify music will play. Then the question is which drains more battery...Audiomix or Poweramp. I will report back my findings.
[Xposed Framework Modules] cAase:
When greenifying poweramp does the music play when headphone jack is plugged in? Seems it doesn't work when poweramp is hibernated.
[Xposed Framework Modules] tylerdurden83:
I agree with you, but I'm still not sure how to interpret the numbers. First of all there is no clear indication of the t0, are they since last reboot? Unplugged cable?.

Also, I'm assuming that at least some of the stats are relative to all wakelocks, even those that I'm not managing with the app.

For example, where it says 13637 wakelocks acquired, it isnt referring to just the managed wakelocks (which in my case are NlpWakeLock and NlpCollectorWakeLock), but to ALL wakelocks. This number is imho irrelevant as it is, because it includes wakelocks that I can't or don't want to unbounce, like the 8488 RILJ wakelocks, etc.

On the other hand, the wakelock blocked count must only refer to those that I am managing, making it a case of comparing apples and oranges in my book.

My suggestion would be that the wakelock acquired count would only refer to the managed wakelocks, so it would make sense to compare how many were let throught and how many were unbounced. If both acquired and blocked refer to the same wakelocks, then they would be easily and meaningful to compare.

The same goes for the time allowed and time blocked, not just the count, and for the alarm count.
[Xposed Framework Modules] Osama Zabin:
Which version are using?

I faced FCs with 1.1.8, but after updating to 1.1.9 everything is Ok.

Try check the available updates through xposed and see if you really have the latest version; there was two version released in past 24 hours.
[Xposed Framework Modules] Kocane:
The most recent one :).. I went a version back, tgo 1.1.8rc2 and it was all good
[Xposed Framework Modules] tboooe:
Just curious if you are still seeing higher drain? Have you tried the latest version 1.1.9?
[Xposed Framework Modules] cryptyk:
The counts on the home screen are the global stats for your device. All wakelocks and alarms. I feel it's important to include the unmanaged wakelocks here because it shows the overall picture of how your battery is being used.

If you want stats (blocked vs. allowed) on a particular wakelock or alarm, you can find that on the wakelock detail page, or the alarm detail page. This shows you the impact for that particular item.

Thanks,

Ryan
[Xposed Framework Modules] tylerdurden83:
Sorry Ryan, but I still think that the stats are somewhat deceiving.

For example, are the stats since the last time I wiped them manually? In my case, the homepage allowed wakelock count is very high. Going in the wakelock tab, I can see that a big chunk of the total comes from the allowed almost 9k RILJ wakelocks. I entered the RILJ wakelock page, and it states that it's a wakelock that is held while having a phone call with the screen off. Problem is, since I rebooted the phone 6-7 hours ago, I did zero seconds of calls (I had to double check with another app). Like this, it's very hard to know what is truly offending and what is noise in the statistics.

Again, I do see your point in having total unmanaged stats in the home page, but I still think that having total managed ones there is also good, so maybe we could have all 3? I can do as you said, and enter in each managed wakelock tab, write down the blocked and unblocked count, go back to another managed wakelock tab, write the numbers down, rinse / repeat till i wrote them all down, then make the sum and see which is bigger and decide if I should raise some timers or not.
[Xposed Framework Modules] Mistertac:
And using WakeLock Detector will give you even more detail like what apps are using AudioMix and for how long for example.

That gives you a good picture as to if you really have an issue or if things are just running normally like they should.

I think every one using this module should at least be using WakeLock Detector and Better Battery Stats.

I never found a use for GSam myself as the other two along with stock Battery Stats is enough for me.

- Tapatalked From The G3 -
[Xposed Framework Modules] blax123:
Looks OK again, don't know if it was the update to 1.1.9 or anything else or magic :D

Sent from my OnePlus One
[Xposed Framework Modules] 1ceb0x:
RILJ is not actually from a phone call with screen off. If you look on the spreadsheet it has other meaning but then again we can't be sure that that one is. I have that wakelock everytime and i do 0 calls since 1 year ago. I always unbounce that wake lock.
[Xposed Framework Modules] tboooe:
Audiomix, Poweramp, Greenify

With unbouncing Audiomix to 240 secs and Poweramp not hibernated in Greenify music would play with the screen off but I got a lot of stuttering. After setting Audiomix back to default music played fine, whether or not Poweramp was set to hibernate in Greenify.
[Xposed Framework Modules] Mistertac:
Good to know. I just use Google Play Music to play my tunes and no issues at all but thanks.

- Tapatalked From The G3 -
[Xposed Framework Modules] DJMartini:
I use Google Play as well... Glad to know this didn't have issues cause I haven't tested it with it yet.

Thx!
[Xposed Framework Modules] kamedonski:
+1
[Xposed Framework Modules] cryptyk:
That's correct. Alarms are not yet supported on versions before 4.2.2. That's why the alarms screen is blank.

Thanks,

Ryan
[Xposed Framework Modules] MIKEMON:
again great work in the new version

many thanks
[Xposed Framework Modules] rignfool:
Ok...

AFAIK...

RILJ is the wake lock that is created every time your software ril interfaces with your hardware...

So... Phone to tower handshake... SMS... MMS... Data handshake... MAY cause RILJ wakelock...
[Xposed Framework Modules] 089man:
Hi have installed now newest version and have donate your app.

What must I do now, all buttons off, must I enable now all that 240 works? Or must I chance to other settings example 300 or other? What's the best entry's for the difficult wake looks....?

Have many wakes on alarm... What must I chance, 240 is standard...?

I9100 Tapatalk 4, Spirit-Rom 4.4. 4
[Xposed Framework Modules] tboooe:
I would reset the stats, fully charge your battery then let it sit overnight. When you wake up use an app like GSAM or BBS to check out your battery drain per hour. If its in a range you comfortable with do nothing. If your phone is draining too much battery per hour then use GSAM or BBS to figure out what is wakelocking your device most. Go into Unbounce and find those wakelocks. Refer to the great doc that was created by 1ceb0x and see if the wakelock is safe to unbounce. If so, proceed with one wakelock at a time. Adjust one then see how it impacts your phone starting with 240. After addressing your wakelocks I would then move on to alarms, again testing one alarm at a time. Remember that a high wakelock or alarm does not necessarily mean its draining your battery significantly. In my experience their will only be a handful of wakelocks or alarms that is causing issues with your phone. The rest are so insignificant that unbouncing them wont make much of an impact.

Just for comparison, my phone drains 0.1-0.2% battery per hour while at idle. This is with 4g, Gmail, sync, wifi, etc all on. I achieve this with the stock Unbounce settings + unbouncing the Icing wakelock.
[Xposed Framework Modules] ak800i:
What should we (the users in countries with disabled in app purchasing) do?
[Xposed Framework Modules] shockwaverider:
Thanks for the input. I'm not really terribly concerned about it; like I said, I'm using default settings anyway, so 1.1.4 works just as well as 1.1.9 for me. I've been on pretty much the exact same rom and kernel setup for probably half a year now, so it's pretty easy for me to notice when things are a bit "off". Which isn't to say that I'm not grateful for this module and cryptyk's work, in fact I donated even though I knew full well that I'll probably never get around to actually using the extra features; I'm just reporting my experiences.

:thumbup:
[Xposed Framework Modules] cryptyk:
Honestly, I'm not sure. Do you know how other apps solve this?

Thanks,

Ryan
[Xposed Framework Modules] the7thson:
I just purchased the Pro version, thanks for your work!

Using version 1.19, the app force closes almost constantly. I can't seem to keep it open for more than a few seconds at a time, I've rebooted and cleard cache etc but it's still happening. Should I try clearing the app's data? I don't wan to lose the settings I put in though ideally. Any ideas what I could try?

Thanks in advance.
[Xposed Framework Modules] tboooe:
Perhaps revert back to an older version until the bugs are weighed out of the current version?
[Xposed Framework Modules] cryptyk:
If you grab a logcat, I can probably fix it.

Otherwise, let android report the crash, and it will show up in my dev console.

Thanks,

Ryan
[Xposed Framework Modules] Pkt_Lnt:
Gravity Box does a donation that allows one to enter the PayPal ID. He even gives codes for those who help out with translatios, committs, etc Nice guy I'm sure he will help if you ping him. He added a Play Store key purchase later.
[Xposed Framework Modules] the7thson:
Thanks for you quick response! This might sound really silly - but how do I let Android report the crash? I don't get a notification, the app just closes and it goes back to the Launcher.

I'm trying to capture a logcat using the app aLogCat from the Play Store, but in reading the logs, there doesn't seem to very much there even though the capture is set to verbose. I did enable "Debug Logging" in the Settings for Unbounce beforehand.

My apologies in advance for the slight off-topic conversation, thanks again.

EDIT: looks like it's also causing FCs for lots of other apps randomly. I'm currently trying to revert back to 1.1.8rc2 or 1.1.7 etc but it keeps crashing Xposed at the moment.
[Xposed Framework Modules] lanwarrior:
I donated and tried to control the LocationManagerService wakelock. I turned the switch to "ON", but nothing happened. Pressing back will not do anything.

Is this by design?
[Xposed Framework Modules] kuchivas:
Click Done on keybroad after setup.
[Xposed Framework Modules] Pkt_Lnt:
No of course not. There was an early bug like this, what version are you using? Try to tap the switch instead of slide. Than tap on "240" and type in 240 then press done on keyboard and THEN back out to see.
[Xposed Framework Modules] lanwarrior:
Ah, I was using the old version. Updated and it is now working. [emoji3]
[Xposed Framework Modules] chhapil:
Any plans to add support for 4.1.2?

Is it feasible?
[Xposed Framework Modules] RedScotch:
garth nix would have hated the matrix movies

Is there a functional-feature comparison matrix for the licensed vs not licensed?
[Xposed Framework Modules] kingvortex:
You don't need a matrix. There is only one difference as explained in the first post.
[Xposed Framework Modules] RedScotch:
there is no pro without spoon?

The not-pro version did not appear to do much of anything hence the inquiry -- aside from the upselling you mention.

Perhaps none of those were actively employed on my device the last time I launched the not-pro version?
[Xposed Framework Modules] malachow:
Quick question related with donation [MENTION=526666]cryptyk[/MENTION]

If I once make a in-app payment, then I make full wipe installation with another rom & install Unbounce again - will it recognize automatically that I had already donated pro version?

Thanks in advance guys.
[Xposed Framework Modules] kingvortex:
Upselling? The module was intended only to deal with those wakelocks and alarms initially. Many people asked for the ability to control other wakelocks/alarms, so it was added for people who donate. If you cannot afford $1, then use the non donate version.

As for it doing nothing, have you had issues with those wakelocks? If not, you will notice no difference.

The donation is linked to your Google account, so if you sign in with same account, then you will get the donate version.
[Xposed Framework Modules] Charmacas:
I've used Unbounce for a while now on my Galaxy Nexus Maguro but I had to deactivate it because it seems to cause lag. Because the GNex is an relatively old device I am more able to notice differences I think.

Just to let you guys know. Anyone else had this phenomenon?
[Xposed Framework Modules] streetrod60:
hi cryptyk , your module just getting better and better since the first release. And my wish come true!! it can now be controlled by tasker..:D However, i am now having trouble with the settings with tasker:

I want to disable all Unbounce in wakelocks and alarms everytime i opened Maps or Camera, everytime i go to tasker, add "Unbounce Plug-in" in the task, it will go configurations with the UI contains options : Change wakelocks, change alarm, reset stats. Then i click change wakelock and lets say i set NLPWakelock to off or i set to 1 second, but everytime i hit back button there is nothing happened, the NLPwakelock still on and there is nothing in the "configuration" in the tasker. Am i supposed to hit back button everytime i set "new value" in the "change wakelock'? or i supposed to doing something else?
[Xposed Framework Modules] Mistertac:
Im just curious what if any additional items have you UnBounced?

Xposed can do some really funny things so it's certainly not out of the question, it could also be this module somehow interacting with another, hard to say.

- Tapatalked From The G3 -
[Xposed Framework Modules] Charmacas:
I deactivated some more than the default ones. But it was also noticeable when just having enabled the default ones. I instantly noticed a slowdown. I don't wanted to believe this and so I used it till today. After deactivating the module the lags vanished.
[Xposed Framework Modules] SenK9:
Fantastic Xposed module, great work by the Dev, donation is en route. Thanks to dev and other helpers in the thread ... I've only been using it a few days, but so far seems to be making a difference. Looking forward to further descriptions for some of the other strange items on the list ..
[Xposed Framework Modules] cryptyk:
Once you adjust the settings for the wakelock or alarm, push SAVE. :)
[Xposed Framework Modules] cryptyk:
I'm surprised that you would notice any lag, but I have done performance improvements for 1.2. Well see if they help.
[Xposed Framework Modules] MonkeyThumper:
Phone freezes after a few hours of having Unbounce activated in Xposed

I have been playing with Unbounce for the past few weeks. I noticed that my phone was sort of freezing overnight, and would require a reboot to fix it.

Here is the rundown of what I have found:

Phone was working fine before Unbounce installed. No issues with freezing.

I go to sleep around midnight, and put phone (ATT Galaxy Note3 running Xnote-7 4.3 ROM), on wireless charger.

I wake up at 7am, and check phone, display comes on, but phone is basically frozen. Time shows when things seemed to have stopped working properly. Usually 4am-5am.

I can turn display on and off with the power button, but the display is basically frozen. I have to either pull battery, or just hold my power button until the phone is forced to reboot. Background apps seem to be frozen also, because my alarm clock app (Alarm Clock Plus) doesn't go off as it should while the display is frozen.

It has done this multiple times, while Unbounce is activated in Xposed.

I disabled Unbounce in Xposed, problem goes away.

New version comes out, I install and re-enable in Xposed, to try and see if my problem is fixed.

Freezing problems happen again around 4-5 in the morning.

I decide to remove all wakelocks and alarms that are being unbounced, so basically unbounce app is just running, but the app doesn't have anything to unbounce.

Still get the freezing issue around 5 yesterday morning.

I then disabled Unbounce in Xposed again, and this morning I had no freezing issues.

It is very consistant. If Unbounce is activated in Xposed, I believe I can about guarantee that my phone will freeze by morning.

I won't be able to test much over the next two weeks. I am on call, and really need to depend on my phone being able to alert me to work emails, and phone calls. Once I am off call again, I will get back to testing and trying to track down what is happening.

So...I pretty much have to point my finger at the Unbounce module itself, and not a wakelock that I thought I may be unbouncing but shouldn't have.

Any ideas/suggestions?
[Xposed Framework Modules] cryptyk:
Is there something else going on at 4-5am? Tasker tasks, other scheduled tasks? Most problems with Unbounce have ended up being conflicts with other apps.

The other thing is to check Logcat around the time it freezes.

Thanks,

Ryan
[Xposed Framework Modules] MIKEMON:
great module

little question

I have viewed in sync / synchronization error Google /

gmail, calendar, everything is fine and notification

It may be this module?

Otherwise everything is ok, super job
[Xposed Framework Modules] ak800i:
They don't. We just have no ability to pay in our stone age country. Perhaps I could send you money through something else and you would send me a pro apk? If such thing is possible

I know this is a bit of a gray area in xda rules, but I'm only trying to pay for an app I really like
[Xposed Framework Modules] the7thson:
Quick update: I cleared cache, cleared data, uninstalled the app, rebooted, reinstalled the app and rebooted. The app still FCs every few seconds and starts to cause other apps to FC randomly as well. How do I let Android report the error back to you so you can see it? This is all I see in the Logcat:

--------- beginning of /dev/log/main
I/dalvikvm( 2925): Enabling JNI app bug workarounds for target SDK version 11...
D/dalvikvm( 2925): JIT code cache reset in 0 ms (0 bytes 4/0)
I/dalvikvm( 2925): DexOpt: illegal method access (call Landroid/content/res/TypedArray;.<init> (Landroid/content/res/Resources;[I[II)V from Landroid/content/res/XResources$XTypedArray;)
I/dalvikvm( 2925): Could not find method android.content.res.TypedArray.<init>, referenced from method android.content.res.XResources$XTypedArray.<init>
W/dalvikvm( 2925): VFY: unable to resolve direct method 82: Landroid/content/res/TypedArray;.<init> (Landroid/content/res/Resources;[I[II)V
D/dalvikvm( 2925): VFY: replacing opcode 0x70 at 0x0002
D/dalvikvm( 2925): JIT code cache reset in 0 ms (0 bytes 5/0)
I/Timeline( 2925): Timeline: Activity_idle id: android.os.BinderProxy@41d43d68 time:8548168
I/Timeline( 2925): Timeline: Activity_idle id: android.os.BinderProxy@41d43d68 time:8603274
W/InputEventReceiver( 2925): Attempted to finish an input event but the input event receiver has already been disposed.
D/dalvikvm( 2925): JIT code cache reset in 0 ms (49372 bytes 6/0)
I/Adreno-EGL( 2925): <qeglDrvAPI_eglInitialize:320>: EGL 1.4 QUALCOMM Build: I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
D/OpenGLRenderer( 2925): Enabling debug mode 0
I/Timeline( 2925): Timeline: Activity_idle id: android.os.BinderProxy@420f61b8 time:8625686
I/Timeline( 2925): Timeline: Activity_launch_request id:com.pushbullet.android time:8627945
I/Timeline( 2925): Timeline: Activity_idle id: android.os.BinderProxy@41d43d68 time:8634975
[Xposed Framework Modules] streetrod60:
sorry, but i could not find "save Button". So after i choose "configuration" in the tasker plugin then i will go to the screen with the three button : Change Wakelock, Change Alarm and Reset Start. Lets say I want to turn off the NlpWakelock Everytime i open map, so i open "change Wakelock" then i clicked "change Wakelock" then i choose NlPwakelock then i set NlpWakelock settings to off, and then where i supposed to find the save button?
[Xposed Framework Modules] Solace50:
for ther spread sheet could you guys re-organzie the alarms/wakelocks into groups like OS/Google/Other i was under the impression system related ones were going to be tested intially but i see you branched out to a few random ones.
[Xposed Framework Modules] Mistertac:
I think it's just a huge WIP really. Personally I've been hitting at the ones that have popped up on my G3 whether they've been OS or Google or Other.

Right now the Spread Sheet is still in its " rough draft " stage and will most definitely get more refined and flow better over time.

I'll try and look at what System/OS ones on my G3 I can add that aren't already in there [emoji2]

- Tapatalked From The G3 -