Related
I see that when a task killer stops a program (cityid, stocks,etc) I can look right back in there and see it running again and in a minute the page is full again of the same apps that I just killed. Even with autokill on they start while the screen is off. I want to know if anyone has figured out what file or service keeps starting these and if there is an edit to it to tell them to quit it ? I am not comfortable with a device that I do not have control of stuff that starts and goes online by itself. Thanks.
madman34 said:
I see that when a task killer stops a program (cityid, stocks,etc) I can look right back in there and see it running again and in a minute the page is full again of the same apps that I just killed. Even with autokill on they start while the screen is off. I want to know if anyone has figured out what file or service keeps starting these and if there is an edit to it to tell them to quit it ? I am not comfortable with a device that I do not have control of stuff that starts and goes online by itself. Thanks.
Click to expand...
Click to collapse
If you're not comfortable with a device you do not have full control of, looks like rooting is for you
Seriously though, rooting your device is the ONLY way to remove City ID, Stocks, etc. from your device. HOWEVER.
You should probably break yourself of the task killer habit. Lifehacker explains it all here: http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them.
In a nutshell, Android is actually really good at preserving memory, and killing apps that will keep popping up drains battery faster. The reason they keep popping up is Android is trying to predict what you're going to use next based on what you just did (or something like that), so potentially anything you have installed that is there on startup will hit that list.
I tried using Watchdog as the article said, but honestly I found in the end I just wanted more control. unrevoked 3.21 and several ROM tries later I'm happy with where I'm at
EDIT: I see by your sig that you have rooted your Dinc.. therefore, it's a very simple process if you want to get rid of the app entirely. If you want to leave it installed, you're not going to find a solution to the constant opening - Android is what Android is.
Most of the apps you see in the task list are not active. They're just loaded in memory so they can launch faster when you need them.
Like the previous poster pointed out, task killers are counter productive. You just get a continuous cycle with the app launching and being killed. Launching again and being killed again. And on and on.
Best just to leave android alone to do what it was designed to do.
If you still feel the need to be more in control use app autostarts. It allows you to block the initial app launch and block based on events.
________________________________
Unrevoked forever
SkyRaider Sense 3.3.2
KiNgxKernel BFS (#5)
Radio 2.15.00.07.28
Mostly what I want to do is,,,,
,,,To stop applications that come on by themselves and log in even when you set in their settings to not do it, like Skype. I do use Skype to do a calll with a bunch of friends from school, but I want to start it when I want to use it, I am all the time having skype calls come in when I have not even launched the app. I figure that if it is listening for a call then it is useing power needlessly. I do not want to have to log out every time I want it to stop, I just want to close it and it behave and stop useing power. Many apps do that and I think it is a major reason for low battery life. My battery will not hold up a full shift at work, but if I kill the GPS and the 3G the thing has been up for 22 hours and is still at 66% and I have talked for over 2 hours today on the phone, so I think that if more control is gained over app behaviour then we can be happier with our batteries ;-)
madman34 said:
...but if I kill the GPS and the 3G the thing has been up for 22 hours and is still at 66% and I have talked for over 2 hours today on the phone,
Click to expand...
Click to collapse
You hit the nail on the head there. It's not the apps killing your battery, it's the 3g and gps.
I leave my wifi on all the time but have it set to disconnect if the phone is idle for 15 min. Bluetooth, gps, and 3g are always turned off except when I need them.
________________________________
Unrevoked forever
SkyRaider Sense 3.3.2
KiNgxKernel BFS (#5)
Radio 2.15.00.07.28
So I recently received my SE LiveView, and like a true geek I did tons of reading during the 5 days I waited for it to get here. As soon as I received it, the first thing I did was charge it fully and then update the firmware via SEUS.
Before I go into what I did to fix it, i'll list my hardware/software:
Phone: Motorola Droid on Verizon Network running CM 6.2.2
Software used for fix: Tasker
So after extensive reading and testing, I've determined that the #1 main cause of disconnect is low memory on the phone. If I have a lot of apps running in the background on the phone, the chance of my LV disconnecting increases greatly. As a matter of fact, I don't get any disconnects sans moving out of range of the LV that don't fall under the "low memory" category.
Testing Done: LV connect/disconnect testing using the LV app; opening the app, connecting via the LV; disconnecting the LV, closing the app, then trying to connect via the LV; having the LV connected, then opening up and using different apps until the LV disconnects, then trying to reconnect via the LV.
Results: I can always reconnect via the LV if the LV app is open, or hasn't been closed by the OS to free up memory. If the LV app has been closed via Android to free memory, the LV disconnects and can't be reconnected until the LV app is reopened. This means that the closure of the LV app is causing the disconnect, and a reconnection isn't possible until the LV app is back in a running state on Android.
Fix: Since Sony hasn't programmed a high priority "ongoing" state into the app (like tasker), it's prone to close if Android gets low on memory and it hasn't been opened via the user in awhile. So knowing the results of the testing, I came up with a work around. Using tasker to track when the LV is connected or disconnected, I can keep the LV app in the memory.
I created the following in tasker:
Condition = State >> Bluetooth Connected >> LiveView
Task = Misc >> Say >> "Liive view connected" (I put two i's in live because with just one the TTS says live i.e. "live and let live", not live i.e. "live from NY it's saturday night!")
Exit Task = Misc >> Say >> "Liive view disconnected"
App >> Load App >> LiveView
In doing this, whenever my LV connects to the phone, my phone announces it. this isn't too important, but it's good notification. The real bread and butter here is that when the LV disconnects from my phone, not only does the phone announce it, but it also automatically opens up the LV app into the forefront of the memory, so I can always reconnect via the LV. Also, until I get back on my phone to do something, the LV app will be "opened" and on screen (of course not actually on screen, since the screen is off) and have the highest priority, so Android won't automatically close it when it needs memory, since it's the highest priority app.
I'm going to add another task to Tasker, that whenever I turn off my screen, it loads the LV app too, so the only time I will ever have to worry about the LV disconnecting, is when i'm using the phone extensively and run out of memory.
Questions? Comments? Soliloquies?
I just ordered mine im excited and will for sure try this
Sent from my SGH-T959 using XDA App
Have set this up, will see what happens!
I'm sorry to report that it's no good for me.
In fact, it nearly rendered my phone unusable.
I had managed to stay connected since I wrote my last post, and I was quite pleased about it. Out of the blue my phone shouted "LiveView Disconnected".
Fair enough, I thought, so I went to check the phone, and sure enough the liveview app had loaded and was waiting to connect, so I hit the button on the liveview, which was followed about 2 seconds later by a "Liveview Connected" message and everything sprung to life.
However, after another couple of seconds I got another "LiveView Disconnected" and the app loaded again...and then straight after a "Liveview Connected" and then disconnected, and then connected...and it just carried on. Every time I went to try and turn off the tasker app the Liveview App popped up and I had to hide it again, but it was connecting and disconnecting so quickly I could barely turn off the tasker task...
Also it was annoying the hell out of everyone in the office as it bellowed it's information at me.
I hope others have more luck.
I think you were missing the point of Tasker opening up the LV app when it disconnects. It's for two reasons. The first is so you can properly reconnect. The second is so the app will stay in the forground (i.e. when you're not using the phone, the LV app stays open). You're going to get poor results if you take the LV app out of the foreground once it connects, as Android will close it completely if your system gets low on memory.
For this to work, the only time you should take the LV app out of the foreground is when you're actively using the phone. when it's not in your hands in use, keep the LV app open in the foreground and you won't get any disconnects.
I'm going on 3 days now without a disconnect.
PCTechNerd said:
I think you were missing the point of Tasker opening up the LV app when it disconnects. It's for two reasons. The first is so you can properly reconnect. The second is so the app will stay in the forground (i.e. when you're not using the phone, the LV app stays open). You're going to get poor results if you take the LV app out of the foreground once it connects, as Android will close it completely if your system gets low on memory.
For this to work, the only time you should take the LV app out of the foreground is when you're actively using the phone. when it's not in your hands in use, keep the LV app open in the foreground and you won't get any disconnects.
I'm going on 3 days now without a disconnect.
Click to expand...
Click to collapse
No, I completely understood the point of Tasker opening it to the foreground - I still got disconnects and once I did it would go up and down like a Yo-yo. I only tried to remove the LV app from the foreground to switch the Tasker app off as all I was getting was "LiveView Connected"..."LiveView Disconnected" every 3 seconds which was annoying and obviously the LiveView wasn't going to work at that point.
I completely get what you're trying to achieve here - but it did not work for me.
and what about battery life? mine shut down after only three hours without a huge use of it.... :-(
is it the same for U?
Mini_Jack said:
and what about battery life? mine shut down after only three hours without a huge use of it.... :-(
is it the same for U?
Click to expand...
Click to collapse
Have you updated the firmware of the LV device yet? Once the firmware is updated, somehow the battery greatly improves. I can go 2 full days of moderate use and still have a little less than half the battery left.
I have made the update when I received it, 10th February, so I hope it's the last firmware?Where can I see which version I have?
Did U use some plugins?
I try tp deinstall all of them to increase battery life.
without plugins work approximately 4 hours.... Better but not enough!
i just got mine today, will test tomorrow to see if this method works...
on a samsung galaxy s (vibrant)
this method seems to work for me on my samsung galaxy s (vibrant)
works like charm on my samsung galaxy tab
I have still one problem
Delay of showing the caller's name for 5 Sc
Is there a solution to this problem
I do this 3 steps:
-1º step
-Using Root Explorer, apply the Fivef Process (this seems to be needed only for non-Sense 2.3.x ROMs - looks like Sense in 2.2 builds allows LV to connect without confirmation).
fivef said:
I have found a solution for the repairing problems occurred on my desire HD with cyanogen 7 RC 1.
copy this file with e.g. root explorer to your SD card. edit it with e.g. astro as described below and then copy it back with root explorer. Restart your device.
/data/misc/bluetoothd/[device bt id]/linkkeys
your linkkeys file has to look something like that:
00:1D:BAD:8C:57 FF579860A41CD5A627D9D1596526715C 0 4
00:01:95:08:20:6F 809CC84592E6C1B06AB750170C365812 0 4
6C:23:B9:9B:4A:85 5AF503E766858EA7916D46C16DD31A34 0 4
The last entry is my liveview.
I just changed the last two numbers from I think
-1 0 to 0 4 so that it looks like the other entries.
The 0 is the linkkey type and the 4 the pin lenght.
But I don't know what the 0 stands for.
Have no time for futher research.
I just know that now the liveview automatically reconnects without an annoying pairing prompt.
Click to expand...
Click to collapse
-2º Step
- Find in the market & install the BEST Android program I've seen yet - "AutomateIt!"
- Create the following rule in this program:
-TRIGGER: BLUETOOTH DEVICE CONNECTED (LIVEVEW)
-ACTION: START APPLICATION (LIVEVIEW)
Using this incredible program, you can completely control every aspect of your phone's behavior - for example, automatically start PlayerPro and disable WiFi when wired headset is connected, automatically start WiFi when GPS detects that you have entered your home or office (!) and do million other cool things.
-3º Step
-Install liveviewcharm from market:
This application will maintain processes from "liveview app" always on, preventing android system to kill them.The LiveView app needs to put itself in the Notifications bar in order to keep from getting killed when it's in the background.
I think that guide will fix all liveview connection problems with all compatible devices and CM7/MIUI/STOCK.
thanks to Drakosha Old, fivef, ishii.
The date I noticed my battery issues coincides with when the update went live. I've tried tinkering as much as I can to disable wake lock permissions in all sorts of apps and using wake lock detector, but I can't really find the culprit.
I'm rooted, on 4.6.3. Is there a way to turn off the OTA check, or fool it into thinking I have 4.6.3.
Is it something else? I have a lot of apps, but the only thing wake lock can tell me about the sheer number of wakes is google play services, which has had it's permission to wake disabled but still is somehow the cause. That and system are about equal. Awake time is 91% since my last full charge and unplug. Not good.
Thanks for any help.
Just to maybe assist you in finding the culprit I'm on 4.6.3 with google apps but no root. I've not experienced any wake locks. Perhaps clearing Google's cache and data?
Sorry I meant I was on 4.6.1 still. Will clear data and see.
adam.nox said:
The date I noticed my battery issues coincides with when the update went live. I've tried tinkering as much as I can to disable wake lock permissions in all sorts of apps and using wake lock detector, but I can't really find the culprit.
I'm rooted, on 4.6.3. Is there a way to turn off the OTA check, or fool it into thinking I have 4.6.3.
Is it something else? I have a lot of apps, but the only thing wake lock can tell me about the sheer number of wakes is google play services, which has had it's permission to wake disabled but still is somehow the cause. That and system are about equal. Awake time is 91% since my last full charge and unplug. Not good.
Thanks for any help.
Click to expand...
Click to collapse
Probably one of those glitches that can be solved by a reboot. However, you can disable updates using hdxposed module for xposed if you want.
Done both of those things plus much more. Anyone else having this issue?
try taking a titanium backup of everything and then factory reset.. with everything backed up to your PC. then root and start restoring everything gradually.. start by social apps and call log and messages.. then your essential apps.. and see.. then add the rest of the apps bit by bit till you find the offending application or maybe something just got screwed will be fixed when the data clears..
just make sure there is nothing out of the norm in your essential apps, meaning they are all tried and tested by everyone.. facebook, whatsapp, keep, launcher.. that stuff. and also make sure in these apps to limit their ability to check every X minutes as they can really drain your battery.
I've disabled wakelock on anything that has reported to use it by wake lock detector that I don't absolutely need to have it. I've uninstalled any non-essential apps. I've done too much tinkering and have too much important app data to risk doing a reset when it may not work.
I need a way to actually get to the bottom of it first.
Why is google play services waking the phone 2000+ times per day? Wake lock detector says the phone has been awake 5 hours out of 10, but then the list of times for each app only adds up to 20 minutes. How do I find out what was keeping it awake the rest of the time?
Possibly some kind of location based frippery. Try removing location access from troublesome app. And turn off auto sync if it's on
Location services are completely disabled. Auto sync is off. Both have been since this started happening.
Used app quarantine to disable almost every app I put on here, and Fire OS is still 51%.
Possible culprits, though I'm not sure if I find it likely: Ultimate dynamic navbar, lightning chat, foscam viewer, google apps, xposed mods (have a few). greenify (that would be ironic), flixter, es file explorer, buildprop editor, calculator, jellybean keyboard, multi timer, skana battery alerts, nova launcher, power toggles, slacker radio, bank app, super user, terminal emulator, outlook, wakelock detector.
Get better battery stats from xda, it gives a better breakdown of wake locks.
Alright what should I look for in there?
Ok here is what I believe I have found out, using network log along with better battery stats.
The phone is waking up constantly due to netbios pings (I know not technically pings), from various computers on my network, mostly my main PC. I don't know why it's doing this. Could be one of many background processes. In my opinion, it shouldn't matter. The phone shouldn't be that stupid.
I was able to... I think, mitigate a lot of this by doing a few things.
The first is editing qcom's ini inside etc/wifi so that if it says offload, I put a 0, I assume it's offloading to the cpu, which causes it to wake for pointless crap. The second thing I did was re-enable optimized wifi. This is probably already on, on everyone else's phone. I turned it off because I was trying to figure out how to tether while connected to a vpn through the phone. Still can't get that to work. And I know how to, because I did it on my nexus prime, but something in the fire OS is f'ing that method up (iptable configs).
I'm considering seeking an app to turn off wifi when the phone sleeps, because better battery shows wifi on 100%, and even with the changes above, I was still responding to some netbios pings in the network (about 1/5th as many). I imagine most networks will have noise like this.
However, even after all this, fire OS is still the main battery draw. Better Battery doesn't account for all the wake time, not even by half.
For now I've put enough time into this.
Hi all,
I'm running several apps that should run all the time (AdGuard, Network Speed Meter) or for a long time (speed trap warner,...) but OxygenOS kills them after a certain period. Some of them restart automatically, some don't. Of course all of these apps are 'not battery optimized'. Is there any chance to prevent OxygenOS from killing them?
Are there custom ROMs that can overcome this problen?
I'm on the latest OxygenOS Pie Beta, but the behavior was similar on Android O...
Thanks a lot,
W
Did you try locking the app via recents menu?
Thank for the info, didn't know that.
Unfortunately it doesn't help, Adguard and the network monitor don't appear in recents. The speed trap warner automatically starts and stops when I'm in the car, i don't want to open recents manually every time.
Battery - Battery optimisation - Don't optimise
safwankatharudheen said:
Battery - Battery optimisation - Don't optimise
Click to expand...
Click to collapse
This is not changing anything,e ven with disable battery disabled, even with adaptative battery disabled.
I have the same problem. I have not found any solution whatsoever. This is really frustrating. I've made sure apps aren't optimized. Advanced optimization is disabled. Developer options background limit is at standard. I've pinned the apps in recent apps and it still happens. Apps get killed all the time.
For example,
1. I use Google Fit to start tracking a run. Within 10 minutes of tracking, the app is closed and workout not tracked. Its not even like i touched the phone and opened other apps during this.
2. I have VoIP account setup in the default dialer. Calls come through only 50% of the time cause the dialer is closed.
3. YouTube Music, constantly gets closed if i simply pause the music. Within 2 minutes, the app is closed.
4. Trying to transfer 15GB of files through Explorer app from phone to file server, never succeeds if i don't watch the app and keep the screen on.
5. Plex gets closed and therefore my photos don't auto backup with the phone is plugged in.
This is absolutely ridiculous! Why the hell a phone with 8GB of RAM is killing apps is beyond me!
Custom ROM on the same phone, like Lineage OS, no issues. Can have optimization on, battery manager on and all. In fact, battery life is better on custom when its not killing the apps! Seems to be the only solution until OOS can stop killing apps so aggressively.
M3drvr said:
I have the same problem. I have not found any solution whatsoever. This is really frustrating. I've made sure apps aren't optimized. Advanced optimization is disabled. Developer options background limit is at standard. I've pinned the apps in recent apps and it still happens. Apps get killed all the time.
For example,
1. I use Google Fit to start tracking a run. Within 10 minutes of tracking, the app is closed and workout not tracked. Its not even like i touched the phone and opened other apps during this.
2. I have VoIP account setup in the default dialer. Calls come through only 50% of the time cause the dialer is closed.
3. YouTube Music, constantly gets closed if i simply pause the music. Within 2 minutes, the app is closed.
4. Trying to transfer 15GB of files through Explorer app from phone to file server, never succeeds if i don't watch the app and keep the screen on.
5. Plex gets closed and therefore my photos don't auto backup with the phone is plugged in.
This is absolutely ridiculous! Why the hell a phone with 8GB of RAM is killing apps is beyond me!
Custom ROM on the same phone, like Lineage OS, no issues. Can have optimization on, battery manager on and all. In fact, battery life is better on custom when its not killing the apps! Seems to be the only solution until OOS can stop killing apps so aggressively.
Click to expand...
Click to collapse
My app is not killed when i lock it in the switch app menu
There's a whole website regarding that issue on several devices, maybe it helps: dontkillmyapp(dot)com/general#user-solution
Fairphone 3+ , /e/ , Magisk
A few days ago, my phone ran out of battery and died. No problem, I just let it recharge for a few minutes and turned it back on. However, it's not working properly anymore.
It generally runs a little slower than it has been. Sometimes it won't respond, or it will fall asleep within 10-20 seconds.
Some background processes don't seem to work all the time. At one point I didn't get Signal messages for several hours until I opened the app.
Some apps / subtasks in apps take extreeeemely long to load (several minutes for things that used to take seconds), and some apps / subtasks don't work.
Every few hours (or less) my phone will just randomly crash and restart.
Another weird thing is that several stock apps that I deinstalled with a debloating tool have reappeared? I can't open them though, so I don't think they're actually installed.
I tried uninstalling AdAway and ProtonVPN because at first I thought it might be some sort of networking timeout problem, but that didn't fix the issue, so I reinstalled them.
Take a long time:
Apps (/e/ app store), Nextcloud News when I open an article, a boardgame which I have since deinstalled, Spotify Lite
Crashes:
Files, Settings->Apps & app data, VLC
I'm uploading two logcat files. One from after an app (I think it was Files) crashed, another from shortly after when the phone crashed.
I don't have a ton of experience with android debugging, but this sounds like some sort of corruption in some part of the system?