[GUIDE] How to Logcat - Moto E General

Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
This is a share.original thread

Hmmm.. I think all can see original guide in Android section...
There's no need of posting it again..
Anyway.. Thanks..

TheStrix said:
Hmmm.. I think all can see original guide in Android section...
There's no need of posting it again..
Anyway.. Thanks..
Click to expand...
Click to collapse
I think that it is good for moto E users, most of them are newbies, so they won't have to search a lot

What's the difference BTW logcat and androids inbuilt Bug report function
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1033 using Tapatalk

jaspreet997 said:
What's the difference BTW logcat and androids inbuilt Bug report functionView attachment 2751421
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Logcat gives you the messages of the system logs and you can submit them to a developer manually. Bug report is kinda an automatic thing that keeps track of your errors

Related

[DEV] Modified Skype app with Video

Hi,
I modified the recently leaked skype w/ video app for the HTC Thunderbolt. Let me document my changes and progress so far:
Here is the original app:http://www.droid-life.com/2011/04/11/download-skype-with-video-on-android/
1) if you try to install the app unmodified on a non HTC thunderbolt phone, you will get an "installation failed" message. I decompiled the app using these instructions: http://jack-mannino.blogspot.com/2010/09/reversing-android-apps-101.html
2) I modified the AndroidManifest.xml to remove this line:
<uses-library android:name="com.htc.device" />
3) I then recompiled and resigned the app( http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/).
4) The apk now installed on my Nexus S but I get this error when I opened it:
"Sorry, your phone is not able to use this version of Skype. To find out more about Skype on mobile, visit www.skype.com"
5) I looked through the code and found the offending text in com.skype.ui.SplashScreenActivity.class:
protected void onResume()
{
super.onResume();
if (!f.a())
{
Toast.makeText(this, "Sorry, your phone is not able to use this version of Skype. To find out more about Skype on mobile, visit www.skype.com", 1).show();
finish();
}
.....
I commented out the toast and finish() line and then recompiled and resigned.
6) The apk installs but crashes when I try to open it:
W/dalvikvm(17595): VFY: bad arg 1 (into Ljava/lang/CharSequence
W/dalvikvm(17595): VFY: rejecting call to Landroid/widget/Toast;.makeText (Landroid/content/Context;Ljava/lang/CharSequence;I)Landroid/widget/Toast;
W/dalvikvm(17595): VFY: rejecting opcode 0x71 at 0x0010
W/dalvikvm(17595): VFY: rejected Lcom/skype/merlin_mecha/ui/SplashScreenActivity;.onResume ()V
W/dalvikvm(17595): Verifier rejected class Lcom/skype/merlin_mecha/ui/SplashScreenActivity;
W/dalvikvm(17595): Class init failed in newInstance call (Lcom/skype/merlin_mecha/ui/SplashScreenActivity
D/AndroidRuntime(17595): Shutting down VM
W/dalvikvm(17595): threadid=1: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime(17595): FATAL EXCEPTION: main
E/AndroidRuntime(17595): java.lang.VerifyError: com.skype.merlin_mecha.ui.SplashScreenActivity
E/AndroidRuntime(17595): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime(17595): at java.lang.Class.newInstance(Class.java:1409)
E/AndroidRuntime(17595): at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
E/AndroidRuntime(17595): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1681)
E/AndroidRuntime(17595): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1793)
E/AndroidRuntime(17595): at android.app.ActivityThread.access$1500(ActivityThread.java:123)
E/AndroidRuntime(17595): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:939)
E/AndroidRuntime(17595): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(17595): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(17595): at android.app.ActivityThread.main(ActivityThread.java:3848)
E/AndroidRuntime(17595): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(17595): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime(17595): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime(17595): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime(17595): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 176): Force finishing activity com.skype.merlin_mecha/.ui.SplashScreenActivity
W/ActivityManager( 176): Force finishing activity info.tikuwarez.launcher3/.ClassicAppPicker
This is my progress so far and here is my modified apk:http://www.mediafire.com/?l6xddlun3u52ung
Does this enable the use of the back camera instead of the front?
For my wife's fascinate
Sent from my ADR6400L using XDA Premium App
@eyeburn : Thanks for the investigation.
Could you try to remove the " if statement " instead ?
I guess the shared library is not only for security, but we will see that later.
More updates. I looked at the SplashScreenActivity.smali code and removed this line:
invoke-virtual {p0}, Lcom/skype/merlin_mecha/ui/SplashScreenActivity;->finish()V
this basically disables the the exiting(the finish() in the code below) of the program during the verizon phone check.
Now the phone doesn't crash but just stays at the "skype mobile" splash screen with the skype background.
I'll look at this again tomorrow. Gonna sleep now.
Updated apk as of midnight Apr 12: http://www.mediafire.com/?eqgr111a7agg3qv
My current thinking is the app is stuck in this while loop:
protected void onResume()
{
super.onResume();
if (!f.a())
{
Toast.makeText(this, "Sorry, your phone is not able to use this version of Skype. To find out more about Skype on mobile, visit www.skype.com", 1).show();
finish();
}
while (true)
{
return;
Intent localIntent1 = new Intent(this, SignInActivity.class);
boolean bool1 = getIntent().getBooleanExtra("LaunchedBySyncAdapter", 0);
Intent localIntent2 = localIntent1.putExtra("LaunchedBySyncAdapter", bool1);
int i = getIntent().getIntExtra("PostLoginCommand", 0);
Intent localIntent3 = localIntent1.putExtra("PostLoginCommand", i);
String str = getIntent().getStringExtra("PostLoginDataUri");
Intent localIntent4 = localIntent1.putExtra("PostLoginDataUri", str);
ac localac = new ac(this, localIntent1);
monitorenter;
try
{
this.a = localac;
Handler localHandler = this.b;
Runnable localRunnable = this.a;
boolean bool2 = localHandler.postDelayed(localRunnable, 1500L);
monitorexit;
continue;
}
finally
{
localObject = finally;
monitorexit;
}
}
throw localObject;
}
}
I keep getting this messages on my logcat:
I/TelephonyRegistry( 176): notifyServiceState: 0 home T - Mobile T - Mobile 310260 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 176): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=3
I/TelephonyRegistry( 176): notifyServiceState: 0 home T - Mobile T - Mobile 310260 HSDPA CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 176): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=8
More likely, that you killed the login intent, which supposed to invoke login activity. You already have 'return' as the first statement of the while loop. The code in it's current state doesn't make sense to me. It should be an exist condition from the loop, otherwise the only way to exit the loop is via exception, which will effectively kill the application.
ivan.volosyuk said:
More likely, that you killed the login intent, which supposed to invoke login activity. You already have 'return' as the first statement of the while loop. The code in it's current state doesn't make sense to me. It should be an exist condition from the loop, otherwise the only way to exit the loop is via exception, which will effectively kill the application.
Click to expand...
Click to collapse
same conclusion here, but I assume this part of code is badly decompiled. There are several other while->true->return in this code.
I/ActivityManager( 176): Starting: Intent { act=android.settings.APPLICATION_DETAILS_SETTINGS dat=package:com.skype.merlin_mecha cmp=com.android.settings/.applications.InstalledAppDetails } from pid 18780
D/dalvikvm(18780): GC_CONCURRENT freed 333K, 48% free 3339K/6343K, external 5923K/6893K, paused 67ms+23ms
I/ActivityManager( 176): Displayed com.android.settings/.applications.InstalledAppDetails: +1s756ms
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
I/Process ( 176): Sending signal. PID: 18721 SIG: 9
I/ActivityManager( 176): Force stopping package com.skype.merlin_mecha uid=10068
I/ActivityManager( 176): Force finishing activity HistoryRecord{4057dcc8 com.skype.merlin_mecha/.ui.SplashScreenActivity}
W/InputManagerService( 176): Window already focused, ignoring focus gain of: [email protected]
E/InputDispatcher( 176): channel '407ae0c0 com.skype.merlin_mecha/com.skype.merlin_mecha.ui.SplashScreenActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 176): channel '407ae0c0 com.skype.merlin_mecha/com.skype.merlin_mecha.ui.SplashScreenActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
I/WindowManager( 176): WIN DEATH: Window{407ae0c0 com.skype.merlin_mecha/com.skype.merlin_mecha.ui.SplashScreenActivity paused=true}
This is what is happening now.
Keep up the good work, a LOT of people will love you if you can get this to work on other phones like the Galaxy S.
Agreed keep up the good work....and Thanks
speaking as someone with a G Tablet, I really want this to work, so please take all the encouragement i can offer!
Keep up the good work.
Oh thank you.
Seriously, I posted about how somebody should modify this to work on all phones yesterday.
As for me, I'm getting "Sorry1, your phone is not able to use this version of skype"
(Wonder why it says "Sorry1")
I'm using a mytouch 4g with cm7 stable
Working on the same thing here on my EVO. I tried your APK but I don't get to the sign-in screen. I removed the same line from the AndroidManifest.xml file that you did so that it would install. I took a different approach and modified the VerizonNetwork and VerizonMerlin check to return 0x1 instead of 0x0 so that it gets by the Toast successfully and I get the sign-in screen. Now after I sign-in, the service crashes.
Code:
I/com.skype.merlin_mecha.service.a(17177): system board:supersonic bootloader:2.10.0001 brand:sprint product:htc_supersonic model:PC36100 manufacturer:HTC device:supersonic display:3.70.651.1 fingerprint:sprint/htc_supersonic/supersonic/supersonic:2.2/FRF91/294884:user/release-keys host:AA109 user:root radio:2.15.00.09.01 tags:release-keys type:user
I/global (17177): Default buffer size used in BufferedInputStream constructor. It would be better to be explicit if an 8k buffer is required.
D/dalvikvm(17177): GC_FOR_MALLOC freed 5340 objects / 712528 bytes in 124ms
I/LSState (12428): EventReceiver:android.intent.action.NOTIFICATION_UPDATE
I/StartSkypeKitOperation(17177): REMOVE THIS ONCE VERIFIED: appToken = KdXVSo6qB9
I/dalvikvm(17177): Jit: resizing JitTable from 4096 to 8192
D/dalvikvm(15756): GC_EXPLICIT freed 3901 objects / 412584 bytes in 100ms
I/ActivityManager(12428): Process com.skype.merlin_mecha (pid 17177) has died.
W/ActivityManager(12428): Scheduling restart of crashed service com.skype.merlin_mecha/.service.SkypeServiceController in 5000ms
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://db.tt/umgHYVq
-Daryel
daryel - i tried it and the same happened to me, but there was nothing that said the app force-closed. it simply closed itself and that was that.
it looks like real headway is being made here. I will faithfully watch this until it is finished
oh the sorry1 was a debugging thing hehe.
so it is now crashing in com.skype.merlin_mecha.service.a
Looks to be failing some fingerprint checking. I guess this is where it verifies the phone.
I wonder which file this line is coming from:
I/StartSkypeKitOperation(17177): REMOVE THIS ONCE VERIFIED: appToken = KdXVSo6qB9
New Edit:
Ok the verification is done in com.skype.merlin_mecha.startup.SignInActivity.
I am speculating, the check and crash is in:
protected void onCreate(Bundle paramBundle)
Thanks guys, it looks like you are pretty close to the solution.
Finger crossed
daryelv said:
Working on the same thing here on my EVO. I tried your APK but I don't get to the sign-in screen. I removed the same line from the AndroidManifest.xml file that you did so that it would install. I took a different approach and modified the VerizonNetwork and VerizonMerlin check to return 0x1 instead of 0x0 so that it gets by the Toast successfully and I get the sign-in screen. Now after I sign-in, the service crashes.
Click to expand...
Click to collapse
Sorry but where is this Verizon check?
There are 2 .so missing.
if you look in a/a/a.smali you will find a ref to
/data/data/com.skype.merlin_mecha/lib/libskype_jni.so
And com\skype\a\c.smali has a ref to /data/data/com.test.java_surface/lib/libskype_jni.so
that means there is more to this
eyeburn said:
I wonder which file this line is coming from:
I/StartSkypeKitOperation(17177): REMOVE THIS ONCE VERIFIED: appToken = KdXVSo6qB9
Click to expand...
Click to collapse
Looks like this comes from com\skype\merlin_mecha\service\bs.class
Code:
Object localObject = "M9QA6f6YIH";
if (!com.skype.merlin_mecha.a.b.b)
continue;
if (!com.skype.merlin_mecha.a.b.a)
continue;
localObject = "KdXVSo6qB9";
String str4 = "REMOVE THIS ONCE VERIFIED: appToken = " + (String)localObject;
int k = Log.i("StartSkypeKitOperation", str4);
bo.g(this.c).SetApplicationToken((String)localObject);
boolean bool1 = bo.c(this.c);
if (bool1)
continue;

