Prevent the standard Task Killer from unloading the applications you need. All devices. | Your favorite apps will always remain in the device’s memory.
Yes, that's been waiting for a few minutes, the gallery rose to priority 2, but had escaped backgammon with -17 to 11 ...
I wait a minute and backgammon on the timer again to -17
may be all the same to make a timer rather than launch the application.? I have a strong impression that the reliability is obtained, including the example of your timer again in a minute.
I wait a minute and backgammon on the timer again to -17
may be all the same to make a timer rather than launch the application.? I have a strong impression that the reliability is obtained, including the example of your timer again in a minute.
Galamar @ 24.10.2012, 16:43
RubberBigPepper, and you can add logging of all actions of the program (at least temporarily)? Black screen depressing. So at least you can understand the reasons behind the program is "stuck"
Can do
Black_BG @ 24.10.2012, 17:01
does not want the program to raise the priority to 2 for application launch ... Only the timer ...
it is necessary to leave only a timer, but to do more often (every 20-30 seconds for example), and checking the change the OOM.
And when the screen can be less often, while the often-for example.
RubberBigPepper @ 24.10.2012, 15:04
should be left only for timer
I also speak about it.
Here, read think, we can enjoy)
Prohibition standard Task Killer'u unload the applications you need. All devices. (Post # 16488515)
0.4 beta.
Added response to switch-off the screen.
When the screen timeout 30seconds, 60 switched off.
At the same time the lowest priority process is made to the least ate percent
AutoOOMmanager.apk(36.62 Kb)
Added response to switch-off the screen.
When the screen timeout 30seconds, 60 switched off.
At the same time the lowest priority process is made to the least ate percent
AutoOOMmanager.apk(36.62 Kb)I come to the conclusion that to realize a normal distribution of memory levels can be only with a timer
I understand that the 0.4 beta Now does not track the launch of applications, and works purely on a timer? and there is no delay before recording -17?
Post has been editedBlack_BG - 24.10.12, 16:11
I understand that the 0.4 beta Now does not track the launch of applications, and works purely on a timer? and there is no delay before recording -17?
Post has been editedBlack_BG - 24.10.12, 16:11
Black_BG @ 24.10.2012, 19:07
I understand that the 0.4 beta Now does not track the launch of applications, and works purely on a timer? and there is no delay before recording -17?
monitors and if it finds a shift, 2 seconds delay
and also the timer goes to 30 or 60sekund and there is no delay
you to test include uvedomlyalku at SU and immediately see
I see in the special prog. I forget it, hanging in a hat.
By the way does not work for off / on the screen ...
and how often checks the applications? times per second as it was?
By the way does not work for off / on the screen ...
and how often checks the applications? times per second as it was?
Black_BG @ 24.10.2012, 20:00
and how often checks the applications? times per second as it was?
yes, once per second.
Posted on 24.10.2012, 17:02:
Black_BG @ 24.10.2012, 20:00
By the way does not work for off / on the screen ...
I have a screen-like turn immediately notice comes from SU As conceived
I do not understand why such a cheat ... Can you explain your logic? Let's do a simple timer
Application verification is unstable fulfills, in principle, still unstable at zapihivanie priority such as 3 ...
Timer reliable. it will also eat at the same frequency, but the timer is all done as needed and where needed.
I have already given an example of how I think should be done.
Posted on 24.10.2012, 17:04:
let him come, but the priority does not change ... or change back and forth immediately changes that I do not have time to see what the priority of -17 ...
Post has been editedBlack_BG - 24.10.12, 17:05
Application verification is unstable fulfills, in principle, still unstable at zapihivanie priority such as 3 ...
Timer reliable. it will also eat at the same frequency, but the timer is all done as needed and where needed.
I have already given an example of how I think should be done.
Posted on 24.10.2012, 17:04:
RubberBigPepper @ 24.10.2012, 18:02
SU As conceived
let him come, but the priority does not change ... or change back and forth immediately changes that I do not have time to see what the priority of -17 ...
Post has been editedBlack_BG - 24.10.12, 17:05
Version 0.5
Added Entry logkat while reading the list of applications.
Those who did not work, see.
Removed check running applications.
AutoOOMmanager.apk(36.83 Kb)
Added Entry logkat while reading the list of applications.
Those who did not work, see.
Removed check running applications.
AutoOOMmanager.apk(36.83 Kb)I'm not on your nelly not claim to you. I say, just in case.
just think that in a dispute born truth.
I for easy solutions.
why I insist that it is necessary to make a timer
check ann is once per second + priority change, theoretically mb after each inspection. it is 2 steps.
check ann does not work with assignment -17 and worse with 2 and 3 priority ....
but the timer is running much more clearly.
Plus, this one action - write to a file, to two - checking and recording.
so I tend to the timer.
ann worth checking, but rarely, to change the timer interval, when you sit for a long time in one APP.
pliz take a look to my algorithm.
ps
once again I want to tell you frankly - thank you!
just think that in a dispute born truth.
I for easy solutions.
why I insist that it is necessary to make a timer
check ann is once per second + priority change, theoretically mb after each inspection. it is 2 steps.
check ann does not work with assignment -17 and worse with 2 and 3 priority ....
but the timer is running much more clearly.
Plus, this one action - write to a file, to two - checking and recording.
so I tend to the timer.
ann worth checking, but rarely, to change the timer interval, when you sit for a long time in one APP.
pliz take a look to my algorithm.
ps
once again I want to tell you frankly - thank you!
RubberBigPepper, in the log I can not see anything useful
logcat
10-24 17: 42: 02.032 I / ActivityManager (909): Starting activity: Intent {act = android.intent.action.MAIN flg = 0x10100000 cmp = rubberbigpepper.AutoOOMmanager / .MainActivity} from pid 909
10-24 17: 42: 02.063 V / HtcAppUsageStats (909): (launch app, package): (AutoOOMmanager, rubberbigpepper.AutoOOMmanager)
10-24 17: 42: 02.153 W / WindowManager (909): HistoryRecord {40d0c570 rubberbigpepper.AutoOOMmanager / .MainActivity} failed creating starting window
10-24 17: 42: 02.533 I / ActivityManager (909): Start proc rubberbigpepper.AutoOOMmanager for activity rubberbigpepper.AutoOOMmanager / .MainActivity: pid = 10959 uid = 10301 gids = {1015}
10-24 17: 42: 05.045 I / ActivityManager (909): Displayed rubberbigpepper.AutoOOMmanager / .MainActivity: + 2s876ms
10-24 17: 42: 06.427 D / InputDispatcher (909): Dispatch MotionEvent [action = 0] ToCurrentInputTarget: 40da9130 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 06.497 D / InputDispatcher (909): Dispatch MotionEvent [action = 1] ToCurrentInputTarget: 40da9130 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 14.144 I / ActivityManager (909): Starting activity: Intent {act = android.intent.action.MAIN flg = 0x10100000 cmp = rubberbigpepper.AutoOOMmanager / .MainActivity} from pid 909
10-24 17: 42: 14.154 V / HtcAppUsageStats (909): (launch app, package): (AutoOOMmanager, rubberbigpepper.AutoOOMmanager)
10-24 17: 42: 14.264 W / WindowManager (909): HistoryRecord {4097fc70 rubberbigpepper.AutoOOMmanager / .MainActivity} failed creating starting window
10-24 17: 42: 14.945 D / NotificationService (909): cancelNotification, ACTION_NOTIFICATION_REMOVE, pkg = rubberbigpepper.AutoOOMmanager, id = 2130968576
10-24 17: 42: 15.345 I / ActivityManager (909): Displayed rubberbigpepper.AutoOOMmanager / .MainActivity: + 1s2ms
10-24 17: 42: 16.176 D / InputDispatcher (909): Dispatch MotionEvent [action = 0] ToCurrentInputTarget: 40a4ec70 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 16.266 D / InputDispatcher (909): Dispatch MotionEvent [action = 1] ToCurrentInputTarget: 40a4ec70 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 18.949 V / HtcAppUsageStats (909): (launch app, package): (AutoOOMmanager, rubberbigpepper.AutoOOMmanager)
10-24 17: 42: 18.949 I / ActivityManager (909): Starting activity: Intent {act = android.intent.action.MAIN flg = 0x10100000 cmp = rubberbigpepper.AutoOOMmanager / .MainActivity} from pid 909
10-24 17: 42: 18.959 W / WindowManager (909): HistoryRecord {40a9f330 rubberbigpepper.AutoOOMmanager / .MainActivity} failed creating starting window
10-24 17: 42: 19.439 D / KEEPSCREEN IS (6907) [75] rubberbigpepper.AutoOOMmanager
10-24 17: 42: 20.080 I / ActivityManager (909): Displayed rubberbigpepper.AutoOOMmanager / .MainActivity: + 1s112ms
10-24 17: 42: 20.430 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 0] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 20.651 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 1] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 21.131 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 0] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 21.351 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 1] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 21.461 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 0] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 21.662 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 1] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 22.092 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 4, action = 0] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 22.332 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 4, action = 1] ToCurrentInputTarget: 40c00450 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 23.153 D / InputDispatcher (909): Dispatch MotionEvent [action = 0] ToCurrentInputTarget: 40c00450 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 23.223 D / InputDispatcher (909): Dispatch MotionEvent [action = 1] ToCurrentInputTarget: 40c00450 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 24.194 D / InputDispatcher (909): Dispatch MotionEvent [action = 0] ToCurrentInputTarget: 40c00450 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 24.234 D / InputDispatcher (909): Dispatch MotionEvent [action = 1] ToCurrentInputTarget: 40c00450 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 02.063 V / HtcAppUsageStats (909): (launch app, package): (AutoOOMmanager, rubberbigpepper.AutoOOMmanager)
10-24 17: 42: 02.153 W / WindowManager (909): HistoryRecord {40d0c570 rubberbigpepper.AutoOOMmanager / .MainActivity} failed creating starting window
10-24 17: 42: 02.533 I / ActivityManager (909): Start proc rubberbigpepper.AutoOOMmanager for activity rubberbigpepper.AutoOOMmanager / .MainActivity: pid = 10959 uid = 10301 gids = {1015}
10-24 17: 42: 05.045 I / ActivityManager (909): Displayed rubberbigpepper.AutoOOMmanager / .MainActivity: + 2s876ms
10-24 17: 42: 06.427 D / InputDispatcher (909): Dispatch MotionEvent [action = 0] ToCurrentInputTarget: 40da9130 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 06.497 D / InputDispatcher (909): Dispatch MotionEvent [action = 1] ToCurrentInputTarget: 40da9130 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 14.144 I / ActivityManager (909): Starting activity: Intent {act = android.intent.action.MAIN flg = 0x10100000 cmp = rubberbigpepper.AutoOOMmanager / .MainActivity} from pid 909
10-24 17: 42: 14.154 V / HtcAppUsageStats (909): (launch app, package): (AutoOOMmanager, rubberbigpepper.AutoOOMmanager)
10-24 17: 42: 14.264 W / WindowManager (909): HistoryRecord {4097fc70 rubberbigpepper.AutoOOMmanager / .MainActivity} failed creating starting window
10-24 17: 42: 14.945 D / NotificationService (909): cancelNotification, ACTION_NOTIFICATION_REMOVE, pkg = rubberbigpepper.AutoOOMmanager, id = 2130968576
10-24 17: 42: 15.345 I / ActivityManager (909): Displayed rubberbigpepper.AutoOOMmanager / .MainActivity: + 1s2ms
10-24 17: 42: 16.176 D / InputDispatcher (909): Dispatch MotionEvent [action = 0] ToCurrentInputTarget: 40a4ec70 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 16.266 D / InputDispatcher (909): Dispatch MotionEvent [action = 1] ToCurrentInputTarget: 40a4ec70 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 18.949 V / HtcAppUsageStats (909): (launch app, package): (AutoOOMmanager, rubberbigpepper.AutoOOMmanager)
10-24 17: 42: 18.949 I / ActivityManager (909): Starting activity: Intent {act = android.intent.action.MAIN flg = 0x10100000 cmp = rubberbigpepper.AutoOOMmanager / .MainActivity} from pid 909
10-24 17: 42: 18.959 W / WindowManager (909): HistoryRecord {40a9f330 rubberbigpepper.AutoOOMmanager / .MainActivity} failed creating starting window
10-24 17: 42: 19.439 D / KEEPSCREEN IS (6907) [75] rubberbigpepper.AutoOOMmanager
10-24 17: 42: 20.080 I / ActivityManager (909): Displayed rubberbigpepper.AutoOOMmanager / .MainActivity: + 1s112ms
10-24 17: 42: 20.430 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 0] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 20.651 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 1] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 21.131 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 0] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 21.351 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 1] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 21.461 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 0] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 21.662 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 82, action = 1] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 22.092 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 4, action = 0] ToCurrentInputTarget: 40a88250 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 22.332 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 4, action = 1] ToCurrentInputTarget: 40c00450 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 23.153 D / InputDispatcher (909): Dispatch MotionEvent [action = 0] ToCurrentInputTarget: 40c00450 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 23.223 D / InputDispatcher (909): Dispatch MotionEvent [action = 1] ToCurrentInputTarget: 40c00450 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 24.194 D / InputDispatcher (909): Dispatch MotionEvent [action = 0] ToCurrentInputTarget: 40c00450 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 17: 42: 24.234 D / InputDispatcher (909): Dispatch MotionEvent [action = 1] ToCurrentInputTarget: 40c00450 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
RubberBigPepper, Here screen. Later if I needed to make a video, although there is nothing to shoot something.
 |
