yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] animefans:
Ryan:

I know that logcat is confusing

Using latest Unbounce, and limit my xposed module to a bare minimum: gesture navigation and performance profile, and I go 2 days without freeze display

Just as I am about to announce victory, screen froze :)

But in different way

Power button can bring display up

double tap screen can bring display up (I can't before)

However, screen does not respond to any gesture

I have a feeling the combination of limiting xpose modules plus the newest version of unbounce will help reduce/remove screen of death
[Xposed Framework Modules] jaibar:
With Beta 1.2x I get the following behaviors:

- installation over 1.19 + reboot, wakelock and alarm tabs are empty (except the filtering keywords "safe/unbounced/etc."

- Clean installation only gets FC.

Tried on two nexus devices (5&7) both stock KK. Using quite a few xposed modules.

Will try to add logs later on
[Xposed Framework Modules] marbertshere:
Hi, I think this has been reported but just wanted to let you know that I get an immediate fc when opening the latest release. I downgraded back to the latest stable release (sorry I don't have the version number ATM) and everything works fine. S4, 4.4.3 GPE ROM. I have several other modules enabled, as well.
[Xposed Framework Modules] bflmpsvz:
Can this be used together with Greenify and if not which app does save battery more effective?
[Xposed Framework Modules] dorndi:
Both apps are very useful and worth a donation. I use both. If i would have to decide i would choose Unbounce.
[Xposed Framework Modules] nereis:
If you FC after update, it's probably just that the module requires a soft reboot then it works again.
[Xposed Framework Modules] 1ceb0x:
That's because the stats are reset and unbounce needs a few minutes to collect data again.
[Xposed Framework Modules] mrQQ:
cryptyk, I'm not sure if I missed your response, but do you have any clue about missing exchange alarms in unbounce?
[Xposed Framework Modules] Kocane:
Anyone else with somewhat bad TimedEventQueue wakelock in process 1013?

Any way to tell what cause such a wakelock? I think one can look in /proc/1013 (in this case) once the wakelock is happening but it's really hard to "catch" that moment
[Xposed Framework Modules] Mistertac:
How long has that one been keeping your phone awake and have you actually noticed a Battery drain from it or could it be business as usual with Android and actually things are just fine?

That is an odd one. I no longer have it showing on my phone and from reading up on it, it could be triggered by quite a few things.

- Tapatalked From The G3 -
[Xposed Framework Modules] Lither:
BBS is showing 482 wakelocks from com.google.android.gms (9.2/hr), how do I fix this?
[Xposed Framework Modules] wilkster:
That's already a low number, not much to fix. The NLP wake locks are grouped in GMS. Use BBS to get more details.
[Xposed Framework Modules] Lither:
This is the BBS information I get from com.google.android.gms

Alarms: 343, Intent: com.google.android.intent.action.GCM_RECONNECT

Alarms: 105, Intent: (com.google.android.gms/com.google.android.gms.checkin.EventLogService$Receiver)

Alarms: 25, Intent: com.google.android.intent.action.SEND_IDLE

Alarms: 4, Intent: (com.google.android.gms/com.google.android.gms.checkin.CheckinService$Receiver)

Alarms: 1, Intent: com.google.android.gms.gcm.ACTION_CHECK_QUEUE

Alarms: 2, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE cmp=com.google.android.gms/com.google.android.gms.icing.service.IndexWorkerService)

Alarms: 2, Intent: (com.google.android.gms/com.google.android.gms.security.snet.SnetService)

Alarms: 1, Intent: com.google.gms.auth.authzen.CHECK_REGISTRATION
[Xposed Framework Modules] Mistertac:
Your first one there GCM RECONNECT I've added into the Spread sheet some time ago and I've UnBounced it without any issue, you could try that.

You also use something like Auto Run Manager and disable Check In Services to get rid of those ones. The ones with Icing in the name I'd have to assume do with Play Services and you can obviously UnBounce those to your liking. Just start low and see how it effects your phone that's all.

- Tapatalked From The G3 -
[Xposed Framework Modules] 1ceb0x:
How are you able to disable Checkin service without any side effects? If i do that i will be unable to install apps from my sdcard...
[Xposed Framework Modules] Mistertac:
I used Rom Toolbox Pro -->Auto Start Manager then under Google Play Services and Google Services Framework I disabled everything with CheckIn in its name :

Spoiler content hidden.

- Tapatalked From The G3 -
[Xposed Framework Modules] 1ceb0x:
oh. thank you for the tip. i think my problem lies under the fact that i was only disable them from the GPS not from the framework as well... makes sense now. cheers brother! ps: i use disable services app
[Xposed Framework Modules] Lither:
What are your unbounce settings for GCM Reconnect? I have searched the thread and see that you have set 600 secs for Icing so I will give that a try

Also I already have AutoRun Manager installed and have disabled all Google Play Services and Framework receivers
[Xposed Framework Modules] Mistertac:
I'd try 240 for the GCM RECONNECT Alarm.

And I've just had good luck with Auto Run / Auto Start Manager myself but I suppose Disable Service app should work too.

- Tapatalked From The G3 -
[Xposed Framework Modules] 1ceb0x:
wow... that must not be good for your phone. how do you get notifications, then?
[Xposed Framework Modules] bweN diorD:
here is what i have so far. all but gcore and geofencer (added this morning) have been on since last night or longer.

only 2 issues so far from something i added last night, gmail isnt pushing (i only unbounced the calender and game syncs as far as i know), and the hotspot didnt turn off after 10min of no connected devices (not a big deal).
[Xposed Framework Modules] wilkster:
Lither, Based on the data you are providing you have an up time of 52+ hrs (482/9.2). Therefore you are getting GCM_RECONNECT wakelocks every 9 minutes (52.39*60/343). I just don't see that as an issue and has a negligible impact on your battery. Why would you consider shutting down the service? Maybe I missed something.
[Xposed Framework Modules] Lither:
I see your point, Unbounce max seconds limit is 600 which is equal to 10 minutes and I'm getting GCM_RECONNECT wakelocks every 9 minutes so I should leave it as that for now and see what happens
[Xposed Framework Modules] MIKEMON:
v1.2b3 installed and everything seems fine

seems better blocking wakelock and total balance

good work

I wish you all stand with this module and donate if you can
[Xposed Framework Modules] Mistertac:
I hadn't looked at what your times were when I said try 240 so yes luckily someone else here caught that it's every 9 minutes roughly for you...

- Tapatalked From The G3 -
[Xposed Framework Modules] Javi22:
Why are you guys using so less aggressive blocking times? For me, I've unbounced Npl wakelocks and audio mix, setting 3600s always, and no have any issue

I always set a number higher than 3600 for anyone, unless I am aware it's clearly convenient to set a lower value
[Xposed Framework Modules] Mistertac:
From what I've seen is that the times will effect each persons setup differently depending on how their phones are setup.

For example those running the Google Launcher and those who use more location based " Google Stuff " or user apps that are Location Aware may need those times lower to function correctly that's all.

Each persons setup is so different that it's easier to start low then monitor the times and increase them checking for issues along the way.

- Tapatalked From The G3 -
[Xposed Framework Modules] bweN diorD:
i have been advancing mine slowly over time to watch for issues. some of mine are @ 1000 but havent got higher yet. if the wakelock time is only a few seconds over hours, im not sure there is any point in limiting it further unless i basically want the item to not function.
[Xposed Framework Modules] Mistertac:
By the way if you're running into issues using Disable Service for CheckIn Services try using my method of Auto Start Manager.

I was just playing around with a One Max disabling these but using Disable Service app and I had nothing but issues like Play Services Force Closing etc... I reverted changes and used Auto Start Manager and everything is disabled and still working just fine.

- Tapatalked From The G3 -
[Xposed Framework Modules] 1ceb0x:
no issues so far. haven't tested my old bug of not being able to install apps from sdcard though. will see how it goes from now on.
[Xposed Framework Modules] bweN diorD:
so i apparently blocked something to do with notifications last night (thought i was careful), now i cant seem to fix it.

tried reverting to defaults, completely disabling unbounce, and cleared cache's. stil no notification from gmail.

any ideas?

thanks

edit,

never-mind, fixed it. uninstalled then re-instlled gmail and all seems to be good.
[Xposed Framework Modules] Mistertac:
Have we already pointed out the issue of not being able to Donate again? I think someone has I just forget lol been a long week for me...

- Tapatalked From The G3 -
[Xposed Framework Modules] bweN diorD:
the current version from the market let me donate again just now, and when i tried again, it was going to let me.
[Xposed Framework Modules] aeoveu:
Okie then...

So I'm on the latest beta (the one that's synced with the Xposed repo as well), AND in addition to the four stock location entry blocks, I've blocked Line Messenger's alarms as well as blocked this specific wakelock (which seems to be a complete pain in the arse since it refuses to tame down):

wake:com.google.android.gms/.auth.be.proximity.authorization.userpresence.UserPresenceService

When I tried throttling it to 240 seconds, I saw that it would still creep up in the wakelocks when the phone was asleep, so I put it to 480 and my phone slept (granted, I was on Wifi and I intentionally abandoned the phone for 1h45m (approx)), and this wakelock didn't show up.

But then - after I had the screen turn on, the stupid frigid wakelock came up and ate around 1 minute all of a sudden - but that happened when the screen was on, so it's not too much of an issue (in my ~2 hours of testing). During this time, the drain on the battery was 0.6% (I reset the GSam monitor stats for this specific experiment).

I thought somebody else might be able to benefit from throttling this wakelock like there's no tomorrow - I have no idea why it's showing up. But there you go!

I'll be able to confirm more accurately tomorrow whether ripping apart this specific wakelock helps or not. Oh, and for the record, I've disabled Greenify (disabled auto hibernation and revoked its root privileges) to check whether the kernel wakelocks are tamed (so far, I can't see any daemon Supersu entries come up - heck, I can't find them now to begin with! :s )

Update: the screen's been on for a while, but this specific wake lock hasn't increased. I really don't know the science behind it, but as long as it doesn't bother me anymore, it should be good news. Will still have to wait till tomorrow to check whether its been fixed or not.
[Xposed Framework Modules] rignfool:
That sounds like gmail sync was off in settings>accounts
[Xposed Framework Modules] :
No side effects with disabling these check-in service? What is it supposed to do? I don't see it in my wake lock list I think, but nevertheless blocking it might help with battery a bit...

Thank you!

N7100 - Paranoid Android 4.4.4 [MENTION=353015]240[/MENTION] dpi
[Xposed Framework Modules] bweN diorD:
that was the first thing i checked, it wasnt.
[Xposed Framework Modules] cryptyk:
There's not currently an opt-out. I'll put on in the future. It only uploads the stats once every 24 hours, and only when your device is awake from a wakelock anyway.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
It's been captured in the bug report / issues list on BitBucket.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
The beta versions aren't configured for Play Store donations. :)
[Xposed Framework Modules] cryptyk:
Thanks for the help testing in the last two days! I've just release v1.2 to the Play Store, OP, and Xposed repo.

The big thing here was performance boost, and global stats. I know the global stats aren't that interesting, but it was a fun side project, written in Go, and running on Google App Engine.

The next release will likely be a bug fix release, and a push to improve performance even more.

Thanks again, everyone. I couldn't wish for a more supportive community. You guys are awesome.

Thanks,

Ryan
[Xposed Framework Modules] Randi:
is there a change log in comparison to b3?

just asking cos I've been having the kernel panic issue and a couple of other bad ones (Google voice dialer opening when receiving a msg, maps crashing) will try to get a log later (thats on a Galaxy S3 Lte (i9305) with stock 4.4.4)

ive been really quite conservative when unbouncing, only the REALLY bad ones which were "safe to unbounce" plus a couple of app specific ones (soundcloud and especially onedrive). imho the "safe" definition in the app is not quite where it should be, and also in comparison with the google sheet where it mentions possible side effects. Any chance to put a link to the sheet / further explanation into the app?

Otherwise quite awesome! :)
[Xposed Framework Modules] cryptyk:
Ugh. Just pushed 1.2.1 to fix the crash people were seeing when upgrading from 1.1.9.