[Guide]Howto LOGCAT

I think this one is definitely needed for this forum. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.
Don't be a noob. Be a newbie..!!
Details here.
Great Guide! Should become a sticky.
You know,today morning you said you were not an expert with logcats.I see this thread and i am awestruck,but then i read the second last line :|
Prawesome said:
You know,today morning you said you were not an expert with logcats.I see this thread and i am awestruck,but then i read the second last line :|
Click to expand...
Click to collapse
I said i am no expert. That doesn't mean i cannot take, read or understand logcat..!!
Don't be a noob. Be a newbie..!!
Details here.
This thread is perfect to be a sticky in the Android Development Section.
Newcommers should know how to properly report bugs. I also leave a redirect in the Original Android Development.
I rather use ddms for all
Command prompt is the most basic thing same old Windows
Sent from my GT-P7300 using xda app-developers app
helped me out. Thanks
Fro "noobs" it will be easier to use qtadb https://qtadb.wordpress.com/download/ , just download, install and run. Nice GUI for adb, contains access to logcat too.
Fro "noobs" it will be easier to use qtadb https://qtadb.wordpress.com/download/ , just download, install and run. Nice GUI for adb, contains access to logcat too.
Click to expand...
Click to collapse
And it colours out errors according to their priority
I am a potato, problem?
Thanks bro
Sent from my GT-S5830 using Tapatalk 2
Extremely useful,
thank you!
However, catlog force closes when I added it as system app.
How can i get application specific logcat like i want to get logcat of systemui only
Really helpful!
Aman
Wysłane z mojego GT-I8190 przy użyciu Tapatalka
Thanks Sir...its helped me a lot..about understanding logcat
---------- Post added at 07:17 AM ---------- Previous post was at 07:12 AM ----------
Thanks Sir...its helped me a lot..about understanding logcat

[Utility][WIN] AIO logcat manager

