Hi all,
I've got a Moto G5 Plus running Android 7.0 running stock firmware. Every day between 22:00-23:00 the phone is unusably slow, looking at the developer options and Tinycore resource information the memory is exhausted but CPU is pretty much idle. Rebooting the phone doesn't resolve the issue, only waiting until after 23:00.
Investigating the issue I've used SD Maid to examine what is running. Killing running tasks one by one doesn't help, nor does killing background services. I can't pin the issue to a rogue app or background service, the slowdown occurs independently of intensive background tasks (Google Photos backup, device backup, built in Play Store security scan). It seems like the issue is a low level OS one. I'm posting here rather than the device specific forum to check if this is a known issue with early Android Nougat builds. I'm at the mercy of Lenovo and still waiting for updates to bug fix point releases.
This has happened since day one of having the phone and I can't see any of the typical causes applying. I don't have any silly apps installed - Cheetah Mobile task killers, anti virus or any apps from nasty sources. I don't use task killers regularly, I only have SD Maid for monthly cleanup and this issue happens every night. Writing this now the phone is doing fine, 20 minutes before 22:00. Around 2.3 GB of memory used according to Tinycore but as we cross 22:00 it will shoot up. At first I thought this was uptime related but it's 22:00 which is the trigger.
Is there anything I'm missing? I've tried searching but the majority of posts relate to a rogue app, the time related trigger seems to be special. Apologies if I'm being silly. As an aside I've switched from iPhone to Android, I had a Nexus One back in the day (Android 2.2) and had years of free iPhones from work. Android has been busy in the intervening years and it's a great platform!
Thanks in advance.
Switch the net off, to check it's not internet related, like updates
Sent from this galaxy
pr1jker said:
Switch the net off, to check it's not internet related, like updates
Sent from this galaxy
Click to expand...
Click to collapse
Thanks for the reply. I've tried switching off mobile data and wifi, and turning on aeroplane mode, they don't make any difference. Forgot about this in my post, sorry.
I have disabled Google Play Store auto app updates. Even if this was the cause I'd expect to see something in my process list showing background activity / services gobbling memory.
Maybe it's something that has been fixed in Android 7.0.1.
Posting just in case anybody else has the same issue...
I'd activated the hidden Night Mode in Android 7.0 using Night Mode Enabler / System UI Tuner. Turning off Night Mode fixes this. Presumably this is why Night Mode didn't ship in 7.0!
Related
I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
crunchybutternut said:
I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
Click to expand...
Click to collapse
I stopped using the app because of this. I tried contacting support and was brushed off. I love the app but not the lack letting my phone sleep.
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
crunchybutternut said:
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
Click to expand...
Click to collapse
That would be great. Thanks for helping him out with this as I would love to use the app.
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Kcarpenter said:
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Click to expand...
Click to collapse
YouMail http://www.youmail.com/home/index.do is a service that replaces Sprint's (or any other provider) voice mail service with their own. It allows you to set custom "smart" greetings for each caller in your contacts, among other things. Check out the site for more info.
Here is the latest response from the developer I have been working with.
Hi [Name],
I did some more research and can confirm that I see the same behavior as you when I run the YouMail app ('active' @ 100%)
I'm not exactly sure what the cause is, as the application is indeed going to sleep when it has nothing to do. The problem also seems to be quite widespread, affecting what seems to be "most" applications that loiter around in the background doing nothing for most of the time.
Since you use 'Spare Parts' you should notice that in there is a way of viewing the 'Partial Wake Lock' usage of a given application. According to the Android developer documentation this is the ONLY way an application can keep the phone "awake" other than 'prodding' it every 30 seconds or so (and you'd notice that 'coz the screen would never go off).
As long as that "Partial Wake Lock" value is low (and it should be unless you're constantly hitting "Menu -> Poll") it means the application is indeed behaving correctly.
All I can offer is that we develop a new feature into the app so that you can tell it to automatically exit when all of the automatic polling settings are disabled - that way the phone would literally shut down the app "sometime" after you back out of the message list. Do you think that's worth it? Or should we wait for HTC/T-Mobile to fix the root cause of the problem?
Doug
Click to expand...
Click to collapse
And my response:
Do you mind if I share some of our conversation with a community forum? It might help get others involved and more feedback for you to use in further development.
As far as other apps loitering in the background, my understanding is that Android (using the same process as other Linux distros) keeps recently used applications in RAM to make them more quickly accessible to the user, and will clear them as the RAM is needed by other apps.
I have seen this issue in the past with other apps (i.e. the HTC messaging app locking the dialer and maintaining 100% awake time) but has all been resolved by updates to the apps themselves.
Click to expand...
Click to collapse
Lastly, his response:
Feel free, I don't think I said anything bad
I we get enough requests from "the community" I'll be given time to add the 'exit when done' option (basically it'll become a "dumb" app that only checks for messages when you start it up instead of waking up every so often to check [like after you miss a call])
And yes, Android is a little stranger than normal in that it tends to leave applications running for an unspecified time after you "close" them. (basically until it needs to run something else, or it runs out of memory, or .....)
The YouMail app is a little different in that it runs as a background service and schedules the phone to wake it up whenever "events of interest" occur (you get a TXT, your phone rings, it needs to poll, etc) - so even if the OS does close the app because you logged onto "hugebitmaps.com" and the phone ran out of memory, it'll start it up again as soon as it can.
I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something
Doug
Click to expand...
Click to collapse
I can post more of the conversation history if it would help. Anyone have any ideas what might be causing this beyond coding issues?
If anyone wants to send their YouMail log for inspection just enter this code in the dialer *#*#963867#*#* (*#*#YMDUMP#*#*) and it will let you send an email with the log's text.
Tried in 2.1 beta
"I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something "
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Hi, Doug from YouMail here.
Just noticed my words and thought I'd give an update - although not much good news.
I basically spent the last 2 days completely reworking the YouMail app's back end code so that anything and everything that could possibly be shut down when it isn't actually doing anything is indeed shut down.
When it came time to test it out -- 100% awake time again (although I stand by my earlier comments that "its not just us").
If I run the same app on a HTC G1 the phone will last a good 2 days (maybe more) without battery issues. If I uninstall the app the difference is minor.
This information, added to all the discussion on the Sprint forums about how the HTC "extras" that this phone comes bundled with have caused the same problem leads me to think that there is something in the Hero that's not behaving properly.
I see other comments like "It does the same on my <insert phone model here>" - well, we don't have unlimited resources, so if you can put the small amount of effort in to dial the 'dump' code mentioned above (*#*#963867#*#*) then maybe we can start to find a pattern here (maybe it's all the Android 1.5 based devices for example).
I'd also like to thank crunchybutternut for all of his assistance and time in trying to sort this issue out.
Doug
superman.namrepus said:
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Click to expand...
Click to collapse
If I can get in touch with someone who has access to the "guts" of the device and that can help me determine whats going wrong then that would be great. Neither the Android developer list nor the HTC forums are particularly helpful when it comes to tricky problems.
Bump
Anyone have some insight on this?
Ok - If someone working on one of these custom builds is prepared to lend a little assistance I'm willing to put a custom build on my phone and try to debug this a little deeper. However, with the number of hours that I get to work on this app.... and all the "fun" blocks that Google have been putting in our way w.r.t Android 2.x, I may not get much more time to work this problem.
That being said, I'm going to try experimenting with a new test app that just adds (one at a time) the raw features of the YouMail app in the hope that a single change triggers this wonderful problem you guys have. If that's the case then I'll put on my Sherlock Holmes hat and try to work around whatever is causing it.
Doug
Any news ?
soundmind said:
Any news ?
Click to expand...
Click to collapse
Got this from ymDoug:
No progress as yet - not seen anything from xda folks either.
I've made *massive* changes to ensure the app is shutting down absolutely everything it can when it has nothing to do - still no joy.
I've even gone through a lot of the Android source code and can't find anything that would indicate I'm doing anything wrong. There is one debugging method I'd dearly love to call inside the Google Android code (it dumps out a list of who is keeping the phone awake at any point in time) but the method is only accessible to (a) Google, and (b) People who cook their own ROMs. The official Android people are doing their usual stand-up job of ignoring the difficult questions
I am still making the odd change here and there, and my test app doesn't seem to be having the same problems (of course)
Regardless, there will be an updated version on the web site in the next day or so - I'll need to ensure my changes haven't completely screwed things up
Click to expand...
Click to collapse
Doug has made some changes, does not seem to completely resolve the sleep issue though.
Here's the link to the change log:
http://forums.youmail.com/forums/viewtopic.php?f=12&t=18
Click to expand...
Click to collapse
FYI: The version in the market is several revisions behind.
Hi there-
My Galaxy S2 just last night started with some new weird behaviour. I had tried to use it for navigation earlier in the evening and left WiFi and GPS on accidentally... an hour or so later the phone was running hot and started rebooting (has never been super-stable, so I wasn't too concerned) - charging overnight and now the phone insists on rebooting after about 1-2 minutes.
Have rebooted into SAFE MODE, and things are relatively ok, until I open the SETTINGS> APPLICATION MANAGER... which triggers a crash/reboot almost immediately.
I've not installed any new apps for some time (nor bothered with any regular virus scanning) - and am not sure what's up with my phone.
I'd really like to avoid having to re-flash/factory reset... as getting one's phone back to "normal" can take months!
Any helpful input would be most appreciated.
Thanks in advance!!! =)
Running Android 4.3.3 JellySNAP ROm, Kernel version: 3.0.101-Apolo_4.13_Regular-gf40153f
[email protected] #603
Build number: JSRA K47|=|v7.0
Maybe found the culprit? How to remove it? :/
Just in case anyone actually cares, I may have found some useful info...
Facebook Messenger has been very resource hungry and unstable... In my culling of apps I'm noticing it is the most resistant to being uninstalled. No matter how I find the app (in Rom Toolbox, App manager etc) - it won't let me kill it fully.
Attempting an uninstall of Messenger triggers an immediate crash/reboot.
How can I completely obliterate it?
Loopster said:
Hi there-
My Galaxy S2 just last night started with some new weird behaviour. I had tried to use it for navigation earlier in the evening and left WiFi and GPS on accidentally... an hour or so later the phone was running hot and started rebooting (has never been super-stable, so I wasn't too concerned) - charging overnight and now the phone insists on rebooting after about 1-2 minutes.
Have rebooted into SAFE MODE, and things are relatively ok, until I open the SETTINGS> APPLICATION MANAGER... which triggers a crash/reboot almost immediately.
I've not installed any new apps for some time (nor bothered with any regular virus scanning) - and am not sure what's up with my phone.
I'd really like to avoid having to re-flash/factory reset... as getting one's phone back to "normal" can take months!
Any helpful input would be most appreciated.
Thanks in advance!!! =)
Running Android 4.3.3 JellySNAP ROm, Kernel version: 3.0.101-Apolo_4.13_Regular-gf40153f
[email protected] #603
Build number: JSRA K47|=|v7.0
Click to expand...
Click to collapse
I managed to "freeze" messenger with a lot of luck... though I can't remove it. Phone is kind-of ok... unless I open the Application Manager.
Seems Messenger doesn't want me even looking at it! (Instant reboot)
Any ideas how to remove this awful program?
Hi there,
You'd be best served asking for help from the experts who own your device here:
[Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Good luck
Hi there!
I've contacted nvidia regarding this issue (reps seems oblivious) and posted it on their official forums to no avail, so I'll try and give it a shot here.
Basically whenever my tablet connects to WiFi after being disconnected for some time (a few hours to a few days), the tablet freezes when it downloads notifications. The freezes can be minimal (like a 5 second freeze) or be quiet substantial (it can lock up for as long as 10 mins). Once all notifications are downloaded and displayed, the tablet then performs like a charm. I even got my tablet replaced from nvidia and it has the same problem as the one I sent in. Uninstalling Facebook and Facebook Messenger improves performance drastically, but when my tablet checks for notifications it freezes still freezes for a few seconds (with Facebook installed, it could lock up for 10 mins and crash the launcher multiple times). Running on max performance did nothing. I'm really curious if this is a hardware or software issue since some people doesn't seem to have this problem.
I'm running on nvidia's stock firmware (4.2) unrooted.
So here is my question. Have any of you guys experienced this problem? Were you able to solve it? How did you solve it (did a custom rom solve this)?
The main reason why I haven't installed a custom rom yet is because I use the stylus frequently and I use the touch-block feature in nvidia's stock roms and couldn't find ports of it.
Here is a video of the issue. (youtube.com/watch?v=cJrUPV7mY6s) Now there are a lot of widgets on the video, but I assure you removing all of them does nothing. I tried.
Facebook Messenger. That says it all. What other apps have you running in the background?
This definitely sounds like a software issue to me.
Maybe you're being hijacked. Who knows.
I've had this same issues since I got the tablet (K1). System reset, no non-Google apps. Happens regardless of FW; I'm on the latest update. Don't be quick to blame the OP.
Basically, every time the tablet gets a new network connection, the system hangs and becomes unresponsive for 10 seconds to 2 minutes at a time. It's obvious that it's updating all the apps' network requests. However, the thread priority should make the system hang. I've only seen this issue on the K1; never on any other Android device. Either they're using a custom network stack, or they've messed with networking priorities.
I'm on the latest update
Click to expand...
Click to collapse
Of Facebook Messenger? Or OS? Or all apps?
Either way, it makes no matter no such issues on Lollipop. I am just saying.
Hi all, long lurking rom-installer who can self-fix most problems here. Got a problem I can't fix that's bothering me. Recently upgraded to an S7 so naturally rooted it on day one and been trying to get it my-kind-of-working fully ever since. I do like to bugger about with things in a vain attempt to shield some private data from some orgs and realise I'm in a particularly specific hole that I'll probably have to climb out of on my own, but if you don't ask...
Internet using apps pretend to work, sometimes for days, then just refuse to open. Screenshot example of the second and persistent error (after simply "Lightning has stopped" the first time) is attached.
Model: G930F
Current ROM: ambasadii 7.0 TW Nougat (here)
Xposed: 88.2
Root: Magisk
Significant mods:
1) use xPrivacy
2) disabled significant number of remaining packages using Package Disabler Pro (list attached)
3) run Orbot
4) run AFWall
5) modify app permissions in Settings/Apps to restrict where I think I safely can
6) run BackgroundRestrictor
The behaviour still emerges even if I don't apply 4), 5) or 6), it has started prior to me finishing my tweaking.
I know xPrivacy is not supported for Nougat but it seems to work ok for the most part with some retweaking of settings since moving from Marshmallow on my old phone. I understand it could be the cause of the problem but I'm wedded to (some of) my privacy enough to persevere before abandoning it. For the record I've checked the usage log for restrictions on any calls around e.g. internet that might be interfering but I've been unusually generous with permissions trying to fix this and there's no restrictions on any apps with internet access around that, or much else really at this point. I've also had a look in general usage log rather than app specific, looking for system components that may be working alongside the app and failing with a restriction but can't see anything being denied. Any system apps haven't been touched by me, I fetched what I could from xprivacy crowdsourced restrictions on the base ROM apps and then only applied my template to apps I've downloaded myself.
Some other background on the problem: everything will be set up as I like it - ROM installed, debloated, all the rest of above modding applied. It will be working super-fine. Nice and fast, little bloat left, just enough Google to get Play Store, apps installed and working, all will be and appear fine. After an undetermined & fluctuating length of time all of the internet-facing apps will suddenly not open. This includes but isn't limited to the Browser (stock and Lightning, Brave, Pale Moon, etc.), Twitter, Signal and the Official TWRP App.
Interestingly, internet-connecting apps that will connect on demand but don't seem to make a call on every app open (mostly due to prior settings changes) do not fail. They will still open fine and work fine, connecting when asked and not crashing. For example, K9 Mail and Pocket.
Another weird data-point: Signal will fail but will often do so later than the other internet-connected apps - possibly it has a token with GCM or something that when it expires will try to renew on app open which is when it starts to fail like the others?
The apps will work again if uninstalled and reinstalled but once the behaviour starts again, and it will, it will repeat. Sometimes twice or more in a day. So reinstalling every time is not going to make for a usable phone. It's like they have an error renewing their wifi lease or something.
It can take up to three days to begin - this build it worked fine for days whilst I was away and slowly, progressively building the system back up with regular TWRP backups. I can restore a TWRP backup from about 6 hours before the problem started and it'll work fine again, but still wait a random amount of time before the problem begins again.
I did think it may be something to do with the router here and home WiFi as it behaved much better whilst away and didn't break until my return, though that is likely coincidence. I'm in pattern-observing mindframe so false positives are everywhere. I thought it was connecting to the PC via USB that was doing it at one point.
Last data point: it's happened with a different base rom too (Decent here), same thing, but came on sooner each time. I would change the base rom again to see if it's something there but I suspect that should be one of the last things I try given it's happened across two roms now.
Anyway, if anyone has any insight on Nougat TW ROMs on an S7 with this kind of set up and/or any clues or ideas as to why internet connects would suddenly be crashing all these apps... I'd be grateful. Otherwise I have many reinstalls and possibilities to eliminate. Which means waiting many sets of days before I can repeat, which makes progress frustratingly slow when you depend on the phone (Signal particularly) to connect with people.
AFWall stands out if you're having problem with net connections to apps etc
Yes good point, thank you. I think i've run the ROM with same problems without any rules applied but I've disabled it fully now just to be sure. Much obliged.
If it persists, the proper way of troubleshooting would be to clean install the ROM only, no tweaks, Xposed, firewalls or anything, just the ROM and your apps you're having problems with
If that all works together fine, then add ONE new thing to the mix, test for a few days, rinse and repeat until you add something that causes the problem again
With testing for a few days between each new addition you're be 100% sure what is causing it once it starts again
Thank you! Yes that's the plan but I thought I'd ask first as there's a lot of waiting down that route. I did do it to a point during last build but only waited overnight after each phase. I think I'll start that.now. I can always restore this backup if the solution presents in the meantime.
Yea that's what I was thinking, backup this ROM, clean install, work out the issue, restore this ROM and fix it
Good luck
Thank you I'll report back if/when I work it out, for any other possible future readers.
I changed the base ROM & installed Xposed in a different way and rooted in a different way and tweaked Permissions to be more permissive and and and... I've read rovo89's farewell so I won't say "It's xprivacy" but it's definitely how xposed & xprivacy interact, whether by flashable zip or systemless magisk. It'll work fine for a good while but then starts corrupting everything internet connecting. Removing it removes the problem & restores the app functionality.
Sadly it's the same even if you restrict nothing in xprivacy & just leave it installed & switched on. I've had to remove it. Considering trying to go back to MM as I know it worked on my previous phone.
I'm an experienced programmer, but a complete novice when it comes to android development. I also hope I'm posting this in the right place...
I have recently bought a OnePlus Nord (AC2003) which I'm *fairly* happy with, and a Samsung Galaxy Watch3. I'm having an issue with it in that the watch and phone will fairly randomly disconnect from each other, even when they're in close proximity to each other. I have read extensively about the possible issue*, and reset both the watch and the phone, and cleared the bluetooth cache, which appears to have made a difference, at least in the long term. The disconnection now only happens about once a day, rather than the every half an hour that was happening originally.
* One school of thought is that the watch is absolutely at fault, as the users have no problems with other bluetooth devices. Another school say it's definitely the phone, as they have no issues when they use the watch with a different handset. Go figure.
My programmer's hunch (which I've learned to trust over the years) is that a service or app in the phone is stopping and starting, and I'd like to get a log of when the phone is stopping and starting apps and services. I've enabled developer mode, and I can see the option for 'Basic Log' and 'Power Consumption Exception' log in the OnePlus logKit.
My question is - Has anyone looked at the logs for this sort of data before, and is there anything in particular I should be looking out for, with particular attention to when the battery management on the phone decides that a process can be stopped or hibernated.
(Obviously, if anyone has anything to share about any Eureka moments regarding smart watch disconnects with this phone, I'd love to hear those too )