Strange - I have same combination, and no issues at all with any of the *Matrix apps.....
It's not always the reported app which is the bad apple you know... it can be conflict with other apps.... i guess you already did a few battery pulls? indexes are being rebuilt when booting....
Watched BeBuzz (which AMS closed at least twice per hour) and IMX (which AMS closed at least once per hour) under Application Management. While TMX stayed put at 0% usage in the background, IMX would steal clock cycles upwards of 8% usage before settling down at 0% before ramping up again for no apparent reason. I can understand the occassional heartbeat (set to bi-weekly verifications), but to have AMS close the app repeatedly with the app not being used was a warning sign that simply I could not ignore. On the other hand, BeBuzz would continuously poll upwards of 5% usage. The very nature of the app dictates that it must continuously poll as a daemon. No problem. Even so, I have elected to remove BeBuzz for the time being as I happen to value 9900 battery life over custom LED notifications. Background apps which remain resident in memory and appear by all accounts to be behaving include ToDoMatrix (TMX), SocialScope, Epocrates Essentials, WhatsApp, BeWeather, BeReader, BuddyGuard Pro, AT&T Navigator and App World.
I wonder if it'll shut down Pandora, which remains resident in memory and uses about 25 sec/day CPU time whether you use it or not. I don't understand why this app is allowed to do this anyway. I see no reason for Pandora to be continuously loaded in RAM.
Agreed. And it certainly is a hassle having to close such offending apps through Engineering Screen Contents > Java VM Engineering Screens > Processes > [Select Process] > Kill Process. There must be an easier way to manage BB procs...
I'm loving the new resource monitor. It has been shutting down apps that have been running in the background -needlessly. I've seen battery life improve.
ARM works well. I have seen a small improvement in my battery life (about an hour extra, on average, per day)
You have the option of not monitoring a repeat offender app (IF you think the conflict lies elsewhere, or you simply need the app to be available when/if you need it)
That's the difficult part, determining conflicts vs. leaks. Though in my case ARM is certainly detecting non-conflicting anomalies, be they memory leaks, or race conditions. IMHO, it makes no sense to knowingly allow an offending app to bypass the auspices of ARM without first understanding the underlying trigger(s). That being said, REXwireless has placed additional monitors on my account in an effort to help understand what is happening with ARM and IMX.
Yes. Wi-Fi hot spots verified working (McDonalds & Starbucks), no microphone drops.
I understand that you can use public Wi-Fi hotspots (McDonalds, etc.), but can
you activate the mobile hotspot on your 9900 without a tethering plan on AT&T?
It was my understanding that only 7.1.0.267 allowed the mobile hotspot on AT&T.
Bebuzz every few hrs and if I leave tapatalk up all night I get the notification in the morning that it was shut down. I took bebuzz off the app shutdown list.
App Resource Monitor is for 7.1.0.xxx. I have it loaded on my 7.1.0.402.
The way to get it is down loading the 9900 7.1.0.253 version, extracting it.
Copying the App Resource Monitor alx file into the 402 root directory and the COD files java directory.
Then loading with the app loader program.
That is how I did it. Not suggesting that any one else do it though.
The way to get it is down loading the 9900 7.1.0.253 version, extracting it.
Copying the App Resource Monitor alx file into the 402 root directory and the COD files java directory.