AIO LOGCAT MANAGER​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since android development and logcat is essential part to track problems and errors..
The three most important log types are:
logcat: the log output of the Android system
radio logcat: the log output of your System / BB / RIL communication
kernel log (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
The tool I made will make you able to do all of these in very friendly interface, and even you could do more,, So let's see how it is
How to use:
It is simple, just run AIO_Logcat_Manager.bat file.. I will explain every feature in next heading.
Walkthrough Features:
Splash screen:
The main screen:
In this main menu, you can choose the type of logcat you want,, All, Error, Fatal, Radio, Kernel... etc
Process logcat filtered by name menu (Option 9):
This is unique in my tool, where you can filter your result logcat for specific process name..
Example: assume you get this logcat
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/MediaPlayerService( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
and you want to see MediaPlayerService process logcat only..!!
So here comes the useful feature of this tool, where you can filter the only process you are interested in..
Read Exported logcats (Option 10):
Here you can read all logcats you have exported to the output folder
Kernel logcats (Option 11):
This feature needs from the user to be rooted in order to access kernel logs..!!!
Here you have the ability either to read or to export different kernel log types..
Reading:
Exporting:
How to read your logcat:
Here is a useful thread written by @Stryke_the_Orc that will help you understanding your logcat files.
http://forum.xda-developers.com/showthread.php?t=2274119
Future ADB engine update:
If ADB engine is outdated, you can download android SDK from official website here and extract adb, AdbWinApi.dll and AdbWinUsbApi.dll from sdk\platform-tools folder and put in AIO_Logcat_Manager\tools folder.
Reporting bugs:
Please feel free reporting any bugs to help to polish upcoming releases :laugh:
Help in development:
If you are developer and you are interested in polishing this work, please go ahead since I KEPT IT OPEN SOURCE, so everyone can participate in development of this tool (just don't forget to give me some credits buddy )
Download:
AIO-Logcat-Manager_v1.0 @ 14/June/2013
Change-log:
@ 14/June/2013 (v1.0):
- The first release of AIO logcat manager.
Special Thanks to XDA Portal Team For Featuring This Utility:
http://www.xda-developers.com/android/simplify-logging-with-aio-logcat-manager/
Lol i love your thread
Inviato dal mio GT-I9070 con Tapatalk 2
KINGbabasula said:
Lol i love your thread
Inviato dal mio GT-I9070 con Tapatalk 2
Click to expand...
Click to collapse
Thank you for support
Very cool, I will be adding this tool to the OP of my thread:good::highfive:
dude, you are great.
this is the best logcat utility ever, especially the filter feature :good:
mike0jj said:
dude, you are great.
this is the best logcat utility ever, especially the filter feature :good:
Click to expand...
Click to collapse
Oh it is great that there is still somebody who cares about this project. I thought it was buried down inside xda archive
Thanks buddy and I hope I could hear some suggestion regarding the utility development.
cheers
majdinj said:
Oh it is great that there is still somebody who cares about this project. I thought it was buried down inside xda archive
Thanks buddy and I hope I could hear some suggestion regarding the utility development.
cheers
Click to expand...
Click to collapse
I push it anyone looking for a logcat tool running windows, it's a great tool. Nice job:thumbup::beer:
Slithering from the nether regions of a twisted mind and tarnished soul
good work man, a lot of people need to say thanks to you
Sabyn said:
good work man, a lot of people need to say thanks to you
Click to expand...
Click to collapse
Thanks man
Thanks for this man. Helpful to everyone! Maybe you could add an option in the future to read logcats already made from ADB. Just a thought if you don't already have it
If I may make a suggestion, it would be a great idea to possibly include something like logcat-color to make viewing of real-time logs a lot easier
Great tool by the way
N_otori0us_ said:
Thanks for this man. Helpful to everyone! Maybe you could add an option in the future to read logcats already made from ADB. Just a thought if you don't already have it
Click to expand...
Click to collapse
Thanks man, but this feature is already implemented in the tool :laugh:
CNexus said:
If I may make a suggestion, it would be a great idea to possibly include something like logcat-color to make viewing of real-time logs a lot easier
Great tool by the way
Click to expand...
Click to collapse
Yeah sure.. but java coding is different from cmd; however it is possible, but it will be very very long scripting if I am using cmd for that. May be I will try to learn some java coding later on, but not in the mean time..
Thanks for suggestion :good:
Thanks for sharing this
I added it to my FAQ Guides HERE and HERE
bigdaddy619 said:
Thanks for sharing this
I added it to my FAQ Guides HERE and HERE
Click to expand...
Click to collapse
wow.. thanks for sharing
you should add a little cat icon instead of the cmd one when running the program ^_^ Thanks for your work! :good:
I get this error: "Unable to open log device '/dev/log/main': No such file or directory" in the log file. Using ezaechiel TW ROM on a Galaxy Note 1. There's no file called 'main' in the folder '/dev/log/'
Any ideas?
Ok managed to get logcat to work, found '/system/etc/init.d/12cleaner' had
Code:
if [ -e /dev/log/main ]
then
rm -f /dev/log/main
Which I commented out and now it's working.
Hello buddy.
+1 to ur work but can u please tell me if I can took out the logcat from my rom while stuck at splash screen??
Sent from my A2 using xda app-developers app
qmobilea2 said:
Hello buddy.
+1 to ur work but can u please tell me if I can took out the logcat from my rom while stuck at splash screen??
Sent from my A2 using xda app-developers app
Click to expand...
Click to collapse
No, for the logcat to work, the system needs to at least start. You can probably grab a kernel log, but I don't think it will show you what you want.
Sent from my SPH-D710 using XDA Premium 4 mobile app
thx a lot for this logcat tool. now is much easyer for me to logcat my sense port

[Q] How do I install AccountAndSyncSettings.apk?

I am trying to access System-Settings-Accounts, but cannot find it on my NST rooted w Nook Manager.
I installed one touch Sync Settings from the market, but when I click on it, the NST reboots.
I found AccountAndSyncSettings.apk in the /system/app folder, but installation fails.
I copied the file over to my desktop and did an adb install. [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
logcat info:
D/AndroidRuntime( 4396):
D/AndroidRuntime( 4396): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 4396): Heap size: -Xmx64m
D/AndroidRuntime( 4396): CheckJNI is OFF
D/dalvikvm( 4396): creating instr width table
D/AndroidRuntime( 4396): --- registering native functions ---
I/NATIVE-EPD( 4396): framebuffer_handle: 20
D/PackageParser( 3554): Scanning package: /data/app/vmdl13223.tmp
D/dalvikvm( 3554): GC freed 34328 objects / 2066216 bytes in 101ms
E/PackageManager( 3554): Package com.android.providers.subscribedfeeds has no si
gnatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 3554): Package couldn't be installed in /data/app/com.android.
providers.subscribedfeeds.apk
D/AndroidRuntime( 4396): Shutting down VM
D/dalvikvm( 4396): DestroyJavaVM waiting for non-daemon threads to exit
D/dalvikvm( 4396): DestroyJavaVM shutting VM down
D/dalvikvm( 4396): HeapWorker thread shutting down
D/dalvikvm( 4396): HeapWorker thread has shut down
D/jdwp ( 4396): JDWP shutting down net...
I/jdwp ( 4396): adbd disconnected
D/dalvikvm( 4396): VM cleaning up
D/dalvikvm( 4396): LinearAlloc 0x0 used 631916 of 5242880 (12%)
D/dalvikvm( 3554): GC freed 4440 objects / 255744 bytes in 121ms
Please advise...
You don't install it. The workaround to change sync settings is to use the gmail app to add an account and enter the same account information you already have setup and you will be able to update the sync settings.
RandyB201 said:
I am trying to access System-Settings-Accounts, but cannot find it on my NST rooted w Nook Manager.
I installed one touch Sync Settings from the market, but when I click on it, the NST reboots.
I found AccountAndSyncSettings.apk in the /system/app folder, but installation fails.
I copied the file over to my desktop and did an adb install. [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
Please advise...
Click to expand...
Click to collapse
You don't install apk's in /system/app/ you just put them in /system/app/ and after reboot start working.
Try to access AccountAndSyncSettings using 'NookColorTools'. If NCT does not allow access to these settings try using 'apktool' to decompile package and try to infer correct 'am start' command from the directory structure,filenames and code. Experiment with 'am start' using adb.
This is a Nook Simple Touch. NookColorTools sounds like something from the nook color?
osowiecki said:
You don't install apk's in /system/app/ you just put them in /system/app/ and after reboot start working.
Try to access AccountAndSyncSettings using 'NookColorTools'. If NCT does not allow access to these settings try using 'apktool' to decompile package and try to infer correct 'am start' command from the directory structure,filenames and code. Experiment with 'am start' using adb.
Click to expand...
Click to collapse
please clarify...
If I understand you correctly, I need to:
1) open gmail
2) add an account (btw, when I click the add account button, it just goes back to the inbox...)
3) enter the same account info i already have in there
I am unclear on how I access sync settings after that is done?
straygecko said:
You don't install it. The workaround to change sync settings is to use the gmail app to add an account and enter the same account information you already have setup and you will be able to update the sync settings.
Click to expand...
Click to collapse
RandyB201 said:
If I understand you correctly, I need to:
1) open gmail
2) add an account (btw, when I click the add account button, it just goes back to the inbox...)
3) enter the same account info i already have in there
I am unclear on how I access sync settings after that is done?
Click to expand...
Click to collapse
Add account shouldn't send you back to the inbox. It should work like this:
Open gmail
Open menu, click on accounts
Click on Add account button
Click on the big g on the Add an account screen
Click Next
Click Sign In
Enter your gmail username and password
Click Sign In
Now you should be on the Data & synchronization page with check boxes for Contacts, Calendar and Gmail. Check/uncheck what you want and click on Finish.
If add account continues to send you back to the inbox get a logcat when that happens and post it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:29 PM ----------
RandyB201 said:
This is a Nook Simple Touch. NookColorTools sounds like something from the nook color?
Click to expand...
Click to collapse
Yes but some of the things in NCT work on the NST. But don't bother installing NCT for this as the Account & Sync Settings isn't there. Don't try digging the intent for am start out of the apk either as market tools like one touch sync settings have already figured that out and that's what they do. I tried all this when I put together NTGAppsAttack and could never get Account & Sync Settings to work. IIRC, its a layout issue. There is something funny about what B&N did to Android on the NST that causes some apps to die with layout issues. If I did remember correctly it might be possible to hack the apk up to get it to work but I don't have the time or motivation to do it as the gmail workaround does everything I need.
logcat...
I am still getting a brief flash and a return to the inbox when I puch the Add Account Button.
logcat info:
D/DeviceManagerBroadcastReceiver( 1110): action (com.bn.devicemanager.ACTION_HAN
DLE_CRASH)
I/dalvikvm( 1235): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 1235): Sending signal. PID: 1235 SIG: 9
I/WindowManager( 785): WIN DEATH: Window{4a0b9b38 com.google.android.gm/com.goo
gle.android.gm.MailboxSelectionActivity paused=false}
I/ActivityManager( 785): Process com.google.android.gm (pid 1235) has died.
I/WindowManager( 785): WIN DEATH: Window{4a1a72f8 com.google.android.gm/com.goo
gle.android.gm.ConversationListActivity paused=false}
I/ActivityManager( 785): Start proc com.google.android.gm for activity com.goog
le.android.gm/.ConversationListActivity: pid=1326 uid=10022 gids={3003}
E/TC ( 1134): KPICollector: 1375724620795 platform process_start {"processN
ame":"com.google.android.gm"}
D/SurfaceFlinger( 785): Frame buffer posted; elapsed time = 22 msecs
I/dalvikvm( 1326): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=38)
I/UsageStats( 785): Unexpected resume of com.google.android.gm while already re
sumed in com.google.android.gm
I/dalvikvm( 1326): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=46)
E/TC ( 1134): KPICollector: 1375724621021 ActivityManager foreground {"comp
onent":"com.google.android.gm/.ConversationListActivity"}
I/ActivityThread( 1326): Publishing provider com.google.android.gmail.Suggestion
Provider: com.google.android.gm.SuggestionsProvider
I/ActivityThread( 1326): Publishing provider com.google.android.gm.attachmentspr
eviews: com.google.android.gm.AttachmentPreviewProvider
V/Gmail ( 1326): onCreate(), id=com.google.android.gm.ConversationListActivity
@49fc4e28
D/Gmail ( 833): MailProvider.query: content://gmail-ls/labels/[email protected]
.com(null, null)
D/Gmail ( 1326): SETTING ACCOUNT, USER:[email protected]
D/Gmail ( 833): MailProvider.query: content://gmail-ls/conversations/randyb20
[email protected](, null)
V/Gmail ( 1326): onStart(), [email protected]
49fc4e28
V/Gmail ( 1326): onRestoreInstanceState(), id=com.google.android.gm.Conversati
[email protected]
V/Activity( 1326): performResume()
D/EPD#ActivityResume( 785): resetRegion 4
D/NATIVE-EPD( 785): epd_reset_region: 0x10
D/EPD#ActivityResume( 785): resetRegion 5
D/NATIVE-EPD( 785): epd_reset_region: 0x20
D/EPD#ActivityResume( 785): resetRegion 6
D/NATIVE-EPD( 785): epd_reset_region: 0x40
D/EPD#ActivityResume( 785): resetRegion 7
D/NATIVE-EPD( 785): epd_reset_region: 0x80
D/EPD#ActivityResume( 785): Disable EPD for 350ms!!!!!!!!
V/Gmail ( 1326): onResume()
I/DeviceManagerHandler( 1110): HandleMessage(): msg.what (1)
I/global ( 1110): Default buffer size used in BufferedWriter constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
I/LogcatProcessor( 1110): LOG END MARKER - 1375724621902
D/Gmail ( 833): clearNewUnreadMailForNotificationLabelIfNeeded. Count: 0, lab
el: -5/^^unseen-^i
D/Gmail ( 833): clearNewUnreadMailForNotificationLabelIfNeeded. Count: 0, lab
el: -6/^^unseen-^^vmi
W/InputManagerService( 785): Got RemoteException sending setActive(false) notif
ication to pid 1235 uid 10022
I/ActivityManager( 785): Displayed activity com.google.android.gm/.Conversation
ListActivity: 1530 ms (total 1530 ms)
D/SurfaceFlinger( 785): Frame buffer posted; elapsed time = 27 msecs
D/dalvikvm( 1110): GC freed 4130 objects / 418424 bytes in 145ms
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
D/WindowManager( 785): CALLING monitor
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
D/WindowManager( 785): CALLING monitor
V/Gmail ( 1326): onPause(), [email protected]
49fc4e28
W/Process ( 785): Unable to open /proc/1235/status
E/TC ( 1134): KPICollector: 1375724628487 ActivityManager background {"comp
onent":"com.google.android.gm/.ConversationListActivity"}
E/TC ( 1134): KPICollector: 1375724628496 ActivityManager foreground {"comp
onent":"com.harasoft.relaunch/.AllApplications"}
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
straygecko said:
Add account shouldn't send you back to the inbox. It should work like this:
Open gmail
Open menu, click on accounts
Click on Add account button
Click on the big g on the Add an account screen
Click Next
Click Sign In
Enter your gmail username and password
Click Sign In
Now you should be on the Data & synchronization page with check boxes for Contacts, Calendar and Gmail. Check/uncheck what you want and click on Finish.
If add account continues to send you back to the inbox get a logcat when that happens and post it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:29 PM ----------
Yes but some of the things in NCT work on the NST. But don't bother installing NCT for this as the Account & Sync Settings isn't there. Don't try digging the intent for am start out of the apk either as market tools like one touch sync settings have already figured that out and that's what they do. I tried all this when I put together NTGAppsAttack and could never get Account & Sync Settings to work. IIRC, its a layout issue. There is something funny about what B&N did to Android on the NST that causes some apps to die with layout issues. If I did remember correctly it might be possible to hack the apk up to get it to work but I don't have the time or motivation to do it as the gmail workaround does everything I need.
Click to expand...
Click to collapse
Do you have B&N apps disabled? If so, reenable and try again. B&N messed with the android authentication stuff and has their own account types. Since you aren't even getting to the page where you select the account type (Google and two generic android) I suspect it might be looking for disabled B&N account stuff and crashing.
The logcat isn't telling me much - is there anything earlier in the log of interest? /data/anr/traces.txt also might help but I'm not optimistic on that one.
Don't try digging the intent for am start out of the apk either as market tools like one touch sync settings have already figured that out and that's what they do.
Click to expand...
Click to collapse
am start -a android.settings.SYNC_SETTINGS
It does not work or you have just missed something?
Got the command from decompiled "AccountAndSyncSettings.apk".
AndroidManifest.xml.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
osowiecki said:
am start -a android.settings.SYNC_SETTINGS
It does not work or you have just missed something?
Got the command from decompiled "AccountAndSyncSettings.apk".
AndroidManifest.xml.
Click to expand...
Click to collapse
It crashes android and restarts. I was wrong about it being a layout issue. Its a null pointer exception.
Code:
20:43:39.624 Debug AccountSettings 670 added authority com.android.contacts to accountType com.google
20:43:39.624 Debug AccountSettings 670 added authority calendar to accountType com.google
20:43:39.624 Debug AccountSettings 670 added authority gmail-ls to accountType com.google
20:43:39.624 Debug AccountSettings 670 added authority subscribedfeeds to accountType com.google
20:43:39.624 Warning dalvikvm 670 threadid=21: thread exiting with uncaught exception (group=0x4001b170)
20:43:39.624 Error AndroidRuntime 670 Uncaught handler: thread android.server.ServerThread exiting due to uncaught exception
20:43:39.624 Error AndroidRuntime 670 *** EXCEPTION IN SYSTEM PROCESS. System will crash.
20:43:39.624 Error dalvikvm 670 Invalid debug info stream. class Lcom/android/server/ServerThread;; proto ()V
20:43:39.733 Error AndroidRuntime 670 java.lang.NullPointerException
20:43:39.733 Error AndroidRuntime 670 at com.android.settings.ManageAccountsSettings.onSyncStateUpdated(ManageAccountsSettings.java:187)
20:43:39.733 Error AndroidRuntime 670 at com.android.settings.ManageAccountsSettings.onAccountsUpdated(ManageAccountsSettings.java:244)
20:43:39.733 Error AndroidRuntime 670 at android.accounts.AccountManager$10.run(AccountManager.java:826)
20:43:39.733 Error AndroidRuntime 670 at android.os.Handler.handleCallback(Handler.java:587)
20:43:39.733 Error AndroidRuntime 670 at android.os.Handler.dispatchMessage(Handler.java:92)
20:43:39.733 Error AndroidRuntime 670 at android.os.Looper.loop(Looper.java:123)
20:43:39.733 Error AndroidRuntime 670 at com.android.server.ServerThread.run(SystemServer.java:334)
20:43:39.733 Info Process 670 Sending signal. PID: 670 SIG: 9
20:43:39.733 Info ActivityThread 896 Removing dead content provider: subscribedfeeds
20:43:39.733 Info ActivityThread 896 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 1004 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 987 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 1073 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 1066 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 932 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 738 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 724 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 717 Removing dead content provider: settings
20:43:39.733 Info ServiceManager 746 service 'SurfaceFlinger' died
20:43:39.733 Info ServiceManager 746 service 'batteryinfo' died
20:43:39.733 Info ServiceManager 746 service 'entropy' died
20:43:39.733 Info ServiceManager 746 service 'telephony.registry' died
20:43:39.733 Info ServiceManager 746 service 'usagestats' died
20:43:39.733 Info ServiceManager 746 service 'epd' died
20:43:39.733 Info ServiceManager 746 service 'power' died
20:43:39.733 Info ServiceManager 746 service 'activity.senders' died
20:43:39.733 Info ServiceManager 746 service 'activity.services' died
20:43:39.733 Info ServiceManager 746 service 'activity.broadcasts' died
20:43:39.733 Info ServiceManager 746 service 'cpuinfo' died
20:43:39.733 Info ServiceManager 746 service 'content' died
20:43:39.733 Info ServiceManager 746 service 'package' died
20:43:39.733 Info ServiceManager 746 service 'statusbar' died
20:43:39.733 Info ServiceManager 746 service 'activity' died
20:43:39.733 Info ServiceManager 746 service 'meminfo' died
20:43:39.733 Info ServiceManager 746 service 'netstat' died
20:43:39.733 Info ServiceManager 746 service 'account' died
20:43:39.733 Info ServiceManager 746 service 'activity.providers' died
20:43:39.733 Info ServiceManager 746 service 'clipboard' died
20:43:39.733 Info ServiceManager 746 service 'backup' died
20:43:39.733 Info ServiceManager 746 service 'appwidget' died
20:43:39.733 Info ServiceManager 746 service 'audio' died
20:43:39.733 Info ServiceManager 746 service 'permission' died
20:43:39.733 Info ServiceManager 746 service 'input_method' died
20:43:39.733 Info ServiceManager 746 service 'battery' died
20:43:39.733 Info ServiceManager 746 service 'hardware' died
20:43:39.733 Info ServiceManager 746 service 'alarm' died
20:43:39.733 Info ServiceManager 746 service 'sensor' died
20:43:39.733 Info ServiceManager 746 service 'window' died
20:43:39.733 Info ServiceManager 746 service 'wifi' died
20:43:39.733 Info ServiceManager 746 service 'wallpaper' died
20:43:39.733 Info ServiceManager 746 service 'autoshutdown' died
20:43:39.733 Info ActivityThread 811 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 768 Removing dead content provider: settings
20:43:39.733 Info ServiceManager 746 service 'devicestoragemonitor' died
20:43:39.733 Info ServiceManager 746 service 'connectivity' died
20:43:39.733 Info ServiceManager 746 service 'accessibility' died
20:43:39.733 Info ServiceManager 746 service 'location' died
20:43:39.733 Info ServiceManager 746 service 'search' died
20:43:39.733 Info ServiceManager 746 service 'notification' died
20:43:39.733 Info ServiceManager 746 service 'mount' died
20:43:39.733 Info ServiceManager 746 service 'checkin' died
20:43:39.733 Error installd 756 eof
20:43:39.733 Error installd 756 failed to read size
20:43:39.733 Info installd 756 closing connection
20:43:39.843 Info Zygote 663 Exit zygote because system server (670) has terminated
20:43:40.170 Debug AndroidRuntime 1197
20:43:40.170 Debug AndroidRuntime 1197 >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I'm pretty stock. Only rooted with NookManager and NTGAppsAttack. All B&N apps enabled. A few other apps installed but not too much. What kind of customization do you have? Maybe we can track down what makes it work on your device.
some answers...
straygecko said:
Do you have B&N apps disabled? If so, reenable and try again. B&N messed with the android authentication stuff and has their own account types. Since you aren't even getting to the page where you select the account type (Google and two generic android) I suspect it might be looking for disabled B&N account stuff and crashing.
Click to expand...
Click to collapse
Here are the apps in my list:
ADB Konnect
Adding Machine
Appstore
Browser
Calculator
Calendar
ColorNote
Contacts
DeviceRegistrator
FBReader
Gallery
Gmail
Kingsoft Office
Library
Market
MemoryInfo-SwapCheck
Music
News and Weather
NOOK friends
Nook Touch Mod Manager
NookHWTest, version
Search Market
Settings
Shop
Social
Superuser
Swapper 2
Talk
TestCenterService
Zo Reader (This reminded me I want to uninstall this, I like FBReader...)
Tasks running:
ReLaunch com.harasoft.relaunch
SYSTEM(+4) android.process.acore
Gmail com.google.android.gm
Calendar(+1) com.android.calendar
SYSTEM (+2) android.process.media
Appstore com.amazon.venezia
Reader com.bn.nook.reader.activities
Home com.bn.nook.home
Dialer (+1) com.android.phone
ADB Konnect com.rockolabs.adbkonnect
Superuser com.noshufou.android.su
Google Partner Setup com.google.android.partnersetup
Services
Android System system
SYSTEM com.google.process.gapps
DeviceManagerService com.bn.devicemanager
TestCEnterService com.bn.serviceone
Settings com.android.settings
Market com.android.vending
SYSTEM com.bn.cloud.svc:svc
WafeformDownloaderService com.bn.waveformdownloader.svc
Android keyboard com.android.inputmethod.latin
Swapper 2 lv.n30.swapper2
com.bn.nook.affiledownloadservice com.bn.nook.affiledownloadservice
com.bn.demomode com.bn.demomode
Dialer com.android.phone
straygecko said:
The logcat isn't telling me much - is there anything earlier in the log of interest?
Click to expand...
Click to collapse
I will redo and post more lines, but nothing jumped out at me.
straygecko said:
/data/anr/traces.txt also might help but I'm not optimistic on that one.
Click to expand...
Click to collapse
I have ReLaunch set to show hidden files, do not hide known extensions and show all files.
When I tap on the data folder it comes up empty, i.e. there is no folder called anr to check for the traces.txt file.
longer logcat file
longer logcat file
RandyB201 said:
longer logcat file
Click to expand...
Click to collapse
OK, that's more helpful. It says you don't have an apk that handles the Add Account intent. It may have to do with your attempt to install AccountAndSyncSettings.apk from /system/app. Does AccountAndSyncSettings.apk still exist in /system/app? If so, try rebooting your NST and try the gmail work around again. If not, move it back there and reboot then try the gmail work around again.
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
RandyB201 said:
I have ReLaunch set to show hidden files, do not hide known extensions and show all files.
When I tap on the data folder it comes up empty, i.e. there is no folder called anr to check for the traces.txt file.
Click to expand...
Click to collapse
Realunch won't see things in that folder. You need to use a file manager tat has an option to explore with root privileges like ES File Explorer. But the logcat you posted was what I needed so no need to post the traces.txt
slogging on...
straygecko said:
OK, that's more helpful. It says you don't have an apk that handles the Add Account intent. It may have to do with your attempt to install AccountAndSyncSettings.apk from /system/app. Does AccountAndSyncSettings.apk still exist in /system/app?
Click to expand...
Click to collapse
yes it is still there
straygecko said:
If so, try rebooting your NST and try the gmail work around again. If not, move it back there and reboot then try the gmail work around again.t
Click to expand...
Click to collapse
I am geeky enough that I had already tried rebooting to fix the problem, but today I powered down the nook. I started it. The only thing I did before trying the gmail trick was start ADBKonnect and connect to the desktop.
The results were the same. My apps, task and service lists are the same with the exception that I uninstalled ZoReader. The task and service lists are identical, but there are a few differences in the "order".
Attaching the logcat file...
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
Realunch won't see things in that folder. You need to use a file manager tat has an option to explore with root privileges like ES File Explorer. But the logcat you posted was what I needed so no need to post the traces.txt[/QUOTE]
I installed and used Root File Manager to find the traces.txt file. It was empty.
Just an afterthought... should I use my NookManager microsd card to reinstall GappsAttack?
osowiecki said:
am start -a android.settings.SYNC_SETTINGS
It does not work or you have just missed something?
Got the command from decompiled "AccountAndSyncSettings.apk".
AndroidManifest.xml.
Click to expand...
Click to collapse
I tried adb shell am start -a android.settings.SYNC_SETTINGS.
Starting: Intent { act=android.settings.SYNC_SETTINGS }
Error: Activity not started, unable to resolve Intent { act=android.settings.SYN
C_SETTINGS flg=0x10000000 }
logcat attached...
RandyB201 said:
I tried adb shell am start -a android.settings.SYNC_SETTINGS.
Starting: Intent { act=android.settings.SYNC_SETTINGS }
Error: Activity not started, unable to resolve Intent { act=android.settings.SYN
C_SETTINGS flg=0x10000000 }
logcat attached...
Click to expand...
Click to collapse
On my NST this command works fine because it starts the Gapps Sync_settings (I have NTGAppsAttack installed and configured)
other commands fail because nook does know which intent goes goes to Oobe.apk and which to Google account settings (I guess, based on ddms error messages).
Connect your nook via adb and run 'ddms' from your Android folder.
It specifically informs you when it is trying to run part of Oobe.apk or Gapps and when these commands generate errors.
Tonight I'll try to look closer to this problem.
08-07 18:58:19.476: D/AndroidRuntime(1466): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
08-07 18:58:19.476: I/AndroidRuntime(1466): Heap size: -Xmx64m
08-07 18:58:19.476: D/AndroidRuntime(1466): CheckJNI is OFF
08-07 18:58:19.484: D/dalvikvm(1466): creating instr width table
08-07 18:58:19.539: D/AndroidRuntime(1466): --- registering native functions ---
08-07 18:58:19.562: I/NATIVE-EPD(1466): framebuffer_handle: 21
08-07 18:58:19.632: D/ddm-heap(1466): Got feature list request
08-07 18:58:19.695: I/ActivityManager(1052): Starting activity: Intent { act=android.settings.SYNC_SETTINGS flg=0x10000000 cmp=com.android.providers.subscribedfeeds/com.android.settings.ManageAccountsSettings }
08-07 18:58:19.710: D/AndroidRuntime(1466): Shutting down VM
08-07 18:58:19.710: D/dalvikvm(1466): DestroyJavaVM waiting for non-daemon threads to exit
08-07 18:58:19.710: D/dalvikvm(1466): DestroyJavaVM shutting VM down
08-07 18:58:19.710: D/dalvikvm(1466): HeapWorker thread shutting down
08-07 18:58:19.710: D/dalvikvm(1466): HeapWorker thread has shut down
08-07 18:58:19.710: D/jdwp(1466): JDWP shutting down net...
08-07 18:58:19.718: I/dalvikvm(1466): Debugger has detached; object registry had 1 entries
08-07 18:58:19.726: D/dalvikvm(1466): VM cleaning up
08-07 18:58:19.749: D/dalvikvm(1466): LinearAlloc 0x0 used 642220 of 5242880 (12%)
08-07 18:58:19.765: V/Activity(1052): performResume()
08-07 18:58:19.765: D/EPD#ActivityResume(1052): resetRegion 4
08-07 18:58:19.765: D/NATIVE-EPD(1052): epd_reset_region: 0x10
08-07 18:58:19.765: D/EPD#ActivityResume(1052): resetRegion 5
08-07 18:58:19.765: D/NATIVE-EPD(1052): epd_reset_region: 0x20
08-07 18:58:19.765: D/EPD#ActivityResume(1052): resetRegion 6
08-07 18:58:19.765: D/NATIVE-EPD(1052): epd_reset_region: 0x40
08-07 18:58:19.765: D/EPD#ActivityResume(1052): resetRegion 7
08-07 18:58:19.765: D/NATIVE-EPD(1052): epd_reset_region: 0x80
08-07 18:58:19.765: D/EPD#ActivityResume(1052): Disable EPD for 350ms!!!!!!!!
08-07 18:58:19.773: D/AccountSettings(1052): added authority com.android.contacts to accountType com.google
08-07 18:58:19.773: D/AccountSettings(1052): added authority calendar to accountType com.google
08-07 18:58:19.773: D/AccountSettings(1052): added authority gmail-ls to accountType com.google
08-07 18:58:19.773: D/AccountSettings(1052): added authority subscribedfeeds to accountType com.google
08-07 18:58:19.820: I/ActivityManager(1052): Start proc org.pocketworkstation.pckeyboard for service org.pocketworkstation.pckeyboard/.LatinIME: pid=1476 uid=10084 gids={}
08-07 18:58:19.820: W/InputManagerService(1052): Starting input on non-focused client [email protected] (uid=10026 pid=1115)
08-07 18:58:19.859: I/dalvikvm(1476): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38)
08-07 18:58:19.867: I/dalvikvm(1476): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=68)
08-07 18:58:19.898: I/ActivityManager(1052): Displayed activity com.android.providers.subscribedfeeds/com.android.settings.ManageAccountsSettings: 203 ms (total 203 ms)
08-07 18:58:19.921: I/PCKeyboard(1476): onCreate(), os.version=2.6.29-omap1
08-07 18:58:19.953: D/SurfaceFlinger(1052): Frame buffer posted; elapsed time = 12 msecs
08-07 18:58:20.023: E/BinaryDictionary(1476): Could not load native library jni_pckeyboard
08-07 18:58:20.031: D/dalvikvm(1476): +++ not scanning '/system/lib/libwebcore.so' for 'openNative' (wrong CL)
08-07 18:58:20.031: D/dalvikvm(1476): +++ not scanning '/system/lib/libmedia_jni.so' for 'openNative' (wrong CL)
08-07 18:58:20.031: D/dalvikvm(1476): +++ not scanning '/system/lib/libexif.so' for 'openNative' (wrong CL)
08-07 18:58:20.031: D/dalvikvm(1476): +++ not scanning '/system/lib/libsrec_jni.so' for 'openNative' (wrong CL)
08-07 18:58:20.031: W/dalvikvm(1476): No implementation found for native Lorg/pocketworkstation/pckeyboard/BinaryDictionary;.openNative (Ljava/nio/ByteBuffer;III)I
08-07 18:58:20.031: W/BinaryDictionary(1476): Failed to load native dictionary
08-07 18:58:20.031: W/BinaryDictionary(1476): java.lang.UnsatisfiedLinkError: openNative
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.BinaryDictionary.openNative(Native Method)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.BinaryDictionary.loadDictionary(BinaryDictionary.java:145)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.BinaryDictionary.loadDictionary(BinaryDictionary.java:173)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.BinaryDictionary.<init>(BinaryDictionary.java:78)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.Suggest.<init>(Suggest.java:109)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.LatinIME.initSuggest(LatinIME.java:521)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.LatinIME.onCreate(LatinIME.java:422)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2780)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.app.ActivityThread.access$3200(ActivityThread.java:119)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1917)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.os.Handler.dispatchMessage(Handler.java:99)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.os.Looper.loop(Looper.java:123)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.app.ActivityThread.main(ActivityThread.java:4363)
08-07 18:58:20.031: W/BinaryDictionary(1476): at java.lang.reflect.Method.invokeNative(Native Method)
08-07 18:58:20.031: W/BinaryDictionary(1476): at java.lang.reflect.Method.invoke(Method.java:521)
08-07 18:58:20.031: W/BinaryDictionary(1476): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
08-07 18:58:20.031: W/BinaryDictionary(1476): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
08-07 18:58:20.031: W/BinaryDictionary(1476): at dalvik.system.NativeStart.main(Native Method)
08-07 18:58:20.039: E/ActivityThread(1476): Failed to find provider info for com.android.contacts
08-07 18:58:25.132: D/dalvikvm(1115): GC freed 6626 objects / 428208 bytes in 77ms
08-07 18:58:30.117: D/dalvikvm(1132): GC freed 2351 objects / 137136 bytes in 55ms
Click to expand...
Click to collapse
RandyB201 said:
yes it is still there
I am geeky enough that I had already tried rebooting to fix the problem, but today I powered down the nook. I started it. The only thing I did before trying the gmail trick was start ADBKonnect and connect to the desktop.
The results were the same. My apps, task and service lists are the same with the exception that I uninstalled ZoReader. The task and service lists are identical, but there are a few differences in the "order".
Attaching the logcat file...
...
I installed and used Root File Manager to find the traces.txt file. It was empty.
Just an afterthought... should I use my NookManager microsd card to reinstall GappsAttack?
Click to expand...
Click to collapse
Logcat shows the same thing. No apk to handle the android.settings.ADD_ACCOUNT_SETTINGS intent. It really sounds like your AccountAndSyncSettings.apk got mangled along the way somehow. Reinstalling NTGAppsAttack won't fix that as AccountAndSyncSettings.apk is part of the stock B&N stuff. A logcat from Android startup (package manager messages) could help pin down what's wrong with the apk you have but knowing that or not the fix would be the same. Either restore to prior to installing NTGAppsAttack and reinstall NTGAppsAttack. Or you could extract the AccountAndSyncSettings.apk from the B&N 1.2.1 update file, copy it to your /system/app folder, reboot and try the gmail workaround again. The first has the highest probability of success but the second isn't too much work and has a pretty good chance of fixing it.
---------- Post added at 09:12 PM ---------- Previous post was at 09:05 PM ----------
osowiecki said:
On my NST this command works fine because it starts the Gapps Sync_settings (I have NTGAppsAttack installed and configured)
other commands fail because nook does know which intent goes goes to Oobe.apk and which to Google account settings (I guess, based on ddms error messages).
Connect your nook via adb and run 'ddms' from your Android folder.
It specifically informs you when it is trying to run part of Oobe.apk or Gapps and when these commands generate errors.
Tonight I'll try to look closer to this problem.
Click to expand...
Click to collapse
The SYNC_SETTINGS intent is handled by AccountAndSyncSettings.apk which is part of stock B&N and isn't installed by NTGAppsAttack. I think this has something to do with the B&N account stuff they patched into android. Seeing from your profile you're not in the US or UK do you even have your device registered with B&N? Not having a B&N account setup might be what's making your device work as sync settings won't be trying to display a B&N account in its list of accounts.
I have the same issue. I tried multiple ways and apps to get to the sync settings. but my nst just reboots at every attempt.
osowiecki said:
am start -a android.settings.SYNC_SETTINGS
It does not work or you have just missed something?
Got the command from decompiled "AccountAndSyncSettings.apk".
AndroidManifest.xml.
i tried this command in terminal app within nst. and it rebooted right away, after a brief pause.
straygecko said:
The SYNC_SETTINGS intent is handled by AccountAndSyncSettings.apk which is part of stock B&N and isn't installed by NTGAppsAttack. I think this has something to do with the B&N account stuff they patched into android. Seeing from your profile you're not in the US or UK do you even have your device registered with B&N? Not having a B&N account setup might be what's making your device work as sync settings won't be trying to display a B&N account in its list of accounts.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
my device is uk. just bought from argos last month rooted with nookmanager. one issue that i notice is that some dialog boxes display empty, possibly because foreground/background colours are same/similar. i can't remember whether i had this problem before rooting.
moving backward..
straygecko said:
Logcat shows the same thing. No apk to handle the android.settings.ADD_ACCOUNT_SETTINGS intent. It really sounds like your AccountAndSyncSettings.apk got mangled along the way somehow. Reinstalling NTGAppsAttack won't fix that as AccountAndSyncSettings.apk is part of the stock B&N stuff. A logcat from Android startup (package manager messages) could help pin down what's wrong with the apk you have but knowing that or not the fix would be the same. Either restore to prior to installing NTGAppsAttack and reinstall NTGAppsAttack. Or you could extract the AccountAndSyncSettings.apk from the B&N 1.2.1 update file, copy it to your /system/app folder, reboot and try the gmail workaround again. The first has the highest probability of success but the second isn't too much work and has a pretty good chance of fixing it.
Click to expand...
Click to collapse
ok. the second option did not work. so, i am trying to reset the nook and start over.
i erased and deregistered it. after reboot i went through the setup process. then i rebooted with my nook manager card and rooted. rebooted and all looks good.
then i rebooted with the nookmanager card to install gapps attack
after reboot, i am stuck at step 16. Go back to ReLaunch and open the Market
when i do this it shows me the license screen i hit accept, then i just get a server error.
gmail and contacts apps seems to be working fine. when i open calendar, it opens but there is an image of an sd card superimposed over the top of the calendar -- i dont remember it doing htat before. talk will not open, it just briefly flashes the screen and goes back to the applications in relaunch.
I have done this entire process several times now and the results have been exactly the same each time???
update: i just tried this with a new gmail account, and the results were the same...
as i have thought about this most of yesterday and today, it seems to me that something is not getting cleared / deleted in the reset process...
aug-12-13 update: i installed nook color tools, used it to uninstall the market update, rebooted, rebooted w nook mgr card, reinstalled gappsattack. no change...
i am not sure if this is significant, but i noticed something else that supports my theory that not everything is getting erased in the reset process. when i open contacts, my google contacts from my original gmail acct are still in the list even though, i deregistered/erased and used a different gmail acct when i did this yesterday...
back to my original question...
I understand that B&N has modified the AccountAndSyncSettings.apk on the nook to fence it in to their company.
Has anyone tried replacing the AccountAndSyncSettings.apk in their nook with one from another Android 2.1 device?
I assume this would break the B&N apps, but I wonder if it would enable apps that need to access that apk...

