What are my Android apps doing behind the scenes?

[Natey2]

To do an effective count, one needs to be able to capture the logs for an extended period of time (to a file), and use a program like grep and wc to get the numbers.

aLogcat has an option to filter. Use GC_ as the filter string to only display GC messages, but the time range of logged messages on the phone is insufficient to get a proper count over time.
I only see a max of about 1000 lines in my logfile snapshots.

If memory is getting scarce and GCs occur more frequently and start slowing things down, a reboot may help (temporarily). A phone with more memory, or running less apps concurrently, should also help.

Sent from my unrooted DroidX using DroidForums app

 

[Natey2]

Recurring Ad-related errors, this time under Gingerbread...
Is there an exception handling problem in the Ad SDK?

06-25 07:01:14.078 I/AdMobSDK( 4076): Requesting fresh ads every 60 seconds.
06-25 07:01:14.086 E/AdMobSDK( 4076): getPublisherId returning null publisher id. Please set the publisher id in AndroidManifest.xml or using AdManager.setPublisherId(String)
06-25 07:01:14.086 E/AdMobSDK( 4076): Unhandled exception requesting a fresh ad.
06-25 07:01:14.086 E/AdMobSDK( 4076): java.lang.IllegalStateException: Publisher ID is not set! To serve ads you must set your publisher ID assigned from www.admob.com. Either add it to AndroidManifest.xml under the <application> tag or call AdManager.setPublisherId().
06-25 07:01:14.086 E/AdMobSDK( 4076): at com.admob.android.ads.b.a(AdRequester.java:369)
06-25 07:01:14.086 E/AdMobSDK( 4076): at com.admob.android.ads.b.a(AdRequester.java:184)
06-25 07:01:14.086 E/AdMobSDK( 4076): at com.admob.android.ads.AdView$b.run(AdView.java:661)


Sent from my unrooted DroidX using DroidForums app.

 

[Natey2]

My stock DroidX on Android Gingerbread 2.3.3 (System Version 4.5.602) starts getting sluggish after about 48 hours.

One should close a cursor before finalizing it. But in the logs, I see:

08-20 05:43:02.435 W/CursorWrapperInner(21944): Cursor finalized without prior close()

Could this be causing resource leaks, again?


Sent from my unrooted DroidX using DroidForums app.

 

[Natey2]

Is someone trying to monitor if I am tethering?

09-26 14:09:22.543 D/Tethering( 1319): Tethering got CONNECTIVITY_ACTION
09-26 14:09:22.543 D/Tethering( 1319): mWifiTethered = falsemUsbTethered = false

Was this introduced in .605, .602, or earlier?

Sent from my unrooted DroidX using DroidForums app.

 

[Natey2]

I hadn't noticed this before, so it must be recent:

Which app(s) use this "Fiksu" module to upload "tracking information" from my phone?

10-18 04:41:11.795 D/FiksuTracking(30612): Successfully uploaded tracking information.

Sent from my unrooted DroidX using DroidForums app.

 

[Natey2]

Sometimes a respected Free App Of The Day from Amazon like OfficeSuite Pro v5.1.519 triggers errors/warnings like this daily (looks like a Java programmer who needed to keep an eye on his SQL code and start using bindargs), while spiking the CPU over 30% in the early hours of the morning:

10-31 04:03:26.207 W/Database(18849): Reached MAX size for compiled-sql statement cache for database /data/data/com.mobisystems.editor.office_registered/databases/search.db; i.e., NO space for this sql statement in cache: SELECT rowid, accessed FROM files_data WHERE fileName = '2011-03-12-11.18.39.txt' AND pathId = 36 LIMIT 1. Please change your sql statements to use '?' for bindargs, instead of using actual values

I must applaud the OS/environment for providing such descriptive error messages to help identify the cause and suggest a possible solution.

Sent from my unrooted DroidX using Tapatalk from GetJar

 

[Heywood]

I have office suite pro from the Amazon freebie day. What am I suppose to be looking for?

 