Thanks,

Ryan
[Xposed Framework Modules] Mystique:
Just got pushed 1.2

East Coast, 9:05pm..

Sent from my GT-I9505G
[Xposed Framework Modules] 1ceb0x:
I have the same issue. Blame google for it. The new Play services update bringed that in. I have disabled this by using Disable services and i have no issue at all now. No side effects either. Try it out.

I disabled them and next thing you know i had a wakelock from Google play services of 40 minutes. I did what [MENTION=5500746]Mistertac[/MENTION] said - disable them from both Google Frameworks and Google Play services + reboot. I have had this kind of behavior before and i thought it is only because i was not disabling them from the framework as well but guess i was wrong.
[Xposed Framework Modules] aeoveu:
I was hoping I could have this mod throttle certain services without having to install any other app. I suppose this is out of the scope of this mod, and if this specific wakelock (as well as a few other nasty ones) doesn't seem to contain itself, I suppose I'll take your route and disable the service.

I'm just avoiding disabling services (for the same reason you wrote regarding the Checkin service and the 40-min wakelock) in case of any unintended consequences, so throttling seems to be a win-win. But - I'll probably try your method again if my method doesn't work.

Gratz! :)
[Xposed Framework Modules] 1ceb0x:
Well you have to test them by yourself. What works for me may not work for you. Since for [MENTION=5500746]Mistertac[/MENTION], he was able to have no side effects by Disabling Checkin Service and EventLogService all together, that didn't worked for me. So better to do it now and test it out for a few days.