[SOLVED][Q] Commands not properly executing

EDIT:
The problem was that i was trying to read a line from the inputreader, when there was no line, so it was waiting for a response there...
Hello,
I am currently building an app to fix a little problem that exists on some devices with the wifi-mac and bluetooth addresses constantly changing (for me it's a N4 but I read somewhere that there are other devices with that problem too)
The thing the app should do is (steps taken from another xda thread: http://forum.xda-developers.com/showpost.php?p=43164157&postcount=1 )
- Mount /persist
- create the folders wifi and bluetooth
- create a text file in each of these directories containing the addresses that should be used in future
- fix the owners and permissions of these files and directories
- execute /system/bin/conn_init as su
The app is mostly done but somehow not working at all.
Everything from generating random adresses to saving them in a temporary file seems to work fine, but as soon as I try to mount the persist directory, the app stops to react.
At first, this was the first thing done by the SU Shell class that I wrote for executing su shell commands, so I thought that might be not working, but when I let that execute echo test it returns test just fine...
The code that is used could be expressed like that (this is missing some debug info and strings that get passed, but it should technically have the same result):
Code:
try {
shell = Runtime.getRuntime().exec("su");
outputStream = new DataOutputStream(shell.getOutputStream());
inputStream = new BufferedReader(new InputStreamReader(shell.getInputStream()));
outputStream.writeBytes("mount /dev/block/mmcblk0p20 /persist");
outputStream.flush();
} catch (IOException e) {
e.printStackTrace();
}
The attached zip file contains my main activity and the before mentioned su shell.
The complete source code of the app is available via my git server: http://greensserver.redirectme.net/greenchris/WiFi-MAC-and-Bluetooth-Adress-Fix.git
Does anybody have an idea why this isn't working?
Greetings
GreenChris
Edit:
I forgot to add the logcat...
Code:
04-09 23:33:21.289 3903-3903/com.janchristiangruenhage.macfixer I/art﹕ Late-enabling -Xcheck:jni
04-09 23:33:21.791 3903-3949/com.janchristiangruenhage.macfixer D/OpenGLRenderer﹕ Render dirty regions requested: true
04-09 23:33:21.797 3903-3903/com.janchristiangruenhage.macfixer D/Atlas﹕ Validating map...
04-09 23:33:21.951 3903-3949/com.janchristiangruenhage.macfixer I/Adreno-EGL﹕ : QUALCOMM Build: 10/28/14, c33033c, Ia6306ec328
04-09 23:33:21.953 3903-3949/com.janchristiangruenhage.macfixer I/OpenGLRenderer﹕ Initialized EGL, version 1.4
04-09 23:33:21.985 3903-3949/com.janchristiangruenhage.macfixer D/OpenGLRenderer﹕ Enabling debug mode 0
04-09 23:33:22.318 3903-3903/com.janchristiangruenhage.macfixer I/Timeline﹕ Timeline: Activity_idle id: [email protected] time:14543691
04-09 23:33:31.781 3903-3919/com.janchristiangruenhage.macfixer I/art﹕ Background sticky concurrent mark sweep GC freed 11333(680KB) AllocSpace objects, 3(44KB) LOS objects, 13% free, 4MB/5MB, paused 5.706ms total 39.550ms
04-09 23:33:31.843 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ address-bytes generated
04-09 23:33:43.923 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ save .bdaddr
04-09 23:33:43.925 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ address written: .bdaddr
04-09 23:33:43.954 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ su shell started
04-09 23:33:43.955 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ added outputstream
04-09 23:33:43.957 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ added inputstreamreader
04-09 23:33:43.957 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ echo test
04-09 23:33:43.973 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ test
04-09 23:33:43.974 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ mount /dev/block/mmcblk0p20 /persist

Categories

Resources