I saw that last part, where the device is sending a message too a couple of days ago. I am not in the US and not using T-Mobile. As far as I can tell, the SMS seems to be the myfaves application trying to communicate with the T-Mobile servers via some proprietary protocol. I suppose the device has to tell the servers which persons you have in your myfaves and stuff like that.
I had a look at my telephone bill to see if the phone company had somehow billed me for sending SMS messages to "453", but that's not the case. In fact I am lucky because 3-digit SMS number cannot be used for premium services (i.e. chargeable) in the country where I live. I wonder if someone somewhere else has notices this on their bill or had any trouble? Best regards, Mads Kristiansen On Thu, Feb 12, 2009 at 12:12 PM, Stoyan Damov <[email protected]>wrote: > > Here's this TERRIBLE BUG, which I suspected and ranted about in my > "Re: Over-the-air upgrade WTF" post. > > > On a side note, not only calls are buggy, but it appears (but I can't > > prove it yet because of the device chooser bug mentioned above) that > > someone has tampered with the way GC works and it now works worse than > > before - in an app which makes *not one* allocation after it > > initializes, I feel GC is kicking in for no reason. > > > > So I went the other route (installed SDK 1.1) and to my NON-surprise, > I see the DAMN GC FROM HELL kicking in for no reason: > > 02-12 12:48:51.770: DEBUG/GpsLocationProvider(51): updateNetworkState > unavailable > 02-12 12:48:57.230: DEBUG/dalvikvm(757): GC freed 110 objects / 5128 > bytes in 74ms > 02-12 12:49:05.160: DEBUG/dalvikvm(135): GC freed 62 objects / 3096 > bytes in 75ms > > These 3 lines would repeat ENDLESSLY with an interval of ~5 seconds > between each line, and about 10-15 secs between every triplet. > And wait, there's MORE - these 3 lines continue being logged after I > exit the app and the device is completely idle. > > Someone, PLEASE, tell me what the hell is going on here? How are games > supposed to run without stuttering, if every 5 seconds the GC would > kick in, even though our games don't make not even ONE memory > allocation after initialization??? And please, don't tell me I'm the > only one experiencing this. > > The device is not even connected to internet and I have no clue as to > why the GpsLocationProvider would want to log that at all if it's so > obvious to it too. > > I have powered the device off, and then back on, and now the GC saga > continues: > > 02-12 13:01:08.827: DEBUG/dalvikvm(119): GC freed 110 objects / 5112 > bytes in 74ms > 02-12 13:01:25.887: DEBUG/dalvikvm(119): GC freed 110 objects / 5112 > bytes in 74ms > 02-12 13:01:49.797: DEBUG/dalvikvm(119): GC freed 110 objects / 5096 > bytes in 74ms > 02-12 13:02:00.027: DEBUG/dalvikvm(119): GC freed 110 objects / 5112 > bytes in 96ms > > It's better, alright, GC kicks in 10-20 secs. But it won't stop > either. And I see a pattern - the allocations are of the same size (w/ > 1 exception). > > But wait, there's more, I'm getting a series of these: > > 02-12 13:00:31.387: INFO/MyFaves(114): starting service with intent: > Intent { flags=0x4 > comp={com.tmobile.myfaves/com.tmobile.myfaves.MyFavesService} (has > extras) } > 02-12 13:00:31.387: INFO/MyFaves(114): handleMessage(0) > 02-12 13:00:31.417: INFO/MyFaves(114): sending msg: > > 16358279014000210001000000000000000000000000000000000000000000000000000000000000 > to 453 > 02-12 13:00:31.517: INFO/ActivityManager(60): Stopping service: > com.tmobile.myfaves/.MyFavesService > 02-12 13:00:35.857: DEBUG/dalvikvm(92): GC freed 5184 objects / 290448 > bytes in 120ms > 02-12 13:00:40.947: DEBUG/dalvikvm(119): GC freed 521 objects / 44944 > bytes in 74ms > 02-12 13:00:46.667: INFO/MyFaves(114): > SMSStatusReceiver.onReceive(extras: Bundle[{id=100}]; resultCode: 1); > action: sent > 02-12 13:00:46.697: INFO/MyFaves(114): starting service with intent: > Intent { comp={com.tmobile.myfaves/com.tmobile.myfaves.MyFavesService} > (has extras) } > 02-12 13:00:46.697: INFO/MyFaves(114): handleMessage(11) > 02-12 13:00:46.757: INFO/ActivityManager(60): Stopping service: > com.tmobile.myfaves/.MyFavesService > > WHAT THE HELL???? Is the device trying to send or receive *anything* > w/o my consent??? > > Thanks! > > > > -- / Mads Kristiansen, [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