Galamar,
hmm, if gives the dialogue a second load, the logkate must be lines.
Try it here
AutoOOMmanager.apk(36.88 Kb)
hmm, if gives the dialogue a second load, the logkate must be lines.
Try it here
AutoOOMmanager.apk(36.88 Kb)RubberBigPepper,
10-24 18: 52: 48.666 I / ActivityManager (909): Starting activity: Intent {act = android.intent.action.MAIN cat = [android.intent.category.LAUNCHER] flg = 0x10200000 cmp = rubberbigpepper.AutoOOMmanager /. MainActivity bnds = [0,70] [96,198]} from pid 14535
10-24 18: 52: 48.706 V / HtcAppUsageStats (909): (launch app, package): (AutoOOMmanager, rubberbigpepper.AutoOOMmanager)
10-24 18: 52: 48.946 W / WindowManager (909): HistoryRecord {40bb6878 rubberbigpepper.AutoOOMmanager / .MainActivity} failed creating starting window
10-24 18: 52: 49.186 I / ActivityManager (909): Start proc rubberbigpepper.AutoOOMmanager for activity rubberbigpepper.AutoOOMmanager / .MainActivity: pid = 16611 uid = 10301 gids = {1015}
10-24 18: 52: 49.737 E / AutoOOM (16611): onCreate started
10-24 18: 52: 50.297 E / AutoOOM (16611): before new ReadAppsTask () execute ().
10-24 18: 52: 50.367 E / AutoOOM (16611): start onPreExecute ()
10-24 18: 52: 50.637 E / AutoOOM (16611): end onPreExecute ()
10-24 18: 52: 50.637 E / AutoOOM (16611): doInBackground ()
10-24 18: 52: 50.678 E / AutoOOM (16611): onCreate end
10-24 18: 52: 50.738 E / AutoOOM (16611): Readed 0 app from settings
10-24 18: 52: 51.388 I / ActivityManager (909): Displayed rubberbigpepper.AutoOOMmanager / .MainActivity: + 2s518ms
10-24 18: 52: 51.789 E / AutoOOM (16611): Readed 0 installed packages from system
10-24 18: 52: 51.789 E / AutoOOM (16611): end doInBackground ()
10-24 18: 52: 53.550 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 4, action = 0] ToCurrentInputTarget: 40d14648 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 18: 52: 53.730 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 4, action = 1] ToCurrentInputTarget: 4055b2c8 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 18: 52: 54.551 D / InputDispatcher (909): Dispatch MotionEvent [action = 0] ToCurrentInputTarget: 4055b2c8 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 18: 52: 54.631 D / InputDispatcher (909): Dispatch MotionEvent [action = 1] ToCurrentInputTarget: 4055b2c8 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 18: 52: 48.706 V / HtcAppUsageStats (909): (launch app, package): (AutoOOMmanager, rubberbigpepper.AutoOOMmanager)
10-24 18: 52: 48.946 W / WindowManager (909): HistoryRecord {40bb6878 rubberbigpepper.AutoOOMmanager / .MainActivity} failed creating starting window
10-24 18: 52: 49.186 I / ActivityManager (909): Start proc rubberbigpepper.AutoOOMmanager for activity rubberbigpepper.AutoOOMmanager / .MainActivity: pid = 16611 uid = 10301 gids = {1015}
10-24 18: 52: 49.737 E / AutoOOM (16611): onCreate started
10-24 18: 52: 50.297 E / AutoOOM (16611): before new ReadAppsTask () execute ().
10-24 18: 52: 50.367 E / AutoOOM (16611): start onPreExecute ()
10-24 18: 52: 50.637 E / AutoOOM (16611): end onPreExecute ()
10-24 18: 52: 50.637 E / AutoOOM (16611): doInBackground ()
10-24 18: 52: 50.678 E / AutoOOM (16611): onCreate end
10-24 18: 52: 50.738 E / AutoOOM (16611): Readed 0 app from settings
10-24 18: 52: 51.388 I / ActivityManager (909): Displayed rubberbigpepper.AutoOOMmanager / .MainActivity: + 2s518ms
10-24 18: 52: 51.789 E / AutoOOM (16611): Readed 0 installed packages from system
10-24 18: 52: 51.789 E / AutoOOM (16611): end doInBackground ()
10-24 18: 52: 53.550 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 4, action = 0] ToCurrentInputTarget: 40d14648 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 18: 52: 53.730 D / InputDispatcher (909): Dispatch KeyEvent [keyCode = 4, action = 1] ToCurrentInputTarget: 4055b2c8 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 18: 52: 54.551 D / InputDispatcher (909): Dispatch MotionEvent [action = 0] ToCurrentInputTarget: 4055b2c8 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
10-24 18: 52: 54.631 D / InputDispatcher (909): Dispatch MotionEvent [action = 1] ToCurrentInputTarget: 4055b2c8 rubberbigpepper.AutoOOMmanager / rubberbigpepper.AutoOOMmanager.MainActivity (server)
Galamar @ 24.10.2012, 22:26
0 Readed installed packages from system
that's the reason why your android that does not issue a list of all installed applications.
RubberBigPepper, and "pm list packages" can also parse, perhaps?
With other applications to load the list of applications do not have problems (LuckyPatcher, TB).
With other applications to load the list of applications do not have problems (LuckyPatcher, TB).
©savagemessiahzine.com2005-2020 All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement