Typical T-Mobile Service Interaction Needs Log Analysis

by Brian Milnes » Sun, 04 Jan 2009 07:44:27 GMT


Sponsored Links
 Folks,

 I have a new G1 and it's started rebooting and bombing out of Chrome.
In fact, I can't load slashdot without it rebooting. So I attempted to
jail break it so that I can read the android log, but the current
recipe no longer works.

 So I'm stuck calling T-Mobile who start with the "newbie" questions,
then on to a technical service rep. The service rep then wants me to
remove ALL applications from the phone and try again. A totally
unacceptable
service interaction. That tech can't read the log to see what
happened,
if I got to a store they can't read the log and I can't read the log.
T-Mobile
does not support the applications, don't know which may cause problems
and thus will always be very paranoid about them.

 This is going to waste a LOT of time, money and customer good will.

 A great solution to this is an over the air log collector and
analyzer that
points to problems. It will need to make the standard judgment of is
the problem Hardware, OS, Android or the applications.

 Is anything like this in the works?


--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. cell tower status

Please how would I display the cell tower status in google map?
Could you provide me some codes or example?
Fradel

-- 

2. com.android.internal

Dear Developers !

I am developing an Application for one of the OEM. And I need to
import com.android.internal classes to new namespace. Yes, I have full
access to android OS and building full ROM flash image.

I do not get any compile time error, but as soon as I launch the app,
I get run-time exception (class not found).

Is there a specific way to import android internal classes ?

Thanks

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. for loop drawing first graphics to x0 y0 if more than 1 iteration

4. Android Market Licensing Problem

5. Update x10

6. Tracking revenue on the Android Market

7. The proliferation of Android markets.