Disable Service app is very small and it does not eat up resources.
[Xposed Framework Modules] gruntparty:
Does anybody know how to reset any services that have been disabled via Disable Service app or Autostarts app? I kind of want to restart fresh cause on every system boot google services has crashed and i have to check the ok box for my other apps to load. Also I just noticed i have the CheckIn and EventLog wakelock as well having disabled them through the Disable Service app.
[Xposed Framework Modules] MrKra:
In better Battery stats I have an alarm dk.tacit.android.foldersync.full.foldersync.

I cant find this alarm in unbounce !?
[Xposed Framework Modules] 1ceb0x:
Settings - Apps - Disable service app - Clear data -Force close - Reboot
[Xposed Framework Modules] magnamentis:
yes

APP: Rom Toolbox Pro

TAB: Auto Start Manager

Setttings ( 3dot top right ) > Restore All

that's it and you can keep your other settings like that
[Xposed Framework Modules] Mistertac:
Anyone else experiencing Play Services Force Closing and not being able to connect to the Play Store????

I don't think it's from this module actually or if it is I don't know what could have caused it because I haven't changed anything to do with Google in a while.

When I got this phone I disabled CheckIn Services and then when this module came out I unbounced some Google Play Services items but everything has been working great and as expected.

I tried ditching this module and that didn't help. I tried enabling the CheckIn Services and that didn't help.

