Currently working on adding an auto reboot function for an app on rooted devices, which is causing us some issues.
The Auto-reboot is performed using a shell command under the SU identify and whilst this works for a few boots, the
app then crashes. We have tested 4 minute and hourly cycles and the issue usually occurs after 5-6 reboots, although there
isn't a consistent pattern of the number of reboots before it dies The issue is seen across different devices (Scroll Extreme and Archos
80 G9 Tablets PC's). Anyone got any experience of auto-reboots and could advise of a possible solution
Related
Hello everyone!
We have an fleet management app that runs continuous background updates every 1 minute using an Android service. We are seeing that sometimes the devices are failing to receive new GPS locations, and continuously report that they are at one location, when they are actually somewhere else. You can imagine this doesn't work well for a fleet management app. Rebooting the device seems to rectify the problem in the short-term. It also doesn't happen on every phone, even if they are the same model with same fw.
Any ideas? Thanks!
Hi, I'm running CM7.2 nightlies on an LG P999 (Canadian version of the G2x). Over the past few weeks, I've had issues where the screen will dim as it approaches the display timeout, but never turn off completely. This is intermittent, and I have yet to notice a consistent pattern. I've been searching to try to find a cause but with no luck so far. I am familiar with using BetterBatteryStats and thelike to track down issues with wakelocks and not going to sleep, but i don't know what to use/look for in this instance (ie how to identify apps that might block the screen from shutting down). Any suggestions?
Tv
tvisforme said:
Hi, I'm running CM7.2 nightlies on an LG P999 (Canadian version of the G2x). Over the past few weeks, I've had issues where the screen will dim as it approaches the display timeout, but never turn off completely. This is intermittent, and I have yet to notice a consistent pattern. I've been searching to try to find a cause but with no luck so far. I am familiar with using BetterBatteryStats and thelike to track down issues with wakelocks and not going to sleep, but i don't know what to use/look for in this instance (ie how to identify apps that might block the screen from shutting down). Any suggestions?
Tv
Click to expand...
Click to collapse
I would recommend using a logcat app to try and narrow down your problems, the recently featured | AIOlog - All in One Android Logger v0.3 is an excellent tool for this job, and if you would prefer to use an app for your phone try CatLog - Logcat Reader. Now as far as what to look for look for things in the logcat that refer to package's (I.E com.android.phone) and wake-locks or changes in power states. For example if you see that a package when in use is causing a wake-lock or keeps changing the power state (It may for example be preventing the display from completely shutting off because it thinks your still using the app and thus should keep the screen on), you know that may be the culprit. If you can narrow down a list of suspected apps carefully disable or uninstall them one at a time (Be very careful if it's a system app, make a backup first), and see if this fixes your problem. Let me know if you need any help troubleshooting !
My phone is getting really hot (like, uncomfortable to have in my pocket).
I went to dev options, and activated the overlay cpu usage to check which process were eating up my CPU.
Top of the list 99% of the time is system_server.
Other symptoms:
– I can't open a terminal session (terminal emulator starts but no prompt, I can't kill it either)
– installing an app takes ages (both the downloading and the installing)
– the wifi symbol in the status bar has both arrows (upload and download) displayed all the time
– some network related activities seems to be very slow
com.google.android.tts and android.process.acore make also regular visit to the top 3 processes, but they are far from system_server.
I have CyanogenMod 11 M3 on a google edition of the S4, encryption is on. I have around 2GB free on my internal storage and 20GB on the external SD.
Any further troubleshooting ideas?
Its an app. Probably one with spyware to be more specific. Either way it's constantly sending or receiving data. Have you installed anything around the time this started happening?
I will deinstall progressively the latest apps I installed and see if it helps.
What I noticed too:
– re flashing CM 11 M3, cleaning cache and davlik cache helps. But just for a short while. After a couple of hours it starts again.
– the network activity is constant but pretty low. Below 10kB/s all the time, regularly below 1kB/s
– I can't uninstall anything right now, every app I uninstall says “uninstalling” forever.
– turning airplane mode on makes it a bit better: phone is still hot, but not uncomfortably so.
How does an app hide its process like this without root access? I didn't thought it was possible in Android. I can only see system_server...
i have the same problem with you
this problems starts couple days ago, and until now i still curious of what happen to my phone
i used xperia z1 now,
does anyone can help to solved this problem
Hello all, new here, hope this is the right place for this post...
I have looked everywhere and can't seem to find anything relevant, so maybe someone here may have some insight. To start, it is (Kingo) rooted stock ROM android 4.1.2, build M36UP61, kernel 3.4.0, just to avoid confusion... Here's the issues numbered so I can correlate answers for each:
1) WiFi will occasionally drop, but the issue is that after (I assume) 5 retries, it leaves the AP as "disabled", and I want it to never do that, like my kyocera hydro, which relentlessly retries until it gets a connection to a known AP. Essentially, to never give up on a known AP for any reason, even if having to connect at least once first. I can find nothing in build.prop or sysctl that seems to relate to this behavior, unless I missed something. Additionally, WiFi will drop despite >-72dB signal unless I am actually watching the WiFi AP settings screen for some reason. I have made minor tweaks to build.prop, however this behavior was occurring prior to rooting.
2) I am getting what appears to be OOM-related FCs (no toast ANRs, just a halt back to launcher), yet with what should be enough RAM and spare CPU at the time. This behavior also prior to rooting, and have tweaked some improvement, but it is apparently not enough. I have not messed around too much with DavlikVM settings, as it still is as intimidating as sysctl for me as a newbie at Linux. I have tried to logcat, but can't get a dump at all, it just doesn't seem to log in time. Am I looking at the wrong log?
3) Touch screen locks, and takes all hardware function with it, even just on the home screen. Hardware power and volume don't respond and touchscreen coordinates are locked in place (I have show touches enabled) with no change in anything else; game/app keeps running smoothly, but is convinced that I have frozen holding (or not holding) my touches in place. Recovers in anywhere between 15 seconds to never, requiring me to pull the battery. Persistent after factory reset (did prior to rooting), occurs only when cfq(?) governor is topped at 1001MHz regardless of CPU load. Occasionally multi touch (max 2) fails intermittently, or averages between them (hold both ends and it shows one touch in the middle).
Just to add, any way to kill autocorrect's tendency to put the wrong word in place of a correctly-spelled one in its dictionary? (Changed dictionary to functionary for no reason, both in database). Also, smaller functions drop out, like WiFi icon stops responding, autocorrect suggestions disappear at random, etc.
I have a phone with Nougat 7.1.1, but also older phones (eg with Lollipop and Gingerbread): the common trouble on all phones is that I have an annoying issue when connected using mobile data:
all the apps which relies on push notifications (eg whatsapp, facebook messenger, Hangouts and Gmail) doesn’t receive push notifications in realtime or in a acceptable time: I mean that I receive notifications - delayed - also after 30 minutes or i receive them only when I turn on the screen. On all these phones I use a SIM card of same carrier.
When I am connected using Wifi (so without mobile data) I receive notifications in realtime (in about 1 or 2 seconds).
What I checked is that all these apps have background data always enabled and I don’t use any battery saver app.
Is like if the mobile data, after some minutes of inactivity, falls in a sort of idle status, and needs to be kept awake: in facts, if I use a method to run a ping command every X minutes, the notifications are received in an acceptable time (in few seconds).
Not all of my phones are rooted: on the phones which are rooted I solved by installing the app called “Push Notification Fixer”; I am aware of the fact that there’s also available the “NO ROOT” version of such app, but doesn’t works for me.
I said “if I use a method to run a ping command every X minutes, the notifications are received in an acceptable time (in few seconds)”: I noticed that mobile data of my carrier falls in a “sleep” state after about 7 minutes: so I setup the following command in a Terminal Emulator:
Code:
ping -i 420 www.google.com
420 is the time in seconds, which is equal to 7 minutes.
The ping method, however, cause other issues: it cause a lot of wakeups (as I can see from Better Battery Stats) and sometimes I notice that it hangs: I excluded the Terminal Emulator from battery optimization and from data saver (and I enabled the option “Wake Lock” (to keeps phone from sleeping while running a command) , but this doesn’t help: I also excluded Google Play Services from battery optimization/Doze and I ensured that background data is not restricted
Obviously I’ve also tried to wipe applications cache and uninstall and reinstall applications: however, since with Wifi I don’t have any trouble, seems not a fault of the phone or apps, since I faced this issue on all phones and different versions of Android: always occurs with mobile data but not with Wifi.
Is sure the fact that when I am on mobile data the phone needs to be awake to receive the notifications. I repeat that when I am connected using wifi, the notifications are instant.
I don’t think that Doze is the culprit: as I’ve said I excluded apps and Google Services from battery optimization/Doze.
I also disabled the data saver option. I have notifications delay issue only when connected with mobile data: furthermore the signal strenght of my carrier (4G) is good.
What can I do (a robust and reliable method) to keep the mobile data connection always active?
I also tried by using “Connection Stabilizer” from the Play Store: this app, also have a method to run a ping command every X seconds or minutes, but also this app suffer from the same issue: after a while the ping command no longer works.
I heard of the fact that this issue could be related to fast dormancy: unfortunately, since the phone is not rooted, I can't disable fast dormancy.
I installed this app: https://play.google.com/store/apps/details?id=eu.thedarken.wl (Wake Lock - PowerManager): This app implemented a Partial Wakelock: in this way the notifications arrives in 1 - 2 seconds, but the downside (due the Partial wake Lock) is a battery drain.
No one else, here, faced the issue of delayed notifications when connected with mobile data?
As I've said, with Wifi I don't have any issue with notifications; furthermore I am not "forced" to rely on wakelocks.
Kind regards.
were you able to fix this ? i am having the exact same problem on my note 8 running pie with no solution so far