[Natey2]

Everyday, around the same time (4am for me), whether you use OfficeSuite Pro or not, it does something that uses a fairly significant amount of CPU for a short while. I've tried turning off auto update checking and auto promotion checking within the product, but the CPU burst usage continues.
The message I posted was to highlight an annoying recurring incident in the software that most people would not have been aware of.
Nevertheless, it is a good product, and we'll see if mobisystems does something about it.

Sent from my unrooted DroidX using Tapatalk from GetJar

 

[Heywood]

Everyday, around the same time (4am for me), whether you use OfficeSuite Pro or not, it does something that uses a fairly significant amount of CPU for a short while. I've tried turning off auto update checking and auto promotion checking within the product, but the CPU burst usage continues.
The message I posted was to highlight an annoying recurring incident in the software that most people would not have been aware of.
Nevertheless, it is a good product, and we'll see if mobisystems does something about it.

Sent from my unrooted DroidX using Tapatalk from GetJar

Thanks Natey2, I'll keep my eyes on it

 

[Natey2]

Sometimes a respected Free App Of The Day from Amazon like OfficeSuite Pro v5.1.519 triggers errors/warnings like this daily (looks like a Java programmer who needed to keep an eye on his SQL code and start using bindargs), while spiking the CPU over 30% in the early hours of the morning

OfficeSuite Pro v5.5.730 does not seem to be spiking the CPU anymore. Seems to have stopped on 12/20/2011 for me.

Sent from my unrooted DroidX using Tapatalk

 

[Natey2]

Re: Verizon/Motorola .621 update - http://support.verizonwireless.com/pdf/system_update/droid_x.pdf

"Fixed issue where the device may power ON without user interaction".
Good to hear they finally admit it. Surely all those users couldn't be imagining this

"Reduced Out of Memory errors".
Nicer way of saying they made an attempt to fix some of their resource leaks? I can guarantee we will see other resource leaks, but this is a start.

Sent from my unrooted DroidX using Tapatalk

 

[Natey2]

My phone has only been running for about 24 hours since the .621 OTA update from Verizon, and I already see messages like this in the logs:

02-25 06:09:27.586 I/ActivityManager( 1327): Process com.google.android.googlequicksearchbox (pid 11985) has died.
02-25 06:09:27.602 I/ActivityManager( 1327): Low Memory: No more background processes.
...
02-25 06:40:01.409 I/ActivityManager( 1327): Process com.motorola.blur.home.other (pid 12724) has died.
02-25 06:40:01.409 I/ActivityManager( 1327): Low Memory: No more background processes.

Things may actually have been better before this .621 update for me. I hope I don't have to reboot my phone every 24 hours now. Used to be at least every 2 or 3 days...

Sent from my unrooted DroidX using Tapatalk

 

[Natey2]

Awesome! More PC-based tools at my disposal to see what these Android apps are up to:

http://bluestacks.com/

"... software that allows Android users to run their apps on all Windows PCs, tablets, and laptops - without any modifications." - http://m.techcrunch.com/2012/04/10/qualcomm-invests-in-bluestacks/

Sent from my unrooted DroidX using Tapatalk

 

[kptphalkon]

Glad to see you're still unraveling the mysteries of Android Natey2!

 

[Natey2]

My smartphone has become so intertwined with my lifestyle that getting it to operate decently has become critical. It is certainly functional as is, but there are so many things that just gnaw away at it over a fairly short amount of time that reduces its level of functionality that I feel compelled to do what I do to expose some of those things here so others become aware too.

In college (long time ago), I had a flakey car that kinda worked most of the time. I took a great interest in finding out why it failed whenever it did. Great learning experience, but not a model I would recommend, since we primarily get a car to travel around in, not for learning why cars fail.
I find myself doing the same thing with my Android Smartphone now.

Currently, I have an extremely reliable and boring (from a maintenance perspective) car.
Maybe if my phone were the same way, I'd be looking for something else to investigate

Sent from my unrooted DroidX using Tapatalk