Only thing that Got me going again was a factory reset which... Is totally a pain in the ass on a stock debloated rom.

Looks like I'll be busy today removing bloat and setting my phone back up lol let me know if any of you have this issue, thanks

- Tapatalked From The G3 -
[Xposed Framework Modules] magnamentis:
general statement taking the opportunity

no issues here and as much as i appreciate all the input found here and how great the benefit to the community might be from those who

tweak their devices to the edge. i long time wanted to say the following and your issue just proofs once again it's right.

there is certainly nothing wrong to try everything out and learn from trial and error, that's how it works, but everyone should be aware of the fact that sooner or later this is what's going to happen:

if we disable apps, services and parts of them and if we do it excessively, sooner or later we are going to loose oversight. there will be so many little checkboxes unchecked and so many tweaks and mods in our config which influence each other and therefore sooner or later interfere and cause trouble. so whoever tweaks to the edge must be aware that sooner or later the only way to get things back to a comfortable working state would be a factory reset and formatting partitions, depending on the apps involved sometimes including data and sdcard0.

so this is not a statement against it but whoever is new to this should know that this is the price which we all pay once in a while and with a

touch of wisdom in choosing and comparing benefit against risks it happens a bit less. so i had to reset once this year with only one device after i lost GPS on my one plus one and last year it was twice after i lost IMEI on Nexus 5 and all went havoc on my N7100 due to changing form ext4 to f2fs file system while kitkat and external sd-cards in combo with exynos chipsets hold another bunch of trouble at the ready haha....
[Xposed Framework Modules] aeoveu:
Gonna update: the wake lock didn't show up in the 7 hours of idle time.

What I did:

- turn on location reporting

- turn off WiFi (WiFi scanning is available...that option in the WiFi menu...that was enabled)

- stayed mostly at home, but went out for around an hour or so by car (not sure if this has an impact, but I'm 90% sure it does)

- disabled Greenify from automatically hibernating apps

- did not turn on the screen for ANYTHING. I received several WhatsApp messages, some Line Messenger alerts (not sure how many, since I don't use it much...I'm subscribed to a traffic update group), and around 7 SMSs.

Since 3g coverage in my house is very weak, I suspect the phone stayed on edge all along. Also, ever since 3g came, edge has taken a hit, so I can't say how well the internet performed, but I can say that the signal strength was good all along.

Anyway, I'll let the screenshots do the talking. I tried to take these all within 1 min so that there wouldn't be any extra drain.

Screenshots are in reverse order (I.e. the last picture = the first screenshot I took)

Thanks for your post. I'm experimenting with my current config right now, but I intend on trying disabling the service method as well. That way, I could reduce the overhead (which seems to have improved quite a bit) from the unbounced mod and simply nuke the offending wake lock altogether.
[Xposed Framework Modules] Mistertac:
Oh you're definitely right there! And I'm certainly guilty of going " too far " at times and like you said this is the price we pay.

Only thing is usually I'd have a Nandroid to fall back on but LG has locked the bootloader on all the G3s except T-Mobile. Ahhhh I do miss my S4 at times.

This time around I'm not going to disable and remove so many things and see if just by using this module I can control everything.

- Tapatalked From The G3 -
[Xposed Framework Modules] magnamentis:
interesting once more

for us europeans it's sometimes hard to comprehend to what extent your IPO's can hold such a tight grip on their users for so many years. if one provider would do such a thing over here it would face a serious loss of customer base and crawl back quite quickly hehe.....

whatever i was not aware that you're US and T-Mobile would definitely be my choice over there ( german enterprise roots pay of here )

however you made me curious, until now i was sure that every bootloader can be unlocked if only the device is prominent enough to attract devs and long enough in the market ( which might not be the case with the G3 here ) so out ouf curiosity i will start evaluating a bit into that direction, specially because as soon as my fiancee will drop her next device ( which happens 4 times a year at least haha.. or crying, depending hehe.. ) i think about going for a G3 as well. albeit we do not have the bootloader problem over here i'm still interested to beat the dragons grrrrrrr.... ) let's see

EDIT: it's so annoying to always use my devices to thank because of the 8 thanks limit, should anyone know another way to get around this just let me know.

EDIT: by the way when you posted your tweaks from within rom toolbox pro recently i was sure it will happen, i never touch those again as well as all the denials in privacy guard ect.

i can really count the day until i have to find the culprit ( which will be difficult on the permission level to find ) or to go with a factory RS
[Xposed Framework Modules] Mistertac:
Well usually Verizon and ATT here are the worst offenders of locking down their phones. As far as the G3 goes though... Even your International version comes with a locked bootloader , hard to believe I know. It actually seems that here T-Mobile has actually requested the bootloader to come unlocked.

Our G3 devs are close to unlocking them though and say it WILL happen. If it doesn't happen however, im leaving Verizon and going with a carrier that has Nexus that's all. To me it's totally wrong a carrier controlling such things but that's a topic for another debate .

Anyways as to stay on topic a little.... This here will give be a great chance to test UnBounce on a fresh device[emoji16]

- Tapatalked From The G3 -
[Xposed Framework Modules] 1ceb0x:
This google wakelocks are unbearable now... Before its update, the process was not even showed in Battery stats and now it helds the phone awake with almost 30 minutes in 8 hours (nm my case).

I will try something.. since we all know that updates can cause some things to break:

Turn unbounce OFF for a few minutes.

Clear data from Google Play Services.

Reboot.

Use the device for a few minutes and then fire up unbounce again.

Hopefully it will give me some results.
[Xposed Framework Modules] Mistertac:
Let me know how that works out. New Play Services brought this one for me, I'm assuming it's same for you.

I've tried letting Google do it's thing after factory resetting my phone but this one just doesn't die, definitely needs UnBounce-ing I think, although I was hesitant to because of my previous Play Services issues that led me to the Factory Reset

- Tapatalked From The G3 -
[Xposed Framework Modules] 1ceb0x:
Yes. That's the very same for me. Even unbounced and still gives problem. I will shout out tomorrow after i gather some more stats.