What are my Android apps doing behind the scenes?

[Natey2]

My phone uptime is at 620 hours now, and is slower in refreshing the home screen compared to yesterday, which would indicate the situation is getting worse (I haven't added/updated any apps).

I see something (IMAP is e-mail related) opening a folder, and then unable to release a lock in the Java finally() block.
I hope the lock gets released eventually, or it will be bad :

02-26 04:54:38.218 D/IMAPPushThread( 8545): openFolderUntilSuccessful(), open succeeded, returning...
02-26 04:54:38.226 D/IMAPPushThread( 8545): ***** Finally block doesn't release lock, # of permits=1


Sent from my DROIDX using DroidForums App

 

[Natey2]

Security Alert:
I see something called ClipDataKeeper that logs the contents of an Android "Copy to Clipboard" into the logs in a DEBUG statement.

If you copy passwords, credit card or social security numbers, etc. They will end up in your logs.
Any application that has access to you logs can find them.

I have also noticed some email programs that log the username and email folder names and Subject lines in the logs.
I have not detected the password getting logged yet, which is a good thing.


Sent from my DROIDX using DroidForums App

 

[Natey2]

Security Alert:
I see something called ClipDataKeeper that logs the contents of an Android "Copy to Clipboard" into the logs in a DEBUG statement.

If you copy passwords, credit card or social security numbers, etc. They will end up in your logs.
Any application that has access to you logs can find them.

I have also noticed some email programs that log the username and email folder names and Subject lines in the logs.
I have not detected the password getting logged yet, which is a good thing.


Sent from my DROIDX using DroidForums App

ClipEventReceiver is also logging the clipboard content to the logfile at INFO level

Sent from my DROIDX using DroidForums App

 

[Natey2]

Is some app trying to access my preference settings without permission?

02-26 04:48:23.570 D/DeviceInfoSettings(22014): system version: sub string:Version.2.3.340.MB810.Verizon.en.US
02-26 04:48:23.640 W/ApplicationContext(22014): Attempt to read preferences file /data/data/com.android.settings/shared_prefs/com.android.settings_preferences.xml without permission


Sent from my DROIDX using DroidForums App

 

[Natey2]

Is some app trying to access my preference settings without permission?

02-26 04:48:23.570 D/DeviceInfoSettings(22014): system version: sub string:Version.2.3.340.MB810.Verizon.en.US
02-26 04:48:23.640 W/ApplicationContext(22014): Attempt to read preferences file /data/data/com.android.settings/shared_prefs/com.android.settings_preferences.xml without permission

I guess the more important question here is, if I was rooted, would that dubious app have been able to access my Settings Preferences without any indication / my knowledge?

Sent from my DROIDX using DroidForums App

 

[AngryHatter]

Dude - obsessing much?
Out of 20 replies - 15 are you?

Enjoy a book, go see a show.

 

[Natey2]

Many alerts like this lately:

02-27 20:50:23.452 I/ActivityManager(21930): Low Memory: No more background processes

Does this mean my phone will not multitask any more?

Then I see multiple processes die (and restart), like this example:

ActivityManager(21930): Process com.android.settings (pid 21619) has died.
02-27 20:50:48.686 I/WindowManager(21930): WIN DEATH: Window{463003e0 com.android.settings/com.android.settings.Settings paused=false}
02-27 20:50:48.710 I/UsageStats(21930): Unexpected resume of com.fede.launcher while already resumed in com.android.settings

And

02-27 20:51:15.350 I/ActivityManager(21930): Process com.android.calendar (pid 18339) has died.
02-27 20:51:15.358 W/ActivityManager(21930): Scheduling restart of crashed service com.android.providers.calendar/.CalendarWidgetProvider$WidgetService in 19799ms


Sent from my DROIDX using DroidForums App

 

[Natey2]

Dude - obsessing much?
Out of 20 replies - 15 are you?

Enjoy a book, go see a show.

Good software engineers are meticulous to the point of obsession.

If you are a software engineer, maybe you can tell us how much memory is leaked by the unclosed cursors?

I see over 1K reads/views on this topic.

Sent from my DROIDX using DroidForums App

 

[Natey2]

My conclusion:

Android 2.2.1 with Motorola blur processes (and possibly some 3rd-party apps from the Android Market) is leaking resources that eventually (after about 400 hours of uptime/usage?) causes some once-normal apps on the phone to operate improperly, due to Low Memory conditions.

This is not a hardware or memory card problem.
This is not a 3rd party task killer issue; the processes are dying due to them not being able to be launched due to low memory conditions, and the OS keeps trying to restart them, resulting in a vicious cycle, and making the phone operate very sluggishly.

If a process can't write or update data/cache properly due to low resources, the app may malfunction even on phone restart because of the corrupted/inconsistent data.

I rebooted my phone manually.
Phone uptime was at 670 hours.


Sent from my DROIDX using DroidForums App

 

[JustisLewis]

I guess the more important question here is, if I was rooted, would that dubious app have been able to access my Settings Preferences without any indication / my knowledge?

Sent from my DROIDX using DroidForums App

Only if you gave said application superuser permissions

Sent from my Droid using Tapatalk

 

[piquat]

I rebooted my phone manually.
Phone uptime was at 670 hours.

Wow, that's almost a month! LOL

My conclusion? I should restart my phone once in a while.

 

[Natey2]

I rebooted my phone manually.
Phone uptime was at 670 hours.

Wow, that's almost a month! LOL

My conclusion? I should restart my phone once in a while.

My phone did reboot by itself around 250 hours when it was hooked up via USB, and the timer did not reset.

I was using this phone to its limits to see what was getting logged when it started failing. Until the memory leaks are fixed, I figure 400 hours (based on my usage) is when enough memory/resources get leaked, and my phone starts running into problems.

I hope the logfile message segments I posted help people detect what is going on in their phones.

Sent from my DROIDX using DroidForums App

 

[kptphalkon]

I notice that when my phone is getting charged, at 90% charge, the following is logged, a couple of times:

02-22 21:19:04.180 I/BATTD ( 1157): set_charge_current=1300
02-22 21:19:06.132 I/BATTD ( 1157): set_charge_current=800
02-22 21:19:11.992 I/BATTD ( 1157): set_charge_current=1300
02-22 21:19:25.672 I/BATTD ( 1157): set_charge_current=800
02-22 21:19:29.579 I/BATTD ( 1157): set_charge_current=1300
02-22 21:19:31.531 I/BATTD ( 1157): set_charge_current=800
02-22 21:19:33.484 I/BATTD ( 1157): set_charge_current=1300
02-22 21:19:35.437 I/BATTD ( 1157): set_charge_current=800
02-22 21:19:37.390 I/BATTD ( 1157): set_charge_current=1300
02-22 21:19:47.156 I/BATTD ( 1157): set_charge_current=800
02-22 21:19:51.070 I/BATTD ( 1157): set_charge_current=1300

It looks like it is alternating between a 1300mA charge and a 800mA charge. Is this some kind of trickle-charge algorithm to prevent overcharging the battery?

Sent from my DROIDX using DroidForums App

Yes. If your phone is fully charged but still plugged in it will switch to battery power and set the charge input to a low state so the battery does not stay at or above '100%' at all times, which is unhealthy.

You need to stop worrying so much.

 

[Natey2]

I notice that when my phone is getting charged, at 90% charge, the following is logged, a couple of times:

02-22 21:19:04.180 I/BATTD ( 1157): set_charge_current=1300
02-22 21:19:06.132 I/BATTD ( 1157): set_charge_current=800
02-22 21:19:11.992 I/BATTD ( 1157): set_charge_current=1300
02-22 21:19:25.672 I/BATTD ( 1157): set_charge_current=800
02-22 21:19:29.579 I/BATTD ( 1157): set_charge_current=1300
02-22 21:19:31.531 I/BATTD ( 1157): set_charge_current=800
02-22 21:19:33.484 I/BATTD ( 1157): set_charge_current=1300
02-22 21:19:35.437 I/BATTD ( 1157): set_charge_current=800
02-22 21:19:37.390 I/BATTD ( 1157): set_charge_current=1300
02-22 21:19:47.156 I/BATTD ( 1157): set_charge_current=800
02-22 21:19:51.070 I/BATTD ( 1157): set_charge_current=1300

It looks like it is alternating between a 1300mA charge and a 800mA charge. Is this some kind of trickle-charge algorithm to prevent overcharging the battery?

Sent from my DROIDX using DroidForums App

Yes. If your phone is fully charged but still plugged in it will switch to battery power and set the charge input to a low state so the battery does not stay at or above '100%' at all times, which is unhealthy.

You need to stop worrying so much.

Thanks for the explanation.

I'm not worried at all.
Just trying to understand what the phone is doing.

The app developer who is leaking cursor resources should be worrying. But I doubt he is worried too. He probably reboots his PC and phone daily.

Sent from my DROIDX using DroidForums App

 

[AngryHatter]

Dude - obsessing much?
Out of 20 replies - 15 are you?

Enjoy a book, go see a show.

Good software engineers are meticulous to the point of obsession.

If you are a software engineer, maybe you can tell us how much memory is leaked by the unclosed cursors?

I see over 1K reads/views on this topic.

Sent from my DROIDX using DroidForums App

No, I am an EE.
(Among other things)
And I'll obsess about it in private until I have something to share.


600 of the views are yours.